WO2007098705A1

WO2007098705A1 - A method and apparatus for cscf to release session

Info

Publication number: WO2007098705A1
Application number: PCT/CN2007/000665
Authority: WO
Inventors: Hui Li
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-03-03
Filing date: 2007-03-02
Publication date: 2007-09-07
Also published as: CN101031139A; CN101031139B

Abstract

Provided a session releasing method used for CSCF to release the session between the user and the CSCF, which comprises the following steps: the CSCF receiving the user deregistration request which includes the deregistration reason for deregistering the user; judging the session type and the deregistration reason value; and determining whether to release the session according to the deregistration reason value and the session type. The present invention makes the implement of session service more reasonable and makes the user feel better about the session.

Description

Method and device for call control entity to release session

The present application claims priority to Chinese Patent Application No. 200610059339.4, entitled "Method for Call Control Entity Dry Session", filed on March 3, 2006, the entire contents of which are incorporated by reference. In this application.

The present invention relates to the field of communications technologies, and more particularly to a method and apparatus for releasing a session between a user and a Call Session Control Function (CSCF).

Background technique

SIP (Session Initiation Protocol) is a standard of Voice over Internet Protocol (VoIP) released by the Internet Engineering Task Force (IETF) in March 1999. SIP, as an important application of the Internet, adds requirements for telephony signaling and quality of service (QoS), and has unique user addressing and location capabilities. Recently, the practical role of SIP has far exceeded the application of VoIP. SIP is a protocol for telephone signaling, used to initiate a session, can control the establishment and termination of multimedia sessions attended by multiple participants, and can dynamically adjust and modify session attributes: such as session bandwidth requirements, transmission media types (voice, video, Data, etc.), media codec format, support for multicast and unicast, etc. Therefore, SIP is conducive to the development of value-added services for a variety of applications in conjunction with the Internet.

IMS (IP Multimedia Subsystem, IP Multimedia Subsystem) is 3GPP (3rd)

The Generation Partnership Project, a sub-system superimposed on the packet network, uses a packet domain as its bearer channel for control signaling and media transmission, and introduces the SIP protocol as a service control protocol. It is easy to expand and convenient for media combination. It provides rich multimedia services by separating service control from bearer control. The main functional entities in IMS include call control entity CSCF (Call Session Control Function) that controls user registration and session control. , call session control function), HSS (Home Subscriber Server) that centrally manages user subscription data, AS (Application Server) that provides various business logic control functions. The IMS network uses the registration process of the SIP protocol to implement user access to the IMS network. During the user registration process, the IMS network authenticates the user's private identity and establishes an access domain security channel. The user registration success will establish the user's public identity and the current location of the user in the home domain S-CSCF (Serving CSCF). In the relationship, the S-CSCF also removes the user's subscription data from the HSS.

The system architecture of the IMS 100 is shown in Figure 1.

Based on the debt of the user or network entity, the CSCF can establish one or more multimedia sessions. In the prior art, the P-CSCF (Proxy-CSCF, Proxy Call Control Entity) and the S-CSCF network element need to release the established session and the established session by sending a BYE message to the calling party and the called party when the user is logged out. .

When the user's IMPU (IP Multimedia Public Identity) registration lifetime expires, or when the network initiates logout, the still active multimedia session initiated by the user through the IMPU is released, that is, the CSCF is The calling side sends a BYE message to release the session being established with the IMPU and the session already established with the IMPU.

In the process of implementing the present invention, the inventors have found that at least the following problems exist in the prior art: all the sessions of the IMPU are released when the user is logged off, and the sessions that some users also wish to keep are also released, and such services are not implemented. reasonable. For the user, either the session is abandoned or the session has to be re-established, causing the user to experience poor performance.

Summary of the invention

The embodiments of the present invention are directed to a method and apparatus for a call control entity to release a session, which solves the problem that the session service is unreasonable in the prior art, and improves the user's perception of the session service.

An embodiment of the present invention provides a method for releasing a session, for causing a call control entity to release a user's session, including the following steps: The call control entity receives a logout user request for canceling a user, and the logout user request includes a logout reason; The session type of the session and the logout reason value of the logout reason; and, based on the logoff reason value and the session type, determine whether to release the session.

An embodiment of the present invention further provides a method for a forwarded session, for causing a call control entity to release a user's session, including the following steps: Receiving a logout user request for logging out the user;

When the type of the user session is a set reservation type, the session is not released. In addition, an embodiment of the present invention further provides a device for a dry session, which is used for a call control entity, including a request receiving unit, a session type unit, and a session management unit, where: the request receiving unit is configured to receive a user for canceling a user. User logout request;

The session type unit is used to determine the type of the session;

The session management unit is operative to determine whether to release the session established by the user requested to log off based on the user logout request and the type of user session.

When the user is logged off, the user decides whether to release the session according to the type of the user session and/or the reason for the cancellation, and the corresponding session can be released or maintained according to the application needs of the user and the network, so that the service realization is more rationalized and improved. User experience. DRAWINGS

The drawings are intended to provide a further understanding of the embodiments of the present invention, and are intended to be a part of the present invention, and the description of the present invention is not intended to limit the invention. In the drawing:

Figure 1 shows an IMS architecture in the prior art;

2 is a flow chart showing a first embodiment of a method for a session established between an S-CSCF # and a user in the present invention;

3 is a flow chart showing the message interaction of the application example 1 of the S-CSCF releasing the session established with the user in the present invention;

4 is a flow chart showing the message interaction of the application example 2 of the S-CSCF releasing the session established with the user in the present invention;

Fig. 5 is a view showing the configuration of an embodiment of a session releasing apparatus for CSCF in the present invention.

detailed description

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

It is to be noted that in the following detailed description of the embodiments, the exemplified call control entity is an S-CSCF, but those skilled in the art will recognize that, except for the case where the following clearly applies only to the S-CSCF, these Embodiments are equally applicable to the P-CSCF. FIG. 2 shows a flow of Embodiment 1 of a method for releasing a session established between an S-CSCF and a user in the present invention.

As shown in FIG. 2, the first embodiment of the method for releasing a session established between the S-CSCF and the user according to the present invention includes the following steps:

In step S102, the S-CSCF receives the logout user request for canceling the user; in step S104, analyzing the session type and analyzing the logout reason value included in the logout user request;

In step S106, when the user is logged off, it is determined whether to release the session according to the session type and the logout reason value.

The method of processing the session dry-out by the S-CSCF user in accordance with the present embodiment will be described in detail below with reference to Tables 1 and 2.

1. CSCF has the following types due to different service types:

• Status-related sessions established in the registered state: This type of session can only be established in the registered state and cannot be established in the unregistered state. For example, a non-response forwarding service; • a session established in the registration state and independent of the registration status: This type of session can be established in both the registered state and the unregistered state, for example, unconditional forwarding service;

• A session established in an unregistered state;

• An emergency session.

Specifically, the CSCF can determine the first three session types according to the user registration status, and then determine whether the session belongs to the emergency session according to the content of the session request.

2. User registration includes:

The registration initiated by the user to the network, the reason values are as follows:

• REGISTRATION: User-initiated registration.

3. The user's logout includes the following:

User initiated logout, the reason values are as follows:

• USER—DEREGISTRATION: User-initiated logout. Another call control entity initiates a call to the call control entity or is initiated by the call control entity. The reason values are as follows:

• TIMEOUT— DEREGISTRATION: The registration timer expires. Logout initiated by CSCF;

• ADMINISTRATIVE— DEREGISTRATION: An administrative logout initiated by CSCF.

The logout initiated by HSS has the following reasons:

• PERMANENT_TERMINATION: The HSS indicates that the IMPU corresponding to the IMPI (IP Multimedia Private Identity) and the implicit registration set are no longer assigned to the S-CSCF (for example, the user's subscription changes) );

• NEW_SERVER_ASSIGNED (new server allocation): HSS indicates S-CSCF The IMPU is assigned to the new S-CSCF;

• SERVER—CHANGE (Server Change): The HSS instructs the S-CSCF to force the user to be logged out, allowing the user to select another S-CSCF;

• REMOVE – SCSCF (Cancel Service Call Control Entity): The HSS indicates that the S-CSCF is not assigned to the S-CSCF.

It is worth noting that with regard to the logout initiated by the HSS, the call control entity can only be the S-CSCF, not the P-CSCF.

4. In the case that the user registration status changes, for the session established by the user, including the established session and the session being established, the session release is handled as follows:

The session established by the user in the unregistered state. If the user state changes from the unregistered state to the registered state during the subsequent session, the network does not release the sessions. If the user state changes from the registered state to the unregistered state during subsequent sessions during the session, the network can selectively release the session based on the session type and the reason value of the release.

The specific method can be seen in the following table:

Table 1: Sessions established by users in an unregistered state

Session type Logout reason Released ^ Tongue Unestablished session established session PERMANENT_ TERMINATION Yes

NEW— SERVER — ASSIGNED Yes

SERVER— CHANGE is

REMOVE - SCSCF is ADMINISTRATIVE_DEREGISTRATION No

TIMEOUT JDEREGISTRATION No

USER_DEREGISTRATION No Emergency session PERMANENT— TERMINATION No

NEW— SERVER — ASSIGNED No

SERVER— CHANGE No

REMOVE_SCSCF No

ADMINISTRATIVE JDEREGISTRATION No

TIMEOUT— DEREGISTRATION No

USER_DEREGISTRATION No

5. The session established by the user in the registered state. During the subsequent session, the user state changes from the registered state to the unregistered state. Then the network can selectively release the session according to the type of the session and the value of the dry source.

The specific method can be seen in the following table:

Table 2: Sessions established by users in the registered state

Session type Logout reason Whether to release ^ 3⁄4" Status established in the registered state PERMANENT TERMINATION Yes

Related conversation

NEW— SERVER — ASSIGNED Yes

SERVER— CHANGE is

REMOVE - SCSCF is

ADMINISTRATIVE JDEREGISTRATION is

TIMEOUT JDEREGISTRATION is

USER— DEREGISTRATION is the status established in the registered state PERMANENT— TERMINATION is

Irrelevant conversation

NEW— SERVER — ASSIGNED Yes

SERVER— CHANGE is REMOVE—SCSCF is

ADMINISTRATIVE_DEREGISTRATION No

TIMEOUT— DEREGISTRATION No

USER_DEREGISTRATION No Urgent PERMANENT— TERMINATION No

NEW— SERVER — ASSIGNED No

SERVER— CHANGE No

REMOVE—SCSCF No

ADMINISTRATIVE— DEREGISTRATION No

TIMEOUT— DEREGISTRATION No

USER_DEREGISTRATION No Application example 1 and application example 2 according to the present embodiment will be explained with reference to Figs. 2 and 3.

Application example one:

Fig. 3 is a flow chart showing the message interaction of the method in which the S-CSCF releases the session established with the user in the application example 1 of the present embodiment.

In this application example, the user subscribes to the unconditional forwarding service, the unconditional forwarding session established in the unregistered state, and the subsequent user state changes from the unregistered state to the registered state during the session. Then, the HSS initiates management to log off the user, and the S-CSCF releases the session. The specific process is as follows:

In step S202, the S-CSCF receives the session establishment request INVITE on the host side, and the user is in an unregistered state, and performs an unconditional forwarding service in an unregistered state;

In step S204, the S-CSCF forwards the session establishment request INVITE to the called network; in step S206, the S-CSCF receives the session establishment response 200 OK;

In step S208, the S-CSCF forwards the session establishment response 200 OK;

In step S210, the user initiates an initial registration request REGISTER;

In step S212, the S-CSCF initiates a request Cx-Request to the HSS;

In step S214, the S-CSCF receives the response of the HSS Cx-Response;

In step S216, the user registration is successful, and the S-CSCF answers the user request 200 OK; In step S218, the HSS initiates management of the RTR, and the reason value is PERMANENT_TERMINATION;

In step S220, the S-CSCF answers the HSS logout user request RTA;

In steps S222 and S224, since the session type of the logged-out user is a session established in an unregistered state, the reason for the logout is PERMANENT_TERMINATION, and the S-CSCF separately reports to the calling side and the queried state according to the session type and the logout reason value of the user. The calling side sends a BYE message, releasing the unconditional forwarding session established by the user;

In steps S226, S228, the calling side and the called side UE respectively send a response 200 OK to the S-CSCF.

Application shows 4 column 2:

Fig. 4 is a flow chart showing the message interaction of the method in which the S-CSCF releases the session established with the user in the application example 2 of the embodiment.

The user subscribes to the unconditional forwarding service, and the unconditional forwarding session is established in the registered state. During the subsequent session, the user initiates the logout, and the state changes from the registered state to the unregistered state. The S-CSCF does not release the session. The specific process is as follows:

In step S302, the user initiates an initial registration request REGISTER;

In step S304, the S-CSCF initiates a request Cx-Request to the HSS;

In step S306, the S-CSCF receives the response of the HSS Cx-Response;

In step S308, the user registration is successful, and the S-CSCF answers the user request 200 OK. In step S310, the S-CSCF receives the session establishment request INVITE on the host side, and the user is in the registered state, and performs an unconditional forwarding irrelevant to the registration status. Business

In step S312, the S-CSCF forwards the session establishment request to the called network INVITE; in step S314, the S-CSCF receives the session establishment response 200 OK;

In step S316, the S-CSCF forwards the session establishment response 200 OK;

In step S318, the user initiates a logout request USER_DEREGISTRATION; in step S320, the S-CSCF initiates a request Cx-Request to the HSS;

In step S322, the S-CSCF receives the response of the HSS Cx-Response;

In step S324, the user logs out successfully, the S-CSCF answers the user request 200 OK, and the user status is unregistered; In step S326, since the session type of the logged-out user is a state-independent session established in the registered state, the reason for the logout is USER_DEREGISTRATION, and the S-CSCF judges according to the user session type and the logout reason value, and does not release the user established session. Unconditional forwarding session.

By analyzing the above embodiment, it can be seen that the S-CSCF will select whether to judge whether to open the established session according to the session type and the reason value of the user logout. For example, in application example 1, the S-CSCF selects to release the established session according to the session type and the reason value of the user logout; and in the application example 2, the S-CSCF selects according to the session type and the reason value of the user logout. Release the established session.

It is worth noting that, from the analysis of Table 2 above, as long as it is determined that the session type is a state-related session established in the registered state, the call control entity will release the session regardless of the value of the logout reason. .

It is also worth noting that, as can be seen from the analysis of Table 2 above, as long as the session type is determined to be an emergency session, the call control entity will not release the session regardless of the value of the logout reason.

It can be seen that the call control entity can also use the session type to determine whether to release the session. In the second embodiment of the method for releasing a session according to the present invention, the session type that is not released is set to the set reservation type in the CSCF; and the session type that needs to be further determined according to the logout reason to release the session may also be set. To set the type of distinction. If the session type does not belong to the above two types, the session is released.

For the sake of brevity, please refer to the foregoing description for the same contents in the second embodiment as in the first embodiment, and the description is not repeated. The processing flow of the CSCF in the second embodiment is as follows:

Receiving a logout user request for logging out the user;

Determine whether the type of the session of the logged-out user belongs to the set reservation type. If yes, the session is not placed.

When the session type of the logged-out user does not belong to the set reservation type, it may further determine whether the type of the session belongs to the set discrimination type, and if yes, determine whether to release the session according to the reason for cancellation in the log-out user request; if not, The session is released.

Corresponding to the session released and not released in Tables 1 and 2 above, the retention type can be set. To include an emergency session; setting the classification type may include a session established in a state where the user is not registered and a state-independent session established in a state in which the user has been registered. For a tongue established in a state where the user is not registered, when the logout reason is permanent logout, new server assignment, server change, or cancel service call control entity, the session is released; when the logout reason is management logout, timeout logout, or user logout, Leave the session unreleased. For a state-independent session established in the user's registered state, when the logout reason is permanent logout, new server assignment, server change, or cancel service call control entity, the session is put dry; when the logout reason is management logout, timeout logout, or user When you log out, the session is not released.

It should be noted that, in the first embodiment and the second embodiment of the method for releasing a session in the present invention, the setting of which sessions are released or not released in Tables 1 and 2 is only a possible manner, and the network service provider may Different settings are made according to the needs of the specific application environment. For example, the network service provider may set the session type other than the four types in Table 1 and Table 2 to be released or reserved, or may be set according to other cancellation reasons other than the seven cancellation reasons in Tables 1 and 2. The session is released or retained, and is not limited to the session type or logout reason exemplified in the above embodiment.

The computer program corresponding to the first embodiment and the second embodiment of the method for releasing a session of the present invention may be stored in a readable storage medium, and the readable storage medium may be accessed by optical, electromagnetic, semi-conductor or other means.

5 is a schematic structural diagram of an embodiment of a session release apparatus for a session control entity CSCF according to the present invention. The request receiving unit 510 receives a user logout request for canceling a user, and the user logout request may be initiated by the user requested to log off to the CSCF. , initiated by another CSCF to the CSCF, initiated internally by the CSCF, or initiated by the home subscriber server to the CSCF.

The request receiving unit 510 outputs the received user logout request to the session management unit 530, and the session management unit 530 queries the session type unit 520 for the session type of the user requested to log off; the session type unit 520 follows the registration status of the user and/or The session request content determines the type of the user session, and returns the determined session type to the session management unit 530; the session management unit 530 determines whether to release the session established by the user who is requested to log out based on the user logout request and the type of the user session. When the session of the user who is requested to log out is set When the retention type is fixed, the session is not played; when the session of the user requested to log off is the set classification type, whether to release the session is determined according to the reason for the cancellation included in the user logout request.

The network service provider can determine the type of user session that is released or not released and/or the reason for the logout, for example, the settings in Tables 1 and 2 above can be used.

The above release session device can be applied in the S-CSCF or in the P-CSCF. In the embodiment of the present invention, the CSCF selects whether to release the established session according to the session type and/or the reason value of the user logout, so that the network service provider can release or maintain the corresponding session according to the user and the specific application requirement. The business implementation is more rationalized; for the user, even after being logged off, some sessions that need to be maintained, such as an emergency session, are still in a reserved state, so that the user feels better.

The above is only the embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention are intended to be included within the scope of the present invention.

Claims

Rights request

A method for releasing a session, the method for releasing a call control entity to a user's session, comprising the steps of:

The call control entity receives a logout user request for deregistering the user, the logout user request including a logout reason;

Analyzing a session type of the session and a logout reason value of the logout reason; and

Whether to release the session is determined based on the logout reason value and the session type.

2. The method of releasing a session according to claim 1, wherein the session type comprises:

The first type indicates a session related to the registration status established in the registered state; the second type indicates a session established in the registered state and independent of the registration status; and the third type indicates the establishment in the unregistered state. Conversation; and/or

The fourth type, which represents an emergency session.

The method for releasing a session according to claim 1, wherein the call control entity comprises a service call control entity or a proxy call control entity.

The method for releasing a session according to claim 2, wherein the cancellation user request is initiated by the user to the call control entity, or initiated by another call control entity to the call control entity, Or initiated by the call control entity, or initiated by the home subscriber server to the call control entity, where the home subscriber server is used to centrally manage user subscription data.

The method for dry-distributing a session according to claim 4, wherein the cancellation reason value comprises:

The user logs out, indicating the logout initiated by the user;

Timeout logout, indicating that the other call control entity initiates to the call control entity, or is initiated by the call control entity, indicating that the registration timer expires; and/or

Management logout, indicating that the other call control entity is to the call control entity Initiating, or management logout initiated internally by the call control entity.

The method for releasing a session according to claim 5, wherein the determining whether to release the session according to the logout reason value and the session type comprises:

When the session type is the first type, determining to release the ^ tongue; when the ^ type is the second type,

If it is determined that the logout reason value is the management logout, it is determined not to release the session;

If it is determined that the logout reason value is the timeout logout, it is determined not to release the session;

If it is determined that the logout reason value is that the user logs out, it is determined not to release the session;

When the session type is the third type,

If it is determined that the logout reason value is the management logout, it is determined that the session is not released;

If it is determined that the logout reason value is that the user logs out, then it is determined not to release the session; or

When the session type is the fourth type, it is determined that the session is not placed.

The release session method according to claim 5 or 6, wherein the cancellation reason value further comprises:

Permanently terminated, indicating that the IP multimedia public user identifier corresponding to the IP multimedia private user identifier of the service call control entity and the implicit registration set are no longer assigned to the service call control entity;

a new server assignment, indicated by the home subscriber server, indicating that the service call control entity IP multimedia public user identity is assigned to a new service call control entity; the server changes, indicating that the home subscriber server initiates, indicating the The service call control entity forcibly deregisters the user, and causes the user to select another service call control entity; and / or

The service call control entity is deactivated, indicating that the IP multimedia public user identity initiated by the home subscriber server indicating that the service call control entity is not registered is no longer assigned to the service call control entity.

The method for releasing a session according to claim 7, wherein the determining whether to release the session according to the cancellation reason value and the session type comprises:

When the session type is the second type,

If it is determined that the logout reason value is the permanent termination, determining to dry the conversation;

Determining to release the session if it is determined that the logout cause value is the new server assignment;

If it is determined that the logout reason value is the server change, determining to release the session;

Determining to release the session if it is determined that the logout reason value is the cancel service call control entity; or

When the session type is the third type,

If it is determined that the logout reason value is the permanent termination, then it is determined that the front is placed;

If it is determined that the logout reason value is the new server allocation, then determining to release the session;

If it is determined that the logout reason value is the server change, then determining to release the session;

If it is determined that the logout reason value is the cancel service call control entity, it is determined to release the session.

A method for releasing a session, the call control entity for releasing a user's session, characterized by comprising the steps of:

Receiving a logout user request for logging out the user;

When the type of the user session is a set reservation type, the session is not played.

10. The method of releasing a session according to claim 9, wherein: the logout The user request includes the reason for the logout;

The method further includes: determining, when the type of the user session is a set discrimination type, whether to release the session according to the logout reason.

The method for releasing a session according to claim 10, wherein: the setting of the classification type includes a session that is established in a state in which the user has been registered and is not related to the registration state; : The session is not released when the logout reason is administrative logout, timeout logout, or user logout.

The method for releasing a session according to claim 10 or 11, wherein: the set discrimination type includes a session established in a state in which the user is not registered;

The determining whether to release the session according to the reason for the cancellation includes: when the reason for the cancellation is management cancellation, timeout cancellation, or user logout, the session is not released.

13. The method of releasing a session of claim 9, wherein: said setting a reservation type comprises an emergency session.

14. A device for releasing a session, for a call control entity, comprising: a request receiving unit, a session type unit, and a session management unit, wherein:

The request receiving unit is configured to receive a user logout request for canceling the user;

The session type unit is used to determine the type of the session;

The apparatus for releasing a session according to claim 14, wherein the session management unit determines whether to release the session comprises: releasing the session when the session of the user requested to log off is a set reservation type.

The device for releasing a session according to claim 14, wherein: the logout user request received by the request receiving unit includes a logout reason;

Determining whether to release the session includes: when the session of the user requested to log off is a set discrimination type, determining whether to release the session according to the logout reason.

17. The apparatus for dry play session of claim 14, wherein: the call control entity comprises a service call control entity or a proxy call control entity.