CN101977246B - Method and system for supporting PMIPv6 (Proxy Mobile IPv6) mobility - Google Patents
Method and system for supporting PMIPv6 (Proxy Mobile IPv6) mobility Download PDFInfo
- Publication number
- CN101977246B CN101977246B CN201010277519.6A CN201010277519A CN101977246B CN 101977246 B CN101977246 B CN 101977246B CN 201010277519 A CN201010277519 A CN 201010277519A CN 101977246 B CN101977246 B CN 101977246B
- Authority
- CN
- China
- Prior art keywords
- ipv4
- publicly
- mag
- message
- home address
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Abstract
The invention discloses a method for supporting PMIPv6 (Proxy Mobile IPv6) mobility, which comprises the following steps of: sending a proxy binding update (PBU) message by a mobile access gateway (MAG) when a mobile node (MN) supporting IPv4 is moved into a PMIPv6 domain of a network address translation scene; receiving the PBU message by a local mobile anchor (LMA), and adding or updating an IPv4 network address translation port number and a public IPv4 home address in binding update items of the MN; adding and updating the IPv4 network address translation port number and the public IPv4 home address by the MAG in a binding update list of the MN; and forwarding the message by the MAG and the LMA according to the public IPv4 home address and the Pv4 network address translation port number. Meanwhile, the invention discloses a system for supporting PMIPv6 mobility. According to the scheme of the invention, the support of PMIPv6 to IPv4 during network address translation can be met.
Description
Technical field
The present invention relates to network transmission technology, relate in particular to the ambulant support method and system of a kind of proxy mobile IPv 6 (PMIPv6).
Background technology
IPv4 is a long-term process to the transition of IPv6, and in this transient process, IPv6 and IPv4 agreement all will be used in identical network configuration.Therefore, mobile node (MN in PMIPv6 territory, MobileNode) may under IPv4-only, IPv6-only or two mode stack, operate, and Mobile Access Gateway (MAG, Mobile Access Gateway) network and between local mobile anchor (LMA, Local MobilityAnchor) may be the network of an IPv4 or IPv6.Like this, need in PMIPv6 territory, provide ambulant support by the MN for IPv4-only, IPv6-only or two mode stacks.
Being briefly described as follows of draft-ietf-netlmm-pmip6-ipv4-support-18 (IPv4 Support for Proxy MobileIPv6) agreement: all mobility entity, LMA and MAG are two stacks, and the type mobility signaling of transmission network is all based on IPv6 arbitrarily.
According to the description of draft-ietf-netlmm-pmip6-ipv4-support-18 agreement, the support method of PMIPv6 to IPv4, as shown in Figure 1, this support method comprises following step:
Step 101: when the MN of support IPv4 moves in PMIPv6 territory, MAG obtains the IP protocol version type of described MN;
Concrete, in the time of in the MN that supports IPv4 moves to PMIPv6 territory, MAG obtains the IP protocol version type of MN from the strategy file (policy profile) of MN, and as IPv4 or IPv6, the IP protocol version type of MN described in this method is IPv4.
Step 102:MAG is IPv4 according to the IP protocol version type of MN, sends the agent binding update messages that carries IPv4 home address request option;
Concrete, MAG is IPv4 according to the IP protocol version type of MN, in agent binding update (PBU, the Proxy Binding Update) message sending to LMA, carry full 0 or comprise the IPv4 home address request option (IPv4Home Address RequestOption) from the IPv4 home address distributing as MN.
Step 103:LMA receives after PBU message, according to the IPv4 home address request option in PBU message, generate or renewed treaty IPv4 home address, at the agent binding returning to MAG, confirm (PBA, ProxyBinding Acknowledgement), in, carry the IPv4 home address that generates or renew a contract;
Concrete, LMA receives after PBU message, when the IPv4 home address in the IPv4 of PBU message Home Address RequestOption is full 0, generates IPv4 home address, and add in the corresponding banding cache entry of MN (BCE, Banding Cache Entry); While having MAG to be the IPv4 home address of MN distribution in the IPv4 of PBU message HomeAddress Request Option, LMA judges that by DHCP Server associated with self or that coexist whether described original IPv4 home address is occupied, do not having when occupied, the BCE that upgrades MN, renews a contract to original IPv4 home address in described BCE; When taking, generate IPv4 home address, and add in the corresponding BCE of MN; In the PBA message of returning to MAG, by IPv4 home address, reply option (IPv4 Home Address ReplyOption) and carry the IPv4 home address of described generation or renewed treaty;
This step also comprises, and: LMA receives after PBU message, according to the MN indicating in PBU message, searches corresponding BCE, when not finding, creates the BCE of described MN;
In this step, described generation IPv4 home address is generally: LMA arranges agreement (DHCP, Dynamic Host Configuration Protocol) server (Server) distributing IP v4 home address by DynamicHost associated with self or that coexist; Described IPv4 home address comprises subnet mask;
Described draft-ietf-netlmm-pmip6-ipv4-support-18 agreement is than PMIPv6, in the BCE of MN, increased MN IPv4 home address, be dispensed to the IPv4 default router address of MN.
Step 104:MAG receives after the PBA that comes from LMA, adds the IPv4 home address that PBA carries in the Binding Update list of entries (BUL, Banding Update List Entry) of MN;
Concrete, MAG receives after the PBA that comes from LMA, in the BUL of MN, add the IPv4 home address that PBA carries by IPv4 Home Address Reply Option, and obtain by the IPv4 Default-Router Address Option in PBA the IPv4 default router address of distributing to MN.
Step 105:MN obtains the IPv4 home address of distribution from MAG by dhcp process.
After above-mentioned steps completes, when LMA E-Packets to MN:
IPv6 header(src＝LMAA，dst＝Proxy-CoA)/*Tunnel Header*/
IPv4 header(src＝CN，dst＝IPv4-MN-HOA)/*Packet Header*/
Upper layer protocols /*Packet Content*/
LMA forwards while coming from the message of MN:
IPv6 header(src＝Proxy-CoA，dst＝LMAA)/*Tunnel Header*/
IPv4 header(src＝IPv4-MN-HOA，dst＝CN)/*Packet Header*/
Upper layer protocols /*Packet Content*/
Wherein, src represents source address; Dst represents destination address; Proxy-CoA represents MAG address; IPv4-MN-HOA represents MN address; LMAA represents LMA address; CN represents the address of peer node (CN).
When said method has solved and has not had network address translation (NAT) between MAG and LMA, in PMIPv6 territory for the support of IPv4.
At present, according to draft-koodli-ipv6-in-mobile-networks-00 (Mobile NetworksConsiderations for IPv6 Deployment) agreement, come from the mobile Internet access of smart mobile phone and other mobile terminal, accelerating exhausting of IPv4 address, can not be unique public network IP v4 address of all mobile terminal configuration.The use of considering private network IPv4 address can postpone the exhaustion of public network IP v4 address, in real network is disposed, can be at related network entity deploy NAT, for mobile terminal distributes private net address, alleviate exhausting of public network IP v4 address, for example, in the scheme of mobile Internet, subscriber terminal equipment interface IP address is all the private net address that distributes 10.*.*.*.
Yet, while there is NAT between MAG and LMA, in prior art, also there is no a kind of PMIPv6 that can solve for the scheme of the support of IPv4, so need to propose a kind of scheme, solve the ambulant support in this scene.
Summary of the invention
In view of this, main purpose of the present invention is to provide the ambulant support method and system of a kind of PMIPv6, can solve while there is NAT between MAG and LMA, and PMIPv6 is for the support of IPv4.
For achieving the above object, technical scheme of the present invention is achieved in that
The ambulant support method of a kind of PMIPv6 provided by the invention, the method comprises:
While supporting that the MN of IPv4 moves in the PMIPv6 territory of NAT scene, MAG sends PBU message to LMA, and described PBU message is carried IPv4 network address conversion port number and the request of publicly-owned IPv4 home address;
LMA receives after PBU message, adds or upgrades IPv4 network address conversion port number and publicly-owned IPv4 home address, and to MAG, return to described publicly-owned IPv4 home address by PBA message according to described PBU message in the BCE of MN;
MAG adds or upgrades IPv4 network address conversion port number and publicly-owned IPv4 home address in the BUL of MN;
When message repeating, MAG and LMA carry out message repeating according to publicly-owned IPv4 home address and IPv4 network address conversion port number.
In such scheme, described MAG sends PBU message to LMA, for: MAG carries full 0 or comprises the publicly-owned IPv4 home address request option from the publicly-owned IPv4 home address distributing as MN in the PBU message sending to LMA, and in PBU message, carries the IPv4 network switch port numbers option that comprises IPv4 network switch port numbers.
In such scheme, describedly by PBA message, to MAG, return to described publicly-owned IPv4 home address, for: in the PBA message of returning to MAG, by publicly-owned IPv4 home address, reply option and carry described publicly-owned IPv4 home address.
In such scheme, during publicly-owned IPv4 home address request option that to carry publicly-owned IPv4 home address in described PBU message be full 0, the method further comprises: LMA receives after PBU message, generates publicly-owned IPv4 home address;
Be the publicly-owned IPv4 of described generation local: LMA distributes publicly-owned IPv4 home address by DHCP Server associated with self or that coexist; Described publicly-owned IPv4 home address comprises subnet mask.
In such scheme, the method further comprises: MN, by DHCP or PMIPv6 registration process, obtains private ip v4 address and the port numbers of self from LMA.
In such scheme, described MAG and LMA carry out message repeating according to publicly-owned IPv4 home address and IPv4 network address conversion port number, for:
When MN sends message to CN, MAG receives that after the message of MN transmission, the NAT coexisting with MAG replaces with publicly-owned IPv4 home address by the source address in heading, and changes source port number into IPv4 network address conversion port number; Then, MAG encapsulates amended heading, and is sent to LMA by the bidirectional tunnel between MAG and LMA; LMA receives after message that decapsulation heading forwards the packet to CN according to destination address;
When CN sends message to MN, LMA receives after the message of CN transmission, according to publicly-owned IPv4 home address, IPv4 network address conversion port number, searches corresponding MN in BCE, and message is sent to MAG by corresponding MAG-LMA tunnel; MAG receives after described message, and the NAT coexisting with MAG is converted to the IPv4 network address conversion port number in the publicly-owned IPv4 home address in the destination address of heading and destination slogan private address and the port numbers of the IPv4 of MN, is sent to MN.
The ambulant back-up system of a kind of PMIPv6 provided by the invention, this system comprises: MAG, LMA; Wherein,
MAG, while moving to the PMIPv6 territory of NAT scene for the MN supporting IPv4, sends PBU message to LMA, and described PBU message is carried IPv4 network address conversion port number and the request of publicly-owned IPv4 home address; And according to PBA message, in the BUL of MN, add or upgrade IPv4 network address conversion port number and publicly-owned IPv4 home address; When message repeating, according to publicly-owned IPv4 home address and IPv4 network address conversion port number, carry out message repeating with LMA;
LMA, for receiving after the PBU message of MAG, adds in the BCE of MN according to described PBU message or upgrades IPv4 network address conversion port number and publicly-owned IPv4 home address, and to MAG, returning to described publicly-owned IPv4 home address by PBA message; When message repeating, according to publicly-owned IPv4 home address and IPv4 network address conversion port number, carry out message repeating with MAG.
In such scheme, this system also comprises: MN, for by DHCP or PMIPv6 registration process, obtains private ip v4 address and the port numbers of self from LMA.
In such scheme, when message repeating, this system also comprises NAT, for the message that forwards MN at MAG during to LMA, according to publicly-owned IPv4 home address, the source address of heading is replaced with to publicly-owned IPv4 home address, and change source port number into IPv4 network address conversion port number; When MAG receives the message of the CN that LMA forwards, the IPv4 network address conversion port number in the publicly-owned IPv4 home address in the destination address of heading and destination slogan is converted to private address and the port numbers of the IPv4 of MN.
The ambulant support method and system of a kind of PMIPv6 provided by the invention, while supporting that the MN of IPv4 moves in the PMIPv6 territory of NAT scene, MAG sends PBU message to LMA, and described PBU message is carried IPv4 network address conversion port number and the request of publicly-owned IPv4 home address; LMA receives after PBU message, adds or upgrades IPv4 network address conversion port number and publicly-owned IPv4 home address, and return to described publicly-owned IPv4 home address to MAG in the BCE of MN; MAG adds or upgrades IPv4 network address conversion port number and publicly-owned IPv4 home address in the BUL of MN; When message repeating, MAG and LMA carry out message repeating according to publicly-owned IPv4 home address and IPv4 network address conversion port number; So, can solve while there is NAT between MAG and LMA, PMIPv6, for the support of IPv4, is suitable for IPv4 to the transition of IPv6.
Accompanying drawing explanation
Fig. 1 is while there is not NAT between MAG and LMA in prior art, the support method of PMIPv6 to IPv4;
Fig. 2 is the schematic flow sheet that the present invention realizes a kind of ambulant support method of PMIPv6;
Fig. 3 is the form schematic diagram of IPv4 NAT Home Address Request Option of the present invention;
Fig. 4 is the form schematic diagram of IPv4 NAT Port Option of the present invention;
Fig. 5 is the form schematic diagram of IPv4 NAT Home Address Reply Option of the present invention;
Fig. 6 is the schematic diagram of MN of the present invention message format while sending message to CN;
Fig. 7 is the schematic diagram of CN of the present invention message format while sending message to MN;
Fig. 8 is the structural representation that the present invention realizes the ambulant back-up system of a kind of PMIPv6.
Embodiment
Basic thought of the present invention is: while supporting that the MN of IPv4 moves in the PMIPv6 territory of NAT scene, MAG sends PBU message to LMA, and described PBU message is carried IPv4 network address conversion port number and the request of publicly-owned IPv4 home address; LMA receives after PBU message, adds or upgrades IPv4 network address conversion port number and publicly-owned IPv4 home address, and return to described publicly-owned IPv4 home address to MAG according to described PBU message in the BCE of MN; MAG adds or upgrades IPv4 network address conversion port number and publicly-owned IPv4 home address in the BUL of MN; When message repeating, MAG and LMA carry out message repeating according to publicly-owned IPv4 home address and IPv4 network address conversion port number.
The present invention realizes a kind of ambulant support method of PMIPv6, and as shown in Figure 2, the method comprises following step:
Step 201: while supporting that the MN of IPv4 moves in the PMIPv6 territory of NAT scene, the IP protocol version type that MAG obtains described MN is IPv4;
Concrete, when the MN that supports IPv4 moves in the PMIPv6 territory of NAT scene, the IP protocol version type that MAG obtains MN from the strategy file (policy profile) of MN is IPv4;
To be that in PMIPv6 territory, MAG and NAT are common exist on an entity in the PMIPv6 territory of described NAT scene.
Step 202:MAG is IPv4 according to the IP protocol version type of MN, to LMA, sends PBU message, and described PBU message is carried IPv4 network address conversion port number and the request of publicly-owned IPv4 home address;
Concrete, MAG is IPv4 according to the IP protocol version type of MN, in the PBU message sending to LMA, carry full 0 or comprise the publicly-owned IPv4 home address request option (IPv4 NAT Home Address Request Option) from the publicly-owned IPv4 home address distributing as MN, and in PBU message, carrying the IPv4 NAT Port Option that comprises IPv4 network switch port numbers;
Described IPv4 network switch port numbers is that MN distributes by MAG;
The form of described IPv4 NAT Home Address Request Option as shown in Figure 3, comprise: data type (Type), data length (Length), prefix length (Prefix-len), flag (N), reserved place (Reserved), publicly-owned IPv4 home address field (IPv4 NAT Home Address), wherein flag N is 1 o'clock, represent that MAG is a publicly-owned IPv4 home address of MN request, IPv4 NAT HomeAddress field is full 0 or is concrete publicly-owned IPv4 home address;
The form of described IPv4 NAT Port Option as shown in Figure 4, comprise: data type (Type), data length (Length), flag (F), reserved place (Reserved), IPv4 network switch port number field (IPv4 Port), wherein flag F is 1 o'clock, represent that it is the IPv4 network switch port numbers that MN distributes that this message is carried MAG, IPv4 Port field is concrete IPv4 network switch port numbers.
Step 203:LMA receives after PBU message, the IPv4 network address conversion port carrying according to described PBU message number and the request of publicly-owned IPv4 home address, in the BCE of MN, add or upgrade IPv4 network address conversion port number and publicly-owned IPv4 home address, and to MAG, returning to described publicly-owned IPv4 home address by PBA message;
Concrete, LMA receives after PBU message, when the publicly-owned IPv4 home address of IPv4 NAT Home AddressRequest Option is full 0 in PBU message, generates publicly-owned IPv4 home address, and adds in the corresponding BCE of MN; While having MAG to be the publicly-owned IPv4 home address of MN distribution in the IPv4 of PBU message NAT Home Address Request Option, LMA is updated to described publicly-owned IPv4 home address in the BCE of MN; In the PBA message of returning to MAG, by publicly-owned IPv4 home address, reply option (IPv4 NAT Home Address Reply Option) and carry described publicly-owned IPv4 home address; And it is the IPv4 network address conversion port number that MN distributes that LMA obtains MAG in PBU message, in the corresponding BCE of MN, add or renewal IPv4 network address conversion port number;
The form of described IPv4 NAT Home Address Reply Option as shown in Figure 5, comprise: data type (Type), data length (Length), mode bit (Status), prefix length (Prefix-len), reserved place (R), flag (N), publicly-owned IPv4 home address field (IPv4 Home Address), wherein N flag is 1 o'clock, represent to return to a publicly-owned IPv4 home address, IPv4 Home Address field is concrete publicly-owned IPv4 home address;
This step also comprises, and: LMA receives after PBU message, according to the MN indicating in PBU message, searches corresponding BCE, when not finding, creates the BCE of described MN; The described BCE that searches, can be to search BCE according to the method described in 5.4.1 in RFC5213, or to take publicly-owned IPv4 home address and the IPv4 network address conversion port number that MAG is that MN distributes be index search BCE;
In this step, the publicly-owned IPv4 home address of described generation generally: LMA distributes publicly-owned IPv4 home address by DHCP Server associated with self or that coexist; Described publicly-owned IPv4 home address comprises subnet mask;
Further, when LMA detects after the publicly-owned IPv4 home address lease expires distributing as MAG, the life span that is PBU message expires, and confirming not have MAG to continue to use after the publicly-owned IPv4 home address of this distribution, LMA can continue to distribute to by described publicly-owned IPv4 home address the MAG that the next one sends request by PBA message.
Step 204:MAG adds or upgrades publicly-owned IPv4 home address that PBA message carries and from the IPv4 network address conversion port number distributing as MN in the BUL of MN;
Further, when under MAG, registration has a plurality of MN, MAG can be in the BUL of each MN, the publicly-owned IPv4 home address that interpolation or renewal PBA message are carried, and by distributing different IPv4 network address conversion port number to distinguish each MN, like this, a plurality of MN under a MAG can share a publicly-owned IPv4 home address; When the product of the publicly-owned IPv4 home address distributing and IPv4 network address conversion port number arrives in limited time above, MAG is the publicly-owned IPv4 home address that the MN of the new access that can not distinguish please look for novelty.
Step 205:MN can obtain self private ip v4 address and port numbers by DHCP or PMIPv6 registration process from LMA;
Concrete, MN directly obtains private ip v4 address and port numbers from LMA or the DHCP Server associated with LMA by dhcp process;
Or MAG, by carry IPv4 Home Address Request option in PBU message, obtain private ip v4 address and the port numbers of distributing for MN, then by DHCP or other process, MN obtains described private ip v4 address and port numbers from LMA.
Step 206: when message repeating, MAG and LMA forward message according to publicly-owned IPv4 home address and IPv4 network address conversion port number;
For example, when MN sends message to CN, message format as shown in Figure 6, comprising:
IPv4 packet header source address (Src) of the message that MN sends is the IPv4 private address (MN IPv4 address) of MN, and destination address (Dst) is CN IPv4 address; MAG receives after the message of MN transmission, the NAT coexisting with MAG is according to the publicly-owned IPv4 home address (NAT home address) obtaining from PBA message, source address in heading is replaced with to publicly-owned IPv4 home address, and change source port number into IPv4 network address conversion port number (nat port); Then, MAG encapsulates amended heading, and is sent to LMA by the bidirectional tunnel between MAG and LMA; LMA receives after message that decapsulation heading forwards the packet to CN according to destination address;
When CN sends message to MN, message format as shown in Figure 7, comprising:
The IPv4 packet header source address of the message that CN sends is the private address of the IPv4 of CN, and destination address is publicly-owned IPv4 home address, and destination slogan is IPv4 network address conversion port number; LMA receives after the message of CN transmission, according to publicly-owned IPv4 home address, IPv4 network address conversion port number, searches corresponding MN in BCE, and message is sent to MAG by corresponding MAG-LMA tunnel; MAG receives after described message, decapsulation heading, the NAT coexisting with MAG is converted to private address and the port numbers of the IPv4 of MN by the IPv4 network address conversion port number in the publicly-owned IPv4 home address in the destination address of heading and destination slogan, and is sent to MN.
In order to realize said method, the present invention also provide a kind of in NAT the ambulant back-up system of PMIPv6, as shown in Figure 8, this system comprises: MAG 81, LMA 82; Wherein,
Described MAG 81 sends PBU message to LMA 82, be specially: MAG 81 carries full 0 or comprises the IPv4 NAT Home Address Request Option from the publicly-owned IPv4 home address distributing as MN in the PBU message sending to LMA 82, and in PBU message, carries the IPv4 NAT Port Option that comprises IPv4 network switch port numbers;
Described LMA 82 returns to described publicly-owned IPv4 home address by PBA message to MAG 81, is specially: LMA 82, in the PBA message of returning to MAG 81, carries described publicly-owned IPv4 home address by IPv4 NAT Home AddressReply Option;
Described system also comprises: MN 83, for by DHCP or PMIPv6 registration process, obtains private ip v4 address and the port numbers of self from LMA82.
When message repeating, this system also comprises NAT, described NAT and MAG 81 coexist, for the message that forwards MN 83 at MAG 81 during to LMA 82, according to the publicly-owned IPv4 home address obtaining from MAG 81, the source address of heading is replaced with to publicly-owned IPv4 home address, and change source port number into IPv4 network address conversion port number; When MAG 81 receives the message of the CN 84 that LMA 82 forwards, the IPv4 network address conversion port number in the publicly-owned IPv4 home address in the destination address of heading and destination slogan is converted to private address and the port numbers of the IPv4 of MN 83;
Further, when 81 times registrations of MAG have a plurality of MN 83, described MAG 81 also adds for the BUL at each MN 83 or upgrades the publicly-owned IPv4 home address that PBA message is carried, and by distributing different IPv4 network address conversion port number to distinguish each MN 83;
Further, when the product of the publicly-owned IPv4 home address distributing and IPv4 network address conversion port number reaches, prescribe a time limit, MAG 81 is the publicly-owned IPv4 home address that the MN 83 of the new access that can not distinguish please look for novelty;
Further, when LMA 82 detects after the publicly-owned IPv4 home address lease expires distributing as MAG, the life span that is PBU message expires, and confirming not have MAG to continue to use after the publicly-owned IPv4 home address of this distribution, LMA 82 can continue to distribute to by described publicly-owned IPv4 home address the MAG 81 that the next one sends request by PBA message.
By method of the present invention, while there is NAT between MAG and LMA, MAG asks publicly-owned IPv4 home address to LMA, and to LMA, send the IPv4 network address conversion port number of MN, like this, when carrying out the forwarding of private address message, can carry out message repeating according to the IPv4 network address conversion port of publicly-owned IPv4 home address and MN number, solve the support of PMIPv6 for IPv4, be suitable for IPv4 to the transition of IPv6.
The above, be only preferred embodiment of the present invention, is not intended to limit protection scope of the present invention, all any modifications of doing within the spirit and principles in the present invention, is equal to and replaces and improvement etc., within all should being included in protection scope of the present invention.
Claims (11)
1. the ambulant support method of proxy mobile IPv 6 PMIPv6, is characterized in that, the method comprises:
While supporting that the mobile node MN of IPv4 moves in the PMIPv6 territory of network address translation NAT scene, Mobile Access Gateway MAG sends agent binding update PBU message to local mobile anchor LMA, and described PBU message is carried IPv4 network address conversion port number and the request of publicly-owned IPv4 home address;
LMA receives after PBU message, according to described PBU message, in the banding cache entry BCE of MN, add or upgrade IPv4 network address conversion port number and publicly-owned IPv4 home address, and confirming that by agent binding PBA message returns to described publicly-owned IPv4 home address to MAG;
MAG adds or upgrades IPv4 network address conversion port number and publicly-owned IPv4 home address in the Binding Update list of entries BUL of MN;
When message repeating, MAG and LMA carry out message repeating according to publicly-owned IPv4 home address and IPv4 network address conversion port number.
2. support method according to claim 1, it is characterized in that, described MAG sends PBU message to LMA, for: MAG carries full 0 or comprises the publicly-owned IPv4 home address request option from the publicly-owned IPv4 home address distributing as MN in the PBU message sending to LMA, and in PBU message, carry the IPv4 network address conversion port option that comprises IPv4 network address conversion port number.
3. support method according to claim 2, it is characterized in that, describedly by PBA message, to MAG, return to described publicly-owned IPv4 home address, for: in the PBA message of returning to MAG, by publicly-owned IPv4 home address, reply option and carry described publicly-owned IPv4 home address.
4. according to the support method described in claim 2 or 3, it is characterized in that, during publicly-owned IPv4 home address request option that to carry publicly-owned IPv4 home address in described PBU message be full 0, the method further comprises: LMA receives after PBU message, generates publicly-owned IPv4 home address;
The publicly-owned IPv4 home address of described generation is: LMA arranges agreement (DHCP) server (Server) by DynamicHost associated with self or that coexist and distributes publicly-owned IPv4 home address; Described publicly-owned IPv4 home address comprises subnet mask.
5. support method according to claim 4, is characterized in that, the method further comprises: MN, by DHCP or PMIPv6 registration process, obtains private ip v4 address and the port numbers of self from LMA.
6. support method according to claim 5, is characterized in that, described MAG and LMA carry out message repeating according to publicly-owned IPv4 home address and IPv4 network address conversion port number, for:
When MN sends message to peer node (CN), MAG receives that after the message of MN transmission, the NAT coexisting with MAG replaces with publicly-owned IPv4 home address by the source address in heading, and changes source port number into IPv4 network address conversion port number; Then, MAG encapsulates amended heading, and is sent to LMA by the bidirectional tunnel between MAG and LMA; LMA receives after message that decapsulation heading forwards the packet to CN according to destination address;
When CN sends message to MN, LMA receives after the message of CN transmission, according to publicly-owned IPv4 home address, IPv4 network address conversion port number, searches corresponding MN in BCE, and message is sent to MAG by corresponding MAG-LMA tunnel; MAG receives after described message, and the NAT coexisting with MAG is converted to the IPv4 network address conversion port number in the publicly-owned IPv4 home address in the destination address of heading and destination slogan private address and the port numbers of the IPv4 of MN, is sent to MN.
7. the ambulant back-up system of proxy mobile IPv 6 PMIPv6, is characterized in that, this system comprises: Mobile Access Gateway MAG, local mobile anchor LMA; Wherein,
MAG, while moving to the PMIPv6 territory of network address translation NAT scene for the mobile node MN supporting IPv4, to LMA, send agent binding update PBU message, described PBU message is carried IPv4 network address conversion port number and the request of publicly-owned IPv4 home address; And confirm that according to agent binding PBA message adds or upgrade IPv4 network address conversion port number and publicly-owned IPv4 home address in the Binding Update list of entries BUL of MN; When message repeating, according to publicly-owned IPv4 home address and IPv4 network address conversion port number, carry out message repeating with LMA;
LMA, for receiving after the PBU message of MAG, according to described PBU message, in the banding cache entry BCE of MN, add or upgrade IPv4 network address conversion port number and publicly-owned IPv4 home address, and to MAG, returning to described publicly-owned IPv4 home address by PBA message; When message repeating, according to publicly-owned IPv4 home address and IPv4 network address conversion port number, carry out message repeating with MAG.
8. back-up system according to claim 7, it is characterized in that, described MAG sends PBU message to LMA, for: MAG carries full 0 or comprises the publicly-owned IPv4 home address request option from the publicly-owned IPv4 home address distributing as MN in the PBU message sending to LMA, and in PBU message, carry the IPv4 network address conversion port option that comprises IPv4 network address conversion port number.
9. back-up system according to claim 7, it is characterized in that, described LMA returns to described publicly-owned IPv4 home address by PBA message to MAG, for: LMA, in the PBA message of returning to MAG, replys option by publicly-owned IPv4 home address and carries described publicly-owned IPv4 home address.
10. back-up system according to claim 9, is characterized in that, this system also comprises: MN, for protocol DHCP or PMIPv6 registration process are set by DynamicHost, obtains private ip v4 address and the port numbers of self from LMA.
11. back-up systems according to claim 10, it is characterized in that, when message repeating, this system also comprises NAT, for the message that forwards MN at MAG during to LMA, according to publicly-owned IPv4 home address, the source address of heading is replaced with to publicly-owned IPv4 home address, and change source port number into IPv4 network address conversion port number; When MAG receives the message of the peer node CN that LMA forwards, the IPv4 network address conversion port number in the publicly-owned IPv4 home address in the destination address of heading and destination slogan is converted to private address and the port numbers of the IPv4 of MN.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010277519.6A CN101977246B (en) | 2010-09-07 | 2010-09-07 | Method and system for supporting PMIPv6 (Proxy Mobile IPv6) mobility |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010277519.6A CN101977246B (en) | 2010-09-07 | 2010-09-07 | Method and system for supporting PMIPv6 (Proxy Mobile IPv6) mobility |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101977246A CN101977246A (en) | 2011-02-16 |
| CN101977246B true CN101977246B (en) | 2014-03-12 |
Family
ID=43577089
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010277519.6A Expired - Fee Related CN101977246B (en) | 2010-09-07 | 2010-09-07 | Method and system for supporting PMIPv6 (Proxy Mobile IPv6) mobility |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101977246B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9749838B2 (en) | 2011-08-17 | 2017-08-29 | Telefonaktiebolaget Lm Ericsson (Publ) | PMIP protocol enhancement |
| RU2591214C2 (en) * | 2011-08-17 | 2016-07-20 | Телефонактиеболагет Л М Эрикссон (Пабл) | Improved pmip protocol |
| CN103581346B (en) * | 2012-07-19 | 2019-06-18 | 中兴通讯股份有限公司 | File transmitting method, system and local mobile anchor |
| CN103686671B (en) * | 2012-09-14 | 2019-01-18 | 中兴通讯股份有限公司 | A kind of method and system of notice access net location information |
| CN110012458A (en) * | 2018-01-04 | 2019-07-12 | 中兴通讯股份有限公司 | A kind of method and device for negotiating IP address type |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101009941A (en) * | 2007-01-15 | 2007-08-01 | 中山大学 | A method for realizing the communication between the mobile IPv4 node and IPv6 communication node |
| CN101087296A (en) * | 2006-06-08 | 2007-12-12 | 上海亿人通信终端有限公司 | Method for utilizing network processor to translate the IPv4/IPv6 network protocol |
| CN101237410A (en) * | 2008-03-04 | 2008-08-06 | 中山大学 | A method for realizing communication of mobile node in IPv4/v6 mixed network |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7356045B2 (en) * | 2002-10-22 | 2008-04-08 | Cisco Technology, Inc. | Shared port address translation on a router behaving as NAT & NAT-PT gateway |
| EP1420559A1 (en) * | 2002-11-13 | 2004-05-19 | Thomson Licensing S.A. | Method and device for supporting a 6to4 tunneling protocol across a network address translation mechanism |
-
2010
- 2010-09-07 CN CN201010277519.6A patent/CN101977246B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101087296A (en) * | 2006-06-08 | 2007-12-12 | 上海亿人通信终端有限公司 | Method for utilizing network processor to translate the IPv4/IPv6 network protocol |
| CN101009941A (en) * | 2007-01-15 | 2007-08-01 | 中山大学 | A method for realizing the communication between the mobile IPv4 node and IPv6 communication node |
| CN101237410A (en) * | 2008-03-04 | 2008-08-06 | 中山大学 | A method for realizing communication of mobile node in IPv4/v6 mixed network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101977246A (en) | 2011-02-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101091357B (en) | Method for controlling routing operations in a network, related network and computer program product thereof | |
| KR101653546B1 (en) | Method of private addressing in proxy mobile ip networks | |
| EP1379034A1 (en) | System for managing mobile node in mobile network | |
| CA2563911C (en) | System and method for providing ipv6 services | |
| CN101977246B (en) | Method and system for supporting PMIPv6 (Proxy Mobile IPv6) mobility | |
| CN103249025B (en) | A kind of LMA Dynamic Discovery method in PMIPv6 environment | |
| CN101702800B (en) | Agent mobile communication system and method | |
| US9326125B2 (en) | Device and method for realizing identity and locator separation network | |
| CN1870633B (en) | Method for supporting mobile IPv4 by double-stack moible IPv6 node | |
| CN1770742B (en) | System for managing mobile node in mobile network | |
| CN100571214C (en) | The double-stack support extension method of layer mobile IPv 6 protocol | |
| KR20070059489A (en) | Routing optimization method in the same nested nemo | |
| JP2003018185A (en) | Mobile ip communication system, mobile ip communication method, network repeater system and terminal for mobile object | |
| US20150049669A1 (en) | Method and system for management of the mobility of a mobile network | |
| JP2005012620A (en) | Network system and address creation method | |
| CN102843667B (en) | Method for deploying subnet mobile in separation mechanism mobility management system | |
| CN104468305B (en) | Realize Layer3 Virtual Private Network method and apparatus | |
| CN101754173B (en) | Home address allocation, method and system for transmitting message by using same | |
| KR20040066432A (en) | Method for Mobility Support using Mobile IP In Networks | |
| US7903649B2 (en) | Mobile IPv6 network system and method for forwarding packet in the system | |
| CN102378284A (en) | Inter-domain switching method of proxy mobile IPv6 (Internet Protocol Version 6) | |
| KR20100073808A (en) | Method for configurating addresses of mobile node in multiples of gateway connected manet and method for selecting a basic gateway of mobile node | |
| KR101433380B1 (en) | MANEMO(MANET for NEMO；Mobile Ad-hoc Network for Network Mobility) System and Method based on Anchor Point | |
| Ren et al. | Implementation and test of PMIPv6 dual stack protocol | |
| EP2568715A1 (en) | Mobile node, care of address acquisition method and system thereof, and dhcp server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20140312 Termination date: 20190907 |