CN101155126A - System, device and method for implementing mobility management - Google Patents
System, device and method for implementing mobility management Download PDFInfo
- Publication number
- CN101155126A CN101155126A CNA2006101398007A CN200610139800A CN101155126A CN 101155126 A CN101155126 A CN 101155126A CN A2006101398007 A CNA2006101398007 A CN A2006101398007A CN 200610139800 A CN200610139800 A CN 200610139800A CN 101155126 A CN101155126 A CN 101155126A
- Authority
- CN
- China
- Prior art keywords
- address
- 3gpp network
- network
- sae anchor
- ipsec tunnel
- 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.)
- Pending
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a system, device and method for implementing the mobility managing. The key device used in the said method is system architecture evolution anchor (SAE Anchor), wherein the said SAE Anchor is used establishing internet security IPSec tunnel when the UE moves to non 3GPP Network by 3GPP Network. The said UE is used in using a general grouping wireless service tunnel protocol GTP in 3GPP Network or strengthening GTP communication, the IPSec tunnel communication is used in non 3GPP Network. The said device and method can obviously reduce the waste of bare resource and address resource and greatly reduce the communication time delay due to UE switch.
Description
Technical field
The present invention relates to the communications field, be specifically related to a kind of system, apparatus and method that realize mobile management.
Background technology
Along with development of Communication Technique, 3rd Generation Partnership Project (3GPP) is attempting studying a kind of wireless evolution network, to be applied to future communications; This wireless evolution network is mainly by evolution Radio Access Network (Evolved RAN) and evolution block core net network (Evolved Packet Core, EPC) composition.
Referring to Fig. 1, Fig. 1 is the wireless evolution network structure chart of prior art.Among Fig. 1, comprise among the EPC anchor point between continuous Mobility Management Entity/user entity (MME/UPE) and different access systems (Inter Access System Anchor, IASA); And IASA is made up of the 3GPP Anchor and the System Architecture Evolution anchor point (SAE Anchor) that link to each other.
MME/UPE links to each other with Evolved RAN, SAE Anchor links to each other with external network, non-3GPP Internet protocol access network (non 3GPP IP Access Network), 3GPP Internet protocol access network (3GPP IP Access Network), and this non 3GPP IP Access Network can be a WLAN 3GPP Internet protocol access network (WLAN 3GPP IP Access Network) etc.; MME/UPE and 3GPP Anchor also link to each other with Serving GPRS Support Node (SGSN) in the general packet radio service core network (GPRS Core).
Have, SGSN also can (GSM/EDGE RAN GERAN) links to each other, and also can link to each other with Universal Terrestrial Radio Access Network network access networks such as (UTRAN) with global system for mobile communications/enhancement mode global system for mobile communications message transmission rate Radio Access Network again; In addition, home subscriber server (HSS) links to each other with EPC, and strategy and charging rule functions (PCRF) entity links to each other with external network with EPC respectively.
In actual applications, subscriber equipment (UE) can pass through the such 3GPP Access Network of UTRAN, GERAN, EvolvedRAN and insert SAE Anchor, with external network communication; UE can also insert SAE Anchor by the such non 3GPP Access Network of WLAN 3GPP IP Access Network, non 3GPP IP Access Network, with external network communication.Usually, non 3GPP Access Network links to each other with SAE Anchor by packet data network pass (PDG).
In the practical communication process, UE probably switches between 3GPP Access Network and non 3GPPAccess Network; In order to guarantee the UE communication continuity, need carry out mobile management to UE, concrete mobile management principle such as Fig. 2, Fig. 3 and shown in Figure 4.
By Fig. 2 and Fig. 3 as seen, between UE and the PDG IP safety (IPSec) tunnel, between PDG and the home agent (HA) mobile IP (MIP) tunnel.As seen from Figure 4, be ipsec tunnel between UE and the PDG, between UE and the HA MIP tunnel; And UE is nested with the ipsec tunnel between the PDG by UE with MIP tunnel between the PDG.Among Fig. 2, Fig. 3 and Fig. 4, HA is realized by SAE Anchor usually, guarantees the continuity when UE switches between 3GPP Access Network and non 3GPPAccess Network.
By Fig. 2, Fig. 3 and Fig. 4 as seen, UE comprises ipsec tunnel and MIP tunnel by the transmission tunnel that non 3GPP Access Network and HA are set up.Obviously, ipsec tunnel and MIP tunnel coexist has simultaneously increased the complexity of system; And, owing to have IPSec and MIP technology simultaneously, so UE can be assigned with in communication process and IPSec and the corresponding mailing address that reaches three of MIP technology, this has all caused very serious waste to interface-free resources and address resource.Have, the existence of MIP technology also requires UE to support the MIP agreement again; Yet, there is a large amount of UE not support the MIP agreement at present, this will cause the UE can't proper communication.In addition, when UE switches, not only to upgrade, also will upgrade the MIP tunnel to ipsec tunnel; This will obviously increase the communication delay that causes because of the UE switching.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of system and method for realizing mobile management, to reduce the waste to interface-free resources and address resource, reduces the communication delay that causes because of the UE switching.
Another object of the present invention is to provide a kind of device of realizing mobile management,, reduce the communication delay that causes because of the UE switching to reduce waste to interface-free resources and address resource.
For achieving the above object, technical scheme of the present invention is achieved in that
The invention discloses a kind of system that realizes mobile management, this system comprises SAE Anchor;
Wherein, described SAE Anchor is used for when UE moves to non 3GPPNetwork by 3GPP Network, sets up the ipsec tunnel that is used to support UE communication in non 3GPP Network;
Described UE is used for using general packet radio service tunnel agreement (GTP) or strengthens GTP communication when 3GPP Network, use ipsec tunnel communication in the time of in non 3GPP Network.
Described SAE Anchor, be further used for finding pairing Local IP address, described Remote IP address, and the packet of receiving is sent to UE by described ipsec tunnel according to the described binding relationship between long-range Internet protocol (Remote IP) address and local Internet protocol (Local IP) address.
Described SAEAnchor is the gateway that connects outside public data network (PDN).
The invention also discloses a kind of SAE Anchor that realizes mobile management, be provided with the ipsec tunnel creating unit that links to each other with SAIE Anchor Transmit-Receive Unit among this SAE Anchor;
Wherein, the ipsec tunnel creating unit is used to the UE that moves to non 3GPPNetwork by 3GPP Network to set up ipsec tunnel;
SAE Anchor Transmit-Receive Unit is used for supporting ipsec tunnel to set up communicating by letter between process UE and the SAE Anchor.
Further be provided with UE packet retransmission unit among the described SAE Anchor, be used for finding pairing Local IP address, described Remote IP address, and the packet that will send to UE by the described ipsec tunnel of setting up for UE sends to the Local IP address that finds according to Remote IP address and the binding relationship between the Local IP address of UE.
The invention also discloses a kind of realization mobility management method, this method comprises:
When UE moved to non 3GPP Network by 3GPP Network, SAE Anchor set up the ipsec tunnel that is used to support UE communication in non3GPP Network.
SAE Anchor further distributes the address by the professional employed Remote IP of non 3GPP Network visit 3GPP for UE, also sets up binding relationship at Remote IP and UE between the Local IP address that non 3GPP network obtains.
When receiving that when being the packet of destination address with described Remote IP address, this method further comprises:
Find pairing Local IP address, described Remote IP address according to the described binding relationship between Remote IP address and the Local IP address, and the packet of receiving is sent to UE by described ipsec tunnel.
Described SAE Anchor is the gateway that connects outside PDN.
Described SAE Anchor uses the MOBIKE agreement to comprise the operation of one of ipsec tunnel establishment, modification, deletion action at least in non 3GPP Network.
UE moves to the 3GPP Network from non 3GPP Network, and this method further comprises:
In described 3GPP Network, carry out the constructive process of GTP tunnel for UE.
Further deletion is the described ipsec tunnel that UE set up in non 3GPP Network.
UE moves to the New non 3GPP Network from the Old non 3GPP Network at current place, and this method further comprises:
New non-3GPP gateway among the New non 3GPP (New non 3GPP GW) is distributed in the IP address of communicating by letter among the New non 3GPP Network for UE; And, be the SAE Anchor renewal of UE service and the ipsec tunnel between the UE.
Described UE uses GTP tunnel/enhancing GTP tunnel communication in 3GPP Network the time.
Compared with prior art, the system of realization mobile management provided by the present invention, apparatus and method all can be applicable in the wireless evolution network, and the Primary Component that is applied to is SAE Anchor; Wherein, described SAE Anchor is used for setting up ipsec tunnel in non 3GPP Network when UE moves to non 3GPP Network by 3GPP Network; Described UE is used for using GTP or strengthens GTP communication when 3GPP Network, use ipsec tunnel communication in the time of in non 3GPP Network.System of the present invention, apparatus and method all can obviously reduce the waste to interface-free resources and address resource, also significantly reduce the communication delay that causes because of the UE switching.
Description of drawings
Fig. 1 is the wireless evolution network structure chart of prior art;
Fig. 2 is a kind of mobile management schematic diagram of prior art;
Fig. 3 is the another kind of mobile management schematic diagram of prior art;
Fig. 4 is another mobile management schematic diagram of prior art;
Fig. 5 is a mobile management schematic diagram of the present invention;
Fig. 6 is the wireless evolution network structure chart of a preferred embodiment of the present invention;
Fig. 7 inserts the flow chart of 3GPP Network for UE;
Fig. 8 is the mobile management flow chart of a preferred embodiment of the present invention;
User face protocol stack schematic diagram when Fig. 9 inserts non 3GPP Network for UE;
Chain of command protocol stack schematic diagram when Figure 10 inserts non 3GPP Network for UE;
Figure 11 is the mobile management flow chart of the another preferred embodiment of the present invention;
User face protocol stack schematic diagram when Figure 12 inserts 3GPP Network for UE;
Chain of command protocol stack schematic diagram when Figure 13 inserts 3GPP Network for UE;
Figure 14 is the present invention's mobile management flow chart of a preferred embodiment again.
Embodiment
Below in conjunction with drawings and the specific embodiments to the detailed description of the invention.
The system of realization mobile management provided by the present invention, this system comprises SAE Anchor; Wherein, described SAE Anchor, be used for when UE moves to non 3GPP Network by 3GPP Network, in non 3GPP Network, set up the ipsec tunnel that is used to support UE communication, can also be further for UE distributes the address by the professional employed Remote IP of non 3GPP Network visit 3GPP, and between Local IP address that non 3GPP network obtains and Remote IP address, set up binding relationship for UE; Described UE is used for using GTP or strengthens GTP communication when 3GPP Network, use ipsec tunnel communication in the time of in non 3GPP Network.
Be provided with the ipsec tunnel creating unit that links to each other with SAE Anchor Transmit-Receive Unit among the SAE Anchor of realization mobile management provided by the present invention; Wherein, the ipsec tunnel creating unit is used to the UE that moves to non 3GPP Network by 3GPP Network to set up ipsec tunnel; The SAEAnchor Transmit-Receive Unit is used for supporting ipsec tunnel to set up communicating by letter between process UE and the SAE Anchor.Have again, can also further be provided with UE packet retransmission unit among the described SAE Anchor, be used for finding pairing Local IP address, described Remote IP address, and the packet that will send to UE by the described ipsec tunnel of setting up for UE sends to the Local IP address that finds according to Remote IP address and the binding relationship between the Local IP address of UE.
Realization mobility management method provided by the present invention comprises: when UE moved to non 3GPP Network by 3GPP Network, SAE Anchor set up the ipsec tunnel that is used to support UE communication in non 3GPP Network; SAE Anchor can also also set up binding relationship at Remote IP and UE further for UE distributes the address by the professional employed Remote IP of non3GPP Network visit 3GPP between the Local IP address that non 3GPP network obtains.
Generally speaking, in actual applications, UE both can also can visit the business of 3GPP by non 3GPP Network by 3GPP Network visit 3GPP business.And in the time of in 3GPP Network, UE uses GTP or strengthens GTP communication; In the time of in non 3GPP Network, UE uses IPsec tunnel transmit traffic data, and uses MOBIKE to carry out mobile management.
Particularly, in the time of in 3GPP Network, it is its IP address allocated that UE uses GTP or enhancing GTP to be connected to SAE Anchor and to obtain SAE Anchor, and the fail safe of communication data is guaranteed by the 3GPP air interface technologies that is adopted in the communication process.In the time of in non 3GPP Network, setting up the IPsec tunnel between UE and the SAE Anchor and obtaining SAE Anchor is its IP address allocated, and the fail safe of communication data is guaranteed by the IPsec tunnel.
Because the mobility of UE, UE can move between 3GPP Network and non 3GPP Network, also can move between different 3GPP Network, can also move between different non3GPP Network.Particularly, when commencing business and between 3GPP Network and non3GPP Network when mobile, UE employed IP address in 3GPP Network and non 3GPP Network normally identical so that can provide business continuance preferably for UE; When UE was mobile between different 3GPP Network, UE used GTP or strengthens GTP and carries out mobile management; When UE is mobile between different non 3GPP Network, Local IP address that UE use MOBIKE protocol update was once write down in SAE Anchor and the corresponding relation between the Remote IP address.
In sum, the principle of the attainable mobile management of the present invention as shown in Figure 5.As seen from Figure 5, non 3GPP Access Network no longer links to each other with SAE Anchor by PDG, but directly links to each other with SAE Anchor.
Mobile management principle shown in Figure 5 can be realized by network configuration shown in Figure 6.Referring to Fig. 6, Fig. 6 is the wireless evolution network structure chart of a preferred embodiment of the present invention.Among Fig. 6, comprise continuous Long Term Evolution anchor point (LTE Anchor) and IASA among the EPC; And IASA is made up of the 3GPP Anchor and the SAE Anchor that link to each other.In actual applications, SAE Anchor occurs as the gateway that connects outside PDN usually.
LTE Anchor links to each other with Evolved RAN, and SAE Anchor links to each other with external network, non 3GPPIP Access Network, 3GPP Access Network; LTE Anchor and 3GPP Anchor also link to each other with SGSN among the GPRS Core.Have, SGSN also can link to each other with access networks such as GERAN, UTRAN again; In addition, HSS links to each other with EPC, and the PCRF entity links to each other with external network with EPC respectively.Described LTE Anchor can be realized by MME/UPE.
As seen from Figure 6, UE can pass through the such 3GPPAccess Network of UTRAN, GERAN, Evolved RAN and insert SAE Anchor, with external network communication; UE can also pass through the such non 3GPPAccess Network of WLAN3GPP IP Access Network, non 3GPP IP Access Network and insert SAE Anchor, with external network communication.
Among Fig. 6, no longer be connected with PDG between non 3GPP Access Network and the SAE Anchor.Like this, when communicating based on system shown in Figure 6, do not re-use the MIP technology between non 3GPP Access Network and the SAEAnchor, this makes the communication between UE and the SAE Anchor only need to realize by IPSec; Therefore, UE can not support the MIP agreement.
In actual applications, when terminal moves to non 3GPP Network, can obtain non 3GPPNetwork and use prior art institute IP address allocated, and can use this IP address and initiate follow-up communication process; This IP address is commonly called Local IP address.Afterwards, UE obtains the address of SAE Anchor by carry out modes such as domain name mapping with name server (DNS), and according to this address applications prior art initiate and SAE Anchor between ipsec tunnel set up process.Set up in the process at described ipsec tunnel, UE can obtain SAE Anchor and use prior art institute IP address allocated, and this IP address is commonly called Remote IP address; And, SAE Anchor set up process or other at described ipsec tunnel with the UE communication process in, write down the described Local IP address of UE and the binding relationship of RemoteIP address.
After finishing above operation, when UE by self with SAE anchor between ipsec tunnel during to SAE anchor transmission upstream data bag, SAE anchor then can pass through the upstream data bag of this ipsec tunnel reception from UE, and after packet is removed encapsulation the raw data packets that obtains is transmitted to external network; When the Remote IP address with UE that external network sent is that the packet of destination address is when being routed to SAE Anchor, SAE Anchor according to own be the pairing LocalIP address, Remote IP address that the binding relationship of Remote IP address that UE write down and Local IP address finds UE, and the packet received is sent to UE by the ipsec tunnel of being set up between self and the UE.
As seen, said process guarantees that UE can conduct interviews to the 3GPP business by non 3GPP Network.
Certainly, when UE changes because of Local IP address former thereby that cause being assigned with such as move between different non 3GPP Network, need to upgrade the ipsec tunnel that UE is used to communicate by letter.
Referring to Fig. 7, Fig. 7 is the flow chart of UE access 3GPP Network, and this flow process may further comprise the steps:
Step 701:UE sends service request (Service Request) to LTE Anchor/SGSN.
When receiving the Service Request from UE, LTE Anchor/SGSN realizes safety function (security function).Particularly, the safety function that realized of LTE Anchor/SGSN is made up of following step 702 to step 705.
Step 702:LTE Anchor/SGSN sends authentication information request (SendAuthentication Info) to HSS.
Step 703:HSS sends authentication information to LTE Anchor/SGSN and confirms (SendAuthentication Info Ack).
Step 704:LTE Anchor/SGSN sends authentication and computation requests (Authenticationand Ciphering Request) to UE.
Step 705:UE sends authentication and calculated response (Authenticationand Ciphering Response) to LTE Anchor/SGSN.
After the completing steps 705, LTE Anchor/SGSN has just realized described authentication function, can support that UE has carried out subsequent communications.
Step 706:UE sends the PDP Context request (ActivatePDP Context Request) that activates to LTE Anchor/SGSN.
Step 707:LTE Anchor/SGSN sends the PDP Context request (Create PDP Context Request) of creating to SAE Anchor.
Step 708:SAE Anchor sends to LTE Anchor/SGSN and creates PDP Context response (Create PDP Context Response).
Step 709:LTE Anchor/SGSN sends to UE and activates PDP Context acceptance (ActivatePDP Context Accept) message.
So far, UE has successfully inserted SAE Anchor by 3GPP Network, can receive the 3GPP business by LTEAnchor/SGSN; And in the time of in 3GPP Network, UE uses GTP or strengthens GTP communication.
Below, with embodiment the described process that communicates to connect management and renewal ipsec tunnel is described in detail.
Embodiment one, UE communicate to connect management when 3GPP Network moves to non 3GPP Network:
Referring to Fig. 8, Fig. 8 is the mobile management flow chart of a preferred embodiment of the present invention, and this flow process may further comprise the steps:
Step 801: when UE had business in 3GPP Network, UE can communicate alternately by SAE Anchor and external network; When moving to non3GPP Network by 3GPP Network in communication process, UE need carry out access authentication procedure with the non 3GPP GW among the non 3GPP Network.
Step 802:non 3GPP GW is according to the UE information that is obtained in access authentication procedure, and (AAA Server) carries out the verification process at UE with the HSS/ AAA server.
Step 803: by carrying out the IP address assignment process with non 3GPP GW, UE obtains to be supported in the IP address of communicating by letter among the non 3GPP Network, i.e. Local IP address.
Step 804:UE obtains the IP address of SAE Anchor by the dns resolution process.Certainly, the IP address of the SAE Anchor that UE obtained should have identical version with described Local IP address.
Step 805:UE sends internet network IKE _ security association _ initiation request (IKE_SA_INIT request) to SAE Anchor.
Step 806:SAE Anchor sends internet network IKE _ security association _ initiation response (IKE_SA_INIT response) to UE.
Step 805 to step 806 has realized the IKE_SA_INIT interacting message between UE and the SAE Anchor, and interactive messages comprises cryptographic algorithm, random number etc.
Step 807:UE sends the internet network IKE _ authentication request (IKE_AUTH request) that comprises UE sign (ID) to SAE Anchor, and notice SAE Anchor is carried on EAP (the EAP over IKE) process on the IKE.
Step 808:SAE Anchor sends the internet network IKE _ authentication response (IKE_AUTH response) that comprises Extensible Authentication Protocol (EAP) message and AUTH parameter to UE.
Step 809 to step 811:SAE Anchor according to from the IKE_AUTH request of UE, be carried on EAP (EAP over IKE) process on the IKE with HSS/AAA Server at UE.Record the corresponding description of the concrete operations that comprised at EAP over IKE process among the 3GPP TS 33.234.
Particularly, EAP over IKE process comprises:
Step 809:SAE Anchor and HSS/AAA Server are carried on EAP (EAP over AAA protocol) process on the aaa protocol at UE.
Step 810:UE finishes the authentication to SAE Anchor, and sends the IKE_AUTH request that comprises EAP message to SAE Anchor.Generally include the parameters for authentication that UE calculates in the described EAP message.
Step 811:SAE Anchor finishes the authentication to UE, and sends the IKE_AUTH response that comprises EAP success (EAP success) message to UE.
In fact, described EAP over IKE process be exactly at present common SAE Anchor be the process that UE sets up ipsec tunnel; After finishing this EAP over IKE process, SAE Anchor just is used to support the ipsec tunnel of communicating by letter for UE has successfully set up.
Step 812: finish after the described EAP over IKE process, UE sends the IKE_AUTH request that comprises AUTH message to SAE Anchor.
Step 813:SAE Anchor is that UE distributes Remote IP address, and the RemoteIP address of being distributed is carried among the IKE_AUTH response sends to UE.Certainly, SAE Anchor also sets up the Local IP address of UE and the binding relationship between the Remote IP address.
The LTE Anchor/SGSN of step 814:UE in 3GPP Network sends the request of deexcitation PDP Context.
Step 815:LTE Anchor/SGSN sends the request of deletion PDP Context to SAE Anchor.
The PDP Context that step 816:SAE Anchor deletion was once created for UE, and to the response of LTEAnchor/SGSN transmission deletion PDP Context.
Step 817:LTE Anchor/SGSN sends the deexcitation PDP Context to UE and accepts message.
After this, when receiving that the Remote IP address with UE from external network is the packet of destination address, SAE Anchor just according to own be the pairing Local IP address, Remote IP address that the binding relationship of Remote IP address that UE write down and LocalIP address finds UE, and the packet received is sent to UE by the ipsec tunnel of being set up between self and the UE.
After UE moved to non 3GPP Network from 3GPP Network, user face protocol stack when UE inserts non3GPP Network and chain of command protocol stack were respectively as Fig. 9, shown in Figure 10.
Embodiment two, the UE mobile management when non 3GPP Network moves to 3GPP Network:
Referring to Figure 11, Figure 11 is the mobile management flow chart of the another preferred embodiment of the present invention, and this flow process may further comprise the steps:
Step 1101: when business being arranged and move to 3GPP Network in non 3GPP Network, UE need use prior art and LTE Anchor/SGSN carries out attaching process, to be attached among the 3GPP Network.
Step 1102:LTE Anchor/SGSN is according to the UE information that obtained in attaching process, carries out verification process at UE with HSS/AAA Server.
Step 1103:UE sends packet data protocol (PDP) to LTE Anchor/SGSN and activates request.
Step 1104: receive that LTE Anchor/SGSN sends the PDP request to create to SAEAnchor when activating request from the PDP of UE.
Step 1105: when receiving the PDP request to create from LTE Anchor/SGSN, SAE Anchor sends PDP to LTE Anchor/SGSN and creates response.
Step 1106: receive when creating response that LTE Anchor/SGSN sends PDP to UE and activates and accept message from the PDP of SAE Anchor.
The operation of the above-mentioned PDP of relating to is actually common PDP constructive process at present, and this PDP constructive process can guarantee the smooth foundation of GTP tunnel.
So far, be used to support the PDP Context of UE communication to create successfully, and be used to support the GTP tunnel of UE communication also successfully to set up.After this, SAE Anchor can transmit the packet of UE by the described GTP tunnel of setting up.
Certainly, further operation shown in the execution in step 1107,1108 is the ipsec tunnel that UE was set up in non3GPP Network with deletion before.
Step 1107:UE sends information request (Informational request) to SAE anchor, is the ipsec tunnel that UE set up before the request SAE Anchor deletion.
Carry deletion payload (delete payload) among the described Informational request and ask, it is the ipsec tunnel that UE set up that this delete payload request SAE Anchor is known needs before the deletion.
Step 1108: when receiving the Informational request from UE, be the ipsec tunnel that UE set up before the SAE Anchor deletion, and send information response (Informational reply) to UE, notice UE has successfully deleted ipsec tunnel.
Above-mentioned Informational request and Informational reply are to transmit by the non 3GPP GW among the non3GPP Network usually.
After this, if SAE anchor receives the data that will send to UE, SAE anchor just can directly send to UE by 3GPP Network with described data.
In fact, described ipsec tunnel also can trigger deletion by network side; And,, so also can not delete described ipsec tunnel if UE supports multi-access systems.
When UE after non 3GPP Network moves to 3GPP Network, user face protocol stack when UE inserts 3GPPNetwork and chain of command protocol stack are respectively as shown in Figure 12 and Figure 13.
Mobile management when embodiment three, UE move to another non 3GPPNetwork by a non 3GPP Network:
Referring to Figure 14, Figure 14 is the present invention's mobile management flow chart of a preferred embodiment again, and this flow process may further comprise the steps:
Step 1401: when moving to New non3GPP Network by Old non 3GPP Network in communication process, UE need carry out access authentication procedure with the New non3GPP GW among the New non 3GPP Network that moves to.
Step 1402:New non 3GPP GW is according to the UE information that obtained in access authentication procedure, carries out verification process at UE with HSS/AAA Server.
Step 1403: by carrying out the IP address assignment process with New non 3GPP GW, UE obtains to be supported in the IP address of communicating by letter among the New non 3GPP Network that moves to, i.e. Local IP address.
Step 1404:UE sends the Informational request that comprises newly assigned described LocalIP address to the SAE Anchor for its service, the ipsec tunnel between request SAE Anchor renewal and the UE.
Step 1405: when receiving the Informational request from UE, SAE Anchor upgrades the ipsec tunnel between self and the UE, preserves the Local IP address that is comprised among the Informational request; And, also sending Informational reply to UE in this Local IP address and for rebuliding binding relationship between the Remote IP address that UE distributed, notice UE has successfully upgraded ipsec tunnel.
Informational request that is carried out between UE and the SAE Anchor and Informationalreply's is mutual, normally realizes by the MOBIKE agreement.
After this, when receiving that the Remote IP address with UE from external network is the packet of destination address, SAE Anchor just finds the pairing Local IP address, Remote IP address of UE according to own binding relationship for Remote IP address that UE rebulid and Local IP address, and the packet the received ipsec tunnel by renewal is sent to UE.
In above-mentioned three embodiment, the communication that UE carried out normally realizes by the non 3GPP GW among the non3GPP Network at UE place.
By above three embodiment as seen, UE can use the MOBIKE agreement to comprise the operation of one of ipsec tunnel establishment, modification, deletion action at least in non 3GPP Network; And no matter UE is mobile still for UE upgrades ipsec tunnel between non 3GPP Network and 3GPP Network, all no longer relate to MIP technology such as MIP agreement, MIP tunnel, and UE can both carry out subsequent communications smoothly.
In actual applications, SAE Anchor Transmit-Receive Unit and the ipsec tunnel creating unit that is connected with each other can be set in SAE Anchor.Wherein, the ipsec tunnel creating unit can be set up the ipsec tunnel that is used to support UE communication in non 3GPPNetwork; SAE Anchor Transmit-Receive Unit then is used for supporting ipsec tunnel to set up communicating by letter between process UE and the SAE Anchor.Concrete ipsec tunnel is set up process and is described in aforementioned content, is not giving unnecessary details at this.
Have again, UE packet retransmission unit can also be set in SAE Anchor, be used for finding pairing Local IP address, described Remote IP address, and the packet that will send to UE sends to the Local IP address that finds according to Remote IP address and the binding relationship between the Local IP address of UE; Particularly, described packet is to send to UE's by the ipsec tunnel of setting up for UE.
Obviously, system provided by the present invention, apparatus and method are the applying MIP tunnel no longer, makes the complexity of system obtain effective reduction; And because applying MIP technology and only use ipsec technology no longer, so UE only can be assigned with the mailing address relevant with ipsec technology in communication process, and this has obviously reduced the waste to interface-free resources and address resource; Have again, because applying MIP technology no longer, so UE also need not support the MIP agreement; In addition, when UE switches, only need upgrade and need not the MIP tunnel be upgraded ipsec tunnel, this can significantly reduce the communication delay that causes because of the UE switching.
Claims (14)
1. a system that realizes mobile management is characterized in that, this system comprises System Architecture Evolution anchor point SAE Anchor;
Wherein, described SAE Anchor, be used for when UE is moved to non-3rd Generation Partnership Project network non 3GPP Network by 3rd Generation Partnership Project network 3GPP Network, in non 3GPP Network, set up the internet safe ipsec tunnel that is used to support UE communication;
Described UE is used for using general packet radio service tunnel agreement GTP or strengthens GTP communication when 3GPP Network, use ipsec tunnel communication in the time of in non 3GPP Network.
2. the system as claimed in claim 1, it is characterized in that, described SAE Anchor, be further used for finding pairing Local IP address, described RemoteIP address, and the packet of receiving is sent to UE by described ipsec tunnel according to the described binding relationship between Remote IP address and the Local IP address.
3. system as claimed in claim 1 or 2 is characterized in that, described SAE Anchor is the gateway that connects outside public data network PDN.
4. a SAE Anchor who realizes mobile management is characterized in that, is provided with the ipsec tunnel creating unit that links to each other with SAE Anchor Transmit-Receive Unit among this SAE Anchor;
Wherein, the ipsec tunnel creating unit is used to the UE that moves to non 3GPPNetwork by 3GPP Network to set up ipsec tunnel;
SAE Anchor Transmit-Receive Unit is used for supporting ipsec tunnel to set up communicating by letter between process UE and the SAE Anchor.
5. SAE Anchor as claimed in claim 4, it is characterized in that, further be provided with UE packet retransmission unit among the described SAE Anchor, be used for finding pairing Local IP address, described Remote IP address, and the packet that will send to UE by the described ipsec tunnel of setting up for UE sends to the LocalIP address that finds according to Remote IP address and the binding relationship between the Local IP address of UE.
6. realize mobility management method for one kind, it is characterized in that this method comprises:
When UE moved to non 3GPP Network by 3GPP Network, SAE Anchor set up the ipsec tunnel that is used to support UE communication in non3GPP Network.
7. method as claimed in claim 6, it is characterized in that, SAE Anchor further distributes the address by the professional employed Remote IP of non 3GPP Network visit 3GPP for UE, also sets up binding relationship at RemoteIP and UE between the Local IP address that non 3GPP network obtains.
8. method as claimed in claim 7 is characterized in that, when receiving that when being the packet of destination address with described Remote IP address, this method further comprises:
Find pairing Local IP address, described Remote IP address according to the described binding relationship between Remote IP address and the Local IP address, and the packet of receiving is sent to UE by described ipsec tunnel.
9. as claim 6 or 7 described methods, it is characterized in that described SAE Anchor is the gateway that connects outside PDN.
10. as claim 6 or 7 described methods, it is characterized in that described SAEAnchor uses the MOBIKE agreement to comprise the operation of one of ipsec tunnel establishment, modification, deletion action at least in non3GPPNetwork.
11., it is characterized in that UE moves to the 3GPP Network from non 3GPPNetwork as claim 6 or 7 described methods, this method further comprises:
In described 3GPP Network, carry out the constructive process of GTP tunnel for UE.
12. method as claimed in claim 11 is characterized in that, further deletion is the described ipsec tunnel that UE set up in non 3GPPNetwork.
13., it is characterized in that UE moves to the New non 3GPP Network from the Oldnon 3GPP Network at current place as claim 6 or 7 described methods, this method further comprises:
New non 3GPP GW among the New non 3GPP is that UE is distributed in the IP address of communicating by letter among the New non 3GPPNetwork; And, be the SAE Anchor renewal of UE service and the ipsec tunnel between the UE.
14. method as claimed in claim 6 is characterized in that, described UE uses GTP tunnel/enhancing GTP tunnel communication in 3GPP Network the time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006101398007A CN101155126A (en) | 2006-09-25 | 2006-09-25 | System, device and method for implementing mobility management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006101398007A CN101155126A (en) | 2006-09-25 | 2006-09-25 | System, device and method for implementing mobility management |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101155126A true CN101155126A (en) | 2008-04-02 |
Family
ID=39256573
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2006101398007A Pending CN101155126A (en) | 2006-09-25 | 2006-09-25 | System, device and method for implementing mobility management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101155126A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009155848A1 (en) * | 2008-06-24 | 2009-12-30 | 华为技术有限公司 | Method, network system and device for service processing of multimode and multi-access terminal |
| CN101335703B (en) * | 2008-05-30 | 2011-08-10 | 中兴通讯股份有限公司 | End-to-end QoS guaranty method |
| CN102316602A (en) * | 2010-07-09 | 2012-01-11 | 中兴通讯股份有限公司 | System, device and method for accessing user equipment into mobile network |
| CN102685921A (en) * | 2011-03-11 | 2012-09-19 | 中兴通讯股份有限公司 | Dual-channel communication method and system |
| CN105075306A (en) * | 2013-01-22 | 2015-11-18 | 华为技术有限公司 | Method and network device for security authentication of mobile communication system |
| CN107070755A (en) * | 2011-06-08 | 2017-08-18 | 阿尔卡特朗讯 | Method and device for providing network insertion for user subject |
-
2006
- 2006-09-25 CN CNA2006101398007A patent/CN101155126A/en active Pending
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101335703B (en) * | 2008-05-30 | 2011-08-10 | 中兴通讯股份有限公司 | End-to-end QoS guaranty method |
| WO2009155848A1 (en) * | 2008-06-24 | 2009-12-30 | 华为技术有限公司 | Method, network system and device for service processing of multimode and multi-access terminal |
| CN102316602A (en) * | 2010-07-09 | 2012-01-11 | 中兴通讯股份有限公司 | System, device and method for accessing user equipment into mobile network |
| WO2012003770A1 (en) * | 2010-07-09 | 2012-01-12 | 中兴通讯股份有限公司 | System, device and method for user equipment to access mobile network |
| CN102316602B (en) * | 2010-07-09 | 2016-04-13 | 中兴通讯股份有限公司 | A kind of system, Apparatus and method for of subscriber equipment access to mobile network |
| CN102685921A (en) * | 2011-03-11 | 2012-09-19 | 中兴通讯股份有限公司 | Dual-channel communication method and system |
| WO2012122910A1 (en) * | 2011-03-11 | 2012-09-20 | 中兴通讯股份有限公司 | Dual-channel communication method and system |
| CN107070755A (en) * | 2011-06-08 | 2017-08-18 | 阿尔卡特朗讯 | Method and device for providing network insertion for user subject |
| US10992674B2 (en) | 2011-06-08 | 2021-04-27 | Nokia Technologies Oy | Method and apparatus for providing network access to a user entity |
| CN105075306A (en) * | 2013-01-22 | 2015-11-18 | 华为技术有限公司 | Method and network device for security authentication of mobile communication system |
| CN105075306B (en) * | 2013-01-22 | 2019-05-28 | 华为技术有限公司 | The method and the network equipment of the safety certification of mobile communication system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7561692B2 (en) | Method of authenticating mobile terminal | |
| JP5189107B2 (en) | Mechanism for uniquely identifying and unifying packet bearer context user sets in mobile communication networks | |
| KR101268578B1 (en) | An Apparatus and a Method for Service Continuity between UMTS network and WLAN network | |
| CN100579123C (en) | Processing method for ensuring information safety in communication system | |
| CN101212461B (en) | Data transmission method and system and core network gateway during switching of heterogeneous IP network | |
| CN101448248B (en) | Method for processing different user attach types by core network of evolved packet system | |
| US20090323635A1 (en) | Method of managing inter working for transferring multiple service sessions between a mobile network and a wireless local area network, and corresponding equipment | |
| CN101631354B (en) | Method, device and system for selecting packet data network | |
| US20090239543A1 (en) | Communication device and communication method | |
| CN102695236B (en) | A kind of data routing method and system | |
| WO2006135216A1 (en) | System and method for tunnel management over a 3g-wlan interworking system | |
| CN105578468A (en) | Packet-forwarding method for proxy mobile IP | |
| CN102546154A (en) | Mobile communication network and switching method of terminal | |
| WO2010124486A1 (en) | Method for establishing chained connection, serving gateway and packet data network gateway | |
| CN101155126A (en) | System, device and method for implementing mobility management | |
| CN103428800A (en) | Route selection method and functional network element | |
| CN101990312B (en) | Connection establishing method of mobile network and system | |
| CN103167461B (en) | Conversation processing method and device | |
| CN101472262B (en) | Method for realizing access network | |
| KR101268579B1 (en) | An Apparatus and a Method for Service Continuity between UMTS network and WLAN | |
| CN104113930B (en) | A kind of method and system for realizing user's termination connection | |
| CN101605373B (en) | Method and system for controlling UE to access to APN | |
| CN103220817A (en) | Session establishing method and device | |
| CN101471840B (en) | Network connection method and network system | |
| CN103582159A (en) | Method and system for establishing multiple connections in fixed and mobile convergence scene |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20080402 |