Network address translation six to four for proxy mobile internet protocol version six
First Claim
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.
1 Assignment
0 Petitions
Accused Products
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.
-
Citations
23 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. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
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. - View Dependent Claims (8, 9, 10, 11, 12)
-
-
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. - View Dependent Claims (15, 16, 17, 18, 19, 20, 21, 22, 23)
-
Specification