Gateway for wireless mobile clients

• US 20070192495A1
• Filed: 02/16/2006
• Published: 08/16/2007
• Est. Priority Date: 02/16/2006
• Status: Active Grant

• Current Assignee: Taiwan Semiconductor Manufacturing Company Limited
• Original Assignee: Softwired AG
• Inventors: Marais, Charl
• Granted Patent: US 7,739,391 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 76/11 Allocation or use of connection identifiers
• CPC Class Codes: H04W 88/16 Gateway arrangements
• CPC Class Codes: H04W 88/182 Network node acting on behalf of an other network entity, e.g. proxy

Abstract

A method for operating a gateway for wireless mobile clients in a messaging system, the messaging system being configured to comprise a plurality of mobile wireless clients (1, 1′, 1″), a core messaging system (7) and at least one gateway process or gateway (5, 5′, 5″) acting as a proxy on behalf of the clients (1, 1′, 1″), the method comprising the step of

• • the gateway (5, 5′, 5″) storing a session context (11), which session context (11) comprises the status of a session established between the core messaging system (7) and one of the clients (1, 1′, 1″), a state of the client connection associated with the session, and a session identifier which is unique to the session.

Claims

1. A method for operating a gateway for wireless mobile clients in a messaging system, the messaging system being configured to comprise a plurality of mobile wireless clients, a core messaging system and at least one gateway process or gateway, the gateway acting as a proxy on behalf of the clients and, in the course of normal operation of the messaging system, maintaining sessions by performing the steps of,

the gateway receiving inbound messages from the clients over wireless bearers using a wireless protocol and forwarding said inbound messages to the core messaging system over a connection using a wirebound protocol;

the gateway receiving outbound messages from the core messaging system over a connection using a wirebound protocol and forwarding said outbound messages to the clients over wireless bearers using a wireless protocol;

the method further comprising the step of

the gateway storing a session context, which session context comprises the status of a session established between the core messaging system and one of the clients, a state of the client connection associated with the session, and a session identifier which is unique to the session.

2. The method of claim 1, comprising the step of:

the gateway, on reconnection by a client library running on a client device that experienced an abrupt disconnection from the wireless network, reading the state of the client'"'"'s connection/session identified by the received session identifier and recreating, on the client'"'"'s behalf, the wireline connection with the core messaging system in the same precise state that resulted from the operations of the client application, prior to the abrupt disconnection.

3. The method of claim 1, comprising the steps of:

the gateway receiving a connection request from a client, the connection request comprising a session identifier;

the gateway checking whether a stored session context exists that comprises the same session identifier;

if such a stored session context exists, the gateway checking a status of the session represented by said stored session context;

if the status indicates that the session is already running, the gateway informing the client that the connection request is rejected.

4. The method of claim 3, wherein the step of checking the status of the session represented by said stored session context comprises the steps of:

the gateway initiating a lock operation on said session context;

if the lock operation does not succeed, the gateway informing the client that the connection request is rejected;

if the lock operation succeeds, the gateway locking the session context, thus preventing other process threads and optionally also other gateways from accessing the session context.

5. The method of claim 4, comprising the further step of:

the gateway reading a session state stored in the session context;

if the session state is closed, indicating that the session is not active, the gateway opening the session and informing the client that the connection request is accepted.

6. The method of claim 5, comprising the further step of:

if the session state is open, indicating that the session is active, the gateway determining a session owner and a run status of said session owner;

if said run status shows the session owner is not running, the gateway opening the session and informing the client that the connection request is accepted;

if said run status of the session owner is running, the gateway informing the client that the connection request is rejected.

7. The method of claim 1, comprising the step of:

mirroring the session context in a data store that is separated from the gateway.

8. The method of claim 1, wherein the step of the gateway receiving inbound messages from the clients comprises:

the gateway receiving notification of client application operations on the API implemented by the client library over a wireless bearer using a wireless protocol;

and the step of storing the session context comprises;

the gateway recording a change in connection/session state in a session context maintained by the gateway to reflect the precise context within which the client application sends and/or receives messages and persisting the session context to a shared store, as well as propagating the client operation to the core messaging system over a connection using a wirebound protocol;

10. A computer program for operating a gateway for wireless mobile clients in a messaging system, which computer program is loadable and executable on a data processing unit in a gateway computer, the messaging system being configured to comprise a plurality of mobile wireless clients, a core messaging system and the gateway computer for providing message forwarding from the clients to the messaging server and vice versa, and which computer program, when being executed on the gateway computer, performs the steps of the method of claim 1.

9. A gateway computer for wireless mobile clients in a messaging system, the messaging system being configured to comprise a plurality of mobile wireless clients and a core messaging system, with the gateway computer comprising at least one gateway process or gateway for acting as a proxy on behalf of the clients and, in the course of normal operation of the messaging system, for maintaining sessions by performing the steps of,

the gateway receiving inbound messages from the clients over wireless bearers using a wireless protocol and forwarding said inbound messages to the core messaging system over a connection using a wirebound protocol;

the gateway receiving outbound messages from the core messaging system over a connection using a wirebound protocol and forwarding said outbound messages to the clients over wireless bearers using a wireless protocol;

the gateway further comprising a session manager for storing a session context, which session context comprises the status of a session established between the core messaging system and one of the clients, a state of the client connection associated with the session, and a session identifier which is unique to the session.