CN101132407B - Method for processing exception caused by re-selection service call conversation control function - Google Patents
Method for processing exception caused by re-selection service call conversation control function Download PDFInfo
- Publication number
- CN101132407B CN101132407B CN 200710138746 CN200710138746A CN101132407B CN 101132407 B CN101132407 B CN 101132407B CN 200710138746 CN200710138746 CN 200710138746 CN 200710138746 A CN200710138746 A CN 200710138746A CN 101132407 B CN101132407 B CN 101132407B
- Authority
- CN
- China
- Prior art keywords
- cscf
- gravity treatment
- user
- request
- response
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Abstract
This invention relates to a method for processing abnormal situation caused by a re-selected service session control function characterizing: when a user starts up a re-registration request and S-CSCF is re-selected, HSS holds the re-selected instruction information in an authentication response to the S-CSCF user and user configuration response information, which holds the information in the successful registration response corresponding to the re-registration request to P-CSCF, which gets to know that the S-CSCF corresponding to the user is re-selected according to the re-selected instruction information, in which, P-CSCF can get to know that S-CSCF is re-selected timely and accurately, so that P-CSCF can cancel the original subscription timely.
Description
Technical field
The abnormal processing method that when in a kind of IP Multimedia System, counterweight is registered, re-selection service call conversation control function causes.
Background technology
IP (Internet Protocol, network interconnection agreement) IP multimedia subsystem, IMS (IP Multimedia CoreNetwork Subsystem, be called for short IMS) be by third generation partner program (3rd GenerationPartnership Project, abbreviation 3GPP) a kind of IP-based network architecture that proposes, it adopts initial session protocol (Session Initial Protocol, be called for short SIP), built an opening and service environment flexibly, support multimedia application, and provide abundant multimedia service for the user.
IMS comprises a plurality of network functional entities such as home subscriber server (Home Subscriber Server is called for short HSS), CSCF (Call Session Control Function is called for short CSCF).
Wherein, CSCF is whole IMS server, the main SIP signaling of being responsible for processing in the multimedia call session process.Its function comprises: Multimedia session control, address transition and service negotiation is served conversion etc.CSCF further can be divided into:
Proxy-Call Session Control Function (Proxy-CSCF is called for short P-CSCF) is the Ingress node that connects IMS terminal and IMS network, and the conversation message that the IMS terminal was initiated and ended to all IMS terminals all will pass through P-CSCF.P-CSCF can be in visited network or home network.
Interrogation-call session control function (Interrogating-CSCF, be called for short I-CSCF), be the Ingress node that the IMS terminal that is in field network enters (comprising that this locality roams to the terminal in other places) local IMS network, the SIP request of I-CSCF route other places terminal and response are to local S-CSCF.I-CSCF is in home network, under special circumstances, also can be in visited network.
Service-call session control function (Serving-CSCF is called for short S-CSCF) is carried out the session control service for the IMS terminal, and keeps session status.The SIP signaling that all IMS terminals are sent and received all will be passed through S-CSCF.
HSS is the central database of storage user related information, except storage user's CAMEL-Subscription-Information and positional information, also preserve and customization data user-dependent, that be used for processing Multimedia session, comprising: local information, checking and authorization message, log-on message, Service Trigger Information, userspersonal information and distribute to S-CSCF of user etc.
At first IMS user needs to register if carry out session.The process of registration is exactly that the position of oneself is registered on network.In addition, by subscribing to (Subscribe)/notice (Notify) mechanism, network functional entity can be subscribed to resource status, and receives the lastest imformation of resource when resource status modification.Above-mentioned resource status can be user registration state.After user registration success, P-CSCF can subscribe to S-CSCF this user's login state, and when this user's login state changed, P-CSCF can receive the notice of S-CSCF, has guaranteed the consistency of user registration state data in network.
Fig. 1 is IMS user's register flow path figure.Relate generally to following network element and equipment: UE (UserEquipment, subscriber equipment), P-CSCF, I-CSCF, S-CSCF, HSS.As shown in Figure 1, IMS user's registration comprises following steps:
101:UE (user) sends registration request (Register) to P-CSCF, in this request with public subscriber identification;
102:P-CSCF receives registration request, inquires about or uses other method to find the I-CSCF of user attaching Network Access Point by DNS (Domain Name System, domain name system), and this registration request is forwarded to I-CSCF;
103:I-CSCF sends S-CSCF to HSS and distributes request, requires to distribute S-CSCF;
104:HSS returns to the S-CSCF assignment response to I-CSCF, comprises S-CSCF address/name or the capabilities list of promising this user assignment in this response message;
105:I-CSCF is selected S-CSCF from above-mentioned S-CSCF address/name or capabilities list, and above-mentioned registration request is sent to this selected S-CSCF;
If S-CSCF need to carry out execution in step 106～116 of authentication to the user, otherwise jumps to step 117.
106～116:S-CSCF sends user authentication request to HSS, to obtain user's Ciphering Key (step 106); HSS returns to user authentication response to S-CSCF, comprises user's Ciphering Key (step 107) in this response message; S-CSCF uses this user's Ciphering Key structure challenge request, i.e. 401Unauthorized (unauthorized) message, and should challenge and ask to be sent to UE (step 108～110); UE constructs challenge responses, and sends it to S-CSCF, and after S-CSCF received this challenge responses, judgement user's legitimacy was completed authentication, authentication (step 111～116) to the user;
117:S-CSCF sends user's configuring request to HSS;
After 118:HSS receives above-mentioned user's configuring request, storage S-CSCF information, and user's configuration response that will comprise user contracting data, charging address information returns to S-CSCF;
119～121:S-CSCF constructs the response (200OK message) of succeeding in registration, and it is transmitted to UE by I-CSCF and P-CSCF.
User's initial registration and re-injection volume (claiming again refresh registration) all adopt above flow process, and when being the re-injection volume, for a certain reason, the user may register on new S-CSCF.
Fig. 2 is that user registration state is subscribed to flow chart.Describe initial subscription and refresh in Fig. 2 and subscribed to flow process.Initial subscribe to set up after, subscribe to example and have certain lifetime, this lifetime consults to determine by subscribing to both sides, before the example lifetime arrives, needs to retransmit subscribe message, refreshes subscription (subscription of weighing again).Initial subscription and refresh is subscribed to and is comprised following steps:
201:P-CSCF receives the response message that succeeds in registration;
P-CSCF can think that user's initial registration is successful after receiving the response message that succeeds in registration, and this moment, P-CSCF can initiate the subscription to this user registration state, and owing to being initial registration, previous not subscription is at this moment initial the subscription;
202:P-CSCF uses this user's public subscriber identification to construct the initial subscribe request (Subscriber) of this user registration state, and should initial subscribe request send to I-CSCF;
203:I-CSCF obtains the S-CSCF address by inquiry HSS;
204:I-CSCF should initial subscribe request send on S-CSCF;
205～206:S-CSCF structure is subscribed to success response (200OK message), and it is sent to P-CSCF through I-CSCF;
207:S-CSCF sends notice request (Notify) to P-CSCF, the login state of informing this user of P-CSCF.After this, when this user registration state changed, S-CSCF also can initiatively send notice request, informs the change of P-CSCF user registration state;
After 208:P-CSCF receives above-mentioned notice request, return to push-notification-answer (200OK message);
209: after initially subscribing to successfully, P-CSCF basis and the subscription example lifetime duration that S-CSCF consults determine to trigger and refresh subscription;
The 210:P-CSCF structure refreshes subscribe request (Subscriber), and sends it to S-CSCF; Be based on initial subscription owing to refreshing subscribe request, and the address of having preserved S-CSCF when initially subscribing to, so this refreshes subscribe request and can directly send to S-CSCF;
After 211:S-CSCF received this and refreshes subscribe request, structure was subscribed to success response (200OK message), and sends it to P-CSCF;
212～213: identical with step 207～208.
After the success of user's initial registration, if S-CSCF is due to the machine of delaying or the reason abnormal such as restart, during the re-injection volume, I-CSCF may register (the S-CSCF gravity treatment has namely occured) for this user selects new S-CSCF, but P-CSCF but and do not know that change has occured S-CSCF.The subscription of P-CSCF to user registration state in this case can not in time be cancelled, and can not set up subscribing relationship with new S-CSCF, but continues to initiate to refresh subscription to original S-CSCF, until subscribe to overtimely, just can discharge original subscription.In addition, due to the change that can't in time know S-CSCF, also can't in time delete based on the session on original S-CSCF (as inviting request etc.) for this user who preserves in P-CSCF, until this session timeout just can be released, caused metering data inaccurate.
For above-mentioned due to gravity treatment S-CSCF cause abnormal, except adopting timeout treatment (subscribing to overtime, session timeout) mechanism, P-CSCF can also receiving network-initiated deregistration notice (Notify message) that (after gravity treatment) S-CSCF sends when requiring logging off users, know that by the S-CSCF information that contrasts in this notice of cancellation S-CSCF changes.Clearly, the network-initiated deregistration notification message that sends according to S-CSCF knows that there is significant limitation in the method for the change of S-CSCF: (1) knows that the time that S-CSCF changes has uncertainty; (2) hide (Topology HidingInter-network Gateway at THIG, the gateway topology hiding) in situation, IBCF (Interconnection Border Control Function interconnection boundary Control function) can be encrypted fields such as Via, Path in the success response of registration request (Register message), Service-route, the S-CSCF information that like this, wherein comprises will be encrypted.That is to say, the S-CSCF information that P-CSCF preserves is enciphered message, therefore, can't compare to judge whether S-CSCF changes by the S-CSCF information that will comprise in itself and Notify message.
In sum, can't in time know the change of the S-CSCF (be called for short the user and register S-CSCF) that has the current registration status information of user due to P-CSCF, can't know that namely the user registers S-CSCF gravity treatment, therefore also just can't obtain the current login state of this user by subscribing/notifying mechanism, also can't in time delete the invalid user session data of current reservation.
Summary of the invention
Technical problem to be solved by this invention is, overcomes the deficiencies in the prior art, proposes a kind of P-CSCF of making and knows that timely and accurately gravity treatment has occured S-CSCF, and in time carry out the abnormal processing method that gravity treatment S-CSCF is caused of respective handling.
In order to address the above problem, the present invention proposes a kind of abnormal processing method that re-selection service call conversation control function is caused, it is characterized in that, when the user initiates the request of re-injection volume, and after the S-CSCF gravity treatment occured, HSS gravity treatment indication information was included in the user authentication response and/or user's configuration response message that sends to the S-CSCF after gravity treatment; S-CSCF after this gravity treatment is included in the gravity treatment indication information in the response of succeeding in registration corresponding with this re-injection volume request and sends to P-CSCF, and P-CSCF knows that according to this gravity treatment indication information gravity treatment has occured S-CSCF corresponding to this user.
In addition, described HSS is included in described gravity treatment indication information in the expansion AVP field of described user authentication response and/or user's configuration response; S-CSCF after described gravity treatment is included in described gravity treatment indication information in the extension header field or spreading parameter of the described response of succeeding in registration.
In addition, HSS will be the gravity treatment indication information be included in the user authentication response of the S-CSCF after sending to gravity treatment in before, described method also comprises: after sending user authentication request for the request of described re-injection volume to described HSS as the S-CSCF after described gravity treatment, carry out following operation:
A) described HSS compares with the S-CSCF information that comprises in the described user's of local storage S-CSCF information and above-mentioned user authentication request, knows that gravity treatment has occured S-CSCF corresponding to this user;
B) S-CSCF of this HSS after this gravity treatment sends the user authentication response that comprises the described indication information of gravity treatment;
C) S-CSCF after this gravity treatment knows that according to the above-mentioned indication information of gravity treatment gravity treatment has occured S-CSCF corresponding to this user, and will be the gravity treatment indication information be included in the response of succeeding in registration corresponding with the request of described re-injection volume and be sent to described P-CSCF.
In addition, HSS will be the gravity treatment indication information be included in the user's configuration response message of the S-CSCF after sending to gravity treatment in before, described method also comprises: after sending user's configuring request for the request of described re-injection volume to described HSS as the S-CSCF after described gravity treatment, carry out following operation:
A1) described HSS compares with the S-CSCF information that comprises in the described user's of local storage S-CSCF information and above-mentioned user's configuring request, knows that gravity treatment has occured S-CSCF corresponding to this user;
B1) S-CSCF of this HSS after this gravity treatment sends the user's configuration response that comprises the described indication information of gravity treatment;
C1) S-CSCF after this gravity treatment knows that according to the above-mentioned indication information of gravity treatment gravity treatment has occured S-CSCF corresponding to this user, and will be the gravity treatment indication information be included in the response of succeeding in registration corresponding with the request of described re-injection volume and be sent to described P-CSCF.
In addition, after described P-CSCF receives the described response of succeeding in registration, proceed as follows: the session of deleting the S-CSCF of this user before based on gravity treatment; And/or, cancel the subscription based on this user registration state of the S-CSCF before this gravity treatment; And/or, to the subscribe request that sends the described S-CSCF that succeeds in registration response and send this user registration state.
In addition, the present invention also provides a kind of abnormal processing method that re-selection service call conversation control function is caused, it is characterized in that, after the user initiated registration request, the S-CSCF that this registration request is processed was included in the S-CSCF label in the response message that succeeds in registration corresponding with this registration request that sends to P-CSCF; This P-CSCF preserves this S-CSCF label, and compares by the S-CSCF label that this label is corresponding with previous this user who preserves and know whether S-CSCF corresponding to this user gravity treatment has occured.
In addition, described S-CSCF label is included in the extension header field or spreading parameter of the described response message that succeeds in registration.
In addition, after the S-CSCF that described registration request is processed receives the user configuration response corresponding with this registration request, carry out following operation:
Corresponding with the described registration request response of succeeding in registration that a) will comprise the S-CSCF label is sent to P-CSCF;
B) this P-CSCF receives this response of succeeding in registration, and preserves the S-CSCF label that wherein comprises;
C) registration request if described registration request is attached most importance to, this P-CSCF compares the S-CSCF label S-CSCF label corresponding with previous this user who preserves that comprises in this response of succeeding in registration, and knows whether S-CSCF corresponding to this user gravity treatment has occured.
In addition, at described step c) comprise afterwards following steps: if gravity treatment has occured S-CSCF corresponding to this user, delete the session of the S-CSCF of this user before based on gravity treatment; And/or, cancel the subscription based on this user registration state of the S-CSCF before this gravity treatment; And/or, to the subscribe request that sends this S-CSCF that succeeds in registration response and send this user registration state.
Adopt method of the present invention can allow P-CSCF know that timely and accurately gravity treatment has occured S-CSCF, thereby make P-CSCF in time cancel former subscription for this situation, delete failed session data, and the login state of relative users is reformulated read.
Description of drawings
Fig. 1 is IMS user's register flow path figure;
Fig. 2 is that user registration state is subscribed to flow chart;
Fig. 3 is the abnormal process flow figure that first embodiment of the invention causes gravity treatment S-CSCF;
Fig. 4 is the abnormal process flow figure that second embodiment of the invention causes gravity treatment S-CSCF.
Embodiment
What during for fear of the re-injection volume, S-CSCF generation gravity treatment caused is abnormal, the present invention modifies to existing register flow path, adopts dual mode to make P-CSCF know that in time gravity treatment occurs S-CSCF: one, the information notification P-CSCF of gravity treatment by S-CSCF, S-CSCF to be occured by HSS; Two, by S-CSCF in user registration and re-injection volume process, the S-CSCF label is included in the response message that succeeds in registration passes to P-CSCF, P-CSCF judges by S-CSCF label relatively whether S-CSCF gravity treatment has occured.
Describe the present invention below in conjunction with drawings and Examples.
Fig. 3 is the abnormal process flow figure that first embodiment of the invention causes gravity treatment S-CSCF.In figure, S-CSCF1 represents the initial S-CSCF that gravity treatment is front, and S-CSCF2 represents the S-CSCF after gravity treatment.
As shown in Figure 3, in conjunction with re-injection volume of the prior art with subscribe to flow process, when UE (user) succeeds in registration on S-CSCF1, and after P-CSCF subscribes to successfully to this user registration state, the present invention is to extremely being handled as follows that gravity treatment S-CSCF causes:
301:UE (user) initiates re-injection volume request (Register message) to P-CSCF;
302: the P-CSCF of access zone network is forwarded to I-CSCF with it after receiving the request of above-mentioned re-injection volume;
303～304:I-CSCF sends S-CSCF to HSS and distributes request, and obtains to be S-CSCF address/name or the capabilities list of this user assignment according to the S-CSCF assignment response message that HSS returns;
305:I-CSCF is that the S-CSCF of this user assignment (being S-CSCF1) forwards the request of above-mentioned re-injection volume before the re-injection volume, and S-CSCF1 due to fault (as the machine of delaying) to this re-injection volume request without response or return to error message; I-CSCF is according to above-mentioned S-CSCF address/name or capabilities list or local collocation strategy, gravity treatment S-CSCF;
306:I-CSCF forwards the request of above-mentioned re-injection volume to above-mentioned selected S-CSCF (being S-CSCF2);
After 307:S-CSCF2 receives the request of above-mentioned re-injection volume, send user authentication request (Multimedia-Auth-Request is called for short MAR) to HSS;
308:HSS compares with the S-CSCF information that comprises in this user's of local storage S-CSCF information (title etc.) and above-mentioned user authentication request, and change has occured judgement S-CSCF;
309:HSS returns to user authentication response (Multimedia-Auth-Answer to S-CSCF2, be called for short MAA), in this response message, expansion (increase) AVP (Attribute Value Pair, property value to) field, and comprise gravity treatment indication information in this expansion AVP field, be used to indicate S-CSCF change (gravity treatment);
After 310:S-CSCF2 receives above-mentioned authentication response message, according to the content that wherein whether comprises in expansion AVP and expansion AVP, determine whether S-CSCF corresponding to this user gravity treatment has occured, preserve the information that S-CSCF changes, then complete this user's subsequent authentication authentication (challenge request/challenge responses);
311:S-CSCF2 sends user's configuring request (Server-Assignment-Request is called for short SAR) to HSS;
312:HSS storage S-CSCF2 information, and user's configuration response that will comprise user contracting data, charging address information returns to S-CSCF2;
313:S-CSCF2 constructs and succeeds in registration response (200OK message) and be sent to I-CSCF; Comprise gravity treatment indication information in this response message, be used to indicate S-CSCF change has occured;
The above-mentioned indication information of gravity treatment can by expansion (increases) sip message head field or in existing sip message head field mode such as expansion (increase) parameter (comprising parameter name and parameter value) etc. be included in to succeed in registration and respond;
314:I-CSCF sends to P-CSCF with the above-mentioned response of succeeding in registration;
315:P-CSCF receives the above-mentioned response of succeeding in registration, and sends it to UE;
316:P-CSCF knows that according to the indication information of gravity treatment that comprises in the above-mentioned response message that succeeds in registration gravity treatment occurs S-CSCF, and can according to local policy or operator's management strategy, select this user of deletion based on the session of S-CSCF1;
317:P-CSCF sends the subscribe request (the Expires value is 0 subscribe request) that cancels subscriptions to S-CSCF1, cancel the subscription based on this user registration state of S-CSCF1;
318: if S-CSCF1 receives the subscribe request that cancels subscriptions, delete local subscription data and return to the subscription success response;
319～325:P-CSCF uses this user's public subscriber identification to construct the subscribe request of this user registration state, and completes follow-up subscription flow process.
Based on principle of the present invention, the present invention can also have following mapping mode on the basis of above-mentioned the first embodiment, and for example, described step 312 is replaced by following steps:
312 ': after HSS receives this user's configuring request, compare with the S-CSCF information that comprises in this user's of local storage S-CSCF information (title etc.) and above-mentioned user's configuring request, change has occured in judgement S-CSCF; Storage S-CSCF2 information, and send user's configuration response to S-CSCF2, in this response message, expansion (increase) AVP (Attribute Value Pair, property value to) field, and comprise gravity treatment indication information in this expansion AVP field;
Fig. 4 is the abnormal process flow figure that second embodiment of the invention causes gravity treatment S-CSCF.As shown in Figure 4, in conjunction with re-injection volume flow process of the prior art, the present invention is to extremely being handled as follows that gravity treatment S-CSCF causes:
401:UE, P-CSCF, I-CSCF, HSS and S-CSCF1 carry out alternately user's (UE) initial registration request is carried out the processing such as the transmission of authentication, user's configuring request and response;
This step and prior art register flow path 101～118 identical, the description that herein leaves out the details.
After 402:S-CSCF1 receives user's configuration response of HSS transmission, construct the response (200OK message) of succeeding in registration, and comprise the S-CSCF label in this response message, it is sent to P-CSCF by I-CSCF;
Above-mentioned S-CSCF label must can unique identification S-CSCF1, for example can use the MAC Address of S-CSCF1 as the S-CSCF label.
The S-CSCF label can be put into the extension header field of this response message, or in the spreading parameter of existing field.
403:P-CSCF receives the above-mentioned response of succeeding in registration, and preserves this S-CSCF label;
The 404:P-CSCF response message that will succeed in registration sends to UE;
So far, completed this user's initial registration.
405:P-CSCF and S-CSCF1 obtain this user's login state by subscribing/notifying mechanism;
This step is identical with the subscription flow process of prior art, the description that herein leaves out the details.
406:UE, P-CSCF, I-CSCF, HSS and S-CSCF2 carry out alternately the processing such as the transmission of authentication, user's configuring request and response are carried out in user's (UE) re-injection volume request;
This step and prior art register flow path 101～118 identical, the description that herein leaves out the details.
For a certain reason, the S-CSCF gravity treatment can occur when the user initiates the request of re-injection volume, namely this registration request is finally transferred to S-CSCF2 and is processed.
After 407:S-CSCF2 receives user's configuration response of HSS transmission, construct the response (200OK message) of succeeding in registration, and comprise the S-CSCF label in this response message, this response of succeeding in registration is sent to P-CSCF by I-CSCF; But this label unique identification S-CSCF2;
408:P-CSCF receives the above-mentioned response of succeeding in registration, and the S-CSCF label S-CSCF label corresponding with previous this UE that preserves that comprises in this response message compared, and knows the S-CSCF gravity treatment has occured;
Notice the user data of this UE that P-CSCF can store by this locality, or registration request corresponding to the S-CSCF label of this UE of the local storage judgement registration request of attaching most importance to.
In addition, owing to hiding in situation at THIG, can not be encrypted sip message extension header field and spreading parameter, therefore can know accurately by above-mentioned S-CSCF label contrast operation whether the S-CSCF gravity treatment has occured.
The 409:P-CSCF response message that will succeed in registration sends to UE;
410:P-CSCF carries out the operation of S-CSCF gravity treatment abnormality processing according to local policy or operator's management strategy;
Above-mentioned S-CSCF gravity treatment abnormality processing operation can comprise: delete this user based on the session of S-CSCF1; Cancellation is based on the subscription of this user registration state of S-CSCF1; Subscribe to this user's login state etc. to S-CSCF2.
Claims (5)
1. abnormal processing method that re-selection service call conversation control function is caused, it is characterized in that, when the user initiates the request of re-injection volume, and after service call conversation control function S-CSCF gravity treatment occured, home subscriber server HSS gravity treatment indication information was included in the user authentication response and/or user's configuration response message that sends to the S-CSCF after gravity treatment; S-CSCF after this gravity treatment gravity treatment indication information is included in the response of succeeding in registration corresponding with this re-injection volume request and sends to Proxy Call Session Control Function P-CSCF, P-CSCF according to this gravity treatment indication information know that gravity treatment has occured S-CSCF corresponding to this user.
2. the abnormal processing method that re-selection service call conversation control function is caused as claimed in claim 1, it is characterized in that, described HSS is included in the extended attribute value of described user authentication response and/or user's configuration response in the AVP field with the described indication information of gravity treatment; S-CSCF after described gravity treatment is included in the described indication information of gravity treatment in the extension header field or spreading parameter of the described response of succeeding in registration.
3. the abnormal processing method that re-selection service call conversation control function is caused as claimed in claim 1, it is characterized in that, HSS will be the gravity treatment indication information be included in the user authentication response of the S-CSCF after sending to gravity treatment in before, described method also comprises: after sending user authentication request for the request of described re-injection volume to described HSS as the S-CSCF after described gravity treatment, carry out following operation:
A) described HSS compares with the S-CSCF information that comprises in the described user's of local storage S-CSCF information and above-mentioned user authentication request, knows that gravity treatment has occured S-CSCF corresponding to this user;
B) S-CSCF of this HSS after this gravity treatment sends the user authentication response that comprises the described indication information of gravity treatment;
C) S-CSCF after this gravity treatment knows that according to the above-mentioned indication information of gravity treatment gravity treatment has occured S-CSCF corresponding to this user, and will be the gravity treatment indication information be included in the response of succeeding in registration corresponding with the request of described re-injection volume and be sent to described P-CSCF.
4. the abnormal processing method that re-selection service call conversation control function is caused as claimed in claim 1, it is characterized in that, HSS will be the gravity treatment indication information be included in the user's configuration response message of the S-CSCF after sending to gravity treatment in before, described method also comprises: after sending user's configuring request for the request of described re-injection volume to described HSS as the S-CSCF after described gravity treatment, carry out following operation:
A1) described HSS compares with the S-CSCF information that comprises in the described user's of local storage S-CSCF information and above-mentioned user's configuring request, knows that gravity treatment has occured S-CSCF corresponding to this user;
B1) S-CSCF of this HSS after this gravity treatment sends the user's configuration response that comprises the described indication information of gravity treatment;
C1) S-CSCF after this gravity treatment knows that according to the above-mentioned indication information of gravity treatment gravity treatment has occured S-CSCF corresponding to this user, and will be the gravity treatment indication information be included in the response of succeeding in registration corresponding with the request of described re-injection volume and be sent to described P-CSCF.
5. the abnormal processing method that re-selection service call conversation control function is caused as described in claim 3 or 4, it is characterized in that, after described P-CSCF receives the described response of succeeding in registration, proceed as follows: the session of deleting the S-CSCF of this user before based on gravity treatment; And/or, cancel the subscription based on this user registration state of the S-CSCF before this gravity treatment; And/or, to the subscribe request that sends the described S-CSCF that succeeds in registration response and send this user registration state.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200710138746 CN101132407B (en) | 2007-08-13 | 2007-08-13 | Method for processing exception caused by re-selection service call conversation control function |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200710138746 CN101132407B (en) | 2007-08-13 | 2007-08-13 | Method for processing exception caused by re-selection service call conversation control function |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101132407A CN101132407A (en) | 2008-02-27 |
| CN101132407B true CN101132407B (en) | 2013-11-06 |
Family
ID=39129532
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200710138746 Expired - Fee Related CN101132407B (en) | 2007-08-13 | 2007-08-13 | Method for processing exception caused by re-selection service call conversation control function |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101132407B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101720080B (en) * | 2009-12-02 | 2012-01-11 | 中兴智能交通（无锡）有限公司 | Method and device of communication registration |
| CN103138984B (en) * | 2011-12-02 | 2016-09-28 | 中兴通讯股份有限公司 | Disaster tolerance refunds the method and system of service call session control function entity |
| CN112714442B (en) * | 2019-10-24 | 2023-04-18 | 中国移动通信集团山东有限公司 | Exception handling method and device, storage medium and server |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1870522A (en) * | 2005-12-08 | 2006-11-29 | 华为技术有限公司 | Processing method for exception in course of P-CSCF and UE log-on |
| CN1881975A (en) * | 2005-09-05 | 2006-12-20 | 华为技术有限公司 | Method for calling user terminal of IP multimedia subsystem |
-
2007
- 2007-08-13 CN CN 200710138746 patent/CN101132407B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1881975A (en) * | 2005-09-05 | 2006-12-20 | 华为技术有限公司 | Method for calling user terminal of IP multimedia subsystem |
| CN1870522A (en) * | 2005-12-08 | 2006-11-29 | 华为技术有限公司 | Processing method for exception in course of P-CSCF and UE log-on |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101132407A (en) | 2008-02-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200383079A1 (en) | Method, apparatus and system for processing registration backup data | |
| CN101176369B (en) | Service profiles in IMS processes | |
| CN100382503C (en) | Registration abnormity handling method in user registration course | |
| CN101621772B (en) | Session control method and equipment | |
| US9185141B2 (en) | Managing roaming agreements between IMS networks | |
| EP2433405B1 (en) | Managing user registrations of roaming ims users | |
| US8768259B2 (en) | Method and apparatus for collecting user activity in a telecommunications system | |
| US8532091B2 (en) | Method and apparatus for providing IMS services to circuit-switched controlled terminals | |
| KR20080068806A (en) | Provision of ims services via circuit-switched access | |
| CN103329499A (en) | Dynamic assignment of a serving network node | |
| WO2006053502A1 (en) | A method for ensuring the information consistency between the network nodes | |
| US20120177194A1 (en) | Method for connecting call | |
| US8908634B2 (en) | Method for controlling VCC functions initiated by network and terminal and network server thereof | |
| KR100703426B1 (en) | Method and apparatus for sending and receiving call unregistered user in a ip multimedia subsystem network | |
| US9578068B2 (en) | Methods and apparatus for processing an IMS session | |
| CN101132407B (en) | Method for processing exception caused by re-selection service call conversation control function | |
| CN101635963A (en) | Multi-registration method, method for registering under condition of multi-registration and corresponding device | |
| KR101075614B1 (en) | Method for terminating call unregistered user in ip multimedia subsystem network | |
| US9426711B2 (en) | Traffic control within an IP multimedia subsystem | |
| EP2382749B1 (en) | Allocation of a serving entity in a communication network | |
| JP2008109653A (en) | Method and system for changing contract |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20131106 Termination date: 20200813 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |