Summary of the invention
Technical problem to be solved by this invention, delivery system and the method that need to provide a kind of local IP access to connect are provided, after changing at Mobility Management Entity, to discharge local IP access, connect.
In order to solve the problems of the technologies described above, the method for releasing that at first the present invention provides a kind of local IP access to connect, discharge the local IP access lost efficacy after changing for Mobility Management Entity and connect, and the method comprises:
Whether the former Mobility Management Entity of serving terminal before change is served target local IAD identification information or Target Wireless side network element ID information or the target home base station gateway identification information of described terminal after obtaining change, and connect effective according to described identification information judgment local IP access; Perhaps
Whether the target mobility management entity of serving described terminal after change is served former local IAD identification information or former wireless side network element ID information or the former home base-station gateway identification information of described terminal before obtaining change, and connect and lost efficacy according to described identification information judgment local IP access;
Described former Mobility Management Entity discharges the local IP access lost efficacy and connects.
Preferably, described change comprises by the switching of terminal described in long evolving system or tracing section updating and causing, or caused by reorientation or the Routing Area Update of terminal described in the universal mobile telecommunications system land wireless access system.
Preferably, in described tracing section updating flow process, described terminal sends the tracing section updating request message to described Target Wireless side network element, described Target Wireless side network element is after described terminal is selected described target mobility management entity, and described tracing section updating request message is transmitted to described target mobility management entity; When described Target Wireless side entity is supported local IP access, described target mobility management entity sends to the identification information that carries described target local IAD or Target Wireless side entity in the context request message of described former Mobility Management Entity, and whether described former Mobility Management Entity connects and lost efficacy according to the described local IP access of the identification information judgment of described target local IAD or Target Wireless side entity;
In described Routing Area Update process, described terminal sends the Routing Area Update request message to described Target Wireless side network element, described Target Wireless side network element is that described terminal is selected described target mobility management entity, and described Routing Area Update request message is transmitted to described target mobility management entity; When described Target Wireless side entity is supported local IP access, described target mobility management entity sends to the identification information that carries described target local IAD or Target Wireless side entity in the context request message of described former Mobility Management Entity, and whether described former Mobility Management Entity connects and lost efficacy according to the described local IP access of the identification information judgment of described target local IAD or Target Wireless side entity.
Preferably, after described former Mobility Management Entity is received described context request message, check and whether exist local IP access to connect, exist and further judge that whether the identification information of described target local IAD is consistent with the identification information of described former local IAD, inconsistent local IP access Joint failure, perhaps further judge that whether the identification information of described Target Wireless side entity is consistent with the identification information of described former wireless side entity, inconsistent local IP access Joint failure.
Preferably, when described Target Wireless side entity is not supported local IP access, described target mobility management entity sends to the identification information that does not carry described target local IAD or Target Wireless side entity in the context request message of described former Mobility Management Entity, perhaps do not carry the identification information of described target local IAD or Target Wireless side entity and carry the indication information of not supporting local IP access, described former Mobility Management Entity is according to the described context request message of the identification information that does not carry described target local IAD or Target Wireless side entity or the described context request message of carrying described indication information, judge described local IP access Joint failure.
Preferably, in described switching or redirection process, described former wireless side network element sends handover request message to described former Mobility Management Entity, and described handover request message is carried the identification information of described target local IAD; Whether described former Mobility Management Entity receives after described handover request message according to the identification information of described target local IAD, judge that described local IP access connects to lose efficacy.
Preferably, in described handoff procedure or redirection process, do not carry the identification information of described target local IAD in described handover request message, the local IP access Joint failure.
Preferably, after described former Mobility Management Entity is received described handover request message, check and whether exist local IP access to connect, further judge that whether the identification information of described target local IAD is consistent with the identification information of described former local IAD, inconsistent local IP access Joint failure while existing.
Preferably, after described former Mobility Management Entity is judged the local IP access connection of inefficacy, the local IP access that the beared information sent to described target mobility management entity does not comprise described inefficacy connects.
Preferably, in described tracing section updating process, described terminal sends the tracing section updating request message to described Target Wireless side network element, described Target Wireless side network element is after described terminal is selected described target mobility management entity, and described tracing section updating request message is transmitted to described target mobility management entity; Described target mobility management entity sends context request message to described former Mobility Management Entity, while existing local IP access to connect, carry the identification information of described former local IAD or former wireless side entity in the context response information that described former Mobility Management Entity sends to described target mobility management entity, whether described target mobility management entity connects and lost efficacy according to the described local IP access of the identification information judgment of described former local IAD or former wireless side entity;
In described Routing Area Update process, described terminal sends the Routing Area Update request message to described Target Wireless side network element, described Target Wireless side network element is that described terminal is selected described target mobility management entity, and described Routing Area Update request message is transmitted to described target mobility management entity; Described target mobility management entity sends context request message to described former Mobility Management Entity, while existing local IP access to connect, carry the identification information of described former local IAD or former wireless side entity in the context response information that described former Mobility Management Entity sends to described target mobility management entity, whether described target mobility management entity connects and lost efficacy according to the described local IP access of the identification information judgment of described former local IAD or former wireless side entity.
Preferably, after described target mobility management entity is received described context response information, check and whether exist local IP access to connect, further judge that whether whether the identification information of described former local IAD consistent with the identification information of described target local IAD while existing, inconsistent local IP access Joint failure, whether whether the identification information that perhaps judges described former wireless side entity consistent with the identification information of described Target Wireless side entity, inconsistent local IP access Joint failure; Local IP access Joint failure while not existing local IP access to connect.
Preferably, while not existing local IP access to connect, do not carry the identification information of described former local IAD or former wireless side entity in the context response information that described former Mobility Management Entity sends to described target mobility management entity, or do not carry the identification information of described former local IAD or former wireless side entity and carry the indication information that does not exist local IP access to connect.
Preferably, in described handoff procedure, described former wireless side network element sends handover request message to described former Mobility Management Entity, described former Mobility Management Entity is after described terminal is selected described target mobility management entity, send the reorientation forwarding request message of the identification information that carries described former local IAD or former wireless side entity to described target mobility management entity, described target mobility management entity sends handover request message to described Target Wireless side network element, described Target Wireless side network element sends switching request acknowledgement message to described target mobility management entity, described switching request acknowledgement message is carried the identification information of described target local IAD or Target Wireless side entity, whether described target mobility management entity connects and lost efficacy according to the described local IP access of the identification information judgment of described target local IAD or Target Wireless side entity,
In described redirection process, described former wireless side network element sends the handover request message of the identification information that carries Target Wireless side network element to described former Mobility Management Entity, described former Mobility Management Entity is after described terminal is selected described target mobility management entity, send the reorientation forwarding request message of the identification information that carries described former local IAD or former wireless side entity to described target mobility management entity, described target mobility management entity sends RELOCATION REQUEST message to described Target Wireless side network element, described Target Wireless side network element sends the re-positioning request acknowledgement message to described target mobility management entity, described re-positioning request acknowledgement message carries the identification information of described target local IAD or Target Wireless side entity, whether described target mobility management entity connects and lost efficacy according to the described local IP access of the identification information judgment of described target local IAD or Target Wireless side entity.
Preferably, after described target mobility management entity is received described reorientation forwarding request message, check and whether exist local IP access to connect, further judge that whether whether the identification information of described former local IAD consistent with the identification information of described target local IAD, inconsistent local IP access Joint failure while existing.
Preferably, described target mobility management entity is responded the local IP access Indication of Losing Efficacy by message to described former Mobility Management Entity after judging the local IP access connection of inefficacy.
Preferably, described former Mobility Management Entity and/or target mobility management entity comprise the Serving GPRS Support Node in mobile management unit, the mobile switching centre in global system for mobile communications or the universal mobile telecommunications system land wireless access system in long evolving system.
Preferably, the identification information of described target local IAD, comprise the address of described target local IAD or be exclusively used in the identification information that identifies described target local IAD;
The identification information of described Target Wireless side network element, comprise the address of described Target Wireless side network element or be exclusively used in the identification information that identifies described Target Wireless side network element;
The identification information of described target home base station gateway, comprise the address of described target home base station gateway or be exclusively used in the identification information that identifies described target home base station gateway;
The identification information of described former local IAD, comprise the address of described former local IAD or be exclusively used in the identification information that identifies described former local IAD;
The identification information of described former wireless side network element, comprise the address of described former wireless side network element or be exclusively used in the identification information that identifies described former wireless side network element;
The identification information of described former home base-station gateway, comprise the address of described former home base-station gateway or be exclusively used in the identification information that identifies described former home base-station gateway.
In order to solve the problems of the technologies described above, the delivery system that the present invention also provides a kind of local IP access to connect, discharge the local IP access lost efficacy after changing for Mobility Management Entity and connect, this system comprises before change the former Mobility Management Entity of serving terminal, wherein:
Described former Mobility Management Entity is served target local IAD identification information or Target Wireless side network element ID information or the target home base station gateway identification information of described terminal after being arranged to obtain change, and whether effectively also discharges the local IP access connection of losing efficacy according to described identification information judgment local IP access connection.
In order to solve the problems of the technologies described above, the delivery system that the present invention also provides another kind of local IP access to connect, discharging the local IP access lost efficacy after changing for Mobility Management Entity connects, this system comprise before change the former Mobility Management Entity of serving terminal and change after serve the target mobility management entity of described terminal, wherein:
Described target mobility management entity is arranged to obtain before change former local IAD identification information or former wireless side network element ID information or the former home base-station gateway identification information of serving described terminal, and, after going out the local IP access Joint failure according to described identification information judgment, by message, to described former Mobility Management Entity, respond the local IP access Indication of Losing Efficacy;
Described former Mobility Management Entity is arranged to discharge according to described local IP access Indication of Losing Efficacy the local IP access lost efficacy and is connected.
Compared with prior art, the system and method for local IP access Connection Release provided by the invention, solved after Mobility Management Entity changes the inefficacy brought and connected the problem how to discharge.
Embodiment
Describe embodiments of the present invention in detail below with reference to drawings and Examples, to the present invention, how the application technology means solve technical problem whereby, and the implementation procedure of reaching technique effect can fully understand and implement according to this.
The method of the local IP access Connection Release that the present invention proposes, in the flow process of switching, reorientation, tracing section updating or Routing Area Update, the Mobility Management Entity of serving terminal before switching, reorientation, tracing section updating or Routing Area Update is the identification information that former Mobility Management Entity obtains target local IAD, Target Wireless side network element or target home base station gateway, and, according to this identification information, judge whether the LIPA connection lost efficacy; Wherein target local IAD, Target Wireless side network element and target home base station gateway, be respectively after this switching, reorientation, tracing section updating or Routing Area Update that the local access network of serving terminal closes, wireless side network element or home base-station gateway;
For the LIPA lost efficacy, connect, former Mobility Management Entity, when the Mobility Management Entity send to need activated or the beared information of switching is served terminal after sending to switching, reorientation, tracing section updating or Routing Area Update is target mobility management entity, does not send the beared information that the LIPA of this inefficacy connects; Perhaps
In the flow process of switching, reorientation, tracing section updating or Routing Area Update, target mobility management entity obtains the identification information of former local IAD, former wireless side network element or former home base-station gateway, and, according to this identification information, judge whether the LIPA connection lost efficacy.For the LIPA lost efficacy, connect, target mobility management entity is notified former Mobility Management Entity LIPA Joint failure.Wherein former local IAD, former wireless side network element and former home base-station gateway, be respectively before this switching, reorientation, tracing section updating or Routing Area Update that the local access network of serving terminal closes, wireless side network element or home base-station gateway.
Wherein, the identification information of above-mentioned target local IAD, comprise the address of target local IAD or be exclusively used in the identification information that identifies the target local IAD; The identification information of above-mentioned Target Wireless side network element, comprise the address of Target Wireless side network element or be exclusively used in the identification information that identifies Target Wireless side network element; The identification information of above-mentioned target home base station gateway, comprise the address of target home base station gateway or be exclusively used in the identification information that identifies the target home base station gateway.
Wherein, the identification information of above-mentioned former local IAD, comprise the address of former local IAD or be exclusively used in the identification information that identifies former local IAD; The identification information of above-mentioned former wireless side network element, comprise the address of former wireless side network element or be exclusively used in the identification information that identifies former wireless side network element; The identification information of above-mentioned former home base-station gateway, comprise the address of former home base-station gateway or be exclusively used in the identification information that identifies former home base-station gateway.
For the LIPA lost efficacy, connect, former Mobility Management Entity discharges this LIPA and connects.
Wherein, the identification information that former Mobility Management Entity obtains is transmitted by target mobility management entity.The identification information that target mobility management entity obtains is transmitted by former Mobility Management Entity.
Wherein, the identification information that local access network closes can be the address that local access network closes, or is exclusively used in the identification information that the sign local access network closes.The identification information of wireless side network element can be the address of wireless side network element, or is exclusively used in the identification information of sign wireless side network element.
Wherein, the wireless side entity can be base station, base station from home or radio network controller (RadioNetwork Controller, referred to as RNC).Mobility Management Entity can be (the Mobility Management Entity of the mobile management unit in the LTE system, referred to as MME), (the Mobile Switching Centre of mobile switching centre in global system for mobile communications (GSM), referred to as MSC) or the UTRAN system in Serving GPRS Support Node (Serving GPRS Support Node, referred to as SGSN).It can be L-SGW, L-PGW or L-GGSN that local access network closes.The core net IAD can be S-GW or SGSN.
Fig. 3 is the schematic flow sheet of first embodiment of the invention.First embodiment of the invention is local IP access Connection Release process in the tracing section updating process in Long Term Evolution LTE system, in conjunction with the network diagram shown in Fig. 1 (a), Fig. 1 (b) and Fig. 1 (c), first embodiment of the invention mainly comprises the steps:
Step 301, the terminal of Idle state is regularly or due to the mobile tracking area list initiating updating of tracking area flow process that changes that causes; It is the wireless side network element of Terminal Service (being referred to as Target Wireless side network element) that terminal transmission Non-Access Stratum (Non-Access-Stratum, referred to as NAS) message-tracing section updating request message is given current.After fast mobile terminal, this Target Wireless side network element may enter Idle state wireless side network element (being referred to as former wireless side network element) difference before with terminal.
Step 302, Target Wireless side network element is that terminal is selected to be currently serviced in the Mobility Management Entity (being referred to as target mobility management entity) of terminal, and the tracing section updating request message is included in S1 message and issues target mobility management entity; If there is home base-station gateway, first this tracing section updating request is transmitted to home base-station gateway, and then by home base-station gateway select target Mobility Management Entity, and this tracing section updating request message is issued to target mobility management entity.
Wherein, in the LTE system, Mobility Management Entity is MME.
Step 303, target mobility management entity is according to the tracing section updating request message, obtain the address that terminal enters Idle state Mobility Management Entity (being referred to as former Mobility Management Entity) before, and initiate context to former Mobility Management Entity and obtain flow process; Target mobility management entity sends context request message to former Mobility Management Entity, and carries the identification information of target local IAD or the identification information of Target Wireless side entity in context request message.
When the Target Wireless side entity is supported local IP access, carry identification information or the Target Wireless side entity identification information of target local IAD in message.
When the Target Wireless side entity is not supported local IP access, the identification information or the Target Wireless side entity identification information that can in message, not carry the target local IAD mean not support local IP access; Perhaps in message, by indication information, indicate and do not support local IP access.
Wherein, the identification information that local access network closes can be the address that local access network closes, or is exclusively used in the identification information that the sign local access network closes; The identification information of wireless side network element can be the address of wireless side network element, or is exclusively used in the identification information of sign wireless side network element.
Wherein, the identification information that local access network closes refers to the address of L-PGW.
Whether step 304, after former Mobility Management Entity is received context request message, check whether terminal exists local IP access to connect, if the LIPA that exists identification information in request message based on context or indication information to check terminal connects, be affected.
For the terminal that exists local IP access to connect:
In message, carry be the identification information of target local IAD the time, former Mobility Management Entity checks that whether the identification information of the local access network pass that the terminal local IP access connects is consistent with the identification information of the target local IAD carried in context request message, if consistent think that local access network that LIPA connects closes and do not change, the LIPA of terminal connects unaffected; If think that inconsistent variation has occurred in the local access network pass that LIPA connects, the LIPA of terminal connects to be needed to discharge.During the identification information that the local access network that the terminal local IP access connects closes is kept at context when terminal is set up the LIPA connection.
In message, carry be the identification information of Target Wireless side network element the time, former Mobility Management Entity checks that whether the wireless side network element ID information of terminal local IP access connection is consistent with the identification information of the Target Wireless side network element carried in message, if unanimously think, terminal is still from former wireless side network element access, and the LIPA of terminal connects unaffected; If think that inconsistent terminal is from new wireless side network element access, the LIPA of terminal connects to be needed to discharge; During the wireless side network element ID information that the terminal local IP access connects is kept at context when terminal is set up the LIPA connection, and when entering Idle state, terminal do not discharge.
When not carrying any identification information or carrying the indication information of not supporting local IP access in message, expression Target Wireless side network element is not supported local IP access, and the local IP access of terminal connects to be needed to discharge.
Step 305, former Mobility Management Entity is included in the contextual information of terminal in context response information, issues target mobility management entity, carries in context response information and needs the beared information activated or be referred to as beared information to be activated; According to the judged result of step 304, local IP access connects to be needed to discharge, and does not need to carry the beared information of this connection in context response information, in order to complete the release of losing efficacy and connecting.
Step 306, target mobility management entity may be initiated the authentication flow process to terminal.
Step 307, target mobility management entity is responded context acknowledgement message to former Mobility Management Entity.
Step 308,309, target mobility management entity is initiated session establishment and the bearer update flow process that core net connects.
Step 310, target mobility management entity is to Authentication Authorization server launch position new technological process more.
Step 311, the Authentication Authorization server is deleted flow process to former Mobility Management Entity launch position.
Step 312, former Mobility Management Entity may be deleted to core net S-GW initiation session.
Step 313, former Mobility Management Entity, according to the judged result of step 304, is initiated the LIPA session to former local IAD and is deleted flow process; This step can be carried out any time after step 304.
Step 314,315, target mobility management entity sends Routing Area Update and accepts to terminal.
In the present embodiment, local access network closes as L-PGW and L-SGW, and it is example near being positioned at wireless side network element or its that the present embodiment be take L-PGW and L-SGW, and the release flow process of terminal local IP access connection be described when Mobility Management Entity changes.When L-SGW does not exist, the Connection Release flow process is similar to this flow process, and difference is that MME needs directly and L-PGW carries out interacting message, no longer includes the participation of L-SGW in flow process, no longer describes in detail herein.
Discharge flow process while for L-SGW, being positioned at core net identical with this flow process, just MME needs and the SGW of core net carries out interacting message, then by core net SGW notice L-PGW, rather than notifies L-PGW by L-SGW, herein detailed description no longer.
Fig. 4 is the schematic flow sheet of second embodiment of the invention.Second embodiment of the invention is local IP access Connection Release process in another tracing section updating process in the LTE system, in conjunction with the network diagram shown in Fig. 1 (a), Fig. 1 (b) and Fig. 1 (c), second embodiment of the invention mainly comprises the steps:
Step 401, the terminal of Idle state regularly or due to mobile causes the tracking area list to change, the initiating updating of tracking area flow process.
It is the wireless side network element of Terminal Service (being referred to as Target Wireless side network element) that terminal transmission Non-Access Stratum (Non-Access-Stratum, referred to as NAS) message-tracing section updating request message is given current;
After fast mobile terminal, this wireless side network element may enter Idle state wireless side network element (being referred to as former wireless side network element) difference before with terminal.
Step 402, the wireless side network element is that terminal is selected to be currently serviced in the Mobility Management Entity (being referred to as target mobility management entity) of terminal, and the tracing section updating request message is included in to initial user message issues target mobility management entity; If there is home base-station gateway, first by this, initial user message is transmitted to home base-station gateway, and then by home base-station gateway select target Mobility Management Entity, and initial user message is issued target mobility management entity by this.
Wherein, in the LTE system, Mobility Management Entity is MME.
Step 403, target mobility management entity is according to the tracing section updating request message, obtain the address that terminal enters Idle state Mobility Management Entity (being referred to as former Mobility Management Entity) before, and send context request message to former Mobility Management Entity, initiate context and obtain flow process.
Step 404, after former Mobility Management Entity is received this context request message, the contextual information of terminal is included in context response information, issue target mobility management entity, carry the identification information of former local IAD or the identification information of former wireless side entity simultaneously in context response information.
When terminal exists local IP access to connect, identification information or the former wireless side entity identification information of carrying former local IAD in context response information.
When terminal does not exist local IP access to connect, identification information or the former wireless side entity identification information of can in context response information, not carry former local IAD mean not exist local IP access to connect; Perhaps in message, by indication information, indicate and do not exist local IP access to connect.
Wherein, the identification information that local access network closes can be the address that local access network closes, or is exclusively used in the identification information that the sign local access network closes; The identification information of wireless side network element can be the address of wireless side network element, or is exclusively used in the identification information of sign wireless side network element.
During the identification information of the former local IAD that wherein, the terminal local IP access connects is kept at context when terminal is set up the LIPA connection; During the former wireless side network element ID information that the terminal local IP access connects is kept at context when terminal is set up the LIPA connection, and when entering Idle state, terminal do not discharge.
Wherein, the identification information that local access network closes refers to the address of L-PGW.
Step 405, after target mobility management entity is received message, check whether terminal exists local IP access to connect, if exist, according to the identification information in message or indication information, checks whether the LIPA connection of terminal is affected.
For the terminal that exists local IP access to connect:
In message, carry be the identification information of former local IAD the time, target mobility management entity checks that whether the identification information of the identification information of target local IAD and the former local IAD carried in message is consistent, if consistent think that local access network that LIPA connects closes and do not change, the LIPA of terminal connects unaffected; If think that inconsistent variation has occurred in the local access network pass that LIPA connects, the LIPA of terminal connects to be needed to discharge.
In message, carry be the identification information of former wireless side network element the time, target mobility management entity checks that whether Target Wireless side network element ID information is consistent with the identification information of the former wireless side network element carried in message, if unanimously think, terminal is still from former wireless side network element access, and the LIPA of terminal connects unaffected; If think that inconsistent terminal is from new former wireless side network element access, the LIPA of terminal connects to be needed to discharge.
When not carrying any identification information or carrying the indication information that local IP access does not connect in message, mean that terminal does not have local IP access to connect.
Carried identification information in message, but, when Target Wireless side network element is not supported local IP access, the local IP access of terminal connects to be needed to discharge.
Step 406, target mobility management entity may be initiated the authentication flow process to terminal.
Step 407, target mobility management entity is responded context acknowledgement message to former Mobility Management Entity; According to the judged result of step 405, if connecting, the LIPA of terminal needs to discharge, in message, carry the LIPA Indication of Losing Efficacy.
Step 408-415, with step 308-315.
In the present embodiment, local access network closes as L-PGW and L-SGW.The present embodiment be take L-PGW and L-SGW and is positioned near wireless side network element or its when example explanation Mobility Management Entity changes, the release flow process that the terminal local IP access connects.Discharge flow process similar to this flow process when L-SGW does not exist, just MME needs directly and L-PGW carries out interacting message, no longer includes the participation of L-SGW in flow process, herein detailed description no longer.Discharge flow process while for L-SGW, being positioned at core net identical with this flow process, just MME needs and the SGW of core net carries out interacting message, then by core net SGW notice L-PGW, rather than notifies L-PGW by L-SGW, herein detailed description no longer.
Fig. 5 is the schematic flow sheet of third embodiment of the invention.Third embodiment of the invention is local IP access Connection Release process in handoff procedure in the LTE system, and in conjunction with the network diagram shown in Fig. 1 (a), Fig. 1 (b) and Fig. 1 (c), third embodiment of the invention mainly comprises the steps:
Step 501, the judgement of wireless side network element needs to initiate the S1 switching; Former wireless side network element and Target Wireless side network element exist when mutual, Target Wireless side network element can be passed to former wireless side network element to the identification information of its local access network pass (target local IAD), or terminal can be given former wireless side network element by the identification-information reporting of target local IAD.
Wherein, the identification information that local access network closes can be the address that local access network closes, or is exclusively used in the identification information that the sign local access network closes.
Wherein, the identification information that local access network closes refers to the address of L-PGW.
Step 502, former wireless side network element sends handover request message to former Mobility Management Entity, carries the identification information of Target Wireless side entity in this handover request message.If obtained the identification information of target local IAD, also be carried in this handover request message and pass to former Mobility Management Entity.If there is home base-station gateway, first this handover request message is transmitted to home base-station gateway, and then by home base-station gateway, handover request message issued to former Mobility Management Entity.
Wherein, in the LTE system, Mobility Management Entity is MME.
Step 503, after former Mobility Management Entity is received handover request message, check whether terminal exists local IP access to connect, if exist, checks whether the LIPA connection of terminal is affected.
For the terminal that exists local IP access to connect:
While carrying the identification information of target local IAD in handover request message, whether the identification information that the local access network that former Mobility Management Entity inspection terminal local IP access connects closes and the identification information of target local IAD be consistent, if consistent think that local access network that terminal LIPA connects closes and do not change, the LIPA of terminal connects unaffected; If think that inconsistent the local access network pass that terminal LIPA connects changes, the LIPA of terminal connects to be needed to discharge.During the identification information that the local access network that the terminal local IP access connects closes is kept at context when terminal is set up the LIPA connection, and when entering Idle state, terminal do not discharge.
While in handover request message, not carrying the identification information of target local IAD, the local IP access of terminal connects to be needed to discharge, now can think that Target Wireless side network element do not support local IP access, no matter perhaps whether Target Wireless side network element supports local IP access, the wireless side network element all needs to discharge local IP access and connects after changing.
Step 504, former Mobility Management Entity is that terminal selection switching is the Mobility Management Entity of Terminal Service (being referred to as target mobility management entity) afterwards, and send reorientation forwarding request message to target mobility management entity, carry the beared information that needs switching in this reorientation forwarding request message.According to the judged result of step 503, if connecting, the terminal local IP access needs to discharge, in message, do not carry the beared information of this connection, in order to complete the release of losing efficacy and connecting.
Step 505, target mobility management entity may be initiated session establishment, the forwarding tunnel Establishing process that core net connects to target S-GW.
Step 506, target mobility management entity sends handover request message to Target Wireless side network element.
Step 507, Target Wireless side network element is responded switching request acknowledgement message to target mobility management entity.
Step 508, continue normal switching flow.
Step 509, terminal may the initiating updating of tracking area flow process.
Step 510, former Mobility Management Entity may be deleted to the former S-GW initiation session of core net, forwarding tunnel is deleted.
Step 511, former Mobility Management Entity, according to the judged result of step 503, is initiated the LIPA session to former local IAD and is deleted flow process; This step can be carried out any time after step 503.
Step 512, target mobility management entity may be initiated forwarding tunnel to core net target S-GW and delete.
In the present embodiment, local access network closes as L-PGW and L-SGW.The present embodiment be take L-PGW and L-SGW and is positioned near wireless side network element or its when example explanation Mobility Management Entity changes, the release flow process that the terminal local IP access connects.Discharge flow process similar to this flow process when L-SGW does not exist, just MME needs directly and L-PGW carries out interacting message, no longer includes the participation of L-SGW in flow process, herein detailed description no longer.Discharge flow process while for L-SGW, being positioned at core net identical with this flow process, just MME needs and the SGW of core net carries out interacting message, then by core net SGW notice L-PGW, rather than notifies L-PGW by L-SGW, herein detailed description no longer.
The present embodiment be take former Mobility Management Entity and is judged that whether influenced terminal LIPA connects is example, and similar with the embodiment shown in Fig. 4, target mobility management entity also can be done this judgement, no longer describes in detail herein.
Other switching flows flow process therewith are similar, no longer describe in detail herein.
Fig. 5 a is the schematic flow sheet of fourth embodiment of the invention.Fourth embodiment of the invention is another local IP access Connection Release process in handoff procedure in the LTE system, and in conjunction with the network diagram shown in Fig. 1 (a), Fig. 1 (b) and Fig. 1 (c), fourth embodiment of the invention mainly comprises the steps:
Step 501a, the judgement of wireless side network element needs to initiate the S1 switching.
Step 502a, former wireless side network element sends handover request message to former Mobility Management Entity; If there is home base-station gateway, first this handover request message is transmitted to home base-station gateway, and then by home base-station gateway, this handover request message message issued to former Mobility Management Entity.
Wherein, in the LTE system, Mobility Management Entity is MME.
Step 503a, former Mobility Management Entity is that terminal selection switching is the Mobility Management Entity of Terminal Service (being referred to as target mobility management entity) afterwards, and send reorientation forwarding request message to target mobility management entity, carry the identification information of former local IAD or the identification information of former wireless side entity in message.
Step 504a, target mobility management entity may be initiated session establishment, the forwarding tunnel Establishing process that core net connects to target S-GW.
Step 505a, target mobility management entity sends handover request message to Target Wireless side network element.
Step 506a, Target Wireless side network element is responded switching request acknowledgement message to target mobility management entity, and carries target local IAD sign in message.
Step 507a, with step 405; But message wherein is switching request acknowledgement message.
Step 508a, target mobility management entity is responded reorientation forward response message.According to the judged result of step 507a, the terminal local IP access connects to be needed to discharge, and carries LIPA Joint failure indication information in message, and indication discharges LIPA and connects.
Step 509a, target mobility management entity is initiated the deleting load-bearing flow process for this LIPA connects.After delete step 505a, the wireless side network element is the reserved resource of this LIPA.
Step 510a-514a is identical with step 508-512 respectively.
Fig. 6 is the schematic flow sheet of fifth embodiment of the invention.Fifth embodiment of the invention is another local IP access Connection Release process in the Route Area renewal process in the UTRAN system, in conjunction with the network diagram shown in Fig. 1 (a), Fig. 1 (b) and Fig. 1 (c), fifth embodiment of the invention mainly comprises the steps:
Step 601, the terminal of Idle state regularly or because movement causes Route Area to change is initiated the Routing Area Update flow process.It is the wireless side network element of Terminal Service (being referred to as Target Wireless side network element) that terminal transmission Non-Access Stratum (Non-Access-Stratum, abbreviation NAS) message-Routing Area Update request is given current.After fast mobile terminal, this wireless side network element may enter Idle state wireless side network element (being referred to as former wireless side network element) difference before with terminal.
Step 602, the wireless side network element is that terminal is selected to be currently serviced in the Mobility Management Entity (being referred to as target mobility management entity) of terminal, and the tracing section updating request message is included in to initial user message issues target mobility management entity.If there is home base-station gateway, first by this, initial user message is transmitted to home base-station gateway, and then by home base-station gateway select target Mobility Management Entity, and initial user message is issued target mobility management entity by this.
Wherein, in the UTRAN system, Mobility Management Entity is SGSN.
Step 603, target mobility management entity is according to the Routing Area Update request message, obtain the address that terminal enters Idle state Mobility Management Entity (being referred to as former Mobility Management Entity) before, and initiate context to former Mobility Management Entity and obtain flow process.Target mobility management entity sends context request message to former Mobility Management Entity, and carries the identification information of target local IAD or the identification information of Target Wireless side entity in this context request message.
When the Target Wireless side entity is supported local IP access, carry identification information or the Target Wireless side entity identification information of target local IAD in context request message.
When the Target Wireless side entity is not supported local IP access, the identification information or the Target Wireless side entity identification information that can in context request message, not carry the target local IAD mean not support local IP access; Perhaps in context request message, by indication information, indicate and do not support local IP access.
Wherein, the identification information that local access network closes can be the address that local access network closes, or is exclusively used in the identification information that the sign local access network closes.The identification information of wireless side network element can be the address of wireless side network element, or is exclusively used in the identification information of sign wireless side network element.
Wherein, the identification information that local access network closes refers to the address of L-GGSN.
Step 604, after former Mobility Management Entity is received context request message, check whether terminal exists local IP access to connect, if exist, whether the LIPA that based on context the identification information in request message or indication information check terminal connects and be affected.
For the terminal that exists local IP access to connect:
In context request message, carry be the identification information of target local IAD the time, former Mobility Management Entity checks that whether the identification information of the local access network pass that the terminal local IP access connects is consistent with the identification information of the target local IAD carried in message, if consistent think that local access network that LIPA connects closes and do not change, the LIPA of terminal connects unaffected; If think that inconsistent variation has occurred in the local access network pass that LIPA connects, the LIPA of terminal connects to be needed to discharge.During the identification information that the local access network that the terminal local IP access connects closes is kept at context when terminal is set up the LIPA connection.
In context request message, carry be the identification information of Target Wireless side network element the time, former Mobility Management Entity checks that whether the wireless side network element ID information of terminal local IP access connection is consistent with the identification information of the Target Wireless side network element carried in context request message, if unanimously think, terminal is still from former wireless side network element access, and the LIPA of terminal connects unaffected; If think that inconsistent terminal is from new former wireless side network element access, the LIPA of terminal connects to be needed to discharge.During the wireless side network element ID information that the terminal local IP access connects is kept at context when terminal is set up the LIPA connection, and when entering Idle state, terminal do not discharge.
When not carrying any identification information or carrying the indication information of not supporting local IP access in message, expression Target Wireless side network element is not supported local IP access, and the local IP access of terminal connects to be needed to discharge.
Step 605, former Mobility Management Entity is included in the contextual information of terminal in context response information, issues target mobility management entity, carries in message and needs the beared information activated or be referred to as beared information to be activated.According to the judged result of step 604, local IP access connects while needing to discharge, and does not carry the beared information of this connection in context response, in order to complete the release of losing efficacy and connecting.
Step 606, target mobility management entity may be initiated the authentication flow process to terminal.
Step 607, target mobility management entity is responded context acknowledgement message to former Mobility Management Entity.
Step 608, the PDP Context that target mobility management entity initiation core net connects is new technological process more.
Step 609, target mobility management entity is to Authentication Authorization server launch position new technological process more.
Step 610, the Authentication Authorization server is deleted flow process to former Mobility Management Entity launch position.
Step 611, former Mobility Management Entity, according to the judged result of step 604, is initiated LIPA to former local IAD and is connected PDP Context deletion flow process; This step can be carried out any time after step 604.
Step 612,613, target mobility management entity sends Routing Area Update and accepts to terminal, and terminal is responded Routing Area Update and is completed.
In the present embodiment, local access network closes as L-GGSN.The present embodiment be take L-GGSN and is positioned near wireless side network element or its when example explanation Mobility Management Entity changes, the release flow process that the terminal local IP access connects.
Fig. 7 is the schematic flow sheet of sixth embodiment of the invention.Sixth embodiment of the invention is another local IP access Connection Release process in the Route Area renewal process in the UTRAN system, in conjunction with the network diagram shown in Fig. 1 (a), Fig. 1 (b) and Fig. 1 (c), sixth embodiment of the invention mainly comprises the steps:
Step 701, the terminal of Idle state regularly or because movement causes Route Area to change is initiated the Routing Area Update flow process.It is the wireless side network element of Terminal Service (being referred to as Target Wireless side network element) that terminal transmission Non-Access Stratum (Non-Access-Stratum, referred to as NAS) message-Routing Area Update request message is given current.After fast mobile terminal, this wireless side network element may enter Idle state wireless side network element (being referred to as former wireless side network element) difference before with terminal.
Step 702, the wireless side network element is that terminal is selected to be currently serviced in the Mobility Management Entity (being referred to as target mobility management entity) of terminal, and the tracing section updating request message is included in to initial user message issues target mobility management entity.If there is home base-station gateway, first by this, initial user message is transmitted to home base-station gateway, and then by home base-station gateway select target Mobility Management Entity, and initial user message message is issued target mobility management entity by this.
Wherein, in the UTRAN system, Mobility Management Entity is SGSN.
Step 703, target mobility management entity is according to the Routing Area Update request message, obtain the address that terminal enters Idle state Mobility Management Entity (being referred to as former Mobility Management Entity) before, and send context request message to former Mobility Management Entity, initiate context and obtain flow process.
Step 704, after former Mobility Management Entity is received context request message, be included in the contextual information of terminal in context response information, issues target mobility management entity.Carry the identification information of former local IAD or the identification information of former wireless side entity simultaneously in context response information.
When terminal exists local IP access to connect, identification information or the former wireless side entity identification information of carrying former local IAD in context response information.
When terminal does not exist local IP access to connect, identification information or the former wireless side entity identification information of can in context response information, not carry former local IAD mean not exist local IP access to connect; Perhaps in message, by indication information, indicate and do not exist local IP access to connect.
Wherein, the identification information that local access network closes can be the address that local access network closes, or is exclusively used in the identification information that the sign local access network closes.The identification information of wireless side network element can be the address of wireless side network element, or is exclusively used in the identification information of sign wireless side network element.
During the identification information of the former local IAD that wherein, the terminal local IP access connects is kept at context when terminal is set up the LIPA connection.During the former wireless side network element ID information that the terminal local IP access connects is kept at context when terminal is set up the LIPA connection, and when entering Idle state, terminal do not discharge.
Wherein, the identification information that local access network closes refers to the address of L-GGSN.
Step 705, target mobility management entity may be initiated the authentication flow process to terminal.
Step 706, after target mobility management entity is received context response information, check whether terminal exists local IP access to connect, if exist, whether the LIPA that based on context the identification information in response message or indication information check terminal connects and be affected.
For the terminal that exists local IP access to connect:
In context response information, carry be the identification information of former local IAD the time, target mobility management entity checks that whether the identification information of the identification information of target local IAD and the former local IAD carried in message is consistent, if consistent think that local access network that LIPA connects closes and do not change, the LIPA of terminal connects unaffected; If think that inconsistent variation has occurred in the local access network pass that LIPA connects, the LIPA of terminal connects to be needed to discharge.
In context response information, carry be the identification information of former wireless side network element the time, target mobility management entity checks that whether Target Wireless side network element ID information is consistent with the identification information of the former wireless side network element carried in context response information, if unanimously think, terminal is still from former wireless side network element access, and the LIPA of terminal connects unaffected; If think that inconsistent terminal is from new former wireless side network element access, the LIPA of terminal connects to be needed to discharge.
When not carrying any identification information or carrying the indication information that local IP access does not connect in context response information, mean that terminal does not have local IP access to connect.
Carried identification information in context response information, but, when Target Wireless side network element is not supported local IP access, the local IP access of terminal connects to be needed to discharge.
Step 707, target mobility management entity is responded context acknowledgement message to former Mobility Management Entity.According to the judged result of step 706, the LIPA of terminal connects while needing to discharge, and carries LIPA Indication of Losing Efficacy information in message.
Step 708-713, with step 608-613.
In the present embodiment, local access network closes as L-GGSN.The present embodiment be take L-GGSN and is positioned near wireless side network element or its when example explanation Mobility Management Entity changes, the release flow process that the terminal local IP access connects.
Fig. 8 is the schematic flow sheet of seventh embodiment of the invention.Seventh embodiment of the invention is local IP access Connection Release process in repositioning process in the UTRAN system, and in conjunction with the network diagram shown in Fig. 1 (a), Fig. 1 (b) and Fig. 1 (c), seventh embodiment of the invention mainly comprises the steps:
Step 801, the judgement of wireless side network element needs to initiate reorientation; Former wireless side network element and Target Wireless side network element exist when mutual, Target Wireless side network element can be passed to former wireless side network element to the identification information of its local access network pass (target local IAD), or terminal can be given former wireless side network element by the identification-information reporting of target local IAD.
Wherein, the identification information that local access network closes can be the address that local access network closes, or is exclusively used in the identification information that the sign local access network closes.
Wherein, the identification information that local access network closes refers to the address of L-GGSN.
Step 802, former wireless side network element sends handover request message, the sign of in this handover request message, carrying the Target Wireless side entity to former Mobility Management Entity.If obtained the identification information of target local IAD, also be carried in this handover request message and pass to former Mobility Management Entity.If there is home base-station gateway, first this handover request message is transmitted to home base-station gateway, and then by home base-station gateway, this handover request message issued to former Mobility Management Entity.
Wherein, in the UTRAN system, Mobility Management Entity is SGSN.
Step 803, after former Mobility Management Entity is received this handover request message, check whether terminal exists local IP access to connect, if exist, checks whether the LIPA connection of terminal is affected.
For the terminal that exists local IP access to connect:
While carrying the identification information of target local IAD in handover request message, whether the identification information that the local access network that former Mobility Management Entity inspection terminal local IP access connects closes and the identification information of target local IAD be consistent, if consistent think that local access network that terminal LIPA connects closes and do not change, the LIPA of terminal connects unaffected; If think that inconsistent the local access network pass that terminal LIPA connects changes, the LIPA of terminal connects to be needed to discharge.During the identification information that the local access network that the terminal local IP access connects closes is kept at context when terminal is set up the LIPA connection, and when entering Idle state, terminal do not discharge.
While in handover request message, not carrying the identification information of target local IAD, the local IP access of terminal connects needs to discharge, now can think that Target Wireless side network element do not support local IP access, also can think no matter whether Target Wireless side network element supports local IP access, the wireless side network element all needs to discharge local IP access and connects after changing.
Step 804, former Mobility Management Entity is that terminal selection switching is the Mobility Management Entity of Terminal Service (being referred to as target mobility management entity) afterwards, and send reorientation forwarding request message to target mobility management entity, carry the beared information that needs switching in this reorientation forwarding request message.According to the judged result of step 803, the terminal local IP access connects while needing to discharge, and does not carry the beared information of this connection in reorientation forwarding request message, in order to complete the release of losing efficacy and connecting.
Step 805, target mobility management entity sends re-positioning request to Target Wireless side network element.
Step 806, continue normal switching flow.
Step 807, former Mobility Management Entity, according to the judged result of step 803, is initiated LIPA to former local IAD and is connected PDP Context deletion flow process; This step can be carried out any time after step 803.
Step 808, terminal may be initiated the Routing Area Update flow process.
In the present embodiment, local access network closes as L-GGSN.The present embodiment be take L-GGSN and is positioned near wireless side network element or its when example explanation Mobility Management Entity changes, the release flow process that the terminal local IP access connects.
The present embodiment be take former Mobility Management Entity and is judged that whether influenced terminal LIPA connects is example, and similar with the method shown in Fig. 7, target mobility management entity also can be done this judgement, no longer describes in detail herein.
The processing method of other switching flow flow process therewith is similar, no longer describes in detail herein.
Fig. 8 a is the schematic flow sheet of eighth embodiment of the invention.Eighth embodiment of the invention is another local IP access Connection Release process in repositioning process in the UTRAN system, in conjunction with the network diagram shown in Fig. 1 (a), Fig. 1 (b) and Fig. 1 (c), eighth embodiment of the invention mainly comprises the steps:
Step 801a, the judgement of wireless side network element needs to initiate reorientation.
Step 802a, former wireless side network element sends handover request message, the sign of in this handover request message, carrying the Target Wireless side entity to former Mobility Management Entity.If there is home base-station gateway, first this handover request message is transmitted to home base-station gateway, and then by home base-station gateway, this handover request message is issued to former Mobility Management Entity.
Wherein, in the UTRAN system, Mobility Management Entity is SGSN.
Step 803a, with step 503a, but message wherein is handover request message.
Step 804a, target mobility management entity sends RELOCATION REQUEST message to Target Wireless side network element.
Step 805a, Target Wireless side network element is responded and is sent the re-positioning request acknowledgement message, and carries target local IAD sign in this re-positioning request acknowledgement message.
Step 806a, with step 507a, but message wherein is the re-positioning request acknowledgement message.
Step 807a, target mobility management entity sends reorientation forward response message to Target Wireless side network element.According to the judged result of step 806a, the terminal local IP access connects while needing to discharge, and in this reorientation forward pass response message, carries LIPA Joint failure indication information, and indication discharges LIPA and connects.
Step 808a, target mobility management entity is initiated the deleting load-bearing flow process for this LIPA connects.After delete step 505a, the wireless side network element is the reserved resource of this LIPA.
Step 809a-811a is identical with step 806-808 respectively.
In the embodiment shown in Fig. 5, Fig. 5 a, Fig. 8 and Fig. 8 a, the identification information of target local IAD can also be to be configured on target mobility management entity, now, adopts the embodiment flow process shown in Fig. 5 a and 8a.In flow process now, target mobility management entity can directly judge whether the LIPA of terminal lost efficacy after receiving switching or this reorientation forwarding request, also no longer needs whether the wireless side network element is the reserved resource of LIPA; Other steps are identical.
According to above the inventive method embodiment, the present invention proposes the delivery system embodiment that a kind of local IP access connects, discharge the local IP access lost efficacy after changing for Mobility Management Entity and connect, this system comprises before change the former Mobility Management Entity of serving terminal, wherein:
Former Mobility Management Entity is served target local IAD identification information or Target Wireless side network element ID information or the target home base station gateway identification information of terminal after being arranged to obtain change, and whether effectively also discharges the local IP access connection of losing efficacy according to the connection of identification information judgment local IP access.
According to above the inventive method embodiment, the invention allows for the delivery system embodiment that another kind of local IP access connects, discharging the local IP access lost efficacy after changing for Mobility Management Entity connects, this system comprise before change the former Mobility Management Entity of serving terminal and change after serve the target mobility management entity of terminal, wherein:
Target mobility management entity is arranged to obtain before change former local IAD identification information or former wireless side network element ID information or the former home base-station gateway identification information of serving terminal, and, after going out the local IP access Joint failure according to identification information judgment, by message, to former Mobility Management Entity, respond the local IP access Indication of Losing Efficacy;
Former Mobility Management Entity is arranged to discharge according to the local IP access Indication of Losing Efficacy local IP access lost efficacy and is connected.
Above two system embodiments, please understand by edition with parallel text inventive method embodiment.
For simplified characterization, above embodiment only be take and is not existed home base-station gateway and local access network to close to be positioned at wireless side entity or near the situation it method for releasing that local IP access is connected to be described as example.Exist the situation of home base-station gateway similar with it.Certainly, there is home base-station gateway, and local access network closes while being positioned near wireless side entity or its, and the message between the message between Mobility Management Entity and wireless side entity and Mobility Management Entity and local access network pass will be via the home base-station gateway transmission.When there being home base-station gateway, and local access network closes while being positioned near home base-station gateway or its, message between Mobility Management Entity and wireless side entity will be via the home base-station gateway transmission, and the message between Mobility Management Entity and local access network pass no longer needs home base-station gateway to forward, in message, newly-increased wireless side network element ID information of carrying now needs to have the identification information of home base-station gateway to replace.In these cases, the mode of local IP access Connection Release is very similar to above-described embodiment, can not impact setting forth the present invention, therefore no longer be repeated in this description at this.
The system and method for a kind of local IP access Connection Release provided by the invention, solved after Mobility Management Entity changes the inefficacy brought and connected the problem how to discharge.In the flow process of the switching of LTE system or tracing section updating, the local access network pass that former Mobility Management Entity provides according to target mobility management entity or the identification information of wireless side network element or home base-station gateway, judge whether the LIPA connection lost efficacy, for the LIPA lost efficacy, connect, former Mobility Management Entity no longer sends to target mobility management entity by the beared information of this connection, and former Mobility Management Entity discharges this LIPA connection simultaneously.
Above embodiment not only can apply and home base station system, too applicable and macro base station system.The wireless side entity can be base station, base station from home or radio network controller (Radio Network Controller, referred to as RNC) in the above-described embodiments.Mobility Management Entity can be MME, MSC or SGSN.It can be L-SGW, L-PGW or L-GGSN that local access network closes.The core net IAD can be S-GW or SGSN.
The wireless side network element of local IP access or home base-station gateway can with local access network, to close address identical.
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, perhaps 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, perhaps they are made into respectively to each integrated circuit modules, perhaps a plurality of modules in them or step being made into to the single integrated circuit module realizes.Like this, the present invention is not restricted to any specific hardware and software combination.
Although the disclosed execution mode of the present invention as above, the execution mode that described content just adopts for the ease of understanding the present invention, not in order to limit the present invention.Technical staff in any the technical field of the invention; under the prerequisite that does not break away from the disclosed spirit and scope of the present invention; can do any modification and variation what implement in form and on details; but scope of patent protection of the present invention, still must be as the criterion with the scope that appending claims was defined.