Pre-Grant Publication Number: 20070192495
Collaborate on the process of community review for this application. Posting will not be forwarded to the USPTO.
Flagging a post as an ACTION ITEM signals further research. Flagging SPAM and ABUSE helps to manage discussion.
Placing double brackets around a reference to a claim or prior art will create a hyperlink to the original
ex. [[claim 1]] and [[prior art 2]].
Facilitator's Comment 
Action Item Show without Noise
<claim-text> 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, <claim-text>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; </claim-text><claim-text>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; </claim-text><claim-text>the method further comprising the step of </claim-text><claim-text>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. </claim-text></claim-text>
PCUs and RNCs are gateways between GSM's wireless data protocols GPRS and UMTS respectively and the Gb interface, which is a wired data interface (IP or frame relay). An associated device, the SGSN maintains a session context called the PDP context, maintains the client connection, and maintains a session identifier which is unique to the session (NSAPI) it connects to the GGSN over a Gn interface. There is nothing novel about combining the PCU and SGSN or the RNC and the SGSN into a single box. This is not done in practice because the SGSN is radio protocol independent and the PCU and RNC are radio protocol dependent. more...
<claim-text> The method of <claim-ref idref='CLM-00001'>claim 1</claim-ref>, comprising the step of: <claim-text>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. </claim-text></claim-text>
<claim-text> The method of <claim-ref idref='CLM-00001'>claim 1</claim-ref>, comprising the steps of: <claim-text>the gateway receiving a connection request from a client, the connection request comprising a session identifier; </claim-text><claim-text>the gateway checking whether a stored session context exists that comprises the same session identifier; </claim-text><claim-text>if such a stored session context exists, the gateway checking a status of the session represented by said stored session context; </claim-text><claim-text>if the status indicates that the session is already running, the gateway informing the client that the connection request is rejected. </claim-text></claim-text>
<claim-text> The method of <claim-ref idref='CLM-00003'>claim 3</claim-ref>, wherein the step of checking the status of the session represented by said stored session context comprises the steps of: <claim-text>the gateway initiating a lock operation on said session context; </claim-text><claim-text>if the lock operation does not succeed, the gateway informing the client that the connection request is rejected; </claim-text><claim-text>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. </claim-text></claim-text>
<claim-text> 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, <claim-text>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; </claim-text><claim-text>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; </claim-text><claim-text>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. </claim-text></claim-text>
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," with "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". This merely indicates that the gateway's agent function could be done by a computer. There is nothing novel about this configuration either. more...
<claim-text> The method of <claim-ref idref='CLM-00001'>claim 1</claim-ref>, comprising the steps of: <claim-text>the gateway receiving a connection request from a client, the connection request comprising a session identifier; </claim-text><claim-text>the gateway checking whether a stored session context exists that comprises the same session identifier; </claim-text><claim-text>if such a stored session context exists, the gateway checking a status of the session represented by said stored session context; </claim-text><claim-text>if the status indicates that the session is already running, the gateway informing the client that the connection request is rejected. </claim-text></claim-text>