CN101883351B

CN101883351B - Method and device for registering mobile IP

Info

Publication number: CN101883351B
Application number: CN200910136545.4A
Authority: CN
Inventors: 王云贵; 吴钦; 宫小玉
Original assignee: Huawei Technologies Co Ltd
Priority date: 2009-05-06
Filing date: 2009-05-06
Publication date: 2014-11-05
Anticipated expiration: 2029-05-06
Also published as: CN101883351A

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

The method and apparatus of mobile IP registration

Technical field

The present invention relates to network communications technology field, relate in particular to a kind of many interfaces MN (MobileNode, mobile node) and carry out the method and apparatus of mobile IP registration.

Background technology

The structural representation of existing mobile IPv 4 system as shown in Figure 1, comprise as lower unit: MN, CN (Correspondent Node, peer node), FA (Foreign Agent, external agent) and HA (Home Agent, home agent).Wherein,

MN: be terminal or the router with locomotive function.In the time that MN moves to another network or subnet from a network or subnet, its attachment point also changes at any time, and change has occurred 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: with the node that MN communicates, be a mobile node or fixed network node.

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 provides the router of mobile management and routing service for MN.

The general work mechanism of mobile IPv 4 system comprises: mobile registration process and data forwarding process.

Hierarchical mobile IP v4 system is expanded and is formed on the basis of mobile IPv 4, has increased network entity a: GFA (Gateway Foreign Agent, gateway external agent) in hierarchical mobile IP v4 system newly.GFA has the function of FA, uses GFA-CoA (Care-ofAddress, Care-of Address) in the time that it provides routing service.In hierarchical mobile IP system, the Co-CoA of mobile IP system and FA-CoA are referred to as to 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, when difference is that MN registers to HA, also need through GFA, on GFA, will set up the binding of MN, comprise the HoA of MN, LCoA and GFA-CoA etc.GFA forwards when registration message to HA, LCoA is removed from registration message, thereby the upper bind package of setting up of HA contains is HoA, GFA-CoA address.On data retransmission face, between GFA and HA, set up bidirectional tunnel, for the data service of MN provides route.

Meanwhile, in hierarchical mobile IP v4 system, in the time that MN moves in the visited network at GFA place, increased regional registration message newly, MN only need to carry out regional registration to GFA, and GFA does not need to be updated to HA, thereby can save MN and move the time delay of switching.

The process that a kind of many interfaces MN of the prior art carries out mobile IPv 4 registration mainly comprises: many interfaces MN obtains a HoA, when the different interface of this MN passes through respectively WiFi (WirelessFidelity, Wireless Fidelity), WiMAX (Worldwide Interoperability for Microwave Access, be micro-wave access global inter communication) etc. after heterogeneous networks access, on each interface, obtain different CoA, initiate mobile registration to HA respectively by different interfaces, thereby set up many tunnels, these many tunnels can make MN obtain more bandwidth.

The HoA of above-mentioned MN and multiple CoA are bound.Move in registration at MN, in order to distinguish different CoA on MN, HA, many interfaces MN, in the time of registration, need to be unique BID of each interface assignment (Binding Identifier, binding logo).Thereby after the CoA of certain interface of MN changes, while moving registration to HA, HA can identify according to the BID of this interface.

Above-mentioned MN is that different business stream distributes FID (Flow Identifier, traffic identifier), and each FID is associated with different BID, and by stream registration process, sets up not homogeneous turbulence binding on HA.Thereby, in the time that HA receives that CN is sent to the Business Stream of MN, can distinguish according to stream binding, then index different binding BID, also can this service route MN be forwarded by different tunnels.

Realizing in process of the present invention, inventor finds that in prior art, at least there are the following problems:

1, carry out in the process of Mobile IP V4 registration at many interfaces MN, do not relate to the scene of hierarchical mobile IP v4, in the time that MN moves to the visited network at GFA place, if GFA does not support many interfaces of MN to move registration simultaneously, MN can only move registration with an interface, thereby can cause the already-existing session of MN not continue, or can not obtain more bandwidth, and quality of service declines.

2,, in the time that multiple interfaces of MN are set up multiple binding by same FA to HA, FA needs to forward registration request to HA for each interface, thereby has increased registration 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 to realize multiple interfaces of MN.

A method for mobile IP registration, comprising:

First network node receives the first registration request that mobile node sends, and carries the first binding logo of interface to be registered in described the first registration request;

According to described the first registration request, and in the time there is no the log-on message of other interface on described mobile node on described first network node, described first network node sends the second registration request to second network node, carries to the second binding logo of described mobile node distribution or the interface identifier information of described interface to be registered in described the second registration request.

A method for IP registration, comprising:

First network node receives the regional registration request that mobile node sends, and carries the binding logo of interface to be registered in described regional registration request, and described regional registration request is the registration request in the territory at described first network node place;

According to described regional registration request, create or upgrade the binding entry of described mobile node.

A device for mobile IP registration, comprising:

Registration request receiver module, for receiving the first registration request of mobile node transmission, carries the first binding logo of interface to be registered in described the first registration request;

Registration request processing module, be used for according to described the first registration request, and in the time there is no the log-on message of other interface on described mobile node on described device, send the second registration request to second network node, in described the second registration request, carry to the second binding logo of described mobile node distribution or the interface identifier information of described interface to be registered.

A device for IP registration, comprising:

Regional registration request receiving module, the regional registration request sending for receiving mobile node, carries the binding logo of interface to be registered in described registration request, and described regional registration request is the registration request in the territory at described first network node place;

Module is set up in binding, for according to the received registration request of described regional registration request receiving module, creates or upgrade the binding entry of described mobile node.

A system for mobile IP registration, comprising:

First network node, for receiving the first registration request of mobile node transmission, carries the first binding logo of interface to be registered in described the first registration request; According to described the first registration request, and in the time there is no the log-on message of other interface on described mobile node on described first network node, send the second registration request to second network node, in described the second registration request, carry to the second binding logo of described mobile node distribution or the interface identifier information of described interface to be registered.

Second network node, the second registration request sending for receiving described first network node, according to the interface identifier information of the second binding logo carrying in described the second registration request or described interface to be registered, registers described mobile node.

The technical scheme being provided by the embodiment of the invention described above can be found out, the embodiment of the present invention is the log-on message on first network node by the interface on first network node the basis registration request and the MN that receive, set up binding to the interface to be registered of MN, and judge whether to send the second registration request to second network node, multiple interfaces of having realized MN can successively be registered to hierarchical mobile IP system, and can reduce the signaling traffic load of hierarchical mobile IP system.

Brief description of the drawings

In order to be illustrated more clearly in the technical scheme of the embodiment of the present invention, below the accompanying drawing of required use during embodiment is described is briefly described, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.

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 present invention one;

The structural representation of a kind of hierarchical mobile IP v4 system that Fig. 3 provides for the embodiment of the present invention one;

Fig. 4 is the application scenarios schematic diagram of the embodiment of the present invention two;

Process chart when the interface IF1 as MN, the interface IF2 that Fig. 5 provides for the embodiment of the present invention two successively registers to HA by GFA;

Interface IF1, the interface IF2 of many interfaces MN that Fig. 6 provides for the embodiment of the present invention three is respectively to the process chart of GFA registration flow;

In the mobile IPv 4 system that Fig. 7 provides for the embodiment of the present invention four, under proxy mode, realize FA support many interfaces successively/the application scenarios schematic diagrames of mobile registration simultaneously;

Process chart when MN upper interface IF1, the interface IF2 that Fig. 8 provides for the embodiment of the present invention four successively registers to HA by FA;

The process chart of the requests that the GFA/FA that Fig. 9 provides for the embodiment of the present invention six binds the foundation of MN more;

A kind of multiple interface mobile node that Figure 10 provides for the embodiment of the present invention carries out the structural representation of the device of mobile IP registration;

The structural representation of the device of a kind of region mobile IP registration that Figure 11 provides for the embodiment of the present invention.

Embodiment

In embodiments of the present invention, the Foreign Agent of mobile node or gateway Foreign Agent are receiving after the registration request that mobile node sends respectively by different interfaces, between each interface of described Foreign Agent or gateway Foreign Agent and described mobile node, set up respectively into binding, the total interface of described mobile node is set up going out to binding between public and home agent.

For ease of the understanding to the embodiment of the present invention, be further explained explanation below in conjunction with accompanying drawing as an example of several specific embodiments example, and each embodiment does not form the restriction to the embodiment of the present invention.

Embodiment mono-

The handling process of the method for a kind of mobile IP registration that this embodiment provides as shown in Figure 2, comprises following treatment step:

Step 21, first network node receive the first registration request that mobile node sends by interface to be registered.

In this embodiment, first, first network node receives the first registration request that mobile node sends by interface to be registered, carries the first binding logo of interface to be registered in described the first registration request.

Such as, in the hierarchical mobile IP v4 system shown in Fig. 3, first network node is GFA/FA.Mobile node sends the first registration request by interface 1 to GFA/FA, carries the first binding logo of interface 1 in this first registration request.

Step 22, first network node are according to described the first registration request, and in the time there is no the log-on message of other interface on described mobile node on described first network node, described first network node sends the second registration request to second network node.

Be specially: first network node receives after above-mentioned the first registration request, while thering is no the log-on message of other interface on described mobile node on inspection first network node, above-mentioned the first registration request sending by interface 1 is first registration request that mobile node sends to GFA/FA.

So above-mentioned first network node sends the second registration request to second network node, in described the second registration request, carry to the 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 the hierarchical mobile IP v4 system shown in above-mentioned Fig. 3, second network node is HA.

Further, the process that first network node sends the second registration request to described second network node specifically comprises:

Described first network node is that described interface to be registered (being interface 1) is set up and comprised entering to binding and comprising the going out to binding of described the second binding logo distributing to described mobile node of described the first binding logo.In Fig. 3, above-mentionedly go out to represent with MN binding X to binding, above-mentionedly go out to be total interface from mobile node to binding shares, above-mentioned go out to the binding information that comprises mobile node request registration in binding.Described the second binding logo and described the first binding logo are identical or different.

Described first network node sends the second registration request that carries the second binding logo distributing 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 registration request to described first network node, while carrying the binding logo of other interface in this registration request.Because interface 1 is registered to above-mentioned first network node, above-mentioned first network node is checked through described mobile node has interface log-on message on described first network node, so described first network node is that described other interface is set up entering to binding of the binding logo that comprises described other interface.Set up out to binding to this other interface, do not send the second registration request to described second network node yet.

Further, when also comprising in described the first registration request: the information of the stream on described mobile node, and, when this stream carries out initial registration on described first network node, described first network node sends the second registration request to second network node, and described the second registration request carries the stream information on described mobile node.

In the time switching between the interface of the stream on MN in the visited network at GFA/FA place, MN switches registration, and now GFA/FA only upgrades in entering to binding of correspondence, goes out to the content of binding and does not change, do not upgrade going out to binding, GFA/FA does not send registration request to HA;

In the time that the interface on MN moves in the visited network at GFA/FA place, there is change in the CoA on interface, MN switches registration, now GFA/FA only upgrades in entering to binding of correspondence, go out to the content of binding and do not change, do not upgrade going out to binding, GFA/FA does not initiate register update to HA;

In the time that the stream on MN or interface move between the interface of the visited network across GFA/FA place, MN switches registration, now GFA/FA upgrades in entering to binding of correspondence, go out to the content of binding and also upgrade simultaneously, need to upgrade going out to binding, GFA/FA initiates register update to HA.If stream is switched on the overseas interface of GFA/FA or interface to move to GFA/FA overseas, GFA/FA deletes the stream information in this binding or deletes the binding that this interface is corresponding.

Embodiment bis-

The present embodiment is described GFA in hierarchical mobile IP v4 system and is supported many interfaces of MN successively to move the method for registration, and the application scenarios schematic diagram of this embodiment as shown in Figure 4.

In the scene shown in Fig. 4, many interfaces MN401 has 3 interface IF1, interface IF2 and interface IF3, respectively corresponding different 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 (Care-of Address coexists), 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 application scenarios shown in above-mentioned Fig. 4, the handling process in the time that interface IF1, the interface IF2 of above-mentioned MN successively register to HA by GFA as shown in Figure 5, comprises 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 network startup process, completes after access authentication, has obtained the 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 registration request (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, the information such as CoA, BID1 in this binding.FA inserts after FA-CoA1 address information in above-mentioned login request message, sends this login request message to GFA.

Step 53, GFA send registration request to HA, and HA returns to registration reply to GFA.

GFA receives after the login request message that above-mentioned FA sends, and determines it is that the interface IF1 of MN is registering.

First GFA sets up for the interface IF1 of MN the entering to binding of binding logo that comprises interface IF1, and this enters to the HoA that comprises MN in binding, the information such as FA-CoA1, BID1, and security parameter, stream information etc.;

Secondly for MN sets up out to binding, this goes out to other information such as HoA, GFA-CoA that comprise newly-generated binding logo BIDx and MN in binding, and and enter to the mapped identification information between binding etc.The value of above-mentioned BIDx is identical or different with the BID1 in the login request message receiving.

Then, GFA sends registration request to HA, and this registration request comprises HoA, the GFA-CoA of MN, and the information such as new binding logo BIDx.HA receives after above-mentioned registration request, for MN creates binding, sets up bidirectional tunnel with GFA, to forward the message of MN.

HA returns to registration reply message by GFA, FA to MN, completes 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 network startup process, completes after access authentication, has obtained home address, GFA-CoA, the information such as Co-CoA2.Then, MN directly sends login request message by interface IF2 to GFA, in this login request message, carry the binding logo BID2 that promising interface IF2 generates, HoA, GFA-CoA, and HFA (Hirarchinal Foreign Agent, graded external agency) scaling option (comprising Co-CoA2), and the information of some other registration request (as security parameter).

The login request message that above-mentioned MN sends to GFA is local login request message or regional registration request message.GFA receives after above-mentioned registration request, determines the registered binding of the interface IF1 BID1 of MN, when the binding BID2 of front port IF2 registration is different with it, is therefore that the interface IF2 of MN sets up new entering to binding.

Meanwhile, 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, performs step 55; If consistent, do not need to upgrade going out to binding of MN, now, the entering to binding of the upper foundation of GFA:

Home address	Care-of Address	Binding logo	Other information
				HoA1	FA-CoA1	BID1	As: strategy/stream information etc. ...
HoA1	Co-CoA2	BID2	...
				...	...	...	...

Upper the going out to binding of setting up of GFA:

Home address	Care-of Address	Binding logo	Other information (as stream information)
				HoA1	GFA-CoA	BIDx	As: strategy/stream information etc. ...
...	...	...	...

Now, GFA does not need to send registration request to HA, and GFA returns to registration reply message to MN.Complete the registration process of above-mentioned interface IF2.

Step 55, GFA upgrade going out to binding of the MN that set up, send the registration request carrying out to the lastest imformation of binding to HA.

When the binding information of IF2 registration of MN and the binding information of IF1 registration are when inconsistent, GFA upgrades 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 in binding of above-mentioned MN to.Then, send to HA the registration request carrying out to the lastest imformation of binding.

HA receives after above-mentioned registration request, for MN upgrades binding.HA returns to registration reply message by GFA, FA to MN.Complete the registration process of above-mentioned interface IF2.

Step 56, MN send login request message by interface IF3 to HA, and HA is that interface IF3 sets up binding.

The interface IF3 of MN is attached to network, by network startup process, completes after access authentication, has obtained home address, Co-CoA3 etc.Then, MN directly sends login request message by interface IF3 to HA, carries the binding logo BID3 that promising interface IF3 generates in this login request message, and HoA, Co-CoA3, and some other information (as security parameter) etc.

HA receives after above-mentioned registration request, for interface IF3 sets up binding.

Thereby upper 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 tri-

On the basis of above-described embodiment two, when MN to GFA send registration request in comprise the stream on mobile node information time, GFA supports stream binding, and the present embodiment is described many interfaces MN and carry out the process of streamer volume, and above-mentioned streamer volume includes but not limited to following several situation:

MN registers one or more stream by certain interface, and all stream is associated with the binding of this interface;

MN registers one or more stream by certain interface, certain binding of associated this interface of some of them stream, and some streams are associated with certain binding of other interfaces;

MN registers one or more stream 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 stream by certain interface, and all stream is not associated with the binding of any interface, and now HA will lose or stores processor corresponding Business Stream.

The process of MN registration flow (with FID) can be carried out with the process of the many bindings of registration (with BID) simultaneously, also can independently carry out.

In the time that the stream on MN carries out initial registration on described GFA, in the time that GFA receives MN and carries out the request of initial flow registration, GFA needs simultaneously entering to binding and go out in binding to upgrade, and sends to HA the registration request that comprises to the information of binding.

Interface IF1, the interface IF2 of many interfaces MN that this embodiment provides to the handling process of GFA registration flow as shown in Figure 6, comprises following treatment step respectively:

Step 61, MN initiate stream login request message by interface IF1 to FA.

The interface IF1 of MN in registration binding BID1 or afterwards, initiates stream login request message to FA, in this stream login request message, carries stream option information, comprises traffic identifier FID1 and stream description, and associated binding logo BID1 etc.

Step 62, FA send stream login request message to GFA.

FA receives after above-mentioned stream login request message, preserves stream option information in binding corresponding to interface IF1.Then, send stream login request message to GFA, in this stream login request message, carry the stream option information of the IF1 of MN, comprise traffic identifier FID1 and stream description, and associated binding logo BID1 etc.

Step 63, corresponding the entering to binding and go out to binding of GFA docking port IF1, send stream login request message to HA.

GFA receives after above-mentioned stream login request message, what docking port IF1 was corresponding enters to binding and goes out to binding to upgrade, entering to binding and going out in binding to increase the stream option information of the interface IF1 of MN, going out in binding, the stream option information of the IF1 of MN is associated with to binding logo BIDx

Then, GFA sends stream login request message to HA, carries the stream option information of the IF1 of MN in this stream login request message.HA receives after above-mentioned stream login request message, and the stream option information of the IF1 of MN is updated in the upper corresponding binding of setting up of HA.

Step 64, MN initiate stream login request message by interface IF2 to GFA.

The interface IF2 of MN in registration binding BID2 or afterwards, directly initiates to flow login request message to GFA, carries the stream option information of the IF2 of MN in this stream login request message, comprises traffic identifier FID2 and stream description, and associated binding logo BID2 etc.

Step 65, corresponding the entering to binding and go out to binding of GFA docking port IF2, send stream login request message to HA.

GFA receives after above-mentioned stream registration request, what docking port IF2 was corresponding enters to binding and goes out to binding to upgrade, entering to binding and go out in binding to increase the stream option information of the interface IF2 of MN, and going out in binding, the stream option information of the IF2 of MN is associated with to binding logo BIDx.

Then, GFA sends stream login request message to HA, carries the stream option information of the IF2 of MN in this stream login request message, comprises traffic identifier FID2 and stream description, and associated binding logo BIDx etc.

HA receives after above-mentioned stream login request message, and the stream option information of the IF2 of MN is updated in the upper corresponding binding of setting up of HA.

On the basis of above-described embodiment two, in the time moving between the stream of the MN interface in the visited network at GFA place, MN flows while switching, and GFA only needs to carry out register update to entering to binding, and does not need to notify HA to carry out register update.

Such as, when MN for example, for example, for the consideration of service needed (needing higher bandwidth) or load balancing (now the load of IF1 is overweight), wish the Business Stream FID1 on interface IF1 to be switched to IF2.So the IF2 of MN, to GFA sending zone login request message, carries the stream option information of Business Stream FID1 in this regional registration request message, comprise traffic identifier FID1 and associated binding logo BID1 thereof, and other necessary information HoA, GFA-CoA etc.

GFA receives after above-mentioned zone login request message, and docking port IF1, corresponding the entering to binding of interface IF2 are upgraded, and do not need docking port IF1, corresponding the going out to binding of interface IF2 to upgrade.

Preferably, GFA cancels request to FA sending zone, with the traffic identifier FID1 cancelling and/or and associated binding logo BID1, and the HoA1 of other necessary informations MN etc.After GFA finishes dealing with, to MN sending zone registration reply message, complete the process that stream switches.

In actual applications, MN can also send streamer volume or switch registration to GFA separately.

On the basis of above-described embodiment two, in the time that an interface of MN moves in GFA territory, for example, for example, due to the load balancing (now the load of FA1 is overweight) of network, the FA1 of the interface IF1 of MN in GFA territory moves to the FA2 in GFA territory, now the LCoA of MN (being also FA-CoA or Co-CoA) will change into FA-CoA2, and MN need to be to GFA sending zone login request message.

Concrete processing procedure comprises:

Due to reasons such as the load balancing of network, network or terminal initiate that the FA1 in GFA territory moves to the FA2 in GFA territory by the interface IF1 of MN, for the IF1 of MN notices new Care-of Address FA-CoA2.

MN, to FA2 sending zone login request message, carries binding logo BID1 in this regional registration request message, and HoA1, GFA-CoA etc.FA2 receives after regional registration request message, for MN creates binding.Then, FA2 inserts after FA-CoA2 in regional registration request message, sends this regional registration request message to GFA.

GFA receives after the login request message of FA2 transmission, according to the information of MN, determines corresponding the entering to binding (it is designated BID1) of interface IF1 of MN.Then, what docking port IF1 was corresponding enter upgrades to the binding information of binding, is mainly that FA-CoA2 is replaced to FA-CoA1, and what docking port IF1 was corresponding enter does not change to other information in binding.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 corresponding enter to when binding or before, cancel message to the binding of FA1 sending zone, this binding is cancelled and in message, is carried the binding logo BID1 and other information HoA1 of MN etc. that cancel, and with cause value, the interface IF1 of instruction MN switches.

After GFA finishes dealing with, reply regional registration response message by FA2 to MN, complete the handoff procedure of interface IF1.

Embodiment tetra-

In the mobile IPv 4 system that the present embodiment provides, under proxy mode, realize FA support many interfaces successively/the application scenarios schematic diagram of mobile registration simultaneously as shown in Figure 7.

In the application scenarios shown in Fig. 7, many interfaces MN701 has 3 interface IF1, interface IF2 and interface IF3, the networks such as difference corresponding WiFi, WiMAX, LTE.

Interface IF1, 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, in other visited network, use Co-CoA3.

Handling process in the time that the MN in the application scenarios shown in above-mentioned Fig. 7 upper interface IF1, interface IF2 successively register to HA by FA as shown in Figure 8, 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 network startup process, completes after access authentication, has obtained home address: FA-CoA1.Now, 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, FA-CoA1 and some other registration request (as security parameter).

Step 82, FA are that MN sets up into binding and going out to binding, forward login request message to HA.

FA receives after above-mentioned login request message, and for MN sets up into binding, this enters to 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 MN request registration to binding, HoA, and FA-CoA1, and newly-generated binding logo BIDy, now the value of BIDy and binding logo BID1 are identical or different.

Then, FA forwards login request message to HA, carries going out to binding information of MN in this login request message.HA receives after above-mentioned login request message, for MN creates binding, sets up bidirectional tunnel with FA, to forward MN message.

HA returns to registration reply message by FA to MN, completes 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 network startup process, completes after access authentication, has obtained home address, FA-CoA1 etc.Then, MN sends login request message by interface IF2 to FA, carries the binding logo BID2 that promising interface IF2 generates in this login request message, and HoA, FA-CoA1, and the information of some other registration request (as security parameter).

The login request message that above-mentioned MN sends to FA is local login request message or local login request message.

FA receives after above-mentioned login request message, checks that the interface IF1 of MN has registered binding BID1, when the binding BID2 of front port IF2 registration difference with it, for the IF2 of MN sets up new entering to binding.Meanwhile, whether the binding information of the IF2 registration of FA inspection MN is consistent with the binding information of IF1 registration, if inconsistent, performs step 84.

If the binding information of IF2 registration is consistent with the binding information of IF1 registration, FA does not need to upgrade going out to binding of MN, does not need to upgrade to HA transmission registration message yet.Now, FA returns to registration reply message to MN, completes registration process.Thereby upper the entering to binding of setting up of FA:

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. ...
...	...	...	...

Step 84, FA upgrade going out to binding of the MN that set up, send the registration request carrying out to the lastest imformation of binding to HA.

In the time that the binding information of IF2 registration changes with the binding information of IF1 registration, FA upgrades 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 to HA the registration request carrying out to the lastest imformation of binding.

HA receives after above-mentioned registration request, for MN upgrades to binding.HA returns to registration reply message by GFA, FA to MN.Complete the registration process of above-mentioned interface IF2.

Step 85, MN send login request message by interface IF3 to HA, and HA is that interface IF3 sets up binding.

The interface IF3 of MN is attached to network, by network startup process, completes after access authentication, has obtained home address, Co-CoA3 etc.Then, MN directly sends login request message by interface IF3 to HA, carries the binding logo BID3 that promising interface IF3 generates in this login request message, and HoA, Co-CoA3, and some other information (such as security parameter etc.).

Thereby upper 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 in a similar manner stream binding 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 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 process such as streamer volume and stream switching in FA territory.

Above-mentioned local login request message is the expansion of the registration message of RFC3344 definition, and except 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 instruction FA.

Care-of Address, for FA-CoA or be empty.

Mobility Session Identification, mobile session identification, for identifying local registration request and response message pair; To distinguish, and prevent message replay attack.

Expansion, 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 the present embodiment is described proxy mode generates BID.

Mode 1, as the embodiment explanation of aforementioned description, GFA/FA can adopt first BID of MN registration in outlet binding, sends the login request message that comprises this first BID to HA simultaneously.In the time that MN moves out the visited network at GFA/FA place or nullifies, GFA/FA needs again to send updating message to HA.

Mode 2, is divided into 2 sections by the BID of 16bit, a part of identification nodes (for example high byte 4bit), and another part represents the numbering (low byte 12bit) of binding.Wherein the 4bit of identification nodes is defined as follows:

0000 MN

0001 FA

0010 GFA

0011 HA

0100～1111 is unallocated.

Based on the application scenarios of the invention described above embodiment bis-, first network node is GFA, and second network node is HA.Interface IF1, interface IF2, the interface IF3 of MN have set up respectively corresponding binding on GFA, HA.Now, because interface moves or the factor such as offered load, the related service stream on interface IF1 will be switched to from GFA territory non-GFA territory; Or due to factors such as the poor signals of interface IF1, interface IF1 exits network.

In this case, the processing procedure that GFA upgrades BID mainly comprises:

First network node (GFA) detects the BID1 attachment removal that the interface IF1 of MN is corresponding, so upgrade the going out to binding of MN, HoA1 is deleted in going out to the mark of binding using the binding BID2 of interface IF2 as MN simultaneously, and what BID1 was corresponding enters to binding.

Above-mentioned first network node detect BID1 that the interface IF1 of MN is corresponding the method for attachment removal include but not limited to following several:

MN has sent the login request message of lifetime=0 to first network node by interface IF1, represent the BID1 attachment removal that interface IF1 is corresponding.

MN sends login request message to HA (second network node), carries HoA1, Co-CoA5, and the binding BID1 information of interface IF1 in this login request message.The information that the interface IF1 of HA renewal MN binds BID1 accordingly.Then send binding to first network node and cancel request message, the HoA1 that carries MN in 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 mark of MN in this login request message, HoA1, GFA-CoA and new binding logo BID2.Thereby on HA, re-create the binding that BID2 is relevant.

Embodiment six

In this embodiment, when GFA/FA receives the multiple registration requests that carried BID that send over by different interfaces, GFA/FA sets up respectively corresponding binding to each interface.Then, above-mentioned multiple registration requests are transmitted to HA by GFA/FA, adds specific indication information at each registration request simultaneously, so that HA distinguishes the registration request from distinct interface according to this indication information, and can set up respectively binding for different registration requests.

With respect to above-described embodiment 1-5, GFA/FA in this embodiment is relatively simple while processing the request of the many bindings of foundation of MN, sets up the binding of each interface registration, does not also need to distinguish to binding and enters to binding; Then, GFA/FA (comprises many binding registrations by all registration messages, streamer volume, interface switches, registration message such as stream switchings grade) all pass through HA, add specific indication information at each registration request, so that HA distinguishes each registration request that HoA from distinct interface is identical with CoA, BID is different according to this indication information, and can set up respectively binding for different registration requests simultaneously.

First network node is GFA/FA, and second network node is HA, and the handling process of the request of the GFA/FA that this embodiment provides to the many bindings of the foundation of MN as shown in Figure 9, comprises following treatment step:

Step 91, MN sends login request message by interface IF1 to first network node.

The interface IF1 of MN is attached to network, by network startup process, completes after access authentication, obtains HoA1, CoA1 address information etc.Then, MN sends login request message by interface IF1 to first network node, carries the binding logo BID1 that promising interface IF1 generates in this login request message, and the information of HoA, CoA1 and some other registration request (as security parameter).

If mobile IPv 4 system, CoA1 is FA-CoA or Co-CoA, and registration request is local registration message; If hierarchical mobile IP v4 system, CoA1 information comprises GFA-CoA and local LCoA (LCoA is FA-CoA or Co-CoA), and registration request is local registration message or regional registration message.

Step 92, the interface IF1 that first network node is MN sets up binding, sends the login request message of the identification information that has carried interface IF1 to second network node.

First network node receives after above-mentioned login request message check whether described interface IF1 registers on described first network node, and if so, described first network node is that described interface to be registered upgrades binding; Otherwise, for the interface IF1 of MN sets up binding, the binding information HoA1 that comprises MN, CoA1, and binding logo BID1 etc.

Then, first network node sends login request message to second network node, in this login request message, carry the binding information of the interface IF1 of MN, in binding logo option, increase the identification information of interface IF1, 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 simultaneously.

Taking classification MIPv4 as example, can in binding logo option, expand an indicating bit, represent by this indicating bit many binding registrations that this interface IF1 that is in hierarchical mobile IP system, GFA is MN carries out.

In actual applications, can also in the login request message sending to HA, be inserted by first network node the link-layer identification of the interface IF1 of MN.Because the link-layer identification of the each interface of MN is different, thereby HA can distinguish different bindings according to the link-layer identification of this interface.

Second network node is received after above-mentioned login request message, searches the existing binding of MN, and mate according to the mark of MN, HoA, BID etc., is now defined as new binding, thereby binds for MN creates.

Alternatively, before setting up binding, (the HoA of second network node to MN, CoA) the specific indication information (indicating bit in binding logo option described above and in registration request, the link-layer identification of interface etc.) carry out together uniqueness inspection, if all identical, refuse this registration request, reply failed response message; Otherwise accept this registration request, further process.After finishing dealing with, set up bidirectional tunnel with first network node, to forward the message of MN.Now, second network node returns to registration reply message by first network node to MN, completes registration process.

First network node, in the time of the login request message of follow-up interface IF2, the interface IF3 transmission that receives MN, carries out the above-mentioned treatment step corresponding with interface IF1 too.

The device that the embodiment of the present invention also provides a kind of multiple interface mobile node to carry out mobile IP registration, this device is first network node, its structural representation as shown in figure 10, comprises as lower module:

Registration request receiver module 101, for receiving the first registration request of mobile node transmission, carries the first binding logo of interface to be registered in described the first registration request;

Registration request processing module 102, be used for according to described the first registration request, and in the time there is no the log-on message of other interface on described mobile node on described first network node, send the second registration request to second network node, in described the second registration request, carry to the 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 to indicate the indication information of interface registration or the link-layer identification of interface.

Described registration request processing module 102, specifically for and in the time there is no the log-on message of other interface on described mobile node on described first network node, set up and comprise entering to binding and comprising the going out to binding of described the second binding logo distributing to described mobile node of described the first binding logo for described interface to be registered, described the second binding logo and described the first binding logo are identical or different; Send the second registration request that carries the second binding logo distributing to described mobile node to described second network node.

Described registration request processing module 102 can also comprise: at least one item in the first processing module 1021 and the second processing module 1022, wherein,

The first processing module 1021, in the time that described mobile node has interface log-on message on described device, for described interface foundation to be registered comprises entering to binding of described the first binding logo;

The second processing module 1022, for checking whether described interface to be registered is registered on described device, if so, for described interface to be registered upgrades binding; Otherwise, for described interface to be registered is set up binding; Send the second registration request of the interface identifier information of carrying described interface to be registered to described second network node.

Described first network node can be gateway external agent, and described second network node is home agent; Or described first network node is external agent, described second network node is home agent or gateway external agent.

Such as, in the hierarchical mobile IP v4 system shown in above-mentioned Fig. 3, first network node is GFA/FA, second network node is HA.

The concrete processing procedure of above-mentioned registration request processing module mainly comprises: when registration request receiver module receives after above-mentioned the first registration request, while thering is no the log-on message of other interface on described mobile node on registration request processing module inspection first network node, this first registration request is first registration request that mobile node sends to first network node.

So above-mentioned registration request processing module sends the second registration request to second network node, in described the second registration request, carry to the second binding logo of described mobile node distribution or the interface identifier information of described interface to be registered.

Further, the process that above-mentioned registration request processing module sends the second registration request to described second network node specifically comprises:

Above-mentioned registration request processing module is that described interface to be registered is set up and comprised entering to binding and comprising the going out to binding of described the second binding logo distributing to described mobile node of described the first binding logo.In Fig. 3, above-mentionedly go out to represent with MN binding X to binding, above-mentionedly go out to be total interface from mobile node to binding shares, above-mentioned go out to the binding information that comprises mobile node request registration in binding.Described the second binding logo and described the first binding logo are identical or different.

Described registration request processing module sends the second registration request that carries the second binding logo distributing to described mobile node to described second network node.

Afterwards, when other interface that passes through of above-mentioned mobile node sends registration request to described first network node, while carrying the binding logo of other interface in this registration request.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 interface log-on message on described first network node, so described first network node is that described other interface is set up entering to binding of the binding logo that comprises described other interface.Set up out to binding to this other interface, do not send the second registration request to described second network node yet.

In the time switching between the interface of the stream on mobile node in the visited network at described first network node place, mobile node switches registration, now described first network node only upgrades in entering to binding of correspondence, go out to the content of binding and do not change, do not upgrade going out to binding, described first network node does not send registration request to second network node;

In the time that the interface on mobile node moves in the visited network at described first network node place, there is change in the CoA on interface, mobile node switches registration, now described first network node only upgrades in entering to binding of correspondence, go out to the content of binding and do not change, do not upgrade going out to binding, described first network node is not initiated register update to described second network node;

In the time that the stream on mobile node or interface move between the interface of the visited network across described first network node place, mobile node switches registration, now described first network node upgrades in entering to binding of correspondence, go out to the content of binding and also upgrade simultaneously, need to upgrade going out to binding, described first network node is initiated register update to described second network node.If stream is switched on the interface outside described first network nodes domains or interface moves to outside described first network nodes domains, the stream information in described this binding of first network knot removal or delete the binding that this interface is corresponding.

The embodiment of the present invention also provides the device of a kind of region mobile IP registration, is applied to mobile node in the territory at the described device place situation to this device sending zone registration request, and its structural representation as shown in figure 11, comprises as lower module:

Regional registration request receiving module 111, the regional registration request sending for receiving mobile node, carries the binding logo of interface to be registered in described registration request, and described regional registration request is the registration request in the territory at described first network node place.

Module 112 is set up in binding, for according to the received registration request of described regional registration request receiving module, creates or upgrade the binding entry of described mobile node.

In described regional registration request, can also carry flow identification information.

Described device can also comprise:

Region de-registration request processing module 113, for the region de-registration request sending to mobile node, carries binding logo information or flow identification information in the de-registration request of described region.

Described device can be gateway external agent or external agent.

The embodiment of the present invention also provides a kind of system of mobile IP registration, it is characterized in that, comprising:

Described first network node is gateway external agent, and described second network node is home agent;

Or,

Described first network node is external agent, and described second network node is home agent or gateway external agent.

Such as, in the networking schematic diagram shown in Fig. 7, first network node is external agent, second network node is home agent.

The concrete processing procedure of above-mentioned first network node mainly comprises:

When first network node receives after above-mentioned the first registration request, while thering is no the log-on message of other interface on described mobile node on first network node inspection first network node, this first registration request is first registration request 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 entering to binding and comprising the going out to binding of described the second binding logo distributing to described mobile node of described the first binding logo.Then, send the second registration request to second network node, in described the second registration request, carry to the second binding logo of described mobile node distribution or the interface identifier information of described interface to be registered.

The concrete processing procedure of above-mentioned second network node mainly comprises: second network node is received after above-mentioned the second registration request, according to the interface identifier information of the second binding logo carrying in described the second registration request or described interface to be registered, described mobile node is registered, for mobile node creates binding, set up bidirectional tunnel with first network node, to forward the message of this mobile node.Then, second network node returns to registration reply message by first network node to mobile node, completes the registration process of the interface to be registered of above-mentioned mobile node.

In sum, the embodiment of the present invention provides into binding to binding and going out to the classification of binding to MN by the GFA/FA in classification MIPv4 system (MIPv4 system), when the multiple interfaces that ensured MN can successively adhere to the network that is registered to GFA/FA place, thereby can make MN obtain more bandwidth, the already-existing session of MN can be continued.

Switch or when interface switches, can only upgrade entering to binding of MN, and not upgrade the going out to binding of MN when MN flows in the territory at GFA/FA place, saving the time delay that stream switches or interface switches, having reduced the signaling traffic load of network.

By newly-increased local login request message in mobile IPv 4 system, can make many interfaces MN in FA territory, carry out carrying out this locality registration to FA in the process such as streamer volume and stream switching.

One of ordinary skill in the art will appreciate that all or part of flow process realizing in above-described embodiment method, can carry out the hardware that instruction is relevant by computer program to complete, described program can be stored in a computer read/write memory medium, this program, in the time carrying out, can comprise as the flow process of the embodiment of above-mentioned each side method.Wherein, described storage medium can be magnetic disc, CD, read-only store-memory body (Read-Only Memory, ROM) or random store-memory body (Random Access Memory, RAM) etc.

The above; only for preferably embodiment of the present invention, but protection scope of the present invention is not limited to this, is anyly familiar with in technical scope that those skilled in the art disclose in the present invention; the variation that can expect easily or replacement, within all should being encompassed in 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

1. a method for mobile IP registration, is characterized in that, comprising:

In the time there is no the log-on message of other interface on described mobile node on described first network node, according to described the first registration request, described first network node sends the second registration request to second network node, carries the second binding logo distributing to described mobile node in described the second registration request;

The step that described first network node sends the second registration request to described second network node specifically comprises: described first network node is that described interface to be registered is set up and comprised entering to binding and comprising the going out to binding of described the second binding logo of described the first binding logo, described in go out to the total interface of binding described mobile node to share; Described first network node sends the second registration request that carries described the second binding logo to described second network node;

In the time having the log-on message of other interface of described mobile node on described first network node, described first network node is that described interface to be registered is set up and comprised the entering to binding of described the first binding logo, and described interface to be registered shares the going out to binding of other interface of described the above mobile node of first network node.

2. the method for mobile IP registration according to claim 1, is characterized in that, in the time also comprising the information of the stream on described mobile node in described the first registration request, described method also comprises:

When the stream on described mobile node carries out initial registration on described first network node, described first network node sends the second registration request to second network node, and described the second registration request carries the stream information on described mobile node.

3. 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 so, 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 registration request of the interface identifier information of carrying described interface to be registered to described second network node.

4. according to the method for the mobile IP registration described in claims 1 to 3 any one, it is characterized in that: described first network node is gateway external agent, described second network node is home agent;

Or,

5. a device for mobile IP registration, is characterized in that, comprising:

Registration request processing module, for in the time there is no the log-on message of other interface on described mobile node on described device, according to described the first registration request, send the second registration request to second network node, in described the second registration request, carry the second binding logo distributing to described mobile node;

Described registration request processing module, comprises entering to binding and comprising the going out to binding of described the second binding logo of described the first binding logo specifically for setting up for described interface to be registered, described in go out to the total interface of binding described mobile node to share; Send the second registration request that carries described the second binding logo to described second network node;

Described registration request processing module also comprises: the first processing module, for in the time having the log-on message of other interfaces of described mobile node on described device, set up and comprise the entering to binding of described the first binding logo for described interface to be registered, described interface to be registered shares the going out to binding of other interface of described the above mobile node of first network node.

6. the device of mobile IP registration according to claim 5, is characterized in that:

Described device is gateway external agent or external agent.

7. according to the device of the mobile IP registration described in claim 5 or 6, it is characterized in that, described registration request processing module also comprises: the second processing module, for checking whether described interface to be registered is registered on described device, if so, for described interface to be registered upgrades binding; Otherwise, for described interface to be registered is set up binding; Send the second registration request of the interface identifier information of carrying described interface to be registered to described second network node.

8. a system for mobile IP registration, is characterized in that, comprising:

First network node, for receiving the first registration request of mobile node transmission, carries the first binding logo of interface to be registered in described the first registration request; In the time there is no the log-on message of other interface on described mobile node on described first network node, according to described the first registration request, send the second registration request to second network node, in described the second registration request, carry the second binding logo distributing to described mobile node; The described step that sends the second registration request to second network node specifically comprises: described first network node is that described interface to be registered is set up and comprised entering to binding and comprising the going out to binding of described the second binding logo of described the first binding logo, described in go out to the total interface of binding described mobile node to share; Described first network node sends the second registration request that carries described the second binding logo to described second network node; In the time having the log-on message of other interface of described mobile node on described first network node, described first network node is that described interface to be registered is set up and comprised the entering to binding of described the first binding logo, and described interface to be registered shares the going out to binding of other interface of described the above mobile node of first network node;

9. the system of mobile IP registration according to claim 8, is characterized in that:

Or,