WO2009109072A1 - 一种实现移动节点在IPv4/v6混合网络中的通信方法 - Google Patents

一种实现移动节点在IPv4/v6混合网络中的通信方法 Download PDF

Info

Publication number
WO2009109072A1
WO2009109072A1 PCT/CN2008/000528 CN2008000528W WO2009109072A1 WO 2009109072 A1 WO2009109072 A1 WO 2009109072A1 CN 2008000528 W CN2008000528 W CN 2008000528W WO 2009109072 A1 WO2009109072 A1 WO 2009109072A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
ipv4
network
mobile
address
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2008/000528
Other languages
English (en)
French (fr)
Inventor
马争鸣
向征
谭庆宇
熊佳妮
郑婵娟
梁文浩
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sun Yat Sen University
Original Assignee
Sun Yat Sen University
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sun Yat Sen University filed Critical Sun Yat Sen University
Publication of WO2009109072A1 publication Critical patent/WO2009109072A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/02—Inter-networking arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/167—Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H04W80/045—Network layer protocols, e.g. mobile IP [Internet Protocol] involving different protocol versions, e.g. MIPv4 and MIPv6
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements

Definitions

  • the present invention relates to the field of network and mobile communications, and to a communication method of a mobile node in an IPv4/v6 hybrid network.
  • IPv4/v6 hybrid network Existing prison before the present invention
  • Mobile IP research 3 ⁇ 4 1 network to support the problem of communication, specifically, mobile IPv4 research IPv4 network bears mobile communication problems, mobile IPv6 research IPv6 network clock communication problem, mobile IPv4/v6 is to study IPv4/v6 network bearer Mobile communication issues.
  • FIG. 1 is a schematic diagram of the basic principles of the Mobile IPv6 technology described in RFC 3344. The steps are as follows:
  • the mobile node moves from the local network to the foreign network
  • the mobile node may also selectively iiM: the Agent Solicitation Message requests the mobile agent of the link to report the message to its ar;
  • the mobile node receives the mobile generation ar message, and judges that it is in the home network according to the message; (5) if the mobile node finds that it is moving to the foreign network, the berth network obtains a forwarding address. Transfer is also 3 ⁇ 41: can be assigned by a foreign agent, or can be obtained by means of DHCP, etc.;
  • the mobile node sends a registration request message to the home agent to register its care-of address.
  • the format of the registration request message is shown in Figure 2A, which includes the mobile node's home address, home agent address, forwarding address, m rn, and the extension department contains the identification between the mobile node and the home agent.
  • the extension part also includes the recognition of the iiE « between the mobile node and the foreign agent ; the registration request eliminates the registration response message of the "minor".
  • the hometown generation 3 « ⁇ describes the registration request message, creates a prayer cache, and hardly registers the response message with the mobile node to notify the mobile node of the registration result.
  • the format of the registration response message is as shown in FIG. 2B, which includes the home address of the mobile node, the home agent address, and the resistance ring, m, including some recognition in the extension unit.
  • the source address is the address of the pass point
  • the destination address is the home address of the mobile node.
  • the transfer address to the mobile node after interception by the township agent is the mobile node ⁇ 3 ⁇ 4 «
  • the source address is the home address of the mobile node
  • the destination address is the address of the ®it1? point, so the message does not need to pass through the home network.
  • FIG. 3 is a diagram of the 3 ⁇ 4* principle of the mobile IPv6 technology described in RFC 3775. The key steps are as follows:
  • the mobile node moves from the local network to the foreign network
  • the mobile node Return Routability Procedure (RRP) process includes four messages, that is, the Home Test Init and Care-of Test Init messages sent by the mobile node to the communication node, and their respective response messages Home Test and Care- The Test message, where the Horae Test Init message and the Home Test message are forwarded by the home agent.
  • the purpose of the RRP process is to ensure that the mobile node's home address and 3 ⁇ 4t address are reachable.
  • Figure 5 is a flow chart of RRP in the Mobile IPv6 technology described in RFC3775.
  • the mobile node After the RRP process ends, the mobile node sends a new message to the Xie tl? point;
  • the first is the "two-way" approach.
  • the earned text sent by the communication node is routed to the home network, the home agent intercepts the data message and tunnels the message to the mobile node, and the mobile node sends the message back. Go to the home network, and then the network fiber to the communication node. In this way, the pass point does not need to know the current location information of the mobile node.
  • the second is the "route optimization" approach. This type of thank-you allows the communication node to call the mobile node's care-of address, mrn ⁇ , and the mobile node must register with the correspondent node to let the pass-through know the binding of its home address to the transfer address.
  • the mobile IPv4/v6 solution depends on how the IPv4 network is mixed with the IPv6 network.
  • IETF recommendation three ways: Mobile IPv4 / v6 solutions awake (RFC3053), dual-stack (RFC2893) and a NAT- PT (RFC2766) 0 proposed by the present invention based on the NAT-PT.
  • ⁇ - ⁇ is a network layer device that can be transparent to both IPv4 and IPv6.
  • the NAT-mechanism is transparent to the same side of the IPv4 network and the IPv6 network by adding a fine-layer gateway.
  • ftp-ALG and DNS-ALG have become standard features of NAT-PT.
  • Figure 6 shows the working principle of DNS query for IPv4/v6 hybrid network using ⁇ - ⁇ gateway plus DNS-ALG. As shown in Figure 6, it is a key step of implementing DNS-Si to the IPv4/v6 hybrid network using NAT-PT gateway plus DNS-ALG. Under the #3 ⁇ 4 port: (1) The IPv6 host should be connected to the IPv4 host, but I don't know what the IPv6 address of the IPv4 host is.
  • IPv4 a DNS request message is issued to ask IPv4, com's IPv6 address, and the DNS request message is transmitted to the DNS server A in the IPv6 network, but the IPv6 record is not found in the DNS server A in the IPv6 network (the IPv6 record is A6 or Is AAAA, and the record of IPv4 is A);
  • the DNS-ALG changes the A6 or MM in the request message to A and forwards it to the IPv4 network.
  • the DNS server B in the IPv4 network receives the request message and replies to the address of the IPv4 host as 202. 116. 78. 11;
  • the DNS-ALG After receiving the address information, the DNS-ALG adds a 96-bit prefix to the IPv4 address to become an IPv6 address prefix: :202. 116. 78. 11;
  • DNS-ALG will change the A to A6 or MM and continue to send the DNS response back to the DNS server in the IPv6 network.
  • IPv6 host considers the address of IPv4, com as prefix: :202. 116. 78. 11, so the source address is 3FFE: 3600.-B: :2, and the destination address is prefix: :202. 116. 78. 11 IPv6 packet;
  • the conversion gateway converts the group header into an IPv4 packet header according to the address relationship of the granularity, the incoming address and the semantic conversion, and the source address in the packet header is "203. 69. 0. 1" and the destination address is "202". 116. 78. 11", then send a packet to the IPv4 network.
  • the reason why the IPv4 host queries the IPv4 address of the IPv6 host is the same, and the communication vine is basically the same.
  • the IETF has already deployed the mobile IPv4 solution (RFC3344) and the mobile IPv6 solution (RFC3775), which is a relatively complete solution for mobile IP in pure IPv4 networks and pure IPv6 networks.
  • RFC mobile IPv4/v6 hybrid network
  • the mobile communication problem of IPv4/v6 hybrid network can be from static angle and dynamic. Corner play! ] is divided into the following 16 questions:
  • Step A1 specifically includes:
  • the home agent and communication node are located in the IPv6 network, and the mobile node moves IPv4 in the IPv4/v6 hybrid network;
  • the home agent is located in the IPv6 network, the communication node is located in the IPv4 network, and the mobile node moves IPv4/v6 when moving in the IPv4/v6 hybrid network;
  • the home agent is located in the IPv4 network, the communication is located in the IPv6 network, and the mobile node moves IPv4/v6 when moving in the IPv4/v6 hybrid network.
  • step A2 the basic problem of the households in step A1 is divided into four questions, and the steps ⁇ 2 specifically include:
  • A23 Mobile IPv4/v6 when the mobile node moves from the IPv network to the IPv6 network;
  • the present invention defines a representation of some terms, and Figure 7 is an abbreviation of some terms used in the present invention and an explanation thereof.
  • the left column of the figure is the original term, and the right column of the figure is the abbreviation of the term, and the present invention adopts the term abbreviated 3 ⁇ 4*3 ⁇ 4 line of the description of the invention.
  • the ship of the invention adds "v4" or "v6" *3 ⁇ 4 to the version 4 or version 6.
  • MIPv4 Mobile IPv4 MIPv4 Mobile IPv4
  • CNv6 represents the home address of the IPv6 network in the IPv6 network and the HoAv6 IPv6 format.
  • the ⁇ - ⁇ network is different for different addresses.
  • the address of the IJ table is the address in the IPv4 address pool in the NAT-PT, in relation to an IPv6 address.
  • CNAv4# is one of the IPv4 address pools in the ⁇ - ⁇ , which is mapped to CNAv6 and is the address label of CNv6 in the IPv4 network. Knowledge. The IPv4 format data message with the CNAv4# destination address will be routed to ⁇ - ⁇ .
  • ⁇ - ⁇ is preceded by an "*" in an IPv6 address
  • the address is 1 33 ⁇ 43 ⁇ 43 ⁇ 4 ⁇ 4 by an IPv4 address and a 96- ⁇ 96-bit address prefix thief.
  • CoAv6* is composed of a 96-bit address prefix of CoAv4 and NAT-PT, and is an address identifier of MNv4 in an IPv6 network.
  • the IPv6 format of the CoAv6* destination address is routed to ⁇ - ⁇ .
  • the object of the present invention is to overcome the deficiencies of the prior art, and to implement a method for a mobile node in an IPv4/v6 hybrid network, which effectively solves the mobile node's mobile communication in an IPv4/v6 hybrid network.
  • the problem is complicated, and at the same time, the mobile communication device to be seen by the present invention does not need a large upgrade, and has great practical value.
  • a communication method for implementing a mobile node in an IPv4/v6 hybrid network implementing an IPv4/v6 hybrid network by setting a mobile IPv4/v6 conversion gateway between an IPv4 network and an IPv6 network
  • the mobile M mobile network includes a NAT-PT network, and the mobile IP surface layer gateway provided thereon, wherein the NAT-PT network has a DNS-ALG.
  • the steps of the mobile node in the IPv4/v6 hybrid network are:
  • Step A is: The mobile IPv4/v6 conversion gateway realizes mutual transparency of RFC3344 and RFC3775 by acting as different entities described in RFC3344 and RFC3775 in the IPv4 network and the IPv6 network, respectively, and by performing transformation between entities within the gateway.
  • the step A specifically includes:
  • the Mobile IPv4 VIII Transition Gateway acts as an entity described in RFC 3344 on the IPv4 network side. This entity ties with other reals in the IPv network as a mobile IP model as described in RFC 3344. This mobile IP model is in accordance with RFC 3344. Described mobile IPv4 co-brain and new;
  • the Mobile IPv4/v6 Transition Gateway acts as an entity described in RFC 3775 on the IPv6 network, and the entity and the other entities in the IPv6 network form a Mobile IP model as described in RFC 3775. This mobile IP model moves as described in RFC 3775. IPv6 co-test and ff ;
  • Step B is: The mobile IPv4/v6 translation gateway is responsible for mobile IP related to the IPv4 network; ⁇ to the IPv6 network. Various message and polygon messages are converted, and are responsible for converting various mobile and IP related messages and polygons sent from the IPv6 network to the IPv network. Specifically, the step B includes:
  • the mobile IPv4/v6 conversion gateway is responsible for converting the message description message described in RFC3344 into the binding new message described in RFC3775, and converting the registration response message described in RFC3344 into the binding confirmation message described in RFC3775;
  • the mobile IPv4/v6 conversion gateway is responsible for converting the binding new message described in RFC3775 into the note request message described in RFC3344, and converting the binding acknowledgement message described in RFC3775 into the registration response message described in RFC3344;
  • the mobile IPv4/v6 conversion gateway is responsible for the conversion of the datagram and the address protocol, and in the IPv6 network.
  • the care-of address in the IP header of the IPv6 format data packet is exchanged with the home address in the extension header.
  • Step C is: The mobile IPv4/v6 conversion gateway intercepts the mobile IP-related message and polygon message according to the following principles: During the update, the message is intercepted according to the message; in the communication, according to the «destination destination address of the message ⁇ message; specifically, the step C includes:
  • the mobile IPv4/v6 conversion gateway acts as a different entity according to different communication situations, since the packets with the IP address of these entities as the destination address will be transferred to the mobile IPv4/v6 conversion gateway.
  • the mobile IPv4/v6 conversion gateway intercepts the polygon packet with the IP address of the IP entity as the destination address;
  • the mobile IPv4/v6 conversion gateway intercepts the message according to the message, and the method further includes:
  • the message that the mobile ⁇ 4/ ⁇ 6 conversion gateway needs to process has the message request and registration response message described in RFC3344, and the newly defined proxy request message and proxy message in the present invention, ⁇ 3 ⁇ 4 four messages.
  • the mobile IPv4/v6 conversion gateway is intercepted at the network layer according to the UDP encapsulation and destination port number of the message, and is distinguished at the application layer according to the load type value of the message; C22.
  • the message required by the mobile IPv4 VIII conversion gateway is RFC3775.
  • Step D The mobile IPv4/v6 conversion gateway uses the security mechanism of the RFC3344 communication when processing the IPv4 format message and the bribe message, and adopts the surname mechanism of the RFC3775 when processing the IPv6 format message and the drawing message; Yes:
  • the steps are as follows: The requirements of the present invention for realizing the mobile node in the ⁇ 4/ ⁇ 6 hybrid network in the ft ⁇ method for the home agent and the communication node and the requirements described in RFC3344 and RFC3775, but increasing the number of nodes Claim.
  • This step E is specifically ⁇ ⁇ Step E specifically includes ⁇
  • the mobile node warehouse meets the requirements for mobile nodes described in RFC3344 and RFC3775 on the same day;
  • the mobile node Xia has recorded the home agent and the pass-through of the 3 ⁇ 41 ⁇ 2, the outgoing DNS Si Xun way to find the mobile IPv4/v6 conversion gateway, and get the address of the home agent and the general point;
  • the mobile node can support the extension of the registration request message and the registration response message, and generate and process the proxy request message and the proxy message.
  • Step F When the home agent is located in the IPv4 network, the access point is located in the IPv6 network, and the key steps of the mobile IPv4/v6 when the mobile node moves in the IPv4/v6 hybrid network include:
  • the mobile node converts the gateway dimension proxy request message to the mobile IPv4/v6, requesting the mobile IPv4/v6 switching network to initiate the mobile node to the point in the IPv6 network.
  • the mobile node After the mobile IPv4/v6 conversion gateway receives the proxy request message, the mobile node sends a call to the IPv6 network ⁇ :, at this time, the mobile ⁇ 4/ ⁇ 6 conversion gateway is on the IPv6 network ⁇ After acting as the home agent in the IPv6 format and the mobile node in the IPv6 format, the mobile IPv4 VIII switching gateway sends a pickup message to the mobile node in the IPv4 network after receiving the binding confirmation message;
  • the format of the delete request message is the same as the format of the message in RFC3344.
  • the format of the message is the same as the format of the registration response message in RFC3344, and the value of the proxy request is tentatively set to 7.
  • the type value of the spam message is tentatively set to 8.
  • FIG. 1 is a diagram of the basic principles of the mobile IPv4 technology described in RFC 3344;
  • 2A is a format of a registration request message
  • 2B is a format diagram of a registration response message
  • Figure 3 is a 3 ⁇ 4 ⁇ diagram of the 3 ⁇ 4 ⁇ principle of the mobile IPv6 technology described in RFC3775;
  • Figure 4 is a schematic diagram of the format of the binding message
  • Figure 4 is a schematic diagram of the format of the binding confirmation message
  • FIG. 5 is a flow chart of RRP in Mobile IPv6 as described in RFC3775;
  • Figure 6 is a schematic diagram showing the operation of the DNS 3 ⁇ 41 of the ⁇ 4/ ⁇ 6 network using the ⁇ - ⁇ gateway plus DNS-ALG;
  • Figure 7 is an abbreviation of some terms in the present invention and its explanation;
  • Figure 8 is a schematic diagram of MIPv4/v6_TG acting as a different entity for a specific communication situation in the present invention
  • Figure 9 is a schematic diagram of the layout of the HA and the CN in the IPv6 network and in the IPv4 VIII hybrid network;
  • FIG. 10 is a schematic diagram of a mobile IPv4/v6 solution when both the HA and the CN are located in an IPv6 network and are displayed in an IPv6 network;
  • FIG. 11 is a diagram showing that both the HA and the CN are located in the IPv6 network, and the MIPv4/v6-TG is moved when the doctor moves in the IPv4 network.
  • Schematic diagram of address configuration Figure 12 is a communication flow chart when both the HA and the CN are located in the IPv6 network and the abdomen moves in the IPv4 network;
  • Figure 13 is a flow chart when both HA and CN are located in an IPv6 network and M is moved in an IPv4 network;
  • Figure 14 is a flow chart of the update when both the ⁇ and CN are located in the IPv6 network and ⁇ move from the IPv6 network to the IPv network;
  • Figure 15A shows the format of the registration request message when both the ⁇ and CN are located in the IPv6 network and ⁇ move from the IPv6 network to the IPv4 network.
  • 15B is a format diagram of a registration response message when both the UI and the CN are located in the IPv6 network and read from the IPv6 network to the IPv4 network;
  • Figure 16 is a schematic diagram of a mobile ⁇ 4/ ⁇ 6 solution when both ⁇ and CN are located on an IPv6 network and have just moved from an IPv4 network to an IPv6 network;
  • Figure 17 is a schematic diagram showing the layout of the HA and CN moving in the IPv4 network and moving in the IPv4/v6 hybrid network;
  • FIG. 18 is a schematic diagram of a mobile IPv4/v6 solution when both the HA and the CN are in the IPv4 network and the mobile in the IPv4 network;
  • FIG. 19 is the address configuration of the MIPv v6-TG when both the HA and the CN are located in the IPv4 network and the MN moves in the IPv6 network.
  • schematic diagram; 20 is a communication flow chart when both the HA and the CN are located in the IPv4 network, and the MN moves in the IPv6 network;
  • FIG. 21 is a flowchart of updating when the HA and the CN are standing on the IPv network and the MN moves in the IPv6 network;
  • FIG. 22 is a flow chart of updating when both the HA and the CN are located in the IPv4 network and the MN is moving from the IPv4 network to the IPv6 network;
  • FIG. 23 is a mobile IPv4/v6 solution when both the HA and the CN are in the IPv4 network and continue to move from the IPv6 network to the IPv4 network. Schematic diagram of the scheme;
  • FIG. 24 is a layout diagram of the HA being located in the IPv6 network, the CN being located in the IPv network, and the MN moving in the IPv4 VIII hybrid network;
  • FIG. 25 is the MIPv4/v6-TG when the HA is located in the IPv6 network, the CN is located in the IPv4 network, and the MN is moving in the IPv6 network. Address configuration diagram;
  • FIG. 26 is a communication flow chart when the HA is located in the IPv6 network, the CN is located in the IPv4 network, and the MN is moving in the IPv6 network;
  • FIG. 27 is a flowchart of updating when the HA is located in the IPv6 network, the CN is located in the IPv4 network, and the MN is moving in the IPv6 network; Is the address configuration of the MIPv4/v6-TG when the HA is located in the IPv6 network, the CN is in the IPv4 network, and the MN is moving in the IPv4 network;
  • FIG. 29 is a flow chart of communication when the HA is located in the IPv6 network, the CN is located in the IPv network, and the leg is moving in the IPv4 network;
  • FIG. 30 is a flowchart when the HA is located in the IPv6 network, the CN is located in the IPv4 network, and the MN is moving in the IPv4 network;
  • FIG. 32A is a schematic diagram showing the format expansion of a registration request message when the HA is located in the IPv6 network, the CN is located in the IPv4 network, and the slave is moved from the IPv6 network to the IPv4 network;
  • FIG. 32B is a format diagram of a registration response message when the HA is located in the IPv6 network, the CN is located in the IPv network, and the MN moves from the IPv6 network to the IPv network;
  • Figure 33 is a flow chart of the update when the HA is located on the IPv6 network, the CN is in the IPv4 network, and the slave is moving from the IPv4 network to the IPv6 network.
  • FIG. 34 is a schematic diagram of a layout in which an HA is located in an IPv4 network, CN is located in an IPv6 network, and a mobile network is in a hybrid network;
  • FIG. 35 is an address configuration of MIPv4/v6-TG when the network is located in an IPv4 network, CN is in an IPv6 network, and is continuously moving in an IPv4 network.
  • FIG. 36 is a communication diagram when the HA is located in the IPv4 network, the CN is located in the IPv6 network, and the MN is moving in the IPv4 network;
  • FIG. 37 is a flow chart when the HA is located in the IPv4 network, the CN is located in the IPv6 network, and is displayed in the IPv4 network;
  • 38 is the address of the MIPv4/v6-TG when the HA is located in the IPv4 network, the CN is in the IPv6 network, and continues to move in the IPv6 network.
  • FIG. 39 is a communication flow chart when the HA is located in the IPv4 network, the CN is located in the IPv6 network, and the MN is moving in the IPv6 network;
  • FIG. 40 is a new flowchart when the HA is located in the IPv4 network, the CN is located in the IPv6 network, and should be moved in the IPv6 network;
  • 43A is a format of a proxy request message when the HA is located in the IPv4 network, the CN is located in the IPv6 network, and the MN is moved from the IPv6 network to the IPv4 network;
  • Figure 43B is a format diagram of the proxy response message when the HA is located in the IPv4 network, the CN is in the IPv6 network, and continues to move from the IPv6 network to the IPv4 network.
  • the invention relates to a communication method for realizing a mobile node in an IPv4/v6 hybrid network, and the signaling method is to solve the sixteen problems of mobile IPV4/V6.
  • the home agent is located in the IPv4 network (denoted as ⁇ 4)
  • the communication node is located in the IPv6 network (denoted as CNv6)
  • the mobile node moves inside the IPv4 network (denoted as MNv4)
  • the MIPv4 is set between the IPv4 network and the IPv6 network.
  • /v6- TG the MIPv4/v6-TG acts as a communication node (denoted as QW4) on the IPv4 network side, and communicates with HAv4 and MNv4 as described in RFC33 4 for MIPv4.
  • MIPv4/v6-TG acts as a mobile node (denoted as MNv6) on the IPv6 network side, and ⁇ technology CN fi3 ⁇ 4 letter as described in RFC3775 with CNv6.
  • MIPv4/v6-TG internally converts between CNv4 and Mv6.
  • both HA and CN are located in the IPv6 network and are allowed to move in the IPv4 VIII hybrid network.
  • the whole t3 ⁇ 4 g can be divided into communication with the CN when the MN moves in the IPv6 network, and communication with the CN when the MN moves in the IPv4 network.
  • the communication with the CN when the MN moves from the IPv6 network to the IPv network and allows communication with the CN when moving from the IPv4 network to the IPv6 network. The communication in these cases will be described in detail below.
  • FIG. 10 is a schematic diagram of a solution for mobile IPv4/v6 when both HA and CN are located in an IPv6 network and MN moves in an IPv6 network.
  • Li moves in the IPv6 network
  • the cis, HA, and CN3 ⁇ 43 ⁇ 4IPv6 network which is a typical problem of MIP V 6, according to RFC3775 dimension
  • the described ⁇ technique is incorporated into the new and concrete implementation of Figure 3.
  • FIG 11 is a schematic diagram of address configuration of MIPv4/v6-TG when both HA and CN are located in an IPv6 network.
  • MIPv4/v6-TG acts as MNv6 on the IPv6 network side
  • CNv6 constitutes two entities of MIPv6 described in RFC3775, communicating according to the ⁇ technology described in RFC3775, in order to make MIPv4/v6-
  • the TG can replace the home address and the care-of address when sending data packets to the CNv6 on the IPv6 network side.
  • the MIP-ALG in the MIPv4/v6-TG must maintain the binding of the home address and the transfer address in the IPv6 format: HoAv6 ⁇ r CoAv6 *.
  • MIPv4/v6-TG acts as HAv4 when transmitting fixed messages, and acts as CNv4 when receiving messages, and M v4 constitutes three entities of MIPv4 technology described in RFC3344, according to MIPv4 technology described in RFC3344. Enter the letter.
  • the NAT-PT in MIPv4/v6-TG must maintain H 4v ⁇ ⁇ 4 ⁇ # and ⁇ 4 ⁇ HoAv4# addresses.
  • MIP-ALG must maintain the binding of the home address and care-of address in IPv4 format. : HoAv4 # ⁇ CoAv4.
  • the NAT-PT in MIPv4/v6-TG must maintain the address mapping of C W# CNAv6.
  • Figure 12 is a flow chart of communication when both HA and CN are in an IPv6 network and continue to move in an IPv4 network.
  • the specific communication steps include:
  • the MNv4 sends a message to the CNv6-dimensional IPv4 format, the address is HoAv f, and the destination address is CNAv4#. According to the destination address, such a message is sent to MIPv4/v6-TG.
  • the data packet of CNv6 to M v4 dimension IPv6 format the source address is CNAv6, the destination address is CoAv6*, and a second header is inserted in the packet, which includes HoAv6. According to the destination address, such a listening message is sent to MIPv4/v6-TG.
  • the MIP-ALG in the MIPvv6-TG removes the HoAv6 from the second type of routing header of the received data packet, and replaces the destination address from CoAv6* to HoAv6.
  • the NAT-PT X-inch MIP4/v6-TG data packet processed by MIP-ALG is translated by address protocol.
  • the converted data source address is CNAv4#, and the destination address is HoAv4#o.
  • the lit is sent to v4, the hidden source address is H v4#, and the destination address is CoAv4.
  • FIG. 13 is a flow chart of updating when both the HA and the CN are located in the IPv6 network and the MN moves in the IPv4 network, when the MN is in the IPv4 network.
  • the pressure is required;
  • MIPv4/v6-TG in the IPv4 network ⁇ «acts as HAv4, and MNv4 carries out the binding update of the home address and care-of address according to the MIPv4 3 ⁇ 4 ⁇ described in RFC334, that is, the hometown maintained in the MIP-ALG. The binding of the address to the care-of address.
  • MIPv4/v6_TG acts as MNv6 on the IPv6 network side, and HAv6 and CNv6 bind the home address and care-of address in accordance with MIPv6 3 ⁇ 4 ⁇ described in RFC37755.
  • the specific update steps include:
  • the message 4 is generated.
  • the source address of the registration request message is CoAv4
  • the destination address is the hall
  • the load includes HoAv.
  • the registration request message is sent to the MIPv4/v6-TG.
  • the MIPv4/v6-TG converts the received registration request message into a binding update message.
  • the source address of the binding update message is CoAv6*
  • the destination address is HAAv6
  • the payload includes HoAv6. According to the destination address, the binding new message is sent to HAv6.
  • HAv6 After receiving the binding update message, HAv6 first updates the binding of the home address and the care-of address that it maintains, and then
  • MIPv4/v6-TG replies with a binding confirmation message.
  • RRP authentication is required before MNv6 is bound to CNv6.
  • MIPv4/v6-TG will act as MNv6 to CNv6 RRP authentication.
  • RRP authentication is performed according to the procedure described in RFC37755. The specific steps of RRP are as follows: MIPv4/v6-TG first sends Home Test Init message and Care-of Test Init to CNv6 at the same time. The message, in which the Home Test Init message needs to pass the HAv6, Care-of Test Init message directly ⁇ CNv6; CNv6 receives the Home Test Init message and the Care-of Test Init message and then responds to the Home Test message and the Care-of Test message respectively. The Home Test message and the Care-of Test message are returned as they are.
  • MIPv4/v6-TG will set a new message to CNv6 3 ⁇ 43 ⁇ 4
  • CNv6 After receiving the binding update message, CNv6 first updates the binding of the home address and the care-of address maintained by itself, and then replies to the MIPv4/v6-TG with a binding confirmation message.
  • the 3 ⁇ 4MIP-ALG maintains the binding of the home address and the care-of address. Then, according to the MIPv4 technology described in RFC3344, the MIPv4/v6-TG generates a registration response message.
  • the source address of the registration reply message is HAAv4#
  • the destination address is CoAv4
  • the payload includes HoAv4#. According to the destination address, the registration response message is sent to break 4.
  • Figure 14 is a flow chart showing the update when both the HA and the CN are in the IPv6 network and the MN is moving from the IPv6 network to the IPv4 network.
  • ⁇ 3 ⁇ 4he ⁇ has two tasks, first to realize the binding of the home address and care-of address maintained by HAv6 and CNv6; the way of discovering MIPv4/v6- TG and MIPv4/ V6- TG into fi3 ⁇ 4 also address @23 ⁇ 4.
  • MIPv4/v6-TG acts as HAv4
  • MIPv4/v6-TG Acting as MNv6.
  • the specific 3 ⁇ 4» steps include:
  • the MNv4 domain name discovers MIPv4/v6-TG and obtains the address of HAv6 in IPv4 format HAAv4#.
  • the NAT-PT in MIPv4/v6-TG has the address: ⁇ HAAv4 #.
  • MNv4 generates a registration request message.
  • the source address of the registration request message is CoAv4, and the destination address is HAAv4#. Since MNv4 does not know ⁇ 4#, the home address of the registration request message is ,, and HoAv6 3 ⁇ 43 ⁇ 4fi is in the extended domain.
  • MIPv4/v6- TG obtains HoAv6, «: lookup address lW table to get CNAv6 and HAAv6 from the received registration request message, and obtain CoAv6* by adding 96-bit NAT-PT gateway prefix before CoAv4. Then, the MIPv6 technology described in RFC 3775, MIPv4/v6- TG generates the new message, the source address of the new message is CoAv6*, the destination address is H v6, and the load includes HoAv6. According to the destination address, the binding plane message is sent to HAv6.
  • HAv6 After receiving the binding ⁇ message, HAv6 binds the home address maintained by itself and the address of the transfer, and replies with a binding confirmation message to MIPv4/v6-TG.
  • RRP authentication is required before MNv6 binds to CNv6 Wei 3 ⁇ 4ff.
  • MIPv4 ⁇ -6-TG will act as MNv6 to CNv6 RRP authentication, and RRP authentication will follow the flow described in RFC37755.
  • the specific steps of RRP are as follows: MIPv4/v6-TG first sends Home Test Init message and Caxe-of to CNv6 at the same time.
  • CNv6 responds to the Home Test message and the Care-of Test message after receiving the Home Test Init message and the Care-of Test Init message .
  • the Home Test message and the Care-of Test message are returned as they are.
  • MIPv4/v6-TG will set a new message to CNv6 ⁇ 3 ⁇ 45.
  • CNv6 first updates the binding of the home address and the care-of address maintained by itself after receiving the binding update message, and then
  • MIPv4/v6-TG replies with a binding confirmation message.
  • the NAT-PT in the MIPv4/v6-TG establishes an address mapping: ⁇ HoAv4 #, MIP-ALG establishes address binding: HoAv4 # CoAv4 and ⁇ ⁇ CoAv6 *.
  • the MIPv4/v6-TG replies to the MNv4 with a registration response message.
  • MIPv4/v6-TG provides HoAv4# to MNv4 in the registration reply message.
  • the format of the registration response message at this time is as shown in FIG. 15B.
  • Figure 16 is a schematic diagram of a mobile IPv4/v6 solution when both HA and CN are located on an IPv6 network, that is, when moving from an IPv4 network to an IPv6 network.
  • the MN, HA, and CN are ⁇ IPv6 networks.
  • This is a typical MIPv6 problem, which will be in accordance with the MIPv6 described in RFC3775, and the specific implementation is shown in Figure 3. .
  • Figure 17 is a schematic diagram of the layout of the HA and the CN in the IPv4 network, and the mobile in the IPv4/v6 hybrid network.
  • both HA and CN are located in the IPv4 network, and the MN moves in the IPv4 VIII hybrid network.
  • the 3 ⁇ 4t ⁇ can be divided into M.
  • MN moves from IPv4 network to
  • Figure 18 is a schematic diagram of the solution of moving ⁇ 4/ ⁇ 6 when both ⁇ and CN are located in the IPv4 network and moving in the IPv4 network.
  • the circle moves within the IPv4 network, it should be, HA and CN
  • this is a typical MIPv4 problem, which will be based on the MIPv4 technology described in RFC3344, and the specific implementation has been implemented.
  • Figure 19 is a schematic diagram showing the address configuration of MIPv4/v6-TG when both HA and CN are located in the IPv4 network and the mobile device moves in the IPv6 network.
  • MIPv4/v6-TG acts as MNv4 on the IPv4 network side
  • CNv4 and HAv4 form the three entities of the MIPv4 technology described in RFC3344
  • the MIPv4 technology described in RFC3344 is used to enter the fi3 ⁇ 4 letter, in order to make MIPv4 ⁇ 6-TG acts as MNv4 on the IPv4 network side
  • NAT-PT in MIPv4/v6-TG must maintain the address mapping of Co W# ⁇ CoAv6.
  • MIPv4/v6-TG acts as CNv6, and MNv6 constitutes two entities of the MIPv6 technology described in RFC3775, communicating according to the MIPv6 technology described in RFC3775.
  • MIP-ALG in the MIPv4 6-TG must maintain the address binding of the v6* CoAv6.
  • Figure 20 is a flow chart of communication when both HA and CN are located in an IPv4 network and are allowed to move in an IPv6 network.
  • the specific communication steps include:
  • the MNv6 to CNv4 ⁇ M. IPv6 format ⁇ message the address is CoAv6, the destination address is CNAv6*, and the destination of the message is inserted into the hometown item of the extension item. Address HoAv6*. According to the destination address, such a 13 ⁇ 4@ message is sent to the MIPv4 VIII-6-TG.
  • the NAT- ⁇ gateway on the MIPv4/v6-TG will be sent to the MIP-ALG for processing according to the feature that the destination address of the packet is CNAv6*.
  • MIP-ALG takes HoAv6* from the home address option of the destination ffi extension of the
  • the source address of the converted message is HoAv4 and the destination address is CNAv4. According to the destination address, such a telegram is sent to CNv4.
  • CNv4 sends an IPv4 format message to MNv6.
  • the 3 ⁇ 4H address is CNAv4 and the destination address is HoAv4.
  • 3 ⁇ 4$g packets are sent to MIPv4/v6-TG.
  • MIP-ALG in MIPv4/v6-TG first decapsulates the received data message, and then hands it over to the NAT-PT gateway for conversion.
  • the translated source address is CNAv6*.
  • the destination address is HoAv6*.
  • the MIP-ALG in MIPv4/v6-TG takes out the CoAv6 from its own address binding ⁇ CoAv6, and converts it through NAT-PT.
  • the destination address of the data packet is replaced with CoAv6, and HoAv6* is filled in the second header of the flip message. According to the destination address, such a Sa message is sent to MNv6.
  • Figure 21 is a flow chart showing the update of HA and CN when they are both in the IPv4 network and when they are moving in the IPv6 network.
  • MNv6 moves the new destination address in the IPv6 network, for normal communication, according to RFC3775, ⁇ requires the binding of the home address and care-of address maintained by HAv6 and CNv6.
  • the new to H 6 is actually new to HAv4 in the IPv4 network, and the address binding maintained by the MIP-ALG in the new actual MIPv4/v6-TG of CNv6 is updated.
  • the specific more tired include:
  • MNv6 produces a new message
  • the address is CoAv6
  • the destination address is HAAv6*
  • the load includes the home address of Mv6 HoAv6*.
  • the binding new message is sent to MIPv4/v6 - TG.
  • the MIPv4/v6-TG converts the received binding update message into a registration request message, the address is CoAv f, the destination address is bilis v4, and the payload includes HoAv4. According to the destination address, the registration request message is sent to HAv4.
  • HAv4 is bound according to the received message: HoAv4 CoAv4#, generates a registration response message.
  • the source address of the registration response message is HAAv4, and the destination address is CoAv4A.
  • the load includes HoAv4 0. According to the destination address, the registration response message is sent to MIPv4-TG.
  • MIPv4/v6- TG converts the received response message into a binding confirmation message, which is difficult to address v6*, destination
  • the address is CoAv6 and the load includes ⁇ .
  • the binding confirmation message is sent to break 6.
  • the yang receives the binding confirmation message, and completes the binding of the home address and the transfer of the maintenance.
  • RRP authentication is required before ⁇ 6 is bound to CNv6.
  • the specific steps of RRP are as follows: ⁇ generates Home Test Init message, the source address of the Home Test Init message is HoAv6*, and the destination address is CNAv6*.
  • the Home Test Init message is sent to MIPv4/v6-TG through ⁇ 3 ⁇ 4.
  • MIPv4/v6- TG acts as HAv6, and the tunnel address is CoAv6 and HMv6*.
  • the MIPv4/v6-TG tunnel replies to the MNv6 Home Test message.
  • the source address of the Home Test message is CNAv6* and the destination address is HoAv6*.
  • Reading v6 generates a Care of Test Init message.
  • the source address of the Care of Test Init message is CoAv6 and the destination address is CNAv6*.
  • the Care of Test Init message is sent to ⁇ 4 ⁇ 6- TG, at which time MIPv4/v6_TG acts as CNv6.
  • MIPv4/v6- TG replies to Care of Test message to MNv6.
  • the Care of Test message source address is CNAv6*
  • the destination address is CoAv6.
  • MNv6 After RRP authentication ends, according to RFC3775, MNv6 generates and sends an update message.
  • the source address of the binding update message is CoAv6, the destination address is CNAv6*, and the payload includes ⁇ . According to the destination address, the binding Wei message is sent to the disconnection. 4 eight 6- TG.
  • MIPvVv6_TG new MIP-ALG maintains the address binding ⁇ * ⁇ CoAv6. Then, MIPv4/v6_TG will reply the binding confirmation message to MN v6.
  • Figure 22 is a flow chart of the update when both the HA and the CN are in the IPv4 network and the mobile device moves from the IPv4 network to the IPv6 network.
  • MNv6 ffi3l3 ⁇ 4gS mode finds MIPv4/v6-TG, and obtains the address of HAv4 IPv6 format HAAv6* 0
  • the Mv6 ⁇ query method finds MIPv4/v6-TG, and the address of CNv4 IPv6 format is CNAv6*.
  • the 6-bit binding update message the source address is CoAv6, the destination address is HAAv6*, and the payload includes HoAv6*.
  • HoAv6* is composed of HoAv4 and the 96-bit ⁇ - ⁇ address prefix extracted from HAAv6*. According to the destination address, the binding update message is sent to MIPv4/v6-TGo
  • the MIPv4/v6-TG After the MIPv4/v6-TG receives the binding new message, it will be in the AT-PT gateway, CoAv4 # CoAv6.
  • the binding new message received in the same day converts the game ship solicitation message, the source address of the registration request message is CoAv4#, the destination address is HAAv4, and the load includes HoAv4. According to the destination address, the registration request message is sent to 4.
  • HAv4 will update the address of the home address it maintains with the address of the care-of address, and reply to the MIPv4/v6-TG with a registration response message.
  • the MIPv4/v6-TG converts the received registration response message into a binding confirmation message and returns to the v6.
  • RRP authentication is required before MNv6 is bound to CNv6; ⁇ .
  • the specific steps of RRP are as follows: MNv6 generates a Home Test Init message, the source address of the Home Test Init message is HoAv6*, and the destination address is CNAv6*.
  • the Test Init message is sent to MIPv4 ⁇ -TG via H3 ⁇ 4.
  • MIPv4/v6-TG acts as HAv6, and the port address is CoAv6 and HMv6* 0 MIPv4/v6-TG tunnels reply to Home MNv6 Home Tes message.
  • the source address of the Home Test message is CNAv6*, and the destination address is ⁇ 6*.
  • ⁇ generates a Care of Test Init message
  • the source address of the Care of Test Init message is CoAv6, and the destination address is CNAv6*.
  • the Care of Test Init message is sent to MIPv4/v6-TG, at which time MIPv4/v6-TG acts as CNv6.
  • MIPv4/v6-TG replies to the Care of Test message to v6.
  • Care of Test message source CNAv6* ; destination address is CoAv6.
  • the hall After RRP authentication is completed, according to RFC3775, the hall generates a concurrent update message.
  • the source address of the binding Wei message is CoAv6, the destination address is CNAv6*, and the load includes HoAv6*. According to the destination address, the binding new message is sent. Go to MIPv4/v6-TG.
  • Figure 23 is a schematic diagram of a mobile IPv4/v6 solution when both HA and CN are located on an IPv4 network and move from an IPv6 network to an IPv4 network.
  • Figure 24 is a schematic diagram of the layout of the HA being located in the IPv6 network, the CN being located in the IPv4 network, and continuing to move in the IPv4 VIII hybrid network.
  • the HA is located in the IPv6 network
  • the CN is located in the IPv4 network
  • the CN is moved in the IPv4/v6 hybrid network.
  • the mapping can be divided into the communication with the CN when moving in the IPv6 network, and the communication with the CN when moving in the IPv4 network.
  • 25 is a schematic diagram of address configuration of the ⁇ 4 ⁇ 6-TG when the HA is located in the IPv6 network, the CN is in the IPv4 network, and the MN is moving in the IPv6 network.
  • MIPv4/v6-TG When moving in an IPv6 network, MIPv4/v6-TG acts as CNv6 on the IPv6 network side and RFC3775 on the MNv6 side.
  • the two entities of the described MIPv6 technology enter the fi3 ⁇ 4 letter according to the MIPv6 technology described in RFC3775, which is: Chad MIPv4/v6-TG performs the home address and care-of address when sending data packets to the MNv6 on the IPv6 network side.
  • the conversion, MIP-ALG in MIPv4/v6-TG must maintain the binding of the home address and the forwarding address in IPv6 format: ⁇ CoAv6.
  • MIPv4/v6-TG acts as ⁇ 4 when transmitting messages, and acts as ⁇ 4 when the message is sent, and CNv4 constitutes three entities of MIPv4 technology described in RFC3344, and enters the fi3 ⁇ 4 letter according to the MIPv4 technology described in RFC3344.
  • MIPv4/v6-TG acts as ⁇ 4 when transmitting messages, and acts as ⁇ 4 when the message is sent
  • CNv4 constitutes three entities of MIPv4 technology described in RFC3344, and enters the fi3 ⁇ 4 letter according to the MIPv4 technology described in RFC3344.
  • Figure 26 is a communication diagram when the HA is located in an IPv6 network, CN is in an IPv4 network, and M is moving in an IPv6 network.
  • the specific communication steps include:
  • ⁇ message, 3 ⁇ 4 address is CoAv6, the destination address is CNAv6*, and the home address is inserted in the home address option of the same day. HoAv6. According to the destination address, such a face message is sent to MIPv4/v6-TG 0.
  • MIP-ALG in MIPv4/v6-TG takes HoAv6 out of the received homepage 3 ⁇ 4B of the message, and replaces the source address of the message from CoAv6 to HoAv6c, then MIPv4/v6-TG NAT-PT network ⁇ X-inch report: 3 ⁇ 43 ⁇ 4 row address protocol conversion, the source address of the converted message is HoAv4#, the destination address is CNAv4. According to the destination address, such face messages are sent directly to CNv4 0
  • CNv4 sends a v6 'IPv4 format ⁇ message, the hard address is CNAv4, and the destination address is HoAv according to the destination address.
  • a face message is sent to MIPv4/v6_TG.
  • the packet received by the NAT-PT in the MIPv4/v6-TG is translated by the protocol.
  • the translated source address is CNAv6* and the destination address is HoAv6.
  • MIP-ALG in MIPv4/v6-TG removes CoAv6 from its own address binding H v6 CoAv6, and the destination address of the NAT-PT-converted data packet is from HoAv6 Wk CoAv6, and is reported in the medical report. Insert a second crane head into the text, which contains HoAv6. According to the destination address, such a flip message is sent to draw v6.
  • FIG. 27 is a flow chart showing an update when the HA is located in an IPv6 network, the CN is in an IPv4 network, and the MN is moving in an IPv6 network.
  • MNv6 moves in the IPv6 network and obtains a new care-of address, in order to maintain normal communication, according to RFC3775
  • ⁇ requires the binding of the home address and the transfer address maintained by ff HAv6 and CNv6.
  • MIPv4/v6-TG acts as CNv6 on the IPv6 network side, and three entities in the MIPv6 update with HAv6 and MNv6, and the new home address and care-of address binding maintained by HAv6 and CNv6 in accordance with RFC3775.
  • the home address and the transfer of the home address maintained by CNv6 are more
  • the new homepage MIP-ALG maintains the home address and the transfer of Zhao Nazhi.
  • the specific 3 ⁇ 4 outlines include:
  • MNv6 generates binding 3 ⁇ 4 new messages, !
  • the address is CoAv6, the destination address is HAAv6, and the load includes the home address HoAv6 of 6.
  • the binding plane message is sent to HAv6.
  • ⁇ After receiving the HSf message, ⁇ renews the binding of the home address and the forwarding address maintained by itself, and then replies to the binding confirmation message to M v6.
  • the source address of the binding confirmation message is HAAv6, and the destination address is CoAv6.
  • RRP authentication is required before MNv6 binds to CNv6.
  • MIPv4/v6-TG will act as CNv6.
  • RRP authentication is popular as described in RFC37755. The specific steps are as follows: M v6 firstly sends MIPv4/v6_TG ⁇ 3 ⁇ 4 Home Test Init message and Care_of Test Init message, where the Home Test Init message needs to go through HAv6, Care-of Test Init message directly Sent to MIPv4/v6- TG; After receiving the Home Test Init message and the Care-of Test Init message, MIPv4/v6-TG replies to the Home Test message and the Care-of Test message respectively, and the Home Test message and the Care-of Test message are in accordance with the original The road returns.
  • MNv6 After RRP authentication is completed, according to RFC3775, MNv6 generates and sends a binding update message.
  • the source address of the binding update message is CoAv6, the destination address is CNAv6*, and the load includes HoAv6.
  • the binding is based on the destination address.
  • the 3 ⁇ 4ff message is sent to MIPv4/v6-TG.
  • Figure 28 is a schematic diagram showing the address configuration of the MIPv4/v6_TG when the HA is located in the IPv6 network, the CN is in the IPv4 network, and the MN is moving in the IPv4 network.
  • MIPv4/v6-TG acts as v4 on the IPv4 network side
  • CNv4 and M v4 form the three entities of the MIPv4 technology described in RFC3344, communicating according to the MIPv4 technology described in RFC3344, in order to make MIPvVv6-TG acts as HAv4 on the IPv4 network side
  • NAT-PT in MIPv4/v6-TG must maintain H ⁇ 4v ⁇ HAAv4# address mapping
  • MIP-ALG must maintain ⁇ > CoAv4 address binding.
  • MNv4 is in the IPv4 format of the home address of the male address, therefore, the NAT-PT in the MIPv4/v6-TG must maintain the address mapping of the Ho4v6 HoAv4 #.
  • Figure 29 is a diagram showing the communication when the HA is located in the IPv6 network, the CN is in the IPv4 network, and the MN is moving in the IPv4 network.
  • the specific communication steps include:
  • MIPv4/v6_TG forwards the received ⁇ message to ⁇ v4, the source address of ⁇ is HAAv4#, and the destination address is CoAv4 0
  • Figure 30 is a flow chart showing the update of the HA when the IPv6 network is located, the CN is located in the IPv4 network, and the MN is moving in the IPv4 network.
  • M After M moves over the IPv4 network and obtains a new care-of address, in order to maintain normal communication, according to RFC3344, M requires a new 1 ⁇ 4 maintained home address and care-of address binding.
  • MIPvVv6-TG acts as HAv4 in IPv4 network H, and two entities in MIPv4 update with MNv4, and maintains the home address of MIP-ALG in MIPv4 ⁇ -TG according to the MIPv4 technology described in RFC3344.
  • MIPv4/v6-TG acts as MNv6 on the IPv6 network side, and constitutes two entities when ⁇ is updated with HAv6, and maintains the home address and transfer of HAv6 according to the MIPv6 technology described in RFC3775. Bind to the vine. Specific personalities include:
  • the intestine generates a registration request message, the source address is CoAv4, and the destination address is earned V load including HoAv4#. According to the destination address, the registration request message is sent to the MIPv4/v6-TG.
  • MIPv4/v6-TG converts the received note Mi message into a binding update message.
  • the source address of the binding update message is CoAv6*
  • the destination address is HAAv6
  • the payload includes HoAv6. According to the destination address, the binding message is sent to HAv6. ; '
  • HAv6 updates the binding of the home address and the care-of address and generates a binding confirmation message reply.
  • the address maintained by the new MIP-ALG is bound to Ho4W #r> CoAv4, and a registration reply message is generated.
  • Figure 31 shows a new flow diagram when the HA is in the IPv6 network, the CN is in the IPv4 network, and the MN is moving from the IPv6 network to the IPv4 network.
  • the household f ⁇ at this time more ii Wo M ⁇ have two tasks, one is to 3 ⁇ 4 HAv6 maintained home address and transfer 3 ⁇ 41 address binding; Second, thank you: 3 ⁇ 41 ⁇ 2 query way to find MIPv4 /v6-TG and ⁇ 4 ⁇ 6- TG into the machine configuration.
  • MIPv4/v6-TG acts as HAv4
  • MIPv4/v6-TG acts as M v6.
  • MNv6 touch ⁇ 3 ⁇ 4i way to find MIPv4/v6-TG, fiber HAV6 IPv4 format address HAAv4# 0 in this 3 ⁇ 43 ⁇ 4 query process, MIPv4-TG NAT- PT 3 ⁇ 4&j: address: HAAv6 ⁇ HAAv4# a
  • MIPv4/v6-TG is found in the MNv6 mode, and the CN44 address in the IPv4 format is obtained CNAv4 0
  • MNv4 generates a registration request message
  • the source address is CoAv4
  • the destination address is leg v4#.
  • MNv4 does not know HoAv4#, it only knows HoAv6. Therefore, v sets the home address field in the registration request message to zero and fills in the extended field with HoAv6.
  • the format of the jffi request message after this exhibition is shown in Figure 32A. According to the destination address, the registration request message is sent to the MIPv4/v6-TG.
  • the MIPv4/v6-TG converts the received registration request message into a binding update message.
  • the source address of the binding update message is
  • the destination address is HMv6, and the load includes HoAv6. According to the destination address, the binding is sent to HAv6.
  • HAv6 After receiving the binding update message, HAv6 updates the binding of the home address and the care-of address and generates a binding confirmation message reply.
  • the address is: ⁇ ⁇ r HoAv4#, in the MIP-ALG, the address is also bound: H ⁇ W# 0 Co4W And generate a registration reply message to reply to MNv4.
  • the registration response message includes the format of the HoAv4# 0 this day t registration response message as shown in FIG. 32B.
  • Figure 33 is a flow diagram of the ff when the HA is in the IPv6 network, the CN is in the IPv4 network, and the packet is moved from the IPv4 network to the IPv6 network.
  • MNv6 ship 3 ⁇ 4 ⁇ query way to obtain HAv6 IPv6 format through HAAv6 0
  • Mv6 ⁇ query method finds MIPv4/v6-TG, and obtains the address of CNv4 in IPv6 format CNAv6* renew
  • ⁇ 6 generates a new message, the address is CoAv6, the destination address is HAAv6, and the load includes Yang's home address HoAv6. According to the destination address, the binding plane message is sent to HAv6.
  • ⁇ After receiving the binding message, ⁇ performs the binding of the home address and the transfer that it maintains, and then replies to the MNv6 with the binding confirmation message.
  • the source address of the binding confirmation message is HAAv6, and the destination address is CoAv6, load. Including MNv6's home address HoAv6.
  • MIPv4/v6-TG will act as CNv6.
  • RRP authentication follows the flow described in RFC37755. The specific steps are as follows: MNv6 firstly sends MIPv v6-TG ⁇ H Home Test Init message and Care-of Test Init message, where Home Test Init message needs to pass HAv6, Care- The Test Init message is sent directly to MIPv4 ⁇ -TG; MIPv4/v6-TG receives Home Test After the Init message and the Care-of Test Init message, respectively, the Home Test eliminates the J l Care-of Test message, and the Home Test message and the Care-of Test message are returned in the same way.
  • break 6 After RRP authentication is completed, according to RFC3775, break 6 generates a concurrent update message.
  • the source address of the binding update message is CoAv6, the destination address is CNAv6*, and the load includes HoAv6. According to the destination address, the binding Hff message is sent. Go to MIPv4/v6- TG.
  • the MIPv4/v6-TG After the MIPv4/v6-TG receives the binding ff message, it is hidden in the NAT-PT: ⁇ ⁇ 4 #, in the MIP- & 3 ⁇ 4 ⁇ ⁇ binding of the home address to the care-of address: HoAv6 ⁇ CoAv6 o Then, the MIPv4/v6-TG generates a binding confirmation message and replies with VS6.
  • Figure 34 is a schematic diagram of the layout of the HA being located in the IPv4 network, the CN being located in the IPv6 network, and moving in the IPv4/v6 hybrid network.
  • the HA is located in the IPv4 network
  • the CN is located in the IPv6 network, and moves in the IPv4/v6 hybrid network.
  • ⁇ can be classified into communication with C when moving in the IPv4 network, and communication with the CN when moving in the IPv6 network.
  • 35 is an address configuration diagram of MIPv4/v6-TG when the HA is located in the IPv4 network, the CN is located in the IPv6 network, and the MN is moving in the IPv4 network.
  • MIPv4/v6-TG acts as CNv4 on the IPv4 network side, and HAv4 and Gu4 form the three entities of the MIPv4 technology described in RFC3344, communicating according to MIPv4 described in RFC3344; MIPv4/v6 - TG acts as MNv6 on the IPv6 network side, and CNv6 constitutes two entities of the MIPv6 technology described in RFC3775, according to the MIPv6 technology described in RFC3775.
  • MIPv4/v6-TG In order for MIPv4/v6-TG to act as CNv4 on the IPv4 network side, the NAT-PT in MIPv4/v6-TG must maintain the address mapping of CNAv4 # - CNAv6. In order for MIPv4/v6-TG to act as MNv6 on the IPv6 network side, the MIP-ALG in MIPv4/v6 ⁇ TG must maintain the address binding of H ⁇ 4v6* CoAv6*.
  • Figure 36 is a communication flow chart when the HA is located in the IPv4 network, the CN is located in the IPv6 network, and moves in the IPv4 network.
  • the specific communication steps include:
  • the MNv4 draws a message to the CNv6 male IPv4 format, the source address is HoAv4, and the destination ii1 ⁇ 2 CNAv4# 0 is sent to the MIPv4/v6-TG according to the destination address.
  • the NAT-PT in MIPv4/v6-TG converts the IPv4 format data packet sent by MNv4 into an IPv6 format data packet.
  • the source address of the translated polygon packet is HoAv6* and the destination address is CNAv6.
  • the MIP-ALG in the MIPv4/v6-TG removes the CoAv6* from the address binding ⁇ * CoAv6* maintained by itself, and replaces the source address of the NAT-PT-converted data packet with CoAv6*, and fill the HoAv6* into the face of the message j: the home extension tlB item of the ship extension header.
  • the destination address such a crane message is sent to CNv6.
  • the destination address is CoAv6*, «the second in the message» is stored in the header HoAv6* 0 according to the destination address, such data message is sent to MIPv4/v6-TGo
  • MIP-ALG in MIPv4/v6-TG is the second in the received data message in IPv6 format according to RFC3775! ⁇ Take the home address HoAv6* from the head, replace CoAv6*, as the destination address.
  • the NAT-PT over-converted M-text in MIPv4/v6-TG is converted to the earned text in IPv4 format.
  • the source address is CNAv4# and the destination address is HoAv4. According to the destination address, such a wake-up text is sent to HAv4.
  • HAv4's message (3 ⁇ 4» ⁇ ⁇ ) is forwarded to 4.
  • the source address is ⁇ ⁇ 4 and the destination address is CoAv4.
  • Figure 37 is a flow chart showing the update when the HA is located in the IPv4 network, the CN is in the IPv6 network, and continues to move in the IPv4 network.
  • a new care-of address will be obtained after the move in the IPv4 network, and the MNv needs to update the binding of the home address and the care-of address maintained by the HAv.
  • CNv6 and MIP-ALG both bind the home address of the IPv6 format to the care-of address: ⁇ * ⁇ CoAv6 *, however, CoAv6* consists of the 96-bit IPv6 address prefix of CoAv4 and NAT-PT, During the communication process, the face message is routed to MIPv4/v6-TG according to the 96-bit IPv6 address prefix of NAT-PT in CoAv6*. CoAv4 does not play a role in it. Therefore, it is not necessary to maintain CNv6 and MIP-ALG. The address is tied to 3 ⁇ 4 ⁇ 4 lines 3 ⁇ 4 ⁇ ?. Specific update steps include:
  • Figure 38 is a schematic diagram showing the address configuration of the MIPv4/v6-TG when the HA is located in the IPv4 network, the CN is in the IPv6 network, and the MN is moving in the IPv6 network.
  • Figure 39 is a communication flow chart when the HA is located in the IPv network, the CN is in the IPv6 network, and the picture is moved in the IPv6 network.
  • the specific communication steps include:
  • the MNv6 sends the message to the CNv6 & IPv6 format, the source address of the I ⁇ message is CoAv6, the destination address is CNAv6, and the home address of the destination option extension header of the data packet. Store HoAv6* in the options.
  • CNv6 sends a message to the MNv6 IPv6 format.
  • the source address of the message is CNAv6, the destination address is CoAv6, and the second message of the face message is stored in the header ⁇ .
  • Figure 40 is a diagram showing the update of the HA when the IPv4 network is located, the CN is located in the IPv6 network, and the MN is moving in the IPv6 network.
  • MIPv4/v6-TG acts as HAv6 on the IPv6 network side, updates the home address and care-of address with MNv6 and CNv6 according to RFC3775, and acts as MNv4 on the IPv4 network side, and home address with HAv4 according to RFC3344. Transfer the address of the vine.
  • Reading v6 generates bindings to earn interest. Binding
  • the source address of the new message is CoAv6, the destination address is H v6*, and the payload includes HoAv6*. According to the destination address, the binding new message is sent to MIPv4/v6_TG.
  • the MIP-ALG in the MIPv4/v6-TG converts the received binding update message into a registration request message.
  • the source address of the registration request message is CoAv4#
  • the destination address is hidden v4
  • the payload includes HoAv4.
  • the note office sends a message to HAv4.
  • HAv4 binds the address of the Fujia Township address to the forwarding address according to the received registration request message, and generates a registration response message.
  • the source address of the registration reply message is HAAv4
  • the destination address is CoAv4#
  • the load includes HoAv4.
  • the registration response message is sent to MIPv4/v6-TG.
  • MIP-ALG converts the registration response message into a binding confirmation message.
  • the source address of the binding acknowledgement message is HMv6*
  • the destination address is CoAv6
  • the load includes HoAv6* 0 according to the destination address.
  • the binding confirmation message is sent to MNv6o to receive the binding confirmation message, and the home address and the transfer maintained by the ship are completed. Also the binding of the vine.
  • RRP authentication is required before MNv6 binds to CNv6 Wei.
  • MIPv4/v6-TG will act as HAv6.
  • RRP authentication follows the flow described in RFC37755.
  • MNv6 first At the same time, MIPv4/v6_TG 3 ⁇ 43 ⁇ 4 Home Test Init message and Care-of Test Init message, where the Home Test Init message needs to pass MIPv4/v6- TG and then forwarded to CNv6, Care- of Test Init message directly: ⁇ CNv6; CNv6 After the Home Test Init message and the Care-of Test Init message, the Home Test message and the Care-of Test message are respectively replied, and the Home Test message and the Care-of Test message are returned in the same way.
  • MN v6 After RRP authentication is completed, according to RFC3775, MN v6 generates a concurrent update message.
  • the source address of the binding update message is CoAv6, the destination address is CNAv6, and the load includes HoAv6*. According to the destination address, the binding message is sent. Go to CNv6.
  • CNv6 After receiving the binding update message, CNv6 updates the binding of the home address and the care-of address maintained by CNv6: Then, CNv6 generates a binding confirmation message and returns to ⁇ v6 0
  • Figure 41 shows the update process when the HA is located on the IPv network, C is on the IPv6 network, and the slave is moving from the IPv4 network to the IPv6 network.
  • the V6 male binding update message the source address is CoAv6, the destination address is HMv6*, and the payload includes ⁇ 6*, ⁇ *.
  • the 96-bit IPv6 address prefix of the NAT-PT is added by HoAv4. According to the destination address, the binding update message will be sent to
  • NAT- ⁇ also addresses: CoAv4# CoAv6, then MIP-ALG converts the binding update message into the offline request message, and the polygon address is CoAv4#, destination address It is HMv4, and the load includes HoAv4. According to the destination address, the message is sent to HAv4.
  • HAv4 updates the binding of the home address and the care-of address, and generates a registration response message.
  • the source address is HMv4, the destination address is CoAv4#, and the load includes HoAv4.
  • the registration response message is sent to (6)
  • the MIP-ALG converts the registration response message into a binding confirmation message.
  • the source address of the binding confirmation message is HAAv6*, the destination address is CoAv6, and the load is HoAv6*.
  • the binding confirmation message is sent to break 6. Break 6 receives the binding confirmation message, and finishes the binding of the home address of the J»HAv4 and the binding of the transfer.
  • RRP authentication is required before MNv6 binds to CNv6 Wei.
  • MIPv4/v6-TG will act as HAv6.
  • RRP authentication follows the flow described in RFC37755.
  • MNv6 first sends the Home Test Init message and the Care-of Test Init message to MIPv4/v6_TG, where the Home Test Init message needs to pass MIPv4/v6-TG and then Forwarded to CNv6, Care-of Test Init message is sent directly to CNv6 ; CNv6 responds to Home Test message and Care-of Test message after receiving Home Test Init message and Care-of Test Init message, Home Test message and Care-of Test The message is returned in the same way.
  • MNv6 After RRP authentication, «RFC3775, MNv6 generates and sends a binding new message.
  • the source address of the binding update message is CoAv6, the destination address is CNAv6, and the load includes HoAv6*. According to the destination address, the binding earns interest. Send to CNv6.
  • CNv6 After receiving the binding update message, CNv6 updates its own address binding: HoAv6 ⁇ ⁇ CoAv6. Then, CNv6 generates a binding confirmation message and replies to 6.
  • Figure 42 is a flow chart showing the update when the HA is located in the IPv4 network, the CN is in the IPv6 network, and the MN is moving from the IPv6 network to the IPv4 network.
  • the solution proposed by the present invention extends the read function, so that the picture warehouse requests the MIPv4/v6-TG agent to initiate the update to CNv6 itself.
  • the bow I entered the proxy to save the two messages, and in order to be as compatible as possible with RFC3344, the format of the proxy request/delivery message and the format of the registration request/registration response message.
  • class values are defined for the proxy request message and the substitute message.
  • M v4 generates and registers a request message with HAv4 fiber
  • the hard address is CoAv4
  • the destination ship is HAAv4
  • the load includes HoAv4. According to the destination address, the registration request message is sent to HAv4.
  • MNv4 requests a message to the MIPvVv6-TG proxy.
  • the source address of the proxy request message is CoAv4, the destination address is CNAv4#, and the load includes HoAv4. According to the destination address, the proxy request message is sent to MIPv4/v6 - TG 0.
  • the value of the proxy request message defined in the present invention is 7, and the format of the proxy request message is as shown in Fig. 43A.
  • MIPv4/v6_TG After receiving the proxy request message, MIPv4/v6_TG will proceed to CNv6.
  • RRP certification is required before CNv6; ⁇ 3 ⁇ 43 ⁇ 4 new.
  • RRP authentication follows the flow described in RFC37755. The specific steps are as follows: MIPv4/v6-TG acts as HAv6 on the IPv6 network side and sends a message to CNv6 ⁇ i Home Test Init.
  • the Home Test Init message source address is HoAv6* and the destination address is CNAv6.
  • CNv6 receives the Home Test Init message and responds to the Home Test message to MIPv4/v6-TG.
  • MIPv4/v6-TG acts as MNv6 and sends a Care of Test Init message to CNv6.
  • the Care of Test Init message source address is CoAv6* and the destination address is CNAv6.
  • CNv6 receives the Care of Test Init message and will respond to the Care of Test message to MIPv4/v6-TG.
  • MIPv4/v6_TG acts as MNv6 and generates a binding update message according to RFC3775.
  • the source address of the binding update message is CoAv6*
  • the destination address is CNAv6
  • the load includes HoAv6*. According to the destination address, the binding Earn a sigh
  • CNv6 After receiving the binding vine message, CNv6 binds the address maintained by the new one: HoAv6* ⁇ CoAv6 *. CNv6 then generates a Binding Acknowledgement message and replies to MIPv4/v6-TG.
  • the MIP-ALG 3 ⁇ 43 ⁇ 4i is also bound to: HoAv6* CoAv6*.
  • the MIPv4/v6-TG sends a message to the MNv4.
  • the source address of the 3 ⁇ 4S answer message is CNAv4#
  • the destination address is CoAv4
  • the payload includes HoAv4.
  • the «value of the generation of the answer message is 8, and the format of the message is as shown in Fig. 43B.
  • the invention realizes mobile communication in the IPv4/v6 hybrid network by setting MIPv4 ⁇ -TG between the IPv4 network and the IPv6 network, and realizes mutual transparency of RFC3334 and RFC3775, which satisfies the period of the network from IPv4 to IPv6.
  • Demand; and the invention only needs X anger node to carry out certain upgrades, but does not need to be 3 ⁇ 4 ⁇ 4 for the home agent and thank you point, because the ⁇ 3 ⁇ 4 ⁇ invention» makes full use of the existing mobile communication equipment, and has great practical value.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

—种实现移动节点在 IPv4/v6混合网络中的通 法
本发明所属 领域
本发明涉及网络和移动通信领域， 具 及一种移动节点在 IPv4/v6混合网络中的通信 法。 在本发明之前的现有狱
目前，移动通信 E联网承载的最为 的应用。移动 IP研¾ 1联网承輔动通信的问题，具 体地， 移动 IPv4研究 IPv4网络承载移动通信的问题， 移动 IPv6研究 IPv6网络承鍾动通信的问 题， 移动 IPv4/v6就是研究 IPv4/v6网络承载移动通信的问题。
图 1是 RFC3344所描述的移动 IPv 技术的基本原理的示意图， 其 步骤如下：
(1)移动节点从本地网络移动到外地网络；
(2)外地代理 代理广告消息 (Agent Advertisement Message)表明它们的存在；
(3)移动节点也可以选择性 iiM:代理请求消息（Agent Solicitation Message)请求所在链 路的移动代理向其 代 ar告消息；
(4)移动节点接收移动代 ar告消息， 并根据此消息判断自己是处于家乡网络还 ^卜地网络； (5)如果移动节点发现自己移动到外地网络，贝 地网络获得一个转 也址。转 也¾1：可以 由外地代理指派， 也可以舰 DHCP等方式获取；
(6)移动节点向家乡代理发送注册请求消息以注册其转交地址。注册请求消息的格式如图 2A 所示， 其中包含移动节点的家乡地址、家乡代理地址、转魏址、 m rn, 而扩展部他含 移动节点和家乡代理之间的认 «¾， 当注編求消息需要经賺也代理时， 扩展部分也会包含移 动节点与外地代理之间的认 iiE«; 注册请求消 min注册应答消息"^要^^卜地代理；
(7)家乡代3«±述注册请求消息，创建禱膽定缓存，并向移动节点難注册应答消 息以把注册的结果通知移动节点。注册应答消息的格式如图 2B所示，其中包含移动节点的家乡地址、 家乡代理地址、耐縛聽， m, 在扩展部^ ¾包括一些认
(8)逝 点向移动节点发送翻报文时，源地址为通^ U点的地址， 目的地址为移动节点的 家乡地址。 报文经 乡网络的时候， ¾ ^乡代理截获后 到移动节点的转交地 址； (9)移动节点向通信节点 ^¾«报文时，源地址为移动节点的家乡地址， 目的地址为 ®it1? 点的地址， 因此 «报文无需经 乡网络。
图 3是 RFC3775所描述的移动 IPv6技术的¾*原理的 图， 其关键步骤如下：
(1)移动节点从本地网络移动到外地网络；
(2)移动节点移动到外地网络后， 将舰有状态^ ¾状态的方式获得一个转娜止；
(3)移动节点 向家乡代 定更新消息的方式向家乡代理注册 ¾$t¾t也址，绑定¾新 消息的格式如图 4A所示；
(4)家乡代 »3±¾^5定 新消息，创建^ §?其绑定缓存，并向移动节点; 定确认消 息以把注册的结¾1知移动节点， 绑定确认消息的格式如图 4B所示；
(5)移动节点 Return Routability Procedure (RRP)过程， RRP过程包括 4条消息， 即 移动节点向通信节点发送的 Home Test Init和 Care-of Test Init消息， 以及它们各自的应答消息 Home Test和 Care- of Test消息， 其中， Horae Test Init消息和 Home Test消息要经 乡代理转 发。 RRP过程的目的是为了保证移动节点的家乡地址以及 ¾t也址是可以到达的。图 5是 RFC3775 所描述的移动 IPv6技术中 RRP的流程图。
(6) RRP过程结束后， 移动节点向谢 tl?点发 定 新消息；
(7)通^ 1?点创建 新其绑定缓存， 并向移动节点 定确认消息；
(8)移动节点与其谢婦删諸两种方式：
第一种是 "双向瞧"方式。通信节点发出的賺艮文被路由到家乡网络， 家乡代理截 匕数 据报文并 隧 31¾此«报文; ^到移动节点的转 ¾i也址； 而移动节点发出的 «报文 反向 隱纖到家乡网络， 然后再 乡网络纖到通信节点。采用这种方式时， 通 点无需知道移 动节点当前的位置信息。
第二种是 "路由优化"方式。这种谢訪式允许通信节点 «¾-报¾¾接雄到移动节点的转 交地址， mrn ^, 移动节点必须向通信节点注册以使通 点知道其家乡地址与转¾¾址的 绑定
移动 IPv4/v6的解决方案取决于 IPv4网络与 IPv6网络混合的方式。目前， IETF推荐三种方式: 醒 (RFC3053),双栈 (RFC2893)和 NAT- PT (RFC2766)0本发明提出的移动 IPv4/v6解决方案基 于 NAT—PT。 ΝΑΤ-ΡΓ是一个网络层的设备，可以 IPv4与 IPv6的互相透明。特别地， NAT- —种机 制， 通在其上增设細层网关的方式條 IPv4网络和 IPv6网络承载的同样麵的互相透明。 目 前， ftp- ALG和 DNS- ALG已经成为 NAT-PT的标准配置。
图 6是用 ΑΤ-ΡΓ网关加上 DNS-ALG实现 IPv4/v6混合网络的 DNS查询的工作原理 图。如图 6所示， 是用 NAT-PT网关加上 DNS- ALG实现 IPv4/v6混合网络的 DNS Si旬的关键步骤， 具 #¾口下： (1) IPv6主机要与 IPv4主机 Μϊΰί接，但是不知道该 IPv4主机的 IPv6地址是什么。于是发 出 DNS请求消息问 IPv4, com的 IPv6地址， DNS请求消息传给 IPv6网络中的 DNS服务器 A, 但在 IPv6网络中的 DNS服务器 A中找不到 IPv 主机的记录 (IPv6的记录是 A6或是 AAAA, 而 IPv4的记 录是 A) ;
(2)于是 IPv6 DNS将此请求消息转发出去， 被 DNS- ALG拦截；
(3) DNS-ALG将请求消息中的 A6或 MM改为 A， 转发到 IPv4网络；
(4) IPv4网络中的 DNS服务器 B接收到此请求消息，回复 IPv4主机的地址为 202. 116. 78. 11;
(5) DNS-ALG接收到此地址信息后， 在 IPv4地址上加上 96位前缀， 变成 IPv6地址 prefix: :202. 116. 78. 11；
(6) DNS-ALG将 A改为 A6或 MM之后继续把 DNS应答消肩送回给 IPv6网络中的 DNS服务器
A, ^合 IPv6主机；
(7) IPv6主机认为 IPv4, com的地址为 prefix: :202. 116. 78. 11, 所以发出源地址为 3FFE: 3600.-B: :2, 目的地址为 prefix: :202. 116. 78. 11的 IPv6分组；
(8)当分组经过转换网关时， 其首先查 地址 1«表中是否有源地址为 3FFE:3600:B: :2的 表项，如果有则直樹姻之，如果没有，从 IPv4地址池中分配一个 IPv4地址给此 IPv6主机，分配
IPv4地址的同时在地址赚表中添加一 ^¾¾3FFE:3600:B: :2—203. 69. 0. 1，同时 NAT- PT网 掉 目的地址的 96位前缀得到一个 IPv4地址， 也即 IPv4主机的 IPv4地址；
(9)转换网关根据粒的地址嘛关系， 进機址和语义转换， 组头转换成 IPv4的分组头， 分组头中的源地址为 "203. 69. 0. 1" ，目的地址为 "202. 116. 78. 11"， 然后向 IPv4网络发出分组。
反之， IPv4主机查询 IPv6主机的 IPv4地址的道理是一样的， 其通信藤基本上是一致的。 目前， IETF已麵布了移动 IPv4的解决方案 (RFC3344)和移动 IPv6的解决方案 (RFC3775), 为移动 IP在纯 IPv4网络和纯 IPv6网络的应用 了较为完整的方案。然而， ±¾E两个 RFC均未涉 及 IPv4/v6混合网络的情况， 随着 IPv4网络向 IPv6网络的 度， 对 IPv4/v6混合网络的移动通信 问题的研究显得十分必要， IPv4/v6混合网络的移动通信问题可以从静态角度和动态角戲！]分为如 下 16 问题：
A1.首先从静态的角度看， 根据家乡代理和通信节点在 IPv4/v6混合网络中的位置， 把移动 IPv4/v6的问题分为四个基本问題， 步骤 A1具体包括：
All.家乡代理和通信节点都位于 IPv6网络， 移动节点在 IPv4/v6混合网络中移动时的移动 IPv4八 6的问题；
A12.家乡代理和通信节点都位于 IPv4网络， 移动节点在 IPv4/v6混合网络中移动时的移动 IPv4/v6的问题；
A13.家乡代理位于 IPv6网络， 通信节点位于 IPv4网络， 移动节点在 IPv4/v6混合网络中移动 时的移动 IPv4/v6的问题；
A14.家乡代理位于 IPv4网络， 通信位于 IPv6网络， 移动节点在 IPv4/v6混合网络中移动时的 移动 IPv4/v6的问题。
A2.其次从动态的角度看， 根据移动节点在 IPv4/v6混合网络中的移动情况， X»述步骤 A1 中戶¾的^^基本问^ ¾一步分成四 问题， 其步骤 Α2具体包括：
A21.移动节点在 IPv4网络中移动时的移动 ΙΡν4/ν6的问题；
A22.移动节点在 IPv6网络中移动时的移动 IPv4/v6的问题；
A23.移动节点从 IPv 网络移动到 IPv6网络时的移动 IPv4/v6的问题；
A24.移动节点从 IPv6网络移动到 IPv4网络时的移动 IPv4/v6的问题。
另外， 为了方便于表达本发明的核心思想， 本发明定义了一些术语的表示方式， 图 7是本发明 中使用到的一些术语的缩略语及其解释。其中图的左边一列是原术语， 图的右边一列是术语的缩略 语，本发明采用术语缩略 ¾*¾行发明内容的陈述。同时本发明舰在上 语后加上" v4"或 "v6" *¾示 version 4或 version 6。例如 MIPv4 Mobile IPv4, CNv6表示处于 IPv6网络的 CN， HoAv6 的 IPv6格式的家乡地址。
另外， ΝΑΤ-ΡΓ网 对不同的地址进行不同的雖。如果 AT-PT在一个 IPv 地 tltjg面加 号，贝 IJ表 ¾¾¾个地址是 NAT—PT中 IPv4地址池里的地址，与一个 IPv6地»成 关系。例如， CNAv4# 是 ΝΑΤ-ΡΓ中 IPv4地址池里的一 ：也址， 与 CNAv6形成映射关系， 是 CNv6在 IPv4网络里的地址标 识。 以 CNAv4#为目的地址的 IPv4格式的数据报文将路由到 ΝΑΤ-ΡΓ。如果 ΝΑΤ-ΡΤ在一个 IPv6地址 后面加 "*"号， 贝 1』¾¾¾¾个地址由一个 IPv4地址和 ΝΑΤ—ΡΤ的 96位地址前缀賊。例如， CoAv6* 是由 CoAv4和 NAT-PT的 96位地址前缀组成， 是 MNv4在 IPv6网络的地址标识。 以 CoAv6*为目的地 址的 IPv6格式的 « -报文辦皮路由到 ΝΑΤ-ΡΓ。 发明目的
本发明的目的是克服现有技术的不足， iii共一种实现移动节点在 IPv4/v6混合网络中的通^ 法， 该方法有效的解决了移动节点在 IPv4/v6混合网络中的移动通信中所雜的问题， 同时本发明 要 见有的移动通信设备无需敝大的升级， 具有很大的实用价值。
本发明采用的餘方案
为了达到 技术目的， 本发明的技术解决方案： 一种实现移动节点在 IPv4/v6混合网络中的 通信方法， 通过在 IPv4网络和 IPv6网络之间设置移动 IPv4/v6转换网关实现 IPv4/v6混合网络中 的移动通信， 戶 M移动 Π Λ6转换网 括 NAT- PT网^ ¾设在其上的移动 IP麵层网关， 其中 NAT-PT网^ ±15¾有 DNS-ALG。
戶 M移动节点在 IPv4/v6混合网络中的通^法的步骤是：
步骤 A为：移动 IPv4/v6转换网关通过在 IPv4网络和 IPv6网络中分别充当 RFC3344和 RFC3775 所描述的不同的实体， 以及通过在网关内部进行实体之间的转换实现 RFC3344和 RFC3775的互相透 明。具体来说， 该步骤 A具体包括：
A1.移动 IPv4八 6转换网关在 IPv4网络一侧充当一个 RFC3344所描述的实体，这个实体与处于 IPv 网络中的其它实 #勾成一个 RFC3344所描述的移动 IP模型，这个移动 IP模型按照 RFC3344所 描述的移动 IPv4协腦现信和 新；
A2.移动 IPv4/v6转换网关在 IPv6网络 充当一个 RFC3775所描述的实体,该实体与处于 IPv6 网络中的其它实彌成一个 RFC3775所描述的移动 IP模型， 这个移动 IP模型按照 RFC3775所描述 的移动 IPv6协 測言和 ff ;
A3.移动 IPv4/v6转换网关 实体之间的内部转换实现自己从一个 IPv4形式的实体向一个 IPv6形式的实体的转换， 从一个 IPv6形式的实体向 IPv4形式的实体的转换， 以及实现同类实 体之间的转换， 从而最终实现 RFC3344和 RFC3775的互相透明。
步骤 B为： 移动 IPv4/v6转换网关负责对从 IPv4网络; ^到 IPv6网络的、与移动 IP有关的 各种消息和麵报文进行转换，负责对从 IPv6网络发送到 IPv 网络的、与移动 IP有关的各种消息 和麵报文进行转换。 具体来说， 该步骤 B包括：
B1.移动 IPv4/v6转换网关负责把 RFC3344所描述的注廳求消息转换成 RFC3775所描述的绑 定 新消息， 把 RFC3344所描述的注册应答消息转换成 RFC3775所描述的绑定确认消息；
B2.移动 IPv4/v6转换网关负责把 RFC3775所描述的绑定 新消息转换成 RFC3344所描述的注 ti青求消息， 把 RFC3775所描述的绑定确认消息转换成 RFC3344所描述的注册应答消息；
B3.移动 IPv4/v6转换网关负责对数据报雄衍也址协议转换， 并且在 IPv6网络
报文时， 按照 RFC3775所描述的要求， 把 IPv6格式的数据报文 IP头中的转交地址与扩展头中的家 乡地删亍交换。
步骤 C是： 移动 IPv4/v6转换网关按照下面的原则截获与移动 IP有关的消息和麵报文： 在 更新时，按照消息的 ¾截获消息；在通信时，按照«报文的目的地址截 ¾ ^报文；具体来说， 该步骤 C包括：
C1.在通信时， 移动 IPv4/v6转换网关根据不同的通信情况充当不同的实体， 由于以这些实体 的 IP地址作为目的地址的隨报文会¾£各由到移动 IPv4/v6转换网关，因此，移动 IPv4/v6转换网 关将截获以鹏实体的 IP地址为目的地址的麵报文；
C2.在更新时， 移动 IPv4/v6转换网关按照消息的 ¾ 截获消息， 法进一步具体包括：
C21.在 IPv4网络， 移动 ΙΡν4/ν6转换网关需要处理的消息有 RFC3344所描述的注廳求消息 和注册应答消息以及本发明中新定义的代理请求消息和代 ® ^答消息， Χί¾四种消息，移动 IPv4/v6 转换网关在网络层根据消息的 UDP封装和目的端口号截获， 在应用层根据消息的负载类型值区分； C22.在 IPv6网络， 移动 IPv4八 6转换网关需要 的消息有 RFC3775所描述的绑定 新消息、 绑定确认消息、 Home Test Init消息、 Home Test消息、 Care of Test Init消息、 Care of Test 消息; 枢些消息，移动 IPv4/v6转换网关在网络层根据消息的移动扩展头的下一个报头编号为 135 作为标志截获消息， 在应用层根据负载中 MH值区分消息。
步骤 D是： 移动 IPv4/v6转换网关在处理 IPv4格式的消息和贿报文时釆用 RFC3344通的 安全机制， 在处理 IPv6格式的消息和画报文时采用 RFC3775搬的姓机制； 该步骤 D具体是：
D1.当移动 IPv4/v6转换网纖收一个消息¾«报文时， 将根据这个消息 报文是 IPv4 格式还是 IPv6格式， 按照 RFC3344或 RFC3775所描述的认证算法进 fiH人证； D2.当移动 IPv4/v6转换网关; ^—个消息 报文时， 将根据这个消息 报文是 IPv4 格式还是 IPv6格式，按照 RFC3344或 RFC3775所描述的认证算法产生认 β¾这^ 1人» ^徘 为这个消息 ¾¾报文的一部分。
步骤 Ε是： 本发明提出的实现移动节点在 ΙΡν4/ν6混合网络中的通 ft ^法中对家乡代理和通信 节点的要求与 RFC3344和 RFC3775所描述的要求保 ~致， 但增加^动节点的要求。该步骤 E具 体是 ·· 步骤 E具体包括 ··
E1.移动节点倉 同日满足 RFC3344和 RFC3775所描述的有关移动节点的要求；
E2.移动节点霞己录家乡代理和通 点的 ¾½， 逝 DNS Si旬的方式发现移动 IPv4/v6 转换网关， 并获得家乡代理和通詳点的地址；
E3.移动节点能够支持 注册请求消息和注册应答消息的扩展， 畲 产生和处理代理请求消息 和代雜答消息。
步骤 F是： 当家乡代理位于 IPv4网络，通 点位于 IPv6网络，移动节点在 IPv4/v6混合网 络中移动时的移动 IPv4/v6的关键步骤包括：
F1.当移动节点从 IPv6网络移动到 IPv4网络时， 移动节点向移动 IPv4/v6转换网关維代理 请求消息，请求移动 IPv4/v6转换网 弋理移动节点向处于 IPv6网络中的通 ^点发起其家乡地址 与转娜止的绑定更新；
F2.移动 IPv4/v6转换网关收到代理请求消息后， ί弋理移动节点向处于 IPv6网络中的通^ Ϊ 点^ «：程， 此时移动 ΙΡν4/ν6转换网关在 IPv6网络 ~{则将分别充当 IPv6格式的家乡代理和 IPv6格式的移动节点， 移动 IPv4八 6转换网关收到绑定确认消息后， 向处于 IPv4网络中的移动节 点发出代 答消息；
F3.删弋理请求消息的格式与 RFC3344中的注廳求消息的格式相同， 代鹏答消息的格式 与 RFC3344中的注册应答消息的格式相同， 其中代理请求的握值被暂定为 7， 代雜答消息的类 型值被暂定为 8。
与现有技^目比， 本发明的优点是：
能够充分利用现有的 MIPv4 (RFC3344)和 MIPv6 (RFC3775)技术， 实现移动节点在 IPv4/v6混 合网络中的移动通信， 而且实现了斷 4技 口 MIPv6技术的兼容， 实现了移动通信与网络从 IPv4 向 IPv6 度的同步性，同时本发明要 见有的移动通信设备无需 ife 大的升级，具有很大的实用价 值。
附图说明
图 1是 RFC3344所描述的移动 IPv4技术的基本原理的 ¾ ^图；
图 2A是注册请求消息的格式 ^图；
图 2B是注册应答消息的格式 图；
图 3是 RFC3775所描述的移动 IPv6技术的 ¾Φ原理的 ¾ ^图；
图 4Α是绑定 消息的格式示意图；
图 4Β是绑定确认消息的格式示意图；
图 5是 RFC3775所描述的移动 IPv6 中 RRP的流程图；
图 6是用 ΝΑΤ-ΡΤ网关加上 DNS-ALG实现 ΙΡν4/ν6网络的 DNS ¾1旬的工作原理示意图； 图 7是本发明中 到的一些术语的缩略语及其解释；
图 8是在本发明中 MIPv4/v6_TG针对一个具体的通信情况充当不同实体的示意图；
图 9是 HA和 CN者啦于 IPv6网络、應在 IPv4八 6混合网络中移动的布局示意图；
图 10是 HA和 CN都位于 IPv6网络、顯在 IPv6网络中移动时移动 IPv4/v6解决方案的示意图; - 图 11是 HA和 CN都位于 IPv6网络，醫在 IPv4网络中移动时 MIPv4/v6- TG的地址配置示意图; 图 12是 HA和 CN都位于 IPv6网络、腹在 IPv4网络中移动时的通信流程图；
图 13是 HA和 CN都位于 IPv6网络、 M 在 IPv4网络中移动时的更 流程图；
图 14是 ΗΑ和 CN都位于 IPv6网络、 Μ 从 IPv6网络移动到 IPv 网络时的更新流程图； 图 15A是 ΗΑ和 CN都位于 IPv6网络、 Μ 从 IPv6网络移动到 IPv4网络时注册请求消息的格式 扩 意图；
图 15B是 ΗΑ和 CN都位于 IPv6网络、讀从 IPv6网络移动到 IPv4网络时的注册应答消息的格 式 图；
图 16是 ΗΑ和 CN都位于 IPv6网络、剛从 IPv4网络移动到 IPv6网络时移动 ΙΡν4/ν6解决方案 的示意图；
图 17是 HA和 CN都位于 IPv4网络， 顺在 IPv4/v6混合网络中移动的布局示意图；
图 18是 HA和 CN都位于 IPv4网络、丽在 IPv4网络中移动时移动 IPv4/v6解决方案的示意图； 图 19是 HA和 CN都位于 IPv4网络、 MN在 IPv6网络中移动时 MIPv v6-TG的地址配置示意图； 图 20是 HA和 CN都位于 IPv4网络、 MN在 IPv6网络中移动时的通信流程图； 图 21是 HA和 CN者立于 IPv 网络、 MN在 IPv6网络中移动时的更新流程图；
图 22是 HA和 CN都位于 IPv4网络、 MN从 IPv4网络移动到 IPv6网络时的更新流程图； 图 23是 HA和 CN都位于 IPv4网络、續从 IPv6网络移动到 IPv4网络时移动 IPv4/v6解决方案 的示意图；
图 24是 HA位于 IPv6网络、 CN位于 IPv 网络、 MN在 IPv4八 6混合网络中移动的布局 图； 图 25是 HA位于 IPv6网络、 CN位于 IPv4网络、顺在 IPv6网络中移动时 MIPv4/v6- TG的地址 配置示意图；
图 26是 HA位于 IPv6网络、 CN位于 IPv4网络、 MN在 IPv6网络中移动时的通信流程图； 图 27是 HA位于 IPv6网络、 CN位于 IPv4网络、 MN在 IPv6网络中移动时的更新流程图； 图 28是 HA位于 IPv6网络、 CN位于 IPv4网络、 MN在 IPv4网络中移动时 MIPv4/v6- TG的地址 配置 ¾¾图；
图 29是 HA位于 IPv6网络、 CN位于 IPv 网络、腿在 IPv4网络中移动时的通信流程图； 图 30是 HA位于 IPv6网络、 CN位于 IPv4网络、 MN在 IPv4网络中移动时的 流程图； 图 31是 HA位于 IPv6网络、 CN位于 IPv 网络、應从 IPv6网络移动到 IPv4网络时的更新流程 图；
图 32A是 HA位于 IPv6网络、 CN位于 IPv4网络、丽从 IPv6网络移动到 IPv4网络时的注册请 求消息的格式扩展示意图；
图 32B是 HA位于 IPv6网络、 CN位于 IPv 网络、 MN从 IPv6网络移动到 IPv 网络时的注册应 答消息的格式 图；
图 33是 HA位于 IPv6网络、 CN位于 IPv4网络、丽从 IPv4网络移动到 IPv6网络时的更新流程 图；
图 34是 HA位于 IPv4网络、 CN位于 IPv6网络、顺在 ΙΡν4Λ6混合网络中移动的布局示意图； 图 35是 ΗΑ位于 IPv4网络、 CN位于 IPv6网络、續在 IPv4网络中移动时 MIPv4/v6- TG的地址 配置示意图；
图 36是 HA位于 IPv4网络、 CN位于 IPv6网络、 MN在 IPv4网络中移动时的通信薩图； 图 37是 HA位于 IPv4网络、 CN位于 IPv6网络、顯在 IPv4网络中移动时的; gf?流程图； 图 38是 HA位于 IPv4网络、 CN位于 IPv6网络、續在 IPv6网络中移动时 MIPv4/v6-TG的地址
ISg¾¾图； .
图 39是 HA位于 IPv4网络、 CN位于 IPv6网络、 MN在 IPv6网络中移动时的通信流程图； 图 40是 HA位于 IPv4网络、 CN位于 IPv6网络、應在 IPv6网络中移动时的 新流程图； 图 41是 HA位于 IPv4网络、 CN位于 IPv6网络、 MN从 IPv4网络移动到 IPv6网络时的更新流程 图；
图 42是 HA位于 IPv4网络、 CN位于 IPv6网络、丽从 IPv6网络移动到 IPv4网络时的更新流程 图；
图 43A是 HA位于 IPv4网络、 CN位于 IPv6网络、 MN从 IPv6网络移动到 IPv4网络时的代理请 求消息的格式^^图；
图 43B是 HA位于 IPv4网络、 CN位于 IPv6网络、續从 IPv6网络移动到 IPv4网络时的代理应 答消息的格式 图。
具^ »J
本发明涉及一种实现移动节点在 IPv4/v6混合网络中的通信方法， 信方法是为了解决移动 IPV4/V6 的十六 问题。
以下参照各附图及具体实施例进ϊ 细的说明。
如图 8所示， 家乡代理位于 IPv4网络（记为 ΗΑν4)、通信节点位于 IPv6网络（记为 CNv6)、移 动节点在 IPv4网络内部移动（记为 MNv4)、 IPv4网络与 IPv6网络之间设置 MIPv4/v6- TG。在这种 情况中， MIPv4/v6- TG在 IPv4网络一侧充当通信节点 (记为 QW4), 与 HAv4和 MNv4按照 RFC33 4 所描述的 MIPv4 进行通信。 MIPv4/v6-TG在 IPv6网络一侧充当移动节点（记为 MNv6), 与 CNv6 按照 RFC3775所描述的 ΜΙΡνθ技术迸 fi¾信。 MIPv4/v6-TG在内部进行 CNv4与 M v6之间的转换。
如图 9所示 HA和 CN都位于 IPv6网络，讓在 IPv4八 6混合网络中移动， 整 t¾ g可以分为 MN 在 IPv6网络中移动时与 CN的通信， MN在 IPv4网络中移动时与 CN的通信， MN从 IPv6网络移动到 IPv 网络时与 CN的通信，讓从 IPv4网络移动到 IPv6网络时与 CN的通信。下面将分别对这几种情 况下的通信进 细的说明。
图 10是 HA和 CN都位于 IPv6网络，丽在 IPv6网络中移动时移动 IPv4/v6的解决方案示意图。 当丽在 IPv6网络内移动时，顺、 HA和 CN¾¾IPv6网络内，这是典型的 MIPV6的问题，維照 RFC3775 所描述的 ΜΙΡνβ技术进 ^¾信和 新， 具体的实施过 图 3。
图 11是 HA和 CN都位于 IPv6网络，丽在 IPv4网络中移动时 MIPv4/v6-TG的地址配置示意图。 当 M 在 IPv4网络移动时， MIPv4/v6- TG在 IPv6网络一侧充当 MNv6， 与 CNv6构成 RFC3775所描述 的 MIPv6 的两个实体， 按照 RFC3775所描述的 ΜΙΡνθ技术进行通信， 为了使得 MIPv4/v6-TG在 IPv6网络一侧向 CNv6发送数据报文时能够进行家乡地址和转交地址的更换， MIPv4/v6-TG中的 MIP-ALG必须维持 IPv6格式的家乡地址与转 ¾i也址的绑定： HoAv6 <r CoAv6 *。
在 IPv4网络一侧， MIPv4/v6-TG在发送固报文时充当 HAv4, 在接收 报文时充当 CNv4， 与 M v4构成 RFC3344所描述的 MIPv4技术的三个实体，按照 RFC3344所描述的 MIPv4技术进 信。 为了充当 HAv4， MIPv4/v6-TG中的 NAT- PT必须维持 H 4v< ϋ^4τ^#和 ^4^ HoAv4# 个地址嘛、 MIP-ALG必须维持 IPv4格式的家乡地址与转交地址的绑定： HoAv4 # <^ CoAv4。 为 了在接收数据报文时充当 CNv4，MIPv4/v6- TG中的 NAT- PT必须维持 C W# CNAv6的地址映射。
图 12是 HA和 CN都位于 IPv6网络， 續在 IPv4网络中移动时的通信流程图。具体的通信步骤 包括：
(1)根据 RFC3344所描述的 MIPv4技术， MNv4向 CNv6維 IPv4格式的薩报文， 地址 是 HoAv f， 目的地址是 CNAv4#。根据目的地址， 这样的 报文发往 MIPv4/v6-TG。
(2) MIP-ALG中的 NAT- FT 报 ¾¾¾¾址协议转换，转换后的»报文的源地址为 ΗοΑνβ, 目的地址为 CNAv6。根据 RFC3775所描述的 MIPv6技术， MIPv4/v6-TG中 MIP- ALG从自己维持的地址 ΗοΑν6 CoAv6 *中取出 CoAv6*，把经过 NAT- PT转换后的 报文的目的地 HoAv6替换 为 CoAv6*， ΗοΑν6填入麵报文的家乡地: t趙项中。根据目的地址，这样的麵报文发往 CNv6。
(3)根据 RFC3775所描述的 MIPv6技术， CNv6向 M v4維 IPv6格式的数据报文， 其源地址 是 CNAv6， 目的地址为 CoAv6*， 并在讓报文中插入一个第二猶由头， 里面包括 HoAv6。根据目 的地址， 这样的聽报文发往 MIPv4/v6-TG。
(4)根据 RFC3775所描述的 MIPv6技术， MIPv v6- TG中的 MIP- ALG从接收到的数据报文的第 二类路由头中取出 HoAv6， 把目的地址从 CoAv6*更换为 HoAv6。 MIPv4/v6-TG中的 NAT-PT X寸经过 MIP-ALG处理的数据报文进行地址协议转换， 转换后的数据报文源地址是 CNAv4#， 目的地址是 HoAv4#o这样的翻报文囊 lit发往應 v4, 隱的源地址是 H v4#， 目的地址是 CoAv4。
图 13是 HA和 CN都位于 IPv6网络、 MN在 IPv4网络中移动时的更新流程图， 当 MN在 IPv4网 络内移动并获得一^ ff的转^ ¾址时，壓需要; 程。在 «¾1中， MIPv4/v6-TG在 IPv4 网络 ~«充当 HAv4， 与 MNv4按照 RFC334 所描述的 MIPv4 ¾^进行家乡地址与转交地址的绑定更 新， 也就是適 MIP-ALG中所维持的家乡地址与转交地址的绑定。然后， MIPv4/v6_TG在 IPv6网络 一侧充当 MNv6， 与 HAv6和 CNv6按照 RFC37755所描述的 MIPv6 ¾ ^进行家乡地址与转交地址的绑 定 新。具体的更新步骤包括：
(1)根据 RFC3344所描述的 MIPV4技术， 斷4产生注廳求消息。注册请求消息的源地址是 CoAv4, 目的地址是廳 ， 负载包括 HoAv 。根据目的地址， 该注册请求消息发往 MIPv4/v6-TG。
(2) MIPv4/v6-TG把接收到的注册请求消息转换为绑定更新消息。 绑定更新消息的源地址是 CoAv6*， 目的地址是 HAAv6， 负载包括 HoAv6。根据目的地址， 该绑定 新消息发往 HAv6。
(3) HAv6收到绑定更新消息后首先更新自己维持的家乡地址与转交地址的绑定， 然后向
MIPv4/v6-TG回复绑定确认消息。
(4)根据 RFC3775, 在 MNv6向 CNv6 绑定 新之前， 要进行 RRP认证。此时 MIPv4/v6-TG 将充当 MNv6向 CNv6 RRP认证， RRP认证按照 RFC37755所描述的流程进行， RRP具体步骤如下： MIPv4/v6-TG首先同时向 CNv6发送 Home Test Init消息和 Care- of Test Init消息，其中 Home Test Init消息需要经过 HAv6， Care-of Test Init消息直接 ^^合 CNv6; CNv6收到 Home Test Init消 息和 Care- of Test Init消息后分别回复 Home Test消息和 Care- of Test消息， Home Test消息和 Care- of Test消息按照原路返回。
(5) RRP认证结束后， MIPv4/v6-TG向 CNv6 ¾¾|?定¾新消息。
(6) CNv6收到绑定更新消息后首先更新自己维持的家乡地址与转交地址的绑定， 然后向 MIPv4/v6-TG回复绑定确认消息。
(7) MIPv4/v6- TG收到绑定确认消息后， ¾MIP- ALG维持的家乡地址与转交地址的绑定。然 后， 根据 RFC3344所描述的 MIPv4技术， MIPv4/v6- TG产生注册应答消息。注册应答消息的源地址 是 HAAv4#， 目的地址是 CoAv4， 负载包括 HoAv4#。根据目的地址， 该注册应答消息发往斷 4。
图 14是 HA和 CN都位于 IPv6网络、 MN从 IPv6网络移动到 IPv4网络时的更新流程图。
如图 14所示，此时 §¾禾^要有两个任务，首先要实现 HAv6和 CNv6所维持的家乡地址与转 交地址的绑定 ；其 旬的方式发现 MIPv4/v6- TG并对 MIPv4/v6- TG进 fi¾也址 @2¾。 在这个更 程中， 在 IPv4网络一侧， MIPv4/v6-TG充当 HAv4， 在 IPv6网络一侧， MIPv4/v6-TG 充当 MNv6。具体的¾»骤包括：
(1) MNv4 域名 旬的方式发现 MIPv4/v6-TG, 并获得 HAv6的 IPv4格式的地址 HAAv4#。 在 itbl程中， MIPv4/v6- TG中的 NAT- PT 了地址 ： ΗΑΑνό HAAv4 #。
(2) M v4 iffil域名 ¾i旬的方式发现 MIPv4/v6-TG, 寻 CNv6的 IPv4格式的地址 CNAv4#。 在此过 ®中， MIPv4/v6- TG中的 NAT- PT建立了地址映射： CNAv4 # <-> CNAv6。
(3)根据 RFC3344所描述的 MIPv4技术， MNv4产生注册请求消息。注册请求消息的源地址是 CoAv4, 目的地址是 HAAv4#。由于 MNv4不知道 ΗοΑν4#，因此，注册请求消息的家乡地址繊嫂为零， HoAv6 ¾¾fi在扩展域中。 另外， 为了使得 MIPv4/v6-TG随后^ I多在 IPv6网络一侧充当丽 v6， 与 HAv6和 CNv6 ¾ RFC3775戶 ¾|的 MIPv6 ¾ ^进行 CNv6所维持的家乡地址与转 ¾i也址的 新， CNAv4# 也放置在扩展域中。扩展后的注册请求消息如图 15A所示。根据目的地址， 该注册请求消息发往
Figure imgf000015_0001
(4) MIPv4/v6- TG从接收到的注册请求消息中得到 HoAv6、 «：查找地址 lW表得到 CNAv6和 HAAv6、通过在 CoAv4前添加 96位的 NAT-PT网关前缀得到 CoAv6*。然后， ¾ RFC3775所描述的 MIPv6技术， MIPv4/v6- TG产 弗定 新消息，绑定 新消息的源地址是 CoAv6*，目的地址是 H v6， 负载包括 HoAv6。根据目的地址， 该绑定麵消息发往 HAv6。
(5) HAv6收到绑定 §消息后 新自己维持的家乡地址和转 ¾t也址的绑定，并向 MIPv4/v6-TG 回复绑定确认消息。
(6)根据 RFC3775, 在 MNv6向 CNv6魏绑定 ¾ff之前， 要进行 RRP认证。此时 MIPv4八 6-TG 将充当 MNv6向 CNv6 RRP认证， RRP认证按照 RFC37755所描述的流禾 St行， RRP具体步骤如下： MIPv4/v6-TG首先同时向 CNv6发送 Home Test Init消息和 Caxe-of Test Init消息，其中 Home Test Init消息需要经过 HAv6， Care-of Test Init消息直接发送给 CNv6; CNv6收到 Home Test Init消 息和 Care- of Test Init消息后分别回复 Home Test消息和 Care- of Test消息， Home Test消息和 Care-of Test消息按照原路返回。
(7) RRP认证结束后， MIPv4/v6-TG向 CNv6 ^¾5定 新消息。
(8 ) CNv6收到绑定更新消息后首先更新自己维持的家乡地址和转交地址的绑定， 然后向
MIPv4/v6-TG回复绑定确认消息。
(9 ) MIPv4/v6-TG收到绑定确认消息后， MIPv4/v6- TG 中的 NAT- PT建立地址映射： ΗοΑνό HoAv4 #， MIP-ALG建立地址绑定： HoAv4 # CoAv4和 ϋοΑνό <→· CoAv6 *。 然 后 MIPv4/v6- TG向 MNv4回复注册应答消息。 MIPv4/v6-TG在注册应答消息中向 MNv4提供了 HoAv4#。 此时注册应答消息的格式如图 15B所示。
图 16是 HA和 CN都位于 IPv6网络，謂从 IPv4网络移动到 IPv6网络时的移动 IPv4/v6解决方 案的示意图。
当 MN从 IPv4网络移动到 IPv6网络后， MN、 HA和 CN者赃 IPv6网络， 这是典型的 MIPv6的问 题， 将按照 RFC3775所描述的 MIPv6 进 ¾¾信和¾新， 具体的实施逝呈见图 3。
图 17是 HA和 CN都位于 IPv4网络， 丽在 IPv4/v6混合网络中移动的布局示意图。
如图 17所示 HA和 CN都位于 IPv4网络，丽在 IPv4八 6混合网络中移动， ¾t ^呈可以分为 M 在 IPv4网络中移动时与 CN的通信， MN在 IPv6网络中移动时与 CN的通信， MN从 IPv4网络移动到
IPv6网络时与 CN的通信， ,从 IPv6网络移动到 IPv4网络时与 CN的通信。下面将分别对这几种情 况下的通信进ϊ 细的说明。
图 18是 ΗΑ和 CN都位于 IPv4网络，丽在 IPv4网络中移动时移动 ΙΡν4/ν6解决方案的示意图。 当圆在 IPv4网络内移动时，應、 HA和 CN者 |¾ IPv4网络内， 这是典型的 MIPv4的问题， 将按 照 RFC3344所描述的 MIPv4技术进 fi¾信和 新， 具体的实施过 ¾¾图 1。
图 19是 HA和 CN都位于 IPv4网络，丽在 IPv6网络中移动时 MIPv4/v6-TG的地址配置示意图。 当 MN在 IPv6网络移动时， MIPv4/v6-TG在 IPv4网络一侧充当 MNv4,与 CNv4和 HAv4构成 RFC3344 所描述的 MIPv4技术的三个实体，按照 RFC3344所描述的 MIPv4技术进 fi¾信,为了使得 MIPv4八 6-TG 在 IPv4网络一侧充当 MNv4， MIPv4/v6-TG中的 NAT- PT必须维持 Co W# <→· CoAv6的地址映射。
在 IPv6网络一侧， MIPv4/v6-TG充当 CNv6， 与 MNv6构成 RFC3775所描述的 MIPv6技术的两个 实体， 按照 RFC3775所描述的 MIPv6技术进行通信。 为了充当 CNv6， MIPv4 6- TG中的 MIP- ALG必 须维持 v6* CoAv6的地址绑定。
图 20是 HA和 CN都位于 IPv4网络， 讓在 IPv6网络中移动时的通信流程图。具体的通信步骤 包括：
( 1 )根据 RFC3775所描述的 ΜΙΡνθ技术， MNv6向 CNv4 ^M. IPv6格式的 β报文， 地址 是 CoAv6， 目的地址是 CNAv6*， 同时 报文的目的«项扩展头的家乡地 项中插入家乡地 址 HoAv6*。根据目的地址， 这样的 1¾@报文发往 MIPv4八 6-TG。 (2) MIPv4/v6- TG上的 NAT- ΡΓ网关根据«报文的目的地址是 CNAv6*的特征将 获并送到 MIP-ALG上处理。 MIP- ALG从 |¾g报文的目的 ffi 项扩展头的家乡地址选项中取出 HoAv6*， 并用这 个 HoAv6*作为薩报文新的源地址， 使移动节点的移动对于上层的业 呆插明。然后， MIP-ALG 把«报文交给 ΝΑΤ-ΡΓ网关处理， NAT- PT网^ j¾g报文进衍也址协议转换， 转换后的 报文 的源地址为 HoAv4， 目的地址为 CNAv4。根据目的地址， 这样的聽报 接发往 CNv4。
(3)根据 RFC3344所描述的 MIPv4技术， CNv4向 MNv6发送 IPv4格式的 报文， ¾H地址 是 CNAv4， 目的地址为 HoAv4， 根据目的地址， ¾$g报文发往 MIPv4/v6-TG。
(4)这样的 ^报文经由 HAv4时被截获， 然后经由 HAv4 M31l«发往 MIPv4/v6— TG。瞧的 源地址是 HAAv4， 目的地址是 CoAv
(5) MIPv4/v6-TG中的 MIP- ALG首先对接收到的数据报文进行解封装， 然后交给 NAT-PT网关 进¾¾也址协议转换， 转换后的«报文源地址是 CNAv6*， 目的地址是 HoAv6*。†雕 RFC3775, 为了 使移动节点的移动对于上层的业 呆漏明， MIPv4/v6-TG中的 MIP- ALG从自己维持的地址绑定 ΗοΑνό^ CoAv6中取出 CoAv6， 把经过 NAT-PT转换后的数据报文的目的地址替换为 CoAv6, 并 把 HoAv6*填入翻报文的第二揚由头中。根据目的地址， 这样的薩报文发往 MNv6。
图 21是 HA和 CN都位于 IPv4网络， 丽在 IPv6网络中移动时的更新流程图。
当 MNv6在 IPv6网络中移动^ ^得新的转 也址后，为了 正常的通信，根据 RFC3775， Μ νβ 需要 HAv6和 CNv6维持的家乡地址和转交地址的绑定。在这里，向 H 6的 新实际上是向处于 IPv4网络中的 HAv4进行 新， 向 CNv6的 新实际上^ MIPv4/v6-TG中 MIP-ALG维持的地址绑定 进行更新。具体的更讓累包括：
(1 ) « RFC3775, MNv6产 定 新消息， 地址是 CoAv6， 目的地址是 HAAv6*， 负载包 括 M v6的家乡地址 HoAv6*。根据目的地址， 该绑定 新消息发往 MIPv4/v6 - TG。
(2) MIPv4/v6- TG把接收到的绑定更新消息转换为注册请求消息， 地址是 CoAv f， 目的地 址是膽 v4， 负载包括 HoAv4。根据目的地址， 该注册请求消息发往 HAv4。
(3) HAv4根据接收到的注髓求消息爾也址绑定： HoAv4 CoAv4#，产生注册应答消息。 注册应答消息的源地 HAAv4， 目的地址是 CoAv4A 负载包括 HoAv40 根据目的地址， 该注册应 答消息发往 MIPv4 -TG。
(4) MIPv4/v6- TG把接收到的 应答消息转换为绑定确认消息，難也址是墜 v6*， 目的地 址是 CoAv6，负载包括 ΗοΑ 。根据目的地址，该绑定确认消息发往斷6。陽接收绑定确认消息， 完成 4维持的家乡地址与转挪止的绑定 新。
(5)根据 RFC3775,在 Νν6向 CNv6魏绑定 新之前，要进行 RRP认证。 RRP具体步骤如下： ΜΝνβ产生 Home Test Init消息， Home Test Init消息的源地址是 HoAv6*， 目的地址是 CNAv6*。 Home Test Init消息通过 Ρϋ¾发往 MIPv4/v6-TG,此时 MIPv4/v6- TG充当 HAv6，隧道道口地址分别为 CoAv6 和 HMv6*。 MIPv4/v6- TG 隧道向 MNv6回复 Home Test消息。 Home Test消息的源地址是 CNAv6*， 目的地址是 HoAv6*。 讀 v6产生 Care of Test Init消息， Care of Test Init消息的源地址是 CoAv6, 目的地址是 CNAv6*。根据目的地址， Care of Test Init消息发往 ΜΙΡν4Λ6- TG， 此时 MIPv4/v6_TG 充当 CNv6。 MIPv4/v6- TG向 MNv6回复 Care of Test消息。 Care of Test消息源地址是 CNAv6*， 目 的地址是 CoAv6。
(6) RRP认证结束后， 根据 RFC3775, MNv6产生并发 定更新消息， 绑定更新消息的源地址 是 CoAv6，目的地址是 CNAv6*，负载包括 ΗοΑ ，根据目的地址，该绑定魏消息发往斷 4八6- TG。
(7)当绑定 新消息经过 MIPv4/v6_TG时被截获， MIPvVv6_TG 新 MIP- ALG维持的地址绑定 ΗοΑνό* <· CoAv6。然后， MIPv4/v6_TG将向丽 v6回复绑定确认消息。
图 22是 HA和 CN都位于 IPv4网络， 丽从 IPv4网络移动到 IPv6网络时的更新流程图。
如图 22所示， 此时 ¾§Μ禾 有两个任务， 一是要实现 ΗΑν4所维持的家乡地址与转¾1：也址 的绑定 新； 二是要 ®1域名查询的方式发现 MIPv4/v6- TG并对 MIPvVv6- TG ®fi¾址配置。在这 个更 1¾程中， 在 IPv4网络一侧， MIPv4/v6- TG充当 M v4， 在 IPv6网络一侧， MIPv4/v6-TG分别 充当 HAv6和 CNv6。 具体的 »骤包括：
( 1 ) MNv6 ffi3l¾gS旬的方式发现 MIPv4/v6-TG, 并获得 HAv4的 IPv6格式的地址 HAAv6*0
(2) M v6 ^査询的方式发现 MIPv4/v6-TG, 得 CNv4的 IPv6格式的地址 CNAv6*。
(3)斷6雄绑定更新消息，源地址是 CoAv6， 目的地址是 HAAv6*，负载包括 HoAv6*， HoAv6* 是由 HoAv4和从 HAAv6*中取出的 96位 ΝΑΤ-ΡΓ地址前缀构成的。根据目的地址， 该绑定更新消息发 往 MIPv4/v6- TGo
(4)MIPv4/v6-TG收到绑定 新消息后会在 AT-PT网关中 ¾ ^也址 CoAv4 # CoAv6。 同日视接收到的绑定 新消息转换戯船胄求消息，注册请求消息的源地址是 CoAv4#， 目的地址是 HAAv4, 负载包括 HoAv4。 根据目的地址， 该注册请求消息发往 4。 (5 ) HAv4收到注册请求消息后会更新其维持的家乡地址与转交地址的地址绑定， 并向 MIPv4/v6-TG回复注册应答消息。
(6) MIPv4/v6- TG把接收到的注册应答消息转换为绑定确认消息并回复丽 v6。
(7)根据 RFC3775,在 MNv6向 CNv6； ^绑定 新之前，要进行 RRP认证。 RRP具体步骤如下： MNv6产生 Home Test Init消息， Home Test Init消息的源地址是 HoAv6*， 目的地址是 CNAv6*。 Home
Test Init消息通过 H¾发往 MIPv4八 6- TG，此时 MIPv4/v6-TG充当 HAv6， «道口地址分别为 CoAv6 和 HMv6*0 MIPv4/v6-TG 隧道向 MNv6回复 Home Tes 消息。 Home Test消息的源地址是 CNAv6*， 目的地址是 ΗοΑν6*。 ΜΝνβ产生 Care of Test Init消息， Care of Test Init消息的源地址是 CoAv6， 目的地址是 CNAv6*。根据目的地址， Care of Test Init消息发往 MIPv4/v6- TG， 此时 MIPv4/v6- TG 充当 CNv6。 MIPv4/v6-TG向應 v6回复 Care of Test消息。 Care of Test消息源地 CNAv6*; 目 的地址是 CoAv6。
(8) RRP认证结束后， 根据 RFC3775,廳产生并发纏定更新消息， 绑定魏消息的源地址 是 CoAv6，目的地址是 CNAv6*，负载包括 HoAv6*，根据目的地址，该绑定 新消息发往 MIPv4/v6-TG。
(9)当绑定更新消息经过 MIPv4/v6- TG时被截获， MIP-ALG ^ίΐ Μ ΗοΑνό* CoAv6。 然后， MIPv4/v6- TG将向丽 v6回复绑定确认消息。
图 23是 HA和 CN都位于 IPv4网络，画从 IPv6网络移动到 IPv4网络时移动 IPv4/v6解决方案 的示意图。
当續从 IPv6网络移动到 IPv4网络时，應、 HA和 CN ¾¾ IPv4网络内， 这是典型的 MIPv4的 问题， 将按照 RFC3344所描述的 MIPv4技术进¾¾信和 新， 具体的实施过程见图 1。
图 24是 HA位于 IPv6网络、 CN位于 IPv4网络、續在 IPv4八 6混合网络中移动的布局示意图。 如图 24所示 HA位于 IPv6网络、 CN位于 IPv4网络、顾在 IPv4/v6混合网络中移动，整 呈 可以分为顧在 IPv6网络中移动时与 CN的通信， M 在 IPv4网络中移动时与 CN的通信， MN从 IPv6 网络移动到 IPv4网络时与 CN的通信， 讀从 IPv4网络移动到 IPv6网络时与 CN的通信。下面将分 别对这几种情况下的通信进 细的说明。
图 25是 HA位于 IPv6网络、 CN位于 IPv4网络、 MN在 IPv6网络中移动时 ΜΙΡν4Λ6- TG的地址 配置示意图。
当顺在 IPv6网络中移动时， MIPv4/v6-TG在 IPv6网络一侧充当 CNv6, 与 MNv6构成 RFC3775 所描述的 MIPv6技术的两个实体,按照 RFC3775所描述的 MIPv6技术进 fi¾信，为： Π吏得 MIPv4/v6-TG 在 IPv6网络一侧向 MNv6发送数据报文时 多进行家乡地址和转交地址的转换， MIPv4/v6-TG中的 MIP-ALG必须维持 IPv6格式的家乡地址与转麵址的绑定： ΗοΑνό CoAv6。
在 IPv4网络 H , MIPv4/v6-TG在发送 报文时充当 ΜΝν4， 报文时充当 ΗΑν4， 与 CNv4构成 RFC3344所描述的 MIPv4技术的三个实体，按照 RFC3344所描述的 MIPv4技术进 fi¾信。 为了充当 M v4， MIPv4/v6-TG中的 NAT- PT M ' ^ HoAv6 <- HoAv4 #的地址映射。
图 26是 HA位于 IPv6网络、 CN位于 IPv4网络、 M 在 IPv6网络中移动时的通信爾呈图。具体 的通信步骤包括：
(1 )根据 RFC3775所描述的 MIPv6技术， MNv6向 CNv4纖 IPv6格式的 | ^报文， ¾地址 是 CoAv6， 目的地址是 CNAv6*， 同日 ½目的 i碰项扩展头的家乡地址选项中插入家乡地址 HoAv6。 根据目的地址， 这样的麵报文发往 MIPv4/v6-TG0
(2) « RFC3775, MIPv4/v6-TG中 MIP- ALG从接收到的 «报文的家乡地 ¾B 项中取出 HoAv6， 把 报文的源地址从 CoAv6替换为 HoAv6c然后， MIPv4/v6-TG中的 NAT- PT网^ X寸 报: ¾¾行 地址协议转换， 转换后的謹艮文的源地址为 HoAv4#, 目的地址为 CNAv4。根据目的地址， 这样的 麵报文直接发往 CNv40
(3)根据 RFC3344所描述的 MIPv4技术， CNv4向顯 v6 ' IPv4格式的誦报文， 難地址 是 CNAv4， 目的地址为 HoAv 根据目的地址， 这样的麵报文发往 MIPv4/v6_TG。
(4) MIPv4/v6-TG中的 NAT- PT 收到的 报文进衍也址协议转换， 转换后的 报文源 地址是 CNAv6*， 目的地址是 HoAv6。根据 RFC3775, MIPv4/v6- TG中的 MIP- ALG从自己维持的地址绑 定 H v6 CoAv6中取出 CoAv6， 把经过 NAT- PT转换后的数据报文的目的地址从 HoAv6 Wk CoAv6, 并在醫报文中插入一个第二鶴由头， 里面包含 HoAv6。根据目的地址，这样的翻报文 发往画 v6。
图 27是 HA位于 IPv6网络、 CN位于 IPv4网络、 MN在 IPv6网络中移动时的更新流程图。 当 MNv6在 IPv6网络中移动并获得新的转交地址后，为了保持正常的通信，根据 RFC3775, ΜΝνβ 需要 ff HAv6和 CNv6维持的家乡地址和转 ¾t也址的绑定。在 « ^呈中， MIPv4/v6-TG在 IPv6网 络一侧充当 CNv6， 与 HAv6和 MNv6构成 MIPv6更新时的三个实体， 按照 RFC3775对 HAv6和 CNv6维 持的家乡地址与转交地址的绑定进行 新，其中对 CNv6维持的的家乡地址与转 址的绑 ¾ϋ行更 新也就题 MIP-ALG维持的家乡地址与转娜止的绑趙行更新。具体的¾綱聚包括：
(1)†艮据 RFC3775, MNv6产生绑定¾新消息， ！地址是 CoAv6， 目的地址是 HAAv6， 负载包 括斷 6的家乡地址 HoAv6。根据目的地址， 该绑定麵消息发往 HAv6。
(2) ΗΑνβ接收到绑定 HSf消息后对自己维持的家乡地址与转 也址的绑定进行 新， 然后向 M v6回复绑定确认消息， 绑定确认消息的源地址是 HAAv6， 目的地址是 CoAv6。
(3)根据 RFC3775, 在 MNv6向 CNv6雄绑定更新之前， 要进行 RRP认证。在此过程中， MIPv4/v6-TG将充当 CNv6。 RRP认证按照 RFC37755所描述的流 行，具体的步骤如下： M v6首先 同时向 MIPv4/v6_TG ^¾ Home Test Init消息和 Care_of Test Init消息， 其中 Home Test Init 消息需要经过 HAv6， Care-of Test Init消息直接发送给 MIPv4/v6- TG; MIPv4/v6-TG收到 Home Test Init消息和 Care-of Test Init消息后分别回复 Home Test消息和 Care-of Test消息， Home Test 消息和 Care- of Test消息按照原路返回。
(4) RRP认证结束后， †艮据 RFC3775, MNv6产生并发送绑定更新消息， 绑定更新消息的源地址 是 CoAv6， 目的地址是 CNAv6*，负载包括 HoAv6，根据目的地址，该绑定； ¾ff消息发往 MIPv4/v6-TG。
(5)当绑定 新消息经过 MIPv4/v6- TG时被截获， MIPv4/v6-TG ff MIP- ALG维持的地址绑定,
Figure imgf000021_0001
然后， MIPv4/v6- TG将向 M v6回复绑定确认消息。
图 28是 HA位于 IPv6网络、 CN位于 IPv4网络、 MN在 IPv4网络中移动时 MIPv4/v6_TG的地址 配置示意图。
当顺在 IPv4网络移动时, MIPv4/v6-TG在 IPv4网络一侧充当 v4，与 CNv4和 M v4构成 RFC3344 所描述的 MIPv4技术的三个实体，按照 RFC3344所描述的 MIPv4技术进行通信，为了使得 MIPvVv6-TG 在 IPv4网络一侧充当 HAv4， MIPv4/v6-TG中的 NAT- PT必须维持 H^4v< →■ HAAv4 #的地址映射； MIP-ALG必须维持 <·> CoAv4的地址绑定。
根据 RFC3344,为了使得 M v4的移动对 CNv4题明的， MNv4以 IPv4格式的家乡地址雄薩 报文， 因此， MIPv4/v6- TG中的 NAT- PT必须维持 Ho4v6 HoAv4 #的地址映射。
图 29是 HA位于 IPv6网络、 CN位于 IPv4网络、 MN在 IPv4网络中移动时的通信爾呈图。具体 的通信步骤包括：
(1)根据 RFC3344所描述的 MIPv4财， 讀 v4向 CNv4纖 IPv4格式的羅报文， 郷地址 是 HoAv佻 目的地址是 CNAv4。根据目的地址， 这样的麵艮文发往 CNv4。 (2)根据 RFC3344所描述的 MIPv4技术， CNv4向 MNv4发送 IPv4格式的 ¾ig报文， ¾¾地址 是 CNAv4， 目的地址为 HoAv4#。根据目的地址， 这样的 «报文发往 MIPv4/v6- TG。
(3)根据 RFC3344, MIPv4/v6_TG把接收到的誦报文逝醒转发给丽 v4， 瞧的源地址是 HAAv4#, 目的地址是 CoAv40
图 30是 HA位于 IPv6网络、 CN位于 IPv4网络、 MN在 IPv4网络中移动时的更新流程图。
当 M 在 IPv4网络中移动并获得新的转交地址后， 为了保持正常的通信， 根据 RFC3344, M 需 要 新1^4维持的家乡地址和转交地址的绑定。在此 «：程中， MIPvVv6- TG在 IPv4网络 H 充当 HAv4,与 MNv4构成 MIPv4更新时的两个实体，按照 RFC3344所描述的 MIPv4技术对 MIPv4八 6- TG 中 MIP- ALG维持的家乡地址与转交地址的绑定进行更新； MIPv4/v6-TG在 IPv6网络一侧充当 MNv6， 与 HAv6构成 ΜΙΡνθ更新时的两个实体， 按照 RFC3775所描述的 MIPv6技术对 HAv6维持的家乡地址 与转娜止的绑定进行藤。具体的更亲肩包括：
(1 )腸产生注册请求消息， 源地址为 CoAv4， 目的地址是賺 V 负载包括 HoAv4#。根据 目的地址， 该注册请求消息发往 MIPv4/v6-TG。
(2) MIPv4/v6-TG把接收到的注 Mi青求消息转换为绑定更新消息。 绑定更新消息的源地址是 CoAv6*， 目的地址是 HAAv6， 负载包括 HoAv6。根据目的地址， 该绑定 消息发往 HAv6。 ； '
(3) HAv6收到绑定更新消息后， 更新家乡地址与转交地址的绑定并产生绑定确认消息回复
Figure imgf000022_0001
(4) MIPv4/v6-TG收到绑定确认消息后， 新 MIP-ALG维持的地址绑定 Ho4W # r> CoAv4， 并产生注册应答消息回复斷 4。
图 31是 HA位于 IPv6网络、 CN位于 IPv4网络、 MN从 IPv6网络移动到 IPv4网络时的 新流程 图。
如图 31戶 f^， 此时更 i i禾 M±要有两个任务， 一是要 ¾ HAv6所维持的家乡地址与转¾1也址 的绑定； 二是要謝：¾½查询的方式发现 MIPv4/v6-TG并对 ΜΙΡν4Λ6- TG进機址配置。在这个更 fi¾程中，在 IPv4网络一侧， MIPv4/v6-TG充当 HAv4，在 IPv6网络一侧， MIPv4/v6-TG充当 M v6。 具体的 骤包括：
(1) MNv6碰:^ ¾i旬的方式发现 MIPv4/v6-TG, 纖得 HAv6的 IPv4格式的地址 HAAv4#0 在此 ¾¾查询的过程中， MIPv4 -TG中的 NAT- PT ¾&j：也址 ： HAAv6 ^ HAAv4# a (2) MNv6 旬的方式发现 MIPv4/v6-TG, 并获得 CNv4的 IPv4格式的地址 CNAv40
(3) MNv4产生注册请求消息， 源地址为 CoAv4, 目的地址是腿 v4#。但是， 因为 MNv4尚不知 道 HoAv4#，只是知道 HoAv6，因此， v把注册请求消息中的家乡地址域置零,在扩展域中填入 HoAv6。 此附广展后的注 jffi青求消息的格式如图 32A所示。根据目的地址，该注册请求消息发往 MIPv4/v6-TG。
(4) MIPv4/v6-TG把接收到的注册请求消息转换为绑定更新消息。绑定更新消息的源地址是
CoAv6*, 目的地址是 HMv6， 负载包括 HoAv6。根据目的地址， 该绑定赚肖息发往 HAv6。
(5) HAv6收到绑定更新消息后， 更新家乡地址与转交地址的绑定并产生绑定确认消息回复
Figure imgf000023_0001
(6) MIPv4/v6- TG收到绑定确认消息后， 在 NAT-PT中¾^也址嘛： ΗοΑνό <r HoAv4#， 在 MIP-ALG中 ^也址绑定： H^W# 0 Co4W， 并产生注册应答消息回复 MNv4。注册应答消息 包括了 HoAv4#0此日 t注册应答消息的格式如图 32B所示。
图 33是 HA位于 IPv6网络、 CN位于 IPv4网络、囊从 IPv4网络移动到 IPv6网络时的更 ff流程 图。
如图 33所示， 此时 «：禾 M±¾ 两个任务， 一是要实现 H/ 6所维持的家乡地址与转 也址 的绑定 新； 二; K 域名 Si旬的方式发现 MIPv4/v6- TG并对 MIPv4/v6-TG ¾fi¾址 155。具体 的 觀聚包括：
(1) MNv6舰 ¾ ^查询的方式获得 HAv6的 IPv6格式的通 HAAv60
(2) M v6 ^查询的方式发现 MIPv4/v6-TG, 并获得 CNv4的 IPv6格式的地址 CNAv6*„
(3) 艮据 RFC3775, ΜΝν6产生绑定 新消息， ¾¾!地址是 CoAv6， 目的地址是 HAAv6， 负载包 括陽的家乡地址 HoAv6。根据目的地址， 该绑定麵消息发往 HAv6。
(4) ΗΑνβ接收到绑定藤消息后对自己维持的家乡地址与转娜止的绑定进行 然后向 MNv6回复绑定确认消息， 绑定确认消息的源地址是 HAAv6， 目的地址是 CoAv6， 负载包括 MNv6的家 乡地址 HoAv6。
(5)根据 RFC3775, 在 M v6向 CNv6魏绑定更新之前， 要进行 RRP认证。
Figure imgf000023_0002
MIPv4/v6-TG将充当 CNv6。 RRP认证按照 RFC37755所描述的流禾 St行，具体的步骤如下： MNv6首先 同时向 MIPv v6-TG ^H Home Test Init消息和 Care- of Test Init消息， 其中 Home Test Init 消息需要经过 HAv6， Care- of Test Init消息直接发送给 MIPv4八 6-TG; MIPv4/v6-TG收到 Home Test Init消息和 Care- of Test Init消息后分别回复 Home Test消 J l Care- of Test消息， Home Test 消息和 Care-of Test消息按照原路返回。
(6) RRP认证结束后， 根据 RFC3775, 斷6产生并发纏定更新消息， 绑定更新消息的源地址 是 CoAv6， 目的地址是 CNAv6*,负载包括 HoAv6,根据目的地址，该绑定 Hff消息发往 MIPv4/v6- TG。
(7) MIPv4/v6-TG接收到绑定 ff消息后， 在 NAT- PT中 ¾¾¾址隱： ΗοΑνό ΗοΑν4 #， 在 MIP- &中¾^ ^乡地址与转交地址的绑定： HoAv6 ^ CoAv6 o然后， MIPv4/v6- TG产生绑定 确认消息并回复顺 v6。
图 34是 HA位于 IPv4网络、 CN位于 IPv6网络、丽在 IPv4/v6混合网络中移动的布局示意图。 如图 34所示 HA位于 IPv4网络、 CN位于 IPv6网络、顺在 IPv4/v6混合网络中移动， ^ 可以分为丽在 IPv4网络中移动时与 C 的通信， M 在 IPv6网络中移动时与 CN的通信， M 从 IPv4 网络移动到 IPv6网络时与 CN的通信， MN从 IPv6网络移动到 IPv4网络时与 CN的通信。下面将分 别对这几种情况下的通信进 ¾^细的说明。
图 35是 HA位于 IPv4网络、 CN位于 IPv6网络、 MN在 IPv4网络中移动时 MIPv4/v6- TG的地址 配置 图。
当顺在 IPv4网络移动时， MIPv4/v6-TG在 IPv4网络一侧充当 CNv4，与 HAv4和顧 v4构成 RFC3344 所描述的 MIPv4技术的三个实体，按照 RFC3344所描述的 MIPv4 进行通信; MIPv4/v6-TG在 IPv6 网络一侧充当 MNv6， 与 CNv6构成 RFC3775所描述的 MIPv6技术的两个实体， 按照 RFC3775所描述 的 MIPv6技术进洒言。
为了使得 MIPv4/v6-TG在 IPv4网络一侧充当 CNv4， MIPv4/v6-TG中的 NAT- PT必须维持 CNAv4 # - CNAv6的地址映射。为了使得 MIPv4/v6-TG在 IPv6网络一侧充当 MNv6， MIPv4/v6~TG 中的 MIP- ALG必须维持 H^4v6* CoAv6 *的地址绑定。
图 36是 HA位于 IPv4网络、 CN位于 IPv6网络、顺在 IPv4网络中移动时的通信流程图。具体 的通信步骤包括：
(1)根据 RFC3344所描述的 MIPv4技术， MNv4向 CNv6雄 IPv4格式的画报文， 源地址是 HoAv4, 目的地 ii½ CNAv4#0根据目的地址， 这样的 报文发往 MIPv4/v6- TG。
(2) MIPv4/v6-TG中的 NAT- PT把 MNv4发出的 IPv4格式的数据报文转换成 IPv6格式的数据报 文， 转换后的麵报文的源地址为 HoAv6*， 目的地址为 CNAv6。根据 RFC3775, 为了使移动节点的 移动对于上层的业务保持透明， MIPv4/v6- TG 中的 MIP-ALG 从自己维持的地址绑定 ΗοΑνό* CoAv6*中取出 CoAv6*，把经过 NAT- PT转换后的数据报文的源地址替换为 CoAv6*，并 把 HoAv6*填入麵报文的目的 j：舰项扩展头的家乡地 tlB 项中。根据目的地址， 这样的鶴报文发 往 CNv6。
(3)棚 RFC3775所描述的 MIPv6技术， CNv6向斷 4雄 IPv6格式的麵报文， 源地址是
CNAv6, 目的地址是 CoAv6*， «报文中的第二 »由头里存放 HoAv6*0根据目的地址， 这样的数 据报文发往 MIPv4/v6-TGo
(4) MIPv4/v6-TG中的 MIP- ALG根据 RFC3775的规定， 从接收到的 IPv6格式的数据报文的第 二！^由头里取出家乡地址 HoAv6*, 替换 CoAv6*， 作为目的地址。 MIPv4/v6-TG中的 NAT- PT 过转换的賺艮文转换为 IPv4格式的賺艮文，源地址为 CNAv4#, 目的地址为 HoAv4。根据目的地 址， 这样的醒艮文发往 HAv4。
(5)按照 RFC3344, HAv4逝 (¾»Ε Ι』的翻报文转发给 4。隨的源地址是 Η ν4， 目 的地址是 CoAv4。
图 37是 HA位于 IPv4网络、 CN位于 IPv6网络、續在 IPv4网络中移动时的更新流程图。 根据 RFC3344, 應在 IPv4网络中发生移动后会获得新的转交地址， MNv 需要更新 HAv 所维持 的家乡地址与转交地址的绑定。 另外， 虽然， CNv6和 MIP- ALG都维鐘 IPv6格式的家乡地址与转 交地址的绑定： ΗοΑνό* →· CoAv6 *， 但是， CoAv6*由 CoAv4和 NAT- PT的 96位 IPv6地址前缀组 成， 在通信过程中， 麵报文是根据 CoAv6*中 NAT- PT的 96位 IPv6地址前缀路由到 MIPv4/v6-TG, CoAv4实质上并不起i可作用， 因此， 不必对 CNv6和 MIP- ALG维持的地址绑 ¾¾行¾§?。具体的更 新步骤包括：
(1)陽产生并向 HAv4雄注廳求消息， 麵也址为 CoAv4， 目的地址是 HMv4， 负载包 括 HoAv4。
(2) H/ 4收到注 i i胄求消息后， 新自己维持的家乡地址与转 ¾t也址的绑定，然后向 MNv4回 复注册应答消息。
图 38是 HA位于 IPv4网络、 CN位于 IPv6网络、 MN在 IPv6网络中移动时 MIPv4/v6- TG的地址 配置示意图。
根据 RFC3775, MNv6和 CNv6之间直観信。但是 HAv4必须维持 IPv4格式的家乡地址与转 址的绑定 Ho4 Co4W#， 以便掌握 M v6所处的具体位置， 因此， MIPv4/v6- TG中的 NATHPT 需要维持 Coyl # CoAv6的地址 寸。
图 39是 HA位于 IPv 网络、 CN位于 IPv6网络、画在 IPv6网络中移动时的通信流程图。具体 的通信步骤包括：
(1 )根据 RFC3775所描述的 MIPv6技术， MNv6向 CNv6 & IPv6格式的薩报文， I ^报文 的源地址是 CoAv6， 目的地址是 CNAv6， 数据报文的目的地选项扩展头中的家乡地址选项里存放 HoAv6*。
(2)根据 RFC3775所描述的 MIPv6技术， CNv6向 MNv6 IPv6格式的 报文， 报文 的源地址是 CNAv6， 目的地址是 CoAv6， 麵报文的第二鶴由头里存放 ΗοΑ 。
图 40是 HA位于 IPv4网络、 CN位于 IPv6网络、丽在 IPv6网络中移动时的更新 呈图。
当 MN在 IPv6网络中移动并获得新的转交地址后，为了保持正常的通信，需要更新 HAv4和 CNv6 维持的家乡地址与转交地址的绑定。在更新时， MIPv4/v6- TG在 IPv6网络一侧充当 HAv6， 与 MNv6 和 CNv6按照 RFC3775进行家乡地址与转交地址的更新， 而在 IPv4网络一侧则充当 MNv4， 与 HAv4 按照 RFC3344进行家乡地址与转交地址的藤。具体的 骤如下：
(1)讀 v6产生绑定赚肖息。绑定 新消息的源地址是 CoAv6， 目的地址是 H v6*， 负载包 括 HoAv6*。根据目的地址， 该绑定 新消息发往 MIPv4/v6_TG。
(2) MIPv4/v6- TG中的 MIP- ALG把接收到的绑定更新消息转换成注册请求消息。注册请求消息 的源地址是 CoAv4#，目的地址是隐 v4，负载包括 HoAv4。根据目的地址，该注廳求消息发往 HAv4。
(3) HAv4根据接收到的注册请求消息藤家乡地址与转魏址的绑定， 并产生注册应答消息。 注册应答消息的源地址是 HAAv4， 目的地址是 CoAv4#， 负载包括 HoAv4。根据目的地址， 该注册应 答消息发往 MIPv4/v6-TG。
(4) MIPv4/v6- TG收到注册应答消息后， NAT- ΡΤ §ίΜ址 ： CoAv4 # CoAv6， MIP-ALG 把该注册应答消息转换成绑定确认消息。绑定确认消息的源地址是 HMv6*， 目的地址是 CoAv6， 负 载包括 HoAv6*0根据目的地址， 该绑定确认消息发往 MNv6o 斷 6接收绑定确认消息， 完舰 维持的家乡地址与转 ¾t也址的绑定藤。
(5)根据 RFC3775, 在 MNv6向 CNv6魏绑定更新之前， 要进行 RRP认证。在此过程中， MIPv4/v6- TG将充当 HAv6。 RRP认证按照 RFC37755所描述的流^ 4行，具体的步骤如下： MNv6首先 同时向 MIPv4/v6_TG ¾¾ Home Test Init消息和 Care-of Test Init消息， 其中 Home Test Init 消息需要经过 MIPv4/v6- TG然后再转发给 CNv6， Care- of Test Init消息直接:^合 CNv6; CNv6收 到 Home Test Init消息和 Care- of Test Init消息后分别回复 Home Test消息和 Care-of Test消 息， Home Test消息和 Care- of Test消息按照原路返回。
(6) RRP认证结束后， 根据 RFC3775, 丽 v6产生并发纖定更新消息， 绑定更新消息的源地址 是 CoAv6， 目的地址是 CNAv6， 负载包括 HoAv6*， 根据目的地址， 该绑定 新消息发往 CNv6。
( 7 ) CNv6 接收到绑定更新消息后， 更新自己维持的家乡地址与转交地址的绑定：
Figure imgf000027_0001
然后， CNv6产生绑定确认消息并回复丽 v60
图 41是 HA位于 IPv 网络、 C 位于 IPv6网络、丽从 IPv4网络移动到 IPv6网络时的更新流程 图。
如图 41所示，此时 «：禾 ¾¾ 两个任务，一是要实现 HAv4和 CNv6所维持的家乡地址与转 交地址的绑定麵；二是要逝: ¾½查询的方式发现 MIPv4/v6-TG并对 MIPv4/v6-TG进涵址配置。 在这个更 1½程中，在 IPv6网络一侧， MIPv4八 6- TG充当 HAv6，与 CNv6和 MNv6构成 MIPv6更新时 的三个实体，按照 RFC3775所描述的 MIPv6技术对 CNv6维持的家乡地址与转¾1：也址的绑定进行更新; 在 IPv4网络一侧， MIPv4/v6-TG充当丽 v4，与 HAv4按照 RFC3344进行家乡地址与转交地址的更新。 具体的藤步骤包括：
( 1 )斷6舰: ^查询的方式发现 MIPv4/v6-TG, 瓶得 HAv4的 IPv6格式的地址 HAAv6*0
(2)陽逝 魏的方式获得 GNv6的 IPv6格式的地址 CNAv6o
(3)丽 v6雄绑定更新消息，源地址是 CoAv6， 目的地址是 HMv6*，负载包括 ΗοΑν6*， ΗοΑνβ* 由 HoAv4添加 NAT-PT的 96位 IPv6地址前缀构成。根据目的地址， 该绑定更新消息将被发往
Figure imgf000027_0002
(4) MIPv4/v6- TG接收到绑定更新消息后， NAT- ΡΓ 也址 ： CoAv4# CoAv6，然后， MIP-ALG把绑定更新消息转换離册请求消息， 麵地址是 CoAv4#， 目的地址是 HMv4， 负载包括 HoAv4, 根据目的地址， 该注廳求消息发往 HAv4。
(5) HAv4收到注册请求消息后， 更新家乡地址与转交地址的绑定， 并产生注册应答消息， 其 源地址是 HMv4， 目的地址是 CoAv4#， 负载包括 HoAv4。根据目的地址， 该注册应答消息发往
Figure imgf000027_0003
(6) MIPv4/v6_TG收到注廳求消息后， MIP- ALG把该注册应答消息转换成绑定确认消息， 绑 定确认消息的源地址是 HAAv6*， 目的地址是 CoAv6， 负载 HoAv6*。根据目的地址，该绑定确认消息 发往斷 6。斷 6接收绑定确认消息， 完 J»HAv4维持的家乡地址与转娜止的绑定的魏。
(7)根据 RFC3775, 在 MNv6向 CNv6魏绑定 新之前， 要进行 RRP认证。在此过程中， MIPv4/v6-TG将充当 HAv6。 RRP认证按照 RFC37755所描述的流禾 亍，具体的步骤如下： MNv6首先 同时向 MIPv4/v6_TG纖 Home Test Init消息和 Care- of Test Init消息， 其中 Home Test Init 消息需要经过 MIPv4/v6-TG然后再转发给 CNv6, Care- of Test Init消息直接发送给 CNv6; CNv6收 到 Home Test Init消息和 Care- of Test Init消息后分别回复 Home Test消息和 Care- of Test消 息， Home Test消息和 Care-of Test消息按照原路返回。
(8) RRP认证结束后， « RFC3775, MNv6产生并发送绑定 新消息， 绑定更新消息的源地址 是 CoAv6， 目的地址是 CNAv6， 负载包括 HoAv6*， 根据目的地址， 该绑定赚肖息发往 CNv6。
(9) CNv6接收到绑定更新消息后，更新自己维持的地址绑定： HoAv6^ ^ CoAv6。然后， CNv6 产生绑定确认消息并回复斷 6。
图 42是图解 HA位于 IPv4网络、 CN位于 IPv6网络、 MN从 IPv6网络移动到 IPv4网络时的更新 流程图。
如图 42所示，此时¾§¾禾 两个任务，一是要实现 HAv4和 CNv6 ¾隹持的家乡地址与转 交地址的绑定 二是要舰： ¾½魏的方式发现斷 4/V6-TG并对 MIPv4/v6-TG进禱細置0 在 呈中，由于此时讀处于 IPv4网络，根据 RFC3344,. M 只需要对 HAv4维持的绑定进行 新， 但当 MN从 IPv6网络移动到 IPv4网络获得一 的转交地址后， CNv6依旧维持原有的地址绑定， 因此， CNv6维持的地址绑定需要更新。但问题在于' 根据 RFC3344,丽不； ^向 CN的 新。本发 明提出的解决方案扩展了讀的功能，使画倉 多请求 MIPv4/v6- TG代理自己发起向 CNv6的更新。为 了¾¾这个目的， 弓 I进了代理请救口代蒙答两个消息， 同时为了尽可能与 RFC3344兼容， 代理请 求 /代 ¾S答消息的格式与注册请求 /注册应答消息的格式 致。另外为了区分消息， 为代理请 求消息和代難答消息定义了類值。具体的; f綱包括：
(1) M v4产生并向 HAv4纖注册请求消息， 難地址为 CoAv4, 目的舰是 HAAv4， 负载包 括 HoAv4。根据目的地址， 该注册请求消息发往 HAv4。
(2) HAv4收到注册请求消息后， ： Eff自己维持的家乡地址与转交地址的绑定， 然后向 M v4回 复注册应答消息。
(3) Μ ν6 旬的方式发现 MIPv4/v6-TG, 并获得 CNv6的 IPv4格式的; tl lJ: CNAv4#o 在此 査询的逝呈中， MIPv4/v6-TG中的 NAT— PT ¾^了地址 CNAv4 # CNAv6。
(4) MNv4向 MIPvVv6- TG 代理请求消息， 代理请求消息的源地址是 CoAv4, 目的地址是 CNAv4#, 负载包括 HoAv4。 艮据目的地址，代理请求消息发往 MIPv4/v6— TG0本发明中定义代理请求 消息的 ¾值为 7， 代理请求消息的格式如图 43A所示。
(5) MIPv4/v6_TG收到代理请求消息后， 理丽 v4向 CNv6 程。根据 RFC3775, 在向 CNv6；^¾¾新之前， 要进行 RRP认证。 RRP认证按照 RFC37755所描述的流禾 1¾行， 具体的步 S聚如下: MIPv4/v6-TG在 IPv6网络一侧充当 HAv6，向 CNv6 ^i Home Test Init消息。 Home Test Init 消息源地址是 HoAv6*， 目的地址是 CNAv6。 CNv6接到 Home Test Init消息， 会向 MIPv4/v6- TG回 应 Home Test消息。 同时， MIPv4/v6- TG充当 MNv6， 向 CNv6发送 Care of Test Init消息。 Care of Test Init消息源地址是 CoAv6*， 目的地址是 CNAv6。 CNv6接到 Care of Test Init消息， 会向 MIPv4/v6- TG回应 Care of Test消息。
(6) RRP认证结束后， MIPv4/v6_TG充当 MNv6并根据 RFC3775产生绑定更新消息，绑定更新消 息的源地址是 CoAv6*， 目的地址是 CNAv6， 负载包括 HoAv6*， 根据目的地址， 该绑定赚肖息发往
(7) CNv6接收到绑定藤消息后， 新自己维持的地址绑定: HoAv6* ^ CoAv6 *。然后， CNv6产生绑定确认消息并回复 MIPv4/v6-TG。
(8) MIPv4/v6-TG收到绑定确认消息后，首先， MIP-ALG ¾¾i也址绑定： HoAv6* CoAv6*。 然后， MIPv4/v6- TG向 MNv4发出代 ¾S答消息。 ¾S答消息的源地址是 CNAv4#,目的地址是 CoAv4, 负载包括 HoAv4。本发明中定义代 am答消息的«值为 8， 代《 ^答消息的格式如图 43B戶^。
本发明通过在 IPv4网络和 IPv6网络之间设置 MIPv4八 6- TG实现了 IPv4/v6混合网络中的移动 通信， 同时也实现了 RFC3334和 RFC3775的互相透明， 會 满足网络从 IPv4向 IPv6 度期间的需 求； 而且本发明只需要 X愤动节点进行一定的升级， 而对家乡代理和谢 点无需¾¾， 因 Ι¾Φ发 明»充分利用现有的移动通信设备， 具有很大的实用价值。

Claims

权利要求
1.一种实现移动节点在 IPv4/v6混合网络中的通信方法， ^IT征在于: m IPv4网络和 IPv6 网络之间设置移动 IPv4/v6转换网关实现 IPv4/v6混合网络中的移动通信， 戶 M移动
Figure imgf000030_0001
转换 网 括 NAT-PT网^ ¾设在其上的移动 IP应用层网关， 其中 NAT- PT网关上 I5S有 DNS- ALG。
2.根据权利要求 1所述的移动节点在 IPv4/v6混合网络中的通 ί訪法， 其特征在于：
Α.移动 ΙΡν4/ν6转换网关通过在 IPv4网络和 IPv6网络中分别充当 RFC3344和 RFC3775所描述 的不同的实体， 以及通过在网关内部进行实体之间的转换实现 RFC3344和 RFC3775的互相透明； B.移动 IPv4/v6转换网关负责对从 IPv4网络发送到 IPv6网络的、 与移动 IP有关的各种消息 和麵报文进行转换，负责对从 IPv6网络纖到 IPv4网络的、与移动 IP有关的各种消 SSI麵报 文进行转换；
C.移动 IPv4/v6转换网关按照下面的原则截获与移动 IP有关的消 m l 报文： 在¾§？时， 按照消息的 截获消息； 在通信时， 按照 «报文的目的地址截« ^报文；
D.移动 IPv4/v6转换网关在处理 IPv4格式的消息和 «报文时采用 RFC3344 »的¾^机制， 在处理 IPv6格式的消息和賺艮文时采用 RFC3775撤的麵几制；
E.在权利要求 1戶 ¾¾的通信方法中，对家乡代理和通 it f点的要求与 RFC334 和 RFC3775中描 述的要求保持一致， 但增加郝动节点的要求。
3.根据权利要求 2所述的移动节点在 ipV4/v6混合网络中的通訪法， 其特征在于：
A具体包括：
(1够动 IPv4/v6转换网关在 IPv 网络 充当一个 RFC334 所描述的实体， 这个实体与处于 IPv4网络中的其它实 成一个 RFC3344所描述的移动 IP模型，这个移动 IP模型按照 RFC3344中 所描述的移动 IPv4协繊棚言和 ；
(2)移动 IPv4八 6转换网关在 IPv6网络一侧充当一个 RFC3775所描述的实体，该实体与处于 IPv6 网络中的其它实体构成一个 RFC3775所描述的移动 IP模型， 这个移动 IP模型按照 RFC3775中所描 述的移动 IPv6协腿機信和更新；
(3)移动 IPv4/v6转换网关通过实体之间的内部转换实现自己从一个 IPv4形式的实体向一个 IPv6形式的实体的转换， 从一个 IPv6形式的实体向一个 IPv4形式的实体的转换， 以及实现同类实 体之间的转换， 从而最终实现 RFC3344和 RFC3775的互相透明。
4.根据权利要求 2戶; ¾fe的移动节点在 IPv4八 6混合网络中的通 ^法， 其特征在于： 戶 M步骤 B具体包括：
(1)移动 IPv4/v6转换网关负责把 RFC3344所描述的注册请求消息转换成 RFC3775所描述的绑定 更新消息， 把 RFC3344所描述的注册应答消息转换成 RFC3775所描述的绑定确认消息；
(2)移动 IPv4/v6转换网关负责把 RFC3775所描述的绑定藤消息转换成 RFC3344所描述的注册 请求消息， 把 RFC3775所描述的绑定确认消息转滅 RFC3344所描述的注册应答消息；
(3)移动 IPv4/v6转换网关负责对醒艮細 ΐί也址协议转换， 并且在 IPv6网络一侧 报文时， 按照 RFC3775所描述的要求， 把 IPv6格式的腿报文 IP头中的转交地址与扩展头中的家 乡地翻亍交换。
5.根据权利要求 2戶 ¾的移动节点在 IPv4/v6混合网络中的通信 法， 征在于： 纖步骤 C具体包括：
( 信时， 移动 ΙΡν4/ν6转换网关根据不同的通信情况充当不同的实体， 由于以这些实体的 IP ¾址作为目的地址的隨报文会被路由到移动 IPv4/v6转换网关， 因此， 移动 IPv4/v6转换网关 将截获以鹏实体的 IP地址为目的地址的麵报文；
(2)在 新时， 移动 IPv4/v6转换网关按照消息的类型截获消息， 该方法进一步具体包括：
(21)在 IPv4网络， 移动 IPv4/v6转换网 要处理的消息有 RFC334 所描述的注 銶消息 和注册应答消息以及在权利要求 1戶 ¾的通 i ¾¾中定义的代理请求消 mi卩代 am答消息， mm 种消息， 移动 IPv4/v6转换网关在网络层根据消息的 UDP封装和目的端口号截获， 在应用层根据消 息的负纖型值区分；
(22)在 IPv6网络， 移动 IPv4/v6转换网关需要处理的消息有 RFC3775所描述的绑定更新消息、 绑定确认消息、 Home Test Init消息、 Home Test消息、 Care of Test Init消息、 Care of Test 消息;对¾¾消息，移动 IPv4/v6转换网关在网络层根据消息的移动扩展头的下一个报头编号为 135 作为标志截获消息， 在 层根据负载中 MH值区分消息。
6.根据权利要求 2所述的移动节点在 IPv4/v6混合网络中的通訪法， 其特征在于： 戶 M步骤 D具体包括：
(1)当移动 IPv4/v6转换网避收一个消息 报文时， 将根据这个消息¾«报文是 IPv4 格式还是 IPv6格式， 按照 RFC3344或 RFC3775所描述的认证算法进 fiH人证；
(2)当移动 IPv4/v6转换网关;^一个消息¾«报文时， 将根据这个消息¾«报文是 IPv4 格式还是 IPv6格式，按照 RFC334 或 RFC3775所描述的认证算法产生认 这^人证麵諭 为这个消息 ¾ 隱一部分。
7.根据权利要求 2戶 ¾的移动节点在 IPV4/V6混合网络中的通信方法， 其特征在于：
E具体包括：
(1)移动节点倉 同时满足 RFC3344和 RFC3775所描述的有关移动节点的要求；
(2)移动节点 记录家乡個和通信节点的 ¾¾， 舰 DNS査询的方式发现移动 IPv4/v6 转换网关， 并获得家乡代理和通 点的地址；
(3)移动节点翻多支持雕册请求消息和注册应答消息的扩展， 應产生和处理代理请求消獻口 代雜答消息。
8.根据权利要求 7纖的移动节点在 IPv4/v6混合网络中的通 {訪法， 其特征在于： 家乡代理 位于 IPv4网络， 通信节点位于 IPv6网络， 移动节点在 IPv4/v6混合网络中移动时的移动 IPv4/v6 的关键步骤包括- (1)当移动节点从 IPv6网络移动到 IPv4网络时，移动节点向移动 IPv4/v6转换网关;^代理请 求消息，请求移动 IPv4/v6转换网关代理移动节点向处于 IPv6网络中的通信节点发起其家乡地址与 转交地址的绑定更新；
(2)移动 IPv4/v6转换网关收到代理请求消息后， 理移动节点向处于 IPv6网络中的通 点 Mim程， 此日 动 IPv4/v6转换网关在 IPv6网络 将分别充当 IPv6格式的家乡代理和 IPv6格式的移动节点， 移动 IPv4/v6转换网关收到绑定确认消息后， 向处于 IPv4网络中的移动节 点发出代理应答消息；
(3)戶 代理请求消息的格式与 RFC3344中的注册请求消息的格式相同，代雜答消息的格式与 RFC3344中的注册应答消息的格式相同，其中代理请求的麵值被暂定为 7,代 答消息的类型值 被暂定为 8。
PCT/CN2008/000528 2008-03-04 2008-03-17 一种实现移动节点在IPv4/v6混合网络中的通信方法 Ceased WO2009109072A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810026585.9A CN101237410B (zh) 2008-03-04 2008-03-04 一种实现移动节点在IPv4/v6混合网络中的通信方法
CN200810026585.9 2008-03-04

Publications (1)

Publication Number Publication Date
WO2009109072A1 true WO2009109072A1 (zh) 2009-09-11

Family

ID=39920775

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/000528 Ceased WO2009109072A1 (zh) 2008-03-04 2008-03-17 一种实现移动节点在IPv4/v6混合网络中的通信方法

Country Status (2)

Country Link
CN (1) CN101237410B (zh)
WO (1) WO2009109072A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101754426B (zh) * 2009-12-11 2011-11-23 中山大学 一种基于代理网关的移动IPv4/v6的通信方法
CN101977246B (zh) * 2010-09-07 2014-03-12 南京中兴软件有限责任公司 一种PMIPv6移动性的支持方法和系统
CN102625280B (zh) * 2012-03-16 2014-12-24 中山大学 一种基于代理锚点网关的移动IPv4/v6的方法
CN110858849A (zh) * 2018-08-23 2020-03-03 贵州白山云科技股份有限公司 一种云分发网络调度系统及方法

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1885818A (zh) * 2005-06-23 2006-12-27 华为技术有限公司 由IPv4到IPv6网络的基于端口的报文转换实现方法
JP2007166532A (ja) * 2005-12-16 2007-06-28 Matsushita Electric Works Ltd 通信システム
CN101009941A (zh) * 2007-01-15 2007-08-01 中山大学 一种实现移动IPv4节点与IPv6通信节点通信的方法
CN101018412A (zh) * 2007-03-05 2007-08-15 中山大学 一种实现移动节点从IPv6网络切换到IPv4网络的通信方法
CN101030934A (zh) * 2007-04-05 2007-09-05 中山大学 一种基于双向隧道的实现跨异构网络移动通信的方法
CN101030936A (zh) * 2007-04-05 2007-09-05 中山大学 一种实现移动节点从IPv4网络切换到IPv6网络的通信方法
CN101039266A (zh) * 2007-04-28 2007-09-19 中山大学 一种实现IPv4通信节点与跨异构网络的移动节点通信的方法

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1885818A (zh) * 2005-06-23 2006-12-27 华为技术有限公司 由IPv4到IPv6网络的基于端口的报文转换实现方法
JP2007166532A (ja) * 2005-12-16 2007-06-28 Matsushita Electric Works Ltd 通信システム
CN101009941A (zh) * 2007-01-15 2007-08-01 中山大学 一种实现移动IPv4节点与IPv6通信节点通信的方法
CN101018412A (zh) * 2007-03-05 2007-08-15 中山大学 一种实现移动节点从IPv6网络切换到IPv4网络的通信方法
CN101030934A (zh) * 2007-04-05 2007-09-05 中山大学 一种基于双向隧道的实现跨异构网络移动通信的方法
CN101030936A (zh) * 2007-04-05 2007-09-05 中山大学 一种实现移动节点从IPv4网络切换到IPv6网络的通信方法
CN101039266A (zh) * 2007-04-28 2007-09-19 中山大学 一种实现IPv4通信节点与跨异构网络的移动节点通信的方法

Also Published As

Publication number Publication date
CN101237410A (zh) 2008-08-06
CN101237410B (zh) 2011-08-24

Similar Documents

Publication Publication Date Title
KR101364402B1 (ko) 신분 아이디 및 위치 아이디 분리 구조를 기반으로 하는 네트워크와 그 백본 네트워크 및 네트워크 요소
AU2004244296B2 (en) Arrangement for traversing an IPv4 network by IPv6 mobile nodes
CN1830182B (zh) 提取用于在移动路由器与对端路由器之间建立双向隧道的路由信息的布置
CN102256236B (zh) 一种分离映射机制下的移动性管理系统及方法
CN102907072B (zh) 利用NAT64启用IPv6移动性
Gladisch et al. Survey on mobility and multihoming in future internet
WO2007109963A1 (en) A vpn gateway and an ipv6 network system and a system for realizing mobile vpn in hybrid network and the method
WO2005086423A1 (ja) レイヤ２スイッチネットワークシステム
WO2002073907A1 (en) System for managing mobile node in mobile network
EP2201742B1 (en) Provisioning mobility services to legacy terminals
WO2009109072A1 (zh) 一种实现移动节点在IPv4/v6混合网络中的通信方法
CN103108056B (zh) 一种实现身份位置分离网络的设备及方法
Novaczki et al. Micromobility support in HIP: survey and extension of host identity protocol
CN101160842B (zh) 一种实现移动IPv6节点与IPv4通信伙伴通信的方法
CN100596106C (zh) 一种实现移动节点从IPv4网络切换到IPv6网络的通信方法
CN103095581A (zh) 分离终端身份位置标识的系统、方法和服务路由器
CN1863152B (zh) 内网用户之间传递各种报文的方法
JP4106621B2 (ja) モバイル端末及びルータ及びアドレス登録方法
CN1870633B (zh) 通过双栈移动IPv6节点支持移动IPv4的方法
Zhou et al. A network-based global mobility management architecture
KR101529175B1 (ko) 비캡슐화 패킷 전송 방식에서의 이동성 관리방법 및 이동성 관리 시스템
Bokor et al. A Complete HIP Based Framework for Secure Micromobility.
JP2007515823A (ja) グローバルＩＰｖ４／グローバルＩＰｖ６遷移のための端末移動性
JP4606391B2 (ja) アクセスネットワーク及びローカルネットワークに接続する方法、移動端末及びプログラム
KR100749816B1 (ko) ＮＥＭＯ 기반 ⅠＰｖ6 네트워크 환경에서 ⅠＰｖ4네트워크 환경으로 이동하는 이동 네트워크의 이동성 제공방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08714981

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08714981

Country of ref document: EP

Kind code of ref document: A1