CN102111899B - Session keep-alive method and device - Google Patents
Session keep-alive method and device Download PDFInfo
- Publication number
- CN102111899B CN102111899B CN201110055644.7A CN201110055644A CN102111899B CN 102111899 B CN102111899 B CN 102111899B CN 201110055644 A CN201110055644 A CN 201110055644A CN 102111899 B CN102111899 B CN 102111899B
- 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.)
- Expired - Fee Related
Links
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 keep-alive method and device.
Background technology
IP Multimedia System (IP Multimedia Subsystem, referred to as IMS) be third generation partnership (3rd Generation Partnership Project, referred to as 3GPP) standard of next generation network of definition, its distinguishing feature is to have adopted session initiation protocol (Session Initiation Protocol, referred to as SIP) system.
Session keepalive be a kind of for detection of session, whether be a kind of mode living, RFC4028 has carried out expansion to Session Initiation Protocol and has realized this keepalive mechanism.RFC4028 has expanded two head: Session-Expires, Min-SE, a function choosing-item: timer (timer) is realized session keepalive audit function.According to the definition in RFC4028, the keep-alive object both sides of session keepalive must support RFC4028 Extended Protocol, and have stipulated following 3 kinds of ways of realization, are explained below:
Form one; calling subscriber (UAC) for the information of keep-alive (for example carries by initial (INVITE) request of inviting; Supported:timer; Session-Expires:90; Min-SE:90); when receiving called subscriber (UAS) or the agency (Proxy) of request, also support RFC4028; and while also wishing Run Sessions keepalive feature; can consult initiate the time interval of keep-alive at 200OK (INVITE), final result is through consultation carried out the keep-alive that the reInvite that regularly initiates or renewal (UPDATE) message carries out session and is detected.When initiatively initiating keep-alive requesting party, do not receive the response message of holding consultation in preset time, or passive receive keep-alive requesting party is not while receiving keep-alive request in the scheduled time, judges session termination, releasing session discharges resource corresponding to this session simultaneously.
Form two, after session establishment, UAC or UAS because demand in follow-up dialogue, ask Update in initiation session keep-alive request (carry RFC4028 regulation the information for keep-alive).
Form three, core network element also can come initiatively when message is forwarded to down hop, to increase the information that Session Timers is relevant according to specific strategy, shows to wish to realize Session Timers function between energy and down hop.
It is that both sides for keep-alive object define while meeting this agreement that session in RFC4028 detects.In IMS application; when all SIP network elements (comprising terminal) all must be supported RFC4028; and in application; while all wishing between each network element to use Session Timers function during session; flow process is roughly similar, and difference is mainly 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 all supports and wishes to use in session the flow chart of Session Timer according to the IMS network element of correlation technique, this figure be take the promoter of session and is initiatively required to carry out SessionTimers function as example during session, this flow process is described, this flow process is through proxy call conversation control function entity (Proxy-Call Session Control Function, referred to as P-CSCF), service call session control function entity (Serving-CSCF, referred to as S-CSCF) and query call conversation control function entity (Interrogating-CSCF, referred to as I-CSCF), as shown in Figure 1, this flow process comprises the steps:
Step S101, calling subscriber (UAC) initiates initial INVITE request message, has carried following information: Session-Expires:90, Min-SE:90, Supported:timer in this request message.These information show, terminal is supported Session Timers, and the keep-alive interval of oneself is provided.
Step S102, the P-CSCF network element of Calling Side forwards this message, and this P-CSCF acquiescence is supported Session Timers function.
Step S103, core network element I/S-CSCF network element forwarding messages, this I/S-CSCF acquiescence is supported Session Timers function.
Step S104, the P-CSCF network element forwarding messages of callee side, this core network element P-CSCF acquiescence is supported Session Timers function.
Step S105, called subscriber (UAS) receives after this message, accepts the relevant agreement of SessionTimer from caller, with being intended to open Session Timer function in 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.Called replied 200OK message after, start Session Timer timer.
Step S106, callee side P-CSCF receives after 200OK (INVITE) message, mates with local relevant information, consults successfully backward core-network side and forwards this message, and start Session Timer timer.
Step S107, core network element I/S-CSCF receives after 200OK (INVITE) message, mates with local relevant information, consults successfully backward core-network side and forwards this message, and start Session Timer timer.
Step S108, Calling Side P-CSCF, receives after 200OK (INVITE) message, mates with local relevant information, consults the successfully rear Session of startup Timer timer.
Step S109, step S110, step S111 and step S112, send and confirm that (ACK) message forwards.
Step S113, Calling Side Session Timer timer expiry, initiatively initiates Session Timer request UPDATE, and this request message comprises: Session-Expires:90, Min-SE:90.
Step S114, Calling Side P-CSCF receives Session Timer request UPDATE, kills Session Timer timer, forwards UPDATE message.
Step S 115, and core network element I/S-CSCF receives Session Timer request UPDATE, kills Session Timer timer, forwards UPDATE message.
Step S116, callee side P-CSCF receives Session Timer request UPDATE, kills Session Timer timer, forwards UPDATE message.
Step S117, called subscriber (UAS) receives the UPDATE request of Session Timer, kills Session Timer timer, replys 200OK (UPDATE).
Step S118, step S119 and step S120, the response message 200OK of the UPDATE request of forwarding Session Timer, each network element, after receiving 200OK (UPDATE), all resets Session Timer timer.
Step between step S113-step S120 will be take Session Timer timer as cycle execution, until occur that Network Abnormal or session are terminated always.
Above-mentioned step is all could carry out when session keepalive both sides all support RFC4028, and when a side of session keepalive does not support RFC4028, session keepalive just can not be carried out.
In IMS system, most core network elements (such as P/I/S-CSCF) have met RFC4028, can effectively realize session keepalive function.But the application of Session Initiation Protocol just started before 1999, RFC4028 just occurred in 2005, market within this time interval, on network, there is a large amount of sip terminals, these terminals should be can not support RFC4028, same also can exist terminal supplier not realize RFC4028 in 2005 later, once these do not support the terminal access to IMS network of RFC4208, session keepalive cannot be provided, this will be easy to cause the SIP network entity resource exhaustions such as P/I/S-CSCF, cause the 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 keep-alive method and device, at least to address the above problem.
According to an aspect of the present invention, provide a kind of session keep-alive method, having comprised: the network element of network side has received message, and determined the information for keep-alive of not carrying RFC4028 regulation in described message; Described network element arranges Session Timer, and described Session Timer then after, send the keep-alive message for keep-alive; After sending described keep-alive message or after receiving 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 determines not carry the described information for keep-alive in described message, described method also comprises: described network element sends for inquiring about the query messages of whether supporting RFC4028; Described network element receives the response message of described query messages, determines that the transmit leg of this response message is not supported RFC4028 according to the response message of described query messages, and described Session Timer then after, send described keep-alive message.
Preferably, described query messages is option OPTION message.
Preferably, described network element adds the information for keep-alive of RFC4028 regulation in the described message receiving, and sends described message; Described network element receives the response message of described message, and judges according to the information for keep-alive that whether carries 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 is not in the situation that the transmit leg of described response message is supported RFC4028, described Session Timer then after, send described keep-alive message.
Preferably, in the situation that described network element is determined the transmit leg support RFC4028 of this response message, described method also comprises; 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 of consulting.
Preferably, in the situation that described response message also carries the 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, for receiving message, and determine the information for keep-alive of not carrying RFC4028 regulation in described message; Session Timer arranges module, for Session Timer is set; The first sending module, for described Session Timer then after, send the keep-alive message for keep-alive; The regular device of described session arranges module, also, for after sending described keep-alive message or after receiving the keep-alive response message in response to described keep-alive message, restarts described Session Timer.
Preferably, this device also comprises: the second sending module, for after determining that described message is not carried the described information for keep-alive, sends for inquiring about the query messages of whether supporting RFC4028; Described the first sending module is also in the situation that determine that according to the response message of described query messages the transmit leg of this response message do not support RFC4028, and described Session Timer then after, send described keep-alive message.
Preferably, this device also comprises: the 3rd sending module, for add the information for keep-alive of RFC4028 regulation in the described message receiving, and sends described message; Described the first sending module, also in the situation that the information for keep-alive that whether carries RFC4028 regulation according to the response message of described message determines that the transmit leg of the response message of described message do not support RFC4028; And described Session Timer then after, send described keep-alive message.
By the present invention, solved the problem of not supporting RFC4028 can not provide session keepalive in correlation technique and causing, and then the support of session keepalive when not supporting RFC4028 is provided.
Accompanying drawing explanation
Accompanying drawing described herein is used to provide a further understanding of the present invention, forms the application's a part, and schematic description and description of the present invention is used for explaining the present invention, does not form inappropriate limitation of the present invention.In the accompanying drawings:
Fig. 1 all supports and wishes to use in session the flow chart of Session Timer according to the IMS network element of correlation technique;
Fig. 2 is according to the flow chart of the session keep-alive method of the embodiment of the present invention;
Fig. 3 is according to the structured flowchart of the session keepalive device of the embodiment of the present 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 according to the Calling Side core network element of the embodiment of the present invention flow chart that the session between same caller detects;
Fig. 7 initiatively initiates according to the callee side core network element of the embodiment of the present invention flow chart detecting with the session between called.
Embodiment
Hereinafter with reference to accompanying drawing, also describe the present invention in detail in conjunction with the embodiments.It should be noted that, in the situation that not conflicting, embodiment and the feature in embodiment in the application can combine 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 apply.
In the present embodiment, provide session keep-alive method, Fig. 2 is according to the flow chart of the session keep-alive method of the embodiment of the present invention, and as shown in Figure 2, this flow process comprises the following steps:
Step S202, the network element of network side receives message, and determines the information for keep-alive of not carrying RFC4028 regulation in this message;
Step S204, this network element arranges Session Timer, and above-mentioned Session Timer then after, send the keep-alive message for keep-alive;
Step S206, after sending keep-alive message or after receiving the keep-alive response message in response to keep-alive message, network element is restarted Session Timer.
By above-mentioned steps, network element, when receiving message, even if do not carry the information for keep-alive in this message, also can initiatively arrange Session Timer, thereby realize keep-alive.For example; this network element can send the information for keep-alive that carries RFC4028 regulation to called subscriber or other network elements; after receiving response message; due to called subscriber or other network elements support RFC4028; therefore in response message, can not carry the information for keep-alive, now this network element can initiatively carry out keep-alive execution above-mentioned steps S204 and step S206.
When implementing, receive the information of not carrying in message for keep-alive and can not illustrate that the transmit leg of this message supports 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 and is not carried the information for keep-alive in message, send for inquire about whether support RFC4028 query messages (for example, this query messages can be option OPTION message), after this network element receives the response message of query messages, according to the response message of this query messages, determine that the transmit leg of this response message do not support RFC4028, and described Session Timer then after, send described keep-alive message.Or this network element can add the information for keep-alive of RFC4028 regulation in the message receiving, and sends this message; After receiving the response message of this message, according to the information for keep-alive that whether carries RFC4028 regulation in the response message of this message, judge whether the transmit leg of the response message of this message supports RFC4028; This network element is not in the situation that the transmit leg of this response message is supported RFC4028, 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; network element can carry out with the transmit leg of response message the negotiation of the session keepalive of RFC4028 regulation, and carries out session keepalive (carrying out the step of RFC4028 regulation) according to the result of consulting.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 with type (for example, invite INVITE, upgrade UPDATE message).
In the present embodiment; a kind of session keepalive device is also provided, and this device is arranged in the network element of network side, and this device is used for realizing above-described embodiment and preferred implementation thereof; carried out repeating no more of explanation, below the module relating in this device had been described.Fig. 3 is according to the structured flowchart of the session keepalive device of the embodiment of the present invention, and as shown in Figure 3, this device comprises: receiver module 32, Session Timer arranges module 34, the first sending modules 36.Below this structure is described.
Receiver module 32, for receiving message, and determines the information for keep-alive of not carrying RFC4028 regulation in this message; Session Timer arranges module 34 and is connected to receiver module 32, and this module is used for arranging Session Timer; The first sending module 36 is connected to Session Timer module 34 is set, this module for Session Timer then after, send the keep-alive message for keep-alive; Session Timer arranges module 34 also for after sending this keep-alive message or after receiving 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: the second sending module, this module, for after definite this message is not carried the information for keep-alive, sends for inquiring about the query messages of whether supporting RFC4028.The first sending module 36 is in the situation that determine that according to the response message of this query messages the transmit leg of this response message do not support RFC4028, 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 receiving the information for keep-alive of RFC4028 regulation, and sends this message.The first sending module 36, in the situation that the information for keep-alive that whether carries RFC4028 regulation according to the response message of this message determines that the transmit leg of the response message of this message do not support RFC4028; And Session Timer then after, send this keep-alive message.
The IP Multimedia System (IMS) of take below describes in conjunction with the preferred embodiments as example.
In this preferred embodiment, when IMS access side core network element (take P-CSCF network element describe for example) is the Calling Side in session, need to be before session establishment in initial INVITE or dialogue INVITE extract relevant information in RFC4028 UPDATE and identify the promoter (UAC) of session and 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 session establishment success (success that receives initial INVITE shake hands ACK message or receive the 200OK message of INVITE); a session keepalive timer is set; refresh timer, can follow RFC4028 agreement, and the minimum duration of this timer is 90 seconds.Then, to the promoter of session, send this terminal of Options requesting query and whether support RFC4028.When the promoter of session supports RFC4028; P-CSCF network element can be initiated in the overtime rear active of refresh timer INVITE or Update message (when capability query result shows that terminal is supported UPDATE method) in dialogue to the promoter of session; come the time of consulting session keep-alive machine-processed with terminal (comprising time, active promoter), detailed process is followed RFC4028.When handling capacity inquiry is obtained terminal and is not really supported RFC4028, P-CSCF network element is initiated NVITE or Update message (when capability query result shows that terminal is supported UPDATE method) in dialogue in the overtime rear active of refresh timer to terminal, again starts this refresh timer simultaneously.
When session keepalive request timed out, do not receive response message and think Network Abnormal or terminal abnormal; P-CSCF network element judgement terminal abnormal or current sessions are abnormal; discharge related resource; initiatively to network, survey and initiate release message BYE simultaneously; so that adjacent network elements also can discharge abnormal resource as early as possible, effectively for other sessions provide service.When session keepalive request, received after response message, shown in the normal use of session, after refresh timer timer expiry, again initiatively initiate request, circulation is until session release successively.
Fig. 6 initiatively initiates according to the Calling Side core network element of the embodiment of the present invention flow chart that the session between same caller detects, and as shown in Figure 6, this flow process comprises the following steps:
Step S601, P-CSCF receives the SIPINVITE message from Calling Side, in this information without Session Timer relevant information.
Step S602, P-CSCF forwarding messages.
Step S603, P-CSCF receives the 200OK (INVITE) from callee side; P-CSCF by extracting the Session Timer relevant information of Calling Side from INVITE and 200OK (INVITE), and result is " without Session Timer relevant information ".
Step S604, P-CSCF forwards 200OK (INVITE) to terminal; P-CSCF arranges session keepalive timer, refresh timer, and duration is 90s.
Step S605, P-CSCF sends out OPTIONS message, the ability of inquiry caller.
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:
The first, both all exist, and show that calling subscriber has supported RFC4028.After the timer expiry that P-CSCF can arrange at S204, to Calling Side, initiate UPDATE request, carry out Session Timer negotiation.
The second, only has Supported:timer, shows terminal support RFC4028, but do not support UPDATE method (RFC3311), after the timer expiry that P-CSCF can arrange at S204, to Calling Side, initiate the INVITE request in dialogue, carry out Session Timer negotiation.
The third, only have Allow:UPDATE, shows that so terminal do not support RFC4028, after the timer expiry that P-CSCF can arrange at S204, to Calling Side, initiates the UPDATE request in dialogue.
The 4th kind, neither exist, after the timer expiry that P-CSCF can arrange at S204, to Calling Side, initiate the INVITE request in dialogue.
This figure is for the third.The processing of the first, the second is exactly to have followed RFC4028 substantially, the third, the 4th kind of situation be the same in fact, just the requesting method of session keepalive is different.So UPDATE method does not exist will be simpler on the flow chart of shaking hands.
Step S607, the refresh timer that step S604 arranges is overtime, and P-CSCF initiates SIP UPDATE message to Calling Side.
Step S608, P-CSCF receives 200OK (UPDATE); Then reset refresh timer timer.
Step S609, the refresh timer that step S607 arranges is overtime, and P-CSCF initiates SIP UPDATE message to Calling Side.
Step S610, P-CSCF receives 200OK (UPDATE); Then reset refresh timer timer.
Step S607-S610 will take refresh timer as interval regular circulation carry out, until session termination, or occur that network etc. is abnormal.
Step S611, P-CSCF initiates UPDATE request again because refresh timer is overtime.
Step S612, when occurring Network Abnormal, or during the nonreply of UPDATE request timed out, P-CSCF network element is judged terminal abnormal, session termination, 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), releasing session related resource.
When the callee side of P-CSCF network element in session, for called subscriber, P-CSCF network element is the promoter of initial message.P-CSCF network element receives when the initial INVITE request forwarding, and P-CSCF network element need to check in this request message, whether there is the characteristic attribute in RFC4028.While there is not the information of session keepalive in initial INVITE, initiatively in message, add: Supported:timer, Session-Expires=90, the heads such as Min-SE=90.When receiving the final success response 200OK of initial request, need to check whether have session keepalive relevant information.When determining while there is not session keepalive relevant information, substantially show that terminal called do not support RFC4028, need to arrange a session keepalive timer, refresh timer, can follow RFC4028 agreement, and the minimum duration of this timer is 90 seconds.Before conversation end, when this timer expiry, P-CSCF network element is initiatively asked INVITE or UPDATE message in called initiation dialogue, again starts refreshtimer timer simultaneously.When request timed out receives response, do not judge that the session of terminal therewith occurs extremely, need to discharging immediately related resource, and to network, survey and initiatively initiate BYE message simultaneously, to notify other network element releasing resources.Session keepalive request is sent, and has received response, shows in the normal use of session, again initiatively initiates request after refresh timer timer expiry, and circulation is until session release successively.
Fig. 7 initiatively initiates with the session overhaul flow chart between called according to the callee side core network element of the embodiment of the present invention, and as shown in Figure 7, this flow process comprises the following steps:
Step S701, the P-CSCF of callee side receives the SIP INVITE of core net.
Step S702, P-CSCF extracts Session Timer relevant information from SIP INVITE, if do not extract relevant information, P-CSCF network element initiatively adds Session Timer relevant information before message forwards: Session-Expires:90, Min-SE:90.
Step S703, P-CSCF receives the response message 200OK (INVITE) from called subscriber (UAS), checks in code stream whether have Session Timer relevant information, and has Require:timer.Two conditions above have 4 kinds of possibilities:
The first, when both exist simultaneously, shows that terminal supports RFC4028, and wishes in session, to carry out this function, and P-CSCF can start session keepalive timer: refresh timer, the time that this time also consults in 200OK is as the criterion.
The second, only has Require:timer, and this situation also shows terminal support RFC4028, and is willing to be intended to carry out Sesssion Timer function during session.P-CSCF can start session keepalive timer: refresh timer, the time that this time adds during with Forward-reques is as the criterion.
The third, when only having Session Timer relevant information, without Require:timer, show that terminal do not support RFC4028, and P-CSCF can start session keepalive timer, refresh timer, and duration is followed RFC4028, and value minimum is 90s.
The 4th kind, both equal nothings, this situation is equal to the third, shows the called RFC4028 that do not support, the now processing of P-CSCF and the third is similar substantially, this Fig. 7 is the processing of the third situation.The first, the second show terminal support RFC4028, and RFC4028 is also followed in follow-up processing.
Step S704, P-CSCF forwards 200OK (INVITE).
Step S705, the Session Timer timer refresh timer arranging in the 3rd, 4 kinds of situations in step S703 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, 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 take refreshtimer as interval regular circulation carry out, until session termination, or occur that network etc. is abnormal.
Step S709, when refreshtimer timer expiry, P-CSCF sends out session keepalive request SIPUPDATE message to terminal, and request timed out is not received response message, and P-CSCF judgement Network Abnormal or terminal abnormal, determine end call.
Step S710, P-CSCF sends BYE message to network side, notifies other network element releasing session related resources P-CSCF in this session to receive 200OK (BYE), discharges this session related resource, conversation end.
Preferably, in above-mentioned steps, P-CSCF can be the network element of supporting arbitrarily RFC4028, includes but not limited to: P/I/S-CSCF, AGCF, SBC, Application-Service etc.When SIP network element both sides do not support RFC4028, the network element on core network also can be realized session protection mechanism according to above-described embodiment and preferred implementation thereof.
Preferably, the session keepalive request message in above-mentioned steps includes but not limited to INVITE, UPDATE message, OPTIONS message etc.
Preferably, in above-mentioned steps, the session keepalive of callee side can also adopt the similar method of same Calling Side: after receiving the handshake information ACK of success response, initiatively to terminal called initiating capacity inquiry request, further to understand the ability of terminal.
In sum, by above-described embodiment, solved in correlation technique and do not supported the problem that RFC4028 can not provide session keepalive to cause to provide the support to session keepalive 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 general calculation element, they can concentrate on single calculation element, or be distributed on the network that a plurality of calculation elements form, alternatively, they can be realized with the executable program code of calculation element, thereby, they can be stored in storage device and be carried out by calculation element, and in some cases, can carry out shown or described step with the order being different from herein, or they are made into respectively to each integrated circuit modules, or a plurality of modules in them or step are made into single integrated circuit module to be realized.Like this, the present invention is not restricted to any specific hardware and software combination.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any modification of doing, be equal to replacement, improvement etc., within all should being included in protection scope of the present invention.
Claims (10)
1. a session keep-alive method, is characterized in that comprising:
The network element of network side receives message, and determines the information for keep-alive of not carrying RFC4028 regulation in described message;
Described network element arranges Session Timer, and described Session Timer then after, send the keep-alive message for keep-alive;
After sending described keep-alive message or after receiving 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 determines not carry the described information for keep-alive in described message, described method also comprises: described network element sends for inquiring about the query messages of whether supporting RFC4028;
Described network element receives the response message of described query messages, determines that the transmit leg of this response message is not supported RFC4028 according to the response message of described query messages, 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 option OPTION message.
4. method according to claim 1, is characterized in that,
Described network element adds the information for keep-alive of RFC4028 regulation in the described message receiving, and sends described message;
Described network element receives the response message of described message, and judges according to the information for keep-alive that whether carries 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 is not in the situation that the transmit leg of described response message is supported RFC4028, described Session Timer then after, send described keep-alive message.
5. according to the method described in any one in claim 2 to 4, it is characterized in that, in the situation that described network element is determined the transmit leg support RFC4028 of this response message, described method also comprises;
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 of consulting.
6. according to the method described in any one in claim 2 to 4; it is characterized in that; in the situation that described response message also carries the 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 or upgrade UPDATE message.
8. a session keepalive device, is arranged in the network element of network side, it is characterized in that comprising:
Receiver module, for receiving message, and determines the information for keep-alive of not carrying RFC4028 regulation in described message;
Session Timer arranges module, for Session Timer is set;
The first sending module, for described Session Timer then after, send the keep-alive message for keep-alive;
The regular device of described session arranges module, also, for after sending described keep-alive message or after receiving 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: the second sending module, for after determining that described message is not carried the described information for keep-alive, sends for inquiring about the query messages of whether supporting RFC4028;
Described the first sending module is also in the situation that determine that according to the response message of described query messages the transmit leg of this response message do not support RFC4028, 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, for add the information for keep-alive of RFC4028 regulation in the described message receiving, and sends described message;
Described the first sending module; also in the situation that the information for keep-alive that whether carries RFC4028 regulation according to the response message of described message determines that the transmit leg of the response message of described message do not support 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 CN102111899A (en) | 2011-06-29 |
| CN102111899B true 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) |
Families Citing this family (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 |
| KR20150084017A (en) | 2012-10-22 | 2015-07-21 | 인터디지탈 패튼 홀딩스, 인크 | Method and apparatus for negotiating "keep-alive" message frequencies of applications running on a mobile station |
| 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 |
| CN106909446B (en) * | 2015-12-23 | 2020-06-23 | 阿里巴巴集团控股有限公司 | Keep-alive method and device for application program |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7421695B2 (en) * | 2003-11-12 | 2008-09-02 | Cisco Tech Inc | System and methodology for adaptive load balancing with behavior modification hints |
-
2011
- 2011-03-08 CN CN201110055644.7A patent/CN102111899B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102111899A (en) | 2011-06-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9160570B2 (en) | Systems and method for enabling IP signaling in wireless networks | |
| EP2112798B1 (en) | Service controlling in a service provisioning system | |
| EP2186310B1 (en) | Call transfer with multiple application servers in session initiation protocol-based network | |
| US7877487B2 (en) | Dynamic service triggers in communication networks | |
| US10212192B2 (en) | Systems and methods for interworking with over the top applications in communications network | |
| CN102111899B (en) | Session keep-alive method and device | |
| CN101997850B (en) | Call management method and device for IP (Internet Protocol) multimedia subsystem | |
| CN104219705A (en) | VoLTE terminal re-registering method and device | |
| CN101137104B (en) | Method and system for implementing resource release | |
| US9392032B2 (en) | Session transfer method, device and system | |
| CN102026365A (en) | Group registration method, IP multimedia sub-system and multiuser access equipment | |
| 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 | |
| CN102487341B (en) | Talk detection method, device and session initial protocol server | |
| US11632405B2 (en) | Proxy-call session control function (P-CSCF) restoration | |
| EP3742695A1 (en) | Network service system and method | |
| US20120290733A1 (en) | Method of establishing communication in a communications network | |
| JP6234272B2 (en) | Session control method, SIP server, and program for controlling transmission timing of early media | |
| CN109996169B (en) | Method and device for acquiring position information of called user | |
| US10798246B2 (en) | Call collision resolution in a communication network | |
| CN101296100B (en) | Explicit call forwarding implementing method | |
| US20100153559A1 (en) | Method and Apparatus for Suspending Network Based Services | |
| CN102045318A (en) | User processing method of application server and application server | |
| 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 |
Granted publication date: 20140820 Termination date: 20180308 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |