SIP and HTTP Convergence in Network Computing Environments

• US 20080189421A1
• Filed: 05/15/2007
• Published: 08/07/2008
• Est. Priority Date: 05/16/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Langen, Anno R., Mehra, Vinod, Khan, Rao Nasir
• Granted Patent: US 8,001,250 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 9/40 Network security protocols

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

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.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

7. 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.

8. The method of claim 1 wherein the application session can be accessed via a call id or a session id by an application.

9. The method of claim 1, further comprising:

encoding an HTTP uniform resource locator (URL) with a jsession id.

10. 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.

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.

12. The system of claim 11 wherein the HTTP session is disassociated from the application session and associated with a new application session.

13. The system of claim 11 wherein the SIP session is disassociated from the application session and associated with a new application session.

14. 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.

15. 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.

16. 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.

17. The system of claim 11 wherein the application session can be accessed via a call id or a session id by an application.

18. The system of claim 11 wherein an HTTP uniform resource locator (URL) is encoded with a jsession id.

19. 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.

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.