WO2009092310A1

WO2009092310A1 - Service provision method and device for a user

Info

Publication number: WO2009092310A1
Application number: PCT/CN2009/070112
Authority: WO
Inventors: Shufeng Shi; Linfei Shen
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2008-01-18
Filing date: 2009-01-12
Publication date: 2009-07-30
Also published as: CN101489215A

Abstract

A service provision method for a user includes the following steps: when a Serving-Call Session Control Function S-CSCF entity receives a service request from the user, it determines that the S-CSCF entity itself does not store user data of the user. The S-CSCF entity obtains user data of the user, and provides services for the user according to user data. A Serving-Call Session Control Function S-CSCF entity is also provided. After the S-CSCF entity in the network is down or restarted abnormally, it can not provide services for the user continuously. The restarted S-CSCF entity or a substitute S-CSCF entity obtains user data and provides continuously initial services or terminating services for the user according to user data, which can avoid the user worse service experience caused by the network entity abnormity.

Description

METHOD AND APPARATUS FOR PROVIDING BUSINESS TO USER This application claims priority to Chinese Patent Application No. 200810001411.7, entitled "Method and Equipment for Providing Business for Users", which was filed on January 18, 2008. The entire contents are incorporated herein by reference. Technical field

The present invention relates to the field of network technologies, and in particular, to a method and device for providing services to users. Background technique

With the development of technologies in the field of communications, IMS (IP Multimedia Subsystem) has become the next generation of fixed and mobile core networks. Access technologies and services will be diversified, IP bearers will be carried, and core networks will be unified to IMS. Development trends and the evolution of the network. Users will get a better business experience in the IMS network.

The existing IMS includes a CSCF (Call Session Control Function), which is in the core control position of the IMS core network, and is responsible for registration authentication and session control of the UE (User Equipment); The Home Subscriber Server (HSS) is a user database server that stores the IMS subscription information set when the operator opens an account, and supports customization and modification of the subscription data by the operator or the terminal user through the interface with the service management system. . The CSCF includes an S-CSCF (Serving-CSCF, Serving Call Session Control Function), a P-CSCF (Proxy-CSCF, Proxy Call Session Control Function), and an I-CSCF (Interrogating-CSCF, Interrogation Call Session Control Function).

In the prior art, if a user wants to use a service, it first needs to register in the network, and then complete the session connection through each interface in the IMS network.

In the process of implementing the present invention, the inventors have found that at least the following problems exist in the prior art: When a S-CSCF registered by a user is suddenly down and restarted, if the user-related UE has not registered in the process , user registration information in HSS No changes have occurred, and registered users are still recorded as being registered on the original S-CSCF. Thus, when the S-CSCF receives the session request sent by the user, because the S-CSCF does not have corresponding user data, the S-CSCF sends a SAR (Server Assignment Request) requesting user data to the HSS, and the HSS finds The S-CSCF recorded in the S-CSCF and the HSS are the same, but the user status of the requested operation is registered in the HSS, and the HSS will not return the user's service information, so the service will fail. Summary of the invention

The embodiments of the present invention provide a method and a device for providing services for a user, so that the S-CSCF in the network can continue to provide services for users after a downtime or abnormal restart.

To achieve the above objective, an embodiment of the present invention provides a method for providing a service for a user, including:

When the service call session control function entity receives the service request from the user, the S-CSCF determines that the user data of the user is not saved.

The S-CSCF obtains user data of the user, and provides a service for the user according to the user data.

The embodiment of the present invention further provides a service call session control function entity S-CSCF, including:

The determining unit, when receiving the service request of the user, determines that the user data of the user is not saved by itself; and the user data of the user is obtained when the user data is used;

And a processing unit, configured to provide a service for the user according to user data acquired by the data acquiring unit.

Compared with the prior art, the embodiment of the invention has the following advantages:

When the S-CSCF fails to provide services to the user after a downtime or abnormal restart in the network, the user's data is obtained, and the user is provided with the originating service or the final service according to the user's data, thereby avoiding the abnormality of the network entity. Poor business volume brought by users DRAWINGS

Figure 1 is a functional architecture diagram of an IMS network;

2 is a schematic diagram of a session flow initiated by a user;

3 is a schematic diagram of a session flow in which an AS initiates a call in place of a user;

4 is a flowchart of a method for providing a service to a user in an embodiment of the present invention;

5 is a flowchart of service recovery after the S-CSCF is restarted in the first embodiment of the present invention; FIG. 6 is a flowchart of service recovery after the S-CSCF is down in the second embodiment of the present invention; FIG. 7 is an S-CSCF in the embodiment of the present invention; Schematic diagram of the structure;

FIG. 8 is a schematic structural diagram of an S-CSCF according to an embodiment of the present invention. detailed description

In the IMS network, the architecture diagram of the IMS network is shown in Figure 1. The CSCF is in the core control position of the IMS core network. It is responsible for the registration authentication and session control of the UE. The execution is for the calling and called terminals. The basic session routing function of the IMS user, and according to the IMS filtering rule signed by the user, the value-added service route triggering and service control interaction to the AS (Application Server, Application Server) are performed when the conditions are met. The HSS is a user database server, which stores the IMS subscription information set when the operator opens an account, and supports customization and modification of the subscription data by the operator or the terminal user through the interface with the service management system. The HSS registers the S-CSCF domain name routing information in the IMS registration process through the Cx interface based on the Diameter protocol with the S-CSCF, and supports downloading the basic IMS subscription information to the S-CSCF through the interface; the HSS passes the I-CSCF The Cx interface based on the Diameter protocol implements the S-CSCF for user selection in the user registration or provides the I-CSCF with the name of the S-CSCF currently serving the user, so that the I-CSCF can route the registration message or session to the correct one. The S-CSCF provides the Sh interface based on the Diameter protocol with the SIP AS. It is a Session Initiation Protocol (SIP) or an Open Access Architecture (SCS) (Service Capability Servers). Service Capability Server) Provides remote database access interfaces for contract data and business logic scripts.

The HSS is only responsible for the transparent storage of the value-added service data of the specific contracted user, and is not semantically parsed. The SLF (Subscription Locator Function) has an address resolution mechanism. When the network operator belongs to multiple independently addressable HSSs, this mechanism enables the I-CSCF, S-CSCF, and AS to find The HSS address where the subscription data of the user identity is located can be physically combined with the HSS. The AS obtains or updates user service related data and user status information through the Sh interface of the HSS, and the S-CSCF obtains the user's subscription information through the Cx interface with the HSS.

After the UE registers in the network, it can use various services provided by the IMS network. At the same time, the UE may choose to subscribe to the unregistered service. When the UE is not registered in the network, the network may still provide the user with unregistered services such as incoming call forwarding, incoming call records, and the like. When the UE is registered in the network or the user is the terminating call, the S-CSCF and the HSS authenticate the user and the service data through the SAR/SAA (Server Assignment Answer) command of the Cx interface.

SAR/SAA application scenario: When the S-CSCF receives a registration request from a UE sent by the P-CSCF or receives a session establishment request INVITE message from the I-CSCF.

(1) The S-CSCF performs the following operations to the HSS through the SAR command:

1. Assign an S-CSCF to the public identity, or clear the name of the S-CSCF assigned to one or more public identities;

2. Request to download user information, including user data or billing information;

3. Change the registration status of the PU (IP Multimedia Public User Identity) of the user.

The main application layer parameters carried in the message are shown in Table 1: Table 1 Main application layer parameters carried in the message

IE name mapped category description

Diameter AVP Public User Public-Identity C One or more public Identities/Public (conditions are required, except for the service identity other than the registration). Must be included and can only contain one. You must include this account when you go to the registration operation but the private identity does not exist.

S-CSCF Name Server-Name M (Required) S-CSCF name

Private User User-Name C Private identity, for S-CSCF Identity/Private (when the condition is met, it must be included. When you select Service Identity), if the public identity does not exist, you must include the private share.

Server Server- M (Required) The S-CSCF asks for an Assignment Assignment to the HSS.

Type Type

User Data Already User-Data- Already- M (Required) The S-CSCF tells the HSS that Available Available data is available.

Server Assignment Type—There are 12 values, the meanings are as follows:

1. NO_ASSIGNMENT(0): Used by the S-CSCF to request user data from the HSS without affecting the registration status of the user;

2, REGISTRATION (l): for the first registration of an identity;

3. RE_REGISTRATION(2): used for re-registration of an identity;

4. UNREGISTERED_USER(3): Used to instruct the S-CSCF to receive an INVITE request for a call to an unregistered user;

5, TIMEOUT_DEREGISTRATION (4): used to deregister due to the registration timer timeout;

6. USER_DEREGISTRATION(5): Used by the S-CSCF to receive a user-initiated deregistration request;

7, TIMEOUT_DEREGISTRATION_STORE_SERVER_NAME (6): Used for deregistration due to the registration timer timeout, while the S-CSCF saves the user data and requests the HSS to save the name of the S-CSCF;

8. USER_DEREGISTRATION_STORE_SERVER_NAME (7): The S-CSCF received the user-initiated de-registration request, and the S-CSCF saved the user data and requested the HSS to save the name of the S-CSCF.

9. ADMINISTRATIVE_DEREGISTRATION(8): Used for S-CSCF to perform an identity de-registration for administrative reasons;

10, AUTHENTIC ATION_FAILURE (9): used to indicate user authentication failure;

11. AUTHENTIC ATION_TIMEOUT(10): Used to indicate the authentication timeout; 12. DEREGISTRATION_TOO_MUCH_DATA(l 1 ): Used by the S-CSCF to request user data from the HSS, but the amount of data received exceeds the size acceptable to the S-CSCF. .

If the name of the S-CSCF in the SAR received by the HSS is different from the name of the S-CSCF stored in the HSS, the HSS will not replace the original with the name of the new S-CSCF, but return the Experimental-Result-Code to

DIAMETER_E OR_IDENTITY_ALREADY_REGISTERED indicates that the user has been assigned an S-CSCF.

When the operation type in the SAR received by the HSS is an operation that is not allowed by the current state of the user, for example, the Server Assignment Type is UNREGISTERED—the USER indicates that the S-CSCF has received an INVITE request to terminate the call to an unregistered IMPU, but the IMPU in the HSS is Registered, HSS will return Experimental-Result-Code to DIAMETER_E OR_IN_ASSIGNMENT_TYPE, indicating that the S-CSCF has been assigned to the user, and the user's current state does not allow the operation.

(2) The contents returned by the HSS to the S-CSCF through the SAA command include: processing result, user data, charging information, and all IMPI (IP Multimedia Private User Identity) belonging to the IMS Subscription.

The main application layer parameters carried in the message are shown in Table 2: Table 2 Main application layer parameters carried in the message Category description of IE name mapping

Diameter AVP

Private User C Private identity. Identity/Private User-Name when available to HSS (conditional satisfaction must be included.

Required for Service Identity)

Registration result Result- M Result-Code is used to indicate

Code/Experimental- (Required) The return Result value defined in the Diameter base protocol Experimental-Result is used to indicate the newly defined return value on the Cx/Dx interface.

User Profile User-Data C requested user data

(conditions are met

Must be selected)

Charging Charging C Address of the accounting function, User-Data Information Information (The condition must exist when the condition is met.

Must be selected)

0 PI or PU in IMS

Associated Associated- (optional) All PIs to which subscription belongs, IMS Private Identities Identities subscription only contains one PI

AVP does not exist.

The HSS may download the user data and billing function address when the operation type is NO_ASSIGNMENT, REGISTRATION, RE_REGISTRATION, UNREGISTERED_USER.

In the prior art, the initial call session process of the user registered in the network, as shown in FIG. 2, includes the following steps:

Step s201: The UE initiates an INVITE message, and may select to fill in a P-Preferred-Identity header field with a Public User Identity that can identify itself.

Step s202: After receiving the INVITE message, the P-CSCF checks whether there is any message in the message. P-Preferred-Identity header field and check whether its value matches a registered Public User Identity recorded in the P-CSCF. If there is and matches, the P-CSCF uses the Public User Identity as the session initiator and fills in the P. - Asserted-Identity; if there is no match or no P-Preferred-Identity header field, the P-CSCF selects a default Public User Identity for the user as the session initiator and fills in the P-Asserted-Identity;

Step s203: After receiving the INVITE message, the S-CSCF performs service triggering according to the identity of the calling user in the P-Asserted-Identity header field in the message, and then performs routing of the subsequent session according to the Request-URI in the INVITE message. .

The AS replaces the initial call session process of the user who has registered in the network. As shown in FIG. 3, the following steps are included:

Step s301: If the AS can obtain the name of the S-CSCF where the user is located before the user initiates the initial call, perform step s301a of FIG. 3, that is, the AS directly routes the session to the S-CSCF where the user is located. If the name of the S-CSCF where the user is located cannot be obtained, the following steps s301bl need to be performed;

Step s301a, routing the session to the S-CSCF of the home domain where the user is located;

Step s301bl, routing the session to the I-CSCF of the home domain where the user is located;

Step s301b2: The I-CSCF initiates a location information request (LIR) message to the HSS, fills in the identity of the calling user in the P-Asserted-Identity header field in the message, and adds an initial call request flag. Query the current location information of the user, that is, the information of the S-CSCF where the user is located;

Step s301b3, the HSS queries the information corresponding to the user in the database according to the identity of the user in the LIR, and returns the name of the S-CSCF where the user is located or the capability set of the S-CSCF to the I through the LIA (Location Info Request). -CSCF;

Step s301b4, if the HSS returns the capability set of the S-CSCF, the I-CSCF needs to select the S-CSCF according to the capability set;

Step s301b5, the I-CSCF routes the INVITE message to the S-CSCF returned by the HSS, or the S-CSCF selected by the user according to the capability set of the S-CSCF returned by the HSS;

Step s302: If the S-CSCF does not have the information of the user, the S-CSCF will message The user identity in the P-Asserted-Identity header field carries the user subscription data in the SAR to the HSS; if there is information about the user, step s304 is directly performed;

Step s303: The HSS returns the requested user subscription data to the S-CSCF through the SAA. Step s304: The S-CSCF performs service control.

Step s305: The S-CSCF performs subsequent processing.

An embodiment of the present invention provides a method for providing a service to a user. As shown in FIG. 4, the method includes the following steps:

Step s401: The S-CSCF receives the service request of the user.

Specifically, the service request of the received user may be: an AS originating service request initiated by the AS, or an originating service request initiated by the I-CSCF instead of the user, or a user terminal forwarded by the I-CSCF. The originating service request initiated, or the final service request sent by the I-CSCF.

Step s402: The S-CSCF finds that the data of the user does not exist locally.

Specifically, the S-CSCF may be restarted due to downtime or abnormality, resulting in loss of user data; or the S-CSCF is an alternative S selected by the I-CSCF when the S-CSCF providing services for the user fails. -CSCF, so there is no data for this user.

Step s403: The S-CSCF acquires data of the user.

Specifically, the S-CSCF may send a request message to the HSS to obtain data of the user. Step s404: The S-CSCF determines a registration status of the user according to the acquired data, and provides a service for the user.

Specifically, the data of the user includes at least the subscription service configuration data of the user, and the S-CSCF performs service matching and triggering according to the initial filtering rule in the subscription service configuration data of the user; and may also include the registered backup data of the user. The registration backup data includes, but is not limited to, the address of the P-CSCF stored by the S-CSCF at the time of registration and the CONTACT address of the user equipment. Based on the acquired data of the user, the S-CSCF can learn the registration status of the user, and then process the service request of the user to provide services for the user.

Specific embodiments of the present invention are described below in conjunction with specific application scenarios.

In the first embodiment of the present invention, the S-CSCF restarted by the downtime receives an originating service request initiated by the AS instead of the user, or receives an AS that is transferred from the I-CSCF instead. When the user initiates an originating service request, or receives a final service request sent by the I-CSCF, the processing flow of the service request is as shown in FIG. 5, and includes the following steps:

Step s501: The S-CSCF receives the AS sent by the AS or the I-CSCF instead of the user-originated originating service request, where step 501a, step 501bl-501b4 is the same as the prior art, or the S-CSCF receives as shown in step 501c. The final service request sent by the I-CSCF;

Step s502: If the S-CSCF does not have the data of the user, request the unregistered service data of the user from the HSS through the SAR according to a normal process;

Step s503a, the HSS determines the name of the S-CSCF requesting the data. When the name of the S-CSCF that the HSS finds the request data is the same as the name of the saved S-CSCF, and the registration status of the user is already registered, the HSS returns The indication information that the user identity of the user has been registered does not return the user subscription data and the registration backup data, wherein the indication information may be indicated by a DIAMETER_ERROR_IN_ASSIGNMENT_TYPE error code, and the HSS may also add an indication to the SAA that the request is not registered. The user identity of the business is registered;

Step s503b: After receiving the error code, the S-CSCF re-requests the user data to the HSS by using the SAR with the recovery indication;

Step s504: The HSS brings the subscription data of the user to the S-CSCF through the SAA, and the HSS may also add an indication to the SAA that the identity of the user requesting the unregistered service is registered;

The HSS may have the same name of the S-CSCF in the discovery request data and the name of the saved S-CSCF, and when the registration status of the user is registered, the user's subscription data is brought to the S- via the SAA while returning the DIAMETER_ERROR_IN_ASSIGNMENT_TYPE error code. CSCF; Then step s503a, step s503b may not be performed. If the HSS saves the user's registered backup data, you can choose to bring the registered backup data together to the S-CSCF through the SAA;

In addition, in the above step s503a or step s504, the S-CSCF can determine that the user is registered by receiving the DIAMETER_E OR_IN_ASSIGNMENT_TYPE, and the S-CSCF can also determine that the user is registered by receiving the registered backup data of the user, S-CSCF. It is also possible to request unregistered services through the instructions carried in the SAA. The user identity is the registered information, and it is determined that the user is registered.

Step s505: When the S-CSCF receives the originating service request from the AS or the I-CSCF, and the S-CSCF determines that the user is in the registered state by using the step s503a or the step s504, the triggering of the originating registration is triggered. Service; otherwise, the originating unregistered service that triggers the match; when the S-CSCF receives the final service request from the I-CSCF, and the S-CSCF determines, by step s503a or step s504, that the user is in the registered state, and At the same time, when the registered backup data is received, the matching terminated service is triggered; if the user is in the registered state but does not receive the registered backup data, the matching unregistered service is triggered.

Step s506: The S-CSCF performs an initial service request.

In the second embodiment of the present invention, after the S-CSCF is down or abnormal, the I-CSCF receives the final service request, or receives the originating service request initiated by the AS instead of the user, or receives the P- When the CSCF forwards the originating service request initiated by the user terminal, the processing flow of the service request is as shown in FIG. 6, and includes the following steps:

Step s601: The I-CSCF forwards the service request to the S-CSCF1 that provides the service for the user; Step s601a, S-CSCF1 returns a failure response indicating that an abnormality cannot continue to provide services for the user; or step s601b, I-CSCF does not receive the S - The response of the CSCF1; Step s602, the I-CSCF explicitly requests the capability set of the S-CSCF to the HSS; if the I-CSCF has received the service request message and has learned that the S-CSCF1 is down or abnormal, the above step s601 may not be performed. Step s601a and step s601b;

Step s603, the HSS returns the capability set of the S-CSCF;

If the previous I-CSCF has obtained the capability set of the S-CSCF serving the user from the HSS, the above step s602, step s603 may not be performed;

Step s604: The I-CSCF reselects an S-CSCF2 for the user according to the capability set of the S-CSCF, and forwards the service request to the new S-CSCF2, optionally, may bring a recovery indication in the message, and explicitly tells S -CSCF2 needs to recover data from HSS;

Step s605: The S-CSCF2 has no user data, and requests the user data to the HSS through the SAR with the recovery indication;

Step s606: The HSS returns the user data to the S-CSCF2 through the SAA, and the HSS may also add an indication to the SAA indicating whether the user identity of the requested data has been injected. Booklet. The user data includes at least the subscription service configuration data of the user, and may optionally include

Registration backup data of the S-CSCF;

Step s607: After receiving the user subscription service configuration data and the registration backup data, the S-CSCF2 triggers the matched registered service. If only the user's subscription service configuration data is received, the user identity of the requested data is not received. The registered information triggers the matching unregistered service; if the user's subscription service configuration data is received, and the information indicating that the user identity of the requested data is registered is received, the start of the matching is triggered for the initial service request. The registered service is sent; for the final service request, the matching unregistered service is triggered.

Step s608, S-CSCF2 performs subsequent routing.

The method provided by the embodiment of the present invention, when the S-CSCF in the network fails to provide services to the user after a downtime or abnormal restart, obtains the user's data, and continues to provide the user with the originating service according to the user data. The final service avoids the poor service experience brought by the network entity exception to the user.

The embodiment of the present invention further provides a service call session control function entity S-CSCF, and its structure is as shown in FIG. 7, which includes:

The determining unit 10, when receiving the service request of the user, determines that the user data of the user is not saved by itself;

The data obtaining unit 20 is configured to acquire user data of the user when the determining unit 10 determines that the user data of the user does not exist locally;

The processing unit 30 is configured to provide a service for the user according to the user data acquired by the data acquiring unit 20.

Specifically, the data obtaining unit 20 further includes:

a first obtaining sub-unit 21, configured to send a request for acquiring user data to the HSS; and a second obtaining sub-unit 22, configured to: when receiving the HSS, returning the user that is returned when the S-CSCF is registered The indication that the user identity of the user has been registered sends a request for carrying the recovery indication to the HSS, and receives data of the user sent by the HSS.

Or further comprising: a third obtaining subunit 23, configured to send the acquiring user to the HSS a request for data, and receiving indication information that the HSS has registered the user identity of the user returned when the user has registered at the S-CSCF, and user data sent by the HSS.

Specifically, the processing unit 30 further includes:

The first determining sub-unit 31 is configured to: when the data obtaining unit receives the indication information that the user identity of the user has been registered or the registered backup data in the received user data, determine that the user has been registered;

The first processing sub-unit 32 is configured to perform processing according to the determination result of the first determining sub-unit 31, and trigger the originating registered service according to the user data for the originating service request of the registered user; for the unregistered user The originating service request, triggering the originating unregistered service according to the user data; and for the final service request of the registered user, if the received user data of the user includes the registered backup data, according to the user data Triggering the terminated service, otherwise triggering the unregistered service; triggering the unregistered service for the unregistered user.

The embodiment of the present invention further provides a service call session control function entity S-CSCF, and its structure is as shown in FIG. 8, which includes:

The determining unit 50, when receiving the service request of the user, determines that the user data of the user is not saved by itself;

The data obtaining unit 60 is configured to acquire user data of the user when the determining unit 50 determines that the user data of the user does not exist locally;

The processing unit 70 is configured to provide a service for the user according to the user data acquired by the data acquiring unit 60.

Specifically, the data obtaining unit 60 further includes:

The fourth obtaining subunit 61 is configured to send a request for carrying the recovery indication to the HSS, and receive user data sent by the HSS.

Specifically, the processing unit 70 further includes:

a second determining sub-unit 71, configured to determine whether the user data acquired by the data acquiring unit includes registration backup data, or information that the HSS indicates that the user identity of the requested data is registered; The second processing sub-unit 72 is configured to perform processing according to the determination result of the second determining sub-unit 71, if the user data includes registration backup data, or when the user identity of the requested data is received as the registered indication information , for the originating service request or the final service request of the user, triggering the originating registered service or the terminally registered service of the user;

If the user data does not include the registered backup data, and the user identity of the requested data is not the registered indication information, the start of the user is triggered for the originating service request or the final service request of the user. Sending an unregistered service or a terminal unregistered service; if the user data does not include the registered backup data, but the user identity of the requested data is the registered indication information, triggering on the initial service request of the user The originating service of the user is registered; for the final service request of the user, the unregistered service of the user is triggered. The foregoing device provided by the embodiment of the present invention, when the S-CSCF in the network fails to provide services for the user after a downtime or abnormal restart, obtains the user's data, and continues to provide the user with the originating service according to the user data. The final service avoids the poor service experience brought by the network entity exception to the user.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a The station apparatus performs the methods described in various embodiments of the present invention.

The above disclosure is only a few specific embodiments of the present invention, but the present invention is not limited thereto, and any changes that can be made by those skilled in the art should fall within the protection scope of the present invention.

Claims

Rights request

A method for providing a service to a user, comprising:

2. The method for providing a service to a user according to claim 1, wherein the obtaining, by the S-CSCF, the user data of the user comprises: the S-CSCF acquiring at least the subscription service configuration data of the user;

The providing the service to the user according to the user data includes: the S-CSCF performs service matching and triggering according to an initial filtering rule in the subscription service configuration data of the user.

3. The method for providing a service to a user according to claim 2, wherein the obtaining, by the S-CSCF, user data of the user includes:

Sending, by the S-CSCF, a request for acquiring user data to the home subscriber server HSS; the S-CSCF receiving the user identity of the user returned by the HSS when determining that the user has registered at the S-CSCF is registered Instructions;

Sending, by the S-CSCF, a request carrying a recovery indication to the HSS;

The S-CSCF receives the response message sent by the HSS, and acquires user data carried in the response message.

4. The method for providing a service to a user according to claim 2, wherein the obtaining, by the S-CSCF, the user data of the user includes:

Sending, by the S-CSCF, a request for acquiring user data to the home subscriber server HSS; the S-CSCF receiving the user identity of the user returned by the HSS when determining that the user has registered at the S-CSCF is registered Instructions, as well as receiving the instructions

User data sent by the HSS.

The method for providing a service to a user according to any one of claims 1 to 4, wherein before the providing the service to the user according to the user data, the method further comprises: receiving, by the S-CSCF according to the receiving Instructions to the user identity of the user that has been registered Or the registered backup data in the received user data, determining that the user has been registered.

The method for providing a service to a user according to claim 5, wherein the providing the service to the user according to the registration status of the user and the user data includes:

For the originating service request of the registered user, the originating registered service is triggered according to the user data; for the originating service request of the unregistered user, the unregistered service is triggered according to the user data;

For the final service request of the registered user, if the received user data of the user includes the registered backup data, the final registered service is triggered according to the user data, otherwise the unregistered service is triggered; The user's final service request triggers the final unregistered service.

7. The method for providing a service to a user according to claim 2, wherein the obtaining, by the S-CSCF, user data of the user includes:

Sending, by the S-CSCF, a request for carrying a recovery indication to the HSS;

The S-CSCF receives user data sent by the HSS.

8. The method for providing a service to a user according to claim 1, 2 or 7, wherein the step of providing a service to the user according to the user data is specifically:

If the user data includes the registration backup data, or the user identity of the requested data is the registered indication information, the originating service request or the final service request of the user is triggered, and the originating of the user is triggered. Registered business or finalized registered business;

If the user data does not include the registered backup data, and the user identity of the requested data is not the registered indication information, the start of the user is triggered for the originating service request or the final service request of the user. Sending an unregistered service or a terminal unregistered service; if the user data does not include the registered backup data, but the user identity of the requested data is the registered indication information, triggering on the initial service request of the user The originating service of the user is registered; for the final service request of the user, the unregistered service of the user is triggered.

A service call session control function entity S-CSCF, comprising: a determining unit, when receiving a service request of a user, determining that the user is not saved by the user User data; when the user data is obtained, the user data of the user is obtained;

The S-CSCF according to claim 9, wherein the data acquisition unit comprises:

a first obtaining subunit, configured to send a request for acquiring user data to the HSS; a second obtaining subunit, configured to: when receiving the HSS, returning the user that is returned when the user has registered at the S-CSCF The indication that the user identity has been registered sends a request carrying the recovery indication to the HSS, and receives data of the user sent by the HSS.

The S-CSCF according to claim 9, wherein the data acquisition unit further comprises:

a third obtaining subunit, configured to send a request for acquiring user data to the HSS, and receive indication information that the HSS returns the user identity of the user that is returned when the user has registered at the S-CSCF, And user data sent by the HSS.

The S-CSCF according to claim 9, 10 or 11, wherein the processing unit comprises:

a first determining subunit, configured to: when the data obtaining unit receives the indication information that the user identity of the user has been registered or the registered backup data in the received user data, determining that the user has been registered;

a first processing sub-unit, configured to perform processing according to the determination result of the first determining sub-unit, and trigger an originating registered service according to the user data for an originating service request of a registered user; Sending a service request, triggering the originating unregistered service according to the user data; and if the received user data of the user includes the registered backup data, the terminal data is triggered according to the user data. The registered service is sent, otherwise the unregistered service is triggered. For the final service request of the unregistered user, the unregistered service is triggered.

And a fourth acquiring subunit, configured to send a request for carrying the recovery indication to the HSS, and receive user data sent by the HSS.

The S-CSCF according to claim 9 or 13, wherein the processing unit further comprises:

a second determining sub-unit, configured to determine whether the user data acquired by the data acquiring unit includes registration backup data, or information that the HSS indicates that the user identity of the requested data is registered;

a second processing sub-unit, configured to perform processing according to the determination result of the second determining sub-unit, if the user data includes registration backup data, or the user identity of the requested data is the registered indication information, The originating service request or the final service request of the user triggers the originating registered service or the terminal registered service of the user; if the user data does not include the registered backup data, the requested data is not received. When the user identity is the registered indication information, triggering the originating unregistered service or the terminal unregistered service of the user for the originating service request or the final service request of the user; if the user data does not include the registration When the data is backed up, but the user identity of the requested data is the registered indication information, the originating service request of the user is triggered, and the originating service request of the user is triggered; , triggering the user's final unregistered service.