Source: http://www.google.com/patents/US20050074101?dq=6519629
Timestamp: 2014-09-16 20:11:32
Document Index: 645297307

Matched Legal Cases: ['arty 137', 'arty 137', 'arty 137', 'arty 137', 'arty 101', 'arty 137', 'arty 101', 'arty 137', 'arty 101', 'arty 137', 'arty 137', 'arty 137', 'arty 101', 'arty 101', 'arty 137', 'arty 101', 'arty 137', 'arty 137', 'arty 101', 'arty 101', 'arty 101', 'arty 101', 'arty 101', 'arty 137', 'arty 137', 'arty 137', 'arty 137', 'arty 101', 'arty 101', 'arty 101', 'arty 137', 'arty 137', 'arty 101', 'arty 101', 'arty 137', 'arty 137', 'arty 137', 'arty 137', 'arty 101', 'arty 137', 'arty 101', 'arty 137', 'arty 101', 'arty 101', 'arty 137', 'arty 101', 'arty 137', 'arty 137', 'arty 137', 'arty 137', 'arty 101', 'arty 137']

Patent US20050074101 - Providing of presence information to a telephony services system - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign in<nobr>Advanced Patent Search</nobr>PatentsIn support of an interactive telephony services system, a presence gateway provides presence information regarding availability of a called party to communicate using an instant communications client....http://www.google.com/patents/US20050074101?utm_source=gb-gplus-sharePatent US20050074101 - Providing of presence information to a telephony services systemAdvanced Patent SearchPublication numberUS20050074101 A1Publication typeApplicationApplication numberUS 10/404,541Publication dateApr 7, 2005Filing dateApr 2, 2003Priority dateApr 2, 2002Also published asDE60325035D1, DE60326217D1, DE60328767D1, DE60331053D1, DE60333002D1, DE60333448D1, EP1495413A1, EP1495413A4, EP1495413B1, EP1495416A2, EP1495416A4, EP1495416B1, EP1495601A1, EP1495601A4, EP1495601B1, EP1495602A2, EP1495602A4, EP1495603A1, EP1495603A4, EP1495603B1, EP1495604A2, EP1495604A4, EP1495604B1, EP1495605A1, EP1495605A4, EP1495625A1, EP1495625A4, EP1495625B1, EP1495626A1, EP1495626A4, EP1495626B1, EP2166505A2, EP2166505A3, EP2166506A2, EP2166506A3, US7382868, US8260967, US8289951, US20030185232, US20030185359, US20030185360, US20030187641, US20030187650, US20030187800, US20030193961, US20040003041, US20110200179, US20110202347, WO2003085539A1, WO2003085844A2, WO2003085844A3, WO2003085913A1, WO2003085914A2, WO2003085914A3, WO2003085915A1, WO2003085916A1, WO2003085937A2, WO2003085937A3, WO2003085940A1, WO2003085941A1Publication number10404541, 404541, US 2005/0074101 A1, US 2005/074101 A1, US 20050074101 A1, US 20050074101A1, US 2005074101 A1, US 2005074101A1, US-A1-20050074101, US-A1-2005074101, US2005/0074101A1, US2005/074101A1, US20050074101 A1, US20050074101A1, US2005074101 A1, US2005074101A1InventorsRichard Moore, Gregory Mumsford, Duraisamy GunasekarOriginal AssigneeWorldcom, Inc.Export CitationBiBTeX, EndNote, RefManReferenced by (46), Classifications (130), Legal Events (4) External Links: USPTO, USPTO Assignment, EspacenetProviding of presence information to a telephony services systemUS 20050074101 A1Abstract In support of an interactive telephony services system, a presence gateway provides presence information regarding availability of a called party to communicate using an instant communications client. Images(23) Claims(76)
Action 233 represents a session initation to establish instant messaging communications with called party 137 and action 235 represents the acceptance of the session. Action 237 is an instant message to received by the calling party containing the aforementioned �Can you chat now?� invitation. Called party 137 provides a response to the invitation in action 239 which, through actions 241 and 243, reaches VPS 103. At this point, billing system 123 may optionally be informed of the acceptance of called party 137 as evidenced by action 245. For example, in some implementations, this event may be significant to billing system 123 as representing the commencement of billable usage by the parties. As shown by action 247, billing system 123 may also be involved in authorizing further action to connect the parties. In some scenarios, part of action 245 may include the passing of information obtained from called party 137, such as billing account information or authorization codes, so that billing system 123 can take such information into account. In action 249, VPS 103 may inform calling party 101 by voice that they are about to engage in a telephony-to-instant-communications session with the called party. VPS 103 may also convey any instructions about how to participate in the session. Likewise, VPS 103 may also provide a connection notification, action 255, comprising a textual message telling called party 137 about the impending commencement of the session. Optionally, actions 249 and 251 may give rise to corresponding confirmations 253 and 255. These optional confirmations may be desirable if, for example, charges for the session or other aspects of the connection must be approved by either or both of the parties. Billing related actions 245 and 247 shown earlier may optionally be performed after, and responsive to, these confirmations. As shown by action 257, VPS 103 then requests IPG 105 to establish a session between the parties. This session, between calling party 101 using a telephony connection and called party 137 using an instant communciations client, involves engaging intelligent information translator 125 to perform substantially real-time conversion among speech signals and textual information. Accordingly, IPG 105 sends a media channel request, in action 259, to the intelligent information translator 125, which allocates the needed resources for a speech-to-text process 127 and a text-to-speech process 129. This may involve reserving ports, allocating memory, and initiating new processes. The result of this allocation is sent back to the intelligent presence gateway 105 as a media channel response shown as action 261. This response may include identifiers, port numbers or other information involved in coordinating communications establishment through IIX 125. Upon successful allocation of a media channel, the intelligent information translator 125 connects the calling party 101 to the media channel, enabling voice channel connectivity as represented by action 263. On the called party end, the intelligent information translator 125 establishes a chat or other instant communications session with the called party 137 via the sender and receiver processes 127, 129 and the instant messaging server 121, and binds the instant message session to the media channel. This instant communications connection, represented by action 265, may be achieved by having IIX 125 take up the same IM session established with the called party 137 in action 231. In this manner, called party 137 experiences continuity of the one session rather than having to separately establish a session for conversing with the calling party 101. At this point, calling party 101 and called party 137 are in communication with one another. As the conversation proceeds, speech recognition algorithms are applied by the speech-to-text process 127 to convert utterances in the speech of the calling party 101 into a textual or character-based representation that is transmitted to the called party 137 via the sender process 113 and the instant messaging server 121. Conversely, text messages comprising words, abbreviations, and so-called �emoticons� received from the called party 137 via the instant messaging server 121 and the receiver process 115 are converted into a speech representation of the words by the text-to-speech process 129. The resulting speech signals may be transmitted to the calling party 101 via the voice-over-IP gateway 131 or through connection 44, VPS 103, bridging switch 54 or other means. Speech-to-text process 127 may employ any of the well known speech recognition technologies available from companies such as Nuance, SpeechWorks, IBM, or Dragon Systems, for example. Text-to-speech process 129 may use DECtalk� speech synthesis technology developed by Digital Equipment Corporation, for example. This translation may also be performed manually by a human operator listening to the utterances via a headset and typing in the text in one direction, and reading the text on a screen and providing a spoken representation in the other direction. Communications among the parties proceeds in this manner through IIX 125 until the parties are finished communicating or until a balance of a billable account is exhausted. For example, at some point during the call, the calling party 101 may wish to terminate the call. This may occur by hanging up of the telephone used by the calling party 101. This action results in a termination request, action 267, being sent from the calling party 101 to VPS 103. In practice, this termination request may be conveyed as telephony signaling, for example. In some implementations, VPS 103 may confirm the termination by sending a termination response, action 269, to the calling party 101. VPS 103 sends termination notification, action 271, to the called party 137 via the intelligent presence gateway 105 and the instant messaging server 121. As represented by action 273, VPS 103 may transmit a service event to billing system 123 as the session is ended. Intelligent presence gateway 105 may also provide a session event, action 275, to the billing system 123. Actions 273 and/or 275 may be peformed so that usage activity may accurately reported upon and charges can be accurately calculated. As with all of the calls flows in FIGS. 2A-5B, the sequence of events depicted in FIGS. 2A and 2B are intended to be merely illustrative and should not be construed to be the only manner in which the present invention may be embodied. Many of the actions shown may be augmented by other actions, omitted, or performed in a different sequence or among different elements than as shown. For example, VPS 103 could participate in engaging IIX 125 directly rather than having IPG 105 do so. Furthermore, according to an alternative approach, aspects of call termination and billing notifications may be performed by IIX 125, especially considering that IIX 125 is actively engaged in the session until it is concluded. Termination of communications may also occur other than as shown in FIGS. 2A-2B. For example, the called party 137 may signal termination by ending the instant messaging session or providing some other indication as may be appropriate in a particular implementation. This scenario is shown in FIGS. 3A and 3B. In FIGS. 3A and 3B, the steps starting from the initial voice call 301 in FIG. 3A through the establishment of the voice call 363 and instant message 365 occur as substantially described with respect to steps 201 through 265 hereinabove in FIGS. 2A and 2B, with some details ommitted for simplicity. However, in this called party termination scenario, the called party 137 sends a termination request, action 367, triggered by the ending of the session, to IIX 125 or, depending on implementation, to the voice processing system 103 via the instant messaging server 121 and the intelligent presence gateway 105. The voice processing system 103 (or IIX 125) confirms the termination by sending a termination response, action 369, to the called party 137 via the intelligent presence gateway 105 and the instant messaging server 121, and by sending a termination notification 371 to the calling party 101. As before, the voice processing system 103 transmits a service event 373 to the billing system 123, and the intelligent presence gateway 105 transmits session event 375 to the billing system 123. FIGS. 4A and 4B illustrate a call re-origination scenario, in which the calling party 101 indicates a desire to make another call without hanging up or reentering the billing information, for example by pressing the pound key (#) on a telephone keypad for two (2) seconds. In this scenario, the steps starting from the initial voice call 401 in FIG. 4A to the establishment of communications among the parties represented by actions 463 and 465 are substantially as described with respect to steps 201-275 presented above in FIGS. 2A and 2B. However, during the �call�, the calling party 101 makes the re-origination request 477 which is detected by VPS 103, perhaps via bridging switch 54. In response, the connection to called party 137 is terminated as shown by action 471, which is optional and may include, for example, a textual notification of the termination for the benefit of called party 137. Actions 473 and 475 inform billing system 123 of the conclusion of the session. Then the operator at VPS 103 offers new service options as shown by action 479. The calling party 101 submits a new service option request 481, which is handled by VPS 103 by taking appropriate steps 483. If the calling party 101 wishes another instant message based communication, then the steps described herein above may be repeated. The interaction just described for VPS 103 may involve or be performed entirely by IIX 125 as well. In another embodiment of the present invention, instant communications is used initially to contact the called party 137 for obtaining billing and capabilities information, but the call is actually then terminated in a voice-over-IP session at the option of the called party 137. FIGS. 5A and 5B illustrate the operation of this embodiment, in which steps 501-543 (transmission of the session response 543 from the intelligent presence gateway 105 to the voice processing system 103) proceed as substantially described with respect to corresponding steps 201-243. However, operator 52 at voice processing system 103 may detect that the called party client 139 is capable of voice-over-IP based on the information in the capability information response 515. An alternative to the process of obtaining information from capabilities server 117 may be to query the called party client 139 directly using, for example, SIP mechanisms for exploring client capabilities. In response the operator may send an instant message 545 to the called party 137 via the intelligent presence gateway 105 and the instant messaging server 121. Instant message 545 may ask the called party to select which capability, voice or text, the called party prefers to use. In reply, the called party 137 returns an instant message 547 that confirms that the voice-over-IP capability of the called party client 139 is to be used. This can happen at any time during the communication session. After interaction with the billing system 123 using billing request 549 and billing response 551, the operator at VPS 103 sends the intelligent presence gateway 105 a session establishment request 553. In response, the intelligent presence gateway 105 sends a session and channel request 555 to the voice-over-IP gateway 131, which establishes a voice-over-IP session with the called party client 139. A session and channel response 557 is then sent from the called party client 139 to the intelligent presence gateway 105. The intelligent presence gateway 105 then sends a session establishment response 559 to VPS 103. To complete the establishment of the call, VPS 103 provides a connection notification 561 to the calling party 101, and a connection notification 563 to the called party 137 via the voice-over-IP gateway 131. In return, the calling party 101 provides a connection confirmation 565 to VPS 103 and the called party 137 provides a connection confirmation 567 to VPS 103 via the voice-over-IP gateway 131. At this point, the voice-over-IP gateway 131 interfaces a voice call leg 569 with the calling party 101 and a voice-over-IP call leg 571 with the called party client 139. These requests, responses, notifications, and confirmations may be carried out using computer generated messages or using human-intelligible voice prompts and Dual Tone Multi-Frequency (DTMF or �touch tone�) or spoken responses. Upon conclusion of the call, the call between the calling party 101 and the called party 137 is torn down in steps 573-581 substantially as described herein above with respect to steps 267-275 in FIG. 2B. In the preceding description of FIGS. 2A-5B, billing system 123 was shown to participate in collecting information indicative of usage activity in the communcations system and in authorizing activity based on whether such activity could be paid for in some manner. It should be noted that various elements in FIG. 1 may report a variety of indications to billing system 123 indicating usage of the system which may be billable. The billing system may note these occurrences and determine charges associated with the usage. Furthermore, as depicted in FIG. 2A-2B and others, billing system 123 may also participate in authorization or metering of activity in the system based upon whether a valid account exists to which charges may be applied. Some types of activity or events in the system relate to invocation of certain actions or features for which charges may be applicable. For example, a calling party (or some other entity to be billed) might be charged for each time they contact the system, each time they use the system to verify presence status for a called party or for each attempt to establish instant communications with a called party. A calling party might also incur fees for having the system map a first identifier, such as a telephone number, to a second identifier, such as an instant messaging screen name. A calling party might be charged differently for invocation of textual messaging versus voice communications. A calling party might be charged a fee each time a translator is engaged to enable telephony-to-instant-communications call completion. A calling party may even be charged for requesting information about the balance on an account. Other types of activity in the system may relate to quantifying usage of system resources. For example, charges may be applied based upon a time duration of a communications session, a volume of data or traffic handled by the system, or a quantity of translation performed. A third possibility for billable activity in the system relates to options and features and subscribed services. Options or features may relate to class of service provided by the system or to customizability. In particular, parties using the system might pay extra to control the translator function in ways such as selecting languages to be used during translation, providing support for �emoticons� or selecting voice characteristics to properly represent the gender or other characteristics of the party who is using textual messaging, or establishing of common phrases, utterances, or signals including, for example, one or more DTMF signals to signify meaning and therefore enhance communications. Another option that might be billable is automatic notification of balance or charges as a party uses the system. In this third category, it is likely that the billing system mostly serves to authorize activity based upon options selected by the user and/or the status of an account that is to pay for the options. Referring now to FIGS. 7A through 9D, three processes are shown depicting three different call experiences that might be provided to a calling party by the system of FIG. 1. It should be noted at the outset that processes 700, 800 and 900 are merely illustrative and not intended to limit the ways in which the present invention may be realized. Many adaptations and variations are possible. For example, throughout processes 700, 800 and 900, the involvement of billing determinations may occur at any juncture in the service processing subject to how one desires to have the system operate. In actual practice, the offering of alternative modes of communication, the soliciting of information from a party and the retrieval of information from databases and such may differ in details and in sequence from what is shown in these examples without affecting the spirit and scope of the present invention. Furthermore, at points where these processes may involve determining, for example, preferences of the communicating parties or billing information, such information may be obtained from a database, such as capabilities server 117, so that user profile information replaces or augments user input. In other words, it is possible for configurable profile information associated with a party to be maintained in a database or the like and to be applied to automating some aspects of how system 100 provides service to calling party 101 and called party 137. For example, called party 137 may desire to have all inbound calls diverted to called party client 139 during certain times of day. This preference information may reside in capabilities server 117 or elsewhere and may be automatically retrieved and applied in, for example, steps 710 and 714 described below. Called party 137 may have billing information or preferences similarly maintained in a database accessible to system 100 so that any steps requiring billing input are automatically carried out without requiring input from the called party. In general, the manner and sequence in which the activities of processes 700, 800 and 900 may be controlled by profile information associated with parties using system 100. Service processing may also be affected by coupling to other systems or elements that maintain and use service-affecting profile information. For example, SIP server 135 may maintain profile information relating to called party 137 or called party client 139. Intelligent presence gateway 105 may coordinate with SIP server 135 so that features such as �Find me�Follow me� implemented in a SIP-controlled environment may be carried out in coordination with other aspects of system 100. In accordance with a first call experience, a calling party reaches the voice processing system 103 by telephone with the original intent of reaching a called party by telephone connection. For example, the calling party may dial �1-800-COLLECT� as they would normally do to use VPS 103 to place a collect call to the called party. The system proceeds to process the collect call as usual. If the call cannot be completed in this manner, then, in accordance with the present teachings, the system investigates the possibility of connecting the calling party to the called party via instant communications. This scenario is described below in conjunction with FIGS. 7A-7D. In accordance with a second call experience, the calling party reaches the voice processing system by calling a specific telephone, such as �1-800-GET-CHAT�, for the express purpose of initiating instant communications with the called party. This scenario is described below in conjunction with FIGS. 8A-8D. In accordance with a third call experience, the calling party directly calls the called party by telephone in the usual manner. When it is detected that the called party telephone is busy or ringing without being answered, the calling party is connected to the voice processing system so that the caller may be offered alternative ways of reaching the called party. In FIGS. 7A through 7D, a process 700 is depicted whereby an enhanced services system may offer a caller an option of communicating to an instant communications client of a called party in accordance with an exemplary embodiment of the present invention. Process 700 particularly illustrates a variety of alternatives and conditional steps in accordance with an exemplary embodiment of the present invention. Referring to FIG. 7A, process 700 commences at step 702 upon a caller calling a voice processing system, such as by calling party 101 contacting an operator 52 or other interactive respondent within voice processing system 103. Next, in step 704, the caller specifies to the operator a particular called party that the caller desires to contact. For example, the called party may be specified by name or by phone number, if known. In the case of an automated or semi-automated response system, the caller may provide the called party information via DTMF tones or by other transmission of signals, perhaps even by speaking into a speech recognizing system that can determine the name or number data being conveyed by the caller. Proceeding to step 706, the operator validates the caller's request by, for example, ensuring the caller has expressed a valid telephone number according to the North American Numbering Plan. Of course, the validation may be performed automatically especially if, for example, the telephone number of the called party is input as DTMF tones or other signals from the caller in step 704. The validating step 706 may comprise validating the authority of the caller to access specific types of services offered via voice processing system 103. Validation step 706 may also comprise ensuring that the operator clearly understands what is intended by the caller. Ways of handling inbound calls that fail to be validated are well known or easily foreseen by those of ordinary skill in the relevant art and so are not elaborated upon here. Assuming that, in step 706, the caller's request is valid, then process 700 continues at step 708 wherein the operator attempts to reach the called party by telephone, as represented called party phone 138 in FIG. 1. Thus far, process 700 is similar to the placement of a collect call. In step 710, it is determined whether the operator has been successful in establishing contact with the called party or at least with someone who has answered the telephone. If successful contact has been made, then execution proceeds to step 716 to determine if the answering party will accept the call. Typically, in the case of a collect call, the identity of the caller will be announced to the called party and the operator or voice processing system will ask the called party if they will accept the call (along with the charges for the call, if applicable). If the caller accepts the call in step 716, then, in step 718, the caller is connected to the called party and usage-based billing may commence. Once the call is established, the operator is no longer needed on the line and, in practice, the connections, operator(s) and other resources employed within the services platform to initiate the call are released. In FIG. 1, for example, bridging switch 54 may typically be used to keep phones 102 and 138 connected, while allowing VPS 103 to disengage via a well-known release link trunk 55 coupling telephone circuits between bridging switch 54 and VPS 103. (For reference, one may consult U.S. Pat. No. 5,787,150 which shows a bridging switch and describes typical operation of a release link trunk.) Accordingly, then, after establishing the connection among parties in step 718, process 700 (following label �D�) proceeds to step 770 (FIG. 7D) causing the operator to be disengaged from the bridging switch. Process 700 then terminates, having successfully connected the parties and effectively handling the caller's request to contact the called party. Returning to step 710, if the operator could not reach the called party by phone, then execution proceeds to step 712 wherein the operator informs the caller that the called party could not be reached by phone. Next, in step 713, the operator explores whether ther are any other ways that the caller might communicate with the called party, such as by instant messaging or by depositing a voice mail message. The operator's exploration of other possibilities allows the operator to present appropriate options to the caller and may entail checking databases to see if, for example, the caller or called party are subscribed to various service options, such as voicemail, chat call completion, paging, etc., accessible to the operator. In step 714, then, based on the operator's findings, a determination is made as to whether a chat session of some sort is a viable alternative by which the caller might communicate with the called party. If instant communications, such as textual chat, is a viable alternative, then process 700 continues to step 720 (FIG. 7B) and other steps to attempt to establish communications between the parties through an instant communications mechanism. Specifically, in step 720, it is determined whether the operator already has access to information by which to contact the party through instant communications, such as by a chat interface. For example, it is conceivable that the operator may have access to a database mapping telephone numbers or personal names to �screen names� used to identify parties in an instant messaging system. On the other hand, the operator may not have such information and may have to solicit input from the caller. Thus, in step 720, if the operator does not have access to sufficient information to reach the called party by instant messaging, then step 722 is performed wherein the operator makes known to the caller that alternatives, such as chat, may be available and the operator asks the caller for contact information, if known. In step 724, if the caller wants to attempt a chat session as an alternative then execution proceeds to step 726, wherein the caller provides contact information by which the operator may attempt to reach the called party by chat or instant messaging. In step 728, the operator uses the contact information obtained in step 726 to then determine if the called party is presently available through a chat system. Referring to FIG. 1, this action might be represented by VPS 103 requesting presence information from watcher process 109 or fetcher process 111 over connection 10. As a called party logs onto client 137, client 137 may register its presence with presence server 119, making the communications status of client 137 available to watcher process 109 or fetcher process 111. If, in step 728, it is determined that the called party is not present or unavailable through a chat session, then, in step 730, the operator informs the caller that the called party is not accessible by chat and execution proceeds, via the connector labeled �C�, to step 760 to possibly provide other alternatives as will be described in greater detail below. Likewise, if, in step 724, it is determined that the caller does not want to try a chat session, then execution also proceeds to step 760 as described below. Otherwise, if in step 728, it is determined that the called party is present and available via chat, then execution proceeds, following the connector labeled �B�, to step 740 of FIG. 7C to attempt a chat session with the called party as will be described shortly. Returning to step 720, if the operator does have chat information for the called party without need of receiving same from the caller, then execution moves to step 732 to determine if the called party is present, using a similar manner to that described in step 728. If the called party is not present, then optionally, in step 733, the operator informs the caller that the party is inaccessible by chat. Thereafter, execution proceeds, following the connector labeled �C� to step 760 to possibly provide other alternatives as will be described in greater detail below. Otherwise, in step 732, if the party is available, then in step 734, the operator offers the caller the option of engaging in chat communications with the called party. In step 736, if the caller declines to use the chat alternative, then execution proceeds, following the connector labeled �C�, to step 760 to possibly provide other alternatives as will be described in greater detail below. If, on the other hand, the caller does elect to try a chat session in step 736, then process 700 continues, following along the connector labeled �B�, to step 740 of FIG. 7C to attempt a chat session with the called party. In FIG. 7C, process 700 continues with attempting to establish a chat session between the caller and the called party. At step 740, coming from either steps 728 or 736, the operator performs a preparatory step in obtaining information from the caller as to how they wish to be announced to the called party. In step 742, the operator contacts the called party (or �callee�) and invites the callee to participate in a chat session with the caller. In this invitation, the operator introduces the caller using the announcement information obtained in step 740. In step 744, the called party's response to the invitation is determined and if the invitation is declined, then execution proceeds, following the connector labeled �C�, to step 760 to possibly provide other alternatives as will be described in greater detail below. Otherwise, if the called party accepts the chat invitation in step 744, then step 746 is executed to determine if the called party client supports voice communications (voice-enabled chat). This may be determined by retrieving profile information from, for example, the capabilities server 117 or by directly querying the called party 137 or called party client 139. If so, then execution proceeds to step 750 wherein the operator asks the called party if they would prefer to engage in voice chat or use text-based chat. In step 752, the called party responds by electing either text or voice. If the callee selects a textual session, then execution proceeds with step 748 wherein a text chat session is established between the parties through a voice/text translator (see translator 125) and billing for the session, if applicable, is initiated. Step 748 is also undertaken if the called party client is found to not support voice sessions in step 746. Returning to step 752, if the callee elects to engage in voice communications through a voice-enabled chat session, then, in step 754, the parties are connected to carry on voice communications. Referring to FIG. 1, this may be represented by connecting the calling party phone 101 through voice processing system 103 or bridging switch 54 to VoIP gateway 131. This connection is completed by an RTP data connection through IP network 133 to called party client 139. This connection may be established by SIP signaling among SIP user agent 56, VoIP gateway 131 and SIP server 135, or by using H.323-type protocols or other suitable mechanisms. Whether a voice connection as in step 754 or a textual chat session as in step 748 ensues, execution then proceeds, along the connector labeled �D�, to step 770 wherein the operator is disengaged from the �call� and then the handling of the caller's original request is concluded in step 772. Referring to FIG. 7D, many determinations in process 700 may result in execution of step 760, generally when attempts to establish telephone or chat messaging to a party have been unsuccessful. In step 760, it is determined if there are yet other alternatives for communicating to the called party, such as paging or voice mail. If not, then in step 768, the caller is informed that the called party is not reachable by any further means beyond what may have already been offered to the caller. Processing then proceeds to step 770 to decouple the caller from the operator which, in this instance, essentially disconnects the caller. If the condition tested in step 760 is found to be true, then, in step 762, such alternatives indicated as available in step 760 are offered to the caller by the operator. In step 764, it is determined whether the caller elects to use an alternative so offered. If so, then step 766 is performed wherein the caller is �connected� in a sense to the alternative, meaning that the caller may be forwarded to a voice mail system or become coupled to a paging application, to name a few examples. Returning to step 764, if the caller elects not to use offered alternatives, then processing continues at step 770 to essentially disconnect the operator from the caller. FIGS. 8A-8D depict a process 800 whereby a caller may contact an enhanced services system to establish communications to a messaging client of a called party in accordance with an exemplary embodiment of the present invention. In FIG. 8A, process 800 commences in step 802 when a caller contacts a voice processing system for the purpose of establishing a chat session with a �called party.� In contrast to the scenario described in process 700 wherein the party initially desired to establish a telephone call, process 800 relates to the caller preferring at the outset to establish a chat session with the called party. The caller might place a telephone call to a �1-800-GET-CHAT� telephone number, for example, to signify to the communications system the intent or desire to preferably establish communications via the instant communications client. Where the VPS 103 supports both process 700 and process 800, the number dialed by the caller to reach the system, or the trunk group by which the call comes to the system, may be used to differentiate handling of the call. The communications system may accordingly, act first to establish contact via a instant communications client in preference to other forms of communication that may be available. Upon the caller reaching the system in step 802, an operator, either manual or automatic or a combination thereof, is connected to the caller and, in step 804, obtains information from the caller about the party they are trying to reach by chat. The operator may also collect other information such as account information to which the use of the system may be billed. In step 806, the operator validates at least the contact information provided by the caller and then verifies whether the party is present on a messaging system and determines capabilities for the destination party. Referring to FIG. 1, operator 52 may cause VPS 103 to obtain timely presence information from fetcher process 111 or watcher process 109 representing the available status of called party client 139. In step 808, it is determined, based on the inquiry of step 806, whether or not the called party is present via a chat messaging client. If presence is not detected, then process 800 continues with step 816 wherein the operator informs the caller that the called party is not accessible, at least not by chat. Thereafter, process 800 continues, following the connector labeled �A�, to step 820 to offer the caller the option of placing a telephone call, as will be described in greater detail below. Returning to step 808, if it is determined that the called party is present and available via chat messaging, then process 800 continues with step 810 wherein the operator obtains information proceeds to establish a chat session between the caller and the called party. In step 810, the operator performs a preparatory step in obtaining information from the caller as to how they wish to be announced to the called party. In step 812, the operator contacts the called party (or �callee�) and invites the callee to participate in a chat session with the caller. In this invitation, the operator introduces the caller using the announcement information obtained in step 810. Then, in step 814, the operator determines whether the callee accepts the offered chat communications. If not, then step 816 is performed wherein the operator informs the caller that the called party is not accessible, at least not by chat. Thereafter, process 800 continues, following the connector labeled �A�, to step 820 to offer the caller the option of placing a telephone call as will be described in greater detail below. Returning to step 814, if the caller does accept the invitation to communicate with the caller via chat, then process 800 continues, following the connector labeled �B�, to step 840 (FIG. 8C) to initiate the chat session. Referring to FIG. 8C, step 840 involves the operator determining whether or not the called party messaging client supports voice communications. If not, then a textual chat session is the only option for communicating with the called party and process 800 continues at step 850 wherein the operator or the service provider system verifies how the ensuing chat session will be billed, if applicable. As with other types of services, billing arrangements may include such arrangements as subscription, collect calling, prepaid calling, third-party pays, billing to credit card, etc. Once any necessary billing arrangements are made in step 850, then, in step 852, the operator causes the parties to be connected together through a two-way voice/text translator and billing, if applicable, is initiated. This connection may be achieved in a manner described earlier in conjunction with FIG. 1 and FIG. 2B. After connecting in step 852, then process 800 proceeds, following the connector labeled �D� to disengage the operator from the call in step 870. In this scenario, the VPS 103 may remain connected to the bridging switch and provide pass through to IIX 125. Alternatively, IIX 125 may be assigned some ports on the bridging switch and once the connection is made, the operator of VPS 103 may be released from the call. Returning to step 840, if the callee's messaging client is found to support voice communications, then process 800 continues execution with step 842 wherein the operator asks the callee to select a voice-enabled chat session or a textual chat session. In step 844, the callee's selection is determined and affects whether a voice session is established or textual chat session is established, the latter via steps 850 and 852 as already described. If the callee selects voice-enabled chat in step 844, then process 800 proceeds with step 846 to secure any necessary billing arrangements and then step 848 to establish the voice chat connection. Referring to FIG. 1, this connection may involve, for example, one or more of VPS 103, bridging switch 54, VoIP gateway 131 and IP network 133. After making the connection, process 800 proceeds, following the connector labeled �D�, to disengage the operator from the call in step 870. Referring now to FIG. 8B, steps 820 through 832 relate to offering the caller an option of placing a telephone call to the called party in lieu of the chat session the caller originally desired. This option may be available to some types of service providers who offer telephony services or have business arrangements through telephone service providers. In step 820, the operator offers the caller the option of trying to reach the called party by telephone, responsive to the previous attempt to chat with the called party having been unsuccessful. In step 822, the caller's preference for a telephone call is determined. If the caller declines to try a telephone connection with the called party, then process 800 proceeds, following the connector labeled �C�, to explore other alternatives by which the caller might be able to communicate with the called party. Otherwise, if, in step 822, the caller elects to try reaching the called party by phone, then, in step 824, the operator obtains information as to how the call is to be billed and then places the call to the called party. In step 826, a determination is made as to whether or not the callee answers the phone and accepts any applicable charges, such as in a collect call scenario. If the called party, answers and otherwise accepts the call, then steps 832, 870 and 872 are performed to connect the call and begin billing, if applicable, disconnect the operator from the call and conclude the processing of process 800 in fulfillment of the caller's request. Returning to step 826, if the called party does not answer, or answers and declines the call from the operator, then in step 830, the operator informs the caller that the callee is unavailable by phone. Thereafter, process 800 proceeds, following the connector labeled �C�, to explore other alternatives by which the caller might be able to communicate with the called party. With reference now to FIG. 8D, steps 860 through 866 relate to determining if yet other alternatives may be offered to the caller for communicating with the called party. Such alternatives might include voice mail, paging, e-mail transcription, etc. In step 860, the operator examines other such possibilities based on communications alternatives available to the operator through system 103 or based upon services for which the parties may be configured or subscribed. If no alternatives are available then, in step 868, the called party is declared unreachable and the operator will likely notify the caller that no further options remain. The session between caller and operator will then terminate, at least by the action of step 870, and then process 800 is concluded in step 872. If at least one alternative is found available in step 860, then in step 862, the operator offers such alternative(s) to the caller. In step 864, if the caller elects an alternative, then the operator connects the caller to, or otherwise invokes, the alternative in step 866. In the caller declines any remaining alternatives presented in step 862, then the decision step 864, bypasses step 866 and proceeds directly to terminate the call, perhaps after a �bye� from the operator. Once the caller's selection is made in step 864 and any appropriate alternative is invoked, then the operator is disconnected from the caller in step 870 and then process 800 is concluded in step 872. FIGS. 9A-9D describe a process 900 whereby a caller places a telephone call directly to a desired called party and, when the call goes unanswered or is otherwise configured to receive alternative processing, the call is diverted to a voice processing system to offer the caller messaging and other alternatives by which to reach the same called party. Process 900 begins with step 902 upon the system detecting or receiving indication that a telephone call has gone unanswered. It is also conceivable that another system, such as telephone network 80, may detect the unanswered call and merely redirect the call to VPS 103. Methods by which a system may detect or be informed of a �no answer� event are known in the industry. This is evidenced among local exchange carriers in the United States, such as Qwest Communications International, Inc., who perform a feature whereby, when a telephone goes unanswered after several rings, an automated voice prompt bridges onto the line and offers, for a fee, to continue trying to reach the called party and to ring the caller's telephone when the called party eventually answers. In the present discussion, an unanswered phone may be due to a so-called �ring�no answer� event or a �line is busy� event. A telephone caller may also encounter a disconnected line, an �all circuits busy� condition or other problems preventing the call from being completed. In any case, process 900 continues with step 904 wherein the call is diverted to an operator within the service provider system. In step 906, the operator greets the caller and offers to assist in reaching the party by other means, such as by a chat session. In step 907, the operator explores available alternatives, based on communications alternatives available to the operator through system 103 or based upon services for which the parties may be configured or subscribed. In step 908, it is determined whether, according to information gleaned in step 907, chat messaging is a viable possibility for reaching the called party. Chat messaging may be impermissible, for example, if the system requires either or both of the caller and called party to be subscribed users of such service and neither of them are subscribed. If chat is not an option, then process 900 continues, following the connector labeled �C�, to step 960 of FIG. 9D to pursue other possible communications options. If the system requires either or both of the caller and called party to be subscribed users of such service and neither of them are subscribed. If chat is not an option, then process 900 continues, following the connector labeled �C�, to step 960 of FIG. 9D to pursue other possible communications options. Otherwise, if, in step 908, chat messaging is seemingly viable, then process 900 continues, following the connector labeled �A�, to step 920 to attempt to establish a chat session with the called party. The remainder of process 900 as depicted in FIGS. 9B, 9C and 9D is essentially identical to corresponding steps depicted in FIGS. 7B, 7C and 8D, respectively. As will be readily apparent to persons of ordinary skill in the relevant art, any of the functional elements, systems and processes depicted in FIGS. 1 through 9D may be implemented in various ways using, for example, suitably equipped data processing systems or computing environments. Such implementations may comprise hardware, firmware, software, or combinations thereof, to accomplish intended functions in accordance with the teachings of the present invention. For example, any or all of voice processing system 103, billing system 123, intelligent information translator 125 and intelligent presence gateway 105, or functional subsystems depicted therein, may be implemented as processes in a program-controlled computing environment. Processes depicted in FIGS. 2A through 9D may be implemented wholly or partially as processing threads occurring within a computer processor under software and/or firmware control. A given process may be implemented in a distributed fashion among multiple physical processors or multiple logical processing threads. A single processor may participate in implementing multiple instances or multiple types of the processes shown. Any of the functions shown, or the hardware used to implement these functions, may be distributed among remote locations or may be collocated. It will also be appreciated that connectivity among elements for carrying control signals, telephony-style signaling, bearer channel signals and messaging traffic and the like, may be accomplished via communications through a network or a shared bus or shared memory resources or by inter-process communications. Even signals representing telephone audio signals may be conveyed to processing equipment in the form of data through a bus or network. Methods and devices for converting among analog audio signals and digital data are well known and are not explicitly shown in FIG. 1, although it is common that telephone network 80 or VPS 103 are equipped to perform these conversions. Adaptation to external systems, such as the PSTN as represented by telephone network 80, may be accomplished by the use of well-known computer-telephony adapter cards (as those made by Dialogic Communications Corporation), commercially available automatic call distributors (ACDs) and Private Branch Exchange (PBX) equipment. An exemplary arrangement of computing hardware suitable for implementing functional elements and processes in accordance with the present invention will now be described in conjunction with FIG. 6, although it should be understood that aspects of the present invention may be embodied in other ways. Hardware Overview FIG. 6 illustrates a computer system 600 upon which an embodiment according to the present invention can be implemented. The computer system 600 includes a bus 601 or other communication mechanism for communicating information and a processor 603 coupled to the bus 601 for processing information. The computer system 600 also includes main memory 605, such as a random access memory (RAM) or other dynamic storage device, coupled to the bus 601 for storing information and instructions to be executed by the processor 603. Main memory 605 can also be used for storing temporary variables or other intermediate information during execution of instructions by the processor 603. The computer system 600 may further include a read only memory (ROM) 607 or other static storage device coupled to the bus 601 for storing static information and instructions for the processor 603. A storage device 609, such as a magnetic disk or optical disk, is coupled to the bus 601 for persistently storing information and instructions. The computer system 600 may be coupled via the bus 601 to a display 611, such as a cathode ray tube (CRT), liquid crystal display, active matrix display, or plasma display, for displaying information to a computer user. An input device 613, such as a keyboard including alphanumeric and other keys, is coupled to the bus 601 for communicating information and command selections to the processor 603. Another type of user input device is a cursor control 615, such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor 603 and for controlling cursor movement on the display 611. According to one embodiment of the invention, call processing is provided by the computer system 600 in response to the processor 603 executing an arrangement of instructions contained in main memory 605. Such instructions can be read into main memory 605 from another computer-readable medium, such as the storage device 609. Execution of the arrangement of instructions contained in main memory 605 causes the processor 603 to perform the process steps in accordance with any or all of the processes described or implied herein. One or more processors in a multi-processing arrangement may also be employed to execute the instructions contained in main memory 605. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the embodiment of the present invention. Thus, embodiments of the present invention are not limited to any specific combination of hardware circuitry and software. The computer system 600 also includes a communication interface 617 coupled to bus 601. The communication interface 617 provides a two-way data communication coupling to a network link 619 connected to a local network 621. For example, the communication interface 617 may be a digital subscriber line (DSL) card or modem, an integrated services digital network (ISDN) card, a cable modem, a telephone modem, or any other communication interface to provide a data communication connection to a corresponding type of communication line. As another example, communication interface 617 may be a local area network (LAN) card (e.g. for Ethernet� or an Asynchronous Transfer Model (ATM) network) to provide a data communication connection to a compatible LAN. Wireless links can also be implemented. In any such implementation, communication interface 617 sends and receives electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information. Further, the communication interface 617 can include peripheral interface devices, such as a Universal Serial Bus (USB) interface, a PCMCIA (Personal Computer Memory Card International Association) interface, etc. Although a single communication interface 617 is depicted in FIG. 6, multiple communication interfaces can also be employed. The network link 619 typically provides data communication through one or more networks to other data devices. For example, the network link 619 may provide a connection through local network 621 to a host computer 623, which has connectivity to a network 625 (e.g. a wide area network (WAN) or the global packet data communication network now commonly referred to as the �Internet�) or to data equipment operated by a service provider. The local network 621 and the network 625 both use electrical, electromagnetic, or optical signals to convey information and instructions. The signals through the various networks and the signals on the network link 619 and through the communication interface 617, which communicate digital data with the computer system 600, are exemplary forms of carrier waves bearing the information and instructions. The computer system 600 can send messages and receive data, including program code, through the network(s), the network link 619, and the communication interface 617. In the Internet example, a server (not shown) might transmit requested code belonging to an application program for implementing an embodiment of the present invention through the network 625, the local network 621 and the communication interface 617. The processor 603 may execute the transmitted code while being received and/or store the code in the storage device 609, or other non-volatile storage for later execution. In this manner, the computer system 600 may obtain application code in the form of a carrier wave. The term �computer-readable medium� as used herein refers to any medium that participates in providing instructions to the processor 605 for execution. Such a medium may take many forms, including but not limited to non-volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as the storage device 609. Volatile media include dynamic memory, such as main memory 605. Transmission media include coaxial cables, copper wire, and fiber optics, including the wires that comprise the bus 601. Transmission media can also take the form of acoustic, optical, or electromagnetic waves, such as those generated during radio frequency (RF) and infrared (IR) data communications. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, CDRW, DVD, any other optical medium, punch cards, paper tape, optical mark sheets, any other physical medium with patterns of holes or other optically recognizable indicia, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave, or any other medium from which a computer can read. Various forms of computer-readable media may be involved in providing instructions to a processor for execution. For example, the instructions for carrying out at least part of the present invention may initially be borne on a magnetic disk of a remote computer. In such a scenario, the remote computer loads the instructions into main memory and sends the instructions over a telephone line using a modem. A modem of a local computer system receives the data on the telephone line and uses an infrared transmitter to convert the data to an infrared signal and transmit the infrared signal to a portable computing device, such as a personal digital assistant (PDA) or a laptop. An infrared detector on the portable computing device receives the information and instructions borne by the infrared signal and places the data on a bus. The bus conveys the data to main memory, from which a processor retrieves and executes the instructions. The instructions received by main memory can optionally be stored on storage device either before or after execution by processor. For example, although aspects of the present invention have been described with respect to computer systems executing software that directs the functions of the present invention, it should be understood that present invention may alternatively be implemented as a program product for use with a data processing system. Programs defining the functions of the present invention can be delivered to a data processing system via a variety of signal-bearing media, which include, without limitation, non-rewritable storage media (e.g., CD-ROM), rewritable storage media (e.g., a floppy diskette or hard disk drive), and communication media, such as digital and analog networks. It should be understood, therefore, that such signal-bearing media, when carrying or encoding computer readable instructions that direct the functions of the present invention, represent alternative embodiments of the present invention. While the present invention has been described in connection with a number of embodiments and implementations, the present invention is not so limited but covers various obvious modifications and equivalent arrangements, which fall within the purview of the appended claims. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7035923Apr 10, 2002Apr 25, 2006Nortel Networks LimitedPresence information specifying communication preferencesUS7050788 *May 20, 2004May 23, 2006Bellsouth Intellectual Property CorporationMethods, systems, and storage mediums for facilitating a billing point of interconnection in a telecommunications environmentUS7139797Apr 10, 2002Nov 21, 2006Nortel Networks LimitedPresence information based on media activityUS7219153 *Dec 2, 2002May 15, 2007Cisco Technology, Inc.Methods and apparatus for distributing contentUS7382868 *Apr 2, 2003Jun 3, 2008Verizon Business Global LlcTelephony services system with instant communications enhancementsUS7555108 *Oct 1, 2002Jun 30, 2009Nortel Networks LimitedPresence information for telephony usersUS7613452Mar 10, 2005Nov 3, 2009Joseph Allen PenceSystem and method for providing communications servicesUS7623632 *Aug 26, 2004Nov 24, 2009At&T Intellectual Property I, L.P.Method, system and software for implementing an automated call routing application in a speech enabled call center environmentUS7701925Jul 28, 2000Apr 20, 2010TekelecPresence registration and routing nodeUS7782839 *May 10, 2004Aug 24, 2010Canon Kabushiki KaishaCommunication terminal, control method of the same, and control program of the sameUS7907713Oct 25, 2006Mar 15, 2011TekelecMethods, systems, and computer program products for using a presence database to deliver enhanced presence information regarding communications made to or from a presentityUS7912207 *Dec 21, 2005Mar 22, 2011Avaya Inc.Data messaging during telephony callsUS7929682 *Mar 4, 2005Apr 19, 2011Palus A31, LlcSystem and method for providing communications servicesUS7933608 *Mar 11, 2005Apr 26, 2011TekelecMethods, systems, and computer program products for providing presence gateway functionality in a telecommunications networkUS7970108 *Oct 2, 2009Jun 28, 2011Palus A31, LlcSystem and method for providing communications servicesUS8027839Dec 19, 2006Sep 27, 2011Nuance Communications, Inc.Using an automated speech application environment to automatically provide text exchange servicesUS8060565 *Jan 31, 2007Nov 15, 2011Avaya Inc.Voice and text session converterUS8078191 *Jan 10, 2008Dec 13, 2011Synchronica PlcSystem and method of updating presence informationUS8098810Feb 6, 2008Jan 17, 2012Fonality, Inc.Intelligent presence management in a communication routing systemUS8175043 *Dec 20, 2007May 8, 2012Verizon Patent And Licensing Inc.Method and system for establishing disparate connection paths from a mobile user device to a base station through a mobile peer-to-peer (PTP) networkUS8204052May 2, 2005Jun 19, 2012Tekelec, Inc.Methods, systems, and computer program products for dynamically coordinating collection and distribution of presence informationUS8228925 *Dec 14, 2005Jul 24, 2012Alcatel LucentInteractive voice response system for online and offline charging and for multiple networksUS8260317Nov 17, 2011Sep 4, 2012Synchronica PlcSystem and method of updating presence informationUS8295272Sep 21, 2009Oct 23, 2012Verizon Laboratories Inc.Methods and systems for presence-based telephony communicationsUS8320365 *Jan 12, 2010Nov 27, 2012Verizon Patent And Licensing Inc.Presence based telephonyUS8325884 *Nov 18, 2009Dec 4, 2012At&T Intellectual Property I, L.P.Method, system and software for implementing an automated call routing application in a speech enabled call center environmentUS8341535Mar 10, 2008Dec 25, 2012Fonality, Inc.System and method for distributed communication control within an enterpriseUS8379832May 3, 2007Feb 19, 2013Fonality, Inc.Universal queuing for inbound communicationsUS8422487Apr 19, 2010Apr 16, 2013Tekelec, Inc.Presence registration and routing nodeUS8495653Mar 10, 2008Jul 23, 2013Fonality, Inc.System and method for event driven browser launchUS8499246Mar 10, 2008Jul 30, 2013Fonality, Inc.System and method for providing single click enterprise communicationUS8515749 *May 20, 2009Aug 20, 2013Raytheon Bbn Technologies Corp.Speech-to-speech translationUS8571202Jan 10, 2013Oct 29, 2013Fonality, Inc.Universal queuing for inbound communicationsUS8645575 *Mar 31, 2004Feb 4, 2014Apple Inc.Apparatus, method, and computer program for performing text-to-speech conversion of instant messages during a conference callUS8654731Feb 28, 2012Feb 18, 2014Verizon Patent And Licensing Inc.Method and system for establishing disparate connection paths from a mobile user device to a base station through a mobile peer-to-peer (PTP) networkUS8693659Jul 11, 2007Apr 8, 2014Fonality, Inc.System and method for centralized presence management of local and remote usersUS8719386Jan 8, 2009May 6, 2014Fonality, Inc.System and method for providing configuration synchronicityUS8780925Aug 17, 2006Jul 15, 2014Fonality, Inc.Mobile use of a PBX systemUS8781081 *Apr 21, 2005Jul 15, 2014At&T Intellectual Property I, L.P.Presence management systemUS8787548Aug 31, 2012Jul 22, 2014Fonality, Inc.System and method for distributed communication control within an enterpriseUS20070189264 *Jun 29, 2006Aug 16, 2007Lucent Technologies Inc.Proxy telephone number system for communication network subscribersUS20080205628 *Mar 1, 2007Aug 28, 2008International Business Machines CorporationSkills based routing in a standards based contact center using a presence server and expertise specific watchersUS20100063800 *Nov 18, 2009Mar 11, 2010At&T Intellectual Property I, L.P.Method, System and Software for Implementing an Automated Call Routing Application in a Speech Enabled Call Center EnvironmentUS20100115019 *Jan 12, 2010May 6, 2010Michael Alan WeintraubPresence based telephonyUS20100296408 *Jul 26, 2010Nov 25, 2010Derek MitsumoriSystem and method for monitoring communications in a networkUS20100299147 *May 20, 2009Nov 25, 2010Bbn Technologies Corp.Speech-to-speech translation* Cited by examinerClassifications U.S. Classification379/114.01International ClassificationH04M3/533, H04L12/14, H04M3/53, H04M7/12, G10L13/04, G10L19/00, G10L15/26, H04M3/493, H04M3/46, H04M17/00, H04L12/56, G06Q20/08, H04M7/00, H04M15/00, H04L12/58, H04M3/42, H04L29/08, H04L12/18, H04L29/06Cooperative ClassificationH04L65/1006, H04L29/06, H04M15/63, H04M15/08, H04M2215/725, H04M3/4931, H04M3/42127, H04M15/07, H04M15/56, H04M3/53308, H04M2203/4536, H04L65/1016, H04M17/00, H04L12/14, H04L12/589, H04M2215/7263, H04L51/066, H04L45/308, H04M2242/30, H04M2203/2066, H04M3/5322, H04M3/46, G10L15/265, H04M15/83, G06Q20/085, H04M3/533, H04M15/7655, H04M15/00, H04M15/77, H04M2201/60, H04L51/36, H04M15/09, H04L12/581, H04M15/772, H04M2203/4509, H04M2215/62, H04M2215/202, H04L65/1069, H04M3/42229, H04M2215/66, H04M15/8292, H04M2215/54, H04M2215/82, H04M7/0003, H04L65/80, H04M15/57, H04L12/58, H04L65/4007, H04M2215/7254, H04L12/5835, G10L13/043, H04L29/06027, H04M2215/44, H04L51/04, H04L12/1822, H04M2215/208, H04L12/1827, H04L12/1403, H04M15/51, H04M2215/64, H04M15/55, H04L12/1813, H04M3/465, H04M7/12, H04L69/329, H04L67/14, H04L69/08, H04L67/24European ClassificationH04M15/83, H04M15/82Q, H04M15/09, H04M15/77, H04M15/63, H04M15/765B, H04M15/77B, H04M15/56, H04M15/08, H04L29/06M2H2, H04M15/07, H04L12/14, H04M15/57, H04M3/42D, H04M3/46M, G10L13/04U, H04L29/06M8, H04L29/08A7, G06Q20/085, H04L29/06M2S1, H04L45/308, H04L29/06C2, H04L12/18D, H04M15/55, G10L15/26A, H04L29/06M4A, H04M17/00, H04L12/14A, H04M3/46, H04M15/51, H04L29/08N13, H04L12/18D2, H04M3/53T, H04L51/04, H04L29/08N23, H04M3/42M, H04M15/00, H04L12/58, H04M7/00B, H04L12/58B, H04L29/06, H04L12/58ULegal EventsDateCodeEventDescriptionApr 22, 2014ASAssignmentOwner name: VERIZON PATENT AND LICENSING INC., NEW JERSEYEffective date: 20140409Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VERIZON BUSINESS GLOBAL LLC;REEL/FRAME:032734/0502Mar 29, 2007ASAssignmentOwner name: MCI, LLC, NEW JERSEYFree format text: MERGER;ASSIGNOR:MCI, INC.;REEL/FRAME:019086/0063Effective date: 20060109Owner name: VERIZON BUSINESS GLOBAL LLC, VIRGINIAFree format text: CHANGE OF NAME;ASSIGNOR:MCI, LLC;REEL/FRAME:019086/0069Effective date: 20061120Oct 7, 2005ASAssignmentOwner name: MCI, INC., VIRGINIAFree format text: CHANGE OF NAME;ASSIGNOR:WORLDCOM, INC.;REEL/FRAME:016649/0488Effective date: 20040419Apr 2, 2003ASAssignmentOwner name: WORLDCOM, INC., MISSISSIPPIFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MOORE, RICHARD G.;MUMFORD, GREGORY L.;GUNSAEKAR, DURAISAMY;REEL/FRAME:013936/0097Effective date: 20030402RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google