WO2008017253A1 - A multiple hosts access method, system and apparatus supporting mixed ip - Google Patents

Abstract

A multiple hosts access method, system and apparatus supporting mixed IP includes mobile router, used for connecting networks which users locate and visit, executing the function of mobile user data interface in IPv4 and IPv6 double stack network in proxy of mobile routers and hosts network; foreign agent, executing the function of mobile user control interface in proxy of mobile routers and hosts network, initiating IPv4 registration request based upon IPv6 network prefix, forwarding said IPv4 registration request as the foreign agent for mobile routers and hosts; double stack home agent for mobile hosts and routers, responding said IPv4 registration request from foreign agents, binding between the IPv6 network prefix of the mobile routers and hosts network and the IPv4 or IPv6 home address of mobile routers, and binding also between the IPv4 or IPv6 home address of mobile routers and the care-of-address of mobile routers and hosts network.

Description

 Multi-host access method, system and device supporting hybrid IP

 The present invention relates to mobile IP technologies, and in particular to a multi-host access method, system and device supporting hybrid IP. Background technique

 In the existing Multiple Hosts architecture (as shown in Figure 1), including hosts, gateways (G-MS/G-RS RG/CNG), access service network (ASN), and connection service network (CSN) ). The ASN provides wireless access to the user, and the CSN provides the user with an IP connection. A Network Access Provider (NAP) is an operational entity that provides wireless access devices to one or more Network Service Providers (NSPs), and a NAP can have one or more ASNs. The NSP is also an operational entity that provides users with IP connectivity and WiMA services. The NSP devices are located in the CSN. In Figure 1, for a WiMAX network, the gateway is G-MS/G-RS; for a wired network (such as a DSL network), the gateway is a residential gateway RG, a routing gateway RG, or a user network gateway CNG. RG/G-RS/G-MS/CNG provides multi-host support and can be connected to one or more hosts (Host). Among them, RG/G-RS/G-MS/CNG and host use 802.3, 802.16e or 802.11 transmission technology; RG/G-RS/G-MS/CNG and ASN use 802.16e wireless transmission technology or DSL Wired transmission technology.

 The Mobile IP (MIP: Mobile IP) and Network Mobile (NEMO) standards of the IETF (Internet Engineering Department) include two methods. The main difference is that the COA (care-of address) is different:

 1) The foreign agent care-of-address (FACOA) is the IP address of the foreign agent (FA: Foreign Agent). There is a port to connect to the mobile node (MN: Mobile Node), or mobile host (MH: Mobile Host) / The foreign link where the mobile router (MR: Mobile Router) is located.

2) Co-located Care-of-Address (CCOA) is a local IP address temporarily assigned to the mobile node/mobile router. The network prefix must be associated with the mobile node/mobile router. The network prefix of the connected foreign link is the same. When there is no foreign agent on the foreign link, the mobile node/mobile router can use this care-of address.

 The above method 2) involves three functional entities: the home agent (HA: Home Agent), the mobile network and the peer communication node (CN: Correspondent Node) where the MN or MH/MR is located; mode 1) one more functional entity: the foreign agent FA. The MIPv4 (RFC3344) standard / NEMOv4 draft standard can be used either in 1) or in 2); ΜΙΡνό standard (RFC 3775)/NEMOv6 (RFC3963) only in mode 2).

 At present, DSL or WiMAX networks can cooperate with MIP and EMO standards to implement mobile IP management solutions under multi-host architecture. However, in the process of invention, the inventors have discovered the following technical problems:

 1. An IPv4 service provider cannot provide access to a pure IPv6 host (Host) under a multi-host architecture;

 2. An IPv6 service provider cannot provide access to a pure IPv4 host (Host) under a multi-host architecture. Summary of the invention

 Embodiments of the present invention provide a hybrid host-enabled multi-master access method, system, and device that binds an IPv6 (or IPv4) network prefix of a mobile router MR and a mobile host MH (or mobile node) network, Implement multi-host access that supports hybrid IP.

 Embodiments of the present invention are implemented by the following technical solutions:

 An embodiment of the present invention provides a multi-homing access method supporting hybrid IP, which includes: a dual-stack network mobile client or a dual-stack proxy network mobile client initiates an IPv4 registration request based on an IPv6 network prefix binding;

 Forwarding the IPv4 registration request to the home agent by the foreign agent;

 During the transmission of the IPv6 data packet, the home agent binds the IPv6 network prefix of the mobile router MR and the mobile host MH network to the IPv4 home address of the MR according to the received IPv4 registration request, and associates the MR IPv4 home address with the MR. Bind to the care-of address of the MH network for the transmission of IPv6 packets.

The embodiment of the present invention further provides a second multi-host access method supporting hybrid IP, which includes: The dual-stack network mobile client or the dual-stack proxy network mobile client initiates an IPv4 registration request based on the IPv6 network prefix binding of the MR and MH networks;

 The home agent binds the IPv6 network prefix of the MR and MH networks to the care-of address of the MR and MH networks according to the received registration request to perform IPv6 data packet transmission.

 The embodiment of the present invention further provides a third multi-host access method supporting hybrid IP, including: a dual-stack network mobile client or a dual-stack proxy network mobile client initiates an IPv6 registration request based on an IPv4 network prefix binding;

 The home agent binds the IPv4 network prefix of the MR and MH networks to the care-of address of the MR and MH networks according to the received IPv6 registration request based on the IPv4 network prefix binding, so as to transmit the IPv4 data packet.

 The embodiment of the present invention further provides a fourth multi-host access method supporting hybrid IP, which includes: a dual-stack network mobile client or a dual-stack proxy network mobile client initiates an IPv4 registration request based on an IPv6 network prefix binding;

 Forwarding the IPv4 registration request to the home agent by the foreign agent;

 The home agent binds the IPv6 network prefix of the MR and MH networks to the IPv6 home address of the MR according to the received IPv4 registration request, and binds the IPv6 home address of the MR to the care-of address of the MR and MH networks to perform IPv6 data. The transmission of the package.

 Embodiments of the present invention also provide a multi-host access system supporting hybrid IP, including: a device having a network mobile client data plane function and capable of transmitting IPv6 data packets by using an IPv4 tunnel or a reverse tunnel;

 A device that supports a network mobile client control plane function and initiates an IPv4 registration request based on an IPv6 network prefix;

 a foreign agent, used to forward an IPv4 registration request;

 The home agent device is configured to establish, according to the received IPv4 registration request, the binding of the IPv6 network prefix of the MR and MH networks to the home address of the IPv4 of the MR, and the binding of the IPv4 home address of the MR and the care-of address of the MR and MH networks. set.

The embodiment of the present invention further provides a second multi-host access system supporting hybrid IP, which includes: The mobile router device supports the dual-stack network mobile client data plane and control plane function, and is used to initiate an IPv4 registration request based on the IPv6 network prefix;

 The home agent device establishes the binding of the IPv6 network prefix of the MR and MH networks to the care-of addresses of the MR and MH networks according to the received IPv4 registration request.

 The embodiment of the present invention further provides a third multi-host access system supporting hybrid IP, which includes: a mobile router M device, a dual-stack network mobile client data plane and a control plane function supporting the mobile router MR and the mobile host MH network. And used to initiate an IPv6 registration request based on an IPv4 network prefix;

 The home agent device is configured to establish a binding between the IPv4 network prefix of the MR and MH networks and the care-of address of the M and MH networks according to the received registration request.

 An embodiment of the present invention further provides a fourth multi-host access system supporting hybrid IP, which includes: a mobile router MR device, configured to support a network mobile client data plane function;

 A device that supports a network mobile client control plane function and initiates an IPv4 registration request based on an IPv6 network prefix;

 a foreign agent, used to forward an IPv4 registration request;

 The home agent device is configured to bind the IPv6 network prefix of the MR and MH networks to the home address of the IPv6 of the MR according to the received IPv4 registration request, and establish a binding of the IPv6 home address of the MR and the care-of address of the MR and MH networks. set.

 An embodiment of the present invention further provides a mobile routing device, including:

 Mobile router MR, used to connect the customer premises network and the visited network;

 The dual-stack network mobile client supports the IPv4 home address and the IPv6 home address, and is used to initiate an IPv4 registration request based on the IPv6 network prefix to notify the home agent to send the IPv6 data packet to the care-of address of the MR and MH network through the tunnel, or notify the hometown. The proxy receives IPv6 packets sent to the home agent from the care-of address of the MR and MH networks through the reverse tunnel.

 An embodiment of the present invention further provides a foreign agent device, including:

A dual-stack proxy network mobile client, configured to initiate an IPv4 network prefix-based IPv4 registration request; a foreign agent, configured to forward the IPv4 registration request, to notify the dual-stack home agent to use the IPv6 data The packet is sent to the IPv4 home address of the mobile router MR through the tunnel, or the dual-stack home agent is notified to receive the IPv6 data packet sent from the IPv4 home address of the M through the reverse tunnel.

 An embodiment of the present invention further provides a foreign agent device, including:

 A dual-stack proxy network mobile client, configured to initiate an IPv4 network prefix-based IPv4 registration request; a foreign agent, configured to forward the IPv4 registration request, to notify the home agent to send the IPv6 data packet to the IPv6 hometown of the mobile router MR through the IPv6 tunnel Address, or notify the dual-stack home agent to receive IPv6 packets sent from the MR's IPv6 home address through the IPv6 reverse tunnel.

 An embodiment of the present invention further provides a home agent device, including:

 The dual-stack home agent is configured to establish a binding between the IPv6 network prefix of the MR and the MH network and the IPv4 home address of the MR according to the received IPv4 registration request based on the IPv6 network prefix;

 Dual stack mobile bonded memory for storing IPv6 network prefix bindings for MR and MH networks. An embodiment of the present invention further provides a home agent device, including:

 The dual-stack home agent is used to bind the IPv4 network prefix of the MR and MH networks to the care-of address of the MR and MH networks according to the received IPv6 network prefix-based IPv6 registration request, and the MR IPv6 HoA and MR and MH The care-of address binding of the network;

 Dual stack mobile bonded memory for storing IPv4 network prefix bindings for MR and MH networks. An embodiment of the present invention further provides a home agent device, including:

 The dual-stack home agent is configured to establish an IPv6 network prefix of the MR and MH networks and a home address of the IPv6 of the MR according to the received IPv4 network prefix-based IPv4 registration request, and establish an IPv6 home address and MR of the MR. Binding to the care-of address of the MH network;

Dual stack mobile binding memory for storing IPv6 network prefix bindings for MR and MH networks. It can be seen from the foregoing specific embodiments of the present invention that, by using the embodiments of the present invention, an IPv4 service provider can provide an access service of a pure IPv6 host in a multi-host architecture; thereby moving the existing IPv4 mobile network to IPv6. Network transitions provide a seamless, efficient, and inexpensive solution; moreover, IPv6 service operators can provide access to pure IPv4 hosts in a multi-host architecture; thus protecting legacy IPv4 users from the new IPv6 mobile network. Investment provides an effective guarantee. DRAWINGS

 In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description of the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description For some embodiments of the present invention, other drawings may be obtained from those skilled in the art without departing from the drawings.

 1 is a schematic diagram of a multi-master architecture in the prior art;

 2 is a block diagram of a dual-stack NEMO function in the FACOA mode according to Embodiment 1 of the present invention; FIG. 3 is a schematic diagram of a dual-stack NEMO processing protocol stack in FACOA mode according to Embodiment 1 of the present invention; FIG. 4 is a CCOA according to Embodiment 1 of the present invention; FIG. 5 is a schematic diagram of a dual-stack EMO processing protocol stack in a CCOA mode according to Embodiment 1 of the present invention; FIG. 6 is a schematic diagram of a dual-stack NEMO processing protocol stack according to Embodiment 2 of the present invention;

 FIG. 3 is a functional block diagram of a dual stack NEMO according to Embodiment 3 of the present invention;

 FIG. 8 is a schematic diagram of a dual-stack NEMO processing protocol stack according to Embodiment 3 of the present invention. detailed description

 BRIEF DESCRIPTION OF THE DRAWINGS The technical solutions in the embodiments of the present invention will be described in detail with reference to the accompanying drawings. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative work are within the scope of the present invention.

 In the embodiment of the present invention, between the mobile router (MR) and the mobile host (MH, or mobile node), it is a mobile subscriber premises network (Mobile CPN), and the MR and the FA are visited networks, and the M may not belong to the network access. Business (NAP).

 Example 1: The visited network supports IPv4, and the mobile premises network supports IPv6 and IPv4.

 This embodiment supports two modes: a coexistence care-of address (CCOA) mode and a foreign agent care-of address (FACOA) mode, which are described below.

 First, FACOA mode

2 is a dual stack of a multi-host access system supporting hybrid IP in FACOA mode in the embodiment. NEMO functional block diagram. As shown in FIG. 2, the system of the present invention includes: a mobile router MR, a dual-stack proxy network mobile version 4 client (Proxy EMOv4 Client, referred to as a dual-stack agent NEMOv4 client, which is optional), a foreign agent FA, a dual-stack HA device ( Includes HA and mobile bonded data storage), authenticators, and AAA (authentication, authorization, accounting) servers. among them:

 The dual-stack proxy network mobile version 4 client is optionally set on the network side (Network Access Provider, NAP) for proxying the functions of the dual-stack NEMO client control plane for the MR and MH networks, wherein the dual stack represents It can support both IPv4 and IPv6. The dual stack NEMO client control plane functions include:

 1. Support the functions of the NEMO customer control plane in the prior art;

 2. Support IPv4 registration function based on IPv6 network prefix binding, that is, the dual-stack Proxy NEMOv4 Client can initiate an IPv4 registration request, including the IPv6 network prefix of the MR and MH networks, the IPv4 HoA of the MR, and the CoA of the MR and MH networks; This is achieved by adding an IPv6 network prefix extension to the IPv4 registration request message, the IPv6 network prefix extension containing the IPv6 network prefix of the MR and MH networks as a new NEMOv4 parameter. The IPv6 network prefix extension of NEMOv4 can be defined by the TLV (Type Length Value) principle.

 After NAP sets up the dual-stack agent NEMOv4 client, MR only needs to support the dual-stack NEMO Client data plane function (the movement brought by the update of the care-of address CoA is transparent to the MR), and the NAP does not support the dual-stack proxy EMO client. In this case, MR needs to support the above dual stack EMO client control plane and data plane functions.

 The dual-stack NEMO Client data plane functions supported by MR include:

 1. The function of the EMOv4 customer data plane in the prior art;

 2. Support dual IP addresses: IPv4 HoA and IPv6 HoA; MR can carry pure IPv6 and / or IPv4 MH;

3. The IPv6 data packet from the peer-to-peer communication node (CN) to the MR and MH networks is sent to the MR4 HoA of the MR via the IPv4 tunnel. The MR should be able to de-encapsulate and obtain the IPv6 data packet. If the destination address of the IPv6 data packet is MH. IPv6 HoA, MR forwards IPv6 packets to MH;

4. The MR should be able to send the IPv6 packets from the MR and MH networks to the CN to the HA through the IPv4 reverse tunnel. The source address of the reverse tunnel is the IPv4 HoA of the MR; 5, MR can support routing function; Or, MR supports IP Bridging (IP bridging) function, that is, MR can sense IP (IP awareness), but does not support routing, MR forwards data through Layer 2 protocol instead of Layer 3 routing.

 The foreign agent FA, set in the NAP (Network Access Provider), is used as a foreign agent for MH and MR. The foreign agent FA supports the following functions:

 1. Support the functions of NEMOv4 FA in the prior art;

 2. Support tracking of MR's IPv4 Ho A;

 3. Notify the dual-stack HA to send the IPv6 data packet to the MR's IPv4 HoA through the tunnel; this can be achieved by simply ignoring the IPv6 network prefix extension information in the IPv4 registration request and simply forwarding the IPv4 registration request;

 4. Notifying the dual stack HA receives the IPv6 packet sent from the MR's IPv4 HoA to the HA through the reverse tunnel; this can simply forward the IPv4 registration request by simply ignoring the IPv6 network prefix extension information in the IPv4 registration request.

 The dual stack HA, set up at the NSP (Network Service Provider), is used as a home agent for MH and MR (the movement brought by the care-of address CoA update is transparent to the MH).

 The dual stack HA supports the following functions:

 1. Support the functions of NEMOv4 HA in the prior art;

 2. Bind the IPv6 network prefix of the MR and MH networks to the IPv4 HoA of the MR according to the received IPv4 registration request based on the IPv6 network prefix binding, and tie the IPv4 HoA of the MR to the CoA of the MR and MH networks. Set

 3. Broadcasting the reachability of the IPv6 network prefix of the MR and MH networks in the home link, intercepting the IPv6 packet with the IPv6 network prefix of the destination address and the MR network;

 4. According to the received IPv4 registration request based on the IPv6 network prefix binding, the HA sends the IPv6 data packet of the CN to the MR and the MH network to the MR through the dual IPv4 tunnel, and the destination address of the outer tunnel is the MR and the MH network. IPv4 CoA, the IPv4 HoA of the inner tunnel whose destination address is M;

5. According to the received IPv4 registration request based on the IPv6 network prefix binding, the HA receives the double reverse IPv4 tunnel encapsulated MR and MH network to the CN IPv6 data packet, and the outer reverse tunnel The source address is the IPv4 CoA of the MR and MH networks, the inner layer reverse tunnel source address is the IPv4 HoA of the MR; or the HA receives the reverse IPv4 tunnel encapsulated MR and MH network to the CN IPv6 packet, the source of the reverse tunnel IPv4 HoA with address MR;

 Dual-stack HA and dual-stack Mobility Bindings data storage can be used to form HA devices; dual-stack mobile binding data storage is used to store IPv6 network prefix bindings for MR and MH networks.

 In this embodiment, for the FACOA mode, the authenticator, the dual stack agent NEMO client, and the FA may collectively form the FA device.

 In WiMAX, MH is G-Host and MR is G-MS/G-RS. In wired access networks, MH is Host and MR is RG.

 The Authenticator (Authenticator) is set in NAP to provide a dual-stack EMO key for the dual-stack agent NEMO client and the FA, and provides authentication services for the MR and/or MH;

 The AAA server is configured in the NSP to provide the required dual-stack EMO key for the HA. The related information required by the NEMO is obtained through the AAA information interactive retrieval process in the authentication process.

 In the present invention, FA exists only in the FACOA mode. The connection between the Authenticator and the MR exists only in the CCOA combination mode. If the dual stack Proxy NEMO Client exists, it must be placed with the authenticator. If the dual-stack Proxy NEMO Client does not exist, the authenticator and the FA need to have a connection.

 MR and FA belong to the same IP Link (connection).

 EMO processing in FACOA mode:

 FACOA mode dual stack NEMO processing protocol stack As shown in Figure 3, the MIPv4 tunnel between HA and MH's CoA (ie MR) must be built on the MIPv4 tunnel between HA and MR CoA (ie FA). For WiMAX networks, 802.16 between G-MS/G-RS and BS uses the IP CS sublayer. The BS/AN supports the IP Bridging function, that is, the BS/AN can be aware of IP (IP awareness), but does not support routing. The MR forwards data through the Layer 2 protocol instead of Layer 3 routing. FA can also be combined with BS/AN.

 Control surface processing:

1) Proxy NEMO Client/NEMO Client initiates IPv6 network based on MR and MH networks IPv4 registration request with prefix binding;

 2) The FA ignores the IPv6 network prefix extension information in the IPv4 registration request, and simply forwards the IPv4 registration request implementation to notify the HA to send the IPv6 data packet to the IPv4 HoA of the M through the tunnel, and notify the HA to receive the MR through the reverse tunnel. The IPv6 packet sent by the IPv4 HoA to the HA;

 3) The HA receives the IPv4 registration request based on the IPv6 network prefix binding, binds the IPv6 network prefix of the MR and MH networks to the IPv4 HoA of the MR, and binds the IPv4 HoA of the MR to the CoA of the MR and MH networks;

 4) Broadcast the reachability of the IPv6 network prefix of the MR and MH networks in the home link.

 Data surface processing:

 When the IPv6 data packet is sent by the communication node CN to the mobile node MH (CN -> MH), the following steps are included:

 1) The IPv6 packet sent by CN (SA=CN IPv6@, DA=MH6 IPv6 HoA) is intercepted by HA;

 The source IP address (SA: Source IP Address) of the IPv6 packet is the IPv6 address of the CN (CN IPv6@), and the destination IP address (DA: Destination IP Address) of the IP packet is the IPv6 home address (HoA) of the MH.

 2) HA performs the first layer MIPv4 tunnel (SA=HA IPv4@, DA=M IPv4 HoA) encapsulation;

 3) HA further encapsulates the IP packet to the CoA of the MR and MH networks through the second layer MIPv4 tunnel (SA=HA IPv4 @, DA=MR and IPv4 CoA of the MH network);

 4) When the IPv6 packet passing through the two-layer MIP tunnel reaches the FA of the MR and MH networks, the second layer MIPv4 tunnel encapsulation is stripped, and an IPv6 packet encapsulated by the first layer MIPv4 tunnel to be sent to the MR, MR and The FA of the MH network sends the IP packet to the MR;

 5) When the MR receives the IP packet of the single layer encapsulation, the remaining first layer MIPv4 tunnel encapsulation is stripped, and then the IPv6 packet to be sent to the MH is obtained, and the MR sends the IPv6 packet to the MH via the MR link.

There are three cases when an IPv6 packet is sent by the mobile node to the peer-to-peer communication node (MH -> CN): One is the case without reverse tunnel, and the IPv6 packet sent by the MH (SA = MH's IPv6 HoA, DA=CN IPv6@ ) is sent directly to the CN;

 The other is the case of a single reverse tunnel, including the following steps:

 1) The IPv6 packet sent by MH (SA=MH IPv6 HoA, DA=CN IPv6@) is sent to

CN;

 2) The IPv6 packet is first intercepted by the MR, and the IPv6 packet is sent to the HA through the MIPv4 tunnel (IPv=M IPv4 HoA, DA=HA IPv4@);

 3) When the IP packet passing through the MIPv4 tunnel arrives at the HA, the MIPv4 tunnel encapsulation is stripped, and the IPv6 packet to be sent to the CN is obtained, and the HA sends the IPv6 packet to the CN.

 The other is the case of a double reverse tunnel, including the following steps:

 1) The IPv6 packet sent by MH (SA=MH IPv6 HoA, DA=CN IPv6@) is sent to

CN;

 2) The IPv6 packet is first intercepted by the MR, and the IPv6 packet is sent to the HA through the first layer MIPv4 tunnel (SA=MR IPv4 HoA, DA=HAIPv4@);

 3) The IP packet encapsulated by the first layer of the MIPv4 tunnel is intercepted by the FA of the MR, and the IP packet is further sent to the HA through the second layer MIPv4 tunnel (the SA4 MRA, DA=HA IPv4@);

 4) When the IP packet of the two-layer MIPv4 tunnel arrives at the HA, the second layer MIPv4 tunnel encapsulation and the first layer MIPv4 tunnel encapsulation are stripped in turn, and then the IPv6 packet to be sent to the CN is obtained, and the HA sends the IPv6 packet to the HA. CN.

 Second, CCOA mode

 4 is a block diagram of a dual-stack NEMO function of a multi-master system supporting hybrid IP in CCOA mode of the present invention. As shown in FIG. 4, the system of the present invention includes: MR, dual stack NEMOv4 client, dual stack HA, authenticator, and AAA server. among them:

 The MR supports the control plane and data plane functions of the dual stack NEMO client.

 The dual-stack EMOv4 client (NEMOv4 Client), which is set up in the same physical entity as the MR (referred to as a mobile router device), is used to perform the dual-stack NEMO client control plane and data plane functions.

 The dual stack NEMO client control surface features supported by MR include:

1. Support the functions of the NEMO customer control plane in the prior art; 2. Support IPv4 registration function based on IPv6 network prefix binding, that is, dual-stack Proxy NEMO Client can initiate IPv4 registration request, including IPv6 network prefix of M and MH networks and CoA of MR and MH networks; this can be requested by IPv4 registration The message is implemented by adding an IPv6 network prefix extension that includes the IPv6 network prefix of the MR and MH networks as a new NEMOv4 parameter. The IPv6 network prefix extension of NEMOv4 can be defined according to the TLV (Type Length Value) principle;

3. Notify the dual stack HA to send the IPv6 data packet through the tunnel to the CoA of the MR and MH networks; this can be achieved by modifying the IPv4 registration request content (such as setting information bits or adding extensions);

 4. Notify the dual stack HA receives the IPv6 packets sent from the MRs of the MR and MH networks to the HA through the reverse tunnel; this can be done by modifying the contents of the IPv4 registration request (such as setting information bits or adding extensions).

 The dual stack NEMO Client data plane features supported by MR include:

 1. The function of the EMOv4 customer data plane in the prior art;

 2. Support dual IP addresses: IPv4 Ho A and IPv6 HoA; MR can carry pure IPv6 or IPv4 MH;

3. The IPv6 data packets of the CN to MR and MH networks are sent to the MR4 HoA of the MR through the IPv4 tunnel. The MR should be able to de-encapsulate and obtain the IPv6 data packet. If the IPv6 data packet destination address is MH's IPv6 HoA, the MR will IPv6 data packet. Forward to MH;

 4. The MR should be able to send the IPv6 packets from the MR and MH networks to the CN to the HA through the IPv4 reverse tunnel. The source address of the reverse tunnel is the IPv4 HoA of the MR;

 5, MR can support routing function; Or, MR supports IP Bridging (IP bridging) function, that is, MR can sense IP (IP awareness), but does not support routing, MR forwards data through Layer 2 protocol instead of Layer 3 routing.

 The dual stack HA, set up in the NSP (Network Service Provider), is used as a home agent for MH and MR (the movement brought by the CoA update is transparent to the MH).

 The dual stack HA supports the following functions:

 1. Support the functions of NEMOv4 HA in the prior art;

2. Binding the IPv6 network prefix of the MR and MH networks to the CoA of the MR and MH networks according to the received IPv4 registration request based on the IPv6 network prefix binding; 3. The home link broadcasts the reachability of the IPv6 network prefix of the MR and MH networks, and intercepts the IPv6 data packet whose destination address includes the IPv6 network prefix of the MR and MH networks;

 4. According to the received IPv4 registration request based on the IPv6 network prefix binding, the HA sends the IPv6 data packet of the CN to the MR and the MH network to the MR through the IPv4 tunnel, and the tunnel destination address is the CoA of the MR and the MH network;

 5. According to the received IPv4 registration request based on the IPv6 network prefix binding, the HA receives the IPv6 data packet of the MR and the MH network encapsulated by the reverse IPv4 tunnel to the CN, and the source address of the reverse tunnel is the CoA of the MR and the MH network. .

 In WiMAX, MH is G-Host and MR is G-MS/G-RS. In wired access networks, MH is Host and MR is RG.

 The Authenticator (Authenticator) is set in NAP to provide a dual-stack EMO key for the dual-stack agent NEMO client and the FA, and provides authentication services for the MR and/or MH;

 The AAA server is configured in the NSP to provide the required dual-stack EMO key for the HA. The related information required by the NEMO is obtained through the AAA information interactive retrieval process in the authentication process.

 NEMO processing in CCOA mode:

 CCOA mode dual stack NEMO processing protocol stack As shown in Figure 5, only one layer of MIP tunnel between HA and MH's CoA (ie MR). For WiMAX networks, 802.16 between G-MS/G-RS and BS uses the IP CS sublayer. The BS/AN supports the IP Bridging function, that is, the BS/AN can be aware of IP (IP awareness), but does not support routing. The MR forwards data through the Layer 2 protocol instead of Layer 3 routing.

 Control surface processing:

 1) The dual-stack NEMO Client initiates an IPv4 registration request based on the MR6 and MH network-based IPv6 network prefix binding, which includes a CoA for informing the HA to send the IPv6 data packet through the tunnel to the MR and MH networks and notifying the HA to receive the reverse The information that the tunnel sends the IPv6 packets from the CoA of the MR and MH networks to the HA;

2) The HA binds the IPv6 network prefix of the MR and MH networks to the CoA of the MR and MH networks according to the received IPv4 registration request based on the IPv6 network prefix binding; 3) The home link links the accessibility of the IPv6 network prefix of the MR and MH networks.

 Data surface processing:

 When CN->MH, the following steps are included:

 1) The IPv6 packet sent by CN (SA=CN IPv6@, DA=MH6 IPv6 HoA) is intercepted by HA;

 2) HA performs MIPv4 tunneling (SA=HA IPv4@, DA=M and Co A of MH network) encapsulation;

 3) When the MR receives the IP packet of the single-layer encapsulation, strips the MIPv4 tunnel encapsulation, and then obtains the IPv6 packet to be sent to the MH, and the MR sends the IPv6 packet to the MH via the MR link.

 There are two cases when MH -> CN:

 The first one is the case of no reverse tunnel. The IPv6 packet sent by the MH (SA=MH IPv6 HoA, DA=CN IPv6@) is sent directly to the CN;

 The other is the case of a reverse tunnel, including:

 1) The IPv6 packet sent by MH (SA=MH IPv6 HoA, DA=CN IPv6@) is sent to

CN;

 2) The IPv6 packet is first intercepted by the MR, and the IPv6 packet is sent to the HA through the MIPv4 tunnel (SA=MR and MH network CoA, DA=HAIPv4@);

 3) When the IP packet passing through the MIPv4 tunnel arrives at the HA, the MIPv4 tunnel encapsulation is stripped, and the IPv6 packet to be sent to the CN is obtained, and the HA sends the IPv6 packet to the CN.

 Example 2: The visited network supports IPv6, and the mobile premises network supports IPv4 and IPv6.

 The present invention proposes a dual-stack NEMO scheme, and its functional block diagram can still be used in FIG. 4. In this embodiment, there is no dual-stack agent EMO client and FA. Therefore, MR needs to support dual-stack NEMO client control plane and data plane function f]

 (1) MR needs to support the dual stack EMO customer control surface function:

 1. Support the functions of the NEMOv6 customer control plane in the prior art;

2. Support IPv6 registration function based on IPv4 network prefix binding, that is, dual-stack EMO Client can initiate IPv6 registration request, including IPv4 network prefix and MR and MH network of MR and MH networks. The CoA of the network; this can be achieved by adding an IPv4 network prefix extension to the IPv6 Binding Update message, which contains the IPv4 network prefix of the MR and MH networks as a new EMOv6 parameter. The IPv4 network prefix extension of NEMOv6 can be defined according to the TLV (Type Length Value) principle;

 3. (CCOA mode) informs the dual-stack HA to receive IPv4 packets sent from the CoA of the MR and MH networks to the HA through the reverse tunnel; this can be achieved by modifying the IPv6 binding update message content (such as setting information bits or adding extensions). .

 (2) MR needs to support dual stack NEMO customer data surface function:

 1. Support the functions of the NEMOv6 customer data plane in the prior art;

 2. Support dual IP addresses: IPv4 Ho A and IPv6 HoA; MR can carry pure IPv6 or IPv4 MH;

3. The IPv4 packets from the CN to the MR and MH networks are sent to the CoA of the MR and MH networks via the IPv6 tunnel. The MR should be able to decapsulate the encapsulated IPv4 packets. If the destination address of the IPv4 packets is MH for IPv4 HoA, MR will be IPv4. The data packet is forwarded to the MH;

 4. The MR shall be able to forward the IPv4 data packets from the MR and MH networks to the CN to the HA through the IPv6 reverse tunnel, and the source address of the reverse tunnel is the CoA of the MR and the MH network;

 5, MR can support routing function; Or, MR supports IP Bridging (IP bridging) function, that is, MR can sense IP (IP awareness), but does not support routing, MR forwards data through Layer 2 protocol instead of Layer 3 routing.

 Set up dual-stack HA in NSP, used as a home agent for MH and MR:

 1. Support the functions of NEMOv6 HA in the prior art;

 2. Binding the IPv4 network prefix of the MR and MH networks to the CoA of the MR and MH networks according to the received IPv6 registration request based on the IPv4 network prefix binding;

 3. Broadcasting the reachability of the IPv4 network prefix of the MR and MH networks in the home link, and intercepting the IPv4 packet with the destination address containing the IPv4 network prefix of the MR and MH networks;

4. According to the received IPv6 registration request based on the IPv4 network prefix binding, the HA receives the MR and MH network encapsulated by the reverse IPv6 tunnel->CN IPv4 data packet, and the source address of the reverse tunnel is MR and MH network CoA. In WiMAX, MH is G-Host and MR is G-MS/G-RS. In the wired access network, MH is Host and MR is RG.

 The dual-stack EMO processing protocol stack is shown in Figure 6. Only one layer of MIP tunnel is required between the CoA (ie, MR) of the HA and MH networks. For WiMA networks, 802.16 between G-MS/G-RS and BS uses the IP CS sublayer. The BS/AN supports the IP Bridging function, that is, the BSZAN can be aware of IP (IP awareness), but does not need to support routing. The MR forwards data through the Layer 2 protocol instead of the Layer 3 route.

 Control surface processing:

 1) The NEMO Client initiates an IPv6 registration request based on the IPv4 network prefix binding of the MR and MH networks, and includes information for informing the HA to receive the IPv4 data packet sent from the MR of the MR and MH networks to the HA through the reverse tunnel;

 2) HA binds the IPv4 network prefix of the MR and MH networks to the CoA of the MR and MH networks according to the received IPv6 registration request based on the IPv4 network prefix binding;

 3) Broadcast the reachability of the IPv4 network prefix of the MR and MH networks in the home link.

 Data surface processing:

 When the IPv4 data packet CN->MH, includes:

 1) The IPv4 packet sent by CN (SA=CN IPv4@, DA=MH's IPv4 HoA) is intercepted by HA;

 2) HA performs the first layer of MIPv6 tunnel (SA=HA IPv6@, DA=MR and MH network)

CoA) package;

 3) When the MR receives the IP packet of the single-layer encapsulation, strips the MIPv6 tunnel encapsulation, and then obtains the IPv4 packet to be sent to the MH, and the MR sends the IPv4 packet to the MH via the MR link.

 There are two cases of MH ->CN, including:

 The first one is the case of no reverse tunnel. The IPv4 packet sent by the MH (SA=MH's IPv4 HoA, DA=CN IPv4@) is sent directly to the CN;

 The other is the case of a reverse tunnel:

1) The IPv4 packet sent by the MH (SA=MH's IPv4 HoA, DA=CN IPv4@) is sent directly to the CN; 2) The IPv4 packet is first intercepted by the MR, and the IPv4 packet is sent to the HA through the MIPv6 tunnel (SA=MR and MH network CoA, DA=HAIPv6@);

 3) When the IP packet passing through the MIPv6 tunnel arrives at the HA, the MIPv6 tunnel encapsulation is stripped, and the IPv4 packet to be sent to the CN is obtained, and the HA sends the IPv4 packet to the CN.

 Embodiment 3: The visited network part supports IPv4, and the FA and mobile premises network support IPv6. The functional block diagram of Embodiment 3 of the present invention is shown in FIG. The visited network section supports IPv4, FA and mobile premises networks support IPv6.

 The dual-stack Proxy NEMO Client (proxy EMOv4 client) is set up in NAP to perform the function of dual-stack NEMO client control plane for proxy MR and MH networks:

 1. Support the functions of the NEMO customer control plane in the prior art;

 2. Support IPv4 registration function based on IPv6 network prefix binding, that is, dual-stack Proxy NEMO Client can initiate IPv4 registration request, including IPv6 network prefix of MR and MH networks, IPv6 HoA of MR and CoA of MR and MH networks; The IPv6 network prefix extension and the IPv6 HoA extension of the MR can be added to the IPv4 registration request message, and the IPv6 network prefix of the MR and MH networks and the IPv6 HoA of the MR are included as the new EMOv4 parameters. The IPv6 network prefix extension of NEMOv4 and the IPv6 HoA extension of MR can be defined in terms of TLV principles.

 MR needs to support the EMO Client data plane function (the movement brought by the CoA update is transparent to MR):

 1. Support the functions of the NEMOv6 customer data plane in the prior art;

 2. The following IPv6 MH can be connected to the MR;

 3 N to the MR and MH network IPv6 packets are sent to the MR IPv6 HoA via the IPv6 tunnel. The MR should be able to de-encapsulate the IPv6 packets. If the IPv6 packet destination address is MH's IPv6 HoA, the MR forwards the IPv6 packets. Give MH;

 4. The MR should be able to send the IPv6 packets from the MR and MH networks to the CN to the HA through the IPv6 reverse tunnel, and the source address of the reverse tunnel is the IPv6 HoA of the MR;

5, MR can support routing function; or, MR supports IP Bridging (IP bridging) function, that is, MR can sense IP (IP awareness), but does not support routing, MR does not use Layer 2 protocol Layer 3 routing for data forwarding.

 Set up dual stack FA in NAP for foreign agents acting as MH and MR:

 1. Support the functions of NEMOv4 FA in the prior art;

 2. Support tracking of MR IPv6 HoA;

 3. Receiving an IPv6 data packet that is sent to the FA via the IPv4 tunnel;

 4. The IPv6 data packet can be sent to the HA through the IPv4 reverse tunnel.

 5. (FACOA mode) notifies the dual-stack HA to send the IPv6 data packet to the IPv6 HoA of the MR through the IPv6 tunnel; this can be achieved by simply ignoring the IPv6 network prefix extension information in the IPv4 registration request and forwarding the IPv4 registration request as it is;

 6. (FACOA mode) informs the dual-stack HA to receive IPv6 packets sent from the IPv6 HoA of the MR to the HA through the IPv6 reverse tunnel; this can simply forward the IPv4 as it is by ignoring the IPv6 network prefix extension information in the IPv4 registration request. Registration request is implemented.

 Set up dual-stack HA in NSP for home agent acting as MH and MR (the movement brought by CoA update is transparent to MH):

 1. Support the functions of NEMOv4 HA in the prior art;

 2. Support dual IP addresses: 11 : 0^4@ and 11 八 1? ¥6@;

 3. Bind the IPv6 network prefix of the M and MH networks to the IPv6 HoA of the MR according to the received IPv4 registration request based on the IPv6 network prefix binding, and bind the IPv6 HoA of the MR to the CoA of the MR and MH networks ( FACOA mode);

 4. Broadcasting the accessibility of the IPv6 network prefix of the MR and MH networks in the home link, intercepting the IPv6 packet with the IPv6 network prefix of the destination address and MR network;

 5. (FACOA mode) According to the received IPv4 registration request based on the IPv6 network prefix binding, the HA sends the IPv6 data packet of the CN to the MR and the MH network to the MR through the dual IP hybrid tunnel, and the destination address of the outer IPv4 tunnel is MR. IPv4 CoA with the MH network, and the IPv6 HoA of the inner IPv6 tunnel destination address is MR;

6. (FACOA mode) According to the received IPv4 registration request based on the IPv6 network prefix binding, the HA receives the IPv6 data packet of the MR and MH network encapsulated by the dual reverse IP hybrid tunnel to the CN, The outer IPv4 reverse tunnel source address is the IPv4 CoA of the MR and MH networks, the inner IPv6 reverse tunnel source address is the IPv6 HoA of the MR; or the HA receives the reverse IPv6 tunnel encapsulated MR and the MH network to the CN IPv6 data. Packet, the source address of the reverse tunnel is the IPv6 HoA of the MR;

 7. In WiMA, MH is G-Host and MR is G-MS/G-RS. In the wired access network, MH is Host and MR is RG.

 Set the Authenticator in the NAP to provide the required dual-stack NEMO key for the dual-stack Proxy NEMO Client and the dual-stack FA, and provide authentication services for the MR and/or MH; set the AAA Server in the NSP for The HA provides the required dual stack EMO key, and the relevant information required by the EMO is obtained through the AAA information interactive retrieval process during the authentication process.

 The dual stack Proxy NEMO Client must be placed with the Authenticator.

 MR and FA belong to the same IP Link (connection).

 The HA device consists of dual-stack HA and dual-stack Mobility Bindings data storage; dual-stack Mobility Bindings are used to store IPv6 network prefix bindings for MR and MH networks.

 The Authenticator, dual stack Proxy NEMO Client, dual stack FA can form a FA device; MR and EMO Client form an MR device.

 FACOA mode dual stack NEMO processing protocol stack As shown in Figure 8, the MHV4 tunnel between HA and MH's CoA (ie MR) must be built on the MIPv4 tunnel between HA and MR CoA (ie FA). For WiMAX networks, 802.16 between G-MS/G-RS and BS uses the IP CS sublayer. The BS/AN supports the IP Bridging function, that is, the BS/AN can be aware of IP (IP awareness), but does not support routing. The MR forwards data through the Layer 2 protocol instead of Layer 3 routing. FA can also be combined with BS/AN.

 Control surface processing:

 1) The NEMO Client initiates an IPv4 registration request based on the IPv6 network prefix binding of the MR and MH networks;

2) The FA ignores the IPv6 network prefix extension information in the IPv4 registration request, and simply forwards the IPv4 registration request implementation to notify the HA to send the IPv6 data packet to the IPv6 HoA of the M through the tunnel, and notify the HA to receive the reverse tunnel from the MR. IPv6 HoA is delivered to the IPv6 packet of the HA; 3) The HA receives the IPv4 registration request based on the IPv6 network prefix binding, binds the IPv6 network prefix of the MR and MH networks to the IPv6 HoA of the MR, and binds the IPv6 HoA of the MR to the CoA of the MR and MH networks;

 4) Broadcast the reachability of the IPv6 network prefix of the MR and MH networks in the home link.

 Data surface processing:

 When the IPv6 packet is CN->MH, it includes:

 1) The IPv6 packet sent by CN (SA=CN IPv6@, DA=MH6 IPv6 HoA) is intercepted by HA;

 2) HA performs the first layer of MIPv6 tunnel (SA= HA IPv6)

Package

 3) HA further encapsulates the IP packet to the CoA of the MR and MH networks through the second layer MIPv4 tunnel (SA=HA IPv4 @, DA=MR and IPv4 CoA of the MH network);

 4) When the IPv6 packet passing through the two-layer MIP tunnel reaches the FA of the MR and MH networks, the second layer MIPv4 tunnel encapsulation is stripped, and an IPv6 packet encapsulated by the first layer MIPv6 tunnel to be sent to the MR, MR and The FA of the MH network sends the IP packet to the MR;

 5) When the MR receives the IP packet of the single layer encapsulation, the remaining first layer MIPv6 tunnel encapsulation is stripped, and then the IPv6 packet to be sent to the MH is obtained, and the MR sends the IPv6 packet to the MH via the MR link.

 There are three cases when an IPv6 packet is used by MH -> CN:

 One is the case of no reverse tunnel. The IPv6 packet sent by the MH (SA=MH IPv6 HoA, DA=CN IPv6@) is sent directly to the CN;

 The other is the case of a single reverse tunnel, the implementation process is as follows:

 1) The IPv6 packet sent by MH (SA=MH6 IPv6 HoA, DA=CN IPv6@) is sent to CN;

 2) The IPv6 packet is first intercepted by the MR, and the IPv6 packet is sent to the HA through the MIPv6 tunnel (SA=MR IPv6 HoA, DA=HA IPv6@);

3) When the IP packet passing through the MIPv6 tunnel arrives at the HA, the MIPv6 tunnel encapsulation is stripped, and then the IPv6 packet to be sent to the CN is obtained, and the HA sends the IPv6 packet to the CN. The other is the case of a double reverse tunnel, which is executed as follows:

 1) The IPv6 packet sent by MH (SA=MH IPv6 Ho A, DA=CN IPv6@) is sent to

CN;

 2) The IPv6 packet is first intercepted by the MR, and the IPv6 packet is sent to the HA through the first layer MIPv6 tunnel (SA=MR IPv6 HoA, DA=HAIPv6@);

 3) The IP packet encapsulated by the first layer MIPv6 tunnel is intercepted by the FA of the MR, and further the IP packet is sent to the HA through the second layer MIPv4 tunnel (the SA=MR and the IPv4 CoA of the MH network, DA=HAIPv4@);

 4) When the IP packet of the two-layer MIP tunnel arrives at the HA, the second layer MIPv4 tunnel encapsulation and the first layer MIPv6 tunnel encapsulation are stripped in turn, and then the IPv6 packet to be sent to the CN is obtained, and the HA sends the IPv6 packet to the CN. .

 Through the invention as described above, an IPv4 service operator can provide an access service for a pure IPv6 host under a multi-host architecture; thereby providing a seamless, efficient, and inexpensive solution for the transition of an existing IPv4 mobile network to an IPv6 mobile network. Solution: The IPv6 service provider can provide access services for pure IPv4 hosts under the multi-host architecture; thus providing an effective guarantee for protecting the terminal investment of the original IPv4 users under the new IPv6 mobile network; MH, MH does not need to implement mobile IP, function single; dual-stack agent NEMO customers can be set on the network side, registration and de-registration operations do not waste air interface resources; support FACOA mode and CCOA mode.

 While the above description is only an embodiment, it is not intended that the scope of the invention be limited to the embodiments described. All other embodiments obtained by modifications, equivalents, and substitutions by those skilled in the art based on the embodiments of the present invention are within the scope of the present invention.

Claims

Rights request A multi-host access method supporting hybrid IP, which is characterized in that:  A dual stack network mobile client or a dual stack proxy network mobile client initiates a second IP version registration request based on the first IP version network prefix binding of the mobile router MR and the mobile host MH network; and utilizes the second IP version tunnel or reverse Tunneling the first IP version data packet;  The home agent binds the first IP version network prefix of the MR and MH networks to the care-of address of the MR and MH networks according to the received second IP version registration request, and performs the first IP version data packet based on the binding relationship. transmission.  2. The method of claim 1, further comprising:  The foreign agent forwards the second IP version registration request to the home agent.  3. The method according to claim 2, wherein the process of binding the first IP version network prefix of the MR and MH networks to the care-of address of the MR and MH networks comprises:  Binding the first IP version network prefix of the MR and MH networks to the home address of the first IP version or the second IP version of the MR and MH networks;  Binding the first IP version or the second IP version home address of the MR and MH networks to the care-of addresses of the MR and MH networks.  4. The method of claim 1, 2 or 3, characterized in that  The first IP version includes IPv4, and the second IP version corresponds to IPV6;  Or,  The first IP version includes IPV6, and the second IP version corresponds to IPv4.  The method according to claim 4, wherein when the first IP version includes IPV6 and the second IP version corresponds to IPv4, the first IP version data is performed based on the binding relationship. The process of packet transmission, including:  The home agent passes the double IPv4 registration request based on the IPv6 network prefix binding. The IPv4 tunnel sends IPv6 packets from the communication node to the MR and MH networks to the MR. The destination address of the outer tunnel is the IPv4 care-of address of the MR and MH networks. The destination address of the inner tunnel is MR and MH. IPv4 home address of the network;  Or,  The home agent sends the IPv6 data packet of the communication node to the MR and MH networks to the MR through the dual IP hybrid tunnel according to the received IPv4 registration request based on the IPv6 network prefix binding. The destination address of the outer IPv4 tunnel is MR and MH. The IPv4 care-of address of the network, and the destination address of the inner IPv6 tunnel is the IPv6 home address of the MR;  Or,  The home agent receives the IPv6 registration request based on the IPv6 network prefix binding, and receives the IPv6 data packet of the MR and MH network encapsulated by the dual reverse IPv4 tunnel to the communication node, and the outer reverse tunnel source address is the MR and MH network. IPv4 care-of address, the inner reverse tunnel source address is the IPv4 home address of the MR and MH networks;  Or,  The home agent receives the IPv6 registration request based on the IPv6 network prefix binding, and receives the IPv6 data packet of the MR and MH network encapsulated by the reverse IPv4 tunnel to the communication node, and the source address of the reverse tunnel is the IPv4 of the MR and the MH network. Home agent.  The method of claim 4, wherein when the first IP version includes IPV6 and the second IP version corresponds to IPv4, the first IP version data is performed based on the binding relationship. The process of packet transmission, including:  The home agent sends the IPv6 data packet of the communication node to the MR and the MH network to the MR through the IPv4 tunnel according to the received registration request, and the tunnel destination address is the care-of address of the M and MH networks; or  The home agent receives the IPv6 registration request based on the IPv6 network prefix binding, and receives the IPv6 data packet of the MR and MH network encapsulated by the reverse IPv4 tunnel to the communication node, and the source address of the reverse tunnel is the handover of the MR and MH networks. address. The method according to claim 4, wherein when the first IP version includes IPV4 and the second IP version corresponds to IPv6, the first IP version data is performed based on the binding relationship. The process of packet transmission, including: The home agent receives the IPv4 packet of the MR and MH network encapsulated by the reverse IPv6 tunnel to the communication node according to the received IPv6 registration request based on the IPv4 network prefix binding, and the source address of the reverse tunnel is the handover of the MR and the MH network. address.  8. A multi-host access system supporting hybrid IP, characterized in that:  Means for supporting a control plane function of a network mobile client, for initiating a second IP version registration request based on a first IP version network prefix binding of the mobile router MR and the mobile host MH network;  A device supporting a data plane function of a network mobile client, configured to transmit a first IP version data packet by using a second IP version tunnel or a reverse tunnel;  a home agent device, configured to bind a first IP version network prefix of the MR and MH networks to a care-of address of the MR and MH networks according to the received second IP version registration request; and perform first according to the binding relationship Transmission of IP version packets.  9. The system of claim 8 further comprising:  The foreign agent device is configured to forward the second IP version registration request to the home agent device.  10. The system according to claim 9, wherein the home agent device is specifically configured to: use a first IP version network prefix of the MR and MH networks, and a first IP version or second of the MR and MH networks Binding the IP address of the home address; binding the first IP version or the second IP version home address of the MR and MH networks to the care-of address of the MR and MH networks; and performing the first based on the binding relationship Transmission of IP version packets.  11. The system of claim 8 or 9, wherein  The apparatus for supporting the control plane function of the network mobile client includes: MR and a dual-stack network mobile client;  The device for supporting the data plane function of the network mobile client includes: a dual stack proxy network mobile client. 12. The system of claim 11 wherein:  a mobile IPv4 tunnel is set up between the home agent and the MR, and the mobile IPv4 tunnel is built on a mobile IPv4 tunnel between the home agent and the foreign agent;  Or, a mobile IPv6 tunnel is set between the home agent and the MR, and the mobile IPv6 tunnel is constructed. a mobile IPv4 tunnel between the home agent and the foreign agent; or a single-layer mobile IPv6 tunnel between the home agent and the MR; or  A single layer mobile IPv4 tunnel is disposed between the home agent and the MR.  13. The system of claim 12, wherein:  The dual-stack network mobile client is further configured to: notify the home agent to receive an IPv4 data packet sent from a care-of address of the MR and the MH network through a reverse tunnel by using an IPv6 network prefix-based IPv6 registration request;  Or,  The dual-stack network mobile client is further configured to: notify the home agent to receive an IPv6 data packet sent from a care-of address of the MR and the MH network through a reverse tunnel by using an IPv4 network prefix-based IPv4 registration request.  14. A mobile routing device, comprising:  Mobile router MR, used to connect the customer premises network and the visited network;  The dual-stack network mobile client supports the IPv4 home address and the IPv6 home address, and is used to initiate an IPv4 registration request based on the IPv6 network prefix to notify the home agent to send the IPv6 data packet to the care-of address of the MR and MH network through the tunnel, or notify the hometown. The proxy receives IPv6 packets sent to the home agent from the care-of address of the MR and MH networks through the reverse tunnel.  15. A foreign agent device, comprising:  a dual-stack proxy network mobile client, configured to initiate an IPv4 network prefix-based IPv4 registration request; a foreign agent, configured to forward the IPv4 registration request, to notify the dual-stack home agent to send the IPv6 data packet to the mobile router MR through the tunnel The home address, or notify the dual-stack home agent to receive the IPv6 packet sent from M's IPv4 home address through the reverse tunnel.  16. A foreign agent device, comprising: a dual-stack proxy network mobile client, configured to initiate an IPv4 network prefix-based IPv4 registration request; a foreign agent, configured to forward the IPv4 registration request, to notify the dual-stack home agent to send the IPv6 data packet to the mobile router MR through the IPv6 tunnel The IPv6 home address, or the dual-stack home agent is notified to receive IPv6 packets sent from the MR's IPv6 home address through the IPv6 reverse tunnel. 17. A home agent device, characterized by comprising:  The dual-stack home agent is configured to establish a binding between the IPv6 network prefix of the MR and the MH network and the IPv4 home address of the MR according to the received IPv4 registration request based on the IPv6 network prefix;  Dual stack mobile bonded memory for storing IPv6 network prefix bindings for MR and MH networks.  18. A home agent device, characterized by comprising:  The dual-stack home agent is configured to bind the IPv4 network prefix of the MR and MH networks to the IPv6 home address of the M and MH networks according to the received IPv6 network prefix-based IPv6 registration request, and bind the MR IPv6 home address with the MR Bind to the care-of address of the MH network;  Dual stack mobile bonded memory for storing IPv4 network prefix bindings for MR and MH networks.  19. A home agent device, characterized by comprising:  The dual-stack home agent is configured to establish an IPv6 network prefix of the MR and MH networks and a home address of the IPv6 of the MR according to the received IPv4 network prefix-based IPv4 registration request, and establish an IPv6 home address and MR of the MR. Binding to the care-of address of the MH network;  Dual stack mobile bonded memory for storing IPv6 network prefix bindings for MR and MH networks.