CN101132407A - 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
- CN101132407A CN101132407A CNA2007101387469A CN200710138746A CN101132407A CN 101132407 A CN101132407 A CN 101132407A CN A2007101387469 A CNA2007101387469 A CN A2007101387469A CN 200710138746 A CN200710138746 A CN 200710138746A CN 101132407 A CN101132407 A CN 101132407A
- Authority
- CN
- China
- Prior art keywords
- cscf
- user
- gravity treatment
- response
- registration
- 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.)
- Granted
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 abnormity processing method that re-selection service call conversation control function caused when counterweight was registered in a kind of IP Multimedia System.
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 framework that proposes, it adopts initial session protocol (Session Initial Protocol, be called for short SIP), made up an opening and service environment flexibly, support multimedia application, and provide abundant multimedia service for the user.
IMS comprises home subscriber server (Home Subscriber Server is called for short HSS), CSCF a plurality of network functional entities such as (Call Session Control Function are called for short CSCF).
Wherein, CSCF is an entire I MS server, the main SIP signaling of being responsible for handling in the multimedia call session process.Its function comprises: Multimedia session control, address transition and service negotiation 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 respond 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 user-dependent, the customization data that is used for handling Multimedia session, comprising: local information, checking and authorization message, log-on message, Service Trigger Information, userspersonal information and distribute to user's S-CSCF etc.
IMS user at first 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 a user registration state.After the user registration success, P-CSCF can subscribe to this user's login state to S-CSCF, 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 register requirement (Register) to P-CSCF, has public subscriber identification in this request;
102:P-CSCF receives register requirement, 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 register requirement is forwarded to I-CSCF;
103:I-CSCF sends the S-CSCF request for allocation to HSS, requires to distribute S-CSCF;
104:HSS returns the S-CSCF assignment response to I-CSCF, comprises S-CSCF address/name or capabilities list that promising this user distributes in this response message;
105:I-CSCF is selected S-CSCF from above-mentioned S-CSCF address/name or capabilities list, and above-mentioned register requirement is sent to this selected S-CSCF;
If S-CSCF need carry out then execution in step 106～116 of authentication to the user, otherwise jump to step 117.
106～116:S-CSCF sends user authentication request to HSS, to obtain authentification of user vector (step 106); HSS returns user authentication response to S-CSCF, comprises authentification of user vector (step 107) in this response message; S-CSCF uses this authentification of user vector 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, after S-CSCF receives this challenge responses, judges user's legitimacy, finishes 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 heavily the registration (claiming refresh registration again) all adopt above flow process, when just heavily registering, 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 among Fig. 2 and refreshed the subscription 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).Initially subscribe to and refresh to subscribe to and comprise 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, owing to be initial registration, previous not subscription, be initial the subscription this moment;
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 the 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 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 refresh 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;
211:S-CSCF receives after this refreshes subscribe request, and structure is 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 owing to the machine of delaying or reason such as restart and take place unusual, when heavily registering, I-CSCF may register (the S-CSCF gravity treatment has promptly taken place) for this user selects new S-CSCF, but P-CSCF but and do not know that change has taken place S-CSCF.P-CSCF can not in time cancel the subscription of user registration state in this case, can not set up subscribing relationship with new S-CSCF, but continues to initiate to refresh subscription to original S-CSCF, and is overtime up to subscribing to, and just can discharge original subscription.In addition,, also can't in time delete based on the session on the original S-CSCF (as inviting request etc.), just can be released, caused metering data inaccurate until this session timeout for this user who preserves among the P-CSCF owing to can't in time know the change of S-CSCF.
For above-mentioned owing to gravity treatment S-CSCF cause unusual, except adopting timeout treatment (subscribing to overtime, session timeout) mechanism, P-CSCF can also know that by the S-CSCF information that contrasts in this notice of cancellation S-CSCF changes receiving network-initiated deregistration notice (Notify message) that (after the gravity treatment) S-CSCF sends when requiring logging off users.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) under the situation, IBCF (Interconnection BorderControl Function interconnection boundary Control function) can encrypt fields such as Via, Path in the success response of register requirement (Register message), Service-route, the S-CSCF information that like this, wherein comprises will be encrypted.That is to say that the S-CSCF information that P-CSCF preserves is enciphered message, therefore, can't compare by the S-CSCF information that will comprise in itself and the Notify message and judge whether S-CSCF changes.
In sum, because P-CSCF can't in time be known 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, can't know that promptly the user registers S-CSCF gravity treatment, therefore also just can't obtain the current login state of this user, also can't in time delete the invalid user session data of current reservation by subscribing mechanism.
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 taken place S-CSCF, and in time carry out the abnormity 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 abnormity processing method that re-selection service call conversation control function is caused, it is characterized in that, when the user initiates heavy register requirement, and after the S-CSCF gravity treatment took place, 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 the 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 heavy register requirement and sends to P-CSCF, and P-CSCF knows that according to this gravity treatment indication information gravity treatment has taken place the S-CSCF of this user's correspondence.
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 the 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, when the S-CSCF after the described gravity treatment at described heavy register requirement after described HSS sends user authentication request, 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 the above-mentioned user authentication request, knows that gravity treatment has taken place the S-CSCF of this user's correspondence;
B) this HSS sends the user authentication response that comprises the described indication information of gravity treatment to this S-CSCF;
C) this S-CSCF knows that according to the above-mentioned indication information of gravity treatment gravity treatment has taken place the S-CSCF of this user's correspondence, and will be the gravity treatment indication information be included in the response of succeeding in registration corresponding and be sent to described P-CSCF with described heavy register requirement.
In addition, when the S-CSCF after the described gravity treatment at described heavy register requirement after described HSS sends user's configuring request, 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 the above-mentioned user's configuring request, knows that gravity treatment has taken place the S-CSCF of this user's correspondence;
B1) this HSS sends the user's configuration response that comprises the described indication information of gravity treatment to this S-CSCF;
C1) this S-CSCF knows that according to the above-mentioned indication information of gravity treatment gravity treatment has taken place the S-CSCF of this user's correspondence, and will be the gravity treatment indication information be included in the response of succeeding in registration corresponding and be sent to described P-CSCF with described heavy register requirement.
In addition, after described P-CSCF receives the described response of succeeding in registration, carry out following operation: the session of deleting the S-CSCF of this user before based on gravity treatment; And/or cancellation is based on the subscription of this user registration state of the S-CSCF before this gravity treatment; And/or, to sending the subscribe request that the described S-CSCF that succeeds in registration response sends this user registration state.
In addition, the present invention also provides a kind of abnormity processing method that re-selection service call conversation control function is caused, it is characterized in that, after the user initiated register requirement, the S-CSCF that this register requirement is handled was included in the S-CSCF label in the response message that succeeds in registration corresponding with this register requirement 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 to know whether the corresponding S-CSCF of this user gravity treatment has taken place.
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 register requirement is handled receives the user configuration response corresponding with this register requirement, carry out following operation:
A) corresponding with the described register requirement response of succeeding in registration that 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) register requirement if described register requirement is attached most importance to, then 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 the S-CSCF of this user's correspondence gravity treatment has taken place.
In addition, after described step c), comprise following steps:, then delete the session of the S-CSCF of this user before based on gravity treatment if gravity treatment has taken place for the S-CSCF of this user's correspondence; And/or cancellation is based on the subscription of this user registration state of the S-CSCF before this gravity treatment; And/or, to sending the subscribe request that this S-CSCF that succeeds in registration response sends this user registration state.
Adopt method of the present invention can allow P-CSCF know that timely and accurately gravity treatment has taken place S-CSCF, thereby make P-CSCF, delete failed session data, and the login state of relative users reformulated read at the former subscription of cancellation in time of this situation.
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 abnormity processing method flow diagram that first embodiment of the invention causes gravity treatment S-CSCF;
Fig. 4 is the abnormity processing method flow diagram that second embodiment of the invention causes gravity treatment S-CSCF.
Embodiment
What S-CSCF took place that gravity treatment caused when heavily registering is unusual, the present invention makes amendment to existing register flow path, adopts dual mode to make P-CSCF know that in time gravity treatment takes place S-CSCF: the information notification P-CSCF that, gravity treatment S-CSCF has been taken place by S-CSCF by HSS; Two, register and weigh in the registration process the user by S-CSCF, the S-CSCF label is included in the response message that succeeds in registration passes to P-CSCF, P-CSCF judges by comparing the S-CSCF label whether S-CSCF gravity treatment has taken place.
Describe the present invention below in conjunction with drawings and Examples.
Fig. 3 is the abnormity processing method flow diagram that first embodiment of the invention causes gravity treatment S-CSCF.S-CSCF1 represents the initial S-CSCF that gravity treatment is preceding among the figure, and S-CSCF2 represents the S-CSCF after the gravity treatment.
As shown in Figure 3, in conjunction with heavy registration 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 carries out following processing unusually to what gravity treatment S-CSCF caused:
301:UE (user) initiates heavy register requirement (Register message) to P-CSCF;
302: the P-CSCF of access zone network is forwarded to I-CSCF with it after receiving above-mentioned heavy register requirement;
303～304:I-CSCF sends the S-CSCF request for allocation to HSS, and obtains S-CSCF address/name or capabilities list for this user's distribution according to the S-CSCF assignment response message that HSS returns;
The above-mentioned heavy register requirement of S-CSCF (being S-CSCF1) forwarding that 305:I-CSCF distributes for this user before heavily registering, and S-CSCF1 does not have response or returns error message this heavy register requirement owing to fault (as the machine of delaying); 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 transmits above-mentioned heavy register requirement to above-mentioned selected S-CSCF (being S-CSCF2);
After 307:S-CSCF2 receives above-mentioned heavy register requirement, 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 the above-mentioned user authentication request, judges that change has taken place S-CSCF;
309:HSS returns 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 in this expansion AVP field, comprise gravity treatment indication information, 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 among expansion AVP and the expansion AVP, whether the S-CSCF that determines this user's correspondence gravity treatment has taken place, preserve the information that S-CSCF changes, finish this user's subsequent authentication authentication (challenge request/challenge responses) then;
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; In this response message, comprise gravity treatment indication information, be used to indicate S-CSCF that change has taken place;
The above-mentioned indication information of gravity treatment can be expanded (increase) parameter modes such as (comprising parameter name and parameter value) by expansion (increase) sip message head field or in existing sip message head field and be included in the response of succeeding in registration;
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 takes place S-CSCF, and can select the session of this user of deletion based on S-CSCF1 according to local policy or operator's management strategy;
317:P-CSCF sends the subscribe request (the Expires value is 0 subscribe request) that cancels subscriptions to S-CSCF1, and cancellation is based on the subscription of this user registration state of S-CSCF1;
318:, then delete local subscription data and return the subscription success response if S-CSCF1 receives the subscribe request that cancels subscriptions;
319～325:P-CSCF uses this user's public subscriber identification to construct the subscribe request of this user registration state, and finishes 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 first embodiment, and for example, described step 312 is replaced by following steps:
312 ': after HSS receives this user's configuring request, compare, judge that change has taken place S-CSCF with the S-CSCF information that comprises in this user's of local storage S-CSCF information (title etc.) and the above-mentioned user's configuring request; 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 in this expansion AVP field, comprise gravity treatment indication information;
Fig. 4 is the abnormity processing method flow diagram that second embodiment of the invention causes gravity treatment S-CSCF.As shown in Figure 4, in conjunction with heavy register flow path of the prior art, the present invention carries out following processing unusually to what gravity treatment S-CSCF caused:
401:UE, P-CSCF, I-CSCF, HSS and S-CSCF1 carry out alternately user's (UE) initial registration request is carried out 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 in this response message, comprise the S-CSCF label, it is sent to P-CSCF by I-CSCF;
Above-mentioned S-CSCF label must can unique identification S-CSCF1, and the MAC Address that for example can use S-CSCF1 is 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, finished this user's initial registration.
405:P-CSCF and S-CSCF1 obtain this user's login state by subscribing 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 user's (UE) heavy register requirement is carried out 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.
For a certain reason, the S-CSCF gravity treatment can take place when the user initiates heavy register requirement, promptly this register requirement is finally transferred to S-CSCF2 and is handled.
After 407:S-CSCF2 receives user's configuration response of HSS transmission, construct the response (200OK message) of succeeding in registration, and in this response message, comprise the S-CSCF label, 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 taken place;
Notice, the user data of this UE that P-CSCF can be by local storage, or the S-CSCF label of this UE of local storage is judged the corresponding register requirement register requirement of attaching most importance to.
In addition,, can not encrypt, therefore can know accurately by above-mentioned S-CSCF label contrast operation whether the S-CSCF gravity treatment has taken place sip message extension header field and spreading parameter owing to hide under the situation at THIG.
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 the session of this user based on 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 (9)
1. abnormity processing method that re-selection service call conversation control function is caused, it is characterized in that, when the user initiates heavy register requirement, and after the S-CSCF gravity treatment took place, 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 the 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 heavy register requirement and sends to P-CSCF, and P-CSCF knows that according to this gravity treatment indication information gravity treatment has taken place the S-CSCF of this user's correspondence.
2. the abnormity processing method that re-selection service call conversation control function is caused as claimed in claim 1 is characterized in that, 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 the 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.
3. the abnormity processing method that re-selection service call conversation control function is caused as claimed in claim 1 is characterized in that, when the S-CSCF after the described gravity treatment at described heavy register requirement after described HSS sends user authentication request, 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 the above-mentioned user authentication request, knows that gravity treatment has taken place the S-CSCF of this user's correspondence;
B) this HSS sends the user authentication response that comprises the described indication information of gravity treatment to this S-CSCF;
C) this S-CSCF knows that according to the above-mentioned indication information of gravity treatment gravity treatment has taken place the S-CSCF of this user's correspondence, and will be the gravity treatment indication information be included in the response of succeeding in registration corresponding and be sent to described P-CSCF with described heavy register requirement.
4. the abnormity processing method that re-selection service call conversation control function is caused as claimed in claim 1 is characterized in that, when the S-CSCF after the described gravity treatment at described heavy register requirement after described HSS sends user's configuring request, 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 the above-mentioned user's configuring request, knows that gravity treatment has taken place the S-CSCF of this user's correspondence;
B1) this HSS sends the user's configuration response that comprises the described indication information of gravity treatment to this S-CSCF;
C1) this S-CSCF knows that according to the above-mentioned indication information of gravity treatment gravity treatment has taken place the S-CSCF of this user's correspondence, and will be the gravity treatment indication information be included in the response of succeeding in registration corresponding and be sent to described P-CSCF with described heavy register requirement.
5. as claim 3, the 4 described abnormity processing methods that re-selection service call conversation control function is caused, it is characterized in that, after described P-CSCF receives the described response of succeeding in registration, carry out following operation: the session of deleting the S-CSCF of this user before based on gravity treatment; And/or cancellation is based on the subscription of this user registration state of the S-CSCF before this gravity treatment; And/or, to sending the subscribe request that the described S-CSCF that succeeds in registration response sends this user registration state.
6. abnormity processing method that re-selection service call conversation control function is caused, it is characterized in that, after the user initiated register requirement, the S-CSCF that this register requirement is handled was included in the S-CSCF label in the response message that succeeds in registration corresponding with this register requirement 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 to know whether the corresponding S-CSCF of this user gravity treatment has taken place.
7. the abnormity processing method that re-selection service call conversation control function is caused as claimed in claim 6 is characterized in that, described S-CSCF label is included in the extension header field or spreading parameter of the described response message that succeeds in registration.
8. the abnormity processing method that re-selection service call conversation control function is caused as claimed in claim 6, it is characterized in that, after the S-CSCF that described register requirement is handled receives the user configuration response corresponding with this register requirement, carry out following operation:
A) corresponding with the described register requirement response of succeeding in registration that 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) register requirement if described register requirement is attached most importance to, then 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 the S-CSCF of this user's correspondence gravity treatment has taken place.
9. the abnormity processing method that re-selection service call conversation control function is caused as claimed in claim 8, it is characterized in that, after described step c), comprise following steps:, then delete the session of the S-CSCF of this user before based on gravity treatment if gravity treatment has taken place for the S-CSCF of this user's correspondence; And/or cancellation is based on the subscription of this user registration state of the S-CSCF before this gravity treatment; And/or, to sending the subscribe request that this S-CSCF that succeeds in registration response sends 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 true CN101132407A (en) | 2008-02-27 |
| CN101132407B 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) |
Cited By (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 |
| CN112714442A (en) * | 2019-10-24 | 2021-04-27 | 中国移动通信集团山东有限公司 | Exception handling method and device, storage medium and server |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1881975B (en) * | 2005-09-05 | 2010-10-13 | 华为技术有限公司 | Method for calling user terminal of IP multimedia subsystem |
| CN100426744C (en) * | 2005-12-08 | 2008-10-15 | 华为技术有限公司 | Processing method for exception in course of P-CSCF and UE log-on |
-
2007
- 2007-08-13 CN CN 200710138746 patent/CN101132407B/en not_active Expired - Fee Related
Cited By (4)
| 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 |
| CN112714442A (en) * | 2019-10-24 | 2021-04-27 | 中国移动通信集团山东有限公司 | Exception handling method and device, storage medium and server |
| CN112714442B (en) * | 2019-10-24 | 2023-04-18 | 中国移动通信集团山东有限公司 | Exception handling method and device, storage medium and server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101132407B (en) | 2013-11-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2047657B1 (en) | Method and apparatus for collecting user activity in a telecommunications system | |
| CN101176369B (en) | Service profiles in IMS processes | |
| US8571548B2 (en) | Method and system for changing a subscription | |
| JP4549393B2 (en) | User registration in communication systems | |
| 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 | |
| CN103329499B (en) | Dynamic allocation method, server, system and the network node of serving network node | |
| EP2433405B1 (en) | Managing user registrations of roaming ims users | |
| US8532091B2 (en) | Method and apparatus for providing IMS services to circuit-switched controlled terminals | |
| WO2004084510A1 (en) | Method, system and network device for routing a message to a temporarily unavailable network user | |
| WO2006053502A1 (en) | A method for ensuring the information consistency between the network nodes | |
| US8600031B2 (en) | Method for connecting calls between an IP multimedia subsystem (IMS) domain and a circuit switched (CS) domain | |
| KR100703426B1 (en) | Method and apparatus for sending and receiving call unregistered user in a ip multimedia subsystem network | |
| WO2007052894A1 (en) | Distributed hss (home subscriber server) architecture | |
| 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 | |
| CN101384085A (en) | Terminal registration method, apparatus and system | |
| 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 | |
| EP2382749B1 (en) | Allocation of a serving entity in a communication network | |
| US9426711B2 (en) | Traffic control within an IP multimedia subsystem | |
| JP4586056B2 (en) | Method and system for changing contracts | |
| US9398054B2 (en) | Optimized user re-distribution over S-CSCF entities |
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 |