CN102843667A - Method for deploying subnet mobile in separation mechanism mobility management system - Google Patents

Abstract

The invention relates to a method for deploying subnet mobile in a separation mechanism mobility management system. The method comprises the following steps of expanding a separation mechanism mobility management system, expanding the functions of AGW (access gateway), CGW (control gateway) and DGW (data gateway) in the system, and modifying the signaling interacted between entities to support the subnet mobile. In order to support preamble proxy, a DHCP (dynamic host configuration protocol) relay proxy is deployed on the AGW, a DHCP server is deployed on the CGW, and a mobile router (MR) is used as a DHCP client, so that the preamble can be allocated for an MNN (mobile network node) through correct interaction by the AGW and the DHCP relay proxy. According to the method provided by the invention, the mobility management network based on the separation mechanism is combined with the subnet mobile, so that the communication under the condition that the MR carriers an LFN (local fixed node) is realized; the DHCPv6 preamble proxy is supported, the preamble is allocated for the LFN by using dynamic address allocation, thus, the utilization of the address is increased, and the configuration of client TCP/IP (transmission control protocol/Internet protocol) is greatly simplified.

Description

A kind of method that the deployment subnet moves in the separation mechanism mobility management systems

Technical field

The present invention relates to a kind of method that subnet moves of in the separation mechanism mobility management systems, disposing.

Background technology

Along with the quick growth of Wi-Fi handheld terminal with to the growth of internet access demand, the NEMO technology that can manage a group node receives much concern.In order to support NEMO, the RFC3963 standard basic NEMO supported protocol (NEMO-BSP), but this agreement is the support to NEMO among the MIPv6.Along with the appearance of the PMIPv6 of management Network Based, IETF MEXT and IETF NETEXT working group also proposed some drafts, supported in PMIPv6, carrying out NEMO.

(application number: 201110152731) proposed a kind of new mobility management protocol, be called the separation mechanism mobility management systems, this system has excellent function, performance and extensibility, but does not support that subnet moves in patent application.

1.2 the prior art one relevant with the present invention

(application number: the network model of the separation mechanism mobile management that 201110152731) proposes is as shown in Figure 1 in patent application.This scheme has proposed three kinds of separation mechanisms: promptly identity is separated with control plane with position separating, datum plane, Access Network separates with core net.This scheme has defined three new functional entitys: IAD (Access GateWay, AGW), control gateway (Control GateWay, CGW) and data gateway (Data GateWay, DGW).

Home address (constant in an Access Network, as to be HoA) through mobile node MN being respectively applied for the sign identity information separates and realizes identity and position separating with access address PCoA (difference according to the AGW that inserts changes);

Separate with the core address that is used for the core net route through the home address that will be used to identify the MN identity information and to realize separating of Access Network and core net;

Through mobility signaling management function and the data route forwarding function refinement of LMA among the PMIPv6 are decomposed: separate into control gateway, realize mobility signaling management function; Data gateway is realized the data route forwarding function.Thereby realize that control plane separates with datum plane.

1.2.1 the shortcoming of prior art one

One of technical scheme is a kind of management method of mobile, does not relate to subnet and moves.Owing to being based on the PMIPv6 agreement, the mobility in the separation mechanism mobility management systems comes; And PMIPv6 the interior single node of support region is mobile; Do not support moving of a group node; Therefore the separation mechanism mobility management systems is not supported moving of a group node yet, and it can only guarantee that a node moves freely and keeps node IP address constant in separation mechanism mobile management territory.

1.3 the prior art two relevant with the present invention

PMIPv6 provides the network connectivty of PMIPv6 territory interior nodes; Because present PMIPv6 standard is only supported the mobility of main frame; Thereby IETF has proposed draft and solves and in PMIPv6, support the problem that subnet moves; And mobile network node (Mobile Network Node, network connectivty MNN) in the assurance mobile subnetwork.

This draft is called the PNEMO agreement with the agreement that based on network support subnet moves, and this agreement is an expansion of PMIPv6 agreement.In this agreement, MR does not participate in Signalling exchange, and signaling message is mutual between MAG and LMA.MR is VMN (Visited Mobile Node) and LFN (Local Fixed Node) transceive data bag.Simultaneously MR also notifies the state of subnet to LMA and MAG.

The MR of the description that draft is detailed is with LFN, subnet is nested and the access of VMN and handoff scenario.The operation of MAG and LMA has also been described simultaneously.

1.4.1 the shortcoming of prior art two

PMIPv6 can only realize limited identity and position separating in the territory; LMA should the processing controls signaling in the process of management mobile subnetwork, transmit again from the packet that mails to mobile subnetwork; Cause LMA to become the single fault node in the PMIPv6 network configuration easily, can't ensure reliability.This subnet moves scheme and is based on the PMIPv6 agreement simultaneously, have have that IP address ambiguity brings defective.

1.4.1 the prior art three relevant with the present invention

Like RFC 3315 (R.Droms, Ed., J.Bound; B.Volz; T.Lemon, C.Perkins, M.Carney. " Dynamic Host Configuration Protocol for IPv6 (DHCPv6) " .RFC 3315; July 2003.) the middle description, Dynamic Host Configuration Protocol server uses the DHCPv6 agreement to provide such as configuration informations such as the IPv6 network addresss to the IPv6 node.It can distribute automatically can the reusable network address and other configuration informations.

In mobile subnetwork; MNN receives mobile network's prefix (Mobile Network Prefix through MR; MNP), the DHCPv6 prefix proxy just can distribute one or more prefixs for the mobile router on the link, but proxy mobile IPv 6 is not but supported the DHCPv6 prefix proxy.Draft (A.Petrescu; M.Boc, C.Janneteau, " Network Mobility with Proxy Mobile IPv6 "; Draft-petrescu-netext-pmip-nemo-00.txt; March 5,2012.) described a kind ofly in proxy mobile IPv 6, use the DHCPv6 prefix proxy to distribute the method for prefix as mobile subnetwork.When using the DHCPv6 prefix proxy to distribute prefix, these prefixs need be bound in PMIPv6.

Here Dynamic Host Configuration Protocol server of describing among the RFC 3315 under the brief account and the Signalling exchange between the dhcp client.Interacting message between this two is divided into four signalings and hands over (four-message handshake) and two signalings friendship (two-message handshake) two kinds of situation.Two kinds of interacting messages are as shown in Figure 2.

When a dhcp client needs server to give its distributing IP address,, need carry out four-message handshake in order to obtain the IP address.

When a dhcp client does not need Dynamic Host Configuration Protocol server to give his distributing IP address; Dhcp client can be through obtaining some like the available dns server and the configuration information of ntp server, just two-message handshake with the mutual single request of Dynamic Host Configuration Protocol server with response message.

In order to allow dhcp client to send message, can use dhcp relay agent (DHCP relay agent) to transmit the message between Dynamic Host Configuration Protocol server and the dhcp client to the Dynamic Host Configuration Protocol server on same link not.The operation of dhcp relay agent is transparent for dhcp client.Dhcp relay agent can allow not, and the Dynamic Host Configuration Protocol server on same link and dhcp client communicate.

1.3.1 the shortcoming of prior art three

Under the described situation of this draft, LMA not only needs the processing controls signaling also will transmit packet, when LMA breaks down, can cause network paralysis, just poor reliability to occur.Equally, this prefix broker case also is based on the PMIPv6 agreement, has the intrinsic defective of IP address ambiguity.

Summary of the invention

For solving the deficiency of above prior art; The present invention proposes the management method that a kind of subnet in the separation mechanism mobility management systems moves; The separation mechanism mobile management is combined with the subnet mobile phase; Utilize the characteristics of separation mechanism mobile management, designed a kind of method that subnet moves of in the separation mechanism mobility management network, disposing.This method can be carried out mobile management to the group node in the separation mechanism network, supports the DHCP prefix proxy simultaneously.

The object of the invention is realized through following technical scheme:

A kind of method that the deployment subnet moves in the separation mechanism mobility management systems, this method comprises the steps:

Step 1:MR is linked into AGW1; (Access Point is so the entering transmission log information that AP) detects MR is to AGW1, after AGW1 receives log information for the last WAP of AGW1; The access style of decision node; Be mobile router or mobile node, and obtain the ID of corresponding access node, accomplish that the mobile management process on the AGW1 is in wait state after these work;

Step 2:MR then sends DHCPv6 CONFIRM message to dhcp relay agent;

After DHCP CONFIRM message is received by step 3:DHCP relay agent, send DHCPv6 RELAY FORWARD message to Dynamic Host Configuration Protocol server;

After step 4:DHCP server is received this message, judge whether the address of carrying in the message is available, if available, then returning a status code to dhcp relay agent is 0 DHCP RELAY REPLY message;

After message was received by step 5:DHCP relay agent, the status code that judges in the message was 0, informed that then the mobile management process on the AGW1 can be sent agent binding update PBU message;

Step 6:AGW1 sends PBU message to CGW1, newly-increased MNP option and R flag bit in the PBU message, and AGW1 goes up and sets up the BUL relevant with MR simultaneously;

Step 7:CGW1 resolves after receiving PBU message, if legal, then send the tunnel and sets up request message TxReq to DGW1, and also newly-increased MNP option and R flag bit in this message, CGW1 goes up and sets up the BCE relevant with MR simultaneously;

After step 8:DGW1 receives and resolves after the TxReq message, set up one and point to the tunnel of AGW1, and return a tunnel acknowledge message TxAck, and on DGW1, set up the TCE relevant, the route that interpolation is relevant with HNP and MNP with MR to CGW1 by DGW1;

Step 9:DGW1 inquires about the address pool on it; For HNP and MNP distribute corresponding core address; And the corresponding relation of corresponding relation, MNP and the core address of HNP and core address is injected in the kernel of DGW1 and goes; Also these two pairs of mapping relations are included in the map updating message simultaneously and issue GMS, carry out up-to-date record;

After step 10:CGW1 receives TxAck message, just send the proxy binding acknowledgment messages PBA that comprises HNP and R flag bit to AGW1;

After step 11:AGW1 receives PBA message, DHCP process this moment can send DHCP REPLY message to MR all over informing;

Step 12:AGW1 parses the HNP information in the PBA message; Announce to MR through advertising of route RA; Set up the other end that is pointed to the tunnel of DGW1 by AGW1 simultaneously, and add the route about HNP and MNP, MR receives behind the HNP home address that generates oneself according to EUI-64;

After the notice that AGW1 sends is received by step 13:DHCP relay agent, just send DHCP REPLY message to MR;

After step 14:MR receives DHCP REPLY message, the MNP that DHCP distributes is announced to LFN through RA message;

Step 15: after MR obtains home address HoA1, LFN acquisition subnet address MNP, can send packet, suppose that here CN also accomplishes corresponding steps to the CN that is positioned at Access Network 2; The home address that obtains at Access Network 2 is HoAn; Make LFN initiate communication to CN, packet is transmitted through MR and at first is sent to AGW1, and data packet format is { HoAn; MNP, data };

Step 16:AGW1 is { DGW1_addr, PCoA, { HoAn with packet encapsulation; MNP, data } } form, and packet is sent to DGW1 through bidirectional tunnel; Wherein PCoA1 also be the current access of MR AGW1 act on behalf of Care-of Address, DGW1_addr is the address of DGW1 in the Access Network side;

Step 17:DGW1 at first carries out decapsulation to it after receiving packet, and packet is reduced to { HoAn; MNP; Data } form, then DGW1 carries out the inquiry of mapping relations, this moment, DGW1 went up two corresponding core addresses of MNP of the HNP1 that has only MR and the LFN of storage; At first inquire about local mapping table the source address MNP of packet is inquired about, obtain corresponding core address 1; Yet DGW1 is the information of not relevant with HoAn core address n at this moment, so DGW1 need obtain the corresponding core address of HoAn with response message with the inquiry of GMS interactive map;

Step 18:DGW1 and inquiry of GMS interactive map and response message obtain the corresponding core address n of HoAn;

Step 19:DGW1 is after having obtained the needed core map addresses of packet information, and then source address and the destination address to packet shines upon replacement, has replaced the back data packet format and has been { core address n, core address 1, data }, and be sent to DGW2;

After step 20:DGW2 receives packet, and do not know the information of the home address that core address 1 is corresponding, so DGW2 inquires about with the GMS interactive map and response message obtains the corresponding MNP in core address 1; DGW2 just separates the mapping replacement to source address, the destination address of packet after obtaining corresponding mapping relations, the data packet format of separating after the mapping is { HoAn, MNP, data };

Step 21:DGW2 since set up and AGWn between bidirectional tunnel, then directly packet is carried out tunnel encapsulation, data packet format is { PCoAn, DGW2_addr, { HoAn, MNP, data } }, and packet is sent to AGWn via the tunnel;

Step 22:AGWn carries out the tunnel decapsulation to packet after receiving packet, the data packet format after the decapsulation { HoAn, MNP, data }, and packet sent to MN.

The invention has the advantages that:

1. the present invention will combine with the subnet mobile phase based on the mobility management network of separation mechanism; The separation mechanism mobility management systems is expanded; Respectively AGW, CGW, DGW are carried out the function expansion, inter-entity interactive signaling message is expanded, support subnet to move.

2. the present invention supports the DHCPv6 prefix proxy, provide the DHCP related entities deployment and with the method for separation mechanism system interaction.And subnet moved with separate mapping network combine, realized that MR carries the communication under the LFN scene.

3. the present invention supports the DHCPv6 prefix proxy, uses dynamic address allocation to distribute prefix as LFN, and the utilance that has increased the address also can be simplified the configuration of client TCP/IP greatly.

4. the present invention can support a group node in the separation mechanism network domains, to move freely and keep communication continuity, and the user can move between the diverse access point in the big zone.

Description of drawings

Fig. 1: existing separation mechanism mobile network figure;

Fig. 2: four signalings and two Signalling exchange flow charts;

Fig. 3: the subnet mobile management network topological diagram that the present invention is based on separation mechanism;

Fig. 4: based on the mobile management figure of separation mechanism subnet;

Fig. 5: dispose the system flow chart that subnet moves in the separation mechanism mobility management systems.

Embodiment

Subnet mobile management network topology based on separation mechanism of the present invention is as shown in Figure 3.What the present invention mainly considered is in the separation mechanism mobility management systems, to dispose the scene of MR with attached LFN, supports the DHCPv6 prefix proxy simultaneously.The present invention is deployed in Dynamic Host Configuration Protocol server on the CGW, and dhcp relay agent is deployed on the AGW, and dhcp client is deployed on the MR.

To introduce ins and outs of the present invention from subnet description, functional entity and division and three aspects of mobile messaging formal definition below.

Subnet is described

When the present invention disposes subnet and moves in the separation mechanism mobility management systems, consideration be the mobile management of whole subnet, comprise MR and LFN, as shown in the figure:

Wherein, MR is the mobile router of definition in [RFC 3963], and LFN (Local Fixed Node) is the mobile node that is under the jurisdiction of MR, and it can only be followed MR and move together.For MR, (Home Network Prefix, HNP), and HNP is constant when MR moves in the separation mechanism territory to need to distribute a specific home network prefix.LFN is with the MNP configuration address that belongs to specific NEMO.In this case, DGW is not merely the packet that MR is redirected MR, also will be redirected the packet of the LFN that belongs to MNP.

Functional entity is divided and expansion

In the separation mechanism mobility management systems, dispose subnet and move and need expand, introduce in detail below the functional entity in the separation mechanism mobility management systems:

（1）AGW

AGW is positioned at the Access Network edge, the MAG of similar PMIPv6 on the function.AGW detects the access of MR and leaves; And replace MR and CGW to carry out the mutual of mobile signaling protocol, and and needing to increase MNP option and R flag bit newly in the mutual PBU message of CGW, the MNP option is used for carrying the mobile subnetwork prefix; The R flag bit is 1 o'clock; What expression inserted is mobile subnetwork, is that what represented in 0 o'clock to insert is single mobile node, needs newly-increased R flag bit in the PBA message.It is that MR still is MN so that carry out different disposal that while AGW needs to distinguish access node.AGW need set up the tunnel with DGW, and next bar address of LFN in the mobile subnetwork also will be arranged above it, also wants can transmit the packet from subnet the data transmit-receive of responsible MR and LFN.

AGW need safeguard the tabulation of Binding Update (Binding Update List BUL), needs to increase the mobile subnetwork prefix option and store the content relevant with MNP among the BUL, concrete data structure is following, and wherein DGW1 is the address of DGW in the Access Network side:

Table 1

Care-of Address	Home address	The mobile subnetwork prefix	The data gateway address
				PCoA1	HNP1	MNP	DGW1

（2）CGW

CGW need accomplish the function of the control plane of LMA among the PMIPv6, be responsible for and AGW between carry out Signalling exchange, the auxiliary mobile management of accomplishing MR.CGW and DGW set up in mutual tunnel needs newly-increased MNP option and R flag bit in the request message (TxReq), the tunnel is set up needs newly-increased R flag bit in the response message (TxAck).CGW need safeguard banding cache clauses and subclauses (Binding Cache Entries, BCE), need increasing the mobile subnetwork prefix option among the BCE, to store the concrete data structure of the content relevant with MNP following:

Table 2

（3）DGW

DGW accomplishes the data plane functions of the LMA among the PMIPv6, is responsible for setting up communication tunnel with AGW, and the packet that mails to MR and LFN finally all is addressed to DGW, and DGW transmits the packet that mails to mobile subnetwork.DGW therefore need to safeguard a tunnel cache entries tabulation (Tunnel Cache Entries, TCE), needing to increase the mobile subnetwork prefix option among the TCE, to store the concrete data structure of the content relevant with MNP as follows:

Table 3

MN identity descriptor	Home address	Care-of Address	The data gateway address	The mobile subnetwork prefix
					mn1example	HoA1	PCoA1	DGW1	MNP1
mn2example	HoA2	PCoA2	DGW1	MNP2

（4）LMS

On the other hand; DGW also is local mapping server simultaneously; The HoA of local all MR of record and the corresponding core address of MNP when Access Network mails to core net via DGW, all will be inquired about local map listing (the Local Mapping List on the local mapping server from the packet of MR and MNN; LML), source address HoA/MNP is replaced to corresponding core address.DGW also is responsible for upgrading and query messages with the GMS interactive map.If local mapping table does not have corresponding list item, inquire about to GMS.When mobile subnetwork inserts or leaves, also to send the information updating map listing in the map listing of DGW on upgrading LMS to GMS.The concrete data structure of local map listing is following:

Table 4

The core address	Access address
		Core address 1	HNP1
Core address 2	HNP2

Core address 3

MNP

（5）GMS

The global map department server is deployed in core network; The main core map addresses query function of accomplishing the overall situation; When packet mail to core net via DGW, GMS of packets need inquiry, GMS need safeguard a global map tabulation (Global Mapping List who comprises mapping relations between all HoA of the overall situation and MNP and the core address; GML), concrete data structure is following:

Table 5

The core address	Access address
		Core address 1	HNP1
Core address 2	HNP2
		Core address 3	HNP3
Core address 4	MNP

2.2.3 mobile messaging formal definition

In the subnet moving process; AGW need comprise MNP (the Mobile Node Prefix) information of mobile subnetwork in the agent binding update messages that CGW sends; Need expand agent binding update messages, increase the MNP option, the agent binding update messages form of expansion is as shown in table 6.

Table 6

The MNP mobile option that increases in the agent binding update messages is used to carry the prefix information of LFN, the MNP mobile option with reference among the RFC 5213 about the definition of HNP.

Equally, CGW is set up request message and also will expand to what DGW sent, comprise the MNP option, the tunnel of expansion is set up shown in the request message table 7.

Table 7

The MNP mobile option that the tunnel request of setting up increases is used to carry the prefix information of LFN, the MNP mobile option with reference among the RFC 5213 about the definition of HNP.

In the face of in this system, using the signaling process and the data interaction flow process of DHCP prefix proxy to introduce, flow process is as shown in Figure 5 down.In conjunction with Fig. 3-4, sending packet with the MR that is positioned at Access Network 1 to the CN that is positioned at Access Network 2 is example, gets into Access Network 1 beginning from MR, begins to introduce the mutual basic procedure of mobile signaling protocol described in the invention.For DHCPv6, as describing among the RFC 3315, the DHCPv6 process comprises the mutual and mutual two kinds of situation of four-message of two-message, and the present invention all supports both of these case, only introduces the mutual situation of two-message here.

For the mutual situation of four-message, only need a step 2 as described below replace to the mutual flow process of four-message among Fig. 2 to step 4, add again use dhcp relay agent situation.In step 5 as described below; When being that four-message is when mutual; Need judge and whether comprise IA-NA option (having carried the prefix that Dynamic Host Configuration Protocol server distributes to node in this option) among the DHCP RELAY REPLY that receives; If comprise, inform that then the mobile management process on the AGW1 is sent PBU message.Here no longer to using the mutual situation of four-message to distribute the situation of prefix to give unnecessary details in the separation mechanism mobility management systems as the node in the mobile subnetwork.

Step 1:MR is linked into AGW1, sends log information to AGW1 so the last AP of AGW1 detects the entering of MR.After AGW1 received log information, the access style of decision node was mobile router or mobile node, and obtains the ID of corresponding access node, accomplished that the mobile management process on the AGW1 just is in wait state after these work.

Step 2:MR then sends DHCPv6 CONFIRM message to dhcp relay agent.

After DHCP CONFIRM message is received by step 3:DHCP relay agent, send DHCPv6 RELAY FORWARD message to Dynamic Host Configuration Protocol server.

After step 4:DHCP server is received this message, judge whether the address of carrying in the message is available, if available, then returning a status code to dhcp relay agent is 0 DHCP RELAY REPLY message.

After message was received by step 5:DHCP relay agent, the status code that judges in the message was 0, informed that then the mobile management process on the AGW1 can be sent agent binding update (PBU) message.

Step 6:AGW1 sends PBU message to CGW1, newly-increased MNP option and R flag bit in the PBU message, and AGW1 goes up and sets up the BUL relevant with MR simultaneously.

Step 7:CGW1 resolves after receiving PBU message, if legal, then send the tunnel to DGW1 and sets up request message (TxReq), also newly-increased MNP option and R flag bit in this message.CGW1 goes up and sets up the BCE relevant with MR simultaneously.

After step 8:DGW1 receives and resolves after the TxReq message, set up one and point to the tunnel of AGW1, and return a tunnel acknowledge message (TxAck), and on DGW1, set up the TCE relevant, the route that interpolation is relevant with HNP and MNP with MR to CGW1 by DGW1.

Step 9:DGW1 inquires about the address pool on it; For HNP and MNP distribute corresponding core address; And the corresponding relation of corresponding relation, MNP and the core address of HNP and core address is injected in the kernel of DGW1 and goes; Also these two pairs of mapping relations are included in the map updating message simultaneously and issue GMS, carry out up-to-date record.

After step 10:CGW1 receives TxAck message, just send the proxy binding acknowledgment messages (PBA) that comprises HNP and R flag bit to AGW1.

After step 11:AGW1 receives PBA message, DHCP process this moment can send DHCP REPLY message to MR all over informing.

Step 12:AGW1 parses the HNP information in the PBA message; Announce to MR through advertising of route (RA); Set up the other end that is pointed to the tunnel of DGW1 by AGW1 simultaneously, and add the route about HNP and MNP, MR receives behind the HNP home address that generates oneself according to EUI-64.

After the notice that AGW1 sends is received by step 13:DHCP relay agent, just send DHCP REPLY message to MR.

After step 14:MR receives DHCP REPLY message, the MNP that DHCP distributes is announced to LFN through RA message.

Step 15: after MR obtains home address HoA1, LFN acquisition subnet address MNP, can send packet to the CN that is positioned at Access Network 2.Here suppose that CN also accomplishes corresponding steps, the home address that obtains at Access Network 2 is HoAn.Make LFN initiate communication to CN, packet is transmitted through MR and at first is sent to AGW1, and data packet format is { HoAn, MNP, data }.

Step 16:AGW1 is { DGW1_addr, PCoA, { HoAn with packet encapsulation; MNP, data } } form, and packet is sent to DGW1 through bidirectional tunnel; Wherein PCoA1 also be the current access of MR AGW1 act on behalf of Care-of Address, DGW1_addr is the address of DGW1 in the Access Network side

Step 17:DGW1 at first carries out decapsulation to it after receiving packet, packet is reduced to the form of { HoAn, MNP, data }.Then DGW1 carries out the inquiry of mapping relations, and this moment, DGW1 went up two corresponding core addresses of MNP of the HNP1 that has only MR and the LFN of storage, at first inquires about local mapping table the source address MNP of packet is inquired about, and obtains corresponding core address 1; Yet DGW1 is the information of not relevant with HoAn core address n at this moment, so DGW1 need obtain the corresponding core address of HoAn with response message with the inquiry of GMS interactive map.

Step 18:DGW1 and inquiry of GMS interactive map and response message obtain the corresponding core address n of HoAn.

Step 19:DGW1 is after having obtained the needed core map addresses of packet information, and then source address and the destination address to packet shines upon replacement, has replaced the back data packet format and has been { core address n, core address 1, data }, and be sent to DGW2.

After step 20:DGW2 receives packet, and do not know the information of the home address that core address 1 is corresponding, so DGW2 inquires about with the GMS interactive map and response message obtains the corresponding MNP in core address 1.DGW2 just separates the mapping replacement to source address, the destination address of packet after obtaining corresponding mapping relations, the data packet format of separating after the mapping is { HoAn, MNP, data }.

Step 21:DGW2 since set up and AGWn between bidirectional tunnel, then directly packet is carried out tunnel encapsulation, data packet format is { PCoAn, DGW2_addr, { HoAn, MNP, data } }, and packet is sent to AGWn via the tunnel.

Step 22:AGWn carries out the tunnel decapsulation to packet after receiving packet, the data packet format after the decapsulation { HoAn, MNP, data }, and packet sent to MN.

So far accomplish the communication process of LFN to CN.

Should be appreciated that the above detailed description of technical scheme of the present invention being carried out by preferred embodiment is schematic and nonrestrictive.Those of ordinary skill in the art is reading on the basis of specification of the present invention and can make amendment to the technical scheme that each embodiment put down in writing, and perhaps part technical characterictic wherein is equal to replacement; And these are revised or replacement, do not make the spirit and the scope of the essence disengaging various embodiments of the present invention technical scheme of relevant art scheme.

Claims (1)

1. in the separation mechanism mobility management systems, dispose the method that subnet moves for one kind, it is characterized in that this method comprises the steps:

Step 1:MR is linked into AGW1; (Access Point is so the entering transmission log information that AP) detects MR is to AGW1, after AGW1 receives log information for the last WAP of AGW1; The access style of decision node; Be mobile router or mobile node, and obtain the ID of corresponding access node, accomplish that the mobile management process on the AGW1 is in wait state after these work;

Step 2:MR then sends DHCPv6 CONFIRM message to dhcp relay agent;

After DHCP CONFIRM message is received by step 3:DHCP relay agent, send DHCPv6 RELAY FORWARD message to Dynamic Host Configuration Protocol server;

After step 4:DHCP server is received this message, judge whether the address of carrying in the message is available, if available, then returning a status code to dhcp relay agent is 0 DHCP RELAY REPLY message;

After message was received by step 5:DHCP relay agent, the status code that judges in the message was 0, informed that then the mobile management process on the AGW1 can be sent agent binding update PBU message;

Step 6:AGW1 sends PBU message to CGW1, newly-increased MNP option and R flag bit in the PBU message, and AGW1 goes up and sets up the BUL relevant with MR simultaneously;

Step 7:CGW1 resolves after receiving PBU message, if legal, then send the tunnel and sets up request message TxReq to DGW1, and also newly-increased MNP option and R flag bit in this message, CGW1 goes up and sets up the BCE relevant with MR simultaneously;

After step 8:DGW1 receives and resolves after the TxReq message, set up one and point to the tunnel of AGW1, and return a tunnel acknowledge message TxAck, and on DGW1, set up the TCE relevant, the route that interpolation is relevant with HNP and MNP with MR to CGW1 by DGW1;

Step 9:DGW1 inquires about the address pool on it; For HNP and MNP distribute corresponding core address; And the corresponding relation of corresponding relation, MNP and the core address of HNP and core address is injected in the kernel of DGW1 and goes; Also these two pairs of mapping relations are included in the map updating message simultaneously and issue GMS, carry out up-to-date record;

After step 10:CGW1 receives TxAck message, just send the proxy binding acknowledgment messages PBA that comprises HNP and R flag bit to AGW1;

After step 11:AGW1 receives PBA message, DHCP process this moment can send DHCP REPLY message to MR all over informing;

Step 12:AGW1 parses the HNP information in the PBA message; Announce to MR through advertising of route RA; Set up the other end that is pointed to the tunnel of DGW1 by AGW1 simultaneously, and add the route about HNP and MNP, MR receives behind the HNP home address that generates oneself according to EUI-64;

After the notice that AGW1 sends is received by step 13:DHCP relay agent, just send DHCP REPLY message to MR;

After step 14:MR receives DHCP REPLY message, the MNP that DHCP distributes is announced to LFN through RA message;

Step 15: after MR obtains home address HoA1, LFN acquisition subnet address MNP, can send packet, suppose that here CN also accomplishes corresponding steps to the CN that is positioned at Access Network 2; The home address that obtains at Access Network 2 is HoAn; Make LFN initiate communication to CN, packet is transmitted through MR and at first is sent to AGW1, and data packet format is { HoAn; MNP, data };

Step 16:AGW1 is { DGW1_addr, PCoA, { HoAn with packet encapsulation; MNP, data } } form, and packet is sent to DGW1 through bidirectional tunnel; Wherein PCoA1 also be the current access of MR AGW1 act on behalf of Care-of Address, DGW1_addr is the address of DGW1 in the Access Network side;

Step 17:DGW1 at first carries out decapsulation to it after receiving packet, and packet is reduced to { HoAn; MNP; Data } form, then DGW1 carries out the inquiry of mapping relations, this moment, DGW1 went up two corresponding core addresses of MNP of the HNP1 that has only MR and the LFN of storage; At first inquire about local mapping table the source address MNP of packet is inquired about, obtain corresponding core address 1; Yet DGW1 is the information of not relevant with HoAn core address n at this moment, so DGW1 need obtain the corresponding core address of HoAn with response message with the inquiry of GMS interactive map;

Step 18:DGW1 and inquiry of GMS interactive map and response message obtain the corresponding core address n of HoAn;

Step 19:DGW1 is after having obtained the needed core map addresses of packet information, and then source address and the destination address to packet shines upon replacement, has replaced the back data packet format and has been { core address n, core address 1, data }, and be sent to DGW2;

After step 20:DGW2 receives packet, and do not know the information of the home address that core address 1 is corresponding, so DGW2 inquires about with the GMS interactive map and response message obtains the corresponding MNP in core address 1; DGW2 just separates the mapping replacement to source address, the destination address of packet after obtaining corresponding mapping relations, the data packet format of separating after the mapping is { HoAn, MNP, data };

Step 21:DGW2 since set up and AGWn between bidirectional tunnel, then directly packet is carried out tunnel encapsulation, data packet format is { PCoAn, DGW2_addr, { HoAn, MNP, data } }, and packet is sent to AGWn via the tunnel;

Step 22:AGWn carries out the tunnel decapsulation to packet after receiving packet, the data packet format after the decapsulation { HoAn, MNP, data }, and packet sent to MN.

Images