JP2013004991A - Communication control method, communication control device, and communication control system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To automatically control permission or non-permission of communication depending on a context of a called person.SOLUTION: A communication control device 100 monitors a context of an incoming side terminal R if it has detected that the incoming side terminal R did not accept a call. Then, the communication control device 100 makes the incoming side terminal R and an originating side terminal S perform call-back communication only if the context of the incoming side terminal R has become the state of incoming call permission. Because the communication control device 100 thus automatically determines the state of incoming call permission of the incoming side terminal R, a user of the incoming side terminal R has no need to bother to remember necessity of a callback. In addition, if the incoming side terminal R is in the state of incoming call non-permission, callback communication is not performed; and therefore the user of the incoming side terminal R does not suffer from receiving a callback request when it is in the state of incoming call non-permission.

Description

  The present invention relates to a communication control method, a communication control device, and a communication control system for controlling communication.

  In the field of communication using telephones, when a communication terminal user receives a call to the communication terminal, it determines whether or not it is in a state where it can permit incoming calls. I refused and later made a call back to the caller.

  Conventionally, there has been a technique in which a user of a communication terminal registers his / her current incoming / outgoing state in a server. In addition, there is a technique for reducing the trouble that the caller himself / herself determines whether or not the call can be received by notifying the server of the call from the caller and automatically determining whether or not the call can be received by the server (for example, the following patent document) 1).

  In addition, as a related technique, there is a technique in which the caller can obtain the information of the callee before making the call so that the caller can determine the validity of the call (for example, See Patent Document 2 below).

Japanese Patent No. 4091517 JP 2008-011148 A

  However, in the above-described prior art, since the callback after the incoming call is rejected is not taken into consideration, the user of the communication terminal determines whether or not he / she is in an incoming call permission state with respect to the callback. There was a problem that it took time and effort. In addition, each time the user's situation changes, it is necessary to reset the incoming / outgoing state in the server, and there is a problem that it takes time to change the setting. Further, when the user's situation changes, if the user does not change the setting, there is a problem that an incoming call not desired by the user is performed.

  An object of the present invention is to provide a communication control method, a communication control apparatus, and a communication control system for making a call back when a callee is in an incoming call permission state in order to solve the above-described problems caused by the prior art. .

  In order to solve the above-described problems and achieve the object, according to one aspect of the present invention, the computer detects that the second terminal has not accepted a call from the first terminal, and the first terminal When it is detected that the second terminal has not accepted the outgoing call from the terminal, the second terminal is in the incoming call permission state by referring to storage means for storing the context indicating the incoming call permission or non-permission for each terminal. A communication control method and a communication control apparatus are proposed for transmitting a callback request to the first terminal to the second terminal when it is determined that the incoming call is permitted.

  In order to solve the above-described problems and achieve the object, according to one aspect of the present invention, a first device for controlling outgoing / incoming calls between terminals and a second for controlling callback to a source terminal. The second device has a storage means for storing a context indicating permission or non-permission for each terminal, and makes a call from the first terminal. When it is detected that the second terminal has not accepted and it is detected that the second terminal has not accepted a call from the first terminal, the second terminal is permitted to receive the call by referring to the storage means. And if it is determined that the incoming call is permitted, a callback request to the first terminal is transmitted to the second terminal, and the first device receives the request from the first terminal. Communication notifying the second device that the call has been sent to the second terminal Your system is proposed.

  In order to solve the above-described problems and achieve the object, according to one aspect of the present invention, a first device for controlling outgoing / incoming calls between terminals and a second device for controlling callback to a caller terminal Are connected to the communication control system, and the second device has storage means for storing a context indicating permission or non-permission for each terminal, and makes a second call from the first terminal. When it is detected that the terminal has not accepted and it is detected that the second terminal has not accepted a call from the first terminal, the second terminal is in an incoming call permission state by referring to the storage means And if it is determined that the incoming call is permitted, a callback request to the first terminal is transmitted to the first device, and the first device receives the second request from the first terminal. To the second device that the call was sent to the terminal A communication control system for notifying a callback request to a second device is proposed.

  According to one aspect of the present invention, there is an effect that a call back is performed when the callee is in a call-permitted state.

FIG. 1 is an explanatory view showing the contents of transmission of a callback request to a callee by the communication control device. FIG. 2 is an explanatory diagram showing a configuration example of the communication system C shown in FIG. FIG. 3 is a block diagram of a hardware configuration example of each server included in the communication control apparatus 100 according to the embodiment. FIG. 4 is an explanatory diagram showing the stored contents of the location DB stored in the context management server 110. FIG. 5 is an explanatory diagram showing the storage contents of the context DB stored in the context management server 110. FIG. 6 is an explanatory diagram showing the storage contents of the monitoring context DB stored in the context management server 110. FIG. 7 is an explanatory diagram showing the storage contents of the call control DB stored in the callback control server 120. FIG. 8 is an explanatory diagram showing the stored contents of the callback DB stored in the callback control server 120. FIG. 9 is a block diagram illustrating a functional configuration of the communication control apparatus 100. FIG. 10 is an explanatory diagram of the contents of the transmission example 1 of the callback request to the callee by the communication control apparatus 100 according to the first embodiment. FIG. 11 is an explanatory diagram of the contents of the transmission example 2 of the callback request to the callee by the communication control apparatus 100 according to the first embodiment. FIG. 12 is a sequence diagram illustrating details of communication contents of each server when a call is transmitted from the originating terminal S in the first embodiment. FIG. 13 is a sequence diagram illustrating details of communication contents of each server when a callback request is transmitted by the callback control server 120 according to the first embodiment. FIG. 14 is a flowchart illustrating details of the processing contents of the callback control processing of the callback control server 120 according to the first embodiment. FIG. 15 is a flowchart illustrating details of the processing contents of the monitoring context registration processing of the context management server 110 according to the first embodiment. FIG. 16 is a flowchart illustrating details of processing contents of a callback trigger notification transmission process of the context management server 110 according to the first embodiment. FIG. 17 is an explanatory diagram of a screen display example of the communication terminal T according to the second embodiment. FIG. 18 is an explanatory diagram of the contents stored in the context DB 112 according to the second embodiment. FIG. 19 is an explanatory diagram showing the contents stored in the monitoring context DB 113 including the monitoring context regarding cancellation of the callback request. FIG. 20 is an explanatory diagram showing the stored contents of the call control DB 121 including call requirements and urgency. FIG. 21 is an explanatory diagram (part 1) of the contents of the transmission example 1 of the callback request to the callee by the communication control apparatus 100 according to the second embodiment. FIG. 22 is an explanatory diagram (part 2) of the contents of the transmission example 1 of the callback request to the callee by the communication control apparatus 100 according to the second embodiment. FIG. 23 is an explanatory diagram of the contents of the transmission example 2 of the callback request to the callee by the communication control apparatus 100 according to the second embodiment. FIG. 24 is a sequence diagram (part 1) illustrating details of communication contents of each server when a call is transmitted from the calling terminal S in the second embodiment. FIG. 25 is a sequence diagram (part 2) illustrating details of communication contents of each server when a call is transmitted from the originating terminal S in the second embodiment. FIG. 26 is a sequence diagram illustrating details of communication contents of each server when a callback request is transmitted by the callback control server 120 according to the second embodiment. FIG. 27 is a sequence diagram illustrating details of communication contents of each server when a callback request is canceled in the second embodiment. FIG. 28 is a flowchart illustrating details of processing contents of the incoming call control processing of the callback control server 120 according to the second embodiment. FIG. 29 is a flowchart illustrating details of the processing contents of the callback control processing of the callback control server 120 according to the second embodiment. FIG. 30 is a flowchart illustrating details of the processing contents of the monitoring context registration processing of the context management server 110 according to the second embodiment. FIG. 31 is a flowchart illustrating details of processing contents of a callback trigger notification transmission process of the context management server 110 according to the second embodiment.

  Exemplary embodiments of a communication control method, a communication control apparatus, and a communication control system according to the present invention will be explained below in detail with reference to the accompanying drawings. The communication control device acquires a context indicating the state of the receiving terminal so that the callback is performed when the receiving terminal is in the incoming call permission state.

  Next, the communication control device refers to the context in the case where the previously held destination terminal is in a call-permitted state and the acquired context of the called terminal so that the state of the called terminal is determined. It is determined whether the incoming call is permitted or not. Then, the communication control apparatus transmits a callback request to the receiving side terminal only when it is determined that the state of the receiving side terminal is an incoming call permission state. As a result, since the callback request is not transmitted when the receiving terminal is in a state in which the incoming call is not permitted, the trouble of the recipient can be reduced.

(Contents of transmission of callback request to callee by communication control device)
First, the contents of transmission of a callback request to a callee by the communication control device will be described with reference to FIG. FIG. 1 is an explanatory view showing the contents of transmission of a callback request to a callee by the communication control device.

  In FIG. 1, a communication terminal T (hereinafter referred to as “calling side terminal S”) on the side that originates a call and a communication terminal T (hereinafter referred to as “incoming side terminal R”) that receives a call, 1 shows a communication system C including a control device 100.

  The caller terminal S is a terminal that sends a call to the callee terminal R by an operation of the user of the caller terminal S. The receiving terminal R is a terminal to which a call transmitted from the calling terminal S is received. The receiving terminal R has a sensor that acquires the context of the receiving terminal R. The context is information indicating the state of the own terminal (and the user of the own terminal). For example, the location where the receiving terminal R is (and the place where the user of the receiving terminal R is located) or the receiving terminal. This is information indicating whether or not R is busy (and whether or not the user of the receiving terminal R is busy). Hereinafter, the user of the caller terminal S is referred to as “sender”. In the following, the user of the receiving terminal R is referred to as “receiver”.

  The communication control device 100 is a device that acquires the context of the receiving terminal R and determines whether the receiving terminal R is permitted or not permitted. Further, the communication control device 100 is a device that transmits a callback request when the receiving terminal R is in an incoming call permission state.

  Specifically, for example, the communication control device 100 is a device that includes a context management server 110 and a callback control server 120. Here, the context management server 110 is a server that manages the context of the receiving terminal R. In addition, the context management server 110 is a server that maintains a monitoring context DB that stores a context in the case where the incoming call is permitted for each communication terminal T, and detects that the communication terminal T is in a communication-permitted state.

  The callback control server 120 is a server that stores a callback DB that stores the telephone number of the calling terminal S for callback. Further, when the context control server 110 notifies the callback control server 120 that the receiving terminal R has been permitted to receive a call, the callback control server 120 communicates callback to the receiving terminal R and the calling terminal S. It is a server to perform.

  In addition, the communication control apparatus 100 may further include a call control server 130. The call control server 130 is a server that connects and disconnects communication between the calling terminal S and the receiving terminal R. Then, the callback control server 120 may cause the receiving terminal R and the calling terminal S to perform callback communication via the call control server 130. Specifically, the call control server 130 causes the receiving terminal R and the calling terminal S to perform callback communication by so-called third-party call control. However, the communication control device 100 may be a single device including the functions of the context management server 110, the callback control server 120, and the call control server 130.

  Here, assuming that the call transmitted from the calling terminal S to the receiving terminal R is not accepted by the receiving terminal R, the communication control apparatus 100 transmits a callback request to the called party. The contents will be described.

  (1) The communication control apparatus 100 detects that a call from the calling terminal S to the receiving terminal R has not been accepted by the receiving terminal R. Specifically, for example, the communication control apparatus 100 is notified by the incoming terminal R that there is an event that rejects the incoming call from the outgoing terminal S to the incoming terminal R. It is detected that the receiving terminal R has not accepted the call. Specifically, for example, when the communication control apparatus 100 controls a call between the calling terminal S and the receiving terminal R by the call control server 130, the call control server 130 transfers to the receiving terminal R. An event that rejects the incoming call is detected, and it is detected that the call has not been accepted by the called terminal R.

  When the communication control apparatus 100 detects that the call from the caller terminal S to the callee terminal R has not been accepted by the callee terminal R, the communication control apparatus 100 starts determining whether or not the callback request can be transmitted. The context of terminal R is monitored.

  (2) Here, the receiving terminal R notifies the communication control apparatus 100 of the context of the receiving terminal R. Here, the context is information indicating the location of the communication terminal T. For example, the communication control apparatus 100 has a table that stores a location corresponding to a wireless LAN SSID (Service Set IDentifier), and the location can be identified from the SSID of the wireless LAN with reference to the table.

  Further, for example, the communication control apparatus 100 has a table that stores a GPS (Global Positioning System) coordinate range corresponding to a location, and the location can be identified from the GPS coordinates by referring to the table.

  Further, for example, an infrared receiver is provided at a target location, and the communication control apparatus 100 has a table for storing a location corresponding to the identifier of the infrared receiver, and the location from the identifier of the infrared receiver with reference to the table Can be specified.

  Note that the trigger that the receiving terminal R notifies the context is, for example, when the context of the receiving terminal R has changed. Further, by using only a change in context when entering a specific location as a trigger, it is possible to stabilize the operation of the communication control device so as not to detect the case where the called party repeatedly enters and exits the specific location. Further, for example, the receiving terminal R may notify the context at regular intervals.

  (3) Next, when receiving the notification of the context of the receiving terminal R, the communication control device 100 refers to the monitoring context DB (DataBase) stored in advance, and the receiving terminal R is in a state where the incoming call is permitted. It is determined whether or not. Here, the communication control device 100 stores the location indicated by the context notified from the receiving terminal R as a break room, and the monitoring context DB stores that the incoming call is permitted except for the conference room. It is determined that the side terminal R is in an incoming call permission state. However, the communication control apparatus 100 may further determine whether or not the caller terminal S is in an incoming call permission state.

  (4) Then, the communication control device 100 transmits a callback request to the receiving terminal R if the receiving terminal R is in the incoming call permission state. Here, the callback request is a message including the telephone number of the calling terminal S, for example. Further, the callback request may be, for example, an application that executes a callback to the calling terminal S. The callback request may be an incoming request from the call control server 130, for example. However, when the communication control apparatus 100 determines in (3) whether or not the caller terminal S is in an incoming call permission state, the communication control apparatus 100 is in a case where both the callee terminal R and the caller terminal S are in an incoming call permission state. For example, a callback request may be transmitted to the called terminal R.

  (5) The receiving terminal R that has received the callback request starts a call with the calling terminal S. Specifically, for example, if the callback request is a message including the telephone number of the calling terminal S, the receiving terminal R receives an operation of sending a call to the telephone number included in the message by the called party. Then, a call with the calling terminal S is started.

  Specifically, for example, if the callback request is an application that executes a callback to the calling terminal S, the receiving terminal R receives the operation of executing the application by the called party, A call with the terminal S is started. Specifically, for example, if the callback request is an incoming request from the call control server 130, the receiving terminal R receives an operation for permitting the incoming request by the called party, Start a call.

  In this way, the communication control apparatus 100 acquires the context of the receiving terminal R and automatically determines whether or not the receiving terminal R is in an incoming call permission state. Then, the communication control apparatus 100 transmits a callback request to the receiving terminal R only when it is determined that the receiving terminal R is in an incoming call permission state. Therefore, it is not necessary for the user of the receiving terminal R to determine whether the incoming call is permitted or not, and the time and effort of the user of the receiving terminal R can be reduced. In addition, the user of the receiving terminal R does not suffer the inconvenience of receiving a callback request even though the incoming call is not permitted.

  In addition, if there is another system that holds the context of the originating terminal S or the terminating terminal R, the communication control apparatus 100 acquires the context from the other system and determines the incoming permission status of the terminating terminal R. It may be used as an index.

  In FIG. 1, there is one outgoing terminal S and one incoming terminal R. However, in the case of a telephone conference or a video conference, it is assumed that there are a plurality of incoming terminals R and the communication control device 100 can be applied. In FIG. 1, a voice telephone is taken as an example, but the communication control apparatus 100 can also be applied to voice mail and text mail.

(Configuration example of the communication system C shown in FIG. 1)
Next, a configuration example of the communication system C shown in FIG. 1 will be described with reference to FIG.

  FIG. 2 is an explanatory diagram showing a configuration example of the communication system C shown in FIG. As shown in FIG. 2, the communication system C includes a plurality of wireless LANs 201, a transmission side terminal S, a reception side terminal R, a context management server 110, a callback control server 120, a call control server 130, and others. System 202. The context management server 110 includes a location DB 111, a context DB 112, and a monitoring context DB 113. The callback control server 120 includes a call control DB 121 and a callback DB 122.

  The context management server 110 is a server that identifies a location corresponding to the SSID of the wireless LAN 201 notified from the communication terminal T based on the location DB. The context management server 110 is a server that stores and manages the context of the communication terminal T including the specified location in the context DB 112. In addition, the context management server 110 is a server that maintains a monitoring context DB 113 that stores a context when the incoming call permission for each communication terminal T is stored, and detects that the communication terminal T is in a communication-permitted state.

  The callback control server 120 is a server that determines whether to perform callback based on the call control DB 121. The callback control server 120 is a server that stores a callback DB that stores the telephone number of the calling terminal S for callback. Further, when the callback control server 120 determines that the callback is to be performed and then the context management server 110 notifies that the receiving terminal R is in the incoming call permission state, the callback control server 120 and the calling terminal This is a server that allows terminal S to perform callback communication.

  The call control server 130 is a server that connects and disconnects communication between the calling terminal S and the receiving terminal R. The callback control server 120 may cause the receiving terminal R and the calling terminal S to perform callback communication via the call control server 130. Specifically, the call control server 130 causes the receiving terminal R and the calling terminal S to perform callback communication by so-called third-party call control.

  The caller terminal S is a terminal that sends a call to the callee terminal R by an operation of the user of the caller terminal S. The receiving terminal R is a terminal to which a call transmitted from the calling terminal S is received. Each communication terminal T is a terminal that has a sensor that acquires the context of the terminal itself and transmits the acquired context to the communication control apparatus 100 via the wireless LAN 201. The context includes, for example, the SSID of the wireless LAN 201 as information indicating the location of the terminal. The other system 202 is a system that maintains the context of the originating terminal S or the terminating terminal R. For example, there is a system that manages the requirements and urgency of a call originated by the originating terminal S.

(Hardware configuration example of communication control device 100)
Next, a hardware configuration example of the communication control apparatus 100 will be described with reference to FIG. As shown in FIG. 1, the communication control device 100 is a device that includes a context management server 110, a callback control server 120, and a call control server 130.

  FIG. 3 is a block diagram of a hardware configuration example of each server included in the communication control apparatus 100 according to the embodiment. In FIG. 3, for example, assuming the context management server 110, the context management server 110 includes a CPU (Central Processing Unit) 301, a ROM (Read-Only Memory) 302, a RAM (Random Access Memory) 303, and a magnetic disk. A drive 304, a magnetic disk 305, an optical disk drive 306, an optical disk 307, a display 308, an I / F (Interface) 309, a keyboard 310, a mouse 311, a scanner 312 and a printer 313 are provided. Yes. Each component is connected by a bus 320.

  Here, the CPU 301 governs overall control of each server. The ROM 302 stores a program such as a boot program. The RAM 303 is used as a work area for the CPU 301. Further, the RAM 303 of the context management server 110 stores a location DB 111, a context DB 112, and a monitoring context DB 113. The magnetic disk drive 304 controls the reading / writing of the data with respect to the magnetic disk 305 according to control of CPU301. The magnetic disk 305 stores data written under the control of the magnetic disk drive 304.

  The optical disk drive 306 controls the reading / writing of the data with respect to the optical disk 307 according to control of CPU301. The optical disk 307 stores data written under the control of the optical disk drive 306, and causes the computer to read data stored on the optical disk 307.

  The display 308 displays data such as a document, an image, and function information as well as a cursor, an icon, or a tool box. As the display 308, for example, a CRT, a TFT liquid crystal display, a plasma display, or the like can be adopted.

  An interface (hereinafter abbreviated as “I / F”) 309 is connected to a network 214 such as a LAN (Local Area Network), a WAN (Wide Area Network), and the Internet through a communication line. Connected to other devices. The I / F 309 controls an internal interface with the network 214 and controls data input / output from an external device. For example, a modem or a LAN adapter may be employed as the I / F 309.

  The keyboard 310 includes keys for inputting characters, numbers, various instructions, and the like, and inputs data. Moreover, a touch panel type input pad or a numeric keypad may be used. The mouse 311 performs cursor movement, range selection, window movement, size change, and the like. A trackball or a joystick may be used as long as they have the same function as a pointing device.

  The scanner 312 optically reads an image and takes in the image data into each server. The scanner 312 may have an OCR (Optical Character Reader) function. The printer 313 prints image data and document data. As the printer 313, for example, a laser printer or an ink jet printer can be employed.

  In FIG. 3, for example, assuming a callback control server 120, the callback control server 120 includes a CPU 301, a ROM 302, a RAM 303, a magnetic disk drive 304, a magnetic disk 305, an optical disk drive 306, and an optical disk. 307, a display 308, an interface (I / F) 309, a keyboard 310, a mouse 311, a scanner 312, and a printer 313. Each component is connected by a bus 320. Since the contents of each component are the same as the contents described assuming the context management server 110, the description is omitted. However, the RAM 303 of the callback control server 120 stores a call control DB 121 and a callback DB 122.

  In FIG. 3, for example, assuming a call control server 130, the call control server 130 includes a CPU 301, a ROM 302, a RAM 303, a magnetic disk drive 304, a magnetic disk 305, an optical disk drive 306, and an optical disk 307. A display 308, an I / F (Interface) 309, a keyboard 310, a mouse 311, a scanner 312, and a printer 313. Each component is connected by a bus 320. Since the contents of each component are the same as the contents described assuming the context management server 110, the description is omitted.

(Storage contents of location DB)
Next, contents stored in the location DB stored in the context management server 110 will be described with reference to FIG. The location DB is a DB that the communication control device 100 (context management server 110) refers to when estimating the location where the communication terminal T is located.

  FIG. 4 is an explanatory diagram showing the stored contents of the location DB stored in the context management server 110. As shown in FIG. 4, the location DB 111 has location items in association with SSID (Service Set IDentifier) items, and configures a record for each SSID.

  The SSID item stores an identifier of an access point in the wireless LAN (hereinafter referred to as “SSID”). The SSID is a maximum of 32 alphanumeric characters. The location item stores the name of the location where the access point identified by the SSID is installed.

(Contents stored in the context DB)
Next, the storage contents of the context DB stored in the context management server 110 will be described with reference to FIG. The context DB is a DB that the communication control device 100 (context management server 110) refers to when acquiring the current context of the communication terminal T.

  FIG. 5 is an explanatory diagram showing the storage contents of the context DB stored in the context management server 110. As shown in FIG. 5, the context DB 112 has a value item and a callback ID item in association with a context type item for each communication terminal T, and records each time a context is received from the communication terminal T. Configure.

  In the context type item, the type of context of the communication terminal T is stored. Specifically, the types of context include “location” that indicates a location where the communication terminal T is located, and “phone” that indicates whether the communication terminal T is in a call.

  In the value item, a state corresponding to the type of context is stored. Specifically, “Office A” is stored in the value item corresponding to “Location” of the context type. Also, “idle” is stored in the value item corresponding to the context type “phone”. “Idle” indicates a state where the calling terminal S or the receiving terminal R is not talking. In the callback ID item, an identifier for identifying a callback is stored.

(Storage contents of monitoring context DB)
Next, the storage content of the monitoring context DB stored in the context management server 110 will be described with reference to FIG. The monitoring context DB is a DB that the communication control device 100 (context management server 110) refers to when determining whether or not the communication terminal T is in an incoming call permission state.

  FIG. 6 is an explanatory diagram showing the storage contents of the monitoring context DB stored in the context management server 110. As shown in FIG. 6, the monitoring context DB 113 has a user ID item, a context type item, and a value item in association with the callback ID item, and a callback opportunity notification request from the callback control server 120. Each time a notification is sent, a record is composed.

  In the callback ID item, an identifier for identifying a callback is stored. In the user ID item, an identifier of the calling terminal S or the receiving terminal R is stored. In the context type item, the type of context of the calling terminal S or the receiving terminal R is stored. In the value item, a state corresponding to the type of context is stored.

(Storage contents of call control DB)
Next, the contents stored in the call control DB stored in the callback control server 120 will be described with reference to FIG. The call control DB is a DB that the communication control device 100 (callback control server 120) refers to when determining whether or not the communication terminal T is in a state where incoming calls are not permitted.

  FIG. 7 is an explanatory diagram showing the storage contents of the call control DB stored in the callback control server 120. As shown in FIG. 7, the call control DB 121 has a value item in association with a context type item for each communication terminal T, and a context condition (hereinafter, referred to as an incoming call rejection state from the communication terminal T). Each time a “call control condition” is received, a record is formed.

  A context type is stored in the context type item. Specifically, the types of context include “location” that indicates a location where the communication terminal T is located, and “phone” that indicates whether the communication terminal T is in a call.

  The value item stores the state of the context type corresponding to the state where the communication terminal T is not permitted to receive a call. Specifically, “conference room” is stored in the value item as the state of the context type “place” corresponding to the state where the communication terminal T is not allowed to receive a call.

(Memory contents of callback DB)
Next, the stored contents of the callback DB stored in the callback control server 120 will be described with reference to FIG. The callback DB is a DB that is referred to in order to identify the telephone number or IP address of the caller terminal S used when the communication control apparatus 100 executes a callback.

  FIG. 8 is an explanatory diagram showing the stored contents of the callback DB stored in the callback control server 120. As shown in FIG. 8, the callback DB 122 has a user type item, a telephone number item, and an IP address item in association with the callback ID item, and the call from the calling terminal S is the receiving side. A record is formed when it is not accepted by the terminal R.

  The stored contents of the callback ID item are the same as the stored contents of the callback ID item shown in FIG. In the user type item, an identifier of the calling terminal S or the receiving terminal R is stored. In the telephone number field, the telephone number of the communication terminal T identified from the contents of the user ID field is stored. In the IP address item, the IP address of the communication terminal T identified from the contents of the user ID item is stored.

(Functional configuration example of communication control apparatus 100)
Next, a functional configuration example of the communication control apparatus 100 will be described with reference to FIG.

  FIG. 9 is a block diagram illustrating a functional configuration of the communication control apparatus 100. The communication control apparatus 100 includes a storage unit 901, a detection unit 902, a determination unit 903, and a transmission unit 904. Specifically, the functions (storage unit 901 to transmission unit 904) serving as the control unit are, for example, a program stored in a storage device such as the ROM 302, RAM 303, magnetic disk 305, and optical disk 307 shown in FIG. The function is realized by executing the function or by the I / F 309.

  The storage unit 901 has a function of storing a context indicating whether incoming is permitted or not for each terminal. Here, the context is the state of the communication terminal T, for example, the location of the communication terminal T or the state of whether or not the communication terminal T is communicating. The context indicating permission or non-permission of the incoming call is a context in which the communication terminal T is in a state where permission or non-permission of the incoming call, and specifically includes, for example, a conference room as a context indicating non-permission.

  Specifically, for example, the storage unit 901 stores the call control DB 121 and the monitoring context DB 113 described above. Thereby, based on the context of the communication terminal T, it becomes possible to determine whether or not the communication device is in an incoming call permission state.

  The detection unit 902 has a function of detecting that the second terminal has not accepted a call from the first terminal. Here, the first terminal is the transmission-side terminal S described above. The second terminal is the receiving terminal R described above.

  Specifically, for example, the detection unit 902 detects that an incoming call rejection operation has been performed at the second terminal for outgoing calls from the first terminal. More specifically, for example, the detection unit 902 rejects an incoming call at the receiving terminal R by receiving a notification from the receiving terminal R that there is an event that rejects the call from the calling terminal S. Detect that the operation was performed. Thereby, it is possible to detect a trigger for starting determination of whether or not a callback request can be transmitted.

  Specifically, for example, the detection unit 902 refers to the storage unit 901 when it is detected that the transmission is made from the first terminal to the second terminal, so that the second terminal does not accept the incoming call. When it is determined that the second terminal is in the state, it is detected that the second terminal has not accepted a call from the first terminal. More specifically, for example, the detecting unit 902 refers to the call control DB 121 to detect that the call incoming from the originating terminal S to the terminating terminal R is rejected. Thereby, it is possible to detect a trigger for starting determination of whether or not a callback request can be transmitted.

  The detection unit 902 has a function of detecting a callback request cancellation request from the first terminal. Specifically, the detection unit 902 detects a cancel request by receiving a callback request cancel request from the calling terminal S. As a result, when the user of the calling-side terminal S enters a state where it is not necessary to be called back, it is possible to detect a trigger for starting a process for preventing an unnecessary callback from being performed. . The detection result is stored in a storage area such as the RAM 303, the magnetic disk 305, and the optical disk 307.

  When it is detected by the detection unit 902 that the second terminal has not accepted the transmission from the first terminal, the determination unit 903 refers to the storage unit 901 so that the second terminal is in an incoming call permission state. It has the function to judge whether it is. Here, the transmission from the first terminal is a call transmitted from the above-described transmission-side terminal S.

  Specifically, for example, when the detection unit 902 detects that the second terminal has not accepted the transmission from the first terminal, the determination unit 903 refers to the storage unit 901 to obtain the first It is determined whether or not the second terminal is in an incoming call permission state for outgoing calls from the terminal.

  More specifically, for example, a case is assumed in which it is detected by the detection unit 902 that the receiving terminal R has not accepted a call from the transmitting terminal S. In this case, the determination unit 903 refers to the monitoring context DB 113 to determine whether or not the receiving terminal R is in an incoming call permission state. Thereby, the transmission of the callback request can be started only when the receiving terminal R is in the incoming call permission state.

  Specifically, for example, when the detection unit 902 detects that the second terminal has not accepted the transmission from the first terminal, the determination unit 903 refers to the storage unit 901 to obtain the first Then, it is determined whether or not the second terminal is in an incoming call permission state.

  More specifically, for example, a case is assumed in which it is detected by the detection unit 902 that the receiving terminal R has not accepted a call from the transmitting terminal S. In this case, the determination unit 903 refers to the monitoring context DB 113 to determine whether or not both the receiving terminal R and the calling terminal S are in an incoming call permission state. Thereby, the transmission of the callback request can be started only when both the receiving side terminal R and the calling side terminal S are in an incoming call permission state.

  Specifically, for example, when the detection unit 902 detects that the second terminal has not accepted the transmission from the first terminal, the determination unit 903 refers to the storage unit 901 to obtain the first It is determined whether or not the second terminal is in an incoming call permission state for outgoing calls from the terminal and whether or not the first terminal is in an incoming call permission state.

  More specifically, for example, the receiving terminal R receives a call request or urgency from the calling terminal S, or a relationship with the user of the calling terminal S (for example, calling for the user of the receiving terminal R) It is assumed that it is determined whether the terminal terminal S is in an incoming call permission state based on that the user of the terminal S is a customer. A case is assumed in which the detecting unit 902 detects that the receiving terminal R has not accepted a call from the transmitting terminal S. In this case, the determination unit 903 determines whether or not the receiving terminal R has been permitted to receive the call from the calling terminal S by referring to the monitoring context DB 113 including the call requirement and the urgency level. To do. In addition, the determination unit 903 determines whether or not the caller terminal S is in an incoming call permission state.

  As a result, transmission of the callback request can be started only when the receiving terminal R is in an incoming call permission state and the calling terminal S is in an incoming call permission state for communication with the calling terminal S. Therefore, for example, the callback to the calling terminal S of the customer and the callback to the calling terminal S of the colleague can be performed according to different standards (monitoring contexts). Can be improved.

  Specifically, for example, when the detection unit 902 detects that the second terminal has not accepted the transmission from the first terminal, the determination unit 903 refers to the storage unit 901 to obtain the first Whether or not the second terminal is in an incoming call permission state for outgoing calls from the terminal, and whether or not the first terminal is in an incoming call permission state for outgoing calls from the second terminal To do.

  More specifically, for example, it is determined whether or not the receiving terminal R is in an incoming call permission state based on the requirements and urgency of the call from the calling terminal S, and the calling terminal S A case is assumed in which it is determined whether or not the incoming call is permitted based on the call request from the terminal R and the urgency level. Each communication terminal T may further refer to the relationship between the user of the own terminal and the user of the communication terminal T of the communication partner. A case is assumed in which the detecting unit 902 detects that the receiving terminal R has not accepted a call from the transmitting terminal S. In this case, the determination unit 903 determines whether or not the receiving terminal R is in an incoming call permission state with respect to communication with the calling terminal S by referring to the monitoring context DB 113 including the call requirement and the urgency level. To do. In addition, the determination unit 903 determines whether or not the caller terminal S is in an incoming call permission state for communication with the callee terminal R.

  As a result, the call-back request is issued only when the receiving terminal R is in an incoming call permission state for communication with the calling terminal S and the calling terminal S is in an incoming call permission state for communication with the receiving terminal R. Transmission can be started. Therefore, for example, a call related to a callback with a customer's communication terminal T and a call related to a callback with a colleague's communication terminal T can be performed according to different standards (monitoring contexts). Can be improved. In addition, it is possible to determine whether the incoming call is permitted or not based on different criteria (monitoring context) depending on the call requirements and the urgency level, and the convenience of the communication terminal T can be improved. The determination result is stored in a storage area such as the RAM 303, the magnetic disk 305, and the optical disk 307.

  The transmission unit 904 has a function of transmitting a callback request to the first terminal to the second terminal when the determination unit 903 determines that the incoming call is permitted. Here, the callback request is, for example, a message including the telephone number of the calling terminal S that serves as an identifier for identifying the calling terminal S. Further, the callback request may be, for example, an application that executes a callback to the calling terminal S. The callback request may be an incoming request from the call control server 130, for example.

  Specifically, for example, when the determining unit 903 determines that the receiving terminal R or both the receiving terminal R and the calling terminal S are in an incoming call permission state, the transmitting unit 904 transmits A callback request for the terminal S is transmitted to the terminal R. However, when the callback request is an incoming request from the call control server 130, the transmission unit 904 transmits an incoming request to the originating terminal S to start communication between the terminating terminal R and the originating terminal S. . As a result, the receiving terminal R can be caused to make a callback to the calling terminal S.

  Further, the transmission unit 904 has a function of not transmitting a callback request to the second terminal when the cancellation request is detected by the detection unit 902. Specifically, for example, when the detection unit 902 detects a cancellation request, the transmission unit 904 does not transmit a callback request to the receiving terminal R. This prevents unnecessary callback requests from being made.

Example 1
Here, Example 1 will be described with reference to FIGS. In the first embodiment, the communication control apparatus 100 detects that the call from the calling terminal S has not been accepted by the communication control apparatus 100 by receiving a notification that there has been an incoming call rejection event from the receiving terminal R. Example of the case.

(Contents of transmission example 1 of callback request to callee by communication control apparatus 100 according to embodiment 1)
Next, the content of the transmission example 1 of the callback request to the callee by the communication control apparatus 100 according to the first embodiment will be described with reference to FIG. Transmission example 1 is an example in which the communication control apparatus 100 transmits a callback request based on whether or not the receiving terminal R is in an incoming call permission state.

  FIG. 10 is an explanatory diagram of the contents of the transmission example 1 of the callback request to the callee by the communication control apparatus 100 according to the first embodiment. In FIG. 10, as in FIG. 1, a communication system including a caller terminal S that a caller has, a callee terminal R that a callee has, and a communication control device 100 is shown. The communication control apparatus 100 is an apparatus that includes a context management server 110, a callback control server 120, and a call control server 130.

  (1) First, the caller terminal S sends a call to the callee terminal R. (2) Here, the receiving terminal R rejects the call from the calling terminal S. The incoming call rejection is performed, for example, when the callee operates the incoming call terminal R. Further, it may be considered that the incoming call is rejected when the caller does not receive a call for a certain period of time without any operation on the receiving terminal R.

  (3) When the incoming terminal R rejects the call, it notifies the communication control apparatus 100 that there has been an incoming call rejection event. (4) Upon receiving notification from the receiving terminal R that there has been an incoming call rejection event, the communication control device 100 starts determining whether or not a callback request can be transmitted and monitors the context of the receiving terminal R .

  (5) Here, it is assumed that the receiving terminal R has moved from the boardroom meeting room to the break room. (6) When the receiving terminal R moves to the break room, it notifies the communication control apparatus 100 of the context of the receiving terminal R. Here, the context is the location of the receiving terminal R.

  (7) Next, when receiving the notification of the context of the receiving terminal R, the communication control device 100 refers to the monitoring context DB 113 held in advance and determines whether the receiving terminal R is in an incoming call permission state. Determine whether or not.

  (8) When the receiving terminal R is in the incoming call permission state, the communication control device 100 refers to the callback DB 122 and creates a callback request. For example, the callback request includes the telephone number of the calling terminal S extracted from the callback DB 122. (9) Then, the communication control apparatus 100 transmits the created callback request to the receiving terminal R.

  (10) Upon receiving the callback request, the receiving terminal R performs a callback to the telephone number included in the callback request and starts a call with the calling terminal S.

  In this way, the communication control apparatus 100 acquires the context of the receiving terminal R and automatically determines whether or not the receiving terminal R is in an incoming call permission state. Then, the communication control apparatus 100 transmits a callback request to the receiving terminal R only when it is determined that the receiving terminal R is in an incoming call permission state. Therefore, it is not necessary for the user of the receiving terminal R to remember that the callback is necessary, and the time and effort of the user of the receiving terminal R can be reduced. In addition, the user of the receiving terminal R does not suffer the inconvenience of receiving a callback request even though the incoming call is not permitted.

(Contents of transmission example 2 of callback request to callee by communication control apparatus 100 according to embodiment 1)
Next, the contents of a transmission example 2 of the callback request to the called party by the communication control apparatus 100 according to the first embodiment will be described with reference to FIG. Transmission example 2 is an example in which the communication control apparatus 100 transmits a callback request based on whether or not the receiving terminal R is in an incoming call permission state and whether or not the calling terminal S is in an incoming call permission state. .

  FIG. 11 is an explanatory diagram of the contents of the transmission example 2 of the callback request to the callee by the communication control apparatus 100 according to the first embodiment. In FIG. 11, similarly to FIG. 1, a communication system including a caller side terminal S that a caller has, a callee side terminal R that a callee has, and a communication control device 100 is shown. The communication control apparatus 100 is an apparatus that includes a context management server 110, a callback control server 120, and a call control server 130.

  Since the processes (1) to (3) are the same as the processes (1) to (3) in FIG. 10, the description thereof is omitted here. (4) Next, when the communication control apparatus 100 receives a notification from the receiving terminal R that there is an incoming call rejection event, the communication control apparatus 100 starts determining whether or not the callback request can be transmitted. The context of the terminal S is monitored.

  (5) Here, it is assumed that the receiving terminal R has moved from the boardroom meeting room to the break room. (6) When the receiving terminal R moves to the break room, it notifies the communication control device 100 of the context of the receiving terminal R. Further, the calling terminal S notifies the communication control device 100 of the context of the calling terminal S. Here, the context is the location of the receiving terminal R.

  (7) Next, when receiving the notification of the context of the receiving terminal R, the communication control device 100 refers to the monitoring context DB 113 held in advance and determines whether the receiving terminal R is in an incoming call permission state. Determine whether or not. Further, the communication control device 100 determines whether or not the calling terminal S is in a state of call rejection from the context of the calling terminal S in the context DB 112.

  (8) When both the receiving terminal R and the calling terminal S are in an incoming call permission state, the communication control apparatus 100 refers to the callback DB 122 and creates a callback request. For example, the callback request includes the telephone number of the calling terminal S extracted from the callback DB 122. (9) Then, the communication control apparatus 100 transmits the created callback request to the receiving terminal R.

  (10) Upon receiving the callback request, the receiving terminal R performs a callback to the telephone number included in the callback request and starts a call with the calling terminal S.

  In this way, the communication control apparatus 100 acquires the context of the receiving terminal R and automatically determines whether or not the receiving terminal R is in an incoming call permission state. Then, the communication control apparatus 100 transmits a callback request to the receiving terminal R only when it is determined that the receiving terminal R is in an incoming call permission state. Therefore, it is not necessary for the user of the receiving terminal R to remember that the callback is necessary, and the time and effort of the user of the receiving terminal R can be reduced. In addition, the user of the receiving terminal R does not suffer the inconvenience of receiving a callback request even though the incoming call is not permitted.

(Specific communication contents of each server in the communication control apparatus 100 according to the first embodiment)
Here, with reference to FIG. 12 and FIG. 13, specific communication contents of each server in the communication control apparatus 100 according to the first embodiment illustrated in FIG. 10 will be described.

(Details of communication contents of each server when a call is transmitted from the calling terminal S in the first embodiment)
First, with reference to FIG. 12, details of communication contents of each server when a call is transmitted from the originating terminal S in the first embodiment will be described.

  FIG. 12 is a sequence diagram illustrating details of communication contents of each server when a call is transmitted from the originating terminal S in the first embodiment. First, the receiving terminal R transmits a call control condition to the callback control server 120 (step S1201). The callback control server 120 updates the call control DB 121 based on the received call control conditions.

  Next, the receiving terminal R notifies the context management server 110 of a context indicating the state of the terminal itself (step S1202). The context management server 110 updates the context DB 112 based on the received context. For example, the context management server 110 specifies the location of the communication terminal T based on the location DB 111 from the SSID included in the context, and updates the context DB 112.

  Here, a call is made from the calling terminal S to the receiving terminal R (step S1203). When receiving a call, the receiving terminal R transmits a context indicating that a call is in progress to the context management server 110 (step S1204). The context management server 110 updates the context DB 112 based on the received context.

  Next, the receiving terminal R rejects the incoming call in response to the operation of the recipient. Then, the receiving terminal R notifies the context management server 110 that there has been an incoming call rejection event (step S1205). The context management server 110 updates the context DB 112 when there is an incoming call rejection event.

  Next, the receiving terminal R notifies the callback control server 120 that there has been an incoming call rejection event (step S1206). The callback control server 120 that is notified that there is an incoming call rejection event refers to the call control DB 121 (step S1207), and notifies the context management server 110 of a callback trigger notification request (step S1208). The callback trigger notification request is a request for causing the context management server 110 to monitor the context of the receiving terminal R and to notify the callback control server 120 when the incoming call permission state is entered.

  Then, the callback control server 120 registers callback information in the callback DB 122 (step S1209). The callback information is, for example, the telephone number and IP address of the calling terminal S used for callback. As a result, the context management server 110 can start monitoring the context of the receiving terminal R to generate a trigger for transmitting a callback request.

(Details of communication contents of each server when a callback request is transmitted by the callback control server 120 in the first embodiment)
Next, details of communication contents of each server when a callback request is transmitted by the callback control server 120 in the first embodiment will be described with reference to FIG. Here, it is assumed that the receiving terminal R whose context is monitored by the context management server 110 moves in FIG. 12 and the context of the receiving terminal R changes to an incoming call permission state.

  FIG. 13 is a sequence diagram illustrating details of communication contents of each server when a callback request is transmitted by the callback control server 120 according to the first embodiment. First, when the context changes due to movement, the receiving terminal R notifies the context management server 110 of a context indicating the state of the terminal itself (step S1301).

  Upon receiving the context notification, the context management server 110 refers to the monitoring context DB 113 and determines whether or not the receiving terminal R is in an incoming call permission state. Then, if the receiving terminal R is in an incoming call permission state, the context management server 110 notifies the callback control server 120 of a callback trigger notification (step S1302).

  The callback control server 120 that has received the callback trigger notification refers to the callback DB 122 (step S1303) and creates a callback request. Then, the callback control server 120 transmits the created callback request to the receiving terminal R (step S1304).

  The receiving terminal R that has received the callback request makes a callback to the calling terminal S based on the telephone number of the calling terminal S included in the callback request (step S1305).

  As a result, the communication control apparatus 100 automatically determines whether or not the receiving terminal R is in an incoming call permission state without remembering that the called party needs a callback. Then, the communication control apparatus 100 transmits a callback request only when the receiving terminal R is in the incoming call permission state.

  Therefore, it is possible to reduce the trouble for the callee to remember that the callback is necessary. Further, there is no inconvenience that a callback request is received even though the incoming terminal R is in a state where incoming calls are not permitted, and the convenience of the incoming terminal R can be improved.

(Details of processing contents of callback control processing of callback control server 120 in embodiment 1)
Next, details of the processing contents of the callback control processing of the callback control server 120 in the first embodiment will be described with reference to FIG. FIG. 14 describes the details of the callback control process performed by the callback control server 120 in FIGS. 12 and 13.

  FIG. 14 is a flowchart illustrating details of the processing contents of the callback control processing of the callback control server 120 according to the first embodiment. First, the callback control server 120 determines whether or not an incoming call rejection event has been received (step S1401). If the incoming call rejection event has not been received (step S1401: No), the callback control server 120 returns to step S1401 and waits for the incoming call rejection event.

  On the other hand, when the incoming call rejection event is received (step S1401: Yes), the callback control server 120 refers to the call control DB 121 and acquires the call control condition of the called terminal R (step S1402).

  Next, the callback control server 120 generates a monitoring context corresponding to the incoming call permission state of the receiving terminal R based on the acquired call control conditions (step S1403). Then, the callback control server 120 transmits a callback opportunity notification request including the generated monitoring context to the context management server 110 (step S1404).

  Next, the callback control server 120 registers callback information in the callback DB 122 (step S1405). The processes in steps S1401 to S1405 described above correspond to the processes in steps S1206 to S1209.

  Next, the callback control server 120 determines whether or not a callback opportunity notification from the context management server 110 has been received (step S1406). Here, when the callback event notification is not received (step S1406: No), the callback control server 120 returns to step S1406 and waits for the reception of the callback event notification.

  On the other hand, when the callback trigger notification is received (step S1406: Yes), the callback control server 120 acquires callback information from the callback DB 122 (step S1407) and transmits a callback request (step S1408). Then, the callback control server 120 ends the callback control process. The processes in steps S1406 to S1408 described above correspond to the processes in steps S1302 to S1304.

  Thereby, the communication control apparatus 100 can transmit a callback request only when the receiving-side terminal R is in the incoming call permission state. The callee can save time and effort to remember that a callback is required. Further, there is no inconvenience that a callback request is received even though the incoming terminal R is in a state where incoming calls are not permitted, and the convenience of the incoming terminal R can be improved.

(Details of processing contents of monitoring context registration processing of context management server 110 in embodiment 1)
Next, details of processing contents of the monitoring context registration processing of the context management server 110 in the first embodiment will be described with reference to FIG. FIG. 15 describes the processing content of the monitoring context registration processing performed by the context management server 110 in FIG.

  FIG. 15 is a flowchart illustrating details of the processing contents of the monitoring context registration processing of the context management server 110 according to the first embodiment. First, the context management server 110 determines whether or not a callback trigger notification request has been received from the callback control server 120 (step S1501). If no callback trigger notification request has been received (step S1501: No), the context management server 110 returns to step S1501 and waits for reception of a callback trigger notification request.

  On the other hand, when a callback trigger notification is received (step S1501: Yes), the context management server 110 extracts a monitoring context from the callback trigger notification request and registers it in the monitoring context DB 113 (step S1502). Then, the context management server 110 ends the monitoring context registration process.

  The processes in steps S1501 to S1502 described above are processes performed by the context management server 110 to which the callback trigger notification request has been transmitted by the process in step S1208. Accordingly, the context management server 110 registers the monitoring context corresponding to the incoming call permission state of the communication terminal T in the monitoring context DB 113, and can monitor whether or not the communication terminal T is in the incoming call permission state.

(Details of processing contents of callback trigger notification transmission processing of context management server 110 in embodiment 1)
Next, details of processing contents of the callback trigger notification transmission processing of the context management server 110 according to the first embodiment will be described with reference to FIG. In FIG. 16, the processing content of the callback opportunity notification transmission process performed by the context management server 110 in FIG. 13 will be described.

  FIG. 16 is a flowchart illustrating details of processing contents of a callback trigger notification transmission process of the context management server 110 according to the first embodiment. First, the context management server 110 determines whether or not the context DB 112 has been updated (step S1601). For example, the context DB 112 is updated when a context from the communication terminal T is received. If the context DB 112 has not been updated (step S1601: No), the context management server 110 returns to step S1601 and waits for the context DB 112 to be updated.

  On the other hand, when the context DB 112 is updated (step S1601: Yes), the context management server 110 determines whether or not a callback ID is registered in the updated record of the context DB 112 (step S1602). Here, when the callback ID is not registered (step S1602: No), the context management server 110 ends the callback opportunity notification transmission process.

  On the other hand, when the callback ID is registered (step S1602: Yes), the context management server 110 determines whether the conditions of all the records in the monitoring context DB 113 corresponding to the registered callback ID are satisfied. (Step S1603). Here, when there is a condition that is not satisfied (step S1603: No), the context management server 110 ends the callback opportunity notification transmission process.

  On the other hand, when the conditions of all the records are satisfied (step S1603: Yes), the context management server 110 transmits a callback trigger notification to the callback control server 120 (step S1604), and callback trigger notification transmission processing Exit. The processes in steps S1601 to S1604 described above correspond to the process in step S1302.

  As a result, the context management server 110 monitors the context of the communication terminal T to be monitored, and transmits a callback trigger notification to the callback control server 120 when the communication terminal T is in an incoming call permission state. Can do.

(Example 2)
Here, Example 2 will be described with reference to FIGS. The second embodiment is an embodiment where the communication control apparatus 100 controls communication between the receiving terminal R and the calling terminal S by the call control server 130. In the second embodiment, the call control server 130 detects that the call from the caller terminal S is not received by the callee terminal R, so that the communication control apparatus 100 receives the call from the caller terminal S. It is an Example in the case of detecting that the terminal R has not accepted.

  In the second embodiment, the caller inputs the call requirement and the urgency level to the caller terminal S. And the communication control apparatus 100 transmits the callback request in consideration of the call requirement and the urgency level by receiving the call requirement and the urgency level from the calling terminal S. In the second embodiment, as an example of a call request, a request for approval of a slip requesting business trip permission from a company is given as an example. However, when the caller inputs the call requirement and the urgency level to the other system 202, the communication control apparatus 100 receives the call requirement and the urgency level from the other system 202. Thus, a callback request is transmitted in consideration of call requirements and urgency.

  Further, it is assumed that a callback request made by the communication control apparatus 100 is not necessary. For example, when the caller request and the callee are sent, the caller and the callee meet directly and the call request is conveyed verbally. Therefore, in the second embodiment, the communication control apparatus 100 can cancel the callback request in response to a request from the calling terminal S.

(Screen display example of the communication terminal T according to the second embodiment)
First, a screen display example of the communication terminal T according to the second embodiment will be described with reference to FIG.

  FIG. 17 is an explanatory diagram of a screen display example of the communication terminal T according to the second embodiment. Specifically, FIG. 17A shows a screen display example of the calling terminal S that can input a call request and an urgency level. As shown in (a), the screen of the calling terminal S includes a part for inputting a destination telephone number and a part for inputting a call requirement and an urgency level. The call requirement and the urgency level entered by the caller on this screen are notified to the caller terminal S and the communication control device 100.

  FIG. 17B shows a screen display example of the receiving terminal R that can display the call request and the urgency level. As shown in (b), the screen of the receiving terminal R includes a portion for displaying the caller's telephone number and a portion for displaying the call requirement and the urgency level. By displaying this screen, the callee can confirm the call requirement and the urgency level and determine whether the call is permitted or not.

(Storage contents of the context DB 112 according to the second embodiment)
First, the stored contents of the context DB 112 according to the second embodiment will be described with reference to FIG. Also in the second embodiment, the context DB 112 stores the same contents as the context DB 112 in the first embodiment.

  FIG. 18 is an explanatory diagram showing the contents stored in the context DB 112. As illustrated in FIG. 18, the context management server 110 includes a context DB 112 for each communication terminal T. The context DB 112 has a value item and a callback ID item in association with the context type item, and configures a record each time a context is received from the communication terminal T.

  In the context type item, the type of context of the calling terminal S or the receiving terminal R is stored. Specifically, in the context type, in addition to “location” and “telephone” shown in the first embodiment, a “slip” indicating whether approval of a slip, which is an example of a call requirement, is necessary. There is "approval".

  In the value item, a state corresponding to the type of context is stored. Specifically, “user A” is stored in the value item corresponding to “slip approval” of the context type. “User A” is the ID of the user of the transmitting terminal S that applied for approval of the slip. In the callback ID item, an identifier for identifying a callback is stored. This slip information is notified to the context management server 110 and stored in the context DB 112 when, for example, the user of the sending terminal S requests the user of the receiving terminal R to approve the slip in the electronic slip system. The

(Storage contents of the monitoring context DB 113 including the monitoring context regarding cancellation of the callback request)
Next, the contents stored in the monitoring context DB 113 including the monitoring context regarding cancellation of the callback request will be described with reference to FIG. In the second embodiment, since the callback request may be canceled, the monitoring context DB 113 stores a monitoring context regarding cancellation of the callback request.

  FIG. 19 is an explanatory diagram showing the contents stored in the monitoring context DB 113 including the monitoring context regarding cancellation of the callback request. As shown in FIG. 19, the monitoring context DB 113 has a type item, a user ID item, a context type item, and a value item in association with the callback ID item, and is called from the callback control server 120. Each time a back trigger notification request is notified, a record is configured.

  In the callback ID item, an identifier for identifying a callback is stored. The type field stores “execution” indicating that the record is a condition for executing transmission of a callback request or “cancel” indicating that the record is a condition for canceling transmission of a callback request. Has been. In the user ID item, an identifier of the calling terminal S or the receiving terminal R is stored. In the context type item, the type of context of the calling terminal S or the receiving terminal R is stored. In the value item, a state corresponding to the type of context is stored.

(Contents stored in the call control DB 121 including call requirements and urgency)
Next, the contents stored in the call control DB 121 including call requirements and urgency will be described with reference to FIG. In the second embodiment, in order to transmit the callback request in consideration of the call requirement and the urgency level, the call control DB 121 stores the call requirement and the urgency level together with the stored contents of the call control DB 121 in the first embodiment. The condition regarding is stored.

  FIG. 20 is an explanatory diagram showing the stored contents of the call control DB 121 including call requirements and urgency. As shown in FIG. 20, the call control DB 121 has a value item, a requirement item, and an urgency item in association with the context type item, and each time a call control condition is received from the communication terminal T. Configure the record.

  A context type is stored in the context type item. Specifically, the type of context includes “location” that is a type indicating a location where the communication terminal T is located. The value item stores the status of the context type. Specifically, “conference room” is stored in the value item as the state of the context type “place”.

  The message item stores a message of a call that is permitted to receive an incoming call in the state indicated by the value item. For example, “customer X” and “*” are stored in the business item. “Customer X” indicates that an incoming call is permitted if the call is related to the customer X or the call is from the customer X. “*” Is a wild card and indicates that the incoming call is permitted regardless of the requirement.

  The urgency level item stores the urgency level for permitting incoming calls in the state indicated by the value item. For example, “high” and “*” are stored in the urgency item. “High” indicates that an incoming call is permitted if the call has a high degree of urgency. “*” Is a wild card and indicates that incoming calls are permitted regardless of the level of urgency.

(Contents of transmission example 1 of callback request to callee by communication control apparatus 100 according to embodiment 2)
Next, the contents of the transmission example 1 of the callback request to the callee by the communication control apparatus 100 according to the second embodiment will be described with reference to FIGS. 21 and 22. Transmission example 1 is an example in which the communication control apparatus 100 transmits a callback request based on whether or not the receiving terminal R is in an incoming call permission state.

  FIGS. 21 and 22 are explanatory diagrams illustrating the contents of a transmission example 1 of the callback request to the callee by the communication control apparatus 100 according to the second embodiment. FIG. 21 shows a communication system including a caller terminal S possessed by a caller, a callee terminal R possessed by a callee, and a communication control device 100, as in FIG. The communication control apparatus 100 is an apparatus that includes a context management server 110, a callback control server 120, and a call control server 130. Then, the communication control apparatus 100 controls communication between the caller terminal S and the callee terminal R by the call control server 130.

  In FIG. 21, (1) First, the calling terminal S transmits a call to the receiving terminal R. A call to the called terminal R is first received by the communication control apparatus 100. (2) Here, the receiving terminal R notifies the communication control apparatus 100 of the context of the receiving terminal R in advance. For this reason, the communication control apparatus 100 stores, as the context of the receiving terminal R, that the location of the receiving terminal R is “office meeting room”.

  (3) Then, the communication control apparatus 100 determines whether the receiving terminal R is in an incoming call permission state based on the context of the receiving terminal R and the call control DB 121. If the receiving terminal R is in a state where incoming calls are not permitted, a call from the calling terminal S is not received by the receiving terminal R.

  When the call from the calling terminal S is not received by the receiving terminal R, the communication control apparatus 100 starts determining whether or not a callback request can be transmitted, and waits for a context notification from the receiving terminal R.

  In FIG. 22, (1) Here, it is assumed that the receiving terminal R has moved from the boardroom meeting room to the break room. (2) When the receiving terminal R moves to the break room, it notifies the communication control apparatus 100 of the context of the receiving terminal R. Here, the context is the location of the receiving terminal R.

  (3) Next, when receiving the notification of the context of the receiving terminal R, the communication control device 100 refers to the monitoring context DB 113 held in advance and determines whether the receiving terminal R is in an incoming call permission state. Determine whether or not.

  (4) When the receiving terminal R is in an incoming call permission state, the communication control apparatus 100 refers to the callback DB 122 and transmits a callback request to the receiving terminal R and the calling terminal S. Here, the callback request is an incoming request from the call control server 130. The incoming call terminal R and the outgoing call terminal S allow the incoming call request from the call control server 130, respectively, and a call between the incoming call terminal R and the outgoing call terminal S is started.

  In this way, the communication control apparatus 100 acquires the context of the receiving terminal R and automatically determines whether or not the receiving terminal R is in an incoming call permission state. Then, the communication control apparatus 100 transmits a callback request to the receiving terminal R only when it is determined that the receiving terminal R is in an incoming call permission state. Therefore, the user of the receiving terminal R does not have to remember that a callback is necessary, and the user's time and effort of the receiving terminal R can be reduced. In addition, the user of the receiving terminal R does not suffer the inconvenience of receiving a callback request even though the incoming call is not permitted.

(Contents of transmission example 2 of callback request to callee by communication control apparatus 100 according to embodiment 2)
Next, the contents of a second example of transmission of a callback request to a callee by the communication control apparatus 100 according to the second embodiment will be described with reference to FIG. Transmission example 2 is an example in which the communication control apparatus 100 transmits a callback request based on whether or not the receiving terminal R is in an incoming call permission state and whether or not the calling terminal S is in an incoming call permission state. .

  FIG. 23 is an explanatory diagram of the contents of the transmission example 2 of the callback request to the callee by the communication control apparatus 100 according to the second embodiment. In FIG. 23, similarly to FIG. 1, a communication system including a caller terminal S possessed by a caller, a callee terminal R possessed by a callee, and a communication control device 100 is shown. The communication control apparatus 100 is an apparatus that includes a context management server 110, a callback control server 120, and a call control server 130. Then, the communication control apparatus 100 controls communication between the caller terminal S and the callee terminal R by the call control server 130.

  In FIG. 23, the communication control apparatus 100 starts determining whether or not the callback request can be transmitted when the call from the calling terminal S is not received by the receiving terminal R as in FIG. R and the context of the calling terminal S are monitored.

  (1) Here, it is assumed that the receiving terminal R has moved from the boardroom to the break room. (2) When the receiving terminal R moves to the break room, it notifies the communication control apparatus 100 of the context of the receiving terminal R. Here, the context is the location of the receiving terminal R.

  (3) Next, when receiving the notification of the context of the receiving terminal R, the communication control device 100 refers to the monitoring context DB 113 held in advance and determines whether the receiving terminal R is in an incoming call permission state. Determine whether or not. Further, the communication control device 100 determines whether or not the calling terminal S is in a state of call rejection from the context of the calling terminal S in the context DB 112.

  (4) When both the receiving terminal R and the calling terminal S are in an incoming call permission state, the communication control apparatus 100 refers to the callback DB 122 and sends a callback request to the receiving terminal R and the calling terminal. To S. Here, the callback request is an incoming request from the call control server 130. The incoming call terminal R and the outgoing call terminal S allow the incoming call request from the call control server 130, respectively, and a call between the incoming call terminal R and the outgoing call terminal S is started.

  In this way, the communication control apparatus 100 acquires the context of the receiving terminal R and automatically determines whether or not the receiving terminal R is in an incoming call permission state. Then, the communication control apparatus 100 transmits a callback request to the receiving terminal R only when it is determined that the receiving terminal R is in an incoming call permission state. Therefore, the user of the receiving terminal R does not have to remember that a callback is necessary, and the user's time and effort of the receiving terminal R can be reduced. In addition, the user of the receiving terminal R does not suffer the inconvenience of receiving a callback request even though the incoming call is not permitted.

(Specific communication contents of each server in the communication control apparatus 100 according to the second embodiment)
Here, with reference to FIGS. 24 and 25, specific communication contents of each server in the communication control apparatus 100 according to the second embodiment illustrated in FIGS. 21 and 22 will be described.

(Details of communication contents of each server when a call is transmitted from the calling terminal S in the second embodiment)
First, the details of communication contents of each server when a call is transmitted from the originating terminal S in the second embodiment will be described with reference to FIGS. 24 and 25.

  24 and 25 are sequence diagrams illustrating details of communication contents of each server when a call is transmitted from the calling terminal S in the second embodiment. In FIG. 24, first, the receiving terminal R transmits a call control condition to the callback control server 120 (step S2401). The callback control server 120 updates the call control DB 121 based on the received call control conditions.

  Next, the receiving terminal R notifies the context management server 110 of a context indicating the state of the terminal itself (step S2402). Note that the context management server 110 updates the context DB 112 based on the received context. For example, the context management server 110 specifies the location of the communication terminal T based on the location DB 111 from the SSID included in the context, and updates the context DB 112.

  Here, the caller tries to request approval from the callee. This request for approval is made, for example, when an originator issues an electronic slip on an electronic slip system (other system 202) (not shown) and requests the recipient to approve it. When the recipient is requested to approve the electronic voucher, an electronic voucher system (not shown) notifies the context management server 110 that the caller has requested the recipient to approve the electronic voucher. The context management server 110 registers the ID (user A) of the caller who is the requester of the approval of the slip as the value that the context type of the context DB 112 of the receiving terminal R is the slip approval.

  Then, in the caller terminal S, the caller sets a request for approval request to the callee terminal R and the urgency level (step S2403). Then, a call including the request for the approval request to the receiving terminal R and the urgency is transmitted to the call control server 130 (step S2404).

  Here, the message and the urgency level are directly notified from the calling terminal S to the call control server 130. However, the call request and the urgency level are registered from the calling terminal S to the above-described electronic voucher system (the other system 202), and the communication control device 100 refers to the system so that the call request and the urgency are stored. You may make it acquire degree.

  Next, the call control server 130 notifies the context to the context management server 110 (step S2405). The context management server 110 updates the context DB 112 based on the received context. The call control server 130 notifies the callback control server 120 of an incoming call control request (step S2406).

  The callback control server 120 notified of the incoming control request refers to the context DB 112 of the context management server 110 (step S2407), refers to the call control DB 121 (step S2408), and determines whether the receiving terminal R is in an incoming call permission state. It is determined whether or not (step S2409). Here, it is assumed that the callback control server 120 determines that the receiving terminal R is in an incoming call rejection state.

  In FIG. 25, the callback control server 120 notifies the call control server 130 of an incoming call control response (step S2501). The incoming call control response includes information indicating that the incoming call terminal R is in an incoming call rejection state.

  The call control server 130 that has received the incoming call control response notifies the calling terminal S of a disconnection request and a callback registration notification (step S2502). The call control server 130 notifies the context management server 110 of the context (step S2503). The context management server 110 updates the context DB 112 based on the received context.

  If the call-back control server 120 determines that the receiving terminal R is in an incoming call disapproval state, the call-back control server 120 starts determining whether or not a callback request can be transmitted (step S2504). Next, the callback control server 120 refers to the call control DB 121 related to the communication terminal T (step S2505).

  Then, the callback control server 120 notifies the context management server 110 of a callback opportunity notification request (step S2506). The callback trigger notification request is a request for causing the context management server 110 to monitor the context of the receiving terminal R and to notify the callback control server 120 when the incoming call permission state is entered.

  Next, the callback control server 120 registers callback information in the callback DB 122 (step S2507). The callback information is, for example, the telephone number and IP address of the calling terminal S used for callback. As a result, the context management server 110 can start monitoring the context of the receiving terminal R to generate a trigger for transmitting a callback request.

(Details of communication contents of each server when a callback request is transmitted by the callback control server 120 in the second embodiment)
Next, details of communication contents of each server when a callback request is transmitted by the callback control server 120 according to the second embodiment will be described with reference to FIG. Here, it is assumed that the receiving terminal R whose context is monitored by the context management server 110 moves in FIG. 25 and the context of the receiving terminal R changes to an incoming call permission state.

  FIG. 26 is a sequence diagram illustrating details of communication contents of each server when a callback request is transmitted by the callback control server 120 according to the second embodiment. First, when the context changes due to movement, the receiving terminal R notifies the context management server 110 of a context indicating the state of the terminal itself (step S2601).

  Upon receiving the context notification, the context management server 110 refers to the monitoring context DB 113 and determines whether or not the receiving terminal R is in an incoming call permission state. Then, if the receiving terminal R is in an incoming call permission state, the context management server 110 notifies the callback control server 120 of a callback trigger notification (step S2602).

  The callback control server 120 that has received the notification of the callback opportunity refers to the callback DB 122 (step S2603) and transmits a callback control request to the call control server 130 (step S2604). The callback control request is a request for causing the call control server 130 to execute so-called third party call control for the calling terminal S and the receiving terminal R.

  Next, the call control server 130 transmits an incoming call request to the calling terminal S and the receiving terminal R (step S2605). Then, the calling side terminal S and the receiving side terminal R are caused to talk. Next, the call control server 130 notifies the context to the context management server 110 (step S2606). The context management server 110 updates the context DB 112 based on the received context.

  As a result, the communication control apparatus 100 automatically determines whether the receiving terminal R is in an incoming call permission state without having to remember that the called party needs to call back. Then, the communication control apparatus 100 transmits a callback request only when the receiving terminal R is in the incoming call permission state.

  Therefore, it is possible to reduce the trouble for the callee to remember that the callback is necessary. Further, there is no inconvenience that a callback request is received even though the incoming terminal R is in a state where incoming calls are not permitted, and the convenience of the incoming terminal R can be improved.

(Details of communication contents of each server when canceling callback request in embodiment 2)
Next, details of communication contents of each server when canceling a callback request according to the second embodiment will be described with reference to FIG.

  FIG. 27 is a sequence diagram illustrating details of communication contents of each server when a callback request is canceled in the second embodiment. First, in the calling side terminal S, when the request for the outgoing call is resolved, the cancellation of the callback request is input (step S2701). Then, the originating terminal S transmits a context indicating that the callback request has been canceled to the context management server 110 (step S2702).

  This may be performed, for example, by canceling a voucher approval request for a callee previously made by an electronic voucher system (other system 202) (not shown) by the sending terminal S. In this case, when the approval request is canceled in the electronic slip system, the fact is notified from the electronic slip system to the context management server 110. Then, the context management server 110 deletes the caller information (user A) registered in the value item whose context type of the receiving terminal R in the context DB 112 is slip approval.

  The context management server 110 updates the context DB 112 and transmits a callback opportunity notification requesting the cancellation of the callback to the callback control server 120 (step S2703). Then, the callback control server 120 deletes the record in the callback DB 122 (step S2704). As a result, unnecessary callback requests are not transmitted.

(Details of processing contents of incoming call control processing of callback control server 120 in embodiment 2)
Next, details of processing contents of the incoming call control processing of the callback control server 120 in the second embodiment will be described with reference to FIG. In FIG. 28, processing contents of the incoming call control processing performed by the callback control server 120 in FIGS. 24 and 25 will be described.

  FIG. 28 is a flowchart illustrating details of processing contents of the incoming call control processing of the callback control server 120 according to the second embodiment. First, the callback control server 120 determines whether or not an incoming call control request has been received (step S2801). If no incoming control request has been received (step S2801: NO), the callback control server 120 returns to step S2801 and waits for the incoming control request.

  On the other hand, when the incoming call control request is received (step S2801: YES), the callback control server 120 acquires the context of the called terminal R (step S2802). Next, the callback control server 120 refers to the record of the call control DB 121 corresponding to the acquired context (step S2803).

  Then, the callback control server 120 determines whether or not the receiving terminal R is in an incoming call permission state based on the referred record of the call control DB 121 (step S2804). Here, when the receiving terminal R is in an incoming call permission state (step S2804: Yes), the callback control server 120 displays an incoming call control response indicating that the incoming terminal R is in an incoming call permission state as a call control. It transmits to the server 130 (step S2805). Then, the callback control server 120 ends the incoming call control process.

  On the other hand, when the receiving terminal R is not in the incoming call permission state (step S2804: No), the callback control server 120 sends an incoming call control response indicating that the incoming terminal R is in the incoming call rejection state to the call control server. It transmits to 130 (step S2806). Next, the callback control server 120 generates an event for starting the callback control process (step S2807). Then, the callback control server 120 ends the incoming call control process.

  The processes in steps S2801 to S2807 described above correspond to the processes in steps S2406 to S2409 and steps S2501 to S2502. As a result, the communication control apparatus 100 can determine whether or not the incoming call terminal R is allowed to receive a call. Therefore, the communication control apparatus 100 determines whether or not the callee is in an incoming call permission state and operates the incoming call terminal R to receive the call. It is possible to reduce the trouble of refusing.

(Details of processing contents of callback control processing of callback control server 120 in embodiment 2)
Next, details of processing contents of the callback control processing of the callback control server 120 in the second embodiment will be described with reference to FIG. In FIG. 29, processing contents of the callback control processing performed by the callback control server 120 in FIGS. 25 to 27 will be described.

  FIG. 29 is a flowchart illustrating details of the processing contents of the callback control processing of the callback control server 120 according to the second embodiment. First, when an event for starting the callback control process occurs, the callback control server 120 starts the callback control process (step S2901). Next, the callback control server 120 refers to the call control DB 121 and acquires the call control condition of the receiving terminal R (step S2902).

  Next, the callback control server 120 generates a monitoring context corresponding to the incoming call permission state of the receiving terminal R based on the acquired call control condition (step S2903). Then, the callback control server 120 generates a callback cancellation condition (step S2904).

  Next, the callback control server 120 transmits a callback opportunity notification including the generated monitoring context and callback cancellation condition to the context management server 110 (step S2905). Then, the callback control server 120 registers callback information in the callback DB 122 (step S2906). Wait for receipt of callback event notification. The processes in steps S2901 to S2906 described above correspond to the processes in steps S2504 to S2507.

  Next, the callback control server 120 determines whether or not a callback trigger notification has been received from the context management server 110 (step S2907). If the callback trigger notification has not been received (step S2907: NO), the callback control server 120 returns to step S2907 and waits for reception of the callback trigger notification.

  On the other hand, when the callback event notification is received (step S2907: YES), the callback control server 120 determines the content of the callback event notification (step S2908). Here, if the content of the callback opportunity notification is execution of callback (step S2908: callback execution), the callback control server 120 acquires information from the callback DB 122 (step S2909). Then, the callback control server 120 transmits a callback request (step S2910) and ends the callback control process. The processes in steps S2907 to S2910 described above are processes corresponding to the processes in steps S2601 to S2604.

  On the other hand, if the content of the callback event notification is the cancellation of the callback (step S2908: callback cancellation), the callback control server 120 deletes the information from the callback DB 122 (step S2911). Then, the callback control server 120 ends the callback control process. The processes in steps S2907 to S2911 described above correspond to the processes in steps S2701 to S2704.

  Thereby, the communication control apparatus 100 can transmit a callback request only when the receiving-side terminal R is in the incoming call permission state. The callee can save time and effort to remember that a callback is required. Further, there is no inconvenience that a callback request is received even though the incoming terminal R is in a state where incoming calls are not permitted, and the convenience of the incoming terminal R can be improved. Further, the convenience of the receiving terminal R can be improved by canceling the callback request that is no longer necessary.

(Details of processing contents of monitoring context registration processing of context management server 110 in embodiment 2)
Next, details of processing contents of the monitoring context registration processing of the context management server 110 according to the second embodiment will be described with reference to FIG.

  FIG. 30 is a flowchart illustrating details of the processing contents of the monitoring context registration processing of the context management server 110 according to the second embodiment. First, the context management server 110 determines whether a callback opportunity notification request has been received from the callback control server 120 (step S3001). If no callback trigger notification request has been received (step S3001: No), the context management server 110 returns to step S3001 and waits for reception of a callback trigger notification request.

  On the other hand, when a callback trigger notification request is received (step S3001: Yes), the context management server 110 extracts a monitoring context from the callback trigger notification request and registers it in the monitoring context DB 113 (step S3002). Then, the context management server 110 ends the monitoring context registration process. Accordingly, the context management server 110 registers the monitoring context corresponding to the incoming call permission state of the communication terminal T in the monitoring context DB 113, and can monitor whether or not the communication terminal T is in the incoming call permission state.

(Details of processing contents of callback trigger notification transmission processing of context management server 110 in embodiment 2)
Next, details of processing contents of the callback trigger notification transmission processing of the context management server 110 in the second embodiment will be described with reference to FIG.

  FIG. 31 is a flowchart illustrating details of processing contents of a callback trigger notification transmission process of the context management server 110 according to the second embodiment. First, the context management server 110 determines whether or not the context DB 112 has been updated (step S3101). For example, the context DB 112 is updated when a context from the communication terminal T is received. If the context DB has not been updated (step S3101: No), the context management server 110 returns to step S3101 and waits for the context DB to be updated.

  On the other hand, when the context DB is updated (step S3101: Yes), the context management server 110 determines whether or not a callback ID is registered in the updated record of the context DB 112 (step S3102). Here, when the callback ID is not registered (step S3102: No), the context management server 110 ends the callback opportunity notification transmission process.

  On the other hand, when the callback ID is registered (step S3102: Yes), the context management server 110 determines whether the conditions of all the records in which the type of the monitoring context DB 113 corresponding to the registered callback ID is executed are satisfied. Is determined (step S3103). Here, when the conditions of all the records are satisfied (step S3103: Yes), the context management server 110 transmits a callback trigger notification indicating callback execution to the callback control server 120 (step S3104), Terminates the callback event notification transmission processing.

  On the other hand, when there is a condition that is not satisfied (step S3103: NO), the context management server 110 determines whether or not all conditions for canceling the type of the monitoring context are satisfied (step S3105).

  Here, when all the conditions are satisfied (step S3105: Yes), the context management server 110 transmits a callback trigger notification indicating callback cancellation to the callback control server 120 (step S3106). The trigger notification transmission process ends.

  On the other hand, when there is a condition that is not satisfied (step S3105: No), the context management server 110 ends the callback trigger notification transmission process. As a result, the context management server 110 monitors the context of the communication terminal T to be monitored, and transmits a callback trigger notification to the callback control server 120 when the communication terminal T is in an incoming call permission state. Can do.

  As described above, according to the communication control method, the communication control apparatus 100, and the communication control system, when the receiving terminal R does not accept the call, the context of the receiving terminal R is monitored, and the receiving terminal R It is determined that is in the incoming call permission state. Then, the communication control apparatus 100 transmits a callback request only when the receiving terminal R is in the incoming call permission state. As a result, the user of the receiving terminal R does not need to remember that a callback is necessary, and the time and effort of the user of the receiving terminal R can be reduced. Further, the callback is performed only when the receiving terminal R is in the incoming call permission state, and the convenience of the receiving terminal R can be improved.

  Further, the communication control apparatus 100 receives the notification that there has been an incoming call rejection event from the receiving terminal R, and starts to determine that the receiving terminal R has entered the incoming call permission state. Requests can be sent.

  Further, when the communication control apparatus 100 includes the call control server 130 and controls communication between the caller terminal S and the callee terminal R, by detecting an incoming call rejection event generated by the call control server 130, Then, it is possible to start the determination that the receiving-side terminal R is in an incoming call permission state and transmit a callback request.

  Further, the communication control apparatus 100 transmits a callback request only when the receiving terminal R is in an incoming call permission state and when the calling terminal S is in an incoming call permission state, The convenience of the communication terminal T can be improved. In addition, the communication control device 100 sets a different incoming call permission state for each communication partner, for example, a call-permitted state for a call with a high degree of urgency due to requirements related to a customer or a customer's calling terminal S Therefore, it is possible to determine that the caller terminal S possessed by the colleague is in an unacceptable state. Therefore, the convenience of the communication terminal T can be further improved.

  In addition, the communication control apparatus 100 receives the callback request cancellation request and does not transmit the callback request, and therefore does not make an unnecessary callback request. For this reason, the user of the transmitting terminal S and the user of the receiving terminal R do not have to spend unnecessary effort such as responding to an unnecessary callback request.

  The communication control method described in this embodiment can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. The communication control program is recorded on a computer-readable recording medium such as a hard disk, a flexible disk, a CD-ROM, an MO, and a DVD, and is executed by being read from the recording medium by the computer. The communication control program may be distributed via a network such as the Internet.

  The following additional notes are disclosed with respect to the embodiment described above.

(Supplementary note 1)
A detection step of detecting that the second terminal has not accepted a call from the first terminal;
By referring to storage means for storing a context indicating permission or non-permission for each terminal when it is detected by the detection step that the second terminal has not accepted a call from the first terminal. A determination step of determining whether the second terminal is in an incoming call permission state;
A transmission step of transmitting a callback request to the first terminal to the second terminal when it is determined that the incoming call is permitted by the determination step;
The communication control method characterized by performing.

(Supplementary Note 2) The detection step includes
The communication control method according to appendix 1, wherein an operation for rejecting an incoming call is performed at the second terminal with respect to a call from the first terminal.

(Supplementary Note 3) The detection step includes
When it is detected that a call is transmitted from the first terminal to the second terminal, it is determined by referring to the storage means that the second terminal is in an incoming call rejection state. The communication control method according to appendix 1, wherein it is detected that the second terminal has not accepted a call from the first terminal.

(Appendix 4)
When it is detected by the detection step that the second terminal has not accepted the call from the first terminal, the second call is transmitted from the first terminal by referring to the storage means. 4. The communication control method according to any one of appendices 1 to 3, wherein it is determined whether the terminal is in an incoming call permission state.

(Appendix 5)
When it is detected by the detecting step that the second terminal has not accepted a call from the first terminal, the first and second terminals are permitted to receive a call by referring to the storage means. It is judged whether it is a state, The communication control method as described in any one of the additional remarks 1-3 characterized by the above-mentioned.

(Appendix 6)
When it is detected by the detection step that the second terminal has not accepted the call from the first terminal, the second call is transmitted from the first terminal by referring to the storage means. The communication according to any one of appendices 1 to 3, wherein a determination is made as to whether or not the first terminal is in an incoming call permission state and whether or not the first terminal is in an incoming call permission state. Control method.

(Supplementary note 7)
When it is detected by the detection step that the second terminal has not accepted the call from the first terminal, the second call is transmitted from the first terminal by referring to the storage means. And determining whether the first terminal is in an incoming call permission state for outgoing calls from the second terminal. The communication control method according to any one of the above.

(Appendix 8) The detection step includes
Detecting a request to cancel the callback request from the first terminal;
The transmission step includes
The communication control method according to any one of appendices 1 to 7, wherein when the cancellation request is detected by the detection step, the callback request is not transmitted to the second terminal.

(Supplementary note 9) The transmission step includes:
The communication control method according to any one of appendices 1 to 8, wherein a callback request to the first terminal including an identifier for identifying the first terminal is transmitted to the second terminal. .

(Supplementary Note 10) The transmission step includes:
The callback request to the first terminal including software for executing transmission to the first terminal is transmitted to the second terminal. Communication control method.

(Supplementary Note 11) The transmission step includes
The communication control method according to any one of supplementary notes 1 to 8, wherein a callback request to the first terminal is transmitted to the first terminal and the second terminal.

(Additional remark 12) The memory | storage means which memorize | stores the context which shows an incoming call permission or disapproval for every terminal,
Detecting means for detecting that the second terminal has not accepted a call from the first terminal;
When it is detected by the detection means that the second terminal has not accepted a call from the first terminal, the second terminal is in an incoming call permission state by referring to the storage means. A judging means for judging whether or not
A transmission unit that transmits a callback request to the first terminal to the second terminal when the determination unit determines that the incoming call is permitted;
A communication control apparatus comprising:

(Supplementary note 13) A communication control system in which a first device for controlling outgoing and incoming calls between terminals and a second device for controlling callback to a caller terminal are connected,
The second device includes:
Storage means for storing a context indicating call acceptance or disapproval for each terminal;
Detecting means for detecting that the second terminal has not accepted a call from the first terminal;
When it is detected by the detection means that the second terminal has not accepted a call from the first terminal, the second terminal is in an incoming call permission state by referring to the storage means. A judging means for judging whether or not
A transmission unit that transmits a callback request to the first terminal to the second terminal when the determination unit determines that the incoming call is permitted;
The first device includes:
A communication control system for notifying the second device that a call is transmitted from the first terminal to the second terminal.

(Supplementary note 14) A communication control system in which a first device for controlling outgoing / incoming calls between terminals and a second device for controlling callback to a caller terminal are connected,
The second device includes:
Storage means for storing a context indicating call acceptance or disapproval for each terminal;
Detecting means for detecting that the second terminal has not accepted a call from the first terminal;
When it is detected by the detection means that the second terminal has not accepted a call from the first terminal, the second terminal is in an incoming call permission state by referring to the storage means. A judging means for judging whether or not
A transmission unit that transmits a callback request to the first terminal to the first device when the determination unit determines that the incoming call is permitted.
The first device includes:
The communication characterized by notifying the second device that the first terminal has transmitted to the second terminal, and notifying the second device of the callback request from the transmission means. Control system.

DESCRIPTION OF SYMBOLS 100 Communication control apparatus 110 Context management server 120 Callback control server 130 Call control server S Originating side terminal R Terminating side terminal 801 Storage part 802 Detection part 803 Judgment part 804 Transmission part

Claims (11)

Computer
A detection step of detecting that the second terminal has not accepted a call from the first terminal;
By referring to storage means for storing a context indicating permission or non-permission for each terminal when it is detected by the detection step that the second terminal has not accepted a call from the first terminal. A determination step of determining whether the second terminal is in an incoming call permission state;
A transmission step of transmitting a callback request to the first terminal to the second terminal when it is determined that the incoming call is permitted by the determination step;
The communication control method characterized by performing. The detection step includes
2. The communication control method according to claim 1, wherein an incoming call rejection operation is performed at the second terminal for a call from the first terminal. The detection step includes
When it is detected that a call is transmitted from the first terminal to the second terminal, it is determined by referring to the storage means that the second terminal is in an incoming call rejection state. The communication control method according to claim 1, further comprising detecting that the second terminal has not accepted a call from the first terminal. The determination step includes
When it is detected by the detection step that the second terminal has not accepted the call from the first terminal, the second call is transmitted from the first terminal by referring to the storage means. 4. The communication control method according to claim 1, wherein it is determined whether the terminal is in an incoming call permission state. 5. The determination step includes
When it is detected by the detecting step that the second terminal has not accepted a call from the first terminal, the first and second terminals are permitted to receive a call by referring to the storage means. It is judged whether it is in a state, The communication control method as described in any one of Claims 1-3 characterized by the above-mentioned. The determination step includes
When it is detected by the detection step that the second terminal has not accepted the call from the first terminal, the second call is transmitted from the first terminal by referring to the storage means. The terminal according to any one of claims 1 to 3, further comprising: determining whether the terminal is in an incoming call permission state and determining whether the first terminal is in an incoming call permission state. Communication control method. The determination step includes
When it is detected by the detection step that the second terminal has not accepted the call from the first terminal, the second call is transmitted from the first terminal by referring to the storage means. And determining whether the first terminal is in an incoming call permission state for outgoing calls from the second terminal. 4. The communication control method according to any one of 3. The detection step includes
Detecting a request to cancel the callback request from the first terminal;
The transmission step includes
8. The communication control method according to claim 1, wherein when the cancellation request is detected by the detection step, the callback request is not transmitted to the second terminal. Storage means for storing a context indicating call acceptance or disapproval for each terminal;
Detecting means for detecting that the second terminal has not accepted a call from the first terminal;
When it is detected by the detection means that the second terminal has not accepted a call from the first terminal, the second terminal is in an incoming call permission state by referring to the storage means. A judging means for judging whether or not
A transmission unit that transmits a callback request to the first terminal to the second terminal when the determination unit determines that the incoming call is permitted;
A communication control apparatus comprising: A communication control system in which a first device for controlling outgoing / incoming calls between terminals and a second device for controlling callback to a caller terminal are connected,
The second device includes:
Storage means for storing a context indicating call acceptance or disapproval for each terminal;
Detecting means for detecting that the second terminal has not accepted a call from the first terminal;
When it is detected by the detection means that the second terminal has not accepted a call from the first terminal, the second terminal is in an incoming call permission state by referring to the storage means. A judging means for judging whether or not
A transmission unit that transmits a callback request to the first terminal to the second terminal when the determination unit determines that the incoming call is permitted;
The first device includes:
A communication control system for notifying the second device that a call is transmitted from the first terminal to the second terminal. A communication control system in which a first device for controlling outgoing / incoming calls between terminals and a second device for controlling callback to a caller terminal are connected,
The second device includes:
Storage means for storing a context indicating call acceptance or disapproval for each terminal;
Detecting means for detecting that the second terminal has not accepted a call from the first terminal;
When it is detected by the detection means that the second terminal has not accepted a call from the first terminal, the second terminal is in an incoming call permission state by referring to the storage means. A judging means for judging whether or not
A transmission unit that transmits a callback request to the first terminal to the first device when the determination unit determines that the incoming call is permitted.
The first device includes:
The communication characterized by notifying the second device that the first terminal has transmitted to the second terminal, and notifying the second device of the callback request from the transmission means. Control system.

Images