Converged mobile-web communications solution

[0001] This application is a continuation-in-part that claims the benefit under 35 U.S.C. Section 120 (e) of U.S. Utility application Ser. No. 12/359,861, filed on Jan. 26, 2009, by Bruce D. Lawler, Krishnakant M. Patel and Brahmananda R. Vempati, entitled “CONVERGED MOBILE-WEB COMMUNICATIONS SOLUTION,” which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. No. 61/023,332, filed on Jan. 24, 2008, by Bruce D. Lawler, Krishnakant M. Patel, Brahmananda R. Vempati and Vyankatesh V. Shanbhag, entitled “CONVERGED MOBILE-WEB COMMUNICATIONS SOLUTION,” both of which applications are incorporated by reference herein.

[0002] This application is related to the following co-pending and commonly-assigned patent applications:

[0003] U.S. Utility application Ser. No. 10/515,556, filed Nov. 23, 2004, by Gorachand Kundu, Ravi Ayyasamy and Krishnakant Patel, entitled “DISPATCH SERVICE ARCHITECTURE FRAMEWORK,” which application claims the benefit under 35 U.S.C. Section 365 of P.C.T. International Application Serial Number PCT/US03/16386, which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. Nos. 60/382,981, 60/383,179 and 60/407,168;

[0004] U.S. Utility application Ser. No. 10/564,903, filed Jan. 17, 2006, by F. Craig Farrill, Bruce D. Lawler and Krishnakant M. Patel, entitled “PREMIUM VOICE SERVICES FOR WIRELESS COMMUNICATIONS SYSTEMS,” which application claims the benefit under 35 U.S.C. Section 365 of P.C.T. International Application Serial Number PCT/US04/23038 (154.7-WO-U1), which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. Nos. 60/488,638, 60/492,650 and 60/576,094 and which application is a continuation-in-part and claims the benefit under 35 U.S.C. Sections 119, 120 and/or 365 of P.C.T. International Application Serial Number PCT/US03/16386;

[0005] U.S. patent application Ser. No. 11/126,587, filed May 11, 2005, by Ravi Ayyasamy and Krishnakant M. Patel, entitled “ARCHITECTURE, CLIENT SPECIFICATION AND APPLICATION PROGRAMMING INTERFACE (API) FOR SUPPORTING ADVANCED VOICE SERVICES (AVS) INCLUDING PUSH TO TALK ON WIRELESS HANDSETS AND NETWORKS,” which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. Nos. 60/569,953 and 60/579,309, and which application is a continuation-in-part and claims the benefit under 35 U.S.C. Sections 119, 120 and/or 365 of U.S. Utility application Ser. No. 10/515,556 and P.C.T. International Application Serial Number PCT/US04/23038;

[0006] U.S. Utility application Ser. No. 11/129,268, filed May 13, 2005, by Krishnakant M. Patel, Gorachand Kundu, Ravi Ayyasamy and Basem Ardah, entitled “ROAMING GATEWAY FOR SUPPORT OF ADVANCED VOICE SERVICES WHILE ROAMING IN WIRELESS COMMUNICATIONS SYSTEMS,” now U.S. Pat. No. 7,403,775, issued Jul. 22, 2008, which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. No. 60/571,075, and which application is a continuation-in-part and claims the benefit under 35 U.S.C. Sections 119, 120 and/or 365 of U.S. Utility application Ser. No. 10/515,556 and P.C.T. International Application Serial Number PCT/US04/23038;

[0007] U.S. Utility application Ser. No. 11/134,883, filed May 23, 2005, by Krishnakant Patel, Vyankatesh V. Shanbhag, Ravi Ayyasamy, Stephen R. Horton and Shan-Jen Chiou, entitled “ADVANCED VOICE SERVICES ARCHITECTURE FRAMEWORK,” which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. Nos. 60/573,059 and 60/576,092, and which application is a continuation-in-part and claims the benefit under 35 U.S.C. Sections 119, 120 and/or 365 of U.S. Utility application Ser. No. 10/515,556, P.C.T. International Application Serial Number PCT/US04/23038, U.S. Utility application Ser. No. 11/126,587, and U.S. Utility application Ser. No. 11/129,268;

[0008] U.S. Utility application Ser. No. 11/136,233, filed May 24, 2005, by Krishnakant M. Patel, Vyankatesh Vasant Shanbhag, and Anand Narayanan, entitled “SUBSCRIBER IDENTITY MODULE (SIM) ENABLING ADVANCED VOICE SERVICES (AVS) INCLUDING PUSH-TO-TALK, PUSH-TO-CONFERENCE AND PUSH-TO-MESSAGE ON WIRELESS HANDSETS AND NETWORKS,” which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. No. 60/573,780, and which application is a continuation-in-part and claims the benefit under 35 U.S.C. Sections 119, 120 and/or 365 of U.S. Utility application Ser. No. 10/515,556, P.C.T. International Application Serial Number PCT/US04/23038, U.S. Utility application Ser. No. 11/126,587, and U.S. Utility application Ser. No. 11/134,883;

[0009] U.S. Utility application Ser. No. 11/158,527, filed Jun. 22, 2005, by F. Craig Farrill, entitled “PRESS-TO-CONNECT FOR WIRELESS COMMUNICATIONS SYSTEMS,” which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. No. 60/581,954, and which application is a continuation-in-part and claims the benefit under 35 U.S.C. Sections 119, 120 and/or 365 of U.S. Utility application Ser. No. 10/515,556 and P.C.T. International Application Serial Number PCT/US04/23038;

[0010] U.S. Utility application Ser. No. 11/183,516, filed Jul. 18, 2005, by Deepankar Biswaas, entitled “VIRTUAL PUSH TO TALK (PTT) AND PUSH TO SHARE (PTS) FOR WIRELESS COMMUNICATIONS SYSTEMS,” which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. No. 60/588,464;

[0011] U.S. Utility application Ser. No. 11/356,775, filed Feb. 17, 2006, by Krishnakant M. Patel, Bruce D. Lawler, Giridhar K. Boray, and Brahmananda R. Vempati, entitled “ENHANCED FEATURES IN AN ADVANCED VOICE SERVICES (AVS) FRAMEWORK FOR WIRELESS COMMUNICATIONS SYSTEMS,” which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. No. 60/654,271;

[0012] P.C.T. International Application Serial Number PCT/US2006/011628, filed Mar. 30, 2006, by Krishnakant M. Patel, Gorachand Kundu, Sameer Dharangaonkar, Giridhar K. Boray, and Deepankar Biswas, entitled “TECHNIQUE FOR IMPLEMENTING ADVANCED VOICE SERVICES USING AN UNSTRUCTURED SUPPLEMENTARY SERVICE DATA (USSD) INTERFACE,” which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. No. 60/666,424;

[0013] U.S. Utility application Ser. No. 11/462,332, filed Aug. 3, 2006, by Deepankar Biswas, Krishnakant M. Patel, Giridhar K. Boray, and Gorachand Kundu, entitled “ARCHITECTURE AND IMPLEMENTATION OF CLOSED USER GROUP AND LIMITING MOBILITY IN WIRELESS NETWORKS,” which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. No. 60/705,115;

[0014] U.S. Utility application Ser. No. 11/463,186, filed Aug. 8, 2006, by Ravi Ayyasamy and Krishnakant M. Patel, entitled “ADVANCED VOICE SERVICES CLIENT FOR BREW PLATFORM,” which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. No. 60/706,265;

[0015] U.S. Utility application Ser. No. 11/567,098, filed Dec. 5, 2006, by Ravi Ayyasamy, Bruce D. Lawler, Krishnakant M. Patel, Vyankatesh V. Shanbhag, Brahmananda R. Vempati, and Ravi Shankar Kumar, entitled “INSTANT MESSAGING INTERWORKING IN AN ADVANCED VOICE SERVICES (AVS) FRAMEWORK FOR WIRELESS COMMUNICATIONS SYSTEMS,” which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. No. 60/742,250;

[0016] U.S. Utility application Ser. No. 11/740,805, filed Apr. 26, 2007, by Krishnakant M. Patel, Giridhar K. Boray, Ravi Ayyasamy, and Gorachand Kundu, entitled “ADVANCED FEATURES ON A REAL-TIME EXCHANGE SYSTEM,” which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. No. 60/795,090;

[0017] U.S. Utility application Ser. No. 11/891,127, filed Aug. 9, 2007, by Krishnakant M. Patel, Deepankar Biswas, Sameer P. Dharangaonkar and Terakanambi Nanjanayaka Raja, entitled “EMERGENCY GROUP CALLING ACROSS MULTIPLE WIRELESS NETWORKS,” which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. No. 60/836,521;

[0018] U.S. Utility application Ser. No. 12/259,102, filed on Oct. 27, 2008, by Krishnakant M. Patel, Gorachand Kundu, and Ravi Ayyasamy, entitled “CONNECTED PORTFOLIO SERVICES FOR A WIRELESS COMMUNICATIONS NETWORK,” which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. Nos. 60/982,650 and 61/023,042;

[0019] U.S. Utility application Ser. No. 12/582,601, filed on Oct. 20, 2009, by Krishnakant M. Patel, Ravi Ayyasamy, Gorachand Kundu, Basem A. Ardah, Anand Narayanan, Brahmananda R. Vempati, and Pratap Chandana, entitled “HYBRID PUSH-TO-TALK FOR MOBILE PHONE NETWORKS,” which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. No. 61/106,689; and

[0020] U.S. Utility application Ser. No. 12/750,175, filed on Mar. 30, 2010, by Bruce D. Lawler, Krishnakant M. Patel, Ravi Ayyasamy, Harisha M. Negalaguli, Basem A. Ardah, Gorachand Kundu, Ramu Kandula, Brahmananda R. Vempati, Ravi Shankar Kumar and Chetan Patel, entitled “ENHANCED GROUP CALLING FEATURES FOR CONNECTED PORTFOLIO SERVICES IN A WIRELESS COMMUNICATIONS NETWORK,” which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Ser. Nos. 61/164,754 and 61/172,129;

[0021] all of which applications are incorporated by reference herein.

[0022] 1. Field of the Invention

[0023] This invention relates in general to wireless communications systems, and more specifically, to a converged mobile-Web communications solution.

[0024] 2. Description of Related Art

[0025] Current market dynamics indicate that Web 2.0 trends will impact mobile phone communications. Specifically, it is expected that web-based applications will displace at least some core wireless services.

[0026] Nonetheless, web-based applications often ignore key components of wireless communications networks. For example, Web 2.0 trends include new virtual online communities for social networking, but typically ignores consumers' most important main network, namely contacts on their mobile phones, which are a constant personal communications companion for most people.

[0027] Nonetheless, web-based applications do provide value-added communications and messaging services heretofore found in communications networks, including:

• • [0028] Long-distance bypass,
  • [0029] Conferencing,
  • [0030] Instant Messaging (IM),
  • [0031] Voice messaging to any phone, and
  • [0032] Short Message Service (SMS), i.e., texting, and Group SMS.

[0033] However, there is a functionality gap between such web-based applications and mobile phone communications:

[0034]

	Web 2.0 Trends	Mobile Phone Communications
Content	Content stored,	Voicemail and text messages
	archived, tagged,	deleted; Conversations never
	and threaded	stored
	Information	No mechanism for “showing
	associated with	off” and obtaining
	identity and	validation
	creativity
	Private information	All contents are private
	can be made
	selectively public
	Online network of	Contact list is just a means of
	communication	calling and text messges - there
		is no mechanism for sharing
		with others or interlinking
Text	1:Many; Many:Many;	Primarily 1:1
Communication	Many:1
	From long to snack-	No threading for snack-size
	size text	information
Presence	Device and user status	Focus only on the applications,
		not the device or the user's
		status

[0035] Thus, notwithstanding the innovations found in web-based applications, there is a need in the art for improvements to these services, as well as additional services, that leverage existing and emerging wireless communications functionality and provide superior user experiences. The present invention aims to satisfy this need by providing a converged mobile-Web communications solution, combining the best of both worlds.

[0036] To overcome the limitations in the prior art described above, and to overcome other limitations that will become apparent upon reading and understanding the present specification, the present invention discloses a converged mobile-Web communications solution. Specifically, the system of the present invention interfaces to both a mobile phone network and an Internet or Intranet network, so that services that are provided to the mobile phone in the mobile phone network are also provided to a web client or web widget in the Internet or Intranet network. These services include: providing the web client or web widget with access to the mobile phone's contacts; providing the web client or web widget with access to the mobile phone's text messaging; allowing the web client or web widget to send text messages to one or more recipient mobile phones in the mobile phone network; providing the web client or web widget with access to the mobile phone's voice messaging; allowing the web client or web widget to send multimedia files to one or more recipient mobile phones in the mobile phone network; allowing the web client or web widget to place a group call to a plurality of recipient mobile phones in the mobile phone network; performing simultaneous ringing to both the mobile phone in the mobile phone network and the web client or web widget in the Internet or Intranet network; transferring calls from the mobile phone in the mobile phone network to the web client or web widget in the Internet or Intranet network; transferring calls from the web client or web widget in the Internet or Intranet network to the mobile phone in the mobile phone network; and synchronizing data between the mobile phone in the mobile phone network and the web client or web widget in the Internet or Intranet network. These and other aspects of the present invention are described in more detail below.

[0052] In the following description of the preferred embodiment, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration the specific embodiment in which the invention may be practiced. It is to be understood that other embodiments may be utilized as structural changes may be made without departing from the scope of the present invention.

[0053] 1.1. Acronyms and Messaging

[0054] In the following sections, a number of industry-standard acronyms are used, including the following:

[0055] ACM: Address Complete Message,

[0056] ACK: Acknowledgement,

[0057] AGC: Advanced Group Connect,

[0058] AGS: Advanced Group Services,

[0059] ANM: Answer Message,

[0060] AVS: Advanced Voice Services,

[0061] Connect: Connect to the terminating number provided in the message,

[0062] Continue: Continue call processing,

[0063] Data_SM: Data Short Message,

[0064] Deliver_SM: Deliver Short Message,

[0065] DTMF: Dual-Tone Multi-Frequency

[0066] FMC: Fixed Mobile Convergence,

[0067] FSM: Forward Short Message,

[0068] HTTP: Hypertext Transfer Protocol,

[0069] IAM: Initial Address Message,

[0070] IDP: Initial Detection Point,

[0071] IDP_SM: Initial Detection Point for SMS,

[0072] IM: Instant Messaging,

[0073] IMS: IP Multimedia Subsystem,

[0074] IN: Intelligent Network,

[0075] MDN: Mobile Directory Number,

[0076] MO_SM: Mobile Originating Short Message,

[0077] RLC: Release Complete Message,

[0078] REL: Release Message,

[0079] SCA: Service Center Address,

[0080] SIP: Session Initiation Protocol, and

[0081] SMS: Short Message Service.

[0082] Voice call related messages in the following call flows include: Setup, Originating, Terminating, IAM, Alerting, ACM, Connect, ANM, Disconnect, REL, release, Disconnect Ack, and RCL release complete.

[0083] SMS related messages in the following call flows include: MO-SM, FSM (a.k.a. Fwd_SM), Data_SM, Deliver_SM, and MT_SM.

[0084] IN related messages in the following call flows include: IDP, Connect, Continue, release, and IDP_SM.

[0085] 1.2. Technical Highlights

[0086] The present invention discloses a converged mobile-Web communications solution, as well as a suite of applications, used both with mobile phones that operate within a mobile phone network and web clients or web widgets that operate within Internet/Intranet networks. Specifically, the present invention provides brings mobile phone services to web clients and web widgets.

[0087] Web clients may execute within a browser, for example, as a plug-in downloaded from a web site, or may comprise standalone programs, while web widgets may comprise programs or plug-ins that are embedded in Web pages, such as those found on social networking sites (for example, a user's FACEBOOK page). Both web clients and web widgets allow Internet/Intranet users to communicate with mobile users using phone calls, advanced voice services, messaging, data exchange, etc.

[0088] Preferably, the present invention includes a number of key features and functionality, including:

• • [0089] Contact/Group Management:
    • [0090] Handset/Web Client/Web Widget synchronization,
    • [0091] Presence notification (handset+Web Client/Web Widget),
  • [0092] Mirror of Handset-based Messaging:
    • [0093] Voice SMS,
    • [0094] Text SMS,
  • [0095] IM Support and Integration:
    • [0096] SMS delivered to IM,
    • [0097] IM conversation delivered to a handset using SMS,
  • [0098] Messaging Delivery to E-mail:
    • [0099] Voice and text SMS,
    • [0100] Video, audio and images,
    • [0101] Reply via e-mail,
  • [0102] FMC/Voice Communications:
    • [0103] Call waiting on a Web Client or Web Widget,
    • [0104] Group call capabilities from a Web Client or Web Widget,
  • [0105] Multimedia Management:
    • [0106] Video, audio and image delivery to both the handset and a Web Client or Web Widget,
    • [0107] Voice SMS as attachments,
  • [0108] Message Management:
    • [0109] Threading, sorting, searching, and history.

[0110] These and other aspects of the present invention are described in more detail below.

[0111] 1.3. Wireless Communications Network Architecture

[0112] FIG. 1 is a block diagram that illustrates an exemplary embodiment of a wireless communications network 100 according to an embodiment of the present invention. This network 100 generally comprises a cellular telephone network (also known as a mobile phone network), and is described in more detail in the cross-referenced applications set forth above in reference to the provision of Advanced Voice Services (AVS), also known as Advanced Group Services (AGS), such as two-way half-duplex voice calls within a group, also known as Push-to-Talk (PTT) or Press-to-Talk (P2T), as well Advanced Group Connect (AGC) functions, such as Push-to-Conference (P2C) or Instant Conferencing (IC), Push-to-Message (P2M), Voice SMS (VSMS), Group SMS (GSMS) with Reply to Sender, Scheduled Conference (SC), Group SMS Chat With Reply All and Address Book backup and restore. In addition, the functionality of this network 100 can also be used to provide the converged mobile-Web communications solution according to one embodiment of the present invention.

[0113] Within the network 100, an RTX 102, also known as a Dispatch Gateway (DG), communicates with a MSC (Mobile Switching Center) 104 and PSTN (Public Switched Telephone Network) 106 using SS7-ISUP/WIN/CAMEL (Signaling System 7-Integrated Services Digital Network User Part/Wireless Intelligent Network/Customized Applications for Mobile Enhanced Logic) messages at a signaling plane 108. A bearer path 110 implements a TDM (Time Division Multiplexing) interface carrying PCM (Pulse Code Modulation) or TFO (Tandem Free Operation) voice frames. Support for TFO in this path 110 is negotiated between a BSC (Base Station Controller) 112 and the RTX 102 for each originating and terminating leg of a call. The use of TFO ensures high voice quality (as voice vocoder conversion is avoided) between mobile-to-mobile calls.

[0114] When a subscriber originates a call, the MSC 104 routes the call to the RTX 102. The MSC 104 also requests the BSC 112 via 116 to establish a radio traffic path 118 with a mobile station (MS) 120 (also known as a handset, mobile unit, mobile phone, or cellular phone) via the BTS (Base Transceiver Station) 122 (as it does for a normal cellular call). At this time, the BSC 112 tries to negotiate TFO (if it is supported) on a TDM link with the far end (in this case, the RTX 102).

[0115] At the same time (after the MSC 104 terminates the call request to the RTX 102), the RTX 102 identifies the terminating group users and their numbers, which may comprise an MS-ISDN (Mobile Station-Integrated Services Digital Network) number, an IMSI (International Mobile Subscriber Identity) number, or an MDN (Mobile Directory Number).

[0116] The RTX 102 sends an ISUP call origination request for each terminating handset 120. It may send requests directly to the MSC 104, PSTN 106 or IP network 124 via a PDSN (Public Data Switched Network) 126, Router 128, and/or Internet/Intranet 130, depending on the routing table configuration for terminating numbers. Once the bearer path 110 is established, the RTX 102 begins a negotiation with the far end (in this case, the terminating BSC 112) for each terminating leg to a handset 120.

[0117] Once bearer paths 110 are established for originating and terminating legs for a call, the RTX 102 switches (or duplicates) voice or data from the originating handset 120 to all terminating handsets 120.

[0118] The RTX 102 may also use an IP network 124 or the Internet/Intranet 130. The IP network 124 or the Internet/Intranet 130 can be used in a toll bypass mode where two RTXs 102 can exchange voice traffic bypassing the PSTN 106. However, each RTX 102 is responsible for terminating traffic to its closest MSC 104. In this case, the IP network 124 or the Internet/Intranet 130 is used as a backbone transport of voice traffic between two RTXs 102.

[0119] The IP network 124 or the Internet/Intranet 130 can also be used for a registration and presence application. Since the MSC 104 will not direct a registration request from a handset 120 to the RTX 102 (because it would require changes in the MSC 104), the latter does not have any information of the registered handset 120. To circumvent this issue, a registration and presence application runs over an IP stack in the handset 120. After the handset 120 registers for a data interface (i.e., obtaining an IP address) with the PDSN 126 (or Serving GSM Service Nodes (SGSN) 140 in the case of GSM networks and Gateway GPRS (General Packet Radio Service) Support Node (GGSN) 142 in the case of GSM phones for transmitting IP packets), the registration and presence application in the handset 120 registers with the RTX 102 using its IP address. The RTX 102 also uses this IP interface to update the presence information to a handset 120.

[0120] An alternative embodiment may use the SMS (Short Message Service) transport to carry presence messages over a data channel. The RTX 102 interacts with the handset 120 using predefined presence application related messages that are transported as SMS messages. The same messages can be transported via the PDSN 126 interface, if users have data service.

[0121] During roaming, a Home Location Register (HLR) 132 and Visitor Location Register (VLR) 134 can be accessed via the MSC 104 and a MAP (Mobile Application Part) link 136. The HLR 132 and VLR 134 are used to track the handsets 120 within home or foreign networks, while the RTX 102 is used to track the presence of members of a group within the home or foreign networks and updates the handsets 120 for those members with the network availability of other members of the group.

[0122] A Short Message Service Center (SMSC) 138 is accessible via the IP network 124 (or other element) for the storage of text messages (SMS messages). When an SMS message is sent to a handset 120, the message is first stored in the SMSC 138 until the recipient handset 120 is available (e.g., a store-and-forward option).

[0123] 1.4. Real Time Exchange

[0124] FIG. 2 illustrates a proposed architecture for the RTX 102 according to the preferred embodiment of the present invention.

[0125] The architecture includes a Call Processing system 200, Presence Server 202, Real-Time Event Processing system 204, one or more Media Managers 206, and an SMPP (Short Message Peer-to-Peer) Transport 208, as well as modules for various SS7 protocols, such as MTP-1 (Message Transfer Part Level 1) 210, MTP-2 (Message Transfer Part Level 2) 212, MTP-3 (Message Transfer Part Level 3) 214, ISUP (Integrated Services Digital Network User Part) 216, SCCP (Signaling Connection Control Part) 218, and TCAP (Transactions Capabilities Application Part) 220 protocols.

[0126] The Call Processing system 200, Presence Server 202, Media Managers 204, SMPP Transport 206, and other modules communicate across an IP network 222. The Real-Time Event Processing system 204 communicates directly with the Call Processing system 200, Presence Server 202, and the modules for various SS7 protocols. The modules for various SS7 protocols communicate with other entities via a SS7 Signaling Link 224. The SMPP Transport 206 communicates with a SMSC (Short Message Service Center) gateway using the SMPP protocol 226. The Media Managers 204 communicate among themselves using the H.110 protocol 228 (or some other protocol, such TCP/IP).

[0127] The originating handset 120 signals the RTX 102 via the wireless network 100, e.g., by transmitting one or more configured DTMF (Dual Tone Multi Frequency) digits to the RTX 102. The Media Manager systems 206 receive the DTMF digits and pass the DTMF digits to the Call Processing system 200. The Call Processing (CP) system 200 determines whether the originating handset 120 has subscribed to the AVS, AGS or AGC service before originating the call. Upon confirmation, the Call Processing system 200 initiates a new call. The Call Processing system 200 interacts with the Presence Server 202 and Real-Time Event Processing system 204 to cause the wireless network 100 to perform call setup with the terminating handsets 120 for the call, and thereafter to manage the call.

[0128] During the call, the Call Processing system 200 interacts with the Media Manager systems 206 to maintain the H.110 channels 227 and assign any additional H.110 channels 228 required for the call, which may span across multiple Media Manager systems 206. During the call, the Media Manager systems 206 of the RTX 102 are used to mix audio streams between the originating handset 120 and the terminating handset 120, and then deliver these mixed audio streams to the originating handset 120 and the terminating handset 120. The H.110 channels 228 are used for passing mixed and unmixed audio streams voice between the Media Manager systems 200 as required.

[0129] In addition, the RTX 102 may include an MMS Relay 228, Notification Server 230, Registrar/SIP Proxy 232, Media Proxy 234, Media Converter 236, Content Server 238, Web Server 240 and Location Server 242. The operation of these various components are described in more detail below, as well as in the co-pending and commonly-assigned patent applications cross-referenced above and incorporated by reference herein.

[0130] 1.5. Handset Components

[0131] FIG. 3 illustrates the high-level functional components and their interfaces in the handset 120 according to an embodiment of the present invention. In one embodiment, the software architecture used in the handset 120 is based on an Open OS implementation and is available under multiple operating systems, including JAVA, WINDOWS MOBILE, SYMBIAN and BREW.

[0132] Preferably, the software architecture used in the handset 120 provides an application programming interface (API) that supports the logic and data required within the handset 120 for providing cellular service, including the functions necessary for the making a call generally, and for providing the AVS, AGS or AGC services specifically.

[0133] The high-level functional components of the handset 120 include an encoder/decoder 302, processing logic 304 and user interface 306. A client application 308 is provided on a subscriber identity module (SIM) 300 that supports AVS, AGS or AGC functionality for the handset 120. In addition, the SIM 300 stores a database 310, which includes an address book, contacts and/or group information.

[0134] At power-on, the handset 120 loads the client application 308 necessary to support the AVS, AGC or AGC services. This functionality provided includes the “look and feel” of the menu displays on the handset 120, as well as user interaction with the menu displays.

[0135] During operation, the encoder/decoder 302 decodes and encodes messages, and populates specific data structures in the handset 120. The encoder/decoder 302 checks the validity of the incoming messages by verifying mandatory parameters for each of the incoming messages. A message will not be processed further if the encoder/decoder 302 fails to decode the message.

[0136] The processing logic 304 handles normal calls, as well as all the AVS, AGS or AGC related functionalities. The processing logic 304 implementation is device-specific and vendor-specific, and it interacts with the other components, including the encoder/decoder 302, user interface 306, client application 308 and database 310.

[0137] The processing logic 304 provides an auto-answer mechanism for calls. Specifically, when a call is received, the processing logic 304 automatically answers the call. The processing logic 304 makes use of call notification for incoming call detection and, based on various parameters received within the call notification, determines whether the call is a normal call or an AVS, AGS or AGC call. The processing logic 304 performs the necessary processing based on this determination.

[0138] In addition, the processing logic 304 provides SMS destination control based on the type of subscriber. At the time of subscriber data provisioning, if it is determined that the handset 120 will use AVS, AGS or AGC based logic, then appropriate logic is invoked in the RTX 102 to send presence messages over SMS to the handset 120. Similarly, the handset 120 is configured at the time of provisioning to receive/accept such SMS and respond to the RTX 102 appropriately.

[0139] Finally, the processing logic 304 also enables subscribers to track the presence of contacts and members of a group on their handset 120, and provides a mechanism and API to carry-out contacts and group management operations on the handset 120, such as add member, delete member, etc.

[0140] Since most of the presence information is stored in the database 310, the database 310 is tightly integrated with the processing logic 304. The database 310 stores groups, contacts, presence and availability related information. The database 310 information essentially contains group and member information along with presence information associated with each group and member. Apart from group and member information, the database 310 also stores subscriber information, such as privileges, presence information, etc. The other components of the handset 120 may interact with the database 310 to retrieve/update the group, members and presence information for various operations. The database 310 also has pointers to the native address book on the handset 120, to provide seamless “alias” naming for contacts used with normal calls, as well as AVS, AGS or AGC services.

[0141] The user interface 306 provides a mechanism for the user to view and manage groups, group members, contacts, presence and availability. The user interface 306 also makes it possible to invoke the AVS, AGS or AGC services from the group/contact list screens, as described in more detail below.

[0142] According to one embodiment of the present invention, the functionality of the converged mobile-Web communications solution includes the following:

[0143]

Contacts	Back-up of contacts online.
	Never have to worry about losing contacts if handset is
	lost.
	No need to transfer contacts from one handset to
	another.
Text	Type from the convenience of a handset, web browser,
Messaging	web client, web widgets, etc., and send a single message
	to a group all at once.
	Messages are all threaded.
Voice	Add a personal touch to a message using voice.
Messaging	Send it to recipients' handsets, IM accounts, and/or e-
	mail addresses as an attachment.
Multimedia	Easily attach multimedia content to a message.
File	Send it to any mobile subscribers with or without a
Attachments	computer.
Group Voice	Flexibility of making an easy group voice call from a
Calls	computer (with a microphone).
	No need to pay expensive international voice call rates
	while traveling overseas.
Message	No more worry about having to delete old messages on
Retrieval	the handset.
	All text and voice messages are saved online and can be
	archived/searched.

[0144] The components that work together to provide the functionality of the converged mobile-Web communications solution according to one embodiment of the present invention are described in more detail in the following sections.

[0145] 2.1. Network Architecture

[0146] FIG. 4 is a block diagram that illustrates an extension 400 to the network 100 architecture used for one embodiment of the present invention. In this diagram, the extension to network 100 architecture includes some of the components from FIG. 1, including the RTX 102, MSC 104, BSC 112, BTS 122, and handset 120; some of the components from FIG. 2, including the Presence Server 202, MMS Relay 228, Notification Server 230, Rgistrar/SIP Proxy 232, Media Proxy 234, Media Converter 236, Content Server 238, Web Server 240, and Location Server 242; as well as other components including a Web Client 402, Web Widgets 404, MMSC 406, SyncML Server 408, and Packet Data Gateway (PDG) 410. These components are typically implemented within the cellular telephone network 100 and/or Internet/Intranet 130 and/or IP network 124, although they may also be implemented within or be accessible via connection through the PSTN 106, and/or the PDSN 126, SGSN 140 or GGSN 142. The operation of these components is described in more detail below.

[0147] Generally, the network 100 is used for making phone calls and exchanging data to and from the handsets 120, wherein the phone calls are initiated by call setup and in-band signaling within the network 100 and voice frames for the phone calls are switched between the handsets 120 across bearer paths in the network 100. The RTX 102 interfaces to at least one MSC 104 in the network 100 to provide the AVS, AGS or AGC services therein, without requiring any changes to the MSC 104 or other equipment of the network 100 to provide the AVS, AGS or AGC services. Both the RTX 102 and the handsets 120 that use the AVS, AGS or AGC services communicate with each other using the call setup and in-band signaling within the network 100, such that at least one MSC 104 routes an originating leg of the AVS, AGS or AGC services from an originating handset 120 to the RTX 102, the RTX 102 exchange initiates one or more terminating legs of the AVS, AGS or AGC services to one or more terminating handsets 120 through at least one MSC 104, and the RTX 102 switches the voice frames for the AVS, AGS or AGC services for the handsets 120 across the bearer paths and through at least one MSC 104 in the network 100.

[0148] In one embodiment, the RTX 102 also interfaces to one or more Intranet or Internet networks, such as 124 or 130, for exchanging data between at least one of the handsets 120 and at least one user on the Intranet or Internet network 124 or 130, in order to provide the AVS, AGS or AGC services (and other services) to the user on the Intranet or Internet network 124 or 130. The user on the Intranet or Internet network 124 or 130 uses a Web Client 402 or Web Widget 404 to exchange the data with the RTX 102 and/or handset 120. The other components of the network 400 together comprise the means, that interface to the network 100 and the network 124 or 130, for providing a converged mobile-Web communications solution to both the handsets 120 and the Web Client 402 or Web Widget 404, wherein the converged mobile-Web communications solution comprises one or more of the following services:

• • [0149] providing a Web Client 402 or Web Widget 404 with access to a handset's 120 contacts;
  • [0150] providing a Web Client 402 or Web Widget 404 with access to a handset's 120 text messaging;
  • [0151] allowing a Web Client 402 or Web Widget 404 to send text messages to one or more recipient handsets 120;
  • [0152] providing a Web Client 402 or Web Widget 404 with access to a handset's 120 voice messaging;
  • [0153] allowing a Web Client 402 or Web Widget 404 to send multimedia files to one or more recipient handsets 120;
  • [0154] allowing a Web Client 402 or Web Widget 404 to place a group call to a plurality of handsets 120;
  • [0155] allowing a Web Client 402 or Web Widget 404 to initiate, receive and/or participate in the various AVS, AGS or AGC services;
  • [0156] performing simultaneous ringing of call to a subscriber's handset 120 and a Web Client 402 or Web Widget 404;
  • [0157] transferring calls from a handset 120 to a Web Client 402 or Web Widget 404;
  • [0158] transferring calls from a Web Client 402 or Web Widget 404 to a handset 120; and
  • [0159] synchronizing data between a handset 120 and a Web Client 402 or Web Widget 404.
    The implementation of these various services is described in more detail below.

[0160] 2.2. Web Client and Web Widgets

[0161] A Web Client 402 may execute within a browser, for example, as a plug-in downloaded from a Web site, or may comprise standalone programs, while a Web Widget 404 may comprise a program or plug-in that is embedded in a Web page.

[0162] The Web Client 402 preferably contains two components:

• • [0163] A web interface executed within a Web browser that displays the user's address-book and messages. This part communicates with the Web Server 240 over HTTP to fetch the data required for a view. The web interface does not store any data outside the HTTP session. Only data required for the current view is stored in memory. (It is similar to web mail interfaces.)
  • [0164] A browser plug-in containing a SIP client for all voice related features, which is downloaded via the web interface. The SIP plug-in registers with the network and can perform all of the functions as the MS 120, including initiate and receive calls, messaging, initiate and participate in the AVS, AGS or AGC services, etc. The SIP plug-in also maintains SIP subscriptions which are used for obtaining presence and for receiving notifications about new messages that need to be displayed on the web interface.

[0165] Alternatively, Web Widgets 404 may be used to perform the same functions as the Web Client 402. A Web Widget 404 is an applet (program) that can be installed within any Web page and then executed by a Web browser when the Web page is accessed. Web Widgets 404 may be implemented using DHTML, JavaScript, Adobe Flash, or other programming languages.

[0166] 2.3. Packet Data Gateway

[0167] The Packet Data Gateway (PDG) 410 is a network 100 component, wherein the Web Client 402/Web Widgets 404 establishes a secure IPSec tunnel with the PDG 410. All SIP communication from the Web Client 402/Web Widgets 404, and optionally the HTTP traffic, will be routed through the secure IPSec tunnel with the PDG 410, to the Web Server 240 and the Registrar/SIP Proxy 232.

[0168] 2.4. Registrar/SIP Proxy and Media Proxy

[0169] All call related features on Web Client 402/Web Widget 404 use the SIP protocol for session establishment and call control. The Registrar/SIP Proxy 232, also known generically as an Access Gateway (AGW), acts as a gateway and routes calls between the Web Client 402/Web Widget 404 and the RTX 102. It also acts as a SIP Registrar 232 that not only authenticates the subscribers before providing access to the RTX 102, but also stores the location and routing information needed for terminating incoming calls on the Web Client 402/Web Widget 404.

[0170] The Registrar/SIP Proxy 232 controls the path for all SIP signaling between the Web Client 402/Web Widget 404 and the RTX 102. The main function of the Registrar/SIP Proxy 232 is to authenticate SIP messages. The SIP authentication is performed using the session ID established at the Web Server 240 by the Web Client 402/Web Widget 404. The Registrar/SIP Proxy 232 also acts as a SIP registrar. The Registrar/SIP Proxy 232 preferably comprises a set of redundant proxy servers/registrars.

[0171] A Web Client 402/Web Widget 404 receives a SIP configuration from the Web Server 240. This configuration contains details of the Registrar/SIP Proxy 232 to be contacted.

[0172] Associated with the Registrar/SIP Proxy 232 is a Media Proxy 234. Similar to the way the Registrar/SIP Proxy 232 acts as a gateway for call signaling, the Media Proxy 234 function acts as a gateway for media packets sent between the Web Client 402/Web Widget 404 on one side and a Content Server 238 in the RTX 102 on the other side.

[0173] 2.5. Web Server

[0174] The Web Server 240 presents the user interface pages to the Web Client 402/Web Widget 404. It also provides the user with a SIP plug-in for installation. The Web Server 240 interfaces with the Content Server 238 to provide views of the user's address book and message inbox. However, the Web Server 240 does not store any user data permanently. All user data served by the Web Server 240 is obtained from the Content Server 238.

[0175] The Web Server 240 is also responsible for authenticating the user with the network. After it establishes an HTTP session with the Web Client 402/Web Widget 404, the Web Server 240 shares the session ID with the Registrar/SIP Proxy 232 for authenticating SIP requests.

[0176] Multiple Web Servers 240 may be deployed to support high availability and redundancy.

[0177] A Web Server 240 may also be deployed in the public internet by the carrier (i.e., the Web Server 240 does not communication with the Web Client 402/Web Widget 404 through the Registrar/SIP Proxy 232). This Web Server 240 will also serve the SIP plug-in and user interface pages to the Web Client 402/Web Widget 404.

[0178] 2.6. Presence Server

[0179] The Presence Server 202 handles SIP subscriptions and publications from the Web Client 402/Web Widget 404. The main function of the Presence Server 202 is to off-load presence related messaging and dialog maintenance overheads from the RTX 102. The RTX 102 maintains the presence state of the user. The Presence Server 202 creates presence documents using the information stored on the RTX 102. The Presence Server 202 also updates the presence state on the RTX 102 when it receives presence publications from the Web Client 402/Web Widget 404.

[0180] 2.7. Location Server

[0181] The Location Server 242 stores information about a user's home RTX 102, Presence Server 202, and Content Server 238. The Location Server 242 is also used to store the session details for Web Clients 402/Web Widgets 404. The Registrar/SIP Proxy 232 uses this information to authenticate SIP messages using the session ID. The session ID is created by the Web Server 240 and is only read by the Registrar/SIP Proxy 232. The Registrar/SIP Proxy 232 cannot extend the life of the session ID directly. The SIP plug-in in the Web Client 402/Web Widgets 404 will trigger “keep-alive” HTTP requests when calls are in progress to prevent HTTP session timeout. The session ID will be removed from the Location Server 242 by the Web Server 240 in case of a session timeout.

[0182] 2.8. RTX

[0183] The RTX 102 has a SIP adaptor that is capable of receiving and originating SIP calls to the Web Client 402/Web Widget 404. The SIP adaptor is integrated with the Call Processing 200 component, which can handle calls with simultaneous SIP and SS7 legs. The SIP adaptor is also capable of injecting SMS signals into the RTX 102, which is used for features such as Voice SMS (VSMS) deposit.

[0184] 2.9. SyncML Server

[0185] The SyncML (Synchronization Markup Language) Server 408 handles SyncML connections from the handset 120 to synchronize the address book and other data between the handset 120 and the Content Server 238.

[0186] 2.10. Content Server

[0187] The Content Server 238 archives all messages belonging to a user. It also holds a view of the user's address book and the messages stored on the handset 120. The Content Server 238 may be a distributed data store. It will interface with the SyncML Server 408 to maintain synchronization with the data from the handset 120.

[0188] The RTX 102 copies all AGC communication sent to users with their Content Server 238. The Web Server 240 will fetch data to be displayed by the Web Client 402/Web Widget 404 from the Content Server 238.

[0189] 2.11. Notification Server

[0190] The Notification Server 230 allows other web services and network components to send notifications to the Web Client 402/Web Widget 404 whenever data changes on the Content Server 238. The Web Client 402/Web Widget 404 will then pull the data from the Content Server 238 through the Web Server 240 using other web services.

[0191] 2.12. MMS Relay

[0192] The MMS Relay 228 provides access to the operator's MMS (Multimedia Messaging Service) by acting as a gateway between the different types of clients (Handset 120, Web Client 402, Web Widget 404) and the MMSC (Multimedia Messaging Service Center).

[0193] 2.13. Media Converter

[0194] The Media Converter 236 provides a media library and multimedia messaging features, and is used for storing the media files. These media files can be any number of different formats, such as JPG, PNG, GIF, etc., for pictures; MP3, WAV, AMR, etc. for audio; and MPG, AVI, 3PG, etc., for video. Since not all formats are supported by all the mobile handsets 120, and also for enabling streaming of audio and video files to the Web Client 402/Web Widget 404, the media files may need to be converted into formats different from the original format of the uploaded files. The Media Converter 236 provides this function within the network.

[0195] The Web Client 402/Web Widget 404 expects the following configuration from the Web Server 240 after authentication:

[0196] 1. Access numbers for the various services.

[0197] 2. DTMF patterns for call transfer.

[0198] 3. Configured numbers for call transfer (mobile and landline numbers).

[0199] 4. Registrar/SIP Proxy 232 details.

[0200] The following sections describe the following message flows:

[0201] 1. Web Server 240 registration and SIP registration.

[0202] 2. Call initiation from the Web Client 402 for AGC services.

[0203] 3. Call termination to the Web Client 402 for AGC services.

[0204] 4. Simultaneous ringing of the handset 120 and the Web Client 402.

[0205] 5. Call transfer to alternate number.

[0206] 6. Call hold.

[0207] 7. Presence publication.

[0208] 8. Presence subscription.

[0209] 9. AGC features notifications to the Web Client 402.

[0210] 10. Data synchronization from the handset 120 using the SyncML Server 408.

[0211] 11. Data synchronization from the Web Client 402 using an HTTP mechanism.

[0212] These message flows are for illustrative purposes only. For example, although these message flows refer only to the Web Client 402, the Web Widget 404 may perform the same functions as the Web Client 402, and may be substituted for the Web Client 402 throughout these message flows.

[0213] In addition, although the terminations to the handset show ISUP messages sent to the handset, the IAM, ACM, ANM, REL, RLC, etc., messages traverse a GMSC.

[0214] 4.1. Registration

[0215] FIG. 5 is a call flow diagram that illustrates the steps performed during Registration in one embodiment of the present invention. The steps include the following:

[0216] 1. An IPSec tunnel is established.

[0217] 2. After the IPSec tunnel is established, the Web Client 402 requests the web pages for the Web Client 402.

[0218] 3. The Web Server 240 receives the request and issues a challenge to the Web Client 402 for authentication.

[0219] 4. The Web Client 402 receives and responds to the challenge:

• • [0220] Option 1: The Web Client 402 retrieves the authentication credentials, for example, from a USB device, and resends the web page request with these details.
  • [0221] Option 2: The Web Client 402 displays a dialog box for the user to enter the username and password. When the user enters these details, the Web Client 402 resends the web page request with these details.

[0222] 5. The Web Server 240 verifies the received authentication credentials and, if successful, stores the session id and the time stamp for the session id in a subscriber information table in the Location Server 242.

[0223] 6. The Web Server 240 then checks for the Registrar/SIP Proxy 232 information for the user on the Location Server 242. If Registrar/SIP Proxy 232 information is not available, then the Web Server 240 selects an Registrar/SIP Proxy 232 to communicate with the Web Client 402 and stores the information in the Location Server 242.

[0224] 7. The Web Server 240 creates and sends a customized web page for that user. As part of the response, the Web Client 402 also receives other configuration information such as the identity of the Registrar/SIP Proxy 232, access numbers for various features, etc.

[0225] 8. The Web Client 402 initiates SIP registration.

[0226] 9. The Registrar/SIP Proxy 232 challenges the Web Client 402 for authentication.

[0227] 10. The Web Client 402 uses the user name entered previously and uses the session id as the password for generating the response. It then resends the registration request with this response.

[0228] 11. The Registrar/SIP Proxy 232 retrieves the session id from the Location Server 242 for the specified user name.

[0229] 12. The Registrar/SIP Proxy 232 then validates the authentication response using the retrieved session id.

[0230] 13. If this is successful, the Registrar/SIP Proxy 232 accepts the registration. The Web Client 402 can now make and receive calls, including AGC calls, through the Web Client 402.

[0231] 14. The Web Client 402 sends a “keep-alive” HTTP message to the Web Server 240 to keep the session id in the Location Server 242 valid.

[0232] 15. The Web Server 240 sends a confirmation message for the “keep-alive” message.

[0233] 16. When the Web Client 402 connection is broken (for example, the web browser window or tab is closed normally) or when the “keep-alive” time is expired, the Web Server 240 removes the session id information from the Location Server 242.

[0234] 4.2. Call Initiation

[0235] FIG. 6 is a call flow diagram that illustrates the steps performed during Call Initiation in one embodiment of the present invention. The steps include the following:

[0236] 1. The user selects contacts B and C and initiates, for example, an AGC call, such as an Instant Conference (IC) call. The Web Client 402 creates and sends a SIP INVITE request containing the list of recipients. The SIP INVITE request also contains the feature tag for IC call. This is used to route the IC call to the RTX 102. The request is addressed to a unique well known URI set up for IC calls. This URI could be the same E.164 number or short code used for IC origination.

[0237] 2. The SIP adapter at the RTX 102 extracts the recipients list from the SIP INVITE and triggers an MO-SMS containing the recipient list.

[0238] 3. The RTX 102 receives the MO-SMS with the recipient list and processes the SIP INVITE.

[0239] 4. The RTX 102 originates the call to B.

[0240] 5. The RTX 102 originates the call to C.

[0241] 6. The RTX 102 receives an ACM from B.

[0242] 7. Since this is the first ACM received for the call, the RTX 102 sends a SIP 180 Ringing response to A.

[0243] 8. The RTX 102 receives an ACM from C.

[0244] 9. User C answers the call first. The RTX 102 receives an ANM from C.

[0245] 10. Since this is the first ANM for the call, the RTX 102 now establishes the call and sends a SIP 200 Ok response to A.

[0246] 11. A's Web Client 402 creates and sends an ACK to complete the INVITE transaction.

[0247] 12. The RTX 102 knows that A has initiated the IC call from a Web Client 402. So, the RTX 102 sends a copy of the IC call rejoin notification in the Content Server 238 against user A's data. This is in addition to the regular SMS notification sent to A's handset (which is not shown in the flow).

[0248] 13. The RTX 102 sends a regular SMS notification to C.

[0249] 14. The Content Server 238 detects a change in user A's data and sends a notification to A's Web Client 402 that the data has changed, asking it to retrieve the data. This notification is sent within the SUBSCRIBE dialog established for presence and data change notifications.

[0250] 15. User A's Web Client 402 uses HTTP to retrieve the notification and sends a HTTP request to the Web Server 240.

[0251] 16. The Web Server 240 sends the changed data that includes the rejoin notification.

[0252] 17. User B answers the call and is joined into the conference by the RTX 102.

[0253] 18. The RTX 102 sends a rejoin notification to B.

[0254] 4.3. Call Termination

[0255] FIG. 7 is a call flow diagram that illustrates the steps performed during Call Termination in one embodiment of the present invention. The steps include the following:

[0256] 1. User selects contacts B and C and initiates an AGC call, such as an IC call. The Web Client 402 creates and sends a SIP INVITE request containing the list of recipients. The SIP INVITE request also contains the feature tag for the IC call. This is used to route the IC call to the RTX 102. The request is addressed to a unique well known URI set up for IC calls. This URI could be the same E.164 number or short code used for IC origination.

[0257] 2. The SIP adapter at the RTX 102 extracts the recipients list from the SIP INVITE and triggers an MO-SMS containing the recipient list.

[0258] 3. The RTX 102 receives the MO-SMS with the recipient list and processes the SIP INVITE.

[0259] 4. The RTX 102 originates a call to B.

[0260] 5. The RTX 102 detects that user C is logged in through the Web Client 402. It looks up the Location Server 242 and finds the Registrar/SIP Proxy 232 through which it can reach C.

[0261] 6. The RTX 102 originates a SIP call to C and sends it to the Registrar/SIP Proxy 232 for C.

[0262] 7. The Registrar/SIP Proxy 232 forwards the call to C.

[0263] 8. In the meantime, the RTX 102 receives an ACM from B.

[0264] 9. Since this is the first ACM for this call, the RTX 102 sends a SIP 180 Ringing response to A.

[0265] 10. C's Web Client 402 receives the SIP INVITE and sends a SIP 180 Ringing response to its Registrar/SIP Proxy 232.

[0266] 11. The Registrar/SIP Proxy 232 forwards the response to the RTX 102.

[0267] 12. User B answers the call and the RTX 102 receives an ANM from B.

[0268] 13. Since this is the first ANM for this call, the RTX 102 sends a SIP 200 Ok response to A.

[0269] 14. A's Web Client 402 sends a SIP ACK to complete the SIP INVITE transaction.

[0270] 15. User C answers the call. C's Web Client 402 sends a SIP 200 Ok response to the Registrar/SIP Proxy 232.

[0271] 16. The Registrar/SIP Proxy 232 forwards the response to the RTX 102.

[0272] 17. The RTX 102 sends a SIP ACK to complete the transaction.

[0273] 18. The Registrar/SIP Proxy 232 receives the SIP ACK message and forwards it to C's Web Client 402.

[0274] Rejoin notification flows are not shown in this flow, as they are similar to the one shown in the Call Initiation flow.

[0275] 4.4. Simultaneous Ringing

[0276] FIG. 8 is a call flow diagram that illustrates the steps performed during Simultaneous Ringing on both the handset 120 and Web Client 402 in one embodiment of the present invention. The steps include the following:

[0277] 1. The RTX 102 receives an incoming call to user A. The RTX 102 determines that user A can be reached through the handset 120 as well as the Web Client 402. The RTX 102 looks up the Registrar/SIP Proxy 232 through which A's Web Client 402 can be reached, in a manner similar to the mechanism shown in the Call Termination message flow.

[0278] 2. The RTX 102 places the call to the handset 120 using SS7 signaling.

[0279] 3. The RTX 102 places the call to the Web Client 402 through the Registrar/SIP Proxy 232 using SIP signaling

[0280] 4. A's handset 120 receives the call and sends an alerting response.

[0281] 5. A's Web Client 402 receives a SIP INVITE and sends an alerting response through the Registrar/SIP Proxy 232.

[0282] Messages #6 to #9 show the message flow when user A answers the call on the Web Client 402.

[0283] 6. The Web Client 402 sends a SIP 200 Ok response to accept the call.

[0284] 7. The RTX 102 connects the Web Client 402 and sends a SIP ACK message to complete the transaction.

[0285] 8. The RTX 102 then releases the call on A's handset 120.

[0286] 9. The handset 120 sends an RLC to complete the transaction.

[0287] Messages #10 to #14 show the message flow when user A answers the call on the handset 120.

[0288] 10. A's handset 120 sends an ANM message to accept the call.

[0289] 11. The RTX 102 connects A's handset 120 to the call and sends a SIP CANCEL request to the Web Client 402 to drop the SIP call leg.

[0290] 12. The Web Client 402 sends a SIP 200 Ok for the CANCEL transaction.

[0291] 13. The Web Client 402 then sends a SIP 487 Request Canceled response for the INVITE transaction to the RTX 102 to indicate that the request was canceled by the RTX 102.

[0292] 14. The RTX 102 sends a SIP ACK to complete the INVITE transaction.

[0293] 4.5. Call Transfer from Web Client to Handset

[0294] FIG. 9 is a call flow diagram that illustrates the steps performed during Call Transfer, from the Web Client 402 to the handset 120, in one embodiment of the present invention. The steps include the following:

[0295] 1. User A is on a call on the Web Client 402. User A wants to transfer the call to the handset 120 and continue the call. User A enters the appropriate DTMF sequence on the Web Client 402 and the handset sends these DTMF signals in-band to the RTX 102.

[0296] 2. The RTX 102 receives the DTMF signals and interprets the signals as a call transfer from the Web Client 402 to the handset 120. It sends a SS7 IAM message to A's handset 120.

[0297] 3. A's handset 120 receives the IAM message, presents the call to the user and sends an ACM message to the RTX 102.

[0298] 4. User A now answers the call on the handset 120. A's handset 120 sends an ANM message to the RTX 102 to accept the call. The RTX 102 connects the handset 120 call leg to the ongoing call.

[0299] 5. The RTX 102 now disconnects the Web Client 402 call leg by sending a SIP BYE to the Web Client 402 through the Registrar/SIP Proxy 232.

[0300] 6. The Web Client 402 completes the transaction by sending a SIP 200 Ok response to the RTX 102 through the Registrar/SIP Proxy 232.

[0301] 4.6. Call Transfer from Handset to Web Client

[0302] FIG. 10 is a call flow diagram that illustrates the steps performed during Call Transfer, from the handset 120 to the Web Client 402, in one embodiment of the present invention. The steps include the following:

[0303] 1. User A is on a call on the handset 120. User A wants to transfer the call to the Web Client 402 and continue the call. User A presses the appropriate DTMF sequence on the handset 120. The handset 120 sends these DTMF signals in-band to the RTX 102.

[0304] 2. The RTX 102 receives the DTMF signals and interprets the signals as a call transfer to the Web Client 402. It sends a SIP INVITE message to A's Web Client 402 through the Registrar/SIP Proxy 232.

[0305] 3. The Web Client 402 receives the INVITE, presents the call to the user and sends a SIP 180 Ringing response to the RTX 102 through the Registrar/SIP Proxy 232.

[0306] 4. User A now answers the call on the Web Client 402. The Web Client 402 sends a SIP 200 Ok response to the RTX 102.

[0307] 5. The RTX 102 sends a SIP ACK message back to the Web Client 402 to complete the INVITE transaction, after connecting the Web Client 402 call leg to the ongoing call.

[0308] 6. The RTX 102 now disconnects the handset 120 call leg by sending a REL message to the handset 120.

[0309] 7. The handset 120 sends a RLC response to the RTX 102 to complete the transaction.

[0310] 4.7. Call Hold

[0311] The Call Hold function performed by the Web Client 402 is performed through normal SIP mechanisms, and thus the message flow is not shown herein.

[0312] 4.8. Presence Publish

[0313] FIG. 11 is a call flow diagram that illustrates the steps performed during Presence Publication in one embodiment of the present invention. In the Presence Publication function, presence updates are received from the Web Client 402 and the handset 120, and stored on the Presence Server 202. This diagram also describes how the new presence state is synchronized between the handset 120 and the Web Client 402. The steps include the following:

[0314] 1. The Web Client 402 sends a SIP PUBLISH through the Registrar/SIP Proxy 232 to the Presence Server 202 with the presence state set by the user.

[0315] 2. The Presence Server 202 receives the presence state and sends a SIP 200 Ok response back to complete the transaction.

[0316] 3. The Presence Server 202 sets its current time stamp to the presence state.

[0317] 4. The Presence Server 202 synchronizes the new presence state with the handset 120 using the Presence Server 202 protocol.

[0318] 5. The HLR 132 detects changes in the on/off state of the handset 120 and reports these changes to the Presence Server 202 in the RTX 102.

[0319] 6. The Presence Server 202 in the RTX 102 updates the new presence state for handset 120.

[0320] 7. The handset 120 sends a presence state update to the Presence Server 202 in the RTX 102.

[0321] 8. The Presence Server 202 updates the presence state.

[0322] 9. The Presence Server 202 sets its current time stamp to the presence state, and then sends a SIP NOTIFY message on the presence/data change SUBSCRIBE dialog to the Web Client 402.

[0323] 10. The Web Client 402 receives the SIP NOTIFY message and sends back a SIP 200 Ok response to complete the transaction.

[0324] 11. The Web Client 402 sends a HTTP GET request to the Web Server 240 to retrieve the changed data, which includes the new presence state.

[0325] 12. The Web Server 240 sends the changed data to the Web Client 402 in the HTTP 200 Ok response.

[0326] 4.9. Presence Subscription

[0327] FIG. 12 is a call flow diagram that illustrates the steps performed during Presence Subscription in one embodiment of the present invention. The steps include the following:

[0328] 1. User A's Web Client 402 subscribes to the presence states of all of A's contacts by sending a single SIP SUBSCRIBE request to the Presence Server 202. The request is addressed to a special URI (e.g. [email protected]) that is understood by the Presence Server 202 to mean all contacts of the user.

[0329] 2. The Presence Server 202 receives the request and sends a SIP 200 Ok response to complete the transaction.

[0330] 3. The Presence Server 202 then retrieves the list of A's contacts from the Content Server 238 where A's data is stored. In this message flow, user A is assumed to have B and C as contacts, both of whom are RTX 102 subscribers.

[0331] 4. After the list of contacts is obtained, the Presence Server 202 determines which of the contacts are RTX 102 subscribers and obtains their home RTX 102 information from the Location Server 242.

[0332] 5. The Presence Server 202 retrieves B's presence state from B's home RTX 102.

[0333] 6. The Presence Server 202 retrieves C's presence state from C's home RTX 102.

[0334] 7. After obtaining the presence states of all contacts who are RTX 102 subscribers, the Presence Server 202 creates and sends a SIP NOTIFY message to the Web Client 402. The SIP NOTIFY message contains the presence information of these contacts.

[0335] 8. The Web Client 402 receives the SIP NOTIFY message and sends a SIP 200 Ok response to complete the transaction.

[0336] One issue that exists is how does the Presence Server 202 obtain updates to B and C's presence states? It is expected that, as soon as a contact changes his/her presence state, subscribers to that presence state should be notified. For example, a suggested solution is for the Presence Server 202 in the home RTX 102 to report presence state change of any of their subscribers to the Presence Servers 202 of other RTXs 102 immediately. Then, it is up to the Presence Servers 202 in these other RTXs 102 to determine who has subscribed to presence information for this subscriber and notify them appropriately.

[0337] 9. The contact list maintained at the Content Server 238 for user A may be modified, either through the Web Client 402 or through the handset 120 (these messages are not shown).

[0338] 10. The Content Server 238 notifies the Presence Server 202 that A's contact list has changed.

[0339] 11. The Presence Server 202 retrieves the new set of contacts from the Content Server 238.

[0340] 12. The Presence Server 202 retrieves the presence states for any added or modified contacts and discards the presence states for any deleted contacts.

[0341] 13. The Presence Server 202 creates and sends a SIP NOTIFY message to the Web Client 402, containing the presence states of the contacts.

[0342] 14. The Web Client 402 receives the SIP NOTIFY and sends a SIP 200 Ok response back to complete the transaction.

[0343] 4.10. Group SMS Origination and Notification Delivery

[0344] FIG. 13 is a call flow diagram that illustrates the steps performed during Group SMS Origination and Notification Delivery in one embodiment of the present invention. The steps include the following:

[0345] 1. User A selects multiple contacts and initiates a Group SMS (GSM) message. The selected contacts include user B, who also uses the Web Client 402. (Message flows for the other contacts are not shown, as the messaging is through the regular SMS mechanism.) User A's Web Client 402 accepts the message text, and creates and sends a SIP MESSAGE request to the RTX 102 containing the message text and the list of recipients.

[0346] 2. The RTX 102 receives the SIP MESSAGE request and sends back a SIP 200 Ok response to complete the transaction.

[0347] 3. The SIP adapter in the RTX 102 parses the message and triggers a MO-SMS in the GSMS format to be sent to the GSMS module of the RTX 102 (not shown).

[0348] 4. The GSMS module of the RTX 102 receives the MO-SMS and processes it for all recipients (including B's handset 120). In doing so, it determines that user B also runs a Web Client 402, and thus looks up the Location Server 242 to determine which Content Server 238 stores B's data.

[0349] 5. The RTX 102 stores a copy of the GSMS notification in the Content Server 238 along with the rest of B's data.

[0350] 6. The Content Server 238 detects a change in B's data and notifies the Presence Server 202.

[0351] 7. The Presence Server 202 creates and sends a SIP NOTIFY request to B's Web Client 402. The NOTIFY request indicates that B's data has changed on the Content Server 238. This NOTIFY message is sent in the SIP SUBSCRIBE dialog created for presence and data change.

[0352] 8. The Web Client 402 receives the NOTIFY request and sends a SIP 200 Ok response to complete the transaction.

[0353] 9. The Web Client 402 then sends a HTTP GET request to the Web Server 240 to retrieve the changed data.

[0354] 10. The Web Server 240 sends a HTTP 200 Ok response with the changed data, wherein the changed data includes the new GSMS notification.

[0355] 4.11. SMS Notification Delivery

[0356] The RTX 102 delivers other connected service notifications in the same manner as shown in messages #4 to #10 in the GSMS message flow of FIG. 13.

[0357] 4.12. Data Synchronization

[0358] FIG. 14 is a call flow diagram that illustrates the steps performed during Data Synchronization in one embodiment of the present invention.

[0359] In this figure, message flows are shown for various scenarios:

• • [0360] Messages #1 to #2: Data retrieval immediately after login or when the user selects a refresh option.
  • [0361] Messages #3 to #10: Data modification from the handset 120. This includes adding, modifying or deleting contacts or groups, etc. (essentially anything that changes the view on the Web Client 402). The example in the call flow shows adding a contact.
  • [0362] Messages #11 to #16: Data modification from the Web Client 402. The example shows deleting data that is marked for view on the handset 120. For modifications that do not affect the handset 120, messages #14 to #16 will not be used.

[0363] The steps of FIG. 14 include the following:

[0364] 1. The Web Client 402 sends a HTTP request to the Web Server 240 to retrieve the various data for display. This may include contacts, groups (group members are downloaded when a group is opened and are retained in memory thereafter), one or two screens worth of message notifications (older notifications are downloaded upon user request). For VSMS, only the notifications are downloaded; the audio data is downloaded and played when the user opens the message to listen to the message.

[0365] 2. The Web Server 240 retrieves the requested data from the Content Server 238 and includes them in the message body of an HTTP 200 Ok response.

[0366] 3. User A adds a contact on the handset 120. The handset 120 sends a SyncML request to the SyncML Server 412 with the added data.

[0367] 4. The SyncML Server 412 interacts with the Content Server 238 to retrieve and add the new data, and then stores the modified data back into the Content Server 238.

[0368] 5. The SyncML Server 412 sends the modified data back to the handset 120 in the response message.

[0369] 6. The Content Server 238 detects the change in user A's data and triggers the Presence Server 202 to send a SIP NOTIFY message to the Web Client 402.

[0370] 7. The Presence Server 202 sends a SIP NOTIFY message to the Web Client 402 through A's Registrar/SIP Proxy 232. The SIP NOTIFY is sent within the SUBSCRIBE dialog created earlier by the Web Client 402 for presence and data change.

[0371] 8. The Web Client 402 receives the SIP NOTIFY request and sends back a SIP 200 Ok response to the Presence Server 202 through the Registrar/SIP Proxy 232.

[0372] 9. The Web Client 402 then sends a HTTP request to the Web Server 240 to retrieve the changed data.

[0373] 10. The Web Server 240 retrieves the changed data from the Content Server 238 and returns them in the HTTP 200 Ok response.

[0374] 11. User A deletes a notification message from the Web Client 402. This notification happens to be marked as visible on the handset 120. The Web Client 402 creates and sends a HTTP request to the Web Server 240 to delete the notification.

[0375] 12. The Web Server 240 accesses the Content Server 238 and marks the notification message for deletion. It then sends a HTTP 200 Ok response to the Web Client 402 to indicate successful deletion of the notification message.

[0376] 13. The Content Server 238 detects the data marked for deletion, initiated by the Web Client 402. It checks whether the data to be deleted is marked as visible on the handset 120.

[0377] 14. Since the data is marked as visible on the handset 120, the Content Server 238 triggers the SyncML Server 412 to update the handset 120.

[0378] 15. The SyncML Server 412 sends a SyncML request to the handset 120 to update its data, specifying the deleted notification.

[0379] 16. The handset 120 updates its data and sends a SyncML response back to the SyncML Server 412 to indicate successful completion of the request.

[0380] The foregoing description of the preferred embodiment of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not with this detailed description, but rather by the claims appended hereto.