WO2011047564A1

WO2011047564A1 - Method for handling users by application server and application server thereof

Info

Publication number: WO2011047564A1
Application number: PCT/CN2010/075245
Authority: WO
Inventors: 邵彬; 周凯祺
Original assignee: 中兴通讯股份有限公司
Priority date: 2009-10-21
Filing date: 2010-07-19
Publication date: 2011-04-28
Also published as: CN102045318B; CN102045318A

Abstract

A method for handling users by Application Server (AS) and an Application Server are disclosed in the present invention. The method includes the following steps: an AS determines whether a registered user timeout occurs; in the case of the registered user timeout, the AS deletes data of the registered user, and releases the call of the registered user. Using the present invention, it can be ensured that the AS can handle users normally in the subsequent procedure.

Description

TECHNICAL FIELD The present invention relates to the field of communications, and in particular to a user processing method and an application server for applying a server. Background technique

The IP Multimedia Core Network Subsystem (IMS) is based on the Session Initiation Protocol (SIP). The SIP protocol is a way to create, modify, and terminate a session between two or more parties. Application layer protocol. The functional entities of the IMS mainly include: a Call Session Control Function (CSCF) that controls functions such as user registration and session; a Home Subscriber Server (HSS) that centrally manages user subscription data; An application server (Application Server, abbreviated as AS) for business logic control functions. FIG. 1 is a flowchart of a third party registration and logout of an IMS user according to the related art. As shown in FIG. 1 , the process mainly involves performing a Serving Call Session Control Function (S-CSCF), an HSS, and an AS. The process includes the following steps: Step S101: The IMS user initiates a registration request. Step S102 to step S103, the S-CSCF acquires user data of the user from the HSS. Step S104, the S-CSCF sends a registration success response to the user. Step S105 to step S106, the S-CSCF initiates a third party registration with the AS, and the registration is successful. Step S107, the IMS user initiates a logout request. Step S108 to step S109, the S-CSCF initiates a third-party logout to the AS, and the logout is successful. In step S110, the S-CSCF sends a logout success response to the user. As can be seen from the above steps, the existing third-party registration and logout mode has the following problems: 1. Conventions in the existing agreement: After the registered user times out, the S-CSCF needs to send a BYE to the calling party to end the session. However, in the actual application, there is a case where the AS registered user times out and the S-CSCF does not time out (or, when the user logs out, the S-CSCF's logout message is not sent to the AS side due to the network;), the protocol in the above case There is no agreement on the behavior of the AS side.

2. When the registered user times out on the AS side, if the AS does not process, the user does not know that it has been logged out, and the subsequent service triggering will fail, resulting in a bad user body.

3. When the registered user timeout occurs on the AS, if the AS does not process the accounting, the accounting time for the user may be too long, and the accounting error may occur. An effective solution has not been proposed in the related art for a problem that may be caused by the fact that the AS side does not have corresponding processing after the registered user times out (for example, the user has abnormal call or the user's billing information is incorrect). SUMMARY OF THE INVENTION The present invention has been made in view of the problems that may be caused by the fact that the AS side does not have corresponding processing after the registration user times out, and the main object of the present invention is to provide a user processing solution of the application server to solve the above problems. one. In order to achieve the above object, according to an aspect of the present invention, a user processing method of an application server is provided. The user processing method of the application server according to the present invention includes: the application server determines whether the registered user times out; in the case that the registered user times out, the application server deletes the data of the registered user and releases the call of the registered user. Preferably, after the application server determines that the registered user times out, the method further includes: the application server sending the charging end information of the registered user to the charging gateway. In order to achieve the above object, according to another aspect of the present invention, an application server is also provided. The application server according to the present invention includes: a determining module, configured to determine whether a registered user times out; a deleting module, configured to delete data of the registered user when the registered user times out; and a release module, configured to release the call of the registered user. Preferably, the application server further includes: a sending module, configured to charge the registered user The bundle information is sent to the billing gateway. With the present invention, the AS deletes the service information related to the time-out registered user, and ensures that the user data is processed normally in the AS. In addition, the AS can also send the charging end information after deleting the related service information of the time-out registered user, and the solution is solved. In the related art, problems may occur due to the absence of corresponding processing on the AS side after the registration user times out, and the normal processing of the subsequent processes of the AS is ensured. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawings: FIG. 1 is a flowchart of a third party registration and deregistration of an IMS user according to the related art; FIG. 2 is a flowchart of a user processing method of an application server according to an embodiment of the present invention; FIG. 3 is a registration of an embodiment of the present invention. FIG. 4 is a flowchart of processing of an internal "user life cycle detection" module in a case of a registered user timeout according to an embodiment of the present invention; FIG. 5 is an application according to an embodiment of the present invention. FIG. 6 is a structural block diagram of an application server according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. In the following embodiments, the steps shown in the flowchart of the accompanying drawings may be performed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some In this case, the steps shown or described may be performed in a different order than the ones described herein. Embodiment 1 In this embodiment, a user processing method of an application server is provided. FIG. 2 is a flowchart of a user processing method of an application server according to an embodiment of the present invention. As shown in FIG. 2, the method includes the following steps 202 to Step 204: The AS determines whether the registered user times out. Step 204: When the registered user times out, the AS deletes the data of the registered user, and releases the call of the timed registered user. Specifically, when the registered user times out, the AS deletes the related user data (that is, the user is an unregistered user for the AS thereafter), and at the same time, releases the current call of the timed registered user (ie, ends the timed registered user) Conversation). The reason why the abnormality of the user's call and the user's billing information are incorrect after the registered user has timed out is as follows: If the registered user has timed out, the user has actually logged off for the AS, and subsequent processing for the user It can only be processed according to the unregistered state. If the user's related data is not deleted and the call related to the user is released, the user's service will be abnormal. Moreover, the AS cancels the user and releases the call related to the user. If the charging end information related to the user is not sent to the charging gateway, the accounting error will be caused. Based on the above, the related data of the timeout registered user is deleted through the above steps 202 to 204, and the timed registered user is released. The call can guarantee the normal processing of the user in the subsequent process of the AS. Preferably, in step 202, the AS may set a lifetime (ie, a registration lifetime) for the registered user after receiving the registration request message of the registered user, and after the timeout period expires, the AS determines that the registered user times out. Preferably, the AS may set the lifetime of the registered user according to the expiration time in the expiration time field carried in the registration request message. Specifically, after the registered user is registered, the AS monitors the registration life cycle of the user in real time; when the registered user times out, the AS deletes the data of the service data area and the call data area of the timeout registered user found through the user account, if the user is still In the call state (ie, there is a call data area), the call data area of the user is deleted; then, the AS sends a BYE message to the calling and called sides respectively. Preferably, the session charging end message may be sent to the charging gateway at the same time, and the reason code value in the charging information may also be filled in as an internal failure. This step can solve the problem of billing errors. Embodiment 2 FIG. 3 is a flowchart of the process of the AS release session in the case of the registered user timeout in the embodiment of the present invention. As shown in FIG. 3, the process includes the following steps: Step S301: When the AS side user registration times out, the AS deletes the user. Data, and release the user call. Step S302, the AS sends the session charging end message to the charging gateway, and the reason code value in the charging information is filled in as an internal failure (the value is filled in as "Internal error" 3 , and the value may refer to 3GPP TS 32.299, where No longer;). Step S303 - Step S306, the AS sends a BYE message to the calling side and the called side respectively. Specifically, in step S303, the AS sends a BYE message to the calling side. In step S304, the calling side returns a message response response of 200 OK. In step S305, the AS sends a BYE message to the called side. Step S306, the called side returns 200 OK. The message replies to the response. Preferably, in order to implement step S301, a "user life cycle detection" logic function module may be added inside the AS to dynamically detect the lifetime of each registered user data in real time, and when the registered user times out, immediately delete the information of the registered user. And notifying the service module to end the session, and sending an accounting end message to the charging gateway. The specific functional principle of the above-mentioned "user life cycle detection" logic function module is as follows: When the module receives the initial third-party registration message of the user, the user's survival is taken out from the expired (expire) field of the register message. The cycle time is used as the timer duration, and the keepalive timer of the user is set. If the module receives the refresh registration message of the user before the user's keep-alive timer expires, the duration in the expire field of the refresh registration message is reset to the keep-alive timer of the user; Before the keep-alive timer expires, the module receives the log-out message of the user, and deletes the keep-alive timer and all service information of the user. Specifically, the module can traverse all the service call data areas according to the Public User Identities (PUI) account of deleting the user. If the data area of the user can be searched, the user is in a call state. At this time, the module will notify the service module to release the data area of the user, end the session of the user, and send the charging end message of the user to the charging gateway; if the user The keep-alive timer expires and no refresh registration or logout message has been received between this user. This indicates that the user's life cycle has expired. At this time, the module will delete all business information of the user. FIG. 4 is a flowchart of processing the internal “user life cycle detection” module of the AS in the case of a registered user timeout according to an embodiment of the present invention. As shown in FIG. 4, the process includes the following steps: Step S402, the initial registration or the received initial registration or Refreshing the expire field value in the registration message is taken out; Step S404, setting and starting the user's keep-alive timer. Step S406: When the keep-alive timer arrives, the user data is deleted. Step S408, the service module is notified to delete the data area, end the session, and send an accounting end message to the charging gateway. Embodiment 3 This embodiment provides an application server, and the application server corresponds to the foregoing embodiment and its preferred embodiments. The descriptions that have been made in the foregoing embodiments are not described herein again. The following is the application. A description of the specific modules in the server. FIG. 5 is a structural block diagram of an application server according to an embodiment of the present invention. As shown in FIG. 5, the application server includes: a determining module 51, a deleting module 52, and a releasing module 53. The following describes the jt匕 structure in detail. a module 51 for determining whether the registered user has timed out; the deleting module 52 is connected to the determining module 51, for deleting the data of the registered user when the registered user times out; the releasing module 53 is connected to the determining module 51, for Release the call of the registered user. FIG. 6 is a structural block diagram of an application server according to an embodiment of the present invention. As shown in FIG. 6, the application server further includes: a receiving module 62, configured to receive a registration request message of a registered user; and the setting module 64 is connected to the receiving module. The determining module 51 is configured to set a lifetime for the registered user. After the timeout period expires, the determining module 51 determines that the registered user times out. Preferably, as shown in FIG. 6, the setting module 64 includes: an obtaining submodule 641 and a setting submodule 642, which will be described below. The obtaining sub-module 641 is configured to obtain the expiration time from the expiration time field carried in the registration request message, and the setting sub-module 642 is configured to set the survival duration according to the expiration time. Preferably, as shown in FIG. 6, the deleting module 52 includes: a first sub-module 521, configured to delete the note The user data of the user; the second sub-module 522 is configured to delete the call data of the registered user. As shown in FIG. 6, the application server further includes: the sending module 66 is connected to the determining module 51, and the module is configured to send the charging end information of the registered user to the charging gateway. In summary, the foregoing embodiment of the present invention solves the problem that the session processing of the user is abnormal when the user registration timeout occurs on the AS side, ensuring normal processing of user data in the AS, and also ensuring charging information. The correctness of the user has increased the user's body-risk. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred 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 scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

A user processing method for applying a server, comprising:

The application server determines whether the registered user times out;

In case the registered user times out, the application server deletes the data of the registered user and releases the call of the registered user.

The method according to claim 1, wherein the determining, by the application server, whether the registered user times out comprises:

After the application server receives the registration request message of the registered user, the application server sets a lifetime for the registered user;

After the timeout period expires, the application server determines that the registered user times out.

The method according to claim 2, wherein the setting, by the application server, the survival time for the registered user comprises:

The application server sets the lifetime duration according to the expiration time in the expiration time field carried in the registration request message.

The method according to claim 1, wherein the deleting, by the application server, the data of the registered user comprises: deleting service data and call data of the registered user.

The method according to any one of claims 1 to 4, wherein after the application server determines that the registered user times out, the method further includes:

The application server sends the charging end information of the registered user to the charging gateway.

6. An application server, characterized in that:

a determining module, configured to determine whether the registered user times out;

a deleting module, configured to delete data of the registered user when the registered user times out;

And a release module, configured to release the call of the registered user.

The application server according to claim 6, further comprising:

a receiving module, configured to receive a registration request message of the registered user; a setting module, configured to set a survival time for the registered user;

The determining module is specifically configured to determine that the registered user times out after the timeout period expires.

The application server according to claim 7, wherein the setting module comprises: an obtaining submodule, configured to obtain the expiration time from an expiration time field carried in the registration request message;

Setting a sub-module, setting the survival time according to the expiration time.

The application server according to claim 6, wherein the deleting module comprises: a first submodule, configured to delete service data of the registered user;

The second submodule is configured to delete the call data of the registered user.

The application server according to any one of claims 6 to 9, further comprising: a sending module, configured to send the charging end information of the registered user to the charging gateway.