One-button intelligent cti dialler

CA 02230692 1998-03-02

One-Button Intelligent CTI Dialler

Field of the Invention

This invention relates in general to phone diallers, and more particularly to a one-button dialler for use in a CTI (Computer Telephony Integration) communication system,.

Background of the Invention

CTI has evolved with the intention of simplifying telephone communications through the use of computers. For example, PC-based call processing, enhanced directory applications and automated attendant functions allow a person to integrate telephone and computer functionality. However, one telephony function - placing a call, is more complicated when executed by computer than when direct dialled on a phone set. Making a phone call from a PC (Personal Computer) usually involves several steps. First, the current application (e.g. MS Word®) is minimised or closed. Second, the CTI application is opened. Third, the phone number is entered using either a numeric keypad or via point-and-click numbers. Then, an “accept” or “dial” button is clicked in the CTI application, resulting in the PC directing the associated telephone to dial out the phone number.

In an effort to simplify dialling, some CTI applications mimic phone speed dialling by using directory applications. However, the user nonetheless is required to

CA 02230692 1998-03-02 navigate the directory which can often take longer than simply picking up the phone and dialling the number.

The general concept of automatic dialling under computer or microprocessor 5 control is well known in the prior art, as for example, disclosed in Di Santo et al (U.S.

Patent 4,870,677), Kikinis et al (U.S. Patent 5,522,089) and Draganoff (U.S. Patent

5,541,988).

in Di Santo et al a telephone number is displayed on a programmable display 10 portion of a telephone set and once selected (via a cursor) one-button dialling results in out-pulsing of the selected telephone number. This system is essentially an enhanced speed dial with directory display on the telephone set.

In Kikinis, the telephone number can be dialled under operating system control.

The telephone number is selected via cursor point-and-click, and then an “OK” button is used to dial the digit.

Draganoff teaches the use of one-button automatic dialling such that, once a telephone number and other alpha-numeric data have been selected on a notebook or

PC, depression of the “Tel” button on the keypad results in dialling via an interface circuit, which receives the telephone number from a CPU via a buffer.

Draganoff is relevant for teaching one-button dialling once a telephone number has been “selected” in a computer application. However, there is no teaching or

CA 02230692 1998-03-02 suggestion in Draganoff (or any of the other references discussed above) of any means for overcoming the prior art difficulty of finding a telephone number and then dialling it in a straightforward, uncomplicated manner.

Summary of the Invention

According to the present invention, a CTI process is provided for implementing one-touch dialling from any application active on a PC. The process of the present invention employs a hierarchical method of locating a phone number to dial from text displayed on the PC screen by the active (or background) applications. Therefore, the method and apparatus of the present invention overcomes the difficulties in the prior art of navigating through complex procedures to find and then dial a phone number.

Brief Description of the Drawings

A detailed description of the preferred embodiment is provided herein below with reference to the following drawings, in which:

Figure 1 is a schematic representation of a CTI system for implementing the one-button intelligent dialler of the present invention;

Figure 2 is a schematic representation of a PC connected to a phone, incorporating software for implementing the preferred embodiment;

CA 02230692 1998-03-02

Figure 3 is a schematic representation of a screen display from an active application on the PC shown in Figure 2, in connection with which the software of the preferred embodiment locates a phone number to dial; and

Figure 4 is a schematic representation of a phone forming part of the CTI system of Figure 1.

Detailed Description of the Preferred Embodiment

Figure 1 shows a CTI system comprising a PC 1, a phone 2, and a communication line 3 between the PC 1 and phone 2 (e.g. USB connection, TAPI, etc.).

According to the invention, phone 2 is provided with a one-touch dial button 4. A mouse pointer 5 is connected to PC 1 in the usual manner.

PC 1 executes various software including operating system 10 (e.g. Windows

NT®, Windows 95®), USB (or other) driver 11, a plurality of applications 13 (e.g. Word®), a spawned process 13 in accordance with the invention, and an interapplication/process communication protocol 15 (e.g. OLE for Windows NT®). This software is resident in RAM memory 31 and executed via CPU 32 in a well known manner.

Applications 13 typical generate an output for viewing on a screen. Figure 3 shows a screen 20 for displaying selected text (e.g. 555-1 111) from an active

CA 02230692 1998-03-02 application 22 (e.g. email application), against a background application 23 (e.g. Excel®) having an application cell 24. The notional screen layout of Figure 2 will, of course, vary from one computer session to the next, depending on which applications are executed, etc. A mouse cursor 25 is displayed under control of mouse controller 5 (Figure 1) in a well known manner.

As shown in Figure 4, within the phone 2, an input controller 41 is provided for communicating with CPU 43 in response to activation of dial button 4. CPU 43 executes software which is resident in memory 42 (e.g. RAM). CPU 43 also transmits 10 and receives data from the communication line 3 (e.g. USB bus) via communication controller 44.

[n operation, a user activates (e.g. presses) the dial button 4 in response to which the phone 2 queries the PC 1 (via communication line 3) for a phone number to dial.

The operating system of the PC 1 spawns a process 14 which checks for a phone number in the active application 13 and returns the phone number to the phone 2 via communication line 3.

More particularly, with reference to Figures 1 to 4 in combination, in response 20 to pressing the dial button 4, input controller 41 (Figure 4) of the phone 2 signals CPU that the button 4 has been activated. The CPU 43 then runs software 42 for generating a signal over the line 3, and waits for a response from the PC 1. The signal on line 2 is detected by USB driver 11 (or other appropriate driver) running in memory

CA 02230692 1998-03-02 on PCI.

Pseudo code for the software 42 executed within phone 2 is as follows:

Procedure OTBD_Pressed

BEGIN

Signal-PC-That-OTDB-is-pressed();

wait-for-response();

number-to-dial:=response-from-PC;

dial(number-to-dail);

END

The process 14 spawned by operating system 10 in PC 1 provides a method for finding phone numbers displayed on screen 20. In the four-step method described below, any methods enclosed with {} indicate a Microsoft specific function call which is available to all software running on Windows NT 3.51, NT 4.0 and Windows 95. It is well within the skill of a programmer to execute any of these functions. Details about the functions are available on the Microsoft Developer Network CD-ROM Development Library (e.g. January 1996 edition). This CD reference library is Microsoft part number 69145.

The method of the present invention, as executed by process 14 is as follows:

1. Find the active application (22) on the screen (2) • For example by using the {GetForegroundWindow} function a handle can be obtained to the active window, or NULL if there is no active window.

2. If there is an Active window, see if the user has highlighted anything in the

CA 02230692 1998-03-02 application (13), and determine if it is a phone number (see below).

• For example, by using the {EM_EXGETSEL} function to the active application the selected text can be obtained.

3. If nothing is selected, or the process is unable to resolve a phone number in step 2, query the OS (10) for the present mouse cursor position (25). Ask the window under the cursor for all of the text within a pre-set (user definable) distance of the mouse cursor, and search for a phone number.

• For example, by using the {GetCursorPos} and {WindowAtPoint} functions it is possible to determine which window the user is pointing at. Then, by sending {SetForegroundWindow} that window can be brought to the foreground. By sending

EMGETTEXTRANGE) to the now active application, the text in the area of the mouse pointer is obtained and the process can search for a telephone number, as discussed in greater detail below.

4. If a phone number still has not been found, capture the screen to RAM and use Optical Character Recognition (OCR) to read all of the text from the screen. The necessary screen capture utility and optical character recognition software are not described in detail herein, but are freely available and commonly and easily used for many other applications. Finally, the process tries to find a phone number from the

OCR text (e.g. 2212” at (24) can be found with this method if the email app (22) does not have a phone number in it).

• Screen Capture programs are well known and easy to find and implement. For example, the product Lview Pro from the MMEdia

CA 02230692 1998-03-02

Research, 1501 East Hallendale Beach Boulevard, #254, Hallendale,

Florida, 33009 is one of many available screen capture programs.

• Using the graphical data from the screen capture, use one of the many available OCR programs to read the screen capture, and covert any characters/words/numbers on the screen to text. Then, parse the text for a phone number (see below). An example of easily available OCR software includes Xocr, Martin Bauer, Zeppelinstr 97, 70193 Stuttgart

Germany.

If a number still cannot be found, the user can be connected to a default extension (e.g. a switchboard).

The pseudocode for finding phone numbers is as follows:

Procedure find_PhoneNumber()

BEGIN

IF(is-there-an-active-window-on-screen)

BEGIN text:=get-selected-text;

number:=findPhoneNumbert(text);

IF(number !=nil) retum(number);

END;

END

ELSE

BEGIN make-window-under-mouse-pointer-foregroundO;

text:=get-text-in-region-of-mouse-in-foreground-window();

number:=findPhoneNumber(text);

IF (number !=nil) retum(number);

END;

/* At this point, there was no number found in the window under the cursor, nor any selected text is a phone number. So, capture the window and run OCR software on it.*/

CA 02230692 1998-03-02 windowGraphic:=captureScreen();

text:=OCR(windowGraphic);

number:=findPhoneNumber(text);

If (number !=nil) return (number)

ELSE return (/*DEFAULT NUMBER HERE, EG: ATTENDANT*/)

END

The process of finding a phone number in a given array of text is well known in the art, and is described herein to clarify the process discussed above.

The process for finding a phone number in a selection or text depends on user definable parameters. For example, a phone number text string could be:

1. 0, or

2. Any 4 digit sequence, or

3. 9 plus any 7 digit sequence, or

4. any seven digit sequence (the 9 is added automatically), or

5. a 9 plus 3 digits plus a plus 4 digits

6. etc...

The pseudocode for resolving a phone number from a set of text, is as follows,

Procedure findPhoneNumber(text)

BEGIN

REPEAT

BEGIN

TEXT:=strip-non-numerics-from-front-of(text);

/*Eg, Donaldx4304 would become 4303, xsdfgsdfg would become ''*/

IF (text=) return nil;

CA 02230692 1998-03-02 temp:=read-through-valid-phone-characters(text) /*0 through 9, -, space, *,# are valid phone characters */ /*Eg, if text=459-7226 (donald smith) then temp would equal 456-7226*/

IF (isValidPhonenumber (temp)) /*isValidPhoneNumber code would depend on whatever criteria the system needs, for example see 1-5 in III*/ return (temp)

ELSE text:=strip-valid-phone-characters(text) /♦so, 34 Donald Smith would become Donald Smith*/

END

END

A representative output of this process is shown in Table 1 :

TABLE 1

<td> Example Input</td><td> Example Output</td>

<td> 1234”</td><td> 1234</td>

<td> Donald Smith x4303</td><td> 4303</td>

<td> Donald's number: 4304 (HOME).</td><td> 4304</td>

<td> sfgkhdsfljg</td><td> nil</td>

A person understanding the principles of the present invention may conceive of alternative embodiments or variations thereof. For example, a “phone number” according to the present invention may include an Internet address (expressed either as a domain name or as an EP address), in which case an Internet phone application can be used to place the call over an ISDN line. Also, dial button 4 may be implemented as the third button on mouse 5 rather than being provided on the phone 2. All such embodiments and variations are believed to be within the sphere and scope as set forth in the claims appended hereto.