CN101883351A - Method and device for registering mobile IP - Google Patents
Method and device for registering mobile IP Download PDFInfo
- Publication number
- CN101883351A CN101883351A CN2009101365454A CN200910136545A CN101883351A CN 101883351 A CN101883351 A CN 101883351A CN 2009101365454 A CN2009101365454 A CN 2009101365454A CN 200910136545 A CN200910136545 A CN 200910136545A CN 101883351 A CN101883351 A CN 101883351A
- Authority
- CN
- China
- Prior art keywords
- interface
- binding
- network node
- register requirement
- mobile
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 75
- 230000027455 binding Effects 0.000 claims abstract description 322
- 238000009739 binding Methods 0.000 claims abstract description 322
- 230000008569 process Effects 0.000 claims description 46
- 230000005540 biological transmission Effects 0.000 claims description 4
- 230000011664 signaling Effects 0.000 abstract description 4
- 239000003795 chemical substances by application Substances 0.000 description 28
- 230000008859 change Effects 0.000 description 10
- 238000003032 molecular docking Methods 0.000 description 8
- 230000002457 bidirectional effect Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 238000007689 inspection Methods 0.000 description 5
- 102100029592 Activator of apoptosis harakiri Human genes 0.000 description 4
- 101150028113 Hrk gene Proteins 0.000 description 4
- 230000004044 response Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 1
- 239000012467 final product Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003137 locomotive effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000012797 qualification Methods 0.000 description 1
Images
Abstract
The invention provides a method and a device for registering a mobile IP. The method mainly comprises the following steps that: a first network node receives a first registration request sent by a mobile node, wherein the first registration request carries a first binding identifier of an interface to be registered; the first network node establishes binding for the interface to be registered according to the first registration request and the registration information of the interface which is arranged on the mobile node on the first network node, and determines whether sending a second registration request to a second network node is necessary; and when needing to send the second registration request to the second network node, the first network node sends the second registration request carrying a second binding identifier distributed to the mobile node or the interface identification information of the interface to be registered to the second network node. The method and the device for registering the mobile IP have the advantage of realizing that a plurality of interfaces of the MN (mobile node) can be successively registered to a grading mobile IP system, and reducing the signaling load of the grading mobile IP system.
Description
Technical field
The present invention relates to network communications technology field, relate in particular to the method and apparatus that a kind of many interfaces MN (MobileNode, mobile node) carries out mobile IP registration.
Background technology
The structural representation of existing mobile IPv 4 system comprises as lower unit: MN, CN (Correspondent Node, peer node), FA (Foreign Agent, external agent) and HA (Home Agent, home agent) as shown in Figure 1.Wherein,
MN: be terminal or router with locomotive function.When MN when a network or subnet move to another network or subnet, its attachment point also changes at any time, change has taken place in the position of MN access network.But the HoA of MN (Home Address, home address) does not change, and MN still can communicate with CN, and session is not interrupted.
CN:, be a mobile node or fixed network node with the node that MN communicates.
FA is after MN moves to visited network and registers, and for MN provides the router of mobile management and routing service, usually, is exactly the default router of MN at visited network.
HA is that MN registers at home network, and the router of mobile management and routing service is provided for MN.
The general work mechanism of mobile IPv 4 system comprises: mobile registration process and data forwarding process.
Hierarchical mobile IP v4 system expands on the basis of mobile IPv 4 and forms, and has increased network entity a: GFA (Gateway Foreign Agent, gateway external agent) in the hierarchical mobile IP v4 system newly.GFA has the function of FA, uses GFA-CoA (Care-ofAddress, Care-of Address) when it provides routing service.Co-CoA and FA-CoA with mobile IP system in the hierarchical mobile IP system are referred to as LCoA (Local CoA, local Care-of Address).
In hierarchical mobile IP v4 system, its initial registration flow process and mobile IPv 4 comparing class seemingly, difference is MN when HA registers, and also needs through GFA, the binding that will set up MN on GFA comprises the HoA of MN, LCoA and GFA-CoA etc.When GFA transmits registration message to HA, LCoA is removed from registration message, thereby HA goes up that the binding of setting up comprises is HoA, GFA-CoA address.On the data forwarding face, set up bidirectional tunnel between GFA and the HA, for the data service of MN provides route.
Simultaneously, in hierarchical mobile IP v4 system, when MN is mobile in the visited network at GFA place, increased regional registration message newly, MN only need carry out regional registration to GFA, and GFA does not need to be updated to HA, thereby can save the time-delay that MN moves switching.
The process that a kind of many interfaces MN of the prior art carries out the mobile IPv 4 registration mainly comprises: many interfaces MN obtains a HoA, when the different interface of this MN respectively by WiFi (WirelessFidelity, Wireless Fidelity), WiMAX (Worldwide Interoperability for Microwave Access, be micro-wave access global inter communication) etc. after heterogeneous networks inserts, on each interface, obtain different CoA, initiate to move registration to HA respectively by different interfaces, thereby set up many tunnels, these many tunnels can make MN obtain more bandwidth.
HoA and a plurality of CoA of above-mentioned MN are bound.Move in the registration at MN, in order to distinguish different CoA on MN, HA, many interfaces MN need be unique BID of each interface assignment (Binding Identifier, binding logo) when registration.Thereby after the CoA of certain interface of MN changed, when HA moved registration, HA can discern according to the BID of this interface.
Above-mentioned MN is different business flow distribution FID (Flow Identifier, a traffic identifier), and each FID is associated with different BID, and by streamer volume process, sets up not homogeneous turbulence binding on HA.Thereby, when HA receives that CN is sent to the Business Stream of MN, can distinguish according to the stream binding, index different binding BID then, also can this service route MN be transmitted by different tunnels.
In realizing process of the present invention, the inventor finds that there are the following problems at least in the prior art:
1, carries out in the process of mobile IPV4 registration at many interfaces MN, do not relate to the scene of hierarchical mobile IP v4, when MN moves to the visited network at GFA place, if GFA does not support many interfaces of MN to move registration simultaneously, then MN can only move registration with an interface, thereby can cause the already-existing session of MN not continue, perhaps can not obtain more bandwidth, and quality of service descends.
2, when a plurality of interfaces of MN by same FA when HA sets up a plurality of binding, FA needs to transmit register requirement to HA at each interface, thereby has increased registration time-delay and signaling traffic load; Further, when Business Stream switches between distinct interface, FA also needs to notify HA to upgrade, thereby has increased the time-delay that stream switches.
Summary of the invention
Embodiments of the invention provide a kind of method and apparatus of mobile IP registration, can successively be registered to the network at GFA/FA place with a plurality of interfaces of realizing MN.
A kind of method of mobile IP registration comprises:
First network node receives first register requirement that mobile node sends, and carries first binding logo of interface to be registered in described first register requirement;
According to described first register requirement, and when not having the log-on message of other interface on the described mobile node on described first network node, described first network node sends second register requirement to second network node, carries in described second register requirement to second binding logo of described mobile node distribution or the interface identifier information of described interface to be registered.
A kind of IP process registration comprises:
First network node receives the regional registration request that mobile node sends, and carries the binding logo of interface to be registered in the described regional registration request, the register requirement in the territory that described regional registration request is the described first network node place;
According to described regional registration request, create or upgrade the binding clauses and subclauses of described mobile node.
A kind of device of mobile IP registration comprises:
The register requirement receiver module is used to receive first register requirement that mobile node sends, and carries first binding logo of interface to be registered in described first register requirement;
The register requirement processing module, be used for according to described first register requirement, and when not having the log-on message of other interface on the described mobile node on the described device, send second register requirement to second network node, carry in described second register requirement to second binding logo of described mobile node distribution or the interface identifier information of described interface to be registered.
A kind of device of IP registration comprises:
Regional registration request receiver module is used to receive the regional registration request that mobile node sends, and carries the binding logo of interface to be registered in the described register requirement, the register requirement in the territory that described regional registration request is the described first network node place;
Module is set up in binding, is used for creating or upgrade the binding clauses and subclauses of described mobile node according to the received register requirement of described regional registration request receiver module.
A kind of system of mobile IP registration comprises:
First network node is used to receive first register requirement that mobile node sends, and carries first binding logo of interface to be registered in described first register requirement; According to described first register requirement, and when not having the log-on message of other interface on the described mobile node on described first network node, send second register requirement to second network node, carry in described second register requirement to second binding logo of described mobile node distribution or the interface identifier information of described interface to be registered.
Second network node is used to receive second register requirement that described first network node sends, and according to the interface identifier information of second binding logo that carries in described second register requirement or described interface to be registered, described mobile node is registered.
The technical scheme that is provided by the embodiment of the invention described above as can be seen, register requirement and the log-on message of the interface on the MN on first network node that the embodiment of the invention receives by first network node basis, set up binding for the interface to be registered of MN, and judge whether and to send second register requirement to second network node, a plurality of interfaces of having realized MN can successively be registered to the hierarchical mobile IP system, and can reduce the signaling traffic load of hierarchical mobile IP system.
Description of drawings
In order to be illustrated more clearly in the technical scheme of the embodiment of the invention, the accompanying drawing of required use is done to introduce simply in will describing embodiment below, apparently, accompanying drawing in describing below only is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 is the structural representation of existing a kind of mobile IPv 4 system;
The process chart of the method for a kind of mobile IP registration that Fig. 2 provides for the embodiment of the invention one;
The structural representation of a kind of hierarchical mobile IP v4 system that Fig. 3 provides for the embodiment of the invention one;
Fig. 4 is the application scenarios schematic diagram of the embodiment of the invention two;
The interface IF1 as MN that Fig. 5 provides for the embodiment of the invention two, interface IF2 are successively by the process chart of GFA when HA registers;
Interface IF1, the interface IF2 of many interfaces MN that Fig. 6 provides for the embodiment of the invention three is respectively to the process chart of GFA registration flow;
Proxy mode realizes that down FA supports many interfaces successively/simultaneously to move the application scenarios schematic diagram of registration in the mobile IPv 4 system that Fig. 7 provides for the embodiment of the invention four;
The MN that Fig. 8 provides for the embodiment of the invention four goes up interface IF1, interface IF2 successively by the process chart of FA when HA registers;
The processing of request flow charts that the GFA/FA that Fig. 9 provides for the embodiment of the invention six binds the foundation of MN more;
A kind of multiple interface mobile node that Figure 10 provides for the embodiment of the invention carries out the structural representation of the device of mobile IP registration;
The structural representation of the device of a kind of regional mobile IP registration that Figure 11 provides for the embodiment of the invention.
Embodiment
In embodiments of the present invention, the Foreign Agent of mobile node or gateway Foreign Agent are after receiving the register requirement that mobile node sends respectively by different interfaces, set up respectively between each interface of described Foreign Agent or gateway Foreign Agent and described mobile node to binding, the total interface of described mobile node is set up going out to binding between public and the home agent.
For ease of understanding, be that example is further explained explanation below in conjunction with accompanying drawing with several specific embodiments, and each embodiment does not constitute the qualification to the embodiment of the invention to the embodiment of the invention.
Embodiment one
The handling process of the method for a kind of mobile IP registration that this embodiment provides comprises following treatment step as shown in Figure 2:
In this embodiment, at first, first network node receives mobile node by first register requirement that interface to be registered sends, and carries first binding logo of interface to be registered in described first register requirement.
Such as, in hierarchical mobile IP v4 system shown in Figure 3, first network node is GFA/FA.Mobile node sends first register requirement by interface 1 to GFA/FA, carries first binding logo of interface 1 in this first register requirement.
Be specially: after first network node receives above-mentioned first register requirement, when checking the log-on message that does not have other interface on the described mobile node on first network node, promptly above-mentioned first register requirement that sends by interface 1 is first register requirement that mobile node sends to GFA/FA.
So above-mentioned first network node sends second register requirement to second network node, carry in described second register requirement to second binding logo of described mobile node distribution or the interface identifier information of described interface to be registered (being interface 1).
Such as, in above-mentioned hierarchical mobile IP v4 system shown in Figure 3, second network node is HA.
Further, first network node specifically comprises to the process that described second network node sends second register requirement:
Described first network node is that described interface to be registered (being interface 1) is set up and to be comprised going into to binding and comprising described the going out to binding of second binding logo that described mobile node distributes of giving of described first binding logo.In Fig. 3, above-mentionedly go out to binding to represent that with MN binding X above-mentioned to go out to binding be that the total interface of mobile node is shared, the above-mentioned binding information that goes out to comprise the mobile node request registration in binding.Described second binding logo and described first binding logo are identical or different.
Described first network node sends second register requirement of carrying second binding logo that distributes to described mobile node to described second network node.
Afterwards, when other interface (such as interface 2) that passes through of above-mentioned mobile node sends register requirement to described first network node, when carrying the binding logo of other interface in this register requirement.Because interface 1 is registered to above-mentioned first network node, above-mentioned first network node is checked through described mobile node has the interface log-on message on described first network node, so described first network node is that described other interface is set up going into to binding of the binding logo that comprises described other interface.Set up out to binding for this other interface, do not send second register requirement yet to described second network node.
Further, in described first register requirement, also comprise: the information of the stream on the described mobile node, and, when this stream carries out initial registration on described first network node, described first network node sends second register requirement to second network node, and described second register requirement carries the stream information on the described mobile node.
When switching between the interface of the stream on the MN in the visited network at GFA/FA place, MN switches registration, and this moment, GFA/FA only upgraded in going into to binding of correspondence, and the content that goes out to binding does not change, do not upgrade going out to binding, GFA/FA does not send register requirement to HA;
When the interface on the MN is mobile in the visited network at GFA/FA place, change has taken place in the CoA on the interface, MN switches registration, this moment, GFA/FA only upgraded in going into to binding of correspondence, the content that goes out to binding does not change, do not upgrade going out to binding, GFA/FA does not initiate register update to HA;
When the stream on the MN or interface are being striden between the interface of visited network at GFA/FA place when mobile, MN switches registration, this moment, GFA/FA upgraded in going into to binding of correspondence, go out to the content of binding also to upgrade simultaneously, need upgrade going out to binding, GFA/FA initiates register update to HA.If stream switches on the overseas interface of GFA/FA or interface to move to GFA/FA overseas, then GFA/FA deletes the stream information in this binding or deletes the binding of this interface correspondence.
Embodiment two
Present embodiment is described the mobile process registration of many interfaces priorities of GFA support MN in the hierarchical mobile IP v4 system, and the application scenarios schematic diagram of this embodiment as shown in Figure 4.
In scene shown in Figure 4, many interfaces MN401 has 3 interface IF1, interface IF2 and interface IF3, corresponding different respectively networks.
Interface IF1 is connected to the visited network at GFA place, uses FA-CoA1 (external agent's Care-of Address), registers to HA404 by FA402, GFA403.
Interface IF2 is connected to the visited network at GFA403 place, uses Co-CoA2 (coexistence Care-of Address), directly registers to HA404 by GFA403.
Interface IF3 connects the visited network at non-GFA place, uses Co-located CoA3 (local Care-of Address coexists) in the visited network at non-GFA place.
In above-mentioned application scenarios shown in Figure 4, when interface IF1, the interface IF2 of above-mentioned MN as shown in Figure 5 by the handling process of GFA when HA registers successively, comprise following treatment step:
Step 51, MN send login request message by interface IF1 to FA.
The interface IF1 of MN is attached to network, by the network startup process, finish access authentication after, obtained information such as home address, GFA-CoA, FA-CoA1.Then, MN sends login request message by interface IF1 to FA, carries the binding logo BID1 that promising interface IF1 generates in this login request message, and the information of HoA, GFA-CoA and some other register requirement (as security parameter).
Step 52, FA send login request message to GFA.
FA receives above-mentioned login request message, for MN sets up binding, comprises the HoA of MN in this binding, information such as CoA, BID1.FA sends this login request message to GFA insert the FA-CoA1 address information in above-mentioned login request message after.
Step 53, GFA send register requirement to HA, and HA returns registration reply to GFA.
GFA determines that the interface IF1 of MN is registering after receiving the login request message of above-mentioned FA transmission.
GFA at first sets up going into to binding of the binding logo that comprises interface IF1 for the interface IF1 of MN, and this goes into the HoA that comprises MN in binding, information such as FA-CoA1, BID1, and security parameter, stream information etc.;
Secondly for MN sets up out to binding, this goes out other information such as HoA, GFA-CoA that comprise newly-generated binding logo BIDx and MN in binding, and and goes into mapped identification information between binding etc.The value of above-mentioned BIDx is identical or different with the BID1 in the login request message that receives.
Then, GFA sends register requirement to HA, comprises HoA, the GFA-CoA of MN in this register requirement, and new information such as binding logo BIDx.After HA receives above-mentioned register requirement,, set up bidirectional tunnel, so that transmit the message of MN with GFA for MN creates binding.
HA returns registration reply message by GFA, FA to MN, finishes the registration process of above-mentioned interface IF1.
Step 54, MN send login request message by interface IF2 to FA, and whether the binding information of the IF2 registration of GFA inspection MN is consistent with the binding information of IF1 registration.
The interface IF2 of MN is attached to network, by the network startup process, finish access authentication after, obtained home address, GFA-CoA, information such as Co-CoA2.Then, MN directly sends login request message by interface IF2 to GFA, carry the binding logo BID2 that promising interface IF2 generates in this login request message, HoA, GFA-CoA, and HFA (Hirarchinal Foreign Agent, the graded external agency) scaling option (comprising Co-CoA2), and the information (as security parameter) of some other register requirement.
Above-mentioned MN is local login request message or regional registration request message to the login request message that GFA sends.After GFA receives above-mentioned register requirement, determine the registered binding of the interface IF1 BID1 of MN,, therefore set up new going into to binding for the interface IF2 of MN when the binding BID2 of front port IF2 registration is different with it.
Simultaneously, whether the binding information of the IF2 registration of GFA inspection MN is consistent with the binding information of IF1 registration, and for example whether stream information is consistent, if inconsistent, then execution in step 55; If consistent, then do not need to upgrade going out of MN to binding, at this moment, the going into of the last foundation of GFA to binding:
| Home address | Care-of Address | Binding logo | Other information |
| ??HoA1 | ??FA-CoA1 | ??BID1 | As: strategy/stream information etc. ... |
| ??HoA1 | ??Co-CoA2 | ??BID2 | ??... |
| ??... | ??... | ??... | ??... |
Last the going out of setting up of GFA to binding:
| Home address | Care-of Address | Binding logo | Other information (as stream information) |
| ??HoA1 | ??GFA-CoA | ??BIDx | As: strategy/stream information etc. ... |
| ??... | ??... | ??... | ??... |
At this moment, GFA does not need to send register requirement to HA, and GFA returns registration reply message to MN.Finish the registration process of above-mentioned interface IF2.
The MN that step 55, GFA renewal have been set up goes out to binding, sends the register requirement that carries out to the lastest imformation of binding to HA.
When the binding information of the IF2 of MN registration was inconsistent with the binding information of IF1 registration, GFA upgraded going out to binding of the MN that set up, also added the binding information (such as stream information) of IF2 registration to above-mentioned MN going out in binding.Then, send the register requirement that carries out to the lastest imformation of binding to HA.
After HA receives above-mentioned register requirement, for MN upgrades binding.HA returns registration reply message by GFA, FA to MN.Finish the registration process of above-mentioned interface IF2.
Step 56, MN send login request message by interface IF3 to HA, and HA sets up binding for interface IF3.
The interface IF3 of MN is attached to network, by the network startup process, finish access authentication after, obtained home address, Co-CoA3 etc.Then, MN directly sends login request message by interface IF3 to HA, carries binding logo BID3 and HoA, Co-CoA3 that promising interface IF3 generates in this login request message, and some other information (as security parameter) etc.
After HA receives above-mentioned register requirement, for interface IF3 sets up binding.
Thereby last the binding of setting up of HA:
| Home address | Care-of Address | Binding logo | Other information |
| ??HoA1 | ??GFA-CoA | ??BIDx | As: strategy/stream information etc. ... |
| ??HoA1 | ??Co-CoA3 | ??BID3 | ??... |
| ??... | ??... | ??... | ??... |
Embodiment three
On the basis of the foregoing description two, when MN comprises the information of the stream on the mobile node in the register requirement that GFA sends, GFA supports the stream binding, and present embodiment is described the process that many interfaces MN carries out the streamer volume, and above-mentioned streamer volume includes but not limited to following several situation:
MN registers one or more streams by certain interface, and all streams are associated with the binding of this interface;
MN registers one or more streams by certain interface, certain binding of related this interface of some of them stream, and some streams are associated with certain binding of other interfaces;
MN registers one or more streams by certain interface, and some of them stream is associated with the binding of this interface and other interfaces simultaneously;
MN registers one or more streams by certain interface, and all streams are not associated with the binding of any interface, and HA will lose or stores processor corresponding business stream this moment.
The process of MN registration flow (having FID) can be carried out simultaneously with the process of the many bindings of registration (having BID), also can independently carry out.
When the stream on the MN carries out initial registration on described GFA, promptly receive MN when carrying out the request of initial flow registration as GFA, GFA needs go into to binding and go out in binding to upgrade simultaneously, and sends the register requirement that comprises to the information of binding to HA.
The interface IF1 of many interfaces MN that this embodiment provides, interface IF2 to the handling process of GFA registration flow as shown in Figure 6, comprise following treatment step respectively:
Step 61, MN initiate streamer volume request message by interface IF1 to FA.
The interface IF1 of MN in registration binding BID1 or afterwards initiates streamer volume request message to FA, carries the stream option information in this streamer volume request message, comprises traffic identifier FID1 and stream description, and related binding logo BID1 etc.
Step 62, FA send streamer volume request message to GFA.
After FA receives above-mentioned streamer volume request message, preserve the stream option information in the binding of interface IF1 correspondence.Then, send streamer volume request message, carry the stream option information of the IF1 of MN in this streamer volume request message, comprise traffic identifier FID1 and stream description to GFA, and related binding logo BID1 etc.
Going into to binding and going out to binding of step 63, GFA docking port IF1 correspondence sends streamer volume request message to HA.
After GFA receives above-mentioned streamer volume request message, going into of docking port IF1 correspondence to binding and going out to binding to upgrade, going into to binding and going out the stream option information that in binding, increases the interface IF1 of MN, going out in binding, the stream option information of the IF1 of MN is associated with binding logo BIDx
Then, GFA sends streamer volume request message to HA, carries the stream option information of the I F1 of MN in this streamer volume request message.After HA receives above-mentioned streamer volume request message, the stream option information of the IF1 of MN is updated to HA goes up in the corresponding binding of setting up.
Step 64, MN initiate streamer volume request message by interface IF2 to GFA.
The interface IF2 of MN in registration binding BID2 or afterwards directly initiates streamer volume request message to GFA, carries the stream option information of the IF2 of MN in this streamer volume request message, comprises traffic identifier FID2 and stream description, and related binding logo BID2 etc.
Going into to binding and going out to binding of step 65, GFA docking port IF2 correspondence sends streamer volume request message to HA.
After GFA receives the request of above-mentioned streamer volume, going into of docking port IF2 correspondence to binding and going out to binding to upgrade, going into to binding and going out the stream option information that in binding, increases the interface IF2 of MN, and going out in binding, the stream option information of the IF2 of MN is being associated with binding logo BIDx.
Then, GFA sends streamer volume request message to HA, carries the stream option information of the IF2 of MN in this streamer volume request message, comprises traffic identifier FID2 and stream description, and related binding logo BIDx etc.
After HA receives above-mentioned streamer volume request message, the stream option information of the IF2 of MN is updated to HA goes up in the corresponding binding of setting up.
On the basis of the foregoing description two, when between the interface of stream in the visited network at GFA place of MN when mobile, promptly MN flows when switching, and GFA only needs to carry out register update to going into to binding, and does not need to notify HA to carry out register update.
Such as, when the consideration of MN, wish the Business Stream FID1 on the interface IF1 is switched to IF2 for service needed (for example needing higher bandwidth) or load balancing (for example the load of IF1 is overweight at this moment).So the IF2 of MN carries the stream option information of Business Stream FID1 to GFA sending zone login request message in this regional registration request message, comprise traffic identifier FID1 and related binding logo BID1 and other necessary information HoA, GFA-CoA etc. thereof.
After GFA receives the above-mentioned zone login request message, docking port IF1, interface IF2 correspondence go into to binding to upgrade, and do not need docking port IF1, interface IF2 correspondence go out to binding to upgrade.
Preferably, GFA cancels request to the FA sending zone, has the traffic identifier FID1 and/or and the binding logo BID1 of association and the HoA1 of other necessary informations MN etc. that cancel.After GFA finishes dealing with,, finish the process that stream switches to MN sending zone registration reply message.
In actual applications, MN can also send the streamer volume or switch registration to GFA separately.
On the basis of the foregoing description two, when the interface of MN is mobile in the GFA territory, for example, because the load balancing of network (for example the load of FA1 is overweight at this moment), under the interface IF1 of MN moves to FA2 in the GFA territory from the FA1 in the GFA territory, the LCoA (also being FA-CoA or Co-CoA) of MN will change into FA-CoA2 this moment, and MN need be to GFA sending zone login request message.
Concrete processing procedure comprises:
Owing to the reasons such as load balancing of network, network or terminal are the new Care-of Address FA-CoA2 of IF1 announcement of MN under initiating the interface IF1 of MN moved to FA2 in the GFA territory from the FA1 in the GFA territory.
MN carries binding logo BID1 to FA2 sending zone login request message in this regional registration request message, and HoA1, GFA-CoA etc.After FA2 receives the regional registration request message, for MN creates binding.Then, FA2 sends this regional registration request message to GFA insert FA-CoA2 in the regional registration request message after.
After GFA receives the login request message that FA2 sends,, determine the going into of interface IF1 correspondence of MN to binding (it is designated BID1) according to the information of MN.Then, the binding information of going into to binding of docking port IF1 correspondence upgrades, and mainly is that FA-CoA2 is replaced FA-CoA1, and other information of going in binding of docking port IF1 correspondence do not change.Going out to binding of MN do not need to upgrade, and do not need to send register update to HA yet.
Optionally, GFA upgrade above-mentioned IF1 correspondence go into to binding the time or before, message is cancelled in binding to the FA1 sending zone, this binding is cancelled and is carried the binding logo BID1 that cancels and other information HoA1 of MN etc. in the message, and having cause value, the interface IF1 of indication MN switches.
After GFA finishes dealing with, reply the regional registration response message to MN, finish the handoff procedure of interface IF1 by FA2.
Embodiment four
Proxy mode realizes that down FA supports successively/simultaneously mobile application scenarios schematic diagram of registering of many interfaces as shown in Figure 7 in the mobile IPv 4 system that present embodiment provides.
In application scenarios shown in Figure 7, many interfaces MN701 has 3 interface IF1, interface IF2 and interface IF3, networks such as corresponding WiFi, WiMAX, LTE respectively.
Interface I F1, interface IF2 are connected to the visited network at FA702 place simultaneously, use FA-CoA1, register to HA703 by FA.
Interface IF3 is positioned at the visited network at non-FA place, may use Co-CoA3 in other visited network.
MN in above-mentioned application scenarios shown in Figure 7 goes up interface IF1, interface IF2 as shown in Figure 8 by the handling process of FA when HA registers successively, comprises following treatment step:
Step 81, MN send login request message by interface IF1 to FA.
The interface IF1 of MN is attached to network, by the network startup process, finish access authentication after, obtained home address: FA-CoA1.At this moment, MN sends login request message by interface IF1 to FA, carries the binding logo BID1 of promising interface IF1 generation and the information (as security parameter) of HoA, FA-CoA1 and some other register requirement in this login request message.
Step 82, FA are that MN sets up into to binding and going out to binding, transmit login request message to HA.
After FA received above-mentioned login request message, for MN sets up into to binding, this went into the binding information that comprises MN in binding, as HoA, and the link layer information of the interface IF1 of MN, and binding logo BID1 etc.; FA is that MN creates out to binding simultaneously, and this goes out the binding information that comprises the MN request registration in binding, HoA, and FA-CoA1, and newly-generated binding logo BIDy, this moment, value and the binding logo BID1 of BIDy were identical or different.
Then, FA transmits login request message to HA, carries the going out to binding information of MN in this login request message.After HA receives above-mentioned login request message,, set up bidirectional tunnel, so that transmit the message of MN with FA for MN creates binding.
HA returns registration reply message by FA to MN, finishes the registration process of interface IF1.
Step 83, MN send login request message by interface IF2 to FA, and whether the binding information of the IF2 registration of FA inspection MN is consistent with the binding information of IF1 registration.
The interface IF2 of MN is attached to network, by the network startup process, finish access authentication after, obtained home address, FA-CoA1 etc.Then, MN sends login request message by interface IF2 to FA, carries binding logo BID2 and HoA, FA-CoA1 that promising interface IF2 generates in this login request message, and the information (as security parameter) of some other register requirement.
Above-mentioned MN is local login request message or local login request message to the login request message that FA sends.
After FA receives above-mentioned login request message, check that the interface IF1 of MN has registered binding BID1, when the binding BID2 of front port IF2 registration different with it, for the IF2 of MN sets up new going into to binding.Simultaneously, whether the binding information of the IF2 registration of FA inspection MN is consistent with the binding information of IF1 registration, if inconsistent, then execution in step 84.
If the binding information of IF2 registration is consistent with the binding information of IF1 registration, then FA does not need to upgrade going out to binding of MN, does not need to upgrade to HA transmission registration message yet.At this moment, FA returns registration reply message to MN, finishes registration process.Thereby last the going into of setting up of FA to binding:
| Home address | Link-layer identification | Binding logo | Other information |
| ??HoA1 | ??LLID1 | ??BID1 | As: strategy/stream information etc. ... |
| ??HoA1 | ??LLID2 | ??BID2 | ??... |
| ??... | ??... | ??... | ??... |
Go out to binding:
| Home address | Care-of Address | Binding logo | Other information (as stream information) |
| ??HoA1 | ??FA-CoA1 | ??BIDy | As: strategy/stream information etc. ... |
| ??... | ??... | ??... | ??... |
The MN that step 84, FA renewal have been set up goes out to binding, sends the register requirement that carries out to the lastest imformation of binding to HA.
When the binding information of the binding information of IF2 registration and IF1 registration changed, FA upgraded going out to binding of the MN that set up, and the binding information (such as stream information) that IF2 is registered also adds going out to binding of above-mentioned MN to.Then, send the register requirement that carries out to the lastest imformation of binding to HA.
After HA receives above-mentioned register requirement, for MN upgrades to binding.HA returns registration reply message by GFA, FA to MN.Finish the registration process of above-mentioned interface IF2.
Step 85, MN send login request message by interface IF3 to HA, and HA sets up binding for interface IF3.
The interface IF3 of MN is attached to network, by the network startup process, finish access authentication after, obtained home address, Co-CoA3 etc.Then, MN directly sends login request message by interface IF3 to HA, carries binding logo BID3 and HoA, Co-CoA3 that promising interface IF3 generates in this login request message, and some other information (for example security parameter etc.).
Thereby last the binding of setting up of HA:
| Home address | Care-of Address | Binding logo | Other information |
| ??HoA1 | ??FA-CoA1 | ??BIDy | As: strategy/stream information etc. ... |
| ??HoA1 | ??Co-CoA3 | ??BID3 | ??... |
| ??... | ??... | ??... | ??... |
Similarly, FA can support the stream binding in a similar manner and flow switching etc.
In basic mobile IPv 4 system, only support that MN sends registration message by FA to HA, the local registration message that does not still have MN directly to send to FA.In actual applications, can in the mobile IPv 4 system, increase local login request message newly, so that MN initiates local registration to FA, so that many interfaces MN carries out carrying out this locality registration to FA in the processes such as streamer volume and stream switching in the FA territory.
Above-mentioned local login request message is the expansion of the registration message of RFC3344 definition, and except that following field, other fields are identical with the registration message of RFC3344 definition.
Type: type, for example value is 20, indicating this message is local registration message;
Foreign Agent Address, the address of indication FA.
Care-of Address is for FA-CoA or be empty.
Mobility Session Identification, mobile session identification, it is right to be used to identify local register requirement and response message; So that distinguish, and prevent message replay attack.
Expansion is used for follow-up new option or the message field of carrying.
Embodiment five
In order to prevent that the BID that GFA/FA generates from conflicting with the BID that MN uses in non-GFA territory, how the GFA/FA that present embodiment is described proxy mode generates BID.
Mode 1, the embodiment that describes as described above explanation, GFA/FA can adopt first BID of MN registration in the outlet binding, send the login request message that comprises this first BID to HA simultaneously.When MN moved out the visited network at GFA/FA place or nullifies, GFA/FA needed to send updating message to HA again.
0000?MN
0001?FA
0010?GFA
0011?HA
0100～1111 is unallocated.
Based on the application scenarios of the invention described above embodiment two, first network node is GFA, and second network node is HA.The interface IF1 of MN, interface IF2, interface IF3 have set up corresponding binding respectively on GFA, HA.At this moment, because interface moves or factor such as offered load, the related service stream on the interface IF1 will switch to non-GFA territory from the GFA territory; Perhaps, because the factors such as poor signal of interface IF1, interface IF1 exits network.
In this case, GFA mainly comprises the processing procedure that BID upgrades:
First network node (GFA) detects the BID1 attachment removal of the interface IF1 correspondence of MN, so upgrade the going out to binding of MN, with the sign from the binding BID2 of interface IF2 to binding of going out as MN, deletes HoA1 simultaneously, the going into to binding of BID1 correspondence.
Above-mentioned first network node detect MN interface IF1 correspondence BID1 the method for attachment removal include but not limited to following several:
MN has sent the login request message of lifetime=0 by interface IF1 to first network node, represents the BID1 attachment removal of interface IF1 correspondence.
MN sends login request message to HA (second network node), carries HoA1 in this login request message, Co-CoA5, and the binding BID1 information of interface IF1.The information that the interface IF1 of HA renewal MN binds BID1 accordingly.Send binding to first network node then and cancel request message, the HoA1 that carries MN in the request message is cancelled in this binding, GFA-CoA, the binding BID1 information of cancelling etc.
Second network node sends login request message to HA, carries the sign of MN in this login request message, HoA1, GFA-CoA and new binding logo BID2.Thereby create the relevant binding of BID2 on the HA again.
Embodiment six
In this embodiment, when GFA/FA receives a plurality of register requirement of having carried BID that send over by different interfaces, GFA/FA sets up corresponding binding respectively for each interface.Then, GFA/FA is transmitted to HA with above-mentioned a plurality of register requirement, simultaneously adds specific indication information in each register requirement, so that HA distinguishes register requirement from distinct interface according to this indication information, and can set up binding respectively for different register requirement.
With respect to the foregoing description 1-5, relatively simple during the request of the many bindings of foundation of the GFA/FA processing MN among this embodiment, the binding of setting up each interface registration gets final product, and does not also promptly need to distinguish to binding and going into to binding; Then, GFA/FA (comprises many binding registrations with all registration messages, the streamer volume, interface switches, registration messages such as stream switching) all pass through HA, add specific indication information in each register requirement simultaneously,, and can set up binding respectively for different register requirement so that HA distinguishes each register requirement that HoA is identical with CoA, BID is different from distinct interface according to this indication information.
First network node is GFA/FA, and second network node is HA, and the GFA/FA that this embodiment provides comprises following treatment step to the foundation of the MN processing of request flow processs of binding as shown in Figure 9:
Step 91, MN sends login request message by interface IF1 to first network node.
The interface IF1 of MN is attached to network, by the network startup process, finish access authentication after, obtain HoA1, CoA1 address information etc.Then, MN sends login request message by interface IF1 to first network node, carries the binding logo BID1 of promising interface IF1 generation and the information (as security parameter) of HoA, CoA1 and some other register requirement in this login request message.
If the mobile IPv 4 system, then CoA1 is FA-CoA or Co-CoA, and register requirement is the local registration message; If hierarchical mobile IP v4 system, then CoA1 information comprises GFA-CoA and local LCoA (LCoA is FA-CoA or Co-CoA), and register requirement is local registration message or regional registration message.
Step 92, first network node are that the interface IF1 of MN sets up binding, send the login request message of the identification information that has carried interface IF1 to second network node.
After first network node is received above-mentioned login request message, check whether described interface IF1 registers on described first network node, if then described first network node is that described interface to be registered upgrades binding; Otherwise, for the interface IF1 of MN sets up binding, comprise the binding information HoA1 of MN, CoA1, and binding logo BID1 etc.
Then, first network node sends login request message to second network node, carry the binding information of the interface IF1 of MN in this login request message, increase simultaneously the identification information of interface IF1 in the binding logo option, the identification information of above-mentioned interface IF1 comprises and is used to indicate the indication information of interface IF1 registration or the link-layer identification of interface IF1.
With classification MIPv4 is example, can expand an indicating bit in the binding logo option, represents that by this indicating bit this is that GFA is many binding registrations that the interface IF1 of MN carries out in the hierarchical mobile IP system.
In actual applications, can also in the login request message that sends to HA, insert the link-layer identification of the interface IF1 of MN by first network node.Because the link-layer identification of each interface of MN is different, thereby HA can distinguish different bindings according to the link-layer identification of this interface.
After second network node is received above-mentioned login request message, search the existing binding of MN according to sign, HoA, the BID etc. of MN, and mate, be defined as new binding this moment, thereby bind for MN creates.
Alternatively, before setting up binding, second network node is to (the HoA of MN, CoA) and the specific indication information in the register requirement (as the indicating bit in the above-mentioned binding logo option, the link-layer identification of interface etc.) carry out the uniqueness inspection together, if all identical, then refuse this register requirement, reply the response message of failure; Otherwise accept this register requirement, further handle.After finishing dealing with, set up bidirectional tunnel, so that transmit the message of MN with first network node.At this moment, second network node returns registration reply message by first network node to MN, finishes registration process.
First network node carries out above-mentioned and the corresponding treatment step of interface IF1 when the login request message that follow-up interface IF2, the interface IF3 that receives MN sends too.
The device that the embodiment of the invention also provides a kind of multiple interface mobile node to carry out mobile IP registration, this device are first network node, and its structural representation comprises as shown in figure 10 as lower module:
Register requirement receiver module 101 is used to receive first register requirement that mobile node sends, and carries first binding logo of interface to be registered in described first register requirement;
Register requirement processing module 102, be used for according to described first register requirement, and when not having the log-on message of other interface on the described mobile node on described first network node, send second register requirement to second network node, carry in described second register requirement to second binding logo of described mobile node distribution or the interface identifier information of described interface to be registered.Above-mentioned interface identifier information comprises and is used in reference to the indication information that shows interface registration or the link-layer identification of interface.
Described register requirement processing module 102, specifically be used for and when not having the log-on message of other interface on the described mobile node on described first network node, set up for described interface to be registered and to comprise going into to binding and comprising described the going out to binding of second binding logo that described mobile node distributes of giving of described first binding logo, described second binding logo and described first binding logo are identical or different; Send second register requirement of carrying second binding logo that distributes to described mobile node to described second network node.
Described register requirement processing module 102 can also comprise: at least one item in first processing module 1021 and second processing module 1022, wherein,
First processing module 1021 is used for when described mobile node has the interface log-on message on described device, for described interface foundation to be registered comprises going into to binding of described first binding logo;
Second processing module 1022 is used to check whether described interface to be registered is registered on described device, if, for described interface to be registered upgrades binding; Otherwise, for described interface to be registered is set up binding; Send second register requirement of the interface identifier information of carrying described interface to be registered to described second network node.
Described first network node can be the gateway external agent, and described second network node is a home agent; Perhaps, described first network node is the external agent, and described second network node is home agent or gateway external agent.
Such as, in above-mentioned hierarchical mobile IP v4 system shown in Figure 3, first network node is GFA/FA, second network node is HA.
The concrete processing procedure of above-mentioned register requirement processing module mainly comprises: after the register requirement receiver module receives above-mentioned first register requirement, when the register requirement processing module was checked the log-on message that does not have other interface on the described mobile node on first network node, promptly this first register requirement was first register requirement that mobile node sends to first network node.
So above-mentioned register requirement processing module sends second register requirement to second network node, carry in described second register requirement to second binding logo of described mobile node distribution or the interface identifier information of described interface to be registered.
Further, above-mentioned register requirement processing module specifically comprises to the process that described second network node sends second register requirement:
Above-mentioned register requirement processing module is that described interface to be registered is set up and comprised going into to binding and comprising described the going out to binding of second binding logo that described mobile node distributes of giving of described first binding logo.In Fig. 3, above-mentionedly go out to binding to represent that with MN binding X above-mentioned to go out to binding be that the total interface of mobile node is shared, the above-mentioned binding information that goes out to comprise the mobile node request registration in binding.Described second binding logo and described first binding logo are identical or different.
Described register requirement processing module sends second register requirement of carrying second binding logo that distributes to described mobile node to described second network node.
Afterwards, when other interface that passes through of above-mentioned mobile node sends register requirement to described first network node, when carrying the binding logo of other interface in this register requirement.Because above-mentioned interface to be registered is registered to above-mentioned first network node, above-mentioned first network node is checked through described mobile node has the interface log-on message on described first network node, so described first network node is that described other interface is set up going into to binding of the binding logo that comprises described other interface.Set up out to binding for this other interface, do not send second register requirement yet to described second network node.
Further, in described first register requirement, also comprise: the information of the stream on the described mobile node, and, when this stream carries out initial registration on described first network node, described first network node sends second register requirement to second network node, and described second register requirement carries the stream information on the described mobile node.
When switching between the interface of the stream on the mobile node in the visited network at the described first network node place, mobile node switches registration, this moment, described first network node only upgraded in going into to binding of correspondence, the content that goes out to binding does not change, do not upgrade going out to binding, described first network node does not send register requirement to second network node;
When the interface on the mobile node is mobile in the visited network at the described first network node place, change has taken place in the CoA on the interface, mobile node switches registration, this moment, described first network node only upgraded in going into to binding of correspondence, the content that goes out to binding does not change, do not upgrade going out to binding, described first network node is not initiated register update to described second network node;
When the stream on the mobile node or interface are being striden between the interface of visited network at the described first network node place when mobile, mobile node switches registration, this moment, described first network node upgraded in going into to binding of correspondence, go out to the content of binding also to upgrade simultaneously, need upgrade going out to binding, described first network node is initiated register update to described second network node.If stream switches on the overseas interface of described first network node or interface to move to described first network node overseas, then described first network node is deleted the stream information in this binding or is deleted the binding of this interface correspondence.
The embodiment of the invention also provides a kind of device of regional mobile IP registration, is applied to mobile node in the territory at described device place to the situation of this device sending zone register requirement, and its structural representation comprises as shown in figure 11 as lower module:
Regional registration request receiver module 111 is used to receive the regional registration request that mobile node sends, and carries the binding logo of interface to be registered in the described register requirement, the register requirement in the territory that described regional registration request is the described first network node place.
Module 112 is set up in binding, is used for creating or upgrade the binding clauses and subclauses of described mobile node according to the received register requirement of described regional registration request receiver module.
Can also carry flow identification information in the described regional registration request.
Described device can also comprise:
Zone de-registration request processing module 113 is used for the regional de-registration request to the mobile node transmission, carries binding logo information or flow identification information in the described regional de-registration request.
Described device can be gateway external agent or external agent.
The embodiment of the invention also provides a kind of system of mobile IP registration, it is characterized in that, comprising:
First network node is used to receive first register requirement that mobile node sends, and carries first binding logo of interface to be registered in described first register requirement; According to described first register requirement, and when not having the log-on message of other interface on the described mobile node on described first network node, send second register requirement to second network node, carry in described second register requirement to second binding logo of described mobile node distribution or the interface identifier information of described interface to be registered.
Second network node is used to receive second register requirement that described first network node sends, and according to the interface identifier information of second binding logo that carries in described second register requirement or described interface to be registered, described mobile node is registered.
Described first network node is the gateway external agent, and described second network node is a home agent;
Perhaps,
Described first network node is the external agent, and described second network node is home agent or gateway external agent.
Such as, in networking schematic diagram shown in Figure 7, first network node is the external agent, second network node is a home agent.
The concrete processing procedure of above-mentioned first network node mainly comprises:
After first network node receives above-mentioned first register requirement, when first network node was checked the log-on message that does not have other interface on the described mobile node on first network node, promptly this first register requirement was first register requirement that mobile node sends to first network node.So above-mentioned first network node is that described interface to be registered is set up and comprised going into to binding and comprising described the going out to binding of second binding logo that described mobile node distributes of giving of described first binding logo.Then, send second register requirement, carry in described second register requirement to second binding logo of described mobile node distribution or the interface identifier information of described interface to be registered to second network node.
The concrete processing procedure of above-mentioned second network node mainly comprises: after second network node is received above-mentioned second register requirement, interface identifier information according to second binding logo that carries in described second register requirement or described interface to be registered, described mobile node is registered, for mobile node is created binding, set up bidirectional tunnel with first network node, so that transmit the message of this mobile node.Then, second network node returns registration reply message by first network node to mobile node, finishes the registration process of the interface to be registered of above-mentioned mobile node.
In sum, the embodiment of the invention provides into binding to binding and going out to the classification of binding to MN by the GFA/FA in the classification MIPv4 system (MIPv4 system), when a plurality of interfaces that guaranteed MN can successively adhere to the network that is registered to the GFA/FA place, thereby can make MN obtain more bandwidth, the already-existing session of MN can be continued.
Switch or interface when switching when MN flows in the territory at GFA/FA place, can only upgrade going into of MN, and do not upgrade the going out of MN, save the time-delay that stream switches or interface switches, reduced the signaling traffic load of network to binding to binding.
By newly-increased local login request message in the mobile IPv 4 system, can make many interfaces MN in the FA territory, carry out carrying out this locality registration to FA in the processes such as streamer volume and stream switching.
One of ordinary skill in the art will appreciate that all or part of flow process that realizes in the foregoing description method, be to instruct relevant hardware to finish by computer program, described program can be stored in the computer read/write memory medium, this program can comprise the flow process as the embodiment of above-mentioned each side method when carrying out.Wherein, described storage medium can be magnetic disc, CD, read-only storage memory body (Read-Only Memory, ROM) or at random store memory body (Random Access Memory, RAM) etc.
The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claim.
Claims (17)
1. the method for a mobile IP registration is characterized in that, comprising:
First network node receives first register requirement that mobile node sends, and carries first binding logo of interface to be registered in described first register requirement;
According to described first register requirement, and when not having the log-on message of other interface on the described mobile node on described first network node, described first network node sends second register requirement to second network node, carries in described second register requirement to second binding logo of described mobile node distribution or the interface identifier information of described interface to be registered.
2. the method for mobile IP registration according to claim 1 is characterized in that, described first network node specifically comprises to the step that described second network node sends second register requirement:
Described first network node is that described interface to be registered is set up and comprised going into to binding and comprising described the going out to binding of second binding logo that described mobile node distributes of giving of described first binding logo, and described second binding logo and described first binding logo are identical or different;
Described first network node sends second register requirement of carrying second binding logo that distributes to described mobile node to described second network node.
3. the method for mobile IP registration according to claim 1 is characterized in that, described method also comprises:
When described mobile node had the log-on message of other interface on described first network node, described first network node was that described interface foundation to be registered comprises going into to binding of described first binding logo.
4. the method for mobile IP registration according to claim 1 is characterized in that, when also comprising the information of the stream on the described mobile node in described first register requirement, described method also comprises:
When the stream on the described mobile node carries out initial registration on described first network node, described first network node sends second register requirement to second network node, and described second register requirement carries the stream information on the described mobile node.
5. the method for mobile IP registration according to claim 1 is characterized in that, described method also comprises:
Check whether described interface to be registered is registered on described first network node, if then described first network node is that described interface to be registered upgrades binding; Otherwise described first network node is that described interface to be registered is set up binding;
Described first network node sends the register requirement of the interface identifier information of carrying described interface to be registered to described second network node.
6. according to the method for each described mobile IP registration of claim 1 to 5, it is characterized in that: described first network node is the gateway external agent, and described second network node is a home agent;
Perhaps,
Described first network node is the external agent, and described second network node is home agent or gateway external agent.
7. an IP process registration is characterized in that, comprising:
First network node receives the regional registration request that mobile node sends, and carries the binding logo of interface to be registered in the described regional registration request, the register requirement in the territory that described regional registration request is the described first network node place;
According to described regional registration request, create or upgrade the binding clauses and subclauses of described mobile node.
8. IP process registration according to claim 7 is characterized in that, also carries flow identification information in the described regional registration request.
9. according to claim 7 or 8 described IP process registration, it is characterized in that described method also comprises:
Regional de-registration request to mobile node sends carries binding logo information and/or flow identification information in the described regional de-registration request.
10. the device of a mobile IP registration is characterized in that, comprising:
The register requirement receiver module is used to receive first register requirement that mobile node sends, and carries first binding logo of interface to be registered in described first register requirement;
The register requirement processing module, be used for according to described first register requirement, and when not having the log-on message of other interface on the described mobile node on the described device, send second register requirement to second network node, carry in described second register requirement to second binding logo of described mobile node distribution or the interface identifier information of described interface to be registered.
11. the device of mobile IP registration according to claim 10 is characterized in that:
Described device is gateway external agent or external agent.
12. the device according to claim 10 or 11 described mobile IP registrations is characterized in that:
Described register requirement processing module, specifically be used to described interface to be registered to set up to comprise going into to binding and comprising described the going out to binding of second binding logo that described mobile node distributes of giving of described first binding logo, described second binding logo and described first binding logo are identical or different; Send second register requirement of carrying second binding logo that distributes to described mobile node to described second network node.
13. the device according to claim 10 or 11 described mobile IP registrations is characterized in that, described register requirement processing module also comprises: at least one item in first processing module and second processing module, wherein,
First processing module is used for when described mobile node has the interface log-on message on described device, for described interface foundation to be registered comprises going into to binding of described first binding logo;
Second processing module is used to check whether described interface to be registered is registered on described device, if, for described interface to be registered upgrades binding; Otherwise, for described interface to be registered is set up binding; Send second register requirement of the interface identifier information of carrying described interface to be registered to described second network node.
14. the device of an IP registration is characterized in that, comprising:
Regional registration request receiver module is used to receive the regional registration request that mobile node sends, and carries the binding logo of interface to be registered in the described register requirement, the register requirement in the territory that described regional registration request is the described first network node place;
Module is set up in binding, is used for creating or upgrade the binding clauses and subclauses of described mobile node according to the received register requirement of described regional registration request receiver module.
15. the device of IP registration according to claim 14 is characterized in that described device also comprises:
Zone de-registration request processing module is used for the regional de-registration request to the mobile node transmission, carries binding logo information or flow identification information in the described regional de-registration request.
16. the system of a mobile IP registration is characterized in that, comprising:
First network node is used to receive first register requirement that mobile node sends, and carries first binding logo of interface to be registered in described first register requirement; According to described first register requirement, and when not having the log-on message of other interface on the described mobile node on described first network node, send second register requirement to second network node, carry in described second register requirement to second binding logo of described mobile node distribution or the interface identifier information of described interface to be registered;
Second network node is used to receive second register requirement that described first network node sends, and according to the interface identifier information of second binding logo that carries in described second register requirement or described interface to be registered, described mobile node is registered.
17. the system of mobile IP registration according to claim 16 is characterized in that:
Described first network node is the gateway external agent, and described second network node is a home agent;
Perhaps,
Described first network node is the external agent, and described second network node is home agent or gateway external agent.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910136545.4A CN101883351B (en) | 2009-05-06 | 2009-05-06 | Method and device for registering mobile IP |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910136545.4A CN101883351B (en) | 2009-05-06 | 2009-05-06 | Method and device for registering mobile IP |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101883351A true CN101883351A (en) | 2010-11-10 |
| CN101883351B CN101883351B (en) | 2014-11-05 |
Family
ID=43055204
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910136545.4A Expired - Fee Related CN101883351B (en) | 2009-05-06 | 2009-05-06 | Method and device for registering mobile IP |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101883351B (en) |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3713264A1 (en) * | 2005-03-31 | 2020-09-23 | Sun Patent Trust | Communication control method, communication node, and mobile node |
| CN101083613A (en) * | 2006-06-01 | 2007-12-05 | 华为技术有限公司 | Mobile terminal network registering method, HA and HoA distribution method and system |
| CN101237394B (en) * | 2007-01-31 | 2012-11-21 | 华为技术有限公司 | Method and system for anchor point device to process multi-interface mobile station report |
-
2009
- 2009-05-06 CN CN200910136545.4A patent/CN101883351B/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CN101883351B (en) | 2014-11-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103947235B (en) | Gateway function for mobile-relay system | |
| US8155041B2 (en) | Method for handover between heterogeneous networks using link trigger signal in multi-interface mobile router | |
| CN101127652B (en) | A method, device and system for identifying access anchor of user terminal to external network | |
| US8379573B2 (en) | Apparatus and method for network mobility management in proxy mobile IPv6 network | |
| CN101501675B (en) | System and method for routing and domain name system support of a mobile node | |
| US20080175201A1 (en) | Systems and methods for using internet mobility protocols with non internet mobility protocols | |
| CN102202286B (en) | Method for terminal access in heterogeneous network, and method and equipment for heterogeneous network switching | |
| CN101534501B (en) | Method, system and equipment for registering local mobile anchor point | |
| CN101897157A (en) | Address allocation method, address allocation system, mobile node, and proxy node | |
| Balfaqih et al. | Fast handover solution for network-based distributed mobility management in intelligent transportation systems | |
| CN101848454B (en) | Method for assigning prefix, network system and local mobile anchor point | |
| CN102118733A (en) | Method and equipment for processing request of SMSonly function of user equipment | |
| CN101594609A (en) | When not switching between same area, keep continuous method, system and the node of session | |
| CN101697615B (en) | Network management server, mobile node and access node | |
| US20100014464A1 (en) | Communication method, communication system, home agent, and mobile node | |
| US20100316035A1 (en) | Position information management device, network edge device, and mobile terminal | |
| JP5121107B2 (en) | Parallel core network for GSM / UMTS | |
| JP4485727B2 (en) | Core network allocation for GSM / UMTS | |
| CN101771991B (en) | Method for controlling position update and terminal | |
| CN100596242C (en) | Method, system and anchor point equipment for forwarding message | |
| CN101883351B (en) | Method and device for registering mobile IP | |
| CN101400122B (en) | Method, apparatus and system for managing user equipment | |
| CN101453727A (en) | Method, system for combined registering, packet exchange domain network side equipment | |
| US20120163337A1 (en) | Method of allocating home network prefix, inter-handoff method, and multi-homing system thereof | |
| KR100927940B1 (en) | Location registration method and packet forwarding method using SRM in mobile network |
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 | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20170630 Address after: 510640 Guangdong City, Tianhe District Province, No. five, road, public education building, unit 371-1, unit 2401 Patentee after: Guangdong Gaohang Intellectual Property Operation Co., Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: Huawei Technologies Co., Ltd. |
|
| CB03 | Change of inventor or designer information |
Inventor after: Zhao Heqi Inventor before: Wang Yungui Inventor before: Wu Qin Inventor before: Gong Xiaoyu |
|
| CB03 | Change of inventor or designer information | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20170913 Address after: 063000 Leting Tangshan City County, Hebei Province town of Leting Hongguang Hongguang community building 52 floor 3 No. 23102 Patentee after: Zhao Heqi Address before: 510640 Guangdong City, Tianhe District Province, No. five, road, public education building, unit 371-1, unit 2401 Patentee before: Guangdong Gaohang Intellectual Property Operation Co., Ltd. |
|
| TR01 | Transfer of patent right | ||
| 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: 20141105 Termination date: 20180506 |