# US 2008/0189421 A1 · SIP and HTTP Convergence in Network Computing Environments > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2008/0189421 A1 - Document ID: US20080189421A1 - Status: Published application - Kind: A1 - Application number: 11/749,082 - Filed: 2007-05-15 - Published: 2008-08-07 - Earliest claimed: 2006-05-16 - Assignees: BEA Systems, Inc. - Inventors: Anno R. Langen; Vinod Mehra; Rao Nasir Khan - Web page: https://patentgrep.com/patent/US20080189421A1 ## CPC - H04L 67/14: Session management (for real-time applications in data packet communications networks H04L65/1066) - H04L 65/1104: Session initiation protocol [SIP] - H04L 69/08: Protocols for interworking; Protocol conversion - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract The SIP server can be comprised of an engine tier and a state tier distributed on a cluster network environment. The engine tier can send, receive and process various messages. The state tier can maintain in-memory state data associated with various SIP sessions. The SIP server can support converged HTTP and SIP modes of communication. An application session can be established for allowing the association of an HTTP session with a SIP session such that data can be exchanged between them. This association can be broken and reestablished with new application sessions such that various SIP and HTTP clients can join and leave new sessions. An API can be provided to enable various associations and method calls for the application session. ## Claims ### Claim 1 A computer implemented method for converging HTTP and SIP protocol communications in a network environment, comprising: establishing an HTTP session for a first client; establishing a SIP session for a second client; establishing an application session for an application; and associating the application session with the HTTP session and the SIP session such that data can be exchanged between the first client and the second client. ### Claim 2 (depends on 1) The method of claim 1, further comprising: disassociating the HTTP session from the application session and associating the HTTP session with a new application session. ### Claim 3 (depends on 1) The method of claim 1, further comprising: disassociating the SIP session from the application session and associating the SIP session with a new application session. ### Claim 4 (depends on 1) The method of claim 1, further comprising: establishing a new HTTP session by a SIP servlet and associating the new HTTP session with the application session such that data can be shared between the SIP session and the new HTTP session. ### Claim 5 (depends on 1) The method of claim 1, further comprising: establishing a new SIP session by the HTTP session and associating the new SIP session with the application session such that data can be shared between the HTTP session and the new SIP session. ### Claim 6 (depends on 1) The method of claim 1 wherein the association is created by establishing pointers in memory between the application session object and the HTTP session object and SIP session object. ### Claim 7 (depends on 1) The method of claim 1, further comprising: implementing the application session by a converged application running on a server wherein the converged application is capable of supporting HTTP and SIP communications. ### Claim 8 (depends on 1) The method of claim 1 wherein the application session can be accessed via a call id or a session id by an application. ### Claim 9 (depends on 1) The method of claim 1, further comprising: encoding an HTTP uniform resource locator (URL) with a jsession id. ### Claim 10 (depends on 1) The method of claim 1 wherein associating the application session and the HTTP session causes the HTTP session to be returned in an iterator once the application session is accessed. ### Claim 11 A system of converging HTTP and SIP communications, comprising: a server that provides an HTTP session for maintaining state associated with an HTTP client and an SIP session for maintaining state associated with an SIP client; an application session established on the server for associating the SIP session with the HTTP session such that data could be shared between them. ### Claim 12 (depends on 11) The system of claim 11 wherein the HTTP session is disassociated from the application session and associated with a new application session. ### Claim 13 (depends on 11) The system of claim 11 wherein the SIP session is disassociated from the application session and associated with a new application session. ### Claim 14 (depends on 11) The system of claim 11, further comprising: a new HTTP session established by a SIP servlet on the server wherein the new HTTP session is associated with the application session such that data can be shared between the SIP session and the new HTTP session. ### Claim 15 (depends on 11) The system of claim 11 wherein the association is created by establishing pointers in memory between the application session object and HTTP session object and SIP session object. ### Claim 16 (depends on 11) The system of claim 11 wherein the application session is implemented by a converged application running on the server, the converged application supporting both HTTP and SIP communications. ### Claim 17 (depends on 11) The system of claim 11 wherein the application session can be accessed via a call id or a session id by an application. ### Claim 18 (depends on 11) The system of claim 11 wherein an HTTP uniform resource locator (URL) is encoded with a jsession id. ### Claim 19 (depends on 11) The system of claim 11 wherein the application session association with the HTTP session causes the HTTP session to be returned in an iterator once the application session is accessed. ### Claim 20 A computer readable medium having instructions stored thereon which when executed by one or more processors cause a system to: establish an HTTP session for a first client; establish a SIP session for a second client; establish an application session for an application; and associate the application session with the HTTP session and the SIP session such that data can be exchanged between the first client and the second client.