Source: http://www.google.com/patents/US20050073999?dq=5920316
Timestamp: 2016-05-24 09:16:37
Document Index: 591919329

Matched Legal Cases: ['arty 130', 'arty 140', 'arty 130', 'arty 140', 'arty 140', 'arty 130', 'arty 130', 'arty 140', 'arty 140', 'arty 130', 'arty 130', 'arty 130', 'arty 140', 'arty 130', 'arty 130', 'arty 130', 'arty 130', 'arty 130', 'arty 130', 'arty 130', 'arty 140', 'arty 140', 'arty 140', 'arty 140', 'arty 140', 'arty 130', 'arty 140', 'arty 140', 'arty 140', 'arty 130', 'arty 130', 'arty 140', 'arty 130', 'arty 130', 'arty 140', 'arty 140', 'arty 130', 'arty 140', 'arty 130', 'arty 140', 'arty 130', 'arty 140', 'arty 130', 'arty 140', 'arty 130', 'arty 130', 'arty 140', 'arty 130', 'arty 140', 'arty 140', 'arty 140', 'arty 140', 'arty 130', 'arty 140', 'arty 130', 'arty 130', 'arty 140', 'arty 130', 'arty 130', 'arty 130', 'arty 130', 'arty 130', 'arty 130', 'arty 130', 'arty 130', 'arty 140', 'arty 130', 'arty 140', 'arty 130', 'arty 130', 'arty 130', 'arty 130', 'arty 130', 'arty 130', 'arty 140', 'arty 140', 'arty 130', 'arty 140', 'arty 140', 'arty 130', 'arty 1530', 'arty 1530', 'arty 1530']

Patent US20050073999 - Delivery of profile-based third party content associated with an incoming ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsThe present disclosure provides a system and method for supplying third party information to a receiving party having a device coupled to the Internet. One embodiment of the present disclosure includes a method and apparatus for providing content to the recipient of an incoming phone call as a data message...http://www.google.com/patents/US20050073999?utm_source=gb-gplus-sharePatent US20050073999 - Delivery of profile-based third party content associated with an incoming communicationAdvanced Patent SearchPublication numberUS20050073999 A1Publication typeApplicationApplication numberUS 10/994,596Publication dateApr 7, 2005Filing dateNov 22, 2004Priority dateMay 13, 2002Publication number10994596, 994596, US 2005/0073999 A1, US 2005/073999 A1, US 20050073999 A1, US 20050073999A1, US 2005073999 A1, US 2005073999A1, US-A1-20050073999, US-A1-2005073999, US2005/0073999A1, US2005/073999A1, US20050073999 A1, US20050073999A1, US2005073999 A1, US2005073999A1InventorsRobert KochOriginal AssigneeBellsouth Intellectual Property CorporationExport CitationBiBTeX, EndNote, RefManPatent Citations (99), Referenced by (49), Classifications (27), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetDelivery of profile-based third party content associated with an incoming communication
DETAILED DESCRIPTION [0036] One embodiment, among others, of the present disclosure provides a communication system and method, wherein during the time a caller or calling party is initiating a telephone call to a receiving party, an Internet caller-ID system is activated. The Internet caller-ID system notifies the receiving party of the identification of the calling party by an Internet caller-ID message. The Internet caller-ID message is delivered to an Internet-connected device of the receiving party, while the call is being completed over a telephone network. The telephone network may be a standard PSTN network or could be another telephone network such as voice over Internet protocol (VoIP). A. Architecture [0037] FIG. 1A is a block diagram showing one embodiment of a communication system 100 of the present disclosure. The system 100 includes an Internet caller-ID system 105, a telephone network 110, and the Internet 120. A communication station 130 of a receiving party is connected to the telephone network 110 and has an associated Internet access 160. Correspondingly, a communication station 140 of a calling party is also included in the communication system 100. The communication station 140 is connected to the telephone network 110, and it may have Internet access 144. Note, that although separation is suggested in FIG. 1A, discrete functions of the Internet caller-ID system 105 can be viewed as being performed by devices that are implemented in other elements, such as the telephone network 110 and by devices that are in implemented in the Internet 120, without limitations. Further, the Internet caller-ID system 105 can be implemented in software, firmware, hardware, or a combination thereof. In some implementations, functions are implemented in software or firmware that is stored in a memory as logic that is executed by a suitable instruction execution system. [0038] FIG. 1B is a more detailed diagram of the communication system 100 of FIG. 1. Here, the Internet caller-ID system 105 includes telephone network switch 112, 116, a service control point (SCP) 114, and an Internet caller-ID server 150 with an associated profile database 156. The communication station of a receiving party 130 is shown connected to the telephone network switch 112 through connection 113, which provides access to the telephone network 110. The communication station of the receiving party may also have access to an Internet network 120 through an Internet service provider (ISP) 170. The communication station of a calling party 140 is connected to a telephone network switch 116. [0039] The communication station of the receiving party 130 contains a telephony device connected to the telephone network and an Internet-connected device 132 that is connected to the Internet 120. Possible telephony devices include, among others, a telephone 131A attached to a telephone line from the telephone network or a wireless cellular telephone 1311B communicating to the telephone network through a mobile switching center 180. The Internet-connected device 132 includes a device for communicating on the Internet 120, such as a computer with Internet capabilities. The Internet-connected device 132 may be connected to the Internet 120 by a variety of manners 160. For example, the Internet-connected device 132 may be connected to a standard modem that converts data signals to voice signals and transmits the converted signals over the telephone line to the ISP 170 that has Internet access. In this sort of setup, however, the telephony device 131A and the Internet-connected device 132 would not be able to both be sending communication signals over one telephone line at the same time. Thus, both could not be “always-on,” unless a second telephone line was utilized. [0040] Another manner for the Internet-connected device 132 to be “always-on” connected to the Internet 120 is for the Internet-connected device 132 to be connected to (or include) a DSL modem which allows the Internet-connected device 132 and the telephony device 131A to both communicate over a telephone line at the same time, so that both the telephony device 131A and the Internet-connected device 132 can be “always-on.” Also, the Internet-connected device 132 could be independently connected to the Internet 120 without the use of a telephone network phone line, by using a cable modem or by using satellite communications, as would be understood by one reasonably skilled in the art. Again then, simultaneous communications over the telephony device 131A and the Internet-connected device 132 would be possible. [0041] The communication station of the calling party 140 includes a telephony device coupled to a telephone network switch 116, where the telephony device 141 may be a telephone 141A attached to a telephone line or a wireless cellular phone 141B communicating with the telephone network 110 through a mobile switching center 180. [0042] The telephone network 110 provides telephone communication services and may be, among others, an analog PSTN network or a digital network, such as VoIP. The telephone network 110 features switches, such as switches 112, 116, within the network 110 which connect and route calls between the parties in a telephone conversation, such as between the calling party 140 and the receiving party 130. Also featured in the telephone network 110, a service control point 114 communicates with the switch 112, 116 and other devices, which may be located outside of the telephone network 110, in order to provide requested telephone services. The service control point 114 is a processing element capable of executing service logic. [0043] Specifically, the Internet caller-ID server 150 communicates with the service control point 114 and the Internet 120 in order to provide Internet caller-ID service to users. In order to provide this service, other network devices such as an IP mapping database 175 that is provided by a ISP 170, and a profile database 156 communicating with the Internet caller-ID server 150 are employed. Further, an instant messaging server 195 may be utilized in the communication system 100, where the instant messaging server is connected to the Internet 120. These Internet connections and others throughout the communication system 100 may be protected by a secure IP network 190, as would be understood by one reasonably skilled in the art. B. Operation [0044] The overall operation of the communication system 100 will be described with reference to FIG. 2-11, which depict the functionality of an implementation of the Internet caller-ID system 100. It should be noted that, in some alternative implementations, the functions noted in the various blocks may occur out of the order depicted in the figures. For example, two blocks shown in succession in the figures may, in fact, be executed substantially concurrently or the blocks may be executed in reverse order depending upon the functionality involved. [0045] Referring now to the flowchart of FIG. 2, one embodiment of the present disclosure includes a method 200 for sending and receiving caller-ID messages over the Internet. The process 200 involves a receiving party setting up Internet caller-ID service, as shown in block 210. In block 220, a resource locator is designated by a receiving party 130, a calling party 140, or a third party. In block 230, the calling party 140 places a telephone call to the receiving party 130. Then in block 240, an Internet caller-ID message is constructed, and transmitted to the receiving party 130, as shown in block 250. Accordingly in block 260, the receiving party 130 receives the Internet caller-ID message before or during the completion of the telephone call from the calling party 140 to the receiving party 130. 1. Setup [0046] The operation of the setup process for an implementation of the Internet caller-ID system will be described with reference to FIG. 3. When a user, such as the receiving party 130, desires to register for the Internet caller-ID service, so that it may receive Internet caller-ID messages, the receiving party 130 first creates a profile, as shown in block 211. The creation of the profile can occur during a registration session for the Internet caller-ID service, where the receiving party 130 provides the information contained in the profile during an Internet session, telephone call, or an interview with a person who would later enter the information into the profile. [0047] In block 212, the information gathered for the profile includes the phone number that the communication station of the receiving party 130 receives incoming phone calls at. This phone number may be the phone number of a telephone 131A attached to a phone line, or it may be even a wireless telephone 131B that the receiving party also uses at the communication station 131. Since multiple telephony devices 131 may be used to receive incoming phone calls, multiple phone numbers may be listed in the profile information for the receiving party 130. As depicted in block 212, the profile also contains the receiving party's 130 delivery transport address and any other information that is needed to deliver, over the Internet, the Internet caller-ID message to the Internet-connected device 132 of the receiving party. The delivery transport address is discussed in more detail later. [0048] In block 213, the resource locator is designated. A resource locator is an address location for a document or media that is included in an Internet caller-ID message. Upon receipt, the receiving party's Internet-connected device 132 can retrieve the document specified by the resource locator. Note, the receiving party 130 may receive Internet caller-ID messages regardless of whether the calling party 140 has registered for the Internet caller-ID service or not. However, if the calling party 140 has registered for the Internet caller-ID service, then the calling party 140 may have the capability of designating a resource locator that is contained in the Internet caller-ID message. [0049] For example, this resource locator could be a URL address for a personal web page of the calling party 140 that contains pictures that the calling party 140 wishes for the receiving party 130 to view. Also as part of the calling party's profile, the calling party 140 may provide additional information such as the calling party's name, address, and any other information that can be placed in the Internet caller-ID message. The profiles are stored on a profile database 156. The profile database 156 is connected to or stored as part of the Internet caller-ID server 150, as shown in block 214. [0050] If the calling party 140 does not designate a resource locator, or if the calling party 140 is not registered with the Internet caller-ID service, then a default resource locator, such as the calling party's entry in the white or yellow pages, may be selected as the resource locator. It is also contemplated that the receiving party 130 may designate a resource locator that is contained in the Internet caller-ID message, or a third party who is not a participant in the telephone communication may designate a resource locator. These steps and features are discussed subsequently herein. [0051] The Internet-connected device 132 of the receiving party should have the capability of displaying the Internet message being sent as soon as it arrives. Therefore in block 215, the Internet-connected device 132 is set to be able to receive messages. For example, if the Internet caller-ID message is in the form of a web page, the Internet-connected device 132 should have a web browser installed and active on the Internet-connected device. Likewise, if the message is in the form of an instant message, the Internet-connected device 132 should have an instant message client loaded and actively running on the Internet-connected device 132. 2. Designating the Resource Locator [0052] As previously stated, the resource locator designations are kept in the profile database 156. The profile database 156 may be protected by a secure IP network 190 and could also be contained in the Internet caller-ID server 150. Each resource locator is an address for a resource or document that may be retrieved by the recipient of an Internet caller-ID message and is associated with a phone number or phone numbers of the receiving party or calling party. The resource locator may be specified by a URL address (with # replaced) like http://#.net/me.htm or file://businessfile.txt. Since more than one resource locator could be contained in the message, a party may designate more than one resource locator to be contained in the message, or multiple parties may separately designate resource locators. For example, a receiving party 130, a calling party 140, or a third party may designate a multitude of resource locators that may be contained in the Internet caller-ID message. Therefore in the profile database 156, both the calling party and the receiving party may have resource locators designated that can be placed in the Internet caller-ID message. FIG. 4 is a flowchart depicting an embodiment of the process for designating a resource locator 220 and is discussed further below. a. Receiving Party [0053] As part of registering to the Internet caller-ID service, a receiving party 130 may have the capability of designating resource locators for the caller-ID messages it receives. Therefore, as shown in block 221, the receiving party could provide a resource locator and have this information stored in the receiving party's profile in the profile database 156. For instance, the receiving party may keep a database of customer records that are organized by a customer's phone numbers. Therefore, in the receiving party's profile, the receiving party 130 could designate the parameterized URL http://#.mypage.net/records.html?CN=CallingDN as a resource locator, where the portion of the URL information indicated by “CallingDN” is replaced by the Internet caller-ID server 150 with the calling party's telephone number in the Internet caller-ID message. Accordingly, for each phone number that calls the receiving party, the receiving party will have instant access to a unique business record for that phone number. b. Calling Party [0054] If the calling party 140 has registered for the Internet caller-ID service, he or she may also have the ability to designate resource locators that are contained in the Internet caller-ID messages that are triggered by the calling party's 140 phone calls. For example in block 222, the calling party 140 may provide, as part of its profile to the profile database 156, the resource locator that it would like made available to a receiving party 130 it is calling. The calling party's resource locator designation may point to a multitude of objects, including a personal web page of the calling party 140 or a favorite music file that a receiving party 130 could access by activating the resource locator in the message. [0055] If a receiving party does not have a preexisting web page to specify, then the Internet caller-ID service could provide as part of its profile setup, the option of filling out a form and having a web page automatically created for the user. If the calling party is not registered for Internet caller-ID service or if a resource locator has not been stored in the profile database 156 for a particular telephone number, a resource locator could still be contained in the message that pertains to the calling party 140: As a default, the message could provide a standard link to the receiving party's 130 listing in an on-line telephone directory, such as in the white or yellow pages, where the telephone directory listings are kept in a database in the telephone network 110. c. Third Party [0056] An Internet caller-ID message may additionally contain a resource locator that is designated by a third party, perhaps at the permission of either the receiving party 130 or calling party 140. For example, a receiving party 130 or calling party 140 may separately agree with a third party that that the third party may add a resource locator to an Internet caller-ID message by storing a resource locator associated with the party's phone number in a profile database 156 for one of the parties having a profile, as depicted in block 223. For example, the receiving party 130 may agree to let a third party announce updates or news pertaining to the third party's website through the caller-ID messages that the receiving party 130 receives. Likewise, a third party may want its announcements to go out on the Internet caller-ID messages that a calling party 140 initiates through its outgoing calls. Therefore for this benefit, a third party may reimburse the receiving party 130 or calling party 140 in the form of, possibly, monetary consideration, subsidizing telephone services, such as the Internet caller-ID service fee, or providing third party services to the calling party 140. Additionally, a receiving 130 or calling party 140 may prefer to have a resource locator be designated by a third party without consideration. For example, a party may be inclined to have a daily horoscope or weather report be provided by the resource locator in the Internet caller-ID messages it sends or receives. [0057] In order to designate the resource locator, the third party could be provided access to the profile database 156 so that the third party would have the ability to store a resource locator in the receiving party's 130 or calling party's 140 profile. Accordingly, in one embodiment of this process, the third party makes an agreement with the provider of the Internet caller-ID service for the ability to add resource locator entries to the profile database 156. In another embodiment of the process, the third party could have a web site whereby a party that is registered for the Internet caller-ID service could assent to the addition of resource locators to the registered party's profile, where the resource locators are designated by the third party. [0058] FIG. 5 is a flowchart representation of one implementation of the supplying of third party announcements in the Internet caller-ID messages of a registered party. In block 610, a receiving party or a calling party registers for Internet caller-ID service. In block 620, the registered party assents to the placement of third party announcements in the registered party's Internet caller-ID messages, and in block 630, the registered party is reimbursed by the third party. Typically, a registered party would assent by verifying (e.g., clicking a VERIFY button on the web page) that the registered party agrees to the inclusion of the resource locators concerning third parties in its Internet caller-ID messages. Accordingly, the third party and the Internet caller-ID provider may have an agreement already established, where the Internet caller-ID provider has given the third party the ability to write to the profile database 156. [0059] Alternatively, the Internet caller-ID service provider may have an arrangement in place with a third party, whereby a party registered for the caller-ID service also agrees to allow the Internet service provider to include resource locator(s) to the registered party's profile. The included resource locator(s) could be a URL to a web site hosted by the third party or possibly a web page describing a service or product offered by the third party. In return for agreeing to the inclusion of the resource locator, the Internet service provider could be reimbursed by the third party, and the registered party could be reimbursed by the third party or even the Internet service provider. 3. Placing the Call [0060] In block 230, the calling party 140 places the telephone call to a receiving party 130. Within the telephone network 110, representative switches 112, 116 are utilized to route calls between points or destinations within the telephone network 110. Associated with telephone calls are services such as call-waiting, call-forwarding, and the conventional caller-ID. When a switch 112 identifies that a service has been requested by either the telephone number originating the call or the telephone number receiving the call, the switch 112 suspends processing of the call and forwards information about the call to a service control point 114, such as a SCP in a signal system 7 (SS7) network or a softswitch in a digital VoIP network. The service control point 114 recognizes the type of service requested from the telephone number and informs the switch 112 on how to handle the call. For example, FIG. 6 shows an embodiment of this process of the present disclosure. In block 231, the switch 112 servicing the calling party 140 receives the request for a connection to be made to the telephone number of the receiving party 130. In block 232, the switch 112 detects that a telephone service has been requested. The switch 112 asks the service control point 114 on how to proceed and temporarily suspends normal call processing, as shown in block 233. The service control point 114 then authorizes the Internet caller-ID server 150 to make and deliver an Internet caller-ID message, as shown in block 234. In block 235, the service control point 114 tells the switch 112 to start processing the call again. 4. Generating the Message [0061] FIG. 7 is a flowchart depicting an embodiment of a process for generating the Internet caller-ID message 240. In block 241, with the service control point's 114 authority, the Internet caller-ID server 150 retrieves the profile information of the receiving party 130, which includes the receiving party's delivery transport address. Additional information such as the caller's name, time, date, and the caller's home address may also be retrieved from the profile database 156 or other databases in the telephone network. Further in block 242, the Internet caller-ID server 150 retrieves the resource locator(s) from the profile database 156 that are to be included in the Internet caller-ID message. If a resource locator is not designated for a particular number in the profile database 156, then in the message, a default resource locator may be provided, such as an Internet address for a online white or yellow page listing of the calling party, as depicted in block 243. With this collected information, the Internet caller-ID message may be constructed 240, as shown in block 244. [0062] FIG. 8 shows a representation of one example, among others, of the content that is contained in an Internet caller-ID message for one embodiment of the present disclosure. One portion of the illustration approximates an instant message display 300 that the internet-connected device 132 of the receiving party would display. As shown, the instant message display 300 may comprise the name 301, address 302, and phone number 303 of the calling party, along with a resource locator 310. The other portion of the illustration approximates the web browser display 320 that would appear when the receiving party activates the resource locator 310 (or “link”) imbedded in the instant message. In this example, the resource locator 310 is an Internet URL of a web page 320 hosted by the calling party 140. 5. Delivering the Message [0063] FIG. 9 is a flowchart depicting an embodiment of a process for delivering the Internet caller-ID message 250. With the receiving party's delivery transport address, the service control point 114 authorizes the Internet caller-ID server 150 to retrieve the profile information for the receiving party 130. The profile information is retrieved from the Internet caller-ID profile database 156 via the Internet caller-ID server 150, as depicted in block 251. The Internet caller-ID server 150 uses the delivery transport address to send the Internet caller-ID message over the Internet to the Internet-connected device 132 of the receiving party, as shown in block 252. a. Push Technology [0064] FIG. 10 depicts one exemplary embodiment of a process for delivering an Internet caller-ID message 250 using push technology. In block 254 a, the Internet caller-ID server uses the delivery transport address to determine the IP address of the Internet-connected device 132. This may occur in a number of ways. For example, the identity of the receiving party's ISP may be the provider of the receiving party's phone services and therefore may be known to the Internet caller-ID server 150. Alternatively, the identity of the ISP 170 may be provided in the receiving party's profile and then may be obtained at the same time that the Internet caller-ID server 150 retrieves the receiving party's 130 delivery transport address. After obtaining the identity of the ISP 170, the Internet caller-ID server 150 could request the IP address from an IP mapping database 175, where the IP mapping database 175 is maintained by the personal ISP 170 of the receiving party. [0065] For instance, whenever the receiving party 130 logs in to its ISP 170 it is dynamically allocated an Internet address by the ISP 170. When the receiving party 130 logs off and discontinues its Internet session, the Internet address is reallocated and is no longer associated with the receiving party 130. Accordingly, the next time the receiving party 130 logs in to its ISP 170 it will receive another address that is highly likely to be different than the previous IP address. Therefore, the IP mapping database 175 stores all the current IP addresses for the active users of the ISP 170. The Internet caller-ID server requests and receives the current IP address from the ISP 170, where the ISP 170 retrieves the information from the IP mapping database 175. In block 255 a, after obtaining the current IP address, the Internet Caller-ID server “pushes” the Internet caller-ID message, in the form of a web page, over the Internet, to an active web browser loaded on the Internet-connected device 132. [0066] Please note, in the most general sense, delivery of an Internet caller-ID message can be accomplished using a low level protocol like TCP or UDP. For example, if the address of the receiving party's Internet-connected device 132 is designated as the delivery transport address of the receiving party 130, the internet caller-ID server 150 could initiate a connection to the receiving party's Internet-connected device 132 and communicate the internet caller-ID message to the receiving party 130. b. Instant Messaging [0067] Another exemplary embodiment of a process of delivery is depicted in FIG. 11. Here, instant messaging technology is used. In block 254 b, the instant messaging address for the receiving party's Internet-connected device 132 is determined using the delivery transport address. For example, the delivery transport address may be the receiving party's instant messaging address, such as fred@jabber.bellsouth.com. With the progression toward an open and interoperable instant messaging protocol, such as the XML based instant messaging system Jabber, this may be all that is needed to deliver an instant message to the receiving party, since an instant message could be addressed in the same fashion as an email address. [0068] In a closed environment, the delivery transport address could be the name of the receiving party's instant messaging userID or nickname. Therefore, the receiving party's instant messaging provider would also be provided in the receiving party's profile with any other information that may be needed. Accordingly, the Internet caller-ID server 150 may authenticate itself to the instant messaging service 170 and act as a surrogate or proxy client on the server. In this manner, the Internet caller-ID server can send instant messages to the receiving party 130. [0069] Therefore, in block 255 b, the Internet caller-ID message is transmitted as an instant message to the Internet-connected device 132 of the receiving party. The active instant messaging client installed on the Internet-connected device 132 receives and displays the Internet caller-ID message. Typically, the instant messaging client will be already installed and running on the Internet-connected device 132 before an Internet caller-ID message is sent. 6. Receiving the Message and Telephone Call [0070] FIG. 12 depicts an embodiment of a process 260 for receiving the Internet caller-ID message and completing the telephone call from the calling party 140 to the receiving party 130. In block 261, after the service control point 114 authorizes the Internet caller-ID server 150 to send the Internet caller-ID message, the service control point 114 authorizes the switch 112 to proceed with completing the calling party's 130 telephone call to the receiving party 140. Hence in block 262, the receiving party 130 receives an Internet caller-ID message on its Internet-connected device 132 at about the same time that it receives a telephone call on its telephony device 131. The receiving party 130 reads the Internet caller-ID message to see who is calling. Additionally, the receiving party 130 can also activate any of the resource locator(s) 350 provided before, during, or after the call is completed, as shown in block 263. Further, if the call is not answered by the receiving party 130 party, the receiving party 130 can still access the resource locator 350 that is contained in the Internet caller-ID message. C. Flow Diagrams [0071] FIGS. 13 and 14 show service flow diagrams for implementations of the present disclosure. The diagram of FIG. 13 specifically shows an example service flow for an embodiment of the present disclosure as would be provided to a PSTN subscriber. In this scenario, the subscriber is the receiving party 130 at the phone number 404-555-6789. This example illustrates a variety of the service in which the calling party 140 defines the resource locator 310 that is to be sent with each call. For this example, it is assumed that the resource locator is in the form of a URL; and the calling party 140 and the receiving party 130 are both represented in a subscriber profile database record which provides common profile information. This information includes at least the following: name, URL, instant messaging address. The application logic resides in the application server 150 (Internet caller-ID server) and implements functionality that allows it to appear as a regular user to an instant messaging server 190. This is known as a surrogate or proxy client. The surrogate/proxy client has connected and authenticated itself to the instant messaging service 170 prior to the initiation of this call scenario. [0072] The call is first presented to the telephone networking switch 112, which is an service switching point (SSP) in a signaling system 7 (SS7)/PSTN advanced intelligent network (AIN) 110, where the SSP 112 hosts the receiving party subscriber line. The subscriber line is provisioned with an AIN termination attempt trigger. Upon encountering the trigger, the SSP 112 will send (1) a TERMINATION ATTEMPT (TAT) query message over the SS7 network 110 to a SCP (service control point) 114 where an AIN trigger handling logic resides. Note, the use of AIN triggers is for example only, other mechanism exists for triggering on an inbound call. For example, in a voice over IP environment, the service could be triggered upon receipt of a session initiation protocol (SIP) invite message by a SIP proxy server. [0073] Upon receipt of the TAT query, the SCP 114 will immediately respond to the SSP 112 with (2) an AUTHORIZE TERMINATION message. In conjunction with this message, the SCP 114 will send a (3) Call Notification message to an application server 150 in which the Internet caller-ID service application logic resides. There are several possible alternate implementations to the form of this notification. The notification could be accomplished using a distributed procedure call mechanism such as CORBA or Java RMI, or it could be transmitted via an ordinary TCP or UDP connection. It is assumed that a variety of methods would be apparent to someone of ordinary skill in the art. [0074] Note, the distinction between SCP (service control point) 114 and the application server (Internet caller-ID server) 150 is a logic distinction. It is not necessary that the functions be provided by separate network elements. It is possible to realize an implementation of this service where the trigger handling logic and application logic are provided by the same application within the same network element. [0075] Upon receipt of the Call Notification (3) message, the application logic will query a database 156 to determine the resource locator and name of the caller, and the instant messaging address of the subscriber. These transactions are show in flows 4-7. In this example, the profile database 156 is assumed to be a relational database implementing the SQL query language. However, the specific representation of the profile database 156 is not important. Alternate implements should be apparent using a number of different access and storage methods. One such example is the use of remote directory server implementing the light-weight directory access protocol (LDAP). [0076] After retrieving the needed information from the profile database 156, the application service logic in the Internet caller-ID server 150 will build and send an instant message (8) to the instant messaging server 190. Upon receipt of the message, the instant messaging server 190 will forward the message (9) to the receiving party's instant messaging client 132. In this example, we have elected to show an interaction with Jabber—an open source instant messaging service defined using XML. Jabber provides at least one widely available instant messaging client that presents URL information in an active form. That is, it allows the user to mouse-click on the URL and open a browser session and view the HTML content. Implementations using other instant messaging services should be apparent to one of ordinary skill in the art. [0077] The diagram of FIG. 14 shows an alternative implementation in which the resource locator information is not under the control of the calling party 140 but is, instead, provided in the form of a template which may be under the control of the subscriber 130 (receiving party). The call flow is identical to the previous flow except that information about the calling party 140 is not retrieved. Instead, when the resource locator information is retrieved from the receiving party 130 profile, the portion of the URL information indicated by “CallingDN” is replaced with the calling party's telephone number in the Internet caller-ID message. All other elements of the service are as described above. The URL syntax is for example only. [0078] This form of the embodiment, among others, of the disclosure allows the calling party to control the information being provided. It could be used to allow a user to bind access to their own web content to inbound calls. For example, a user might elect to have a web front end to a customer relationship management package. The URL template could be constructed such as to allow access to this web based system. [0079] The enhanced visual capabilities of the above-described embodiments of the present disclosure advantageously leads to an improved system and method for providing a full set of information about the maker of a telephone call. The information delivered may be contained in a web server, based on content created by the calling party prior to the call, or other information, such as announcements from third parties. It should be emphasized that the above-described embodiments of the present disclosure are merely possible examples of implementations, merely set forth for a clear understanding of the principles of the disclosure. Many variations and modifications may be made to the above-described embodiment(s) of the disclosure without departing substantially from the principles of the disclosure. For example, it is contemplated that an embodiment of the present disclosure will include the features of conventional caller-ID services in addition to the new features discussed herein. Therefore, under the principles of the present disclosure, standard caller-ID features such as caller-ID blocking are contemplated. Accordingly, it will be understood by those skilled in the art that the present disclosure is not limited to the specific implementations shown in the figures. For example, information stored in separate databases in one embodiment of the disclosure could be collectively be stored in a single database in another embodiment of the disclosure. Further, other Internet transport mediums, such as email and or SMS messaging, may be used to deliver the Internet caller-ID messages. D. Alternative Embodiments [0080] Next, in FIG. 15, a block diagram of another embodiment of a communication system of the present disclosure is shown. The communication system 1500, in FIG. 15, includes a communication network 1510 (e.g., a telephone network, a messaging network, etc.) and the Internet 1520. The communication device 1530 of a receiving party is communicatively coupled to the communication network 1510 and has access 1560 to the Internet 1520. The communication network 1500 further includes a content delivery application 1505. The content delivery application 1505 transmits information to a communication device 1530 of a receiving party. In particular, the content delivery application 1505 constructs a content message including third party content and sends the content message to the receiving party via a content push gateway 1565. From the Internet 1520, the content push gateway 1565 receives a content message from the content delivery application 1505 and formats the message for transmission to the particular communication device 1530 of the receiving party (e.g., a Caller-ID box, a personal digital assistant, a cellular telephone, SMS receiver, web browser, etc.). [0081] Correspondingly, a communication device 1540 of a calling party is also included in the communication system 1500. The communication device 1540 is connected to the communication network 1510, and it may have Internet access 1544. Note, that although separation is suggested in FIG. 15, discrete functions of the content delivery application 1505 can be viewed as being performed by devices that are implemented in other elements, such as the communication network 1510 and by devices that are in implemented in the Internet 1520, without limitations. Further, the content delivery application 1505 can be implemented in software, firmware, hardware, or a combination thereof. In some implementations, functions are implemented in software or firmware that is stored in a memory as logic that is executed by a suitable instruction execution system. A third party database 1570 is accessible from the Internet 1520 and stores content to be delivered to the receiving party in a content message. Further, a profile database 1580 is accessible from the Internet and is used to store profile information for the receiving party that may include a phone number or address, content preferences, and content delivery address. For example, based upon content preferences specified in the receiving party's profile, content is selected to be included in a content message for the receiving party. Therefore, the content message is customized for a particular receiving party, in some embodiments, and is transmitted to the content delivery address. [0082] For some embodiments, when a user, such as the receiving party 1530, desires to register for the content delivery service, so that it may receive content messages, the receiving party 1530 first creates a profile, for some embodiments. The information gathered for the profile may include the phone number that the communication device of the receiving party 1530 receives incoming phone calls at. This phone number may be the phone number of a telephone attached to a phone line, or it may be even a wireless telephone that the receiving party also uses. Therefore, the communication device 1530 of the receiving party may receive telephone calls from a wire-based or a wireless communication network 1520. Since multiple telephony devices may be used to receive incoming phone calls, multiple phone numbers may be listed in the profile information for the receiving party. When the receiving party receives an incoming telephone call, additional information from a third party is also delivered (e.g., “piggy-backed”) to the receiving party with the incoming phone call along with caller identification information. [0083] Thus, pre-specified preferred information to a receiving party can be delivered along with an incoming call attempt. As such, various embodiments of the present disclosure delivers information to a receiving party on a periodic basis (as frequently as incoming phone calls or messages arrive) when the receiving party is being alerted of another incoming communication. Moreover, preferred information is provided in such a way as to offer the opportunity for the third party to provide consideration to the receiving party (in the form of discounts, coupons, payments that subsidize the cost of the communication service (e.g., telephone service, messaging service, etc.) to the receiving party, or other compensation. [0084] FIG. 16 is a flowchart of one embodiment of a method for establishing content delivery preferences. The process 1600 involves a receiving party logging (1610) into a profile database and setting (1620) their telephone address in a profile for the receiving party (e.g., by accessing a registration system via the World Wide Web, an interactive voice response unit, etc.). Next, the receiving party sets (1630) their content preferences in the profile. For example, the content preferences may specify categories of information that the receiving party is willing to receive over a communication device, such as weather reports, entertainment news, stock information, etc. Further, the receiving party sets (1640) their content delivery address in the profile. The content delivery address is the address where content messages are sent. For example, for a personal communication device that has both a phone number and a text messaging email address, the content delivery address may be specified to be the text messaging email address for the personal communication device. In other embodiments, content delivery addresses also include a variety of messaging formats, such as instant messaging addresses, short message service addresses, telephone numbers, Internet Protocol addresses, etc. [0085] With access to the receiving party's content delivery address, the communication network 1510 can detect a telephone call being sent to the receiving party and utilize the content delivery address of the receiving party to send caller identification information along with additional information to the receiving party at the content delivery address. FIG. 17 depicts one exemplary embodiment of a process for delivering a content message using push technology. In block 1710, a calling party places (1710) a telephone call to a receiving party. The communication network detects (1720) that content delivery has been requested by the receiving party. [0086] The communication network then requests (1730) the content delivery application to create and deliver a content message. The content delivery application queries (1740) the profile database for a profile based on the called number. From the retrieved profile, the content delivery application determines (1750) content preferences and collects third party content accordingly. The content delivery application constructs (1760) the content message in the proper format for the respective content delivery address (e.g., short message service format, wireless markup language, hypertext markup language, etc.) and delivers the content message with the content delivery address to a content push gateway. The content push gateway then sends (970) the content message to the receiving party at the content delivery address. Also, the communication network delivers (980) the telephone call to the receiving party. [0087] FIG. 18 is a flowchart representation of one implementation of the supplying of third party announcements in the content messages of a registered party. In block 1810, a receiving party registers for content delivery service that supplies content messages. As part of the registration process, the receiving party may specify the particular advertisers or types of advertising that would be preferred to be received in content messages. In block 1820, the registered party assents to the receipt of third party content via content messages, and in block 1830, the registered party is reimbursed by the third party for agreeing to register for the content delivery service and receipt of third party content. Typically, a registered party would assent by verifying (e.g., clicking a VERIFY button on a registration web page) that the registered party agrees to the inclusion of the content message from a third party. In doing so, consideration could be provided to the registered party. For example, consideration may be provided to subsidize the cost of communication services to the registered party. Alternatively, consideration in the form of a coupon of a product offered by the third party may be provided, for example. In addition, consideration could also be provided to the content delivery service by the third party. [0088] Next, FIG. 19 shows one embodiment of an interface demonstrating delivery of a content message to a receiving party. In the example of FIG. 19, a representation 1900 of a mobile personal communication device is shown. This particular representation 1900 is intended to support wireless networks, such as Code Division Multiple Access (CDMA) and Global System for Mobile Communications (GSM), and a variety of communication formats, including voice communication over telephone network, short message service (SMS), multimedia message service (MMS), wireless application protocol (WAP), electronic mail (e-mail), etc. In the example of FIG. 19, the mobile personal communication device 1900 (e.g., a Blackberry� messaging phone) has received information 1910 about the calling party making an incoming call to the personal communication device. In addition, the mobile communication device has also received customized third party content 1920. Since a user is likely to check identification information of a caller of an incoming telephone call, the user is also increasingly likely to view additional information that is appended to the caller identification information. Thus, this is an effective way to distribute content information to a user and for a user to dictate the nature of the content that he or she prefers to receive. For example, there may be specific retail stores or other businesses with which the receiving party normally does business. Accordingly, the receiving party would prefer to receive advertising from their preferred businesses as opposed to a random list of businesses, making the utility of the information that is delivered to the receiving party greater. Likewise, there may be preferred types of timely information that the receiving party would like to receive, e.g., entertainment news, local news, stock information for specific stocks, and weather information for their hometown. Accordingly, all such modifications and variations are intended to be included herein within the scope of the disclosure and the present disclosure and protected by the following claims. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS4582956 *Jul 12, 1983Apr 15, 1986At&T Bell LaboratoriesMethod and apparatus for displaying at a selected station special service information during a silent interval between ringingUS4649433 *May 4, 1984Mar 10, 1987U.S. Philips CorporationArrangement for making a photographic slide or cine-film recording of a television pictureUS4649533 *Oct 25, 1983Mar 10, 1987Keycom Electronic PublishingMethod and apparatus for retrieving remotely located informationUS4797911 *Jun 16, 1987Jan 10, 1989Inventions, Inc.Customer account online servicing systemUS4802202 *Sep 3, 1987Jan 31, 1989Sanyo Electric Co., Ltd.Telephone call selectorUS4817133 *Sep 14, 1987Mar 28, 1989Sanyo Electric Co., Ltd.Party selecting circuit arrangementUS4823304 *Jan 15, 1987Apr 18, 1989International Business Machines IncorporatedMethod of providing synchronous message exchange in an asychronous operating environmentUS4995075 *Sep 5, 1989Feb 19, 1991At&T Bell LaboratoriesApparatus and method for encoding telephone ringing signalsUS5109405 *Aug 16, 1990Apr 28, 1992Dytel CorporationAutomated call screeningUS5200994 *Aug 2, 1989Apr 6, 1993Kabushiki Kaisha ToshibaCommunication terminal apparatus and control method with party identification featuresUS5206901 *Dec 23, 1991Apr 27, 1993At&T Bell LaboratoriesMethod and apparatus for alerting multiple telephones for an incoming callUS5278894 *Oct 25, 1991Jan 11, 1994At&T Bell LaboratoriesUse of incoming caller line identificationUS5289542 *Mar 4, 1991Feb 22, 1994At&T Bell LaboratoriesCaller identification system with encryptionUS5383466 *May 14, 1993Jan 24, 1995Becton, Dickinson And CompanyInstrument having enhanced ultrasound visibilityUS5386460 *Jan 4, 1993Jan 31, 1995At&T Corp.Feature configurable telephone terminalUS5388150 *Jul 28, 1992Feb 7, 1995Schneyer; RobinAutomatic incoming telephone call identification and disposition systemUS5481594 *Aug 6, 1993Jan 2, 1996Aastra CorporationAudio caller identification unitUS5481599 *Nov 15, 1994Jan 2, 1996Macallister; Donald I.Automated audio output device for a telephone setUS5481602 *Dec 27, 1994Jan 2, 1996At&T Corp.Method and apparatus for alternate destination routing for switching egress customersUS5490205 *Jun 14, 1994Feb 6, 1996Matsushita Electric Industrial Co., Ltd.Telephone set for handling a callUS5497414 *May 4, 1994Mar 5, 1996Bell Atlantic Network Services, Inc.Telephone system processing of designated caller ID private callsUS5502762 *Jun 10, 1994Mar 26, 1996Andrew; Brian J.System and method for simultaneously controlling ringing at local and remote telephonesUS5506893 *Nov 29, 1994Apr 9, 1996At&T Corp.Telecommunication network arrangement for providing real time access to call recordsUS5511111 *Nov 1, 1993Apr 23, 1996Engineering And Business Systems, Inc.Caller name and identification communication system with caller screening optionUS5602908 *May 18, 1995Feb 11, 1997Fan; Yuan-NengCalling party identifying apparatus and method thereforUS5608788 *Sep 8, 1995Mar 4, 1997Lucent Technologies Inc.Information display provided to calling partyUS5724412 *Oct 7, 1996Mar 3, 1998U S West, Inc.Method and system for displaying internet identification on customer premises equipmentUS5734706 *May 7, 1996Mar 31, 1998Windsor; Victoria BreinCaller identification and data retrieval systemUS5859903 *Dec 26, 1996Jan 12, 1999Samsung Electronics Co., Ltd.Method of displaying caller identification for abandoned call in key-phone systemUS5872834 *Sep 16, 1996Feb 16, 1999Dew Engineering And Development LimitedTelephone with biometric sensing deviceUS5872934 *Aug 26, 1996Feb 16, 1999Sony CorporationMethod and apparatus for connecting several video distribution units to a serial data busUS5878036 *Dec 20, 1995Mar 2, 1999Spartz; Michael K.Wireless telecommunications system utilizing CDMA radio frequency signal modulation in conjunction with the GSM A-interface telecommunications network protocolUS5883942 *Jan 24, 1997Mar 16, 1999Cybiotronics, Ltd.Voice caller I.D. apparatusUS5884144 *Sep 27, 1995Mar 16, 1999Lucent Technologies Inc.Maintenance and administration of remote systems via radio pagerUS6014559 *Apr 10, 1997Jan 11, 2000At&T Wireless Services, Inc.Method and system for delivering a voice mail notification to a private base station using cellular phone networkUS6016512 *Aug 18, 1998Jan 18, 2000Telcordia Technologies, Inc.Enhanced domain name service using a most frequently used domain names table and a validity code tableUS6021188 *Jun 16, 1997Feb 1, 2000Meg; AlfredCaller identification information printing system and methodUS6021427 *May 22, 1997Feb 1, 2000International Business Machines CorporationMethod and system for preventing routing maelstrom loops of automatically routed electronic mailUS6031899 *Oct 28, 1996Feb 29, 2000Ericsson IncMethod and apparatus for identifying type of callUS6044148 *Jul 16, 1997Mar 28, 2000Nortel Networks CorporationPre-ring caller identification apparatus and method and call screening therefromUS6169911 *Sep 26, 1997Jan 2, 2001Sun Microsystems, Inc.Graphical user interface for a portable telephoneUS6173049 *Dec 1, 1998Jan 9, 2001Bellsouth Intellectual Property CorporationSystem and method for automated provision and customer selection of temporary caller identification servicesUS6178232 *Jul 24, 1998Jan 23, 2001Ameritech CorporationMethod and system for providing enhanced caller identificationUS6181928 *Aug 21, 1997Jan 30, 2001Ericsson Inc.Method and apparatus for event notification for wireless devicesUS6185289 *Mar 27, 1998Feb 6, 2001Bell Atlantic Network Services, Inc.Mediated AIN control of short code access to information service providersUS6187254 *Mar 25, 1997Feb 13, 2001Sandvik AbMethod of sintering silicon nitride based materialsUS6192115 *Mar 9, 1999Feb 20, 2001Lucent TechnologiesObtaining information about a called telecommunications partyUS6192116 *Aug 31, 1998Feb 20, 2001Lucent Technologies Inc.System and method for generating CID/CIDCW information with a user inputted messageUS6198480 *Jan 29, 1999Mar 6, 2001Wonderware CorporationObject-oriented tag browserUS6198920 *Mar 16, 2000Mar 6, 2001Padcom, Inc.Apparatus and method for intelligent routing of data between a remote device and a host systemUS6202023 *Feb 25, 1999Mar 13, 2001Go2 Systems, Inc.Internet based geographic location referencing system and methodUS6337904 *Sep 12, 2000Jan 8, 2002Genesys Telecommunications Laboratories, IncAutomated survey control routine in a call center environmentUS6337979 *Jun 29, 1998Jan 8, 2002Nec CorporationPDC (personal digital cellular) communication controlling apparatus and system thereofUS6339639 *Nov 4, 1997Jan 15, 2002Daniel A. HendersonEnhanced call-waiting with caller identification method and apparatusUS6341161 *Aug 3, 1999Jan 22, 2002Teresa Farias LatterMethod and system for providing enhanced caller identification information including tailored announcementsUS6345187 *May 24, 1999Feb 5, 2002Agere Systems Guardian Corp.Receipt of type II caller identification in multi-cordless environmentUS6347136 *Jul 15, 1999Feb 12, 2002Winbond Electronics CorporationCalling party announcement message management systems and methodsUS6351637 *May 24, 1999Feb 26, 2002Samsung Electronics, Co., Ltd.Method of transmitting a caller's identification number to a mobile instrument from a home base stationUS6353664 *Dec 1, 1997Mar 5, 2002Agere Systems Guardian Corp.Caller ID equipment which displays location of callerUS6361637 *Aug 13, 1999Mar 26, 2002Gore Enterprise Holdings, Inc.Method of making a kink resistant stent-graftUS6363140 *Jul 23, 1998Mar 26, 2002Mitel KnowledgeDialable screening profileUS6363411 *Oct 19, 1999Mar 26, 2002Mci Worldcom, Inc.Intelligent networkUS6507737 *Sep 30, 1998Jan 14, 2003Lucent Technologies Inc.Method for automatically monitoring continuity and integrity of communication trunksUS6529500 *Aug 26, 1999Mar 4, 2003Verizon Laboratories Inc.Unified messaging notificationUS6529591 *Jul 30, 1999Mar 4, 2003Nazir DosaniMethod and system for communication caller identification information between a remote site and a central monitoring station over PSTNUS6532490 *Jun 13, 2000Mar 11, 2003Bellsouth Intellectual Property CorporationMethods and elements to reduce the number of quieries to a foreign network elementUS6539080 *Jul 14, 1998Mar 25, 2003Ameritech CorporationMethod and system for providing quick directionsUS6683870 *Jun 25, 1998Jan 27, 2004Mci Communications CorporationMethod and system for multicasting call notificationsUS6687341 *Dec 21, 1999Feb 3, 2004Bellsouth Intellectual Property Corp.Network and method for the specification and delivery of customized information content via a telephone interfaceUS6697357 *Jul 15, 2002Feb 24, 2004Emerson, Iii Harry E.Call management messaging system for integrating the internet with the public switched telephone networkUS6701160 *May 22, 2000Mar 2, 2004Motorola, Inc.Method and apparatus to locally block incoming selected callsUS6842512 *Feb 28, 2001Jan 11, 2005Fuji Xerox Co., Ltd.Systems and methods for managing electronic communicationsUS6845151 *Feb 6, 2002Jan 18, 2005Meiloon Industrial Co., Ltd.Picture/sound output equipment with caller identification and volume adjustment functionsUS6845512 *Jan 28, 2003Jan 18, 2005Sunonwealth Electric Machine Industry Co., Ltd.Device with spring-loaded curved tongues for holding an optical disk around a rotary shaft of a motorUS6853710 *Jul 17, 2002Feb 8, 2005Timothy M HarrisTelephone call messaging deviceUS6853711 *Sep 10, 2001Feb 8, 2005Nortel Networks LimitedMethod for adding context to communicationsUS6856677 *Feb 20, 2002Feb 15, 2005Ab Aurora InvestCall queue handlingUS6859527 *Apr 27, 2000Feb 22, 2005Hewlett Packard/LimitedCommunications arrangement and method using service system to facilitate the establishment of end-to-end communication over a networkUS6865266 *Jan 16, 2002Mar 8, 2005Verizon Services Corp.Methods and apparatus for transferring from a PSTN to a VOIP telephone networkUS6865384 *Nov 2, 2001Mar 8, 2005Motorola, Inc.Method and communication network for routing a real-time communication message based on a subscriber profileUS6868155 *Oct 5, 1999Mar 15, 2005Agere Systems Inc.Off-hook visual message waiting indicatorUS6870924 *Oct 18, 2000Mar 22, 2005Nec CorporationAutomatic call distribution system and methodUS6871076 *Jul 11, 2002Mar 22, 2005International Business Machines CorporationMethod and system for automatically adjusting location based system information in a mobile computerUS6996211 *Dec 23, 2002Feb 7, 2006Sbc Properties, L.P.Voice over IP method of determining caller identificationUS7012999 *Jun 25, 2001Mar 14, 2006Bellsouth Intellectual Property CorporationAudio caller identificationUS7016482 *Jul 9, 2002Mar 21, 2006Sbc Knowledge Ventures, L.P.Method and system of providing caller identification with nameUS7020250 *Jun 26, 2002Mar 28, 2006Sbc Properties, L.P.System and method for providing visual indication of caller and telephony platform information on customer premises equipmentUS7184533 *Dec 7, 1999Feb 27, 2007Siemens Communications, Inc.Method and apparatus for mixed media contact notification serviceUS20020009184 *Oct 22, 1999Jan 24, 2002J. Mitchell ShnierCall classification indication using sonic meansUS20020016748 *May 22, 2001Feb 7, 2002Comverse Network Systems, Ltd.System and method enabling remote access to and customization of multimediaUS20030007620 *Jul 22, 2002Jan 9, 2003Elsey Nicholas J.Technique for effectively providing concierge-like services in a directory assistance systemUS20030026416 *Aug 1, 2001Feb 6, 2003Fusco Marc E.Personalized telephone announcementUS20030050100 *Sep 12, 2001Mar 13, 2003Dent Paul W.Network architecture for mobile communication network with billing module for shared resourcesUS20030053602 *Sep 18, 2001Mar 20, 2003Stuckman Bruce EdwardSubscriber-based emergency alert method and systemUS20040049545 *Sep 6, 2002Mar 11, 2004Terry Wayne LockridgeInstant message notification via caller IDUS20060002540 *Jul 2, 2004Jan 5, 2006Barrett KreinerReal-time customer service representative workload managementUS20060013375 *Jul 15, 2004Jan 19, 2006Donald SmithMethods of providing caller identification information and related registries and radiotelephone networksUS20060029209 *Oct 13, 2005Feb 9, 2006Moton Robert TVoice caller IDUS20070064911 *Jun 18, 2002Mar 22, 2007Bedingfield James C SrMethod for using ain to deliver caller ID to text/alpha-numeric pagers as well as other wireless devices, for calls delivered to landline networks* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7545918 *Nov 26, 2003Jun 9, 2009At&T Intellectual Property I, L.P.Call tickerUS7623849 *Nov 13, 2003Nov 24, 2009At&T Intellectual Property, I, L.P.Method, system, and storage medium for providing comprehensive originator identification servicesUS7672444Mar 2, 2010At&T Intellectual Property, I, L.P.Client survey systems and methods using caller identification informationUS7702753Dec 13, 2005Apr 20, 2010Accenture Global Services GmbhUnified directory and presence system for universal access to telecommunications servicesUS7852828 *Aug 7, 2002Dec 14, 2010Cisco Technology, Inc.Extended telephony functionality at end pointsUS7917124 *Mar 29, 2011Accenture Global Services LimitedThird party access gateway for telecommunications servicesUS7920583Dec 13, 2005Apr 5, 2011Accenture Global Services LimitedMessage sequencing and data translation architecture for telecommunication servicesUS7925880Apr 12, 2011Accenture Global Services LimitedAuthentication and authorization architecture for an access gatewayUS7929675Jul 20, 2006Apr 19, 2011At&T Intellectual Property I, L.P.Visual caller identificationUS7945253May 17, 2011At&T Intellectual Property I, L.P.Method, system, and storage medium for providing comprehensive originator identification servicesUS7978833Apr 18, 2003Jul 12, 2011At&T Intellectual Property I, L.P.Private caller ID messagingUS7978841Oct 19, 2009Jul 12, 2011At&T Intellectual Property I, L.P.System and method for gathering information related to a geographical location of a caller in a public switched telephone networkUS8019064Dec 20, 2007Sep 13, 2011At&T Intellectual Property I, L.P.Remote notification of communicationsUS8073121 *Dec 6, 2011At&T Intellectual Property I, L.P.Caller ID messagingUS8102994Jan 24, 2012At&T Intellectual Property I, L.P.Client survey systems and methods using caller identification informationUS8139758Aug 25, 2008Mar 20, 2012At&T Intellectual Property I, L.P.Voice caller IDUS8155287May 1, 2007Apr 10, 2012At&T Intellectual Property I, L.P.Systems and methods for providing user profile information in conjunction with an enhanced caller information systemUS8160226Apr 17, 2012At&T Intellectual Property I, L.P.Key word programmable caller IDUS8195136Jun 5, 2012At&T Intellectual Property I, L.P.Methods of providing caller identification information and related registries and radiotelephone networksUS8199902 *Jun 12, 2012Avaya Inc.Passing URL for XML documents via a telephone signaling systemUS8243909Aug 22, 2007Aug 14, 2012At&T Intellectual Property I, L.P.Programmable caller IDUS8270581 *Sep 18, 2012Time Warner Cable, Inc.System and method for displaying caller identification information via an instant messaging serviceUS8416938Jun 29, 2012Apr 9, 2013At&T Intellectual Property I, L.P.Programmable caller IDUS8433301 *Dec 14, 2005Apr 30, 2013Telecom Italia S.P.A.Method and system for automatically providing contents from a service provider to a mobile telephonic terminalUS8452268May 28, 2013At&T Intellectual Property I, L.P.System and method for gathering information related to a geographical location of a callee in a public switched telephone networkUS8787549Mar 14, 2013Jul 22, 2014At&T Intellectual Property I, L.P.Programmable caller IDUS8831578 *Apr 18, 2011Sep 9, 2014At&T Mobility Ii LlcManaging multiple CLI identitiesUS9008293 *Nov 25, 2005Apr 14, 2015At&T Intellectual Property I, L.P.Caller ID information to internet protocol television displaysUS9240970Mar 7, 2013Jan 19, 2016Accenture Global Services LimitedCommunication collaborationUS20040028027 *Aug 7, 2002Feb 12, 2004Cisco Technology, Inc.Extended telephony functionality at end pointsUS20040209605 *Apr 18, 2003Oct 21, 2004Urban Blake R.Caller ID MessagingUS20050111644 *Nov 26, 2003May 26, 2005Michael EdwardsCall tickerUS20050135589 *Dec 22, 2003Jun 23, 2005International Business Machines CorporationManagement of guest servicesUS20050135591 *Dec 22, 2003Jun 23, 2005International Business Machines CorporationGuest services management system and methodUS20070067385 *Dec 13, 2005Mar 22, 2007Accenture S.P.A.Third party access gateway for telecommunications servicesUS20070121584 *Nov 25, 2005May 31, 2007Chaoxin QiuCaller ID information to internet protocol television displaysUS20070121821 *Nov 22, 2006May 31, 2007Chengchun SuSystem and Method for Displaying Ring Back Tone and Caller Display in Picture/Video FormatUS20070123253 *Dec 13, 2005May 31, 2007Accenture S.P.A.Unified directory and presence system for universal access to telecommunications servicesUS20070133763 *Dec 13, 2005Jun 14, 2007Accenture S.P.A.Authentication and authorization architecture for an access gatewayUS20090117925 *Dec 14, 2005May 7, 2009Roberto De BonisMethod and System for Automatically Providing Contents From a Service Provider to a Mobile Telephonic TerminalUS20090185555 *Feb 15, 2007Jul 23, 2009Alcatel LucentMethod and device for providing multimedia data when establishing a telephone callUS20090190732 *Jul 30, 2009Howard PfefferSystem and method for displaying caller identification information via an instant messaging serviceUS20110201321 *Aug 18, 2011At&T Mobility Ii LlcManaging multiple cli identitiesUS20130218995 *Feb 5, 2013Aug 22, 2013GogroupsTwo-way instant message forwardingEP1889428A2 *May 31, 2006Feb 20, 2008Roamware, Inc.Method and system for call-setup triggered push contentWO2006130783A2May 31, 2006Dec 7, 2006Roamware, Inc.Method and system for call-setup triggered push contentWO2007068268A1 *Dec 14, 2005Jun 21, 2007Telecom Italia S.P.A.Method and system for automatically providing contents from a service provider to a mobile telephonic terminalWO2007093743A2 *Feb 15, 2007Aug 23, 2007Alcatel LucentMethod and device for providing multimedia data when setting up of a telephone callWO2007093743A3 *Feb 15, 2007Oct 25, 2007Alcatel LucentMethod and device for providing multimedia data when setting up of a telephone call* Cited by examinerClassifications U.S. Classification370/352International ClassificationH04M3/42, H04L12/18, H04L12/66, H04L29/06, H04L29/08, H04L12/58Cooperative ClassificationH04L65/1069, H04M3/42068, H04M3/42076, H04L29/06027, H04L12/581, H04L12/1859, H04L51/04, H04L12/58, H04M3/42042, H04L69/329, H04L67/306, H04L67/26European ClassificationH04M3/42C1N, H04L29/08N29U, H04L29/06C2, H04L29/08A7, H04L12/58, H04L29/08N25, H04L12/18P, H04L29/06M2S1Legal EventsDateCodeEventDescriptionNov 22, 2004ASAssignmentOwner name: BELLSOUTH INTELLECTUAL PROPERTY CORP., DELAWAREFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KOCH, ROBERT A.;REEL/FRAME:016027/0520Effective date: 20041122RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services