[go: up one dir, main page]

CN101656944B - Anchoring data pathway function entity transfer method and apparatus - Google Patents

Anchoring data pathway function entity transfer method and apparatus Download PDF

Info

Publication number
CN101656944B
CN101656944B CN200810141929A CN200810141929A CN101656944B CN 101656944 B CN101656944 B CN 101656944B CN 200810141929 A CN200810141929 A CN 200810141929A CN 200810141929 A CN200810141929 A CN 200810141929A CN 101656944 B CN101656944 B CN 101656944B
Authority
CN
China
Prior art keywords
message
asn
dpf
business network
network gateway
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
CN200810141929A
Other languages
Chinese (zh)
Other versions
CN101656944A (en
Inventor
李波杰
梁文亮
卢磊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN200810141929A priority Critical patent/CN101656944B/en
Priority to PCT/CN2009/073288 priority patent/WO2010020163A1/en
Publication of CN101656944A publication Critical patent/CN101656944A/en
Application granted granted Critical
Publication of CN101656944B publication Critical patent/CN101656944B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

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 the target access service network gateway packs all Anchor_DPF_HO_Req messages of the RRP messages.

Description

A kind of method and apparatus of anchoring data pathway function entity transfer
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 Access Control, 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 (mobile station/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 Service Network 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 and Accounting, authentication) server.
In existing protocol, communicate through the interface from R1 to R6 between the logic entity between MS/SS, ASN, the CSN, like 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 said MS/SS need move.
The inventor finds that 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 said anchoring data pathway function entity relates to is redundancy too, 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, said anchoring data pathway function entity and authentication device entity are positioned at same gateway, and 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;
Said former access business network gateway sends Anchor_DPF_HO_Req message to said target access business network gateway; Be packaged with said rrq message in the said Anchor_DPF_HO_Req message, so that said target access business network gateway sends to home agent HA with said rrq message;
Receive from the registration of said HA after the corresponding RRP message at said target access business network gateway; Said former access business network gateway receives the Anchor_DPF_HO_Rsp message from said target access business network gateway, is packaged with said RRP message in the said Anchor_DPF_HO_Rsp message.
A kind of moving apparatus of anchoring data pathway function entity, said anchoring data pathway function entity and authentication device entity are positioned at same gateway, 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 said 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 register response RRP message from said target access business network gateway.
Through using embodiment of the invention the methods and apparatus disclosed; Proxy mobile internet protocol client on the former access business network gateway is that the terminal generates rrq message according to external agent's Care-of Address of target access business network; By said former access business network gateway said rrq message is encapsulated in and sends to target access business network gateway in the Anchor_DPF_HO_Req message; And receive the Anchor_DPF_HO_Rsp message that is packaged with RRP message from said target access business network gateway, accomplish the migration of A-DPF.When anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, said 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 sketch map.
Embodiment
For making the object of the invention, technical scheme and advantage clearer, the specific embodiment of the invention is done further to describe in 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 the anchoring data pathway function entity before moving (diagram Old A-DPF) place, and the target access network 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 said ASN (b), but the anchoring data pathway function entity of said MS (A-DPF) do not move as yet, still is the said Old A-DPF that is positioned at said ASN (a).
Said method is as shown in Figure 2, and concrete steps are following:
GW (the Gate Way of step 201, said ASN (a); Gateway; Below be called 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 said ASN (b) is that said MS generates RRQ (Registration Request, register requirement) message; Said ASN (a) GW sends Anchor_DPF_HO_Req message to ASN (b) GW, is packaged with said rrq message in the said Anchor_DPF_HO_Req message.
Step 202, said ASN (b) GW transmit said rrq message to HA (Home Agent, home agent), beginning PMIP registration.
Step 203, said HA reply RRP (Registration Response, register response) message to said ASN (b) GW, accomplish the PMIP registration.
Step 204, said ASN (b) GW are encapsulated in the said RRP message that receives in the step 204 and send to said ASN (a) GW in the Anchor_DPF_HO_Rsp message.
Said ASN (a) succeeds in registration according to the said PMIP of said RRP message authentication, and the last DPF of said ASN (b) GW promptly becomes said New A-DPF, and the A-DPF migration is so far accomplished.
Through using embodiment of the invention disclosed method; The last PMIP Client of ASN (a) GW is that said MS generates rrq message according to external agent's Care-of Address of said ASN (b), by said ASN (a) GW said rrq message is encapsulated in and sends to ASN (b) GW in the Anchor_DPF_HO_Req message.Carry out PMIP registration by said ASN (b) GW and HA, and RRP message is encapsulated in sends to said ASN (a) GW in the Anchor_DPF_HO_Rsp message, accomplish the migration of A-DPF.When anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, said 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 said 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 preceding anchoring data pathway function entity of migration (diagram Old A-DPF) and anchoring authentication device (diagram Old A-Authenticator) place, and the target access network 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 said ASN (b); But the anchoring data pathway function entity of said MS (A-DPF) and anchoring authentication device (A-Authenticator) do not move as yet, still for being positioned at said Old A-DPF and the Old A-Authenticator of said ASN (a).
Said method is as shown in Figure 3, and concrete steps are following:
Step 301, if the migration of said anchoring data pathway function entity initiate by said ASN (b); Then carry out this step: GW (the Gate Way of said ASN (b); Gateway; Below be called ASN (b) GW) send Anchor_DPF_HO_Trigger message to the GW of said ASN (a) (below be called ASN (a) GW), said Anchor_DPF_HO_Trigger message is used to indicate said 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 said ASN (b) in the said Anchor_DPF_HO_Trigger message.The last FA-CoA that preserves said ASN (b) of said ASN (b) GW is a prior art, repeats no more here.
Step 302, be positioned at the last PMIP Client of said ASN (a) GW (Proxy Mobile Internet Protocol Client; The proxy mobile internet protocol client) be that said MS generates RRQ (Registration Request, register requirement) message according to said FA-CoA; Said ASN (a) GW sends Anchor_DPF_HO_Req message to said ASN (b) GW, is packaged with said rrq message in the said Anchor_DPF_HO_Req message.
Optional; Also carry the information that authentication device moves required transmission in the said Anchor_DPF_HO_Req message; MS Security History (terminal security historical) information for example; Alternatively; The information that said authentication device moves required transmission can also comprise any several of following message: MS Authorization Context (authorization terminal context), REG Context (registration context), Anchor MM Context (grappling MM Context), Authenticator ID (authentication device sign, said authentication device is a said 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 said anchoring data pathway function entity initiated by said ASN (a), and said ASN (a) obtained said 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 possibly make said ASN (a) before the initial scene that the embodiment of the invention is described, obtain said FA-CoA; What for example before the initial scene that the embodiment of the invention is described, take place counts in the business network handoff procedure; Said ASN (a) possibly obtain said FA-CoA, and concrete acquisition methods repeats no more at this.
If the migration of said anchoring data pathway function entity is initiated by said ASN (a); But said ASN (a) does not also obtain said FA-CoA; Then said ASN (a) sends the preparatory trigger messages of anchoring data pathway function entity transfer to said ASN (b), triggers said ASN (b) execution in step 301.The preparatory trigger messages of said anchoring data pathway function entity transfer can be to be newly-increased R4 message, also can be for carrying the existing R4 message that triggers indication information.
Step 303, said ASN (b) GW transmit said rrq message to HA (Home Agent, home agent), beginning PMIP registration.
Step 304, said HA reply RRP (Registration Response, register response) message to said ASN (b) GW, accomplish the PMIP registration.
Step 305, said ASN (b) GW are encapsulated in the said RRP message that receives in the step 304 and send to said ASN (a) GW in the Anchor_DPF_HO_Rsp message.
Step 306, said ASN (a) succeed in registration according to the said PMIP of said RRP message authentication, and the last DPF of said ASN (b) GW promptly becomes said New A-DPF, and the A-DPF migration is so far accomplished.Said ASN (a) GW sends Context_Rpt message, the address of carrying said New A-DPF in the said Context_Rpt message to the BS that is positioned at said ASN (b) of the current access of said MS.Said New A-DPF promptly is positioned at the last DPF of said ASN (b) GW.Said ASN (a) GW knows that the address of the DPF that said ASN (b) GW is last is a prior art.
Step 307, said BS send Context_Ack message to said ASN (a) GW, confirm the address that it has received said New A-DPF.
Need to prove; In embodiments of the present invention; Step 306 to step 307 also can substitute with following scheme: said ASN (a) succeeds in registration according to the said PMIP of said RRP message authentication, and then said ASN (a) GW sends the RRP acknowledge message to said ASN (b) GW; Said ASN (b) GW sends Context_Rpt message, the address of carrying said New A-DPF in the said Context_Rpt message to the BS that is positioned at said ASN (b) of the current access of said MS; Said BS replys Context_Ack message to said ASN (b) GW and confirms.Said RRP acknowledge message can be newly-increased R4 message, also can be for carrying the existing R4 message of RRP affirmation indication information.
Step 308, said ASN (a) GW send Relocation_Req message to said ASN (b) GW, carry the information that said authentication device moves required transmission in the said Relocation_Req message.
Step 309, said ASN (b) GW reply Relocation_Rsp message to said ASN (a) GW.
What said step 308 to step 309 was described is the negotiation of A-Authenticator migration, and said 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 said push pattern can use the scheme of pull pattern to substitute: said ASN (a) sends said RRP acknowledge message to said ASN (b) GW after succeeding in registration according to the said PMIP of the said RRP message authentication of step 305; After said ASN (b) GW receives said RRP acknowledge message, send Relocation_Notify message, notify said old A-Authenticator to carry out the A-Authenticator migration to said ASN (a) GW at said oldA-Authenticator place; Said ASN (a) GW sends Relocation_Notify_Rsp message to said ASN (b) GW, carries the information that said authentication device moves required transmission in the said Relocation_Notify_Rsp message.
Need to prove; If carried the information that said authentication device moves required transmission in the said Anchor_DPF_HO_Req message in the step 302; The negotiations process of then said A-Authenticator migration can be omitted; Be that step 308 to step 309 can be omitted, its replacement scheme also can be omitted.
Said Old A-Authenticator can get into " 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.Said " 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 here.
Step 310, said MS are through carrying out discrimination weight (Re-Authentication) process between last Authenticator of said BS and said ASN (b) GW and the AAA.Need use said MS Security History information in the said discrimination weight process.
Step 311, said ASN (b) GW send Relocation_Complete_Req message to said ASN (a) GW, carry the authenticating result indication in the said Relocation_Complete_Req message, notify the completion of said discrimination weight process.Optional, can carry MS context request information in the said Relocation_Complete_Req message.
Step 312, said ASN (a) GW send Relocation_Complete_Rsp message to said 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 said MS context request information is asked in the then said Relocation_Complete_Rsp message.If the authenticating result described in the step 311 in the Relocation_Complete_Req message is designated as success, then said oldA-Authenticator stops said " discrimination weight locking " state.
Step 313, if carry said MS contextual information in the Relocation_Complete_Rsp message in the step 312, then carry out this step: said ASN (b) GW sends Relocation_Complete_Ack message to said ASN (a) GW.
If do not carry said MS contextual information in the said Relocation_Complete_Rsp message in the step 312, then said anchoring authentication device migrates to step 312 and promptly accuses completion.If carry said MS contextual information in the said Relocation_Complete_Rsp message in the said step 312; Then said anchoring authentication device migrates to step 313 and promptly accuses completion, and the last Authenticator of said ASN (b) GW becomes said New A-Authenticator.
Through 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 said FA-CoA, by said ASN (a) GW said rrq message is encapsulated in and sends to ASN (b) GW in the Anchor_DPF_HO_Req message.Carry out PMIP registration by said ASN (b) GW and HA, and RRP message is encapsulated in sends to said ASN (a) GW in the Anchor_DPF_HO_Rsp message, accomplish the migration of A-DPF.When anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, said method had compared with prior art been omitted redundant information exchanging process, has saved the communication resource.Further; Said ASN (a) GW can also be in the information interaction of said A-DPF transition process; Trigger the common migration of A-Authenticator, avoided New A-DPF and NewA-Authenticator after the said 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 said MS inserts; The relaying paging controller) and Anchor PC (Anchor Paging Controller; 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 preceding anchoring data pathway function entity of migration (diagram Old A-DPF) and anchoring authentication device (diagram OldA-Authenticator) place, and the target access network 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 said ASN (b); But the anchoring data pathway function entity of said MS (A-DPF) and anchoring authentication device (A-Authenticator) do not move as yet, still for being positioned at said Old A-DPF and the Old A-Authenticator of said ASN (a).
Said method is as shown in Figure 4, and concrete steps are following:
Step 401, MS send RNG-REQ message to the BS of the ASN of current access (b); Carry PC ID (Paging Controller ID in the said RNG-REQ message; The paging controller sign), the Bit#0 in the Ranging Purpose Indication TLV in the said RNG-REQ message (the range finding purpose indication parameter) field puts 1.Said RNG-REQ message is used to initiate the process that said MS withdraws from Idle state.Said PC ID is the ID of the Anchor PC (anchoring paging controller, diagram A-PC) of said MS access, and said MS knows that said PC ID is a prior art.
Step 402, said BS send IM_Exit_State_Change_Req message to said ASN (b) GW at Relay PC (relaying paging controller) place, indicate said MS request to withdraw from Idle state.Anchor PC id field in the said IM_Exit_State_Change_Req message is provided with according to said PCID by said BS.
ASN (b) GW at step 403, said Relay PC place sends IM_Exit_State_Change_Req message to said ASN (a) GW at Anchor PC (anchoring paging controller, diagram A-PC) place, indicates said MS request to withdraw from Idle state.Carry the FA-CoA of said ASN (b) in the said IM_Exit_State_Change_Req message, indicate said ASN (a) to begin to carry out the A-DPF migration.The last FA-CoA that preserves said ASN (b) of said ASN (b) GW is a prior art, repeats no more here.ASN (b) GW at said Relay PC place confirms the address of said ASN (a) GW at said Anchor PC place according to the Anchor PC id field in the message of IM_Exit_State_Change_Req described in the step 402.
Step 404, to be positioned at the last PMIP Client of said ASN (a) GW be that said MS generates rrq message according to said FA-CoA; Said ASN (a) GW sends Anchor_DPF_HO_Req message to said ASN (b) GW, is packaged with said rrq message in the said Anchor_DPF_HO_Req message.
Optional; Can also carry the information that authentication device moves required transmission in the said Anchor_DPF_HO_Req message; MS Security History information for example; Perhaps, alternatively, the information that said authentication device moves required transmission can also comprise any several of following message: MS Authorization Context, REG Context, Anchor MM Context, Authenticator ID, BS ID etc.
Step 405, said ASN (b) GW transmit said rrq message to HA, beginning PMIP registration.
Step 406, said HA reply RRP message to said ASN (b) GW, accomplish the PMIP registration.
Step 407, said ASN (b) GW send Anchor_DPF_HO_Rsp message to said ASN (a) GW, are packaged with the RRP message in the step 406 in the said Anchor_DPF_HO_Rsp message.
Step 408, said ASN (a) succeed in registration according to the said PMIP of said RRP message authentication, and the last DPF of said ASN (b) GW promptly becomes said New A-DPF, and the A-DPF migration is so far accomplished.Said ASN (a) GW sends IM_Exit_State_Change_Rsp message to said ASN (b) GW, and indication A-DPF moves successfully, carries the relevant information of the said MS of said Anchor PC preservation in the said IM_Exit_State_Change Rsp message.The particular content of the relevant information of said MS can be confirmed according to prior art, because it is not the scope of embodiment of the invention definition, so repeat no more.
Optional, can also carry the information that said authentication device moves required transmission in the said IM_Exit_State_Change_Rsp message.
Step 409, said ASN (b) GW send IM_Exit_State_Change_Rsp message, the address of carrying said new A-DPF in the said IM_Exit_State_Change_Rsp message to the BS that is positioned at ASN (b).Said New A-DPF promptly is positioned at the last DPF of said ASN (b) GW.Said ASN (a) GW knows that the address of the DPF that said ASN (b) GW is last is a prior art.
Step 410, said BS send Path_Reg_Req message according to the address of said new A-DPF to said ASN (b) GW at said new A-DPF place, and new data path is set up in request.
Said ASN (b) GW at step 411, said new A-DPF place replys Path_Reg_Rsp message to said BS, confirms the foundation of new data path.
Step 412, said BS send RNG-RSP message to said MS, and said RNG-RSP message indicates said MS to send the network re-entry process of band discrimination weight.
Need to prove; If all do not carry the information that said authentication device moves required transmission in said Anchor_DPF_HO_Req message in the step 404 and the said IM_Exit_State_Change_Rsp message in the step 408; Then after step 408; Before the step 413, with said step 409 to step 412 simultaneously, can also operate as follows:
Said old A-Authenticator and being positioned at carries out the negotiation of A-Authenticator migration between the last Authenticator of ASN (b) GW.Said negotiation has two kinds of pattern: Pull (drawing) patterns or Push (pushing away) pattern.
If the Pull pattern is adopted in said negotiation, then said ASN (b) GW sends Relocation_Notify message to said ASN (a) GW at said old A-Authenticator place, notifies said oldA-Authenticator to carry out the A-Authenticator migration; Said ASN (a) GW sends Relocation_Notify_Rsp message to said ASN (b) GW, carries the information that said authentication device moves required transmission in the said Relocation_Notify_Rsp message.
If the Push pattern is adopted in said negotiation; Said ASN (a) GW at then said old A-Authenticator place sends Relocation_Req message to said ASN (b) GW, carries the information that said authentication device moves required transmission in the said Relocation_Req message; Said ASN (b) GW sends Relocation_Rsp message to said ASN (a) GW.
The negotiations process of said A-Authenticator migration can trigger said Old A-Authenticator and get into " authentication device locking " state.
Need to prove that said old A-Authenticator can also get into " discrimination weight locking " state according to the message in step 403 or step 404 or step 407 or the step 408.Said " 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 here.
Carry out the mutual of L2 network re-entry process between step 413, said MS and the said BS, network side is that said MS carries out discrimination weight (Re-Authentication) through said BS and the last Authenticator of said ASN (b) GW.Said discrimination weight process need is used said MS Security History information.Said L2 network re-entry process and discrimination weight process are prior art, repeat no more here.
Step 414, said BS send Path_Reg_Ack message to ASN (b) GW at said new A-DPF place.
Step 415, said ASN (b) GW send Relocation_Complete_Req message to said ASN (a) GW, carry the authenticating result indication in the said Relocation_Complete_Req message, notify the completion of said discrimination weight process.Optional, can carry MS context request information in the said Relocation_Complete_Req message.
Step 416, said ASN (a) GW send Relocation_Complete_Rsp message to said ASN (b) GW.If carry MS context request information in the Relocation_Complete_Req message in the step 415, carry the MS contextual information that said MS context request information is asked in the then said Relocation_Complete_Rsp message.If the authenticating result described in the step 415 in the Relocation_Complete_Req message is designated as success, then said oldA-Authenticator stops said " discrimination weight locking " state.
Step 417, if carry said MS contextual information in the Relocation_Complete_Rsp message in the step 416, then carry out this step: said ASN (b) GW sends Relocation_Complete_Ack message to said ASN (a) GW.
If do not carry said MS contextual information in the said Relocation_Complete_Rsp message in the step 416, then said anchoring authentication device migrates to step 416 and promptly accuses completion.If carry said MS contextual information in the said Relocation_Complete_Rsp message in the said step 416; Then said anchoring authentication device migrates to step 417 and promptly accuses completion, and the last Authenticator of said ASN (b) GW becomes said New A-Authenticator.
Through 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 said FA-CoA, by said ASN (a) GW said rrq message is encapsulated in and sends to ASN (b) GW in the Anchor_DPF_HO_Req message.Carry out PMIP registration by said ASN (b) GW and HA, and RRP message is encapsulated in sends to said ASN (a) GW in the Anchor_DPF_HO_Rsp message, accomplish the migration of A-DPF.When anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, said method had compared with prior art been omitted redundant information exchanging process, has saved the communication resource.Further; Said ASN (a) GW can also be in the information interaction of said A-DPF transition process; Trigger the common migration of A-Authenticator, avoided New A-DPF and NewA-Authenticator after the said 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 triggers entering Idle state (Idle) with MS self, 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 preceding anchoring data pathway function entity of migration (diagram Old A-DPF) and anchoring authentication device (diagram Old A-Authenticator) place, and the target access network 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 said ASN (b); But the anchoring data pathway function entity of said MS (A-DPF) and anchoring authentication device (A-Authenticator) do not move as yet, still for being positioned at said Old A-DPF and the Old A-Authenticator of said ASN (a).
Said method is as shown in Figure 5, and concrete steps are following:
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 said DREG-REQ message is set to 0x01.Said DREG-REQ message is used to initiate the process that said MS gets into Idle state.
Step 502, said BS send IM_Entry_State_Change_Req message to said ASN (b) GW at PC (anchoring paging controller) place, indicate said MS request to get into Idle state.
Step 503, said PC select self as Anchor PC (anchoring paging controller, diagram A-PC), and ASN (b) GW at said A-PC place sends Anchor_DPF_HO_Trigger message to said ASN (a) GW.Carry the FA-CoA of said ASN (b) in the said Anchor_DPF_HO_Trigger message.The last FA-CoA that preserves said ASN (b) of said ASN (b) GW is a prior art, repeats no more here.
Step 504, to be positioned at the last PMIP Client of said ASN (a) GW be that said MS generates rrq message according to said FA-CoA; Said ASN (a) GW sends Anchor_DPF_HO_Req message to said ASN (b) GW, is packaged with said rrq message in the said Anchor_DPF_HO_Req message.
Step 505, said ASN (b) GW transmit said rrq message to HA, beginning PMIP registration.
Step 506, said HA reply RRP message to said ASN (b) GW, accomplish the PMIP registration.
Step 507, said ASN (b) GW send Anchor_DPF_HO_Rsp message to said ASN (a) GW, are packaged with the RRP message in the step 306 in the said Anchor_DPF_HO_Rsp message.
Step 508, said ASN (a) succeed in registration according to the said PMIP of said RRP message authentication, and the last DPF of said ASN (b) GW promptly becomes said New A-DPF, and the A-DPF migration is so far accomplished.Said ASN (a) GW sends Relocation_Req message to said ASN (b) GW, carries the information that authentication device moves required transmission in the said Relocation_Req message.Said Relocation_Req message is used to begin the A-Authenticator transition process, indicates said A-DPF migration to accomplish simultaneously.
Step 509, said ASN (b) GW send Relocation_Rsp message to said ASN (a) GW.
Need to prove; Step 508 to step 509 can be substituted by following scheme: said ASN (a) GW succeeds in registration according to the said PMIP of said RRP message authentication; And to ASN (b) GW transmission RRP acknowledge message; Said RRP acknowledge message can be newly-increased R4 message, also can be for increasing the existing R4 message that RRP confirms indication; After said ASN (b) GW receives said RRP acknowledge message, send Relocation_Notify message to said ASN (a) GW and begin the A-Authenticator transition process; Said ASN (a) GW returns Relocation_Notify_Rsp message to said ASN (b) GW and responds, and carries the information that authentication device moves required transmission in the said Relocation_Notify_Rsp message.
Said old A-Authenticator can get into " discrimination weight locking " state according to the arbitrary steps (except step 505 to the step 506) or the message in its alternative steps of step 503 to step 509.Said " 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 here.
Step 510, said ASN (b) GW send IM_Entry_State_Change_Rsp message to the BS of said ASN (b); The address of carrying said new A-DPF in the said IM_Entry_State_Change_Rsp message; Optional; Also carry indication in the said IM_Entry_State_Change_Rsp message, be used to indicate said BS after said MS carries out discrimination weight, to send DREG-CMD message to said MS.
Step 511, said BS send IM_Entry_State_Change_Ack message to said ASN (b) GW.
Step 512, MS are through carrying out discrimination weight (Re-Authentication) process between last Authenticator of said BS and said ASN (b) GW and the AAA.
ASN (b) GW at step 513, said new A-Authenticator place sends Relocation_Complete_Req message to ASN (a) GW at said oldA-Authenticator place; Carry the authenticating result indication in the said Relocation_Complete_Req message, notify the completion of said discrimination weight process.Optional, can carry MS context request information in the said Relocation_Complete_Req message.
Step 514, said ASN (a) GW send Relocation_Complete_Rsp message to said ASN (b) GW.If carry MS context request information in the Relocation_Complete_Req message in the step 513, carry the MS contextual information that said MS context request information is asked in the then said Relocation_Complete_Rsp message.If the authenticating result described in the step 513 in the Relocation_Complete_Req message is designated as success, then said oldA-Authenticator stops said " discrimination weight locking " state.
Step 515, if carry said MS contextual information in the Relocation_Complete_Rsp message in the step 514, then carry out this step: said ASN (b) GW sends Relocation_Complete_Ack message to said ASN (a) GW.
If do not carry said MS contextual information in the said Relocation_Complete_Rsp message in the step 514, then said anchoring authentication device migrates to step 514 and promptly accuses completion.If carry said MS contextual information in the said Relocation_Complete_Rsp message in the said step 514; Then said anchoring authentication device migrates to step 515 and promptly accuses completion, and the last Authenticator of said ASN (b) GW becomes said New A-Authenticator.
Step 516, said BS send DREG-CMD message to said MS, and instruct MS gets into Idle state, and start management resource maintenance timer.
Step 517, said BS send Path_DeReg_Req message to said ASN (b) GW at said new A-DPF place after said management resource keeps timer expiry, data path is nullified in request.
Step 518, said ASN (b) GW reply Path_DeReg_Rsp message to said BS, confirm the cancellation of data path.
Step 519, said BS send Path_DeReg_Ack message to said ASN (b) GW at said new A-DPF place, accomplish 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 said said BS information to said MS transmission DREG-CMD message after said MS carries out discrimination weight that is used to indicate at this moment in the said 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 can not have sequential relationship with step 513 to step 515 yet, only need all occur in step 512 and get final product afterwards.
Through 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 said FA-CoA, by said ASN (a) GW said rrq message is encapsulated in and sends to ASN (b) GW in the Anchor_DPF_HO_Req message.Carry out PMIP registration by said ASN (b) GW and HA, and RRP message is encapsulated in sends to said ASN (a) GW in the Anchor_DPF_HO_Rsp message, accomplish the migration of A-DPF.When anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, said method had compared with prior art been omitted redundant information exchanging process, has saved the communication resource.Further; Said ASN (a) GW can also be in the information interaction of said A-DPF transition process; Trigger the common migration of A-Authenticator, avoided New A-DPF and NewA-Authenticator after the said 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 triggers MS entering Idle state (Idle) with network side, 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 preceding anchoring data pathway function entity of migration (diagram Old A-DPF) and anchoring authentication device (diagram Old A-Authenticator) place, and the target access network 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 said ASN (b); But the anchoring data pathway function entity of said MS (A-DPF) and anchoring authentication device (A-Authenticator) do not move as yet, still for being positioned at said Old A-DPF and the Old A-Authenticator of said ASN (a).
Said method is as shown in Figure 6, and concrete steps are following:
The BS of the ASN of step 601, the current access of MS (b) sends IM_Entry_State_Change_Req message to said ASN (b) GW at PC (anchoring paging controller) place, indicates said MS to get into Idle state.
Step 602, said PC select self as Anchor PC (anchoring paging controller, diagram A-PC), and ASN (b) GW at said A-PC place sends Anchor_DPF_HO_Trigger message to said ASN (a) GW.Carry the FA-CoA of said ASN (b) in the said Anchor_DPF_HO_Trigger message.The last FA-CoA that preserves said ASN (b) of said ASN (b) GW is a prior art, repeats no more here.
Step 603, to be positioned at the last PMIP Client of said ASN (a) GW be that said MS generates rrq message according to said FA-CoA; Said ASN (a) GW sends Anchor_DPF_HO_Req message to said ASN (b) GW, is packaged with said rrq message in the said Anchor_DPF_HO_Req message.
Step 604, said ASN (b) GW transmit said rrq message to HA, beginning PMIP registration.
Step 605, said HA reply RRP message to said ASN (b) GW, accomplish the PMIP registration.
Step 606, said ASN (b) GW send Anchor_DPF_HO_Rsp message to said ASN (a) GW, are packaged with the RRP message in the step 306 in the said Anchor_DPF_HO_Rsp message.
Step 607, said ASN (a) succeed in registration according to the said PMIP of said RRP message authentication, and the last DPF of said ASN (b) GW promptly becomes said New A-DPF, and the A-DPF migration is so far accomplished.Said ASN (a) GW sends Relocation_Req message to said ASN (b) GW, carries the information that authentication device moves required transmission in the said Relocation_Req message.Said Relocation_Req message is used to begin the A-Authenticator transition process, indicates said A-DPF migration to accomplish simultaneously.
Step 608, said ASN (b) GW send Relocation_Rsp message to said ASN (a) GW.
Need to prove; Step 607 to step 608 can be substituted by following scheme: said ASN (a) GW succeeds in registration according to the said PMIP of said RRP message authentication; And to ASN (b) GW transmission RRP acknowledge message; Said RRP acknowledge message can be newly-increased R4 message, also can be for increasing the existing R4 message that RRP confirms indication; After said ASN (b) GW receives said RRP acknowledge message, send Relocation_Notify message to said ASN (a) GW and begin the A-Authenticator transition process; Said ASN (a) GW returns Relocation_Notify_Rsp message to said ASN (b) GW and responds, and carries the information that authentication device moves required transmission in the said Relocation_Notify_Rsp message.
Said old A-Authenticator can get into " discrimination weight locking " state according to the arbitrary steps (except step 604 to the step 605) or the message in its alternative steps of step 602 to step 608.Said " 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 here.
Step 609, said ASN (b) GW send IM_Entry_State_Change_Rsp message to the BS of said ASN (b); The address of carrying said new A-DPF in the said IM_Entry_State_Change_Rsp message; Optional; Also carry indication in the said IM_Entry_State_Change_Rsp message, be used to indicate said BS after said MS carries out discrimination weight, to send DREG-CMD message to said MS.
Step 610, MS are through carrying out discrimination weight (Re-Authentication) process between last Authenticator of said BS and said ASN (b) GW and the AAA.
ASN (b) GW at step 611, said new A-Authenticator place sends Relocation_Complete_Req message to ASN (a) GW at said old A-Authenticator place; Carry the authenticating result indication in the said Relocation_Complete_Req message, notify the completion of said discrimination weight process.Optional, can carry MS context request information in the said Relocation_Complete_Req message.
Step 612, said ASN (a) GW send Relocation_Complete_Rsp message to said 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 said MS context request information is asked in the then said Relocation_Complete_Rsp message.If the authenticating result described in the step 611 in the Relocation_Complete_Req message is designated as success, then said oldA-Authenticator stops said " discrimination weight locking " state.
Step 613, if carry said MS contextual information in the Relocation_Complete_Rsp message in the step 612, then carry out this step: said ASN (b) GW sends Relocation_Complete_Ack message to said ASN (a) GW.
If do not carry said MS contextual information in the said Relocation_Complete_Rsp message in the step 612, then said anchoring authentication device migrates to step 612 and promptly accuses completion.If carry said MS contextual information in the said Relocation_Complete_Rsp message in the said step 612; Then said anchoring authentication device migrates to step 613 and promptly accuses completion, and the last Authenticator of said ASN (b) GW becomes said New A-Authenticator.
Step 614, said BS send DREG-CMD message to said MS, and instruct MS gets into Idle state, and start management resource maintenance timer.
Step 615, said MS send DREG-REQ message to said BS, and get into Idle state.
Step 616, said BS send IM_Entry_State_Change_Ack message to said ASN (b) GW.
Step 617, said BS send Path_DeReg_Req message to said ASN (b) GW at said new A-DPF place after said management resource keeps timer expiry, data path is nullified in request.
Step 618, said ASN (b) GW reply Path_DeReg_Rsp message to said BS, confirm the cancellation of data path.
Step 619, said BS send Path_DeReg_Ack message to said ASN (b) GW at said new A-DPF place, accomplish 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 said IM_Entry_State_Change_Rsp message in the step 609 this moment and saidly be used to indicate said BS information to said MS transmission DREG-CMD message said MS carries out discrimination weight after, and the relative position of other steps is constant.
Step 614 to step 619 can not have sequential relationship with step 611 to step 613 yet, only need all occur in step 610 and get final product later.
Through 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 said FA-CoA, by said ASN (a) GW said rrq message is encapsulated in and sends to ASN (b) GW in the Anchor_DPF_HO_Req message.Carry out PMIP registration by said ASN (b) GW and HA, and RRP message is encapsulated in sends to said ASN (a) GW in the Anchor_DPF_HO_Rsp message, accomplish the migration of A-DPF.When anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, said method had compared with prior art been omitted redundant information exchanging process, has saved the communication resource.Further; Said ASN (a) GW can also be in the information interaction of said A-DPF transition process; Trigger the common migration of A-Authenticator, avoided New A-DPF and NewA-Authenticator after the said 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.
Said device is as shown in Figure 7, 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 said 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 register response RRP message from said target access business network gateway.
Said first sending module sends be packaged with said rrq message Anchor_DPF_HO_Req message and arrive said target access business network gateway after, said target access business network gateway sends to home agent HA with said rrq message.Said first receiver module receives before the Anchor_DPF_HO_Rsp message that is packaged with the corresponding RRP message of registration from said target access business network gateway, and said target access business network gateway receives the said RRP message from said HA.
Optional, said 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 said target access business network in said Anchor_DPF_HO_Trigger message or the IM_Exit_State_Change_Req message from said target access business network gateway;
The said FA-CoA that said proxy mobile internet protocol client modules receives according to said second receiver module of target is that terminal MS generates the register requirement rrq message.
Optional, said device also comprises:
Second sending module: the base station BS that is used for inserting to said 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 said Context_Rpt or IM_Entry_State_Change_Rsp or the IM_Exit_State_Change_Rsp message.
Optional, said 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 said IM_Exit_State_Change_Rsp message to said target access business network gateway.
Optional, said device also comprises:
The 3rd receiver module: be used to receive Relocation_Complete_Req message, carry the authenticating result indication in the said Relocation_Complete_Req message from said target access business network gateway.
Through using the disclosed device of present embodiment, former accessing business network gate ASN (a) GW can be that MS generates rrq message according to said FA-CoA, by said ASN (a) GW said rrq message is encapsulated in and sends to ASN (b) GW in the Anchor_DPF_HO_Req message.Carry out PMIP registration by said ASN (b) GW and HA, and RRP message is encapsulated in sends to said ASN (a) GW in the Anchor_DPF_HO_Rsp message, accomplish the migration of A-DPF.When anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, said method had compared with prior art been omitted redundant information exchanging process, has saved the communication resource.Further; Said ASN (a) GW can also be in the information interaction of said A-DPF transition process; Trigger the common migration of A-Authenticator, avoided NewA-DPF and New A-Authenticator after the said migration to be positioned at different entities, further saved the communication resource.
Through 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 said FA-CoA, by said ASN (a) GW said rrq message is encapsulated in and sends to ASN (b) GW in the Anchor_DPF_HO_Req message.Carry out PMIP registration by said ASN (b) GW and HA, and RRP message is encapsulated in sends to said ASN (a) GW in the Anchor_DPF_HO_Rsp message, accomplish the migration of A-DPF.When anchoring data pathway function entity and authentication device entity were positioned at same gateway entity, said method had compared with prior art been omitted redundant information exchanging process, has saved the communication resource.Further; Said ASN (a) GW can also be in the information interaction of said A-DPF transition process; Trigger the common migration of A-Authenticator, avoided New A-DPF and NewA-Authenticator after the said migration to be positioned at different entities, further saved the communication resource.
Description through above execution mode; 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 be come out with the embodied of software product, and this computer software product is stored in the storage medium that can read, like the floppy disk of 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 is only in order to explaining technical scheme of the present invention, but not to its restriction; Although with reference to previous embodiment the present invention has been carried out detailed explanation, 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 are revised or replacement, do not make the spirit and the scope of the essence disengaging various embodiments of the present invention technical scheme of relevant art scheme.

Claims (13)

1. the method for an anchoring data pathway function entity transfer, said anchoring data pathway function entity and authentication device entity are positioned at same gateway, it is characterized in that, and 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;
Said former access business network gateway sends Anchor_DPF_HO_Req message to said target access business network gateway; Be packaged with said rrq message in the said Anchor_DPF_HO_Req message, so that said target access business network gateway sends to home agent HA with said rrq message;
Receive from the registration of said HA after the corresponding RRP message at said target access business network gateway; Said former access business network gateway receives the Anchor_DPF_HO_Rsp message from said target access business network gateway; Be packaged with said RRP message in the said Anchor_DPF_HO_Rsp message, also carry the information that authentication device moves required transmission in the said Anchor_DPF_HO_Req message.
2. the method for claim 1 is characterized in that, this takes a step forward and comprises step:
Said former access business network gateway receives the Anchor_DPF_HO_Trigger message from said target access business network gateway, carries said FA-CoA in the said Anchor_DPF_HO_Trigger message.
3. method as claimed in claim 2 is characterized in that, after this further comprises step:
Said former access business network gateway sends Context_Rpt message or IM_Entry_State_Change_Rsp message to the base station BS that said MS inserts, and carries the address of the anchoring data pathway function entity after the migration in said Context_Rpt message or the IM_Entry_State_Change_Rsp message;
Anchoring data pathway function entity after the said migration is the data pathway function entity that is positioned on the said target access business network gateway.
4. the method for claim 1 is characterized in that, this takes a step forward and comprises step:
Said former access business network gateway receives the IM_Exit_State_Change_Req message from said target access business network gateway, carries said FA-CoA in the said IM_Exit_State_Change_Req message.
5. method as claimed in claim 4 is characterized in that, after this further comprises step:
Said former access business network gateway sends IM_Exit_State_Change_Rsp message to the base station BS that said MS inserts, and carries the address of the anchoring data pathway function entity after the migration in the said IM_Exit_State_Change_Rsp message;
Anchoring data pathway function entity after the said migration is the data pathway function entity that is positioned on the said target access business network gateway.
6. the method for claim 1 is characterized in that, further comprises step:
Said former access business network gateway sends IM_Exit_State_Change_Rsp message to said target access business network gateway, carries the information that said authentication device moves required transmission in the said IM_Exit_State_Change_Rsp message.
7. method as claimed in claim 6 is characterized in that, the information that said authentication device moves required transmission comprises the historical MS Security of terminal security History information.
8. method as claimed in claim 7 is characterized in that, further comprises step before the said discrimination weight process:
The preceding anchoring authentication device of migration that is positioned on the said former access business network gateway gets into " discrimination weight locking " state.
9. method as claimed in claim 8 is characterized in that, further comprises step:
Said former access business network gateway receives the Relocation_Complete_Req message from said target access business network gateway, carries the authenticating result indication in the said Relocation_Complete_Req message;
If said authenticating result is designated as success, the anchoring authentication device before the then said migration stops said " discrimination weight locking " state.
10. the moving apparatus of an anchoring data pathway function entity, said anchoring data pathway function entity and authentication device entity are positioned at same gateway, it 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 said 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 register response RRP message from said target access business network gateway;
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 said IM_Exit_State_Change_Rsp message to said target access business network gateway.
11. device as claimed in claim 10 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 said target access business network in said Anchor_DPF_HO_Trigger message or the IM_Exit_State_Change_Req message from said target access business network gateway;
The said FA-CoA that said proxy mobile internet protocol client modules receives according to said second receiver module is that terminal MS generates the register requirement rrq message.
12. device as claimed in claim 10 is characterized in that, also comprises:
Second sending module: the base station BS that is used for inserting to said 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 said Context_Rpt or IM_Entry_State_Change_Rsp or the IM_Exit_State_Change_Rsp message.
13. device as claimed in claim 10 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 said Relocation_Complete_Req message from said target access business network gateway.
CN200810141929A 2008-08-19 2008-08-19 Anchoring data pathway function entity transfer method and apparatus Expired - Fee Related CN101656944B (en)

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 CN101656944A (en) 2010-02-24
CN101656944B true CN101656944B (en) 2012-10-17

Family

ID=41706859

Family Applications (1)

Application Number Title Priority Date Filing Date
CN200810141929A Expired - Fee Related 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)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102196407B (en) * 2010-03-18 2015-09-16 中兴通讯股份有限公司 Anchoring authentication device method for relocating and system
US9769713B2 (en) 2010-03-25 2017-09-19 Alcatel Lucent Method of relocating access service network functional entities during mobility events in WiMAX networks

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1794870A (en) * 2005-07-11 2006-06-28 华为技术有限公司 Method of establishing interface link
US20070201697A1 (en) * 2006-02-27 2007-08-30 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

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1794870A (en) * 2005-07-11 2006-06-28 华为技术有限公司 Method of establishing interface link
US20070201697A1 (en) * 2006-02-27 2007-08-30 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

Also Published As

Publication number Publication date
CN101656944A (en) 2010-02-24
WO2010020163A1 (en) 2010-02-25

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
CN101083839B (en) Cipher key processing method for switching among different mobile access systems
CN102196520B (en) Leave over and advanced access service network internetworking
KR101201414B1 (en) Method, system and device for location update in networks
US20170265108A1 (en) Security processing method and system in network handover process
KR101498917B1 (en) Method of relocating access service network functional entities during mobility events in wimax networks
JP5226202B2 (en) Relocation control device in wireless communication network
US20110063997A1 (en) Interworking between wimax and 3gpp networks
EP3664568B1 (en) Communication methods
CN101785343B (en) Method, system and device for fast transitioning resource negotiation
CN1960567B (en) Communication method for terminal to enter to and exit from idle mode
EP2229018B1 (en) Method and system for authenticating in a communication system
CN101663877A (en) System for fa relocation with context transfer in wireless networks
CN101400154B (en) Method for triggering network withdraw of mobile terminal by network side under WIMAX idle mode
Huang et al. A fast authentication scheme for WiMAX–WLAN vertical handover
CN101730171B (en) Switching control method and switching control system
CN101656944B (en) Anchoring data pathway function entity transfer method and apparatus
CN1802024B (en) Method for carrying out management on information of terminal quitting idle mode
CN101516121B (en) Method for transmitting switching information of base station, system and device thereof
CN108924831A (en) The verification method and device of terminal
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
CN101325804B (en) Method, device and system for acquiring cryptographic key
CN101577912B (en) Method and device for keeping consistent user states in all network elements of ASN

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20121017