WO2009079756A1

WO2009079756A1 - System and method for connecting telephony users

Info

Publication number: WO2009079756A1
Application number: PCT/CA2008/002191
Authority: WO
Inventors: Tommy DÉSILETS; John R. Feifer
Original assignee: Desilets Tommy; Feifer John R
Priority date: 2007-12-20
Filing date: 2008-12-08
Publication date: 2009-07-02

Abstract

A system and method are provided that enable users to communicate in a telephone communication without any of the parties having to dial a number on their own phone. In one embodiment, a central call server stores account information for each user and a user interface is provided to the caller. The caller can simply select the intended recipient of the call and the system seamlessly connects the caller and the recipient by calling each side and bridging the call. Information stored by the call server can also be used to provide custom appointments and reminders.

Description

SYSTEM AND METHOD FOR CONNECTING TELEPHONY USERS

[0001] This application claims priority from U.S. Application No. 61/015,314 filed December 20, 2007, the contents of which are incorporated herein by reference.

TECHNICAL FIELD

[0002] The following relates generally to telecommunication systems and has particular utility in connecting users in such telecommunication systems.

BACKGROUND

[0003] The telephone call is still regarded as an important tool in conversing with family, friends, doing business, and for leaving and saving messages. Telephone features are continually converging with Internet-based communication protocols to enable a user to converse verbally using either an Internet connection, a standard telephone connection, or both.

[0004] Despite being such an important form of communication, when initiating a telephone call, regardless of the communication medium, the caller must remember or look up the particular telephone number associated with the intended recipient, which requires that the caller either maintain their own contact details or rely on publicly available sources, which can be incomplete and may not be up to date when the recipient moves locations. In addition to knowing how to reach the recipient, a basic telephone service requires that the user remembers when and why a particular call is to be made.

[0005] It is therefore an object of the present invention to provide a system and method for connecting telephony users which addresses the above disadvantages.

SUMMARY

[0006] The following enables users to communicate in a telephone communication without any of the parties having to dial a number on their own phone. In one embodiment, a central call server stores account information for each user and a user interface is provided to the caller. The caller can simply select the intended recipient of the call and the system seamlessly connects the caller and the recipient by calling each side and bridging the call.

[0007] In one aspect, there is provided a method for connecting a first user and a second user for participating in a telephone communication, the method comprising receiving a

21835649 1 request from the first user to call the second user; calling the first user; and upon connecting to the first user, bridging the second user to the first user on the same gateway by calling the second user.

[0008] In another aspect, there is a computer readable storage medium comprising computer executable instructions for connecting a first user and a second user for participating in a telephone communication, the computer executable instructions comprising instructions for performing the method above.

[0009] In yet another aspect, there is provided a system for connecting a first user and a second user for participating in a telephone communication, the system comprising a call server comprising a connection to at least one communications network for connecting the first user and the second user, and a memory comprising a user database for storing information pertaining to users in the system including the first and second users, and the computer readable medium above.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] An embodiment of the invention will now be described by way of example only with reference to the appended drawings wherein:

[0011] Figure 1 is a schematic diagram of a seamless telephone connection system.

[0012] Figure 2A is a schematic diagram of one embodiment of an interface device for using the system of Figure 1.

[0013] Figure 2B is a schematic diagram of another embodiment of an interface device for using the system of Figure 1.

[0014] Figure 2C is a schematic diagram of yet another embodiment of an interface device for using the system of Figure 1.

[0015] Figure 3 A is a screenshot of one embodiment of a user interface to be displayed on the interface device of any one or all of Figures 2 A, 2B, and 2C.

[0016] Figure 3B is a screenshot of another embodiment of a user interface to be displayed on the interface device of any one or all of Figures 2A,2B, and 2C.

2183₅649 1 [0017] Figure 4 is a flow diagram illustrating a protocol for connecting one user of the system in Figure 1 with another user.

[0018] Figure 5 is a flow diagram illustrating a protocol for connecting two users of the system of Figure 1 according to an appointment.

DETAILED DESCRIPTION OF THE DRAWINGS

[0019] Referring now to Figure 1 , a seamless telephone connection system is denoted by numeral 10. The system 10 includes, in the example shown, a first user 12 (User 1) or "caller" and a second user 14 (User 2) or "callee", "called party" or "intended recipient", who establish a telephony connection through a call server 16. The first user 12 communicates with the call server 16 through a first interface device 18. The second user 14 may also communicate with or otherwise receive the call through a second interface device 20. However, it will be appreciated that the second user 14 may instead receive the call over a standard telephone or Internet connection (e.g. through a computer or telephone) by way of specific network 22 that provides the infrastructure 24 for supporting the call. As will be exemplified below, the interface device 18, 20 can be any software, hardware or combination of both that provides a user interface (UI) to enable a user to interact with and, participate in use of, the system 10.

[0020] The call server 16 includes a connection module 26 for handling the bridging of connections between the users 12, 14 and a user database 28 for storing user account information such as names, telephone numbers, appointment information, billing information and other contact details appropriate to the service being provided. The connection module 26 is responsible for communicating with the network 22 in order to bridge a call between the users 12, 14.

[0021] There can be many configurations for the call server 16. One such configuration involves the call server 16 using specialized hardware to reach User 1 and User 2 to establish a direct connection with the public switched telephony network (PSTN) enabling the call server 16 to call regular phone lines and then bridge the calls together. In another configuration, the call server 16 can use VoIP (on regular Internet network) to reach VoIP software being used by User 1 and User 2. In yet another configuration, the call server 16 can connect to a commercial VoIP-to-PSTN gateway in order to place calls to regular phone

21835649 1 lines. In this case, the VoIP calls are placed to the gateway to reach User 1 and the call server 16 bridges the two VoIP calls together. In yet another configuration, the call server 16 can use a different configuration for each call leg (User 1 or User 2). For example, a kiosk may use a direct VoIP connection to the caller server 16 and User 2 is reached by placing a VoIP call to the commercial VoIP-to-PSTN gateway to reach a regular phone line. It can therefore be seen that any suitable configuration for seamlessly connecting User 1 and User 2 can be used.

[0022] Figures 2 A, 2B, and 2C provide examples of various manifestations of the interface device 18, 20 that can be used to initiate, receive, and participate in the call. In the example shown in Figure 2 A, a kiosk is shown having a display screen 30a, an input/interface mechanism 32a such as a keyboard, interactive touch screen or panel of buttons and a telephone receiver 34a. The kiosk version is typically only for use by the called party unless assurance can be made that User 2 would also be at a kiosk at the same time. In the example shown in Figure 2B, the interface device 18, 20 is hosted by a personal computer (PC). The PC includes a display monitor 30b, a keyboard 32b, pointing device (mouse) 35, and an internet connection 36. In Figure 2B it can be seen that a user interface (UI) 38 is provided, along with a VoIP application 40 to enable the user to place and/or receive the call using the PC. Alternatively, a separate telephone 34b can be used to actually carry out the call as will be explained in greater detail below. In Figure 2C, a more compact version of the kiosk in Figure 2A is provided, which provides a touchscreen 33 which, as is well known in the art, provides both a monitor 30c and an input mechanism 32c (by way of "touching" the screen at an appropriate location) and has an attached cradle and handset 34c. A mounting bracket 31 on the rear of the unit can be provided to facilitate installation of the unit. The embodiment shown in Figure 2C is particularly suitable for mounting in public places such as airports, train stations, hotel lobbies, etc.

[0023] It will be appreciated that the examples shown in Figures 2A, 2B, and 2C are for illustrative purposes only and that any suitable interface device that can enable the user to interact with the call server 16 and then participate in a telephone call, e.g. by having a wired or wireless connection, speaker, microphone etc. Also, as can be seen, any combination of hardware and software can be used in various configurations to suit particular needs.

21835649 1 [0024] Figures 3 A and 3B provide two examples of the UI 38 shown in Figure 2B. In Figure 3A, a first UI 38' provides a list of users 42 with whom the caller may initiate a call. The list 42 includes a selection mechanism 48 such as radio buttons as well as a name or other identifier 44 and a corresponding telephone number 46. The user can scroll through the list 42, identify the intended recipient of the call, select the corresponding radio button 48 and then press a connect button 50. A cancel button 52 is also provided to enable a user to exit the connection, e.g. to log off the call server's system.

[0025] In Figure 3B, another UI 38" showing a list of users in another configuration is provided wherein each user is shown with an identifier 54 and, if permission is received from the user, a corresponding number 56. A separate CALL! button 58 can also be used. The user that wishes to initiate a call may browse the list and simply press the corresponding CALL! button 58 to begin the connection. The identifier 54 should be able to indicate to the user, to whom they would reach if the corresponding CALL! button 58 is selected and, if the number 56 is included, further identification can be made, e.g. where the same person has two different numbers. Alternatively, the number 56 or multiple numbers 56 can be hidden and the user given a choice of which number to access such as home vs. work vs. cell etc. It will be appreciated that the examples shown in Figures 3A and 3B are for illustrative purposes only and that any other UI 38 can be used. For example, web-based applications can include a plug-in or applet or an entirely separate web-page can be used to connect the call. Also, a password-protected user account can be provided to each user to control access the call server's system. The UI 38 should be a user-friendly application that enables the user to simply select a desired recipient without having to dial or remember a phone number. Any amount of information associated with the users can be displayed such as pictures or biographical information.

[0026] It may be noted that, as discussed above, the number 56 for a user in the system 10 may be kept private at the request of the user or by default. In this way, a company could keep a certain number private and make sure that all incoming calls made to this number are coming from the call back system 10 described herein. To facilitate recognition of a caller, a user profile (not shown), e.g. for User 1, could also be sent to User 2 before the call is answered akin to an advanced caller ID system.

2183S649 1 [0027] Turning now to Figure 4, an exemplary protocol is shown for enabling User 1 to call User 2, and the call be connected, with either party having to dial a number. At step 1 , User 1 selects or initiates a call by first accessing the UI 38 through any appropriate interface device 18. For example, User 1 can log in or pay at a kiosk which displays the appropriate list 42 of users. At step 2, the UI 38 and/or interface device 18 sends a request to the call server 16 which identifies both the caller (i.e. User 1 in this example) and the intended recipient (i.e. User 2 in this example). The call server 16 then receives the request at step 3 through the connection module 26 and the connection module 26 accesses the user database 28 to lookup the numbers for User 1 and User 2. Since either or both of User 1 and User 2 may have multiple numbers associated with their account (e.g. home, office and cell), the request should include a tag or identifier that indicates which number to lookup.

[0028] The connection module 26 then places a call to User 1 at the phone number indicated in the request and/or found in the database 28 at step 4. User 1 then answers the call at step 5. It will be appreciated that steps 3 and 4 do not require looking up User 1 's information if they are calling from a custom kiosk or pay-access site which provides a receiver 34a. In this way, User 1 can use their account and connect from any location, not necessarily a location associated with a number in their account. Typically, there would be no profile or account stored on the kiosk or other public interface device 18 itself, but users would be given access to a general system directory and can place calls as if they were using a public telephone. Preferably, when User 1 answers the call, a welcome message is played which prompts the user to continue. This may be done to avoid false calls such as those made to fax machines and those that simply encounter voicemail.

[0029] As shown in Figure 4, one way to do this is to have the connection module 26 send a welcome message at step 6, which may be sent once User 1 answers at step 5. User 1 then listens to the welcome message at step 7. The welcome message can simply be a prompt or may include something more sophisticated, depending on the nature of the interface devices 18, 20 being used, such as a short audio or video advertisement, before the call to User 2 is made. At step 8, the connection module 36 sends the prompt to User 1, either as a separate packet or with the welcome message. User 1 then presses the appropriate key at step 9, e.g. zero to ignore call or one to accept. The response to the prompt (i.e. the press of a

21835649.1 telephone button) when using a regular phone creates a dual tone multi frequency (DTMF) signal that is sent back to the call server 16 at step 10.

[0030] It may be noted that the prompt can be made the same whether or not the user is using VoIP or PSTN etc. This enables the user to be presented with the same "phone experience" without having to know that they are actually being bridged on a VoIP "middleman". VoIP protocols such as SIP, IAX and H323 can understand and generate DTMF tones. The tone is either transmitted directly in the RTP voice stream if the voice codec used allows it. If a low bitrate codec is used, any available standard to send the DTMF in the RTP stream (e.g. see RFC2833) can be used. This allows all call servers 16, regardless of configuration, to be DTMF compatible so that, e.g., a user could press "1" on a PC UI or a telephone and have the call connected in the manner described herein.

[0031] The connection module 26, upon receiving the response and assuming the response is positive (i.e. connect the call), begins to bridge User 1 and User 2 at step 12 by calling User 2 at the appropriate number at step 13. This is done by placing the call on the same gateway so that User 1 is able to hear the ring back tone of the second call (sent at step 13). This is shown at step 14. User 1 is then responsible for hanging up the call if it fails or if they realize that a wrong number has been called. Assuming User 2 is at the number being called, User 2 answers the call at step 15 and User 1 may begin their conversation. Step 16 shows that the connection module 26 and/or network 22 maintains the connection between User 1 and User 2 as would a normal telephone call and step 17 indicates when the call ends. In this example, because both voice and DTMF are supported, the call is bridged seamlessly.

[0032] The call server 16 can also be configured to support other features such as automatic calling for appointments, conference calls, reminders, etc. The connection module 26 in such configuration would be programmed to recognize dates and times that are associated with events such as appointments customized by a user. On the specific date at the specific time, the connection module 26 would lookup the number associated with the user and perform the action associated with the event. In one example, the call server 16 is used to automatically connect User 1 and User 2 in a conference call without requiring either party to initiate, let alone dial into the call. Figure 5 shows an exemplary protocol for make such a connection.

21835649 1 [0033] At step 1 , the connection module 26 detects an appointment. This can be done by running a background program such as a calendar program or by receiving triggers from another entity (e.g. from a mobile device or PC for the user). At step 2, the connection module 26 then determines that the event associated with the appointment is to connect a call between User 1 and User 2 and then looks us the number for each of them. At step 3, User 1 is called and answers at step 4. In this example, the connection module 26 also sends a prerecorded, custom or standard reminder at step 5 to remind User 1 of the appointment and to ensure they accept the call. At step 6, User 1 listens to the reminder the end of which includes a prompt sent in step 7, similar to that in Figure 4. User 1 then presses the appropriate key (e.g. accept or ignore) at step 8, which initiates a response that is sent to the connection module at step 9. The connection module then detects and interprets the response, e.g. according to the DTMF signal carried thereto at step 10. If User 1 accepts the appointment, then at step 11, the connection module bridges User 2 by calling the number for User 2 indicated either in the appointment or as determined from their account at step 12. Again, the call is bridged on the same gateway and therefore at step 13, User 1 can listen to the connection as if they dialled the number. Assuming User 2 answers the call at step 14, the connection is maintained at step 15 until the call ends at step 16.

[0034] It will be appreciated that the reminder and prompt used in steps 5 and 7 respectively can also be sent to User 2 in order to ensure that the call or conference is accepted by both parties. This may be a feature that can be switched on or off when the appointment is created.

[0035] The protocol shown in Figure 5 can also be used to send only reminders to either or both User 1 and User 2. For example, two hours prior to initiating a conference call, steps 1-5 can be executed to reminder each party of the upcoming conference call. In this way, a portion of the protocol is executed at a "reminder" event and the entire protocol is executed at the "appointment" event. It will be appreciated that the same considerations regarding the privacy of user information can be incorporated into this and other embodiments.

[0036] It can therefore be seen that the call server 16 enables parties to initiate a telephone connection both through user interaction at an interface device 18 and automatically based on events stored by the call server 16. Not only can the system 10 be used to seamlessly connect telephony users but also to take advantage of the user information

21835649.1 stored in the user database 28 to provide custom reminders or to provide other telephone based messages.

[0037] Although the invention has been described with reference to certain specific embodiments, various modifications thereof will be apparent to those skilled in the art without departing from the spirit and scope of the invention as outlined in the claims appended hereto.

21835649.1

Claims

Claims:

1. A method for connecting a first user and a second user for participating in a telephone communication, the method comprising: receiving a request from said first user to call said second user; calling said first user; and upon connecting to said first user, bridging said second user to said first user on the same gateway by calling said second user.

2. The method according to claim 1 wherein calling said first user comprises looking up a number for said first user in a user database, sending a message to said first user upon said first user answering and sending a prompt to said first user to initiate the connection.

3. The method according to claim 1 wherein said request received from said first user to obtained through an interface device.

4. The method according to claim 3 wherein said interface device comprises a display, one or more input mechanisms for interacting with said interface device, and a handset for making said call.

5. The method according to claim 4 wherein said display and said input mechanisms are provided by a touchscreen.

6. The method according to claim 4 wherein said interface device is a remote terminal.

7. The method according to claim 3 wherein said interface device is provided via software running on a personal computer (PC).

8. The method according to claim 2 wherein said message comprises advertising content.

9. The method according to claim 2 wherein said message comprises a reminder.

10. The method according to claim 9 wherein said reminder pertains to an appointment and is sent either in advance of said appointment or at the time of said appointment.

21835649 1

11. The method according to claim 10 wherein said appointment is a conference call with at least said second user.

12. The method according to claim 11 wherein said request from said first user is made in advance and stored in a database to enable said conference call to be initiated by a third party rather than said first and second users.

13. The method according to claim 3 wherein said user interface enables said first user to initiate said call with said second user without entering a telephone number.

14. A computer readable storage medium comprising computer executable instructions for connecting a first user and a second user for participating in a telephone communication, said computer executable instructions comprising instructions for performing the method according to any one of claims 1 to 13.

15. A system for connecting a first user and a second user for participating in a telephone communication, the system comprising a call server comprising a connection to at least one communications network for connecting said first user and said second user, and a memory comprising a user database for storing information pertaining to users in said system including said first and second users, and the computer readable medium according to claim 14.

21835649.1