WO2006133624A1

WO2006133624A1 - A method for registering at the internet protocol multimedia subsystem

Info

Publication number: WO2006133624A1
Application number: PCT/CN2006/001143
Authority: WO
Inventors: Fenqin Zhu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2005-06-17
Filing date: 2006-05-29
Publication date: 2006-12-21
Also published as: CN1852556A; CN100433913C

Abstract

The present invention is a method for registering at the internet protocol(IP) multimedia subsystem(IMS). The method comprises: presetting and storing the corresponding relation between the S-CSCF and its supporting authentication capability. When it receives the registering request, it gets the S-CSCF’s capability set information of the UE, then determines the type of the authentication capability that the UE supported, and gets the S-CSCF that satisfying the service capability of the UE and supporting the authentication capability of the UE according to the corresponding relation between the S-CSCF and its supporting authentication capability and the S-CSCF’s capability set information , and then sends the register request to the abtained S-CSCF, and continuing the rear process. Therefore, it provide that the authentication capability the UE supported being match with the authentication capability the S&lowbar;CSCF supported

Description

Method for implementing registration in IP multimedia subsystem

The invention relates to the field of mobile communication technologies, in particular to an IP multimedia subsystem

The method of implementing registration in (IMS). Background of the invention

With the development of broadband networks, mobile communications are not limited to traditional voice communications, through the combination of data services such as presence, messaging, web browsing, location information, push services (PUSH), and file sharing. Mobile communication enables a variety of media types such as audio, video, pictures and text to meet the diverse needs of users.

Organizations such as the 3rd Generation Mobile Communications Standardization Partnership Project (3GPP) and the 3rd Generation Mobile Communications Standardization Partnership Project 2 (3GPP2) have introduced IP-based Multimedia Subsystem (IMS) architectures, which are designed to use one in mobile networks. A standardized open structure to implement a wide variety of multimedia applications to provide users with more choices and richer feelings.

The IMS architecture is superimposed on a packet domain network (PS-Domain) in which the authentication-related entities include a Call State Control Function (CSCF) entity and a Home Subscriber Server (HSS) functional entity.

CSCF can be divided into three logical entities: service CSCF (S-CSCF), proxy CSCF (P-CSCF), and query CSCF (I-CSCF). These three logical entities may be different physical devices or the same physical device. Different functional modules in the device. The S-CSCF is a service control center of the IMS, which is used to perform session control, maintain session state, manage user information, and generate charging information. The P-CSCF is an access point for the terminal user to access the IMS, and is used to complete user registration. Quality of Service (QoS) control and security management; I-CSCF is responsible for interworking between IMS domains, managing the allocation of S-CSCFs, hiding network topology and configuration information, and Generate billing data, etc. The HSS is a very important user database that is used to support the processing of calls and sessions by various network entities.

IMS was only considered for use in third-generation mobile communication networks when it was initially introduced (R5 version protocol). Due to the abundance of services on the IMS, there is a need for operators to use IMS on 2G networks. However, in 2G networks, security-related functions of IMS based on 3G networks cannot be supported, such as quintuple authentication/network authentication. In order to solve the problem of user authentication faced by 2G users using IMS networks, 3GPP proposes a transitional authentication. Early IMS, which provides certain security functions for IMS services on 2G. When the user supports the 3G authentication scheme, the complete 3G-based authentication scheme is used to authenticate the access user.

Since two authentication methods are introduced, especially Early IMS is introduced later, there are cases where different network element entities developed by device manufacturers in different periods may support different authentication capability types. The entity supporting the 2G transition authentication mode is referred to as an entity supporting Early IMS authentication, and the entity supporting the 3G authentication mode is referred to as an entity supporting Full 3GPP IMS authentication. Since there are entities in the network that support different authentication methods, the following situations are inevitable: For example, in the home network domain of the user, there are both S-CSCFs that support and do not support Early IMS. If only the Early IMS authentication mode is supported. The P-CSCF sends the received SIP registration request from the UE that supports only the Early IMS authentication mode to the S-CSCF that supports only the Full 3GPP IMS authentication mode. The S-CSCF must follow the Full 3GPP IMS authentication mode. Checking the receipt of the registration request. At this time, the S-CSCF finds that the related header field is missing from the received SIP message, and considers the message to be an illegal message, thus returning a failure response message to the user, but if it is selected at this time Another S-CSCF that supports Early IMS authentication, the user may register successfully.

It can be seen that the user authentication failure in the above situation is caused by the UE not supporting the authentication mode supported by the S-CSCF, not because the UE is not legal, and this is unfair to the legitimate user. Will inevitably reduce user satisfaction. In order to avoid the above situation, some operators of the 3GPP at the current stage stipulate that both the P-CSCF and the S-CSCF are placed in the home network, and support the same type of authentication mode, thereby avoiding the P-CSCF and the S-CSCF. Supporting different types of authentication methods, that is, avoiding the case where the UE and the S-CSCF support different types of authentication methods. However, in actual network operations, as the service progresses, it is impossible to always place the P-CSCF on the home network, that is, there is a case where the P-CSCF is placed on the visited network. In this case, since the P-CSCF and the S-CSCF (P/S-CSCF) belong to different operators, there may be different types of authentication capabilities supported by the P/S-CSCF due to different IMS phases introduced by the operator. Case. Moreover, even if the P/S-CSCF is placed on the same network, it is possible that the P/S-CSCF supports different authentication types due to different stages of introduction.

Furthermore, in order to ensure that the P-CSCF can always select a compatible S-CSCF, the following two methods can be used:

One method is to configure the authentication capability data supported by the S-CSCF in the network in the P-CSCF. With the expansion of the carrier network, the configuration data process will inevitably be complicated and not feasible. At this time, even if the P/S-CSCF is upgraded to support both ways to avoid the complication of the configuration data, there are also successive upgrades, which may cause the network to support different authentication capability types for a period of time. The possibility of P/S-CSCF.

Another method is to combine the P/S-CSCFs in the same network entity, so that as long as the UE is compatible with the authentication capability type of the P-CSCF, it can be guaranteed to be compatible with the S-CSCF authentication capability type. However, as the size of the carrier network expands, the logical functions of the P/S-CSCF are bound to be distributed on different physical entities. In this case, this method cannot be used any more.

The above problems are not considered by the 3GPP but are unavoidable. Summary of the invention

In view of this, the main object of the present invention is to provide an IP multimedia subsystem. The method of implementing registration in (IMS) avoids authentication failure caused by mismatch of authentication capability types.

To achieve the above objective, the technical solution of the present invention is implemented by pre-setting and preserving the correspondence between the S-CSCF and the type of authentication capability supported by the S-CSCF, and the method includes the following steps:

a. After receiving the registration request from the user equipment UE, the I-CSCF obtains S-CSCF capability set information that can provide services for the UE.

The I-CSCF determines the type of the authentication capability supported by the UE, and obtains the requirement of the UE according to the correspondence between the S-CSCF and the type of the authentication capability supported by the S-CSCF and the S-CSCF capability set information. S-CSCF of the service capability type and supporting the UE's authentication capability type;

c. The I-CSCF sends a registration request to the obtained S-CSCF, and continues the subsequent registration processing.

In step b of the foregoing method, the step of determining, by the I-CSCF, the type of authentication capability supported by the UE includes:

The I-CSCF determines whether the acquired S-CSCF capability set information includes the authentication capability type data required by the user, and if yes, determines the authentication supported by the UE according to the authentication capability type data required by the user. The capability type, otherwise, the type of authentication capability supported by the UE is determined according to the registration request initiated by the UE.

In the step b of the foregoing method, the manner in which the I-CSCF determines the type of the authentication capability according to the registration request initiated by the UE includes:

The I-CSCF determines, according to the received registration request of the UE, whether to include an authorized Authorization header field or according to a preset feature that supports different types of authentication capabilities, determining an authentication capability type supported by the UE;

Wherein, determining, according to whether the registration request includes an Authorization header field, determining a UE branch The step of the authentication capability type includes: if the registration request includes an Authorization header field, and the header field usage conforms to the current 3GPP requirements, determining that the UE supports the Full IMS authentication mode; if the registration request does not include the Authorization header field, It is determined that the UE supports the Early IMS authentication mode.

In step b of the foregoing method, the step of the I-CSCF acquiring an S-CSCF that satisfies the service capability required by the UE and supports the authentication capability type of the UE includes:

The I-CSCF determines whether the acquired S-CSCF capability set information includes the authentication capability type data required by the user, and if so, the I-CSCF and the supported authentication capability type of the S-CSCF The corresponding relationship and the authentication capability type data in the acquired S-CSCF capability set information directly obtain an S-CSCF that satisfies the service capability required by the UE and supports the UE's authentication capability type; otherwise, the I-CSCF First, the S-CSCF capability set that satisfies the service capability of the UE is obtained from the obtained S-CSCF capability set information, and then the authentication capability type supported by the UE is determined according to the registration request initiated by the UE, and then the content is satisfied according to the The S-CSCF capability set of the UE's service capability, the determined authentication capability type, and the correspondence between the S-CSCF and the type of authentication capability supported by the UE, obtain the service capability that satisfies the UE and supports the authentication of the UE. The capability type of S-CSCF.

In the above method, the step b further includes: when the acquired S-CSCF capability set information includes the authentication capability type data required by the user set in advance, but the I-CSCF cannot directly obtain the data according to the authentication capability type data. When the S-CSCF that supports the service capability required by the UE and supports the UE's authentication capability type is satisfied, the I-CSCF obtains the S-CSCF capability that satisfies the service capability of the UE from the acquired S-CSCF capability set information. And determining, according to the registration request initiated by the UE, the type of the authentication capability supported by the UE, and then determining the type of the S-CSCF capability that meets the capability of the UE, the type of the authentication capability supported by the UE, and the determined Determining the correspondence between the S-CSCF and the type of authentication capability supported by the S-CSCF, and obtaining the service capability required by the UE and supporting the type of authentication capability of the UE S-CSCF.

In the above method, the step of saving the correspondence between the S-CSCF and the type of authentication capability supported by the S-CSCF includes: saving, in the form of a data table, the S-CSCF identifier and the supported template in the I-CSCF. Type of power.

In the above method, the method further includes: when the I-CSCF cannot obtain the UE that satisfies the registration request according to the correspondence between the S-CSCF and the type of the authentication capability supported by the S-CSCF and the S-CSCF capability set information. When the required service capability and the S-CSCF of the UE authentication capability type are supported, the I-CSCF returns a response message of the registration failure to the UE through the P-CSCF, or the I-CSCF randomly selects an S-CSCF, and then The S-CSCF sends a registration request and performs subsequent registration processing according to a normal procedure.

In the above method, if the S-CSCF arbitrarily selected by the I-CSCF satisfies the service capability requirement of the UE and matches the authentication capability type supported by the UE, the S-CSCF sends the UE to the UE through the I-CSCF and the P-CSCF. Returning the response information of the registration success; if the S-CSCF arbitrarily selected by the I-CSCF satisfies the service capability requirement of the UE and/or does not match the authentication capability type supported by the UE that initiated the registration request, the S-CSCF passes the I- The CSCF and the P-CSCF return response information of the registration failure to the UE.

In the above method, the response information of the registration failure further includes the sender information of the information and the reason for the failure, and the failure reason is that the S-CSCF whose matching capability type matches is not found.

In step b of the foregoing method, when the S-CSCF that satisfies the service capability required by the UE and supports the UE's authentication capability type is more than one, an S-CSCF is arbitrarily selected from the S-CSCF.

In summary, the technical solution of the present invention mainly includes: pre-setting and saving a correspondence between an S-CSCF and an authentication capability type supported by the S-CSCF; and after receiving the registration request of the UE, the I-CSCF acquires the S of the UE. -CSCF capability set information; then determine the support supported by the UE The capability type, and the S-CSCF that satisfies the service capability of the UE and supports the UE's authentication capability type according to the correspondence between the S-CSCF and the authentication capability type supported by the S-CSCF and the S-CSCF capability set information. Then, a registration request is sent to the acquired S-CSCF to continue the subsequent processing. Therefore, the authentication capability types supported by the UE and the S-CSCF are matched, and the authentication failure problem caused by the mismatch of the authentication capability types is avoided. In addition, the method of the present invention further includes providing a reason for the failure in the response message of the registration failure, thereby assisting the UE to perform the related operation. Since the present invention is less modified to the prior art solution, the existing configuration data method changes brought by the network size adjustment are minimized, so that the existing network has good compatibility. BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 shows the flow chart for user registration using the Early IMS authentication method. Mode for carrying out the invention

The invention will be further described in detail below with reference to the drawings and specific embodiments.

It is assumed in the present application that the types of authentication capabilities supported by the UE and the P-CSCF are mutually matched. For the case where the above two do not match, the current 3GPP protocol has described the processing method of the P-CSCF, that is, the above two The case of mismatch between the parties is not within the scope of the present invention.

In order to implement the technical solution of the present invention, the correspondence between the S-CSCF and the type of authentication capability supported by the S-CSCF needs to be set and saved in advance, and the corresponding relationship may be saved in the form of a data table in the I-CSCF. The S-CSCF identifier is implemented by the type of authentication capability it supports. The form of the data table can be as shown in Table 1 below: S-CSCF identifies the authentication capabilities supported by the S-CSCF

S-CSCF1 Early IMS

Full 3GPP IMS

S-CSCF2 . Early IMS

S-CSCF3 Full 3 GPP IMS

. . ' Table 1

The above S-CSCF data table for indicating the type of authentication capability supported by the S-CSCF is usually set in the I-CSCF.

Figure 1 shows the flow chart for user registration using the Early IMS authentication method. In this embodiment, the UE matches the authentication mode of the P-CSCF, and the UE initiates the registration request by using the SIP message. The process mainly includes the following steps:

Step 101: The UE initiates a new IMS registration request message. Because the P-CSCF that receives the user registration request message matches the authentication capability type supported by the UE that initiated the request, the P-CSCF can correctly forward the registration request of the UE. Message. The registration request message includes the identifier of the UE.

Step 102 103: The identifier of the P-CSCF in the UE determines its home domain, and determines the IP address of the entry point I-CSCF of the home domain by querying data in the Address Resolution Server (DNS).

Step 104: The P-CSCF forwards the registration request to the I-CSCF.

Steps 105 - 106, the I-CSCF sends a query location message to the HSS, where the query location message includes the identifier of the UE. Since the user is initially registered, the HSS finds the user subscription data of the UE according to the UE identifier in the query message, and obtains the S-CSCF capability set information according to the capability required by the subscription data, and then sets the S-CSCF capability set. Information returned to The I-CSCF, at the same time, if the authentication capability type data indicating the type of authentication capability supported by the UE is pre-configured according to the user subscription data in the HSS, the type of authentication capability indicating the type of authentication capability supported by the UE The data will be returned to the I-CSCF as part of the SC SCF capability set information.

Step 107: The I-CSCF selects, from the received S-CSCF capability set information, an S-CSCF set that can satisfy the service capability required by the UE and supports the UE's authentication capability type. The specific selection process is as follows:

If the information returned by the HSS to the I-CSCF includes the authentication capability type data indicating the type of the authentication capability supported by the UE, the I-CSCF determines, according to the authentication capability type data, the authentication supported by the UE that initiated the request. The capability type, according to the correspondence between the S-CSCF identifier in the set data table and the type of authentication capability supported by the S-CSCF, and the acquired S-CSCF capability set information, directly select a service that can meet the requirements of the UE. An S-CSCF set capable of supporting the UE's authentication capability type, the S-CSCF set may have one or more S-CSCFs, and if the S-CSCF set includes multiple S-CSCFs, the I-CSCF may be from the middle Pick an S-CSCF.

If the information returned by the HSS to the I-CSCF does not include the authentication capability type data indicating the type of authentication capability supported by the UE, the I-CSCF first selects from the S-CSCF capability set information returned by the HSS. The S-CSCF capability set that satisfies the UE service capability, and then determines the authentication capability type supported by the UE according to the registration request initiated by the UE, and then according to the S-CSCF identifier in the set data table and the supported profile thereof Corresponding relationship of the capability type, and the selected S-CSCF capability set capable of satisfying the UE service capability, selecting an S-CSCF set capable of satisfying the service capability required by the UE and supporting the UE's authentication capability type There may be one or more S-CSCFs in the S-CSCF set. If the S-CSCF set contains multiple S-CSCFs, the I-CSCF may select one S-CSCF from it.

The foregoing I-CSCF determines, according to the received registration request, the UE supported by the requesting request. The method of the authentication capability type is: determining, according to whether an authorization (Authorization) header field exists in the registration request, the type of authentication capability supported by the UE that initiated the request, that is, if the registration request includes an Authorization header field and the header field usage is consistent Currently, the 3GPP requires that the UE that initiates the request supports the Full IMS authentication capability type. If the registration request does not include the Authorization header field, the UE that initiated the request supports the Early IMS authentication mode.

Alternatively, the type of authentication capability supported by the UE that initiates the registration request may be determined according to a feature set by the operator that supports different types of authentication capabilities.

It is assumed that the UE that initiates the registration request in this embodiment only supports the Early IMS authentication capability type. According to the data in Table 1, only the S-CSCF1 and/or S may be included in the S-CSCF set selected by the I-CSCF. -CSCF2, but not S-CSCF3.

Step 108: The I-CSCF sends a registration request message to the selected S-CSCF.

Steps 109 ~ 110, the S-CSCF requests the authentication parameter from the HSS, and obtains the required parameters from the response information of the HSS.

Steps 111 to 112, the S-CSCF performs authentication according to the authentication parameters obtained by the HSS, and returns an authentication result to the HSS. It is assumed here that the S-CSCF adopts Early IMS authentication, and the specific authentication process is the same as the prior art, and will not be described in detail herein.

Steps 113 ~ 115, the S-CSCF returns a registration response message to the user. In this embodiment, it is assumed that the registration is successful, and the S-CSCF returns a registration success message to the UE through the P-CSCF.

The above embodiment is described by the registration process of the user who authenticates with Early IMS. For the 3G user who uses FULL 3GPP IMS authentication, the difference between the registration process and the existing registration process is that it is preset to represent S. - The S-CSCF data table of the authentication capability type supported by the CSCF, the data table containing the correspondence between the S-CSCF identifier and the type of authentication capability supported by it, and the S-CSCF capability received from the HSS at the I-CSCF After the information is collected, determining the type of authentication capability supported by the UE that initiated the request, and according to the correspondence between the identifier of the S-CSCF in the set data table and the type of authentication capability supported by the set, And obtaining the S-CSCF capability set information, selecting an S-CSCF set capable of satisfying the service capability required by the UE that initiates the registration request, and supporting the UE's authentication capability type, and then selecting an S-CSCF from the set, Follow the normal process to continue the subsequent registration process. The method of specifically selecting the S-CSCF set is exactly the same as the processing of the above step 107.

If the authentication capability type data supported by the UE is pre-configured in the HSS, but the I-CSCF cannot find the matching S-CSCF according to the S-CSCF capability set information returned by the HSS, that is, it cannot find the requirement that the UE can meet the requirements. The service capability and the S-CSCF set of the authentication capability type of the UE are supported. In this case, the I-CSCF can be processed as follows: The S-CSCF capability set information returned from the HSS is selected to meet the UE service capability. The S-CSCF capability set is determined according to the registration request initiated by the UE, and then the type of the authentication capability supported by the UE is determined, and then the correspondence between the S-CSCF identifier and the supported authentication capability type in the set data table is determined. And the selected S-CSCF capability set capable of satisfying the service capability of the user, and selecting an S-CSCF set capable of supporting the authentication capability type supported by the UE that initiates the registration request. That is, when the authentication capability type data supported by the UE is pre-configured in the HSS, but the I-CSCF cannot find the matching S-CSCF according to the S-CSCF capability set information returned by the HSS, the I-CSCF can The method is determined by a method for determining the type of authentication capability of the UE according to the registration request of the UE. Alternatively, you can follow the failure method described below.

Regardless of the UE that uses the Early IMS authentication mode or the UE of the Full 3GPP authentication mode, if an abnormal situation occurs, for example, the I-CSCF does not configure the above S-CSCF data table; or the I-CSCF determines the user's authentication capability. The type is matched with the pre-configured S-CSCF data table, and no related entries are found. Of course, the abnormal situation is not limited to this, and the I-CSCF cannot select the service that satisfies the UE from the acquired S-CSCF capability set. The capability requirements and/or the S-CSCF set that matches the type of authentication capability supported by the UE that initiated the registration request, the I-CSCF has the following two methods: Method 1: The I-CSCF returns a response message of registration failure to the UE through the P-CSCF. The initiator information and the reason for the failure may be included in the response message of the registration failure. The initiator information indicates that the failure response message is initiated by the I-CSCF, instead of the authentication failure at the P-CSCF; the failure reason indicates that the S-CSCF whose matching capability type matches is not found, for example, using 400 messages. , that is, Bad Request, indicates that the UE that initiated the request supports Early IMS, but the network side does not support the authentication method, that is, the network side only supports the FULL 3GPP IMS authentication method; and the 420 message, that is, the Bad Extension, indicates that the requesting UE is supported. Full 3GPP IMS, but the network side does not support the authentication method, that is, the network side only supports the Early IMS authentication method.

Method 2: The I-CSCF randomly selects an S-CSCF, sends a registration request to the selected S-CSCF, and continues the subsequent processing according to a normal procedure. At this point, there will be two more cases:

A. The S-CSCF selected by the I-CSCF matches the type of authentication capability supported by the UE that initiated the request. At this time, the S-CSCF returns to the authentication result after normal processing, that is, through the I-CSCF and the P-CSCF. The UE returns a response message indicating that the registration is successful. The reason for this may be that the data in the S-CSCF data table that is pre-configured to indicate the type of authentication capability supported by the S-CSCF is incorrect or imperfect.

B. The S-CSCF selected by the I-CSCF does not match the authentication capability type supported by the UE that initiated the request, and the S-CSCF returns the response information of the registration failure to the UE through the I-CSCF and the P-CSCF, and the registration fails. The response information may further include initiator information and the reason for the failure. The initiator information indicates that the failure response message is initiated by the S-CSCF, which can be distinguished from the failure response message initiated by the P-CSCF. In the failure reason, it is indicated that the S-CSCF whose matching capability type matches is not found, for example. The 400 message, that is, the Bad Request, indicates that the UE that initiated the request supports the Early IMS, and the S-CSCF only supports the Full 3GPP IMS. The 420 message, that is, the Bad Extension, indicates that the UE that initiated the request supports Full 3GPP IMS and the S-CSCF only Support for Early IMS. By giving the reason for the failure in the response message of the registration failure, the UE can be assisted to perform subsequent related operations.

The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalents, and improvements made within the spirit and scope of the present invention should be included in the present invention. Within the scope of protection.

Claims

Claim

A method for implementing registration in an Internet Protocol IP Multimedia Subsystem, characterized in that a correspondence between an S-CSCF and an authentication capability type supported by the S-CSCF is preset and saved, and the method includes the following steps:

The method according to claim 1, wherein in step b, the step of determining, by the I-CSCF, the type of authentication capability supported by the UE comprises:

The method according to claim 2, wherein, in the step b, the manner in which the I-CSCF determines the type of the authentication capability according to the registration request initiated by the UE includes:

The method according to claim 2, wherein in step b, the step of the I-CSCF acquiring the S-CSCF that satisfies the service capability required by the UE and supports the authentication capability type of the UE includes:

The I-CSCF determines whether the acquired S-CSCF capability set information includes the authentication capability type data required by the user set in advance, and if yes, the I-CSCF according to the S-CSCF and the type of authentication capability supported by the I-CSCF The corresponding relationship and the authentication capability type data in the acquired S-CSCF capability set information directly obtain an S-CSCF that satisfies the service capability required by the UE and supports the UE's authentication capability type; otherwise, the I-CSCF First, the S-CSCF capability set that satisfies the service capability of the UE is obtained from the obtained S-CSCF capability set information, and then the authentication capability type supported by the UE is determined according to the registration request initiated by the UE, and then the content is satisfied according to the The S-CSCF capability set of the UE's service capability, the determined authentication capability type, and the correspondence between the S-CSCF and the type of authentication capability supported by the UE, obtain the service capability that satisfies the UE and supports the authentication of the UE. The capability type of S-CSCF.

The method according to claim 4, wherein the step b further comprises: when the acquired S-CSCF capability set information includes the authentication capability type data required by the user, but the I-CSCF When the S-CSCF that satisfies the service capability required to initiate the UE and supports the UE's authentication capability type is not directly obtained according to the authentication capability type data, the I-CSCF obtains the obtained S-CSCF capability set information from the acquired information. Determining the type of the authentication capability supported by the UE according to the registration request initiated by the UE, and then determining the UE according to the obtained S-CSCF capability set that satisfies the service capability of the UE. Types of supported authentication capabilities and the S-CSCF and the authentication it supports The correspondence between the capability types is obtained by the S-CSCF that satisfies the service capability required by the UE and supports the UE's authentication capability type.

The method according to claim 1, wherein the step of saving the correspondence between the S-CSCF and the type of authentication capability supported by the S-CSCF comprises: correspondingly storing the data table in the I-CSCF The S-CSCF identifier and the type of authentication capability it supports.

The method according to claim 1, wherein the method further comprises: when the I-CSCF cannot according to the correspondence between the S-CSCF and the type of authentication capability supported by the I-CSCF and the S-CSCF When the capability set information acquires the S-CSCF that meets the service capability required by the UE that initiates the registration request and supports the UE authentication capability type, the I-CSCF returns the response information of the registration failure to the UE through the P-CSCF, or, the I-CSCF Optionally, an S-CSCF is selected, and then a registration request is sent to the S-CSCF, and subsequent registration processing is performed according to a normal procedure.

The method according to claim 7, wherein if the S-CSCF arbitrarily selected by the I-CSCF satisfies the service capability requirement of the UE and matches the authentication capability type supported by the UE, the S-CSCF passes The I-CSCF and the P-CSCF return the response information of the registration success to the UE; if the S-CSCF arbitrarily selected by the I-CSCF satisfies the service capability requirement of the UE and/or the type of authentication capability supported by the UE that initiates the registration request If there is no match, the S-CSCF returns the response information of the registration failure to the UE through the I-CSCF and the P-CSCF.

The method according to claim 7 or 8, wherein the response information of the registration failure further includes initiator information of the information and a reason for the failure, and the reason for the failure is that the authentication capability type is not found. Matching S-CSCF.

The method according to any one of claims 1 to 7, wherein, in step b, when the S-CSCF that satisfies the service capability required by the UE and supports the UE's authentication capability type is one In the above, an S-CSCF is arbitrarily selected from it.