CN102111899A - Session keep-alive method and device - Google Patents
Session keep-alive method and device Download PDFInfo
- Publication number
- CN102111899A CN102111899A CN2011100556447A CN201110055644A CN102111899A CN 102111899 A CN102111899 A CN 102111899A CN 2011100556447 A CN2011100556447 A CN 2011100556447A CN 201110055644 A CN201110055644 A CN 201110055644A CN 102111899 A CN102111899 A CN 102111899A
- Authority
- CN
- China
- Prior art keywords
- message
- keep
- alive
- session
- rfc4028
- 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
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a session keep-alive method and a session keep-alive device. The method comprises that: a network element on a network side receives a message and determines that information specified by RFC4028 and used for keeping alive is not carried in the message; the network element sets a session timer and transmits a keep-alive message for keeping alive after the session timer expires; and the network element restarts a session timer after the keep-alive message is transmitted or after a keep-alive response message responding to the keep-alive message is received. Through the invention, session keep-alive support is provided when RFC4028 is not supported.
Description
Technical field
The present invention relates to communication field, particularly, refer more particularly to session keepalive method and device.
Background technology
IP Multimedia System (IP Multimedia Subsystem, abbreviate IMS as) be third generation affiliate tissue (3rd Generation Partnership Project, abbreviate 3GPP as) standard of next generation network of definition, its distinguishing feature is to have adopted session initiation protocol (Session Initiation Protocol abbreviates SIP as) system.
Session keepalive is whether a kind of to be used to detect session be a kind of mode that lives, and RFC4028 has carried out expansion to Session Initiation Protocol and realized this keepalive mechanism.RFC4028 has expanded two head: Session-Expires, Min-SE, a function choosing-item: timer (timer) is realized the session keepalive audit function.According to the definition among the RFC4028, the keep-alive object both sides of session keepalive must support the RFC4028 Extended Protocol, and have stipulated following 3 kinds of ways of realization, are explained below:
Form one; calling subscriber (UAC) by initial (INVITE) request of inviting carry be used for keep-alive information (for example; Supported:timer; Session-Expires:90; Min-SE:90); when the called subscriber (UAS) of the request of receiving or agency (Proxy) also support RFC4028; and when also wishing the Run Sessions keepalive feature; then can consult to initiate the time interval of keep-alive at 200OK (INVITE), the keep-alive that reInvite that final result through consultation regularly initiates or renewal (UPDATE) message are carried out session detects.Do not receive the response message of holding consultation in preset time when initiatively initiating the keep-alive requesting party, perhaps passive when accepting the keep-alive requesting party and not receiving the keep-alive request at the fixed time, judge that then session stops, discharge session, discharge the resource of this session correspondence simultaneously.
Form two, after session was set up, UAC or UAS were because demand is asked initiation session keep-alive request among the Update (carrying the information that is used for keep-alive of RFC4028 regulation) in follow-up dialogue.
Form three, core network element also can come initiatively to increase the relevant information of Session Timers in forwards when next is jumped according to specific strategy, show that hope energy and next realize Session Timers function between jumping.
It is that both sides at the keep-alive object define when satisfying this agreement that session among the RFC4028 detects.In IMS uses; when all SIP network elements (comprising terminal) all must be supported RFC4028; and in application; when all wishing between each network element during session, to use Session Timers function; flow process is roughly similar, and difference mainly is the request promoter of negotiate further execution Session Timers function and the time interval (being mainly reflected in head part S ession-Expires) of keep-alive.
Fig. 1 is a flow chart of all supporting and wish to use Session Timer according to the IMS network element of correlation technique in session, it is example that this figure initiatively requires to carry out the SessionTimers function during session with the promoter of session, this flow process is described, this flow process is through proxy call conversation control function entity (Proxy-Call Session Control Function, abbreviate P-CSCF as), service call session control function entity (Serving-CSCF, abbreviate S-CSCF as) and query call conversation control function entity (Interrogating-CSCF, abbreviate I-CSCF as), as shown in Figure 1, this flow process comprises the steps:
Step S101, calling subscriber (UAC) initiates the initial INVITE request message, has carried following information: Session-Expires:90, Min-SE:90, Supported:timer in this request message.These information show that terminal is supported Session Timers, and the keep-alive interval of oneself is provided.
Step S102, the P-CSCF network element of Calling Side is transmitted this message, and this P-CSCF acquiescence is supported Session Timers function.
Step S103, core network element I/S-CSCF network element is transmitted message, and this I/S-CSCF acquiescence is supported Session Timers function.
Step S104, the P-CSCF network element of callee side is transmitted message, and this core network element P-CSCF acquiescence is supported Session Timers function.
Step S105 after called subscriber (UAS) receives this message, accepts the relevant agreement of SessionTimer from caller, with being intended to open Session Timer function in the session.Callee side increases following information in the 200OK message of replying, so that the negotiation result of Session Timer: Session-Expires:90, refresher:uac, Min-SE:90, Require:timer to be provided.The called answer after the 200OK message starts Session Timer timer.
Step S106, callee side P-CSCF mate with local relevant information after receiving 200OK (INVITE) message, consult successfully then to transmit this message to core-network side, and start Session Timer timer.
Step S107, core network element I/S-CSCF mate with local relevant information after receiving 200OK (INVITE) message, consult successfully then to transmit this message to core-network side, and start Session Timer timer.
Step S108, Calling Side P-CSCF, receive 200OK (INVITE) message after, mate with local relevant information, consult successfully the back and start Session Timer timer.
Step S109, step S110, step S111 and step S112 send affirmation (ACK) message and transmit.
Step S113, Calling Side Session Timer timer expiry is initiatively initiated Session Timer request UPDATE, and this request message comprises: Session-Expires:90, Min-SE:90.
Step S114, Calling Side P-CSCF receive Session Timer request UPDATE, kill Session Timer timer, transmit UPDATE message.
Step S 115, and core network element I/S-CSCF receives Session Timer request UPDATE, kills Session Timer timer, transmits UPDATE message.
Step S116, callee side P-CSCF receive Session Timer request UPDATE, kill Session Timer timer, transmit UPDATE message.
Step S117, called subscriber (UAS) receive the UPDATE request of Session Timer, kill Session Timer timer, reply 200OK (UPDATE).
Step S118, step S119 and step S120, the UPDATE request responding message 200OK of forwarding Session Timer, each network element all is provided with Session Timer timer again after receiving 200OK (UPDATE).
Step between the step S113-step S120 will be to carry out in the cycle with Session Timer timer always, be terminated up to the unusual or session of network occurring.
Above-mentioned step all is could carry out when the session keepalive both sides all support RFC4028, and when a side of session keepalive did not support RFC4028, session keepalive just can not be carried out.
In the IMS system, most core network elements (such as P/I/S-CSCF) have satisfied RFC4028, can effectively realize the session keepalive function.But the application of Session Initiation Protocol just began before 1999; RFC4028 then just occurred in 2005; market in this time interval; a large amount of sip terminals has appearred on the network; these terminals should be can not support RFC4028; later also can exist the terminal supplier not realize RFC4028 in same 2005; in case these do not support the terminal access to IMS network of RFC4208; session keepalive can't be provided; this will be easy to cause SIP network entity resource exhaustions such as P/I/S-CSCF, cause SIP network entities such as P/I/S-CSCF to provide normal service for validated user.
Summary of the invention
Main purpose of the present invention is to provide session keepalive method and device, to address the above problem at least.
According to an aspect of the present invention, provide a kind of session keepalive method, comprising: the network element of network side receives message, and determines not carry in the described message information that is used for keep-alive of RFC4028 regulation; Described network element is provided with Session Timer, and described Session Timer then after, send the keep-alive message be used for keep-alive; After sending described keep-alive message or receiving after the keep-alive response message in response to described keep-alive message, described network element is restarted described Session Timer.
Preferably, after described network element determined not carry in the described message the described information that is used for keep-alive, described method also comprises: described network element sent and is used to inquire about the query messages of whether supporting RFC4028; Described network element receives the response message of described query messages, determines that according to the response message of described query messages the transmit leg of this response message is not supported RFC4028, and described Session Timer then after, send described keep-alive message.
Preferably, described query messages is an option OPTION message.
Preferably, described network element adds the information that is used for keep-alive of RFC4028 regulation in the described message that receives, and sends described message; Described network element receives the response message of described message, and judges according to the information that is used for keep-alive that whether carries the RFC4028 regulation in the response message of described message whether the transmit leg of the response message of described message supports RFC4028; Described network element do not support under the situation of RFC4028 at the transmit leg of described response message, described Session Timer then after, send described keep-alive message.
Preferably, determine that at described network element the transmit leg of this response message supports that described method also comprises under the situation of RFC4028; The transmit leg of described network element and described response message carries out the negotiation of the session keepalive of RFC4028 regulation, and carries out session keepalive according to the result who consults.
Preferably, also carry at described response message under the situation of type of the described keep-alive message that the transmit leg of described response message supports, described network element described Session Timer then after, send the keep-alive message corresponding with described type.
Preferably, the type of described keep-alive message comprises: invite INVITE, upgrade UPDATE message.
According to a further aspect in the invention, provide a kind of session keepalive device, be arranged in the network element of network side, this device comprises: receiver module is used to receive message, and determines not carry in the described message information that is used for keep-alive of RFC4028 regulation; Session Timer is provided with module, is used to be provided with Session Timer; First sending module, be used for described Session Timer then after, send the keep-alive message be used for keep-alive; The regular device of described session is provided with module, also is used for after sending described keep-alive message or is receiving after the keep-alive response message in response to described keep-alive message, restarts described Session Timer.
Preferably, this device also comprises: second sending module, be used for after determining that described message is not carried the described information that is used for keep-alive, and send and be used to inquire about the query messages of whether supporting RFC4028; Described first sending module also is used for not supporting under the situation of RFC4028 at the transmit leg of determining this response message according to the response message of described query messages, and described Session Timer then after, send described keep-alive message.
Preferably, this device also comprises: the 3rd sending module is used for adding in the described message that receives the information that is used for keep-alive of RFC4028 regulation, and sends described message; Described first sending module also is used for determining that in the information that is used for the keep-alive whether response message according to described message carries RFC4028 regulation the transmit leg of the response message of described message do not support under the situation of RFC4028; And described Session Timer then after, send described keep-alive message.
By the present invention, solved the problem of not supporting RFC4028 then can not provide session keepalive in the correlation technique and causing, and then the support of session keepalive when not supporting RFC4028 is provided.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 is a flow chart of all supporting and wish to use Session Timer according to the IMS network element of correlation technique in session;
Fig. 2 is the flow chart according to the session keepalive method of the embodiment of the invention;
Fig. 3 is the structured flowchart according to the session keepalive device of the embodiment of the invention;
Fig. 4 is the structured flowchart one of session keepalive device according to the preferred embodiment of the invention;
Fig. 5 is the structured flowchart two of session keepalive device according to the preferred embodiment of the invention;
Fig. 6 initiatively initiates the flow chart that detects with the session between the caller according to the Calling Side core network element of the embodiment of the invention;
Fig. 7 initiatively initiates the flow chart that detects with the session between called according to the callee side core network element of the embodiment of the invention.
Embodiment
Hereinafter will describe the present invention with reference to the accompanying drawings and in conjunction with the embodiments in detail.Need to prove that under the situation of not conflicting, embodiment and the feature among the embodiment among the application can make up mutually.
Following examples can be applied to support in the network of Session Initiation Protocol, for example, IMS network (but being not limited to this), other support Session Initiation Protocol networks also can use.
In the present embodiment, provide the session keepalive method, Fig. 2 is the flow chart according to the session keepalive method of the embodiment of the invention, and as shown in Figure 2, this flow process may further comprise the steps:
Step S202, the network element of network side receives message, and determines not carry in this message the information that is used for keep-alive of RFC4028 regulation;
Step S204, this network element is provided with Session Timer, and above-mentioned Session Timer then after, send the keep-alive message be used for keep-alive;
Step S206, after sending keep-alive message or receiving after the keep-alive response message in response to keep-alive message, network element is restarted Session Timer.
By above-mentioned steps, network element even do not carry the information that is used for keep-alive in this message, also can initiatively be provided with Session Timer when receiving message, thereby realizes keep-alive.For example; this network element can send the information that is used for keep-alive that carries the RFC4028 regulation to called subscriber or other network elements; after receiving response message; because called subscriber or other network elements are supported RFC4028; therefore can not carry the information that is used for keep-alive in the response message, this moment, this network element can initiatively carry out keep-alive execution above-mentioned steps S204 and step S206.
When implementing; receive and do not carry the transmit leg that the information that is used for keep-alive can not illustrate this message in the message and support RFC4028 scarcely; for example; the transmit leg of this message is supported RFC4028; but initiatively do not initiate keep-alive; therefore; preferably; can also be after network element be determined not carry the information that is used for keep-alive in the message; transmission be used to inquire about whether support RFC4028 query messages (for example; this query messages can be option OPTION message); this network element receives after the response message of query messages; determine that according to the response message of this query messages the transmit leg of this response message do not support RFC4028, and described Session Timer then after, send described keep-alive message.Perhaps, this network element can add the information that is used for keep-alive of RFC4028 regulation in the message that receives, and sends this message; After receiving the response message of this message, judge according to the information that is used for keep-alive that whether carries the RFC4028 regulation in the response message of this message whether the transmit leg of the response message of this message supports RFC4028; This network element do not support under the situation of RFC4028 at the transmit leg of this response message, Session Timer then after, send keep-alive message.
Preferably; if said network element is determined the transmit leg of this response message and is supported RFC4028; then network element can carry out the negotiation of the session keepalive of RFC4028 regulation with the transmit leg of response message, and carries out session keepalive (promptly carrying out the step of RFC4028 regulation) according to the result who consults.Certainly, can not hold consultation yet, and directly adopt step S204 and step S206.
Preferably; when implementing; in above-mentioned response message, can also carry the type of the keep-alive message that the transmit leg of response message supports; in this case; this network element Session Timer then after; send the keep-alive message corresponding (for example, inviting INVITE, renewal UPDATE message) with type.
In the present embodiment; a kind of session keepalive device also is provided, and this device is arranged in the network element of network side, and this device is used to realize the foregoing description and preferred implementation thereof; carried out repeating no more of explanation, below the module that relates in this device had been described.Fig. 3 is the structured flowchart according to the session keepalive device of the embodiment of the invention, and as shown in Figure 3, this device comprises: receiver module 32, Session Timer are provided with module 34, the first sending modules 36.Below this structure is described.
Receiver module 32 is used to receive message, and determines not carry in this message the information that is used for keep-alive of RFC4028 regulation; Session Timer is provided with module 34 and is connected to receiver module 32, and this module is used to be provided with Session Timer; First sending module 36 is connected to Session Timer module 34 is set, this module be used for Session Timer then after, send the keep-alive message be used for keep-alive; Session Timer is provided with module 34 and also is used for after sending this keep-alive message or is receiving after the keep-alive response message in response to this keep-alive message, restarts Session Timer.
Fig. 4 is the structured flowchart one of session keepalive device according to the preferred embodiment of the invention; as shown in Figure 4; this device also comprises: second sending module, this module are used for after definite this message is not carried the information that is used for keep-alive, send to be used to inquire about the query messages of whether supporting RFC4028.First sending module 36 is used for not supporting under the situation of RFC4028 at the transmit leg of determining this response message according to the response message of this query messages, and Session Timer then after, send this keep-alive message.
Fig. 5 is the structured flowchart two of session keepalive device according to the preferred embodiment of the invention; as shown in Figure 5; this device also comprises the 3rd sending module 52, and this module is used for adding in this message that receives the information that is used for keep-alive of RFC4028 regulation, and sends this message.First sending module 36 is used for determining that in the information that is used for the keep-alive whether response message according to this message carries RFC4028 regulation the transmit leg of the response message of this message do not support under the situation of RFC4028; And Session Timer then after, send this keep-alive message.
Below be that example describes in conjunction with the preferred embodiments with IP Multimedia System (IMS).
In this preferred embodiment, when IMS inserts side core network element (is that example describes with the P-CSCF network element) when being the Calling Side in session, need be before session establishment in initial INVITE or dialogue INVITE the relevant information among the extraction RFC4028 is discerned session the UPDATE promoter (UAC) whether support this Extended Protocol.When session initiator is not supported this Extended Protocol, record in the related information of this session, " terminal is not supported RFC4028 ".After (success that receives initial INVITE shake hands ACK message or receive the 200OK message of INVITE) set up successfully in session; a session keepalive timer is set; refresh timer can follow the RFC4028 agreement, and the minimum duration of this timer is 90 seconds.Then, send this terminal of Options request inquiry to the promoter of session and whether support RFC4028.When the promoter of session supports RFC4028; the P-CSCF network element can be in refresh timer overtime back active INVITE or Update message (when the capability query result shows that terminal is supported the UPDATE method) in the promoter of session initiates to talk with; come the time mechanism (comprise time, initiatively promoter) of consulting session keep-alive with terminal, detailed process is followed RFC4028.When handling capacity inquiry is obtained terminal and is not supported RFC4028 really, the P-CSCF network element then in refresh timer overtime back active NVITE or Update message (when the capability query result shows that terminal is supported the UPDATE method) in terminal is initiated dialogue, starts this refresh timer simultaneously once more.
Do not receive response message when the session keepalive request timed out and then think the unusual or terminal abnormal of network; P-CSCF network element judgement terminal abnormal or current sessions are unusual; discharge related resource; initiatively survey simultaneously and initiate release message BYE to network; so that also can discharge abnormal resource as early as possible, effectively provide service for other sessions in abutting connection with network element.After response message has been received in the session keepalive request, show then in the normal use of session that treat initiatively to initiate request once more behind the refresh timer timer expiry, circulating successively discharges up to session.
Fig. 6 initiatively initiates the flow chart that detects with the session between the caller according to the Calling Side core network element of the embodiment of the invention, and as shown in Figure 6, this flow process may further comprise the steps:
Step S601, P-CSCF receive the SIPINVITE message from Calling Side, no Session Timer relevant information in this information.
Step S602, P-CSCF transmits message.
Step S603, P-CSCF receives the 200OK (INVITE) from callee side; P-CSCF is by extracting the Session Timer relevant information of Calling Side from INVITE and 200OK (INVITE), the result is " a no Session Timer relevant information ".
Step S604, P-CSCF transmits 200OK (INVITE) to terminal; P-CSCF is provided with the session keepalive timer, and refresh timer, duration are 90s.
Step S605, P-CSCF send out OPTIONS message, the ability of inquiring calling.
Step S606, P-CSCF receive from user's response 200OK (OPTIONS); P-CSCF is information extraction from 200OK: whether have Supported:timer, Allow:UPDATE.These two conditions can have four kinds of combinations:
First kind, both all exist, and show that then the calling subscriber has supported RFC4028.P-CSCF can initiate the UPDATE request to Calling Side behind the timer expiry that S204 is provided with, carry out Session Timer and consult.
Second kind, have only Supported:timer, then show terminal support RFC4028, but do not support UPDATE method (RFC3311), then P-CSCF can be behind the timer expiry that S204 is provided with, and the INVITE request in Calling Side is initiated dialogue is carried out Session Timer and consulted.
The third has only Allow:UPDATE, shows that so terminal do not support RFC4028, and then P-CSCF can be behind the timer expiry that S204 is provided with, and the UPDATE in Calling Side is initiated dialogue asks.
The 4th kind, neither exist, then P-CSCF can be behind the timer expiry that S204 is provided with, the INVITE request in Calling Side is initiated dialogue.
This figure is at the third.First kind, second kind processing is exactly to have followed RFC4028 substantially, the third, the 4th kind of situation be the same in fact, the requesting method difference of session keepalive just.So the UPDATE method does not exist will be simpler on the flow chart of shaking hands.
Step S607, the refresh timer that step S604 is provided with is overtime, and P-CSCF initiates SIP UPDATE message to Calling Side.
Step S608, P-CSCF receive 200OK (UPDATE); Reset refresh timer timer then.
Step S609, the refresh timer that step S607 is provided with is overtime, and P-CSCF initiates SIP UPDATE message to Calling Side.
Step S610, P-CSCF receive 200OK (UPDATE); Reset refresh timer timer then.
Step S607-S610 will serve as that at interval circulation is clocklike carried out with refresh timer, stop up to session, and it is unusual network etc. perhaps to occur.
Step S611, P-CSCF initiate the UPDATE request once more because of refresh timer is overtime.
Step S612, unusual when network occurring, perhaps during the no response of UPDATE request timed out, the P-CSCF network element is judged terminal abnormal, and session stops, and speed sends BYE message to network side, to notify the resource of the network element instant-free in other sessions.
Step S613, P-CSCF receives 200OK (BYE), discharges the session related resource.
When the callee side of P-CSCF network element in session, for the called subscriber, the P-CSCF network element is the promoter of initial message.When the P-CSCF network element received initial INVITE request to be transmitted, the P-CSCF network element need be checked the characteristic attribute that whether exists in this request message among the RFC4028.When not having the information of session keepalive among the initial INVITE, then initiatively in message, add: Supported:timer, Session-Expires=90, heads such as Min-SE=90.When receiving the final success response 200OK of initial request, need to check whether have the session keepalive relevant information.When determining there is not the session keepalive relevant information, show that substantially terminal called do not support RFC4028, then need to be provided with a session keepalive timer, refresh timer can follow the RFC4028 agreement, and the minimum duration of this timer is 90 seconds.When this timer expiry, the P-CSCF network element is request INVITE or UPDATE message in called initiation dialogue initiatively, starts the refreshtimer timer simultaneously once more before conversation end.Do not judge then that when request timed out receives response the session of terminal therewith occurs need discharging related resource immediately unusually, and survey to network simultaneously and initiatively initiate BYE message, discharge resource to notify other network elements.The session keepalive request is sent, and has received response, then shows in the normal use of session, treats initiatively to initiate request once more behind the refresh timer timer expiry, and circulating successively discharges up to session.
Fig. 7 initiatively initiates with the session testing process figure between called according to the callee side core network element of the embodiment of the invention, and as shown in Figure 7, this flow process may further comprise the steps:
Step S701, the P-CSCF of callee side receive the SIP INVITE of core net.
Step S702, P-CSCF extracts Session Timer relevant information from the SIP INVITE, if do not extract relevant information, the P-CSCF network element initiatively adds Session Timer relevant information before forwards: Session-Expires:90, Min-SE:90.
Step S703, P-CSCF receives the response message 200OK (INVITE) from called subscriber (UAS), checks in the code stream whether have Session Timer relevant information, and Require:timer is arranged.Two top conditions have 4 kinds of possibilities:
First kind, when both exist simultaneously, show that terminal supports RFC4028, and wish to carry out this function in session that P-CSCF can start the session keepalive timer: refresh timer, the time that this time also consults among the 200OK is as the criterion.
Second kind, have only Require:timer, this situation also shows terminal support RFC4028, and is willing to be intended to carry out Sesssion Timer function during the session.P-CSCF can start the session keepalive timer: refresh timer, the time that this time adds when asking to transmit is as the criterion.
The third, when having only Session Timer relevant information, no Require:timer shows that then terminal do not support RFC4028, P-CSCF then can start the session keepalive timer, refresh timer, duration is followed RFC4028, and the value minimum is 90s.
The 4th kind, both all do not have, and this situation is equal to the third, promptly show the called RFC4028 that do not support, this moment, the processing of P-CSCF and the third were similar basically, and this Fig. 7 is the processing of the third situation.First kind, second kind then shows terminal support RFC4028, and RFC4028 is also followed in follow-up processing.
Step S704, P-CSCF transmits 200OK (INVITE).
Step S705, the Session Timer timer refresh timer that is provided with under the 3rd among the step S703, the 4 kind of situation is overtime, and P-CSCF sends out session keepalive request SIP UPDATE message to terminal.
Step S706, P-CSCF receives 200OK (UPDATE); Refresh timer timer is set.
Step S707, repeating step S705, the refreshtimer timer expiry, P-CSCF sends out session keepalive request SIPUPDATE message to terminal;
Step S708, repeating step S706, P-CSCF receives 200OK (UPDATE); Refresh timer timer is set.
Step S705-S708 will be that at interval circulation is clocklike carried out with refreshtimer, stop up to session, and it is unusual network etc. perhaps to occur.
Step S709, when the refreshtimer timer expiry, P-CSCF sends out session keepalive request SIPUPDATE message to terminal, and request timed out is not received response message, and then P-CSCF judges the unusual or terminal abnormal of network, decision end call.
Step S710, P-CSCF sends BYE message to network side, notifies in this session other network elements to discharge session related resource P-CSCF and receives 200OK (BYE), discharges this session related resource, conversation end.
Preferably, P-CSCF can be a network element of supporting RFC4028 arbitrarily in the above-mentioned steps, includes but not limited to: P/I/S-CSCF, AGCF, SBC, Application-Service etc.When SIP network element both sides did not support RFC4028, the network element on the core network also can be realized the session protection mechanism according to the foregoing description and preferred implementation thereof.
Preferably, the session keepalive request message in the above-mentioned steps includes but not limited to INVITE, UPDATE message, OPTIONS message etc.
Preferably, the session keepalive of callee side can also adopt with the similar method of Calling Side in the above-mentioned steps: after receiving the handshake information ACK of success response, initiatively to terminal called initiating capacity query requests, with the ability of further understanding terminal.
In sum, solved by the foregoing description and not supported the problem that RFC4028 then can not provide session keepalive to cause in the correlation technique, the support to session keepalive is provided when not supporting RFC4028.
Obviously, those skilled in the art should be understood that, above-mentioned each module of the present invention or each step can realize with the general calculation device, they can concentrate on the single calculation element, perhaps be distributed on the network that a plurality of calculation element forms, alternatively, they can be realized with the executable program code of calculation element, thereby, they can be stored in the storage device and carry out by calculation element, and in some cases, can carry out step shown or that describe with the order that is different from herein, perhaps they are made into each integrated circuit modules respectively, perhaps a plurality of modules in them or step are made into the single integrated circuit module and realize.Like this, the present invention is not restricted to any specific hardware and software combination.
The above is the preferred embodiments of the present invention only, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. session keepalive method is characterized in that comprising:
The network element of network side receives message, and determines not carry in the described message information that is used for keep-alive of RFC4028 regulation;
Described network element is provided with Session Timer, and described Session Timer then after, send the keep-alive message be used for keep-alive;
After sending described keep-alive message or receiving after the keep-alive response message in response to described keep-alive message, described network element is restarted described Session Timer.
2. method according to claim 1 is characterized in that,
After described network element determined not carry in the described message the described information that is used for keep-alive, described method also comprises: described network element sent and is used to inquire about the query messages of whether supporting RFC4028;
Described network element receives the response message of described query messages, determines that according to the response message of described query messages the transmit leg of this response message is not supported RFC4028, and described Session Timer then after, send described keep-alive message.
3. method according to claim 2 is characterized in that, described query messages is an option OPTION message.
4. method according to claim 1 is characterized in that,
Described network element adds the information that is used for keep-alive of RFC4028 regulation in the described message that receives, and sends described message;
Described network element receives the response message of described message, and judges according to the information that is used for keep-alive that whether carries the RFC4028 regulation in the response message of described message whether the transmit leg of the response message of described message supports RFC4028;
Described network element do not support under the situation of RFC4028 at the transmit leg of described response message, described Session Timer then after, send described keep-alive message.
5. according to each described method in the claim 2 to 4, it is characterized in that, determine that at described network element the transmit leg of this response message supports that described method also comprises under the situation of RFC4028;
The transmit leg of described network element and described response message carries out the negotiation of the session keepalive of RFC4028 regulation, and carries out session keepalive according to the result who consults.
6. according to each described method in the claim 2 to 4; it is characterized in that; also carry at described response message under the situation of type of the described keep-alive message that the transmit leg of described response message supports; described network element described Session Timer then after, send the keep-alive message corresponding with described type.
7. method according to claim 6 is characterized in that, the type of described keep-alive message comprises: invite INVITE, upgrade UPDATE message.
8. session keepalive device is arranged in the network element of network side, it is characterized in that comprising:
Receiver module is used to receive message, and determines not carry in the described message information that is used for keep-alive of RFC4028 regulation;
Session Timer is provided with module, is used to be provided with Session Timer;
First sending module, be used for described Session Timer then after, send the keep-alive message be used for keep-alive;
The regular device of described session is provided with module, also is used for after sending described keep-alive message or is receiving after the keep-alive response message in response to described keep-alive message, restarts described Session Timer.
9. device according to claim 8 is characterized in that,
Also comprise: second sending module, be used for after determining that described message is not carried the described information that is used for keep-alive, send and be used to inquire about the query messages of whether supporting RFC4028;
Described first sending module also is used for not supporting under the situation of RFC4028 at the transmit leg of determining this response message according to the response message of described query messages, and described Session Timer then after, send described keep-alive message.
10. device according to claim 8 is characterized in that,
Also comprise: the 3rd sending module is used for adding in the described message that receives the information that is used for keep-alive of RFC4028 regulation, and sends described message;
Described first sending module also is used for determining that in the information that is used for the keep-alive whether response message according to described message carries RFC4028 regulation the transmit leg of the response message of described message do not support under the situation of RFC4028; And described Session Timer then after, send described keep-alive message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110055644.7A CN102111899B (en) | 2011-03-08 | 2011-03-08 | Session keep-alive method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110055644.7A CN102111899B (en) | 2011-03-08 | 2011-03-08 | Session keep-alive method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102111899A true CN102111899A (en) | 2011-06-29 |
| CN102111899B CN102111899B (en) | 2014-08-20 |
Family
ID=44175882
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110055644.7A Expired - Fee Related CN102111899B (en) | 2011-03-08 | 2011-03-08 | Session keep-alive method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102111899B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103516685A (en) * | 2012-06-25 | 2014-01-15 | 中国移动通信集团公司 | Method and system for obtaining terminal connecting state in IMS network, and equipment |
| CN104813641A (en) * | 2012-10-22 | 2015-07-29 | 交互数字专利控股公司 | Method and apparatus for negotiating "keep-alive" message frequencies of applications running on a mobile station |
| CN105323721A (en) * | 2014-07-02 | 2016-02-10 | 中兴通讯股份有限公司 | Speaking right application processing method and device |
| CN105517095A (en) * | 2014-09-25 | 2016-04-20 | 北京信威通信技术股份有限公司 | Relay routing method of session boundary controller |
| CN106909446A (en) * | 2015-12-23 | 2017-06-30 | 阿里巴巴集团控股有限公司 | The keepalive method and device of a kind of application program |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050102393A1 (en) * | 2003-11-12 | 2005-05-12 | Christopher Murray | Adaptive load balancing |
| CN1946062A (en) * | 2006-10-10 | 2007-04-11 | 华为数字技术有限公司 | Method and system for keep-alive conversation table in NAT device |
| CN101753597A (en) * | 2008-12-09 | 2010-06-23 | 华为技术有限公司 | Keeping alive method between peer node and client under peer node-client architecture |
-
2011
- 2011-03-08 CN CN201110055644.7A patent/CN102111899B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050102393A1 (en) * | 2003-11-12 | 2005-05-12 | Christopher Murray | Adaptive load balancing |
| CN1946062A (en) * | 2006-10-10 | 2007-04-11 | 华为数字技术有限公司 | Method and system for keep-alive conversation table in NAT device |
| CN101753597A (en) * | 2008-12-09 | 2010-06-23 | 华为技术有限公司 | Keeping alive method between peer node and client under peer node-client architecture |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103516685A (en) * | 2012-06-25 | 2014-01-15 | 中国移动通信集团公司 | Method and system for obtaining terminal connecting state in IMS network, and equipment |
| CN104813641A (en) * | 2012-10-22 | 2015-07-29 | 交互数字专利控股公司 | Method and apparatus for negotiating "keep-alive" message frequencies of applications running on a mobile station |
| US9832101B2 (en) | 2012-10-22 | 2017-11-28 | Interdigital Patent Holdings, Inc. | Method and apparatus for negotiating “keep-alive” message frequencies of applications running on a mobile station |
| CN104813641B (en) * | 2012-10-22 | 2018-08-24 | 交互数字专利控股公司 | The method and apparatus that " keep-alive " message frequency for the application to being run on movement station is held consultation |
| CN105323721A (en) * | 2014-07-02 | 2016-02-10 | 中兴通讯股份有限公司 | Speaking right application processing method and device |
| CN105323721B (en) * | 2014-07-02 | 2019-11-19 | 南京中兴软件有限责任公司 | The processing method and processing device of the right to apply for words |
| CN105517095A (en) * | 2014-09-25 | 2016-04-20 | 北京信威通信技术股份有限公司 | Relay routing method of session boundary controller |
| CN106909446A (en) * | 2015-12-23 | 2017-06-30 | 阿里巴巴集团控股有限公司 | The keepalive method and device of a kind of application program |
| CN106909446B (en) * | 2015-12-23 | 2020-06-23 | 阿里巴巴集团控股有限公司 | Keep-alive method and device for application program |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102111899B (en) | 2014-08-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2112798B1 (en) | Service controlling in a service provisioning system | |
| EP2186310B1 (en) | Call transfer with multiple application servers in session initiation protocol-based network | |
| RU2449488C2 (en) | Session access controller, multimedia ip subsystem and registration and method for session establishing using them | |
| US20170339740A1 (en) | Media resource reservation request failure handling for voice over mobile wireless network | |
| US20100064172A1 (en) | Apparatus and method for macro operation involving a plurality of session protocol transactions | |
| EP2705647B1 (en) | Method and network entity for s-cscf server allocation in an ims based multimedia over ip network | |
| US20110225307A1 (en) | Apparatus and method for reducing responses when executing a session initiation protocol operation | |
| CA2605475C (en) | Session initiation from application servers in an ip multimedia subsystem | |
| EP2100429A2 (en) | Dynamic service triggers in communication networks | |
| CN102111899B (en) | Session keep-alive method and device | |
| CN104284360A (en) | P-CSCF fault processing method and system | |
| CN103685286A (en) | Method and device for releasing session resources | |
| CN101997850B (en) | Call management method and device for IP (Internet Protocol) multimedia subsystem | |
| CN104219705A (en) | VoLTE terminal re-registering method and device | |
| US9392032B2 (en) | Session transfer method, device and system | |
| CN101137104B (en) | Method and system for implementing resource release | |
| EP3255860B1 (en) | Crossed-invite call handling | |
| CN101212814A (en) | Service handling method, system, and network element in case the network element data fails or the network element fails | |
| EP3742695B1 (en) | Network service system and method | |
| EP3136756A1 (en) | System, device and method for implementing ring back tone service | |
| US10798246B2 (en) | Call collision resolution in a communication network | |
| CN101296100B (en) | Explicit call forwarding implementing method | |
| CN109196836B (en) | Method, system and storage medium for improving handling of internet multimedia subsystem, IMS, conversational services of a user equipment | |
| CN101163344B (en) | Method of processing call initiated from application server camouflaged by user facility | |
| KR20110043272A (en) | Method for providing instant message in multimedia system |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20140820 Termination date: 20180308 |