CN100433751C - Implementation method and application server for third-party control service - Google Patents

Abstract

In network with service provided through conversation initiating protocol, the method includes steps: user of signing contract already builds two calling connections; application server as back-to-back user agent for handling the service is located in call signaling path of user of signing contract; initiating call operation for third party controlled service, the user of signing contract sends service operation information of carrying conversation ID of the call; after receiving the service operation information, the application server locates the conversation corresponding to the conversation ID based on mechanism of back-to-back user agent; the application server redirects the conversation to complete the service process. The invention realizes CONF and ECT services without need of support from MGCF to SIP REFER message so as to simplify flow for implementing service.

Description

Implementation method and application server for third-party control service

technical field

The invention relates to a third-party control service in a packet switching network, in particular to a method for realizing the third-party control service and an application server.

Background technique

At present, with the continuous maturity of packet technology, the traditional telecommunication network based on circuit switching is developing towards the broadband telecommunication network based on packet switching, and SIP (Session Initiation Protocol, hereinafter referred to as SIP) is used as the call of the core network of packet telecommunication Control signaling is one of the current technological development trends, such as the research on NGN (Next Generation Network, Next Generation Network) by standard organizations such as ITU-T and ETSI. In this new packet telecommunication network, new packet terminals SIP terminals will gradually replace traditional terminal phones.

Among them, TISPAN (Telecommunications and Internet Converged Services and Protocols for Advanced Networking) under ETSI collectively refers to services with traditional service characteristics provided to SIP end users in NGN as PSTN/ISDN simulation services. TISPAN has established a number of work items (Work Item, WI) to study these simulation services, such as WI 03023 (DTS/TISPAN-03023-NGN-R1NGN CONF) research on CONF (Conference, conference business, hereinafter referred to as CONF), WI 03055 ( DTS/TISPAN-03055-NGN-R1 Explicit Communication Transfer) studies the explicit call transfer ECT (Explicit Communication Transfer, hereinafter referred to as: ECT) business.

The CONF service enables users to participate in and control a call with many users. The ECT service enables one party in a call to transfer the call to a third party. For more detailed service descriptions, please refer to the current latest standards of WI 03023 and WI 03055 draft.

In the two business standards currently formulated by WI 03023 and WI 03055, the same technology is used to realize the business process, and the analysis is as follows:

1) CONF meeting business process analysis

In the business implementation process of the CONF conference, the user can invite a user who has established a session relationship with him to join a conference, and the user sends a SIP REFER message (Session Initiation Protocol Reference Information Message) to realize this function. In the SIP REFER message, the meeting ID is set in the Request-URI (request-uniform resource identifier); the invited user ID is set in the Refer-To, and when the invited user has multiple registered terminals, it needs to be used in the Refer-To Globally Routable User Agent URIs (Globally Routable User Agent URIs, hereinafter referred to as GRUU; UniformResource Identifier, Uniform Resource Identifier, hereinafter referred to as: URI) to identify and initiate the invited user to establish a session relationship with the invited user terminal; Refer- The method parameter of To is set to "INVITE"; the Dialog identifier of the established session between two users is set in Replaces (replacement parameter), indicating that the session will be replaced by a new session established between the conference and the invited user;

The SIP REFER message will be routed to the application server AS (Application Server, hereinafter referred to as AS) that handles the CONF conference business according to the conference ID set by the Request-URI. The AS will refer to the settings in the SIP REFER message according to the aforementioned session initiation protocol. Send the session initiation protocol invitation information SIP INVITE message (session initiation protocol invitation message) to the invited user (terminal), and continue to carry the Replaces information carried in the SIP REFER message by the SIP INVITE message, so that the meeting and the invited user (terminal) At the same time, the invited user (terminal) releases the established session between the two users according to the Replaces information in the SIP INVITE message.

In the current draft standard of WI 03023, an example of the signaling process is given, as shown in Figure 1, and the brief introduction of the process is as follows;

Step 1): User UE-A initiates a session and calls a PSTN/ISDN user.

Steps 2-14): The session between the user UE-A and the PSTN/ISDN user is established successfully, and the conversation starts.

Step 15): User UE-A applies for creating a conference, and initiates a session to the AS that handles conference services.

Steps 16-24): The conference requested by user UE-A is created successfully.

Step 25): User UE-A invites the PSTN/ISDN user who is talking with him to join the conference, and sends a SIP REFER message to the AS that handles the conference business.

Steps 26-30): The SIP REFER message arrives at the AS that handles the conference business, and the AS sends a SIPNOTIFY message to notify the UE-A that the REFER message has been received.

Step 31): The AS that handles the conference service initiates a session to the PSTN/ISDN user according to the relevant content set in the received SIP REFER message, and sends a SIP INVITE message.

Steps 32-41): Since the PSTN/ISDN user belongs to the traditional circuit domain user, the intercommunication call will be handled by the media gateway control function MGCF (Media Gateway Control Functions) between the circuit domain and the packet domain, and the SIP INVITE message is sent to the MGCF, and the MGCF will "replace "Create a session between a PSTN/ISDN user and a conference, and add the PSTN/ISDN user to the conference. The AS that handles the conference service sends a SIP NOTIFY message to notify UE-A that the operation requested by REFER is successful.

Steps 42-47): According to the Replaces information in the SIP INVITE message, the MGCF releases the session specified by the Dialog identifier set in the Replaces information (the established session between the user UE-A and the PSTN/ISDN user).

For a more detailed process explanation, please refer to the current draft standard of WI 03023, which will not be described in detail here.

2) ECT display call transfer business process analysis

In the implementation process of the ECT transfer service, user B establishes two sessions with user A and user C respectively, and user B can establish a new session between user A and user C, and withdraw himself from the two previously established sessions , User B realizes this function by sending a SIPREFER message to User A. In the SIP REFER message, User C’s identity is set in Refer-To. When User C has multiple registered terminals, GRUU can also be used in Refer-To. To identify the user C terminal that has established a session relationship with user B; the method parameter of Refer-To is set to "INVITE"; the Dialog identifier of the session that has been established between user B and user C is set in Replaces, indicating that the session will be Replaced by a new session established between user C and user A; Target-Dialog (target session parameter) sets the Dialog identifier of the session already established between user B and user A.

After user A receives this SIP REFER message, according to the setting content in the aforementioned SIP REFER message, through the Target-Dialog information, it is confirmed that this is a call transfer request sent by user B who is in conversation with him, and then sent to user C (terminal) SIP INVITE message, and the Replaces information carried in the SIP REFER message continues to be carried by the SIP INVITE message, so that a new session is established between user A and user C, and user C releases itself and user B according to the Replaces information in the SIP INVITE message session already established. After the new session between user A and user C is established, user B releases the session it has established with user A.

For a detailed process explanation, please refer to the current draft standard of WI 03055, which will not be described in detail here.

It can be seen from this that in the CONF and ECT service implementation processes, the same technical points exist: the user uses the SIP REFER message to initiate a service operation request, and uses the GRUU to identify and initiate a service operation to request the user to have a session connection terminal , Use Replaces to indicate the session Dialog identifier to be replaced and released, etc.

Above-mentioned technical scheme is as follows problem:

1) In the interworking scenario, for ECT services, MGCF needs to process SIP REFER messages. At this time, MGCF is equivalent to a SIP UA (User Agent, User Agent) to process services, but the original function of MGCF is only to process between the packet domain and the circuit domain. Whether MGCF can be used as a SIP UA to handle services is still a big controversy among standard organizations. If the function of MGCF remains unchanged in the end, the technical solution using SIP REFER cannot meet the service implementation process in the interworking scenario.

2) In addition to the user terminal that initiates the service operation request, there are also special requirements for other user terminals participating in the service, and these users have not signed the CONF/ECT service. If these user terminals do not support REFER/Refer-To, Replaces, Target -Dialog and other operations, the users who have signed the CONF/ECT service still cannot apply the service successfully.

3) The GRUU mechanism is only a draft of the IETF standard organization at present. If the subscriber terminal of the CONF/ECT service does not support the GRUU mechanism, the service cannot be successfully applied.

From the previous analysis, it can be seen that the shortcoming of TISPAN WI 03023 and WI 03055 standard drafts is that the SIP REFER operation initiated by the subscriber is required to be sent to other user terminals participating in the service, which causes the service cooperation of these user terminals and MGCF special requirements.

Contents of the invention

The purpose of the present invention is to provide a third-party control service implementation method, which does not require MGCF support for SIP REFER messages, has no special requirements for other user terminals participating in the service, does not need to use the GRUU mechanism, and greatly simplifies the service Realize the process and facilitate the promotion of the business.

Technical scheme of the present invention comprises:

A method for realizing a third-party control service, comprising:

After the service subscriber establishes a call, the application server receives service operation information, and the service operation information carries the session identifier of the call;

The application server determines the session that needs to be redirected according to the session identifier;

The application server performs a redirection operation on the session to be redirected;

Wherein, the application server is in the signaling path of the call as a back-to-back user agent.

Technical scheme of the present invention also includes:

An application server, the application server includes:

A module for receiving service operation information after the service subscriber establishes a call, and the service operation information carries the session identifier of the call;

A module for determining a session that needs to be redirected according to the session identifier;

A module for redirecting the session to be redirected;

Wherein, the application server is in the signaling path of the call as a back-to-back user agent.

The technical scheme provided by the present invention does not require the support of the SIP REFER message by the MGCF and has no special requirements for other user terminals participating in the service, and does not need to use the GRUU mechanism. Instead, the AS that processes the CONF or ECT service acts as the B2BUA (Back to Back User Agent, back-to-back user agent) is in the call signaling path of the subscriber in advance, and intercepts the SIP REFER operation initiated by the subscriber, and uses the redirection technology to realize the CONF and ECT services, which greatly simplifies the service implementation process. Facilitate business promotion.

Description of drawings

FIG. 1 is a schematic diagram of the prior art CONF meeting business process;

Fig. 2 is the schematic flow sheet of the first preferred embodiment of the method of the present invention;

Fig. 3 is the schematic flow sheet of the second preferred embodiment of the method of the present invention;

Fig. 4 is a schematic flow chart of the third preferred embodiment of the method of the present invention.

Detailed ways

Various preferred embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings.

The present invention will propose a new service implementation process of CONF and ECT. The service implementation process is a service controlled by a third party. It does not require MGCF to support the session initiation protocol reference information SIPREFER message, and does not require other user terminals participating in the service. Special requirements, do not need to support reference operation REFER, reference target parameter Refer-To, replacement parameter Replaces, target session parameter Target-Dialog and other operations, only need to support the basic SIP protocol mechanism, do not need to use the GRUU mechanism, contracted users use SIP REFER The message initiates a service operation request, and the AS that handles the CONF/ECT business of the subscriber is in the signaling path of the subscriber as a B2BUA in advance, intercepts the SIP REFER message, and uses the redirection technology to complete the corresponding service processing.

The key technology of the method of the present invention is that the AS of the subscriber who handles the CONF/ECT service is in the signaling path of the subscriber as a B2BUA in advance, and after receiving the SIP REFER message, does not send the message to other users participating in the service Instead, a redirection technology is used to complete the corresponding business processing.

The business processes of CONF and ECT realized by the technology of the present invention will be described below through three specific embodiments. It should be noted that the flow diagrams and text descriptions made in the present invention are only to highlight the key technologies of the present invention. The explanation does not represent a complete call and service control flow, nor does it exhaust all possible branch flows.

As shown in Figure 2, the first embodiment of the method of the present invention has a scenario similar to the conference service scenario of the prior art Figure 1, the difference is that the called user is a SIP user like the calling user, rather than the prior art PSTN/ISDN user: SIP user UE-A is a service subscriber, SIP user UE-A establishes a call with SIP user UE-B, SIP user UE-A applies for conference resource creation successfully, and SIP user UE-A initiates a third-party control operation - The REFER operation also joins the user UE-B into the conference. The process is explained as follows:

User UE-A calls user UE-B and initiates a SIP INVITE message. The session identifier of the message is assumed to be Dialog 1. "INVITE[1]" as shown in Figure 2 means the SIP INVITE message of session Dialog 1.

The AS processing the CONF service receives the SIP INVITE[1] message, uses the B2BUA mechanism in the SIP protocol to terminate the session, and re-initiates a new session SIP INVITE[2] message to the user UE-B. The session ID of the message Assume Dialog 2. User UE-B receives the SIP INVITE[2] message, responds, and sends a 200 OK[2] response code.

The AS processing the CONF service receives the 200 OK[2] response code, converts it into a 200 OK[1] response code, and sends it to the calling user UE-A. User UE-A receives the 200 OK[1] response code and initiates an ACK[1] confirmation message. The AS processing the CONF service receives the ACK[1] confirmation message, converts it into an ACK[2] confirmation message, and sends it to the called user UE-B.

The session between the user UE-A and the user UE-B is successfully established, and a call can be started, and media streams can be exchanged between user terminals.

Compared with the conference service implementation process in the prior art Fig. 1, the method of the present invention is obviously different in that: the AS processing the CONF service is added to the call signaling path initiated by the SIP user UE-A to the called user, and the AS Using the B2BUA mechanism, a Dialog 1 session is created with the calling user, and a Dialog 2 session is created with the called user.

The user UE-A initiates an application for conference resources, and the creation is successful. This process is the same as steps 15-24 in FIG. 1 of the prior art, and the description is omitted. User UE-A initiates a SIP REFER operation to add user UE-B to the established conference. In the REFER message, Request-URI is set to the created conference ID conf@home.net, Refer-To is set to the ID of user UE-B, and Replaces is set to the session ID of Dialog 1. The content set in the REFER message indicates that the conference is expected to initiate a session request to the user UE-B and invite it to join the conference.

The AS that handles the CONF service receives and parses the SIP REFER message, judges that the Dialog 1 session ID set in Replaces corresponds to the session ID Dialog 2 in the called section according to the B2BUA mechanism, and uses the session ID Dialog 2 of user UE-B as The redirection technology adds it to the conference that has been created, and sends the SIP INVITE[2] message to the user UE-B again, and the message carries the SDP (Session Description Protocol, Session Description Protocol) information of the conference that has been created. Generally, this INVITE is also referred to as a re-invitation message Re-INVITE.

It can be seen here that the GRUU mechanism is not used in this embodiment of the present invention. Even if the called user has multiple registered terminals and multiple simultaneous sessions, the AS in this embodiment can uniquely locate the called user through the settings in Replaces. Which session of the user to redirect.

However, in the business process of Fig. 1 of the prior art, since the AS does not adopt B2BUA and redirection technology, when the called user has multiple registered terminals and multiple concurrent sessions, the callee can only pass through the GRUU (of course it may be other Alternative technology) firstly send the session to a certain called user terminal, and the settings in Replaces will only come into play on the called user terminal.

The user UE-B receives the SIPRe-INVITE[2] message, and performs SDP information negotiation with the AS on the conference SDP information carried in the message. The negotiation process is omitted in this embodiment. User UE-B responds to the INVITE[2] message and sends a 200 OK[2] response code.

After receiving the 200 OK[2] response code, the AS sends an ACK[2] confirmation message. The redirection process of the session Dialog 2 between the AS and the user UE-B is completed, and the session Dialog 2 previously established by the user UE-B is redirected to the created conference (the previous peer SDP information of the session Dialog 2 is user UE-A, now becomes the conference), that is, the user UE-B joins the conference.

In the second preferred embodiment of the method of the present invention, as shown in Figure 3, its scenario is exactly the same as the conference service scenario of the prior art Figure 1: SIP user UE-A is a service subscriber, and SIP user UE-A and PSTN/ISDN user B establishes a call, SIP user UE-A applies for conference resource creation successfully, and SIP user UE-A initiates a REFER operation to add user B to the conference.

The same as the service implementation process of Embodiment 1 of the method of the present invention, the call signaling path initiated by user UE-A to PSTN/ISDN user B passes through the AS that processes the CONF service, and the AS uses the B2BUA mechanism to create two sessions respectively, and A session Dialog 1 is created between the calling user UE-A, and a session Dialog 2 is created between the calling user UE-A and the MGCF.

After the call between the user UE-A and the user B is successfully established, an application for a conference resource is initiated and established successfully. User UE-A initiates a REFER operation to add user B to the created conference. The process is explained as follows:

User UE-A initiates a SIP REFER operation. The difference from Embodiment 1 is that another setting method is used in the REFER message, which can also achieve the effect of adding the called user to the conference: the Request-URI is set to user B's ID, Refer-To is set to the created conference ID conf@home.net, and Replaces is set to the Dialog 1 session ID. The content set in the REFER message indicates that user B is expected to initiate a session request to the conference to join the conference.

The AS handling the CONF business receives and parses the SIP REFER message, judges that the Dialog 1 session ID set in Replaces corresponds to the session ID Dialog 2 in the called section according to the B2BUA mechanism, and uses redirection technology to redirect the session Dialog 2 It joins the established conference, and sends a Re-INVITE[2] message to the called user B (MGCF), and the message carries the SDP information of the established conference.

The MGCF receives the SIP Re-INVITE[2] message, and performs SDP information negotiation with the AS on the SDP information of the meeting carried in the message. The negotiation process is well known in the prior art, so it will not be described again. MGCF responds to the INVITE[2] message and sends a 200 OK[2] response code.

After receiving the 200 OK[2] response code, the AS sends an ACK[2] confirmation message. The redirection process of the session Dialog 2 between AS and MGCF (user B) is completed, and user B joins the conference.

In the third preferred embodiment of the method of the present invention, as shown in Figure 4: SIP user UE-B is a service subscriber, a call is established between user UE-A and user UE-B, and user UE-B and user UE-B A call is established between C, user UE-B initiates a third-party control REFER operation to establish a call between user UE-A and user UE-C, and user UE-B exits the communication with user UE-A and UE-C A previously established call.

Similar to the service implementation process in the first embodiment above, the call signaling path between user UE-B and user UE-A passes through the AS that handles the ECT service, and the AS uses the B2BUA mechanism to create two sessions respectively, and user UE-A A session Dialog 1 is created between A, and a session Dialog2 is created between user UE-B; similarly, the call signaling path between user UE-B and user UE-C also passes through the AS that handles the ECT service, and the AS adopts The B2BUA mechanism creates two sessions respectively, a session Dialog 3 is created with user UE-B, and a session Dialog 4 is created with user UE-C.

The user UE-B initiates a REFER operation to establish a call between the user UE-A and the user UE-C. The process is explained as follows:

User UE-A initiates a SIP REFER operation. In the REFER message, Request-URI is set to user UE-A's identity, Refer-To is set to user UE-C's identity, Target-Dialog is set to Dialog 2 session identity, and Replaces is set to Dialog 3 session ID. The content set in the REFER message indicates that the user UE-A is expected to initiate a call request to the user UE-C.

Of course, as described in Embodiment 2, the REFER message can also be set in another way to achieve the same effect: Request-URI is set to the identity of user UE-C, Refer-To is set to the identity of user UE-A, and Target-URI is set to the identity of user UE-A. Dialog is set to the Dialog 3 session ID, and Replaces is set to the Dialog 2 session ID, to indicate that user UE-C is expected to initiate a call request to user UE-A.

The AS that handles the ECT service receives and parses the SIP REFER message, judges that the Dialog 2 session ID set in the Target-Dialog corresponds to the session ID Dialog 1 in the UE-A section according to the B2BUA mechanism, and then replays the session Dialog 1 Directed to user UE-C, user UE-A sends a Re-INVITE[1] message, which carries the SDP information of user UE-C.

The user UE-A receives the SIP Re-INVITE[1] message, and performs SDP information negotiation with the AS on the SDP information of the user UE-C carried in the message. The negotiation process is omitted in this embodiment. UE-A responds to the INVITE[1] message and sends a 200 OK[1] response code.

AS receives the 200 OK[1] response code, obtains the SDP information of user UE-A that has been negotiated, and judges that the Dialog 3 session identifier set in Replaces corresponds to the session of user UE-C according to the B2BUA mechanism If Dialog4 is identified, the session Dialog4 is redirected to user UE-A, and user UE-C sends a Re-INVITE[4] message, which carries the negotiated SDP information of user UE-A.

User UE-C receives the SIPRe-INVITE[4] message, responds, and sends a 200 OK[4] response code. After receiving the 200 OK[4] response code, the AS sends an ACK[1] confirmation message to UE-A. The AS sends an ACK[4] confirmation message to the user UE-C.

The call between user UE-A and user UE-C has been established. It can be seen that this call still creates two sessions between user UE-A and user UE-C through the AS using the B2BUA mechanism: Dialog 1 and Dialog 4.

AS needs to exit user UE-B from previously created session Dialog2 associated with user UE-A and session Dialog3 associated with user UE-C, send a SIP BYE[2] message, and release session Dialog 2.

User UE-B receives the BYE[2] message, releases the session Dialog 2, and sends a 200 OK[2] response code. AS sends SIP BYE[3] message to release session Dialog 3.

User UE-B receives the BYE[3] message, releases the session Dialog 3, and sends a 200 OK[3] response code.

It can be seen from the above three embodiments that the AS that processes CONF or ECT services in the method of the present invention must be in the call signaling path of the subscriber as a B2BUA in advance; secondly, the AS according to the Replaces/Target- The session identifier set by Dialog uniquely locates the session that needs to be redirected according to the B2BUA mechanism, so that there is no need to use the GRUU mechanism to locate the terminal; finally, the AS redirects the session that needs to be redirected, so that other users participating in the service The terminal/MGCF only needs to process the Re-INVITE message of the basic SIP protocol, and does not need to support REFER/Refer-To, Replaces and other operations, so as to complete the service processing.

Finally, it should be pointed out that the solution of the present invention is not only applicable to CONF and ECT services, but also applicable to services controlled by a third party using SIP REFER operations. The service subscribers have established call connections with two other SIP UAs. The service subscriber initiates a REFER operation, and the REFER message carries the two SIP UA identities. After receiving the REFER message, the AS adopts redirection technology to establish a call connection between the two SIP UAs, so that the service subscriber can perform third-party control the goal of. For example, for the CONF service, the subscriber has established two call connections with the conference resource and another user B, and through the third-party control of SIP REFER, the call connection between user B and the conference resource is also established, even if user B Join the meeting.

The method of the present invention does not require MGCF to support the SIP REFER message, has no special requirements for other user terminals participating in the service, does not need to support operations such as REFER/Refer-To, Replaces, and Target-Dialog, and only needs to support the basic SIP protocol mechanism; There is no need to use the GRUU mechanism, but the AS that handles the CONF or ECT business acts as a B2BUA in the call signaling path of the subscriber in advance, intercepts the SIP REFER operation initiated by the subscriber, and uses redirection technology to realize the CONF and ECT business , which greatly simplifies the business implementation process and facilitates business promotion.

It should be understood that the above descriptions for specific embodiments are relatively detailed, but should not be construed as limiting the scope of the patent protection of the present invention, and the scope of protection of the patent protection of the present invention should be determined by the appended claims.

Claims (11)

1, a kind of third party controls professional implementation method, and described method comprises:

After the service contracting user set up calling, application server received business operation information, and described business operation information is carried the session identification of described calling;

Described application server is determined the session that needs are redirected according to described session identification;

Described application server carries out redirect operation to the session that described need are redirected;

Wherein, described application server is in the described calling signaling path as back-to-back user agent.

2, method according to claim 1 is characterized in that, described business operation information is carried on Session initiation Protocol with reference in the informational message.

3, method according to claim 1, it is characterized in that described session identification is arranged in one of following at least parameter: described Session initiation Protocol is with reference in the alternative parameter of informational message, the target session parameter of described Session initiation Protocol with reference to informational message.

4, method according to claim 2 is characterized in that,

Described application server carries out redirect operation according to one of following parameter: described Session initiation Protocol identifies Request-URI with reference to the reference object parameters R efer-To of informational message, described Session initiation Protocol with reference to the request-unified resource of informational message.

5, method according to claim 1 is characterized in that, described application server receives business operation information and specifically comprises: described application server receives the request of carrying described business operation information from described service contracting Client-initiated.

6, method according to claim 1 is characterized in that, described method also comprises: described application server discharges the session of described session identification correspondence.

7, method according to claim 1 is characterized in that, described application server determines that according to described session identification the session that needs are redirected specifically comprises:

Described application server judges that described session identification is a session identification in the described calling;

Described application server is determined the session that needs are redirected according to described session identification.

8, method according to claim 7 is characterized in that, described application server determines that according to described session identification the session that needs are redirected is specially:

Described application server is determined the session that described needs are redirected according to back-to-back user agent mechanism.

9, a kind of application server, described application server comprises:

Be used for after the service contracting user sets up calling, receive the module of business operation information, described business operation information is carried the session identification of described calling;

Be used for determining the module of the session that needs are redirected according to described session identification;

Be used for module that the session that described need are redirected is redirected;

Wherein, described application server is in the described calling signaling path as back-to-back user agent.

10, application server according to claim 9 is characterized in that, described application server also comprises:

Be used to discharge the module of the session of described session identification correspondence.

11, application server according to claim 9 is characterized in that, described being used for determines that according to described session identification the module of the session that needs are redirected comprises:

Be used for judging that described session identification is the submodule of a session identification of described calling;

Be used for determining the submodule of the session that needs are redirected according to described session identification.

Images