JP2006350635A - Session management system, session management method, server and communication system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To execute replication in a fusion server while maintaining dependence between a plurality of sessions relating to each application. <P>SOLUTION: A session management system comprises a first application management means and a second application management means for managing applications of different protocols respectively, a second session correspondence conversion means for converting session information about a first session into identification information about a corresponding second session, a second session search means for searching the second application management means for the corresponding second session according to the identification information about the second session, a first session correspondence conversion means for converting session information about a second session into identification information about a corresponding first session, and a first session search means for searching the first application management means for the corresponding first session according to the identification information about the first session. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a session management system, a session management method, a server, and a communication system, and can be applied to a system, a server, and a communication system that manage sessions between a plurality of network protocols.

  In recent years, system development using an application server has been widely performed when developing web applications and the like. For example, J2EE (Java 2 Platform, Enterprise Edition) is defined as an application server technology in the Java environment (see Non-Patent Document 1).

  As a service using the Internet, VoIP (Voice Over IP) using SIP (Session Initiation Protocol) is also widely used (see Non-Patent Document 2). For example, there is a SIP application server standard defined in Non-Patent Document 3.

  In general, these applications are often developed independently, but by simultaneously controlling a plurality of protocols, it becomes possible to provide an application with high added value.

  An example of an application using both the HTTP protocol and the SIP protocol is “click to dial”. The detailed operation of SIP related to click-to-dial is described in Non-Patent Document 4.

  An operation for providing a click-to-dial on a conventional application server will be described with reference to FIGS.

  FIG. 2 is a functional configuration diagram of a conventional application server in a non-clustering environment. The application server 100 includes an HTTP servlet container 101 that operates an HTTP application, and a SIP servlet container 102 that operates a SIP application.

  In FIG. 2, when there is a call request (HTTP protocol) from the web browser 105 that is a terminal on the caller side, the application server 100 is given to the HTTP servlet container 101.

  The HTTP servlet container 101 operates the HTTP application 103 corresponding to the request, generates an HTTP session 108, and notifies the SIP application 104 of a call request.

  On the other hand, the SIP application 104 generates an AP session 109 for managing 3PCC (third party call control function) processing in response to a call request, and an SIP session 111 related to a connection request to the softphone 107 on the receiver side. And the SIP session 110 related to the connection request to the softphone 106 on the caller side, and the AP session 109 and the SIP sessions 110 and 111 are associated with each other.

  Note that the AP session 109 corresponds to a SIP Application Session object in the SIP Servlet API.

  When the caller responds to the connection request, the SIP application 104 mediates the SIP message transmitted / received between the SIP sessions 110 and 111 as B2BUA (Back To Back User Agent), and between the caller and the receiver. Realize the call.

  Furthermore, the SIP application 104 associates the HTTP session 108 that triggered the 3PCC process with the AP session 109, so that the caller can cancel or disconnect the call using the HTTP protocol using the Web browser 105 during the above process. Make sure that you can select the appropriate call even if you request it via.

  Next, a click-to-dial operation provided on a conventional application server in a clustering environment will be described with reference to FIG.

  In FIG. 3, the secondary server 203 is a server used as a replication destination of the primary server 202, and all HTTP sessions and SIP sessions created on the primary server 202 are replicated on the secondary server 203. To do.

  When there is a call request (HTTP protocol) from the Web browser 212 which is a caller side terminal, the primary server 202 is given to the HTTP servlet container 204 via the HTTP / SIP load balancer 201.

  The HTTP servlet container 204 operates the HTTP application 206 for the request, generates an HTTP session 215, and notifies the SIP application 207 of a call request. At this time, the HTTP servlet container 204 cooperates with the HTTP servlet container 208 to generate a replica of the HTTP session 215 (HTTP session 219) on the secondary server 203.

  On the other hand, when the SIP application 207 generates an AP session 216 for managing the 3PPC process corresponding to the outgoing request from the HTTP application 206, the SIP servlet container 205 cooperates with the SIP servlet container 209 to replicate the AP session 216 replica ( AP session 223) is generated on the secondary server 203. Similarly, when the SIP session generates the SIP session 218 and the SIP session 217, the SIP servlet container 205 cooperates with the SIP servlet container 209 to perform a replica of the SIP session 218 (SIP session 222) and the SIP session 217 on the secondary server 203. Replica (SIP session 221).

  As described above, each of the HTTP session, AP session, and SIP session generated on the primary server 202 is created as a replica on the secondary server 203. The replica of each session is updated by cooperation between the containers so that the latest internal state is always reflected even when the internal state of the session changes.

Java 2 Platform, Enterprise Edition (J2EE). [Online]. Sun Microsystems. [Search May 6, 2005]. <http: // java. sun. com / j2ee / index. jsp> Session Initiation Protocol, Network Working Group, Request For Comments: 3261, [Search May 6, 2005], <http: // www. ietf. org / rfc / rfc3261. txt> JSR-000116 SIP Servlet API, [Online], Java Community Process, [Search May 6, 2005], <http: // www. jcp. org / aboutJava / communityprocess / final / jsr116 /> Best Current Practices for Third Party Call Control (3 pcc) in the Session Initiation Protocol (SIP), Network Working Group, Request for Comments: 3725/2005, p. ietf. org / rfc / rfc3725. txt>

  However, when an application for controlling a plurality of protocols as shown in FIG. 3 described above is operated on an application server having only a conventional replication function, there are the following problems.

  In FIG. 3, when the HTTP servlet container 204 on the primary server 202 creates or updates a replica of the HTTP session 215 on the secondary server 203, the AP session 216 or the SIP sessions 217 and 218 are added to the attribute information of the HTTP session. When stored, the HTTP servlet container 208 creates a restoration object 223 such as an AP session, and a replica of the HTTP session 219 has a reference to the restoration object 223 as an HTTP session attribute.

  Similarly, when the SIP servlet container 205 on the primary server 202 creates or updates a replica of the AP session 216 or the SIP sessions 217 and 218 on the secondary server 203, and also when the internal information of the AP session or the SIP session When the HTTP session 215 is stored in the attribute information, the SIP servlet container 209 creates the HTTP session restoration object 224 and the AP session 216 or the replicas of the SIP sessions 217 and 218 (the AP session 220, the SIP session 221, the SIP session). The session 222) has a reference to the restored object 224 as a SIP session attribute.

  That is, the cooperation information between HTTP / SIP sessions set on the primary server 202 is disconnected from each other at the time of replication on the secondary server 203 and managed as separate session information.

  As a result, even if the primary server 202 goes down and the HTTP / SIP load balancer 201 delivers the subsequent HTTP / SIP message to the secondary server 203, the HTTP / SIP cooperation application does not operate as expected. That is, a SIP-only application or an HTTP-only application continues to operate normally, but there is a problem that processing such as disconnection of the SIP connection by the HTTP request from the Web browser cannot be performed as described above.

  Therefore, in a server that can execute each application based on a plurality of network protocols, a session management system and a session that can execute replication while maintaining a dependency relationship between a plurality of sessions related to each application There is a need for a management method, a server, and a communication system.

  In order to solve this problem, a session management system according to a first aspect of the present invention includes (1) first application management means for managing an application based on a first network protocol and managing a first session related to an execution application. (2) second application management means for managing an application based on the second network protocol and managing a second session related to the execution application; and (3) session information of the first session is related to the second session. Second session corresponding conversion means for converting the session information of the first session into the corresponding identification information of the second session, and (4) the session information of the first session information is the second If it is session identification information, Second session search means for searching the corresponding second session from the second application management means based on the identification information of the application, and (5) information indicating that the session information of the second session is related to the first session. A first session correspondence conversion means for converting the session information of the second session into the corresponding identification information of the first session, if included, (6) the session information of the second session information is the identification information of the first session The first session search means for searching for the corresponding first session from the first application management means based on the identification information of the first session.

  The session management method of the second aspect of the present invention includes (1) a first application management step for managing an application based on a first network protocol and managing a first session related to an execution application, and (2) a second network protocol. And a second application management step for managing a second session related to the execution application, and (3) session information of the first session includes information indicating that it is related to the second session. A second session correspondence conversion step of converting the session information of the first session into corresponding identification information of the second session, and (4) when the session information of the first session information includes the identification information of the second session. , Based on the identification information of the second session A second session search step for searching for the second session from the second application management means; and (5) if the session information of the second session includes information indicating that it is related to the first session, the second session A first session correspondence conversion step of converting the session information into corresponding first session identification information; and (6) identification of the first session when the first session identification information is included in the session information of the second session information. And a first session search step of searching from the first application management means for a corresponding first session based on the information.

  The server according to the third aspect of the present invention is a server that provides a service in which a plurality of applications using a plurality of different network protocols are combined, and the session management system according to the plurality of applications includes the session management according to the first aspect of the present invention. It corresponds to the system.

  A communication system according to a fourth aspect of the present invention is a communication system in which when a server generates a session related to an execution application, a replica of the session is generated so that a plurality of other servers can be used. It is the server of this invention.

  According to the present invention, a server that can execute each application based on a plurality of network protocols can execute replication while maintaining a dependency relationship between a plurality of sessions related to each application.

(A) First Embodiment Hereinafter, a first embodiment of a session management system, a session management method, a server, and a communication system of the present invention will be described with reference to the drawings.

  The present embodiment shows a case where the server of the present invention is applied to an application server that can use two types of network protocols, HTTP protocol and SIP protocol.

(A-1) Configuration of First Embodiment FIG. 1 is a functional block diagram showing the internal configuration of the application server of the present invention.

  As shown in FIG. 1, the application server 300 according to the present embodiment includes an HTTP servlet container 301 and a SIP servlet container 302.

  The HTTP servlet container 301 operates an HTTP application 303 compliant with the HTTP servlet technology created by the application developer. When receiving a desired HTTP request from a client terminal (for example, a Web terminal) (not shown) through a network, for example, the HTTP servlet container 301 starts up and operates a predetermined HTTP application corresponding to the HTTP request. Further, the HTTP servlet container 301 includes a SIP session / ID conversion module 305 used during replication processing.

  The SIP session / ID conversion module 305 associates the HTTP session with the AP session or the SIP session based on the attribute information of the HTTP session to be replicated on the primary server during the replication process. In this case, the session information is converted into a session ID.

  Further, the SIP session / ID conversion module 305 uses the session search module 307 when the persistent data to be restored given from the primary server is the session ID of the AP session or SIP session on the secondary server. Then, the AP session or SIP session corresponding to the session ID is acquired.

  The SIP servlet container 302 operates a SIP application that complies with the SIP servlet technology created by the application developer. In addition, the SIP servlet container 302 has an HTTP session / ID conversion module 306 used during replication processing.

  In the replication process, the HTTP session / ID conversion module 306 determines that the AP session is associated with the HTTP session on the primary server based on the attribute information of the AP session to be replicated. The session information is converted into a session ID.

  In addition, on the secondary server, the HTTP session / ID conversion module 306 uses the session search module 307 when the restoration target persistent data given from the primary server is the session ID of the HTTP session, An HTTP session corresponding to the session ID is acquired.

  The HTTP servlet container 301 and the SIP servlet container 302 include a session search function 307 for searching session information managed by each container from the session ID, and can be called between the containers.

  Next, a configuration of a system that manages a session in a clustering environment using a plurality of application servers according to the present embodiment will be described.

  FIG. 4 is a functional block diagram for providing a click-to-dial on the two application servers described in FIG.

  The system of this embodiment shown in FIG. 4 includes a primary server 402 and a secondary server 403 that are two application servers, an HTTP / SIP load balance 401, a web browser 412 and a first soft phone 413 of a caller side terminal, reception And a second soft phone 414 of the terminal on the user side.

  The HTTP / SIP load balancer 401 is a load balancer that supports the HTTP protocol and the SIP protocol, and when executing a click-to-dial process, the same server is continuously selected for both HTTP and SIP unless a failure occurs in the cluster environment. It is assumed that it is set as follows. The HTTP / SIP load balance 401 includes a server determination unit that determines to which server the received request is given, and delivers the request to the application server determined by the server determination function. In general, in the case of the click-to-dial process, the server determination unit determines for each click-to-dial process. Furthermore, the HTTP / SIP load balancer 401 delivers all HTTP / SIP messages delivered to the primary server 402 to the secondary server 403 when the primary server 402 stops the service due to a system failure or the like. .

  The primary server 402 and the secondary server 403 are both application servers having corresponding functions, and the server determined by the HTTP / SIP load balancer 401 is the primary server.

  The primary server 402 is an application server that operates an application based on a request given from the HTTP / SIP load balance 401, and creates a replica of session information on the secondary server 403.

  The secondary server 403 is an application server used by the primary server 402 as a replication destination of session information, and all HTTP sessions and SIP sessions created on the primary server 402 are created on the secondary server 403.

  The primary server 402 includes an HTTP servlet container 404, an HTTP application 406, an SIP servlet container 405, and an SIP application 407. The secondary server 403 includes an HTTP servlet container 408, an HTTP application 410, an SIP servlet container 409, and an SIP application 411. Prepare. These correspond to the containers and applications described in FIG.

(A-2) Operation of the First Embodiment Hereinafter, the click-to-dial operation in a clustering environment having such a configuration will be described with reference to FIG.

  First, the caller uses the Web browser 412 to request a call with the receiver. This call request reaches the HTTP / SIP load balancer 401 by the HTTP protocol (S1).

  When a call request is given to the load balancer 401, the load balancer 401 gives an HTTP request to the application server determined by the preset server selection means. In the present embodiment, it is assumed that the load balancer 401 gives an HTTP request to the primary server 402 (S2).

  When an HTTP request is given from the load balancer 401, the HTTP servlet container 404 on the primary server 402 receives the HTTP request (S3).

  When receiving the HTTP request, the HTTP servlet container 404 delivers the HTTP request to the appropriate HTTP application 406 based on the URI information included in the HTTP request (S4).

  The HTTP application 406 that has received the HTTP request generates an HTTP session 415 in order to associate the received HTTP request with another HTTP request (S5).

  Further, the HTTP application 406 determines the content of the received HTTP request, and when determining that the request is a call start request, notifies the SIP application 407 of the call request (S6).

  Here, the timing of generating the HTTP session 415 is not limited to the time when the request for a call request is received, and may be, for example, at the time of login to the HTTP application 406 before that.

  In addition, when the HTTP application 406 creates the HTTP session 415, the HTTP servlet container 404 cooperates with the HTTP servlet container 408 to create a replica of the HTTP session 415 (HTTP session 419) on the secondary server 403 (S7).

  At this time, the replica (HTTP session 419) exists on the secondary server 403 until the HTTP session 415 is deleted, and is updated according to the state change of the HTTP session 415.

  Here, when generating a replica of the HTTP session 415 (HTTP session 419), the following processing is performed between the HTTP servlet container 404 and the HTTP servlet container 408.

  First, in the HTTP servlet container 404 of the primary server 402, the HTTP servlet container 404 determines whether an AP session or a SIP session is included based on the attribute information of the HTTP session 415 to be replicated. Accordingly, it can be determined whether the HTTP session is related to a related AP session or SIP session that has already been generated.

  When the HTTP servlet container 404 determines that the HTTP session 415 includes an AP session or a SIP session, the SIP session / ID conversion module 423 converts the session information into a session ID. As a result, AP session or SIP session information can be associated with the session ID. In addition, when the AP session or the SIP session is not included in the attribute information of the HTTP session 415, a replica process similar to the conventional one is performed.

  On the other hand, in the HTTP servlet container 408 of the secondary server 403, the HTTP servlet container 408 converts the SIP session / ID conversion when the restoration target persistent data given from the HTTP servlet container 404 is the session ID of the AP session or SIP session. The module 426 uses the session search module 428 to acquire an AP session or SIP session object corresponding to the session ID from the SIP servlet container 409. In other cases, replica restoration processing is performed as usual.

  In S6, when the SIP application 407 receives a call request from the HTTP application 406, the SIP application 407 generates an AP session 416 for managing 3PCC processing corresponding to the request (S8).

  When the SIP application 407 generates the AP session 416, the SIP servlet container 405 creates a replica 420 of the AP session 416 on the secondary server 403 in cooperation with the SIP servlet container 409 (S9).

  Here, when creating a replica of the AP session 416 (AP session 420), the following processing is performed between the SIP servlet container 405 and the SIP servlet container 409.

  First, in the SIP servlet container 405 of the primary server 402, based on the attribute information of the AP session 416 to be replicated, the SIP servlet container 405 is associated with the HTTP session, or the attribute information of the AP session or SIP session. It is determined whether there is an HTTP session registered as.

  When it is determined that there is an HTTP session associated with the SIP session 416, the HTTP session / ID conversion module 424 converts the HTTP session information into a session ID. If there is no HTTP session associated with the attribute information of the AP session 416, the same replica processing as in the conventional case is performed.

  On the other hand, in the SIP servlet container 409 of the secondary server 403, the SIP servlet container 409 determines that the HTTP session / ID conversion module 427 determines that the restoration target persistent data given from the SIP servlet container 405 is the session ID of the HTTP session. An HTTP session object corresponding to the session ID is acquired from the HTTP servlet container 408 using the session search module 428. In other cases, replica restoration processing is performed as usual.

  By doing so, the reference to the already restored HTTP session 419 is restored without multiple restoration of the HTTP session associated with the AP session.

  Subsequently, the SIP application 407 creates a first SIP session 418 and transmits a connection request according to the SIP protocol to the second softphone 414 existing on the receiver side (S10).

  Further, the SIP servlet container 405 cooperates with the SIP servlet container 409 to create a replica 422 of the SIP session 418 on the secondary server 403 (S11).

  When the receiver side softphone 414 responds to the connection request from the primary server 402, the SIP servlet container 405 of the primary server 402 creates a second SIP session 417, and the sender side first A connection request is transmitted to the softphone 413 (S12).

  Further, the SIP servlet container 405 cooperates with the SIP servlet container 409 to create a replica 421 of the SIP session 417 on the secondary server 403 (S13).

  Thereafter, when the caller side responds to the connection request, the SIP application 407 mediates the SIP message transmitted / received between the first SIP session 418 and the second SIP session 417 as B2BUA, so that the caller and the receiver can communicate with each other. Realize calls between.

  The SIP servlet container 405 also updates the replicas 422 and 421 each time the first SIP session 418 or the second SIP session 417 is updated.

  Even in the replication processing of the SIP sessions 417 and 418, even if the HTTP session is associated with the SIP session by using the HTTP session / ID conversion modules 424 and 427, as in the replication processing of the AP session 416, Can be restored as a reference to an already restored HTTP session without multiple restoration.

(A-3) Effect of First Embodiment As described above, according to this embodiment, as described in detail, the session management method according to the present invention is an application server that supports a plurality of protocols. However, the replication process can be executed without breaking the dependency between sessions.

(B) Other Embodiments In the above-described embodiments, the application server that supports the HTTP protocol and the SIP protocol has been described. However, the protocol to be applied is not limited to this, and other protocols may be used. It may be an application server that supports more than one protocol.

  In the embodiment described above, each container (such as an HTTP servlet container) has been described as including a session / ID conversion module of another protocol. However, either one of the containers is responsible for both session / ID conversion processes. It is possible to arrange in

  In the session / ID conversion module, the replication is performed by converting / restoring the session object to the session ID. However, means other than the session ID may be used as the permanent information.

It is a functional block diagram of the application server of 1st Embodiment. It is a functional block diagram of the conventional application server. It is a block diagram of the communication system in the conventional clustering environment. It is a block diagram of the communication system in the clustering environment of 1st Embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Communication system 300, 402 and 403 ... Application server, 301, 404 and 408 ... HTTP servlet container, 302, 405 and 409 ... SIP servlet container, 303, 406 and 410 ... HTTP application, 304, 407 and 411 ... SIP Application, 305, 423 and 426 ... SIP session / ID conversion module, 306, 424 and 427 ... HTTP session / ID conversion module, 307, 425 and 428 ... Session search module.

Claims (4)

First application management means for managing an application based on the first network protocol and managing a first session related to the execution application;
A second application management means for managing an application based on the second network protocol and managing a second session related to the execution application;
When the session information of the first session includes information indicating that it is related to the second session, the session information of the first session is converted into the corresponding identification information of the second session. Conversion means;
When the session information of the first session information is the identification information of the second session, a second session search for searching the corresponding second session from the second application management means based on the identification information of the second session Means,
When the session information of the second session includes information indicating that it is related to the first session, the session information of the second session is converted into the corresponding identification information of the first session. Conversion means;
When the session information of the second session information is the identification information of the first session, a first session search for searching the corresponding first session from the first application management means based on the identification information of the first session And a session management system. A first application management step of managing an application based on the first network protocol and managing a first session related to the execution application;
A second application management step of managing an application based on the second network protocol and managing a second session related to the execution application;
When the session information of the first session includes information indicating that it is related to the second session, the session information of the first session is converted into the corresponding identification information of the second session. Conversion process;
Second session search for searching for a corresponding second session from the second application management means based on the identification information of the second session when the session information of the first session information includes the identification information of the second session Process,
When the session information of the second session includes information indicating that it is related to the first session, the session information of the second session is converted into the corresponding identification information of the first session. Conversion process;
When the session information of the second session information includes the identification information of the first session, a first session search for retrieving the corresponding first session from the first application management unit based on the identification information of the first session A session management method comprising: a process.   In a server that provides a service in which a plurality of applications using a plurality of different network protocols are fused, the session management system according to the plurality of applications corresponds to the session management system according to claim 1. A server characterized by In a communication system that generates a replica of the session so that a plurality of other servers can use when a server generates a session related to the execution application, each of the servers is the server according to claim 3. A communication system characterized by the above.

Images