CN1852289A - Method and system for restraining user mark beingness - Google Patents

Abstract

The invention discloses a method and system for HSS to restrict the existence of user identifications, wherein the method includes the following steps: setting in advance on the HSS a user identification existence constraint table for storing the corresponding relationship between the operation type and the number of user identifications; receiving After receiving the SAR message sent by the S-CSCF, the HSS judges whether the number of user IDs in the SAR message matches the number of user IDs corresponding to the operation type in the SAR message in the user ID existence constraint table, and if so Then perform corresponding operations according to the operation type in the SAR message, and return an SAA message to the S-CSCF; otherwise, return an SAA message indicating an error to the S-CSCF. The invention restricts the user identification in the SAR message at the HSS end, so that the HSS can correctly complete the corresponding operation, thereby making up for the shortcomings in the existing 3GPP related protocols.

Description

A method and system for constraining the existence of user identification

technical field

The invention relates to an IP-based multimedia subsystem (IMS), in particular to a method and a system for a home subscriber server (HSS) to restrict the existence of user identification.

Background technique

In the IMS domain, a piece of subscription data (IMS Subscription) contains a private user identity (IMS Private User Identity, IMPI), a public user identity (IMS Public User Identity, IMPU) and a mobile station International Integrated Services Digital Network (ISDN) number (MSISDN). FIG. 1 is a schematic diagram of the relationship between user identifiers in the IMS domain. In the IMS Subscription in Figure 1, there are two IMPIs: IMPI-1 and IMPI-2, and IMPI-1 is associated with IMPU-1 and IMPU-2, and IMPI-2 is associated with IMPU-2 and IMPU-3. In HSS IMPU-1 is associated with Service Profile-1, and IMPU-2 and IMPU-3 are associated with Service Profile-2. It should be noted that in the records saved by the HSS, the user's registration status is associated with a pair of IMPI-IMPU, that is, the HSS stores the association relationship between IMPI and IMPU and the user registration status corresponding to each IMPI-IMPU, while the HSS The subscription data of is only associated with the IMPU.

During the IMS user registration process, the user registration/deregistration request message (SAR) sent by the serving call session control function entity (S-CSCF) to the HSS through the interface (Cx interface) between the call session control function entity (CSCF) and the HSS , the SAR message carries a parameter operation type (ServerAssignmentType) and user identifiers IMPI and IMPU. When the value of the parameter ServerAssignmentType is different, the constraints on the existence and number of IMPI and IMPU are also different. The values of ServerAssignmentType and the corresponding meanings of various values are shown in Table 1. The HSS performs corresponding operations according to different values of ServerAssignmentType in the SAR message and returns an SAA message to the S-CSCF. The returned SAA message needs to carry the IMPI.

The corresponding operations performed by HSS according to ServerAssignmentType are as follows:

When the ServerAssignmentType is NO_ASSIGNMENT, the HSS returns the data to be read to the S-CSCF through the SAA message, without changing the registration status of the user. ServerAssignmentType value meaning NO_ASSIGNMENT fetch data REGISTRATION register RE_REGISTRATION re-register UNREGISTERED_USER User does called registration TIMEOUT_DEREGISTRATION timeout logout USER_DEREGISTRATION user logout TIMEOUT_DEREGISTRATION_STORE_SERVER_NAME Timeout logout and save server address USER_DEREGISTRATION_STORE_SERVER_NAME User logs out and saves server address ADMINISTRATIVE_DEREGISTRATION console logout AUTHENTICATION_FAILURE Authentication failed AUTHENTICATION_TIMEOUT Authentication timeout DEREGISTRATION_TOO_MUCH_DATA Too much data logout

Table 1 Values of ServerAssignmentType

When the ServerAssignmentType is REGISTRATION, the HSS changes the user registration status to Registered, and returns the SAA message to the S-CSCF;

When the ServerAssignmentType is RE_REGISTRATION, the HSS changes the user registration status to Registered, and returns the SAA message to the S-CSCF;

When the ServerAssignmentType is UNREGISTERED_USER, the HSS changes the user registration status to unregistered (Unregistered), and returns the requested service data to the S-CSCF through the SAA message;

When ServerAssignmentType is TIMEOUT_DEREGISTRATION, USER_DEREGISTRATION or ADMINISTRATIVE_DEREGISTRATION, HSS changes the user status to logout (Not Registered), and returns SAA message to S-CSCF;

When ServerAssignmentType is TIMEOUT_DEREGISTRATION_STORE_SERVER_NAME, USER_DEREGISTRATION_STORE_SERVER_NAME, HSS changes the user status to unregistered (Unregistered), saves the server address (Server Name), and returns SAA message to S-CSCF;

When rverAssignmentType is AUTHENTICATION_FAILURE or AUTHENTICATION_TIMEOUT, HSS will clear the user's authentication pending flag (Pending Flag), change the user status to logout (Not Registered), and return SAA message to S-CSCF;

When the ServerAssignmentType is DEREGISTRATION_TOO_MUCH_DATA, the HSS changes the user status to Not Registered, and returns the SAA message to the S-CSCF.

The existing 3rd Generation Partnership Project (3GPP) TS29.228v6.5.0 protocol roughly describes the number of IMPI and IMPU that the SAR message should carry when the ServerAssignmentType takes different values.

The 3GPP TS29.228v6.5.0 protocol stipulates that when the ServerAssignmentType parameter is TIMEOUT_DEREGISTRATION, USER_DEREGISTRATION or ADMINISTRATIVE_DEREGISTRATION, the SAR message can contain multiple IMPUs, and in other cases the SAR message can only contain one IMPU. In some cases of deregistration, the IMPU must be included when the IMPI is not included in the SAR message. When the S-CSCF can obtain the IMPI, it shall include the IMPI in the SAR message. The protocol specifically points out that when the ServerAssignmentType is equal to UNREGISTERED_USER, the SAR message may not include the IMPI. When the ServerAssignmentType is TIMEOUT_DEREGISTRATION, USER_DEREGISTRATION or ADMINISTRATIVE_DEREGISTRATION, the IMPI must be included when the IMPU is not included in the SAR message.

In the above solutions, the constraints on the existence of IMPI and IMPU in the SAR message are not clearly described. When the value of the parameter ServerAssignmentType in the SAR message is REGISTRATION or RE REGISTRATION, UNREGISTERED USER, NO_ASSIGNMENT, AUTHENTICATION_FAILURE, AUTHENTICATION_TIMEOUT, the above scheme stipulates the constraint on the existence of IMPU, that is, it can contain only one IMPU, but does not specify the IMPU The existence constraint only means that if the S-CSCF can obtain the IMPI, it must carry the IMPI in the SAR message, and the SAR message may not contain the IMPI when the value of ServerAssignmentType is UNREGISTERED_USER. When the value of the parameter ServerAssignmentType in the SAR message is TIMEOUT_DEREGISTRATION or USER_DEREGISTRATION, DEREGI-STRATION_TOO_MUCH_DATA, or ADMINISTRATIVE_DEREGISTRATION, the above scheme stipulates that if the SAR message does not contain IMPU, it must contain IMPI. However, there is no clear regulation on whether the IMPU must exist and how many exist. For the case where ServerAssignmentType is TIMEOUT_DEREGISTRATION_STORE_SERVER_NAME or USER_DEREGISTRATION_STORE_SERVER_NAME, the above solution does not impose any constraints on IMPI and IMPU.

Because there is no restriction on the existence of IMPI and IMPU in the SAR message, it brings difficulties for the HSS to process the SAR message. If the HSS cannot obtain the correct number of user IDs, it will not be able to perform further operations such as user status update requested by the S-CSCF through the SAR message.

Contents of the invention

In view of this, the present invention proposes a method and system for the HSS to restrict the existence of user IDs, so as to ensure that the HSS can obtain the correct number of user IDs for subsequent processing.

According to the above purpose, the present invention provides a method for the HSS to restrict the existence of user IDs. In this method, a user ID existence constraint table for storing the corresponding relationship between the operation type and the number of user IDs is set on the HSS in advance. The method also Further includes:

A. After receiving the SAR message sent by the S-CSCF, the HSS judges whether the number of user IDs in the SAR message matches the number of user IDs corresponding to the operation type in the SAR message in the user ID existence constraint table , if yes, go to step B, otherwise go to step C;

B. The HSS performs corresponding operations according to the operation type in the SAR message, and returns the SAA message to the S-CSCF to end this process;

C. The HSS returns an error SAA message to the S-CSCF.

When the user identification in the SAR message includes more than one private user identification IMPI, the step C is: the HSS returns an SAA message indicating too many parameters to the S-CSCF.

When the user ID in the SAR message does not include the IMPI and the public user ID IMPU, the step C is: the HSS returns an SAA message indicating that the user ID is missing to the S-CSCF.

Before step B, it further includes: when the user identifier in the SAR message includes multiple IMPUs, the HSS judges whether the multiple IMPUs are associated with the same IMPU according to the pre-saved association relationship between IMPIs and IMPUs, and if so, execute step B, Otherwise, return the SAA message indicating that the user IDs do not match to the S-CSCF.

Step B further includes the following steps: when the user identifier in the SAR message includes IMPI, the HSS packs the IMPI into the SAA message returned to the S-CSCF; when the user identifier in the SAR message does not include When IMPI, the HSS retrieves the IMPI associated with the IMPU according to the IMPU in the SAR message and the pre-saved relationship between the IMPU and the IMPU, and packs any one of the IMPIs into the SAA returned to the S-CSCF in the news.

The corresponding relationship between the operation type stored in the user identification existence constraint table and the user identification data is: fetching data NO_ASSIGNMENT, registering REGISTRATION, re-registering RE_REGISTRATION, authentication failure AUTHENTICATION_FAILURE, and authentication overtime AUTHENTICATION_TIMEOUT are respectively corresponding to an IMPU and an IMPI; When the user registers as called, UNREGISTERED_USER corresponds to the absence of an IMPU and IMPI, or an IMPU corresponds to an IMPI; timeout logout TIMEOUT_DEREGISTRATION, user logout USER_DEREGISTRATION, timeout logout and save server address TIMEOUTDEREGISTERED_STORE_SERVER_NAME, user logout and save server address USER_DEREGISTRATION_STORE_SERVER_NAME, console logout ADMINISTRATI Too much data cancellation DEREGISTRATION_TOO_MUCH_DATA corresponds to one IMPU and one IMPI, or multiple IMPUs and one IMPI, or missing IMPU and one IMPI.

The present invention also provides a system that can be used for HSS to restrict the existence of user identifiers. The system includes an interface unit, a constraint table unit, an existence checking unit, and a SAR message processing unit. The unit is connected with the SAR message processing unit for receiving the SAR message sent by the S-CSCF and forwarding the SAR message to the existence checking unit, and sending the existence checking unit and the SAR message processing unit to return the SAA to the S-CSCF Message: Constraint table unit, connected with the existence check unit, used to save the user identification existence constraint table of the corresponding relationship between the preset operation type and the number of user identifications, and provide the existence check unit with the user identification existence constraint Table; an existence checking unit, used to judge whether the number of user identifications in the SAR message matches the number of user identifications corresponding to the operation type in the SAR message in the user identification existence constraint table provided by the constraint table unit, And in the case of yes, the SAR message is forwarded to the SAR message processing unit, otherwise an SAA message indicating an error is returned to the S-CSCF through the interface unit; the SAR message processing unit is used to forward the SAR message from the existence checking unit The operation type in the message performs the corresponding operation, and returns the SAA message to the S-CSCF through the interface unit.

The system further includes a recording unit connected to the SAR message processing unit, used to pre-save the association relationship between IMPI and IMPU, and provide the association relationship to the SAR processing unit; the SAR message processing unit further includes an IMPI insertion module for Insert IMPI into the SAA message returned by the SAR message processing unit to the S-CSCF, when the user identifier in the SAR message includes IMPI, the IMPI insertion module packs the IMPI into the SAA message; when the When the user identifier in the SAR message does not include IMPI, the IMPI inserting module retrieves the IMPI associated with the IMPU according to the IMPU in the SAR message and the association relationship between the IMPI and the IMPU provided by the recording unit, and inserts the IMPI in the IMPI Either one is packaged into the SAA message.

The system further includes a recording unit and a matching checking unit, wherein the recording unit is connected to the matching checking unit for pre-saving the association relationship between the IMPI and the IMPU, and providing the matching relationship to the matching checking unit; the matching checking The unit is connected between the existence checking unit and the SAR message processing unit, and is also connected with the interface unit and the recording unit, and is used for the user identification in the SAR message that the existence checking unit forwards to the SAR message processing unit includes When there are multiple IMPUs, judge whether the IMPU in the SAR message is associated with the same IMPU according to the association relationship between the IMPI and the IMPU provided by the recording unit, if so, forward the SAR message to the SAR message processing unit, otherwise The interface unit returns to the S-CSCF an SAA message indicating that the user IDs do not match.

As can be seen from the above scheme, since the present invention pre-sets the user identification existence constraint table for storing the corresponding relationship between the operation type and the number of user identifications, after receiving the SAR message, judge the number of user identifications in the SAR message Whether it is consistent with the number of user identifications corresponding to the operation type in the SAR message in the user identification existence constraint table, if they match, perform the corresponding operation requested by the SAR message, otherwise return an SAA message indicating an error to the S-CSCF. The invention restricts the user identification in the SAR message at the HSS end, so that the HSS can complete corresponding operations according to the correct SAR message. The invention makes up for the shortcomings in the existing 3GPP related protocols, and has the advantage of convenient implementation.

Description of drawings

FIG. 1 is a schematic diagram of the relationship between user identifiers in the IMS domain;

Fig. 2 is a schematic flow sheet of the method according to the present invention;

Fig. 3 is a schematic structural diagram of the system according to the present invention.

Detailed ways

In order to make the purpose, technical solution and advantages of the present invention clearer, the following examples are given to further describe the present invention in detail.

The present invention pre-sets on the HSS a user identification existence constraint table for storing the corresponding relationship between the operation type and the number of user identifications, and after receiving the SAR message sent by the S-CSCF, the HSS judges the user identification in the SAR message Whether the number matches the number of user identifications corresponding to the operation type in the SAR message in the user identification existence constraint table, if yes, perform corresponding operations according to the operation type in the SAR message, and return the SAA message to the S-CSCF; Otherwise, an SAA message indicating an error is returned to the S-CSCF.

Referring to Fig. 2, the flow process of this embodiment includes the following steps:

Step 201, pre-setting the user identification existence constraint table in the HSS, the user identification existence constraint table saves the corresponding relationship between ServerAssignmentType and user identification IMPI, IMPU number, and the corresponding relationship specifies that IMPI and IMPU should be carried in the SAR message the rules. The principle is as follows:

1. When a user registers or re-registers, that is, when the ServerAssignmentType is REGISTRATION or RE_REGISTRATION, the IMPI and IMPU must be complete and associated. That is to say, at this time, the SAR message must carry both the IMPI and the IMPU, and the two must be associated.

2、用户注销时，即ServerAssignmentType为USER_DEREGISTRATION、USER_DEREGISTRATION_STORE_SERVER_NAME、TIMEOUT_DEREGISTRATION、TIMEOUT_DEREGISTRATION_STORE_SERVER_NAME、ADMINISTRATIVE_DEREGISTRATION或DEREGISTRATION_TOO_MUCH_DATA时，SAR消息可以单独携带IMPI，用以注销所有和该IMPI关联的IMPU；SAR消息也可以同时携带IMPI和与其关联One or more IMPUs in the SAR message are used to deregister the IMPUs in the SAR message; however, the SAR message cannot carry the IMPUs alone.

3. When the user authentication fails to log out, that is, when the ServerAssignmentType is AUTHENTICATION_FAILURE or AUTHENTICATION_TIMEOUT, the IMPI and IMPU in the SAR message must be complete and associated, that is, the user ID in the SAR message must include IMPI and IMPU, and the two must be associated.

4. When the user registers as a called party, that is, when the ServerAssignmentType is UNREGISTERED_USER, the SAR message can carry an IMPU alone. At this time, the HSS selects an IMPI associated with this IMPU for processing, and sets the status of the IMPI-IMPU as Unregistered. And send the selected IMPI in the SAA message; the SAR message can also carry the IMPI and IMPU at the same time, and the IMPI and IMPU must be associated.

5. When the user has registered to read relevant business data, that is, when the ServerAssignmentType is NO_ASSIGNMENT, the IMPI and IMPU in the SAR message must be complete and associated, that is, the user ID in the SAR message must include IMPI and IMPU, and the two must be associated .

6. In any case, if the SAR message carries an IMPI, the SAR message can only carry one IMPI. In other words, the user identifier in the SAR message can only contain no IMPI, or contain one IMPI.

According to the above principles, the user identification existence constraint table shown in Table 2 is set, which stores the corresponding relationship between ServerAssignmentType and the number of IMPI and IMPU when ServerAssignmentType takes different values. For example, when the value of ServerAssignmentType is REGISTRATION, it corresponds to an IMPI and an IMPU.

Of course, user identification existence constraint tables of other corresponding relationships can also be set according to other similar principles, which can be understood and realized by those skilled in the art.

Table 2 User ID Existence Constraint Table in SAR Message

According to the content in Table 2, the corresponding relationship between the operation type stored in the user identification existence constraint table and the user identification data is as follows: data fetch NO_ASSIGNMENT, registration REGISTRATION, re-registration RE_REGISTRATION, authentication failure AUTHENTICATION_FAILURE, authentication timeout AUTHENTICATION_TIMEOUT and an IMPU and Corresponding to one IMPI; the user is called to register UNREGISTERED_USER and an IMPU and IMPI are missing, or an IMPU and an IMPI correspond; timeout logout TIMEOUT_DEREGISTRATION, user logout USER_DEREGISTRATION, timeout logout and save server address TIMEOUTDEREGISTERATION_STORE_SERVER_NAME, user logout and save server address USER_DEREGISTRATION_STORE_SERVER_NAME, control Deregistration of ADMINISTRATIVE_DEREGISTRATION and deregistration of too much data DEREGISTRATION_TOO_MUCH_DATA correspond to one IMPU and one IMPI, or multiple IMPUs and one IMPI, or missing IMPUs and one IMPI.

Step 202: After receiving the SAR message sent by the S-CSCF, the HSS finds the corresponding number of user identifications in the user identification existence constraint table according to the value of ServerAssignmentType in the SAR message, and judges the user identification IMPI and Whether the number of IMPUs matches the found number of user identifications, if yes, go to step 203, otherwise go to step 204.

In step 203, the HSS performs corresponding operations according to the ServerAssignmentType in the SAR message, and returns the SAA message to the S-CSCF. The process in which the HSS operates according to the ServerAssignmentType in this step is the same as the process in which the HSS correctly processes the SAR message request operation in the prior art, and will not be repeated here.

The SAA message needs to carry the IMPI. When the SAR message carries the IMPI, the HSS packs the IMPI into the SAA message returned to the S-CSCF; when the SAR message does not carry the IMPI, the HSS according to The IMPU in the SAR message retrieves the associated IMPI from the record. If there is only one IMPI, the IMPI is packaged into the SAA message. If there are multiple IMPIs, one is selected and packaged into the SAA message. The records, that is, the records of the association relationship between IMPI and IMPU and the user registration status corresponding to each IMPI-IMPU are stored in the HSS described in the prior art.

Further, before performing the operation requested by the SAR message, if the user identifier in the SAR message contains multiple IMPUs, the HSS can also judge whether the IMPU in the SAR message is associated with the same IMPU according to the association relationship between the IMPI and the IMPU in the above record , if yes, perform the operation requested by the SAR message, otherwise return the SAA message carrying the error code DIAMETER_ERRORIDENTITIES_DONT_MATCH, the error code indicates that the user ID does not match.

In step 204, the HSS does not execute the operation requested by the SAR message, and returns an SAA message indicating an error to the S-CSCF.

For example: when the SAR message carries multiple IMPIs, the HSS returns the SAA message carrying the error code DIAMETER_AVP_OCCURS_TOO_MANY_TIMES to the S-CSCF, which indicates that there are too many parameters. When the SAR message does not carry the IMPI and IMPU, the HSS returns to the S-CSCF the SAA message carrying the error code DIAMETER_MISSING_USER_ID, which indicates that the user ID is missing.

Specifically, for example, when the ServerAssignmentType in the SAR message is REGISTRATION, and the user ID in it contains one IMPU and two IMPIs, and the number of user IDs corresponding to REGISTRATION in the user ID existence constraint table is one IMPU and one IMPI, then the HSS judges If the number of user IDs in the SAR message does not match the number of user IDs corresponding to REGISTRATION in the user ID existence constraint table, the HSS does not perform the operation requested by the SAR message, and returns an error SAA message to the S-CSCF. Since the user ID of the SAR message contains two IMPIs, the SAA message will carry the error code DIAMETER_AVP_OCCURS_TOO_MANY_TIMES.

Referring to FIG. 3 , the system for restricting the existence of user IDs according to the present invention includes an interface unit, a constraint table unit, a recording unit, an existence checking unit and a SAR message processing unit. Wherein, the interface unit is connected with the existence checking unit and the SAR message processing unit; the existence checking unit is connected with the interface unit, the constraint table unit and the SAR message processing unit; the recording unit is connected with the SAR message processing unit.

Wherein, the constraint table unit is preset with a user identifier presence constraint table for storing the corresponding relationship between the operation type and the user identifier IMPI and IMPU numbers, and the constraint table is used to provide the presence check unit with the user identifier presence constraint table . The association relationship between IMPI and IMPU, and the user registration status corresponding to each IMPI-IMPU are stored in the recording unit in advance, and the recording unit provides the user registration status to the SAR message processing unit as in the prior art. The interface unit is used to receive the SAR message from the S-CSCF and forward it to the existence checking unit, and the interface unit is also used to send the SAA message returned by the HSS to the SAR. The existence checking unit is used to determine whether the number of user identifications in the SAR message is consistent with the number of user identifications corresponding to the operation type in the SAR message in the user identification existence constraint table provided by the constraint table unit, and in the matching In the case, the SAR message is forwarded to the SAR message processing unit; otherwise, an SAA message indicating an error is returned to the S-CSCF through the interface unit. The SAR message processing unit is used to perform corresponding operations according to the ServerAssignmentType in the SAR message forwarded from the existence checking unit, and return the SAA message to the S-CSCF through the interface unit, and the operation process is the same as the HSS in the prior art to correctly process the SAR The process of the message request operation is the same and will not be repeated here.

As shown in Figure 3, the system can further include a matching checking unit connected between the existence checking unit and the SAR message processing unit, the matching checking unit is also connected with the interface unit and the recording unit, the matching checking unit When the user identifier in the SAR message forwarded by the existence checking unit to the SAR message processing unit includes multiple IMPUs, judge the multiple IMPUs in the SAR message according to the association relationship between the IMPI and the IMPUs pre-stored in the recording unit. Whether two IMPUs are associated with the same IMPI, if so, forward the SAR message to the SAR message processing unit, otherwise return the SAA message carrying the error code DIAMETER_ERROR_IDENTITIES_DONT_MATCH to the S-CSCF through the interface unit.

The SAR message processing unit may further include an IMPI inserting unit, configured to insert the user identifier IMPI into the SAA message generated by the SAR message processing unit. When the IMPI is carried in the SAR message, the IMPI insertion unit packs the IMPI into the SAA message returned to the S-CSCF; when the IMPI is not carried in the SAR message, the IMPI insertion unit according to the IMPU and The corresponding IMPI is retrieved from the association relationship between the IMPI and the IMPU provided by the recording unit. If there is only one IMPI, the IMPI is packaged into the SAA message. If there are multiple IMPIs, one is selected and packaged into the SAA message.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the scope of the present invention. within the scope of protection.

Claims (9)

1. A method for the home subscriber server HSS to restrict the existence of user identifications, characterized in that the method pre-sets on the HSS a user identification existence constraint table for storing the corresponding relationship between the operation type and the number of user identifications, the The method further includes: A. After receiving the user registration/deregistration request SAR message sent by the serving call session function entity S-CSCF, the HSS judges whether the number of user identifications in the SAR message corresponds to the number in the user identification existence constraint table The number of user identifications of the operation type in the SAR message matches, if so, perform step B, otherwise perform step C; B. The HSS performs corresponding operations according to the operation type in the SAR message, and returns the user registration/deregistration response SAA message to the S-CSCF, and ends this process; C. The HSS returns an error SAA message to the S-CSCF. 2. The method of claim 1, wherein: When the user identification in the SAR message includes more than one private user identification IMPI, the step C is: the HSS returns an SAA message indicating too many parameters to the S-CSCF. 3. The method of claim 1, wherein: When the user ID in the SAR message does not include the IMPI and the public user ID IMPU, the step C is: the HSS returns an SAA message indicating that the user ID is missing to the S-CSCF. 4. The method according to claim 1, further comprising: before step B, when the user identifier in the SAR message includes multiple IMPUs, the HSS judges the multiple Whether the IMPU is associated with the same IMPI, if yes, execute step B, otherwise return to the S-CSCF an SAA message indicating that the user IDs do not match. 5. The method according to claim 1, wherein step B further comprises the following steps: When the user identifier in the SAR message includes IMPI, the HSS packs the IMPI into the SAA message returned to the S-CSCF; When the user identifier in the SAR message does not include an IMPI, the HSS retrieves the IMPI associated with the IMPU according to the IMPU in the SAR message and the pre-saved association between the IMPI and the IMPU, and sends any one of the IMPI Packed into the SAA message returned to the S-CSCF. 6. The method according to claim 1, wherein the corresponding relationship between the operation type and user identification data stored in the user identification existence constraint table is as follows: Fetching data NO_ASSIGNMENT, registering REGISTRATION, re-registering RE_REGISTRATION, authentication failure AUTHENTICATION_FAILURE, authentication timeout AUTHENTICATION_TIMEOUT correspond to one IMPU and one IMPI respectively; The user registers as a called UNREGISTERED_USER corresponding to a missing IMPU and IMPI, or an IMPU and an IMPI; Timeout logout TIMEOUT_DEREGISTRATION, user logout USER_DEREGISTRATION, timeout logout and save server address TIMEOUT_DEREGISTRATION_STORE_SERVER_NAME, user logout and save server address USER_DEREGISTRATION_STORE_SERVER_NAME, console logout ADMINISTRATIVE_DEREGISTRATION, too much data logout DEREGISTRATION_TOO_MUCH_DATAIM with one or more IMPU and one IMPU Or a missing IMPU corresponds to an IMPI. 7. A system that can be used for HSS to restrict the existence of user identification, characterized in that the system includes an interface unit, a constraint table unit, an existence checking unit, and a SAR message processing unit, Wherein, the interface unit is respectively connected with the existence checking unit and the SAR message processing unit, and is used for receiving the SAR message sent by the S-CSCF and forwarding the SAR message to the existence checking unit, and sending the existence checking unit and The SAR message processing unit returns the SAA message to the S-CSCF; The constraint table unit is connected with the existence check unit, and is used to save the user identification existence constraint table of the preset operation type and the user identification number corresponding relationship, and provide the user identification existence constraint table to the existence check unit; an existence checking unit, configured to determine whether the number of user identifications in the SAR message matches the number of user identifications corresponding to the operation type in the SAR message in the user identification existence constraint table provided by the constraint table unit, and If yes, the SAR message is forwarded to the SAR message processing unit, otherwise, an SAA message indicating an error is returned to the S-CSCF through the interface unit; The SAR message processing unit is configured to perform corresponding operations according to the operation type in the SAR message forwarded from the existence checking unit, and return the SAA message to the S-CSCF through the interface unit. 8. The system according to claim 7, characterized in that the system further comprises a recording unit connected to the SAR message processing unit, used to pre-save the association relationship between IMPI and IMPU, and provide the association relationship to the SAR processing unit ; The SAR message processing unit further includes an IMPI insertion module, configured to insert an IMPI into the SAA message returned by the SAR message processing unit to the S-CSCF, and when the user identifier in the SAR message includes IMPI, the IMPI insertion module will The IMPI is packaged into the SAA message; when the user identifier in the SAR message does not include the IMPI, the IMPI insertion module retrieves the IMPI according to the IMPU in the SAR message and the association relationship between the IMPI and the IMPU provided by the recording unit. The IMPI associated with the IMPU, and pack any one of the IMPIs into the SAA message. 9. The system according to claim 7, characterized in that the system further comprises a recording unit and a matching checking unit, Wherein, the recording unit is connected with the matching checking unit, and is used to pre-save the association relationship between the IMPI and the IMPU, and provide the matching relationship to the matching checking unit; The matching checking unit is connected between the existence checking unit and the SAR message processing unit, and is also connected with the interface unit and the recording unit, and is used for the SAR message forwarded to the SAR message processing unit by the existence checking unit When the user identification includes multiple IMPUs, according to the association relationship between the IMPI and the IMPU provided by the recording unit, it is judged whether the IMPU in the SAR message is associated with the same IMPU, and if so, the SAR message is forwarded to the SAR message for processing unit, otherwise the interface unit returns an SAA message indicating that the user IDs do not match to the S-CSCF.

Images