CN1996911A - A method for controlling the R3 re-anchoring in the multi-host WiMAX system - Google Patents
A method for controlling the R3 re-anchoring in the multi-host WiMAX system Download PDFInfo
- Publication number
- CN1996911A CN1996911A CN 200610000501 CN200610000501A CN1996911A CN 1996911 A CN1996911 A CN 1996911A CN 200610000501 CN200610000501 CN 200610000501 CN 200610000501 A CN200610000501 A CN 200610000501A CN 1996911 A CN1996911 A CN 1996911A
- Authority
- CN
- China
- Prior art keywords
- host
- target
- function
- reorientation
- data path
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Abstract
This invention relates to Imax and to one method to re-anchor in the system, which comprises the following steps: in re-quire information in R3 portable with needed re-positioning G-MS and or its connected host machine label information to initiate G-MS and or host re-positioning and to determine re-positioning G-MS or host buffer data send closure before breaking off R4 data channel to ensure the data completeness.
Description
Technical field
The present invention relates to WiMAX (World wide Interoperability for Microwave Access) technology, particularly the method for control R3 re-anchoring in many main frames (Multiple Hosts) WiMAX system.
Background technology
Existing common WiMAX network architecture system as shown in Figure 2, comprise MS (Mobile Station, travelling carriage), ASN (Access Service Network, access service network) and CSN (ConnectivityService Network, connectivity serving network), wherein:
MS is a mobile subscriber terminal equipment, and the user uses this devices accessing WiMAX network;
ASN comprises BS (Base Station, base station) and ASN-GW (Access Service Network GateWay, access service network gateway) etc., is used to the WiMAX terminal equipment that the network function set of wireless access service is provided.As: based on as described in BS functions such as the compression of being connected of BS and MS, RRM, measurement and power control, air interface data and encryption are provided; Based on described ASN-GW, for MS authentication function provides agency (Proxy) function, supports the network of NSP to find and select, provide for MS the functions such as Relay function (as the relaying of IP address assignment message), RRM of L3 information.For finishing above-mentioned functions, BS and ASN-GW comprise following functional entity (FunctionalEntity): physics/media interviews controlled function entity (PHY/MAC Function), data channel controlled function entity (DP Function is abbreviated as DP Function), switching control function entity (HO Function) and external agent FA (Foreign Agent) functional entity etc.
CSN is used to the WiMAX terminal that IP is provided Connection Service, as: be MS distributing IP address, provide the Internet to insert, AAA Proxy or service are provided, authorization control based on the user is provided, ASN is provided the data path to CSN, be equivalent to home agent (the Home Agent in the mobile IP technology, HA), WiMAX user's charging and the clearing between the operator are provided, data path under the roaming condition between the CSN, switching between the different ASN, and various WiMAX service is (as location-based business, multi-medium multi-packet broadcasting and broadcasting service, the IP Multimedia System business) etc.
Current WiMAX multi-host communication system configuration as shown in Figure 2, travelling carriage (G-MS) and it with main frame (Host) connect by WLAN, G-MS connects the base station by wave point, interface between the involved difference in functionality entity of the mobility of terminal comprises: the interface between the base station is the R8 interface, interface between base station and the access service network gateway ASN GW (Access Service Network Gateway) is the R6 interface, interface between the ASN GW is an Interface R4, and the interface between ASN GW and the connectivity serving network CSN (Connectivity Service Network) is an Interface R3.
G-MS and it with the switching of Host between two base stations relate to below several situations:
1, R8 switches: travelling carriage switches between two base stations that are connected on the same ASN GW.After the finishing switching, serving BS still is point (Anchor) base station of casting anchor, and the data path before switching does not change, and has increased the data path of a R8 between two base stations;
2, R6 switches: travelling carriage switches between two base stations that are connected on the same ASN GW.After the finishing switching, target BS becomes point (Anchor) base station of casting anchor, and serving BS before switching and the disconnection of the R6 data path between the ASN GW, sets up the R6 data path between new target BS and the ASN GW;
3, R4 switches: travelling carriage switches between two base stations that are connected on the different ASN GW.After the finishing switching, service ASN GW still is point (Anchor) the ASN GW that casts anchor, and the data path before switching does not change, and has increased the data path of a R4 between two ASN GW;
4, R3 switches: travelling carriage switches between two base stations that are connected on the different ASN GW.After the finishing switching, target ASN GW becomes point (Anchor) the ASN GW that casts anchor, and service ASN GW before switching and the R3 data path between HA (G-MS) and the HA (Host) disconnect, and set up the R3 data path between new target ASN GW and HA (G-MS) and the HA (Host);
In current WiMAX communication system, after G-MS and/or Host have finished R4 and have switched, when perhaps network carries out resource optimization, network may be Target ASN GW reorientation (Relocate) Anchor ASN GW according to some conditional decisions, disconnect R4 data path between Serving ASN GW and Target (Anchor) the ASN GW and the R3 data path between Serving ASN GW and HA (G-MS) and the HA (Host) simultaneously, and set up R3 data path between Target ASN GW and HA (G-MS) and the HA (Host), this process is called as R3 re-anchoring (R3 Re-anchor) process, in this process, need to extract Care-of Address (the Care ofAddress of this Target/Anchor ASN-GW, CoA, this address can be the FA address of Anchor ASN-GW, also can be the address of a G-MS or Host) and register to HA, HA need to prove that according to the data flow that the Care-of Address CoA after upgrading sends G-MS or Host HA (G-MS) and HA (Host) may be arranged in same NSP network.Data path before the R3 Re-anchor is shown in the dotted line among Fig. 3, and the data path after the R3 Re-anchor is shown in the solid line among Fig. 4.
In current common WiMAX system, no matter be based on PMIP (the ProxyMobile Internet Protocol under the IPv4 agreement, act on behalf of mobile network protocol) and CMIP (Client Mobile InternetProtocol, the client mobile network protocol) agreement, also be based on the CMIP agreement under the IPv6 agreement, the triggering of R3 Re-anchor process all comprises two kinds of situations: the netinit R3 Re-anchor process that one triggers for the MS mobility event; It two is the netinit R3Re-anchor process of network resource optimization Event triggered.
Wherein, the netinit Re-anchor flow process that triggers based on the MS mobility event of CMIPv4 agreement in the common WiMAX system as shown in Figure 5, need to prove, Serving DP Function and Serving FA may be positioned on the Serving ASN-GW1 simultaneously, also may be arranged in different network entities, equally, Target DP Function and Target FA may be positioned on the Target ASN-GW2 simultaneously, also may be arranged in different network entities, data path between Serving DP Function and the Target DP Function may be based upon in the ASN network (Inter-ASN), also may be based upon (Intra-ASN) between the different ASN.R3 Re-anchor comprises the steps:
1-2, old ASN and the contextual reciprocal process of MIP;
Wherein, arrow 1 is represented the intra-ASN data path; Arrow 2 is represented the MIP context of FA to HA, and this context is just set up before switching;
R3 switches by ASN Functional Entity initialization, and the Inter-ASN mobility triggers and comprises step 3a and 3b:
The ASN functional entity (ASN Functional Entity) of 3a, execution network resource management sends R3 re-positioning request (R3 Relocate Request) to TargetFA;
3b, Target FA success received R3 Relocate Request after, will return to a R3 Relocate of ASNFunctional Entity Confirm;
4 and, Target FA will send mobile broadcast (Mobility Advertisement) and give MS;
The last Care-of Address that will produce new MS binding of 5-6, MIP updating context: HA;
7, behind the R3 handover success target FA with the corresponding R3 relocation response of ASN Functional Entity (R3 Relocate Response) that sends to; Switching under the unsuccessful situation, ASN FunctionalEntity also is apprised of, to recover old state.
8-10, set up new Intra-ASN data path: be accompanied by the carrying out of R3 Re-anchor, new intra-ASN data path will be established.
Intra-ASN-GW is after having received R3 Relocate Response, and old intra-ASN Data Path resource will be released/upgrade, and new R3 data path mobility context is with obtained.
Inform R3 reorientation success by R3 Relocate Response message to ASN Functional Entity.Under unsuccessful switch instances, ASN Functional Entity also is apprised of, and so just can return to old state.Successful R3 Relocate Response notice ASN Functional EntityR4 forward data path can be deleted.
R3 Re-anchor process under other agreements is basic identical, in order to carry out R3 Re-anchor process, need an ASN functional entity (ASN Functional Entity) of carrying out network resource management to send the process that R3 Relocate Request primitive comes initialization R3 R3-anchor.Also need R3 RelocateConfirm to confirm that R3 Relocate Request is by correct reception.Also need R3 RelocateResponse to represent whether R3 Re-anchor process is finished, if finish, so original data path just can be released at last.
R3 Relocate Request, the content that comprises respectively among R3 Relocate Confirm and the R3 Relocate Response is as shown in table 1:
Table 1.
| Primitive | Message content |
| R3 Relocate Request | MS ID，Target FA，Transaction ID |
| R3 Relocate Confirm | MS ID，Transaction ID |
| R3 Relocate Response | MS ID，Transaction ID |
Wherein, the content of MS ID, Target FA and Transaction ID is as follows respectively:
MS ID: define the MS that this R3 reorientation is asked, this MS ID is based on the NAI of MS, and in PMIP, MS refers in particular to the some clients in the PMIP client;
Target FA: cast anchor a little for MS has defined new R3, the address of Target FA meets the Care-of Address CoA of FA in the MIP topological structure;
Transaction ID: a number that produces at random, this number can carry out relevant with response to request.Transaction ID and MS ID together, unique definition a request.
In the WiMAX of many main frames system, the current process that does not also have technology can realize R3 Re-anchor.In the WiMAX of many main frames system, there is not technology to be implemented in the method that guarantees data integrity in the R3 Re-anchor process yet.Same, if yet do not have technology to relate in a multi-host WiMAX system G-MS now and be connected in that only some need carry out Re-anchor in the main frame above it, and another part keeps using the situation of original Care-of Address.And in the prior art, because R3 RelocateRequest, can only indicate the MS ID that will carry out R3Re-anchor among R3 Relocate Confirm and the R3 Relocate Response, so when a plurality of Host also needed to carry out R3 Re-anchor, the content in these primitive just can not have been supported.
Summary of the invention
The invention provides a kind of in multi-host WiMAX system the method for control R3 re-anchoring, solving in the prior art, when all or part of needs carry out R3 Re-anchor in G-MS and the main frame that is connected, how to carry out the problem of R3 re-anchoring;
Further, the method for the invention has solved when all or part of needs carry out R3 Re-anchor in G-MS and the main frame that is connected, the problem how to guarantee data integrity.
According to concrete IPv4 agreement and the IPv6 agreement of using in the multi-host WiMAX system, the method for control R3 re-anchoring of the present invention is described respectively below.
The method of control R3 re-anchoring comprises the steps: in a kind of multi-host WiMAX system under the IPv4 agreement
The access service network functional entity ASN Functional Entity of A, execution network resource management sends R3 data path re-positioning request, wherein carry the G-MS that need carry out reorientation and/or the address information of main frame Host information and target foreign agent Target FA, described Host connects G-MS;
B, Target FA will be transmitted to the home agent HA of G-MS and/or main frame Host according to the Care-of Address CoA register requirement that re-positioning request triggers respectively, and request HA upgrades the Care-of Address CoA of described G-MS and/or Host;
C, HA are respectively the R3 data path between newly-built HA of G-MS and/or Host and the Target FA, and G-MS and/or Host are reoriented on the Target FA after confirming that respectively the Care-of Address CoA of the G-MS that asks and/or Host succeeds in registration.
Also comprise the steps: after the described step C
The HA of D1, G-MS and/or Host correspondence extracts the sequence number with the packet of first described G-MS that sends by newly-built R3 data path and/or Host respectively, and respectively the sequence number that extracts is sent to Target DP Function;
E1, Target DP Function are received packet before the sequence number of a G-MS who carries out reorientation and/or Host correspondence by the R4 data path respectively from grappling data channel controlled function entity A nchor DP Function after, trigger and disconnect corresponding described R4 data path.
Also comprise the steps: after the described step C
D2, Target DP Function by newly-built R3 data path receive carry out first packet of the G-MS of reorientation and/or Host from each of corresponding HA after, extract the sequence number of first packet of this G-MS and/or Host respectively;
E2, Target DP Function are received packet before the sequence number of a G-MS who carries out reorientation and/or Host correspondence by the R4 data path respectively from grappling data channel controlled function entity A nchor DP Function after, trigger and disconnect corresponding described R4 data path.
Carry out the G-MS and/or the Host of reorientation for each, specifically comprise the steps: among described step e 1 or the E2
This sequence number that carries out last packet of the G-MS of reorientation and/or Host that Target DP Function determines to receive from Anchor DP Function subtracts 1 for corresponding described sequence number;
The described sequence number that Target DP Function receives this G-MS and/or Host correspondence by described R4 data path from Anchor DP Function triggers the R4 data path that disconnects this G-MS and/or Host after subtracting 1 packet.
Perhaps, carry out the G-MS and/or the Host of reorientation, specifically comprise the steps: among described step e 1 or the E2 for each
Target DP Function sends to Anchor DP Function with this described sequence number that carries out the G-MS of reorientation and/or Host correspondence and carries out the transfer of data inquiry;
Anchor DP Function confirms to send this G-MS and/or after the described sequence number of Host correspondence subtracts 1 packet, to return an inquiry response to Target DPFunction to Target DP Function by described R4 data path;
After Target DP Function receives inquiry response, trigger the R4 data path that disconnects this G-MS and/or Host.
Described step D specifically comprises the steps:
The registration reply message that each HA that carries out the G-MS of reorientation and/or Host correspondence will carry corresponding described sequence number respectively sends to target foreign agent Target FA;
The described sequence number that Target FA carries out each G-MS of reorientation and/or Host correspondence respectively is carried to trigger in the message that disconnects described R4 data path and sends to Target DP Function.
When adopting the CMIPv4 agreement:
In the described steps A, ASN Functional Entity sends re-positioning request to Target FA, TargetFA returns the reorientation of carrying the G-MS that need carry out reorientation and/or main frame Host information to ASN Functional Entity and confirms, and to described G-MS and/or Host broadcasting mobility message;
Among the described step B, after described G-MS and/or Host receive the mobility broadcast, transmit Care-of Address CoA address registration request by Target FA to the home agent HA of oneself respectively;
Among described step e 1 or the E2, the process that trigger to disconnect the R4 data path of a G-MS who has carried out reorientation and/or Host specifically comprises:
Target DP Function returns the triggered response that disconnects described R4 data path to Target FA, wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host;
Target FA wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host to the response that ASN Functional Entity sends the reorientation success;
ASN Functional Entity disconnects the R4 data path of this G-MS and/or Host.
When adopting the PMIPv4 agreement:
In the described steps A, ASN Functional Entity sends re-positioning request to client PMIP Client;
Among the described step B, PMIP Client returns the reorientation of carrying the G-MS that need carry out reorientation and/or main frame Host information to ASN Functional Entity and confirms, and carries out the G-MS of reorientation and/or the home agent HA of main frame Host is transmitted Care-of Address CoA register requirement by Target FA to each respectively;
Among described step e 1 or the E2, the process that trigger to disconnect the R4 data path of a G-MS who has carried out reorientation and/or Host specifically comprises:
Target DP Function returns the triggered response that disconnects described R4 link to Target FA, wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host;
Target FA sends the registration response to client, wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host;
Client sends the reorientation success response to the access service network functional entity ASN FunctionalEntity that carries out network resource management, wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host;
ASN Functional Entity disconnects corresponding R4 link.
The method of control R3 re-anchoring comprises the steps: in a kind of multi-host WiMAX system under the IPv6 agreement
The access service network functional entity ASN Functional Entity of a, execution network resource management inserts route TargetAR to target and sends R3 data path re-positioning request, wherein carry the information of the G-MS and/or the main frame Host of reorientation, described Host connects G-MS;
B, Target AR send router broadcast message to described G-MS and/or Host, notify this G-MS and/or Host to carry out Care-of Address CoA Binding Update to the external agent HA of oneself respectively;
C, corresponding external agent HA are reoriented to its R3 data path on the target data passage controlled function entity Target DP Function after G-MS that confirms request and/or the success of Host Binding Update.
Also comprise the steps: after the described step c
The HA of d1, G-MS and/or Host correspondence extracts the sequence number of the packet of first described G-MS that passes through newly-built R3 data path transmission and/or Host respectively, and respectively the sequence number that extracts is sent to Target DP Function;
E1, Target DP Function are received packet before the sequence number of a G-MS who carries out reorientation and/or Host correspondence by the R4 data path respectively from grappling data channel controlled function entity A nchor DP Function after, trigger and disconnect corresponding R4 data path.
Also comprise the steps: after the described step c
D2, Target DP Function by newly-built R3 data path receive carry out first packet of the G-MS of reorientation and/or Host from each of corresponding HA after, extract the sequence number of first packet of this G-MS and/or Host respectively;
E2, Target DP Function are received packet before the sequence number of a G-MS who carries out reorientation and/or Host correspondence by the R4 data path respectively from grappling data channel controlled function entity A nchor DP Function after, trigger and disconnect corresponding R4 data path.
Specifically comprise the steps: among described step e1 or the e2
Target DP Function determine to receive from Anchor DP Function each carry out the G-MS of reorientation and/or the sequence number of last packet of Host subtracts 1 for corresponding described sequence number;
The described sequence number that Target DP Function receives each G-MS that carries out reorientation and/or Host correspondence by described R4 data path from Anchor DP Function subtracts to trigger behind 1 the packet and disconnects described R4 data path.
Perhaps, specifically comprise the steps: among described step e1 or the e2
Target DP Function sends to Anchor DP Function with each described sequence number that carries out the G-MS of reorientation and/or Host correspondence and carries out the transfer of data inquiry;
After Anchor DP Function confirms respectively to subtract 1 packet to the described sequence number that Target DP Function sends a G-MS who carries out reorientation and/or Host correspondence by described R4 data path, return to Target DP Function and to carry the corresponding G-MS and/or the inquiry response of Host identification information;
After Target DP Function whenever receives an inquiry response, trigger the corresponding R4 data path of this G-MS of disconnection and/or Host.
Described steps d specifically comprises the steps:
The Binding Update acknowledge message that HA will carry described sequence number sends to target access route TargetAR;
Target AR is carried at described sequence number to trigger in the message that disconnects described R4 data path and sends to Target DP Function.
When adopting the CMIPv6 agreement, among described step e1 or the e2, the process that triggers the R4 data path that disconnects a G-MS who has carried out reorientation and/or Host specifically comprises:
Target DP Function returns the triggered response that disconnects described R4 data path to Target FA, wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host;
Target FA wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host to the response that ASN Functional Entity sends the reorientation success;
ASN Functional Entity disconnects the R4 data path of this G-MS and/or Host.
The information of the G-MS of described reorientation and/or main frame Host comprises that G-MS and/or each are reoriented to the identification information of the Host on the Target DP Function.
When described G-MS and each Host that is attached thereto all carry out reorientation, the information of described G-MS and/or main frame Host comprises identification information and flag information of this G-MS, and this flag information shows that each Host that is connected with this G-MS all is reoriented to Target DP Function.
Beneficial effect of the present invention is as follows:
The method of the invention resets the identification information that carries the main frame that need carry out the G-MS of reorientation and/or be attached thereto in the request message at R3, thereby initiate the reorientation of G-MS and/or main frame synchronously, for the R3 re-anchoring control method that is suitable for is provided in the multi-host WiMAX system;
And the present invention is further before the R4 data path of the G-MS of reorientation and/or main frame is carried out in disconnection, confirm to carry out the G-MS of reorientation and/or data cached transmission of main frame finishes, thereby guaranteed to carry out the data integrity of the G-MS and/or the main frame of reorientation.
Description of drawings
Fig. 1 is common WiMAX system configuration schematic diagram;
Fig. 2 is the multi-host WiMAX system structural representation;
Fig. 3 is in the multi-host WiMAX system structure, carries out R3 Re-anchor data path before shown in the dotted line among the figure;
Fig. 4 is in the multi-host WiMAX system structure, carries out R3 Re-anchor data path afterwards shown in the solid line among the figure;
Fig. 5 is existing common WiMAX system, based on the netinit Re-anchor schematic flow sheet of the MS mobility Time Triggered of PMIPv4 agreement;
Fig. 6 is embodiment one flow chart of the method for the invention based on the CMIPv4 agreement;
Fig. 7 is the flow chart of the method for the invention based on another embodiment two of CMIPv4 agreement;
Fig. 8 is embodiment three flow charts of the method for the invention based on the CMIPv6 agreement.
Embodiment
The present invention at first proposes to realize in a kind of WiMAX multi-host system the method for R3 Re-anchor, and technical conceive is as follows:
Owing to network resource optimization or G-MS such as move at reason, G-MS and being connected in when all or part of needs carry out R3 Re-anchor in the main frame above it at first sends the process that R3Relocate Request asks initialization R3 Re-anchor by ASN Functional Entity.In R3 Relocate Request, need needs and carry out the ID tabulation of the G-MS of R3 Re-anchor and Host to inform that TargetFA (perhaps TargetAR) which G-MS and Host need be by reorientation (Relocate).Same, also need needs to carry out the ID tabulation of G-MS and the Host of R3Re-anchor among R3 Relocate Confirm and the R3 Relocate Response, after all new R3 data paths that need carry out the main frame of R3 Re-anchor and G-MS were set up, this R3 Re-anchor process had just been finished.Wherein, if G-MS and the main frame that is connected in above it all need carry out R3 Re-anchor, can in R3Relocate Request, R3 Relocate Confirm and R3 Relocate Response, use a flag bit all to need to carry out reorientation to represent all G-MS and Host;
Further, for guaranteeing the data integrity in the R3 Re-anchor process, before disconnecting the R4 data path, inquiry is buffered in the G-MS that carries out R3 Re-anchor among the Serving ASN GW and whether the data of Host all send, if also do not send, disconnect original R4 data path again after then waiting pending data to send; If send all data, then disconnect original R4 data path immediately.
Equally, in multi-host WiMAX system, difference according to concrete agreement, R3 Re-anchor process can be slightly variant, but no matter based on (the Proxy Mobile InternetProtocol of the PMIP under the IPv4 agreement, act on behalf of mobile network protocol) and CMIP (Client Mobile Internet Protocol, the client mobile network protocol) agreement, also be based on the CMIP agreement under the IPv6 agreement, the triggering of R3 Re-anchor process all comprises two kinds of situations: the netinit R3Re-anchor process that one triggers for the MS mobility event; It two is the netinit R3 Re-anchor process of network resource optimization Event triggered, and therefore, the process of existing R3 Re-anchor generally comprises six kinds of situations, below with specific embodiment and be described with reference to the accompanying drawings above technical conceive:
Embodiment one,
As shown in Figure 6, be R3 Re-anchor control method of the present invention concrete implementing procedure figure under the CMIPv4 agreement, with G-MS be connected in a Host above it to carry out R3 Re-anchor be example, comprise the steps:
1a-1b, old MIP context reciprocal process;
2-3, new ASN internal data way are set up process;
Wherein, arrow 1a and 1b represent Interface R3, and arrow 2 is represented the data path of inter/intra-ASN, and arrow 3 representatives are switched the ASN internal data way that the back is set up at inter/intra-ASN.Switch the packet loss that causes in order to reduce switching delay and R3, need set up an interim R4 forward data path, this R4 data path may be disconnected after the R3 handover success is finished;
The ASN functional entity (ASN Functional Entity) of 4a, execution network resource management sends R3 re-positioning request (R3 Relocate Request) to TargetFA;
4b, Target FA success received R3 Relocate Request after, will return to a R3 Relocate of ASNFunctional Entity Confirm;
Under the situation that G-MS moves or network resource optimization needs, ASN Functional Entity switches to Target FA initialization R3 by sending R3 Relocate Request.In R3 RelocateRequest primitive, comprise and to carry out the Host of R3 Re-anchor and the ID of G-MS.Target FA sends R3 Relocate Confirm message, and indication has successfully received R3Relocate Request to ASN Functional Entity.
According to the method for the invention, for the R3 Re-anchor process in the WiMAX system that supports many main frames, content in R3 Relocate Request and the R3 Relocate Confirm message need be made amendment, and what comprise in the amended primitive thes contents are as follows shown in the table 2:
Table 2
| Primitive | Message content |
| R3 Relocate Request | MS(G-MS)/Host ID，Target FA，Transaction ID |
| R3 Relocate Confirm | MS(G-MS)/Host ID，Hransaction ID |
Wherein original MS ID should be MS (G-MS)/Host ID.MS (G-MS)/Host ID represents to carry out the G-MS of R3 Re-anchor process and ID number of Host.
If the whole Re-anchor of the Host that G-MS links to each other with it to Target FA, also can only increase a flag bit in these three primitive, this flag bit is used to represent whether G-MS needs to carry out R3 Re-anchor with the Host that is connected in above it.Like this as all G-MS be connected in and just do not need all ID number all to be write in these three primitive the byte that can save primitive when Host above it needs to carry out R3 Re-anchor.
5a-5b) successful reception after the R3 mobility handover trigger, Target FA is according to ID number of G-MS among the R3 RelocateRequest and Host, the G-MS from R3 Re-anchor process to needs and the Host that carry out send Mobility Advertisement message;
Mobility Advertisement notice G-MS and Host carry out reorientation, have wherein carried the identification information of G-MS and host
6a-8b) MIP updating context;
The G-MS that need carry out R3 Re-anchor process utilizes the relevant information of MIP to send a MIP Registration Request message to Target FA respectively with Host, Target FA transmits MIPRegistration Request respectively and gives the HA of G-MS and the HA of Host then, to upgrade the Care-of Address CoA of G-MS and Host binding.After the Binding Update success, need carry out the G-MS of reorientation and the new R3 data path of Host and just set up.HA (G-MS) and HA (Host) succeed in registration to Target FA transmission MIP Registration Reply message authentication respectively then.
MIP Registration Request has the function of the new Care-of Address CoA of registration, the production method of new Care-of Address CoA has a variety of, a kind of Target of being FA carries a Care-of Address tabulation in Mobility Advertisement, selecting one by terminal oneself registers by Target FA then, a kind of is directly to select the address (it is exactly a Care-of Address) of Target FA to register according to Mobility Advertisement message, also having a kind of is to seek DHCP (Dynamic Host Configuration Protocol) server after terminal is received Mobility Advertisement, automatically give CoA address of terminal distribution by this server, and then register to HA by FA by terminal, the distribution method of this CoA address has a lot, and comparative maturity, no longer describe in detail here.
9a-9b) after the successful registration, the R3 MIP context of new G-MS and Host is established, and all data paths from HA (G-MS) and HA (Host) will be redirected to Target FA.
If G-MS and the Host that is connected in above it carry out R3 Re-anchor success, this G-MS and the original R4 data path that uses of Host that is connected in above it can be disconnected, for all data that guarantee Anchor DP Function before data path disconnects have all been issued Target DP Function, before disconnecting the R4 data path, inquire whether original Anchor DP Function has distributed data in buffer, if do not send, then wait for after it sends data in buffer disconnecting original R4 data path again; If send, then disconnect original R4 data path immediately, wherein:
Under the IPv4 agreement, whether trigger TargetDP Function inquiry Anchor DP Function data after Target FA receives MIP registration Reply distributes, if distribute, then begin the flow process of back again, if do not distribute, then wait for the flow process of carrying out the back after Anchor DP Function distributes data in buffer again;
Under the IPv6 agreement, whether trigger Target DP Function inquiry Anchor DP Function data after Target AR receives Binding Update affirmation (BU Confirmation) distributes, if distribute, then begin the flow process of back again, if do not distribute, then wait for the flow process of carrying out the back after Anchor DP Function distributes data in buffer again.
Still as shown in Figure 6, the present invention increases or has optimized following steps:
8a, HA (G-MS) send MIP Registration Reply message to Target FA, wherein carry the sequence number X of first packet that HA (G-MS) will send to this G-MS of Target DP Function by newly-built R3 data path
G-MS
8b, HA (Host) send MIP Registration Reply message to Target FA, wherein carry the sequence number X of first packet that HA (Host) will send to this Host of Target DP Function by newly-built R3 data path
Host
It just stops to send data to Anchor DP Function after HA (G-MS) has sent MIP Registration Reply message, and data are sent to Target DP Function.In like manner, it just stops to send data to Anchor DP Function after HA (Host) has sent MIP Registration Reply message, and these data are sent to Target DP Function.
After 10a, Target FA receive MIP Registration Reply, send Trigger message, wherein carry sequence number X to Target DP Function
G-MSAnd X
Host
Sequence number X
G-MSAnd X
HostCan be carried at one and trigger transmission simultaneously in the message, also can be carried at two and trigger transmission respectively in the message.
10b, when Target DP Function sends DP Status Request primitive to Anchor DP Function, inquire whether the data of buffer memory (Buffer) among the current Anchor DP send, wherein carry sequence number X
G-MSAnd X
Host
In like manner, sequence number X
G-MSAnd X
HostCan be carried at transmission simultaneously in the DP Status Request primitive, also can be carried at transmission respectively in two DP Status Request primitive.
The sequence number to last packet of G-MS that Anchor DP Function then confirms need to send is X
G-MS-1, the sequence number to last packet of Host that need to send is X
Host-1.If the packet before current Anchor DP Function does not successfully send then continues the data (Buffer Data Transfer) of transmission buffer, and is sending back execution in step 10c by the R4 data path; If instead current Anchor DP Function is as successfully sending packet before, then direct execution in step 10c;
10c, current Anchor DP Function send DP Status Response primitive for Target DP Function, and the data that are illustrated among the Anchor DP all send;
Each carries out the G-MS of reorientation or the transfer of data of Host is independently, when G-MS carries out reorientation together with the Host that is attached thereto, Anchor DP Function sends DP Status Response primitive to Target DPFunction respectively, after Target DP Function has only the packet before the described sequence number of the G-MS that confirms this reorientation or Host all to finish receiving, send a Trigger message trigger and disconnect relevant R4 data path, carry the identification information of corresponding G-MS or Host in the Trigger message of each triggering.
10d, Target DP Function trigger the MIP Registration Reply message that Target FA sends the identification information that carries corresponding G-MS or Host to the Trigger message that Target FA sends the identification information that carries corresponding G-MS or Host;
After 11a-b) Target FA receives trigger from Target DP Function, send MIP Registration Reply message with response MIP RegistrationRequest message to G-MS and the Host that is connected in above it respectively, carry the identification information of corresponding G-MS or Host equally in this MIP Registration Request message;
12) successful R3 switch finish after, it be the R3 Relocate Response message of Successful that Target FA will send Status Field territory to ASN Functional Entity, wherein still need to carry the identification information of corresponding G-MS or Host;
If R3 switches unsuccessful, ASN Functional Entity will receive that also R3 Relocate Response that a Status Field territory is Unsuccessful is to return to original state so.
After ASN Function Entity receives that Status Field territory is the R3 RelocateResponse message of Successful, disconnect the R4 data path of this G-MS or Host again, target access gateway before this G-MS or the Host becomes an IAD that casts anchor, HA continues the data flow of this G-MS and Host is sent on the FA of Anchor ASN-GW by newly-built R3 data path, FA is forwarded to G-MS by BS, and G-MS is transmitted to Host again.If the Status Field territory among the R3 Relocate Response is Unsuccessful, ASN Function Entity keeps original R4 data path.
Equally, in order to realize the method for the invention, should carry in the R3 Relocate Response primitive and confirm to receive the G-MS of data or the id information of Host, all need carry out the G-MS of R3 Re-anchor process or data cached whole transmissions of Host finish with notice ASN Functional Entity.
Embodiment one is being that example has been described the step that guarantees data integrity under the CMIPv4 agreement, if be applied to the PMIPv4 agreement, the technological means that guarantees data integrity is just the same, and the client functionality of G-MS is born by independent function entity, therefore is with the embodiment difference:
1, the RELOCATION REQUEST message of ASN Functional Entity sends to PMIP client (PMIPClient), client directly sends care-of address registration request to the HA of correspondence respectively by Target FA, and needs are carried out G-MS in request or Host carries out the registration of Care-of Address;
2, triggering disconnection R4 link also is to finish by client, and one of them triggers disconnection process and is summarized as follows:
Target DP Function returns the triggered response that disconnects described R4 link to Target FA, wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host;
Target FA sends the registration response to PMIP client (PMIP Client), wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host;
Client sends the reorientation success response to the access service network functional entity ASN FunctionalEntity that carries out network resource management, wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host;
ASN Functional Entity disconnects and has carried out the G-MS of reorientation and/or the R4 data path of Host.
Embodiment two,
Method is equally applicable to the CMIPv6 agreement described in the foregoing description one, as shown in Figure 7, comprises the steps:
1a-1b, old MIP context reciprocal process;
2-3, new ASN internal data way are set up process;
Wherein, arrow 1a and 1b represent Interface R3, and arrow 2 is represented the data path of inter/intra-ASN, and arrow 3 representatives are switched the ASN internal data way that the back is set up at inter/intra-ASN.Switch the packet loss that causes in order to reduce switching delay and R3, need set up an interim R4 forward data path, this R4 data path may be disconnected after the R3 handover success is finished;
The ASN functional entity (ASN Functional Entity) of 4a, execution network resource management sends R3 re-positioning request (R3 Relocate Request) to TargetAR;
4b, Target AR success received R3 Relocate Request after, will return to a R3 Relocate of ASNFunctional Entity Confirm;
Under the situation that G-MS moves or network resource optimization needs, ASN Functional Entity switches to Target AR initialization R3 by sending R3 Relocate Request.In R3 RelocateRequest primitive, comprise and to carry out the Host of R3 Re-anchor and the ID of G-MS.Target AR sends R3 Relocate Confirm message, and indication has successfully received R3Relocate Request to ASN Functional Entity.
According to the method for the invention, for the R3 Re-anchor process in the WiMAX system that supports many main frames, content among R3 Relocate Request and the R3 Relocate Confirm need be made amendment, and what comprise in the amended primitive thes contents are as follows shown in the table 2:
Table 2
| Primitive | Message content |
| R3 Relocate Request | MS(G-MS)/Host ID，Target AR，Transaction ID |
| R3 Relocate Confirm | MS(G-MS)/Host ID，Transaction ID |
Wherein original MS ID should be MS (G-MS)/Host ID.MS (G-MS)/Host ID represents to carry out the G-MS of R3 Re-anchor process and ID number of Host.
If the whole Re-anchor of the Host that G-MS links to each other with it to Target AR, also can only increase a flag bit in these three primitive, this flag bit is used to represent whether G-MS needs to carry out R3 Re-anchor with all Host that are connected in above it.Like this as all G-MS be connected in and just do not need all ID number all to be write in these three primitive the byte that can save primitive when Host above it needs to carry out R3 Re-anchor.
5a-5b) successful reception after the R3 mobility handover trigger, Target AR is according to ID number of G-MS among the R3 RelocateRequest and Host, the G-MS from R3 Re-anchor process to needs and the Host that carry out send Router Advertisement message;
Router Advertisement message is used to notify G-MS and Host to carry out reorientation, has wherein carried the id information (this id information can be their home address) of G-MS and Host)
6a-6b), the MIP updating context, the G-MS and the Host that need carry out R3 Re-anchor process calculate new Care-of Address CoA respectively;
7a-8b, G-MS and Host are respectively and carry out Binding Update (Binding Update) and binding acknowledgement (Binding Acknowledgement) between the affiliated HA;
9a-10) new G-MS and the R3 MIP context of Host are established, and all data paths from HA (G-MS) and HA (Host) will be redirected to Target AR.
11, successfully after the registration, Target AR will receive Binding Update affirmation (BU Confirmation) message of HA (G-MS) and HA (Host);
If G-MS and be connected in that only some need carry out R3 Re-anchor process among the Host above it, R4 data path originally can keep the operate as normal with Host or the G-MS that guarantees not carry out Re-anchor always.
If G-MS and the Host that is connected in above it need to carry out R3 Re-anchor, so after R3Re-anchor finishes, old R4 data path can be disconnected, for all data that guarantee Anchor DP Function before data path disconnects have all been issued Target DP Function, before disconnecting the R4 data path, inquire whether original Anchor DP Function has distributed data in buffer, if do not send, then wait for after it sends data in buffer disconnecting original R4 data path again; If send, then disconnect original R4 data path immediately, wherein:
Still as shown in Figure 7, the present invention increases or has optimized following steps:
11a, HA (G-MS) send BU Confirmation message to Target AR, wherein carry the sequence number X of first packet that HA (G-MS) will send to this G-MS of Target DP Function by newly-built R3 data path
G-MS
11b, HA (Host) send BU Confirmation message to Target AR, wherein carry the sequence number X of first packet that HA (Host) will send to this Host of Target DP Function by newly-built R3 data path
Host
After HA (G-MS) has sent BU Confirmation message, stop to send data to Anchor DPFunction, and data are sent to Target DP Function.In like manner, after HA (Host) has sent BU Confirmation message, stop to send data to Anchor DP Function, and these data are sent to Target DP Function.
After 12a, Target AR receive BU Confirmation, send to Target DP Function respectively and carry sequence number X
G-MSOr X
HostTrigger message;
12b, Target DP Function send to Anchor DP Function respectively and carry sequence number X
G-MSOr X
HostDP Status Request primitive, inquire whether the data of buffer memory (Buffer) among the current Anchor DP Function send;
The sequence number to last packet of G-MS that Anchor DP Function then confirm to need sends respectively is X
G-MS-1, the sequence number to last packet of Host that need to send is X
Host-1.If the packet before current Anchor DP Function does not successfully send then continues the data (Buffer Data Transfer) of transmission buffer, and is sending back execution in step 12c by the R4 data path; If instead current Anchor DP Function is as successfully sending packet before, then direct execution in step 12c;
12c, current Anchor DP Function send DP StatusResponse primitive for respectively Target DP Function, and the data that are illustrated among the Anchor DP all send;
Anchor DP Function sends DP Status Response primitive to Target DP Function respectively, and Target DP Function triggers respectively and disconnects corresponding R4 data path.
12d, Target DP Function send Trigger message to Target AR respectively, wherein carry the G-MS that finished reorientation or the information of Host, triggering Target AR, to send Status Field territory to ASN Functional Entity be the R3 Relocate Response message of Successful;
If R3 switches unsuccessful, ASN Functional Entity will receive that also R3 Relocate Response that a Status Field territory is Unsuccessful is to return to original state so.
After ASN Function Entity receives that Status Field territory is the R3 RelocateResponse message of Successful, disconnect the R4 data path again, target access gateway before becomes an IAD that casts anchor, HA continues the data flow of G-MS and Host is sent on the AR of AnchorASN-GW by newly-built R3 data path, AR is forwarded to G-MS by BS, and G-MS is transmitted to Host again.If the Status Field territory among the R3 Relocate Response is Unsuccessful, ASN Function Entity keeps original R4 data path.
Equally,, must carry the G-MS that finishes reorientation or the information of Host in the R3 Relocate Response primitive, disconnect corresponding R4 data path with notice ASN Functional Entity in order to realize the method for the invention.
In the foregoing description, need be in process based on the R3 Re-anchor of the multi-host WiMAX communication system of CMIPv4 and CMIPv6 agreement, increase inquiry Anchor DP Function and whether sent the primitive DP Status Request of all data and the response primitive DP Status Response of this inquiry, and corresponding Trigger message, the existing MIP Registration Reply message of expansion is carried sequence number X, and optimizes the handling process of related functional entities.
Like this, after target FA (perhaps AR) receives MIP Registration Reply (perhaps BUConfirmation), triggering target DP Function sends DP StatusRequest primitive for Anchor DP Function, whether data in buffer sends among the inquiry Anchor DP, if do not send, then continue the data of transmission buffer, after sending all data in buffer, Anchor DP Function sends a DP Status Response primitive just for target DP Function, the data that are illustrated among the Anchor DP all send, serve DP Function then and just give triggered response of Target FA (perhaps Target AR), Target FA (perhaps Target AR) just sends MIP registrationReply (perhaps directly sending R3 Relocate Response) after receiving this response.
By in MIP Registration Reply, increasing the sequence number that HA will send to first packet of Target DP Function, make Target DP Function obtain the sequence number of first packet that HA transmits.Target DP Function is under the situation of the sequence number that has obtained first packet that HA transmits, the sequence number that wait is transmitted by Anchor DP Function is the packet (i.e. last packet that is sent by AnchorDP Function) of X-1, thereby guarantees the integrality of data.
The affirmation process of transfer of data integrality can also further be reduced to following two steps:
The first step: Target DP Function confirms from the sequence X-1 of last packet of Anchor DP Function reception two kinds of implementation methods are arranged:
1, still in MIP Registration Reply (or BU Confirmation) message, increases and carry the sequence number X that HA will issue first packet of Target DP Function, after Target AR receives this message, in the triggering message that sends to Target DP Function, carry this sequence number X, then confirm from the sequence X-1 of last packet of Anchor DP Function reception;
2, in the process of R3 Re-anchor, receive first packet that transmits from HA as Target DP Function after, note the sequence number X of this packet.
Second step: Target DP Function receives the packet that sequence number is X-1 from Anchor DP Function after, trigger disconnection R3 data path again.
Be that example also is elaborated in conjunction with the accompanying drawings with above-mentioned second method below:
Embodiment three
As shown in Figure 8, be R3 Re-anchor control method of the present invention another concrete implementing procedure figure under the CMIPv4 agreement, compare with Fig. 6, it is as described below to trigger the step disconnect the R4 data path of G-MS wherein, and the step that the R4 data path of Host disconnects is similar with it:
After 10a, Target FA receive MIP Registration Reply from HA (G-MS), send the triggering message that disconnects the R3 data path to TargetDP Function;
Abstraction sequence X the packet of first this G-MS that 10b, Target DP Function receive from HA (G-MS)
G-MSAnd record;
Then, Target DP Function determines that the sequence number of last packet of this G-MS that receive from Anchor Data Path Function is X
G-MS-1;
10b, Target DP Function confirm that receiving sequence number is X
G-MSBehind-1 the packet, send Trigger message, trigger Target FA and send MIP Registration Reply message to TargetFA;
After ASN Function Entity receives that Status Field territory is the R3 RelocateResponse message of Successful, disconnect the R4 data path of this G-MS again, target access gateway before becomes an IAD that casts anchor, and continuation step 11 and 12, HA continues the data flow of this travelling carriage is sent on the FA of Anchor ASN-GW by newly-built R3 data path, and FA is forwarded to this G-MS by BS.If the Status Field territory among the R3 Relocate Response is Unsuccessful, ASN FunctionEntity keeps original R4 data path.
Equally,, must carry the G-MS that finishes reorientation or the information of Host in the R3 Relocate Response primitive, disconnect corresponding R4 data path with notice ASN Functional Entity in order to realize the method for the invention.
Optimization method based on the PMIPv6 agreement also can be simplified, and transfer of data is confirmed that step was reduced to for two steps, and method for simplifying is identical, repeats no more here.
In the foregoing description three, need be in process based on the R3 Re-anchor of the multi-host WiMAX communication system of CMIPv4 and CMIPv6 agreement, increase corresponding Trigger message, expansion MIPRegistration Reply message is carried sequence number X, and the handling process of optimization related functional entities is to finish technical solution of the present invention.
It is that example describes that above embodiment carries out R3 Re-anchor with a G-MS simultaneously with a Host who is attached thereto, and the method for the invention is applicable to following scene:
1, G-MS and an above Host being attached thereto carry out R3 Re-anchor simultaneously;
2, G-MS carries out R3 Re-anchor separately;
3, a plurality of Host carry out R3 Re-anchor simultaneously.
Concrete thinking and embodiments of the invention are identical, give unnecessary details no longer one by one here, and obviously, those skilled in the art can carry out various changes and modification and not break away from the spirit and scope of the present invention the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (19)
1, the method for control R3 re-anchoring in a kind of multi-host WiMAX system under the IPv4 agreement is characterized in that, comprises the steps:
The access service network functional entity ASN Functional Entity of A, execution network resource management sends R3 data path re-positioning request, wherein carry the G-MS that need carry out reorientation and/or the address information of main frame Host information and target foreign agent Target FA, described Host connects G-MS;
B, Target FA will be transmitted to the home agent HA of G-MS and/or main frame Host according to the Care-of Address CoA register requirement that re-positioning request triggers respectively, and request HA upgrades the Care-of Address CoA of described G-MS and/or Host;
C, HA are respectively the R3 data path between newly-built HA of G-MS and/or Host and the Target FA, and G-MS and/or Host are reoriented on the Target FA after confirming that respectively the Care-of Address CoA of the G-MS that asks and/or Host succeeds in registration.
2, the method for claim 1 is characterized in that, also comprises the steps: after the described step C
The HA of D1, G-MS and/or Host correspondence extracts the sequence number with the packet of first described G-MS that sends by newly-built R3 data path and/or Host respectively, and respectively the sequence number that extracts is sent to Target DP Function;
E1, Target DP Function are received packet before the sequence number of a G-MS who carries out reorientation and/or Host correspondence by the R4 data path respectively from grappling data channel controlled function entity A nchor DP Function after, trigger and disconnect corresponding described R4 data path.
3, the method for claim 1 is characterized in that, also comprises the steps: after the described step C
D2, Target DP Function by newly-built R3 data path receive carry out first packet of the G-MS of reorientation and/or Host from each of corresponding HA after, extract the sequence number of first packet of this G-MS and/or Host respectively;
E2, Target DP Function are received packet before the sequence number of a G-MS who carries out reorientation and/or Host correspondence by the R4 data path respectively from grappling data channel controlled function entity A nchor DP Function after, trigger and disconnect corresponding described R4 data path.
4, as claim 2 or 3 described methods, it is characterized in that, carry out the G-MS and/or the Host of reorientation, specifically comprise the steps: among described step e 1 or the E2 for each
This sequence number that carries out last packet of the G-MS of reorientation and/or Host that Target DP Function determines to receive from Anchor DP Function subtracts 1 for corresponding described sequence number;
The described sequence number that Target DP Function receives this G-MS and/or Host correspondence by described R4 data path from Anchor DP Function triggers the R4 data path that disconnects this G-MS and/or Host after subtracting 1 packet.
5, as claim 2 or 3 described methods, it is characterized in that, carry out the G-MS and/or the Host of reorientation, specifically comprise the steps: among described step e 1 or the E2 for each
Target DP Function sends to Anchor DP Function with this described sequence number that carries out the G-MS of reorientation and/or Host correspondence and carries out the transfer of data inquiry;
Anchor DP Function confirms to send this G-MS and/or after the described sequence number of Host correspondence subtracts 1 packet, to return an inquiry response to Target DPFunction to Target DP Function by described R4 data path;
After Target DP Function receives inquiry response, trigger the R4 data path that disconnects this G-MS and/or Host.
6, as claim 2 or 3 described methods, it is characterized in that described step D specifically comprises the steps:
The registration reply message that each HA that carries out the G-MS of reorientation and/or Host correspondence will carry corresponding described sequence number respectively sends to target foreign agent Target FA;
The described sequence number that Target FA carries out each G-MS of reorientation and/or Host correspondence respectively is carried to trigger in the message that disconnects described R4 data path and sends to Target DP Function.
7, as claim 2 or 3 described methods, it is characterized in that, when adopting the CMIPv4 agreement:
In the described steps A, ASN Functional Entity sends re-positioning request to Target FA, TargetFA returns the reorientation of carrying the G-MS that need carry out reorientation and/or main frame Host information to ASN Functional Entity and confirms, and to described G-MS and/or Host broadcasting mobility message;
Among the described step B, after described G-MS and/or Host receive the mobility broadcast, transmit Care-of Address CoA address registration request by Target FA to the home agent HA of oneself respectively;
Among described step e 1 or the E2, the process that trigger to disconnect the R4 data path of a G-MS who has carried out reorientation and/or Host specifically comprises:
Target DP Function returns the triggered response that disconnects described R4 data path to Target FA, wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host;
Target FA wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host to the response that ASN Functional Entity sends the reorientation success;
ASN Functional Entity disconnects the R4 data path of this G-MS and/or Host.
8, as claim 2 or 3 described methods, it is characterized in that, when adopting the PMIPv4 agreement:
In the described steps A, ASN Functional Entity sends re-positioning request to client PMIP Client;
Among the described step B, PMIP Client returns the reorientation of carrying the G-MS that need carry out reorientation and/or main frame Host information to ASN Functional Entity and confirms, and carries out the G-MS of reorientation and/or the home agent HA of main frame Host is transmitted Care-of Address CoA register requirement by Target FA to each respectively;
Among described step e 1 or the E2, the process that trigger to disconnect the R4 data path of a G-MS who has carried out reorientation and/or Host specifically comprises:
Target DP Function returns the triggered response that disconnects described R4 link to Target FA, wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host;
Target FA sends the registration response to client, wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host;
Client sends the reorientation success response to the access service network functional entity ASN FunctionalEntity that carries out network resource management, wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host;
ASN Functional Entity disconnects corresponding R4 link.
9, the method for claim 1 is characterized in that, the information of the G-MS of described reorientation and/or main frame Host comprises that G-MS and/or each are reoriented to the identification information of the Host on the Target DP Function.
10, the method for claim 1, it is characterized in that, when described G-MS and each Host that is attached thereto all carry out reorientation, the information of described G-MS and/or main frame Host comprises identification information and flag information of this G-MS, and this flag information shows that each Host that is connected with this G-MS all is reoriented to Target DP Function.
11, the method for control R3 re-anchoring in a kind of multi-host WiMAX system under the IPv6 agreement is characterized in that, comprises the steps:
The access service network functional entity ASN Functional Entity of a, execution network resource management inserts route TargetAR to target and sends R3 data path re-positioning request, wherein carry the information of the G-MS and/or the main frame Host of reorientation, described Host connects G-MS;
B, Target AR send router broadcast message to described G-MS and/or Host, notify this G-MS and/or Host to carry out Care-of Address CoA Binding Update to the external agent HA of oneself respectively;
C, corresponding external agent HA are reoriented to its R3 data path on the target data passage controlled function entity Target DP Function after G-MS that confirms request and/or the success of Host Binding Update.
12, method as claimed in claim 11 is characterized in that, also comprises the steps: after the described step c
The HA of d1, G-MS and/or Host correspondence extracts the sequence number of the packet of first described G-MS that passes through newly-built R3 data path transmission and/or Host respectively, and respectively the sequence number that extracts is sent to Target DP Function;
E1, Target DP Function are received packet before the sequence number of a G-MS who carries out reorientation and/or Host correspondence by the R4 data path respectively from grappling data channel controlled function entity A nchor DP Function after, trigger and disconnect corresponding R4 data path.
13, method as claimed in claim 11 is characterized in that, also comprises the steps: after the described step c
D2, Target DP Function by newly-built R3 data path receive carry out first packet of the G-MS of reorientation and/or Host from each of corresponding HA after, extract the sequence number of first packet of this G-MS and/or Host respectively;
E2, Target DP Function are received packet before the sequence number of a G-MS who carries out reorientation and/or Host correspondence by the R4 data path respectively from grappling data channel controlled function entity A nchor DP Function after, trigger and disconnect corresponding R4 data path.
14, as claim 12 or 13 described methods, it is characterized in that, specifically comprise the steps: among described step e1 or the e2
Target DP Function determine to receive from Anchor DP Function each carry out the G-MS of reorientation and/or the sequence number of last packet of Host subtracts 1 for corresponding described sequence number;
The described sequence number that Target DP Function receives each G-MS that carries out reorientation and/or Host correspondence by described R4 data path from Anchor DP Function subtracts to trigger behind 1 the packet and disconnects described R4 data path.
15, as claim 12 or 13 described methods, it is characterized in that, specifically comprise the steps: among described step e1 or the e2
Target DP Function sends to Anchor DP Function with each described sequence number that carries out the G-MS of reorientation and/or Host correspondence and carries out the transfer of data inquiry;
After Anchor DP Function confirms respectively to subtract 1 packet to the described sequence number that Target DP Function sends a G-MS who carries out reorientation and/or Host correspondence by described R4 data path, return to Target DP Function and to carry the corresponding G-MS and/or the inquiry response of Host identification information;
After Target DP Function whenever receives an inquiry response, trigger the corresponding R4 data path of this G-MS of disconnection and/or Host.
16, as claim 12 or 13 described methods, it is characterized in that described steps d specifically comprises the steps:
The Binding Update acknowledge message that HA will carry described sequence number sends to target access route TargetAR;
Target AR is carried at described sequence number to trigger in the message that disconnects described R4 data path and sends to Target DP Function.
17, method as claimed in claim 16 is characterized in that, when adopting the CMIPv6 agreement, among described step e1 or the e2, the process that triggers the R4 data path that disconnects a G-MS who has carried out reorientation and/or Host specifically comprises:
Target DP Function returns the triggered response that disconnects described R4 data path to Target FA, wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host;
Target FA wherein carries and has carried out the G-MS of reorientation and/or the identification information of Host to the response that ASN Functional Entity sends the reorientation success;
ASN Functional Entity disconnects the R4 data path of this G-MS and/or Host.
18, method as claimed in claim 11 is characterized in that, the information of the G-MS of described reorientation and/or main frame Host comprises that G-MS and/or each are reoriented to the identification information of the Host on the Target DP Function.
19, method as claimed in claim 11, it is characterized in that, when described G-MS and each Host that is attached thereto all carry out reorientation, the information of described G-MS and/or main frame Host comprises identification information and flag information of this G-MS, and this flag information shows that each Host that is connected with this G-MS all is reoriented to Target DP Function.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200610000501 CN1996911A (en) | 2006-01-05 | 2006-01-05 | A method for controlling the R3 re-anchoring in the multi-host WiMAX system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200610000501 CN1996911A (en) | 2006-01-05 | 2006-01-05 | A method for controlling the R3 re-anchoring in the multi-host WiMAX system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN1996911A true CN1996911A (en) | 2007-07-11 |
Family
ID=38251859
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200610000501 Pending CN1996911A (en) | 2006-01-05 | 2006-01-05 | A method for controlling the R3 re-anchoring in the multi-host WiMAX system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1996911A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009092308A1 (en) * | 2008-01-10 | 2009-07-30 | Huawei Technologies Co., Ltd. | Method and device for triggering re-authentication |
| WO2010000150A1 (en) * | 2008-06-30 | 2010-01-07 | 华为技术有限公司 | Method and system for transfering context information, and access service network |
| CN101309223B (en) * | 2008-07-02 | 2011-08-10 | 中兴通讯股份有限公司 | Data channel establishing method and system |
| CN102196407A (en) * | 2010-03-18 | 2011-09-21 | 中兴通讯股份有限公司 | Re-positioning method and system for anchored authentication device |
| CN101370260B (en) * | 2007-08-15 | 2013-01-30 | 北京三星通信技术研究有限公司 | Method for AAA implementing MS location capability negotiation |
| CN101370271B (en) * | 2007-08-15 | 2013-04-24 | 北京三星通信技术研究有限公司 | Method for positioning mobile station MS in WiMAX network |
-
2006
- 2006-01-05 CN CN 200610000501 patent/CN1996911A/en active Pending
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101370260B (en) * | 2007-08-15 | 2013-01-30 | 北京三星通信技术研究有限公司 | Method for AAA implementing MS location capability negotiation |
| CN101370271B (en) * | 2007-08-15 | 2013-04-24 | 北京三星通信技术研究有限公司 | Method for positioning mobile station MS in WiMAX network |
| WO2009092308A1 (en) * | 2008-01-10 | 2009-07-30 | Huawei Technologies Co., Ltd. | Method and device for triggering re-authentication |
| CN101483634B (en) * | 2008-01-10 | 2013-06-26 | 华为技术有限公司 | Method and apparatus for triggering reidentification |
| WO2010000150A1 (en) * | 2008-06-30 | 2010-01-07 | 华为技术有限公司 | Method and system for transfering context information, and access service network |
| CN101309223B (en) * | 2008-07-02 | 2011-08-10 | 中兴通讯股份有限公司 | Data channel establishing method and system |
| 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 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8423025B2 (en) | Method and system for managing context of mobile station | |
| KR100762615B1 (en) | Mobile Telecommunication System and Handoff Method for the Same | |
| US9036601B2 (en) | Support for continuity of tunnel communications for mobile nodes having multiple care of addressing | |
| KR101080852B1 (en) | Apparatus and method for network mobility management in Proxy Mobile IPv6 Network | |
| US8233437B2 (en) | Mobile IP communication system, apparatus, and method with DHCP proxy functions | |
| CN101247317B (en) | Routing switching method and system | |
| CN101803326B (en) | Method, system and device for location update in networks | |
| CN102106166A (en) | Anchoring services of a mobile station attached to a first service domain at a home agent in a second service domain | |
| CN100405871C (en) | Three-layer mobile switchover implementing method based on two-layer prediction and trigging | |
| CN1996911A (en) | A method for controlling the R3 re-anchoring in the multi-host WiMAX system | |
| CN101841877A (en) | Switching method, router and communication system | |
| CN100455111C (en) | Method and system of realizing R3 interface shift based on resource optimization | |
| CN101765092B (en) | Network switching method, device and system | |
| CN100596229C (en) | Method for apprizing the binding result of the target network address and mobile user terminal | |
| CN104540120A (en) | Route optimization method and system of mobile multicast supported by PMIPv6 | |
| KR100485355B1 (en) | Inter-Distribution system handoff method in WLANs | |
| JP5055428B2 (en) | Wireless communication system, gateway control apparatus, and base station | |
| KR100989732B1 (en) | HMIPv6 Network Based Handover Scheme and Access Router and Mobile Node Using Thereof | |
| CN101047996B (en) | Method, system for acquiring target network transmission address information and its application | |
| US7463606B2 (en) | Method for establishing a MIP and performing handoff by a mobile node | |
| CN1992659B (en) | Method of implementing data lossless transmission in the process of R3 re-anchoring | |
| KR20090054145A (en) | Method for performing fast handover traffic based on network | |
| KR20080010990A (en) | Method for serving mobile node supporting mobile ip in mobile telecommunication system using proxy mobile ip and therefor system | |
| KR101037531B1 (en) | Method for providing soft handover using communication state information in wireless internet system | |
| JP2003037626A (en) | Mobile communication method and system utilizing ip network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |