CN102035800B - Third party registration failure processing method and device used for IMS (IP Multimedia Subsystem) - Google Patents

Abstract

The present invention provides a third-party registration failure processing method and device for IMS. The method includes: receiving a user status subscription request sent by a subscriber, and querying whether the third-party registration of the user fails; if the third-party registration of the user fails , a failure response is sent to the subscriber; the subscriber logs out the user according to the failure response. The present invention effectively guarantees the consistency of user data between devices, and realizes the synchronization of user data between devices, so it overcomes the third-party registration failure processing method in the related art, which makes the subscription session unable to be established due to the third-party registration failure of the user, so it cannot be notified The subscriber logs out the user, resulting in inconsistencies in user data between devices.

Description

Third-party registration failure processing method and device for IMS

technical field

The present invention relates to the communication field, in particular, to a third-party registration failure processing method and device for IMS (IP Multimedia Subsystem, IP Multimedia Subsystem).

Background technique

As a high-level component of the next-generation network, the IMS system establishes an open SIP (Session Initiation Protocol, Session Initiation Protocol)/IP-based and manageable and controllable platform to realize rich services. It is realized and provided by various application servers AS (Application Server). In the IMS communication network, if the user wants to use the multimedia service provided by the network, the PUI (Public UserIdentities, public user identity) associated with the user UE (User Equipment, user equipment) must be registered in the IMS core network and AS in advance, and The registration of PUI on AS is the third-party registration.

According to the description of the 3GPP 24.229 technical specification, the specific registration process for the PUI associated with the user UE to register on the IMS core network and the AS is shown in Figure 1, where P-CSCF (Proxy-Call Session Control Function, proxy call session control function) subscribes The process is steps 112a-112h, and the UE subscription process is steps 113a-113h, which are two independent service processing processes. There is no strict sequence relationship between the two processing processes, and they can be processed in parallel. In order to make the signaling process clearer, here Draw the two processes separately, including the following steps:

Step 101, the UE initiates network registration, and sends a REGISTER (registration) request to the P-CSCF;

Step 102, P-CSCF forwards the REGISTER request to I-CSCF (Interrogating-CSCF, query call session control function);

Step 103, the I-CSCF sends a UAR (User Authorization Request, user authorization request) request to the HSS (Home Subscriber Server, home subscription server) to query the user status;

Step 104, the HSS returns the user status query result to the I-CSCF through a UAA (UserAuthorization Answer) message;

Step 105, I-CSCF forwards the registration REGISTER request to S-CSCF (Serving-CSCF, serving call session control function);

Step 106, the S-CSCF sends a SAR (Server Assignment Request, server assignment request) request to the HSS to notify the user to register, and download the user's subscription data;

Step 107, HSS returns SAA (Server Assignment Answer, server assignment answer), and downloads user subscription data to S-CSCF;

Step 108, the registration is completed, and the S-CSCF returns a 200 OK response for registration;

Step 109a, S-CSCF triggers third-party registration according to user subscription data, and sends REGISTER (the third-party, third-party) message to AS;

Step 109b, AS returns 200OK for third-party registration;

Step 110, the I-CSCF forwards the 200 OK response in step 108 to the P-CSCF;

Step 111, the P-CSCF forwards the 200 OK response in step 110 to the UE;

Step 112a, P-CSCF initiates user registration status subscription, and sends a SUBSCRIBE (subscription) request to I-CSCF;

Step 112b, the I-CSCF sends a UAR request to the HSS to query the user status;

Step 112c, the HSS returns the user status query result to the I-CSCF through the UAA;

Step 112d, I-CSCF forwards SUBSCRIBE subscription request to S-CSCF;

Step 112e, the S-CSCF accepts the subscription and returns a 200OK response;

Step 112f, I-CSCF forwards 200 OK response to P-CSCF;

Step 112g, the S-CSCF sends a NOTIFY notification request. Since the subscription has been established, the S-CSCF directly sends a NOTIFY to the P-CSCF to notify the P-CSCF of the registration status of the user;

In step 112h, the P-CSCF returns a 200 OK response to the NOTIFY notification request to the S-CSCF, and the P-CSCF subscription process ends;

Step 113a, the UE initiates user registration status subscription, and sends a SUBSCRIBE subscription request to the P-CSCF;

Step 113b, P-CSCF forwards UE's SUBSCRIBE subscription request to S-CSCF;

Step 113c, the S-CSCF accepts the subscription and returns a 200OK response;

Step 113d, P-CSCF forwards 200 OK response to UE;

Step 113e, the S-CSCF sends a NOTIFY notification request to notify the UE of the registration status of the user;

Step 113f, the P-CSCF forwards the NOTIFY notification request to the UE;

Step 113g, the UE returns a 200OK response to the NOTIFY notification request;

In step 113h, the P-CSCF forwards a 200 OK response to the S-CSCF, and the UE subscription procedure ends.

In the above process, the user UE initiates initial network registration with the associated PUI, and the registration is successful (corresponding to steps 101-107), and the S-CSCF returns a 200 OK response to the registration success (corresponding to steps 108, 110-111), P- After receiving the 200OK response, the CSCF and the UE respectively initiate a subscription to the registration status of the PUI (corresponding to steps 112a~112d and steps 113a~113b respectively). According to the subscription, the S-CSCF will also notify the subscriber of the registration status of the PUI at any time. State change (corresponding to step 112g and steps 113e-113f, respectively). According to the service trigger rule subscribed by the user PUI, if the registration is successful, the S-CSCF will also send a third-party registration request to each AS matching the third-party registration trigger condition (corresponding to step 109a). Normally, after receiving the REGISTER request sent by the S-CSCF, the AS returns a 200 OK success response (corresponding to step 109b). So far, the registration of the user UE in the network is completed, and the resources and services provided by the network can be used normally.

However, after receiving the third-party REGISTER request, the AS may immediately return a 5xx failure response message due to some reasons that the service cannot be provided, that is, a third-party registration failure occurs.

The related technology provides a third-party registration failure processing method for IMS. This method follows the 3GPP 24.229 technical specification. When the S-CSCF receives the 5xx response returned by the AS, there are two default processing methods according to the PUI contract. : "SESSION_CONTINUED": S-CSCF will no longer do any processing, and the user's registration in the core network still exists; "SESSION_TERMINATED": S-CSCF will cancel the previous registration of the PUI in the core network. In order to provide users with excellent service and satisfactory user experience, the PUI contract more often adopts the "SESSION_TERMINATED" method. In this method, after the S-CSCF receives a 5xx response, according to the description of the 24.229 technical specification, the S-CSCF will Execute the network deregistration process. Before the deregistration, the PUI is registered in the core network. Under normal circumstances, when the S-CSCF executes the network deregistration process, the UE and P-CSCF subscriptions have been successfully completed, so that the S-CSCF can normally notify the UE and P-CSCF. The CSCF deletes the user registration data on it.

The inventors found that in the third-party registration failure processing method in the related art, when the S-CSCF receives a 5xx response and executes the network deregistration process, it is likely that the network unit processes the message and there is a delay in network transmission, resulting in the following two situations: exception:

1. When the UE or P-CSCF’s subscription request SUBSCRIBE reaches the I-CSCF, and the I-CSCF initiates a LIR (Location Info Request, location information request) query, the HSS has received the SAR deregistration request sent by the S-CSCF, that is, the user is in The HSS is already in the unregistered state, and the HSS returns a user unregistered response to the I-CSCF, resulting in subscription failure;

2. When the UE or P-CSCF's subscription request SUBSCRIBE reaches the S-CSCF, the S-CSCF has deleted the user data on it according to the 5xx response received from the AS before. Since there is no user registration information, the S-CSCF CSCF refuses to subscribe, resulting in subscription failure;

The first abnormal situation above is that the SUBSCRIBE subscription request does not reach the S-CSCF, and the second abnormal situation above is that the time for the SUBSCRIBE subscription request to reach the S-CSCF lags behind the time for the 5xx response returned by the AS to reach the S-CSCF. In both cases, the subscription session cannot be established, so the subscriber cannot be notified to log out the user, resulting in inconsistency of user data between devices.

Contents of the invention

The purpose of the present invention is to provide a third-party registration failure processing method and device for IMS, which can solve the problem that the third-party registration failure processing method in the related art cannot notify the subscriber to logout due to the failure of the third-party registration of the user to make the subscription session unable to be established. users, resulting in inconsistencies in user data between devices.

In order to achieve the above object, according to one aspect of the present invention, a third-party registration failure processing method for IMS is provided, including the following steps: receiving the user status subscription request sent by the subscriber, and querying whether the third-party registration of the user fails ; If the user's third-party registration fails, send a failure response to the subscriber; the subscriber logs out the user according to the failure response.

Preferably, in the above method, receiving the user state subscription request sent by the subscriber, and inquiring whether the user's third-party registration fails specifically includes: I-CSCF receiving the user state subscription request sent by the P-CSCF; I-CSCF sending the HSS Send the user's user status query request.

Preferably, in the above method, if the user's third-party registration fails, sending a failure response to the subscriber specifically includes: if the query result shows that the user is not registered, then the I-CSCF sends a no failure response to the P-CSCF.

Preferably, in the above method, the subscriber canceling the user according to the failure response specifically includes: the P-CSCF receives no failure response; the P-CSCF deletes the registration information of the user.

Preferably, in the above method, receiving the user status subscription request sent by the subscriber, and inquiring whether the user's third-party registration fails specifically includes: S-CSCF receiving the user status subscription request sent by the UE; S-CSCF inquiring whether there is a user status subscription request. user data.

Preferably, in the above method, if the user's third-party registration fails, sending a failure response to the subscriber specifically includes: if the user data does not exist, the S-CSCF sends a failure response not found to the UE.

Preferably, in the above method, the subscriber deregistering the user according to the failure response specifically includes: the UE receiving the failure response not found; the UE setting the user status of the user as unregistered.

In order to achieve the above object, according to another aspect of the present invention, a third-party registration failure processing device for IMS is also provided, including: a query module, configured to receive the user status subscription request sent by the subscriber, and query the user's Whether the third-party registration fails; the response module is used to send a failure response to the subscriber if the user's third-party registration fails; the logout module is used for the subscriber to log out the user according to the failure response.

Preferably, in the above device, the response module specifically includes: a first response unit, configured to send a non-discovery failure response from the I-CSCF to the P-CSCF when the query result is that the user is not registered.

Preferably, in the above device, the deregistration module specifically includes: a first receiving unit, configured for the P-CSCF to receive a no failure response; a first deregistration unit, configured for the P-CSCF to delete the registration information of the user.

Preferably, in the above device, the response module specifically includes: a second response unit, configured to send the S-CSCF a no failure response to the UE when the user data does not exist.

Preferably, in the above device, the deregistration module specifically includes: a second receiving unit, configured for the UE to receive a non-discovery failure response; a second deregistration unit, configured for the UE to set the user status of the user as unregistered.

In the above embodiment, after receiving the subscription request from the subscriber, it is inquired whether the third-party registration of the user corresponding to the request fails, and if it fails, the subscriber is notified to log out the user through a failure response. Since the failure response does not need to be initiated depending on the pre-established subscription relationship, no matter whether the subscription relationship has been established when the S-CSCF performs network logout for the third-party registration failure, the subscriber can be notified by sending a failure response to the third party of the user The registration failure makes the subscriber complete the logout of the user, thereby effectively ensuring the consistency of user data between devices and realizing the synchronization of user data between devices, so it overcomes the third-party registration failure processing method in the related technology. If the registration fails, the subscription session cannot be established, so the subscriber cannot be notified to log out the user, resulting in inconsistency of user data between devices.

Description of drawings

The accompanying drawings described here are used to provide a further understanding of the present invention and constitute a part of the application. The schematic embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations to the present invention. In the attached picture:

FIG. 1 shows a flow chart of UE performing initial registration and subscription;

Fig. 2 shows the flowchart of the processing method according to the first embodiment of the present invention;

Fig. 3 shows the flowchart of the processing method according to the second embodiment of the present invention;

Fig. 4 shows a structural diagram of a processing device according to a third embodiment of the present invention.

Detailed ways

The present invention will be described in detail below with reference to the accompanying drawings and in combination with embodiments.

Fig. 2 shows the flowchart of the processing method according to the first embodiment of the present invention, and this method comprises the following steps:

Step 201, receiving the user status subscription request SUBSCRIBE sent by the subscriber, and querying whether the third-party registration of the user fails;

Step 202, if the user's third-party registration fails, send a failure response to the subscriber;

Step 203, the subscriber logs out the user according to the failure response.

After receiving the subscription request from the subscriber, this embodiment inquires whether the third-party registration of the user corresponding to the request fails. If it fails, the subscriber is notified to logout the user through a failure response. Since the failure response does not need to be initiated depending on the pre-established subscription relationship, no matter whether the subscription relationship has been established when the S-CSCF performs network logout for the third-party registration failure, the subscriber can be notified by sending a failure response to the third party of the user The registration failure allows the subscriber to complete the logout of the user, thereby effectively ensuring the consistency of user data between devices, so it overcomes the failure of the third-party registration in the related technology, which makes the subscription session unable to be established due to the failure of the third-party registration of the user. Therefore, the subscriber cannot be notified to log out the user, resulting in inconsistency of user data between devices. The application scenario of this embodiment is that the UE initiates network initial registration with the associated PUI, and the AS returns a 5xx response, and the default processing method of the PUI subscription is "SESSION_TERMINATED"; as for other scenarios, that is, the AS returns a successful response to the third-party registration request, not a 5xx For situations such as failure response and response timeout, the S-CSCF handles it according to the description in the protocol specification.

Preferably, in the above method, step 101 specifically includes: the I-CSCF receives the user status subscription request SUBSCRIBE sent by the P-CSCF; the I-CSCF sends the user status query request of the user to the HSS.

This embodiment is the case where the P-CSCF initiates a user registration state subscription request (that is, the subscriber is the P-CSCF). The subscription request SUBSCRIBE initiated by the P-CSCF first reaches the I-CSCF, and the I-CSCF queries the user status of the user on the HSS by sending a query request. If the third-party registration of the user initiated by the S-CSCF fails, the AS will return a 5xx response to the S-CSCF, and the S-CSCF will delete the user data on it, and at the same time notify the HSS to log out the user through the SAR logout request, and the HSS receives The SAR logout request will set the user's status as unregistered, so the user status of the user on the HSS reflects the completion of the user's third-party registration. This embodiment makes full use of the process in which the I-CSCF sends a UAR request to the HSS after receiving the SUBSCRIBE and the HSS returns the user status query result to realize the query of the success or failure of the user's third-party registration.

Preferably, in the above method, step 102 specifically includes: if the result of the query is that the user is not registered, the I-CSCF sends a non-discovery failure response to the P-CSCF.

In this embodiment, the P-CSCF initiates a user registration status subscription request (that is, the subscriber is the P-CSCF), and the third-party registration of the user fails. If the result returned by HSS is that the user is not registered, it means that the third-party registration of the user failed. At this time, the I-CSCF constructs a 404Not Found (404 not found) failure response and returns it to the P-CSCF. The 404NotFound failure response is used to indicate The subscriber (P-CSCF in this embodiment) deletes the user data on it. This solves the problem that the S-CSCF cannot notify the P-CSCF to delete the user data on it due to the first situation in the background technology (that is, the SUBSCRIBE subscription request cannot reach the S-CSCF).

Preferably, in the above method, step 103 specifically includes: the P-CSCF receives a no failure response; and the P-CSCF deletes the registration information of the user.

In this embodiment, the P-CSCF initiates a user registration status subscription request (that is, the subscriber is the P-CSCF), and the third-party registration of the user fails. If the S-CSCF deletes the user registration data on it before the P-CSCF subscription is completed, and notifies the HSS to set the user as unregistered, then when the P-CSCF's SUBSCRIBE subscription request for the PUI user arrives at the I- When the CSCF is used, the I-CSCF returns a 404 Not Found failure response to the P-CSCF, and the P-CSCF deletes the user registration data after receiving the 404 Not Found failure response, realizing data synchronization between the S-CSCF and the P-CSCF. In this way, the S-CSCF cannot notify the P-CSCF due to the first situation in the background technology (that is, the SUBSCRIBE subscription request cannot reach the S-CSCF), and the P-CSCF cannot delete the user data on it, resulting in S-CSCF The user data on the CSCF and the P-CSCF are inconsistent, and there is a problem of garbage data on the P-CSCF.

Preferably, in the above method, step 101 specifically includes: the S-CSCF receives the user status subscription request sent by the UE; the S-CSCF inquires whether there is user data of the user.

In this embodiment, the UE initiates a user registration status subscription request (that is, the subscriber is the UE). The subscription request SUBSCRIBE initiated by the UE first arrives at the P-CSCF, and the P-CSCF forwards the SUBSCRIBE subscription request to the S-CSCF. The S-CSCF can know the third party of the user by checking whether it has saved the user data of the user. Whether the registration failed. If the third-party registration of the user initiated by the S-CSCF fails, the AS will return a 5xx response to the S-CSCF, and the S-CSCF will delete the user data on it, so whether there is user data on the S-CSCF reflects the The completion of the user's third-party registration. This embodiment makes full use of the process of the S-CSCF deleting user data after the third-party registration fails, and realizes the query of the success or failure of the user's third-party registration.

Preferably, in the above method, step 102 specifically includes: if the user data does not exist, then the S-CSCF sends a no-discovery failure response to the UE.

In this embodiment, the UE initiates a user registration status subscription request (that is, the subscriber is the UE), and the third-party registration of the user fails. If the S-CSCF query obtains that the user data does not exist, it means that the third-party registration of the user has failed. At this time, the S-CSCF constructs a 404NotFound failure response and returns it to the UE. The 404Not Found failure response is used to indicate the subscriber (this embodiment) In the case of UE), the user is deregistered, that is, the user status is set as unregistered. In this way, the second situation in the background technology (that is, the time when the SUBSCRIBE subscription request arrives at the S-CSCF lags behind the time when the 5xx response returned by the AS arrives at the S-CSCF) causes the S-CSCF to be unable to notify the UE to log off by means of the subscription relationship The user's question.

Preferably, in the above method, step 103 specifically includes: the UE receives a no-discovery failure response; and the UE sets the user status of the user as unregistered.

In this embodiment, the UE initiates a user registration status subscription request (that is, the subscriber is the UE), and the third-party registration of the user fails. If the S-CSCF deletes the user registration data on the P-CSCF before the P-CSCF subscription is completed, when the UE's SUBSCRIBE subscription request for the PUI user reaches the S-CSCF, the S-CSCF returns a 404NotFound failure response to the UE, and the UE After receiving the 404 Not Found failure response, the user status of the user is set as unregistered, and the data synchronization between the S-CSCF and the UE is realized. In this way, the second situation in the background technology (that is, the time when the SUBSCRIBE subscription request arrives at the S-CSCF lags behind the time when the 5xx response returned by the AS arrives at the S-CSCF) causes the S-CSCF to fail to notify the UE, and the UE cannot timely The user is logged out, resulting in the inconsistency between the user data on the S-CSCF and the UE, and the UE cannot log out the user in time.

Fig. 3 shows the flowchart of the processing method according to the second embodiment of the present invention, and this method comprises the following steps:

Step 301, the UE initiates network registration and sends a REGISTER request to the P-CSCF;

Step 302, the P-CSCF forwards the REGISTER request to the I-CSCF;

Step 303, the I-CSCF sends a UAR request to the HSS to query the user status;

Step 304, the HSS returns the user status query result to the I-CSCF through the UAA message;

Step 305, the I-CSCF forwards the REGISTER request to the S-CSCF;

Step 306, the S-CSCF sends a SAR request to the HSS to notify the user of registration, and download the user subscription data;

Step 307, the HSS returns the SAA, and downloads the user subscription data to the S-CSCF;

Step 308, the registration is completed, and the S-CSCF returns a 200 OK response for registration;

Step 309a, S-CSCF triggers third-party registration according to user subscription data, and sends REGISTER (the third-party) message to AS;

Step 309b, the AS returns a 5xx response to the third-party registration request, the S-CSCF deletes the user data on it after receiving the 5xx response returned by the AS, and notifies the HSS to cancel the user, and the HSS sets the user as unregistered according to the notification ;

Step 310, the I-CSCF forwards the 200 OK response in step 308 to the P-CSCF;

Step 311, the P-CSCF forwards the 200 OK response in step 310 to the UE;

Step 312a, P-CSCF initiates user registration status subscription, and sends SUBSCRIBE request to I-CSCF;

Step 312b, the I-CSCF sends a UAR request to the HSS to query the user status;

Step 312c, the HSS returns to the I-CSCF through the UAA that the user is not registered;

Step 312d, the I-CSCF constructs a 404Not Found failure response and returns it to the P-CSCF, and the P-CSCF deletes the registration data corresponding to the user after receiving the 404Not Found response;

Step 313a, the UE initiates user registration status subscription, and sends a SUBSCRIBE subscription request to the P-CSCF;

Step 313b, P-CSCF forwards UE's SUBSCRIBE subscription request to S-CSCF;

Step 313c: After receiving the SUBSCRIBE request, the S-CSCF checks that the user data does not exist, constructs and returns a 404 Not Found failure response to the P-CSCF;

In step 313d, the P-CSCF forwards the 404 Not Found failure response to the UE, and the UE sets the user status as unregistered after receiving the 404 Not Found response.

Steps 312a to 312d in this embodiment solve the problem of the first situation in the background technology (that is, the SUBSCRIBE subscription request cannot reach the S-CSCF), which causes the S-CSCF to fail to notify the P-CSCF, and the P-CSCF cannot delete its users data, thereby causing the user data on the S-CSCF and the P-CSCF to be inconsistent, and there is a problem of garbage data on the P-CSCF; steps 313a to 313d solve the problem caused by the second case in the background technology (that is, the SUBSCRIBE subscription request reaches the S-CSCF The time lags behind the time when the 5xx response returned by the AS arrives at the S-CSCF), so that the S-CSCF cannot notify the UE, resulting in the inconsistency between the user data on the S-CSCF and the UE, and the UE cannot log out the user in time. Therefore, in this embodiment, regardless of whether the subscription relationship has been established when the S-CSCF executes network cancellation for the third-party registration failure, the subscriber can be notified by sending a failure response that the third-party registration of the user failed, so that the subscriber completes the registration of the user. Logout, thus effectively ensuring the consistency of user data between devices and realizing the synchronization of user data between devices.

FIG. 4 shows a structural diagram of a processing device according to a third embodiment of the present invention, the device comprising:

The query module 401 is configured to receive the user status subscription request sent by the subscriber, and query whether the third-party registration of the user fails;

A response module 402, configured to send a failure response to the subscriber if the user's third-party registration fails;

A logout module 403, configured for the subscriber to log out the user according to the failure response.

In this embodiment, first, the query module 401 is used to receive the subscription request of the subscriber, and to query whether the third-party registration of the user corresponding to the request fails. If it fails, the response module 402 is used to send a failure response to notify the subscriber to log off the user. The logout module 403 logs out the user. Since the failure response does not need to be initiated depending on the pre-established subscription relationship, no matter whether the subscription relationship has been established when the S-CSCF performs network logout for the third-party registration failure, the subscriber can be notified by sending a failure response to the third party of the user The registration failure allows the subscriber to complete the logout of the user, thereby effectively ensuring the consistency of user data between devices, so it overcomes the failure of the third-party registration in the related technology, which makes the subscription session unable to be established due to the failure of the third-party registration of the user. Therefore, the subscriber cannot be notified to log out the user, resulting in inconsistency of user data between devices. The application scenario of this embodiment is that the UE initiates network initial registration with the associated PUI, and the AS returns a 5xx response, and the default processing method of the PUI subscription is "SESSION_TERMINATED"; as for other scenarios, that is, the AS returns a successful response to the third-party registration request, not a 5xx For situations such as failure response and response timeout, the S-CSCF handles it according to the description in the protocol specification.

Preferably, in the above device, the response module 402 specifically includes: a first response unit, configured to send a non-discovery failure response from the I-CSCF to the P-CSCF when the query result is that the user is not registered.

In this embodiment, the P-CSCF initiates a user registration status subscription request (that is, the subscriber is the P-CSCF), and the third-party registration of the user fails. If the result returned by the HSS is that the user is not registered, it means that the third-party registration of the user failed. At this time, the I-CSCF constructs a 404Not Found failure response and returns it to the P-CSCF. The 404Not Found failure response is used to indicate the subscriber (this In the embodiment, it is P-CSCF) to delete the user data on it. This solves the problem that the S-CSCF cannot notify the P-CSCF to delete the user data on it due to the first situation in the background technology (that is, the SUBSCRIBE subscription request cannot reach the S-CSCF).

Preferably, in the above-mentioned device, the deregistration module 403 specifically includes: a first receiving unit, configured for the P-CSCF to receive no failure response; a first deregistration unit, configured for the P-CSCF to delete the registration information of the user.

In this embodiment, the P-CSCF initiates a user registration status subscription request (that is, the subscriber is the P-CSCF), and the third-party registration of the user fails. If the S-CSCF deletes the user registration data on it before the P-CSCF subscription is completed, and notifies the HSS to set the user as unregistered, then when the P-CSCF's SUBSCRIBE subscription request for the PUI user arrives at the I- When the CSCF is used, the I-CSCF returns a 404 Not Found failure response to the P-CSCF, and the P-CSCF deletes the user registration data after receiving the 404 Not Found failure response, realizing data synchronization between the S-CSCF and the P-CSCF. In this way, the S-CSCF cannot notify the P-CSCF due to the first situation in the background technology (that is, the SUBSCRIBE subscription request cannot reach the S-CSCF), and the P-CSCF cannot delete the user data on it, resulting in S-CSCF The user data on the CSCF and the P-CSCF are inconsistent, and there is a problem of garbage data on the P-CSCF.

Preferably, in the above-mentioned apparatus, the response module 402 specifically includes: a second response unit, configured to send the S-CSCF a failure-not-discovery response to the UE when the user data does not exist.

In this embodiment, the UE initiates a user registration status subscription request (that is, the subscriber is the UE), and the third-party registration of the user fails. If the S-CSCF query obtains that the user data does not exist, it means that the third-party registration of the user has failed. At this time, the S-CSCF constructs a 404NotFound failure response and returns it to the UE. The 404Not Found failure response is used to indicate the subscriber (this embodiment) In the case of UE), the user is deregistered, that is, the user status is set as unregistered. In this way, the second situation in the background technology (that is, the time when the SUBSCRIBE subscription request arrives at the S-CSCF lags behind the time when the 5xx response returned by the AS arrives at the S-CSCF) causes the S-CSCF to be unable to notify the UE to log off by means of the subscription relationship The user's question.

Preferably, in the above device, the deregistration module 403 specifically includes: a second receiving unit, configured for the UE to receive a non-discovery failure response; a second deregistration unit, configured for the UE to set the user status of the user as unregistered.

In this embodiment, the UE initiates a user registration status subscription request (that is, the subscriber is the UE), and the third-party registration of the user fails. If the S-CSCF deletes the user registration data on the P-CSCF before the P-CSCF subscription is completed, when the UE's SUBSCRIBE subscription request for the PUI user reaches the S-CSCF, the S-CSCF returns a 404NotFound failure response to the UE, and the UE After receiving the 404 Not Found failure response, the user status of the user is set as unregistered, and the data synchronization between the S-CSCF and the UE is realized. In this way, the second situation in the background technology (that is, the time when the SUBSCRIBE subscription request arrives at the S-CSCF lags behind the time when the 5xx response returned by the AS arrives at the S-CSCF) causes the S-CSCF to fail to notify the UE, and the UE cannot timely The user is logged out, resulting in the inconsistency between the user data on the S-CSCF and the UE, and the UE cannot log out the user in time.

From the above description, it can be seen that in the above embodiments of the present invention, no matter whether the subscription relationship has been established when the S-CSCF executes the network logout for the third party registration failure, it can send a failure response to notify the subscriber of the user's first The failure of the three-party registration allows the subscriber to complete the logout of the user, thereby effectively ensuring the consistency of user data between devices and realizing the synchronization of user data between devices.

Obviously, those skilled in the art should understand that each module or each step of the above-mentioned present invention can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network formed by multiple computing devices Optionally, they can be implemented with program codes executable by a computing device, so that they can be stored in a storage device and executed by a computing device, or they can be made into individual integrated circuit modules, or they can be integrated into Multiple modules or steps are fabricated into a single integrated circuit module to realize. As such, the present invention is not limited to any specific combination of hardware and software.

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

Claims (12)

1. A third-party registration failure processing method for IMS, comprising the following steps: Receive the user status subscription request sent by the subscriber, and query whether the third-party registration of the user fails; If the user's third-party registration fails, send a failure response to the subscriber, wherein the failure response does not need to be initiated depending on the previously established subscription relationship; The subscriber logs out the user according to the failure response. 2. The method according to claim 1, wherein receiving the user status subscription request sent by the subscriber, and inquiring whether the user's third-party registration fails specifically includes: The query call session control function network element receives the user status subscription request sent by the proxy call session control function network element; The query call session control function network element sends the user status query request of the user to the home subscription server. 3. The method according to claim 2, wherein if the third-party registration of the user fails, sending a failure response to the subscriber specifically includes: If the query result is that the user is not registered, the querying-CSCF network element sends a no failure response to the proxy-CSCF network element. 4. The method according to claim 3, wherein the subscriber canceling the user according to the failure response specifically comprises: The PCSCF network element receives the no failure response; The proxy-CSCF network element deletes the registration information of the user. 5. The method according to claim 1, wherein receiving the user status subscription request sent by the subscriber, and inquiring whether the user's third-party registration fails specifically includes: The service call session control function network element receives the user status subscription request sent by the user terminal; The SCF network element queries whether there is user data of the user. 6. The method according to claim 5, wherein if the third-party registration of the user fails, sending a failure response to the subscriber specifically includes: If the user data does not exist, the SCSCF network element sends a no-discovery failure response to the user terminal. 7. The method according to claim 6, wherein the subscriber canceling the user according to the failure response specifically comprises: The user terminal receives the non-discovery failure response; The user terminal sets the user status of the user as unregistered. 8. A third-party registration failure processing device for IMS, characterized in that it comprises: A query module, configured to receive the user status subscription request sent by the subscriber, and query whether the third-party registration of the user fails; A response module, configured to send a failure response to the subscriber if the third-party registration of the user fails, wherein the failure response does not need to be initiated depending on a pre-established subscription relationship; A logout module, configured for the subscriber to log out the user according to the failure response. 9. The device according to claim 8, wherein the response module specifically comprises: The first response unit is configured to: when the home subscription server returns that the user is unregistered, the inquiry-CSCF network element sends a no failure response to the proxy-CSCF network element. 10. The device according to claim 9, wherein the logout module specifically comprises: a first receiving unit, configured for the proxy call session control function network element to receive the non-discovery failure response; A first deregistration unit, configured for the PCSCF network element to delete the registration information of the user. 11. The device according to claim 8, wherein the response module specifically comprises: The second response unit is configured to: when the user data does not exist in the S-CSCF network element, the S-CSCF network element sends a no failure response to the user terminal. 12. The device according to claim 11, wherein the logout module specifically comprises: a second receiving unit, configured for the user terminal to receive the no failure response; The second logout unit is configured for the user terminal to set the user status of the user as unregistered.

Images