INFRARED DATA ASSOCIATION CALLER IDENTIFICATION APPARATUS
FIELD OF THE INVENTION The present invention relates generally to infrared data association communication and more particularly to infrared data association caller identification.
BACKGROUND OF THE INVENTION Infrared data association IrDA protocols were developed to permit transmitting of information from one computer to another quickly and easily without the need to configure protocols or connect wires. The IrDA protocols have been adopted by many different personal desk accessory PDA manufacturers, notably the Palm and Windows CE platforms, as well as by many desktop and portable computers. The ability to "beam" information from one Palm or other PDA or computer to another is a very useful function. Any two people with compatible PDA's and/or software can transfer records or programs.
Although the user of caller identification ID is prevalent in telephone communications, the data is normally locked up inside a caller ID "box" or adjunct device and must be manually entered into a PDA or computer. Manually entry of caller ID information can be tedious and time consuming where many calls and their ID information are logged over a day or several days.
Accordingly, there is a need for eliminating re-keying of caller identification information from a caller ID device by allowing the caller identification data to be beamed directly to any IrDA capable computer.
SUMMARY OF THE INVENTION An infrared data association caller identification apparatus includes a phone network interface, an infrared transceiver for wireless data exchange with a device that has an infrared data association interface for data exchange, a caller identification decoder coupled to the phone network interface, and a central processing unit coupled to
the decoder and the infrared transceiver for processing requests for caller identification from across the infrared transceiver. A method for handling caller identification requests across an infrared wireless link, the method comprising the steps of interfacing to a phone network, decoding caller identification for a phone communication through the interfacing to the phone network interface, receiving a caller identification request across an infrared transceiver from a device having an infrared data association interface, and transferring the caller identification from the decoding across the infrared transceiver to the device having an infrared data association interface.
BRIEF DESCRIPTION OF THE DRAWINGS A more complete understanding of the present invention may be obtained from consideration of the following description in conjunction with the drawings, in which: FIG. 1 is a block diagram of an infrared data association IrDA caller identification device according to an embodiment of the invention; FIG. 2 is a diagram of the internal blocks in the IrDA caller identification device of FIG. 1; FIG. 3 is a block diagram of the operating logic of the central processing unit of FIG. 2; To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures.
DETAILED DESCRIPTION Referring to the block diagram 100 of FIG. 1, the present infrared data association IrDA caller identification (Caller ID) device 111 incorporates an interface to telephone network , e.g., public switched telephone network 106, capable of decoding Caller ID signals, and an IrDA transceiver 203 capable of exchanging data with computers. The purpose is to provide a translation of Caller ID data into a form that can be transmitted to a computer with IrDA capability 104, and optionally to also allow the computer to provide a phone number to dial.
The inventive IrDA Caller ID device is constructed by combining a telephone line interface circuitry and CTD decoding hardware with an intelligent processor tied to an IrDA transceiver. A block diagram 201 of the internal components in the IrDA caller identification device 111 are shown in FIG. 2. The internal workings of the IrDA caller identification device 103 include an IrDA compatible transceiver (IrPHY) 203, and a central processing unit CPU 201 controlling a caller identification CID decoder and dialer 202 across Data In, Control Signals and Data Out connections. The processor CPU 201 implements the IrDA protocols necessary to transfer the data to a computer 104. In FIG. 3, a block diagram 300 shows an exemplary operating logic of the central processing unit CPU 201 of FIG. 2. The operating logic of the central processing unit includes an IrDA physical layer IrPHY driver and IrDA protocol stack 304, a control program 302 that manages data flow and features, a caller identification CID decoder 301, a phone line interface 305 and an optional DTMF dialer driver 303. The IrDA protocol stack includes IrPHY, LLAP, IrLMP, Tiny TP, IrOBEX and IrCOMM layers.
The Infrared Physical Layer is the lowest protocol level of the IrDA protocol stack and is referred to as IrPHY. IrPHY defines the method and format of the data frames sent and received on the infrared media. The Infrared Link Access Protocol (IrLAP) and Infrared Link Management Protocol (IrLMP) allow devices to discover each other and connect to services provided. The Tiny Transport Protocol (TinyTP) is used by applications to make connections and to send and receive data using a reliable transport. At the top of the IrDA protocol stack, the application can use IrOBEX or IrCOMM to communicate with other devices. The Infrared object Exchange Protocol Layer (IrOBEX) allows systems of all sizes and types to exchange a wide variety of data and commands in a resource-sensitive standardized fashion. This protocol layer takes an arbitrary data object (a file, for instance) and sends it to whomever the IR device is pointing. IrOBEX also provides tools that enable the object to be intelligently recognized and handled on the receive
side. The Infrared Communications IrCOMM protocol layer provides an emulation of a device connected via a serial or parallel port. Legacy applications proceed to work the same way in communicating with the devices through the same APIs without knowing that it is actually the IrDA protocol stack that is put to operation. By this way, older applications are made to make use of the latest and efficient means of communications available.
The control program 302 handles requests received from an IrDA capable computerl04 through the IrOBEX protocol. The control program responds to those requests, providing transfer of Caller ID information. It may also have the capability to transfer a copy of the program necessary for operating the device to the computer through an IrOBEX data file transfer.
Optionally, this device may include a dual tone multi-frequency DTMF dialer mechanism, which will allow the computer to send an IrOBEX request to the control program to initiate a temporary off-hook status on the line and DTMF tones to dial the number provided.
Although various embodiments which incorporate the teachings of the present invention have been shown and described in detail herein, those skilled in the art can readily devise many other varied embodiments that will still incorporate these teachings.