SIP and HTTP convergence in network computing environments

• US 8,001,250 B2
• Filed: 05/15/2007
• Issued: 08/16/2011
• Est. Priority Date: 05/16/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Mehra, Vinod, Langen, Anno R., Khan, Rao Nasir
• Primary Examiner(s): Bates; Kevin
• Assistant Examiner(s): NICKERSON, JEFFREY L
• Application Number:
  US11/749,082
• Publication Number:
  US 20080189421A1
• Time in Patent Office: 1,554 Days
• Field of Search: 709/227, 709/249, 709/228
• 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 hypertext transfer protocol (HTTP) and session initiation protocol (SIP) communications in a network environment, said method comprising:

deploying an application on a server, wherein said application includes both an HTTP servlet and a SIP servlet;

establishing an HTTP session for a first client on said server;

establishing a SIP session for a second client on said server;

generating a single unified session object in memory for the application on said server, wherein the unified session object shares data between the HTTP session and the SIP session, and wherein both the HTTP session and the SIP session are accessible programmatically via the single unified session object; and

wherein said data is shared between the HTTP session and the SIP session by way of the unified session object; and

wherein the server includes a single unified application programming interface (API) accessible by both said SIP servlet and said HTTP servlet, wherein said API includes a method for creating a new HTTP session from within the SIP servlet;

receiving a call identifier from the second client that is in communication with the SIP servlet, wherein the call identifier is used to access the unified session object; and

receiving, directly from the SIP servlet, an invocation of the method for creating the new HTTP session on said unified API, wherein the server instantiates the new HTTP session in response to the invocation of the method on said unified API by the SIP servlet.

2. The method of claim 1, further comprising:

disassociating the HTTP session from the unified session object and associating the HTTP session with a new application unified session object created on said server.

3. The method of claim 1, further comprising:

disassociating the SIP session from the unified session object and associating the SIP session with a new unified session object created on said server.

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 unified session object 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 unified session object 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 an object in memory containing the application session and an object in memory containing the HTTP session and an object in memory containing the SIP session.

7. The method of claim 1, further comprising:

implementing the unified session object 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 unified session object 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 unified session object 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 hypertext transfer protocol (HTTP) and session initiation protocol (SIP) communications, said system comprising:

a server executing on a computing device, said server having an application deployed thereon, wherein said application includes both an HTTP servlet and a SIP servlet;

an HTTP client in communication with said server, wherein the server provides an HTTP session for maintaining state associated with an said HTTP client;

a SIP client in communication with said server, wherein the server provides a SIP session for maintaining state associated with said SIP client; and

wherein the server generates a single unified session object in memory for the application, wherein the unified session object shares data between the HTTP session and the SIP session, and wherein both the HTTP session and the SIP session are accessible programmatically via the single unified session object;

wherein said data is shared between the HTTP session and the SIP session by way of the unified session object; and

wherein the server an includes a single unified application programming interface (API) accessible by both said SIP servlet and said HTTP servlet, wherein said API includes a method for creating a new HTTP session from within the SIP servlet

wherein the server receives a call identifier from the SIP client that is in communication with the SIP servlet, wherein the call identifier is used to access the unified session object; and

wherein the server receives, directly from the SIP servlet, an invocation of the method for creating the new HTTP session on said unified API, wherein the server instantiates the new HTTP session in response to the invocation of the method on said unified API by the SIP servlet.

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

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

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 unified session object 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 unified session object and an object in memory containing the HTTP session and an object in memory containing the SIP session.

16. The system of claim 11 wherein the unified session object 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 unified session object 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 unified session object association with the HTTP session causes the HTTP session to be returned in an iterator once the unified session object is accessed.

20. A non-transitory computer readable storage medium having instructions stored thereon which when executed by one or more processors cause the one or more processors to:

deploy an application on a server, wherein said application includes both an HTTP servlet and a SIP servlet;

establish an HTTP session for a first client on said server;

establish a SIP session for a second client on said server;

generate a single unified session object in memory for the application on said server, wherein the unified session object shares data between the HTTP session and the SIP session, and wherein both the HTTP session and the SIP session are accessible programmatically via the single unified session object; and

wherein said data is shared between the HTTP session and the SIP session by way of the unified session object; and

wherein the server includes a single unified application programming interface (API) accessible by both said SIP servlet and said HTTP servlet, wherein said API includes a method for creating a new HTTP session from within the SIP servlet;

receive a call identifier from the second client that is in communication with the SIP servlet, wherein the call identifier is used to access the unified session object; and

receive, directly from the SIP servlet, an invocation of the method for creating the new HTTP session on said unified API, wherein the server instantiates the new HTTP session in response to the invocation of the method on said unified API by the SIP servlet.