Multiplex communications – Pathfinding or routing – Combined circuit switching and packet switching
Reexamination Certificate
1998-08-19
2004-02-24
Ho, Duc (Department: 2665)
Multiplex communications
Pathfinding or routing
Combined circuit switching and packet switching
C370S392000, C370S401000, C370S466000, C455S432300, C455S433000, C709S238000
Reexamination Certificate
active
06697354
ABSTRACT:
FIELD OF INVENTION
This invention relates to computer networks. More specifically, it relates to a method and system for distributed network address translation for mobile network devices on computer networks.
BACKGROUND OF THE INVENTION
The Internet Protocol (“IP”) is an addressing protocol designed to route traffic within a network or between networks. The Internet Protocol is used on many computer networks including the Internet, intranets and other networks. Internet Protocol addresses are typically assigned to “immobile” nodes on a network. An immobile node may be moved to a different computer network, but is typically associated with a static physical location (e.g., 3Com Corporation in Santa Clara, Calif.).
The Mobile Internet Protocol allows “mobile” nodes to transparently move between different Internet Protocol sub-networks (“subnets”). Internet Protocol addresses are typically assigned to mobile nodes based on their home Internet Protocol subnet. The home subnet is connected to an external network (e.g., the Internet or an intranet) with a “home agent” that serves as the subnet's gateway router. As is known in the art, the gateway connects computer networks using different networking protocols or operating at different transmission capacities. As is known in the art, a router translates differences between network protocols and routes data packets to an appropriate network node or network device. When a mobile node “roams,” (i.e., dynamically changes its physical location), it periodically transmits “agent solicitation” messages to other gateway routers. A mobile node also listens for “agent advertisement” messages from other gateway routers. When a mobile node receives an agent advertisement message indicating that it is now on a foreign subnet, it registers with the foreign gateway router or “foreign agent” and its home agent. The registration with the home agent indicates the mobile node is away from “home” (i.e., away from its home subnet). The registration with the foreign agent allows the mobile node to receive data on the foreign subnet.
The Mobile Internet Protocol allows a mobile node to dynamically change its network connectivity in a manner that is transparent to protocol layers above the Internet Protocol layer. For example, without re-establishing Transmission Control Protocol or User Datagram Protocol sessions. As is known in the art, the Internet Protocol suite includes from lowest-to-highest, a link, network, transport and application layer. The Internet Protocol typically resides in the network layer in the Internet Protocol suite. Transmission Control Protocol and User Datagram Protocol typically reside in the transport layer of the Internet Protocol suite.
As is known in the art, Transmission Control Protocol (“TCP”) and User Datagram Protocol (“UDP”) are often used over IP in computer networks. Transmission Control Protocol provides a connection-oriented, end-to-end reliable protocol designed to fit into a layered hierarchy of protocols that support multi-network applications. User Datagram Protocol provides a transaction oriented datagram protocol, where delivery and duplicate packet protection are not guaranteed.
Current versions of Internet Protocol such as Internet Protocol version-4 (“IPv4”), including those used for Mobile Internet Protocol are becoming obsolete because of limited address space. With a 32-bit address-field, it is possible to assign 2
32
different addresses, which is 4,294,967,296, or greater than 4 billion possible addresses. However, with the explosive growth of the Internet and intranets, and the increased use of Mobile Internet Protocol, Internet Protocol addresses using a 32-bit address-field may soon be exhausted. Internet Protocol version-6 (“IPv6”) proposes the use of a 128-bit address-field for IP addresses. However, a large number of legacy networks including a large number of Internet subnets will still be using older versions for Internet Protocol with a 32-bit address space for many years to come.
Network Address Translation (“NAT”) has been proposed to extend the lifetime of Internet Protocol version 4 and earlier versions of Internet Protocol by allowing subnets to exist behind a single or small number of Internet Protocol addresses. A single Internet Protocol address is used for communication with external networks such as the Internet. Internally, the subnet uses local addressing. When a device or node using local addressing desires to communicate with the external world, a local address is translated to a common external Internet Protocol address used for communication with an external network by a network address translation device.
There are several problems associated with using network address translation to extend the life of the Internet Protocol including Mobile Internet Protocol. Network address translation interferes with the end-to-end routing principal of the Internet that recommends that packets flow end-to-end between network devices without changing the contents of any packet along a transmission route (see e.g., “Routing in the Internet,” by C. Huitema, Prentice Hall, 1995, ISBN 0-131-321-927).
Current versions of network address translation replace a local network address in a data packet header with an external network address on outbound traffic, and replace an external network address in a data packet header with a local network address on inbound traffic. This type of address translation is computationally expensive, causes security problems by preventing certain types of encryption from being used, or break a number of existing applications in a network that cannot provide network address translation (e.g., File Transfer Protocol (“FTP”)).
Current versions of network address translation may not gracefully scale beyond a small subnet containing a few dozen nodes or devices because of the computational and other resources required. Network address translation potentially requires support for many different internal network protocols be specifically programmed into a translation mechanism for external protocols in a network address translation device such as a network address translation router. Computational burdens placed on a network address translation router may be significant and degrade network performance, especially if several network address translation-enabled stub networks share the same network address translation router. In a worst case scenario, a network address translation router translates every inbound and outbound data packet.
When network address translation is used to translate a Transmission Control Protocol/Internet Protocol or User Datagram Protocol/Internet Protocol data packet, the packet's Internet Protocol, Transmission Control Protocol or User Datagram Protocol checksums are recalculated. When a port in a Transmission Control Protocol or User Datagram Protocol header is translated, the packet's Transmission Control Protocol or User Datagram Protocol checksums are also recalculated. This further increases the computational cost of translation in a network address translation router.
When an Internet Protocol address or port is translated with network address translation, a new length may result for the data packet and a possible change in a Transmission Control Protocol sequence number. A running sequence number offset (i.e., a delta) must then be maintained throughout the remainder of the connection. This delta must be applied to a future traffic, including acknowledgment numbers further increasing computational time in a network address translation router.
In addition to Transmission Control Protocol or User Datagram Protocol, a network address translation router should be able to translate addresses, ports, change lengths and maintain sequence numbers for a number of different protocols that may transmit an Internet Protocol address or port number (e.g., FTP, H.323, H.324, CUSeeME, RealAudio, Internet Relay Chat and others). On a networks using Internet Protocol, it is desirable to provide network address translation without large computatio
Borella Michael S.
Grabelsky David
Mahler Jerry
Sidhu Ikhlaq
3Com Corporation
Ho Duc
McDonnell & Boehnen Hulbert & Berghoff
LandOfFree
Method and system for distributed network address... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Method and system for distributed network address..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method and system for distributed network address... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3306913