Caller ID messaging telecommunications services

Abstract
Methods, systems, and apparatuses for caller identification messaging are disclosed. According to one embodiment, a calling party uses a Caller ID Messaging Device that supplants the incoming calling line identification (ICLID) signal with a Caller ID Messaging Signal and transmits the Caller ID Messaging Signal to a destination communications address. An alternate embodiment provides that the calling party may use a conventional telephone to access a communications network, activate Caller ID Messaging Services, compose or retrieve a stored Caller ID Message of the Caller ID Messaging Signal, and transmit the Caller ID Messaging Signal to the destination communications address. The Caller ID Message and Caller ID Messaging Signal may include text, video, voice, and/or digital data.
Description
CROSS REFERENCE TO RELATED APPLICATIONS

This application relates to applicants' co-pending U.S. patent application Ser. No. 10/418,878, entitled “Caller ID Messaging,” filed simultaneously herewith and of which the “Brief Summary of the Invention” and “Detailed Description of the Invention” sections are incorporated herein by this reference.


This application relates to applicants' co-pending U.S. patent application Ser. No. 10/418,774, entitled “Caller ID Messaging Device,” filed simultaneously herewith and of which the “Brief Summary of the Invention” and “Detailed Description of the Invention” sections are incorporated herein by this reference.


This application relates to applicants' co-pending U.S. patent application Ser. No. 10/418,768, entitled “Dynamic Caller ID Messaging,” filed simultaneously herewith and of which the “Brief Summary of the Invention” and “Detailed Description of the Invention” sections are incorporated herein by this reference.


This application relates to applicants'co-pending U.S. patent application Ser. No. 10/418,775, entitled “Private Caller ID Messaging,” filed simultaneously herewith and of which the “Brief Summary of the Invention” and “Detailed Description of the Invention” sections are incorporated herein by this reference.


NOTICE OF COPYRIGHT PROTECTION

A portion of the disclosure of this patent document and its figures contain material subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, but otherwise reserves all copyrights whatsoever.


BACKGROUND OF THE INVENTION

1. Field of the Invention


This invention relates generally to the field of communications. More particularly, this invention relates to a system and method for caller identification messaging.


2. Description of the Related Art


Telecommunications has experienced explosive growth, and more growth is planned as telecommunication access and numerous communications devices improve. This explosive growth is revolutionizing special services offered to subscribing customers. Of the special service offerings, the most relevant to this invention is the caller identification or Caller ID services. A customer or a user of a telephone that is served by the Caller ID service is provided with a calling party's directory information. Presently available Caller ID systems provide the calling party's telephone number and a billing name associated with the calling party's telephone number (if available) when an incoming caller line identification (ICLID) signal can be detected, decoded, and transmitted to the called telephone or other display device associated with the called telephone (e.g., a Caller ID device). The Caller ID services also allow a receiving party to receive directory information for other incoming calls while the receiving party's phone is used (e.g., during a conversation with another party); this service is sometimes referred to as Caller ID Call Waiting service.


A customer may use the displayed Caller ID information to make a decision whether to answer and/or to prepare for the call. Thereafter, the customer has a record of the Caller ID information and may use that information to return a call or to track incoming calls. A problem arises when the customer cannot recognize the Caller ID information. For example, if a calling party uses a pay phone to place the incoming call, then the Caller ID information displays the number associated with the pay phone. If the customer does not recognize the pay phone number, the customer, then, cannot associate the number with the calling party. Other problems exist with limited information transmitted with the ICLID signal and with limited capabilities of Caller ID devices. In recent years, telephony providers and manufacturers have tried to provide alternate caller identification systems and methods.


For example, U.S. Pat. No. 5,784,444, entitled “Method and Apparatus for Providing Personal Calling Identification at Remote Locations,” discloses a method for a caller to provide an alternate telephone number to be used instead of the telephone number of the calling station as the ICLID number. Further, the '444 patent discloses an apparatus that displays both the alternate telephone number and the telephone number of the calling station and that also displays a textual message along with both telephone numbers. Another example is U.S. Pat. No. 6,192,116 B1, entitled “System and Method for Generating CID/CIDW Information with a User Inputted Message,” that discloses a method and system for sending the CID/CIDW information along with an alphanumeric message to a second phone. Both the '444 and '116 patents, however, have several drawbacks that include necessitating specialized peripheral hardware and equipment, limiting the textual message and alphanumeric message for visual presentation by the specialized peripheral hardware and equipment, and limiting transmission of the textual message and the alphanumeric message to the called phone.


BRIEF SUMMARY OF THE INVENTION

This invention addresses the above and other needs by providing systems and methods for enabling and/or generating Caller ID messaging. Typically, a calling party uses a Caller ID Messaging Device that supplants the incoming calling line identification (ICLID) signal with a Caller ID Messaging Signal and transmits the Caller ID Messaging Signal to a destination communications address. The Caller ID Messaging Signal includes a personalized message and may also include an identifier of the calling party (e.g., name, address of calling party's communications device, such as an originating telephone number, etc.), an identifier of the destination communications address (e.g., name of called party, address of the called party's communications device, such as the destination telephone number, etc.), and/or an identifier of the calling party's communications device (e.g., POTS phone, cellular phone, personal digital assistant, etc.). Alternatively, the calling party may use a conventional telephone to access a communications network, activate Caller ID messaging services, compose or retrieve a stored Caller ID Message, and transmit the Caller ID Messaging Signal to the destination communications address. The Caller ID Message may include text, video, voice, and/or digital data. After the Caller ID Messaging Signal is transmitted to the destination communications address, a receiving party (e.g., called party) may act on the caller identification messaging signal. For example, the receiving party may review the Caller ID Message signal, respond with a response Caller ID Message, forward the Caller ID Messaging Signal, store the Caller ID Messaging Signal, ignore the Caller ID Messaging Signal, and other handling options. Additionally, a telecommunications customer may subscribe to a Caller ID Messaging Blocking service to decline Caller ID Messaging (similar to Privacy Director).


In an embodiment, a Caller ID messaging communications system includes a communications network having a communications server, a caller identification messaging application, and a caller identification messaging dataserver. The communications server communicates with the communications network to detect an incoming communications signal on a communications link from a calling party's communications device to a caller identification messaging access address (e.g., an 800 number or local access number). After a connection is established between the calling party's communications device and the communications network, the caller identification messaging program prompts a calling party to input and/or select data for generating a caller identification message and/or a caller identification messaging signal. The caller identification messaging application further interfaces the caller identification messaging dataserver to access a stored (or alternatively, to save) caller identification messaging profile. The communications network may include a public switched telephone network (PSTN), a mobile switching telephone communications network (MSTO), a world wide electronic data communications network (e.g., Intranet, Internet, and Extranet), satellite communications network, and/or other networks.


In another embodiment, a method for caller identification messaging includes processing a communications signal from a calling party communications device to a caller identification access address, associating an incoming line identification (ICLID) signal with the communications signal, associating a caller identification messaging profile with the ICLID signal, and generating a caller identification messaging signal using the caller identification messaging profile and/or a caller identification messaging instruction supplied by a calling party (e.g., the communications network prompts for the destinations communications address and the calling party enters a telephone number of the receiving party's communications device). The calling identification messaging signal includes a caller identification message and/or (1) an identifier of the calling party, (2) an identifier of the destinations communications address, and/or (3) an identifier of an originating communications address of the calling party. In further embodiments, the method includes transmitting the caller identification message and/or the caller identification message signal to the destinations communications address.


The caller identification messaging profile includes data for (1) the caller identification message, (2) the identifier of the calling party (e.g., a name of the calling party), (3) the identifier of the originating communications address (e.g., a phone number of the calling party's telephone), (4) caller identification messaging services associated with at least one of the calling party and the originating address, (5) the identifier of the destinations communications address (e.g., a telephone number of the receiving party), (6) an identifier of a receiving party communications device (e.g., a cellular phone), (7) caller identification messaging services associated with at least one of the receiving party and the destinations communications address, and (8) caller identification messaging default service parameters (e.g., always format the caller identification message as text). Typically, the caller identification messaging services provide instructions for (1) billing for communications of caller identification messaging signals over the communications network, (2) parameters that enable caller identification messaging including times of day and days of week, (3) parameter that disable caller identification messaging including times of day and days of week, (4) parameters to block caller identification messaging, (5) identification and authentication parameters, (6) parameters to bypass the disable parameters, (7) memory services for data stored with caller identification messaging signals, and/or (8) configuration and formatting preferences for each calling party communications device communicating with the network.


Further details on these embodiments and other possible embodiments of this invention are set forth below. As is appreciated by those of ordinary skill in the art, this invention has wide utility in a number of areas as illustrated by the discussion below. These embodiments may be accomplished singularly, or in combination, in one or more of the implementations of this invention.





BRIEF DESCRIPTION OF THE DRAWINGS

The above and other embodiments, objects, uses, advantages, and novel features of this invention are more clearly understood by reference to the following description taken in connection with the accompanying figures, wherein:



FIG. 1 is a schematic of a Caller ID messaging communications system illustrating a communications network connecting a calling party's communications device with a Caller ID Messaging Device and a receiving party's communications device according to an embodiment of this invention;



FIG. 2 is a block diagram of a Caller ID Messaging Device according to an embodiment of this invention;



FIGS. 3-4 are perspective front views of the Caller ID Messaging Device of FIG. 2 including screen displays for inputting a destination communications address and a Caller ID Message according to embodiments of this invention;



FIG. 5 is a perspective front view of a conventional Caller ID Device (labeled “PRIOR ART”) illustrating the screen display presenting an incoming line identification (ICLID) signal;



FIG. 6 is a perspective front view of the Caller ID Device of FIG. 5 illustrating the screen display supplanting a Caller ID Message of the Caller ID Messaging Signal for the ICLID signal;



FIG. 7 is a more detailed schematic of a Caller ID messaging communications system further illustrating the communications connections of the calling party's communications device and Caller ID Messaging Device, the communications network(s), and the receiving party's communications device according to an embodiment of this invention;



FIG. 8 is a another exemplary schematic of a Caller ID messaging communication system illustrating alternate calling party communications devices according to an embodiment of this invention;



FIG. 9 is another exemplary schematic of a Caller ID messaging communications system illustrating a personal computer having a Caller ID Messaging Program Interface coupled with the modem of FIG. 8 according to an embodiment of this invention;



FIG. 10 is a schematic of another Caller ID messaging communications system illustrating a communications network connecting a calling party's communications device with a Caller ID Messaging Device and a receiving party's communications device with a Caller ID Messaging Device according to an embodiment of this invention;



FIG. 11 is a perspective front view of the receiving party's Caller ID Messaging Device of FIG. 10 including a screen display for presenting the caller identification messaging signal according to an embodiment of this invention;



FIG. 12 is a perspective front view of the receiving party's Caller ID Messaging Device of FIG. 10 including a screen display for the selection of inputting a response caller identification message according to an embodiment of this invention;



FIG. 13 is a perspective front view of the receiving party's Caller ID Messaging Device of FIG. 12 including a screen display for inputting the response caller identification message according to an embodiment of this invention;



FIG. 14 is a perspective front view of the receiving party's Caller ID Messaging Device of FIG. 10 including a screen display for inputting a forwarded communications address to forward the caller identification messaging signal according to an embodiment of this invention;



FIG. 15 is a detailed schematic of a Caller ID messaging communications system illustrating the communications connections of a calling party's telephone and Caller ID Messaging Device, a receiving party's communications device and Caller ID Messaging Device, a forwarded party's communications device(s), and the communications network(s) according to an embodiment of this invention;



FIG. 16 is a schematic of another Caller ID messaging communications system illustrating a communications network connecting a calling party's communications device and a receiving party's communications device according to an embodiment of this invention;



FIG. 17 is a more detailed schematic of the Caller ID messaging communications system of FIG. 16 further illustrating the communications connections of the calling party's telephone, the communications network(s), and a receiving party's communications device according to an embodiment of this invention; and



FIGS. 18-20 are flowcharts illustrating communications methods for Caller ID messaging according to embodiments of this invention.





DETAILED DESCRIPTION OF THE INVENTION

This invention now will be described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those of ordinary skill in the art. Moreover, all statements herein reciting embodiments of the invention, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future (i.e., any elements developed that perform the same function, regardless of structure).


Thus, for example, it will be appreciated by those of ordinary skill in the art that the diagrams, schematics, flowcharts, and the like represent conceptual views or processes illustrating systems and methods embodying this invention. The functions of the various elements shown in the figures may be provided through the use of dedicated hardware as well as hardware capable of executing associated software. Similarly, any switches shown in the figures are conceptual only. Their function may be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the entity implementing this invention. Those of ordinary skill in the art further understand that the exemplary hardware, software, processes, methods, and/or operating systems described herein are for illustrative purposes and, thus, are not intended to be limited to any particular named manufacturer.


The Caller ID messaging systems and methods of this invention operate with different communications devices and communications networks to generate, enable, and/or transmit a Caller ID Message. Typically, a public switched telecommunications network (PSTN) automates configuration and routing of a Caller ID Messaging Signal that includes the Caller ID Message and may also include an identifier of a calling party, an identifier of a destinations communications address (typically associated with a receiving party's communications device), and an identifier of an originating communications address (typically associated with a calling party's communications device). The Caller ID Messaging Signal may be generated by a Caller ID Messaging Device and/or by interactions with the PSTN (or, alternatively other communications networks) and the calling party's communications device. Some advantages of Caller ID messaging include the ability to use a conventional POTS phone with a connected communications network to generate a Caller ID Message, the ability of the communications network to transmit a Caller ID Message to a conventional Caller ID device (so that specialized hardware and equipment is not necessitated), the ability of the communications network to identify the receiving party's communications device to format the Caller ID Message for presentation by the receiving party's communications device, the ability to use a Caller ID Messaging Device to generate, respond to, forward, and/or otherwise manage Caller ID Messages (including other information that may be transmitted with the Caller ID Messaging Signal), the ability to transmit the Caller ID Message to numerous communications devices associated with a receiving party, and the ability to identify whether the receiving party blocks or does not accept Caller ID Messaging Signals and, if so, notify the calling party of the Caller ID Message delivery failure.


As used herein, the term “communications device” includes wired and wireless communications devices, such as a mobile phone, a wireless phone, a WAP phone, a satellite phone, a computer, a modem, a pager, a digital music device, a digital recording device, a personal digital assistant, an interactive television, a digital signal processor, and a Global Positioning System device. Further, as used herein, the term “data” includes electronic information, such as, for example facsimile, electronic mail (e-mail), text, video, audio, and/or voice in a variety of formats, such as dual tone multi-frequency, digital, analog, and/or others. Additionally, the data may include: (1) executable programs, such as a software application, (2) an address, location, and/or other identifier of the storage location for the data, (3) integrated or otherwise combined files, such as a grouping of destination communications addresses associated with the receiving party, and/or (4) profiles associated with the Caller ID Messaging Signal, including configuration, authenticity, security, and others. In various embodiments, the data may be stored by the communications network, a peripheral storage device connected to the communications network, the Caller ID Messaging Device, and/or other connected networks.


Referring now to the figures, FIG. 1 illustrates a Caller ID messaging communications system 100 including a calling party's communications device 110 having (or coupled with) a Caller ID Messaging Device 200, at least one communications network 120, and a receiving party's communications device 130. A calling party composes, retrieves, and/or otherwise generates a Caller ID Message using his/her communications device 110 and/or the Caller ID Messaging Device 200 which transmits a Caller ID Messaging Signal with the Caller ID Message, an identifier of a calling party (e.g., name, workstation, name of employer, phone number, etc.), an identifier of a destinations communications address (e.g., receiving party's telephone number, receiving party's IP address, etc.), and/or an identifier of the calling party's communications device (e.g., cellular phone, personal digital assistant, etc.) to the communications network 120. Typically, the communications network 120 detects and decodes the incoming Caller ID Messaging Signal, compares the incoming Caller ID Messaging Signal with Caller ID messaging data stored in one or more databases of the communications network to determine one or more destination communications addresses of the receiving party, whether the destination communications address(es) accepts Caller ID Messaging Signals, and/or presentation capabilities of the receiving party's communications device 130 associated with each destination communications address.



FIG. 2 is a block diagram showing the Caller ID Messaging Device 200 according to an embodiment of this invention. The Caller ID Messaging Device 200 includes a Caller ID Messaging Program 214 that operates within a system memory device 212. The Caller ID Messaging Program 214, however, could also reside in flash memory or a peripheral storage device 216. The Caller ID Messaging Device 200 also has one or more central processors 220 executing an operating system. The operating system, as is well known, has a set of instructions that control the internal functions of the Caller ID Messaging Device 200. A system bus 222 communicates signals, such as data signals, control signals, and address signals, between the central processor(s) 220 and a system controller 210. The system controller 210 provides a bridging function between the memory subsystem 212, the one or more central processors 220, a graphics subsystem 230, a keyboard subsystem 232, an audio subsystem 234, a PCI (Peripheral Controller Interface) bus 224, and a Communications (“Comm”) Device Interface 250. The PCI bus 224 is controlled by a Peripheral Bus Controller 240. The Peripheral Bus Controller 240 is an integrated circuit that serves as an input/output hub for various peripheral ports and/or transceivers. These peripheral ports allow the Caller ID Messaging Device 200 to communicate with a variety of communications devices through networking ports (such as SCSI or Ethernet) that include Wireless Communications (“Comm”) Device Transceiver 242 (such as Wireless 802.11 and Infrared) and Wired Communications (“Comm”) Device Port/Connection 244 (such as modem V90+ and compact flash slots). These peripheral ports could also include other networking ports, such as, a serial port (not shown) and/or a parallel port (not shown). The Comm Device Interface 250 allows the Caller ID Messaging Device 200 to monitor, detect, receive, and decode incoming communications signals to the communications device(s) connected to the Wireless Comm Device Transceiver 242 and/or the Wired Comm Device Port/Connection 246. Further, the Comm Device Interface 250 transmits the outgoing Caller ID Messaging Signal to the Wireless Comm Device Transceiver 242 and/or the Wired Comm Device Port/Connection 246. Still further, the Caller ID Messaging Device 200 may include a power source 260, such as a rechargeable battery to provide power and allow the Caller ID Messaging Device 200 to be portable. In alternate embodiments, the Caller ID Messaging Device 200 could include its own telephone line (or other communications connection) to the communications network 120 (not shown). Another alternative may include the Caller ID Messaging Device 200 incorporated into a specially designed communications device (not shown).


The system memory device (shown as memory subsystem 212 or peripheral storage device 216) may also contain one or more application programs. For example, an application program may cooperate with the operating system and with a video display unit (via graphics subsystem 230) to provide a GUI for the Caller ID Messaging Program 214. The GUI typically includes a combination of signals communicating with the graphics subsystem 230 and/or the keyboard subsystem 232. The GUI provides a convenient visual and/or audible interface with the user of the Caller ID Messaging Device 200. As is apparent to those of ordinary skill in the art, the user (e.g., calling party) interacts with the Caller ID Messaging Program over a variety of mediums, such as, for example, a stylus, keyboard, and punch buttons of the keyboard subsystem 232, a display screen of the graphics subsystem 230, and/or a voice-activated menu prompt of the audio subsystem 234. Additionally, the peripheral bus controller 240 provides an interface with a biometrics sensor 246, such as, for example, a fingerprint ID device. The biometrics sensor 246 may provide security features that prevent unauthorized users from exploiting the Caller ID Messaging Device 200. The biometrics sensor 246 could also comprise retina recognition device and software, DNA/RNA recognition device and software, facial recognition device and software, speech recognition device and software, and/or scent recognition device and software.


Referring now to FIGS. 3-4 in conjunction with FIG. 2, the graphics subsystem 230 includes a display screen 300 having displays for a time 302, a date 304, a numeric identifier 306 of an incoming Caller ID Message (transmitting ICLID signal), a numeric identifier 308 of an outgoing (or an incoming) Caller ID Messaging Signal, and a graphical user interface 310 for selecting and/or inputting a destinations communications address of the Caller ID Messaging Signal. The Caller ID Messaging Device 200 also includes a lighted display panel 320 that flashes to produce a visual alert of incoming and/or outgoing Caller ID Messaging Signals and/or incoming ICLID (e.g., Caller ID) signals. The lighted display panel 320 may be part of graphics subsystem 230 or may be an isolated component. The keyboard subsystem 232 includes punch buttons 330, 335, 340, 342, 344, 346, and 348, keyboard 350, and stylus 355. The stylus 355 is connected by a cord 356 or other appropriate connection assembly (not shown) to a housing 370 of the Caller Id Messaging device 200 and positioned in a storage holder 357 when not in use. The stylus 355 may be used to interact with the keyboard 350 and/or with the display 300 to input Caller ID messaging data (e.g., destinations communications address, Caller ID Message, etc.). Alternatively, the user could use his/her fingers or other pointed device to select each character from the keyboard 350 and/or to sketch something onto the display 300 (such as a doodle to transmit with the Caller ID Message signal). With regards to the punch buttons, they provide a convenient interface for quickly interacting with the Caller ID Messaging Device 200. For example, the user may punch or press (1) a left arrow key 330 to scroll backwards through Caller ID Messages, go back a step when interacting with the Caller ID Messaging Program 214, and/or for other interactions with the Caller ID Messaging Program 214, (2) a right arrow key 335 to scroll forwards through Caller ID Messages and for other interactions with the Caller ID Messaging Program 214, (3) a “Compose/Respond” button 340 to initiate composing or responding to a Caller ID Messaging Signal, (4) a “Send” button 342 to send or otherwise transmit the Caller ID Messaging Signal, (5) a “Delete” button 344 to erase Caller ID Messages, (6) a “Save” 346 button to store Caller ID Messages, (7) a “Voice” button 348 to record a voice or other audio message (in different embodiments, the audio message may be converted from a speech-to-text message for the outgoing Caller ID Messaging Signal and/or the audio message may be transmitted as the Caller ID Message) and/or to convert a text Caller ID Message from text-to-speech (such as with visually impaired customers), and (8) an “Enter” button 349 to enter and/or confirm selection of information displayed on the display screen 300. Further, the “Voice” button 348 interfaces with a speaker/recorder 360 of the audio subsystem 234 to audibly present and/or record data of the Caller ID Messaging Signal and to interact with the Caller ID Messaging Program 214 to administer and otherwise manage the Caller ID Messaging Device 200.


Typically, the calling party composes a Caller ID Messaging Signal by punching or pressing the “Compose/Respond” button 340 that brings up an interactive destinations communications addressing GUI 310. The user may select to (1) input a new address (e.g., telephone number), (2) select an address from recent calls (including outgoing and incoming), and (3) select an address from an address book (created by Caller ID Messaging Program 214). After the destination communications address(es) is selected, the address is displayed at a “Number to Call” portion 410 of the display screen 300. Alternatively, the address may be displayed as “Name of Receiving Party to Contact,” “Communications Address to Contact,” and so on, such that the destinations communications address may be associated with the receiving party and/or with communications devices using non-North American Numbering Plan (NANP) addressing schemes. After the destinations communications address is input, the calling party presses the “Enter” button 349 to enter the communications address and to bring up a Caller ID Message GUI 420 that allows the calling party to select whether to (1) input a new Caller ID Message or (2) select a Caller ID Message from memory. For example, if the user uses the right arrow 335 (or left arrow 330) to move pointer 440 on “Input A New Message” and then presses the “Enter” button 349, an Input Message GUI (not shown) is displayed and the user may use the keyboard subsystem 232, graphics subsystem 230, and/or audio subsystem 234 to enter the Caller ID Message. Should the user wish to erase or modify the Caller ID Message, the user may use the left arrow button 330 to back up and re-enter the Caller ID Message. Thereafter, the user punches or presses the “Send” button 342, and the Caller ID Messaging Program 214 uses the input information to generate the Caller ID Messaging Signal and transmits it to the Comm Device Interface 250. If, however, the calling party uses the right arrow 335 to move the pointer 440 on “Select A Message From Memory” and then presses “Enter” button 349, a Select Message GUI (not shown) is displayed with a menu for navigating stored Caller ID Messages (such as, for example, doodles drawn by a user, Caller ID Messages associated with the calling party or receiving party, an alphabetical or numeric listing of Caller ID Messages, search options for finding a stored Caller ID Message, frequently sent Caller ID Messages, and so on) and the calling party selects the Caller ID Message and presses the “Send” button 342 to generate the Caller ID Message and transmit it to the Comm Device Interface 250. The stored Caller ID Messages may be stored by local memory device 216, or by a peripheral storage device (such as Caller ID Messaging DataServer 718 shown in FIG. 7). The Comm Device Interface 250 initiates communications with the communications network 120 and transmits the Caller ID Messaging Signal. In an alternate embodiment, the Comm Device Interface 250 may format the Caller ID Messaging Signal for a connected or integrated communications device (via the Wireless Comm Device Transceiver 242 and/or Wired Comm Device Port/Connection 244), and, the connected or integrated communications device would then initiate communications with the communications network 120 and transmit the Caller ID Messaging Signal (via the connected or integrated communications device). Still, in another alternated embodiment, the Comm Device Interface may include intelligent componentry that detects or otherwise identifies the receiving party's communications device 130 and formats or otherwise configures the Caller ID Messaging Signal for presentation by the receiving party's communications device 130 (e.g., if the Caller ID Message is audio data, but the receiving party's communications device 130 does not present and/or accept audio data, then the audio data is converted to text).


The Caller ID Messaging Signal is routed over the communications network 120 to a receiving party's communications device 120. As illustrated in FIGS. 5 and 6, the receiving party's communications device 120 is a conventional Caller ID device 500. The Caller ID device 500 includes a display screen 500 having a time identifier 502, a date identifier 504, a numeric identifier of an incoming Caller ID signal (e.g., ICLID signal) 506, a lighted panel 520 that alerts the receiving party of a new, incoming, and/or stored Caller ID, a “Save” punch button 546, a “Delete” punch button, a left arrow button 530, a right arrow button 535, and a housing 550 that protects the internal componentry of the Caller ID device 500. Typically, the Caller ID device 500 receives an incoming ICLID signal and displays an originating NANP number 510 (i.e., the telephone number of the calling party) and a name 512 associated with the originating NANP number (shown as “CITY-COUNTY GOV” in FIG. 5). Conventional Caller ID devices comply with standards known in the art that limit the display of the ICLID signal to two lines of text, each line containing approximately fifteen (15) characters. As shown in FIG. 6, this invention supplants the ICLID signal (the NANP number 512 and name 512) with a Caller ID Message 610 of the Caller ID Messaging Signal so that a short personalized message (e.g., the Caller ID Message) is displayed or otherwise presented by conventional Caller ID device 500.



FIG. 7 is a schematic of a Caller ID messaging communications system 700 illustrating communications connections of the communications network(s) (shown as reference numerals 710 and 760) with the calling party's communications device 110 and the Caller ID Messaging Device 200 and with the receiving party's communications device 130. The Caller ID messaging communications system 700 includes the calling party's communications device 110 (shown as a POTS telephone) connected to the Caller ID Messaging Device 200, a communications switch 705 connected to a telecommunications network 710 that includes a service switching point (SSP) 712, a service control point (SCP) 714, an Intranet 716 (for the telecommunications provider to administer and program the telecommunications network 71 components), a Caller ID Messaging Dataserver 718, a database of one or more Caller ID Messaging Profiles 719, an Internet Service Provider (e.g., America On-Line) 750, a data network 760, a gateway 770, and a second communications switch 720 connected to the receiving party's communications device 130 (shown as an telephone capable of communications with the telecommunications network and with the data network). Each switch 705, 720 allows the connected communications devices 110, 130 to transceive electronic communication signals via the data network 760 (e.g., world wide electronic data network such as an Internet, an Intranet, and/or an Extranet) and/or the telecommunications network 710 (e.g., a central office (CO), a mobile telephone switching office (MTSO), and/or a combination CO/MTSO). The telecommunications network 710 may use any means of coupling one of the switches 705, 720 to the telecommunications network 710, but the coupling means is preferably high-capacity, high-bandwidth optical transport services, Gigabit Ethernet services, and/or the like. As those of ordinary skill in the art of telecommunications understand, the telecommunications network 710 could also link each of the switches 705, 720 via other appropriate means, such as, for example a Synchronous Optical Network (SONET) structure with redundant, multiple rings.


Typically, a customer and/or user of Caller ID Messaging Services (e.g., someone who subscribes to and/or someone who uses Caller ID Messaging Services) uses the Caller ID Messaging Device 200 and/or the calling party's communications device 110 to gain access to the telecommunications network 710. Each Caller ID Messaging Signal sent from the calling party's communications device 110 and/or Caller ID Messaging Device 200 is routed through the telecommunications network 710 via switch 705. The Caller ID Messaging Signal and other communications signals (e.g., ICLID) associated with an address of calling party's communications device 110 arrive at SSP 712 that analyzes the signals and routes the Caller ID Messaging Signal to the SCP 714 and then to the Caller ID Messaging DataServer 718 for further Caller ID Messaging Signal processing and routing information. The Caller ID Messaging DataServer 718 accesses the database 719 of Caller ID Messaging Profiles to determine if the receiving party's communications device blocks Caller ID messaging calls, to access presentation capabilities of the destination communications address and/or the receiving party's communications device 130, and/or to obtain other preferences, instructions, files, and/or associated Caller ID Messaging data as further described below. Thereafter, the telecommunications network 710 may transmit the Caller ID Messaging Signal (or a portion of the Caller ID Messaging Signal, such as just the Caller ID Message) via switch 720 to the receiving party's communications device 130. Alternatively, the telecommunications network 710 may transmit the Caller ID Messaging Signal via ISP 750 (or other connection) to the data network 760. The data network 760 then sends the Caller ID Messaging Signal via the gateway 770 to the receiving party's communications device 130 via switch 130. Still, another alternative, is for the telecommunications network 710 to transmit the Caller ID Messaging Signal directly to the gateway 770 (such as when a Caller ID Messaging Profile associates a static IP address of the receiving party's communications device 130) to transmit to the receiving party's communications device 130 via switch 720. In addition to transmitting the Caller ID Messaging Signal, the telecommunications network 710 may also connect the calling party's communications device 110 with the receiving party's communications device 130 to establish a voice connection (e.g., connect the telephone call). That is, when the receiving party is alerted (via an audible alert and/or visual alert) of the incoming communication(s) (e.g., the Caller ID Message and/or telephone call), the receiving party can review the Caller ID Message (and/or other information transmitted with the Caller ID Messaging Signal) and decide whether to answer the call to have a conversation with the calling party.



FIG. 8 is a schematic of a Caller ID messaging communications system 800 similar to the Caller ID messaging communications system 700 disclosed in FIG. 7. However, Caller ID messaging communications system 800 illustrates alternate calling party communications devices 810 that include a Personal Digital Assistant (PDA) 811, an IP phone 812, a modem 813, an interactive pager 814, a global positioning system (GPS) 815, an MP3 player 816, a digital signal processor (DSP) 817, and an interactive television 818. Regardless of the calling party's communications device (reference numerals 110 and 811-818) used to communicate the Caller ID Messaging Signal, this information may need to be formatted accordingly for the receiving party's communications device (including audio, text (e.g., ASCII), video, other digital formats, and combination thereof). Accordingly, the Comm Device Interface 250 of the Caller ID Messaging Device 200, the Caller ID Messaging DataServer 718 (via the Caller ID Messaging Profile), and/or the gateway 770 of the data network 760 has the intelligence for appropriate formatting of the Caller ID Messaging Signal for transmission to the receiving party's communications device. For example, if the calling party's communications device uses the Wireless Application Protocol (WAP) technique, then the Caller ID Messaging Signal is formatted using the Wireless Mark-up Language (WML) and must be configured for Caller ID standards known in the art. The Wireless Mark-up Language (WML) and the WAP technique are known and will not be further described. This is a description of a solution for a specific wireless protocol, such as WAP. This solution may be clearly extended to other wireless protocol, such as i-mode, VoiceXML (Voice eXtensible Markup Language), Dual Tone Multi-Frequency (DTMF), and other signaling means. Alternatively, the Caller ID Messaging Signal may be formatted and/or otherwise configured for presentation by an application and/or componentry of the receiving party's communications device 130.



FIG. 9 is a schematic of a Caller ID messaging communications system 900 similar to the Caller ID messaging communications systems 700 and 800 disclosed in FIGS. 7-8. However, Caller ID messaging communications system 900 illustrates the modem 813 connected to a networked personal computer 910 having a Caller ID Messaging Program Interface 905 as well as calling party's communications device 110 and Caller ID Messaging Device 200. The customer and/or the user interacts with the Caller ID Messaging Program Interface 905 and with Intranet 716 to access and login to the Caller ID Messaging DataServer 718 to establish a Caller ID Messaging Profile in the database 719. Alternatively, an administrator of the telecommunications network 710 could similarly use another personal computer (not shown) and/or alternate workstation (not shown) networked with the Intranet 716 to access, add, delete, store, modify, and manage the database 719 of one or more Caller ID Messaging Profiles. The Caller ID Messaging Profiles control access, sharing, notification, routing, security, transactions, troubleshooting, management, and/or additional processing of Caller ID Messaging Signals exchanged to/from telecommunications network customers, users, and non-customers. More specifically, the Caller ID Messaging Profiles establish preferences for processing the Caller ID Messaging Signal including (1) archiving the Caller ID Messaging Signal to a storage device associated with the telecommunications service provider (so that a database of Caller ID Messaging Signals including Caller ID Messages and destinations communications addresses are stored), (2) encrypting the Caller ID Messaging Signal (or a portion of the Caller ID Messaging Signal) so that only the receiving party's communications device can decipher the Caller ID Message, (3) copying the Caller ID Messaging Signal (e.g., copying the Caller ID Messaging Signal from/to the Caller ID Messaging Device 200), and (4) associating the Caller ID Messaging Signal with a variety of fields, files, and/or other data for Caller ID Messaging Services, such as, for example login information associated with the customer, user, and/or administrator, password, telephone number(s) or Service Node(s) of the customer (this may include a plurality of addresses that are associated with a Service Node or other switch serving the calling party's communications device 110), TCP/IP address of the customer, email address of the customer, profile of the calling party's communications device (shown as reference numerals 110, 811-818 and 910 in FIGS. 1-9) associated with the incoming Caller ID Messaging Signal (e.g., presentation formats of various communications devices), a time or date identifier (e.g., day of week or calendar date), other information associated with the incoming line identification (ICLID) communications signal, size and content of Caller ID Messaging Signal, reply(s), delivery failure notification(s), display and/or presentation data associated with a GUI (e.g., color, font, placement of telecommunications network Management Module on screen, etc.), telecommunications network defaults. Typically, the Caller ID Messaging Profile includes data for (1) the caller identification message, (2) the identifier of the calling party (e.g., a name of the calling party), (3) the identifier of the originating communications address (e.g., a phone number of the calling party's telephone), (4) caller identification messaging services associated with at least one of the calling party and the originating address, (5) the identifier of the destinations communications address (e.g., a telephone number of the receiving party), (6) an identifier of a receiving party's communications device (e.g., a cellular phone), (7) caller identification messaging services associated with at least one of the receiving party and the destinations communications address, and (8) caller identification messaging default service parameters (e.g., always format the caller identification message as text). The data of the Caller ID Messaging Services provide instructions for (1) billing for communication of caller identification messaging signals over the communications network, (2) parameters that enable caller identification messaging including times of day and days of week, (3) parameter that disable caller identification messaging including times of day and days of week, (4) parameters to block caller identification messaging, (5) identification and authentication parameters, (6) parameters to bypass the disable parameters, (7) memory services for data stored with caller identification messaging signals, and/or (8) configuration and formatting preferences for each calling party's communications device communicating with the network. In addition, the data for the Caller ID Messaging Services may include instructions for troubleshooting problems including error messages. Thus, Caller ID Messaging DataServer 718 functions as a computer server, database, and processor that is dedicated to managing Caller ID Messaging Services including communications of Caller ID Messaging Signals over the telecommunications network 710 to other connected networks (e.g., data network 760) and/or connected communications devices (e.g., receiving party's communications device 130).


The telecommunications network 710 may include wired, optical, and/or wireless elements and may further include private network elements, such as private branch exchanges (PBXs), and/or other elements (not shown). The telecommunications network 710 includes Advanced Intelligent Network (AIN) componentry controlling many features of the network. The telecommunications network 710 and/or each of the switches 705, 720 could also include a packet-based “soft switch” that uses software control to provide voice, video, and/or data services by dynamically changing its connection data rates and protocols types. If the telecommunications network 710 and/or one of the switches 705, 720 should include a softswitch, the AIN componentry is replaced by an application server that interfaces with the softswitch via a packet protocol, such as Session Initiation Protocol (SIP). The means of communicating the Caller ID Messaging Signal between or among the calling party's communications device 110, the Caller ID Messaging Device 200, the switches 705, 720, the telecommunications network 710 including AIN componentry, the data network 760 including the gateway 770, and the receiving party's communications device 130 include a variety of means, including optical transmission of data (e.g., any medium capable of optically transmitting the data), wireless transmission of data (e.g., wireless communications of the data using any portion of the electromagnetic spectrum), and/or fixed-wire transmission of data (e.g., any medium capable of transmitting electrons along a conductor). Fiber optic technologies, spectrum multiplexing (such as Dense Wave Division Multiplexing), Ethernet and Gigabit Ethernet services, Infrared, the family of IEEE 802 standards, and Digital Subscriber Lines (DSL) are just some examples of the transmission means. The signaling between the calling party's communications device 110, the Caller ID Messaging Device 200, the switches 705, 720, the telecommunications network 710 including AIN componentry, the data network 760 including the gateway 770, and the receiving party's communications device 130, however, are well understood in by those of ordinary skill the art and will not be further described. Further, those of ordinary skill in the art will be able to apply the principles of this invention to their own network configurations which may differ substantially from the communications system(s) shown in the figures.


Referring now to FIG. 10, another Caller ID messaging communications system 1000 similar to the Caller ID messaging communications system 100 of FIG. 1 is shown; however, Caller ID messaging communications system 1000 includes the receiving party communications device also having the Caller ID Messaging Device 200. Thus, the calling party communications device 110 and the receiving party communications device 130 each include and/or are coupled with specialized hardware and equipment (i.e., Caller ID Messaging Device 200) to engage in Caller ID messaging. For example, FIG. 11 illustrates the Caller ID Messaging Device 200 of the receiving party presenting the incoming Caller ID Messaging Signal (via display 300). The Caller ID Messaging Device 200 displays the communications address 1102 (e.g., telephone number) associated with the calling party communications device 110, a name and/or identifier of the calling party communications address 1104, a name and/or identifier of the calling party 1106, and the Caller ID Message 1110. While the Caller ID Message 1110 shown in FIG. 11 complies with conventional formatting of Caller ID information (i.e., two lines, each with approximately fifteen characters—Line 1: “CANCEL DINNER”, Line 2: “WORKING LATE”), the Caller ID Messaging Device 200 is enabled to display a Caller ID Message having the size of less than or equal to 255 bytes, or alternatively, a Caller ID Message that is transmitted in less than or equal to four (4) seconds. Thus, the display screen 300 is configured to have a display of at least three (3) lines by thirty (30) characters and/or to have a display capable of presenting other visual data (e.g., a picture, a map, etc.).


As shown in FIG. 12, the receiving party uses Caller ID Messaging Device 200 to respond to Caller ID Message 1110. To initiate the response, the receiving party punches or presses the “Compose/Respond” button 340 that brings up a response GUI 1210 for the receiving party to select and/or input a response Caller ID Message. The user may select to (1) input a new response or (2) to select a response from memory. For example, if the user uses the right arrow 335 (or left arrow 330) to move pointer 440 on “Input A New Response” and then presses the “Enter” button 349, an Input Response GUI 1310 of FIG. 13 is displayed and the receiving party can use the stylus 355 and/or keyboard 350 to compose the response Caller ID Message. When the receiving party has finished inputting the response Caller ID Message, the receiving party presses the “Send” button 342 and the Caller ID Messaging Device 200 automatically transmits the response Caller ID Messaging Signal with the response Caller ID Message through telecommunications network 710 and/or data network 760 to the calling party communications device 110 for interactive Caller ID Messaging. If, however, the receiving party uses the right arrow 335 to move the pointer 440 on “Select A Response From Memory” and then presses “Enter” button 349, a Select Response GUI (not shown) is displayed with a menu for navigating stored Caller ID Messages (such as, for example, doodles drawn by a user, Caller ID Messages associated with the calling party or receiving party, an alphabetical or numeric listing of Caller ID Messages, search options for finding a stored Caller ID Message, frequently sent Caller ID Messages, and so on) and the receiving party selects the Caller ID Message and presses the “Send” button 342 to transmit the response Caller ID Message. The stored Caller ID Messages may be stored by local memory device 216, by Caller ID Messaging DataServer 718 (via a Caller ID Messaging Profile associated with the receiving party and/or the calling party), or by another peripheral storage device (not shown).


Typically, the original Caller ID Messaging Signal is transmitted similar to Caller ID (e.g., ICLID signals for Caller ID and Caller ID Call Waiting are transmitted with an incoming call). Similarly, response and/or interactive Caller ID messaging (e.g., the calling party responds to the response Caller ID Message) may be communicated with an incoming communications signal. However, alternate embodiments of this invention provide that the response and/or interactive Caller ID messaging is transmitted via an established connection between the calling party communications device 110 (and/or caller id messaging device 200) and the receiving party communications device 130 (and/or caller id messaging device 200 such that a data burst is transmitted and/or received during an active connection (e.g., during a conversation between the calling party and the receiving party).


As shown in FIG. 14, the receiving party (and/or a calling party) uses a “Forward” button 1410 to forward the Caller ID Message (original Caller ID Message sent from calling party, response Caller ID Message, interactive Caller ID Messages, and/or a stored Caller ID Message). For example, if the receiving party receives the incoming Caller ID Message 1110 and wants to forward the Caller ID Message 1110, the receiving party presses the “Forward” button 1410 that brings up a Forwarding Caller ID Messaging GUI 1420 with an identifier of the Caller ID Message to forward (shown as “Forwarding Caller ID Messaging #10 from Rob in FIG. 14”). Thereafter, the receiving party selects a communications address similar to the methods and systems described in FIG. 4.



FIG. 15 illustrates the Caller ID Messaging communications system 1500 similar to the Caller ID Messaging communications system 700 of FIG. 7; however, FIG. 15 further includes one or more third party's communications devices 1530 including a Personal Digital Assistant (PDA) 1531, an IP phone 1532, a modem 1533, an interactive pager 1534, a global positioning system (GPS) 1535, an MP3 player 1536, a digital signal processor (DSP) 1537, an interactive television 1538, a POTS telephone 1539, and a personal computer 1540. One or more of the third party's communications devices 1530 receives the forwarded Caller ID Message similar to the systems and methods described above. In alternate embodiments (not shown), one or more of the third party's communications device 1530 may include and/or be coupled with a Caller ID Messaging Device 200 and use the Caller ID Messaging Device 200 to engage in interactive Caller ID Messaging conferencing (e.g., more than two parties engaged in Caller ID messaging). Still further, the calling party, the receiving party, and the third party could communicate the Caller ID Messaging Signal, the response Caller ID Messaging Signal, and a third party initiated caller identification messaging signal during the voice connection of the calling party and the receiving party.


According to an embodiment, a third party sponsor (e.g., an advertiser, marketing company, family member) could provide a third party sponsored access address (e.g., an 800 number, IP address, etc.) that allows the calling party to establish the communications connection with the receiving party when the calling party (and/or the receiving party) agrees to receive and/or respond to a third party caller identification messaging signal during the voice connection with the receiving party and the third party is billed for the communications connection of the calling party and the receiving party. Thus, the calling party is able to engage in free or reduced rate communications with the receiving party in exchange for viewing, listening, playing, and/or responding to the third party caller identification message. Typically, the calling party calls the third party sponsored access address, inputs the telephone number and/or destination communications address of the receiving party's communications device, inputs and/or confirms the communications address of the calling party's communications device for the transmission of third party caller identification messaging and thereby agrees to receive and/or respond to the caller identification messages. Thereafter, the third party communications sponsor established the communications connection via the communications network between the calling party's communications device and the receiving party's communications device (similar to the connection established when the calling party uses a calling card access number to place a long distance call to the receiving party). The third party sponsor then initiates transmission of the third party sponsored caller identification messaging signals to the calling party's communications device (and/or receiving party's communications device), and thus, the third party sponsor does not need to maintain a voice connection with either the calling party's communications device nor the receiving party's communications device. Rather, the third party sponsor may elect to maintain an alternate communications connection such that the third party maintains a dynamic caller identification messaging communications connection such that only the third party caller identification messaging signals are transmitted to the calling party's communications device and/or the receiving party's communications device. Alternatively, after the communications connection between the calling party and the receiving party, the third party is released from the communications connections, and, thereafter establishes a new communications connection each time the third party caller identification messaging signal is transmitted to the calling party and/or the receiving party (similar to communications of Caller ID Call Waiting signals that are sent when the calling party and the receiving party are engaged in a voice connection). Finally, the third party sponsor may limit the duration of the phone conversation, such as, only agreeing to pay for a set period of time (e.g., 10 minutes), to pay for the communications connection so long as the calling party continues to respond to third party caller identification messages, to pay for the communications connection if the receiving party also agrees to receive and respond to the third party caller identification messages, and other billing arrangements.


In an alternate embodiment, this invention includes methods and systems for Caller ID Messaging according to the systems disclosed in FIGS. 16-17. FIG. 16 illustrates a Caller ID Messaging Communications system 1600 that includes the calling party communications device 110 and the receiving party device 130 communicating with the communications network 120. Neither the calling party communications device 110 nor the receiving party communications device 130 integrate and/or are coupled with the Caller ID Messaging Device. Rather, the calling party makes use of an access number of the telecommunications network (shown as reference numeral 710 in FIG. 17) to compose, generate, transmit, and/or otherwise manage Caller ID Messaging Signals and Caller ID messaging services. According to FIG. 17, the calling party uses calling party communications device 110 to dial an access number of the telecommunications network 710 for Caller ID messaging (similar to dialing an 800 calling card number). Once the incoming communication from the calling party communications device 110 is connected with the access number, the telecommunications network 710 decodes the incoming communications signal, prompts the calling party for authorization and/or identification (e.g., a pin number associated with a billing number, password, and/or other verification information), associates one or more Caller ID Messaging profiles with the decoded incoming communications signal and/or inputted calling party identification, and presents a menu of options for the calling party to select in order to access stored Caller ID Messaging Signals, compose and/or generate a new Caller ID Messaging Signals including inputting one or more destination communications addresses, and/or manage Caller ID Service. Thereafter, the telecommunications network 710 routes the Caller ID Messaging Signal to one or more receiving party communications devices 1710 similar to the systems and methods described above.


Moreover, the Caller ID Messaging menu presented by telecommunications network 710 may be programmed over a variety of mediums, such as, for example, a voice-activated and/or Dual Tone Multi-Frequency (DTMF) menu prompt. The calling party, for example, might select to access stored Caller ID Messaging Signals by entering a “1” on a touch-tone keypad or by speaking into a receiving audio subsystem and stating the word “one.” This entry would then prompt the calling party through choices such as accessing recently sent Caller ID Messaging Signals, alphanumeric listings of each receiving party, and so on. After making a selection, the telecommunications network 710 retrieves the stored Caller ID Messaging Signal from the database 719. In addition, the calling party might enter a code (e.g., “*99”) in order to automatically block any exchange of Caller ID Messaging Signals. Similarly the calling party could unblock and allow the exchange of Caller ID messaging by entering another code.



FIGS. 18-20 are flowcharts showing processes of providing the Caller ID Messaging Services according to embodiments of this invention. While the processes in FIGS. 18-20 are shown in series, these processes may occur in different orders and/or at simultaneous times as one of ordinary skill in the art will understand.


A calling party uses a Caller ID Messaging Program (such as reference numeral 214 of FIG. 2) associated with the calling party and/or calling party's communications device to compose and/or to select a Caller ID Message [block 1800] and to input and/or select a destinations communications address (and/or a receiving party that has an associated destinations communications address of the receiving party communications device) [block 1810] for a Caller ID Messaging Signal. Thereafter, the calling party initiates routing of the Caller ID Messaging Signal (such as by pressing the “Send” button 342 of Caller ID Messaging Device 200 disclosed above) and the signal is transmitted to a telecommunications network [block 1820]. The telecommunications network detects and decodes the incoming communications signal (e.g., ICLID) and/or Caller ID Messaging Signal [block 1830] and determines if the receiving party's communications device supports enhanced Caller ID Messaging (e.g., presentation capabilities of the receiving party's communications device, such as whether the receiving party's communications device includes componentry to present more than two lines of text, each line with fifteen characters) [block 1840]. If yes, then the telecommunications network establishes a connection (or alternatively sends a data burst of the Caller ID Messaging Signal) [block 1850] and communicates the Caller ID Messaging Signal to the receiving party communications device [block 1900]. After the Caller ID Message is presented by the receiving party communication device and/or Caller ID Messaging Device, the receiving party decides whether to send a response Caller ID Message [block 1910]. If yes, then the receiving party uses a Caller ID Messaging profile stored by the telecommunications network, the incoming Caller ID Messaging Signal, and/or a Caller ID Messaging Program of the receiving party communications device and/or the receiving party's Caller ID Messaging Device to prepare the response Caller ID Message [block 1920]. The response Caller ID Message is transmitted with a response Caller ID Messaging Signal to the telecommunications network, and the telecommunications network establishes a connection to the address of the calling party communications device [block 1940] and communicates the response Caller ID Messaging Signal [block 1950]. Alternatively, the telecommunications network may use an established connection (such as when the receiving party and calling party are also engaged in a voice connection when the response Caller ID Messaging Signal is sent) to transmit the response Caller ID Messaging Signal. If the receiving party does not want to transmit a response Caller ID Message, then the Caller ID Messaging ends. Although not shown, the receiving party could also elect to forward the incoming or a stored Caller ID Messaging Signal to a third party.


Referring back to “Block 1840,” if the receiving party communications device does not support enhanced Caller ID Messaging, then the telecommunications network determines whether the receiving party (and/or receiving party's communications device) blocks or prevents incoming Caller ID messaging [block 2000]. If yes, then the telecommunications network advises the calling party that the receiving party does not accept Caller ID messaging [block 2010] and determines whether the calling party wants to establish an alternate communication connection such as a voice connection (if the Caller ID Messaging Signal is just transmitted as a data transmission to the Caller ID Messaging Device) [block 2020]. If yes, then the telecommunications network establishes the alternate communications connection [block 2030]. However, if the calling party does not want to establish alternate communications, then the communication is terminated [block 2040]. Referring back to “Block 2000,” if the receiving party and/or the receiving party's communications device does not block Caller ID messaging, then the telecommunications network supplants the ICLID signal with the Caller ID message of the Caller ID messaging signal [block 2050], establishes a connection to the address of the receiving party's communications device [block 2060], and communicates the Caller ID message to the receiving party's communications device [block 2070].


While several exemplary implementations of embodiments of this invention are described herein, various modifications and alternate embodiments will occur to those of ordinary skill in the art. For example, the next generation “softswitch” simply replaces the SCP with an “application server.” This application server is a conventional computer server that also includes triggers for telecommunications services so that “new entrants” into telecommunications services (e.g., new telecommunications service providers) don't have to purchase an expensive SSP and/or SCP to process telephone calls. This next-generation packet network represents an alternative operating environment for the Caller ID Messaging systems, methods, programs, and apparatuses. Here the telecommunications switch includes a packet-based “softswitch.” This “softswitch” uses software control to provide voice, data, and video services by dynamically changing its connection data rates and protocols types. An application server interfaces with the “softswitch” via a packet protocol, such as Session Initiation Protocol (SIP). This application server includes voice service protocols, triggers, and operations that allow the PSTN and the data network (e.g., the world wide electronic communications network) to interoperate. Accordingly, this invention is intended to include those other variations, modifications, and alternate embodiments that adhere to the spirit and scope of this invention.

Claims
  • 1. A communications system for providing caller identification messaging, the system comprising: a communications server communicating with a communications network for detecting an incoming commutations signal on a communications link from a calling party communications device to a caller identification messaging access address;a caller identification messaging application communicating with at least one of the communications network, the calling party communications device, and a caller identification messaging dataserver, the caller identification messaging application generating at least one of a caller identification message and a caller identification messaging signal, the caller identification messaging signal comprising the caller identification message and at least one of (i) an identifier of a calling party, (ii) an identifier of a destination communications address, and (iii) an identifier of an originating communications address; andthe caller identification messaging dataserver for storing a caller identification messaging profile, the caller identification messaging profile comprising at least one of (i) the caller identification message, (ii) the identifier of the calling party, (iii) the identifier of the originating communications address, (iv) caller identification messaging services associated with at least one of the calling party and the originating address, (v) the identifier of the destinations communications address, (vi) an identifier of a receiving party communications device, (vii) caller identification messaging services associated with at least one of the receiving party and the destinations communications address, and (viii) caller identification messaging default service parameters,the caller identification messaging application determining that the receiving party has requested a response caller identification message, the caller identification messaging application accessing the caller identification messaging dataserver to access the caller identification messaging profile in creation of response caller identification message from the receiving party to the calling party.
  • 2. The system of claim 1, further comprising: a second communications server for communicating at least one of the caller identification message and the caller identification messaging signal to a destinations communications address, the second communications server in communication with the receiving party communications device on a communications link.
  • 3. The system of claim 1, wherein the communications network comprises at least one of a public switched telephone network and a mobile switching telephone communications network.
  • 4. The system of claim 1, wherein the calling party communications device comprises at least one of the following: a caller identification messaging device,a POTS phone,a wireless communications device,a mobile phone,a wireless phone,a WAP phone,a satellite phonea computer,a modem,a pager,a digital music device,a digital recording device,a personal digital assistant,an interactive television,a digital signal processor, anda Global Positioning System device.
  • 5. The system of claim 1, wherein the receiving party communications device comprises at least one of the following: a caller identification device,a caller identification messaging device,a POTS phone,a wireless communications device,a mobile phone,a wireless phone,a WAP phone,a satellite phonea computer,a modem,a pager,a digital music device,a digital recording device,a personal digital assistant,an interactive television,a digital signal processor, anda Global Positioning System device.
  • 6. The system of claim 1, the communications network further comprising a world wide electronic data communications network having a caller identification messaging interface via at least one of an internet, an intranet, or an extranet.
  • 7. The system of claim 1, the communications network further comprising an audio caller identification messaging application, the audio caller identification messaging application operable to configure a text format of the caller identification message to an audio format of the caller identification message.
  • 8. The system of claim 7, wherein the audio presentation application includes a text-to-speech application.
  • 9. The system of claim 1, the communications network further including a speech-to-text caller identification messaging application, the speech-to-text caller identification messaging application operable to configure an audio format of the caller identification message to a text format of the caller identification message.
  • 10. The system of claim 1, the receiving party communications device comprising a caller identification messaging device, the caller identification messaging device transmitting a response caller identification messaging signal comprising at least one of (i) a response caller identification message, (ii) an identifier of a responding party, (iii) an identifier of a response communications address, and (iv) an identifier of the second communications device.
  • 11. The system of claim 1, the calling party caller identification messaging services providing instructions for at least one of (i) billing for communication of caller identification messaging signals over the communications network, (ii) a parameter that enables caller identification messaging including times of day and days of week, (iii) a parameter that disables caller identification messaging including times of day and days of week, (iv) a parameter to block caller identification messaging, (v) an identification and authentication parameter, (vi) a parameter to bypass the disable parameter, (vii) memory services for data stored with caller identification messaging signals, and (viii) configuration and formatting preferences for each calling party communications device communicating with the network.
  • 12. The system of claim 1, the receiving party caller identification messaging services providing instructions for at least one of (i) billing for communication of caller identification messaging signals over the communications network, (ii) a parameter that enables caller identification messaging including times of day and days of week, (iii) a parameter that disables caller identification messaging including times of day and days of week, (iv) a parameter to block caller identification messaging, (v) a parameter for identification and authentication, (vi) a parameter to bypass the disable parameter, (vii) a memory service parameter for data stored with caller identification messaging signals, and (viii) a configuration and formatting preference for each receiving party communications device communicating with the network.
  • 13. A method for caller identification messaging, comprising: processing a communications signal from a calling party communications device to a caller identification messaging access address;associating an incoming line identification (ICLID) signal with the communications signal;associating a caller identification messaging profile with the ICLID signal, the caller identification profile comprising at least one of (i) a caller identification message, (ii) an identifier of the calling party, (iii) an identifier of the originating communications address, (iv) caller identification messaging services associated with at least one of the calling party arid the originating address, (v) an identifier of the destinations communications address, (vi) an identifier of a receiving party communications device, (vii) caller identification messaging services associated with at least one of the receiving party and the destinations communications address, and (viii) caller identification messaging default service parameters;generating a caller identification messaging signal using at least one of the caller identification messaging profile and or a caller identification messaging instruction supplied by the calling party, the caller identification messaging signal comprising a caller identification message and at least one of (i) the identifier of a calling party, (ii) the identifier of a destination communications address, and (iii) the identifier of an originating communications address; anddetermining that the receiving party has requested a response caller identification message, accessing the caller identification messaging profile in creation of response caller identification message from the receiving party to the calling party.
  • 14. The method of claim 13, further comprising: transmitting the caller identification message to the destinations communications address.
  • 15. The method of claim 13, further comprising: presenting the caller identification message via the receiving party communications device.
  • 16. The method of claim 13, further comprising: transmitting the caller identification messaging signal to the destinations communications address.
  • 17. A communications method, comprising: receiving communications signals from a calling party communications device to a communications network;using the communication signals to generate a caller identification messaging signal, the caller identification messaging signal comprising a caller identification message and at least one of (i) an identifier of a calling party, (ii) an identifier of a destination communications address, and (iii) an identifier of the calling party communications device;communicating at least one of die caller identification message and the caller identification messaging signal to the destinations communications address; andquerying a database for at least one of (i) acceptance of the caller identification message and (ii) presentation capabilities associated with at least one of the destination communications address and a destination communications device,if transmission of the caller identification message is initiated, then formatting the caller identification message for presentation to the destination communications address, and transmitting the caller identification message to the destination communications address,if transmission of the caller identification message is not initiated, then retrieving a caller identification messaging delivery failure notification and transmitting the message delivery failure notification to a communications address of the calling party communications device,determining that the receiving party has requested a response caller identification message, accessing the caller identification messaging profile in creation of response caller identification message from the receiving party to the calling party.
US Referenced Citations (461)
Number Name Date Kind
4266098 Novak May 1981 A
4268722 Little et al. May 1981 A
4277649 Sheinbein Jul 1981 A
4582956 Doughty Apr 1986 A
4649533 Chorley et al. Mar 1987 A
4663777 Szeto May 1987 A
4698839 DeVaney et al. Oct 1987 A
4791664 Lutz et al. Dec 1988 A
4797911 Szlam et al. Jan 1989 A
4802202 Takahashi et al. Jan 1989 A
4817133 Takahashi et al. Mar 1989 A
4823304 Frantz et al. Apr 1989 A
4845743 Lutz Jul 1989 A
4850013 Rose Jul 1989 A
4995075 Angiolillo-Bent Feb 1991 A
5029196 Morganstein Jul 1991 A
5109405 Morganstein Apr 1992 A
5121423 Morihiro et al. Jun 1992 A
5151929 Wolf Sep 1992 A
5157712 Wallen, Jr. Oct 1992 A
5161181 Zwick Nov 1992 A
5200994 Sasano et al. Apr 1993 A
5206901 Harlow Apr 1993 A
D338889 Fuqua et al. Aug 1993 S
5260987 Mauger Nov 1993 A
5263084 Chaput et al. Nov 1993 A
5265145 Lim Nov 1993 A
5274699 Ranz Dec 1993 A
5278894 Shaw Jan 1994 A
5289542 Kessler Feb 1994 A
5315650 Smith et al. May 1994 A
5333152 Wilber Jul 1994 A
5338889 Vora et al. Aug 1994 A
5341411 Hashimoto Aug 1994 A
5347574 Morganstein Sep 1994 A
5361295 Solomon et al. Nov 1994 A
5383466 Partika Jan 1995 A
5386460 Boakes et al. Jan 1995 A
5388150 Schneyer et al. Feb 1995 A
5413605 Ashby et al. May 1995 A
5420910 Rudokas et al. May 1995 A
5420914 Blumhardt May 1995 A
5420920 Capper et al. May 1995 A
5425076 Knippelmier Jun 1995 A
5425089 Chan et al. Jun 1995 A
5430719 Weisser, Jr. Jul 1995 A
5446785 Hirai Aug 1995 A
5452089 Bushman Sep 1995 A
5452346 Miyamoto Sep 1995 A
5459779 Backaus et al. Oct 1995 A
5466785 De Framond Nov 1995 A
5467388 Redd, Jr. et al. Nov 1995 A
5475748 Jones Dec 1995 A
5481594 Shen et al. Jan 1996 A
5481599 MacAllister et al. Jan 1996 A
5481602 Griffiths et al. Jan 1996 A
5490205 Kondo et al. Feb 1996 A
5497414 Bartholomew Mar 1996 A
5502762 Andrew Mar 1996 A
5506893 Buscher et al. Apr 1996 A
5511111 Serbetcioglu et al. Apr 1996 A
5530741 Rubin Jun 1996 A
5533106 Blumhardt Jul 1996 A
5535265 Suwandhaputra Jul 1996 A
5539809 Mayer Jul 1996 A
5546447 Skarbo et al. Aug 1996 A
5548447 Skarbo et al. Aug 1996 A
5550900 Ensor et al. Aug 1996 A
5550905 Silverman Aug 1996 A
5563935 Small Oct 1996 A
5563936 Washington Oct 1996 A
5602908 Fan Feb 1997 A
5608788 Demlow et al. Mar 1997 A
5619561 Reese Apr 1997 A
5631950 Brown May 1997 A
5636269 Eisdorfer Jun 1997 A
5644629 Chow Jul 1997 A
5646979 Knuth Jul 1997 A
5657372 Ahlberg et al. Aug 1997 A
D383466 Burrell et al. Sep 1997 S
5668852 Holmes Sep 1997 A
5696809 Voit Dec 1997 A
5696815 Smyk Dec 1997 A
5699523 Li et al. Dec 1997 A
5701301 Weisser, Jr. Dec 1997 A
5703934 Zicker et al. Dec 1997 A
H01714 Partridge, III Mar 1998 H
5724412 Srinivasan Mar 1998 A
5734706 Windsor et al. Mar 1998 A
5754635 Kim May 1998 A
5754636 Bayless et al. May 1998 A
5764775 Adamson et al. Jun 1998 A
5771281 Batten, Jr. Jun 1998 A
5771283 Chang et al. Jun 1998 A
5781621 Lim et al. Jul 1998 A
5784444 Snyder et al. Jul 1998 A
5796806 Birckbichler Aug 1998 A
5799072 Vulcan Aug 1998 A
5802160 Kugell Sep 1998 A
5802251 Cohen et al. Sep 1998 A
5805587 Norris et al. Sep 1998 A
5805682 Voit et al. Sep 1998 A
5805997 Farris Sep 1998 A
5809128 McMullin Sep 1998 A
5812533 Cox et al. Sep 1998 A
5812649 Shen Sep 1998 A
5838774 Weisser, Jr. Nov 1998 A
5841838 Itoh et al. Nov 1998 A
5841850 Fan Nov 1998 A
5848142 Yaker Dec 1998 A
5850435 Devillier Dec 1998 A
5850436 Rosen et al. Dec 1998 A
5857017 Ohi Jan 1999 A
5859903 Lee Jan 1999 A
5872834 Teitelbaum Feb 1999 A
5878036 Spratz et al. Mar 1999 A
5883942 Lim et al. Mar 1999 A
5884144 Chavz et al. Mar 1999 A
5894504 Alfred et al. Apr 1999 A
5901209 Tannenbaum et al. May 1999 A
5901212 True et al. May 1999 A
5903636 Malik May 1999 A
5905794 Gunn et al. May 1999 A
5907596 Karnowski May 1999 A
5907604 Hsu May 1999 A
5915000 Nguyen et al. Jun 1999 A
5917817 Dunn et al. Jun 1999 A
5923744 Cheng Jul 1999 A
5930701 Skog Jul 1999 A
5940484 DeFazio et al. Aug 1999 A
5946363 Rominger et al. Aug 1999 A
5946636 Uyeno et al. Aug 1999 A
5946684 Lund Aug 1999 A
D413605 Thomas et al. Sep 1999 S
5948040 DeLorme et al. Sep 1999 A
5949865 Fusinato Sep 1999 A
5953399 Farris et al. Sep 1999 A
5953657 Ghisler Sep 1999 A
5963626 Nabkel Oct 1999 A
5969647 Mou et al. Oct 1999 A
5970127 Smith et al. Oct 1999 A
5970128 Kim Oct 1999 A
5974309 Foti Oct 1999 A
5982866 Kowalski Nov 1999 A
5991377 Malik Nov 1999 A
5999207 Rodriguez et al. Dec 1999 A
5999599 Shaffer et al. Dec 1999 A
5999613 Nabkel et al. Dec 1999 A
6006087 Amin Dec 1999 A
6009321 Wang et al. Dec 1999 A
6014559 Amin Jan 2000 A
6016512 Huitema Jan 2000 A
6021188 Meg Feb 2000 A
6021427 Spagna et al. Feb 2000 A
6031899 Wu Feb 2000 A
6044148 Bleile Mar 2000 A
6049291 Kikinis Apr 2000 A
6058171 Hoopes May 2000 A
6061434 Corbett May 2000 A
6061566 Friman May 2000 A
6064876 Ishida May 2000 A
6065844 Chen May 2000 A
6072859 King Jun 2000 A
6078581 Shtivelman et al. Jun 2000 A
6091947 Sumner Jul 2000 A
6094478 Shepherd et al. Jul 2000 A
6094573 Heinonen et al. Jul 2000 A
6094574 Vance et al. Jul 2000 A
6094575 Anderson et al. Jul 2000 A
6101246 Heinmiller et al. Aug 2000 A
6104784 Robbins Aug 2000 A
6104800 Benson Aug 2000 A
6108630 Kuechler et al. Aug 2000 A
6111939 Brabanec Aug 2000 A
6134235 Goldman et al. Oct 2000 A
6134311 Ekstrom Oct 2000 A
6137870 Scherer Oct 2000 A
6137871 Maier et al. Oct 2000 A
6141341 Jones Oct 2000 A
6141409 Madoch et al. Oct 2000 A
6144644 Bajzath et al. Nov 2000 A
6154531 Clapper Nov 2000 A
6160876 Moss et al. Dec 2000 A
6161021 Akpa Dec 2000 A
6163595 Parker et al. Dec 2000 A
6163691 Buettner et al. Dec 2000 A
6167254 Chavez, Jr. et al. Dec 2000 A
6173049 Malik Jan 2001 B1
6178232 Latter et al. Jan 2001 B1
6181928 Moon Jan 2001 B1
D437879 Weinandt Feb 2001 S
6185289 Hetz et al. Feb 2001 B1
6185426 Alperovich Feb 2001 B1
6192115 Toy et al. Feb 2001 B1
6192116 Mayak Feb 2001 B1
6198480 Cotugno et al. Mar 2001 B1
6198920 Doviak et al. Mar 2001 B1
6202023 Hancock et al. Mar 2001 B1
6219407 Kanevsky et al. Apr 2001 B1
6226367 Smith et al. May 2001 B1
6226369 Lim et al. May 2001 B1
6226399 Robinson May 2001 B1
6230006 Keenan et al. May 2001 B1
6236975 Boe et al. May 2001 B1
6243448 Corbett et al. Jun 2001 B1
6243461 Hwang Jun 2001 B1
6252952 Kung et al. Jun 2001 B1
6256671 Strentzsch et al. Jul 2001 B1
6262987 Mogul Jul 2001 B1
6266399 Weller et al. Jul 2001 B1
6278704 Creamer et al. Aug 2001 B1
6278862 Henderson Aug 2001 B1
6282275 Gurbani et al. Aug 2001 B1
6292479 Bartholomew et al. Sep 2001 B1
6292549 Lung et al. Sep 2001 B1
6295502 Hancock et al. Sep 2001 B1
6301350 Henningson et al. Oct 2001 B1
6304644 Karnowski Oct 2001 B2
6310943 Kowalski Oct 2001 B1
6311057 Barvesten Oct 2001 B1
6317488 DePond et al. Nov 2001 B1
6317781 DeBoor et al. Nov 2001 B1
6324263 Sherwood et al. Nov 2001 B1
6324271 Sawyer et al. Nov 2001 B1
6327347 Gutzmann Dec 2001 B1
6332021 Latter et al. Dec 2001 B2
6333973 Smith et al. Dec 2001 B1
6339639 Henderson Jan 2002 B1
6341161 Latter et al. Jan 2002 B1
6345187 Berthoud et al. Feb 2002 B1
6347136 Horan Feb 2002 B1
6351637 Lee Feb 2002 B1
6353664 Cannon et al. Mar 2002 B1
6361637 Martin et al. Mar 2002 B2
6363411 Dugan et al. Mar 2002 B1
6366661 Devillier et al. Apr 2002 B1
6366772 Arnson Apr 2002 B1
6377807 Iparrea et al. Apr 2002 B1
6377979 Yamashita et al. Apr 2002 B1
6389124 Schnarel et al. May 2002 B1
6400809 Bossemeyer et al. Jun 2002 B1
6400947 Bright et al. Jun 2002 B1
6404868 Beamish et al. Jun 2002 B1
6404875 Malik et al. Jun 2002 B2
6411692 Scherer Jun 2002 B1
6421425 Bossi et al. Jul 2002 B1
6422263 Spicer Jul 2002 B1
6427003 Corbett et al. Jul 2002 B1
6427064 Henderson Jul 2002 B1
6434394 Grundvig et al. Aug 2002 B1
6437879 Temple Aug 2002 B1
6438216 Aktas Aug 2002 B1
6438584 Powers Aug 2002 B1
6442249 Miller, Jr. Aug 2002 B1
6442262 Moss et al. Aug 2002 B1
6442263 Beaton et al. Aug 2002 B1
6445781 Heinmiller et al. Sep 2002 B1
6449351 Moss et al. Sep 2002 B1
6449361 Okuda Sep 2002 B1
6462646 Helferich Oct 2002 B2
6466653 Hamrick et al. Oct 2002 B1
6477246 Dolan et al. Nov 2002 B1
6480589 Lee et al. Nov 2002 B1
6483898 Lew et al. Nov 2002 B2
6493430 Leuca et al. Dec 2002 B2
6493431 Troen-Krasnow et al. Dec 2002 B1
6493437 Olshansky Dec 2002 B1
6493439 Lung et al. Dec 2002 B2
6494953 Hayes et al. Dec 2002 B2
6496569 Pelletier et al. Dec 2002 B2
6496571 Wilson Dec 2002 B1
6496692 Shanahan Dec 2002 B1
6498841 Bull et al. Dec 2002 B2
6507737 Laham et al. Jan 2003 B1
6529500 Pandharipande Mar 2003 B1
6529591 Dosani et al. Mar 2003 B1
6532490 Lewis et al. Mar 2003 B1
6539080 Bruce et al. Mar 2003 B1
6542583 Taylor Apr 2003 B1
6542586 Helstab Apr 2003 B1
6542591 Amro et al. Apr 2003 B1
6542602 Elazar Apr 2003 B1
6542812 Obradovich et al. Apr 2003 B1
6546092 Corbett et al. Apr 2003 B2
6549621 Christie, IV et al. Apr 2003 B1
6553110 Peng Apr 2003 B1
6553221 Nakamura Apr 2003 B2
6556540 Mawhinney et al. Apr 2003 B1
6560317 Quagliana May 2003 B1
6560327 McConnell May 2003 B1
6566995 Furuuchi et al. May 2003 B2
6570971 Latter et al. May 2003 B2
6570974 Gerszberg et al. May 2003 B1
6574319 Latter et al. Jun 2003 B2
6580904 Cox et al. Jun 2003 B2
6584490 Schuster et al. Jun 2003 B1
6587458 Burg et al. Jul 2003 B1
6597905 Hijii Jul 2003 B1
6603840 Fellingham et al. Aug 2003 B2
6608891 Pelletier et al. Aug 2003 B1
6618474 Reese Sep 2003 B1
6625595 Anderson et al. Sep 2003 B1
6631181 Bates et al. Oct 2003 B1
6633633 Bedingfield Oct 2003 B1
6639979 Kim Oct 2003 B1
6650743 Heinmiller et al. Nov 2003 B2
6659597 Murata et al. Dec 2003 B2
6661785 Zhang et al. Dec 2003 B1
6665388 Bedingfield Dec 2003 B2
6683870 Archer Jan 2004 B1
6687341 Koch et al. Feb 2004 B1
6697357 Emerson, III Feb 2004 B2
6701160 Pinder et al. Mar 2004 B1
6718021 Crockett et al. Apr 2004 B2
6721407 Michelena Apr 2004 B1
6724872 Moore et al. Apr 2004 B1
6725872 Kindell et al. Apr 2004 B2
6728355 Kowalski Apr 2004 B2
6728360 Brennan Apr 2004 B1
6728365 Li et al. Apr 2004 B1
6731727 Corbett et al. May 2004 B2
6732188 Flockhart et al. May 2004 B1
6738615 Chow et al. May 2004 B1
6748058 Schwend et al. Jun 2004 B1
6748068 Walsh et al. Jun 2004 B1
6751457 Martin Jun 2004 B1
6757274 Bedingfield et al. Jun 2004 B1
6757740 Parekh et al. Jun 2004 B1
6760413 Cannon et al. Jul 2004 B2
6765998 Bruce et al. Jul 2004 B2
6766003 Moss et al. Jul 2004 B2
6766782 Brown et al. Jul 2004 B1
6768792 Brown et al. Jul 2004 B2
D494953 Leung Aug 2004 S
6771754 Pelletier et al. Aug 2004 B2
6771755 Simpson Aug 2004 B1
6771956 Beeler Aug 2004 B1
6775366 Cobbett et al. Aug 2004 B1
6775540 Iyer Aug 2004 B2
6778524 Augart Aug 2004 B1
6779020 Henrick Aug 2004 B1
6785301 Chapman et al. Aug 2004 B1
6785368 Eason et al. Aug 2004 B1
6785540 Wichelman Aug 2004 B1
6792266 Masuda et al. Sep 2004 B1
6798841 Hansen Sep 2004 B2
6798879 Beham Sep 2004 B1
6807267 Moss et al. Oct 2004 B2
6810077 Dezonno Oct 2004 B1
6810115 Fukuda Oct 2004 B2
6813344 Lemke Nov 2004 B1
6816481 Adams et al. Nov 2004 B1
6818474 Kim et al. Nov 2004 B2
6826271 Kanabar et al. Nov 2004 B1
6830595 Reynolds, III Dec 2004 B2
6831974 Watson et al. Dec 2004 B1
6842512 Pedersen Jan 2005 B2
6845151 Peng Jan 2005 B2
6853710 Harris Feb 2005 B2
6853711 Brisebois et al. Feb 2005 B2
6865266 Peshan Mar 2005 B1
6868155 Cannon et al. Mar 2005 B1
6871076 Samn Mar 2005 B2
6888927 Cruickshank et al. May 2005 B1
6888972 Berg et al. May 2005 B2
6898275 Dolan et al. May 2005 B2
6904276 Freeman et al. Jun 2005 B1
6907034 Begis Jun 2005 B1
6909777 Latter et al. Jun 2005 B2
6914953 Boerstler Jul 2005 B2
6922411 Taylor Jul 2005 B1
6928154 Cheaito et al. Aug 2005 B1
6931007 Jones Aug 2005 B2
6952469 Han Oct 2005 B2
6970546 Kent, Jr. et al. Nov 2005 B2
6977993 Starbuck et al. Dec 2005 B2
6996211 Reynolds et al. Feb 2006 B2
7012999 Ruckart Mar 2006 B2
7016482 Moss et al. Mar 2006 B2
7027408 Nabkel et al. Apr 2006 B2
7076051 Brown et al. Jul 2006 B2
7079837 Sherman et al. Jul 2006 B1
7085358 Ruckart et al. Aug 2006 B2
7097169 Mueller Aug 2006 B2
7103167 Brahm et al. Sep 2006 B2
7103662 Ray et al. Sep 2006 B2
7113577 Cook et al. Sep 2006 B2
7127488 Scott et al. Oct 2006 B1
7139374 Scott et al. Nov 2006 B1
20010005854 Murata et al. Jun 2001 A1
20010044898 Benussi et al. Nov 2001 A1
20020009184 Shnier Jan 2002 A1
20020016748 Emodi Feb 2002 A1
20020041605 Benussi et al. Apr 2002 A1
20020055926 Dan et al. May 2002 A1
20020067816 Bushnell Jun 2002 A1
20020077102 Achuthan et al. Jun 2002 A1
20020082050 Mountney et al. Jun 2002 A1
20020085687 Contractor et al. Jul 2002 A1
20020090933 Rouse et al. Jul 2002 A1
20020094826 Lee Jul 2002 A1
20020118812 Contractor Aug 2002 A1
20020119430 Szynalski Aug 2002 A1
20020120629 Leonard Aug 2002 A1
20020122401 Xiang et al. Sep 2002 A1
20020183098 Lee Dec 2002 A1
20020188443 Reddy et al. Dec 2002 A1
20020191755 Lew Dec 2002 A1
20030007620 Elsey Jan 2003 A1
20030012147 Buckman et al. Jan 2003 A1
20030012353 Tang et al. Jan 2003 A1
20030016143 Ghazarian Jan 2003 A1
20030016800 Fukuda Jan 2003 A1
20030026413 Brandt et al. Feb 2003 A1
20030026416 Fusco Feb 2003 A1
20030032414 Melaku et al. Feb 2003 A1
20030050100 Dent Mar 2003 A1
20030053602 Stuckman et al. Mar 2003 A1
20030063730 Woodring Apr 2003 A1
20030063731 Woodring Apr 2003 A1
20030092384 Ross, III May 2003 A1
20030095650 Mize May 2003 A1
20030112938 Kanakubo et al. Jun 2003 A1
20030119503 Shohara et al. Jun 2003 A1
20030133553 Khakoo Jul 2003 A1
20030133653 De Barros et al. Jul 2003 A1
20030148758 McMullin Aug 2003 A1
20030152207 Ryan Aug 2003 A1
20030172183 Anderson et al. Sep 2003 A1
20030187949 Bhatt Oct 2003 A1
20030196206 Shusman Oct 2003 A1
20030198322 White, Jr. Oct 2003 A1
20030219107 Richardson et al. Nov 2003 A1
20040049545 Wayne Lockridge et al. Mar 2004 A1
20040101118 Powell May 2004 A1
20040101124 Koch et al. May 2004 A1
20040109558 Koch Jun 2004 A1
20040114730 Koch et al. Jun 2004 A1
20040120475 Bauer et al. Jun 2004 A1
20040125929 Pope Jul 2004 A1
20040171370 Natarajan Sep 2004 A1
20040181587 Cao et al. Sep 2004 A1
20040202298 Lopez et al. Oct 2004 A1
20040202299 Schwartz Oct 2004 A1
20040208301 Urban et al. Oct 2004 A1
20040208302 Urban et al. Oct 2004 A1
20040209604 Urban et al. Oct 2004 A1
20040209605 Urban et al. Oct 2004 A1
20040209640 Urban et al. Oct 2004 A1
20040233892 Roberts et al. Nov 2004 A1
20040242212 Bacon et al. Dec 2004 A1
20040248560 Bedingfield et al. Dec 2004 A1
20050073999 Koch Apr 2005 A1
20050100158 Kreiner et al. May 2005 A1
20050107074 Zellner May 2005 A1
20050147228 Perrella et al. Jul 2005 A1
20060002540 Kreiner et al. Jan 2006 A1
20060013375 Smith et al. Jan 2006 A1
20060029209 Moton et al. Feb 2006 A1
20060152207 Riebel et al. Jul 2006 A1
20070064911 Bedingfield, Sr. et al. Mar 2007 A1
Foreign Referenced Citations (6)
Number Date Country
0821511 Jan 1998 EP
2002014945 Feb 2002 KR
9750225 Dec 1997 WO
03030501 Apr 2003 WO
03030502 Apr 2003 WO
WO 03090432 Oct 2003 WO
Related Publications (1)
Number Date Country
20040209604 A1 Oct 2004 US