CN101237410B

CN101237410B - A method for realizing communication of mobile node in IPv4/v6 mixed network

Info

Publication number: CN101237410B
Application number: CN200810026585.9A
Authority: CN
Inventors: 马争鸣; 向征; 谭庆宇; 熊佳妮; 郑婵娟; 梁文浩
Original assignee: National Sun Yat Sen University
Current assignee: Sun Yat Sen University; National Sun Yat Sen University
Priority date: 2008-03-04
Filing date: 2008-03-04
Publication date: 2011-08-24
Anticipated expiration: 2028-03-04
Also published as: CN101237410A; WO2009109072A1

Abstract

The invention relates to a method for realizing the communication of a mobile node in an IPv4/v6 mixing network, which particularly realizes mobile communication in the IPv4/v6 mixing network through having a mobile IPv4/v6 translation gateway arranged between an IPv4 network and an IPv6 network; the mobile IPv4/v6 translation gateway comprises an NAT-PT gateway and a mobile IP application-level gateway arranged on the NAT-PT gateway, wherein, a DNS-ALG is configured on the NAT-PT gateway. The invention can make the best use of the prior art of MIPv4(RFC3344) and MIPv6(RFC3775), effectively solves the problems of the mobile communication of the mobile node in the IPv4/v6 mixing network and realizes the compatibility of MIPv4 technology and MIPv6 technology and the synchronicity of the transition of the mobile communication and network from the IPv4 to the IPv6; at the same time, the invention requires that the prior mobile communication equipment need no oversize upgrading and has great utility value.

Description

A kind of communication means of mobile node in the IPv4/v6 hybrid network of realizing

Technical field

The present invention relates to network and moving communicating field, be specifically related to the communication means of a kind of mobile node in the IPv4/v6 hybrid network.

Background technology

At present, mobile communication is the of paramount importance application of the Internet bearer.The problem of mobile IP research the Internet bearer mobile communication, particularly, the problem of mobile IPv 4 research IPv4 network carrying mobile communication, the problem of mobile IP v 6 research IPv6 network carrying mobile communication, mobile IPv 4/v6 is exactly the problem of research IPv4/v6 network carrying mobile communication.

Fig. 1 is the schematic diagram of the basic principle of the described mobile IPv 4 technology of RFC3344, and its committed step is as follows:

(1) mobile node moves to field network from local network;

(2) Foreign Agent shows their existence by agent advertisement message (Agent Advertisement Message);

(3) mobile node also can optionally ask the mobile agent of place link to send agent advertisement message to it by Agent Solicitation (Agent SolicitationMessage);

(4) mobile node receives the mobile agent advertisement information, and oneself is in home network or field network according to this message judgement;

(5) if mobile node is found oneself to move to field network, then obtain a Care-of Address from field network.Care-of Address can be assigned by Foreign Agent, also can obtain by modes such as DHCP;

(6) mobile node sends login request message to register its Care-of Address to home agent.The form of login request message is shown in Fig. 2 A, the data such as home address, hometown-agent-address, Care-of Address, identifier that wherein comprise mobile node, and expansion comprises the verify data between mobile node and the home agent, when login request message need be passed through Foreign Agent, expansion also can comprise the verify data between mobile node and the Foreign Agent; Login request message and registration reply message generally will be passed through Foreign Agent;

(7) home agent is handled above-mentioned login request message, creates or upgrades its banding cache, and send registration reply message with the result notification mobile node of registration to mobile node.The form of registration reply message wherein comprises the data such as home address, hometown-agent-address, identifier of mobile node shown in Fig. 2 B, in addition, also comprise some verify datas at expansion;

(8) communication node is when mobile node sends datagram, and source address is the address of communication node, and destination address is the home address of mobile node.In the time of this data message process home network, intercepted and captured the back is sent to mobile node by the tunnel Care-of Address by home agent;

(9) mobile node is when communication node sends datagram, and source address is the home address of mobile node, and destination address is the address of communication node, so data message need not through home network.

Fig. 3 is the schematic diagram of the basic principle of the described mobile IP v 6 technology of RFC3775, and its committed step is as follows:

(1) mobile node moves to field network from local network;

(2) after mobile node moves to field network, will obtain a Care-of Address by state or stateless mode are arranged;

(3) mobile node is registered its Care-of Address by the mode that sends binding update messages to home agent to home agent, and the form of binding update messages is shown in Fig. 4 A;

(4) home agent is handled above-mentioned binding update messages, creates or upgrades its banding cache, and send binding acknowledgement message with the result notification mobile node of registration to mobile node, and the form of binding acknowledgement message is shown in Fig. 4 B;

(5) mobile node is initiated Return Routability Procedure (RRP) process, the RRP process comprises 4 message, be Home Test Init and the Care-of Test Init message that mobile node sends to communication node, and their response message Home Test and Care-of Test message separately, wherein, HomeTest Init message and Home Test message will be transmitted through home agent.The purpose of RRP process be for the home address that guarantees mobile node with and Care-of Address can arrive.Fig. 5 is the flow chart of RRP in the described mobile IP v 6 technology of RFC3775.

(6) after the RRP process finished, mobile node sent binding update messages to communication node;

(7) communication node is created or is upgraded its banding cache, and sends binding acknowledgement message to mobile node;

(8) the mobile node communication that communicates with node has dual mode:

First kind is " bidirectional tunnel " mode.The data message that communication node sends is routed to home network, and home agent is intercepted and captured this data message and this data message sent to the Care-of Address of mobile node by the tunnel; And the data message that mobile node sends sends to home network by reverse tunnel, and then sends to communication node from home network.When adopting this mode, communication node need not to know the mobile node current position information.

Second kind is " routing optimality " mode.This communication mode allows communication node that data message is directly sent to the Care-of Address of mobile node, and its precondition is that mobile node must be to the communication node registration so that communication node be known the binding relationship of its home address and Care-of Address.

The solution of mobile IPv 4/v6 depends on the mode of IPv4 network and IPv6 mixture of networks.At present, IETF recommends three kinds of modes: tunnel (RFC3053), two stack (RFC2893) and NAT-PT (RFC2766).Mobile IPv 4/v6 solution that the present invention proposes is based on NAT-PT.

NAT-PT is the equipment of a network layer, can keep that IPv4 and IPv6's is transparent mutually.Especially, NAT-PT provides a kind of mechanism, keeps same application transparent mutually of the IPv4 network and the IPv6 network carrying by the mode of setting up ALG thereon.At present, ftp-ALG and DNS-ALG have become the standard configuration of NAT-PT.

Fig. 6 adds that with the NAT-PT gateway DNS-ALG realizes the operation principle schematic diagram of the DNS inquiry of IPv4/v6 hybrid network.As shown in Figure 6, be to add that with the NAT-PT gateway DNS-ALG realizes the committed step of the DNS inquiry of IPv4/v6 hybrid network, specific as follows:

(1) the IPv6 main frame will connect with the IPv4 main frame, but does not know what the IPv6 address of this IPv4 main frame is.So send the IPv6 address that the DNS request message is asked IPv4.com, the DNS request message is passed to the dns server A in the IPv6 network, but can not find the record (record of IPv6 is A6 or AAAA, and the record of IPv4 is A) of IPv4 main frame among the dns server A in the IPv6 network;

(2) so IPv6DNS forwards this request message, tackled by DNS-ALG;

(3) DNS-ALG changes A6 in the request message or AAAA into A, is forwarded to the IPv4 network;

(4) the dns server B in the IPv4 network receives this request message, and the address of replying the IPv4 main frame is 202.116.78.11;

(5) after DNS-ALG receives this address information, on the IPv4 address, add 96 prefixes, become IPv6 address prefix::202.116.78.11;

(6) DNS-ALG changes A into and continues after A6 or the AAAA DNS response message is sent back to dns server A in the IPv6 network, passes to the IPv6 main frame again;

(7) the IPv6 main frame thinks that the address of IPv4.com is prefix::202.116.78.11, is 3FFE:3600:B::2 so send source address, and destination address is the IPv6 grouping of prefix::202.116.78.11;

(8) when grouping process transfer gateway, it is at first searched, and whether source address is arranged in its address mapping table is the list item of 3FFE:3600:B::2, if have then directly use it, if do not have, from the IPv4 address pool, distribute an IPv4 address to give this IPv6 main frame, in address mapping table, add a list item 3FFE:3600:B::2-203.69.0.1 in the time of distributing IP v4 address, 96 prefixes that while NAT-PT gateway removes destination address obtain an IPv4 address, also are the IPv4 address of IPv4 main frame;

(9) transfer gateway is according to the address mapping relation of setting up, carry out address and semantic conversion, the group head converts the packets headers of IPv4 to, and the source address in the packets headers is " 203.69.0.1 ", destination address is " 202.116.78.11 ", sends grouping to the IPv4 network then.

Otherwise the reason of the IPv4 address of IPv4 host query IPv6 main frame is the same, and its communication process is consistent basically.

At present, IETF has issued the solution (RFC3344) of mobile IPv 4 and the solution (RFC3775) of mobile IP v 6, for mobile IP provides comparatively complete scheme in the application of pure IPv4 network and pure IPv6 network.Yet, above-mentioned two RFC all do not relate to the situation of IPv4/v6 hybrid network, along with of the transition of IPv4 network to the IPv6 network, research to the mobile communication problem of IPv4/v6 hybrid network seems very necessary, and the mobile communication problem of IPv4/v6 hybrid network can be divided into following 16 subproblems from static angular and dynamic angle:

A1. at first from the angle of static state, the position in the IPv4/v6 hybrid network according to home agent and communication node is divided into four basic problems to the problem of mobile IPv 4/v6, and steps A 1 specifically comprises:

A11. home agent and communication node all are positioned at the IPv6 network, the problem of mobile node mobile IPv 4/v6 when mobile in the IPv4/v6 hybrid network;

A12. home agent and communication node all are positioned at the IPv4 network, the problem of mobile node mobile IPv 4/v6 when mobile in the IPv4/v6 hybrid network;

A13. home agent is positioned at the IPv6 network, and communication node is positioned at the IPv4 network, the problem of mobile node mobile IPv 4/v6 when mobile in the IPv4/v6 hybrid network;

A14. home agent is positioned at the IPv4 network, and communication is positioned at the IPv6 network, the problem of mobile node mobile IPv 4/v6 when mobile in the IPv4/v6 hybrid network.

A2. secondly from dynamic angle, according to the situation of movement of mobile node in the IPv4/v6 hybrid network, again each basic problem described in the described steps A 1 further is divided into four subproblems, its steps A 2 specifically comprises:

A21. the problem of mobile node mobile IPv 4/v6 when mobile in the IPv4 network;

A22. the problem of mobile node mobile IPv 4/v6 when mobile in the IPv6 network;

A23. the problem of the mobile IPv 4/v6 of mobile node when the IPv4 network moves to the IPv6 network;

A24. the problem of the mobile IPv 4/v6 of mobile node when the IPv6 network moves to the IPv4 network.

In addition, for convenience in expressing core concept of the present invention, the present invention has defined the expression mode of some terms, and Fig. 7 is the abbreviation and the explanation thereof of some terms of using among the present invention.Wherein the left side one row of figure are former terms, and the right one row of figure are abbreviations of term, and the present invention adopts the term abbreviation to carry out the statement of summary of the invention.The present invention simultaneously represents version 4 or version 6 by add " v4 " or " v6 " behind above-mentioned term.For example MIPv4 represents Mobile IPv4, and CNv6 represents to be in the CN of IPv6 network, and HoAv6 represents the home address of the IPv6 form of MN.

In addition, the NAT-PT gateway can carry out different processing to different addresses.If NAT-PT adds " # " number in back, an IPv4 address, represent that then this address is the address in the IPv4 address pool among the NAT-PT, form mapping relations with an IPv6 address.For example, CNAv4# is an address in the IPv4 address pool among the NAT-PT, forms mapping relations with CNAv6, is the address designation of CNv6 in the IPv4 network.The data message that with CNAv4# is the IPv4 form of destination address will be routed to NAT-PT.If NAT-PT adds " * " number in back, an IPv6 address, represent that then this address is made up of the 96 bit address prefixes of an IPv4 address and NAT-PT.For example, CoAv6 ^*96 bit address prefixes by CoAv4 and NAT-PT are formed, and are the address designation of MNv4 at the IPv6 network.With CoAv6 ^*For the data message of the IPv6 form of destination address will be routed to NAT-PT.

Summary of the invention

The objective of the invention is to overcome the deficiencies in the prior art, a kind of communication means of mobile node in the IPv4/v6 hybrid network of realizing is provided, this method has effectively solved existing problem in the mobile communication of mobile node in the IPv4/v6 hybrid network, the present invention simultaneously requires existing mobile communication equipment to need not to do too big upgrading, has great practical value.

In order to reach above-mentioned technical purpose, technical solution of the present invention: a kind of communication means of mobile node in the IPv4/v6 hybrid network of realizing, by the mobile communication in mobile IPv 4/v6 transfer gateway realization IPv4/v6 hybrid network is set between IPv4 network and IPv6 network, described mobile IPv 4/v6 transfer gateway comprises the NAT-PT gateway and establishes thereon mobile IP ALG, wherein disposes DNS-ALG on the NAT-PT gateway.

The step of the communication means of described mobile node in the IPv4/v6 hybrid network is:

Steps A is: mobile IPv 4/v6 transfer gateway is by serving as RFC3344 and the described different entity of RFC3775 respectively in IPv4 network and IPv6 network, and realizes that by the conversion of carrying out at intra-gateway between the entity RFC3344 and RFC3775's is transparent mutually.Specifically, this steps A specifically comprises:

A1. mobile IPv 4/v6 transfer gateway serves as a described entity of RFC3344 in IPv4 network one side, this entity constitutes the described mobile IP model of RFC3344 with other entity that is in the IPv4 network, and this moves IP model and communicates according to the described mobile IPv 4 agreement of RFC3344 and upgrade;

A2. mobile IPv 4/v6 transfer gateway serves as a described entity of RFC3775 in IPv6 network one side, this entity constitutes the described mobile IP model of RFC3775 with other entity that is in the IPv6 network, and this moves IP model and communicates according to the described mobile IPv 6 protocol of RFC3775 and upgrade;

A3. mobile IPv 4/v6 transfer gateway is realized the conversion of own entity from an IPv4 form to the entity of an IPv6 form by the internal conversion between the entity, from the conversion of the entity of an IPv6 form to the entity of an IPv4 form, and realize conversion between the similar entity, thereby realize that finally RFC3344 and RFC3775's is transparent mutually.

Step B is: mobile IPv 4/v6 transfer gateway is responsible for changing send to various message and data message the IPv6 network, relevant with mobile IP from the IPv4 network, is responsible for changing send to various message and data message the IPv4 network, relevant with mobile IP from the IPv6 network.Specifically, this step B comprises:

B1. mobile IPv 4/v6 transfer gateway is responsible for the described login request message of a RFC3344 and is converted the described binding update messages of RFC3775 to, and the described registration reply message conversion of RFC3344 is become the described binding acknowledgement message of RFC3775;

B2. mobile IPv 4/v6 transfer gateway is responsible for the described binding update messages of a RFC3775 and is converted the described login request message of RFC3344 to, and the described binding acknowledgement message conversion of RFC3775 is become the described registration reply message of RFC3344;

B3. mobile IPv 4/v6 transfer gateway is responsible for the data message is carried out the address protocol conversion, and when IPv6 network one side transceive data message, according to the described requirement of RFC3775, Care-of Address in the data message IP head of IPv6 form and the home address in the extension header are exchanged.

Step C is: mobile IPv 4/v6 transfer gateway is intercepted and captured message and the data message relevant with mobile IP according to following principle: when upgrading, intercept and capture message according to the type of message; When communication, according to the destination address intercepted data message of data message; Specifically, this step C comprises:

C1. when communication, mobile IPv 4/v6 transfer gateway serves as different entities according to different signal intelligences, owing to can be routed to mobile IPv 4/v6 transfer gateway as the data message of destination address with the IP address of these entities, therefore, will to intercept and capture the IP address with these entities be the data message of destination address to mobile IPv 4/v6 transfer gateway;

C2. when upgrading, mobile IPv 4/v6 transfer gateway is intercepted and captured message according to the type of message, and this method further specifically comprises:

C21. at the IPv4 network, the message that mobile IPv 4/the v6 transfer gateway need be handled has the Agent Solicitation and the proxy response message of redetermination among the described login request message of RFC3344 and registration reply message and the present invention, to these four kinds of message, mobile IPv 4/v6 transfer gateway is intercepted and captured according to the UDP encapsulation and the destination slogan of message in network layer, distinguishes according to the loadtype value of message in application layer;

C22. at the IPv6 network, the message that mobile IPv 4/the v6 transfer gateway need be handled has the described binding update messages of RFC3775, binding acknowledgement message, Home Test Init message, Home Test message, Care of Test Init message, Care of Test message; To these message, mobile IPv 4/v6 transfer gateway is numbered 135 in network layer according to the mobile prolate-headed next header of message and as a token of intercepts and captures message, application layer according to load in the MH value distinguish message.

Step D is: the security mechanism that mobile IPv 4/v6 transfer gateway adopts RFC3344 to provide when the message of process IP v4 form and data message, the security mechanism that adopts RFC3775 to provide when the message of process IP v6 form and data message; This step D is specifically:

D1. when mobile IPv 4/v6 transfer gateway receives message or data message, will be IPv4 form or IPv6 form, authenticate according to RFC3344 or the described identifying algorithm of RFC3775 according to this message or data message;

D2. when mobile IPv 4/v6 transfer gateway sends message or data message, to be IPv4 form or IPv6 form according to this message or data message, produce verify data according to RFC3344 or the described identifying algorithm of RFC3775, this verify data will be as the part of this message or data message.

Step e is: the requirement to home agent and communication node in the communication means of realization mobile node in the IPv4/v6 hybrid network that the present invention proposes is consistent with RFC3344 and the described requirement of RFC3775, but increase is to the requirement of mobile node.This step e is specifically: step e specifically comprises:

E1. mobile node can satisfy the requirement of RFC3344 and the described relevant mobile node of RFC3775 simultaneously;

E2. mobile node can write down the domain name of home agent and communication node, can find mobile IPv 4/v6 transfer gateway by the mode of DNS inquiry, and obtain the address of home agent and communication node;

E3. mobile node can be supported the expansion to login request message and registration reply message, can produce and handle Agent Solicitation and proxy response message.

Step F is: when local agency is positioned at the IPv4 network, communication node is positioned at the IPv6 network, and the committed step of mobile node mobile IPv 4/v6 when mobile in the IPv4/v6 hybrid network comprises:

F1. when mobile node when the IPv6 network moves to the IPv4 network, mobile node sends Agent Solicitation to mobile IPv 4/v6 transfer gateway, and the request mobile IPv 4/communication node of v6 transfer gateway proxy mobile node in being in the IPv6 network initiated the Binding Update of its home address and Care-of Address;

F2. after mobile IPv 4/the v6 transfer gateway is received Agent Solicitation, the communication node of proxy mobile node in being in the IPv6 network initiated renewal process, this moment, mobile IPv 4/v6 transfer gateway will serve as the home agent of IPv6 form and the mobile node of IPv6 form respectively in IPv6 network one side, after mobile IPv 4/v6 transfer gateway was received binding acknowledgement message, the mobile node in being in the IPv4 network sent proxy response message;

F3. the form of the login request message among the form of described Agent Solicitation and the RFC3344 is identical, the form of the registration reply message among the form of proxy response message and the RFC3344 is identical, wherein the types value of proxy requests is 7 by fixing tentatively, and the types value of proxy response message is 8 by fixing tentatively.

Compared with prior art, advantage of the present invention is:

Can make full use of existing MIPv4 (RFC3344) and MIPv6 (RFC3775) technology, realize the mobile communication of mobile node in the IPv4/v6 hybrid network, and realized the compatibility of MIPv4 technology and MIPv6 technology, realized that mobile communication and network are from the synchronism of IPv4 to the IPv6 transition, the present invention simultaneously requires existing mobile communication equipment to need not to do too big upgrading, has great practical value.

Description of drawings

Fig. 1 is the schematic diagram of the basic principle of the described mobile IPv 4 technology of RFC3344;

Fig. 2 A is the form schematic diagram of login request message;

Fig. 2 B is the form schematic diagram of registration reply message;

Fig. 3 is the schematic diagram of the basic principle of the described mobile IP v 6 technology of RFC3775;

Fig. 4 A is the form schematic diagram of binding update messages;

Fig. 4 B is the form schematic diagram of binding acknowledgement message;

Fig. 5 is the flow chart of RRP in the described mobile IP v 6 technology of RFC3775;

Fig. 6 adds that with the NAT-PT gateway DNS-ALG realizes the operation principle schematic diagram of the DNS inquiry of IPv4/v6 network;

Fig. 7 is the abbreviation and the explanation thereof of some terms of using among the present invention;

Fig. 8 is that MIPv4/v6-TG serves as the schematic diagram of different entities at a concrete signal intelligence in the present invention;

Fig. 9 is that HA and CN are arranged in IPv6 network, MN at the mobile schematic layout pattern of IPv4/v6 hybrid network;

Figure 10 is that HA and CN are arranged in IPv6 network, MN move the IPv4/v6 solution when the IPv6 network is mobile schematic diagram;

Figure 11 is that HA and CN are positioned at the IPv6 network, MN address configuration schematic diagram of MIPv4/v6-TG when mobile in the IPv4 network;

Figure 12 is that HA and CN are arranged in IPv6 network, the communication flow diagram of MN when the IPv4 network is mobile;

Figure 13 is that HA and CN are arranged in IPv6 network, the renewal flow chart of MN when the IPv4 network is mobile;

Figure 14 is that HA and CN are positioned at IPv6 network, the MN renewal flow chart when the IPv6 network moves to the IPv4 network;

Figure 15 A is the form expansion schematic diagram of HA and CN login request message when being positioned at IPv6 network, MN and moving to the IPv4 network from the IPv6 network;

Figure 15 B is the form schematic diagram that HA and CN are positioned at IPv6 network, the MN registration reply message when the IPv6 network moves to the IPv4 network;

Figure 16 is that HA and CN are positioned at IPv6 network, MN move to the network time-shifted moving IPv4/v6 solution of IPv6 from the IPv4 network schematic diagram;

Figure 17 is that HA and CN are positioned at the IPv4 network, the schematic layout pattern that MN moves in the IPv4/v6 hybrid network;

Figure 18 is that HA and CN are arranged in IPv4 network, MN move the IPv4/v6 solution when the IPv4 network is mobile schematic diagram;

Figure 19 is the address configuration schematic diagram that HA and CN are arranged in IPv4 network, MN MIPv4/v6-TG when the IPv6 network is mobile;

Figure 20 is that HA and CN are arranged in IPv4 network, the communication flow diagram of MN when the IPv6 network is mobile;

Figure 21 is that HA and CN are arranged in IPv4 network, the renewal flow chart of MN when the IPv6 network is mobile;

Figure 22 is that HA and CN are positioned at IPv4 network, the MN renewal flow chart when the IPv4 network moves to the IPv6 network;

Figure 23 is that HA and CN are positioned at IPv4 network, MN move to the network time-shifted moving IPv4/v6 solution of IPv4 from the IPv6 network schematic diagram;

Figure 24 is that HA is arranged in the IPv6 network, CN is positioned at IPv4 network, MN at the mobile schematic layout pattern of IPv4/v6 hybrid network;

Figure 25 is that HA is arranged in the address configuration schematic diagram that IPv6 network, CN are positioned at IPv4 network, MN MIPv4/v6-TG when the IPv6 network is mobile;

Figure 26 is that HA is arranged in the IPv6 network, CN is positioned at IPv4 network, the communication flow diagram of MN when the IPv6 network is mobile;

Figure 27 is that HA is arranged in the IPv6 network, CN is positioned at IPv4 network, the renewal flow chart of MN when the IPv6 network is mobile;

Figure 28 is that HA is arranged in the address configuration schematic diagram that IPv6 network, CN are positioned at IPv4 network, MN MIPv4/v6-TG when the IPv4 network is mobile;

Figure 29 is that HA is arranged in the IPv6 network, CN is positioned at IPv4 network, the communication flow diagram of MN when the IPv4 network is mobile;

Figure 30 is that HA is arranged in the IPv6 network, CN is positioned at IPv4 network, the renewal flow chart of MN when the IPv4 network is mobile;

Figure 31 is that HA is positioned at IPv6 network, CN and is positioned at IPv4 network, the MN renewal flow chart when the IPv6 network moves to the IPv4 network;

Figure 32 A is that HA is positioned at the form expansion schematic diagram that IPv6 network, CN are positioned at IPv4 network, the MN login request message when the IPv6 network moves to the IPv4 network;

Figure 32 B is that HA is positioned at the form schematic diagram that IPv6 network, CN are positioned at IPv4 network, the MN registration reply message when the IPv6 network moves to the IPv4 network;

Figure 33 is that HA is positioned at IPv6 network, CN and is positioned at IPv4 network, the MN renewal flow chart when the IPv4 network moves to the IPv6 network;

Figure 34 is that HA is arranged in the IPv4 network, CN is positioned at IPv6 network, MN at the mobile schematic layout pattern of IPv4/v6 hybrid network;

Figure 35 is that HA is arranged in the address configuration schematic diagram that IPv4 network, CN are positioned at IPv6 network, MN MIPv4/v6-TG when the IPv4 network is mobile;

Figure 36 is that HA is arranged in the IPv4 network, CN is positioned at IPv6 network, the communication flow diagram of MN when the IPv4 network is mobile;

Figure 37 is that HA is arranged in the IPv4 network, CN is positioned at IPv6 network, the renewal flow chart of MN when the IPv4 network is mobile;

Figure 38 is that HA is arranged in the address configuration schematic diagram that IPv4 network, CN are positioned at IPv6 network, MN MIPv4/v6-TG when the IPv6 network is mobile;

Figure 39 is that HA is arranged in the IPv4 network, CN is positioned at IPv6 network, the communication flow diagram of MN when the IPv6 network is mobile;

Figure 40 is that HA is arranged in the IPv4 network, CN is positioned at IPv6 network, the renewal flow chart of MN when the IPv6 network is mobile;

Figure 41 is that HA is positioned at IPv4 network, CN and is positioned at IPv6 network, the MN renewal flow chart when the IPv4 network moves to the IPv6 network;

Figure 42 is that HA is positioned at IPv4 network, CN and is positioned at IPv6 network, the MN renewal flow chart when the IPv6 network moves to the IPv4 network;

Figure 43 A is that HA is positioned at the form schematic diagram that IPv4 network, CN are positioned at IPv6 network, the MN Agent Solicitation when the IPv6 network moves to the IPv4 network;

Figure 43 B is that HA is positioned at the form schematic diagram that IPv4 network, CN are positioned at IPv6 network, the MN proxy response message when the IPv6 network moves to the IPv4 network.

Embodiment

The present invention relates to a kind of communication means of mobile node in the IPv4/v6 hybrid network of realizing, this communication means is in order to solve 16 subproblems that mobile IPv 4/v6 exists.

Followingly be described in detail with reference to each drawings and the specific embodiments.

As shown in Figure 8, home agent is positioned at IPv4 network (being designated as HAv4), communication node and is positioned at IPv6 network (being designated as CNv6), mobile node and moves between (being designated as MNv4), IPv4 network and the IPv6 network in the IPv4 network internal MIPv4/v6-TG is set.In this case, MIPv4/v6-TG serves as communication node (being designated as CNv4) in IPv4 network one side, communicates according to the described MIPv4 technology of RFC3344 with HAv4 and MNv4.MIPv4/v6-TG serves as mobile node (being designated as MNv6) in IPv6 network one side, communicates according to the described MIPv6 technology of RFC3775 with CNv6.MIPv4/v6-TG carries out the conversion between CNv4 and the MNv6 in inside.

HA and CN are positioned at the IPv6 network as shown in Figure 9, MN moves in the IPv4/v6 hybrid network, whole process can be divided into MN in the IPv6 network when mobile with the communicating by letter of CN, MN in the IPv4 network when mobile with the communicating by letter of CN, MN when the IPv6 network moves to the IPv4 network with the communicating by letter of CN, MN when the IPv4 network moves to the IPv6 network with the communicating by letter of CN.To be described in detail the communication under these several situations respectively below.

Figure 10 is that HA and CN are positioned at the IPv6 network, and MN moves the solution schematic diagram of IPv4/v6 when mobile in the IPv6 network.When MN was mobile in the IPv6 network, all in the IPv6 network, this was the problem of typical MIPv6 for MN, HA and CN, will communicate and upgraded according to the described MIPv6 technology of RFC3775, and concrete implementation process is seen Fig. 3.

Figure 11 is that HA and CN are positioned at the IPv6 network, MN address configuration schematic diagram of MIPv4/v6-TG when mobile in the IPv4 network.When MN when the IPv4 network moves, MIPv4/v6-TG serves as MNv6 in IPv6 network one side, two entities with the described MIPv6 technology of CNv6 formation RFC3775, communicate according to the described MIPv6 technology of RFC3775, in order to make MIPv4/v6-TG can carry out the replacing of home address and Care-of Address when IPv6 network one side direction CNv6 sends datagram, the MIP-ALG among the MIPv4/v6-TG must keep the binding of the home address and the Care-of Address of IPv6 form: HoAv6

CoAv6 ^*

In IPv4 network one side, MIPv4/v6-TG serves as HAv4 when sending datagram, and serves as CNv4 when receiving data packets, and three entities with the described MIPv4 technology of MNv4 formation RFC3344 communicate according to the described MIPv4 technology of RFC3344.In order to serve as HAv4, the NAT-PT among the MIPv4/v6-TG must keep HAAv6

HAAv4# and HoAv6

Two map addresses of HoAv4#, MIP-ALG must keep the binding of the home address and the Care-of Address of IPv4 form: HoAv4#

CoAv4.In order to serve as CNv4 when the receiving data packets, the NAT-PT among the MIPv4/v6-TG must keep CNAv4#

The map addresses of CNAv6.

Figure 12 is that HA and CN are positioned at the IPv6 network, and MN is the communication flow diagram when mobile in the IPv4 network.Concrete communication steps comprises:

(1) according to the described MIPv4 technology of RFC3344, MNv4 is to the data message of CNv6 transmission IPv4 form, and its source address is HoAv4#, and destination address is CNAv4#.According to destination address, such data message mails to MIPv4/v6-TG.

(2) NAT-PT among the MIP-ALG carries out the address protocol conversion to the data message, and the source address of the data message after the conversion is HoAv6, and destination address is CNAv6.According to the described MIPv6 technology of RFC3775, the address binding HoAv6 of MIP-ALG from oneself keeping among the MIPv4/v6-TG

CoAv6 ^*The middle CoAv6 that takes out ^*, the destination address through the data message after the NAT-PT conversion is replaced with CoAv6 from HoAv6 ^*, and HoAv6 is inserted in the home address option of data message.According to destination address, such data message mails to CNv6.

(3) according to the described MIPv6 technology of RFC3775, CNv6 is to the data message of MNv4 transmission IPv6 form, and its source address is CNAv6, and destination address is CoAv6 ^*, and in data message, insert one second class route head, the inside comprises HoAv6.According to destination address, such data message mails to MIPv4/v6-TG.

(4) according to the described MIPv6 technology of RFC3775, the MIP-ALG among the MIPv4/v6-TG takes out HoAv6 from the second class route head of the data message that receives, destination address from CoAv6 ^*Be replaced by HoAv6.NAT-PT among the MIPv4/v6-TG carries out the address protocol conversion to the data message of handling through MIP-ALG, and the data message source address after the conversion is CNAv4#, and destination address is HoAv4#.Such data message mails to MNv4 by the tunnel, and the source address in tunnel is HAAv4#, and destination address is CoAv4.

Figure 13 is that HA and CN are arranged in IPv6 network, the renewal flow chart of MN when the IPv4 network is mobile, and when MN moved in the IPv4 network and obtain a new Care-of Address, MN need initiate renewal process.In renewal process, MIPv4/v6-TG serves as HAv4 in IPv4 network one side, carry out the Binding Update of home address and Care-of Address with MNv4 according to the described MIPv4 technology of RFC3344, the home address that just upgrades among the MIP-ALG to be kept and the binding of Care-of Address.Then, MIPv4/v6-TG serves as MNv6 in IPv6 network one side, carries out the Binding Update of home address and Care-of Address according to the described MIPv6 technology of RFC37755 with HAv6 and CNv6.Concrete step of updating comprises:

(1) according to the described MIPv4 technology of RFC3344, MNv4 produces login request message.The source address of login request message is CoAv4, and destination address is HAAv4#, and load comprises HoAv4#.According to destination address, this login request message mails to MIPv4/v6-TG.

(2) MIPv4/v6-TG is converted to binding update messages to the login request message that receives.The source address of binding update messages is CoAv6 ^*, destination address is HAAv6, load comprises HoAv6.According to destination address, this binding update messages mails to HAv6.

(3) HAv6 receives and at first upgrades the home address oneself kept and the binding of Care-of Address behind the binding update messages, replys binding acknowledgement message to MIPv4/v6-TG then.

(4), before CNv6 initiates Binding Update, carry out the RRP authentication at MNv6 according to RFC3775.MIPv4/v6-TG will serve as MNv6 to CNv6 initiation RRP authentication this moment, the RRP authentication is carried out according to the described flow process of RFC37755, the RRP concrete steps are as follows: MIPv4/v6-TG sends Home Test Init message and Care-of Test Init message to CNv6 at first simultaneously, wherein Home Test Init message need be passed through HAv6, and Care-of Test Init message directly sends to CNv6; CNv6 replys Home Test message and Care-of Test message respectively after receiving HomeTest Init message and Care-of Test Init message, and Home Test message and Care-of Test message are returned according to former road.

(5) after the RRP authentication finished, MIPv4/v6-TG sent binding update messages to CNv6.

(6) CNv6 receives and at first upgrades the home address oneself kept and the binding of Care-of Address behind the binding update messages, replys binding acknowledgement message to MIPv4/v6-TG then.

(7) after MIPv4/v6-TG receives binding acknowledgement message, the home address that renewal MIP-ALG keeps and the binding of Care-of Address.Then, according to the described MIPv4 technology of RFC3344, MIPv4/v6-TG produces registration reply message.The source address of registration reply message is HAAv4#, and destination address is CoAv4, and load comprises HoAv4#.According to destination address, this registration reply message mails to MNv4.

Figure 14 is that HA and CN are positioned at IPv6 network, the MN renewal flow chart when the IPv6 network moves to the IPv4 network.

As shown in figure 14, this moment, renewal process mainly contained two tasks, at first will realize the home address that HAv6 and CNv6 keep and the Binding Update of Care-of Address; Its less important mode by inquiry of the domain name is found MIPv4/v6-TG and MIPv4/v6-TG is carried out address configuration.In this renewal process, in IPv4 network one side, MIPv4/v6-TG serves as HAv4, and in IPv6 network one side, MIPv4/v6-TG serves as MNv6.Concrete step of updating comprises:

(1) MNv4 finds MIPv4/v6-TG by the mode of inquiry of the domain name, and obtains the address HAAv4# of the IPv4 form of HAv6.In this process, the NAT-PT among the MIPv4/v6-TG has set up map addresses: HAAv6 HAAv4#.

(2) MNv4 finds MIPv4/v6-TG by the mode of inquiry of the domain name, and obtains the address CNAv4# of the IPv4 form of CNv6.In this process, the NAT-PT among the MIPv4/v6-TG has set up map addresses: CNAv4#

CNAv6.

(3) according to the described MIPv4 technology of RFC3344, MNv4 produces login request message.The source address of login request message is CoAv4, and destination address is HAAv4#.Because MNv4 does not know HoAv4#, therefore, the home address territory of login request message is changed to zero, and HoAv6 is placed in the extension field.In addition, in order to make MIPv4/v6-TG can serve as MNv6 in IPv6 network one side subsequently, carry out the home address that CNv6 kept and the renewal of Care-of Address with HAv6 and CNv6 according to the described MIPv6 technology of RFC3775, CNAv4# also is placed in the extension field.Login request message after the expansion is shown in Figure 15 A.According to destination address, this login request message mails to MIPv4/v6-TG.

(4) MIPv4/v6-TG obtains HoAv6, obtains CNAv6 and HAAv6, obtains CoAv6 by the NAT-PT gateway prefix of adding 96 before CoAv4 by searching address mapping table from the login request message that receives ^*Then, according to the described MIPv6 technology of RFC3775, MIPv4/v6-TG produces binding update messages, and the source address of binding update messages is CoAv6 ^*, destination address is HAAv6, load comprises HoAv6.According to destination address, this binding update messages mails to HAv6.

(5) HAv6 receives and upgrades the home address oneself kept and the binding of Care-of Address behind the binding update messages, and replys binding acknowledgement message to MIPv4/v6-TG.

(6), before CNv6 initiates Binding Update, carry out the RRP authentication at MNv6 according to RFC3775.MIPv4/v6-TG will serve as MNv6 to CNv6 initiation RRP authentication this moment, the RRP authentication is carried out according to the described flow process of RFC37755, the RRP concrete steps are as follows: MIPv4/v6-TG sends Home Test Init message and Care-of Test Init message to CNv6 at first simultaneously, wherein Home Test Init message need be passed through HAv6, and Care-of Test Init message directly sends to CNv6; CNv6 replys Home Test message and Care-of Test message respectively after receiving HomeTest Init message and Care-of Test Init message, and Home Test message and Care-of Test message are returned according to former road.

(7) after the RRP authentication finished, MIPv4/v6-TG sent binding update messages to CNv6.

(8) CNv6 receives and at first upgrades the home address oneself kept and the binding of Care-of Address behind the binding update messages, replys binding acknowledgement message to MIPv4/v6-TG then.

(9) after MIPv4/v6-TG received binding acknowledgement message, the NAT-PT among the MIPv4/v6-TG set up map addresses: HoAv6 HoAv4#, MIP-ALG sets up address binding: HoAv4#

CoAv4 and HoAv6

CoAv6 ^*MIPv4/v6-TG replys registration reply message to MNv4 then.MIPv4/v6-TG provides HoAv4# to MNv4 in registration reply message.The form of registration reply this moment message is shown in Figure 15 B.

Figure 16 is that HA and CN are positioned at the IPv6 network, the schematic diagram of the mobile IPv 4/v6 solution of MN when the IPv4 network moves to the IPv6 network.

After MN moved to the IPv6 network from the IPv4 network, MN, HA and CN were at the IPv6 network, and this is the problem of typical MIPv6, will communicate and upgraded according to the described MIPv6 technology of RFC3775, and concrete implementation process is seen Fig. 3.

Figure 17 is that HA and CN are positioned at the IPv4 network, the schematic layout pattern that MN moves in the IPv4/v6 hybrid network.

HA and CN are positioned at the IPv4 network as shown in figure 17, MN moves in the IPv4/v6 hybrid network, whole process can be divided into MN in the IPv4 network when mobile with the communicating by letter of CN, MN in the IPv6 network when mobile with the communicating by letter of CN, MN when the IPv4 network moves to the IPv6 network with the communicating by letter of CN, MN when the IPv6 network moves to the IPv4 network with the communicating by letter of CN.To be described in detail the communication under these several situations respectively below.

Figure 18 is that HA and CN are positioned at the IPv4 network, and MN moves the schematic diagram of IPv4/v6 solution when mobile in the IPv4 network.

When MN was mobile in the IPv4 network, all in the IPv4 network, this was the problem of typical MIPv4 for MN, HA and CN, will communicate and upgraded according to the described MIPv4 technology of RFC3344, and concrete implementation process is seen Fig. 1.

Figure 19 is that HA and CN are positioned at the IPv4 network, MN address configuration schematic diagram of MIPv4/v6-TG when mobile in the IPv6 network.

When MN when the IPv6 network moves, MIPv4/v6-TG serves as MNv4 in IPv4 network one side, three entities with CNv4 and the described MIPv4 technology of HAv4 formation RFC3344, communicate according to the described MIPv4 technology of RFC3344, in order to make MIPv4/v6-TG serve as MNv4 in IPv4 network one side, the NAT-PT among the MIPv4/v6-TG must keep CoAv4#

The map addresses of CoAv6.

In IPv6 network one side, MIPv4/v6-TG serves as CNv6, and two entities with the described MIPv6 technology of MNv6 formation RFC3775 communicate according to the described MIPv6 technology of RFC3775.In order to serve as CNv6, the MIP-ALG among the MIPv4/v6-TG must keep HoAv6*

The address binding of CoAv6.

Figure 20 is that HA and CN are positioned at the IPv4 network, and MN is the communication flow diagram when mobile in the IPv6 network.Concrete communication steps comprises:

(1) according to the described MIPv6 technology of RFC3775, MNv6 is to the data message of CNv4 transmission IPv6 form, and its source address is CoAv6, and destination address is CNAv6 ^*, in the home address option of the destination of data message option extension head, insert home address HoAv6 simultaneously ^*According to destination address, such data message mails to MIPv4/v6-TG.

(2) the NAT-PT gateway on the MIPv4/v6-TG is CNAv6 according to the destination address of data message ^*Feature with its intercepting and capturing and deliver to MIP-ALG and go up to handle.MIP-ALG takes out HoAv6 from the home address option of the destination option extension head of data message ^*, and use this HoAv6 ^*As the new source address of data message, make the business that moves for the upper strata of mobile node keep transparent.Then, MIP-ALG gives NAT-PT gateway processes data message, and the NAT-PT gateway carries out the address protocol conversion to the data message, and the source address of the data message after the conversion is HoAv4, and destination address is CNAv4.According to destination address, such data message directly mails to CNv4.

(3) according to the described MIPv4 technology of RFC3344, CNv4 is to the data message of MNv6 transmission IPv4 form, and its source address is CNAv4, and destination address is HoAv4, and according to destination address, this data message mails to MIPv4/v6-TG.

Intercepted and captured when (4) such data message is via HAv4, mail to MIPv4/v6-TG via HAv4 by the tunnel then.The source address in tunnel is HAAv4, and destination address is CoAv4#.

(5) MIP-ALG among the MIPv4/v6-TG at first carries out decapsulation to the data message that receives, and gives the NAT-PT gateway then and carries out the address protocol conversion, and the data message source address after the conversion is CNAv6 ^*, destination address is HoAv6 ^*According to RFC3775, for the business that moves for the upper strata that makes mobile node keeps transparent, the address binding HoAv6 of the MIP-ALG among the MIPv4/v6-TG from oneself keeping ^* Take out CoAv6 among the CoAv6, the destination address through the data message after the NAT-PT conversion is replaced with CoAv6, and HoAv6 ^*Insert in the second class route head of data message.According to destination address, such data message mails to MNv6.

Figure 21 is that HA and CN are positioned at the IPv4 network, and MN is the renewal flow chart when mobile in the IPv6 network.

After MNv6 moved in the IPv6 network and obtains new Care-of Address, in order to keep normal communication, according to RFC3775, MNv6 need upgrade the home address that HAv6 and CNv6 keep and the binding of Care-of Address.Here, the HAv4 that is actually in being in the IPv4 network to the renewal of HAv6 upgrades, and the address binding that MIP-ALG keeps in the renewal of CNv6 is actually MIPv4/v6-TG upgrades.Concrete step of updating comprises:

(1) according to RFC3775, MNv6 produces binding update messages, and its source address is CoAv6, and destination address is HAAv6 ^*, load comprises the home address HoAv6 of MNv6 ^*According to destination address, this binding update messages mails to MIPv4/v6-TG.

(2) MIPv4/v6-TG is converted to login request message to the binding update messages that receives, and its source address is CoAv4#, and destination address is HAAv4, and load comprises HoAv4.According to destination address, this login request message mails to HAv4.

(3) HAv4 is according to the login request message scheduler binding that receives: HoAv4

CoAv4# produces registration reply message.The source address of registration reply message is HAAv4, and destination address is CoAv4#, and load comprises HoAv4.According to destination address, this registration reply message mails to MIPv4/v6-TG.

(4) MIPv4/v6-TG is the registration reply message conversion that receives a binding acknowledgement message, and its source address is HAAv6 ^*, destination address is CoAv6, load comprises HoAv6 ^*According to destination address, this binding acknowledgement message mails to MNv6.MNv6 receives binding acknowledgement message, finishes the home address that HAv4 keeps and the Binding Update of Care-of Address.

(5), before CNv6 initiates Binding Update, carry out the RRP authentication at MNv6 according to RFC3775.The RRP concrete steps are as follows: MNv6 produces Home Test Init message, and the source address of Home Test Init message is HoAv6 ^*, destination address is CNAv6 ^*Home Test Init message mails to MIPv4/v6-TG by the tunnel, and this moment, MIPv4/v6-TG served as HAv6, and road, tunnel port address is respectively CoAv6 and HAAv6 ^*MIPv4/v6-TG replys Home Test message by the tunnel to MNv6.The source address of Home Test message is CNAv6 ^*, destination address is HoAv6 ^*MNv6 produces Care of Test Init message, and the source address of Care of Test Init message is CoAv6, and destination address is CNAv6 ^*According to destination address, Care of Test Init message mails to MIPv4/v6-TG, and this moment, MIPv4/v6-TG served as CNv6.MIPv4/v6-TG replys Care of Test message to MNv6.Care of Test message source address is CNAv6 ^*, destination address is CoAv6.

(6) after the RRP authentication finished, according to RFC3775, MNv6 produced and sends binding update messages, and the source address of binding update messages is CoAv6, and destination address is CNAv6 ^*, load comprises HoAv6 ^*, according to destination address, this binding update messages mails to MIPv4/v6-TG.

(7) intercepted and captured when binding update messages process MIPv4/v6-TG, MIPv4/v6-TG upgrades the address binding HoAv6* that MIP-ALG keeps

CoAv6.Then, MIPv4/v6-TG will reply binding acknowledgement message to MNv6.

Figure 22 is that HA and CN are positioned at the IPv4 network, the renewal flow chart of MN when the IPv4 network moves to the IPv6 network.

As shown in figure 22, this moment, renewal process mainly contained two tasks, and the one, realize the home address that HAv4 keeps and the Binding Update of Care-of Address; The 2nd, find MIPv4/v6-TG and MIPv4/v6-TG is carried out address configuration by the mode of inquiry of the domain name.In this renewal process, in IPv4 network one side, MIPv4/v6-TG serves as MNv4, and in IPv6 network one side, MIPv4/v6-TG serves as HAv6 and CNv6 respectively.Concrete step of updating comprises:

(1) MNv6 finds MIPv4/v6-TG by the mode of inquiry of the domain name, and obtains the address HAAv6 of the IPv6 form of HAv4 ^*

(2) MNv6 finds MIPv4/v6-TG by the mode of inquiry of the domain name, and obtains the address CNAv6 of the IPv6 form of CNv4 ^*

(3) MNv6 sends binding update messages, and source address is CoAv6, and destination address is HAAv6 ^*, load comprises HoAv6 ^*, HoAv6 ^*Be by HoAv4 with from HAAv6 ^*Middle 96 NAT-PT address prefixs that take out constitute.According to destination address, this binding update messages mails to MIPv4/v6-TG.

(4) MIPv4/v6-TG can set up map addresses: CoAv4# after receiving binding update messages in the NAT-PT gateway

CoAv6.Simultaneously the binding update messages that receives is converted to login request message, the source address of login request message is CoAv4#, and destination address is HAAv4, and load comprises HoAv4.According to destination address, this login request message mails to HAv4.

(5) HAv4 understands the address binding that upgrades its home address kept and Care-of Address after receiving login request message, and replys registration reply message to MIPv4/v6-TG.

(6) MIPv4/v6-TG is the registration reply message conversion that receives binding acknowledgement message and replys MNv6.

(7), before CNv6 initiates Binding Update, carry out the RRP authentication at MNv6 according to RFC3775.The RRP concrete steps are as follows: MNv6 produces Home Test Init message, and the source address of Home Test Init message is HoAv6 ^*, destination address is CNAv6 ^*Home Test Init message mails to MIPv4/v6-TG by the tunnel, and this moment, MIPv4/v6-TG served as HAv6, and road, tunnel port address is respectively CoAv6 and HAAv6 ^*MIPv4/v6-TG replys Home Test message by the tunnel to MNv6.The source address of Home Test message is CNAv6 ^*, destination address is HoAv6 ^*MNv6 produces Care of Test Init message, and the source address of Care of Test Init message is CoAv6, and destination address is CNAv6 ^*According to destination address, Care of Test Init message mails to MIPv4/v6-TG, and this moment, MIPv4/v6-TG served as CNv6.MIPv4/v6-TG replys Care of Test message to MNv6.Care of Test message source address is CNAv6 ^*, destination address is CoAv6.

(8) after the RRP authentication finished, according to RFC3775, MNv6 produced and sends binding update messages, and the source address of binding update messages is CoAv6, and destination address is CNAv6 ^*, load comprises HoAv6 ^*, according to destination address, this binding update messages mails to MIPv4/v6-TG.

(9) intercepted and captured when binding update messages process MIPv4/v6-TG, MIP-ALG sets up address binding HoAv6*

CoAv6.Then, MIPv4/v6-TG will reply binding acknowledgement message to MNv6.

Figure 23 is that HA and CN are positioned at the IPv4 network, and MN moves to the schematic diagram of the network time-shifted moving IPv4/v6 solution of IPv4 from the IPv6 network.

When MN when the IPv6 network moves to the IPv4 network, all in the IPv4 network, this is the problem of typical MIPv4 for MN, HA and CN, will communicate and upgrades according to the described MIPv4 technology of RFC3344, concrete implementation process is seen Fig. 1.

Figure 24 is that HA is arranged in the IPv6 network, CN is positioned at IPv4 network, MN at the mobile schematic layout pattern of IPv4/v6 hybrid network.

HA is arranged in that IPv6 network, CN are positioned at the IPv4 network, MN moves at the IPv4/v6 hybrid network as shown in figure 24, whole process can be divided into MN in the IPv6 network when mobile with the communicating by letter of CN, MN in the IPv4 network when mobile with the communicating by letter of CN, MN when the IPv6 network moves to the IPv4 network with the communicating by letter of CN, MN when the IPv4 network moves to the IPv6 network with the communicating by letter of CN.To be described in detail the communication under these several situations respectively below.

Figure 25 is that HA is arranged in the address configuration schematic diagram that IPv6 network, CN are positioned at IPv4 network, MN MIPv4/v6-TG when the IPv6 network is mobile.

When MN is mobile in the IPv6 network, MIPv4/v6-TG serves as CNv6 in IPv6 network one side, two entities with the described MIPv6 technology of MNv6 formation RFC3775, communicate according to the described MIPv6 technology of RFC3775, in order to make MIPv4/v6-TG can carry out the conversion of home address and Care-of Address when IPv6 network one side direction MNv6 sends datagram, the MIP-ALG among the MIPv4/v6-TG must keep the binding of the home address and the Care-of Address of IPv6 form: HoAv6

CoAv6.

In IPv4 network one side, MIPv4/v6-TG serves as MNv4 when sending datagram, and serves as HAv4 when receiving data packets, and three entities with the described MIPv4 technology of CNv4 formation RFC3344 communicate according to the described MIPv4 technology of RFC3344.In order to serve as MNv4, the NAT-PT among the MIPv4/v6-TG must keep HoAv6 The map addresses of HoAv4#.

Figure 26 is that HA is arranged in the IPv6 network, CN is positioned at IPv4 network, the communication flow diagram of MN when the IPv6 network is mobile.Concrete communication steps comprises:

(1) according to the described MIPv6 technology of RFC3775, MNv6 is to the data message of CNv4 transmission IPv6 form, and its source address is CoAv6, and destination address is CNAv6 ^*, in the home address option of destination option extension head, insert home address HoAv6 simultaneously.According to destination address, such data message mails to MIPv4/v6-TG.

(2) according to RFC3775, MIP-ALG takes out HoAv6 among the MIPv4/v6-TG from the home address option of the data message that receives, and the source address of data message is replaced with HoAv6 from CoAv6.Then, the NAT-PT gateway among the MIPv4/v6-TG carries out the address protocol conversion to the data message, and the source address of the data message after the conversion is HoAv4#, and destination address is CNAv4.According to destination address, such data message directly mails to CNv4.

(3) according to the described MIPv4 technology of RFC3344, CNv4 is to the data message of MNv6 transmission IPv4 form, and its source address is CNAv4, and destination address is HoAv4#.According to destination address, such data message mails to MIPv4/v6-TG.

(4) NAT-PT among the MIPv4/v6-TG carries out the address protocol conversion to the data message that receives, and the data message source address after the conversion is CNAv6 ^*, destination address is HoAv6.According to RFC3775, the address binding HoAv6 of the MIP-ALG among the MIPv4/v6-TG from oneself keeping

Take out CoAv6 among the CoAv6, the destination address through the data message after the NAT-PT conversion is replaced with CoAv6 from HoAv6, and insert one second class route head in data message, the inside comprises HoAv6.According to destination address, such data message mails to MNv6.

Figure 27 is that HA is arranged in the IPv6 network, CN is positioned at IPv4 network, the renewal flow chart of MN when the IPv6 network is mobile.

After MNv6 moved in the IPv6 network and obtains new Care-of Address, in order to keep normal communication, according to RFC3775, MNv6 need upgrade the home address that HAv6 and CNv6 keep and the binding of Care-of Address.In renewal process, MIPv4/v6-TG serves as CNv6 in IPv6 network one side, three entities when constituting the MIPv6 renewal with HAv6 and MNv6, the home address of HAv6 and CNv6 being kept according to RFC3775 and the binding of Care-of Address are upgraded, wherein to CNv6 keep home address and home address that MIP-ALG is kept is upgraded just in the binding of Care-of Address and the binding of Care-of Address is upgraded.Concrete step of updating comprises:

(1) according to RFC3775, MNv6 produces binding update messages, and its source address is CoAv6, and destination address is HAAv6, and load comprises the home address HoAv6 of MNv6.According to destination address, this binding update messages mails to HAv6.

(2) HAv6 receives the home address behind the binding update messages oneself kept and the binding of Care-of Address is upgraded, and replys binding acknowledgement message to MNv6 then, and the source address of binding acknowledgement message is HAAv6, and destination address is CoAv6.

(3), before CNv6 initiates Binding Update, carry out the RRP authentication at MNv6 according to RFC3775.In this process, MIPv4/v6-TG will serve as CNv6.The RRP authentication is carried out according to the described flow process of RFC37755, concrete step is as follows: MNv6 sends HomeTest Init message and Care-of Test Init message to MIPv4/v6-TG at first simultaneously, wherein Home Test Init message need be passed through HAv6, and Care-of Test Init message directly sends to MIPv4/v6-TG; MIPv4/v6-TG replys Home Test message and Care-of Test message respectively after receiving Home TestInit message and Care-of Test Init message, and Home Test message and Care-of Test message are returned according to former road.

(4) after the RRP authentication finished, according to RFC3775, MNv6 produced and sends binding update messages, and the source address of binding update messages is CoAv6, and destination address is CNAv6 ^*, load comprises HoAv6, according to destination address, this binding update messages mails to MIPv4/v6-TG.

(5) intercepted and captured when binding update messages process MIPv4/v6-TG, MIPv4/v6-TG upgrades the address binding HoAv6 that MIP-ALG keeps

CoAv6.Then, MIPv4/v6-TG will reply binding acknowledgement message to MNv6.

Figure 28 is that HA is arranged in the address configuration schematic diagram that IPv6 network, CN are positioned at IPv4 network, MN MIPv4/v6-TG when the IPv4 network is mobile.

When MN when the IPv4 network moves, MIPv4/v6-TG serves as HAv4 in IPv4 network one side, three entities with CNv4 and the described MIPv4 technology of MNv4 formation RFC3344, communicate according to the described MIPv4 technology of RFC3344, in order to make MIPv4/v6-TG serve as HAv4 in IPv4 network one side, the NAT-PT among the MIPv4/v6-TG must keep HAAv6

The map addresses of HAAv4#; MIP-ALG must keep HoAv4#

The address binding of CoAv4.

According to RFC3344, in order to make that the mobile of MNv4 is transparent to CNv4, MNv4 sends datagram with the home address of IPv4 form, and therefore, the NAT-PT among the MIPv4/v6-TG must keep HoAv6 The map addresses of HoAv4#.

Figure 29 is that HA is arranged in the IPv6 network, CN is positioned at IPv4 network, the communication flow diagram of MN when the IPv4 network is mobile.Concrete communication steps comprises:

(1) according to the described MIPv4 technology of RFC3344, MNv4 is to the data message of CNv4 transmission IPv4 form, and its source address is HoAv4#, and destination address is CNAv4.According to destination address, such data message mails to CNv4.

(2) according to the described MIPv4 technology of RFC3344, CNv4 is to the data message of MNv4 transmission IPv4 form, and its source address is CNAv4, and destination address is HoAv4#.According to destination address, such data message mails to MIPv4/v6-TG.

(3) according to RFC3344, MIPv4/v6-TG is transmitted to MNv4 to the data message that receives by the tunnel, and the source address in tunnel is HAAv4#, and destination address is CoAv4.

Figure 30 is that HA is arranged in the IPv6 network, CN is positioned at IPv4 network, the renewal flow chart of MN when the IPv4 network is mobile.

After MN moved in the IPv4 network and obtains new Care-of Address, in order to keep normal communication, according to RFC3344, MN need upgrade the home address that HAv4 keeps and the binding of Care-of Address.In this renewal process, MIPv4/v6-TG serves as HAv4 in IPv4 network one side, two entities when constituting MIPv4 and upgrade with MNv4, the home address of MIP-ALG among the MIPv4/v6-TG being kept according to the described MIPv4 technology of RFC3344 and the binding of Care-of Address are upgraded; MIPv4/v6-TG serves as MNv6 in IPv6 network one side, two entities when constituting MIPv6 and upgrade with HAv6, and the home address of HAv6 being kept according to the described MIPv6 technology of RFC3775 and the binding of Care-of Address are upgraded.Concrete step of updating comprises:

(1) MNv4 produces login request message, and source address is CoAv4, and destination address is HAAv4#, and load comprises HoAv4#.According to destination address, this login request message mails to MIPv4/v6-TG.

(3) after HAv6 receives binding update messages, upgrade the binding of home address and Care-of Address and produce binding acknowledgement message and reply MIPv4/v6-TG.

(4) after MIPv4/v6-TG receives binding acknowledgement message, upgrade the address binding HoAv4# that MIP-ALG keeps

CoAv4, and produce registration reply message answer MNv4.

Figure 31 is that HA is positioned at IPv6 network, CN and is positioned at IPv4 network, the MN renewal flow chart when the IPv6 network moves to the IPv4 network.

As shown in figure 31, this moment, renewal process mainly contained two tasks, and the one, upgrade the home address that HAv6 keeps and the binding of Care-of Address; The 2nd, find MIPv4/v6-TG and MIPv4/v6-TG is carried out address configuration by the mode of inquiry of the domain name.In this renewal process, in IPv4 network one side, MIPv4/v6-TG serves as HAv4, and in IPv6 network one side, MIPv4/v6-TG serves as MNv6.Concrete step of updating comprises:

(1) MNv6 finds MIPv4/v6-TG by the mode of inquiry of the domain name, and obtains the address HAAv4# of the IPv4 form of HAv6.In the process of this inquiry of the domain name, the NAT-PT among the MIPv4/v6-TG sets up map addresses: HAAv6

HAAv4#.

(2) MNv6 finds MIPv4/v6-TG by the mode of inquiry of the domain name, and obtains the address CNAv4 of the IPv4 form of CNv4.

(3) MNv4 produces login request message, and source address is CoAv4, and destination address is HAAv4#.But, because MNv4 does not still know HoAv4#, just know HoAv6, therefore, MNv4 inserts HoAv6 to the home address territory zero setting in the login request message in extension field.The form of the login request message after expansion this moment is shown in Figure 32 A.According to destination address, this login request message mails to MIPv4/v6-TG.

(4) MIPv4/v6-TG is converted to binding update messages to the login request message that receives.The source address of binding update messages is CoAv6 ^*, destination address is HAAv6, load comprises HoAv6.According to destination address, this binding update messages mails to HAv6.

(5) after HAv6 receives binding update messages, upgrade the binding of home address and Care-of Address and produce binding acknowledgement message and reply MIPv4/v6-TG.

(6) after MIPv4/v6-TG receives binding acknowledgement message, in NAT-PT, set up map addresses: HoAv6

HoAv4# sets up address binding: HoAv4# in MIP-ALG

CoAv4, and produce registration reply message answer MNv4.Registration reply message has comprised HoAv4#.The form of registration reply this moment message is shown in Figure 32 B.

Figure 33 is that HA is positioned at IPv6 network, CN and is positioned at IPv4 network, the MN renewal flow chart when the IPv4 network moves to the IPv6 network.

As shown in figure 33, this moment, renewal process mainly contained two tasks, and the one, realize the home address that HAv6 keeps and the Binding Update of Care-of Address; The 2nd, find MIPv4/v6-TG and MIPv4/v6-TG is carried out address configuration by the mode of inquiry of the domain name.Concrete step of updating comprises:

(1) MNv6 obtains the address HAAv6 of the IPv6 form of HAv6 by the mode of inquiry of the domain name.

(3) according to RFC3775, MNv6 produces binding update messages, and its source address is CoAv6, and destination address is HAAv6, and load comprises the home address HoAv6 of MNv6.According to destination address, this binding update messages mails to HAv6.

(4) HAv6 receives the home address behind the binding update messages oneself kept and the binding of Care-of Address is upgraded, reply binding acknowledgement message to MNv6 then, the source address of binding acknowledgement message is HAAv6, and destination address is CoAv6, and load comprises the home address HoAv6 of MNv6.

(5), before CNv6 initiates Binding Update, carry out the RRP authentication at MNv6 according to RFC3775.In this process, MIPv4/v6-TG will serve as CNv6.The RRP authentication is carried out according to the described flow process of RFC37755, concrete step is as follows: MNv6 sends HomeTest Init message and Care-of Test Init message to MIPv4/v6-TG at first simultaneously, wherein Home Test Init message need be passed through HAv6, and Care-of Test Init message directly sends to MIPv4/v6-TG; MIPv4/v6-TG replys Home Test message and Care-of Test message respectively after receiving Home TestInit message and Care-of Test Init message, and Home Test message and Care-of Test message are returned according to former road.

(6) after the RRP authentication finished, according to RFC3775, MNv6 produced and sends binding update messages, and the source address of binding update messages is CoAv6, and destination address is CNAv6 ^*, load comprises HoAv6, according to destination address, this binding update messages mails to MIPv4/v6-TG.

(7) after MIPv4/v6-TG receives binding update messages, in NAT-PT, set up map addresses: HoAv6 HoAv4#, the binding of in MIP-ALG, setting up home address and Care-of Address: HoAv6

CoAv6.Then, MIPv4/v6-TG produces binding acknowledgement message and replys MNv6.

Figure 34 is that HA is arranged in the IPv4 network, CN is positioned at IPv6 network, MN at the mobile schematic layout pattern of IPv4/v6 hybrid network.

HA is arranged in that IPv4 network, CN are positioned at the IPv6 network, MN moves at the IPv4/v6 hybrid network as shown in figure 34, whole process can be divided into MN in the IPv4 network when mobile with the communicating by letter of CN, MN in the IPv6 network when mobile with the communicating by letter of CN, MN when the IPv4 network moves to the IPv6 network with the communicating by letter of CN, MN when the IPv6 network moves to the IPv4 network with the communicating by letter of CN.To be described in detail the communication under these several situations respectively below.

Figure 35 is that HA is arranged in the address configuration schematic diagram that IPv4 network, CN are positioned at IPv6 network, MN MIPv4/v6-TG when the IPv4 network is mobile.

When MN when the IPv4 network moves, MIPv4/v6-TG serves as CNv4 in IPv4 network one side, constitutes three entities of the described MIPv4 technology of RFC3344 with HAv4 and MNv4, communicates according to the described MIPv4 technology of RFC3344; MIPv4/v6-TG serves as MNv6 in IPv6 network one side, and two entities with the described MIPv6 technology of CNv6 formation RFC3775 communicate according to the described MIPv6 technology of RFC3775.

In order to make MIPv4/v6-TG serve as CNv4 in IPv4 network one side, the NAT-PT among the MIPv4/v6-TG must keep CNAv4# The map addresses of CNAv6.In order to make MIPv4/v6-TG serve as MNv6 in IPv6 network one side, the MIP-ALG among the MIPv4/v6-TG must keep HoAv6 ^*

CoAv6 ^*Address binding.

Figure 36 is that HA is arranged in the IPv4 network, CN is positioned at IPv6 network, the communication flow diagram of MN when the IPv4 network is mobile.Concrete communication steps comprises:

(1) according to the described MIPv4 technology of RFC3344, MNv4 is to the data message of CNv6 transmission IPv4 form, and source address is HoAv4, and destination address is CNAv4#.According to destination address, such data message mails to MIPv4/v6-TG.

(2) data message of the IPv4 form that MNv4 is sent of the NAT-PT among the MIPv4/v6-TG converts the data message of IPv6 form to, and the source address of the data message after the conversion is HoAv6 ^*, destination address is CNAv6.According to RFC3775, for the business that moves for the upper strata that makes mobile node keeps transparent, the address binding HoAv6 of the MIP-ALG among the MIPv4/v6-TG from oneself keeping ^* CoAv6 ^*The middle CoAv6 that takes out ^*, the source address through the data message after the NAT-PT conversion is replaced with CoAv6 ^*, and HoAv6 ^*Insert in the home address option of destination option extension head of data message.According to destination address, such data message mails to CNv6.

(3) according to the described MIPv6 technology of RFC3775, CNv6 is to the data message of MNv4 transmission IPv6 form, and source address is CNAv6, and destination address is CoAv6 ^*, the second class route in the data message is deposited HoAv6 in front ^*According to destination address, such data message mails to MIPv4/v6-TG.

(4) MIP-ALG among the MIPv4/v6-TG is according to the regulation of RFC3775, takes out home address HoAv6 in front from the second class route of the data message of the IPv6 form that receives ^*, replace CoAv6 ^*, as destination address.NAT-PT among the MIPv4/v6-TG is the data message that is converted to the IPv4 form through the data converted message, and source address is CNAv4#, and destination address is HoAv4.According to destination address, such data message mails to HAv4.

(5) according to RFC3344, HAv4 gives MNv4 the data message forwarding of receiving by the tunnel.The source address in tunnel is HAAv4, and destination address is CoAv4.

Figure 37 is that HA is arranged in the IPv4 network, CN is positioned at IPv6 network, the renewal flow chart of MN when the IPv4 network is mobile.

According to RFC3344, after being moved, MN can obtain new Care-of Address in the IPv4 network, and MNv4 need upgrade the home address that HAv4 keeps and the binding of Care-of Address.In addition, though CNv6 and MIP-ALG are keeping the binding of the home address and the Care-of Address of IPv6 form: HoAv6 ^*

CoAv6 ^*, still, CoAv6 ^*96 IPv6 address prefixs by CoAv4 and NAT-PT are formed, and in communication process, data message is according to CoAv6 ^*In 96 IPv6 address prefixs of NAT-PT be routed to MIPv4/v6-TG, therefore CoAv4, needn't upgrade the address binding that CNv6 and MIP-ALG keep in fact and cut little ice.Concrete step of updating comprises:

(1) MNv4 produces and sends login request message to HAv4, and its source address is CoAv4, and destination address is HAAv4, and load comprises HoAv4.

(2) after HAv4 receives login request message, upgrade the home address oneself kept and the binding of Care-of Address, reply registration reply message to MNv4 then.

Figure 38 is that HA is arranged in the address configuration schematic diagram that IPv4 network, CN are positioned at IPv6 network, MN MIPv4/v6-TG when the IPv6 network is mobile.

According to RFC3775, direct communication between MNv6 and the CNv6.But HAv4 must keep the home address of IPv4 form and the binding HoAv4 of Care-of Address CoAv4#, so that grasp the residing particular location of MNv6, therefore, the NAT-PT among the MIPv4/v6-TG need keep CoAv4#

The map addresses of CoAv6.

Figure 39 is that HA is arranged in the IPv4 network, CN is positioned at IPv6 network, the communication flow diagram of MN when the IPv6 network is mobile.Concrete communication steps comprises:

(1) according to the described MIPv6 technology of RFC3775, MNv6 is to the data message of CNv6 transmission IPv6 form, and the source address of data message is CoAv6, and destination address is CNAv6, deposits HoAv6 in the home address option in the destination option extension head of data message ^*

(2) according to the described MIPv6 technology of RFC3775, CNv6 is to the data message of MNv6 transmission IPv6 form, and the source address of data message is CNAv6, and destination address is CoAv6, and the second class route of data message is deposited HoAv6 in front ^*

Figure 40 is that HA is arranged in the IPv4 network, CN is positioned at IPv6 network, the renewal flow chart of MN when the IPv6 network is mobile.

After MN moves in the IPv6 network and obtains new Care-of Address, in order to keep normal communication, the home address that needs renewal HAv4 and CNv6 keep and the binding of Care-of Address.When upgrading, MIPv4/v6-TG serves as HAv6 in IPv6 network one side, carry out the renewal of home address and Care-of Address with MNv6 and CNv6 according to RFC3775, then serve as MNv4, carry out the renewal of home address and Care-of Address according to RFC3344 with HAv4 in IPv4 network one side.Concrete step of updating is as follows:

(1) MNv6 produces binding update messages.The source address of binding update messages is CoAv6, and destination address is HAAv6 ^*, load comprises HoAv6 ^*According to destination address, this binding update messages mails to MIPv4/v6-TG.

(2) MIP-ALG among the MIPv4/v6-TG converts the binding update messages that receives to login request message.The source address of login request message is CoAv4#, and destination address is HAAv4, and load comprises HoAv4.According to destination address, this login request message mails to HAv4.

(3) HAv4 upgrades the binding of home address and Care-of Address according to the login request message that receives, and produces registration reply message.The source address of registration reply message is HAAv4, and destination address is CoAv4#, and load comprises HoAv4.According to destination address, this registration reply message mails to MIPv4/v6-TG.

(4) after MIPv4/v6-TG receives registration reply message, NAT-PT scheduler mapping: CoAv4#

CoAv6, MIP-ALG becomes binding acknowledgement message to this registration reply message conversion.The source address of binding acknowledgement message is HAAv6 ^*, destination address is CoAv6, load comprises HoAv6 ^*According to destination address, this binding acknowledgement message mails to MNv6.MNv6 receives binding acknowledgement message, finishes the home address that HAv4 is kept and the Binding Update of Care-of Address.

(5), before CNv6 initiates Binding Update, carry out the RRP authentication at MNv6 according to RFC3775.In this process, MIPv4/v6-TG will serve as HAv6.The RRP authentication is carried out according to the described flow process of RFC37755, concrete step is as follows: MNv6 sends HomeTest Init message and Care-of Test Init message to MIPv4/v6-TG at first simultaneously, wherein Home Test Init message need and then be transmitted to CNv6 through MIPv4/v6-TG, and Care-of Test Init message directly sends to CNv6; CNv6 replys Home Test message and Care-of Test message respectively after receiving Home Test Init message and Care-of Test Init message, and Home Test message and Care-of Test message are returned according to former road.

(6) after the RRP authentication finished, according to RFC3775, MNv6 produced and sends binding update messages, and the source address of binding update messages is CoAv6, and destination address is CNAv6, and load comprises HoAv6 ^*, according to destination address, this binding update messages mails to CNv6.

(7) after CNv6 receives binding update messages, upgrade the home address and the binding of Care-of Address: the HoAv6 that oneself keep ^*

CoAv6.Then, CNv6 produces binding acknowledgement message and replys MNv6.

Figure 41 is that HA is positioned at IPv4 network, CN and is positioned at IPv6 network, the MN renewal flow chart when the IPv4 network moves to the IPv6 network.

As shown in figure 41, this moment, renewal process mainly contained two tasks, and the one, realize the home address that HAv4 and CNv6 keep and the Binding Update of Care-of Address; The 2nd, find MIPv4/v6-TG and MIPv4/v6-TG is carried out address configuration by the mode of inquiry of the domain name.In this renewal process, in IPv6 network one side, MIPv4/v6-TG serves as HAv6, three entities when constituting MIPv6 and upgrade with CNv6 and MNv6, and the home address of CNv6 being kept according to the described MIPv6 technology of RFC3775 and the binding of Care-of Address are upgraded; In IPv4 network one side, MIPv4/v6-TG serves as MNv4, carries out the renewal of home address and Care-of Address according to RFC3344 with HAv4.Concrete step of updating comprises:

(2) MNv6 obtains the address CNAv6 of the IPv6 form of CNv6 by the mode of inquiry of the domain name.

(3) MNv6 sends binding update messages, and source address is CoAv6, and destination address is HAAv6 ^*, load comprises HoAv6 ^*, HoAv6 ^*96 IPv6 address prefixs that added NAT-PT by HoAv4 constitute.According to destination address, this binding update messages will be addressed to MIPv4/v6-TG.

(4) after MIPv4/v6-TG received binding update messages, NAT-PT set up map addresses: CoAv4# CoAv6, then, MIP-ALG converts binding update messages to login request message, and its source address is CoAv4#, and destination address is HAAv4, and load comprises HoAv4, according to destination address, this login request message mails to HAv4.

(5) after HAv4 receives login request message, upgrade the binding of home address and Care-of Address, and produce registration reply message, its source address is HAAv4, and destination address is CoAv4#, and load comprises HoAv4.According to destination address, this registration reply message mails to MIPv4/v6-TG.

(6) after MIPv4/v6-TG received login request message, MIP-ALG became binding acknowledgement message to this registration reply message conversion, and the source address of binding acknowledgement message is HAAv6 ^*, destination address is CoAv6, load HoAv6 ^*According to destination address, this binding acknowledgement message mails to MNv6.MNv6 receives binding acknowledgement message, finishes the renewal of the binding of home address that HAv4 is kept and Care-of Address.

(7), before CNv6 initiates Binding Update, carry out the RRP authentication at MNv6 according to RFC3775.In this process, MIPv4/v6-TG will serve as HAv6.The RRP authentication is carried out according to the described flow process of RFC37755, concrete step is as follows: MNv6 sends HomeTest Init message and Care-of Test Init message to MIPv4/v6-TG at first simultaneously, wherein Home Test Init message need and then be transmitted to CNv6 through MIPv4/v6-TG, and Care-of Test Init message directly sends to CNv6; CNv6 replys Home Test message and Care-of Test message respectively after receiving Home Test Init message and Care-of Test Init message, and Home Test message and Care-of Test message are returned according to former road.

(8) after the RRP authentication finished, according to RFC3775, MNv6 produced and sends binding update messages, and the source address of binding update messages is CoAv6, and destination address is CNAv6, and load comprises HoAv6 ^*, according to destination address, this binding update messages mails to CNv6.

(9) after CNv6 receives binding update messages, upgrade the address binding of oneself keeping: HoAv6*

CoAv6.Then, CNv6 produces binding acknowledgement message and replys MNv6.

Figure 42 is that diagram HA is positioned at IPv4 network, CN and is positioned at IPv6 network, the MN renewal flow chart when the IPv6 network moves to the IPv4 network.

As shown in figure 42, this moment, renewal process mainly contained two tasks, and the one, realize the home address that HAv4 and CNv6 keep and the Binding Update of Care-of Address; The 2nd, find MIPv4/v6-TG and MIPv4/v6-TG is carried out address configuration by the mode of inquiry of the domain name.In renewal process, because this moment, MN was in the IPv4 network, according to RFC3344, MN only need upgrade the binding that HAv4 keeps, but when MN moves to new Care-of Address of IPv4 network acquisition from the IPv6 network after, CNv6 still keeps original address binding, and therefore, the address binding that CNv6 keeps needs to upgrade.But problem is that according to RFC3344, MN does not initiate the renewal to CN.The solution that the present invention proposes has been expanded the function of MN, makes MN can ask the renewal of MIPv4/v6-TG agency oneself initiation to CNv6.In order to reach this purpose, introduced two message of proxy requests and proxy response, simultaneously for as far as possible with the RFC3344 compatibility, the form of the form of proxy requests/proxy response message and register requirement/registration reply message is consistent.In addition in order to distinguish message, for Agent Solicitation and proxy response message definition types value.Concrete step of updating comprises:

(1) MNv4 produces and sends login request message to HAv4, and its source address is CoAv4, and destination address is HAAv4, and load comprises HoAv4.According to destination address, this login request message mails to HAv4.

(3) MNv6 finds MIPv4/v6-TG by the mode of inquiry of the domain name, and obtains the address CNAv4# of the IPv4 form of CNv6.In the process of this inquiry of the domain name, the NAT-PT among the MIPv4/v6-TG has set up map addresses: CNAv4#

CNAv6.

(4) MNv4 sends Agent Solicitation to MIPv4/v6-TG, and the source address of Agent Solicitation is CoAv4, and destination address is CNAv4#, and load comprises HoAv4.According to destination address, Agent Solicitation mails to MIPv4/v6-TG.The types value of definition Agent Solicitation is 7 among the present invention, and the form of Agent Solicitation is shown in Figure 43 A.

(5) after MIPv4/v6-TG receives Agent Solicitation, will act on behalf of MNv4 and initiate renewal process to CNv6.According to RFC3775, before initiating to upgrade, carry out the RRP authentication to CNv6.The RRP authentication is carried out according to the described flow process of RFC37755, and concrete step is as follows: MIPv4/v6-TG serves as HAv6 in IPv6 network one side, sends Home Test Init message to CNv6.Home Test Init message source address is HoAv6 ^*, destination address is CNAv6.CNv6 receives Home Test Init message, can respond Home Test message to MIPv4/v6-TG.Simultaneously, MIPv4/v6-TG serves as MNv6, sends Care of Test Init message to CNv6.Care of Test Init message source address is CoAv6 ^*, destination address is CNAv6.CNv6 receives Care of Test Init message, can respond Care of Test message to MIPv4/v6-TG.

(6) after the RRP authentication finished, MIPv4/v6-TG served as MNv6 and produces binding update messages according to RFC3775, and the source address of binding update messages is CoAv6 ^*, destination address is CNAv6, load comprises HoAv6 ^*, according to destination address, this binding update messages mails to CNv6.

(7) after CNv6 receives binding update messages, upgrade the address binding of oneself keeping: HoAv6 ^*

CoAv6 ^*Then, CNv6 produces binding acknowledgement message and replys MIPv4/v6-TG.

(8) after MIPv4/v6-TG received binding acknowledgement message, at first, MIP-ALG set up address binding: HoAv6 ^*

CoAv6 ^*Then, MIPv4/v6-TG sends proxy response message to MNv4.The source address of proxy response message is CNAv4#, and destination address is CoAv4, and load comprises HoAv4.The types value of definition proxy response message is 8 among the present invention, and the form of proxy response message is shown in Figure 43 B.

The present invention has realized mobile communication in the IPv4/v6 hybrid network by MIPv4/v6-TG is set between IPv4 network and IPv6 network, simultaneously also realized the transparent mutually of RFC3334 and RFC3775, can satisfy network from the demand of IPv4 to the IPv6 transition period; And the present invention only need carry out certain upgrading to mobile node, and home agent and communication node be need not to improve, so the present invention can make full use of existing mobile communication equipment, has great practical value.

Claims

1. realize the communication means of mobile node in the IPv4/v6 hybrid network for one kind, it is characterized in that: by the mobile communication in mobile IPv 4/v6 transfer gateway realization IPv4/v6 hybrid network is set between IPv4 network and IPv6 network, described mobile IPv 4/v6 transfer gateway comprises the NAT-PT gateway and establishes thereon mobile IP ALG, wherein dispose DNS-ALG on the NAT-PT gateway, concrete steps are:

A. mobile IPv 4/v6 transfer gateway is by serving as RFC3344 and the described different entity of RFC3775 respectively in IPv4 network and IPv6 network, and realizes that by the conversion of carrying out at intra-gateway between the entity RFC3344 and RFC3775's is transparent mutually;

B. mobile IPv 4/v6 transfer gateway is responsible for changing send to various message and data message the IPv6 network, relevant with mobile IP from the IPv4 network, is responsible for changing send to various message and data message the IPv4 network, relevant with mobile IP from the IPv6 network;

C. mobile IPv 4/v6 transfer gateway is intercepted and captured message and the data message relevant with mobile IP according to following principle: when upgrading, intercept and capture message according to the type of message; When communication, according to the destination address intercepted data message of data message;

D. mobile IPv 4/v6 transfer gateway security mechanism of when the message of process IP v4 form and data message, adopting RFC3344 to provide, the security mechanism that when the message of process IP v6 form and data message, adopts RFC3775 to provide;

E. the requirement of describing among the requirement of home agent and communication node and RFC3344 and the RFC3775 is consistent, but increases requirement, specifically comprise mobile node:

(1) mobile node can satisfy the requirement of RFC3344 and the described relevant mobile node of RFC3775 simultaneously;

(2) mobile node can write down the domain name of home agent and communication node, can find mobile IPv 4/v6 transfer gateway by the mode of DNS inquiry, and obtain the address of home agent and communication node;

(3) mobile node can be supported the expansion to login request message and registration reply message, can produce and handle Agent Solicitation and proxy response message.

2. the communication means of mobile node according to claim 1 in the IPv4/v6 hybrid network, it is characterized in that: described steps A specifically comprises:

(1) mobile IPv 4/v6 transfer gateway serves as a described entity of RFC3344 in IPv4 network one side, this entity constitutes the described mobile IP model of RFC3344 with other entity that is in the IPv4 network, and this moves IP model and communicates according to the mobile IPv 4 agreement described in the RFC3344 and upgrade;

(2) mobile IPv 4/v6 transfer gateway serves as a described entity of RFC3775 in IPv6 network one side, this entity constitutes the described mobile IP model of RFC3775 with other entity that is in the IPv6 network, and this moves IP model and communicates according to the mobile IPv 6 protocol described in the RFC3775 and upgrade;

(3) mobile IPv 4/v6 transfer gateway is realized the conversion of own entity from an IPv4 form to the entity of an IPv6 form by the internal conversion between the entity, from the conversion of the entity of an IPv6 form to the entity of an IPv4 form, and realize conversion between the similar entity, thereby realize that finally RFC3344 and RFC3775's is transparent mutually.

3. the communication means of mobile node according to claim 1 in the IPv4/v6 hybrid network, it is characterized in that: described step B specifically comprises:

(1) mobile IPv 4/v6 transfer gateway is responsible for the described login request message of a RFC3344 and is converted the described binding update messages of RFC3775 to, and the described registration reply message conversion of RFC3344 is become the described binding acknowledgement message of RFC3775;

(2) mobile IPv 4/v6 transfer gateway is responsible for the described binding update messages of a RFC3775 and is converted the described login request message of RFC3344 to, and the described binding acknowledgement message conversion of RFC3775 is become the described registration reply message of RFC3344;

(3) mobile IPv 4/v6 transfer gateway is responsible for the data message is carried out the address protocol conversion, and when IPv6 network one side transceive data message, according to the described requirement of RFC3775, Care-of Address in the data message IP head of IPv6 form and the home address in the extension header are exchanged.

4. the communication means of mobile node according to claim 1 in the IPv4/v6 hybrid network, it is characterized in that: described step C specifically comprises:

(1) when communication, mobile IPv 4/v6 transfer gateway serves as different entities according to different signal intelligences, owing to can be routed to mobile IPv 4/v6 transfer gateway as the data message of destination address with the IP address of these entities, therefore, will to intercept and capture the IP address with these entities be the data message of destination address to mobile IPv 4/v6 transfer gateway;

(2) when upgrading, mobile IPv 4/v6 transfer gateway is intercepted and captured message according to the type of message, and this method further specifically comprises:

(21) at the IPv4 network, the message that mobile IPv 4/the v6 transfer gateway need be handled has the described login request message of RFC3344 and registration reply message and Agent Solicitation and proxy response message, to these four kinds of message, mobile IPv 4/v6 transfer gateway is intercepted and captured according to the UDP encapsulation and the destination slogan of message in network layer, distinguishes according to the loadtype value of message in application layer; (22) at the IPv6 network, the message that mobile IPv 4/the v6 transfer gateway need be handled has the described binding update messages of RFC3775, binding acknowledgement message, Home Test Init message, Home Test message, Care ofTest Init message, Care ofTest message; To these message, mobile IPv 4/v6 transfer gateway is numbered 135 in network layer according to the mobile prolate-headed next header of message and as a token of intercepts and captures message, application layer according to load in the MH value distinguish message.

5. the communication means of mobile node according to claim 1 in the IPv4/v6 hybrid network, it is characterized in that: described step D specifically comprises:

(1) when mobile IPv 4/v6 transfer gateway receives message or data message, will be IPv4 form or IPv6 form, authenticate according to RFC3344 or the described identifying algorithm of RFC3775 according to this message or data message;

(2) when mobile IPv 4/v6 transfer gateway sends message or data message, to be IPv4 form or IPv6 form according to this message or data message, produce verify data according to RFC3344 or the described identifying algorithm of RFC3775, this verify data will be as the part of this message or data message.

6. the communication means of mobile node according to claim 5 in the IPv4/v6 hybrid network, it is characterized in that: home agent is positioned at the IPv4 network, communication node is positioned at the IPv6 network, and the committed step of mobile node mobile IPv 4/v6 when mobile in the IPv4/v6 hybrid network comprises:

(1) when mobile node when the IPv6 network moves to the IPv4 network, mobile node sends Agent Solicitation to mobile IPv 4/v6 transfer gateway, and the request mobile IPv 4/communication node of v6 transfer gateway proxy mobile node in being in the IPv6 network initiated the Binding Update of its home address and Care-of Address;

(2) after mobile IPv 4/the v6 transfer gateway is received Agent Solicitation, the communication node of proxy mobile node in being in the IPv6 network initiated renewal process, this moment, mobile IPv 4/v6 transfer gateway will serve as the home agent of IPv6 form and the mobile node of IPv6 form respectively in IPv6 network one side, after mobile IPv 4/v6 transfer gateway was received binding acknowledgement message, the mobile node in being in the IPv4 network sent proxy response message;

(3) form of the login request message among the form of described Agent Solicitation and the RFC3344 is identical, the form of the registration reply message among the form of proxy response message and the RFC3344 is identical, wherein the types value of proxy requests is 7 by fixing tentatively, and the types value of proxy response message is 8 by fixing tentatively.