CN101977246A - 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
- CN101977246A CN101977246A CN2010102775196A CN201010277519A CN101977246A CN 101977246 A CN101977246 A CN 101977246A CN 2010102775196 A CN2010102775196 A CN 2010102775196A CN 201010277519 A CN201010277519 A CN 201010277519A CN 101977246 A CN101977246 A CN 101977246A
- Authority
- CN
- China
- Prior art keywords
- address
- message
- ipv4home
- public
- mag
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 238000006243 chemical reaction Methods 0.000 claims description 9
- 230000008569 process Effects 0.000 claims description 8
- 230000002457 bidirectional effect Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 6
- 230000009977 dual effect Effects 0.000 description 3
- 230000007704 transition Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
- Small-Scale Networks (AREA)
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 technologies, and in particular, to a method and a system for supporting mobility of proxy mobile IPv6(PMIPv 6).
Background
The transition from IPv4 to IPv6 is a long-term process in which both IPv6 and IPv4 protocols will be used in the same network architecture. Thus, a Mobile Node (MN) in the PMIPv6 domain may operate in IPv4-only, IPv6-only or dual stack mode, and the network between the Mobile Access Gateway (MAG) and the Local Mobility Anchor (LMA) may be an IPv4 or IPv6 network. Thus, there is a need to provide mobility support for IPv4-only, IPv6-only or dual stack mode MNs in the PMIPv6 domain.
A brief description of the draft-ietf-netlmm-pmip6-IPv4-Support-18(IPv4 Support for Proxy MobileIPv6) protocol is as follows: all mobility entities, LMA and MAG are dual stacks and the type mobility signaling of any transport network is based on IPv 6.
According to the description of a draft-ietf-netlmm-pmip6-IPv4-support-18 protocol, a PMIPv6 support method for IPv4 is shown in fig. 1, and the support method comprises the following steps:
step 101: when an MN supporting IPv4 moves into a PMIPv6 domain, a MAG acquires the IP protocol version type of the MN;
specifically, when the MN supporting IPv4 moves into the PMIPv6 domain, the MAG obtains an IP protocol version type of the MN, such as IPv4 or IPv6, from a policy file (policy profile) of the MN, where the IP protocol version type of the MN in the method is IPv 4.
Step 102: the MAG sends an agent binding update message carrying an IPv4home address request option according to the fact that the IP protocol version type of the MN is IPv 4;
specifically, the MAG carries all 0 or an IPv4Home Address request option (IPv4Home Address request option) including an IPv4Home Address allocated to the MN in a Proxy Binding Update (PBU) message sent to the LMA according to the IP protocol version type of the MN being IPv 4.
Step 103: after receiving the PBU message, the LMA generates or renews an IPv4home address according to an IPv4home address request option in the PBU message, and carries the generated or renewed IPv4home address in a Proxy Binding Acknowledgement (PBA) returned to the MAG;
specifically, after receiving the PBU message, the LMA generates an IPv4Home Address when the IPv4Home Address in the IPv4Home Address request option of the PBU message is all 0, and adds the IPv4Home Address to a binding Cache Entry (BCE, binding Cache Entry) corresponding to the MN; when the IPv4 HomeAddress Request operation of the PBU message has the IPv4home address distributed by the MAG for the MN, the LMA judges whether the original IPv4home address is occupied or not through the DHCP Server associated with the LMA or coexisting with the LMA, and when the original IPv4home address is not occupied, the BCE of the MN is updated, namely the original IPv4home address in the BCE is continued; when the mobile terminal is occupied, generating an IPv4home address, and adding the address into a corresponding BCE of the MN; in the PBA message returned to the MAG, the generated or continued IPv4Home Address is carried by an IPv4Home Address reply option (IPv4Home Address reply option);
the method also comprises the following steps: after receiving the PBU message, the LMA searches a corresponding BCE according to the MN indicated in the PBU message, and when the PBE is not searched, the LMA creates the BCE of the MN;
in this step, the generation of the IPv4home address is generally: the LMA allocates an IPv4home address through a Dynamic Host Configuration Protocol (DHCP) Server (Server) associated with or coexisting with the LMA; the IPv4home address comprises a subnet mask;
compared with PMIPv6, the draft-ietf-netlmm-pmip6-IPv4-support-18 protocol increases the IPv4home address of the MN and the IPv4 default router address allocated to the MN in the BCE of the MN.
Step 104: after receiving the PBA from the LMA, the MAG adds an IPv4home address carried by the PBA in a binding Update List Entry (BUL) of the MN;
specifically, after receiving the PBA from the LMA, the MAG adds an IPv4Home Address carried by the PBA through an IPv4Home Address Reply Option to the BUL of the MN, and obtains an IPv4 Default Router Address allocated to the MN through an IPv4 Default-Router Address Option in the PBA.
Step 105: the MN obtains the assigned IPv4home address from the MAG through a DHCP process.
After the above steps are completed, when the LMA forwards the message to the 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*/
when the LMA forwards the message from the 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*/
where src represents the source address; dst represents the destination address; Proxy-CoA represents MAG address; IPv4-MN-HOA denotes MN address; LMAA represents LMA address; the CN indicates the address of the Correspondent Node (CN).
The method solves the support of IPv4 in the PMIPv6 domain when Network Address Translation (NAT) does not exist between the MAG and the LMA.
At present, according to a draft-koodli-IPv6-in-Mobile-networks-00(Mobile networks connectivity for IPv6 delivery) protocol, Mobile internet access from smart phones and other Mobile terminals is accelerating the exhaustion of IPv4 addresses, and it is impossible to configure a unique public network IPv4 address for all Mobile terminals. Considering that the use of the private network IPv4 address can delay the exhaustion of the public network IPv4 address, in actual network deployment, a NAT can be deployed on an associated network entity to allocate a private network address to the mobile terminal, so as to alleviate the exhaustion of the public network IPv4 address, for example, in the scheme of the mobile internet, the user terminal device interface IP address is allocated with a 10.
However, when NAT exists between MAG and LMA, there is no solution in the prior art that can solve the support of PMIPv6 for IPv4, so a solution needs to be proposed to solve the support of mobility in this scenario.
Disclosure of Invention
In view of this, the main object of the present invention is to provide a PMIPv6 mobility support method and system, which can solve the problem of supporting IPv4 by PMIPv6 when NAT exists between MAG and LMA.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
the invention provides a PMIPv6 mobility support method, which comprises the following steps:
when an MN supporting IPv4 moves to a PMIPv6 domain of an NAT scene, MAG sends a PBU message to LMA, wherein the PBU message carries an IPv4 network address translation port number and a public IPv4home address request;
after receiving the PBU message, the LMA adds or updates an IPv4 network address translation port number and a public IPv4home address in the BCE of the MN according to the PBU message, and returns the public IPv4home address to the MAG through the PBA message;
the MAG adds or updates an IPv4 network address translation port number and a public IPv4home address in the BUL of the MN;
when the message is forwarded, the MAG and the LMA forward the message according to the public IPv4home address and the IPv4 network address translation port number.
In the above scheme, the MAG sending the PBU message to the LMA is: the MAG carries all 0 or public IPv4home address request options containing a public IPv4home address allocated for the MN by itself in a PBU message sent to the LMA, and carries an IPv4 network switch port number option containing an IPv4 network switch port number in the PBU message.
In the above solution, the returning the public IPv4home address to the MAG through the PBA message is: in the PBA message returned to the MAG, the public IPv4home address is carried by the public IPv4home address reply option.
In the above scheme, when the PBU message carries a public IPv4home address request option that the public IPv4home address is all 0, the method further includes: after receiving the PBU message, the LMA generates a public IPv4home address;
the generation public IPv4 is hometown: LMA distributes public IPv4home address through DHCP Server associated or coexisting with LMA; the public IPv4home address includes a subnet mask.
In the above scheme, the method further comprises: the MN obtains its own private IPv4 address and port number from the LMA through DHCP or PMIPv6 registration process.
In the above solution, the MAG and LMA forward messages according to the public IPv4home address and IPv4 network address translation port number, and the method includes:
when the MN sends a message to the CN, after the MAG receives the message sent by the MN, the NAT coexisting with the MAG replaces a source address in a message header with a public IPv4home address and changes a source port number into an IPv4 network address translation port number; then, the MAG encapsulates the modified message header and sends the modified message header to the LMA through a bidirectional tunnel between the MAG and the LMA; after receiving the message, the LMA decapsulates the message header and forwards the message to the CN according to the destination address;
when CN sends message to MN, LMA receives message sent by CN, according to public IPv4home address and IPv4 network address conversion port number, searches corresponding MN in BCE, sends message to MAG through corresponding MAG-LMA tunnel; after receiving the message, the MAG and the coexisting NAT of the MAG convert the public IPv4home address in the destination address of the message header and the IPv4 network address translation port number in the destination port number into the private address and port number of the IPv4 of the MN, and send the private address and port number to the MN.
The invention provides a PMIPv6 mobility support system, which comprises: MAG, LMA; wherein,
the MAG is used for sending a PBU message to the LMA when the MN supporting the IPv4 moves into a PMIPv6 domain of a NAT scene, wherein the PBU message carries an IPv4 network address translation port number and a public IPv4home address request; adding or updating an IPv4 network address translation port number and a public IPv4home address in the BUL of the MN according to the PBA message; when the message is forwarded, the message is forwarded with the LMA according to the public IPv4home address and the IPv4 network address translation port number;
the LMA is used for adding or updating an IPv4 network address conversion port number and a public IPv4home address in a BCE of the MN according to the PBU message after receiving the PBU message of the MAG, and returning the public IPv4home address to the MAG through the PBA message; when the message is forwarded, the message is forwarded with the MAG according to the public IPv4home address and the IPv4 network address translation port number.
In the above scheme, the system further comprises: MN for obtaining its own private IPv4 address and port number from LMA through DHCP or PMIPv6 registration procedure.
In the above scheme, when forwarding a message, the system further includes an NAT, configured to replace a source address of a header of the message with a public IPv4home address according to a public IPv4home address and change a source port number to an IPv4 network address translation port number when the MAG forwards the message of the MN to the LMA; when the MAG receives a CN message forwarded by the LMA, the public IPv4home address in the destination address of the message header and the IPv4 network address translation port number in the destination port number are converted into the private address and port number of the MN IPv 4.
The invention provides a PMIPv6 mobility support method and a PMIPv6 mobility support system, when an MN supporting IPv4 moves to a PMIPv6 domain of an NAT scene, a MAG sends a PBU message to an LMA, and the PBU message carries an IPv4 network address translation port number and a public IPv4home address request; after receiving the PBU message, the LMA adds or updates an IPv4 network address translation port number and a public IPv4home address in the BCE of the MN, and returns the public IPv4home address to the MAG; the MAG adds or updates an IPv4 network address translation port number and a public IPv4home address in the BUL of the MN; when the message is forwarded, the MAG and the LMA forward the message according to the public IPv4home address and the IPv4 network address conversion port number; thus, the support of PMIPv6 on IPv4 when NAT exists between MAG and LMA can be solved, and the method is suitable for transition from IPv4 to IPv 6.
Drawings
FIG. 1 is a method for supporting IPv4 by PMIPv6 when NAT does not exist between MAG and LMA in the prior art;
FIG. 2 is a flowchart illustrating a PMIPv6 mobility support method according to the present invention;
FIG. 3 is a schematic diagram of the IPv4 NAT Home Address Request Option format;
FIG. 4 is a schematic diagram of the IPv4 NAT Port Option format;
FIG. 5 is a schematic diagram of the format of the IPv4 NAT Home Address Reply Option;
FIG. 6 is a diagram illustrating a message format when a MN sends a message to a CN according to the present invention;
FIG. 7 is a diagram illustrating a message format when a CN sends a message to a MN according to the present invention;
fig. 8 is a schematic structural diagram of a PMIPv6 mobility support system according to the present invention.
Detailed Description
The basic idea of the invention is: when an MN supporting IPv4 moves to a PMIPv6 domain of an NAT scene, MAG sends a PBU message to LMA, wherein the PBU message carries an IPv4 network address translation port number and a public IPv4home address request; after receiving the PBU message, the LMA adds or updates an IPv4 network address translation port number and a public IPv4home address in the BCE of the MN according to the PBU message, and returns the public IPv4home address to the MAG; the MAG adds or updates an IPv4 network address translation port number and a public IPv4home address in the BUL of the MN; when the message is forwarded, the MAG and the LMA forward the message according to the public IPv4home address and the IPv4 network address translation port number.
The present invention realizes a PMIPv6 mobility support method, as shown in fig. 2, the method includes the following steps:
step 201: when the MN supporting IPv4 moves into a PMIPv6 domain of an NAT scene, MAG acquires that the IP protocol version type of the MN is IPv 4;
specifically, when the MN supporting IPv4 moves into the PMIPv6 domain of the NAT scene, the MAG obtains the IP protocol version type of the MN from a policy file (policy profile) of the MN as IPv 4;
the PMIPv6 domain of the NAT scene is an entity in which MAG and NAT coexist in the PMIPv6 domain.
Step 202: the MAG sends a PBU message to the LMA according to the IP protocol version type of the MN being IPv4, wherein the PBU message carries an IPv4 network address translation port number and a public IPv4home address request;
specifically, the MAG carries a public IPv4Home Address Request Option (IPv4 NAT Home Address Request Option) of all 0 or including a public IPv4Home Address allocated to the MN in the PBU message sent to the LMA according to the IP protocol version type of the MN being IPv4, and carries an IPv4 NAT Port Option including an IPv4 network translation Port number in the PBU message;
the IPv4 network conversion port number is allocated to the MN by the MAG;
the format of the IPv4 NAT Home Address Request Option is shown in fig. 3, and includes: the method comprises the steps of data Type (Type), data Length (Length), Prefix Length (Prefix-len), identification bit (N), Reserved bit (Reserved) and public IPv4Home Address field (IPv4 NAT Home Address), wherein when the identification bit N is 1, MAG requests a public IPv4Home Address for MN, and the IPv4 NAT HomeAddress field is all 0 or is a specific public IPv4Home Address;
the IPv4 NAT Port Option format is shown in fig. 4, and includes: the message comprises a data Type (Type), a data Length (Length), an identification bit (F), a Reserved bit (Reserved), and an IPv4 network translation Port number field (IPv4 Port), wherein when the identification bit F is 1, the message carries an IPv4 network translation Port number allocated by the MAG to the MN, and the IPv4 Port field is a specific IPv4 network translation Port number.
Step 203: after receiving the PBU message, the LMA adds or updates the IPv4 network address translation port number and the public IPv4home address in the BCE of the MN according to the IPv4 network address translation port number and the public IPv4home address request carried by the PBU message, and returns the public IPv4home address to the MAG through the PBA message;
specifically, after receiving the PBU message, the LMA generates a public IPv4Home address when the public IPv4Home address of the IPv4 NAT Home Address request operation in the PBU message is all 0, and adds the public IPv4Home address into a corresponding BCE of the MN; when the IPv4 NAT Home Address Request operation of the PBU message has a public IPv4Home Address which is allocated to the MN by the MAG, the LMA updates the public IPv4Home Address into the BCE of the MN; in a PBA message returned to the MAG, carrying the public IPv4Home Address through a public IPv4Home Address Reply Option (IPv4 NAT Home Address Reply Option); in addition, the LMA acquires the IPv4 network address translation port number distributed by the MAG for the MN in the PBU message, and adds or updates the IPv4 network address translation port number in the corresponding BCE of the MN;
the format of the IPv4 NAT Home Address Reply Option is shown in fig. 5, and includes: the method comprises the steps of determining the Home Address of the mobile terminal, wherein the Home Address comprises a data Type (Type), a data Length (Length), a Status bit (Status), a Prefix-len, a reserved bit (R), an identification bit (N) and a public IPv4Home Address field (IPv4Home Address), wherein when the N identification bit is 1, the public IPv4Home Address is returned, and the IPv4Home Address field is a specific public IPv4Home Address;
the method also comprises the following steps: after receiving the PBU message, the LMA searches a corresponding BCE according to the MN indicated in the PBU message, and when the PBE is not searched, the LMA creates the BCE of the MN; the BCE is searched according to a method described in 5.4.1 in RFC5213, or the BCE is searched by taking a public IPv4home address and an IPv4 network address translation port number distributed by MAG as the MN as an index;
in this step, the generation of the public IPv4home address is generally: LMA distributes public IPv4home address through DHCP Server associated or coexisting with LMA; the public IPv4home address includes a subnet mask;
further, when the LMA detects that the lease of the public IPv4home address allocated to the MAG by itself expires, that is, the lifetime of the PBU message expires, and confirms that no MAG continues to use the allocated public IPv4home address, the LMA may continuously allocate the public IPv4home address to the next MAG sending the request through the PBA message.
Step 204: MAG adds or updates the public IPv4home address carried by PBA message and the IPv4 network address conversion port number distributed for MN in BUL of MN;
further, when a plurality of MNs are registered under the MAG, the MAG can add or update the public IPv4home address carried by the PBA message in the BUL of each MN, and distinguish each MN by allocating different IPv4 network address conversion port numbers, so that a plurality of MNs under one MAG can share one public IPv4home address; when the product of the allocated public IPv4home address and the IPv4 network address translation port number reaches the upper limit, the MAG requests a new public IPv4home address for the newly accessed MN which cannot be distinguished.
Step 205: MN can obtain its own private IPv4 address and port number from LMA through DHCP or PMIPv6 registration process;
specifically, the MN directly obtains a private IPv4 address and a port number from the LMA or a DHCP Server associated with the LMA through a DHCP process;
or, the MAG obtains the private IPv4 Address and port number allocated to the MN from the LMA by carrying the IPv4Home Address Request option in the PBU message, and then the MN obtains the private IPv4 Address and port number through DHCP or other processes.
Step 206: when the message is forwarded, the MAG and the LMA forward the message according to the public IPv4home address and the IPv4 network address translation port number;
for example, when the MN sends a message to the CN, the format of the message is as shown in fig. 6, which includes:
the IPv4 header source address (Src) of the message sent by the MN is the IPv4 private address (MN IPv4 address) of the MN, and the destination address (Dst) is the CN IPv4 address; after receiving the message sent by the MN, the MAG and the NAT coexisting with the MAG replace the source address in the message header with a public IPv4home address according to the public IPv4home address (NAT home address) obtained from the PBA message, and change the source port number into an IPv4 network address translation port number (NAT port); then, the MAG encapsulates the modified message header and sends the modified message header to the LMA through a bidirectional tunnel between the MAG and the LMA; after receiving the message, the LMA decapsulates the message header and forwards the message to the CN according to the destination address;
when the CN sends the message to the MN, the format of the message is shown in fig. 7, which includes:
the IPv4 packet header source address of the message sent by the CN is the private address of the IPv4 of the CN, the destination address is a public IPv4home address, and the destination port number is an IPv4 network address translation port number; after receiving the message sent by the CN, the LMA converts the port number according to the public IPv4home address and the IPv4 network address, searches the corresponding MN in the BCE, and sends the message to the MAG through the corresponding MAG-LMA tunnel; after receiving the message, the MAG decapsulates the message header, and the NAT coexisting with the MAG converts the public IPv4home address in the destination address of the message header and the IPv4 network address translation port number in the destination port number into the private address and port number of the MN IPv4 and sends the private address and port number to the MN.
In order to implement the above method, the present invention further provides a PMIPv6 mobility support system in NAT, as shown in fig. 8, the system includes: MAG 81, LMA 82; wherein,
the MAG 81 is used for sending a PBU message to the LMA82 when the MN supporting the IPv4 moves into a PMIPv6 domain of a NAT scene, wherein the PBU message carries an IPv4 network address translation port number and a public IPv4home address request; adding or updating an IPv4 network address translation port number and a public IPv4home address in the BUL of the MN according to the PBA message; when the message is forwarded, the message is forwarded with the LMA82 according to the public IPv4home address and the IPv4 network address translation port number;
LMA82, configured to add or update an IPv4 network address translation port number and a public IPv4home address in a BCE of the MN according to an IPv4 network address translation port number and a public IPv4home address request carried in the PBU message after receiving the PBU message of the MAG 81, and return the public IPv4home address to the MAG 81 through a PBA message; when the message is forwarded, the message is forwarded with the MAG 81 according to the public IPv4home address and the IPv4 network address translation port number;
the MAG 81 sends a PBU message to the LMA82, specifically: MAG 81 carries all 0 or IPv4 NAT Home Address Request Option containing public IPv4Home Address allocated for MN in PBU message sent to LMA82, and carries IPv4 NAT Port Option containing IPv4 network conversion Port number in PBU message;
the LMA82 returns the public IPv4home address to the MAG 81 through a PBA message, which specifically includes: the LMA82 carries the public IPv4Home address through an IPv4 NAT Home Address reply operation in a PBA message returned to the MAG 81;
the system further comprises: MN 83, used for obtaining its own private IPv4 address and port number from LMA82 through DHCP or PMIPv6 registration process.
When the message is forwarded, the system also comprises an NAT, wherein the NAT and the MAG 81 coexist, and the NAT is used for replacing a source address of a message header with a public IPv4home address according to a public IPv4home address obtained from the MAG 81 when the MAG 81 forwards the message of the MN 83 to the LMA82, and changing a source port number into an IPv4 network address translation port number; when MAG 81 receives a message of CN 84 forwarded by LMA82, the public IPv4home address in the destination address of the message header and the IPv4 network address translation port number in the destination port number are converted into the private address and port number of the IPv4 of MN 83;
further, when a plurality of MNs 83 are registered under the MAG 81, the MAG 81 is further configured to add or update a public IPv4home address carried in a PBA message in a BUL of each MN 83, and distinguish each MN 83 by allocating different IPv4 network address translation port numbers;
further, when the product of the allocated public IPv4home address and the IPv4 network address translation port number reaches an upper limit, the MAG 81 requests a new public IPv4home address for the newly accessed MN 83 that cannot be distinguished;
further, when the LMA82 detects that the lease of the public IPv4home address allocated to the MAG is expired, that is, the lifetime of the PBU message expires, and confirms that no MAG continues to use the allocated public IPv4home address, the LMA82 may continuously allocate the public IPv4home address to the MAG 81 that sends the request next through the PBA message.
By the method, when NAT exists between MAG and LMA, MAG requests public IPv4home address to LMA and sends MN IPv4 network address translation port number to LMA, thus, when forwarding private address message, message forwarding can be performed according to public IPv4home address and MN IPv4 network address translation port number, thereby solving the problem of IPv4 support by PMIPv6 and being suitable for transition from IPv4 to IPv 6.
The above description is only exemplary of the present invention and should not be taken as limiting the scope of the present invention, and any modifications, equivalents, improvements, etc. that are within the spirit and principle of the present invention should be included in the present invention.
Claims (11)
1. A method for supporting proxy mobile IPv6(PMIPv6) mobility, the method comprising:
when a Mobile Node (MN) supporting IPv4 moves into a PMIPv6 domain of a NAT scene, a Mobile Access Gateway (MAG) sends a Proxy Binding Update (PBU) message to a Local Mobility Anchor (LMA), wherein the PBU message carries an IPv4 network address translation port number and a public IPv4home address request;
after receiving the PBU message, the LMA adds or updates an IPv4 network address translation port number and a public IPv4home address in a Binding Cache Entry (BCE) of the MN according to the PBU message, and returns the public IPv4home address to the MAG through a Proxy Binding Acknowledgement (PBA) message;
the MAG adds or updates an IPv4 network address translation port number and a public IPv4home address in a binding update list entry (BUL) of the MN;
when the message is forwarded, the MAG and the LMA forward the message according to the public IPv4home address and the IPv4 network address translation port number.
2. The support method of claim 1, wherein the MAG sends a PBU message to the LMA as: the MAG carries all 0 or public IPv4home address request options containing a public IPv4home address allocated for the MN by itself in a PBU message sent to the LMA, and carries an IPv4 network switch port number option containing an IPv4 network switch port number in the PBU message.
3. The support method of claim 2, wherein the return of the public IPv4home address to the MAG via PBA message is: in the PBA message returned to the MAG, the public IPv4home address is carried by the public IPv4home address reply option.
4. The support method according to claim 2 or 3, wherein when the PBU message carries a public IPv4home address request option with a public IPv4home address of all 0, the method further comprises: after receiving the PBU message, the LMA generates a public IPv4home address;
the generation public IPv4 is hometown: LMA distributes public IPv4home address through Dynamic Host Configuration Protocol (DHCP) Server (Server) associated with or coexisting with LMA; the public IPv4home address includes a subnet mask.
5. The method of claim 4, further comprising: the MN obtains its own private IPv4 address and port number from the LMA through DHCP or PMIPv6 registration process.
6. The support method according to claim 5, wherein the MAG and LMA perform message forwarding according to the public IPv4home address and IPv4 network address translation port number, and the method is as follows:
when a MN sends a message to a Corresponding Node (CN), after a MAG receives the message sent by the MN, the NAT coexisting with the MAG replaces a source address in a message header with a public IPv4home address and changes a source port number into an IPv4 network address translation port number; then, the MAG encapsulates the modified message header and sends the modified message header to the LMA through a bidirectional tunnel between the MAG and the LMA; after receiving the message, the LMA decapsulates the message header and forwards the message to the CN according to the destination address;
when CN sends message to MN, LMA receives message sent by CN, according to public IPv4home address and IPv4 network address conversion port number, searches corresponding MN in BCE, sends message to MAG through corresponding MAG-LMA tunnel; after receiving the message, the MAG and the coexisting NAT of the MAG convert the public IPv4home address in the destination address of the message header and the IPv4 network address translation port number in the destination port number into the private address and port number of the IPv4 of the MN, and send the private address and port number to the MN.
7. A PMIPv6 mobility support system, comprising: MAG, LMA; wherein,
the MAG is used for sending a PBU message to the LMA when the MN supporting the IPv4 moves into a PMIPv6 domain of a NAT scene, wherein the PBU message carries an IPv4 network address translation port number and a public IPv4home address request; adding or updating an IPv4 network address translation port number and a public IPv4home address in the BUL of the MN according to the PBA message; when the message is forwarded, the message is forwarded with the LMA according to the public IPv4home address and the IPv4 network address translation port number;
the LMA is used for adding or updating an IPv4 network address conversion port number and a public IPv4home address in a BCE of the MN according to the PBU message after receiving the PBU message of the MAG, and returning the public IPv4home address to the MAG through the PBA message; when the message is forwarded, the message is forwarded with the MAG according to the public IPv4home address and the IPv4 network address translation port number.
8. The support system of claim 7, wherein the MAG sends a PBU message to the LMA as: the MAG carries all 0 or public IPv4home address request options containing a public IPv4home address allocated for the MN by itself in a PBU message sent to the LMA, and carries an IPv4 network switch port number option containing an IPv4 network switch port number in the PBU message.
9. The support system of claim 7, wherein the LMA returns the public IPv4home address to MAG via PBA message, being: and the LMA carries the public IPv4home address through a public IPv4home address reply option in a PBA message returned to the MAG.
10. The support system of claim 9, further comprising: MN for obtaining its own private IPv4 address and port number from LMA through DHCP or PMIPv6 registration procedure.
11. The support system according to claim 10, wherein at the time of message forwarding, the system further comprises a NAT for replacing a source address of a message header with a public IPv4home address and changing a source port number to an IPv4 network address translation port number according to a public IPv4home address when the MAG forwards a message of the MN to the LMA; when the MAG receives a CN message forwarded by the LMA, the public IPv4home address in the destination address of the message header and the IPv4 network address translation port number in the destination port number are converted into the private address and port number of the MN IPv 4.
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 true CN101977246A (en) | 2011-02-16 |
| CN101977246B 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) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103581346A (en) * | 2012-07-19 | 2014-02-12 | 中兴通讯股份有限公司 | Message sending method, message sending system and local mobility anchor |
| WO2014040552A1 (en) * | 2012-09-14 | 2014-03-20 | 中兴通讯股份有限公司 | Method and system for notifying access network position information |
| CN103999543A (en) * | 2011-08-17 | 2014-08-20 | 瑞典爱立信有限公司 | PMIP protocol enhancement |
| US9749838B2 (en) | 2011-08-17 | 2017-08-29 | Telefonaktiebolaget Lm Ericsson (Publ) | PMIP protocol enhancement |
| CN110012458A (en) * | 2018-01-04 | 2019-07-12 | 中兴通讯股份有限公司 | A kind of method and device for negotiating IP address type |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040076180A1 (en) * | 2002-10-22 | 2004-04-22 | Cisco Technology, Inc. | Shared port address translation on a router behaving as NAT & NAT-PT gateway |
| US20060259639A1 (en) * | 2002-11-13 | 2006-11-16 | Aken Dirk V | Method and device for supporting a 6to4 tunneling protocol across a network address translation mechanism |
| 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 |
-
2010
- 2010-09-07 CN CN201010277519.6A patent/CN101977246B/en not_active Expired - Fee Related
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040076180A1 (en) * | 2002-10-22 | 2004-04-22 | Cisco Technology, Inc. | Shared port address translation on a router behaving as NAT & NAT-PT gateway |
| US20060259639A1 (en) * | 2002-11-13 | 2006-11-16 | Aken Dirk V | Method and device for supporting a 6to4 tunneling protocol across a network address translation mechanism |
| 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 |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103999543A (en) * | 2011-08-17 | 2014-08-20 | 瑞典爱立信有限公司 | PMIP protocol enhancement |
| US9749838B2 (en) | 2011-08-17 | 2017-08-29 | Telefonaktiebolaget Lm Ericsson (Publ) | PMIP protocol enhancement |
| CN103999543B (en) * | 2011-08-17 | 2018-05-04 | 瑞典爱立信有限公司 | PMIP protocol enhancements |
| US10623941B2 (en) | 2011-08-17 | 2020-04-14 | Telefonaktiebolaget Lm Ericsson (Publ) | PMIP protocol enhancement |
| CN103581346A (en) * | 2012-07-19 | 2014-02-12 | 中兴通讯股份有限公司 | Message sending method, message sending system and local mobility anchor |
| WO2014040552A1 (en) * | 2012-09-14 | 2014-03-20 | 中兴通讯股份有限公司 | Method and system for notifying access network position information |
| US9854555B2 (en) | 2012-09-14 | 2017-12-26 | Zte Corporation | Method and system for notifying access network location information |
| CN110012458A (en) * | 2018-01-04 | 2019-07-12 | 中兴通讯股份有限公司 | A kind of method and device for negotiating IP address type |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101977246B (en) | 2014-03-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101653546B1 (en) | Method of private addressing in proxy mobile ip networks | |
| US7639686B2 (en) | Access network clusterhead for providing local mobility management of a roaming IPv4 node | |
| JP2004186989A (en) | Mobile terminal, and inter-terminal packet communication method | |
| KR20100090972A (en) | Method for supporting mobility of a mobile node in a multi-hop ip network and network system therefor | |
| CN101977246A (en) | Method and system for supporting PMIPv6 (Proxy Mobile IPv6) mobility | |
| EP1739899B1 (en) | A method and system for providing ipv6 service | |
| US20120195232A1 (en) | Method And An Apparatus For Providing Configuration Information To A Mobile Terminal | |
| JP2006279167A (en) | Mobile router, home agent and method of managing terminal position | |
| JP3881198B2 (en) | Mobile IP communication system, mobile IP communication method, network relay device, and mobile terminal | |
| CN101790146B (en) | Method for allocating address information, network equipment and network system | |
| US9307391B2 (en) | Method and system for management of the mobility of a mobile network | |
| CN1870633B (en) | Method for supporting mobile IPv4 by double-stack moible IPv6 node | |
| JP4319655B2 (en) | Terminal mobility for transition between private IPv4 / global IPv6 | |
| CN101754173B (en) | Home address allocation, method and system for transmitting message by using same | |
| EP2568715A1 (en) | Mobile node, care of address acquisition method and system thereof, and dhcp server | |
| KR20040066432A (en) | Method for Mobility Support using Mobile IP In Networks | |
| EP2262294A1 (en) | Packet routing method, proxy server and apparatus | |
| Ren et al. | Implementation and test of PMIPv6 dual stack protocol | |
| Kang et al. | DHT-based identifier-locator mapping management for mobile oriented future internet | |
| EP2668795B1 (en) | Hip proxy and method for mobility management in a wireless communications system | |
| Thakolsri et al. | Transition mechanism in IP-based wireless networks | |
| JP2007189751A (en) | Address converter, address conversion system, and sip server | |
| WO2004036948A2 (en) | Communication system and method of routing information | |
| KR20080002076A (en) | Wireless internet connection system | |
| WO2014187122A1 (en) | Lma dynamic discovery method in pmipv6 environment |
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 |
Granted publication date: 20140312 Termination date: 20190907 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |