CN101656944A - Anchoring data pathway function entity transfer method and apparatus - Google Patents
Anchoring data pathway function entity transfer method and apparatus Download PDFInfo
- Publication number
- CN101656944A CN101656944A CN200810141929A CN200810141929A CN101656944A CN 101656944 A CN101656944 A CN 101656944A CN 200810141929 A CN200810141929 A CN 200810141929A CN 200810141929 A CN200810141929 A CN 200810141929A CN 101656944 A CN101656944 A CN 101656944A
- Authority
- CN
- China
- Prior art keywords
- message
- network gateway
- business network
- dpf
- asn
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 98
- 238000004873 anchoring Methods 0.000 title claims abstract description 96
- 230000037361 pathway Effects 0.000 title claims abstract description 67
- 238000012546 transfer Methods 0.000 title claims abstract description 26
- 230000004044 response Effects 0.000 claims abstract description 11
- 230000005012 migration Effects 0.000 claims description 50
- 238000013508 migration Methods 0.000 claims description 50
- 230000008569 process Effects 0.000 claims description 41
- 230000005540 biological transmission Effects 0.000 claims description 24
- 238000012856 packing Methods 0.000 abstract 1
- 238000010586 diagram Methods 0.000 description 34
- 238000004891 communication Methods 0.000 description 16
- 239000003795 chemical substances by application Substances 0.000 description 14
- 230000007704 transition Effects 0.000 description 10
- 230000003993 interaction Effects 0.000 description 7
- 238000013475 authorization Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000012467 final product Substances 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000004321 preservation Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
- H04W88/182—Network node acting on behalf of an other network entity, e.g. proxy
Abstract
Embodiments of the invention disclose an anchoring data pathway function entity transfer method and apparatus, to realize transfer of anchoring data pathway function entity. The method comprises: an agent mobile internet protocol client at original access service network gateway generating register request RRQ message with external agent deliver address FA-CoA of a target access service network gateway as terminal; the original access service network gateway transmitting an Anchor_DPF_HO_Req message of packing all TQ message, such that the target access service network gateway transmits the RRQ message to a home agent HA; after the target access service network gateway receives the register response RRP from the HA, the original access service network gateway receiving the message that thetarget access service network gateway packs all Anchor_DPF_HO_Req messages of the RRP messages.
Description
Technical field
The invention belongs to communication technical field, relate in particular to a kind of method and apparatus of anchoring data pathway function entity transfer.
Background technology
WiMAX (Worldwide Interoperability for Microwave Access, worldwide interoperability for microwave insert) technology is that the serial wideband wireless standard with IEEE 802.16 is a kind of air-interface standard that the basis proposes.Current WiMAX network wireless side is mainly based on IEEE 802.16d/e standard; 802.16d standard definition support MAC (Medium AccessControl, medium access control) layer and corresponding a plurality of physical layer framework of the fixed broadband wireless access system of multiple business type; 802.16e standard has increased the new function of part on the basis of 802.16d standard, to support user's mobility.
Fig. 1 is a WiMAX network architecture reference model, mainly comprise three parts: client (mobilestation/subscriber station, be called for short MS/SS, be portable terminal/registration terminal), accessing business network (Access Service Network, be called for short ASN) and connect service network (Connectivity ServiceNetwork is called for short CSN).
Wherein, ASN can comprise base station (Base Station is called for short BS) and accessing business network gate (Access Service Network Gateway is called for short ASN GW); CSN can comprise logic entities such as PPS (Prepaid Service, pre-payment) server, AAA (Authorization, Authentication andAccounting, authentication) server.
In existing protocol, communicate by the interface from R1 to R6 between the logic entity between MS/SS, ASN, the CSN, as Fig. 1, wherein the R1 interface is a wireless air interface, mainly by the IEEE802.16d/e definition, R2 is a logic interfacing, and R3, R4, R5 interface are wireline interface.
MS/SS can switch between different ASN.Under some scene, after ASN switched, the anchoring data pathway function entity of described MS/SS need move.
The inventor finds, in the prior art, when anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, the information interaction that the technical scheme of the migration of described anchoring data pathway function entity relates to was too redundant, has wasted the communication resource.
Summary of the invention
The embodiment of the invention discloses a kind of method, device and system of anchoring data pathway function entity transfer, to realize the migration of anchoring data pathway function entity.
A kind of method of anchoring data pathway function entity transfer is characterized in that, this method comprises:
The proxy mobile internet protocol client that is positioned at former access business network gateway is that terminal MS generates the register requirement rrq message according to external agent's Care-of Address FA-CoA of target access business network;
Described former access business network gateway sends Anchor_DPF_HO_Req message to described target access business network gateway, be packaged with described rrq message in the described Anchor_DPF_HO_Req message, so that described target access business network gateway sends to home agent HA with described rrq message;
After described target access business network gateway receives from the registration of described HA response RRP message, described former access business network gateway receives the Anchor_DPF_HO_Rsp message from described target access business network gateway, is packaged with described RRP message in the described Anchor_DPF_HO_Rsp message.
A kind of moving apparatus of anchoring data pathway function entity is characterized in that, comprising:
The proxy mobile internet protocol client modules: the external agent's Care-of Address FA-CoA that is used for according to the target access business network is that terminal MS generates the register requirement rrq message;
First sending module: be used for that the rrq message that described proxy mobile internet protocol client modules generates is encapsulated in Anchor_DPF_HO_Req message and send to target access business network gateway;
First receiver module: be used to receive the Anchor_DPF_HO_Rsp message that is packaged with registration response RRP message from described target access business network gateway.
By using embodiment of the invention the methods and apparatus disclosed, proxy mobile internet protocol client on the former access business network gateway is that terminal generates rrq message according to external agent's Care-of Address of target access business network, by described former access business network gateway described rrq message is encapsulated in and sends to target access business network gateway in the Anchor_DPF_HO_Req message, and reception is finished the migration of A-DPF from the Anchor_DPF_HO_Rsp message that is packaged with RRP message of described target access business network gateway.When anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, described method had compared with prior art been omitted redundant information exchanging process, has saved the communication resource.
Description of drawings
Fig. 1 is a WIMAX cellular logic structure chart;
Fig. 2 is the method flow diagram of the disclosed anchoring data pathway function entity transfer of the embodiment of the invention;
Fig. 3 is the method flow diagram of the disclosed anchoring data pathway function entity transfer of the embodiment of the invention;
Fig. 4 is the method flow diagram of the disclosed anchoring data pathway function entity transfer of the embodiment of the invention;
Fig. 5 is the method flow diagram of the disclosed anchoring data pathway function entity transfer of the embodiment of the invention;
Fig. 6 is the method flow diagram of the disclosed anchoring data pathway function entity transfer of the embodiment of the invention;
Fig. 7 is the disclosed anchoring data pathway function entity transfer apparatus structure of an embodiment of the invention schematic diagram.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, the specific embodiment of the invention is described in further detail below in conjunction with accompanying drawing.
The embodiment of the invention discloses a kind of method of anchoring data pathway function entity transfer.
In embodiments of the present invention, former accessing business network network (diagram ASN (a)) is the access business network at anchoring data pathway function entity (the diagram Old A-DPF) place before the migration, and target access network is the access business network at the anchoring data pathway function entity after moving (diagram New A-DPF) place.The described initial scene of the embodiment of the invention is that the access business network that MS inserts is described ASN (b), but the anchoring data pathway function entity of described MS (A-DPF) do not move as yet, still is the described Old A-DPF that is positioned at described ASN (a).
Described method as shown in Figure 2, concrete steps are as follows:
GW (the Gate Way of step 201, described ASN (a), gateway, hereinafter referred to as ASN (a) GW) on PMIP Client (Proxy Mobile Internet Protocol Client, the proxy mobile internet protocol client) the external agent's Care-of Address according to described ASN (b) is that described MS generates RRQ (Registration Request, register requirement) message; Described ASN (a) GW sends Anchor_DPF_HO_Req message to ASN (b) GW, is packaged with described rrq message in the described Anchor_DPF_HO_Req message.
Step 203, described HA reply RRP (Registration Response, registration response) message to described ASN (b) GW, finish the PMIP registration.
Step 204, described ASN (b) GW are encapsulated in the described RRP message that receives in the step 204 and send to described ASN (a) GW in the Anchor_DPF_HO_Rsp message.
Described ASN (a) succeeds in registration according to the described PMIP of described RRP message authentication, and the DPF on described ASN (b) GW promptly becomes described New A-DPF, and the A-DPF migration is so far finished.
By using embodiment of the invention disclosed method, PMIP Client on ASN (a) GW is that described MS generates rrq message according to external agent's Care-of Address of described ASN (b), by described ASN (a) GW described rrq message is encapsulated in and sends to ASN (b) GW in the Anchor_DPF_HO_Req message.Carry out PMIP registration by described ASN (b) GW and HA, and RRP message is encapsulated in sends to described ASN (a) GW in the Anchor_DPF_HO_Rsp message, finish the migration of A-DPF.When anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, described method had compared with prior art been omitted redundant information exchanging process, has saved the communication resource.
The following preferred embodiment of describing the method for described anchoring data pathway function entity transfer according to the residing different conditions of MS respectively.
The embodiment of the invention discloses a kind of method of anchoring data pathway function entity transfer.
It is example that the embodiment of the invention is in activated state (Active) with MS, and the method for anchoring data pathway function entity transfer is described.In embodiments of the present invention, former accessing business network network (diagram ASN (a)) is the access business network at anchoring data pathway function entity before moving (diagram Old A-DPF) and anchoring authentication device (diagram Old A-Authenticator) place, and target access network is the access business network at anchoring data pathway function entity after moving (diagram New A-DPF) and anchoring authentication device (diagram New A-Authenticator) place.The described initial scene of the embodiment of the invention is that the access business network that MS inserts is described ASN (b), but the anchoring data pathway function entity of described MS (A-DPF) and anchoring authentication device (A-Authenticator) do not move as yet, still for being positioned at described Old A-DPF and the Old A-Authenticator of described ASN (a).
Described method as shown in Figure 3, concrete steps are as follows:
Step 301, if the migration of described anchoring data pathway function entity initiate by described ASN (b), then carry out this step: GW (the Gate Way of described ASN (b), gateway, hereinafter referred to as ASN (b) GW) send Anchor_DPF_HO_Trigger message to the GW of described ASN (a) (hereinafter referred to as ASN (a) GW), described Anchor_DPF_HO_Trigger message is used to indicate described ASN (a) to carry out the A-DPF migration.Carry external agent's Care-of Address (Foreign Agent-Care of Address, diagram FA-CoA) of described ASN (b) in the described Anchor_DPF_HO_Trigger message.The FA-CoA that preserves described ASN (b) on described ASN (b) GW is a prior art, repeats no more herein.
Optionally, also carry the information that authentication device moves required transmission in the described Anchor_DPF_HO_Req message, MS Security History (terminal security history) information for example, alternatively, the information that described authentication device moves required transmission can also comprise any several of following message: MS AuthorizationContext (authorization terminal context), REG Context (registration context), Anchor MM Context (grappling MM Context), Authenticator ID (authentication device sign, described authentication device is a described MS authentication device at that time, i.e. anchoring authentication device before the migration), BS ID (Base Station Identification).
Need to prove that if the migration of described anchoring data pathway function entity initiated by described ASN (a), and described ASN (a) obtained described FA-CoA before the initial scene that the embodiment of the invention is described, and then omitted step 301, directly carried out this step.Application to prior art promptly may make described ASN (a) obtain described FA-CoA before the initial scene that the embodiment of the invention is described, for example in the access business network handoff procedure that took place before the initial scene that the embodiment of the invention is described, described ASN (a) may obtain described FA-CoA.Concrete acquisition methods repeats no more herein.
If the migration of described anchoring data pathway function entity is initiated by described ASN (a), but described ASN (a) does not also obtain described FA-CoA, then described ASN (a) sends anchoring data pathway function entity transfer to described ASN (b) and triggers message in advance, triggers described ASN (b) execution in step 301.It can be to be newly-increased R4 message that described anchoring data pathway function entity transfer triggers message in advance, also can be for carrying the existing R4 message that triggers indication information.
Step 306, described ASN (a) succeed in registration according to the described PMIP of described RRP message authentication, and the DPF on described ASN (b) GW promptly becomes described New A-DPF, and the A-DPF migration is so far finished.Described ASN (a) GW sends Context_Rpt message, the address of carrying described New A-DPF in the described Context_Rpt message to the BS that is positioned at described ASN (b) of the current access of described MS.Described New A-DPF promptly is positioned at the DPF on described ASN (b) GW.Described ASN (a) GW knows that the address of the DPF on described ASN (b) GW is a prior art.
Step 307, described BS send Context_Ack message to described ASN (a) GW, confirm the address that it has received described New A-DPF.
Need to prove, in embodiments of the present invention, step 306 to step 307 also can substitute with following scheme: described ASN (a) succeeds in registration according to the described PMIP of described RRP message authentication, and then described ASN (a) GW sends the RRP acknowledge message to described ASN (b) GW; Described ASN (b) GW sends Context_Rpt message, the address of carrying described New A-DPF in the described Context_Rpt message to the BS that is positioned at described ASN (b) of the current access of described MS; Described BS replys Context_Ack message to described ASN (b) GW and confirms.Described RRP acknowledge message can be newly-increased R4 message, also can be for carrying the existing R4 message of RRP affirmation indication information.
Step 309, described ASN (b) GW reply Relocation_Rsp message to described ASN (a) GW.
What described step 308 to step 309 was described is the negotiation of A-Authenticator migration, and described negotiation has two kinds of pattern: Pull (drawing) patterns or Push (pushing away) pattern, and step 308 to step 309 is the push pattern.The scheme of described push pattern can substitute with the scheme of pull pattern: described ASN (a) sends described RRP acknowledge message to described ASN (b) GW after succeeding in registration according to the described PMIP of the described RRP message authentication of step 305; After described ASN (b) GW receives described RRP acknowledge message, send Relocation_Notify message, notify described old A-Authenticator to carry out the A-Authenticator migration to the described ASN at described oldA-Authenticator place (a) GW; Described ASN (a) GW sends Relocation_Notify_Rsp message to described ASN (b) GW, carries the information that described authentication device moves required transmission in the described Relocation_Notify_Rsp message.
Need to prove, if carried the information that described authentication device moves required transmission in the described Anchor_DPF_HO_Req message in the step 302, the negotiations process of then described A-Authenticator migration can be omitted, be that step 308 to step 309 can be omitted, its replacement scheme also can be omitted.
Described Old A-Authenticator can enter " discrimination weight locking " state according to step 301 to arbitrary steps (except the step 303 and 304) or the message in its alternative steps between 309.Described " discrimination weight locking " state is used to stop the triggering of third party's entity to Old A-Authenticator discrimination weight process, specifically is defined as prior art, repeats no more herein.
Step 311, described ASN (b) GW send Relocation_Complete_Req message to described ASN (a) GW, carry the authenticating result indication in the described Relocation_Complete_Req message, notify finishing of described discrimination weight process.Optionally, can carry MS context request information in the described Relocation_Complete_Req message.
Step 312, described ASN (a) GW send Relocation_Complete_Rsp message to described ASN (b) GW.If carry MS context request information in the Relocation_Complete_Req message in the step 311, carry the MS contextual information that described MS context request information is asked in the then described Relocation_Complete_Rsp message.If the authenticating result described in the step 311 in the Relocation_Complete_Req message is designated as success, then described oldA-Authenticator stops described " discrimination weight locking " state.
Step 313, if carry described MS contextual information in the Relocation_Complete_Rsp message in the step 312, then carry out this step: described ASN (b) GW sends Relocation_Complete_Ack message to described ASN (a) GW.
If do not carry described MS contextual information in the described Relocation_Complete_Rsp message in the step 312, then described anchoring authentication device migrates to step 312 and promptly accuses and finish.If carry described MS contextual information in the described Relocation_Complete_Rsp message in the described step 312, then described anchoring authentication device migrates to step 313 and promptly accuses and finish, and the Authenticator on described ASN (b) GW becomes described New A-Authenticator.
By using embodiment of the invention disclosed method, former accessing business network gate ASN (a) GW can obtain the FA-CoA of target accessing business network, and be that MS generates rrq message according to described FA-CoA, by described ASN (a) GW described rrq message is encapsulated in and sends to ASN (b) GW in the Anchor_DPF_HO_Req message.Carry out PMIP registration by described ASN (b) GW and HA, and RRP message is encapsulated in sends to described ASN (a) GW in the Anchor_DPF_HO_Rsp message, finish the migration of A-DPF.When anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, described method had compared with prior art been omitted redundant information exchanging process, has saved the communication resource.Further, described ASN (a) GW can also be in the information interaction of described A-DPF transition process, trigger the common migration of A-Authenticator, avoided New A-DPF and NewA-Authenticator after the described migration to be positioned at different entities, further saved the communication resource.
The embodiment of the invention discloses a kind of method of anchoring data pathway function entity transfer
The embodiment of the invention is in MS and withdraws from Idle state (Idle), and Relay PC (the Relay Paging Controller that described MS inserts, the relaying paging controller) and Anchor PC (Anchor PagingController, anchoring paging controller) being positioned at different entities is example, and the method for anchoring data pathway function entity transfer is described.In embodiments of the present invention, former accessing business network network (diagram ASN (a)) is the access business network at anchoring data pathway function entity before moving (diagram Old A-DPF) and anchoring authentication device (diagram OldA-Authenticator) place, and target access network is the access business network at anchoring data pathway function entity after moving (diagram New A-DPF) and anchoring authentication device (diagram New A-Authenticator) place.The described initial scene of the embodiment of the invention is that the access business network that MS inserts is described ASN (b), but the anchoring data pathway function entity of described MS (A-DPF) and anchoring authentication device (A-Authenticator) do not move as yet, still for being positioned at described Old A-DPF and the Old A-Authenticator of described ASN (a).
Described method as shown in Figure 4, concrete steps are as follows:
Step 402, described BS send IM_Exit_State_Change_Req message to described ASN (b) GW at Relay PC (relaying paging controller) place, indicate described MS request to withdraw from Idle state.Anchor PC id field in the described IM_Exit_State_Change_Req message is provided with according to described PCID by described BS.
ASN (b) GW at step 403, described Relay PC place sends IM_Exit_State_Change_Req message to described ASN (a) GW at Anchor PC (anchoring paging controller, diagram A-PC) place, indicates described MS request to withdraw from Idle state.Carry the FA-CoA of described ASN (b) in the described IM_Exit_State_Change_Req message, indicate described ASN (a) to begin to carry out the A-DPF migration.The FA-CoA that preserves described ASN (b) on described ASN (b) GW is a prior art, repeats no more herein.ASN (b) GW at described Relay PC place determines the address of described ASN (a) GW at described Anchor PC place according to the Anchor PC id field in the message of IM_Exit_State_Change_Req described in the step 402.
Optionally, can also carry the information that authentication device moves required transmission in the described Anchor_DPF_HO_Req message, MS Security History information for example, perhaps, alternatively, the described authentication device information of moving required transmission can also comprise any several of following message: MS Authorization Context, REG Context, Anchor MM Context, Authenticator ID, BS ID etc.
Optionally, can also carry the information that described authentication device moves required transmission in the described IM_Exit_State_Change_Rsp message.
Step 410, described BS send Path_Reg_Req message according to the address of described new A-DPF to the described ASN (b) at described new A-DPF place GW, and new data path is set up in request.
Described ASN (b) GW at step 411, described new A-DPF place replys Path_Reg_Rsp message to described BS, confirms the foundation of new data path.
Need to prove, if all do not carry the information that described authentication device moves required transmission in described Anchor_DPF_HO_Req message in the step 404 and the described IM_Exit_State_Change_Rsp message in the step 408, then after step 408, before the step 413, with described step 409 to step 412 simultaneously, can also carry out following operation:
Described old A-Authenticator and be positioned at the negotiation of carrying out the A-Authenticator migration between the Authenticator on ASN (b) GW.Described negotiation has two kinds of pattern: Pull (drawing) patterns or Push (pushing away) pattern.
If the Pull pattern is adopted in described negotiation, then described ASN (b) GW sends Relocation_Notify message to the described ASN (a) at described old A-Authenticator place GW, notifies described oldA-Authenticator to carry out the A-Authenticator migration; Described ASN (a) GW sends Relocation_Notify_Rsp message to described ASN (b) GW, carries the information that described authentication device moves required transmission in the described Relocation_Notify_Rsp message.
If the Push pattern is adopted in described negotiation, described ASN (a) GW at then described old A-Authenticator place sends Relocation_Req message to described ASN (b) GW, carries the information that described authentication device moves required transmission in the described Relocation_Req message; Described ASN (b) GW sends Relocation_Rsp message to described ASN (a) GW.
The negotiations process of described A-Authenticator migration can trigger described Old A-Authenticator and enter " authentication device locking " state.
Need to prove that described old A-Authenticator can also enter " discrimination weight locking " state according to the message in step 403 or step 404 or step 407 or the step 408.Described " discrimination weight locking " state is used to stop the triggering of third party's entity counterweight authentication process, specifically is defined as prior art, repeats no more herein.
Carry out the mutual of L2 network re-entry process between step 413, described MS and the described BS, network side is that described MS carries out discrimination weight (Re-Authentication) by the Authenticator on described BS and described ASN (b) GW.Described discrimination weight process need is used described MS Security History information.Described L2 network re-entry process and discrimination weight process are prior art, repeat no more herein.
Step 414, described BS send Path_Reg_Ack message to the ASN (b) at described new A-DPF place GW.
If do not carry described MS contextual information in the described Relocation_Complete_Rsp message in the step 416, then described anchoring authentication device migrates to step 416 and promptly accuses and finish.If carry described MS contextual information in the described Relocation_Complete_Rsp message in the described step 416, then described anchoring authentication device migrates to step 417 and promptly accuses and finish, and the Authenticator on described ASN (b) GW becomes described New A-Authenticator.
By using embodiment of the invention disclosed method, former accessing business network gate ASN (a) GW can obtain the FA-CoA of target accessing business network, and be that MS generates rrq message according to described FA-CoA, by described ASN (a) GW described rrq message is encapsulated in and sends to ASN (b) GW in the Anchor_DPF_HO_Req message.Carry out PMIP registration by described ASN (b) GW and HA, and RRP message is encapsulated in sends to described ASN (a) GW in the Anchor_DPF_HO_Rsp message, finish the migration of A-DPF.When anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, described method had compared with prior art been omitted redundant information exchanging process, has saved the communication resource.Further, described ASN (a) GW can also be in the information interaction of described A-DPF transition process, trigger the common migration of A-Authenticator, avoided New A-DPF and NewA-Authenticator after the described migration to be positioned at different entities, further saved the communication resource.
The embodiment of the invention discloses a kind of method of anchoring data pathway function entity transfer
It is example that the embodiment of the invention enters Idle state (Idle) with MS self triggering, and the method for anchoring data pathway function entity transfer is described.In embodiments of the present invention, former accessing business network network (diagram ASN (a)) is the access business network at anchoring data pathway function entity after moving (diagram New A-DPF) and anchoring authentication device (diagram NewA-Authenticator) place for the access business network at anchoring data pathway function entity before moving (diagram Old A-DPF) and anchoring authentication device (diagram Old A-Authenticator) place, target access network.The described initial scene of the embodiment of the invention is that the access business network that MS inserts is described ASN (b), but the anchoring data pathway function entity of described MS (A-DPF) and anchoring authentication device (A-Authenticator) do not move as yet, still for being positioned at described Old A-DPF and the Old A-Authenticator of described ASN (a).
Described method as shown in Figure 5, concrete steps are as follows:
Step 501, MS send DREG-REQ message to the BS of the ASN of current access (b), and De-Registration Request code (de-registration request sign indicating number) parameter in the described DREG-REQ message is set to 0x01.Described DREG-REQ message is used to initiate the process that described MS enters Idle state.
Step 502, described BS send IM_Entry_State_Change_Req message to the described ASN (b) at PC (anchoring paging controller) place GW, indicate described MS request to enter Idle state.
Step 504, the PMIP Client that is positioned on described ASN (a) GW are that described MS generates rrq message according to described FA-CoA; Described ASN (a) GW sends Anchor_DPF_HO_Req message to described ASN (b) GW, is packaged with described rrq message in the described Anchor_DPF_HO_Req message.
Step 507, described ASN (b) GW send Anchor_DPF_HO_Rsp message to described ASN (a) GW, are packaged with the RRP message in the step 306 in the described Anchor_DPF_HO_Rsp message.
Step 508, described ASN (a) succeed in registration according to the described PMIP of described RRP message authentication, and the DPF on described ASN (b) GW promptly becomes described New A-DPF, and the A-DPF migration is so far finished.Described ASN (a) GW sends Relocation_Req message to described ASN (b) GW, carries the information that authentication device moves required transmission in the described Relocation_Req message.Described Relocation_Req message is used to begin the A-Authenticator transition process, indicates described A-DPF migration to finish simultaneously.
Step 509, described ASN (b) GW send Relocation_Rsp message to described ASN (a) GW.
Need to prove, step 508 to step 509 can be substituted by following scheme: described ASN (a) GW succeeds in registration according to the described PMIP of described RRP message authentication, and to ASN (b) GW transmission RRP acknowledge message, described RRP acknowledge message can be newly-increased R4 message, also can be for increasing the existing R4 message that RRP confirms indication; After described ASN (b) GW receives described RRP acknowledge message, send Relocation_Notify message to described ASN (a) GW and begin the A-Authenticator transition process; Described ASN (a) GW returns Relocation_Notify_Rsp message to described ASN (b) GW and responds, and carries the information that authentication device moves required transmission in the described Relocation_Notify_Rsp message.
Described old A-Authenticator can enter " discrimination weight locking " state according to step 503 to the message in the arbitrary steps of step 509 (step 505 to step 506 except) or its alternative steps.Described " discrimination weight locking " state is used to stop the triggering of third party's entity to Old A-Authenticator discrimination weight process, specifically is defined as prior art, repeats no more herein.
Step 511, described BS send IM_Entry_State_Change_Ack message to described ASN (b) GW.
ASN (b) GW at step 513, described new A-Authenticator place sends Relocation_Complete_Req message to the ASN at described oldA-Authenticator place (a) GW, carry the authenticating result indication in the described Relocation_Complete_Req message, notify finishing of described discrimination weight process.Optionally, can carry MS context request information in the described Relocation_Complete_Req message.
If do not carry described MS contextual information in the described Relocation_Complete_Rsp message in the step 514, then described anchoring authentication device migrates to step 514 and promptly accuses and finish.If carry described MS contextual information in the described Relocation_Complete_Rsp message in the described step 514, then described anchoring authentication device migrates to step 515 and promptly accuses and finish, and the Authenticator on described ASN (b) GW becomes described New A-Authenticator.
Step 517, described BS send Path_DeReg_Req message to the described ASN (b) at described new A-DPF place GW after described management resource keeps timer expiry, data path is nullified in request.
Step 518, described ASN (b) GW reply Path_DeReg_Rsp message to described BS, confirm the cancellation of data path.
Need to prove that step 510 can not have sequential relationship with step 509, the two can take place simultaneously, also can change order.Step 510 can also occur in after the step 512, before the step 516, do not carry the described described BS information to described MS transmission DREG-CMD message after described MS carries out discrimination weight that is used to indicate at this moment in the described IM_Entry_State_Change_Rsp message in the step 510, step 511 then occurs between step 516 and the step 517, and the relative position of other steps is constant.
Step 516 to step 519 and step 513 to step 515 can not have sequential relationship yet, only need all occur in step 512 and get final product afterwards.
By using embodiment of the invention disclosed method, former accessing business network gate ASN (a) GW can obtain the FA-CoA of target accessing business network, and be that MS generates rrq message according to described FA-CoA, by described ASN (a) GW described rrq message is encapsulated in and sends to ASN (b) GW in the Anchor_DPF_HO_Req message.Carry out PMIP registration by described ASN (b) GW and HA, and RRP message is encapsulated in sends to described ASN (a) GW in the Anchor_DPF_HO_Rsp message, finish the migration of A-DPF.When anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, described method had compared with prior art been omitted redundant information exchanging process, has saved the communication resource.Further, described ASN (a) GW can also be in the information interaction of described A-DPF transition process, trigger the common migration of A-Authenticator, avoided New A-DPF and NewA-Authenticator after the described migration to be positioned at different entities, further saved the communication resource.
The embodiment of the invention discloses a kind of method of anchoring data pathway function entity transfer
It is example that the embodiment of the invention enters Idle state (Idle) with network side triggering MS, and the method for anchoring data pathway function entity transfer is described.In embodiments of the present invention, former accessing business network network (diagram ASN (a)) is the access business network at anchoring data pathway function entity after moving (diagram New A-DPF) and anchoring authentication device (diagram NewA-Authenticator) place for the access business network at anchoring data pathway function entity before moving (diagram Old A-DPF) and anchoring authentication device (diagram Old A-Authenticator) place, target access network.The described initial scene of the embodiment of the invention is that the access business network that MS inserts is described ASN (b), but the anchoring data pathway function entity of described MS (A-DPF) and anchoring authentication device (A-Authenticator) do not move as yet, still for being positioned at described Old A-DPF and the Old A-Authenticator of described ASN (a).
Described method as shown in Figure 6, concrete steps are as follows:
The BS of the ASN of step 601, the current access of MS (b) sends IM_Entry_State_Change_Req message to the described ASN (b) at PC (anchoring paging controller) place GW, indicates described MS to enter Idle state.
Step 602, described PC select self as Anchor PC (anchoring paging controller, diagram A-PC), and ASN (b) GW at described A-PC place sends Anchor_DPF_HO_Trigger message to described ASN (a) GW.Carry the FA-CoA of described ASN (b) in the described Anchor_DPF_HO_Trigger message.The FA-CoA that preserves described ASN (b) on described ASN (b) GW is a prior art, repeats no more herein.
Step 603, the PMIP Client that is positioned on described ASN (a) GW are that described MS generates rrq message according to described FA-CoA; Described ASN (a) GW sends Anchor_DPF_HO_Req message to described ASN (b) GW, is packaged with described rrq message in the described Anchor_DPF_HO_Req message.
Step 604, described ASN (b) GW transmit described rrq message to HA, beginning PMIP registration.
Step 605, described HA reply RRP message to described ASN (b) GW, finish the PMIP registration.
Step 606, described ASN (b) GW send Anchor_DPF_HO_Rsp message to described ASN (a) GW, are packaged with the RRP message in the step 306 in the described Anchor_DPF_HO_Rsp message.
Step 607, described ASN (a) succeed in registration according to the described PMIP of described RRP message authentication, and the DPF on described ASN (b) GW promptly becomes described New A-DPF, and the A-DPF migration is so far finished.Described ASN (a) GW sends Relocation_Req message to described ASN (b) GW, carries the information that authentication device moves required transmission in the described Relocation_Req message.Described Relocation_Req message is used to begin the A-Authenticator transition process, indicates described A-DPF migration to finish simultaneously.
Step 608, described ASN (b) GW send Relocation_Rsp message to described ASN (a) GW.
Need to prove, step 607 to step 608 can be substituted by following scheme: described ASN (a) GW succeeds in registration according to the described PMIP of described RRP message authentication, and to ASN (b) GW transmission RRP acknowledge message, described RRP acknowledge message can be newly-increased R4 message, also can be for increasing the existing R4 message that RRP confirms indication; After described ASN (b) GW receives described RRP acknowledge message, send Relocation_Notify message to described ASN (a) GW and begin the A-Authenticator transition process; Described ASN (a) GW returns Relocation_Notify_Rsp message to described ASN (b) GW and responds, and carries the information that authentication device moves required transmission in the described Relocation_Notify_Rsp message.
Described old A-Authenticator can enter " discrimination weight locking " state according to step 602 to the message in the arbitrary steps of step 608 (step 604 to step 605 except) or its alternative steps.Described " discrimination weight locking " state is used to stop the triggering of third party's entity to Old A-Authenticator discrimination weight process, specifically is defined as prior art, repeats no more herein.
Step 609, described ASN (b) GW send IM_Entry_State_Change_Rsp message to the BS of described ASN (b), the address of carrying described new A-DPF in the described IM_Entry_State_Change_Rsp message, optionally, also carry indication in the described IM_Entry_State_Change_Rsp message, be used to indicate described BS after described MS carries out discrimination weight, to send DREG-CMD message to described MS.
Step 610, MS are by carrying out discrimination weight (Re-Authentication) process between Authenticator on described BS and described ASN (b) GW and the AAA.
ASN (b) GW at step 611, described new A-Authenticator place sends Relocation_Complete_Req message to the ASN at described oldA-Authenticator place (a) GW, carry the authenticating result indication in the described Relocation_Complete_Req message, notify finishing of described discrimination weight process.Optionally, can carry MS context request information in the described Relocation_Complete_Req message.
Step 612, described ASN (a) GW send Relocation_Complete_Rsp message to described ASN (b) GW.If carry MS context request information in the Relocation_Complete_Req message in the step 611, carry the MS contextual information that described MS context request information is asked in the then described Relocation_Complete_Rsp message.If the authenticating result described in the step 611 in the Relocation_Complete_Req message is designated as success, then described oldA-Authenticator stops described " discrimination weight locking " state.
Step 613, if carry described MS contextual information in the Relocation_Complete_Rsp message in the step 612, then carry out this step: described ASN (b) GW sends Relocation_Complete_Ack message to described ASN (a) GW.
If do not carry described MS contextual information in the described Relocation_Complete_Rsp message in the step 612, then described anchoring authentication device migrates to step 612 and promptly accuses and finish.If carry described MS contextual information in the described Relocation_Complete_Rsp message in the described step 612, then described anchoring authentication device migrates to step 613 and promptly accuses and finish, and the Authenticator on described ASN (b) GW becomes described New A-Authenticator.
Step 614, described BS send DREG-CMD message to described MS, and instruct MS enters Idle state, and start management resource maintenance timer.
Step 615, described MS send DREG-REQ message to described BS, and enter Idle state.
Step 616, described BS send IM_Entry_State_Change_Ack message to described ASN (b) GW.
Step 617, described BS send Path_DeReg_Req message to the described ASN (b) at described new A-DPF place GW after described management resource keeps timer expiry, data path is nullified in request.
Step 618, described ASN (b) GW reply Path_DeReg_Rsp message to described BS, confirm the cancellation of data path.
Step 619, described BS send Path_DeReg_Ack message to the described ASN (b) at described new A-DPF place GW, finish the cancellation of data path.
Need to prove that step 609 can not have sequential relationship with step 608, the two can take place simultaneously, also can change order.Step 609 can also occur in after the step 610, before the step 614, do not carry in the described IM_Entry_State_Change_Rsp message in the step 609 this moment and describedly be used to indicate described BS information to described MS transmission DREG-CMD message described MS carries out discrimination weight after, and the relative position of other steps is constant.
Step 614 to step 619 and step 611 to step 613 can not have sequential relationship yet, only need all occur in step 610 and get final product later.
By using embodiment of the invention disclosed method, former accessing business network gate ASN (a) GW can obtain the FA-CoA of target accessing business network, and be that MS generates rrq message according to described FA-CoA, by described ASN (a) GW described rrq message is encapsulated in and sends to ASN (b) GW in the Anchor_DPF_HO_Req message.Carry out PMIP registration by described ASN (b) GW and HA, and RRP message is encapsulated in sends to described ASN (a) GW in the Anchor_DPF_HO_Rsp message, finish the migration of A-DPF.When anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, described method had compared with prior art been omitted redundant information exchanging process, has saved the communication resource.Further, described ASN (a) GW can also be in the information interaction of described A-DPF transition process, trigger the common migration of A-Authenticator, avoided New A-DPF and NewA-Authenticator after the described migration to be positioned at different entities, further saved the communication resource.
The embodiment of the invention discloses a kind of moving apparatus of anchoring data pathway function entity.
Described device comprises as shown in Figure 7:
The proxy mobile internet protocol client modules: the external agent's Care-of Address FA-CoA that is used for according to the target access business network is that terminal MS generates the register requirement rrq message;
First sending module: be used for that the rrq message that described proxy mobile internet protocol client modules generates is encapsulated in Anchor_DPF_HO_Req message and send to target access business network gateway;
First receiver module: be used to receive the Anchor_DPF_HO_Rsp message that is packaged with registration response RRP message from described target access business network gateway.
Described first sending module sends be packaged with described rrq message Anchor_DPF_HO_Req message and arrive described target access business network gateway after, described target access business network gateway sends to home agent HA with described rrq message.Before the Anchor_DPF_HO_Rsp message that is packaged with registration response RRP message of described first receiver module reception from described target access business network gateway, described target access business network gateway receives the described RRP message from described HA.
Optionally, described device also comprises:
Second receiver module: be used to receive Anchor_DPF_HO_Trigger message or IM_Exit_State_Change_Req message, carry external agent's Care-of Address FA-CoA of described target access business network in described Anchor_DPF_HO_Trigger message or the IM_Exit_State_Change_Req message from described target access business network gateway;
The described FA-CoA that described proxy mobile internet protocol client modules receives according to described second receiver module of target is that terminal MS generates the register requirement rrq message.
Optionally, described device also comprises:
Second sending module: the base station BS that is used for inserting to described MS sends Context_Rpt message or IM_Entry_State_Change_Rsp message or IM_Exit_State_Change_Rsp message, carries the address of the anchoring data pathway function entity after the migration in described Context_Rpt or IM_Entry_State_Change_Rsp or the IM_Exit_State_Change_Rsp message.
Optionally, described device also comprises:
The 3rd sending module: be used for sending IM_Exit_State_Change_Rsp message, carry the information that authentication device moves required transmission in the described IM_Exit_State_Change_Rsp message to described target access business network gateway.
Optionally, described device also comprises:
The 3rd receiver module: be used to receive Relocation_Complete_Req message, carry the authenticating result indication in the described Relocation_Complete_Req message from described target access business network gateway.
By using the disclosed device of present embodiment, former accessing business network gate ASN (a) GW can be that MS generates rrq message according to described FA-CoA, by described ASN (a) GW described rrq message is encapsulated in and sends to ASN (b) GW in the Anchor_DPF_HO_Req message.Carry out PMIP registration by described ASN (b) GW and HA, and RRP message is encapsulated in sends to described ASN (a) GW in the Anchor_DPF_HO_Rsp message, finish the migration of A-DPF.When anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, described method had compared with prior art been omitted redundant information exchanging process, has saved the communication resource.Further, described ASN (a) GW can also be in the information interaction of described A-DPF transition process, trigger the common migration of A-Authenticator, avoided NewA-DPF and New A-Authenticator after the described migration to be positioned at different entities, further saved the communication resource.
By using embodiment of the invention the methods and apparatus disclosed, former accessing business network gate ASN (a) GW can obtain the FA-CoA of target accessing business network, and be that MS generates rrq message according to described FA-CoA, by described ASN (a) GW described rrq message is encapsulated in and sends to ASN (b) GW in the Anchor_DPF_HO_Req message.Carry out PMIP registration by described ASN (b) GW and HA, and RRP message is encapsulated in sends to described ASN (a) GW in the Anchor_DPF_HO_Rsp message, finish the migration of A-DPF.When anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, described method had compared with prior art been omitted redundant information exchanging process, has saved the communication resource.Further, described ASN (a) GW can also be in the information interaction of described A-DPF transition process, trigger the common migration of A-Authenticator, avoided New A-DPF and NewA-Authenticator after the described migration to be positioned at different entities, further saved the communication resource.
Through the above description of the embodiments, the those skilled in the art can be well understood to the present invention and can realize by the mode that software adds essential general hardware platform, can certainly pass through hardware, but the former is better execution mode under a lot of situation.Based on such understanding, the part that technical scheme of the present invention contributes to prior art in essence in other words can embody with the form of software product, this computer software product is stored in the storage medium that can read, floppy disk as computer, hard disk or CD etc., comprise some instructions with so that computer equipment (can be personal computer, server, the perhaps network equipment etc.) carry out the described method of each embodiment of the present invention.
Above embodiment only in order to technical scheme of the present invention to be described, is not intended to limit; Although with reference to previous embodiment the present invention is had been described in detail, those of ordinary skill in the art is to be understood that: it still can be made amendment to the technical scheme that aforementioned each embodiment put down in writing, and perhaps part technical characterictic wherein is equal to replacement; And these modifications or replacement do not make the essence of appropriate technical solution break away from the spirit and scope of various embodiments of the present invention technical scheme.
Claims (15)
1, a kind of method of anchoring data pathway function entity transfer is characterized in that, this method comprises:
The proxy mobile internet protocol client that is positioned at former access business network gateway is that terminal MS generates the register requirement rrq message according to external agent's Care-of Address FA-CoA of target access business network;
Described former access business network gateway sends Anchor_DPF_HO_Req message to described target access business network gateway, be packaged with described rrq message in the described Anchor_DPF_HO_Req message, so that described target access business network gateway sends to home agent HA with described rrq message;
After described target access business network gateway receives from the registration of described HA response RRP message, described former access business network gateway receives the Anchor_DPF_HO_Rsp message from described target access business network gateway, is packaged with described RRP message in the described Anchor_DPF_HO_Rsp message.
2, the method for claim 1 is characterized in that, this takes a step forward and comprises step:
Described former access business network gateway receives the Anchor_DPF_HO_Trigger message from described target access business network gateway, carries described FA-CoA in the described Anchor_DPF_HO_Trigger message.
3, method as claimed in claim 2 is characterized in that, after this further comprises step:
Described former access business network gateway sends Context_Rpt message or IM_Entry_State_Change_Rsp message to the base station BS that described MS inserts, and carries the address of the anchoring data pathway function entity after the migration in described Context_Rpt message or the IM_Entry_State_Change_Rsp message;
Anchoring data pathway function entity after the described migration is the data pathway function entity that is positioned on the described target access business network gateway.
4, the method for claim 1 is characterized in that, this takes a step forward and comprises step:
Described former access business network gateway receives the IM_Exit_State_Change_Req message from described target access business network gateway, carries described FA-CoA in the described IM_Exit_State_Change_Req message.
5, method as claimed in claim 4 is characterized in that, after this further comprises step:
Described former access business network gateway sends IM_Exit_State_Change_Rsp message to the base station BS that described MS inserts, and carries the address of the anchoring data pathway function entity after the migration in the described IM_Exit_State_Change_Rsp message;
Anchoring data pathway function entity after the described migration is the data pathway function entity that is positioned on the described target access business network gateway.
6, the method for claim 1 is characterized in that,
Also carry the information that authentication device moves required transmission in the described Anchor_DPF_HO_Req message.
7, method as claimed in claim 4 is characterized in that, further comprises step:
Described former access business network gateway sends IM_Exit_State_Change_Rsp message to described target access business network gateway, carries the information that described authentication device moves required transmission in the described IM_Exit_State_Change_Rsp message.
8, as claim 6 or 7 described methods, it is characterized in that,
The information that described authentication device moves required transmission comprises the historical MS Security of terminal security History information;
Further comprise step:
Described MS carries out the discrimination weight process according to described MS Security History information by the serving BS of current access and new anchoring authentication device and authentication, authentication, the accounting server AAA that is positioned on the described target access business network gateway.
9, method as claimed in claim 8 is characterized in that, further comprises step before the described discrimination weight process:
The preceding anchoring authentication device of migration that is positioned on the described former access business network gateway enters " discrimination weight locking " state.
10, method as claimed in claim 9 is characterized in that, further comprises step:
Described former access business network gateway receives the Relocation_Complete_Req message from described target access business network gateway, carries the authenticating result indication in the described Relocation_Complete_Req message;
If described authenticating result is designated as success, the anchoring authentication device before the then described migration stops described " discrimination weight locking " state.
11, a kind of moving apparatus of anchoring data pathway function entity is characterized in that, comprising:
The proxy mobile internet protocol client modules: the external agent's Care-of Address FA-CoA that is used for according to the target access business network is that terminal MS generates the register requirement rrq message;
First sending module: be used for that the rrq message that described proxy mobile internet protocol client modules generates is encapsulated in Anchor_DPF_HO_Req message and send to target access business network gateway;
First receiver module: be used to receive the Anchor_DPF_HO_Rsp message that is packaged with registration response RRP message from described target access business network gateway.
12, device as claimed in claim 11 is characterized in that, also comprises:
Second receiver module: be used to receive Anchor_DPF_HO_Trigger message or IM_Exit_State_Change_Req message, carry external agent's Care-of Address FA-CoA of described target access business network in described Anchor_DPF_HO_Trigger message or the IM_Exit_State_Change_Req message from described target access business network gateway;
The described FA-CoA that described proxy mobile internet protocol client modules receives according to described second receiver module of target is that terminal MS generates the register requirement rrq message.
13, device as claimed in claim 11 is characterized in that, also comprises:
Second sending module: the base station BS that is used for inserting to described MS sends Context_Rpt message or IM_Entry_State_Change_Rsp message or IM_Exit_State_Change_Rsp message, carries the address of the anchoring data pathway function entity after the migration in described Context_Rpt or IM_Entry_State_Change_Rsp or the IM_Exit_State_Change_Rsp message.
14, device as claimed in claim 11 is characterized in that, also comprises:
The 3rd sending module: be used for sending IM_Exit_State_Change_Rsp message, carry the information that authentication device moves required transmission in the described IM_Exit_State_Change_Rsp message to described target access business network gateway.
15, device as claimed in claim 11 is characterized in that, also comprises:
The 3rd receiver module: be used to receive Relocation_Complete_Req message, carry the authenticating result indication in the described Relocation_Complete_Req message from described target access business network gateway.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810141929A CN101656944B (en) | 2008-08-19 | 2008-08-19 | Anchoring data pathway function entity transfer method and apparatus |
| PCT/CN2009/073288 WO2010020163A1 (en) | 2008-08-19 | 2009-08-17 | Method and device for anchor data path function entity handover |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810141929A CN101656944B (en) | 2008-08-19 | 2008-08-19 | Anchoring data pathway function entity transfer method and apparatus |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101656944A true CN101656944A (en) | 2010-02-24 |
| CN101656944B CN101656944B (en) | 2012-10-17 |
Family
ID=41706859
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200810141929A Active CN101656944B (en) | 2008-08-19 | 2008-08-19 | Anchoring data pathway function entity transfer method and apparatus |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101656944B (en) |
| WO (1) | WO2010020163A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102196407A (en) * | 2010-03-18 | 2011-09-21 | 中兴通讯股份有限公司 | Re-positioning method and system for anchored authentication device |
| WO2011119797A1 (en) | 2010-03-25 | 2011-09-29 | Alcatel-Lucent Usa Inc. | Method of relocating access service network functional entities during mobility events in wimax networks |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100450291C (en) * | 2005-07-11 | 2009-01-07 | 华为技术有限公司 | Method of establishing interface link |
| US7561692B2 (en) * | 2006-02-27 | 2009-07-14 | Alvarion Ltd. | Method of authenticating mobile terminal |
| CN101106491A (en) * | 2006-07-11 | 2008-01-16 | 华为技术有限公司 | Migration method for R3 interface in microwave access global intercommunication network ant its system |
-
2008
- 2008-08-19 CN CN200810141929A patent/CN101656944B/en active Active
-
2009
- 2009-08-17 WO PCT/CN2009/073288 patent/WO2010020163A1/en active Application Filing
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102196407A (en) * | 2010-03-18 | 2011-09-21 | 中兴通讯股份有限公司 | Re-positioning method and system for anchored authentication device |
| US9032485B2 (en) | 2010-03-18 | 2015-05-12 | Zte Corporation | Anchor authenticator relocation method and system |
| CN102196407B (en) * | 2010-03-18 | 2015-09-16 | 中兴通讯股份有限公司 | Anchoring authentication device method for relocating and system |
| WO2011119797A1 (en) | 2010-03-25 | 2011-09-29 | Alcatel-Lucent Usa Inc. | Method of relocating access service network functional entities during mobility events in wimax networks |
| CN102845103A (en) * | 2010-03-25 | 2012-12-26 | 阿尔卡特朗讯公司 | Method of relocating access service network functional entities during mobility events in wimax networks |
| JP2015109696A (en) * | 2010-03-25 | 2015-06-11 | アルカテル−ルーセント | Method of relocating access service network functional entities during mobility events in wimax networks |
| JP2017108430A (en) * | 2010-03-25 | 2017-06-15 | アルカテル−ルーセント | Method of relocating access service network function entity during mobility event in wimax network |
| US9769713B2 (en) | 2010-03-25 | 2017-09-19 | Alcatel Lucent | Method of relocating access service network functional entities during mobility events in WiMAX networks |
| CN108112043A (en) * | 2010-03-25 | 2018-06-01 | 阿尔卡特朗讯公司 | The method that access service network functional entity is relocated during mobility event in WiMAX network |
| CN108112043B (en) * | 2010-03-25 | 2021-03-26 | 阿尔卡特朗讯公司 | Method for relocating access service network functional entities during mobility events in a WiMAX network |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2010020163A1 (en) | 2010-02-25 |
| CN101656944B (en) | 2012-10-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7561692B2 (en) | Method of authenticating mobile terminal | |
| US7831253B2 (en) | Method and system for error handling in wireless communication networks | |
| US8219117B2 (en) | Method of paging a mobile terminal | |
| CN1960567B (en) | Communication method for terminal to enter to and exit from idle mode | |
| US7920521B2 (en) | Method and system for foreign agent relocation in wireless network | |
| CN101083839B (en) | Cipher key processing method for switching among different mobile access systems | |
| US20170265108A1 (en) | Security processing method and system in network handover process | |
| CN102196520B (en) | Leave over and advanced access service network internetworking | |
| KR101201414B1 (en) | Method, system and device for location update in networks | |
| EP2019512A1 (en) | A method and system for a ue in spare mode logging out a network | |
| KR101498917B1 (en) | Method of relocating access service network functional entities during mobility events in wimax networks | |
| US7630712B2 (en) | Method for reconnecting a mobile terminal in a wireless network | |
| EP3664568B1 (en) | Communication methods | |
| CN1802024B (en) | Method for carrying out management on information of terminal quitting idle mode | |
| EP2229018B1 (en) | Method and system for authenticating in a communication system | |
| WO2011028442A2 (en) | Pre-registration security support in multi-technology interworking | |
| CN102752725A (en) | Event notifying method, terminal equipment and authentication server | |
| Huang et al. | A fast authentication scheme for WiMAX–WLAN vertical handover | |
| CN101400154A (en) | Method for triggering network withdraw of mobile terminal by network side under WIMAX idle mode | |
| CN101656944B (en) | Anchoring data pathway function entity transfer method and apparatus | |
| CN102123494A (en) | Method, device and system for logging out and revoking a femto base station | |
| CN101516121B (en) | Method for transmitting switching information of base station, system and device thereof | |
| US20050013270A1 (en) | Method and system for de-registering a broadcast/multicast service in a high-rate packet data system | |
| CN101047946B (en) | Network reaccess procedure leaded by network | |
| CN1997213B (en) | Method for security information acquisition of the switched target base station in the wireless communication system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |