GB2378347A

GB2378347A - Handling incoming calls whilst connected to the internet

Info

Publication number: GB2378347A
Application number: GB0118362A
Authority: GB
Inventors: S Swaminathan; Rajendra L Mahajan; Ramprashad Panigrahi; Sushrut J Mair; Pradeep Nair; Himmat Kaklothar; Sandeep Nag; Vaibhav Sathe
Original assignee: GLOBAL TELE SYSTEMS Ltd
Current assignee: GLOBAL TELE SYSTEMS Ltd
Priority date: 2001-07-27
Filing date: 2001-07-27
Publication date: 2003-02-05
Also published as: GB0118362D0

Abstract

A communications system 1 and method for handling a telephone call to a telephone number is described. The communications system 1 receives a telephone call at a node 3 thereof when the call is diverted the node 3 because the telephone line associated with the called telephone number is busy. The system 1 includes a server 9, which receives information about the call from the node 3, and determines whether the called telephone number is one of a plurality of subscriber telephone numbers stored in a database 11. If the called telephone number is a subscriber telephone number, the server 9 sends a notification to a client, using the client identifier associated with the called telephone number stored in a database 11, to indicate the presence of the telephone call. The notification may present the client device with options, eg ignore call, answer call or redirect call to another number or a voicemail system. The notification option is sent back to the server which then takes appropriate action. May be used to notify a user of an incoming call whilst that user is connected to the Internet.

Description

IMPROVED TELEPHONE CALL HANDLING The present invention relates to communications systems and more particularly to a system and method for providing a consumer telecommunications service for handling incoming telephone calls when the consumer's telephone line is busy (engaged).

It is common for domestic telephone subscribers to use a single PSTN telephone line for both voice and data telecommunications (by telephone and/or facsimile apparatus) and for access to the Internet (using a personal computer equipped with a modem).

When a subscriber is using the telephone line for Internet access, it is not possible to receive incoming telephone calls.

Some telephone service providers have developed services to notify a subscriber of the presence of an incoming call when the line is busy with another telephone call.

An example of such a service is"Call Waiting"provided by British Telecommunications pic. However, such services require the use of telephone equipment to receive the signal over the PSTN indicating the presence of an incoming telephone call; the notification is not recognised by a personal computer receiving the signal on a modem.

The present invention seeks to address this problem.

Generally speaking, the present invention provides a method and apparatus for notifying a user, who is utilising a telephone line by means of a processing device equipped with a modem, of the presence of an incoming telephone call to the telephone line, by sending a notification to the processing device over the Internet.

In accordance with a first aspect, the present invention provides a method of handling a telephone call to a telephone number in a communications system when the

telephone call is diverted to a node of the communications system because the telephone line associated with the telephone number is busy, the method comprising the steps of. determining the called telephone number to which the call is directed; determining if a client identifier associated with the called telephone number is stored in memory, and if a client identifier is found, sending a notification to the client having the client identifier, the notification indicating the presence of the telephone call.

In a preferred embodiment, the client identifier is a subscriber ID, and the notification is sent over a connection denoted by the subscriber ID Preferably, the connection between the client and the server is established by a client application running on a subscriber PC or other processing device when the subscriber PC utilises the telephone line for access to the Internet.

In accordance with a second aspect, the present invention provides a computer readable medium including a computer program for carrying out the method in accordance with the first aspect of the present invention.

In accordance with a third aspect, the present invention provides a communications system for handling a telephone call to a called telephone number, the system comprising: a node for receiving the telephone call from the Public Switched Telephone Network, the call being diverted to the node when the telephone line associated with the called telephone number is busy, the node including a processor for determining the called telephone number to which the call is directed; and a server for receiving a communication from the node about the telephone call and for sending a notification to a client having a client identifier associated with the called telephone number, the notification indicating the presence of the telephone call.

Further optional and preferred features of the present invention will be apparent from the following description and accompanying claims Embodiments of the present invention will now be described, by way of example, with reference to the accompanying drawings, in which

Figure 1 is a block diagram of a communications system implementing a method of call handling in accordance with a preferred embodiment of the present invention; Figure 2 is a flow diagram illustrating the steps performed by a computer program forming a part of a web server application in accordance with a preferred embodiment of the present invention; Figure 3 is a flow diagram illustrating the steps performed by a computer program forming another part of a web server application in accordance with a preferred embodiment of the present invention ; Figures 4A and 4B are flow diagrams illustrating the steps performed by a computer program forming yet another part of a web server application in accordance with a preferred embodiment of the present invention; Figure 5 is a flow diagram illustrating the steps performed by a computer program forming still another part of a web server application in accordance with a preferred embodiment of the present invention; Figure 6 is a flow diagram illustrating the steps performed by a computer program forming yet another part of a web server application in accordance with a preferred embodiment of the present invention; Figure 7 is a flow diagram illustrating the steps performed by a computer program forming a part of an application server application in accordance with a preferred embodiment of the present invention; Figure 8 is a flow diagram illustrating the steps performed by a computer program forming another part of an application server application in accordance with a preferred embodiment of the present invention;

Figure 9 is a flow diagram illustrating the steps performed by a computer program forming yet another part of an application server application in accordance with a preferred embodiment of the present invention ; Figure 10 is a flow diagram illustrating the steps performed by a computer program forming a part of a client application in accordance with a preferred embodiment of the present invention; Figure 11 is a flow diagram illustrating the steps performed by a computer program forming another part of a client application in accordance with a preferred embodiment of the present invention; Figure 12 is a flow diagram illustrating the steps performed by a computer program forming another part of a client application in accordance with a preferred embodiment of the present invention, and Figure 13 is a flow diagram illustrating the steps performed by a computer program forming yet another part of a client application in accordance with a preferred embodiment of the present invention.

Figure 1 shows the components of a communications system in accordance with a preferred embodiment of the present invention The system 1 comprises an intelligent node 3 and a web server 9, which, in accordance with the preferred embodiment, are located on the same Intranet. In other embodiments, the web server 9 and the intelligent node may not be on the same Intranet, but instead communicate across the Internet.

The intelligent node 3 includes an intelligent telecommunications switch 5 connected to the Public Switched Telephone Network (PSTN), and an application server 7. The web server 9 and the application server 7 communicate across the Intranet, and the web server 9 is accessible to subscribers across the Internet. The web server 9 has an associated database 11, which stores information relating to subscribers to the service.

Each subscriber typically utilises a single telephone line 15, as illustrated in Figure 1. The subscriber may utilise the subscriber telephone 19 to make telephone calls over the PSTN, or may use a subscriber PC 17 equipped with a modem to access the Internet through an Internet Service Provider (ISP) 20 The individual components of the system 1 and their functions will now be described in more detail.

Intelligent Node The intelligent node 3 may be of any suitable configuration. For example, in one possible arrangement, the intelligent telecommunications switch 5 comprises a Meridian EPABX (Option lie) available from Nortel. It will be appreciated that any other suitable programmable EPABX may be employed. The EPABX is coupled to the PSTN by El lines. The application server 7 comprises a standard PC with a dialogic card, and is similarly coupled to the EPABX by conventional analogi E 1 lines.

In an alternative arrangement, the intelligent telecommunications switch 5 comprises an IPS720 available from TelSpec pic. It will be appreciated that any other suitable programmable switch may be employed. The IPS720 is connected the PSTN by E1 lines. The IPS720 includes Interactive Voice Response (IVR) System, which is programmed to handle all incoming telephone calls, and is in turn connected to the application server 7, which is a standard PC The intelligent node 3 is responsible for handling telephone calls received over the PSTN when the subscriber's telephone line 15 is busy A subscriber to the service is provided by the PSTN with a Call Forward on Busy (CFB) facility, which transfers telephone calls to a predefined telephone number when the telephone line 15 is busy (engaged). In accordance with the present invention, the CFB facility diverts such calls to the telephone number of the intelligent telecommunications switch 5 when the subscriber's telephone line 15 is busy

When a telephone call is diverted to the switch 5, information relating to the call is passed to the application server 7 which authenticates the call in association with the web server 9 and database 11, as described below.

In addition to the above, in accordance with the preferred embodiment, the application server 7 provides a voice mail service, which allows callers to leave voice mail messages for the subscriber, and the subscriber to retrieve such voice mail messages over the PSTN.

Web Server The web server 9 comprises a standard PC. In accordance with the preferred embodiment of the present invention, the web server provides the following key functions Firstly, the web server 9 permits customers to subscribe to the service over the Internet. In so doing, the customer downloads client application software that is used to interact with the web server 9 when the subscriber is using the telephone line 15 to access the Internet. When subscribing to the service, a prospective subscriber will provide subscriber information, as detailed below, which the web server 9 will store in the database 11.

Secondly, the web server 9 functions to interact with the application server 7 during call handling, primarily to authenticate and control calls, as described below.

Thirdly, the web server 9 functions to notify the subscriber, by means of the client application on the subscriber PC 17, of the presence of a valid incoming telephone call when the subscriber is using the telephone line 15 to access the Internet, as described below.

If a call, notified to the web server 9 by the intelligent node 3 is determined by the web server 9 to be valid, then the web server 9 preferably determines if the subscriber PC 17 is utilising the subscriber line 15 for browsing the web, and if so

communicates with the client application on the subscriber PC 17 in order to notify the subscriber that a telephone call is waiting. In accordance with the preferred embodiment of the present invention, the subscriber is provided with various options and can communicate with the web server 9 via the client application to choose the desired way of handling the call.

Call Handling An overview of the method of call handling in accordance with the present invention will now be described. As will be appreciated from the more detailed description that follows, in a preferred embodiment the method is implemented entirely in software, and in particular as part of a software application running on the intelligent node 3, a web server application running on the web server 9 and a client application 21 running on the subscriber PC 17.

When a telephone call is made to the subscriber's telephone number, and the line 15 is engaged, the call is forwarded to the intelligent node 3, by means of the CFB facility. The intelligent node 3 accepts the telephone call and preferably plays a message to the caller to hold. The intelligent node 3 determines information relating to the call, in particular, the called number, that is the telephone number of the subscriber, and the calling number, and sends them to the web server 9 for authentication. The database 11, associated with the web server 9, stores details of current subscribers' telephone numbers, against which the called number is checked. In addition, the subscriber may register the telephone numbers of callers, the calls from whom he wishes to receive notification while browsing the Internet. These numbers are stored in the subscriber's profile in the database 11. Thus, the web server 9 may also check the calling number against the subscriber's profile. In addition, in accordance with the preferred embodiment, the web server 9 determines whether it has received communication from the subscriber's client application to indicate that the subscriber PC 17 is utilising the telephone line 15 to access the Internet. In the preferred embodiment, as described below, the subscriber's client application communicates with the web server 9 by way of a session connection, when the subscriber PC 17 starts browsing the Internet.

If the web server 9 determines that the subscriber PC 17 is accessing the Internet, then the web server 9 communicates with the client application to notify the subscriber that a call is waiting. On the other hand, if the web server 9 determines that the subscriber PC 17 is not utilising the telephone subscriber telephone line 15, then either the subscriber telephone 19 is utilising the line 15 on a normal voice call, or the subscriber PC is utilising the line 15 but the client application is not activated. In either case, the web server 9 informs the intelligent node 3, which in turn informs the telephone caller that the line is busy. Optionally, the caller may be invited to leave a message on the voice mailbox of the subscriber, where this facility is provided.

Assuming that the subscriber is using the subscriber PC 17, and receives notification from the web server 9 that the call is waiting, the subscriber may then select one of several possible options. Whichever option is chosen, the client application communicates with the web server 9, which in turn notifies the intelligent node 3. The intelligent node 3 then processes the telephone call accordingly. In accordance with the preferred embodiment, the options include (i) to accept the call, (ii) to reject the call, (iii) to forward the call to another telephone number, and (iv) to redirect the call to the subscriber's voice mailbox.

If the subscriber opts to reject the call, the web server 9 notifies the intelligent node 3 which plays a voice message to the caller that the line is busy. If the option chose is to accept the call, the client application will notify the web server 9, which in turn will notify the intelligent node 3. The client application will disconnect the modem of the subscriber PC 17 from the telephone line 15, so that the call can be accepted on the subscriber telephone 19 The intelligent node 3 will divert the call back to the subscriber's telephone number over the PSTN.

If the subscriber elects to forward the incoming call to another telephone number, the web server 9 will notify the intelligent node 3, which will forward the call to the alternative telephone number via the PSTN In the preferred embodiment, the alternative telephone number is entered by the subscriber as part of the selection process, as described below. If the option chosen is to divert the call to voice mail, the

web server 9 will notify the intelligent node 3, which will invite the caller to leave a voice mail message for the subscriber.

As explained previously, in accordance with the preferred embodiment, the above described method of call handling is implemented in software in the form of application server software running on application server 7; web server software running on web server 9, and client application software running on subscriber PC 17.

Details of the principle aspects of these three software applications will now be described with reference to Figures 2 to 13 WEB SERVER SOFTWARE Figures 2 to 6 illustrate program steps performed by various aspects of the web server software application in accordance with a preferred embodiment of the present invention.

Subscriber Registration Figure 2 illustrates the program steps performed by the web server software application when a telephone subscriber registers for the call handling service. A subscriber will access the web site on the web server 9 using subscriber PC 17 in the conventional manner.

The program starts when a prospective subscriber logs on to the registration area of the web site at step 101. When this occurs, the program determines whether the user is a new user. This is achieved by looking for a subscriber ID in the database 11 If step 103 determines that the user is a new user, then the program continues by sending a registration form to the user, requesting subscriber details, as described below.

Alternatively, if step 103 determines that the user is an existing user, the user is allowed to modify his details at steps 104 and 105.

Returning to step 106, the registration form is sent by the web server 9 to the subscriber PC 17 where the registration form is displayed on the display screen thereof At step 107, the user enters his name, address, telephone details, including telephone

number, and any preferences, such as the telephone numbers of callers, the calls from whom he wishes to receive notification at his subscriber PC 17 Once the form is fully completed, at step 108, the user submits the details to the web server 9.

At step 109, the program receives the completed registration form from the user, either from step 108 or step 105, and checks whether the details contained in the form are valid. For instance, the program checks that the telephone number is a valid telephone number, and that the address is complete.

At step 110, if it is determined that the details received from the user are not valid, the program prompts the user to enter valid data and returns to step 107. If step 110 determines that the data is valid, at step 112, the program saves the registration details as a user profile in the database 11 together with a subscriber ID. The subscriber ID is an 8-digit number which is stored against the subscriber's telephone number in the database 11. A PIN is also associated with the subscriber ID in the database 11 for security purposes Once a new subscriber has registered with the service, the service will be activated, either manually or automatically, on payment of a subscription charge. Once the service is active, the web site permits the subscriber to download the client application software 21 for installation on his subscriber PC 17, as described below, and provides the subscriber with the subscriber ID and PIN, and the voicemail access service telephone number for use when accessing the Web Server, and/or voicemail box.

Client Application Authentication Figure 3 illustrates the program steps performed by the web server application to authenticate a client application when it connects to the web server In accordance with the preferred embodiment of the present invention, the client application 21 automatically connects to the web server 9 when the user is utilising the telephone line 15, in order to activate the call handling service In other embodiments,

the connection may be made through user activation of the client application. The computer program illustrated in Figure 3 is provided to update the database 11 to indicate that the subscriber is utilising the telephone line 15 for access to the Internet, in order to ensure proper call handling.

At step 301, the program receives a login packet from the client application of the subscriber PC 17. The login packet is sent in a predetermined format and contains the subscriber ID. At step 302, the program determines whether the login packet is valid, e. g. that it is complete and in the correct format. If step 302 determines that the login packet is not valid, the program sends a request to the client application to resend the login packet at step 304, unless as step 303 the program determines that there have been more than a predetermined number of attempts to send the login packet (in the embodiment, the predetermined number is 5). If step 303 does determine that there have been more than 5 tries, the link is disconnected at step 305.

If step 302 determines that the login packet is valid, at step 307 the program compares the Subscriber ill against the identifier's of current subscribers stored in the database 11, and at step 307 determines whether the client is an authenticate subscriber.

The program determines that the client is authenticate if the client identifier is included in the current set of subscribers in the database 11. If it is determined that the subscriber is not authenticate (i. e. a licensed client) the program continues with steps 303 and 304. If it is determined that the subscriber is authenticate the program continues with step 308 by updating the database 11. In particular, the program will set a status flag associated with the subscriber's profile to indicate that the subscriber PC is browsing the Internet.

Incoming Call Notification Figure 4A illustrates the program steps performed by the web server application, in order to authenticate incoming calls notified to it from the intelligent node 3

The program starts when the web server 9 receives notification of an incoming call from the application server 7, as described below. The notification includes data containing information about the call including the identity of the called subscriber (Dialled Digits Identity-"DDI") and the caller responsible for the incoming call (Caller ID-Caller Line Identity"CLI"). At step 401, the program determines if the data received from the application server is valid i. e. complete. If not, the program will send a request to the application server to resend the data, unless at step 402 it is determined that the application server has tried to send the data more than a predetermined number of times (in the illustrated embodiment five times) in which case the program stops.

If the data received from the application server 7 is valid, the program continues, by determining, at step 404, whether the DDI is valid, i. e. the called subscriber is a current subscriber, by comparing the DDI with the list of DDIs of current subscribers stored in the database. If the DDI is not valid, the program informs the intelligent node 3 at step 407 that the DDI is invalid. Alternatively, if step 404 determines that the DDI is valid, the program continues at step 405 by considering whether the subscriber is activated or deactivated in the database. If step 404 determines that the subscriber is deactivated, the program informs the intelligent node 3 at step 406 and stops. If step 404 determines that the subscriber is activated the program continues with step 408.

At step 408 the program determines whether the subscriber PC is browsing the Internet. In particular, step 408 considers the state of the status flag, associated with the called telephone number/DDI, in database 11. If the status flag is set, as in step 308 of the program of Figure 3, it is determined that the subscriber is browsing the Internet, and the program continues with step 410. Otherwise, the program continues with step 408A of Figure 4B, described below.

At step 410 the program determines whether the caller is authenticated or not, i. e. the telephone number/DDI of the calling party in the profiled group of the subscriber stores in the database 11. More particularly, the program compares the telephone number of the caller against the list of telephone numbers; calls from which the subscriber wishes to receive notification. If it is determined that the calling party is not

in the profiled list then the program continues with step 411 where it informs the intelligent node 3 that the calling party is not in the profiled list. If there is a match, that is, it is determined that the caller is in the subscriber's profile, or there are no numbers in the subscriber's profile, indicating that the subscriber wishes to receive notification of calls from all callers, the program continues at step 412 by sending an incoming call notification to the client application. After steps 411 and 412 both the program waits for more incoming messages The program of Figure 4B starts with step 408A by determining whether the caller is authenticated or not i. e. the caller is included in the subscriber's profile in database 11. If the caller is authenticated then the program goes to step 408B where it informs the intelligent node 3 that the subscriber is on another voice call. Alternatively, if the subscriber is not authenticated then the program proceeds to step 408C by informing the intelligent node that the calling party is not in the profiled list. After both 408B and 408C the web server again waits for more incoming messages.

Call Handling Options from Client Figure 5 illustrates the program steps performed by the web server application when processing responses, from the subscriber's client application, to notifications of incoming calls sent at step 412 of the program of Figure 4A.

At step 501, the program determines the option selected by the subscriber from the option data in the packet received from the client application.

At step 502, the program determines whether the data is complete. If the data is incomplete, the program causes the web server 9 to send a request to the client application to resend the option data at step 504, unless at step 503 it has been determined that the client application has attempted to send the data more than a predetermined number of times (in the embodiment five times).

If at step 502 it is determined that the data is complete, the web server 9 sends the selected option information to the application server 7 The intelligent node 3 then handles the call, according to the selected option, as described below.

Voice Mail Figure 6 illustrates the program steps performed by the web server application where a voice mail facility is provided. In accordance with a preferred embodiment, the voice mail message are received and stored by the application server 7 in the intelligent node 3. Although not essential, in accordance with the preferred embodiment the web server 9 is utilised to check that a caller attempting to retrieve the voice mail is authenticate, i. e. a current subscriber. The caller will dial the voicemail access service telephone number and be invited to dial his or her subscriber ID and PIN for authentification.

Thus, at step 601, the program receives a data packet from the intelligent node 3 requesting it to determine whether a caller attempting to access voice mail messages is authenticate. The request includes the caller's subscriber ID and PIN. At step 602, the program determines whether the request is valid i. e. it is complete and contains the caller's details. If step 602 determines that the data packet is incomplete, at step 604 the program sends a request to the intelligent node 3 to resend the request, unless at step 603 it is determined that the intelligent node has tried to send the request more than a predetermined number of times (in the illustrated embodiment five times) in which case the program stops.

If step 602 determines that the data packet is valid, at step 605 the program determines whether the caller is a valid subscriber by comparing the caller's subscriber ID (as above) against the list of subscriber IDs of current subscriber's stored in database 11. If there is a match, step 605 determines that the caller is a valid subscriber and at step 606 sends a data packet to the intelligent node 3 indicating that the caller is a valid subscriber and including subscriber information which may be used in retrieving the voice mail. Similarly, if step 605 determines that the caller is not a valid subscriber, at step 607 the program sends a data packet to the intelligent node 3 indicating this.

APPLICATION SERVER SOFTWARE Figures 7 to 9 illustrate the program steps performed by the computer program for handling incoming telephone calls to the intelligent node 3, which is run on the application server 7.

Initialisation and Call Receiving Referring to Figure 7, following initialisation of the intelligent node 3 at step 701, the program starts at step 702 by waiting for an incoming call to the intelligent switch 5. If an incoming call is received at step 702, the program continues with step 703. Otherwise, the program continues to wait for an incoming call at step 702.

At step 703, the program considers whether the incoming call is a voicemail access call (i. e. the DDI is the voicemail access service telephone number) or an incoming call from a subscriber.

If step 703 determines that the incoming call is a voicemail access call, the program continues with step 805 of Figure 8B. Otherwise, the program continues with step 801 of Figure 8A At step 801, the program plays a welcome message to the caller and captures the CLI and the DDI for the call. At step 802 the program determines whether the CLI (i. e. the number of the calling party) is in the profiled list for the DDI. If step 802 determines that the CLI is in the profiled list, then at step 803 the program plays to the caller a hold message The program then continues with step 901 of Figure 9, by handling the incoming call If step 802 determines that the CLI is not in the profiled list for the DDI, then the caller is not one for which the subscriber wishes to receive notifications of incoming

calls. Accordingly, the program continues with step 804 by playing an appropriate message to the caller The program then ends At step 805, the program plays the caller a welcome message and captures the subscriber ID and PIN which are entered by the caller. At step 806 the program plays a hold message whilst checking the subscriber ID and PIN for authentification in the database 11 If step 806 determines that the caller is authenticate, then the program continues with steps 808,809, 810 and 811 by playing the voice mail messages in conventional manner If step 806 determines that the caller is not authenticate, the program plays an appropriate message at step 807 Call Handling by Intelligent Node At step 901, the program sends to the web server 9 a data packet containing the identity of the called number (i. e. the subscriber's number) (DDI) and the calling party's number (CLI), and waits for a reply At step 902, the program periodically considers whether a reply has been received from the web server 9. If no reply has been received, the program continues to wait at step 902, unless at step 903, the program determines that a predetermined count has elapsed, during which no reply has been received. If step 903 determines that the count is above a predetermined number, then at step 904, the program notifies the caller, e. g. by playing a voice message, and terminates the call If step 902 determines that a reply has been received from the web server, then at step 905, the program considers whether the data received from the web server indicates that the DDI is valid or not. If the DDI is valid then the program continues with step 906 Otherwise, the program plays a sales prompt for the caller and hangs up the call at step 906B At step 906 the program determines if the DDI is activated for service usage or not If the data indicates that the DDI is inactivated then the program plays a suitable message to the caller and hangs up. Otherwise, the program continues with step 906A by checking to see if the calling party is profiled or not. If the calling party is not profiled then the program continues to step 906 else it continues to step 907

where it checks to see if the called party is on another voice call. If step 907 determines that the called party is on another voice call, then the program plays an appropriate message to the caller. In accordance with the preferred embodiment, in which a voice

'I f it m mail facility is provided, at step 908 the program prompts the caller to leave a voice mail message, and at step 909 records the message in the subscriber's voice mailbox.

The program then ends If step 907 determines that the called party is not on another voice call, that is, the subscriber is accessing the Internet, at step 910 the program determines which option the subscriber has selected from the data received from the web server. At step 911, the program plays an appropriate message to the caller according to the selected option. Thus, if the subscriber selection option (i), to reject the message, the program plays a message or provides a tone indicating that the subscriber's line is engaged and hangs up. If the subscriber has selected option (ii), to accept the call, the program plays a message requesting the caller to hold whilst the call is redirected to the DDI via the PSTN. If the subscriber has selected option (iii), to transfer the call to another telephone line, then the program plays to the caller a message to hold the line, whilst the call is redirected via the PSTN to the appropriate telephone line. If the subscriber has selected option (iv), to divert the call to voice mail, the program plays the message to leave a voice mail according to step 908.

The program ends after playing the message at step 909 and hanging up the call.

CLIENT APPLICATION The client application is illustrated by Figures 10 to 13. The client application is automatically activated, in accordance with the preferred embodiment, when a user switches on the subscriber PC 17, and continuously monitors the status of the modem.

When the modem connects to an Internet Service Provider, the client application automatically establishes a connection to the web server 9 In accordance with the preferred embodiment, the subscriber is requested to supply his identification and password at this stage. The client application then waits for communications from the web server 9, i. e. notifications of incoming calls.

Automatic Activation of Client Application Figure 10 illustrates the program steps performed by the client application when the subscriber PC 17 is turned on. At step 1001 the client application is initiated and at step 1002 the program checks to see whether the modem is connected. If step 1002 determines that the modem is not connected, the program waits at step 1002. If step 1002 determines that the modem is connected, then the program activates the service at step 1003.

At step 1004, the program attempts to retrieve the IP address of the web server 9 from memory of the subscriber PC 17, and if the IP address is found at step 1005, the program connects to the web server 9 at step 1007. If the IP address of the web server is not found at step 1005, the program prompts the user to reinstall software to enable the client application to connect to the web server 9 at step 1006.

Connection to Web Server Following step 1007, the program determines at step 1101, illustrated in Figure 11, if the web server has been found. If the web server 9 has not been found, the program attempts to reconnect at step 1103. If the program successfully connects to the web server, at step 1101 or step 1104, the program continues with step 1102.

At step 1102, the program determines whether the subscriber needs to login and enter his password for authentication by the web server 9 In particular, the web server will send a prompt to the subscriber to enter a subscriber ID and PIN, unless the subscriber has selected the remember mode option so that the web server remembers the subscriber ID and PIN, which obviates the need for the subscriber to enter these details on each occasion. Once the login details and password have been verified as valid, at step 1105, the program successfully logs on to the web server and continues with the program steps of Figure 12.

Handling Messages from Web Server At step 1201, the program periodically checks whether the client application has received a message from the web server 9. Messages may be sent by the web server to the client application by step 412 of the program of Figure 4A. If step 1201 determines that the client application has not received a message from the web server 9, then the program waits at step 1201. If step 1201 determines that the client application has received a message from the web server, then the program continues with step 1202 At step 1202, the client application displays on the subscriber PC 17 a pop-up window showing that an incoming call is waiting and preferably displaying the caller details of the incoming call, and invites the subscriber to select one of four possible options. At step 1203 the client application receives a selection from the subscriber.

The selection may be made using the user interfaces of the subscriber PC, for example a keyboard or a mouse.

Step 1204 determines which of the four possible options (i) to (iv) have been. chosen by the subscriber.

If the subscriber has chosen option (i), to accept the call, the program continues with step 1205 by sending notification of this option to the web server 9. If option (ii), to reject the call, has been selected, then at step 1206 the program sends an appropriate notification to the web server. If option (iii), to transfer the call, has been selected, the client application prompts the subscriber to enter the telephone number to which the call should be redirected, and once this information has been received and validated, the program sends notification to the web server indicating that the call should be transferred to the entered number at step 1210 of Figure 12B. If option (iv), to direct the call to voice mail, has been selected by the subscriber, then step 1209 sends appropriate notification to the web server 9.

Deactivation of Client Application Figure 13 illustrates the program steps performed by the client application when the subscriber PC 17 disconnects from the modem. At step 1301, the client application

gives notification to the subscriber that disconnection from the modem has taken place.

At step 1302, the program continues to check whether there is a modem connection. If the modem reconnects, i. e. step 1302 determines that modem is connected, the client application continues with step 1004 of the program of Figure 10. If step 1302 does not find a modem connection, the program continues checking for a modem connection at step 1302.

As the skilled person will appreciate, various modifications and changes may be made to the described embodiments. For example, whilst the client application of the preferred embodiment establishes a secure connection to the web server when the subscriber PC begins browsing the Internet, so that the web server uses socket numbers to identify clients, other forms of client identifier (e. g. IP addresses, e-mail addresses) can be used for communication between the client application and the web server.

It is intended to include all such variations, modifications and equivalents which fall within the scope of the present invention as defined in the accompanying claims.

Claims

CLAIMS 1. A method of handling a telephone call to a telephone number in a communications system when the telephone call is diverted to a node of the communications system because the telephone line associated with the telephone number is busy, the method comprising the steps of : determining the called telephone number to which the call is directed ; determining if a client identifier associated with the called telephone number is stored in memory, and if a client identifier is found, sending a notification to a client having the client identifier, the notification indicating the presence of the telephone call.
2. A method as claimed in claim 1, wherein, prior to the step of sending a notification, the method further comprises: determining the calling telephone number from which the call originates; comparing the calling telephone number against a plurality of notifiable calling telephone numbers associated with the called telephone number, and sending the notification depending upon whether the calling telephone number is included in the plurality of notifiable calling telephone numbers associated with the called telephone number.
3. A method as claimed in claim 1 or claim 2, wherein, prior to the step of sending a notification, the method further comprises: determining whether the telephone line associated with the called telephone number is in use for access to the Internet.
4 - A method as claimed in claim 3, wherein the step of determining whether the telephone line associated with the called telephone number is in use for access to the Internet, comprises determining whether a status flag, associated with the called telephone number in memory, is set

<Desc/Clms Page number 22>
5 A method as claimed in claim 4, wherein, the status flag is changed when a notification is received from a processing device having a client identifier associated with the called telephone number.
6 A method as claimed in any one of claims 1 to 5, wherein the step of determining if a client identifier associated with the called telephone number is stored in memory comprises : sending from the node a request to a server device having associated memory, the request including the called telephone number and a command to find a client identifier associated with the called telephone number in memory, and wherein if the server device finds a client identifier, sending the notification from the server device to the client.
7 A method as claimed in claim 6, wherein the client identifier is a subscriber ID associated with the called telephone number, and the step of sending the notification comprises sending a notification to a connection denoted by the subscriber ID.
8. A method as claimed in claim 6 or claim 7, wherein the notification includes at least one option for the handling of the telephone call, the method further comprising: receiving, at the server device, a response to the notification from a processing device having the client identifier, the response including a selected option, and forwarding details of the selected option to the node; the node handling the telephone call depending upon the selected option
9. A method as claimed in claim 8, wherein the at least one option includes an option to accept the telephone call, wherein, if the information received by the node indicates that the selected option is to accept the call, the method further comprises : forwarding the telephone call from the node to the called telephone number
10. A method as claimed in claim 8 or claim 9, wherein the at least one option includes an option to reject the telephone call, wherein, if the information received by

<Desc/Clms Page number 23>

the node indicates that the selected option is to reject the call, the method further comprises notifying the caller that the called telephone number is busy.
11. A method as claimed in claim 8,9 or 10, wherein the at least one option includes an option to forward the telephone call to an alternative telephone number, wherein, if the information received by the node indicates that the selected option is to forward the call to an alternative telephone number and includes the alternative telephone number, the method further comprises: forwarding the telephone call from the node to the alternative telephone number.
12. A method as claimed in claim 8,9, 10 or 11, wherein the at least one option includes an option to transfer the telephone call to voicemail, wherein, if the information received by the node indicates that the selected option is to forward the telephone call to voicemail, the method further comprises: transferring the telephone call to the voicemail service associated with the called telephone number.
13. A method as claimed in any one of the preceding claim, further comprising: after the step of determining the called telephone number, comparing the determined called telephone number with a plurality of subscriber telephone numbers stored in memory, the method proceeding if the called telephone number is included in the plurality of subscriber telephone numbers,
14. A computer readable medium including a computer program for carrying out the method as claimed in any one of claims I to 13.
15 A communications system for handling a telephone call to a called telephone number, the system comprising: a node for receiving the telephone call from the Public Switched Telephone Network, the call being diverted to the node when the telephone line associated with the

<Desc/Clms Page number 24>

called telephone number is busy, the node including a processor for determining the called telephone number to which the call is directed; and a server for receiving a communication from the node about the telephone call and for sending a notification to a client having a client identifier associated with the called telephone number, the notification indicating the presence of the telephone call.
16. A system as claimed in claim 15, wherein the node comprises a telecommunications switch and a processor.
17. A system as claimed in claim 15 or claim 16, wherein the server has an associated database, the database comprising subscriber information including subscriber telephone numbers and associated client identifiers.