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
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.
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.
You will need to help me out here. The basic idea is that we need to match the prior art with the claims. We need to address the basic claims in [Claim 0001] which claims a gateway between wireless and wired protocols, stores a session context, maintains a client connection state, and a session identifier which is unique to the session.
The P-CSCF (call session control function) interfaces wireless protocols with the wired protocol, thus it does the gateway function at the IMS layer. The rest of the CSCF stores a session context, maintains a client connection state, a session identifier unique to the session.
Here is a nice description and diagram: http://www.dataconnection.com/sbc/imsarch.htm
The SIP layer does the call control - adding/dropping call legs. As such, it must establish all the call legs when the caller pushes the talk button and drop all the call legs when the caller releases the talk button.