US20070281680A1

US20070281680A1 - Method and system for extending services to cellular devices

Info

Publication number: US20070281680A1
Application number: US11/422,173
Authority: US
Inventors: Vish Raju; Alain Mouttham
Original assignee: Firsthand Technologies Inc
Current assignee: Firsthand Technologies Inc
Priority date: 2006-06-05
Filing date: 2006-06-05
Publication date: 2007-12-06
Also published as: US9131006B2; WO2007140582A1; EP2030464A4; US20070281682A1; US8165576B2; EP2030464A1; US20120157059A1

Abstract

A system is provide for extending services to cellular devices. The system includes a wireless gateway having a client side with an intelligent client agent and a server side with an intelligent server agent, a wireless device having a first mode operable in a cellular system and a second mode operable in a wireless local area network and including an intelligent client agent for determining operation mode and for communicating with the intelligent client agent of the wireless gateway and a communications protocol for communication between the wireless gateway intelligent client agent and the wireless device intelligent client agent to effect services. The services include one or more of voice, directory, presence, and media services. The voice service includes at least one of call waiting, call forwarding conferencing, and caller identification. The media service includes at least one of interactive voice response (IVR), text-to-speech, speech recognition, play, record. The directory service includes a public switched telephone network (PSTN) directory, a cellular network directory, an Internet directory and a private branch exchange (PBX) directory. The communications protocol includes encapsulation for at least one of directory, mobility and security services and other protocols. The other protocols include at least one of Internet protocol (IP), session initiation protocol (SIP), and lightweight directory access protocol (LDAP).

Description

FIELD OF THE INVENTION

The present invention relates to methods and systems for extending services to cellular devices and is particularly concerned with using session initiation protocol.

BACKGROUND OF THE INVENTION

There have be proposals on how to extend services to cellular phone users. For example, in U.S. Pat. No. 6,993,360, a mobile branch exchange (MBX) allows a user of a mobile telephone to exploit the functionality of a private branch exchange (PBX) as if the user were using a PBX-connected wire line telephone in an office setting. However, this proposal uses computer telephony integration (CTI), which may lead to a complex solution that may not scale easily.
Session initiation protocol (SIP) was developed for interactive user session involving multimedia. It has become one of the leading signaling protocols for voice over IP (VoIP). There are now many services available based upon the SIP protocol. Unfortunately, a large number of subscribers do not have access to such services. These are subscribers to cellular systems.
Consequently, there is a need in the prior art for a method and system for providing session initiation protocol (SIP) services to cellular wireless devices.

SUMMARY OF THE INVENTION

An object of the present invention is to provide an improved method and system for extending services to cellular devices.
A system for seamlessly extending enterprise services to multi-modal wireless devices comprising: a wireless communication gateway having a client side with an intelligent client agent and a server side with an intelligent server agent; a wireless device having a first mode capable of both voice and data operable in a wide-area cellular network and a second mode operable in a wireless local area network and including an intelligent client agent for determining operation mode and for communicating with the intelligent server agent of the wireless communication gateway to setup and maintain continuity of services as it roams within and between networks; and a communications protocol for communication between the wireless communication gateway intelligent server agent and the wireless device intelligent client agent to setup and maintain continuity of services.
A system for seamlessly extending enterprise services to wireless devices comprising: a wireless communication gateway having a client side with an intelligent client agent and a server side with an intelligent server agent; a wireless device having a first mode capable of both voice and data operable in a wide-area cellular network and including an intelligent client agent for communicating with the intelligent server agent of the wireless communication gateway to setup and maintain continuity of services as it roams within the network; and a communication protocol for communication between the wireless communication gateway intelligent server agent and the wireless device intelligent client agent to setup and maintain continuity of services.
A system for seamlessly extending enterprise services to wireless devices comprising: a wireless communication gateway having an intelligent server agent; a wireless device having a data mode operable in a wide-area cellular network and including an intelligent client agent for communicating with the intelligent server agent of the wireless communication gateway to setup and maintain continuity of services as it roams within the network; a voice device accessible by the wireless communication gateway intelligent server agent; a communication protocol for communication between the wireless communication gateway intelligent server agent and the wireless device intelligent client agent to setup and maintain continuity of services; whereby the services provided combine the use of a data channel on the wireless device and a voice channel on the voice device, both being controlled by the intelligent client agent and the intelligent server agent.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be further understood from the following detailed description with reference to the drawings in which:

FIG. 1 illustrates in a block diagram showing an example of a system for extending services into a cellular network;

FIG. 2 illustrates in a block diagram application software that runs inside the wireless dual mode device of FIG. 1;

FIG. 3 illustrates the wireless communications gateway of FIG. 2 in further detail;

FIG. 4 illustrates the convergence services session manager of FIG. 3 in further detail;

FIG. 5 illustrates the proprietary protocol that is used to communicate over the cell data network;

FIG. 6 shows a screen shot of the mobile console client homepage;

FIG. 7 shows a screen shot of the SMS inbox;

FIG. 8 shows a screen shot of the SMS compose page;

FIG. 9 shows a screen shot of the SMS reply window;

FIG. 10 shows a screen shot of the mobile console client new text message notification;

FIG. 11 shows a screen shot of the mobile console client configuration for notification;

FIG. 12 shows a screen shot of the mobile console client saving to Outlook; and

FIG. 13 shows a screen shot of the Outlook with messages saved from the mobile client.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Referring to FIG. 1 there is illustrated in a block diagram an example of a system architecture for extending services into a cellular network. The system hardware includes a LAN (0) to which is connected:

- a wireless communication gateway (11)
- PBX (12)
- SIP phones (13)
- workstations (14)
- SIP servers (1)
- a base station network (5)
- a directory services server (2)
- a presence server (3)
- a firewall/router (10, 9)
- a PSTN gateway (4)
- a media server (37)

This system facilitates the extension of enterprise services to mobile wireless devices. These devices can be wide area cellular (Class A or B, both data and voice) or dual mode: wide area cellular (Class A or B, both data and voice) and Local Area Wireless. As roaming occurs, inside or between networks, the user is left unaware. In the case of dual mode devices, the user is given the same UI for invoking the services and the underlying mode is transparent to the user.
The intelligent client and server agents are responsible for this transparency. They select the network, maintain the connections and apply policies for the user under-the-hood. These policies can be configured by the user or the system administrator.
Services available can include Voice calls and features, Instant Messaging, Presence, Directory Services, IVR and Conferencing.
In Voice Services, a single number can be used by anyone wanting to call the user, and will be sent as the CLID when the user makes a call from the enterprise. The mobile wireless device can have the same extension number as an IP PBX phone (shared line), or can be an extension on its own. In the case of a shared line, calls can be moved from the IP PBX phone to the mobile wireless device and vice versa. Features available on the IP PBX are also available on the mobile wireless device. The user also has his cell phone number which can be reached or used independently of the enterprise number.
The system architecture includes both a data network and a voice network. The data network includes one or more local area networks (LANs) (0) connected to the wide area network (WAN). The voice network can use both traditional circuit switched nodes 8 b as well a voice over IP (VoIP) nodes 8 a, which utilize the data network to communicate. The voice network spans both the enterprise domain and the public domain.
Devices/boxes connected to the data network (including VoIP devices) typically include in memory a unique network address such as an IP address. This allows data packets to be routed to the device (phone, server, gateway, base station, desktop, etc.)
Devices 15 connected to the circuit switched voice network use traditional telephony addressing (telephone numbers or extensions). They are connected with standard interfaces such as T1 trunks, digital lines, etc.
In operation, the PBX (12) uses SIP to communicate with the SIP servers (1) and is connected via the LAN (0) via firewall 10 and router 9. The PBX (12) is connected to phones (16) via circuit-switched connections. The PBX (12) can be connected to the PSTN (8 b) either via the PSTN gateway (4) or it can be directly connected (not shown).
The SIP servers (1) are connected to the PSTN gateway (4) via the LAN (0). The PSTN gateway (4) translates SIP into various PSTN protocols. The SIP phones (13) are connected to the SIP Servers (11) via the LAN (0).
The wireless communication gateway (11) talks to the SIP servers (1) using SIP via the LAN (0). The wireless communication gateway (11) is connected to the Internet (8 a) through the LAN (0). The directory services (2) use LDAP to communication with the wireless communication gateway (11) and are connected via the LAN (0). The presence server (3) uses SIP (SIMPLE) to communicate with the wireless communication gateway (11) and is connected via the LAN (0).
There are wireless devices (6 a, 6 b), which provide connectivity to the cell phone network (7) via GSM/CDMA, and in the case of dual mode devices, to the base station network (5) via WiFi. The cell network (7) connects to the PSTN (8 b) and the Internet (8 a). Any voice calls will travel from the cell network to the PSTN via trunks, and data packets will travel from the cell network to the Internet. An external voice user phone (15) is connected to the PSTN via trunks.
Note: All boxes shown in building can be integrated into many different combinations. For example, the PBX and SIP Servers could be in one box, the wireless communication gateway could be in the same box as the SIP servers, or the SIP servers and the PBX.
FIGS. 2 through 4 show a possible internal software architecture. It assumes that the software is running in an operating system such as Linux, Windows, etc. and has access to memory and data. SIP user agents are a well-known software entity. Each block identified can be implemented as a software process that can exchange information with other software processes in known ways including messages, invoking external procedures, and shared memory access.
In operation, the media gateway 37 of FIG. 1 is used for interactive voice response (IVR) and conferencing functionality. In the case of a third-party gateway, the SIP proxy user agent (26) uses SIP to communicate with it. When using the media gateway, a higher degree of functionality can be offered.
Media gateways offer the following functionality:

- Conferencing
- Play
- Record
- Text-to-Speech
- Speech Recognition

Conferencing: There are two types of conferences, ad-hoc and group call.

- Ad-hoc conferences are set up when a user is in a call, and decides to call someone else and create a conference between all three parties.
- Group call is when a user selects or creates a group list and then requests that everyone in the list be added to a conference.

Play: A previously recorded message can be played to a user or a conference.
Record: Messages, calls or conferences can be recorded and stored.
Text-To-Speech: Words can be converted to speech and played to a user or a conference.
NOTE: This functionality can exist in a separate media sever (37) or could reside inside the wireless communications gateway (11).
Referring to FIG. 2 there is illustrated in a block diagram application software that runs inside the wireless dual mode device of FIG. 1. There is application software that runs inside the wireless device (6 a, 6 b) to manage:

- the interaction of the device with the wireless communication gateway (11);
- consistency of the display, no matter what mode the device is in;
- the interaction of the device with the SIP server (1) when in WiFi mode; and
- security.

The application software includes:
An intelligent client agent (70) that includes:

- roaming agent (17)
- cellular phone user agent (21)
- WiFi SIP user agent (20)
- convergence services agent (22)
- policy manager (24)
- security agent (50)

The wireless dual mode device application software includes a roaming agent (17) for monitoring the WiFi interface (18) and the cell interface (19) and determining which mode the phone should be using. The roaming agent (17) then communicates with the convergence services agent (22), which in turn enables either the WiFi SIP user agent (20) or the cellular phone user agent (21). The convergence services agent (22) can also use policies from the policy manager (24) to determine which mode is applicable. The convergence services agent (22) is also responsible for interacting with the display on the device and making sure that the correct options (also based on policy) are presented to the user in a uniform way regardless of function or mode. The convergence services agent (22) also uses the security agent (50) to encrypt/decrypt messages, collect PINs and passwords and invoke a ‘kill’ command. The kill command causes the cell phone to be unusable, and the data on it inaccessible.
Referring to FIG. 3 there is illustrated the wireless communications gateway of FIG. 2.
The application software runs inside the wireless communication gateway (11) to:

- Manage the interaction of the dual mode device while in cell mode with the SIP servers (1);
- Interact with supplementary services to provide them to the mobile wireless device; and
- Interact with directory services to get information and send it to the mobile wireless device.

The intelligent service agent (71) is responsible for the above functions and includes wireless communication gateway application software having an LDAP connector (25) that manages the interface with directory services (2). A SIP proxy user agent (26), which acts like a proxy for the mobile wireless device while it is in cell mode. The device uses its own WiFi SIP user agent (20) while in WiFi mode, but when it switches to cell mode, it needs the SIP proxy user agent (26) to act for it. There also can be proprietary connectors (27) that can talk specific proprietary protocols to access other supplementary services.
In operation, the convergence services session manager (28) sends and receives messages using a special convergence protocol (see FIG. 5) over the data cell network to the convergence services agent (22) on the dual mode device. The convergence services session manager (28) communicates back and forth with the SIP proxy user agent (26) for SIP service requests/responses, translating to and from the convergence protocol. The convergence services session manager (28) also communicates with the LDAP connector (25) for directory services requests/responses translating to and from the convergence protocol.
The convergence services session manager (28) is part of the intelligent server agent (71). It is responsible for:

- receiving and sending convergence protocol (see FIG. 5) messages
- translating to and from the convergence protocol (see FIG. 5) to SIP or LDAP or a proprietary protocol
- managing the various sessions between all the mobile wireless devices (6 a, 6 b)
- managing the need for a SIP proxy user agent (26) for the mobile wireless device (6 a, 6 b) while in cellular mode
- managing policies related to users using mobile wireless devices (6 a, 6 b)
- and keeping the data connections with the mobile wireless devices (6 a, 6 b) alive
- security

The convergence services session manager software includes a translator (30), which is responsible for translating between SIP, LDAP, and any proprietary protocol and the convergence protocol.
It also includes a session manager (29), which keeps track of all of the various sessions underway with all the mobile wireless devices (6 a, 6 b). The session manager (29) gets messages from the input/output adaptor (31), and determines which session they belong to. If necessary, it then uses the translator (30) to translate them into the appropriate protocol (LDAP, SIP, proprietary), consults the policy manager (33) to see if any policies apply, then passes the newly translated message on to either the SIP, proprietary or LDAP connectors. The session manager 29 manages requests received from the input/output adaptor to create a SIP proxy user agent (26) using the mobility manager (34), and also consults the policy manager (33) to see if any policies apply. The session manager (29) also uses the security agent (51) to encrypt/decrypt messages, check PINs and Passwords and if set by the administrator, administer a ‘kill’ command to a client. The kill command is used in the case where a cell phone is lost or stolen. By setting a special flag through the administration function, this security agent can send an encrypted message to the cell phone intelligent client agent (70) that renders the cell phone unusable, and the data on it inaccessible.
The policy manager uses policy data stored in a database (35).
The session manager (29) uses the session controller (32) to make sure that a data connection is maintained to all the active mobile wireless devices (6 a, 6 b). It creates pinholes through the firewall and uses a keep-alive mechanism to accomplish this.
Referring to FIG. 4 there is illustrated the convergence services session manager of FIG. 3. The convergence services session manager software includes a translator (30), which is responsible for translating between SIP, LDAP, and any proprietary protocol and the convergence protocol. The convergence services session manager also includes a session manager (29), which keeps track of all of the various sessions underway with all mode wireless devices (6 a, 6 b). The session manager (29) gets messages from the input/output adaptor (31), and determines to which session they belong. If necessary, the convergence services session manager then uses the translator (30) to translate the messages into the appropriate protocol (LDAP, SIP, proprietary), consults the policy manager (33) to see if any policies apply, then passes the newly translated message on to either the SIP, proprietary or LDAP connectors. The convergence services session manager also manages requests received from the input/output adaptor to create a SIP proxy user agent (26) using the mobility manager (34), and also consults the policy manager (33) to see if any policies apply.
FIG. 5 illustrates the proprietary protocol that is used to communicate over the cell data network. The convergence protocol is a proprietary protocol which encapsulates all of the SIP services, directory services and mobility services that would normally be part of the SIP and LDAP protocols. These are adapted into a package to address security, device mobility including changes in IP address, firewall and bandwidth issues to do with the cellular network.
The convergence protocol provide the following:

- Extensibility: the protocol can easily be extended to allow additional functionality;
- Anti-theft security: the protocol allows for the wiping of all sensitive data from the device in the event of loss or theft;
- Persistent session maintenance during periods of signal loss (eg. during flights etc); allows the enterprise user to retrieve all event data upon reconnection (missed calls etc);
- Allows tracking of GPS data on the device for enterprise location services

In operation, when the dual mode wireless device (6 a) is in WiFi mode, it has its own SIP user agent (20) which communicates directly with a SIP Server (1). When the phone goes out of range for WiFi, the software in the phone (see FIG. 2) determines this, and then requests the wireless communication gateway (11) to act on behalf of the phone. It does this by instantiating a “proxy” SIP user agent (26) which registers with the SIP server (1), and then uses a proprietary protocol that travels over the cell data network from the phone software to the gateway to pass information. This protocol mimics all the functionality that the normal WiFi connection has available, but does it in a way that addresses security, firewall and bandwidth issues that are inherent in cell networks.

1. Change from WiFi to Cell Mode

Referring to FIG. 2, the roaming agent (17) is monitoring the WiFi signal strength. When the roaming agent (17) determines that the WiFi signal is no longer viable, it informs the convergence services agent (CSA) (22), which communicates with the WiFi SIP user agent (20). The WiFi SIP then determines what to do with any existing sessions. This could include handing the call off to the cellular phone user agent (21). The WiFi SIP then communicates with the CSA (22) to update the display appropriately. The CSA (22) then asks the WiFi SIP user agent (20) to shut down. The CSA (22) then checks any policies with the policy manager (24), which could include policies on whether this user is enabled for service continuity on the cellular side. If everything is okay, the CSA (22) then enables the cellular phone user agent (CPUA) (21). The CPUA (21) then tries to establish a connection with the wireless communications server (WCS) (11) (see FIG. 1 and FIGS. 3, 4). Once a connection has been established, the roaming agent (17) then informs the CSA (22).
Referring to FIG. 3 and FIG. 4, the input/output adapter (31) informs the session manager (29) that a device wishes to establish a new connection. The session manager (29) passes this to the mobility manager (34), which then checks with the policy manager (33) to see if system, user, and device level policies and profiles allow this connection. If everything is ok, the session manager (29) creates a new instance of a SIP proxy user agent (26), which registers with a SIP server (1). The SIP proxy user agent (26) also reestablishes all the subscriptions for presence information for the user's buddy list. If this is successful, then the session controller (32) is informed so it can keep a data connection alive between the WCS (11) and the device. The session manager (29) then sends a message to the CSA (22) through the input/output adapter (31), informing it of the success. Finally the CSA (22) updates the display, informing the user of the successful change.

2. Incoming Call in Cell Mode

When an incoming call is received at the SIP server for the user, SIP will broadcast this to all registered devices. Referring to FIG. 3 and FIG. 4, the SIP proxy user agent (26) will receive this request, and will pass it to the session manager (29). The session manager (29) then uses the translator (30) to translate the message into the convergence protocol. The session manager then uses the input/output adapter (31) to send the message to the cellular phone user agent (CPUA) (21) on the mobile wireless device (MDWD) (6 a, 6 b).
Referring to FIG. 2, the CPUA (21) receives the request, and then passes it to the convergence services agent (CSA) (22), which displays the call to the user, with options and calling line ID. If the user selects the option to answer the call, then the CSA (22) informs the CPUA (21), which sends a convergence protocol accept message through the cell interface software (19) back to the convergence services session manager (CSSM) (28). This message includes the phone number or SIP address of where to send the call.
Referring to FIG. 4, the accept message is received by the input/output adapter (31) and passed to the session manager (29) that figures out which session it is for, and then uses the translator (30) to create a SIP redirect message which is then given to the SIP user agent (26). The SIP user agent (26) then uses the SIP redirect mechanism to redirect the call through the PSTN gateway (4) to the number received in the accept message.

3. Accessing a Buddy List with Presence Information and Making a Call in Cell Mode

Referring to FIG. 4, when there are updates to presence information, the SIP proxy user agent (26) is informed, and it informs the session manager (29). the session manager then uses the translator (30) to create an update buddy message in the convergence protocol and then sends it to the convergence services agent (22) through the input/output adapter (31).
Referring to FIG. 2, the convergence services agent (CSA) (22) receives the update buddy message and saves the new presence information. When the user selects to access the buddy list on the display, the buddy information, along with the presence information is displayed. The user selects a buddy and chooses to make a call. This is given to the CSA (22), which checks with the policy manager (24), and determines whether the call should go directly out on the cellular network, or should go through the SIP server (1) so that it is presented and billed properly. If the call is to go through the SIP server (1), the CSA 22 sends a convergence protocol invite message, including the buddy information to the convergence services session manager (28) through the cell interface software (19).
Referring to FIG. 4, the input/output adaptor (31) receives this invite message and passes it to the session manger (29). The session manager determines which session this applies to and then translates the message into SIP using the translator (30), and passes it to the SIP proxy user agent (26). The SIP proxy user agent (26) establishes a SIP call to the cell user first, and when the answer occurs the SIP proxy user agent (26) does an SIP invite to the selected buddy, and then a SIP refer to transfer the cell phone call to the called party.

Advanced Functionality

In the simple call scenarios that were described previously, once the call is established, the WCG (11) is no longer involved. However, when you want to offer more than simple call functionality, such as hold, transfer, conference, call waiting, then things become more complicated.
Most cell phones today are Class B, which means that they can be connected to GPRS service and GSM service (voice, SMS), but using only one or the other at a given time. During GSM service (voice call or SMS), GPRS service is suspended, and then resumed automatically after the GSM service (voice call or SIMS) has concluded.
By contrast, Class A cell phones can be connected to CPRS service and GSM service (voice, SMS), using both at the same time. In order to invoke in-call features, an indication must be sent to the WCG (11). Prior art uses SMS messaging to do this, but it has problems in that it can be very slow. In order to make these features happen in real time, the solution is achieved by combining the WCG (11) functionality with the media server functionality.
In this case, the SIP proxy user agent (26) is not enough, we need a back-to-back user agent (B2BUA) (38). The B2BUA (38) registers at the PBX (12) on behalf of the mobile wireless device user, and acts as a proxy to both ends of a Session Initiation Protocol (SIP) call. The B2BUA is responsible for handling all SIP signaling between both ends of the call, from call establishment to termination. Each call is tracked from beginning to end, allowing the operators of the B2BUA to offer value-added features to the call. This functionality is present in the media server (37) for conferencing. By extending this concept, all calls that want in-call features can be created as pseudo 2-party conferences, with added functionality.
In the case of a normal incoming or outgoing call, instead of using the SIP Redirect or Refer functionality, two SIP calls are set up, both terminating on the B2BUA (38).
When a Class A cell phone is used, then there can be both a Voice and Data channel available at the same time. In this case, DTMF messaging is not needed, but a relationship between the voice and data session must be maintained. This is handled by the intelligent client/server agents. This also applies to the case where there are two devices involved, one to handle the voice and the other to handle the data. When the user decides to make a call, they can specify the device that they wish the voice call to be established on. If they choose a different device than the one originating the request, then they can choose to manage the voice call through a data channel to the originating device. For example, a PDA could be used to set up a call with a SIP phone (13) being the target voice device. Once the voice call is established, the PDA can be used to manage features for that voice call (see example features below).

1. Incoming Call:

When the broadcast to registered users occurs, and the cell phone accepts the call, then the B2BUA (38) is invoked instead of the SIP proxy user agent (26) and the B2BUA (38) answers the incoming call by using the SIP accept (typical SIP protocol), and makes a new call to the cell phone (through the PSTN Gateway (4)), which is automatically answered by the cellular phone user agent (21). Voice packets are then streamed through the WCG (11) and the B2BUA (38).

2. Outgoing Call:

Instead of the SIP proxy user agent (SPUR) (26), the B2BUA (38) acts as the calling party for both calls, and stays in the middle, unlike the SPUA (26) which does a Refer and then is no longer part on the call.

3. In Call Features

Hold, Transfer, Ad-Hoc Conference: Now that the B2BUA (38) has control over both parts of the call, including the voice path, in-call features can be added. Since we no longer have a data connection back to the WCG (11), another signaling method must be used. In this case, it is DTMF signaling that will be used to invoke different features.
Referring to FIG. 2, the user will still have a unified display for invoking features. When they select an in-call feature, the convergence services agent (22) will then use pre-stored data to cause the cellular phone user agent (21) to out pulse a particular DTMF stream.
The PSTN gateway (4) will receive these DTMF digits and convert them into SIP DTMF messages. It then sends these to the B2BUA (38).
The B2BUA (38) receives these DTMF messages and uses digit conversion (40) functionality provided by the media server (37) to convert them into the correct function and then uses the SIP equivalent to invoke the feature on the PBX.
If a separate data channel is available, then instead of DTMF, a connection between the data call and the voice call is made (‘super-session’) between the intelligent client agent (70) and the intelligent server agent (71). Messages to invoke the features will be sent using the convergence protocol.

4. Call Waiting:

When a call waiting is offered to the B2BUA (38), it uses a play function to inject a quick tone or message to the mobile wireless device user call to let them know that a call is waiting. The message can be pre-canned, or it can also use text-to-speech functionality to say the name of the person calling if there is calling line ID available. This can be done in one of two ways. Either a “conference” is created and the play function is injected into the call so that both parties can hear it, or the connection between the two parties is temporarily broken, and the sound is played and only heard by the mobile wireless device user.

5. Group Call:

Group call can be set up in one of two ways. Either the list of members is set up previously and stored in the WCS (11) and the mobile wireless device user selects this list, or the mobile wireless device user creates a new list of people to make the call to. In the first case, the convergence services agent (22) conveys the conference request along with which list has been selected using the convergence protocol to the convergence services session manager (CSSM) (28), who then retrieves the list of users from the database. In the second case, the convergence services agent (22) conveys the conference request along with the list of users using the convergence protocol to the CSSM (28). (FIG. 2)
Once the list of users has been determined, the CSSM (28) gives the request to the media server (37), which then sets up the conference.
Added functionality can be put into the conference set up. The play function can be used to inform potential members of the conference, and who is setting it up with or without Text-to-Speech. The user can choose to accept or not, and the DTMF response can trigger the call. The media server (37) makes a call to the conferee, and acts as the endpoint for the SIP call. The conferee could also have the option of delaying his entrance, and this can be announced into the conference via a play function to conferees. As members join, they can use DTMF to ask for a list of members in the conference, which again could be played to them. Members leaving the conference could also use this type of functionality.
The conference can also be created using mixed-mode. This would need a separate voice and data channel. In this case, instant messaging and voice conferences could be set up at the same time, so that members can talk in the conference, but also have a list of conference members in a special IM session, and choose to side-bar through text with one or more of the members. Instant messaging can be used to inform potential members of the conference, and who is setting it up. They can choose to accept or not, and the typed response can trigger the voice call. The media server (37) makes a voice call to the conferee, and acts as the endpoint for the SIP call. The conferee could also use IM to delay his entrance to the conference, which can be sent to the members via and instant message (IM). Members leaving would have their status updated in the IM window. The advantage to this functionality is that the conference isn't being inundated with messages as people come and go, and as people join, they are given an immediate view of who is in the conference, who is going to be in the conference, and who has not accepted, getting rid of the need to announce all the members via voice every time someone new joins.
Referring to FIGS. 7 through 14 there are illustrated screen shots for a mobile console operable on the wireless device of FIG. 1. The mobile console client supports short messaging through both the cellular radio and WiFi packet interfaces shown in FIG. 2. The mobile console client provides an integrated interface for sending and receiving SMS messages through both the cellular and WiFi accesses. The mobile console provides the device user with a uniform experience in terms of composing, viewing, sending and receiving short text messages regardless of the network being used. The mobile console client also allows the wireless device (6) to receive and decode text messages containing voicemail waiting indications through either network and to display these indication in its graphic user interface (GUI). The reception of a short text message does not interfere with a voice session in progress.
Referring to FIG. 6, there is shown a screen shot of the mobile console client homepage where the SMS view is invoked from the SMS icon on the status bar.
FIG. 7 shows a screen shot of the SMS inbox. The SMS view shows the inbox with the received SMS/IM messages. Selecting the Inbox window displays the contents of the SMS in the window frame below the inbox as shown in FIG. 2. The inbox window also shows the network (WiFi or Cell) on which the message was received, the start of the message and the received date and time.
FIG. 8 shows a screen shot of the SMS compose page. To compose an SMS message, the user clicks on the “Compose: link, which opens up the Compose Window as shown in FIG. 9. The current active network is selected by default. The network (WiFi or Cell) radio button is enabled only if the network is registered. IF the network is not registered or unavailable, the radio button is grayed out and is not available for selection. If the user is sending an IM, the user can enter the fully qualified SIP URI (e.g., sip:280@10.1.0.238) or just the user name (e.g. 280). If the user is sending an SMS on the cell network, the user centers the destination number to send the SMS.
FIG. 9 shows a screen shot of the SMS reply window. To reply to a received SMS, the user selects the SMS message in the inbox window and clicks the reply link. This opens the Compose window with the recipient address filled in the “to” window as shown in FIG. 10.
FIG. 10 shows a screen shot of the mobile console client new text message notification. If there is an incoming message and the “SMS Notification” in the Settings→Advanced page has been set to “Yes” as shown in FIG. 12, the user is notified when there is a new incoming text message as shown in FIG. 11. When a new SMS/IM is received a notification balloon pops up as shown in FIG. 11
FIG. 11 shows a screen shot of the mobile console client configuration for notification. To delete an SMS, select the SMS in the inbox window and click the “Delete” link.
FIG. 12 shows a screen shot of the mobile console client saving to Outlook. The “Save to Outlook” option saves the cellular messages to the Outlook text messages inbox as shown in FIG. 12. The messages in the SMS messages folders are persistent.
FIG. 13 shows a screen shot of the Outlook with messages saved from the mobile client.

Claims

1. A system for seamlessly extending enterprise services to multi-modal wireless devices comprising:

a wireless communication gateway having a client side with an intelligent client agent and a server side with an intelligent server agent;

a wireless device having a first mode capable of both voice and data operable in a wide-area cellular network and a second mode operable in a wireless local area network and including an intelligent client agent for determining operation mode and for communicating with the intelligent server agent of the wireless communication gateway to setup and maintain continuity of services as it roams within and between networks; and

a communications protocol for communication between the wireless communication gateway intelligent server agent and the wireless device intelligent client agent to setup and maintain continuity of services.

2. A system as claimed in claim 1 wherein the services include one or more of voice, directory, presence, and media services

3. A system as claimed in claim 2 wherein the voice service is accessible by the enterprise number no matter what mode it is in and voice service includes at least one of call waiting, call forwarding, conferencing, caller identification.

4. A system as claimed in claim 2 wherein the media service includes at least one of interactive voice response (IVR), text-to-speech, speech recognition, play, record and conferencing.

5. A system as claimed in claim 1 wherein the communications protocol includes encapsulation for at least one of voice, directory, mobility and security services.

6. A system as claimed in claim 5 wherein the communications protocol includes encapsulation for other protocols.

7. A system as claimed in claim 6 wherein the other protocols include at least one of Internet protocol (IP), session initiation protocol (SIP), lightweight directory access protocol (LDAP), line information database (LIDB) and caller name display (CNAM).

8. A system as claimed in claim 5 wherein the security service includes end-to-end security.

9. A system as claimed in claim 1 wherein the wireless device intelligent client agent includes a graphical user interface (GUI) for providing a similar user interface in both the first and second modes.

10. A system as claimed in claim 1 wherein the first mode of the wireless device is class A or class B.

11. A system for seamlessly extending enterprise services to wireless devices comprising:

a wireless device having a first mode capable of both voice and data operable in a wide-area cellular network and including an intelligent client agent for communicating with the intelligent server agent of the wireless communication gateway to setup and maintain continuity of services as it roams within the network; and

a communication protocol for communication between the wireless communication gateway intelligent server agent and the wireless device intelligent client agent to setup and maintain continuity of services.

12. A system as claimed in claim 11 wherein the services include one or more of voice, directory, presence, and media services

13. A system as claimed in claim 12 wherein the voice service accessible by the enterprise number and voice service includes at least one of call waiting, call forwarding, conferencing, and caller identification.

14. A system as claimed in claim 12 wherein the media service includes at least one of interactive voice response (IVR), text-to-speech, speech recognition, play, record, and conferencing.

15. A system as claimed in claim 11 wherein the communications protocol includes encapsulation for at least one of voice, directory, mobility and security services.

16. A system as claimed in claim 11 wherein the communications protocol includes encapsulation for other protocols.

17. A system as claimed in claim 16 wherein the other protocols include at least one of Internet protocol (IP), session initiation protocol (SIP), lightweight directory access protocol (LDAP), line information database (LIDB) and caller name display (CNAM)

18. A system as claimed in claim 11 wherein the wireless device is a class A device

19. A system as claimed in claim 11 wherein the wireless device is a class B device

20. A system as claimed in claim 11 wherein the first mode of the wireless device is class A or class B.

21. A system as claimed in claim 20 wherein the dual modes are cellular network and wireless local area network modes.

22. A system as claimed in claim 15 wherein the security service includes end-to-end security.

23. A system for seamlessly extending enterprise services to wireless devices comprising:

a wireless communication gateway having an intelligent server agent;

a wireless device having a data mode operable in a wide-area cellular network and including an intelligent client agent for communicating with the intelligent server agent of the wireless communication gateway to setup and maintain continuity of services as it roams within the network;

a voice device accessible by the wireless communication gateway intelligent server agent;

a communication protocol for communication between the wireless communication gateway intelligent server agent and the wireless device intelligent client agent to setup and maintain continuity of services;

whereby the services provided combine the use of a data channel on the wireless device and a voice channel on the voice device, both being controlled by the intelligent client agent and the intelligent server agent.

24. A system as claimed in claim 23, wherein the voice channel services includes at least one of: IVR, call waiting, call forwarding, conferencing, hold, transfer, shared line, pickup or call park, and the data channel services include the means for invoking them and controlling them.

25. A system as claimed in claim 23, wherein the data channel services includes at least one of directory or presence services.

26. A system as claimed in claim 23 wherein the communications protocol includes encapsulation for at least one of voice, directory, mobility and security services.

27. A system as claimed in claim 23 wherein the communications protocol includes encapsulation for other protocols.

28. A system as claimed in claim 27 wherein the other protocols include at least one of Internet protocol (IP), session initiation protocol (SIP), lightweight directory access protocol (LDAP), information database (LIDB) and caller name display (CNAM).

29. A system as claimed in claim 23 wherein the wireless device is a class A device.

30. A system as claimed in claim 23 wherein the wireless device is a class A device and the voice channel is provided by this device.

31. A system as claimed in claim 23 wherein the wireless device is a class B device.

32. A system as claimed in claim 23 wherein the wireless device is a dual mode device.

33. A system as claimed in claim 33 wherein the dual modes are cellular network and wireless local area network modes.

34. A system as claimed in claim 26 wherein the security service includes end-to-end security.