CN101883351B - Method and device for registering mobile IP - Google Patents

Abstract

The present invention provides a mobile IP registration method and device, the method mainly includes: the first network node receives the first registration request sent by the mobile node, and the first registration request carries the first binding identifier of the interface to be registered ; The first network node establishes a binding for the interface to be registered according to the first registration request and the registration information of the interface on the mobile node on the first network node, and determines whether it needs to be registered The second network node sends a second registration request; when it is necessary to send a second registration request to the second network node, the first network node sends to the second network node the second binding that is assigned to the mobile node A second registration request for the identifier or the interface identifier information of the interface to be registered. The invention realizes that multiple interfaces of the MN can be successively registered in the hierarchical mobile IP system, and can reduce the signaling load of the hierarchical mobile IP system.

Description

Method and device for mobile IP registration

Technical Field

The present invention relates to the field of network communication technologies, and in particular, to a method and an apparatus for performing mobile IP registration for a multi-interface MN (mobile node).

Background

The structural diagram of the existing mobile IPv4 system is shown in fig. 1, and includes the following elements: MN, CN (Correspondent Node), FA (Foreign Agent), and HA (Home Agent). Wherein,

MN: is a mobile terminal or router. As a MN moves from one network or subnet to another, its point of attachment also changes from time to time, and the location of the MN's access network changes. But the HoA (Home Address) of the MN is not changed, the MN can still communicate with the CN, and the session is not interrupted.

CN: the node communicating with the MN is a mobile node or a fixed network node.

The FA is a router which provides mobility management and routing services for the MN after the MN moves to the visited network and registers, and is generally a default router of the MN in the visited network.

The HA is a router which registers with the home network and provides mobility management and routing services for the MN.

The general working mechanism of the mobile IPv4 system includes: a mobile registration procedure and a data forwarding procedure.

The hierarchical mobile IPv4 system is formed by expanding on the basis of mobile IPv4, and a network entity is added in the hierarchical mobile IPv4 system: GFA (Gateway Foreign Agent). The GFA has the function of the FA, using the GFA-CoA (Care-of address) when it provides routing traffic. Co-CoA and FA-CoA of a mobile IP system are collectively called LCoA (Local CoA, Local care-of address) in a hierarchical mobile IP system.

In the hierarchical mobile IPv4 system, the initial registration process is similar to that of mobile IPv4, except that when the MN registers with the HA, the MN also needs to go through the GFA, and a binding of the MN, including the HoA, LCoA, and GFA-CoA of the MN, is established on the GFA. When the GFA forwards the registration message to the HA, the LCoA is removed from the registration message, so that the binding established on the HA includes the HoA and the GFA-CoA address. On the data forwarding plane, a bidirectional tunnel is established between the GFA and the HA, and a route is provided for data traffic of the MN.

Meanwhile, in the hierarchical mobile IPv4 system, when the MN moves within the visited network where the GFA is located, a regional registration message is newly added, and the MN only needs to perform regional registration with the GFA, but the GFA does not need to update to the HA, so that the delay of MN mobility handover can be saved.

In the prior art, a process of a multi-interface MN for mobile IPv4 registration mainly includes: the multi-interface MN obtains a HoA, when different interfaces of the MN are accessed through different networks such as WiFi (Wireless Fidelity), WiMAX (Worldwide Interoperability for Microwave Access) and the like, different CoA (CoA) is obtained on each interface, mobile registration is initiated to HA through different interfaces respectively, and therefore a plurality of tunnels are established, and the plurality of tunnels can enable the MN to obtain more bandwidths.

And binding the HoA of the MN with a plurality of CoA. In mobile registration of the MN, in order to distinguish different coas on the MN and the HA, a unique BID (Binding Identifier) needs to be allocated to each interface when the multi-interface MN registers. Therefore, when mobile registration is carried out on the HA after the CoA of a certain interface of the MN is changed, the HA can carry out identification according to the BID of the interface.

The MN allocates FIDs (Flow identifiers) to different service flows, each FID is associated with a different BID, and establishes different Flow bindings on the HA through a Flow registration process. Therefore, when the HA receives the service flow sent to the MN by the CN, the HA can distinguish the service flow according to the flow binding, and then index to a different binding BID, that is, the HA can forward the service flow to the MN through a different tunnel.

In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:

1. in the process of mobile IPV4 registration of a multi-interface MN, a scenario of hierarchical mobile IPV4 is not involved, and when the MN moves to a visited network where a GFA is located, if the GFA does not support simultaneous mobile registration of multiple interfaces of the MN, the MN can only use one interface to perform mobile registration, which may cause that an existing session of the MN cannot continue or more bandwidths cannot be obtained, and the quality of service is reduced.

2. When multiple interfaces of MN establish multiple bindings to HA through the same FA, FA needs to forward registration request to HA for each interface, thereby increasing registration delay and signaling load; further, when the service flow is switched between different interfaces, the FA needs to notify the HA to update, thereby increasing the delay of flow switching.

Disclosure of Invention

The embodiment of the invention provides a method and a device for mobile IP registration, which are used for realizing that a plurality of interfaces of MN can be successively registered to a network where GFA/FA is positioned.

A method of mobile IP registration, comprising:

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;

according to the first registration request and when the first network node does not have the registration information of other interfaces on the mobile node, the first network node sends a second registration request to a second network node, wherein the second registration request carries a second binding identifier distributed to the mobile node or interface identifier information of the interface to be registered.

A method of IP registration, comprising:

a first network node receives a regional registration request sent by a mobile node, wherein the regional registration request carries a binding identifier of an interface to be registered, and the regional registration request is a registration request in a domain where the first network node is located;

and creating or updating a binding entry of the mobile node according to the area registration request.

An apparatus for mobile IP registration, comprising:

a registration request receiving module, configured to receive a first registration request sent by a mobile node, where the first registration request carries a first binding identifier of an interface to be registered;

and a registration request processing module, configured to send a second registration request to a second network node according to the first registration request and when the device does not have registration information of other interfaces on the mobile node, where the second registration request carries a second binding identifier allocated to the mobile node or interface identifier information of the interface to be registered.

An apparatus for IP registration, comprising:

a regional registration request receiving module, configured to receive a regional registration request sent by a mobile node, where the registration request carries a binding identifier of an interface to be registered, and the regional registration request is a registration request in a domain where the first network node is located;

and the binding establishing module is used for creating or updating the binding entry of the mobile node according to the registration request received by the area registration request receiving module.

A system for mobile IP registration, comprising:

the first network node is used for receiving a first registration request sent by the mobile node, wherein the first registration request carries a first binding identifier of an interface to be registered; and sending a second registration request to a second network node according to the first registration request and when the first network node does not have the registration information of other interfaces on the mobile node, wherein the second registration request carries a second binding identifier distributed to the mobile node or the interface identifier information of the interface to be registered.

And the second network node is used for receiving a second registration request sent by the first network node and registering the mobile node according to a second binding identifier carried in the second registration request or the interface identifier information of the interface to be registered.

It can be seen from the technical solutions provided in the embodiments of the present invention that, in the embodiments of the present invention, the first network node establishes a binding for the interface to be registered of the MN according to the received registration request and the registration information of the interface on the MN on the first network node, and determines whether the second registration request needs to be sent to the second network node, so that multiple interfaces of the MN can be registered in the hierarchical mobile IP system sequentially, and the signaling load of the hierarchical mobile IP system can be reduced.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.

Fig. 1 is a schematic structural diagram of a conventional mobile IPv4 system;

fig. 2 is a flowchart illustrating a method for mobile IP registration according to an embodiment of the present invention;

fig. 3 is a schematic structural diagram of a hierarchical mobile IPv4 system according to an embodiment of the present invention;

fig. 4 is a schematic view of an application scenario of a second embodiment of the present invention;

fig. 5 is a processing flow chart when the interface IF1 and the interface IF2 of the MN register with the HA sequentially through the GFA according to the second embodiment of the present invention;

fig. 6 is a flowchart of processing that interface IF1 and interface IF2 of the multi-interface MN register flows with the GFA respectively according to the third embodiment of the present invention;

fig. 7 is a schematic view of an application scenario for implementing that the FA supports multi-interface successive/simultaneous mobile registration in the proxy mode in the mobile IPv4 system according to the fourth embodiment of the present invention;

fig. 8 is a processing flow chart of registration of an interface IF1 and an interface IF2 on the MN with the HA successively through the FA according to the fourth embodiment of the present invention;

fig. 9 is a flowchart of processing of a GFA/FA request to establish multi-binding for an MN according to a sixth embodiment of the present invention;

fig. 10 is a schematic structural diagram of an apparatus for performing mobile IP registration by a multi-interface mobile node according to an embodiment of the present invention;

fig. 11 is a schematic structural diagram of a device for regional mobile IP registration according to an embodiment of the present invention.

Detailed Description

In the embodiment of the invention, after a foreign agent or a gateway foreign agent of a mobile node receives registration requests respectively sent by the mobile node through different interfaces, an ingress binding is respectively established between the foreign agent or the gateway foreign agent and each interface of the mobile node, and an egress binding between a public and a home agent is established between all interfaces of the mobile node.

For the convenience of understanding the embodiments of the present invention, the following description will be further explained by taking several specific embodiments as examples in conjunction with the drawings, and the embodiments are not to be construed as limiting the embodiments of the present invention.

Example one

The processing flow of the method for mobile IP registration provided in this embodiment is shown in fig. 2, and includes the following processing steps:

step 21, the first network node receives a first registration request sent by the mobile node through the interface to be registered.

In this embodiment, first, a first network node receives a first registration request sent by a mobile node through an interface to be registered, where the first registration request carries a first binding identifier of the interface to be registered.

For example, in the hierarchical mobile IPv4 system shown in fig. 3, the first network node is a GFA/FA. The mobile node sends a first registration request to the GFA/FA through the interface 1, wherein the first registration request carries the first binding identifier of the interface 1.

Step 22, the first network node sends a second registration request to the second network node according to the first registration request and when the first network node has no registration information of other interfaces on the mobile node.

The method specifically comprises the following steps: after receiving the first registration request, the first network node checks that there is no registration information of other interfaces on the mobile node on the first network node, that is, the first registration request sent through the interface 1 is the first registration request sent by the mobile node to the GFA/FA.

Then, the first network node sends a second registration request to a second network node, where the second registration request carries a second binding identifier allocated to the mobile node or interface identifier information of the interface to be registered (i.e., interface 1).

For example, in the hierarchical mobile IPv4 system shown in fig. 3, the second network node is an HA.

Further, the process of the first network node sending the second registration request to the second network node specifically includes:

the first network node establishes an incoming binding containing the first binding identifier and an outgoing binding containing the second binding identifier allocated to the mobile node for the interface to be registered (i.e., interface 1). In fig. 3, the outbound binding is represented by MN binding X, which is common to all interfaces of the mobile node, and includes binding information for requesting registration of the mobile node. The second binding identifier is the same as or different from the first binding identifier.

The first network node sends a second registration request to the second network node carrying a second binding identifier assigned to the mobile node.

Then, when the mobile node sends a registration request to the first network node through another interface (such as interface 2), where the registration request carries the binding identifier of the other interface. Since the interface 1 is registered with the first network node, the first network node checks that the mobile node has interface registration information on the first network node, and then the first network node establishes an inbound binding containing the binding identifier of the other interface for the other interface. And does not establish a binding for the other interface nor send a second registration request to the second network node.

Further, when the first registration request further includes: and when the flow is initially registered on the first network node, the first network node sends a second registration request to a second network node, wherein the second registration request carries the flow information on the mobile node.

When the flow on MN is switched between interfaces in the visit network where GFA/FA is located, MN performs switching registration, at this time, GFA/FA updates only the corresponding in-bound, the content of the out-bound is not changed, the out-bound is not updated, and GFA/FA does not send a registration request to HA;

when an interface on the MN moves in a visiting network where the GFA/FA is located, CoA on the interface changes, the MN performs switching registration, the GFA/FA updates only corresponding incoming binding at the moment, the content of the outgoing binding is not changed, the outgoing binding is not updated, and the GFA/FA does not initiate registration updating to HA;

when the flow or interface on MN moves between the interfaces of visiting network crossing GFA/FA, MN switches registration, GFA/FA updates the corresponding incoming binding, the content of outgoing binding is updated at the same time, the outgoing binding needs to be updated, and GFA/FA initiates registration update to HA. And if the flow is switched to the interface outside the GFA/FA domain or the interface moves out of the GFA/FA domain, the GFA/FA deletes the flow information in the binding or deletes the binding corresponding to the interface.

Example two

The embodiment describes a method for supporting multi-interface successive mobile registration of an MN by a GFA in a hierarchical mobile IPv4 system, and an application scenario diagram of the embodiment is shown in fig. 4.

In the scenario shown in fig. 4, the multi-interface MN401 has 3 interfaces IF1, IF2, and IF3, which correspond to different networks.

The interface IF1 is connected to the visited network where the GFA is located, and registers with the HA404 through the FA402, GFA403 using FA-CoA1 (foreign agent care-of address).

The interface IF2 is connected to the visited network where the GFA403 is located and registers directly with the HA404 through the GFA403 using the Co-CoA2 (Co-located care-of address).

The interface IF3 connects to the visited network where the non-GFA is located, using Co-located CoA3 (Co-located local care-of address) in the visited network where the non-GFA is located.

In the application scenario shown in fig. 4, a processing flow when the interface IF1 and the interface IF2 of the MN register with the HA sequentially through the GFA is shown in fig. 5, and includes the following processing steps:

step 51, the MN sends a registration request message to the FA via interface IF 1.

Interface IF1 of MN attaches to network, through the network start-up process, after finishing the access authentication, has obtained information such as home address, GFA-CoA, FA-CoA 1. Then, the MN sends a registration request message to the FA through the interface IF1, the registration request message carrying the binding identity BID1 generated for the interface IF1, and information (such as security parameters) of the HoA, GFA-CoA, and some other registration requests.

The FA sends a registration request message to the GFA, step 52.

The FA receives the registration request message and establishes binding for the MN, wherein the binding comprises information of HoA, CoA, BID1 and the like of the MN. After inserting FA-CoA1 address information into the registration request message, the FA sends the registration request message to the GFA.

Step 53, the GFA sends a registration request to the HA, and the HA returns a registration response to the GFA.

After receiving the registration request message sent by the FA, the GFA determines that the interface IF1 of the MN is registering.

The GFA firstly establishes an incoming binding including a binding identifier of an interface IF1 for an interface IF1 of the MN, wherein the incoming binding includes information of HoA, FA-CoA1, BID1 and the like of the MN, security parameters, flow information and the like;

and secondly, establishing an outgoing binding for the MN, wherein the outgoing binding comprises a newly generated binding identifier BIDx, other information such as HoA and GFA-CoA of the MN, mapping identifier information between the outgoing binding and the incoming binding, and the like. The value of the BIDx may be the same as or different from BID1 in the received registration request message.

Then, the GFA sends a registration request to the HA, where the registration request includes information such as HoA of the MN, GFA-CoA, and new binding identity BIDx. After receiving the registration request, the HA establishes binding for the MN and establishes a bidirectional tunnel with the GFA so as to forward a message of the MN.

The HA returns a registration response message to the MN through the GFA and the FA, and completes the registration process of the interface IF 1.

Step 54, MN sends registration request message to FA through interface IF2, GFA checks IF binding information registered by IF2 of MN is consistent with binding information registered by IF 1.

Interface IF2 of MN attaches to network, through the network start-up process, after finishing the access authentication, has obtained information such as home address, GFA-CoA, Co-CoA 2. The MN then sends a registration request message directly to the GFA via interface IF2, which carries the binding identity BID2, HoA, GFA-CoA, and HFA (hierarchical Foreign Agent) extension options (including Co-CoA2) generated for interface IF2, as well as some other registration request information (e.g., security parameters).

The registration request message sent by the MN to the GFA is a home registration request message or a regional registration request message. After the GFA receives the registration request, it determines that the interface IF1 of the MN has registered the binding BID1, and the binding BID2 registered by the current interface IF2 is different from the binding BID1, so that a new incoming binding is established for the interface IF2 of the MN.

Meanwhile, the GFA checks whether the binding information registered by the IF2 of the MN is identical to the binding information registered by the IF1, for example, whether the flow information is identical, and IF not, performs step 55; if the two binding rules are consistent, the outbound binding of the MN does not need to be updated, and at this time, the established inbound binding on the GFA is defined as:

home address	Care-of address	Binding identifier	Other information
				HoA1	FA-CoA1	BID1	Such as: policy/flow information, etc.
HoA1	Co-CoA2	BID2	...
				...	...	...	...

The outbound binding established on GFA is defined as:

home address	Care-of address	Binding identifier	Other information (e.g. stream information)
				HoA1	GFA-CoA	BIDx	Such as: policy/flow information, etc.
...	...	...	...

At this time, the GFA does not need to send a registration request to the HA, and the GFA returns a registration reply message to the MN. The registration process of interface IF2 described above is completed.

Step 55, GFA updates the established outbound binding of MN and sends a registration request carrying the update information of the outbound binding to HA.

When the binding information registered at IF2 of the MN is not identical to the binding information registered at IF1, the GFA updates the already-established outbound binding of the MN, and also adds the binding information (such as flow information) registered at IF2 to the above-mentioned outbound binding of the MN. Then, a registration request carrying out the update information to the binding is sent to the HA.

And after receiving the registration request, the HA updates the binding for the MN. The HA returns a registration response message to the MN through the GFA and the FA. The registration process of interface IF2 described above is completed.

Step 56, the MN sends a registration request message to the HA via interface IF3, and the HA establishes a binding for interface IF 3.

Interface IF3 of MN attaches to network, through the network start-up process, after finishing the access authentication, has obtained home address, Co-CoA3 etc.. Then, the MN sends a registration request message directly to the HA via the interface IF3, where the registration request message carries the binding identity BID3 generated for the interface IF3, and HoA, Co-CoA3, and other information (such as security parameters).

The HA, upon receiving the registration request, establishes a binding for interface IF 3.

The binding established on the HA is thus:

home address	Care-of address	Binding identifier	Other information
				HoA1	GFA-CoA	BIDx	Such as: policy/flow information, etc.
HoA1	Co-CoA3	BID3	...
				...	...	...	...

EXAMPLE III

On the basis of the second embodiment, when a registration request sent by the MN to the GFA includes information of a flow on the mobile node, the GFA supports flow binding, and this embodiment describes a process of flow registration by the multi-interface MN, where the flow registration includes, but is not limited to, the following cases:

MN registers one or more flows through a certain interface, and all flows are associated to the binding of the interface;

MN registers one or more flows through a certain interface, wherein some flows are associated with a certain binding of the interface, and some flows are associated with a certain binding of other interfaces;

MN registers one or more flows through a certain interface, wherein some flows are simultaneously associated with the binding of the interface and other interfaces;

the MN registers one or more flows through a certain interface, all flows are not associated with the binding of any interface, and at the moment, the HA loses or stores the corresponding service flows.

The process of MN registering for flow (with FID) and the process of registering for multi-binding (with BID) can be done simultaneously or independently.

When a flow on the MN performs initial registration on the GFA, that is, when the GFA receives a request for initial flow registration from the MN, the GFA needs to update in-bound and out-bound simultaneously, and send a registration request containing information of out-bound to the HA.

The processing flow of registering flows with the GFA by the interface IF1 and the interface IF2 of the multi-interface MN provided in this embodiment is as shown in fig. 6, and includes the following processing steps:

step 61, the MN initiates a flow registration request message to the FA via interface IF 1.

The interface IF1 of the MN initiates a flow registration request message to the FA while or after registering the binding BID1, where the flow registration request message carries flow option information including a flow identifier FID1 and a flow description, and its associated binding identifier BID 1.

At step 62, the FA sends a flow registration request message to the GFA.

After receiving the flow registration request message, the FA stores the flow option information in the binding corresponding to the interface IF 1. Then, a flow registration request message is sent to the GFA, where the flow registration request message carries the flow option information of the IF1 of the MN, including the flow identifier FID1 and the flow description, and its associated binding identifier BID1, etc.

Step 63, GFA sends flow registration request message to HA for ingress-to-binding and egress-to-binding corresponding to interface IF 1.

After receiving the flow registration request message, the GFA updates the ingress binding and the egress binding corresponding to the interface IF1, adds the flow option information of the interface IF1 of the MN in the ingress binding and the egress binding, and associates the flow option information of the IF1 of the MN with the binding identifier BIDx in the egress binding

Then, the GFA sends a flow registration request message to the HA, which carries the flow option information of the IF1 of the MN. After the HA receives the flow registration request message, it updates the flow option information of IF1 of the MN to the corresponding binding established on the HA.

Step 64, the MN initiates a flow registration request message to the GFA via interface IF 2.

The interface IF2 of MN directly initiates a flow registration request message to the GFA while or after registering the binding BID2, where the flow registration request message carries the flow option information of the IF2 of MN, including the flow identifier FID2 and the flow description, and its associated binding identifier BID2, etc.

Step 65, GFA sends flow registration request message to HA for ingress and egress binding corresponding to interface IF 2.

After receiving the flow registration request, the GFA updates the ingress binding and the egress binding corresponding to the interface IF2, adds the flow option information of the interface IF2 of the MN in the ingress binding and the egress binding, and associates the flow option information of the IF2 of the MN with the binding identifier BIDx in the egress binding.

Then, the GFA sends a flow registration request message to the HA, where the flow registration request message carries the flow option information of the IF2 of the MN, including the flow identifier FID2 and the flow description, and its associated binding identifier BIDx, etc.

After the HA receives the flow registration request message, it updates the flow option information of IF2 of the MN to the corresponding binding established on the HA.

On the basis of the second embodiment, when the flow of the MN moves between interfaces in the visited network where the GFA is located, that is, when the MN performs flow switching, the GFA only needs to perform registration update on the incoming binding, and does not need to notify the HA of performing registration update.

For example, when the MN is considering traffic needs (e.g., needs higher bandwidth) or load balancing (e.g., when the load of IF1 is too heavy), it may be desirable to switch the traffic flow FID1 on interface IF1 to IF 2. Then, IF2 of MN sends area registration request message to GFA, where the area registration request message carries flow option information of traffic flow FID1, including flow id FID1 and its associated binding id BID1, and other necessary information HoA, GFA-CoA, etc.

After receiving the area registration request message, the GFA updates the inbound binding corresponding to interface IF1 and interface IF2, without updating the outbound binding corresponding to interface IF1 and interface IF 2.

Preferably, the GFA sends an area revocation request to the FA, with the revoked flow identity FID1 and/or its associated binding identity BID1, and other necessary information MN's HoA1, etc. After the GFA finishes processing, sending a region registration response message to the MN, and finishing the process of stream switching.

In practical applications, the MN may also send a flow registration or a handoff registration to the GFA alone.

On the basis of the second embodiment, when an interface of the MN moves in the GFA domain, for example, due to load balancing of the network (for example, when the load of the FA1 is too heavy), the interface IF1 of the MN moves from the FA1 in the GFA domain to the FA2 in the GFA domain, and when the LCoA (i.e., the FA-CoA or Co-CoA) of the MN changes to the FA-CoA2, the MN needs to send a region registration request message to the GFA.

The specific treatment process comprises the following steps:

due to the load balance of the network and the like, the network or the terminal initiates to move the interface IF1 of the MN from the FA1 in the GFA domain to the FA2 in the GFA domain, and informs the IF1 of the MN of a new care-of address FA-CoA 2.

The MN sends an area registration request message to the FA2, wherein the area registration request message carries the binding identifier BID1, the HoA1, the GFA-CoA and the like. The FA2, upon receiving the regional registration request message, creates a binding for the MN. Then, the FA2 transmits the area registration request message to the GFA after inserting the FA-CoA2 in the area registration request message.

After receiving the registration request message sent by the FA2, the GFA determines the inbound binding (whose id is BID1) corresponding to the interface IF1 of the MN according to the information of the MN. Then, the binding information of the incoming binding corresponding to the interface IF1 is updated, mainly the FA-CoA2 is replaced by the FA-CoA1, and other information in the incoming binding corresponding to the interface IF1 is not changed. The MN's outbound binding does not need to be updated, nor does it need to send registration updates to the HA.

Optionally, when or before updating the inbound binding corresponding to the IF1, the GFA sends an area binding revocation message to the FA1, where the binding revocation message carries the revoked binding identifier BID1 and other information HoA1 of the MN, and has a cause value, and indicates that the interface IF1 of the MN has been handed over.

After the GFA process is completed, the FA2 replies to the MN with an area registration response message to complete the handover procedure of the interface IF 1.

Example four

Fig. 7 shows an application scenario diagram of the mobile IPv4 system in the proxy mode for supporting multiple interface tandem/simultaneous mobile registration by the FA according to this embodiment.

In the application scenario shown in fig. 7, the multi-interface MN701 has 3 interfaces IF1, IF2, and IF3, which respectively correspond to networks such as WiFi, WiMAX, and LTE.

The interface IF1 and the interface IF2 are simultaneously connected to the visited network where the FA702 is located, and register with the HA703 through the FA using the FA-CoA 1.

The interface IF3 is located in a visited network where the non-FA is located, possibly in other visited networks, using Co-CoA 3.

When the interface IF1 and the interface IF2 on the MN register with the HA successively through the FA in the application scenario shown in fig. 7, a processing flow is shown in fig. 8, which includes the following processing steps:

step 81, the MN sends a registration request message to the FA via interface IF 1.

Interface IF1 of MN attaches to the network, through the network start-up process, after finishing the access authentication, has obtained the home address: FA-CoA 1. At this time, the MN sends a registration request message to the FA through the interface IF1, the registration request message carrying the binding identity BID1 generated for the interface IF1, and information (such as security parameters) of the HoA, FA-CoA1, and some other registration requests.

Step 82, the FA establishes an in-bound and an out-bound for the MN and forwards the registration request message to the HA.

After receiving the registration request message, the FA establishes an entry binding for the MN, where the entry binding includes binding information of the MN, such as HoA, link layer information of an interface IF1 of the MN, and a binding identifier BID 1; and meanwhile, the FA creates an outbound binding for the MN, wherein the outbound binding comprises binding information of the MN requesting registration, HoA, FA-CoA1 and a newly generated binding identifier BIDy, and the value of the BIDy is the same as or different from that of the binding identifier BID 1.

Then, the FA forwards a registration request message to the HA, where the registration request message carries the outbound binding information of the MN. After receiving the registration request message, the HA establishes binding for the MN and establishes a bidirectional tunnel with the FA so as to forward the MN message.

The HA returns a registration reply message to the MN via the FA, completing the registration procedure at interface IF 1.

In step 83, the MN sends a registration request message to the FA through the interface IF2, and the FA checks whether the binding information registered at the IF2 of the MN is consistent with the binding information registered at the IF 1.

Interface IF2 of MN attaches to network, through the network start-up process, after finishing the access authentication, has obtained home address, FA-CoA1, etc. Then, the MN sends a registration request message to the FA through the interface IF2, the registration request message carrying the binding identity BID2 generated for the interface IF2, and information (such as security parameters) of the HoA, FA-CoA1, and some other registration requests.

The registration request message sent by the MN to the FA is a home registration request message or a local registration request message.

After receiving the registration request message, the FA checks that the interface IF1 of the MN has registered the binding BID1, and the binding BID2 registered by the current interface IF2 is different from the binding BID1, so as to establish a new incoming binding for the IF2 of the MN. Meanwhile, the FA checks whether the binding information registered at the IF2 of the MN is identical to the binding information registered at the IF1, and IF not, performs step 84.

IF the binding information registered by IF2 is identical to the binding information registered by IF1, the FA does not need to update the MN's outgoing binding nor send a registration message to the HA for updating. At this time, the FA returns a registration response message to the MN, completing the registration process. The entry established on the FA is thus bound to be:

home address	Link layer identification	Binding identifier	Other information
				HoA1	LLID1	BID1	Such as: policy/flow information, etc.
HoA1	LLID2	BID2	...
				...	...	...	...

The outward binding is as follows:

home address	Care-of address	Binding identifier	Other information (e.g. stream information)
				HoA1	FA-CoA1	BIDy	Such as: policy/flow information, etc.
...	...	...	...

Step 84, the FA updates the established outbound binding of the MN and sends a registration request carrying the update information of the outbound binding to the HA.

When the binding information registered at IF2 is changed from the binding information registered at IF1, the FA updates the already established outbound binding of the MN, and also adds the binding information (such as flow information) registered at IF2 to the outbound binding of the MN as described above. Then, a registration request carrying out the update information to the binding is sent to the HA.

After receiving the registration request, the HA updates the binding for the MN. The HA returns a registration response message to the MN through the GFA and the FA. The registration process of interface IF2 described above is completed.

Step 85, the MN sends a registration request message to the HA via interface IF3, and the HA establishes a binding for interface IF 3.

Interface IF3 of MN attaches to network, through the network start-up process, after finishing the access authentication, has obtained home address, Co-CoA3 etc.. Then, the MN directly sends a registration request message, which carries the binding identity BID3 generated for interface IF3, and HoA, Co-CoA3, and some other information (e.g., security parameters, etc.), to the HA through interface IF 3.

The binding established on the HA is thus:

home address	Care-of address	Binding identifier	Other information
				HoA1	FA-CoA1	BIDy	Such as: policy/flow information, etc.
HoA1	Co-CoA3	BID3	...
				...	...	...	...

Likewise, the FA can support flow binding, flow switching, and the like in a similar manner.

In the basic mobile IPv4 system, only the MN is supported to send the registration message to the HA through the FA, and no local registration message is sent by the MN directly to the FA. In practical application, a local registration request message may be newly added in the mobile IPv4 system, so that the MN initiates local registration with the FA, so that the multi-interface MN performs local registration with the FA during flow registration, flow handover and the like in the FA domain.

The above-mentioned local registration request message is an extension of the registration message defined in RFC3344, and the other fields are the same as the registration message defined in RFC3344 except for the following fields.

Type: type, e.g., value 20, indicates that the message is a local registration message;

foreign Agent Address, indicating the Address of the FA.

Care-of Address, either FA-CoA or null.

A Mobility Session Identification for identifying a local registration request and response message pair; for differentiation and to prevent message replay attacks.

And the extension part is used for carrying a new option or a message field subsequently.

EXAMPLE five

In order to prevent the BID generated by the GFA/FA from colliding with the BID used by the MN in the non-GFA domain, the present embodiment describes how the GFA/FA in the proxy mode generates the BID.

Mode 1, as illustrated in the previously described embodiments, the GFA/FA may employ the first BID registered by the MN in the egress binding while sending a registration request message including the first BID to the HA. When the MN moves out of the visited network where the GFA/FA is located or logs off, the GFA/FA needs to send the update message to the HA again.

Mode 2, a 16-bit BID is divided into 2 segments, one part identifying the node (e.g., 4 bits high) and the other part representing the number of the binding (12 bits low). Wherein the 4 bits identifying the node are defined as follows:

0000 MN

0001 FA

0010 GFA

0011 HA

0100 ~ 1111 are not distributed.

Based on the application scenario of the second embodiment of the present invention, the first network node is a GFA, and the second network node is an HA. Interface IF1, interface IF2 and interface IF3 of MN have already established corresponding bindings on GFA and HA, respectively. At this time, due to factors such as interface movement or network load, the relevant traffic flow on the interface IF1 will be switched from the GFA domain to the non-GFA domain; alternatively, interface IF1 has exited the network due to factors such as poor signaling at interface IF 1.

In this case, the process of updating the BID by the GFA mainly includes:

the first network node (GFA) detects that the BID1 corresponding to the interface IF1 of the MN is detached, and then the outgoing binding of the MN is updated, the binding BID2 of the interface IF2 is used as the identification of the outgoing binding of the MN, and meanwhile, the incoming binding corresponding to the HoA1 and the BID1 is deleted.

The above-mentioned methods for the first network node to detect that the BID1 corresponding to the interface IF1 of the MN has been detached include, but are not limited to, the following:

the MN sends a registration request message with lifetime 0 to the first network node via interface IF1 to indicate that BID1 corresponding to interface IF1 is unattached.

The MN sends a registration request message to the HA (second network node), wherein the registration request message carries binding BID1 information of the HoA1, the Co-CoA5 and the interface IF 1. The HA updates the information of the binding BID1 corresponding to the interface IF1 of the MN. And then sending a binding revocation request message to the first network node, wherein the binding revocation request message carries HoA1, GFA-CoA, revoked binding BID1 information and the like of the MN.

And the second network node sends a registration request message to the HA, wherein the registration request message carries the identifier of the MN, the HoA1, the GFA-CoA and the new binding identifier BID 2. Thus recreating the BID2 related binding on the HA.

EXAMPLE six

In this embodiment, when the GFA/FA receives multiple registration requests carrying BID sent via different interfaces, the GFA/FA establishes a corresponding binding for each interface. Then, the GFA/FA forwards the plurality of registration requests to the HA, and adds specific indication information into each registration request, so that the HA can distinguish the registration requests from different interfaces according to the indication information and can respectively establish binding for different registration requests.

Compared with the above embodiments 1-5, the GFA/FA in this embodiment is relatively simple to process the request for establishing multi-binding of the MN, and only needs to establish the binding registered for each interface, i.e., it is not necessary to distinguish between the inbound binding and the outbound binding; then, the GFA/FA passes all registration messages (including registration messages of multi-binding registration, flow registration, interface switching, flow switching, etc.) to the HA, and adds specific indication information to each registration request, so that the HA can distinguish the registration requests with the same HoA and CoA and different BIDs from different interfaces according to the indication information, and can establish binding for different registration requests respectively.

The processing flow of the GFA/FA request for establishing multi-binding to MN provided by this embodiment is as shown in fig. 9, and includes the following processing steps:

at step 91, the MN sends a registration request message to the first network node via interface IF 1.

An interface IF1 of the MN is attached to a network, and after access authentication is completed through a network starting process, HoA1, CoA1 address information and the like are acquired. The MN then sends a registration request message to the first network node via interface IF1, the registration request message carrying the binding identity BID1 generated for interface IF1, and information of the HoA, CoA1 and some other registration requests (e.g., security parameters).

If the system is a mobile IPv4 system, the CoA1 is FA-CoA or Co-CoA, and the registration request is a home registration message; in case of hierarchical mobile IPv4 system, the CoA1 information includes GFA-CoA and local LCoA (LCoA is FA-CoA or Co-CoA), and the registration request is a home registration message or a regional registration message.

Step 92, the first network node establishes binding for interface IF1 of MN, and sends registration request message carrying identification information of interface IF1 to the second network node.

After receiving the registration request message, the first network node checks whether the interface IF1 is registered on the first network node, and IF so, the first network node updates the binding for the interface to be registered; otherwise, a binding is established for the interface IF1 of the MN, including binding information HoA1, CoA1, and binding identification BID1 of the MN.

Then, the first network node sends a registration request message to the second network node, where the registration request message carries the binding information of interface IF1 of MN, and adds the identification information of interface IF1 in the binding identification option, where the identification information of interface IF1 includes indication information for indicating registration of interface IF1 or link layer identification of interface IF 1.

Taking hierarchical MIPv4 as an example, an indication bit can be extended in the binding identification option, and this is indicated by the indication bit that this is multi-binding registration in hierarchical mobile IP system with GFA as interface IF1 of MN.

In practical applications, the link-layer identity of interface IF1 of the MN may also be inserted by the first network node in a registration request message sent to the HA. Since the link layer identifiers of each interface of the MN are different from each other, the HA can distinguish different bindings according to the link layer identifier of the interface.

After receiving the registration request message, the second network node searches the existing binding of the MN according to the identifier of the MN, the HoA, the BID and the like, performs matching, determines the existing binding as a new binding at the moment, and accordingly creates the binding for the MN.

Optionally, before establishing the binding, the second network node performs uniqueness check on the (HoA, CoA) of the MN together with specific indication information (such as the indication bits in the binding identifier option, the link layer identifier of the interface, and the like) in the registration request, and if the two are the same, rejects the registration request and replies with a failed response message; otherwise, the registration request is accepted and further processed. After the processing is completed, a bidirectional tunnel is established with the first network node so as to forward the message of the MN. At this time, the second network node returns a registration response message to the MN through the first network node, and completes the registration process.

The first network node also performs the processing steps corresponding to interface IF1 described above when subsequently receiving the registration request message sent by interface IF2 and interface IF3 of the MN.

The embodiment of the present invention further provides a device for performing mobile IP registration by a multi-interface mobile node, where the device is a first network node, and a schematic structural diagram of the device is shown in fig. 10, and the device includes the following modules:

a registration request receiving module 101, configured to receive a first registration request sent by a mobile node, where the first registration request carries a first binding identifier of an interface to be registered;

a registration request processing module 102, configured to send a second registration request to a second network node according to the first registration request and when the first network node does not have registration information of other interfaces on the mobile node, where the second registration request carries a second binding identifier allocated to the mobile node or interface identifier information of the interface to be registered. The interface identification information includes indication information for indicating interface registration or a link layer identification of the interface.

The registration request processing module 102 is specifically configured to, when there is no registration information of other interfaces on the mobile node on the first network node, establish an inbound binding including the first binding identifier and an outbound binding including the second binding identifier allocated to the mobile node for the interface to be registered, where the second binding identifier is the same as or different from the first binding identifier; sending a second registration request to the second network node carrying a second binding identifier assigned to the mobile node.

The registration request processing module 102 may further include: at least one of a first processing module 1021 and a second processing module 1022, wherein,

a first processing module 1021, configured to establish an inbound binding including the first binding identifier for the interface to be registered when the mobile node has interface registration information on the apparatus;

a second processing module 1022, configured to check whether the interface to be registered is already registered on the device, and if so, update a binding for the interface to be registered; otherwise, establishing binding for the interface to be registered; and sending a second registration request carrying the interface identification information of the interface to be registered to the second network node.

The first network node may be a gateway foreign agent, and the second network node is a home agent; or, the first network node is a foreign agent, and the second network node is a home agent or a gateway foreign agent.

For example, in the hierarchical mobile IPv4 system shown in fig. 3, the first network node is a GFA/FA, and the second network node is an HA.

The specific processing procedure of the registration request processing module mainly includes: when the registration request receiving module receives the first registration request, the registration request processing module checks that the first network node has no registration information of other interfaces on the mobile node, that is, the first registration request is the first registration request sent by the mobile node to the first network node.

Then, the registration request processing module sends a second registration request to a second network node, where the second registration request carries a second binding identifier allocated to the mobile node or interface identifier information of the interface to be registered.

Further, the process of sending the second registration request to the second network node by the registration request processing module specifically includes:

the registration request processing module establishes an inbound binding containing the first binding identifier and an outbound binding containing the second binding identifier allocated to the mobile node for the interface to be registered. In fig. 3, the outbound binding is represented by MN binding X, which is common to all interfaces of the mobile node, and includes binding information for requesting registration of the mobile node. The second binding identifier is the same as or different from the first binding identifier.

The registration request processing module sends a second registration request to the second network node carrying a second binding identifier assigned to the mobile node.

And then, when the mobile node sends a registration request to the first network node through other interfaces, wherein the registration request carries the binding identifiers of other interfaces. Since the interface to be registered is registered with the first network node, the first network node checks that the mobile node has interface registration information on the first network node, and then the first network node establishes an inbound binding including a binding identifier of the other interface for the other interface. And does not establish a binding for the other interface nor send a second registration request to the second network node.

Further, when the first registration request further includes: and when the flow is initially registered on the first network node, the first network node sends a second registration request to a second network node, wherein the second registration request carries the flow information on the mobile node.

When the flow on the mobile node is switched between interfaces in a visiting network where the first network node is located, the mobile node performs switching registration, at the moment, the first network node only performs updating on the corresponding incoming binding, the content of the outgoing binding is not changed, the outgoing binding is not updated, and the first network node does not send a registration request to the second network node;

when an interface on a mobile node moves in a visited network where the first network node is located, the CoA on the interface is changed, the mobile node performs switching registration, at the moment, the first network node updates only the corresponding incoming binding, the content of the outgoing binding is not changed, the outgoing binding is not updated, and the first network node does not initiate registration update to the second network node;

when a flow or an interface on the mobile node moves between interfaces of a visiting network crossing the first network node, the mobile node performs switching registration, at this time, the first network node updates the corresponding incoming binding, the content of the outgoing binding is also updated at the same time, the outgoing binding needs to be updated, and the first network node initiates registration update to the second network node. And if the flow is switched to an interface outside the domain of the first network node or the interface moves to the outside of the domain of the first network node, the first network node deletes the flow information in the binding or deletes the binding corresponding to the interface.

The embodiment of the present invention further provides a device for regional mobile IP registration, which is applied to a situation that a mobile node in a domain where the device is located sends a regional registration request to the device, and a schematic structural diagram of the device is shown in fig. 11, where the device includes the following modules:

a regional registration request receiving module 111, configured to receive a regional registration request sent by a mobile node, where the registration request carries a binding identifier of an interface to be registered, and the regional registration request is a registration request in a domain where the first network node is located.

A binding establishing module 112, configured to create or update a binding entry of the mobile node according to the registration request received by the regional registration request receiving module.

The area registration request may also carry flow identification information.

The apparatus may further include:

a region logout request processing module 113, configured to send a region logout request to the mobile node, where the region logout request carries the binding identifier information or the flow identifier information.

The device may be a gateway foreign agent or a foreign agent.

The embodiment of the invention also provides a system for mobile IP registration, which is characterized by comprising the following steps:

the first network node is used for receiving a first registration request sent by the mobile node, wherein the first registration request carries a first binding identifier of an interface to be registered; and sending a second registration request to a second network node according to the first registration request and when the first network node does not have the registration information of other interfaces on the mobile node, wherein the second registration request carries a second binding identifier distributed to the mobile node or the interface identifier information of the interface to be registered.

And the second network node is used for receiving a second registration request sent by the first network node and registering the mobile node according to a second binding identifier carried in the second registration request or the interface identifier information of the interface to be registered.

The first network node is a gateway external agent, and the second network node is a home agent;

or,

the first network node is a foreign agent, and the second network node is a home agent or a gateway foreign agent.

For example, in the networking diagram shown in fig. 7, the first network node is a foreign agent, and the second network node is a home agent.

The specific processing procedure of the first network node mainly includes:

when the first network node receives the first registration request, the first network node checks that the first network node has no registration information of other interfaces on the mobile node, that is, the first registration request is the first registration request sent by the mobile node to the first network node. Then, the first network node establishes an inbound binding including the first binding identifier and an outbound binding including the second binding identifier allocated to the mobile node for the interface to be registered. And then, sending a second registration request to a second network node, wherein the second registration request carries a second binding identifier allocated to the mobile node or interface identifier information of the interface to be registered.

The specific processing procedure of the second network node mainly includes: after receiving the second registration request, the second network node registers the mobile node according to a second binding identifier carried in the second registration request or the interface identifier information of the interface to be registered, creates a binding for the mobile node, and establishes a bidirectional tunnel with the first network node so as to forward a message of the mobile node. Then, the second network node returns a registration response message to the mobile node through the first network node, and the registration process of the interface to be registered of the mobile node is completed.

In summary, the embodiments of the present invention provide the MN with the ingress-egress binding hierarchical binding through the GFA/FA in the hierarchical MIPv4 system (MIPv4 system), so as to ensure that multiple interfaces of the MN can successively attach and register to the network where the GFA/FA is located, thereby enabling the MN to obtain more bandwidth and enabling the existing session of the MN to continue.

When the MN performs flow switching or interface switching in the domain where the GFA/FA is located, only the incoming binding of the MN can be updated, but not the outgoing binding of the MN, so that the delay of flow switching or interface switching is saved, and the signaling load of a network is reduced.

By adding the local registration request message in the mobile IPv4 system, the multi-interface MN can perform local registration to the FA in the processes of flow registration, flow switching and the like in the FA domain.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.

The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (9)

1. A method of mobile IP registration, comprising:

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;

when the first network node does not have the registration information of other interfaces on the mobile node, the first network node sends a second registration request to a second network node according to the first registration request, wherein the second registration request carries a second binding identifier distributed to the mobile node;

the step of sending, by the first network node, the second registration request to the second network node specifically includes: the first network node establishes an incoming binding containing the first binding identifier and an outgoing binding containing the second binding identifier for the interface to be registered, and the outgoing binding is common to all interfaces of the mobile node; the first network node sends a second registration request carrying the second binding identifier to the second network node;

when the first network node has the registration information of other interfaces of the mobile node, the first network node establishes an incoming binding containing the first binding identifier for the interface to be registered, and the interface to be registered shares the outgoing binding of other interfaces of the mobile node on the first network node.

2. The method of claim 1, wherein when the first registration request further includes information of flows at the mobile node, the method further comprises:

when the flow on the mobile node is initially registered on the first network node, the first network node sends a second registration request to a second network node, and the second registration request carries the flow information on the mobile node.

3. The method of mobile IP registration according to claim 1, wherein the method further comprises:

checking whether the interface to be registered is registered on the first network node, if so, updating binding for the interface to be registered by the first network node; otherwise, the first network node establishes binding for the interface to be registered;

and the first network node sends a registration request carrying the interface identification information of the interface to be registered to the second network node.

4. A method for mobile IP registration according to any of claims 1 to 3, characterized by: the first network node is a gateway external agent, and the second network node is a home agent;

or,

the first network node is a foreign agent, and the second network node is a home agent or a gateway foreign agent.

5. An apparatus for mobile IP registration, comprising:

a registration request receiving module, configured to receive a first registration request sent by a mobile node, where the first registration request carries a first binding identifier of an interface to be registered;

a registration request processing module, configured to send a second registration request to a second network node according to the first registration request when the device does not have registration information of other interfaces on the mobile node, where the second registration request carries a second binding identifier allocated to the mobile node;

the registration request processing module is specifically configured to establish, for the interface to be registered, an inbound binding including the first binding identifier and an outbound binding including the second binding identifier, where the outbound binding is common to all interfaces of the mobile node; sending a second registration request carrying the second binding identifier to the second network node;

the registration request processing module further comprises: a first processing module, configured to establish an inbound binding including the first binding identifier for the interface to be registered when there is registration information of other interfaces of the mobile node on the device, where the interface to be registered shares an outbound binding of other interfaces of the mobile node on the first network node.

6. The apparatus of claim 5, wherein:

the device is a gateway external agent or an external agent.

7. The apparatus of claim 5 or 6, wherein the registration request processing module further comprises: the second processing module is used for checking whether the interface to be registered is registered on the device, and if so, updating binding for the interface to be registered; otherwise, establishing binding for the interface to be registered; and sending a second registration request carrying the interface identification information of the interface to be registered to the second network node.

8. A system for mobile IP registration, comprising:

the first network node is used for receiving a first registration request sent by the mobile node, wherein the first registration request carries a first binding identifier of an interface to be registered; when the first network node does not have the registration information of other interfaces on the mobile node, sending a second registration request to a second network node according to the first registration request, wherein the second registration request carries a second binding identifier allocated to the mobile node; the step of sending the second registration request to the second network node specifically includes: the first network node establishes an incoming binding containing the first binding identifier and an outgoing binding containing the second binding identifier for the interface to be registered, and the outgoing binding is common to all interfaces of the mobile node; the first network node sends a second registration request carrying the second binding identifier to the second network node; when the first network node has the registration information of other interfaces of the mobile node, the first network node establishes an incoming binding containing the first binding identifier for the interface to be registered, and the interface to be registered shares the outgoing binding of other interfaces of the mobile node on the first network node;

and the second network node is used for receiving a second registration request sent by the first network node and registering the mobile node according to a second binding identifier carried in the second registration request or the interface identifier information of the interface to be registered.

9. A system for mobile IP registration according to claim 8, wherein:

the first network node is a gateway external agent, and the second network node is a home agent;

or,

the first network node is a foreign agent, and the second network node is a home agent or a gateway foreign agent.