Network address translation six to four for proxy mobile internet protocol version six

• US 9,210,735 B2
• Filed: 06/28/2011
• Issued: 12/08/2015
• Est. Priority Date: 07/02/2010
• Status: Active Grant

• Current Assignee: Futurewei Technologies Incorporated (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Futurewei Technologies Incorporated (Huawei Investment & Holding Co., Ltd.)
• Inventors: Sarikaya, Behcet, Xia, Yangsong
• Primary Examiner(s): Nickerson, Jeffrey
• Assistant Examiner(s): Cousins, Joseph M
• Application Number:
  US13/170,545
• Publication Number:
  US 20120005372A1
• Time in Patent Office: 1,624 Days
• Field of Search: 709/245
• US Class Current: 1/1
• CPC Class Codes: H04L 61/251 between different IP versions
• CPC Class Codes: H04L 61/2553 Binding renewal aspects, e.g. using keep-alive messages
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04W 80/045 involving different protocol versions, e.g. MIPv4 and MIPv6
• CPC Class Codes: H04W 88/182 Network node acting on behalf of an other network entity, e.g. proxy

Abstract

An apparatus comprising a Local Mobility Anchor (LMA) configured to couple to a mobile node (MN), a network address translation (NAT) server, and an Internet Protocol (IP) version four (IPv4) only host and to associate an IP version six (IPv6) address for an interface with the MN with an IPv4 address for an interface with the IPv4 only host in a NAT state table entry, wherein the NAT state table entry is used to translate an IPv6 packet associated with the MN to an IPv4 packet associated with the IPv4 only host.

Claims

1. A method implemented in a router acting as a Proxy Mobile Internet Protocol version 6 (PMIPv6) Local Mobility Anchor (LMA), wherein the router comprises a hardware processor configured to implement the method, the method comprising:

receiving a proxy binding update for a mobile node (MN) from a media access gateway (MAG);

creating a binding cache entry (BCE) for the MN;

sending a proxy binding acknowledgement to the MAG;

receiving an Internet Protocol (IP) version six (IPv6) packet from a mobile node (MN) wirelessly connected to the MAG, wherein the IPv6 packet comprises a source address and a destination address, wherein the source address is the MN'"'"'s IPv6 address, and wherein the destination address comprises a IPv6 prefix;

matching the source address in the IPv6 packet to the BCE;

determining whether the IPv6 prefix in the destination address of the IPv6 packet matches a prefix stored in a prefix table;

forwarding the IPv6 packet to an IPv6 host when the IPv6 prefix in the destination address of the IPv6 packet matches the prefix stored in the prefix table;

determining whether an IPv6 only flag in the BCE for the MN has been set when the IPv6 prefix in the destination address of the IPv6 packet does not match the prefix stored in the prefix table, wherein the IPv6 packet is destined to an IPv4 host that does not support IPv6 when the IPv6 prefix in the destination address of the IPv6 packet does not match the prefix stored in the prefix table;

setting the IPv6 only flag in the BCE for the MN when the IPv6 prefix in the destination address of the IPv6 packet does not match the prefix stored in the prefix table; and

processing multicast messages sent by the IPv4 host to the MN.

2. The method of claim 1, further comprising:

determining that the source address of the IPv6 packet does not match an entry in a network address translation (NAT) state table;

creating a new entry in the NAT state table;

linking the new entry in the NAT state table to the BCE for the MN;

translating the IPv6 packet into an IPv4 packet using the new entry for the NAT state table; and

forwarding the IPv4 packet to the IPv4 host.

3. The method of claim 2, wherein the new entry in the NAT state table associates the source address and an IPv6 port at the router on which the IPv6 packet was received with an IPv4 address for the IPv4 host and an IPv4 port on the router on which IPv4 packets are sent to the IPv4 host.

4. The method of claim 3, wherein the router supports Protocol Independent Multicast (PIM) on the IPv4 port.

5. The method of claim 1, further comprising:

determining that the source address of the IPv6 packet matches an entry in a network address translation (NAT) state table;

translating the IPv6 packet into an IPv4 packet; and

forwarding the IPv4 packet to the IPv4 host.

6. The method of claim 1, further comprising instructing the MAG to disable localized routing between the MAG and another MAG by setting an EnableMAGLocalROuting flag to zero.

7. A router acting as a Proxy Mobile Internet Protocol version 6 (PMIPv6) Local Mobility Anchor (LMA), the router comprising:

a receiver configured to receive a proxy binding update for a mobile node (MN) from a media access gateway (MAG);

a processor configured to create a binding cache entry (BCE) for the MN;

a transmitter configured to send a proxy binding acknowledgement to the MAG,

wherein the receiver is further configured to receive an Internet Protocol (IP) version six (IPv6) packet, wherein the IPv6 packet comprises a source address and a destination address, wherein the source address is the MN'"'"'s IPv6 address, and wherein the destination address comprises a IPv6 prefix,

wherein the processor is further configured to

match the source address in the IPv6 packet to the BCE;

determine whether the IPv6 prefix in the destination address of the IPv6 packet matches a prefix stored in a prefix table;

forward the IPv6 packet to an IPv6 host when the IPv6 prefix in the destination address of the IPv6 packet matches the prefix stored in the prefix table;

determine whether an IPv6 only flag in the BCE for the MN has been set when the IPv6 prefix in the destination address of the IPv6 packet does not match the prefix stored in the prefix table;

set the IPv6 only flag in the BCE for the MN when the IPv6 prefix in the destination address of the IPv6 packet does not match the prefix stored in the prefix table; and

process multicast messages sent by an IP version 4 (IPv4) host to the MN, and wherein the IPv4 host does not support IPv6.

8. The router of claim 7, wherein the transmitter is further configured to send keepalive messages to a network address translation (NAT) server that is coupled to and external to the router, wherein the keepalive messages refresh an entry for the MN in a NAT table in the NAT server, wherein the MN does not send any keepalive messages to the LMA and does not send any keepalive messages to the MAG, wherein the NAT state table entry is linked to the BCE for the MN, and wherein the BCE maps an IP address of the MN to a care-of-address (CoA) for the MN.

9. The router of claim 8, wherein the keepalive messages are Internet Control Message Protocol (ICMP) Echo Request messages.

10. The router of claim 9, wherein the ICMP Echo Request messages are ICMP version 6 (ICMPv6) Echo Request messages, wherein the NAT server is configured to translate the ICMPv6 Echo Request messages into ICMP version 4 (ICMPv4) Echo Request messages, and wherein the NAT server is configured to send the ICMPv4 Echo Request messages to the IPv4 host.

11. The router of claim 10, wherein the ICMPv6 Echo Request messages are encoded with a User Datagram Protocol (UDP) header.

12. The router of claim 11, wherein a keepalive packet has a second source address and a second destination address, and wherein the second source address is the MN'"'"'s IP address.

13. A network component comprising:

a transmitter;

a receiver at a Local Mobility Anchor (LMA) configured to receive an Internet Protocol version six (IPv6) packet, wherein the IPv6 packet comprises a source address and a destination address, wherein the source address is a mobile node'"'"'s (MN'"'"'s) IPv6 address, and wherein the destination address comprises an IPv6 prefix,

a processor at the LMA that is coupled to the receiver and configured to;

match the source address in the IPv6 packet to a Binding Cache Entry (BCE);

determine whether the IPv6 prefix in the destination address of the IPv6 packet matches a prefix stored in a prefix table;

forward the IPv6 packet to an IPv6 host when the IPv6 prefix in the destination address of the IPv6 packet matches the prefix stored in the prefix table;

determine whether an IPv6 only flag in the BCE for the MN has been set when the IPv6 prefix in the destination address of the IPv6 packet does not match the prefix stored in the prefix table; and

set the IPv6 only flag in the BCE for the MN when the IPv6 prefix in the destination address of the IPv6 packet does not match the prefix stored in the prefix table;

wherein the receiver is further configured to receive an Internet Protocol (IP) version four (IPv4) multicast data packet that comprises an IPv4 address from an IPv4 host;

wherein the processor is further configured to translate the IPv4 multicast data packet into an IPv6 multicast data packet that comprises an IPv6 address based on the IPv4 address; and

wherein the transmitter is configured to send the IPv6 multicast data packet to a mobile access gateway (MAG) associated with a plurality of the mobile nodes (MNs) that are subscribed to the IPv6 address, and

wherein the LMA supports source-specific multicast (SSM) and Protocol Independent Multicast (PIM) on an upstream interface of the LMA.

14. A router acting as a Proxy Mobile Internet Protocol version 6 (PMIPv6) Local Mobility Anchor (LMA), the router comprising:

a receiver configured to receive a proxy binding update for a mobile node (MN) from a media access gateway (MAG);

a processor configured to create a binding cache entry (BCE) for the MN;

a transmitter configured to send a proxy binding acknowledgement to the MAG,

wherein the receiver is further configured to subsequently receive a Multicast Listener Discovery (MLD) Join message for the MN from the MAG,

wherein the processor is further configured to translate the MLD Join message into an Internet Group Management Protocol (IGMP) Join message,

wherein the transmitter is further configured to send the IGMP Join message to an Internet Protocol (IP) version four (IPv4) host, thereby joining the MN to a multicast group to which the IPv4 host sends IPv4 multicast data packets,

wherein the receiver is further configured to receive an IP version six (IPv6) packet, wherein the IPv6 packet comprises a source address and a destination address, wherein the source address is the MN'"'"'s IPv6 address, and wherein the destination address comprises a IPv6 prefix,

wherein the processor is further configured to;

match the source address in the IPv6 packet to the BCE;

determine whether the IPv6 prefix in the destination address of the IPv6 packet matches a prefix stored in a prefix table;

forward the IPv6 packet to an IPv6 host when the IPv6 prefix in the destination address of the IPv6 packet matches the prefix stored in the prefix table;

determine whether an IPv6 only flag in the BCE for the MN has been set when the IPv6 prefix in the destination address of the IPv6 packet does not match the prefix stored in the prefix table; and

set the IPv6 only flag in the BCE for the MN when the IPv6 prefix in the destination address of the IPv6 packet does not match the prefix stored in the prefix table;

wherein the receiver is further configured to receive the IPv4 multicast data packets from the IPv4 host,

wherein the IPv4 multicast data packets comprise an IPv4 destination address and an IPv4 source address,

wherein the processor is further configured to translate the IPv4 multicast data packets into IP version six (IPv6) multicast data packets by adding an IPv6 prefix onto the IPv4 destination address, and

wherein the transmitter is further configured to tunnel the IPv6 multicast data packets to the MAG using a proxy Care of Address (CoA) for the MN.

15. The router of claim 14, wherein the MLD Join request comprises a plurality of individual MLD Join requests that have been aggregated together by the MAG, wherein each individual MLD Join request is for one of a plurality of the MNs wirelessly connected to the MAG, and wherein the MAG is configured to duplicate the IPv6 multicast data packets and send the tunneled IPv6 multicast data packets to each of the MNs.

16. The router of claim 14, wherein the processor does not check the BCE when translating the IPv4 multicast data packets into IPv6 multicast data packets.

17. The router of claim 14, wherein the processor is further configured to confirm that the last 32 bits of an IPv4 multicast address in the IGMP Join message are in a range from 224/8 to 239/8 prior to the receiver sending the IGMP Join message to the IPv4 host.

18. The router of claim 14, wherein a second source address of the IPv6 multicast packets sent to the MAG is an IPv6 interface address for the LMA.

19. The router of claim 14, wherein translating the IPv4 multicast data packets into the IPv6 multicast data packets comprises:

copying a type of service (TOS) field from the IPv4 multicast data packets into a traffic class field in the IPv6 multicast data packets;

copying an IPv4 protocol field from the IPv4 multicast data packets into a next header field in the IPv6 multicast data packets;

copying a time to live (TTL) field from the IPv4 multicast data packets into a hop limit field in the IPv6 multicast data packets; and

copying an IPv4 payload from the IPv4 multicast data packets into an IPv6 payload in the IPv6 multicast data packets.

20. The router of claim 14, wherein at least some of the IPv4 multicast data packets are IPv4 fragment packets, and wherein translating the IPv4 multicast data packets into the IPv6 multicast data packets comprises:

copying a fragmentation offset field from the IPv4 multicast data packets into a fragment header in the IPv6 multicast data packets;

copying a 16-bit identification field from the IPv4 multicast data packets into a low-order 16 bits of the IPv6 fragment header identification field;

setting the high-order bits in the IPv6 fragment header identification field to zero; and

copying a more fragment (MF) field from the IPv4 multicast data packets into a MF field in the IPv6 multicast data packets.

21. The router of claim 14, wherein the LMA sends a plurality of keepalive messages based on a determined keepalive interval to a network address translation (NAT) server instead of the MN to refresh a NAT state table entry that is associated with the BCE for the MN, and wherein the keepalive messages are Internet Control Message Protocol (ICMP) Echo Request messages that each comprise a User Datagram Protocol (UDP) header and serve as outbound refresh messages for outgoing packets to the IPv4 host.

22. The router of claim 21, wherein the LMA receives a plurality of keepalive messages based on a determined time interval from the NAT server to refresh the BCE for the MN, and wherein the keepalive messages are ICMP Echo Reply messages that serve as inbound refresh messages for incoming packets from the IPv4 host.

23. The router of claim 22, wherein the NAT state table entry comprises an IPv6 prefix (Pref64) that is assigned to the NAT server and the keepalive interval for keeping alive a communication session for the MN.