JP5802116B2 - Call system with data sharing function - Google Patents

Description

  The present invention relates to a technique for sharing data and making a call between users.

Conventionally, voice response by telephone has been mainly used for various inquiries at a call center or the like. However, with the voice alone, it is difficult for the inquiring party to explain detailed conditions and subtle events, and for the responding party, it may be difficult to explain complicated procedures and unusual operations.
For this reason, inquiries by FAX or electronic mail are also made.

JP 2003-283670 A

When making an inquiry using FAX or e-mail, it is possible to show a picture or photograph, but the description will be written in text, which is also troublesome.
Therefore, it is possible to send a picture or photo by fax or e-mail, and make an inquiry using the telephone while watching the picture or photo. In this case, the user making the inquiry can send a fax or e-mail. , Phone calls must be made separately, which takes time. Also, the call center side needs to associate FAX and e-mails and telephones that are sent separately, which is inefficient.

  On the other hand, an electronic conference system is known as a system for making a meeting while showing materials such as pictures and photographs. In the electronic conference system, it is possible to make a meeting while watching the material by transmitting and receiving the data of the material such as a diagram, a table, and a photograph together with the audio data via the network.

  However, the electronic conference system requires that each user has a device that transmits and receives audio data and document data in accordance with a predetermined standard via a network, and is not a configuration that can be applied when one user makes an inquiry to a call center. It was. In addition, when data is transmitted / received via a network, data is packetized and transmitted / received. However, in order to maintain good call quality when voice data is packet-communicated, it is difficult to cause packet loss. It was necessary to set up the environment and secure sufficient bandwidth, and could not be easily introduced.

  In addition, a so-called video phone is also put into practical use, in which a caller is photographed with a camera and this image data is transmitted together with audio data to the other party via a telephone line. Videophones occupy the necessary bandwidth every time a call is connected, so the call quality will not deteriorate, but image data bandwidth will also be secured, so a large amount of bandwidth will be occupied on the telephone line. There is a problem that.

  Accordingly, an object of the present invention is to provide a technique for transmitting shared data to a user terminal in association with a call, sharing the data between the user terminals, and performing a call.

In order to solve the above problems, the message management system of the present invention provides:
A data receiving unit for receiving shared data addressed to the terminal of the second user from the terminal of the first user via the network;
A linkage number issuing unit for issuing a linkage phone number corresponding to the shared data;
A data transmission unit for transmitting the shared data together with the cooperation telephone number to the terminal of the second user;
A first call control unit for establishing a call with a terminal of a first user via a telephone line;
Call the second user's terminal via the telephone line with the cooperation telephone number as the caller number, or call made to the cooperation telephone number from the second user's terminal via the telephone line A second call control unit to receive,
Is provided.

  When the second user's terminal receives a call using the link telephone number as the caller number or when a call addressed to the link telephone number is established, the call system And an output control unit that outputs shared data corresponding to.

  The first call control unit makes a call to the first user's terminal via the telephone line using the cooperation telephone number as a caller number, or the cooperation telephone via the telephone line from the first user terminal. It may be configured to receive a call sent to a number.

In addition, in order to solve the above problems, the calling method of the present invention is:
Receiving the shared data from the terminal of the first user via the network;
Issuing a cooperation telephone number corresponding to the shared data;
Transmitting the shared data to a terminal of a second user;
Establishing a call with the first user's telephone;
Calling the second user's terminal as the caller number as the caller number, or receiving a call sent from the second user's phone to the link phone number;
Is executed by the computer.

  When the second user terminal receives a call with the link telephone number as a caller number or when a call addressed to the link telephone number is established, The step of outputting the shared data corresponding to the number may be further executed.

  Further, in the telephone call method, in the step of establishing a call with the first user's telephone, a call is made to the first user's terminal via a telephone line using the cooperation telephone number as a caller number, or You may receive the call transmitted from the said 1st user's terminal to the said telephone number for cooperation via a telephone line.

  Further, the present invention may be a program for causing a computer to execute the above calling method. Furthermore, the program may be recorded on a computer-readable recording medium.

  Here, the computer-readable recording medium refers to a recording medium that accumulates information such as data and programs by electrical, magnetic, optical, mechanical, or chemical action and can be read from the computer. . Examples of such a recording medium that can be removed from the computer include a flexible disk, a magneto-optical disk, a CD-ROM, a CD-R / W, a DVD, a DAT, an 8 mm tape, and a memory card.

  Further, there are a hard disk, a ROM (read only memory), and the like as a recording medium fixed to the computer.

  INDUSTRIAL APPLICABILITY The present invention can provide a technique for transmitting shared data in association with a call to a user terminal, sharing the data between the user terminals, and making a call.

Schematic diagram of call system Schematic diagram of application server Schematic diagram of call control device Illustration of calling method Illustration of calling method Illustration of calling method Illustration of calling method The figure which shows the modification of the telephone call method The figure which shows the modification of the telephone call method The figure which shows an example of the table which registered PhoneCookie (registered trademark) and the storage place of shared data The figure which shows the example of a screen display in the user terminal 3B in process of an incoming call Figure showing an example of broadcast destination input Explanatory diagram of the data linkage method when a broadcast destination is specified Configuration diagram of application server according to Embodiment 2 External view of user terminal according to the second embodiment Functional block diagram of user terminal The figure which shows the example of the screen which designates the telephone number Explanatory drawing of the telephone call method concerning Embodiment 2. The figure which shows the example of a display of the schedule where the information of the call was registered The figure which shows the example of a display of the information of the telephone call registered as schedule information The figure which shows the modification of the telephone call method which concerns on Embodiment 2 The figure which shows an example of the affiliation department table which matched the affiliation department and telephone number of each user The figure which shows an example of a keyword table

Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. The configuration of the following embodiment is an exemplification, and the present invention is not limited to the configuration of the embodiment.
Embodiment 1
<System configuration>
FIG. 1 is a schematic diagram of a data linkage system according to the first embodiment. The data linkage system 10 of this example includes the application server 2 and the call control device 7, and uses PhoneCookie (registered trademark) to link a call via a telephone line and data via a network.
The user terminals 3A and 3B have a function as a client terminal that performs web browsing and transmission / reception of electronic mail via a network N such as the Internet, and a function as a telephone that performs a voice call via a telephone line D. Yes. The user terminals 3A and 3B are not limited to those having the functions of the client terminal and the telephone, but the client terminal 3 and the telephone 4 may be separate.

FIG. 2 is a schematic configuration diagram of the application server 2. As shown in FIG. 2, the application server 2 includes an arithmetic processing unit 22 including a central processing unit (CPU) and a main memory, storage units (hard disks) 23 and 26 storing data and software for the arithmetic processing, The computer includes an output interface 24, a communication control unit (CCU: Communication Control Unit) 25, and the like.

  The input / output interface 24 is an interface that is connected to input / output means and performs input / output of signals. A console (including a keyboard and a display), a storage medium read / write device, and the like are appropriately connected to the input / output interface 24 as input / output means.

  The CCU 25 establishes a connection with another computer via the network N, and controls communication with the other computer according to a command from the CPU.

  Software such as an operating system (OS) and application software (call program) is installed in the storage unit 23. The storage unit 26 stores contact data, shared data, and the like.

The arithmetic processing unit 22 appropriately reads out and executes the OS and application program from the storage unit 23 and performs arithmetic processing on information input from the input / output interface 24 and the CCU 25 and information read from the storage units 23 and 26. , PhoneCookie issuing unit (linkage number issuing unit) 221, call control link unit 222, data receiving unit 223, and data transfer unit (data transmitting unit) 224.

  The data reception unit 223 receives call request information such as shared data addressed to the second user's terminal, information on the sender of the shared data, and information on the destination of the shared data from the first user's terminal via the network.

When the PhoneCookie issuing unit 221 receives call request information from the terminal of the first user ,
Issue a phone number for cooperation as PhoneCookie corresponding to the call request information. This link telephone number is a telephone number reserved for the call control device so that the call control device 7 will receive a call when a call is made to the telephone number from the user terminal 3A, 3B or telephone 4 as will be described later. It is. For example, when an 11-digit telephone number such as 050-ABCD-xxx is used, 10,000 telephone numbers from 0000 for the last 4 digits to 9999 for the last 4 digits are secured. That is, if the first seven digits are 050-ABCD, all calls are received by the call control device 7 regardless of the number of the last four digits. Therefore, even when the last four digits are numbered freely and notified to the user, all calls addressed to this number can be received by the call control device 7. In this way, a plurality of telephone numbers for the call control device 7 are secured, and the PhoneCookie issuing unit 221 assigns one of the phone numbers for the call control device 7 as PhoneCookie to each call request information, and each PhoneCookie makes a call. Make it unique among all PhoneCookies assigned to request information. That is, call request information corresponding to PhoneCookie can be uniquely specified.

  The call control cooperation unit 222 transmits a command for controlling the call to the call control device 7 based on the call request information. For example, when the call request information is received from the terminal of the first user, the call control device includes a command for establishing a call between the user and the contact, and a telephone instruction parameter including the user's telephone number and the contact's telephone number. 7 to send.

  The data transfer unit 224 transmits the shared data received from the first user terminal to the second user terminal.

On the other hand, the call control device 7 is a device that controls calls between telephones via the telephone line network D. In the present embodiment, the call control device 7 is a CTI server that controls calls between telephones by SIP (Session Initiation Protocol). Note that the call control device 7 according to the present embodiment is not limited to the SIP server, but may be a telephone switch of another system as long as the call can be controlled according to a command from the application server 2. FIG. 3 is a schematic configuration diagram of the call control device 7. As shown in FIG. 3, the call control device 7 includes an arithmetic processing unit 72 composed of a central processing unit (CPU) and a main memory, a storage unit (hard disk) 73 storing data and software for arithmetic processing, input / output The computer includes an interface 74, a communication control unit (CCU) 75, and the like.

  The input / output interface 74 is an interface that is connected to input / output means and performs input / output of signals. To the input / output interface 74, a console (including a keyboard and a display), a read / write device for a storage medium, and the like are appropriately connected as input / output means.

  The CCU 75 establishes a connection with another device via the telephone line network D, and controls communication according to a command from the CPU. The CCU 75 of this embodiment performs communication according to SIP, and controls calls such as the telephone 4 and user terminals 3A and 3B via a VoIP gateway and a radio base station in the telephone network D. For example, the telephone 4 is accommodated in a VoIP gateway in the telephone network D, and voice signals and control signals from the telephone 4 are converted into VoIP packets by the VoIP gateway and sent to the call control device 7. The VoIP packet transmitted from the call control device 7 to the telephone 4 is converted into a voice signal or a control signal by the VoIP gateway and sent to the telephone 4. In addition, user terminals 3A and 3B having a call function such as a mobile phone and a smartphone are accommodated in a radio base station via a mobile phone line, and audio signals and control signals from the user terminals 3A and 3B are transmitted from the radio base station. It is converted into a VoIP packet and sent to the call control device 7. The VoIP packet transmitted from the call control device 7 to the user terminal 3 is converted into a voice signal or a control signal by the radio base station and sent to the user terminals 3A and 3B.

  Software such as an operating system (OS) and application software is installed in the storage unit 73.

  The arithmetic processing unit 72 appropriately reads out and executes the OS and application program from the storage unit 73, and performs arithmetic processing on information input from the input / output interface 74 and the CCU 75 and information read from the storage unit 73. It also functions as one call control unit 721, second call control unit 722, and connection control unit 723.

The first call control unit 721 establishes a call with the originating user terminal 3A, and transmits and receives voice data. For example, when the user terminal 3A calls a predetermined telephone number (PhoneCookie in this example), the first call control unit 721 of the call control device 7 receives the call and makes a call to the user terminal 3A. Establish.

The second call control unit 722 establishes a call with the receiving user terminal 3B. For example, a telephone instruction based on the call destination information is received from the application server 2, and PhoneCookie is set as a caller number, and a call is made to the call destination telephone number, that is, to the receiving user terminal 3B. Alternatively, it receives a call sent from the receiving user terminal 3B to PhoneCookie via the telephone line D.

  The connection control unit 723 receives a call control command from the application server 2 and controls the first call control unit 721 and the second call control unit 722 in accordance with the command, so that the user terminal 3, the contact telephone 4, etc. Perform call control. For example, voice data received by the first call control unit 721 via a call with the user terminal 3 is transmitted from the second call control unit 722 to the telephone 4 via a call with the telephone 4, and a call with the telephone 4 is made. The voice data received by the second call control unit 722 via the first call control unit 721 is transmitted from the first call control unit 721 to the user terminal 3 via a call with the user terminal 3, thereby making a call between the user terminal 3 and the telephone 4. It is possible. The process of connecting these two calls is so-called third party call control, and since a known technique can be used, detailed description is omitted. Note that the number of calls to be connected is not limited to two, and may be three or more calls.

  In addition, the connection control unit 723 disconnects the call when receiving the call end signal or the disconnection signal of the call for which the call control is performed, and notifies the call control cooperation unit 222 of the application server 2 that the call has ended.

<Data linkage method>
Next, a data linkage method executed by the data linkage system will be described with reference to FIGS.

  As shown in FIG. 4, first, the user terminal 3 </ b> A activates the application and receives input of call destination information such as a call destination telephone number and a destination address by the user's operation on the calling side (S <b> 11). FIG. 9 shows a state in which an application is activated on the user terminal 3A and a call destination input screen is displayed. When the user presses the input key 50 in the number input mode displayed on the display unit, the input is made as a call destination telephone number on the touch panel and displayed in the telephone number column 51. When the user switches the input key 50 to the alphabet input mode and presses the input key 50, the destination address of the data shared with the call destination is input by the touch panel and displayed in the address field 52. As described above, the user is not limited to directly inputting the call destination, but may be configured to select the call destination from the address book. For example, when the address book icon 53 is selected, the user terminal 3A reads a list of call partners registered in advance from the storage unit, that is, an address book (not shown) and displays it on the display unit. The telephone number and address of the called party are set as the destination telephone number and destination address.

Next, a selection of a file to be shared during a call is received (S12). For example, when the file icon 54 is selected, the user terminal 3A displays the directory structure in the storage unit and the files stored in the directory in a tree shape to prompt selection, and the user selects the selected file as shared data. Accept as. The shared data may be a shared file itself or information for accessing a shared file such as a URL. For example, when the browser icon 55 is selected, the user terminal 3A reads the browsing history and bookmarks of the web browser and displays them in a list, and accepts URLs selected by the user from the browsing history and bookmarks as shared data. Further, when the GPS icon 56 is selected, the user terminal 3A obtains the current position based on GPS signals received from a plurality of GPS satellites, and accepts this position information as shared data.
Further, the user terminal 3A may accept title information as a subject of a call as shared data. For example, when the user switches the input key 50 shown in FIG. 9 to the alphabet input mode and presses the input key 50, title information is input by the touch panel and displayed in the title column 58. The example of FIG. 9 shows an example in which “Immediately! The title information is not limited to what is directly input by the user, and the file name of the file selected as shared data may be used as the title information. If the file selected as shared data is a document file, the first character string or heading character may be extracted from the document file as title information. Furthermore, the web page corresponding to the URL selected as the shared data, that is, the title or headline character of the web page to be shared may be extracted and used as title information. Further, a thumbnail image of shared data such as a file selected as shared data, a web page corresponding to a URL, a map corresponding to position information, or the like may be added as title information. FIG. 9 shows an example in which a thumbnail image 59 of an image file selected as shared data is displayed at the right end of the title field 58.
Moreover, in this system, since the PhoneCookie is notified to the receiving side as the caller number and the telephone number of the caller is not notified, the caller information may be input as shared data and transmitted to the receiving side. The caller information is, for example, a caller's name, nickname, user ID, and caller image. The user terminal 3A may be configured to accept caller information input by the user at the time of transmission, or may read information registered in advance in the storage unit and accept it as caller information. In this example, the name stored as the owner information in the storage unit of the user terminal 3A is read and used as the sender information.

  When the user selects the call button 57, the user terminal 3A receives the information requesting the application server 2 for a call, the destination information received in step S11, and the shared data received in step S12. A call request is transmitted to the application server 2 via the network N (S13). Note that the process of extracting characters from a document file or a web page to obtain title information, the process of creating a thumbnail image of shared data to obtain title information, and the like are not limited to those executed by the user terminal 3, but an application server 2 may be configured to create title information based on shared data received from the user terminal 3.

Upon receiving this communication request (S14), the application server 2 issues a unique telephone number corresponding to the communication request as a PhoneCookie and notifies the user terminal 3A (S1).
5).

When PhoneCookie is received (S16), the user terminal 3A makes a call to the telephone number as PhoneCookie (S17). The call destined for PhoneCookie may be automatically made by the user terminal 3A when the PhoneCookie is received, or when the user presses this button when a button for making a call is received when the PhoneCookie is received. It is good also as a structure which calls. Then, the first call control unit 721 of the call control device 7 receives the call addressed to the PhoneCookie, and establishes a call with the user terminal 3A (S18).

On the other hand, the application server 2 transmits the shared data received from the user terminal 3A together with the PhoneCookie to the user terminal 3B based on the call destination information (S19). The user terminal 3B receives the shared data and PhoneCookie from the application server 2, and stores the received shared data and PhoneCookie in the storage unit in association with each other (S20). For example, using PhoneCookie as an index, the storage location of the corresponding shared data is registered in the table. FIG. 10 is a diagram illustrating an example of a table in which the received PhoneCookie and the storage destination of the shared data are registered.

Further, the call control cooperation unit 222 of the application server 2 transmits to the call control device 7 a telephone instruction parameter for instructing a call to the user terminal 3B, that is, a call addressed to the call destination telephone number. The second call control unit 722 of the call control device 7 makes a call to the user terminal 3B based on the call destination telephone number of the telephone instruction parameter and notifies the PhoneCookie as the caller number (S
21). When the user terminal 3B receives the call from the call control device 7 (S22), the user terminal 3B reads the shared data corresponding to the PhoneCookie as the caller number from the storage unit and displays it on the display unit (S23). FIG. 11 shows a screen display example in the user terminal 3B that is receiving a call. As shown in FIG. 11, when an incoming call is received, PhoneCookie 61 as a caller number is displayed, and at least a part of shared data corresponding to the PhoneCookie 61, for example, caller information 6 is displayed.
2, title information 63, thumbnail image 63 </ b> A, and the like are read from the storage unit and displayed. Thereby, the user on the receiving side can determine whether or not reception is possible by looking at the displayed title information and sender information. For example, in the case of refusing reception, the end button 64 is selected to end the process. When receiving, when the user selects the reception button 65, the user terminal 3 </ b> B establishes a call with the call control device 7. Here, the call control device 7 enables a call between the user terminal 3A and the user terminal 3B by connecting a call with the user terminal 3A and a call with the user terminal 3B. The user terminal 3B starts and displays shared data corresponding to the PhoneCookie 61 as shown in FIG. The user terminal 3A also displays the shared data transmitted to the user terminal 3B on the display unit (S24).

Since the shared data can be transmitted in association with the call in this way, the data can be shared between the calling user terminal 3A and the called user terminal 3B during the call. Therefore, it is possible to have a specific conversation while watching the shared data, and to communicate closely. In FIG. 1, the user terminal 3A sends the location information of the current location as shared data, acquires an image of the current location, a so-called street view from a server that provides map information etc. on the network N, and displays it on the user terminals 3A and 3B. An example is shown. That is, each user can share the same image data and have a conversation based on the shared data, such as “turn right at the back of the fast food restaurant with a red signboard”.

4 shows an example in which the shared data is transmitted at the time of outgoing call, but the shared data can be transmitted and shared during a call. FIG. 5 is an explanatory diagram of processing for sending a shared file from the user terminal 3B to the user terminal 3A during a call.
When the user selects shared data during a call (S31) and selects a call button, the user terminal 3B transmits the selected shared data to the application server 2 together with PhoneCookie (S32).

The application server 2 that has received this shared data (S33)
Based on, information on the terminal to which the PhoneCookie is assigned is read from the storage unit 26, and the shared data is transmitted to the user terminal 3A (S34).

When shared data and PhoneCookie are received from the application server 2 (S35),
The user terminal 3A displays the received shared data on the display unit if the received PhoneCookie matches the caller ID of the call in progress (S36).

By transmitting the shared data together with the PhoneCookie to the application server 2 in this way, the data can be shared during a call with a call partner (user terminal 3A) to which the PhoneCookie is assigned.

  In addition, in steps S31 to S36 in FIG. 5, an example of transmission from the reception-side user terminal 3B to the transmission-side user terminal 3A has been shown. Similarly, as illustrated in steps S41 to S46, the transmission-side user terminal 3A to the reception-side user It can also be transmitted to the terminal 3B.

Then, when ending the call, for example, when the user on the calling side selects the end call, the user terminal 3A transmits an end call signal to the call control device 7 as shown in FIG. Processing such as output of shared data is terminated (S51).
When the call end signal is received from the user terminal 3A (S52), the call control device 7 disconnects the call with the user terminal 3A and transmits the call end signal to the user terminal 3B (S53).

  When the call termination signal is received from the call control device 7 (S54), the user terminal 3B transmits a disconnection signal to the call control device 7 (S55), and disconnects the call based on the disconnection signal received by the call control device 7. (S56) The application server 2 is notified that the call has ended (S57).

  When notified of the end of the call, the application server 2 releases the PhoneCookie assigned to the call, that is, deletes information such as the user terminal associated with the PhoneCookie, thereby enabling a new assignment.

  In the example of FIG. 6, the end of the call is notified first from the calling user terminal 3A. However, the present invention is not limited to this, and the end of the call is notified first from the receiving user terminal 3B. Contrary to the above flow, the end of the call may be notified to the user terminal 3A.

Further, the timing for releasing PhoneCookie is not limited to the time when the call ends, and may be configured to be opened after the expiration of the valid period. In this case, if it is within the validity period, it is possible to make a call again by using the PhoneCookie.

FIG. 7 is an explanatory diagram for making a call again according to PhoneCookie.
When a call is made from the user terminal 3A to the telephone number as PhoneCookie by the user's operation (S61), the first call control unit 721 of the call control device 7 receives the call and establishes the call (S62). 723 notifies the call control cooperation unit 222 of the application server 2 that the incoming call addressed to PhoneCookie is received, and confirms whether or not the PhoneCookie is within the valid period (
S63). The call control cooperation unit 222 refers to the storage unit, determines whether or not the current time exceeds the valid period of the PhoneCookie, and replies to the call control device 7 (S64).

Based on the response from the control cooperation unit 222, the call control device 7 terminates the processing if the PhoneCookie is outside the valid period (not shown), and makes a call to the user terminal 3B if the PhoneCookie is within the valid period (S65). ). The user terminal 3B that has received the call from the call control device 7 (S66) reads out the shared data corresponding to the caller number (PhoneCookie) of the call from the storage unit and displays it (S67). Further, the shared data corresponding to the PhoneCookie is also read from the storage unit and displayed on the originating user terminal 3A (S68).

  In the example of steps S61 to S68, an example is shown in which the user terminal 3A is redialed. However, the present invention is not limited to this, and as shown in steps S71 to S78 contrary to the processing flow of steps S61 to S68 described above. In addition, the user terminal 3B can be redirected to PhoneCookie.

Therefore, if the call is once within the valid period even after the call is terminated, the call between the user terminals 3A-3B can be resumed by calling the PhoneCookie from either the user terminal 3A or the user terminal 3B, and the shared data You can talk while watching.

Similarly, when a communication request is made from the calling user terminal 3A, even if the receiving user terminal 3B cannot receive a call and the process ends without connecting the call between the user terminals 3A and 3B, By making a call to PhoneCookie from either the user terminal 3A or the user terminal 3B, the user terminal 3A-3B can talk while viewing the shared data.

As described above, according to the present embodiment, since shared data can be associated with a call using PhoneCookie, it is possible to implement a call with a call partner while referring to the shared data by sending the shared data attached to the call. .

<Modification 1>
In the first embodiment, an example in which a call is made from the calling user terminal 3A to PhoneCookie is shown. However, a configuration may be adopted in which a call is made from the center side, that is, from the call control device 7 to the user terminal 3A. FIG. 8 is an explanatory diagram of a modification in which a call is made from the call control device 7 to the user terminal 3A.

As shown in FIG. 8, in this modification, first, when a communication request is made from the user terminal 3A (S11 to S13) as in the above-described embodiment (FIG. 4), the application that receives this communication request (S14). The server 2 issues a unique telephone number corresponding to the communication request as PhoneCookie (S15). Further, the application server 2 sends telephone instruction parameters including the telephone number of the user terminal 3A, the telephone number (call destination telephone number) of the user terminal 3B, and the PhoneCookie (caller number) to the call control device 7 to perform call control. (S15A).

The call control device 7 that has received the telephone instruction parameter first calls the user terminal 3A based on the caller number (S16A). Here, the call control device 7 sets the caller number as PhoneCookie.
That is, the user terminal 3A that has received the call from the call control device 7 (S17A) stores the PhoneCookie in the storage unit as an incoming call history.

When the call control device 7 establishes a call with the user terminal 3A (S18), the call control device 7 makes a call to the user terminal 3B based on the call destination telephone number of the telephone instruction parameter as in the above-described embodiment (FIG. 4). (S21). When the user terminal 3B receives the call from the call control device 7 (S22), the shared data corresponding to the PhoneCookie as the caller number is read from the storage unit,
This is displayed on the display unit (S23). The user terminal 3A also displays the shared data transmitted to the user terminal 3B on the display unit (S24).

  As described above, even with the configuration of the present modification, it is possible to transmit the call with the shared data attached to the call and call the call partner while referring to the shared data, as in the above-described embodiment.

<Modification 2>
In the first embodiment, an example in which a caller and a receiver make a call with two people has been shown. However, the present invention is not limited to this, and the caller designates a plurality of recipients and calls with three or more people. There may be.

  In FIG. 9, when the CC button 41 is selected, the call destination column becomes “Broadcast 1” as shown in FIG. 12, and another call destination (hereinafter also referred to as a broadcast destination) can be input. As for the broadcast destination, the telephone number and the address are input in the respective columns 51 and 52 as described above. The number of broadcast destinations is not limited to one, and can be increased to “broadcast 2” or “broadcast 3” each time the CC button 41 is selected. Further, even if the BCC button 42 is selected, a broadcast destination can be added in the same manner. Further, a list in which broadcast destinations are registered in advance may be stored, and the broadcast destination registered in the list may be read and added by selecting the list button 43.

  FIG. 13 is an explanatory diagram of a data linkage method when a broadcast destination is designated. In FIG. 13, 31 is a user terminal 3B designated as a call destination, and 32 is a user terminal 3B designated as a broadcast destination. In the second modification, an example in which the number of broadcast destinations is one is shown. However, even if there are two or more broadcast destinations, the same can be realized by only performing a plurality of communications with the broadcast destinations.

  First, the user terminal 3A receives an input of a call destination (including a broadcast destination) (S11), receives a selection of a shared file (S12), and transmits a communication request to the application server 2 (S13).

Upon receiving this communication request (S14), the application server 2 issues a unique telephone number corresponding to the communication request as a PhoneCookie, and the shared data received from the user terminal 3A together with the PhoneCookie, based on the destination information. It transmits to the user terminal 3B (31) and the user terminal 3B (32) of the broadcast destination (S19). These user terminals 3B receive the shared data and PhoneCookie from the application server 2, and store the received shared data and PhoneCookie in the storage unit in association with each other (S20).

On the other hand, the application server 2 notifies the PhoneCookie user terminal 3A issued in step S15. When receiving the PhoneCookie from the application server 2 (S16), the user terminal 3A makes a call to the telephone number as the PhoneCookie (S17).

The call control device 7 receives a call addressed to the PhoneCookie from the user terminal 3A, establishes a call with the user terminal 3A (S18), and based on the telephone instruction parameter corresponding to the PhoneCookie. A call is made to the user terminal 3B (31) as a call destination and the user terminal 3B (32) as a broadcast destination (S21). Then, the call control device 7 receives a response from the user terminal 3B (31) that is the call destination and the response from the user terminal 3B (32) that is the broadcast destination (S21), and establishes a call with each of the user terminal 3B (31) and the user terminal 3A. The call and the call with the user terminal 3B (31, 32) are connected to enable a three-party call. Further, the user terminal 3A and the user terminal 3B (31, 32) display the shared data on the display unit (S23, S24).
Thereby, it is possible to make a call while sharing data among three or more parties.

In addition, when transmitting the shared data to each user terminal 3 </ b> B in step S <b> 19, the application server 2 transmits the broadcast destination information together with the sender information. Thereby, when the user terminal 3B receives a call from the call control device 7 in step S21, the user terminal 3B can display the information of the broadcaster together with the caller information corresponding to the PhoneCookie on the incoming call screen. In step S11, the call control device 7 transmits only the broadcast destination information added by the user (sender) selecting the CC button 41 to the user terminal 3B, and the user (sender) The broadcast destination information added by selecting the button 42 is not transmitted to the user terminal 3B. For this reason, the broadcast destination added by the BCC button 42 is not displayed on the user terminal 3B of the other call destination, and can join the call while hiding its presence. In this case, the broadcast-destination user terminal 3B added by the BCC button 42 is configured to receive only and not transmit, for example, the call control device 7 transmits the voice from the user terminal 3B to the other user terminal 3B. It is good also as a structure which does not relay to.

<< Embodiment 2 >>
The second embodiment is different from the first embodiment in the configuration for managing calls by the schedule management unit. In addition, compared with the above-mentioned Embodiment 1, the same code | symbol is attached | subjected to the same element etc., and description again is abbreviate | omitted.

  FIG. 14 is a configuration diagram of the application server 2 according to the second embodiment. As shown in FIG. 14, the application server 2 of the second embodiment includes a schedule management unit 225 in addition to the configuration shown in FIG. In the second embodiment, the application server 2 includes the schedule management unit 225. However, the present invention is not limited to this, and the server separate from the application server 2 includes the schedule management unit 225 to manage the schedule. Also good.

  The schedule management unit 225 stores the schedule information of each user and provides the schedule information in response to requests from the user terminals 3A and 3B. That is, each user can register a schedule in the application server 2 through the user terminals 3A and 3B, and can check the schedule through the user terminals 3A and 3B as appropriate.

  FIG. 15 is an external view of the user terminals 3A and 3B according to the second embodiment. As shown in FIG. 15, the user terminals 3 </ b> A and 3 </ b> B include a handset 37, a display unit 38, and a touch panel 39 superimposed on the display unit 38, and the user performs transmission and reception operations on the touch panel 39 with the handset 37 in hand. It is possible to make a call while watching the display unit 38.

FIG. 16 is a functional block diagram of the user terminals 3A and 3B. As shown in FIG. 16, the user terminals 3A and 3B include an arithmetic processing unit 32 including a central processing unit (CPU) and a main memory, a storage unit (SDD) 33 storing data and software for arithmetic processing, and an input unit. The computer includes an output interface 34, a communication control unit (CCU) 35, a call control unit 36, and the like.

  The input / output interface 34 is an interface that is connected to input / output means and performs input / output of signals. To the input / output interface 34, a receiver having a speaker and a microphone, a storage medium read / write device, a camera, a touch panel 39, a display unit 38, and the like are appropriately connected as input / output means.

The call control unit 36 is connected to the call control device 7 via the telephone line D and establishes a call to control the call. For example, a voice signal is received from the call control device 7 via a call, and is sent to the speaker of the receiver 37 and output as a voice. Further, the voice uttered by the user toward the receiver 37 is converted into an electric signal by the microphone, and the call control unit 36 transmits this signal to the call control device 7 as a voice signal.

  The CCU 35 establishes a connection with another computer via the network N, and controls communication with the other computer in accordance with a command from the CPU.

  The storage unit 33 is installed with software such as an operating system (OS) and application software (call program), and stores contact data and the like.

  The arithmetic processing unit 32 appropriately reads out and executes the OS and application programs from the storage unit 33, and performs arithmetic processing on information input from the input / output interface 34 and the CCU 35 and information read from the storage unit 33, thereby obtaining data. It also functions as a cooperation unit 321, a scheduling unit 322, and a call instruction unit 323.

The call instruction unit 323 transmits the call destination information selected by the user by operating the touch panel 39 or the like to the application server 2 as a communication request, and makes a call to the telephone number as PhoneCookie issued from the application server 2. The call control unit 36 is instructed (notified).

The data linkage unit 321 reads out the corresponding shared data from the storage unit 33 based on PhoneCookie and outputs it. For example, an image or a web page is displayed on the display unit 38, or a sound or a moving image is reproduced.

  The scheduling unit 322 transmits schedule information input by the user by operating the touch panel 39 or the like to the application server 2 to register it. In addition, the scheduling unit 322 acquires schedule information from the application server 2 and causes the display unit 38 to display the schedule information.

FIG. 17 is a diagram illustrating an example of a screen for designating a call destination. The user inputs the destination telephone number in the telephone number column 51 and the destination address of the shared data in the address column 52 as in the above-described embodiment. In addition, the file tab 54 is selected, and shared data is selected from the files displayed in a tree shape.
Further, title information may be input in the title column 58.

  Note that the call destination information may be input by selecting the call destination button 66 and inputting predetermined call destination information. Further, a list of callees may be displayed by selecting the phone book tab 53, and a callee may be selected from this list.

  FIG. 18 is an explanatory diagram of a calling method according to the second embodiment. Note that steps S11 to S24 from the time when the user terminal 3A inputs call destination information to make a call and the time when the user terminal 3B calls and makes a call are the same as those in the first embodiment. When the call is started, the call control device 7 transmits the voice data of the call to the application server 2 (S25), and the application server 2 records this in the storage unit 26 (S26).

  When the call ends (S27), the application server 2 registers the call information in the storage unit 26 as the schedule information of the user who participated in the call (S28).

FIG. 19 is a diagram illustrating a display example of a schedule in which call information is registered, and FIG. 20 is a diagram illustrating a display example of call information registered as schedule information.

  When the schedule tab 67 shown in FIG. 17 is selected, schedule information in which the schedule is registered for each day is displayed in time series as shown in FIG. In FIG. 19, a link 68 indicates registered call information. For example, when a call is made from 10:00 to 10:45 on October 27, information on the call is registered as a schedule for this time, and title information is recorded at the date and time on the schedule as shown in FIG. The link 68 is displayed.

When the link 68 in FIG. 19 is selected, the call information is displayed in detail as shown in FIG.
In the example of FIG. 20, PhoneCookie 61, caller information 62, title information 63, shared data 69, and link 70 to voice data are displayed as call information. By selecting the link 70 to the voice data, the voice data at the time of the call stored in the storage unit 26 by the application server 2 can be downloaded or played by streaming.

Note that by selecting the call button 57, it is possible to call PhoneCookie 61 and make a call again.

As described above, according to the present embodiment, information on a call can be managed in time series by registering the call information as a schedule for the call time.
In the above description, the example of FIG. 4 is shown as the calling method. However, the present invention is not limited to this, and the second embodiment can be similarly applied to FIGS. 5 to 8 and 13.

<Modification>
FIG. 21 is a diagram illustrating a modification of the calling method according to the second embodiment. Compared with FIG. 18 of the second embodiment described above, the present modification is different in the steps for making a call to the user terminal 3B on the receiving side, and the other configurations are the same.

  FIG. 22 shows an example of a department table that associates the department to which each user belongs with the telephone number of each user. As shown in FIG. 22, for example, department A is associated with telephone numbers 050-EFGH-0001 to 050-EFGH-0003, and department B is associated with telephone numbers 050-EFGH-0011 to 050-EFGH-0013. It has been. The department table is stored in the storage unit 26 of the application server 2.

  In the call method of FIG. 21, steps S11 to S18 from when the user terminal 3A inputs call destination information to place a call and establish a call with the call control device 7 are the same as in the second embodiment.

After issuing PhoneCookie (S15), the application server 2 refers to the schedule of the user designated as the call destination (S36), and determines whether or not the user is present (S37). For example, when there is a schedule for another meeting or when there is a schedule for going out, it is determined that the person is absent, and when there is no schedule, the person is determined to be present.

  If the user is present (S37, Yes), the call control parameter is notified to the call control device 7 to make a call according to the communication request from the user terminal 3A (S38). Therefore, the call control device 7 calls the user terminal 3B (31), and the subsequent processing (S21 to S28) is the same as that in FIG.

On the other hand, when it is determined in step S37 that the user is absent, that is, not present (S
37, No), the application server 2 refers to the department table of FIG. 22 to extract the telephone number associated with the same department as the telephone number of the call and calls the telephone so as to call the telephone number. The telephone instruction parameter is notified to the control device 7 (S38A). Accordingly, the call control device 7 makes a call to the user terminal 3B (32) of the user who belongs to the same department as the user. In addition, when there are a plurality of telephone numbers associated with the same department, a random number is extracted, the smallest number or the largest number is extracted, and the next or previous number of the destination telephone number is extracted. It can be extracted by any method. Further, the process may return to step S36 so as to refer to the user's schedule corresponding to the extracted telephone number and determine whether or not the user is present. The shared data is also transmitted from the application server 2 to the user terminal 3B (32) (S19A), which is received by the user terminal 3B and stored in the storage unit (S20A).

  Then, the user terminal 3B (32) receives a call (S22A) and outputs shared data (S23A).

  Thus, according to this modification, when the receiving user is absent, the call can be transferred to another user terminal 3B in the same department.

  In the above example, the transfer is performed depending on whether or not the receiving user is present. However, the call destination may be transferred based on shared data such as title information.

  For example, as shown in FIG. 23, the application server 2 has a keyword table in which keywords and departments are stored in association with each other in the storage unit 23, and a character string from a document, a web page, title information, or the like as shared data. Are extracted from the keyword table, and a department corresponding to the matched keyword is obtained. For example, when the character string “repair” is extracted from the title information, the keyword table is referred to and the department A is obtained as the department corresponding to the matching keyword.

  Then, the application server 2 refers to the department table shown in FIG. 22, extracts the telephone number corresponding to the department A, and notifies the call control device 7 of the telephone instruction parameter so as to make a call to the telephone number ( S21), the subsequent processing (S22 to S28) is performed as in FIG.

  As a result, calls can be distributed based on shared data such as title information.

  Furthermore, a distribution based on shared data such as title information may be combined with a distribution based on a schedule.

<Others>
The present invention is not limited to the illustrated examples described above, and various modifications can be made without departing from the scope of the present invention. For example, the following configuration may be used. Each component may be combined as much as possible.

(Appendix 1)
A data receiving unit for receiving shared data addressed to the terminal of the second user from the terminal of the first user via the network;
A linkage number issuing unit for issuing a linkage phone number corresponding to the shared data;
A data transmission unit for transmitting the shared data together with the cooperation telephone number to the terminal of the second user;
A first call control unit for establishing a call with a terminal of a first user via a telephone line;
Call the second user's terminal via the telephone line with the cooperation telephone number as the caller number, or call made to the cooperation telephone number from the second user's terminal via the telephone line A second call control unit to receive,
Call system with data sharing function.

(Appendix 2)
A schedule management unit that stores schedule information of each user in a storage unit, reads and provides the schedule information according to a request,
Between the first user's terminal and the second user's terminal via the call of the first user's terminal and the first call control unit and the call of the second user's terminal and the second call control unit The call system having the data sharing function according to appendix 1, wherein, when a call is made, the schedule management unit stores information related to the call in the storage unit as information on a schedule of the time of the call.

(Appendix 3)
The call system having the data sharing function according to appendix 2, wherein the schedule management unit records at least a voice during a call as information related to the call.

(Appendix 4)
When the terminal of the second user receives a call using the link telephone number as the caller number, or when a call addressed to the link telephone number is established, the shared data corresponding to the link telephone number 4. A call system having a data sharing function according to any one of supplementary notes 1 to 3, further comprising an output control unit that outputs the data.

(Appendix 5)
The first call control unit makes a call to a first user's terminal via a telephone line using the cooperation telephone number as a caller number, or the cooperation telephone from the first user terminal via a telephone line. 5. A call system having a data sharing function according to any one of appendices 1 to 4, which receives a call sent to a number.

(Appendix 6)
Receiving the shared data from the terminal of the first user via the network;
Issuing a cooperation telephone number corresponding to the shared data;
Transmitting the shared data to a terminal of a second user;
Establishing a call with the first user's telephone;
Calling the second user's terminal as the caller number as the caller number, or receiving a call sent from the second user's phone to the link phone number;
The computer performs the calling method.

(Appendix 7)
Storing the schedule information of each user in a storage unit, further comprising the step of reading and providing the schedule information in response to a request;
Between the first user's terminal and the second user's terminal via the call of the first user's terminal and the first call control unit and the call of the second user's terminal and the second call control unit The call method according to appendix 6, wherein when a call is made, information related to the call is stored in the storage unit as information on a schedule of the time when the call is made.

(Appendix 8)
The call method according to appendix 7, wherein, at the step of reading and providing the schedule information, at least voice during a call is recorded as the information related to the call.

(Appendix 9)
When the terminal of the second user receives a call using the link telephone number as the caller number, or when a call addressed to the link telephone number is established, the shared data corresponding to the link telephone number The call method according to any one of appendices 6 to 8, wherein:

(Appendix 10)
A call made to the first user's terminal via the telephone line using the cooperation telephone number as a caller number, or a call sent from the first user terminal to the cooperation telephone number via the telephone line The calling method according to any one of appendices 6 to 9, which is received.

(Appendix 11)
Receiving the shared data from the terminal of the first user via the network;
Issuing a cooperation telephone number corresponding to the shared data;
Transmitting the shared data to a terminal of a second user;
Establishing a call with the first user's telephone;
Calling the second user's terminal as the caller number as the caller number, or receiving a call sent from the second user's phone to the link phone number;
Call program to make computer run.

(Appendix 12)
Storing the schedule information of each user in a storage unit, further comprising the step of reading and providing the schedule information in response to a request;
Between the first user's terminal and the second user's terminal via the call of the first user's terminal and the first call control unit and the call of the second user's terminal and the second call control unit The call program according to appendix 11, wherein when a call is made, information related to the call is stored in the storage unit as information on a schedule of the time when the call is made.

(Appendix 13)
The call program according to appendix 12, wherein, at the step of reading and providing the schedule information, at least voice during a call is recorded as the information related to the call.

(Appendix 14)
When the terminal of the second user receives a call using the link telephone number as the caller number, or when a call addressed to the link telephone number is established, the shared data corresponding to the link telephone number 14. The calling program according to any one of appendices 11 to 13, which outputs:

(Appendix 15)
A call made to the first user's terminal via the telephone line using the cooperation telephone number as a caller number, or a call sent from the first user terminal to the cooperation telephone number via the telephone line 15. The calling program according to any one of appendices 11 to 14, which is received.

DESCRIPTION OF SYMBOLS 1 Server 2 Application server 3A Originating user terminal 3B Receiving user terminal 7 Call control device

Claims (5)

A data reception unit that receives a call destination telephone number, shared data, and a destination address indicating a destination of the shared data as a call request from the terminal of the first user via the network;
A linkage number issuing unit for issuing a linkage phone number corresponding to the call request ;
A data transmission unit that transmits the shared data to a second user's terminal together with a cooperation telephone number based on the destination address of the call request ;
A first call control unit for establishing a call with a terminal of a first user via a telephone line;
Call the second user's terminal via the telephone line with the cooperation telephone number as the caller number, or call made to the cooperation telephone number from the second user's terminal via the telephone line A second call control unit to receive,
Equipped with a,
A call system having a data sharing function for displaying the shared data when the terminal of the first user and the terminal of the second user establish the call. A schedule management unit that stores schedule information of each user in a storage unit, reads and provides the schedule information according to a request,
Between the first user's terminal and the second user's terminal via the call of the first user's terminal and the first call control unit and the call of the second user's terminal and the second call control unit The call system having a data sharing function according to claim 1, wherein, when a call is made, the schedule management unit stores information related to the call in the storage unit as information on a schedule of the time of the call.   The call system having a data sharing function according to claim 2, wherein the schedule management unit records at least a voice during a call as information related to the call. Receiving a call destination telephone number, shared data and a destination address indicating a destination of the shared data as a call request from the terminal of the first user via the network;
Issuing a linkage phone number corresponding to the call request ;
Transmitting the shared data to a second user's terminal based on the destination address of the call request ;
Establishing a call with the first user's telephone;
Calling the second user's terminal as the caller number as the caller number, or receiving a call sent from the second user's phone to the link phone number;
The computer runs ,
The terminal of the first user executes the step of displaying the shared data when the call is established;
A call method in which the terminal of the second user executes the step of displaying the shared data when the call is established . Receiving the shared data from the terminal of the first user via the network, using the destination telephone number, the shared data and a destination address indicating the destination of the shared data as a call request ;
Issuing a linkage phone number corresponding to the call request ;
Transmitting the shared data to a second user's terminal based on the destination address of the call request ;
Establishing a call with the first user's telephone;
Calling the second user's terminal as the caller number as the caller number, or receiving a call sent from the second user's phone to the link phone number;
To the computer ,
Causing the terminal of the first user to execute the step of displaying the shared data when the call is established;
Call program order to execute the step of displaying the shared data when establishing said call to a terminal of the second user.

Images