US20060274749A1 - Method enabling network address translation of incoming session initiation protocol connections base on dynamic host configuration protocol address assignments - Google Patents

Method enabling network address translation of incoming session initiation protocol connections base on dynamic host configuration protocol address assignments Download PDF

Info

Publication number
US20060274749A1
US20060274749A1 US11/490,833 US49083306A US2006274749A1 US 20060274749 A1 US20060274749 A1 US 20060274749A1 US 49083306 A US49083306 A US 49083306A US 2006274749 A1 US2006274749 A1 US 2006274749A1
Authority
US
United States
Prior art keywords
internet protocol
dhcp
network device
address
packet
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.)
Abandoned
Application number
US11/490,833
Inventor
Niels Beier
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Intel Corp filed Critical Intel Corp
Priority to US11/490,833 priority Critical patent/US20060274749A1/en
Publication of US20060274749A1 publication Critical patent/US20060274749A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5007Internet protocol [IP] addresses
    • H04L61/5014Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/25Mapping addresses of the same type
    • H04L61/2503Translation of Internet protocol [IP] addresses
    • H04L61/2514Translation of Internet protocol [IP] addresses between local and global IP addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5076Update or notification mechanisms, e.g. DynDNS

Definitions

  • This invention relates to the field of network address assigning, and, more specifically, to a system, method, and apparatus for enabling Network Address Translation (NAT) of incoming Session Initiation Protocol (SIP) connections based on Dynamic Host Configuration Protocol (DHCP) address assignments.
  • NAT Network Address Translation
  • SIP Session Initiation Protocol
  • DHCP Dynamic Host Configuration Protocol
  • LANs Local area networks
  • IP Internet Protocol
  • a LAN typically has a set number of unique Internet Protocol (IP) addresses for all of the devices on the LAN. More specifically, multiple computers on the LAN may be represented by the same IP address and use the same router(s). In such embodiments, there may be 10 computers, for example, assigned to one router, where the router has its own unique IP address.
  • IP Internet Protocol
  • NAT Network Address Translation
  • a major problem with using NAT is to locate the correct device on the internal network when a packet from the Internet arrives at the router, because all packets received from the Internet are addressed to the router and not to the devices behind the router.
  • Configuring static mappings in the router can, in some cases, solve the problem.
  • the router may be configured to send all World Wide Web (WEB) traffic to a specific PC behind a router, and send all File Transfer Protocol (FTP) traffic to a different specified PC behind the router.
  • WEB World Wide Web
  • FTP File Transfer Protocol
  • the problem with this type of static mapping is that it requires specific configuration of the router, which may be expensive for an ISP shipping thousands of routers.
  • the access device can always establish the NAT mapping without the use of any additional information.
  • connections may only be made from inside a local network to a location outside of the network.
  • a device outside the network cannot connect to a device on the local network without the router being specifically configured to do so. Therefore, the prior art suffers from a serious inefficiency in that a connection cannot be initiated with a device on a LAN by a device outside the LAN without specific configuration of the router at the LAN.
  • FIG. 1 illustrates a general overview of a system according to an embodiment of the invention
  • FIG. 2 illustrates a basic DHCP packet according to an embodiment of the invention
  • FIG. 3 illustrates an additional option field portion of a DHCP packet according to an embodiment of the invention
  • FIG. 4 illustrates a process by which a device is assigned a local IP address according to an embodiment of the invention
  • FIG. 5 illustrates an association table according to an embodiment of the present invention
  • FIG. 6 illustrates a process by which a packet is sent from a local device to a destination address on the Internet according to an embodiment of the present invention
  • FIG. 7 illustrates a process by which packets are received and routed to the destination device on a local network.
  • An embodiment of the present invention includes a device that simultaneously acts as a Dynamic Host Configuration Protocol (DHCP) server and a Network Translation Address, (NAT) apparatus.
  • the device may be used within an access router connected to the Internet.
  • Such a device routes incoming packets to devices on a network based upon symbolic names acquired by a DHCP program running on the DHCP server.
  • the device allows an incoming Session Initiation Protocol (SIP) Internet Protocol (IP) call originating from the Internet to be routed to the correct device on the Local Area Network (LAN) segment that uses a private IP address.
  • SIP Session Initiation Protocol
  • IP Internet Protocol
  • DHCP is a software program that automatically assigns IP addresses to client stations logging onto an IP network. It eliminates the need to manually assign permanent IP addresses.
  • DHCP software typically runs on servers and is also found in network devices such as Integrated Services Digital Network (ISDN) routers and modem routers that allow multiple users access to the Internet.
  • ISDN Integrated Services Digital Network
  • NAT is an Internet Engineering Task Force (IETF) standard that allows an organization to present itself to the Internet with one address. NAT converts the address of each LAN node into one IP address for the Internet and vice versa. It also serves as a firewall by keeping individual IP addresses hidden from the outside world.
  • SIP is a protocol that provides IP telephony services, such as realtime, interactive voice and videoconferencing over LANs and the Internet. It allows any combination of voice, video and data to be transported.
  • FIG. 1 illustrates a general overview of the system according to an embodiment of the invention.
  • a number of devices are coupled to an access router 115 capable of transmitting and receiving data via the Internet.
  • FIG. 1 illustrates an embodiment where a first computer 100 , a second computer 105 , and a SIP IP telephone 110 all reside on a LAN connected to the router 115 .
  • the first computer 100 has a host name, or symbolic name, “Victor.”
  • the second computer 105 has a symbolic name “Hugo.”
  • the SIP IP telephone 110 has the symbolic name “Yrsa.”
  • the first computer 100 , the second computer 105 , and the SIP IP telephone 110 are all connected to the access router 115 , which serves as the pathway for communication between them and destinations on the Internet 120 .
  • the access router 115 serves as the pathway for communication between them and destinations on the Internet 120 .
  • the first computer 100 For the first computer 100 to send data to a destination address on the Internet, the first computer 100 must send a packet to the router 115 , which then sends the packet to the destination address on the Internet 120 .
  • the router 115 In order for a device on the LAN to receive packets of data from a site on the Internet, the router 115 must be configured to route certain packets to a particular device. In other words, the router 115 must extrapolate, from a received packet, the destination address of the packet. To determine which packets must be routed to which devices on the LAN, the router 115 typically has to have prior knowledge about each of the devices.
  • a device To receive and transmit packets over the LAN, or to an Internet site outside of the LAN, a device must have an IP address. As shown in FIG. 1 , the first computer 100 has the “private” IP address 10.0.1.1., the second computer 105 has the private IP address 10.0.1.2, and the SIP IP telephone 110 has the private IP address 10.0.1.3.
  • a private IP address is an IP address that is not known or directly accessible by a device outside the LAN.
  • the access router 115 has the “public” IP address 89.20.171.92.
  • a public IP address is accessible by a device inside or outside the LAN. Whenever a packet is sent to the LAN from a destination on the Internet 120 , the packet is sent to the router's 115 public IP address. Once received, the router 115 may then transmit the packet to the local IP address of one of the devices on the LAN.
  • a variable number of devices may be hooked up to a router 115 over the LAN.
  • the device For a device to transmit and receive data from outside the network, the device may be assigned a local IP address.
  • a router 115 may be utilized to assign IP addresses to devices on the LAN. To assign a device a local IP address, the device may send an IP address request to the router 115 , which then assigns a local IP address to the device. Each time a device is powered down, and then powered back up, it may be assigned an IP address that need not necessarily be identical to the IP address assigned to the device before being powered down.
  • DHCP is a program, executable by a router 115 , that may be used to assign a local IP address to a device on the LAN.
  • FIG. 2 illustrates a basic DHCP packet 200 according to an embodiment of the invention.
  • the request is in the form of a DHCP packet 200 .
  • the packet contains various fields of information, such as operation (op) code 205 .
  • Op code 205 is used to signify whether the packet is a request for an IP address or an assignment of an IP address. If an IP address request is sent, the op code 205 for the DHCP packet is set to “1”.
  • a DHCP server which may be located at the router 115 , responds to the request by sending a DHCP packet with op code 205 set to “2”.
  • the IP address assigned to client is stored in the “yiaddr” field 2210 .
  • a basic DHCP packet 200 does not contain the client name, most clients include an optional field in the “options” field 220 of the DHCP request packet 200 .
  • FIG. 3 illustrates an additional host option field 300 portion of a DHCP packet according to an embodiment of the invention.
  • the host option field 300 is utilized to store the symbolic name of a device requesting an IP address.
  • the host option field 300 is located in the options field 220 of the DHCP request packet 200 .
  • the host option field 300 is comprised of a plurality of bytes.
  • the first byte 305 represents the DHCP option code for the option field.
  • a DHCP option code of “12” represents the host name option.
  • the second byte 310 represents the length of the host name.
  • FIG. 3 shows the bytes in which a host name having four characters may be stored.
  • the first byte 315 , the second byte 320 , the third byte 325 , and the fourth byte 330 may be stored in consecutive bytes in the host option field 300 .
  • the second byte would be set to “6”, the length of the host name. There would then be “6” bytes in which one of the letters of the name would be stored, respectively.
  • the router 115 does not have any information concerning the name of any devices on the LAN before those devices send an IP address request.
  • the router 115 receives an IP address request in the form of a DHCP packet, the router 115 takes the symbolic name of the device from the host option field 300 , assigns the IP address, and maintains a table in which the assigned IP address is associated with the symbolic name of the device. For example, if the DHCP server assigns the local IP address 10.0.01.1 to the device having the symbolic name “Victor”, the table will associate the name “Victor” with the local IP address 10.0.1.1.
  • FIG. 4 illustrates a process by which a device is assigned a local IP address according to an embodiment of the invention.
  • the device is booted 400 .
  • the device sends 405 an IP request to the DHCP server.
  • the DHCP server is typically located at the router 115 .
  • the device need not have knowledge of the location of the DHCP server when booted.
  • a device may be booted, and then may send a DHCP packet 200 requesting an assignment of an IP address to all devices on the LAN.
  • the device having the DHCP server will receive a DHCP packet 200 , assign an IP address to the device, and send a DHCP response packet to the device.
  • the DHCP response packet contains the local IP address assigned to the device.
  • the DHCP server receives the IP request.
  • the DHCP server then assigns 415 a local IP address to the device, and stores the symbolic name of the device in memory.
  • the symbolic name of the device is associated 420 with the assigned IP address and is then stored in memory.
  • a DHCP response packet having the assigned IP address is sent 425 to device.
  • An embodiment of the present invention uses a table of symbolic names and assigned local IP addresses to route incoming packets to devices on the LAN.
  • the first computer 100 has a symbolic name Victor.
  • the first computer 100 initially boots, it sends a DHCP IP address request packet to the DHCP server at the router 115 .
  • the router 115 then assigns the first computer 100 a local IP address.
  • the local IP address is “10.0.1.1”.
  • the router 115 uses the association table to determine which device on the LAN has the symbolic name “Victor.” In such an instance, the packet would be received by the router 115 and sent to the first computer 100 .
  • FIG. 5 illustrates an association table 500 according to an embodiment of the present invention.
  • the association table 500 has a “Host Name” column 505 and an “Assigned IP address” column 510 .
  • the host names are “Victor”, “Hugo”, and “Yrsa”, and the assigned IP addresses are “10.0.1.1”, “10.0.1.2”, and “10.0.1.3”, respectively.
  • the device When a packet is sent from a device on the LAN to the router 115 , and then to a destination on the Internet, the device sends a packet with the device's local IP address and port number.
  • the IP address is utilized to identify the device, and the port number indicates the service on the device. For example, if the IP address “100.100.100.100” is an HTTP server, its port number is “80”, the industry standard port number for HTTP. If it is a Telnet server, its port number is “23”, the industry standard port number for Telnet.
  • An embodiment of the present invention may use NAT to present the entire LAN, and all devices located thereon, as having only the public IP address of the router 115 .
  • the public IP address of the LAN is “89.20.171.92”, the IP address of the router 115 . All packets received by the network, but meant for any of the devices on the LAN, are addressed to the public IP address of the router 115 . Therefore, the router 115 is configured to route packets to particular devices on the LAN. If the second computer 105 , with the symbolic name “Hugo”, initiates a connection to an IP address on the Internet, such as “95.10.1.5”, the router 115 creates a NAT session entry for second computer 105 .
  • the entry contains an instruction that traffic from 95.10.1.5 sent to public IP address 89.20.171.92 should be forwarded to 10.0.1.2. Also, packets sent from 10.0.1.2 are altered to contain the public IP address 89.20.171.92 as the source IP address. So when a packet from the address 95.10.1.5 arrives from the Internet, the router 115 uses the stored NAT entry and forwards the packet to 10.0.1.2.
  • the packet When a packet is sent from a device on the network to a device on the Internet outside the network, the packet contains a source IP address and port number, and a destination IP address and port number.
  • the packet would contain the source IP address “10.0.1.1” and a source port number.
  • the source port number is chosen by the first computer 100 . For example, the first computer may assign the port number “1050” as the source port.
  • the destination IP address is “100.100.100.100” and the destination port number is “80”.
  • the router 115 receives the packet, it first verifies that no other devices on the LAN are already using the source port “1050”. If any other devices are using that port number, the router assigns a new source port number to the packet. Also, the router 115 changes the source IP address from 10.0.0.1 to the public IP address of the router, “89.20.171.92”.
  • FIG. 6 illustrates a process by which a packet is sent from a local device to a destination address on the Internet according to an embodiment of the present invention.
  • the local device sends 600 a packet to the router 115 .
  • the packet contains a source local IP address and port number, and a destination IP address and port number.
  • the router 115 translates 605 the local IP address to the public IP address. More specifically, the router 115 removes the local IP address from the packet and inserts the public IP address. In the embodiment illustrated in FIG. 1 , the public IP address “89.20.171.92” would be inserted into the packet.
  • the router 115 changes 610 the source port number in the packet if another local device is already using the same source port number.
  • the router 115 sends 615 the packet to the destination IP address over the Internet.
  • the router 115 When a connection is not initiated by a device on the LAN, the router 115 is configured to send a received packet to the correct device on the LAN.
  • the system uses the association table 500 to determine which local device to route an incoming packet. For example, an incoming packet may have the symbolic name of the destination device stored in the packet payload of the incoming packet. The system can then extract the symbolic name from the packet, determine the local IP address from the association table 500 , and route the packet to the correct local device. For example, in the embodiment shown in FIG.
  • a packet sent the public IP address “89.20.171.92” addressed to the symbolic name “yrsa@89.20.171.92” would be routed to the local IP address “10.0.1.3”, which corresponds to the symbolic name “Yrsa”.
  • An SIP IP telephone connection can therefore be initiated by a device outside the LAN by addressing a packet to the public IP address of the router 115 , and including the symbolic name “yrsa@89.20.171.92” in the packet payload.
  • FIG. 7 illustrates a process by which packets are received and routed to the destination device on a local network.
  • the router 155 receives 700 a packet from a remote location on the Internet.
  • the router 115 searches 705 in the packet payload for a symbolic name address.
  • the router 115 utilizes the association table 500 to match 710 the symbolic name with an associated local IP address, if there is one.
  • the router 115 sends 715 the packet to the local device having the located symbolic name.

Abstract

A system for using Dynamic Host Configuration Protocol (DHCP) address assignments to determine a local destination address of a received packet in a Network Address Translation (NAT) environment. The system includes a DHCP server to assign local IP addresses to devices on a network. The system has a NAT device to execute network address translation, and a packet device to receive packets. The system further includes an addressing device to determine the local destination address of a packet received by the packet device. The addressing device uses an association table created from symbolic names of the devices on the network and the local IP addresses associated with the devices.

Description

    BACKGROUND OF THE INVENTION
  • 1. Field of the Invention
  • This invention relates to the field of network address assigning, and, more specifically, to a system, method, and apparatus for enabling Network Address Translation (NAT) of incoming Session Initiation Protocol (SIP) connections based on Dynamic Host Configuration Protocol (DHCP) address assignments.
  • 2. Background of the Invention
  • Local area networks (LANs) have been used with network devices such as personal computers. A LAN typically has a set number of unique Internet Protocol (IP) addresses for all of the devices on the LAN. More specifically, multiple computers on the LAN may be represented by the same IP address and use the same router(s). In such embodiments, there may be 10 computers, for example, assigned to one router, where the router has its own unique IP address.
  • In such a LAN, Network Address Translation (NAT) allows a single device, such as a router, to act as an agent between the Internet, or “public network”, and a local, or “private”, network. This means that only a single, unique IP address is required to represent an entire group of computers.
  • In such an embodiment, a major problem with using NAT is to locate the correct device on the internal network when a packet from the Internet arrives at the router, because all packets received from the Internet are addressed to the router and not to the devices behind the router. Configuring static mappings in the router can, in some cases, solve the problem. For example, the router may be configured to send all World Wide Web (WEB) traffic to a specific PC behind a router, and send all File Transfer Protocol (FTP) traffic to a different specified PC behind the router. However, the problem with this type of static mapping is that it requires specific configuration of the router, which may be expensive for an ISP shipping thousands of routers. Moreover, it is problematic if several PCs are performing the same service (FTP, WEB, etc.).
  • When a connection is initiated from a device on the internal network to an external device, the access device can always establish the NAT mapping without the use of any additional information. However, when using NAT, connections may only be made from inside a local network to a location outside of the network. A device outside the network cannot connect to a device on the local network without the router being specifically configured to do so. Therefore, the prior art suffers from a serious inefficiency in that a connection cannot be initiated with a device on a LAN by a device outside the LAN without specific configuration of the router at the LAN.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 illustrates a general overview of a system according to an embodiment of the invention;
  • FIG. 2 illustrates a basic DHCP packet according to an embodiment of the invention;
  • FIG. 3 illustrates an additional option field portion of a DHCP packet according to an embodiment of the invention;
  • FIG. 4 illustrates a process by which a device is assigned a local IP address according to an embodiment of the invention;
  • FIG. 5 illustrates an association table according to an embodiment of the present invention;
  • FIG. 6 illustrates a process by which a packet is sent from a local device to a destination address on the Internet according to an embodiment of the present invention; and
  • FIG. 7 illustrates a process by which packets are received and routed to the destination device on a local network.
  • DETAILED DESCRIPTION
  • An embodiment of the present invention includes a device that simultaneously acts as a Dynamic Host Configuration Protocol (DHCP) server and a Network Translation Address, (NAT) apparatus. The device may be used within an access router connected to the Internet. Such a device routes incoming packets to devices on a network based upon symbolic names acquired by a DHCP program running on the DHCP server. The device allows an incoming Session Initiation Protocol (SIP) Internet Protocol (IP) call originating from the Internet to be routed to the correct device on the Local Area Network (LAN) segment that uses a private IP address.
  • DHCP is a software program that automatically assigns IP addresses to client stations logging onto an IP network. It eliminates the need to manually assign permanent IP addresses. DHCP software typically runs on servers and is also found in network devices such as Integrated Services Digital Network (ISDN) routers and modem routers that allow multiple users access to the Internet. NAT is an Internet Engineering Task Force (IETF) standard that allows an organization to present itself to the Internet with one address. NAT converts the address of each LAN node into one IP address for the Internet and vice versa. It also serves as a firewall by keeping individual IP addresses hidden from the outside world. SIP is a protocol that provides IP telephony services, such as realtime, interactive voice and videoconferencing over LANs and the Internet. It allows any combination of voice, video and data to be transported.
  • FIG. 1 illustrates a general overview of the system according to an embodiment of the invention. In an embodiment of the invention, a number of devices are coupled to an access router 115 capable of transmitting and receiving data via the Internet. FIG. 1 illustrates an embodiment where a first computer 100, a second computer 105, and a SIP IP telephone 110 all reside on a LAN connected to the router 115. The first computer 100 has a host name, or symbolic name, “Victor.” The second computer 105 has a symbolic name “Hugo.” The SIP IP telephone 110 has the symbolic name “Yrsa.”
  • The first computer 100, the second computer 105, and the SIP IP telephone 110 are all connected to the access router 115, which serves as the pathway for communication between them and destinations on the Internet 120. For the first computer 100 to send data to a destination address on the Internet, the first computer 100 must send a packet to the router 115, which then sends the packet to the destination address on the Internet 120.
  • In order for a device on the LAN to receive packets of data from a site on the Internet, the router 115 must be configured to route certain packets to a particular device. In other words, the router 115 must extrapolate, from a received packet, the destination address of the packet. To determine which packets must be routed to which devices on the LAN, the router 115 typically has to have prior knowledge about each of the devices.
  • To receive and transmit packets over the LAN, or to an Internet site outside of the LAN, a device must have an IP address. As shown in FIG. 1, the first computer 100 has the “private” IP address 10.0.1.1., the second computer 105 has the private IP address 10.0.1.2, and the SIP IP telephone 110 has the private IP address 10.0.1.3. A private IP address is an IP address that is not known or directly accessible by a device outside the LAN. In this example, the access router 115 has the “public” IP address 89.20.171.92. A public IP address is accessible by a device inside or outside the LAN. Whenever a packet is sent to the LAN from a destination on the Internet 120, the packet is sent to the router's 115 public IP address. Once received, the router 115 may then transmit the packet to the local IP address of one of the devices on the LAN.
  • In an embodiment of the invention, a variable number of devices may be hooked up to a router 115 over the LAN. For a device to transmit and receive data from outside the network, the device may be assigned a local IP address. A router 115 may be utilized to assign IP addresses to devices on the LAN. To assign a device a local IP address, the device may send an IP address request to the router 115, which then assigns a local IP address to the device. Each time a device is powered down, and then powered back up, it may be assigned an IP address that need not necessarily be identical to the IP address assigned to the device before being powered down. DHCP is a program, executable by a router 115, that may be used to assign a local IP address to a device on the LAN.
  • FIG. 2 illustrates a basic DHCP packet 200 according to an embodiment of the invention. When a device on the network sends an IP address assignment request to the router 115, the request is in the form of a DHCP packet 200. The packet contains various fields of information, such as operation (op) code 205. Op code 205 is used to signify whether the packet is a request for an IP address or an assignment of an IP address. If an IP address request is sent, the op code 205 for the DHCP packet is set to “1”. A DHCP server, which may be located at the router 115, responds to the request by sending a DHCP packet with op code 205 set to “2”.
  • In the DHCP response, the IP address assigned to client is stored in the “yiaddr” field 2210. Although a basic DHCP packet 200 does not contain the client name, most clients include an optional field in the “options” field 220 of the DHCP request packet 200.
  • FIG. 3 illustrates an additional host option field 300 portion of a DHCP packet according to an embodiment of the invention. The host option field 300 is utilized to store the symbolic name of a device requesting an IP address. The host option field 300 is located in the options field 220 of the DHCP request packet 200. The host option field 300 is comprised of a plurality of bytes. The first byte 305 represents the DHCP option code for the option field. A DHCP option code of “12” represents the host name option. The second byte 310 represents the length of the host name. FIG. 3 shows the bytes in which a host name having four characters may be stored. The first byte 315, the second byte 320, the third byte 325, and the fourth byte 330 may be stored in consecutive bytes in the host option field 300. In the event that the symbolic name “Victor” were to be stored in the host option field 300, the second byte would be set to “6”, the length of the host name. There would then be “6” bytes in which one of the letters of the name would be stored, respectively.
  • In an embodiment of the invention, the router 115 does not have any information concerning the name of any devices on the LAN before those devices send an IP address request. When the router 115 receives an IP address request in the form of a DHCP packet, the router 115 takes the symbolic name of the device from the host option field 300, assigns the IP address, and maintains a table in which the assigned IP address is associated with the symbolic name of the device. For example, if the DHCP server assigns the local IP address 10.0.01.1 to the device having the symbolic name “Victor”, the table will associate the name “Victor” with the local IP address 10.0.1.1.
  • FIG. 4 illustrates a process by which a device is assigned a local IP address according to an embodiment of the invention. First, the device is booted 400. Next, the device sends 405 an IP request to the DHCP server. The DHCP server is typically located at the router 115. The device need not have knowledge of the location of the DHCP server when booted. In an embodiment of the present invention, a device may be booted, and then may send a DHCP packet 200 requesting an assignment of an IP address to all devices on the LAN. The device having the DHCP server will receive a DHCP packet 200, assign an IP address to the device, and send a DHCP response packet to the device. The DHCP response packet contains the local IP address assigned to the device.
  • Next, at step 410, the DHCP server receives the IP request. The DHCP server then assigns 415 a local IP address to the device, and stores the symbolic name of the device in memory. The symbolic name of the device is associated 420 with the assigned IP address and is then stored in memory. Finally, a DHCP response packet having the assigned IP address is sent 425 to device.
  • An embodiment of the present invention uses a table of symbolic names and assigned local IP addresses to route incoming packets to devices on the LAN. Referring to FIG. 1, the first computer 100 has a symbolic name Victor. When the first computer 100 initially boots, it sends a DHCP IP address request packet to the DHCP server at the router 115. The router 115 then assigns the first computer 100 a local IP address. In this case, the local IP address is “10.0.1.1”. If a packet is received, from outside the LAN, by the router 115 and is addressed to “Victor” at the public IP address “89.20.171.92”, the router 115 uses the association table to determine which device on the LAN has the symbolic name “Victor.” In such an instance, the packet would be received by the router 115 and sent to the first computer 100.
  • FIG. 5 illustrates an association table 500 according to an embodiment of the present invention. After all of the devices on the LAN illustrated in FIG. 1 have been assigned local IP addresses, the association table 500 for the LAN is complete. The association table 500 has a “Host Name” column 505 and an “Assigned IP address” column 510. For the LAN illustrated in FIG. 1, the host names are “Victor”, “Hugo”, and “Yrsa”, and the assigned IP addresses are “10.0.1.1”, “10.0.1.2”, and “10.0.1.3”, respectively.
  • When a packet is sent from a device on the LAN to the router 115, and then to a destination on the Internet, the device sends a packet with the device's local IP address and port number. The IP address is utilized to identify the device, and the port number indicates the service on the device. For example, if the IP address “100.100.100.100” is an HTTP server, its port number is “80”, the industry standard port number for HTTP. If it is a Telnet server, its port number is “23”, the industry standard port number for Telnet.
  • An embodiment of the present invention may use NAT to present the entire LAN, and all devices located thereon, as having only the public IP address of the router 115. In the example illustrated in FIG. 1, the public IP address of the LAN is “89.20.171.92”, the IP address of the router 115. All packets received by the network, but meant for any of the devices on the LAN, are addressed to the public IP address of the router 115. Therefore, the router 115 is configured to route packets to particular devices on the LAN. If the second computer 105, with the symbolic name “Hugo”, initiates a connection to an IP address on the Internet, such as “95.10.1.5”, the router 115 creates a NAT session entry for second computer 105. The entry contains an instruction that traffic from 95.10.1.5 sent to public IP address 89.20.171.92 should be forwarded to 10.0.1.2. Also, packets sent from 10.0.1.2 are altered to contain the public IP address 89.20.171.92 as the source IP address. So when a packet from the address 95.10.1.5 arrives from the Internet, the router 115 uses the stored NAT entry and forwards the packet to 10.0.1.2.
  • When a packet is sent from a device on the network to a device on the Internet outside the network, the packet contains a source IP address and port number, and a destination IP address and port number. If the first computer 100, “Victor”, sends a packet destined for a HTTP server at the IP address “100.100.100.100”, the packet would contain the source IP address “10.0.1.1” and a source port number. The source port number is chosen by the first computer 100. For example, the first computer may assign the port number “1050” as the source port. The destination IP address is “100.100.100.100” and the destination port number is “80”. When the router 115 receives the packet, it first verifies that no other devices on the LAN are already using the source port “1050”. If any other devices are using that port number, the router assigns a new source port number to the packet. Also, the router 115 changes the source IP address from 10.0.0.1 to the public IP address of the router, “89.20.171.92”.
  • FIG. 6 illustrates a process by which a packet is sent from a local device to a destination address on the Internet according to an embodiment of the present invention. First, the local device sends 600 a packet to the router 115. The packet contains a source local IP address and port number, and a destination IP address and port number. Next, the router 115 translates 605 the local IP address to the public IP address. More specifically, the router 115 removes the local IP address from the packet and inserts the public IP address. In the embodiment illustrated in FIG. 1, the public IP address “89.20.171.92” would be inserted into the packet. The router 115 then changes 610 the source port number in the packet if another local device is already using the same source port number. Finally, the router 115 sends 615 the packet to the destination IP address over the Internet.
  • When a connection is not initiated by a device on the LAN, the router 115 is configured to send a received packet to the correct device on the LAN. In an embodiment of the present invention, the system uses the association table 500 to determine which local device to route an incoming packet. For example, an incoming packet may have the symbolic name of the destination device stored in the packet payload of the incoming packet. The system can then extract the symbolic name from the packet, determine the local IP address from the association table 500, and route the packet to the correct local device. For example, in the embodiment shown in FIG. 1, a packet sent the public IP address “89.20.171.92” addressed to the symbolic name “yrsa@89.20.171.92” would be routed to the local IP address “10.0.1.3”, which corresponds to the symbolic name “Yrsa”. An SIP IP telephone connection can therefore be initiated by a device outside the LAN by addressing a packet to the public IP address of the router 115, and including the symbolic name “yrsa@89.20.171.92” in the packet payload.
  • FIG. 7 illustrates a process by which packets are received and routed to the destination device on a local network. First, the router 155 receives 700 a packet from a remote location on the Internet. Next, the router 115 searches 705 in the packet payload for a symbolic name address. The router 115 utilizes the association table 500 to match 710 the symbolic name with an associated local IP address, if there is one. Finally, the router 115 sends 715 the packet to the local device having the located symbolic name.
  • While the description above refers to particular embodiments of the present invention, it will be understood that many modifications may be made without departing from the spirit thereof. The accompanying claims are intended to cover such modifications as would fall within the true scope and spirit of the present invention. The presently disclosed embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims, rather than the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.

Claims (10)

1-26. (canceled)
27. A method, comprising:
receiving, at a first network device, respective Dynamic Host Configuration Protocol (DHCP) requests issued by respective devices in a set of devices, respective ones of the DHCP requests including a symbolic identifier of the device issuing the DHCP request in an options field of the DHCP request;
responding, by the first network device, to the respective DHCP requests with respective DHCP responses, respective ones of the DHCP responses including an Internet Protocol address assigned by the first network device to the device issuing the DHCP request;
storing, by the first network device, data associating the respective Internet Protocol addresses assigned by the first network device with the, respective, symbolic identifiers;
receiving, at the first network device, a Session Initiation Protocol (SIP) packet to initiate an SIP Internet Protocol telephone connection from a device other than a device that issues a DHCP request to the first network device, the SIP packet including one of the symbolic identifiers and the Internet Protocol address of the first network device;
performing a lookup of the one of the symbolic identifiers in the received SIP packet in the data associating the respective Internet Protocol addresses assigned by the first network device with the, respective, symbolic identifiers; and
routing an SIP packet to initiate an Internet Protocol telephone connection to the device corresponding to the Internet Protocol address associated with the symbolic identifier included in the received SIP packet.
28. The method of claim 27, wherein the received SIP packet includes the one of the symbolic identifiers and the Internet Protocol of the first network device in a format of:
symbolic-identifier@Internet-Protocol-address-of-the-first-network-device.
29. The method of claim 27, further comprising:
receiving, at the first network device from a one of the set of devices that issued a DHCP request to the first network device, an SIP packet to initiate an SIP Internet Protocol telephone connection that includes the Internet Protocol address of the device that issued a DHCP request to the first network device and a destination Internet Protocol address; and
transmitting an SIP packet toward the destination Internet Protocol address that replaces the Internet Protocol address of the device that issued a DHCP request to the first network device with the Internet Protocol address of the first network device.
30. An apparatus, comprising logic to:
receive, at a apparatus, respective Dynamic Host Configuration Protocol (DHCP) requests issued by respective devices in a set of devices, respective ones of the DHCP requests including a symbolic identifier of the device issuing the DHCP request in an options field of the DHCP request;
respond, by the apparatus, to the respective DHCP requests with respective DHCP responses, respective ones of the DHCP responses including an Internet Protocol address assigned by the apparatus to the device issuing the DHCP request;
store, by the apparatus, data associating the respective Internet Protocol addresses assigned by the apparatus with the, respective, symbolic identifiers;
receive, at the apparatus, a Session Initiation Protocol (SIP) packet to initiate an SIP Internet Protocol telephone connection from a device other than a device that issues a DHCP request to the apparatus, the SIP packet including one of the symbolic identifiers and the Internet Protocol address of the apparatus;
perform a lookup of the one of the symbolic identifiers in the received SIP packet in the data associating the respective Internet Protocol addresses assigned by the apparatus with the, respective, symbolic identifiers; and
route an SIP packet to initiate an Internet Protocol telephone connection to the device corresponding to the Internet Protocol address associated with the symbolic identifier included in the received SIP packet.
31. The apparatus of claim 30, wherein the received SIP packet includes the one of the symbolic identifiers and the Internet Protocol of the apparatus in a format of:
symbolic-identifier@Internet-Protocol-address-of-the-apparatus.
32. The apparatus of claim 30, further comprising logic to:
receive, at the apparatus from a one of the set of devices that issued a DHCP request to the apparatus, an SIP packet to initiate an SIP Internet Protocol telephone connection that includes the Internet Protocol address of the device that issued a DHCP request to the apparatus and a destination Internet Protocol address; and
transmit an SIP packet toward the destination Internet Protocol address that replaces the Internet Protocol address of the device that issued a DHCP request to the apparatus with the Internet Protocol address of the apparatus.
33. A system, comprising:
multiple networked devices including a first network device; and
logic to provide Internet Protocol telephone connections by:
receiving, at a first network device, respective Dynamic Host Configuration Protocol (DHCP) requests issued by respective devices in a set of devices, respective ones of the DHCP requests including a symbolic identifier of the device issuing the DHCP request in an options field of the DHCP request;
responding, by the first network device, to the respective DHCP requests with respective DHCP responses, respective ones of the DHCP responses including an Internet Protocol address assigned by the first network device to the device issuing the DHCP request;
storing, by the first network-device, data associating the respective Internet Protocol addresses assigned by the first network device with the, respective, symbolic identifiers;
receiving, at the first network device, a Session Initiation Protocol (SIP) packet to initiate an SIP Internet Protocol telephone connection from a device other than a device that issues a DHCP request to the first network device, the SIP packet including one of the symbolic identifiers and the Internet Protocol address of the first network device;
performing a lookup of the one of the symbolic identifiers in the received SIP packet in the data associating the respective Internet Protocol addresses assigned by the first network device with the, respective, symbolic identifiers; and
routing an SIP packet to initiate an Internet Protocol telephone connection to the device corresponding to the Internet Protocol address associated with the symbolic identifier included in the received SIP packet.
34. The system of claim 33, wherein the received SIP packet includes the one of the symbolic identifiers and the Internet Protocol of the first network device in a format of:
symbolic-identifier@Internet-Protocol-address-of-the-first-network-device.
35. The system of claim 33, further comprising:
receiving, at the first network device from a one of the set of devices that issued a DHCP request to the first network device, an SIP packet to initiate an SIP Internet Protocol telephone connection that includes the Internet Protocol address of the device that issued a DHCP request to the first network device and a destination Internet Protocol address; and
transmitting an SIP packet toward the destination Internet Protocol address that replaces the Internet Protocol address of the device that issued a DHCP request to the first network device with the Internet Protocol address of the first network device.
US11/490,833 2001-06-27 2006-07-21 Method enabling network address translation of incoming session initiation protocol connections base on dynamic host configuration protocol address assignments Abandoned US20060274749A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/490,833 US20060274749A1 (en) 2001-06-27 2006-07-21 Method enabling network address translation of incoming session initiation protocol connections base on dynamic host configuration protocol address assignments

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/892,932 US7106739B2 (en) 2001-06-27 2001-06-27 Method enabling network address translation of incoming session initiation protocol connections based on dynamic host configuration protocol address assignments
US11/490,833 US20060274749A1 (en) 2001-06-27 2006-07-21 Method enabling network address translation of incoming session initiation protocol connections base on dynamic host configuration protocol address assignments

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/892,932 Continuation US7106739B2 (en) 2001-06-27 2001-06-27 Method enabling network address translation of incoming session initiation protocol connections based on dynamic host configuration protocol address assignments

Publications (1)

Publication Number Publication Date
US20060274749A1 true US20060274749A1 (en) 2006-12-07

Family

ID=25400733

Family Applications (2)

Application Number Title Priority Date Filing Date
US09/892,932 Expired - Fee Related US7106739B2 (en) 2001-06-27 2001-06-27 Method enabling network address translation of incoming session initiation protocol connections based on dynamic host configuration protocol address assignments
US11/490,833 Abandoned US20060274749A1 (en) 2001-06-27 2006-07-21 Method enabling network address translation of incoming session initiation protocol connections base on dynamic host configuration protocol address assignments

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/892,932 Expired - Fee Related US7106739B2 (en) 2001-06-27 2001-06-27 Method enabling network address translation of incoming session initiation protocol connections based on dynamic host configuration protocol address assignments

Country Status (6)

Country Link
US (2) US7106739B2 (en)
EP (1) EP1400092B1 (en)
CN (1) CN1611053B (en)
AT (1) ATE524913T1 (en)
TW (1) TWI301024B (en)
WO (1) WO2003003697A1 (en)

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060173955A1 (en) * 2005-01-28 2006-08-03 Phoenix Contact Gmbh & Co. Kg Method and apparatus for allocating network subscriber device addresses in a profinet IO network
US20080259941A1 (en) * 2007-04-19 2008-10-23 At&T Knowledge Ventures, L.P. System and apparatus for managing ip addresses
US20100135313A1 (en) * 2002-05-06 2010-06-03 Foundry Networks, Inc. Network routing system for enhanced efficiency and monitoring capability
US20110069711A1 (en) * 2009-09-21 2011-03-24 Brocade Communications Systems, Inc. PROVISIONING SINGLE OR MULTISTAGE NETWORKS USING ETHERNET SERVICE INSTANCES (ESIs)
US20110185085A1 (en) * 2009-09-08 2011-07-28 Wichorus, Inc. Network Address Translation Based on Recorded Application State
US20110182183A1 (en) * 2009-09-08 2011-07-28 Wichorus, Inc. Method and Apparatus for Network Address Translation
US20110182290A1 (en) * 2009-09-08 2011-07-28 Wichorus, Inc. Method and Apparatus for Performing Network Address Translation
US20120102146A1 (en) * 2009-07-03 2012-04-26 Qin Wu Method, device and system for obtaining local domain name
US8671219B2 (en) 2002-05-06 2014-03-11 Foundry Networks, Llc Method and apparatus for efficiently processing data packets in a computer network
US8718051B2 (en) 2003-05-15 2014-05-06 Foundry Networks, Llc System and method for high speed packet transmission
US8730961B1 (en) 2004-04-26 2014-05-20 Foundry Networks, Llc System and method for optimizing router lookup
US8964754B2 (en) 2000-11-17 2015-02-24 Foundry Networks, Llc Backplane interface adapter with error control and redundant fabric
US8989202B2 (en) 2002-05-06 2015-03-24 Foundry Networks, Llc Pipeline method and system for switching packets
US9030943B2 (en) 2006-11-22 2015-05-12 Foundry Networks, Llc Recovering from failures without impact on data traffic in a shared bus architecture
US9112780B2 (en) 2007-01-11 2015-08-18 Foundry Networks, Llc Techniques for processing incoming failure detection protocol packets
US9338100B2 (en) 2004-03-26 2016-05-10 Foundry Networks, Llc Method and apparatus for aggregating input data streams
US9378005B2 (en) 2005-12-28 2016-06-28 Foundry Networks, Llc Hitless software upgrades
US20190306112A1 (en) * 2016-07-08 2019-10-03 Waldemar Augustyn Network communication method and apparatus
US20220191169A1 (en) * 2019-04-04 2022-06-16 Telefonaktiebolaget Lm Ericsson (Publ) Service handling in software defined networking based container orchestration systems

Families Citing this family (53)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003124962A (en) * 2001-10-18 2003-04-25 Fujitsu Ltd Packet transferring apparatus and method, and semiconductor device
KR100485769B1 (en) * 2002-05-14 2005-04-28 삼성전자주식회사 Apparatus and method for offering connection between network devices located in different home networks
US20030225910A1 (en) * 2002-05-30 2003-12-04 Albert Pan Host resolution for IP networks with NAT
KR100886550B1 (en) * 2002-09-17 2009-03-02 삼성전자주식회사 Apparatus and method for allocating the ip address
JP2004120534A (en) * 2002-09-27 2004-04-15 Matsushita Electric Ind Co Ltd Router, repeater and forwarding method
KR100514196B1 (en) * 2003-02-14 2005-09-13 삼성전자주식회사 System and method for Controlling network address translation and session
CA2422334C (en) * 2003-03-17 2009-06-09 British Telecommunications Public Limited Company Authentication of network users
JP2005051473A (en) * 2003-07-28 2005-02-24 Sony Corp Network interconnection device, network interconnection method, name solving device, and computer program
CN100359893C (en) * 2003-08-28 2008-01-02 华为技术有限公司 Method for realizing address translation application gateway by host mode
US20050076141A1 (en) * 2003-09-19 2005-04-07 Williams Aidan Michael Use of an autoconfigured namespace for automatic protocol proxying
US20050097610A1 (en) * 2003-11-03 2005-05-05 Pedlow Leo M.Jr. Distribution of preferences, provisioning and entitlements in clustered, distributed entertainment networks
US8108496B2 (en) * 2004-04-07 2012-01-31 American Power Conversion Corporation Method and apparatus for selecting forwarding modes
US8711839B2 (en) * 2004-04-29 2014-04-29 General Instrument Corporation Device and method to automatically configure port forwarding
US7912072B1 (en) * 2004-06-21 2011-03-22 Nortel Networks Limited Communication with a remote device
US7864709B2 (en) * 2004-06-25 2011-01-04 Apple Inc. Method and apparatus for looking up configuration information for a network node
US7948890B2 (en) 2004-12-14 2011-05-24 Industrial Technology Research Institute System and method for providing a communication channel
CN1866951B (en) * 2005-05-20 2010-09-22 华为技术有限公司 Method and system for detecting shared access host machine in network
CN1863143A (en) * 2005-08-09 2006-11-15 华为技术有限公司 Method, system and apparatus for implementing Web server access
US20070097970A1 (en) * 2005-11-01 2007-05-03 Georgios Margaritis Packet retransmitter
EP1980108A2 (en) 2006-01-20 2008-10-15 Nxp B.V. Replacement of frame data in a video stream signal
US8416691B1 (en) * 2006-04-27 2013-04-09 Alcatel Lucent Associating hosts with subscriber and service based requirements
CN101179477B (en) * 2006-11-10 2010-12-08 中国科学院声学研究所 Method for implementing built-in router
US8929360B2 (en) * 2006-12-07 2015-01-06 Cisco Technology, Inc. Systems, methods, media, and means for hiding network topology
CN102148879A (en) * 2010-10-22 2011-08-10 华为技术有限公司 Port mapping method and device and communication system
AU2013277922B2 (en) * 2012-06-18 2017-01-19 Quick Grip Staples (Hk) Limited An accessory for a fastening gun
US9729439B2 (en) 2014-09-26 2017-08-08 128 Technology, Inc. Network packet flow controller
US10277506B2 (en) 2014-12-08 2019-04-30 128 Technology, Inc. Stateful load balancing in a stateless network
KR102145935B1 (en) * 2014-12-11 2020-08-21 비트데펜더 아이피알 매니지먼트 엘티디 Systems and methods for securing network endpoints
US20160261457A1 (en) * 2015-03-03 2016-09-08 Qualcomm Incorporated Recovering from connectivity failure at a bridging device
US9736184B2 (en) 2015-03-17 2017-08-15 128 Technology, Inc. Apparatus and method for using certificate data to route data
US9729682B2 (en) 2015-05-18 2017-08-08 128 Technology, Inc. Network device and method for processing a session using a packet signature
US9762485B2 (en) 2015-08-24 2017-09-12 128 Technology, Inc. Network packet flow controller with extended session management
US9871748B2 (en) 2015-12-09 2018-01-16 128 Technology, Inc. Router with optimized statistical functionality
US9985883B2 (en) 2016-02-26 2018-05-29 128 Technology, Inc. Name-based routing system and method
US10205651B2 (en) 2016-05-13 2019-02-12 128 Technology, Inc. Apparatus and method of selecting next hops for a session
US10298616B2 (en) 2016-05-26 2019-05-21 128 Technology, Inc. Apparatus and method of securing network communications
US10841206B2 (en) 2016-05-31 2020-11-17 128 Technology, Inc. Flow modification including shared context
US11075836B2 (en) 2016-05-31 2021-07-27 128 Technology, Inc. Reverse forwarding information base enforcement
US10257061B2 (en) 2016-05-31 2019-04-09 128 Technology, Inc. Detecting source network address translation in a communication system
US10200264B2 (en) 2016-05-31 2019-02-05 128 Technology, Inc. Link status monitoring based on packet loss detection
US10091099B2 (en) 2016-05-31 2018-10-02 128 Technology, Inc. Session continuity in the presence of network address translation
US9832072B1 (en) 2016-05-31 2017-11-28 128 Technology, Inc. Self-configuring computer network router
US10009282B2 (en) 2016-06-06 2018-06-26 128 Technology, Inc. Self-protecting computer network router with queue resource manager
US9985872B2 (en) 2016-10-03 2018-05-29 128 Technology, Inc. Router with bilateral TCP session monitoring
US10630507B2 (en) * 2016-11-29 2020-04-21 Ale International System for and method of establishing a connection between a first electronic device and a second electronic device
US10425511B2 (en) 2017-01-30 2019-09-24 128 Technology, Inc. Method and apparatus for managing routing disruptions in a computer network
EP4195597A1 (en) 2017-03-07 2023-06-14 128 Technology, Inc. Routing device using flow duplication
US10432519B2 (en) 2017-05-26 2019-10-01 128 Technology, Inc. Packet redirecting router
US11165863B1 (en) 2017-08-04 2021-11-02 128 Technology, Inc. Network neighborhoods for establishing communication relationships between communication interfaces in an administrative domain
US20190253341A1 (en) 2018-02-15 2019-08-15 128 Technology, Inc. Service Related Routing Method and Apparatus
CN109743402B (en) * 2019-01-31 2020-07-07 深圳云合科技有限公司 Processing method, transmission method, receiver and answering machine of answering information
WO2021188026A1 (en) * 2020-03-20 2021-09-23 Telefonaktiebolaget Lm Ericsson (Publ) Methods, host devices and computer program products for assigning communication ports
CN115428411A (en) 2020-04-23 2022-12-02 瞻博网络公司 Session monitoring using session establishment metrics

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6029203A (en) * 1997-09-26 2000-02-22 3Com Corporation Apparatus and methods for use therein for an ISDN LAN modem that provides enhanced network activity
US6108701A (en) * 1998-07-20 2000-08-22 Lucent Technologies, Inc. Soft switch extension for internet protocol applications
US6195705B1 (en) * 1998-06-30 2001-02-27 Cisco Technology, Inc. Mobile IP mobility agent standby protocol
US6614800B1 (en) * 1999-09-02 2003-09-02 International Business Machines Corporation Method and system for virtual private network administration channels
US6772227B2 (en) * 1998-01-29 2004-08-03 Ip Dynamics, Inc. Communicating between address spaces
US6822957B1 (en) * 1998-03-05 2004-11-23 3Com Corporation Distributed network address translation for a network telephony system
US6856616B1 (en) * 2000-02-29 2005-02-15 3Com Corporation System and method for providing service provider configurations for telephones using a central server in a data network telephony system
US7283519B2 (en) * 2001-04-13 2007-10-16 Esn, Llc Distributed edge switching system for voice-over-packet multiservice network
US7450560B1 (en) * 1998-03-05 2008-11-11 3Com Corporation Method for address mapping in a network access system and a network access device for use therewith

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2274050A1 (en) * 1996-12-09 1998-06-18 Motorola, Inc. System, device, and method for routing dhcp packets in a public data network
US6028848A (en) * 1997-09-26 2000-02-22 3Com Corporation Apparatus and methods for use therein for an ISDN LAN modem utilizing internal DNS and DHCP servers for transparent translation of local host names to IP addresses

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6029203A (en) * 1997-09-26 2000-02-22 3Com Corporation Apparatus and methods for use therein for an ISDN LAN modem that provides enhanced network activity
US6772227B2 (en) * 1998-01-29 2004-08-03 Ip Dynamics, Inc. Communicating between address spaces
US6822957B1 (en) * 1998-03-05 2004-11-23 3Com Corporation Distributed network address translation for a network telephony system
US7450560B1 (en) * 1998-03-05 2008-11-11 3Com Corporation Method for address mapping in a network access system and a network access device for use therewith
US6195705B1 (en) * 1998-06-30 2001-02-27 Cisco Technology, Inc. Mobile IP mobility agent standby protocol
US6108701A (en) * 1998-07-20 2000-08-22 Lucent Technologies, Inc. Soft switch extension for internet protocol applications
US6614800B1 (en) * 1999-09-02 2003-09-02 International Business Machines Corporation Method and system for virtual private network administration channels
US6856616B1 (en) * 2000-02-29 2005-02-15 3Com Corporation System and method for providing service provider configurations for telephones using a central server in a data network telephony system
US7283519B2 (en) * 2001-04-13 2007-10-16 Esn, Llc Distributed edge switching system for voice-over-packet multiservice network

Cited By (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8964754B2 (en) 2000-11-17 2015-02-24 Foundry Networks, Llc Backplane interface adapter with error control and redundant fabric
US8671219B2 (en) 2002-05-06 2014-03-11 Foundry Networks, Llc Method and apparatus for efficiently processing data packets in a computer network
US8989202B2 (en) 2002-05-06 2015-03-24 Foundry Networks, Llc Pipeline method and system for switching packets
US20100135313A1 (en) * 2002-05-06 2010-06-03 Foundry Networks, Inc. Network routing system for enhanced efficiency and monitoring capability
US9461940B2 (en) 2003-05-15 2016-10-04 Foundry Networks, Llc System and method for high speed packet transmission
US8718051B2 (en) 2003-05-15 2014-05-06 Foundry Networks, Llc System and method for high speed packet transmission
US8811390B2 (en) 2003-05-15 2014-08-19 Foundry Networks, Llc System and method for high speed packet transmission
US9338100B2 (en) 2004-03-26 2016-05-10 Foundry Networks, Llc Method and apparatus for aggregating input data streams
US8730961B1 (en) 2004-04-26 2014-05-20 Foundry Networks, Llc System and method for optimizing router lookup
US20060173955A1 (en) * 2005-01-28 2006-08-03 Phoenix Contact Gmbh & Co. Kg Method and apparatus for allocating network subscriber device addresses in a profinet IO network
US7949754B2 (en) * 2005-01-28 2011-05-24 Phoenix Contact Gmbh & Co. Kg Method and apparatus for prescribing station identifiers in a profit IO network
US9378005B2 (en) 2005-12-28 2016-06-28 Foundry Networks, Llc Hitless software upgrades
US9030943B2 (en) 2006-11-22 2015-05-12 Foundry Networks, Llc Recovering from failures without impact on data traffic in a shared bus architecture
US9112780B2 (en) 2007-01-11 2015-08-18 Foundry Networks, Llc Techniques for processing incoming failure detection protocol packets
US20080259941A1 (en) * 2007-04-19 2008-10-23 At&T Knowledge Ventures, L.P. System and apparatus for managing ip addresses
US20120102146A1 (en) * 2009-07-03 2012-04-26 Qin Wu Method, device and system for obtaining local domain name
US11363023B2 (en) 2009-07-03 2022-06-14 Huawei Technologies Co., Ltd. Method, device and system for obtaining local domain name
US10601830B2 (en) 2009-07-03 2020-03-24 Huawei Technologies Co., Ltd. Method, device and system for obtaining local domain name
US9602463B2 (en) * 2009-07-03 2017-03-21 Huawei Technologies Co., Ltd. Method, device and system for obtaining local domain name
US8990424B2 (en) * 2009-09-08 2015-03-24 Wichorus, Inc. Network address translation based on recorded application state
US9013992B2 (en) 2009-09-08 2015-04-21 Wichorus, Inc. Method and apparatus for network address translation
US20110182290A1 (en) * 2009-09-08 2011-07-28 Wichorus, Inc. Method and Apparatus for Performing Network Address Translation
US20110185085A1 (en) * 2009-09-08 2011-07-28 Wichorus, Inc. Network Address Translation Based on Recorded Application State
US20110182183A1 (en) * 2009-09-08 2011-07-28 Wichorus, Inc. Method and Apparatus for Network Address Translation
US8942233B2 (en) 2009-09-08 2015-01-27 Wichorus, Inc. Method and apparatus for performing network address translation
US9166818B2 (en) 2009-09-21 2015-10-20 Brocade Communications Systems, Inc. Provisioning single or multistage networks using ethernet service instances (ESIs)
US8599850B2 (en) 2009-09-21 2013-12-03 Brocade Communications Systems, Inc. Provisioning single or multistage networks using ethernet service instances (ESIs)
US20110069711A1 (en) * 2009-09-21 2011-03-24 Brocade Communications Systems, Inc. PROVISIONING SINGLE OR MULTISTAGE NETWORKS USING ETHERNET SERVICE INSTANCES (ESIs)
US20190306112A1 (en) * 2016-07-08 2019-10-03 Waldemar Augustyn Network communication method and apparatus
US10749840B2 (en) * 2016-07-08 2020-08-18 Waldemar Augustyn Network communication method and apparatus
US11277378B2 (en) 2016-07-08 2022-03-15 Waldemar Augustyn Network communication method and apparatus
US20220191169A1 (en) * 2019-04-04 2022-06-16 Telefonaktiebolaget Lm Ericsson (Publ) Service handling in software defined networking based container orchestration systems

Also Published As

Publication number Publication date
EP1400092A1 (en) 2004-03-24
WO2003003697A1 (en) 2003-01-09
CN1611053A (en) 2005-04-27
TWI301024B (en) 2008-09-11
US7106739B2 (en) 2006-09-12
CN1611053B (en) 2010-12-22
ATE524913T1 (en) 2011-09-15
US20030002496A1 (en) 2003-01-02
EP1400092B1 (en) 2011-09-14

Similar Documents

Publication Publication Date Title
EP1400092B1 (en) Network address translation of incoming sip connections
EP2253124B1 (en) Method and apparatus for communication of data packets between local networks
US7701952B2 (en) Packet communication method and apparatus and a recording medium storing a packet communication program
US6580717B1 (en) Packet communication method and apparatus and a recording medium storing a packet communication program
JP4130962B2 (en) System and method for using a domain name to route data sent to a destination on a network
KR100317443B1 (en) Internet protocol filter
JP3953955B2 (en) Access network
US7290060B2 (en) Network-connecting apparatus and method for providing direct connections between network devices in different private networks
US8005981B2 (en) Computer network with unique identification
JP5368459B2 (en) Support for triple operation services in user equipment
US7154891B1 (en) Translating between globally unique network addresses
JP2003087336A (en) Address conversion method
US20090041058A1 (en) Network system and an interworking apparatus
JP2004129126A (en) Address assignment system
CN1965515A (en) Arrangement for reaching IPv4 public network nodes by a node in an IPv4 private network via an IPv6 access network
US20060268863A1 (en) Transparent address translation methods
EP1187426B1 (en) Method for using a unique IP address in a private IP address domain
JPH11252172A (en) Packet generation method, information processor having its function and storage medium where packet generation program is recorded
US20080049765A1 (en) Method and system for inter working a point-to-point link and a LAN service
US7085836B1 (en) System and method for automatic private IP address selection
JP2010062757A (en) Dns proxy apparatus and dns relay method
US20060002384A1 (en) Network system and connecting method thereof
KR100562390B1 (en) Network Data Flow Identification Method and System Using Host Routing and IP Aliasing Technique
EP1432214B1 (en) Method, system and console for controlling of a radio network by means of a GTP tunnel
JP2005268888A (en) Communication system, transfer processing method, communication device, and program

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION