WO2004064356A2 - Nat server traversal by means of a relay server - Google Patents
Nat server traversal by means of a relay server Download PDFInfo
- Publication number
- WO2004064356A2 WO2004064356A2 PCT/JP2004/000259 JP2004000259W WO2004064356A2 WO 2004064356 A2 WO2004064356 A2 WO 2004064356A2 JP 2004000259 W JP2004000259 W JP 2004000259W WO 2004064356 A2 WO2004064356 A2 WO 2004064356A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- host
- server
- network
- nat
- http
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/256—NAT traversal
- H04L61/2567—NAT traversal for reachability, e.g. inquiring the address of a correspondent behind a NAT server
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/256—NAT traversal
- H04L61/2575—NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5076—Update or notification mechanisms, e.g. DynDNS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/029—Firewall traversal, e.g. tunnelling or, creating pinholes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
Definitions
- IP internet protocol
- a typical NAT is connected to the public internet on one side and has at least one global or public IP address for receiving and sending data packets from and to the public internet.
- IP Internet Protocol
- On the other side of the typical NAT is a private network, in which each network node (computer) is assigned a local arbitrary address.
- the NAT assigns arbitrary addresses to the nodes of the private network using a Dynamic host Control Protocol (DHCP) or alternatively the NAT assigns static translation addresses.
- DHCP Dynamic host Control Protocol
- the NAT provides a convenient way of providing shared and transparent communication between the public internet and the computers (attached to a private network) having a non-globally-unique IP address, i.e., an IP address that is not globally- unique.
- IP address i.e., an IP address that is not globally- unique.
- not all forms of communications are operable over NAT.
- Many types of applications require a globally-unique IP address as a termination point or require IP address consistency over the whole communication cycle.
- an IP enabled phone will typically require a globally-unique IP address to receive and send voice- transmission using the IP.
- Presence of a NAT at the receiving end of the IP phone call may block the receiver from receiving the phone IP packets.
- the presence of NATs in a network poses another type of problem as described next.
- HTTP Hypertext Transfer Protocol
- a typical webserver e.g., an HTTP server, which is not behind a NAT, is readily accessible from the public internet if it has an IP address that can be resolved using common methods like the Domain Name System (DNS).
- DNS Domain Name System
- an HTTP server on a host is assumed to use the default port number, namely 80, for a host.
- An advantage of this arrangement is that the user of the browser does not need to designate a port number in addition to the address of the host because the default port number will be assumed.
- DNS Domain Name System
- DDNS dynamic DNS
- a domain name e.g., 'www.name.com'
- URL universal resource locator
- most users of browsers have no understanding that a domain name of an HTTP server maps to a port number of the host as well as an address of the host because most users have never had to provide a port number.
- TCP/IP allows multiple applications to run on a single computer using a variety of port numbers.
- a NAT is used by a private network to share an IP address, then the port addresses are shielded behind the NAT from the outside network. This situation can be further complicated by presence of a firewall with a security policy that does not allow access to specific ports of the computers on the private network as described next.
- a port-forwarding solution creates a "tunnel" through the firewall so that external users from the public internet can access a specific computer in the private network using the designated port for the tunnel.
- a port forwarding solution has a maximum number of about five forwarded port entries.
- many applications like network-gaming, instant messaging and collaboration software may require access to previously "unopened" specific TCP/UDP ports from the external public internet. Creating all the required tunnels for such applications can be an impractical task for a typical user, since the tunnel configuration process can be complicated and confusing.
- Port forwarding is typically a kind of functionality provided by a router, hence it typically raises a need for a specific router that has an inbuilt port forwarding capability.
- NAT Network Address Translation
- DDNS Dynamic Domain Name System
- FQDN Fully Qualified Domain Name
- a DDNS trying to route packets to an IP address due to a FQDN access request will fail since the NAT- assigned private address is invisible to the public internet side of the NAT.
- DMZ an acronym for De-Militarized Zone
- DMZ allows a machine behind the NAT to operate as if it is directly connected to the internet.
- DMZ like port forwarding discussed above, can be confusing to configure for a typical user, since it requires user expertise to configure it.
- DMZ cannot be used to open-up all machines of a network to the public internet.
- DMZ exposes a given machine to all the vulnerabilities that are associated with a direct connection to the internet, since it overrides the firewall protection.
- neither DMZ nor port forwarding is a satisfactory solution to the problem of transparent NAT traversal that requires no or minimum user effort to implement.
- UnP Universal Plug-and-Play
- UPnP can provide the public IP address to the client behind the NAT.
- UPnP facilities are typically provided by the router itself. But the drawback of this approach lies in the special hardware requirement in the form of a router that is UPnP compliant.
- protocols like TURN (Traversal Using Relay NAT), STUN (Simple Traversal of UDP through NAT), SPAN-A (Simple Protocol for Augmenting NATs), etc.
- STUN can detect the presence of a NAT and the type of NAT.
- the STUN protocol by itself does not allow applications using HTTP protocol to overcome NAT traversal issues.
- TURN or SPAN-A protocols allocate a TCP listener on the relay server to relay incoming packets from one point to another, but do not address the problem of how an application can operate using NAT traversal.
- a host running an HTTP server behind a Network Address Translator (NAT) connected to an IP network uses a NAT-discovery process, e.g., a STUN test, to determine the presence of the NAT.
- the host updates information in a redirect server based on the response of a relay server.
- An HTTP client host initiates a DNS query which connects it to the redirect server.
- the HTTP client host sends an HTTP request to the redirect server, which in turn redirects the HTTP request to a port on the packet relay server.
- the packet relay server relays the HTTP request to the HTTP server behind the NAT, which generates an HTTP response that is relayed back to the HTTP client.
- Seamless communication in an IP network is made possible by using a DDNS server that is updated using a user registration database.
- the IP network may have hosts located behind NATs and hosts that are directly connected to the IP network. Further areas of applicability of the present invention will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description and specific examples, while indicating the preferred embodiment of the invention, are intended for purposes of illustration only and are not intended to limit the scope of the invention. BRIEF DESCRIPTION OF DRAWINGS
- Figure 1 shows a network configuration according to an embodiment of the present invention
- Figure 2 is a sequence diagram of operations according to an embodiment of the present invention
- Figure 3 is an association diagram between a Dynamic DNS (DDNS) and a redirect
- Figure 1 shows a network configuration 10 according to an embodiment of the present invention.
- Network configuration 10 includes a public IP network 12 that can be,
- a packet relay server 20 a packet relay server 20, a NAT-discovery, e.g., STUN (Simple Traversal UDP (User Datagram Protocol) through NATs), server 22, a redirect server 24, a dynamic DNS (DDNS) server 26, a DNS (domain name system) server 26, a host computing device 16 5 , a host computing device 16 6 , a network address translator (NAT) 14 ⁇ and a NAT 14 2 .
- the redirect server 24 and the DDNS server 26 also have a direct connection independent of the public IP network 12, e.g., representing a shared database (not depicted in Fig. 1).
- the network configuration 10 further includes a private network 18 t and a private network 18 2 .
- Host computing devices 16 ⁇ and 16 2 connect to the network 18 ⁇ while host computing devices 16 3 and 16 4 connect to the network 18 2 .
- an application e.g., a web browser 30, that runs on the host 16 5 ; an application, e.g., an HTTP server 29, that runs on the host 16j; an input unit 100, a processing unit 102 and an output unit 104 in the relay server 20; an application, e.g., a listener 31, that runs on the packet relay server 20; and an application, e.g., an HTTP server 80, that runs on the host 16 6 .
- Hosts 16 ⁇ and 16 2 are indirectly connected to the public network 12 via the NAT
- NAT 14 2 indirectly connects the hosts 16 3 and 16 4 to the public IP network 12 via the private IP network 18 2 .
- Hosts 16 5 and 16 6 are directly connected to the public IP network 12.
- Network configuration 10 described above including the hosts, NATs and private IP networks is a non-limiting example of how the network configuration 10 can be implemented in an embodiment of the present invention.
- Those skilled in the art will appreciate that any combination of NATs, private IP networks, hosts and directly connected hosts can be included in the network configuration 10.
- the difficulty of using a host shielded by a NAT is described next in the context of an illustration.
- Host 16 ⁇ can exchange IP packets with the public IP network 12 through the NAT
- the function of the NAT 14 ⁇ is to allow hosts 16j and 16 2 to share a single public IP address.
- the NAT 14 ⁇ assigns private addresses to the hosts 16 ⁇ and 16 2 . Such private addresses are not visible to other IP devices connected to the public network 12. For example, the directly connected host 16 5 cannot readily send a packet addressed to the private address of host 16 2 that was assigned by the NAT 14 ⁇ .
- NAT 14 ⁇ assigns private IP addresses to the hosts 16 ⁇ and 16 2 that are located "behind" it, i.e., the hosts 16 ⁇ and 16 2 share the public or global IP address assigned to the NAT 14 ⁇ plus each has (typically) a separate port number on the NAT 14 K The combination of an IP address and a port number is referred to as a transport address.
- the browser 30 on the host 16 5 can send the packets to the global IP address of the NAT 14 ⁇ and the port number assigned to the host 16 5 if the browser 30 knows this information. Then, the NAT 14 ⁇ in turn forwards the packets to the private address of the host 16 2 .
- network configuration 10 includes additional elements as described next.
- the HTTP server 29 running on the host 16 ⁇ performs a NAT- discovery process, e.g., a STUN test, to find out if its host 16 ⁇ is located behind a NAT.
- a STUN test the host 16 ⁇ attempts to initiate a STUN session with the STUN server 22.
- the host 16 ⁇ is located behind, i.e., shielded by NAT 14 ⁇ .
- the STUN test session initiated by the host 16 ⁇ will indicate that the NAT 14 ⁇ is present in the connection between the host 16 ⁇ and the STUN server 22.
- the host 16 ⁇ connects to the packet relay server 20, which is operable to receive and forward IP packets.
- Host 16 initiates a TCP (Transmission Control Protocol) session and sends a packet relay initiation request to the input unit 100 of the relay server 20.
- TCP Transmission Control Protocol
- Phraseology that has been used to describe this arrangement is that, in response, the processing unit 102 of the relay server 20 can run a TCP application known as a listener 31.
- the relay server 20 is similar in some respects to an HTTP proxy server (not depicted) and an SEP type of TURN server (not depicted).
- An HTTP proxy server analyzes packet payload to determine whether progress of a packet beyond the proxy server should be blocked or facilitated. In contrast, the relay server 20 ignores the content of the packet, i.e., the relay server 20 does not block packet progress based upon the type of payload.
- the TURN protocol run by the TURN server in contrast, generally supports a device (e.g., host 16 ⁇ behind a NAT (e.g., 14 ⁇ ), but specifically does not support the hosting of a server (e.g., HTTP server 29) by the host 16 ⁇ .
- the output unit 104 of the relay server 20 returns to the host 16 ⁇ a global IP address (namely, the IP address of the packet relay server 20) and a port on which it (namely, the packet relay server 20 running the listener 31) will receive and send packets on behalf of the host 16 K AS is known, the packet relay server 20 assigns the address and port to the listener 31 dynamically. As such, the changing IP address and port must be tracked, as will be discussed below. Hosts connected to the public IP network 12 such as the Internet can send packets to the IP address and port number designated by the relay server 20 as the listener 31.
- the listener 31 forwards such packets to the host 16 ⁇ (by extracting the payloads from the packets it receives, rewrapping with a new header identifying the HTTP server 29 as the destination and forwarding the rewrapped payloads via the NAT 14 ⁇ to the HTTP server 29).
- the host 16 ⁇ can send packets to the relay server 20, and the relay server 20 can rewrap the payloads and transmit them to the specific forwarding IP address given in the packets.
- the relay server 20 provides a mechanism for the host 16 ⁇ to indirectly obtain a global IP address (namely, an address on the public network 12) over which it can send and receive packets to/from the public network 12.
- the host 16 ⁇ via the NAT 14 ⁇ provides the redirect server 24 with the IP address and port number of the listener 31. Then the listener 31 can redirect HTTP requests from the public IP network 12 seeking the HTTP server 29 to the global IP address and port number of the listener 31 on the relay server 20.
- the host 16 ⁇ can send and receive packets as if it was directly connected to the public network 12, as described above.
- any user/client of the HTTP server 30 connected to the public IP network 12 such as the browser 30 will need a mechanism to connect to the HTTP server 29 on host l ⁇ ⁇ via the packet relay server 20.
- the HTTP server 29 on host 16 ⁇ is assigned a FQDN (again, a type of Universal Resource Locator (URL)), e.g., for the purposes of discussion say "www.somenet.com,” which is statically associated with a global IP address on the redirect server 24.
- the redirect server 24 adaptively maps the FQDN 'www.somenet.com' to the dynamic IP address and port number of the listener 31.
- the redirect server 24 can use multiple methods to redirect the HTTP request to the listener 31 on the relay server 20. Some examples of redirecting methods are described next.
- the redirect server 24 can redirect an HTTP request by providing a "splash page" (not depicted) to the browser 30 when a request to access the host 16 ⁇ is made.
- a hyperlink can be provided on such a "splash page", which (if clicked by the user) will transfer the user to the listener 34 on the relay server 20. This further involves the user after the initial HTTP request had been submitted.
- the redirect server 24 can automatically redirect the HTTP request to the TCP listener 34 on the relay server 20 using the "307 Temporary Redirect" feature of the HTTP 1.1 protocol.
- the HTTP 1.1 temporary redirect method can eliminate the need to show a splash page and elicit a hyperlink click from the user of the browser 30.
- the redirect server 24 can transfer or redirect any HTTP request for the HTTP server 30 on the host 16 ⁇ to the TCP listener 31 on the relay server 20.
- Figure 2 is a sequence diagram of operations according to an embodiment of the present invention.
- Figure 2 does not strictly conform to the conventions of UML-type sequence diagrams.
- the HTTP server 29 running on the host 16 ⁇ sends a message 70 initiating a ⁇ AT-discovery process, e.g., a STUN test.
- the message 70 is sent to the NAT-discovery server, e.g., STUN server 22, via the NAT 14 ⁇ .
- the intervening role of the NAT 14 ⁇ is indicated by the dot 72 at the intersection of the message 70 and the lifeline 74 of the NAT 14 ⁇ . Such a dot convention will be used for other messages passing via the NAT 14 ⁇ .
- the NAT-discovery server 22 sends a return message 76 to indicate the presence of the NAT 14 ⁇ to the host 16 ⁇ .
- Host 16 ⁇ sends a message 32 to the packet relay server 20 requesting it to open a listener 31.
- the packet relay server 20 sends back a message 34 to the host 16 ⁇ indicating the global IP address (of the packet relay server 20) and the port number (on the packet relay server 20) assigned to the listener 31.
- the host 16 ⁇ then updates the redirect server 24 by a message 36 to register the global IP address and port number of the listener 31 on the relay server 20.
- the redirect server 24 will authenticate the message 36 and update its database to associate the IP address and port number of the listener 31 with the FQDN (here, in the example, www.somenet.com) of the HTTP server 29.
- FQDN here, in the example, www.somenet.com
- the user can access the, e.g., of the browser 30 on the host 16 5 , HTTP server 29 running on the host 16 ⁇ .
- the browser 30 on the host 16 5 is representative of any computer or IP-enabled device connected to the public IP network 12 (shown in Fig. 1).
- the browser 31 on the host 16 5 sends a message 38 to the DNS server 28 with the FQDN in order to obtain the DNS entry of the entered URL.
- the DNS server 28 sends back a message 40 to the host 16 5 with the IP address of the redirect server 24. It may be necessary for the DNS server 28 to communicate (not shown as a message in Fig.
- the redirect server 24 checks its database to find a set of IP address and port number of the listener 31 on the relay server 20 that correspond to the requested URL or URI (Universal Resource Indicator). In other words, the redirect server 24 maintains a mapping to port numbers on the relay server 20, whereas the DNS 28/DNS 26 maintains merely the IP address of the listener 31/relay server 20.
- URI Universal Resource Indicator
- the redirect server 24 Upon finding a match, the redirect server 24, as shown by a message 44, responds by redirecting the HTTP request of the browser 30 to the relay server 20 using any of the above-described redirection methods.
- Host 16 5 (as part of hosting the browser 30) then sends an HTTP request to the relay server 20 as indicated by the message 46 based on the redirection IP address and port number received from the redirect server 24.
- the relay server 20 in turn sends a message 48 to the host 16 ⁇ with which it has maintained a live TCP session.
- the relay server 20 unwraps the payloads of the packets (not shown) it receives that are directed to the listener 31, re- wraps the payloads to indicate the global IP address of the NAT 14 ⁇ (which is also the global IP address of the HTTP server 29) and the port on the NAT 14 ⁇ assigned to the HTTP server 29, and forwards the re-wrapped packets to the HTTP server 29 (via the NAT 14 ⁇ ).
- the host 16 ⁇ (as part of hosting the HTTP server 29) will send a response to the packet relay server 20 as message 50. Further, the relay server 20 transmits the response to the browser 30 on the host 16 5 .
- the relay server 20 receives packets sent by the HTTP server 29 whose destination is the browser 30, similarly rewraps the payloads as packets for the browser 30, and sends the re-wrapped packets to the browser 30.
- an HTTP session is established where the browser 30 on the host 16 5 can access the HTTP server 29 on the host 16 ⁇ even though the host 16 ⁇ is located behind the NAT 14 ⁇ , i.e., even though the NAT 14 ⁇ is located between the browser 30 and the HTTP server 29.
- Such NAT traversal is achieved above without the browser 30 on the host 16 5 having knowledge of the private IP address of the HTTP server 29 shielded by the NAT 14 ⁇ . No manual step or configuration is required at the host 16 5 , i.e., on the user side of the HTTP access operation.
- Such transparent NAT traversal can be important if the accessing device is a device, i.e., such as an IP phone, since it would be difficult for a user to manually configure the whole process of NAT traversal. Again, such difficulty is due to the majority of users of such devices, similar to the majority of browser users, not understanding the mapping of a domain name to a URL, much less the aspect of needing to designate a port as well as an IP address.
- FIG 3 is an association diagram between the Dynamic DNS (DDNS) server 26 and a redirect Server 64 according to an embodiment of the present invention.
- the redirect server 64 is similar to the redirect server 26 of Fig. 1.
- the redirect server 64 includes: a user registrar unit 54; a user registration database 58; and an IP registrar unit 60.
- the HTTP server is not located behind a NAT.
- host 16 6 is not located behind a NAT.
- a DDNS server 26 can be present that assigns a dynamic IP address and port number to the host 16 5 .
- the unit 54, the unit 60 and the database 58 can be hosted by a processing entity other than the redirect server 64.
- the DDNS server 26 can host the database 58.
- IP addresses typically change for other known reasons, e.g., expiration of a finite lifetime.
- the DDNS is used to overcome the problem of a changing IP address.
- DDNS allows a domain name to be associated with a changing, i.e., dynamic, IP address.
- DDNS takes care of directing the DNS to point to the currently updated dynamic IP address for a given domain name.
- a given network configuration 10 includes a host (e.g., 16 6 ) that is not behind a NAT
- the HTTP server (e.g., 80) on the host can initiate a NAT-discovery process and will determine that no NAT is present in its connection path.
- the HTTP host 80 thereafter updates the redirect server 64 with its own dynamic IP address.
- the DDNS server 26 is present in the system, then the step of updating the redirect server 64 can be eliminated, since the DNS server 28 will be able to resolve the dynamic IP address when a DNS query (e.g., message 38 in figure 2) is received.
- a DNS query e.g., message 38 in figure 2
- a user registrar 54 accepts online registration requests 310 from IP devices, for example, hosts running HTTP servers.
- User registrar 54 receives a message 56 from a user (not depicted) that includes a registration request 310 and updates a user registration database 58.
- an IP registrar 60 receives a message 62 that includes an IP update 62.
- the IP registrar 60 If the IP registrar 60 is able to authenticate the IP update 311 of message 62, then it updates the IP address and port number associated with the registered user in the user registration database 58 and also information about the presence of the NAT.
- the DDNS server 26 continuously tracks changes to the user registration database
- the DDNS server 26 As soon as the DDNS server 26 detects any change to the user registration database 58, it finds out about the presence of NAT for the recent update. If a NAT is not present for the recently updated IP address and port number, then the DDNS server 26 updates its internal DDNS lookup table(s) with the updated IP address and port number. The DDNS lookup table(s) (not depicted) is searched by all DNS servers 28 for resolving DNS queries (represented by the double-headed arrow 312, which corresponds to the messages 38 and 40 in Fig. 2). If a NAT is present, then the DDNS server 26 registers the IP address of the redirect server 26 and port number. Hence, the user registration database 58 provides a seamless mechanism for both type of hosts, i.e., those that are behind NATs and those that are not behind (not depicted) NATs.
- DDNS server 26 would supply the IP address and port number of the redirect server 64.
- the DDNS server 26 can simply supply the IP address and port number of the particular host in response to a DNS query, i.e., the redirect server would not be needed.
Abstract
A host running an HTTP server behind a Network Address Translator (NAT) connected to an IP network uses a NAT-discovery process, e.g., a STUN test to determine the presence of the NAT. The host updates information in a redirect server based on the response of a relay server. An HTTP client host initiates a DNS query which connects it to the redirect server. The HTTP client host sends a HTTP request to the redirect server, which in turn redirects the HTTP request to a port on the packet relay server. The packet relay server relays the HTTP request to the HTTP server behind the NAT, which generates an HTTP response that is relayed back to the HTTP client. Seamless communication in an IP network is made possible by using a DDNS server that is updated using a user registration database. The IP network may have hosts located behind the NATs and hosts that are directly connected to the IP network.
Description
DESCRIPTION RELAYED NETWORK ADDRESS TRANSLATOR (NAT) TRAVERSAL
BACKGROUND ART In the last decade, the number of computers connected to the Internet has increased by an enormous order of magnitude. High growth in the number of Internet connections has put severe pressure on the available address-space of routable internet protocol (IP) addresses. To overcome the problem of limited and diminishing IP address-space, it became imperative to have a solution that would allow multiple users to share a single routable internet address. The commonly used solution for sharing a single IP address is known as a Network Address Translator (NAT). Operation of a typical NAT is described next.
The basic concept underlying a NAT is to have a device or software module that allows sharing of one or more routable Internet Protocol (IP) addresses by multiple computers. A typical NAT is connected to the public internet on one side and has at least one global or public IP address for receiving and sending data packets from and to the public internet. On the other side of the typical NAT is a private network, in which each network node (computer) is assigned a local arbitrary address. Typically, the NAT assigns arbitrary addresses to the nodes of the private network using a Dynamic host Control Protocol (DHCP) or alternatively the NAT assigns static translation addresses.
The NAT provides a convenient way of providing shared and transparent communication between the public internet and the computers (attached to a private network) having a non-globally-unique IP address, i.e., an IP address that is not globally- unique. However, not all forms of communications are operable over NAT. Many types of applications require a globally-unique IP address as a termination point or require IP
address consistency over the whole communication cycle. For example, an IP enabled phone will typically require a globally-unique IP address to receive and send voice- transmission using the IP. Presence of a NAT at the receiving end of the IP phone call may block the receiver from receiving the phone IP packets. The presence of NATs in a network poses another type of problem as described next. There is no simple and convenient way to access a server type of device located behind a NAT from the public internet side of the NAT. For example, if a Hypertext Transfer Protocol (HTTP) webserver is located behind a NAT, then it has a private address which is invisible to the outside world through the public internet. On the contrary, a typical webserver, e.g., an HTTP server, which is not behind a NAT, is readily accessible from the public internet if it has an IP address that can be resolved using common methods like the Domain Name System (DNS).
Typically, an HTTP server on a host is assumed to use the default port number, namely 80, for a host. An advantage of this arrangement is that the user of the browser does not need to designate a port number in addition to the address of the host because the default port number will be assumed. Because of the prevalence of Domain Name System (DNS) servers and dynamic DNS (DDNS) servers, most users of browsers do not understand that a domain name, e.g., 'www.name.com', represents a universal resource locator (URL), which is a long string of numbers. Moreover, most users of browsers have no understanding that a domain name of an HTTP server maps to a port number of the host as well as an address of the host because most users have never had to provide a port number.
TCP/IP allows multiple applications to run on a single computer using a variety of port numbers. When a NAT is used by a private network to share an IP address, then the port addresses are shielded behind the NAT from the outside network. This situation can
be further complicated by presence of a firewall with a security policy that does not allow access to specific ports of the computers on the private network as described next.
A port-forwarding solution creates a "tunnel" through the firewall so that external users from the public internet can access a specific computer in the private network using the designated port for the tunnel. Typically, a port forwarding solution has a maximum number of about five forwarded port entries. But many applications like network-gaming, instant messaging and collaboration software may require access to previously "unopened" specific TCP/UDP ports from the external public internet. Creating all the required tunnels for such applications can be an impractical task for a typical user, since the tunnel configuration process can be complicated and confusing. Port forwarding is typically a kind of functionality provided by a router, hence it typically raises a need for a specific router that has an inbuilt port forwarding capability.
The presence of NAT may not affect the network much if the transport connections are initiated from the clients that are behind the NAT. But if a server is located behind a NAT, then IP requests originating from the public network may not be able to access the server due to the presence of NAT. An approach to solve this problem and its drawbacks are discussed next. In a Dynamic Domain Name System (DDNS) the users attempting to access a server located behind a NAT using a Fully Qualified Domain Name (FQDN) may face problems. Such problems result from the situation when a server or device behind a NAT is assigned a private IP address by a NAT which is invisible. A DDNS trying to route packets to an IP address due to a FQDN access request will fail since the NAT- assigned private address is invisible to the public internet side of the NAT.
One approach to get around the NAT restrictions is called DMZ (an acronym for De-Militarized Zone) which allows a given machine behind a NAT to be directly connected to the internet, without compromising security of other machines in the network.
DMZ allows a machine behind the NAT to operate as if it is directly connected to the internet. DMZ, like port forwarding discussed above, can be confusing to configure for a typical user, since it requires user expertise to configure it. Those skilled in the art will appreciate that DMZ cannot be used to open-up all machines of a network to the public internet. DMZ exposes a given machine to all the vulnerabilities that are associated with a direct connection to the internet, since it overrides the firewall protection. Hence, neither DMZ nor port forwarding is a satisfactory solution to the problem of transparent NAT traversal that requires no or minimum user effort to implement.
Universal Plug-and-Play (UPnP) is another method for NAT traversal. UPnP can provide the public IP address to the client behind the NAT. Like port forwarding, UPnP facilities are typically provided by the router itself. But the drawback of this approach lies in the special hardware requirement in the form of a router that is UPnP compliant.
Attempts have been made to define protocols for solving the NAT traversal problem described above. For example, protocols like TURN (Traversal Using Relay NAT), STUN (Simple Traversal of UDP through NAT), SPAN-A (Simple Protocol for Augmenting NATs), etc., provide an approach that does not require routers to have specific functionality of supporting NAT traversal. However, the above protocols have their own drawbacks. STUN can detect the presence of a NAT and the type of NAT. However, the STUN protocol by itself does not allow applications using HTTP protocol to overcome NAT traversal issues. TURN or SPAN-A protocols allocate a TCP listener on the relay server to relay incoming packets from one point to another, but do not address the problem of how an application can operate using NAT traversal. DISCLOSURE OF INVENTION
A host running an HTTP server behind a Network Address Translator (NAT) connected to an IP network uses a NAT-discovery process, e.g., a STUN test, to determine
the presence of the NAT. The host updates information in a redirect server based on the response of a relay server. An HTTP client host initiates a DNS query which connects it to the redirect server. The HTTP client host sends an HTTP request to the redirect server, which in turn redirects the HTTP request to a port on the packet relay server. The packet relay server relays the HTTP request to the HTTP server behind the NAT, which generates an HTTP response that is relayed back to the HTTP client. Seamless communication in an IP network is made possible by using a DDNS server that is updated using a user registration database. The IP network may have hosts located behind NATs and hosts that are directly connected to the IP network. Further areas of applicability of the present invention will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description and specific examples, while indicating the preferred embodiment of the invention, are intended for purposes of illustration only and are not intended to limit the scope of the invention. BRIEF DESCRIPTION OF DRAWINGS
Figure 1 shows a network configuration according to an embodiment of the present invention;
Figure 2 is a sequence diagram of operations according to an embodiment of the present invention; and Figure 3 is an association diagram between a Dynamic DNS (DDNS) and a redirect
Server according to an embodiment of the present invention.
BEST MODE FOR CARRYING OUT THE INVENTION
The following description of the example embodiment(s) is merely exemplary in nature and is in no way intended to limit the invention, its application, or uses.
Figure 1 shows a network configuration 10 according to an embodiment of the present invention. Network configuration 10 includes a public IP network 12 that can be,
e.g., the Internet.
Included as being attached to the public network 12 are: a packet relay server 20, a NAT-discovery, e.g., STUN (Simple Traversal UDP (User Datagram Protocol) through NATs), server 22, a redirect server 24, a dynamic DNS (DDNS) server 26, a DNS (domain name system) server 26, a host computing device 165, a host computing device 166, a network address translator (NAT) 14χ and a NAT 142. The redirect server 24 and the DDNS server 26 also have a direct connection independent of the public IP network 12, e.g., representing a shared database (not depicted in Fig. 1).
The network configuration 10 further includes a private network 18t and a private network 182. Host computing devices 16χ and 162 connect to the network 18χ while host computing devices 163 and 164 connect to the network 182.
For the purposes of subsequent discussion, it can be helpful to think in terms of examples in which there is: an application, e.g., a web browser 30, that runs on the host 165; an application, e.g., an HTTP server 29, that runs on the host 16j; an input unit 100, a processing unit 102 and an output unit 104 in the relay server 20; an application, e.g., a listener 31, that runs on the packet relay server 20; and an application, e.g., an HTTP server 80, that runs on the host 166. Hosts 16ι and 162 are indirectly connected to the public network 12 via the NAT
14ι and the private IP network 18χ. Similarly, NAT 142 indirectly connects the hosts 163 and 164 to the public IP network 12 via the private IP network 182. Hosts 165 and 166 are directly connected to the public IP network 12.
Network configuration 10 described above including the hosts, NATs and private IP networks is a non-limiting example of how the network configuration 10 can be
implemented in an embodiment of the present invention. Those skilled in the art will appreciate that any combination of NATs, private IP networks, hosts and directly connected hosts can be included in the network configuration 10. The difficulty of using a host shielded by a NAT is described next in the context of an illustration. Host 16ι can exchange IP packets with the public IP network 12 through the NAT
14ι. The function of the NAT 14χ is to allow hosts 16j and 162 to share a single public IP address. The NAT 14ι assigns private addresses to the hosts 16ι and 162. Such private addresses are not visible to other IP devices connected to the public network 12. For example, the directly connected host 165 cannot readily send a packet addressed to the private address of host 162 that was assigned by the NAT 14χ.
NAT 14ι assigns private IP addresses to the hosts 16χ and 162 that are located "behind" it, i.e., the hosts 16χ and 162 share the public or global IP address assigned to the NAT 14ι plus each has (typically) a separate port number on the NAT 14K The combination of an IP address and a port number is referred to as a transport address. In order to send packets to the host 16ι, the browser 30 on the host 165 can send the packets to the global IP address of the NAT 14ι and the port number assigned to the host 165 if the browser 30 knows this information. Then, the NAT 14ι in turn forwards the packets to the private address of the host 162. But, as a practical matter, the presence of NAT 14ι will not allow a typical client, e.g., the browser 30, to directly access the HTTP server 29 on host 16i, since the browser 30 is most unlikely to have the port number of host 16χ that was assigned by the NAT 16K This problem is known as the NAT traversal problem. To perform a NAT traversal, network configuration 10 according to an embodiment of the present invention includes additional elements as described next.
After booting up, the HTTP server 29 running on the host 16χ performs a NAT- discovery process, e.g., a STUN test, to find out if its host 16ι is located behind a NAT. In
the example of a STUN test, the host 16ι attempts to initiate a STUN session with the STUN server 22. Again, in the present example, the host 16ι is located behind, i.e., shielded by NAT 14ι. Hence, the STUN test session initiated by the host 16ι will indicate that the NAT 14χ is present in the connection between the host 16χ and the STUN server 22. After positively determining the presence of a NAT, the host 16χ connects to the packet relay server 20, which is operable to receive and forward IP packets. Host 16 initiates a TCP (Transmission Control Protocol) session and sends a packet relay initiation request to the input unit 100 of the relay server 20. Phraseology that has been used to describe this arrangement is that, in response, the processing unit 102 of the relay server 20 can run a TCP application known as a listener 31.
It is noted that the relay server 20 is similar in some respects to an HTTP proxy server (not depicted) and an SEP type of TURN server (not depicted). An HTTP proxy server analyzes packet payload to determine whether progress of a packet beyond the proxy server should be blocked or facilitated. In contrast, the relay server 20 ignores the content of the packet, i.e., the relay server 20 does not block packet progress based upon the type of payload. The TURN protocol run by the TURN server, in contrast, generally supports a device (e.g., host 16^ behind a NAT (e.g., 14ι), but specifically does not support the hosting of a server (e.g., HTTP server 29) by the host 16ι.
The output unit 104 of the relay server 20 returns to the host 16ι a global IP address (namely, the IP address of the packet relay server 20) and a port on which it (namely, the packet relay server 20 running the listener 31) will receive and send packets on behalf of the host 16K AS is known, the packet relay server 20 assigns the address and port to the listener 31 dynamically. As such, the changing IP address and port must be tracked, as will be discussed below.
Hosts connected to the public IP network 12 such as the Internet can send packets to the IP address and port number designated by the relay server 20 as the listener 31. The listener 31 in turn forwards such packets to the host 16χ (by extracting the payloads from the packets it receives, rewrapping with a new header identifying the HTTP server 29 as the destination and forwarding the rewrapped payloads via the NAT 14ι to the HTTP server 29). Similarly, the host 16ι can send packets to the relay server 20, and the relay server 20 can rewrap the payloads and transmit them to the specific forwarding IP address given in the packets. The relay server 20 provides a mechanism for the host 16ι to indirectly obtain a global IP address (namely, an address on the public network 12) over which it can send and receive packets to/from the public network 12.
After obtaining the set of global IP address and port number from the relay server 20, the host 16ι via the NAT 14ι provides the redirect server 24 with the IP address and port number of the listener 31. Then the listener 31 can redirect HTTP requests from the public IP network 12 seeking the HTTP server 29 to the global IP address and port number of the listener 31 on the relay server 20.
Using the packet relay server 20, the host 16ι can send and receive packets as if it was directly connected to the public network 12, as described above. However, any user/client of the HTTP server 30 connected to the public IP network 12 such as the browser 30 will need a mechanism to connect to the HTTP server 29 on host lβ\ via the packet relay server 20. The HTTP server 29 on host 16χ is assigned a FQDN (again, a type of Universal Resource Locator (URL)), e.g., for the purposes of discussion say "www.somenet.com," which is statically associated with a global IP address on the redirect server 24. The redirect server 24 adaptively maps the FQDN 'www.somenet.com' to the dynamic IP address and port number of the listener 31. Hence, when a user (not depicted) makes a request via the browser 30 to access the FQDN "www.somenet.com", the request
from the browser 30 will first be received by the redirect server 24. The redirect server 24 can use multiple methods to redirect the HTTP request to the listener 31 on the relay server 20. Some examples of redirecting methods are described next.
The redirect server 24 can redirect an HTTP request by providing a "splash page" (not depicted) to the browser 30 when a request to access the host 16χ is made. A hyperlink can be provided on such a "splash page", which (if clicked by the user) will transfer the user to the listener 34 on the relay server 20. This further involves the user after the initial HTTP request had been submitted. Alternatively, the redirect server 24 can automatically redirect the HTTP request to the TCP listener 34 on the relay server 20 using the "307 Temporary Redirect" feature of the HTTP 1.1 protocol. The HTTP 1.1 temporary redirect method can eliminate the need to show a splash page and elicit a hyperlink click from the user of the browser 30. Further, a combination of splash page with an automatic JANA-script-based redirect method can also be used. Via any of the above methods, the redirect server 24 can transfer or redirect any HTTP request for the HTTP server 30 on the host 16ι to the TCP listener 31 on the relay server 20.
Figure 2 is a sequence diagram of operations according to an embodiment of the present invention. Figure 2 does not strictly conform to the conventions of UML-type sequence diagrams. After booting-up, the HTTP server 29 running on the host 16χ sends a message 70 initiating a ΝAT-discovery process, e.g., a STUN test. The message 70 is sent to the NAT-discovery server, e.g., STUN server 22, via the NAT 14ι. The intervening role of the NAT 14χ is indicated by the dot 72 at the intersection of the message 70 and the lifeline 74 of the NAT 14χ. Such a dot convention will be used for other messages passing via the NAT 14χ. The NAT-discovery server 22 sends a return message 76 to indicate the presence of the NAT 14χ to the host 16χ.
Host 16χ sends a message 32 to the packet relay server 20 requesting it to open a listener 31. The packet relay server 20 sends back a message 34 to the host 16χ indicating the global IP address (of the packet relay server 20) and the port number (on the packet relay server 20) assigned to the listener 31. The host 16χ then updates the redirect server 24 by a message 36 to register the global IP address and port number of the listener 31 on the relay server 20. The redirect server 24 will authenticate the message 36 and update its database to associate the IP address and port number of the listener 31 with the FQDN (here, in the example, www.somenet.com) of the HTTP server 29. After the above initiation process is over, the user can access the, e.g., of the browser 30 on the host 165, HTTP server 29 running on the host 16χ.
Harkening back to the example, it is to be noted that the browser 30 on the host 165 is representative of any computer or IP-enabled device connected to the public IP network 12 (shown in Fig. 1). When the user of the browser 30 types in the URL (Universal Resource Locator), e.g., FQDN, of the HTTP server 29, the browser 31 on the host 165 sends a message 38 to the DNS server 28 with the FQDN in order to obtain the DNS entry of the entered URL. The DNS server 28 sends back a message 40 to the host 165 with the IP address of the redirect server 24. It may be necessary for the DNS server 28 to communicate (not shown as a message in Fig. 2) with the DDNS server 26 in order to collectively provide the IP address of the redirect server 24 to the browser 30. The typical browser 30 on the host 165 can then initiate an HTTP request to the IP address of the redirect server 24 on the default port 80 (for HTTP protocol communications) via a message 42. The redirect server 24 in turn checks its database to find a set of IP address and port number of the listener 31 on the relay server 20 that correspond to the requested URL or URI (Universal Resource Indicator). In other words, the redirect server 24 maintains a mapping to port numbers on the relay server 20, whereas
the DNS 28/DNS 26 maintains merely the IP address of the listener 31/relay server 20. Upon finding a match, the redirect server 24, as shown by a message 44, responds by redirecting the HTTP request of the browser 30 to the relay server 20 using any of the above-described redirection methods. Host 165 (as part of hosting the browser 30) then sends an HTTP request to the relay server 20 as indicated by the message 46 based on the redirection IP address and port number received from the redirect server 24. The relay server 20 in turn sends a message 48 to the host 16χ with which it has maintained a live TCP session. Again, the relay server 20 unwraps the payloads of the packets (not shown) it receives that are directed to the listener 31, re- wraps the payloads to indicate the global IP address of the NAT 14χ (which is also the global IP address of the HTTP server 29) and the port on the NAT 14χ assigned to the HTTP server 29, and forwards the re-wrapped packets to the HTTP server 29 (via the NAT 14χ).
On the return side, the host 16χ (as part of hosting the HTTP server 29) will send a response to the packet relay server 20 as message 50. Further, the relay server 20 transmits the response to the browser 30 on the host 165. In more detail, the relay server 20 receives packets sent by the HTTP server 29 whose destination is the browser 30, similarly rewraps the payloads as packets for the browser 30, and sends the re-wrapped packets to the browser 30. Thus, an HTTP session is established where the browser 30 on the host 165 can access the HTTP server 29 on the host 16ι even though the host 16χ is located behind the NAT 14χ, i.e., even though the NAT 14χ is located between the browser 30 and the HTTP server 29.
Such NAT traversal is achieved above without the browser 30 on the host 165 having knowledge of the private IP address of the HTTP server 29 shielded by the NAT 14χ. No manual step or configuration is required at the host 165, i.e., on the user side of the
HTTP access operation. Such transparent NAT traversal can be important if the accessing device is a device, i.e., such as an IP phone, since it would be difficult for a user to manually configure the whole process of NAT traversal. Again, such difficulty is due to the majority of users of such devices, similar to the majority of browser users, not understanding the mapping of a domain name to a URL, much less the aspect of needing to designate a port as well as an IP address.
Figure 3 is an association diagram between the Dynamic DNS (DDNS) server 26 and a redirect Server 64 according to an embodiment of the present invention. The redirect server 64 is similar to the redirect server 26 of Fig. 1. The redirect server 64 includes: a user registrar unit 54; a user registration database 58; and an IP registrar unit 60. In a given network configuration 10 (see Figure 1), it is possible that the HTTP server is not located behind a NAT. For example, host 166 is not located behind a NAT. Further, a DDNS server 26 can be present that assigns a dynamic IP address and port number to the host 165. Alternatively, the unit 54, the unit 60 and the database 58 can be hosted by a processing entity other than the redirect server 64. For example, the DDNS server 26 can host the database 58.
Internet Service Providers typically provide dial-up users with a non-static IP address that changes from time to time as users login and logout. IP addresses also change for other known reasons, e.g., expiration of a finite lifetime. The DDNS is used to overcome the problem of a changing IP address. DDNS allows a domain name to be associated with a changing, i.e., dynamic, IP address. DDNS takes care of directing the DNS to point to the currently updated dynamic IP address for a given domain name.
Where a given network configuration 10 includes a host (e.g., 166) that is not behind a NAT, the HTTP server (e.g., 80) on the host can initiate a NAT-discovery process
and will determine that no NAT is present in its connection path. The HTTP host 80 thereafter updates the redirect server 64 with its own dynamic IP address. In case the DDNS server 26 is present in the system, then the step of updating the redirect server 64 can be eliminated, since the DNS server 28 will be able to resolve the dynamic IP address when a DNS query (e.g., message 38 in figure 2) is received. A mechanism to make the NAT traversal work seamlessly in situations where a NAT may or may not be present for a given host is described next.
Seamless network operation, either where no NAT is present in a DDNS environment or a NAT is present and there also is both a relay server 20 and a redirect server 64 (that receives/provides an HTTP request/response as represented by a double- headed arrow 313, which corresponds to the messages 42 and 44 in Fig. 2), can be made possible as described next. A user registrar 54 accepts online registration requests 310 from IP devices, for example, hosts running HTTP servers. User registrar 54 receives a message 56 from a user (not depicted) that includes a registration request 310 and updates a user registration database 58. Then, an IP registrar 60 receives a message 62 that includes an IP update 62. If the IP registrar 60 is able to authenticate the IP update 311 of message 62, then it updates the IP address and port number associated with the registered user in the user registration database 58 and also information about the presence of the NAT. The DDNS server 26 continuously tracks changes to the user registration database
58. As soon as the DDNS server 26 detects any change to the user registration database 58, it finds out about the presence of NAT for the recent update. If a NAT is not present for the recently updated IP address and port number, then the DDNS server 26 updates its internal DDNS lookup table(s) with the updated IP address and port number. The DDNS lookup table(s) (not depicted) is searched by all DNS servers 28 for resolving DNS queries
(represented by the double-headed arrow 312, which corresponds to the messages 38 and 40 in Fig. 2). If a NAT is present, then the DDNS server 26 registers the IP address of the redirect server 26 and port number. Hence, the user registration database 58 provides a seamless mechanism for both type of hosts, i.e., those that are behind NATs and those that are not behind (not depicted) NATs.
In case of a given host behind a NAT, the internal tables (not depicted) of the
DDNS server 26 would supply the IP address and port number of the redirect server 64.
For the other situation, where a given host is not behind an NAT, then the DDNS server 26 can simply supply the IP address and port number of the particular host in response to a DNS query, i.e., the redirect server would not be needed.
The description of the invention is merely exemplary in nature and, thus, variations that do not depart from the gist of the invention are intended to be within the scope of the invention. Such variations are not to be regarded as a departure from the spirit and scope of the invention.
Claims
1. A system for communicating over a Network Address Translator (NAT) connected to an Internet Protocol (IP) network there being a first host connected via the NAT to the IP network and a second host connected to the IP network that seeks to communicate with the first host, the system comprising: at least one relay server connected to the IP network, the relay server being operable as a representative of the first host on the IP network; and at least one redirect server connected to the IP network; the redirect server and the relay server being operative, respectively, to cooperatively respond to an access request, which is originated by the second host and targets the first host, by cooperatively facilitating establishment of an IP communication channel between the second host and the first host.
2. The system of claim 1, wherein: the redirect server is operable to receive the access message from the second host, and redirect the access message to a listener operated by the relay server; and the relay server is operable to relay the access message to the first host.
3. The system of claim 2, wherein the redirect server is operable to redirect the access message to the relay server using at least one of a splash page with a manual redirect, a splash page with an automatic redirect, a protocol based automatic redirect mechanism, and a splash page with a script-based automatic redirect.
4. The system of claim 1, wherein the relay server is operable, prior to receipt of the access request from the second host, to receive a packet relay request from the first host, and then provide a listener on behalf of the first host
5. The system of claim 4, wherein the relay server is further operable to provide the first host with an IP address and a port number of the listener.
6. The system for claim 4, wherein the relay server is a packet relay server, and the listener is a Transmission Control Protocol (TCP) listener.
7. The system of claim 1, wherein the redirect server is operable to receive an update as to an IP address and a port number of a listener on the relay server corresponding to the first host.
8. The system of claim 7, wherein the update received by the redirect server comes from the first host.
9. The system of claim 1, wherein the relay server is operable to represent an HTTP server being hosted by the first host and the IP communication channel is a Hypertext Transfer Protocol (HTTP) type of connection.
10. The system of claim 1, wherein the IP network is the Internet.
11. An apparatus for seamlessly communicating over an Internet Protocol (IP) network, the apparatus comprising: at least one Dynamic DNS (DDNS) server; and a DNS lookup table including a direct transport address for a second host that is directly connected to the IP network and a transport address which a redirect server associates with a first host that is connected via a Network Address Translator (NAT) to the IP network, the DNS lookup table being associated with the DDNS server, the DDNS server resolving a DNS query using the DNS lookup table.
12. The apparatus of claim 11, further comprising: a user registration database, the DDNS server updating the DNS lookup table after sensing an update to the user registration database.
13. The apparatus of claim 12, further comprising: a user registrar connected to the user registration database, the user registrar performing online registration of a user to update the registration database; and an IP registrar connected to the user registration database, the IP registrar updating a transport address of an authenticated user corresponding to one of the first host and the second host.
14. A method for facilitating communication between a client connected to the IP network and a host connected via a Network Address Translator (NAT) to the IP network, the method comprising: receiving at a relay server connected to the IP network, if a NAT is present in a communication path connecting the host to the IP network, a packet relay request originated by a source server being hosted on the first host; providing a relay response from the relay server to the source server; and receiving, at a redirect server, update information originated by the source server based upon the relay response, the update information being usable by the redirect server to facilitate establishment of an IP communication channel between the client and the source server.
15. The method of claim 14, wherein the source server is a Hypertext Transfer Protocol (HTTP) server, the IP network is the Internet, and the IP communication channel is an HTTP type of connection.
16. A method for facilitating communication between a client connected to the IP network and a host connected via a Network Address Translator (NAT) to the IP network, the method comprising: receiving, at a redirect server, an access request from a second host; forwarding the access request to a relay server; and transferring the access request from the relay server to a first host; the receiving, forwarding and transferring collectively facilitating the establishment of an IP communication channel between the first host and the second host.
17. The method of claim 16, wherein the access request is an HTTP request the IP communication channel is an HTTP connection, an HTTP server is being hosted on the first host and the second host is an HTTP client of the HTTP server.
18. The method of claim 17, wherein the establishment of the IP communication channel includes: receiving an HTTP response from the HTTP server on the first host at the relay server; and transmitting the HTTP response from the relay server to the second host.
19. A method for seamlessly communicating over an Internet Protocol (IP) network, the method comprising: receiving a DNS query from an HTTP client to a DDNS server; resolving the DNS query using at least one DDNS server having a DNS lookup table, wherein the DNS lookup table includes a direct transport address for a second host that is directly connected to the IP network and a transport address which a redirect server associates with a first host that is connected via a Network Address Translator (NAT) to the IP network; and generating a DNS response, wherein the DNS response using at least one of the direct transport address and the redirect server's address based upon the DNS query being directed to at least one of the first host and the second host, respectively.
20. The method of claim 19, further comprising: updating the DNS lookup table with information from a user registration database, the user registration database including transport addresses and NAT indicators for indicating presence of NATs for hosts similar to the second host.
21. The method of claim 20, further comprising: registering a user connected to the user registration database through a user registrar; and authenticating an IP update from the user using an IP registrar; and updating the user registration database with a transport address of an authenticated user, the transport address corresponding to at least one of the first host and the second host.
22. A method for facilitating communication from a client connected to the IP network to a host connected via a Network Address Translator (NAT) to the IP network, the method comprising: receiving a packet relay request at a packet relay server connected to the IP network, the request coming from the host connected via the NAT to the IP network; and providing a response from the relay server via the NAT to the host that indicates establishment of listener on the relay server that will listen on behalf of the host for communication from the client to the host.
23. The method of claim 22, wherein the host is operable for hosting an HTTP server.
24. The method of claim 22, wherein the listener is a Transmission Control Protocol (TCP) listener.
25. The method of claim 22, wherein the IP network is the Internet.
26. A packet relay server, connected to an Internet Protocol (IP) network, for facilitating communication from a client connected to the IP network to a host connected via a Network Address Translator (NAT) to the IP network, the apparatus comprising: an input unit to receive a packet relay request coming from the host connected via the NAT to the IP network; and a processor unit operable to generate a listener that will listen on behalf of the host for communication from the client to the host, and provide a response via the NAT to the host that indicates in IP address and port number of listener.
27. The packet relay server of claim 26, wherein an application hosted by the host, for which the listener is generated, is an HTTP server.
28. The packet relay server of claim 26, wherein the listener is a Transmission Control Protocol (TCP) listener.
29. The packet relay server of claim 26, wherein the IP network is the Internet.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/342,304 | 2003-01-15 | ||
US10/342,304 US7899932B2 (en) | 2003-01-15 | 2003-01-15 | Relayed network address translator (NAT) traversal |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2004064356A2 true WO2004064356A2 (en) | 2004-07-29 |
WO2004064356A3 WO2004064356A3 (en) | 2004-12-16 |
Family
ID=32711678
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2004/000259 WO2004064356A2 (en) | 2003-01-15 | 2004-01-15 | Nat server traversal by means of a relay server |
Country Status (2)
Country | Link |
---|---|
US (2) | US7899932B2 (en) |
WO (1) | WO2004064356A2 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7543064B2 (en) | 2004-09-30 | 2009-06-02 | Logitech Europe S.A. | Multiplayer peer-to-peer connection across firewalls and network address translators using a single local port on the local host |
US7738468B2 (en) | 2005-03-22 | 2010-06-15 | Logitech Europe S.A. | Method and apparatus for packet traversal of a network address translation device |
US7886057B2 (en) | 2003-10-20 | 2011-02-08 | Logitech Europe S.A. | Method and apparatus for communicating data between two hosts |
US9794218B2 (en) | 2014-04-29 | 2017-10-17 | Trustiosity, Llc | Persistent network addressing system and method |
Families Citing this family (335)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002033773A (en) * | 2000-07-17 | 2002-01-31 | Web On Demand:Kk | Web on-demand system |
US8458754B2 (en) | 2001-01-22 | 2013-06-04 | Sony Computer Entertainment Inc. | Method and system for providing instant start multimedia content |
US6658091B1 (en) | 2002-02-01 | 2003-12-02 | @Security Broadband Corp. | LIfestyle multimedia security system |
US7711847B2 (en) | 2002-04-26 | 2010-05-04 | Sony Computer Entertainment America Inc. | Managing users in a multi-user network game environment |
US20030217135A1 (en) | 2002-05-17 | 2003-11-20 | Masayuki Chatani | Dynamic player management |
US8060626B2 (en) | 2008-09-22 | 2011-11-15 | Sony Computer Entertainment America Llc. | Method for host selection based on discovered NAT type |
US8131802B2 (en) | 2007-10-05 | 2012-03-06 | Sony Computer Entertainment America Llc | Systems and methods for seamless host migration |
US8560707B2 (en) | 2007-10-05 | 2013-10-15 | Sony Computer Entertainment America Llc | Seamless host migration based on NAT type |
US8224985B2 (en) * | 2005-10-04 | 2012-07-17 | Sony Computer Entertainment Inc. | Peer-to-peer communication traversing symmetric network address translators |
US7752334B2 (en) | 2002-10-15 | 2010-07-06 | Nomadix, Inc. | Intelligent network address translator and methods for network address translation |
US20050027882A1 (en) * | 2003-05-05 | 2005-02-03 | Sullivan Alan T. | Systems and methods for direction of communication traffic |
US7827607B2 (en) | 2002-11-27 | 2010-11-02 | Symantec Corporation | Enhanced client compliancy using database of security sensor data |
US7694343B2 (en) * | 2002-11-27 | 2010-04-06 | Symantec Corporation | Client compliancy in a NAT environment |
US7899932B2 (en) * | 2003-01-15 | 2011-03-01 | Panasonic Corporation | Relayed network address translator (NAT) traversal |
JP4110977B2 (en) * | 2003-01-21 | 2008-07-02 | 松下電器産業株式会社 | server |
JP3741312B2 (en) * | 2003-03-28 | 2006-02-01 | ソニー株式会社 | Network system and communication method, information processing apparatus and method, and program |
JP2004341732A (en) * | 2003-05-14 | 2004-12-02 | Canon Inc | Processor, data processing method, program and storage medium |
US6985920B2 (en) * | 2003-06-23 | 2006-01-10 | Protego Networks Inc. | Method and system for determining intra-session event correlation across network address translation devices |
CN1571440A (en) * | 2003-07-25 | 2005-01-26 | 中兴通讯股份有限公司 | A system and method for implementing multimedia call crossing private network |
SE0302189L (en) * | 2003-08-11 | 2004-05-11 | Dan Duroj | Handheld network connection created with at least two pocket storage media with communication software |
CN100440886C (en) * | 2003-09-02 | 2008-12-03 | 华为技术有限公司 | Method for realizing multimedia protocol passing through network address translation device |
US7478169B2 (en) * | 2003-10-16 | 2009-01-13 | International Business Machines Corporation | Accessing data processing systems behind a NAT enabled network |
WO2005041500A1 (en) * | 2003-10-27 | 2005-05-06 | Matsushita Electric Industrial Co., Ltd. | Communication system, information processing apparatus, server, and communication method |
US8234383B2 (en) * | 2003-11-07 | 2012-07-31 | Panasonic Corporation | Bubble packet port identification using detection packets |
EP1677465B1 (en) * | 2003-11-07 | 2014-08-13 | Panasonic Corporation | Communication system, information processing apparatus and communication method |
TWI257217B (en) * | 2003-11-10 | 2006-06-21 | Inst Information Industry | Method to detect the form of network address translation |
TWI255113B (en) * | 2003-11-10 | 2006-05-11 | Inst Information Industry | Method of media relay passing through Network Address Translation equipments to be decreased |
JP4269226B2 (en) * | 2003-11-14 | 2009-05-27 | ソニー株式会社 | Information communication system and method, information processing apparatus and method, program, and recording medium |
US8239446B2 (en) * | 2003-11-19 | 2012-08-07 | Sony Computer Entertainment America Llc | Content distribution architecture |
ATE353522T1 (en) * | 2003-12-23 | 2007-02-15 | Cit Alcatel | METHOD FOR EXECUTING A SYMMETRIC ADDRESS CONVERSION |
ES2315579T3 (en) * | 2004-01-23 | 2009-04-01 | Siemens Aktiengesellschaft | PROCEDURE FOR THE ASSIGNMENT OF AN IP ADDRESS TO A TEAM. |
US8065418B1 (en) * | 2004-02-02 | 2011-11-22 | Apple Inc. | NAT traversal for media conferencing |
US8085741B2 (en) * | 2004-03-10 | 2011-12-27 | Core Wireless Licensing S.A.R.L. | System and method for pushing content to a terminal utilizing a network-initiated data service technique |
US7680065B2 (en) * | 2005-01-18 | 2010-03-16 | Cisco Technology, Inc. | System and method for routing information packets |
US10382452B1 (en) | 2007-06-12 | 2019-08-13 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US20090077623A1 (en) | 2005-03-16 | 2009-03-19 | Marc Baum | Security Network Integrating Security System and Network Devices |
US10444964B2 (en) | 2007-06-12 | 2019-10-15 | Icontrol Networks, Inc. | Control system user interface |
US8988221B2 (en) | 2005-03-16 | 2015-03-24 | Icontrol Networks, Inc. | Integrated security system with parallel processing architecture |
US10156959B2 (en) | 2005-03-16 | 2018-12-18 | Icontrol Networks, Inc. | Cross-client sensor user interface in an integrated security network |
US10127802B2 (en) | 2010-09-28 | 2018-11-13 | Icontrol Networks, Inc. | Integrated security system with parallel processing architecture |
US9172553B2 (en) | 2005-03-16 | 2015-10-27 | Icontrol Networks, Inc. | Security system with networked touchscreen and gateway |
US10375253B2 (en) | 2008-08-25 | 2019-08-06 | Icontrol Networks, Inc. | Security system with networked touchscreen and gateway |
US8612591B2 (en) | 2005-03-16 | 2013-12-17 | Icontrol Networks, Inc. | Security system with networked touchscreen |
US8963713B2 (en) | 2005-03-16 | 2015-02-24 | Icontrol Networks, Inc. | Integrated security network with security alarm signaling system |
US10339791B2 (en) | 2007-06-12 | 2019-07-02 | Icontrol Networks, Inc. | Security network integrated with premise security system |
US11201755B2 (en) | 2004-03-16 | 2021-12-14 | Icontrol Networks, Inc. | Premises system management using status signal |
US11677577B2 (en) | 2004-03-16 | 2023-06-13 | Icontrol Networks, Inc. | Premises system management using status signal |
US11343380B2 (en) | 2004-03-16 | 2022-05-24 | Icontrol Networks, Inc. | Premises system automation |
US10200504B2 (en) | 2007-06-12 | 2019-02-05 | Icontrol Networks, Inc. | Communication protocols over internet protocol (IP) networks |
US10313303B2 (en) | 2007-06-12 | 2019-06-04 | Icontrol Networks, Inc. | Forming a security network including integrated security system components and network devices |
US10721087B2 (en) | 2005-03-16 | 2020-07-21 | Icontrol Networks, Inc. | Method for networked touchscreen with integrated interfaces |
US8635350B2 (en) | 2006-06-12 | 2014-01-21 | Icontrol Networks, Inc. | IP device discovery systems and methods |
US11244545B2 (en) | 2004-03-16 | 2022-02-08 | Icontrol Networks, Inc. | Cross-client sensor user interface in an integrated security network |
US11489812B2 (en) | 2004-03-16 | 2022-11-01 | Icontrol Networks, Inc. | Forming a security network including integrated security system components and network devices |
US11316958B2 (en) | 2008-08-11 | 2022-04-26 | Icontrol Networks, Inc. | Virtual device systems and methods |
US9191228B2 (en) | 2005-03-16 | 2015-11-17 | Icontrol Networks, Inc. | Cross-client sensor user interface in an integrated security network |
US9729342B2 (en) | 2010-12-20 | 2017-08-08 | Icontrol Networks, Inc. | Defining and implementing sensor triggered response rules |
US9531593B2 (en) | 2007-06-12 | 2016-12-27 | Icontrol Networks, Inc. | Takeover processes in security network integrated with premise security system |
US11368429B2 (en) | 2004-03-16 | 2022-06-21 | Icontrol Networks, Inc. | Premises management configuration and control |
US10237237B2 (en) | 2007-06-12 | 2019-03-19 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US9609003B1 (en) | 2007-06-12 | 2017-03-28 | Icontrol Networks, Inc. | Generating risk profile using data of home monitoring and security system |
JP2007529826A (en) | 2004-03-16 | 2007-10-25 | アイコントロール ネットワークス, インコーポレイテッド | Object management network |
US8473619B2 (en) | 2005-03-16 | 2013-06-25 | Icontrol Networks, Inc. | Security network integrated with premise security system |
US11916870B2 (en) | 2004-03-16 | 2024-02-27 | Icontrol Networks, Inc. | Gateway registry methods and systems |
US11113950B2 (en) | 2005-03-16 | 2021-09-07 | Icontrol Networks, Inc. | Gateway integrated with premises security system |
US10142392B2 (en) | 2007-01-24 | 2018-11-27 | Icontrol Networks, Inc. | Methods and systems for improved system performance |
US9141276B2 (en) | 2005-03-16 | 2015-09-22 | Icontrol Networks, Inc. | Integrated interface for mobile device |
US8996665B2 (en) | 2005-03-16 | 2015-03-31 | Icontrol Networks, Inc. | Takeover processes in security network integrated with premise security system |
US11159484B2 (en) | 2004-03-16 | 2021-10-26 | Icontrol Networks, Inc. | Forming a security network including integrated security system components and network devices |
US20170118037A1 (en) | 2008-08-11 | 2017-04-27 | Icontrol Networks, Inc. | Integrated cloud system for premises automation |
US11277465B2 (en) | 2004-03-16 | 2022-03-15 | Icontrol Networks, Inc. | Generating risk profile using data of home monitoring and security system |
US11582065B2 (en) | 2007-06-12 | 2023-02-14 | Icontrol Networks, Inc. | Systems and methods for device communication |
US10348575B2 (en) | 2013-06-27 | 2019-07-09 | Icontrol Networks, Inc. | Control system user interface |
US7711796B2 (en) | 2006-06-12 | 2010-05-04 | Icontrol Networks, Inc. | Gateway registry methods and systems |
US11811845B2 (en) | 2004-03-16 | 2023-11-07 | Icontrol Networks, Inc. | Communication protocols over internet protocol (IP) networks |
US10522026B2 (en) | 2008-08-11 | 2019-12-31 | Icontrol Networks, Inc. | Automation system user interface with three-dimensional display |
US20050229243A1 (en) * | 2004-03-31 | 2005-10-13 | Svendsen Hugh B | Method and system for providing Web browsing through a firewall in a peer to peer network |
US8234414B2 (en) | 2004-03-31 | 2012-07-31 | Qurio Holdings, Inc. | Proxy caching in a photosharing peer-to-peer network to improve guest image viewing performance |
US7620033B2 (en) * | 2004-05-21 | 2009-11-17 | Alcatel-Lucent Usa Inc. | Method for optimal path selection in traversal of packets through network address translators |
JP4533247B2 (en) * | 2004-06-08 | 2010-09-01 | キヤノン株式会社 | Service providing system, service providing method, and service providing apparatus |
US20070078720A1 (en) * | 2004-06-29 | 2007-04-05 | Damaka, Inc. | System and method for advertising in a peer-to-peer hybrid communications network |
US7570636B2 (en) | 2004-06-29 | 2009-08-04 | Damaka, Inc. | System and method for traversing a NAT device for peer-to-peer hybrid communications |
US20060206310A1 (en) * | 2004-06-29 | 2006-09-14 | Damaka, Inc. | System and method for natural language processing in a peer-to-peer hybrid communications network |
US7623476B2 (en) * | 2004-06-29 | 2009-11-24 | Damaka, Inc. | System and method for conferencing in a peer-to-peer hybrid communications network |
US20060095365A1 (en) * | 2004-06-29 | 2006-05-04 | Damaka, Inc. | System and method for conducting an auction in a peer-to peer network |
US7623516B2 (en) * | 2004-06-29 | 2009-11-24 | Damaka, Inc. | System and method for deterministic routing in a peer-to-peer hybrid communications network |
US7656870B2 (en) | 2004-06-29 | 2010-02-02 | Damaka, Inc. | System and method for peer-to-peer hybrid communications |
US7933260B2 (en) * | 2004-06-29 | 2011-04-26 | Damaka, Inc. | System and method for routing and communicating in a heterogeneous network environment |
US8437307B2 (en) | 2007-09-03 | 2013-05-07 | Damaka, Inc. | Device and method for maintaining a communication session during a network transition |
US8050272B2 (en) | 2004-06-29 | 2011-11-01 | Damaka, Inc. | System and method for concurrent sessions in a peer-to-peer hybrid communications network |
US8009586B2 (en) * | 2004-06-29 | 2011-08-30 | Damaka, Inc. | System and method for data transfer in a peer-to peer hybrid communication network |
US7778187B2 (en) * | 2004-06-29 | 2010-08-17 | Damaka, Inc. | System and method for dynamic stability in a peer-to-peer hybrid communications network |
US7706401B2 (en) * | 2004-08-13 | 2010-04-27 | Verizon Business Global Llc | Method and system for providing interdomain traversal in support of packetized voice transmissions |
US7502806B2 (en) * | 2004-08-23 | 2009-03-10 | Quiro Holdings, Inc. | Method and system for providing image rich web pages from a computer system over a network |
KR100608582B1 (en) * | 2004-08-28 | 2006-08-03 | 삼성전자주식회사 | Method and apparatus for universal plug and play communication |
US7719971B1 (en) | 2004-09-15 | 2010-05-18 | Qurio Holdings, Inc. | Peer proxy binding |
CN100486193C (en) * | 2004-09-29 | 2009-05-06 | 腾讯科技(深圳)有限公司 | Multi-policy P2P connection establishment method |
US8250230B2 (en) * | 2004-09-30 | 2012-08-21 | Microsoft Corporation | Optimizing communication using scalable peer groups |
US7613703B2 (en) * | 2004-09-30 | 2009-11-03 | Microsoft Corporation | Organizing resources into collections to facilitate more efficient and reliable resource access |
US20070133520A1 (en) * | 2005-12-12 | 2007-06-14 | Microsoft Corporation | Dynamically adapting peer groups |
US7660798B1 (en) * | 2004-10-04 | 2010-02-09 | Adobe Systems Incorporated | System and method for providing document security, access control and automatic identification of recipients |
US8549180B2 (en) * | 2004-10-22 | 2013-10-01 | Microsoft Corporation | Optimizing access to federation infrastructure-based resources |
US7558249B2 (en) * | 2004-11-08 | 2009-07-07 | Panasonic Corporation | Communication terminal, and communication method |
US7698386B2 (en) * | 2004-11-16 | 2010-04-13 | Qurio Holdings, Inc. | Serving content from an off-line peer server in a photosharing peer-to-peer network in response to a guest request |
US7483393B2 (en) * | 2004-12-07 | 2009-01-27 | Cisco Technology, Inc. | Method and apparatus for discovering internet addresses |
US7558862B1 (en) * | 2004-12-09 | 2009-07-07 | LogMeln, Inc. | Method and apparatus for remotely controlling a computer with peer-to-peer command and data transfer |
US7948890B2 (en) * | 2004-12-14 | 2011-05-24 | Industrial Technology Research Institute | System and method for providing a communication channel |
US20060171378A1 (en) * | 2005-01-04 | 2006-08-03 | Harris John C | IP video telephone |
US7912046B2 (en) * | 2005-02-11 | 2011-03-22 | Microsoft Corporation | Automated NAT traversal for peer-to-peer networks |
EP1694034B1 (en) * | 2005-02-16 | 2014-05-21 | Alcatel Lucent | Method to establish a peer-to-peer connection between two user agents located behind symmetric NATs |
CN1825828B (en) * | 2005-02-24 | 2011-04-27 | 北京风行在线技术有限公司 | Method and apparatus for controlling direct transmission communication with two terminals under different NAT |
KR100652958B1 (en) * | 2005-02-28 | 2006-12-01 | 삼성전자주식회사 | Method of transmitting data by improvement of translating network address in gateway and system thereof |
US7646775B2 (en) * | 2005-03-08 | 2010-01-12 | Leaf Networks, Llc | Protocol and system for firewall and NAT traversal for TCP connections |
US7543065B2 (en) * | 2005-03-15 | 2009-06-02 | Microsoft Corporation | Method and system for reducing the number of ports allocated by a relay |
US8713132B2 (en) | 2005-03-16 | 2014-04-29 | Icontrol Networks, Inc. | Device for data routing in networks |
US11496568B2 (en) | 2005-03-16 | 2022-11-08 | Icontrol Networks, Inc. | Security system with networked touchscreen |
US8819178B2 (en) | 2005-03-16 | 2014-08-26 | Icontrol Networks, Inc. | Controlling data routing in integrated security systems |
US9059863B2 (en) * | 2005-03-16 | 2015-06-16 | Icontrol Networks, Inc. | Method for data routing in networks |
US20110128378A1 (en) | 2005-03-16 | 2011-06-02 | Reza Raji | Modular Electronic Display Platform |
US20170180198A1 (en) | 2008-08-11 | 2017-06-22 | Marc Baum | Forming a security network including integrated security system components |
US10999254B2 (en) | 2005-03-16 | 2021-05-04 | Icontrol Networks, Inc. | System for data routing in networks |
US11700142B2 (en) | 2005-03-16 | 2023-07-11 | Icontrol Networks, Inc. | Security network integrating security system and network devices |
US20120324566A1 (en) | 2005-03-16 | 2012-12-20 | Marc Baum | Takeover Processes In Security Network Integrated With Premise Security System |
US9450776B2 (en) | 2005-03-16 | 2016-09-20 | Icontrol Networks, Inc. | Forming a security network including integrated security system components |
US9306809B2 (en) | 2007-06-12 | 2016-04-05 | Icontrol Networks, Inc. | Security system with networked touchscreen |
US8825871B2 (en) * | 2005-03-16 | 2014-09-02 | Icontrol Networks, Inc. | Controlling data routing among networks |
US11615697B2 (en) | 2005-03-16 | 2023-03-28 | Icontrol Networks, Inc. | Premise management systems and methods |
JP4672405B2 (en) * | 2005-03-17 | 2011-04-20 | パナソニック株式会社 | Communication system, information processing system, connection server, processing server, information processing apparatus, and information processing method |
US7522618B2 (en) * | 2005-03-18 | 2009-04-21 | Panasonic Corporation | Communication apparatus, communication system and communication method |
US20060236386A1 (en) * | 2005-03-31 | 2006-10-19 | Popkin Laird A | Method and apparatus for cooperative file distribution in the presence of firewalls |
US7817647B2 (en) * | 2005-04-22 | 2010-10-19 | Microsoft Corporation | Flower-petal resolutions for PNRP |
US7436814B2 (en) * | 2005-04-22 | 2008-10-14 | Cisco Technology, Inc. | Selecting transport addresses to route streams between endpoints |
KR100642935B1 (en) * | 2005-05-06 | 2006-11-10 | (주)아이디스 | Name service system and method thereof |
US8619765B2 (en) * | 2005-06-13 | 2013-12-31 | Cisco Technology, Inc. | Automatic reconfiguration of layer 3 device to layer 2 device upon detection of upstream NAT/NAPT device |
US7631352B1 (en) * | 2005-06-15 | 2009-12-08 | Daniel John Nelson | Link2File automated computer location and linking system |
US8688801B2 (en) | 2005-07-25 | 2014-04-01 | Qurio Holdings, Inc. | Syndication feeds for peer computer devices and peer networks |
CN1917512B (en) * | 2005-08-18 | 2010-09-29 | 腾讯科技(深圳)有限公司 | Method for establishing direct connected peer-to-peer channel |
US20070091907A1 (en) * | 2005-10-03 | 2007-04-26 | Varad Seshadri | Secured media communication across enterprise gateway |
WO2007048344A1 (en) * | 2005-10-28 | 2007-05-03 | Huawei Technologies Co., Ltd. | A method for establishing the peer-to-peer connection, a method device and system for realizing network communication traversal nat |
US7805752B2 (en) * | 2005-11-09 | 2010-09-28 | Symantec Corporation | Dynamic endpoint compliance policy configuration |
US20070112962A1 (en) * | 2005-11-14 | 2007-05-17 | Steve Lewontin | Network connection establishment using out of band connection request |
US8005889B1 (en) | 2005-11-16 | 2011-08-23 | Qurio Holdings, Inc. | Systems, methods, and computer program products for synchronizing files in a photosharing peer-to-peer network |
EP1793563A1 (en) * | 2005-11-30 | 2007-06-06 | Thomson Telecom Belgium | Apparatus and method for connecting to servers located behind a network address translator |
US20070130294A1 (en) * | 2005-12-02 | 2007-06-07 | Leo Nishio | Methods and apparatus for communicating with autonomous devices via a wide area network |
US8788572B1 (en) | 2005-12-27 | 2014-07-22 | Qurio Holdings, Inc. | Caching proxy server for a peer-to-peer photosharing system |
US8296437B2 (en) * | 2005-12-29 | 2012-10-23 | Logmein, Inc. | Server-mediated setup and maintenance of peer-to-peer client computer communications |
US20070153812A1 (en) * | 2005-12-29 | 2007-07-05 | John Kemp | Dynamic discovery of a network service on a mobile device |
DE102006004025A1 (en) * | 2006-01-27 | 2007-08-09 | Siemens Ag | Method for transmitting a message, network node and network |
JP2007226360A (en) * | 2006-02-21 | 2007-09-06 | Sharp Corp | Information terminal, information terminal control method, information terminal control program, and recording medium |
US7609701B2 (en) * | 2006-02-22 | 2009-10-27 | Zheng Yang | Communication using private IP addresses of local networks |
US8788706B2 (en) * | 2006-02-27 | 2014-07-22 | Vudu, Inc. | Method and system for managing data transmission between devices behind network address translators (NATs) |
GB0604573D0 (en) * | 2006-03-07 | 2006-04-19 | Ghost Telecom Ltd | Method and apparatus of interfacing and connecting a wireless devices(s) and a wireless network for in-and out-going SMS, voice-and data-call(s) routing |
US7877457B2 (en) * | 2006-03-17 | 2011-01-25 | Macrovision Corporation | Peer to peer gateway |
US20070253418A1 (en) * | 2006-04-27 | 2007-11-01 | D.S.P. Group Ltd. | Routing path optimization between sip endpoints |
CN100452753C (en) * | 2006-04-28 | 2009-01-14 | 腾讯科技(深圳)有限公司 | Data transmission system and method |
US10079839B1 (en) | 2007-06-12 | 2018-09-18 | Icontrol Networks, Inc. | Activation of gateway device |
US20080317241A1 (en) * | 2006-06-14 | 2008-12-25 | Derek Wang | Code-based echo cancellation |
US20090016333A1 (en) * | 2006-06-14 | 2009-01-15 | Derek Wang | Content-based adaptive jitter handling |
US8239915B1 (en) | 2006-06-30 | 2012-08-07 | Symantec Corporation | Endpoint management using trust rating data |
EP2039138B1 (en) * | 2006-07-07 | 2019-05-22 | Genband US LLC | Identifying network entities in a peer-to-peer network |
US20080031237A1 (en) * | 2006-08-02 | 2008-02-07 | Tsu-Hung Liu | Internet media server finding and playing methodologies |
TW200812316A (en) * | 2006-08-17 | 2008-03-01 | Color City Entpr Co Ltd | SWINT (SIP with interactive NAT traversal) |
WO2008022829A1 (en) * | 2006-08-22 | 2008-02-28 | France Telecom | Method of managing a secure transfer session through an address translation device, corresponding server and computer program |
FR2905812B1 (en) * | 2006-09-08 | 2008-10-24 | Alcatel Sa | TRAVERSSEE OF NAT NAT ADDRESS TRANSLATION EQUIPMENT FOR SIP PROTOCOL SIGNALING MESSAGES |
WO2008035578A1 (en) * | 2006-09-22 | 2008-03-27 | Panasonic Corporation | Communication apparatus, communication method and communication system |
US8554827B2 (en) * | 2006-09-29 | 2013-10-08 | Qurio Holdings, Inc. | Virtual peer for a content sharing system |
US7782866B1 (en) | 2006-09-29 | 2010-08-24 | Qurio Holdings, Inc. | Virtual peer in a peer-to-peer network |
US20080126232A1 (en) * | 2006-11-28 | 2008-05-29 | Kevin Lee | System and method for routing Internet transactions from within an organizational network |
US20090106364A1 (en) * | 2007-10-17 | 2009-04-23 | Nokia Corporation | Method and apparatus for peer-to-peer network traffic analysis |
US7738383B2 (en) * | 2006-12-21 | 2010-06-15 | Cisco Technology, Inc. | Traceroute using address request messages |
US11706279B2 (en) | 2007-01-24 | 2023-07-18 | Icontrol Networks, Inc. | Methods and systems for data communication |
US7633385B2 (en) | 2007-02-28 | 2009-12-15 | Ucontrol, Inc. | Method and system for communicating with and controlling an alarm system from a remote server |
US7764691B2 (en) * | 2007-03-15 | 2010-07-27 | Microsoft Corporation | Allowing IPv4 clients to communicate using teredo addresses when both clients are behind a NAT |
US7715386B2 (en) * | 2007-03-15 | 2010-05-11 | Microsoft Corporation | Reducing network traffic to teredo server |
JP4411332B2 (en) * | 2007-03-20 | 2010-02-10 | パナソニック株式会社 | IP communication apparatus, IP communication system, and these IP communication methods |
US8194683B2 (en) * | 2007-03-30 | 2012-06-05 | Microsoft Corporation | Teredo connectivity between clients behind symmetric NATs |
US7693091B2 (en) * | 2007-03-30 | 2010-04-06 | Microsoft Corporation | Teredo connectivity between clients behind symmetric NATs |
US8451986B2 (en) | 2007-04-23 | 2013-05-28 | Icontrol Networks, Inc. | Method and system for automatically providing alternate network access for telecommunications |
JP4910881B2 (en) * | 2007-05-23 | 2012-04-04 | ブラザー工業株式会社 | Communication system, node device, node processing program, and message transmission / reception method |
US7995478B2 (en) * | 2007-05-30 | 2011-08-09 | Sony Computer Entertainment Inc. | Network communication with path MTU size discovery |
US10616075B2 (en) | 2007-06-12 | 2020-04-07 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US11089122B2 (en) * | 2007-06-12 | 2021-08-10 | Icontrol Networks, Inc. | Controlling data routing among networks |
US10498830B2 (en) | 2007-06-12 | 2019-12-03 | Icontrol Networks, Inc. | Wi-Fi-to-serial encapsulation in systems |
US10389736B2 (en) | 2007-06-12 | 2019-08-20 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US10423309B2 (en) | 2007-06-12 | 2019-09-24 | Icontrol Networks, Inc. | Device integration framework |
US11237714B2 (en) | 2007-06-12 | 2022-02-01 | Control Networks, Inc. | Control system user interface |
US11316753B2 (en) | 2007-06-12 | 2022-04-26 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US10666523B2 (en) | 2007-06-12 | 2020-05-26 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US11646907B2 (en) | 2007-06-12 | 2023-05-09 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US11601810B2 (en) | 2007-06-12 | 2023-03-07 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US11218878B2 (en) | 2007-06-12 | 2022-01-04 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US11423756B2 (en) | 2007-06-12 | 2022-08-23 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US10523689B2 (en) | 2007-06-12 | 2019-12-31 | Icontrol Networks, Inc. | Communication protocols over internet protocol (IP) networks |
US11212192B2 (en) | 2007-06-12 | 2021-12-28 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US10051078B2 (en) | 2007-06-12 | 2018-08-14 | Icontrol Networks, Inc. | WiFi-to-serial encapsulation in systems |
US7804830B2 (en) * | 2007-06-19 | 2010-09-28 | International Secure Virtual Offices (Asia) Pte. Ltd | IP connectivity with NAT traversal |
US8631155B2 (en) * | 2007-06-29 | 2014-01-14 | Microsoft Corporation | Network address translation traversals for peer-to-peer networks |
US7933273B2 (en) * | 2007-07-27 | 2011-04-26 | Sony Computer Entertainment Inc. | Cooperative NAT behavior discovery |
US7876737B2 (en) * | 2007-07-31 | 2011-01-25 | Symbol Technologies, Inc. | Methods and apparatus for locationing based NAT access in wireless networks |
US11831462B2 (en) | 2007-08-24 | 2023-11-28 | Icontrol Networks, Inc. | Controlling data routing in premises management systems |
US9154552B2 (en) | 2007-09-06 | 2015-10-06 | Microsoft Technology Licensing, Llc | Method and apparatus for cooperative file distribution with receiver determined quality of services |
US9483405B2 (en) | 2007-09-20 | 2016-11-01 | Sony Interactive Entertainment Inc. | Simplified run-time program translation for emulating complex processor pipelines |
WO2009043016A2 (en) | 2007-09-28 | 2009-04-02 | Damaka, Inc. | System and method for transitioning a communication session between networks that are not commonly controlled |
CN101132424B (en) * | 2007-09-29 | 2011-08-31 | 杭州华三通信技术有限公司 | Network address conversion method and device thereof |
JP2009089183A (en) * | 2007-10-01 | 2009-04-23 | Brother Ind Ltd | Information processing device and information processing program |
TWI441493B (en) * | 2007-11-27 | 2014-06-11 | Ind Tech Res Inst | System and method for connection of hosts behind nats |
WO2009070718A1 (en) | 2007-11-28 | 2009-06-04 | Damaka, Inc. | System and method for endpoint handoff in a hybrid peer-to-peer networking environment |
US7908393B2 (en) | 2007-12-04 | 2011-03-15 | Sony Computer Entertainment Inc. | Network bandwidth detection, distribution and traffic prioritization |
EP2071809A1 (en) * | 2007-12-13 | 2009-06-17 | Alcatel Lucent | Method of establishing a connection in a peer-to-peer network with network address translation (NAT) |
US9143493B2 (en) * | 2007-12-20 | 2015-09-22 | The Directv Group, Inc. | Method and apparatus for communicating between a user device and a gateway device to form a system to allow a partner service to be provided to the user device |
US11916928B2 (en) | 2008-01-24 | 2024-02-27 | Icontrol Networks, Inc. | Communication protocols over internet protocol (IP) networks |
US20090215438A1 (en) * | 2008-02-23 | 2009-08-27 | Ajay Mittal | Methods for performing transparent callback |
US8825883B2 (en) | 2008-02-29 | 2014-09-02 | Microsoft Corporation | Connectivity platform |
US8364847B2 (en) * | 2008-02-29 | 2013-01-29 | Microsoft Corporation | Address management in a connectivity platform |
US7856506B2 (en) | 2008-03-05 | 2010-12-21 | Sony Computer Entertainment Inc. | Traversal of symmetric network address translator for multiple simultaneous connections |
US20090281833A1 (en) * | 2008-05-09 | 2009-11-12 | Tele Video Md, Inc. | System and method for secure multi-party medical conferencing |
US20170185278A1 (en) | 2008-08-11 | 2017-06-29 | Icontrol Networks, Inc. | Automation system user interface |
TW201006194A (en) * | 2008-07-17 | 2010-02-01 | D Link Corp | Method of building connection channels among network terminal devices using servers with dynamic domain names |
CN101645875A (en) * | 2008-08-04 | 2010-02-10 | 友讯科技股份有限公司 | Method for establishing on-line channel |
TWI385999B (en) * | 2008-08-05 | 2013-02-11 | Davicom Semiconductor Inc | And a method of accessing the connection between the user side and the network device in the network system |
US11258625B2 (en) | 2008-08-11 | 2022-02-22 | Icontrol Networks, Inc. | Mobile premises automation platform |
US10530839B2 (en) | 2008-08-11 | 2020-01-07 | Icontrol Networks, Inc. | Integrated cloud system with lightweight gateway for premises automation |
US11758026B2 (en) | 2008-08-11 | 2023-09-12 | Icontrol Networks, Inc. | Virtual device systems and methods |
US11792036B2 (en) | 2008-08-11 | 2023-10-17 | Icontrol Networks, Inc. | Mobile premises automation platform |
US11729255B2 (en) | 2008-08-11 | 2023-08-15 | Icontrol Networks, Inc. | Integrated cloud system with lightweight gateway for premises automation |
US20160164923A1 (en) * | 2008-08-25 | 2016-06-09 | Paul J. Dawes | Method for data routing in networks |
EP2169903A1 (en) * | 2008-09-30 | 2010-03-31 | France Telecom | Apparatus and method for routing allowing the translation of addresses in cascade in a network |
US8554946B2 (en) * | 2008-10-13 | 2013-10-08 | Telefonaktiebolaget L M Ericsson (Publ) | NAT traversal method and apparatus |
US9049198B2 (en) * | 2008-10-15 | 2015-06-02 | Aster Risk Management Llc | Methods and systems for distributing pull protocol requests via a relay server |
US20100094962A1 (en) * | 2008-10-15 | 2010-04-15 | Patentvc Ltd. | Internet backbone servers with edge compensation |
JP5265016B2 (en) * | 2008-10-29 | 2013-08-14 | ドルビー ラボラトリーズ ライセンシング コーポレイション | Internetworking domain and key system |
US9628440B2 (en) | 2008-11-12 | 2017-04-18 | Icontrol Networks, Inc. | Takeover processes in security network integrated with premise security system |
US9160794B2 (en) * | 2008-12-04 | 2015-10-13 | Microsoft Technology Licensing, Llc | Network address translators (NAT) type detection techniques |
US8121600B2 (en) * | 2008-12-30 | 2012-02-21 | Motorola Mobility, Inc. | Wide area mobile communications over femto-cells |
WO2010076603A1 (en) * | 2008-12-30 | 2010-07-08 | Nokia Corporation | Methods, apparatuses, and computer program products for facilitating randomized port allocation |
US8107956B2 (en) * | 2008-12-30 | 2012-01-31 | Motorola Mobility, Inc. | Providing over-the-top services on femto cells of an IP edge convergence server system |
TW201029413A (en) * | 2009-01-21 | 2010-08-01 | Univ Nat Taipei Technology | NAT traversal method in Session Initial Protocol |
US8612592B2 (en) * | 2009-01-23 | 2013-12-17 | Cisco Technology, Inc. | Protected device initiated pinhole creation to allow access to the protected device in response to a domain name system (DNS) query |
WO2010103781A1 (en) * | 2009-03-13 | 2010-09-16 | 村田機械株式会社 | First relay server and second relay server |
US8149851B2 (en) * | 2009-03-16 | 2012-04-03 | Sling Media, Inc. | Mediated network address translation traversal |
US8032652B2 (en) | 2009-04-30 | 2011-10-04 | Aruba Networks, Inc. | Initiating peer-to-peer tunnels |
US9049045B2 (en) * | 2009-04-24 | 2015-06-02 | Aruba Networks, Inc. | Peer-to-peer forwarding for packet-switched traffic |
US8638211B2 (en) | 2009-04-30 | 2014-01-28 | Icontrol Networks, Inc. | Configurable controller and interface for home SMA, phone and multimedia |
US8274918B2 (en) * | 2009-06-01 | 2012-09-25 | The Regents Of The University Of Michigan | Method for extending the use of single IPv4 addresses to multiple network end-hosts |
KR20100134433A (en) * | 2009-06-15 | 2010-12-23 | 엘지전자 주식회사 | Mobile terminal with function control module and the method thereof |
US9083587B2 (en) * | 2009-08-21 | 2015-07-14 | Cisco Technology, Inc. | Port chunk allocation in network address translation |
TWI408936B (en) * | 2009-09-02 | 2013-09-11 | Ind Tech Res Inst | Network traversal method and network communication system |
US8126987B2 (en) | 2009-11-16 | 2012-02-28 | Sony Computer Entertainment Inc. | Mediation of content-related services |
US8725895B2 (en) | 2010-02-15 | 2014-05-13 | Damaka, Inc. | NAT traversal by concurrently probing multiple candidates |
US8892646B2 (en) | 2010-08-25 | 2014-11-18 | Damaka, Inc. | System and method for shared session appearance in a hybrid peer-to-peer environment |
US8874785B2 (en) * | 2010-02-15 | 2014-10-28 | Damaka, Inc. | System and method for signaling and data tunneling in a peer-to-peer environment |
US8689307B2 (en) * | 2010-03-19 | 2014-04-01 | Damaka, Inc. | System and method for providing a virtual peer-to-peer environment |
US9043488B2 (en) | 2010-03-29 | 2015-05-26 | Damaka, Inc. | System and method for session sweeping between devices |
KR100994076B1 (en) * | 2010-04-12 | 2010-11-12 | 주식회사 나우콤 | Nat-enabled system to prevent the blocking of a normal client's web service using nat and control method thereof |
US9191416B2 (en) | 2010-04-16 | 2015-11-17 | Damaka, Inc. | System and method for providing enterprise voice call continuity |
US8352563B2 (en) | 2010-04-29 | 2013-01-08 | Damaka, Inc. | System and method for peer-to-peer media routing using a third party instant messaging system for signaling |
US10200325B2 (en) * | 2010-04-30 | 2019-02-05 | Shazzle Llc | System and method of delivering confidential electronic files |
WO2011137458A1 (en) | 2010-04-30 | 2011-11-03 | Icontrol Networks, Inc. | Power and data solution for remote low-power devices |
AU2011250886A1 (en) | 2010-05-10 | 2013-01-10 | Icontrol Networks, Inc | Control system user interface |
CN102918811B (en) * | 2010-05-11 | 2016-03-23 | 知惠创出株式会社 | Intercommunication system and the server unit for this system |
US8433759B2 (en) | 2010-05-24 | 2013-04-30 | Sony Computer Entertainment America Llc | Direction-conscious information sharing |
US8446900B2 (en) | 2010-06-18 | 2013-05-21 | Damaka, Inc. | System and method for transferring a call between endpoints in a hybrid peer-to-peer network |
US8611540B2 (en) | 2010-06-23 | 2013-12-17 | Damaka, Inc. | System and method for secure messaging in a hybrid peer-to-peer network |
FR2964524A1 (en) * | 2010-09-07 | 2012-03-09 | France Telecom | DATA PROCESSING FOR THE NOTIFICATION OF EQUIPMENT |
US20120066311A1 (en) * | 2010-09-09 | 2012-03-15 | I O Interconnect, Ltd. | Network connection establishment and data transmission method |
US8468010B2 (en) | 2010-09-24 | 2013-06-18 | Damaka, Inc. | System and method for language translation in a hybrid peer-to-peer environment |
US8836467B1 (en) | 2010-09-28 | 2014-09-16 | Icontrol Networks, Inc. | Method, system and apparatus for automated reporting of account and sensor zone information to a central station |
US8743781B2 (en) | 2010-10-11 | 2014-06-03 | Damaka, Inc. | System and method for a reverse invitation in a hybrid peer-to-peer environment |
US8352576B2 (en) * | 2010-11-15 | 2013-01-08 | Google Inc. | Media file access |
JP5636941B2 (en) * | 2010-12-16 | 2014-12-10 | 村田機械株式会社 | Relay communication system and relay server |
US11750414B2 (en) | 2010-12-16 | 2023-09-05 | Icontrol Networks, Inc. | Bidirectional security sensor communication for a premises security system |
US9147337B2 (en) | 2010-12-17 | 2015-09-29 | Icontrol Networks, Inc. | Method and system for logging security event data |
KR101263783B1 (en) * | 2010-12-27 | 2013-05-13 | 삼성에스디에스 주식회사 | System and method for data transmission using relay server |
US9560141B2 (en) * | 2010-12-29 | 2017-01-31 | Open Invention Network, Llc | Method and apparatus of performing peer-to-peer communication establishment |
US8588233B1 (en) * | 2010-12-31 | 2013-11-19 | Akamai Technologies, Inc. | Peer-to-peer connection establishment using TURN |
WO2012092670A1 (en) | 2011-01-06 | 2012-07-12 | Research In Motion Limited | System and method for enabling a peer-to-peer (p2p) connection |
KR101190307B1 (en) * | 2011-01-14 | 2012-10-12 | 김대영 | Method of transmitting push message |
US8862693B2 (en) * | 2011-03-11 | 2014-10-14 | Qualcomm Incorporated | Remote access and administration of device content and configuration using HTTP protocol |
US9052898B2 (en) | 2011-03-11 | 2015-06-09 | Qualcomm Incorporated | Remote access and administration of device content, with device power optimization, using HTTP protocol |
US8819233B2 (en) | 2011-03-11 | 2014-08-26 | Qualcomm Incorporated | System and method using a web proxy-server to access a device having an assigned network address |
US8799470B2 (en) | 2011-03-11 | 2014-08-05 | Qualcomm Incorporated | System and method using a client-local proxy-server to access a device having an assigned network address |
US8924556B2 (en) * | 2011-03-11 | 2014-12-30 | Qualcomm Incorporated | System and method for accessing a device having an assigned network address |
US8407314B2 (en) | 2011-04-04 | 2013-03-26 | Damaka, Inc. | System and method for sharing unsupported document types between communication devices |
US8776202B2 (en) * | 2011-04-08 | 2014-07-08 | Cisco Technology, Inc. | Method and apparatus to scale authenticated firewall traversal using trusted routing point |
US8694587B2 (en) | 2011-05-17 | 2014-04-08 | Damaka, Inc. | System and method for transferring a call bridge between communication devices |
US8478890B2 (en) | 2011-07-15 | 2013-07-02 | Damaka, Inc. | System and method for reliable virtual bi-directional data stream communications with single socket point-to-multipoint capability |
CN102318323B (en) * | 2011-07-30 | 2013-10-02 | 华为技术有限公司 | NAT disposal method, equipment and system of call between private network and off-network clients |
US9154426B2 (en) * | 2011-10-31 | 2015-10-06 | Apple Inc. | Low-latency hole punching |
TWI434595B (en) * | 2011-11-09 | 2014-04-11 | Quanta Comp Inc | Connection establishing management methods for use in a network system and systems thereof |
EP2805478B1 (en) | 2012-01-18 | 2017-11-22 | Qualcomm Incorporated | Remote access and administration of device content, with device power optimization, using http protocol |
JP5962676B2 (en) * | 2012-02-13 | 2016-08-03 | ソニー株式会社 | Information processing apparatus, information processing method, and program |
KR101758681B1 (en) * | 2012-03-27 | 2017-07-14 | 한화테크윈 주식회사 | Communication system, and data transmitting method in the system |
US20120204228A1 (en) * | 2012-04-18 | 2012-08-09 | Howard Fluker | Methods for hosting data on a group of networked hosts |
US9928975B1 (en) | 2013-03-14 | 2018-03-27 | Icontrol Networks, Inc. | Three-way switch |
US9867143B1 (en) | 2013-03-15 | 2018-01-09 | Icontrol Networks, Inc. | Adaptive Power Modulation |
US9287727B1 (en) | 2013-03-15 | 2016-03-15 | Icontrol Networks, Inc. | Temporal voltage adaptive lithium battery charger |
EP2787693B1 (en) * | 2013-04-05 | 2015-12-09 | Telefonaktiebolaget L M Ericsson (publ) | User plane traffic handling using network address translation and request redirection |
US9027032B2 (en) | 2013-07-16 | 2015-05-05 | Damaka, Inc. | System and method for providing additional functionality to existing software in an integrated manner |
EP3031206B1 (en) | 2013-08-09 | 2020-01-22 | ICN Acquisition, LLC | System, method and apparatus for remote monitoring |
US9379952B2 (en) * | 2013-08-20 | 2016-06-28 | Futurewei Technologies, Inc. | Monitoring NAT behaviors through URI dereferences in web browsers |
US9357016B2 (en) | 2013-10-18 | 2016-05-31 | Damaka, Inc. | System and method for virtual parallel resource management |
US11405463B2 (en) | 2014-03-03 | 2022-08-02 | Icontrol Networks, Inc. | Media content management |
US11146637B2 (en) | 2014-03-03 | 2021-10-12 | Icontrol Networks, Inc. | Media content management |
CN103873826B (en) * | 2014-03-06 | 2017-08-15 | 浙江宇视科技有限公司 | Media stream control method and device |
WO2015136582A1 (en) * | 2014-03-13 | 2015-09-17 | パナソニックIpマネジメント株式会社 | Information device identification system, information device identification method, information device, and program |
US9609056B2 (en) * | 2014-03-29 | 2017-03-28 | Google Technology Holdings LLC | Methods for obtaining content from a peer device |
KR102147246B1 (en) * | 2014-05-26 | 2020-08-24 | 삼성전자 주식회사 | Method and apparatus to improve performance in communication network |
KR101585138B1 (en) * | 2014-06-24 | 2016-01-13 | 주식회사 아이티엑스시큐리티 | Security device connecting system and method using a Peer to Peer relay demon |
CN105208139B (en) * | 2014-06-26 | 2018-08-07 | 浙江大华技术股份有限公司 | A kind of method, the terminal and server of terminal foundation connection |
CN106537885A (en) * | 2014-07-18 | 2017-03-22 | 诺基亚技术有限公司 | Access to a node |
CA2956617A1 (en) | 2014-08-05 | 2016-02-11 | Damaka, Inc. | System and method for providing unified communications and collaboration (ucc) connectivity between incompatible systems |
US9350818B2 (en) * | 2014-09-05 | 2016-05-24 | Openpeak Inc. | Method and system for enabling data usage accounting for unreliable transport communication |
US20170244666A1 (en) * | 2014-09-10 | 2017-08-24 | Gainsborough Hardware Industries Limited | Network control systems, building control systems, remote communication devices and method thereof |
RO131252A2 (en) | 2014-11-27 | 2016-06-30 | Ixia, A California Corporation | Methods, systems and computer-readable medium for receiving test configuration information |
US9118582B1 (en) | 2014-12-10 | 2015-08-25 | Iboss, Inc. | Network traffic management using port number redirection |
RO131360A2 (en) * | 2015-02-09 | 2016-08-30 | Ixia, A California Corporation | Methods, systems and computer-readable medium that facilitate resolving endpoint hostnames in testing-environment with firewalls, network address translations () or clouds |
TWI574536B (en) * | 2015-02-11 | 2017-03-11 | Senao Networks Inc | Domain name resolution using web address translation |
TWI595765B (en) * | 2015-10-22 | 2017-08-11 | 財團法人工業技術研究院 | Method and communication device for network address translation traversal |
US10091025B2 (en) | 2016-03-31 | 2018-10-02 | Damaka, Inc. | System and method for enabling use of a single user identifier across incompatible networks for UCC functionality |
TWI612789B (en) * | 2016-04-07 | 2018-01-21 | 物聯智慧科技(深圳)有限公司 | Network communication system and network-traversal method |
TWI608749B (en) * | 2016-08-31 | 2017-12-11 | 群暉科技股份有限公司 | Method for controlling a client device to access a network device, and associated control apparatus |
US10681005B2 (en) | 2016-12-08 | 2020-06-09 | Keysight Technologies Singapore (Sales) Pte. Ltd. | Deploying a networking test tool in a cloud computing system |
US10666626B2 (en) * | 2017-01-18 | 2020-05-26 | Cisco Technology, Inc. | Graceful handling of dynamic update in peer address of secure communication session |
US20190007293A1 (en) * | 2017-06-28 | 2019-01-03 | Cpacket Networks Inc. | Apparatus and method for correlating network traffic on opposite sides of a network address translator |
CN107979659A (en) * | 2018-01-23 | 2018-05-01 | 深圳市天贝物联科技有限公司 | Convenient access method, system, electronic equipment and storage medium based on domain name |
US10911532B1 (en) * | 2018-01-23 | 2021-02-02 | Whatsapp Inc. | Port prediction for peer-to-peer communications |
US11212260B2 (en) | 2018-03-24 | 2021-12-28 | Keysight Technologies, Inc. | Dynamic firewall configuration and control for accessing services hosted in virtual networks |
US10765952B2 (en) | 2018-09-21 | 2020-09-08 | Sony Interactive Entertainment LLC | System-level multiplayer matchmaking |
US10695671B2 (en) | 2018-09-28 | 2020-06-30 | Sony Interactive Entertainment LLC | Establishing and managing multiplayer sessions |
US11277379B2 (en) * | 2020-05-12 | 2022-03-15 | Citrix Systems, Inc. | Modification of application-provided turn servers |
US11272007B2 (en) * | 2020-07-21 | 2022-03-08 | Servicenow, Inc. | Unified agent framework including push-based discovery and real-time diagnostics features |
US11743349B2 (en) * | 2020-12-29 | 2023-08-29 | Vmware, Inc. | Service request handling with protocol translation |
US11909711B2 (en) * | 2021-05-18 | 2024-02-20 | At&T Intellectual Property I, L.P. | Dynamic port allocations in carrier grade network address translation networks |
US11356296B1 (en) * | 2021-07-30 | 2022-06-07 | Quantum Networks (SG) Pte. Ltd. | System and method for independent binding of virtual networks overlay using a physical network topology |
US11683286B2 (en) * | 2021-11-18 | 2023-06-20 | Cisco Technology, Inc. | Anonymizing server-side addresses |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020083342A1 (en) * | 2000-12-21 | 2002-06-27 | Webb Brian T. | Systems, methods and computer program products for accessing devices on private networks via clients on a public network |
WO2002073921A2 (en) * | 2001-03-09 | 2002-09-19 | Loran Network Management Ltd. | Method to proxy ip services |
US20020147810A1 (en) * | 2001-01-22 | 2002-10-10 | Traversat Bernard A. | Peer-to-peer resource resolution |
Family Cites Families (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6353614B1 (en) * | 1998-03-05 | 2002-03-05 | 3Com Corporation | Method and protocol for distributed network address translation |
US6393488B1 (en) * | 1999-05-27 | 2002-05-21 | 3Com Corporation | System and method for supporting internet protocol subnets with network address translators |
US7797433B2 (en) | 2000-06-30 | 2010-09-14 | Net2Phone | System, method, and computer program product for resolving addressing in a network including a network address translator |
US7042876B1 (en) * | 2000-09-12 | 2006-05-09 | Cisco Technology, Inc. | Stateful network address translation protocol implemented over a data network |
US6661799B1 (en) * | 2000-09-13 | 2003-12-09 | Alcatel Usa Sourcing, L.P. | Method and apparatus for facilitating peer-to-peer application communication |
US20020075844A1 (en) * | 2000-12-15 | 2002-06-20 | Hagen W. Alexander | Integrating public and private network resources for optimized broadband wireless access and method |
KR100360274B1 (en) | 2000-12-30 | 2002-11-09 | 엘지전자 주식회사 | Method for supporting general ip telephone system in nat based private network |
US6993012B2 (en) | 2001-02-20 | 2006-01-31 | Innomedia Pte, Ltd | Method for communicating audio data in a packet switched network |
US6993037B2 (en) * | 2001-03-21 | 2006-01-31 | International Business Machines Corporation | System and method for virtual private network network address translation propagation over nested connections with coincident local endpoints |
US20020157090A1 (en) * | 2001-04-20 | 2002-10-24 | Anton, Jr. Francis M. | Automated updating of access points in a distributed network |
US7227864B2 (en) * | 2001-12-17 | 2007-06-05 | Microsoft Corporation | Methods and systems for establishing communications through firewalls and network address translators |
US20030140142A1 (en) * | 2002-01-18 | 2003-07-24 | David Marples | Initiating connections through firewalls and network address translators |
FI116017B (en) | 2002-01-22 | 2005-08-31 | Netseal Mobility Technologies | Procedure for sending messages over secure mobile communication links |
US20030221009A1 (en) * | 2002-05-21 | 2003-11-27 | Logitech Europe S.A. | Dual mode peer-to-peer link establishment for instant message video |
US7287054B2 (en) * | 2002-05-31 | 2007-10-23 | Microsoft Corporation | Systems and methods for shared browsing among a plurality of online co-users |
US20030233471A1 (en) * | 2002-06-17 | 2003-12-18 | Julian Mitchell | Establishing a call in a packet-based communications network |
US9497168B2 (en) * | 2002-07-30 | 2016-11-15 | Avaya Inc. | Method and apparatus for supporting communications between a computing device within a network and an external computing device |
US7333500B2 (en) * | 2002-09-24 | 2008-02-19 | Nortel Networks Limited | Methods for discovering network address and port translators |
US20040064584A1 (en) * | 2002-09-27 | 2004-04-01 | Julian Mitchell | Apparatus and methods of assisting in NAT traversal |
US8037202B2 (en) * | 2002-10-31 | 2011-10-11 | Oracle America, Inc. | Presence detection using mobile agents in peer-to-peer networks |
US7899932B2 (en) * | 2003-01-15 | 2011-03-01 | Panasonic Corporation | Relayed network address translator (NAT) traversal |
-
2003
- 2003-01-15 US US10/342,304 patent/US7899932B2/en active Active
- 2003-02-25 US US10/372,218 patent/US7328280B2/en active Active
-
2004
- 2004-01-15 WO PCT/JP2004/000259 patent/WO2004064356A2/en active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020083342A1 (en) * | 2000-12-21 | 2002-06-27 | Webb Brian T. | Systems, methods and computer program products for accessing devices on private networks via clients on a public network |
US20020147810A1 (en) * | 2001-01-22 | 2002-10-10 | Traversat Bernard A. | Peer-to-peer resource resolution |
WO2002073921A2 (en) * | 2001-03-09 | 2002-09-19 | Loran Network Management Ltd. | Method to proxy ip services |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7886057B2 (en) | 2003-10-20 | 2011-02-08 | Logitech Europe S.A. | Method and apparatus for communicating data between two hosts |
US8230079B2 (en) | 2003-10-20 | 2012-07-24 | Logitech Europe S.A. | Method and apparatus for communicating data between two hosts |
US7543064B2 (en) | 2004-09-30 | 2009-06-02 | Logitech Europe S.A. | Multiplayer peer-to-peer connection across firewalls and network address translators using a single local port on the local host |
US7738468B2 (en) | 2005-03-22 | 2010-06-15 | Logitech Europe S.A. | Method and apparatus for packet traversal of a network address translation device |
US7957406B2 (en) | 2005-03-22 | 2011-06-07 | Logitech Europe S.A. | Method and apparatus for packet traversal of a network address translation device |
DE102006012614B4 (en) * | 2005-03-22 | 2011-08-18 | Logitech Europe S.A. | Method and apparatus for the passage of packets through a means for network address translation |
US9794218B2 (en) | 2014-04-29 | 2017-10-17 | Trustiosity, Llc | Persistent network addressing system and method |
Also Published As
Publication number | Publication date |
---|---|
WO2004064356A3 (en) | 2004-12-16 |
US20040139228A1 (en) | 2004-07-15 |
US7899932B2 (en) | 2011-03-01 |
US20040139227A1 (en) | 2004-07-15 |
US7328280B2 (en) | 2008-02-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7899932B2 (en) | Relayed network address translator (NAT) traversal | |
US7609701B2 (en) | Communication using private IP addresses of local networks | |
US7590758B2 (en) | Peer-to-peer (P2P) connection despite network address translators (NATs) at both ends | |
US7924832B2 (en) | Facilitating transition of network operations from IP version 4 to IP version 6 | |
EP2306689B1 (en) | Devices and method for accessing a web server in a local space | |
US7272650B2 (en) | Communication protocols operable through network address translation (NAT) type devices | |
KR100650843B1 (en) | Method and system in an ip network for using a network address translationnat with any type of application | |
US8972483B2 (en) | Method and system for providing connectivity between clients connected to the internet | |
KR101232768B1 (en) | Process for managing resource address requests and associated gateway device | |
US20170034174A1 (en) | Method for providing access to a web server | |
EP2449749B1 (en) | Method and apparatus for relaying packets | |
US20130339509A1 (en) | Networking systems | |
JP2007104624A (en) | Network appliance and management method thereof | |
US8234358B2 (en) | Communicating with an entity inside a private network using an existing connection to initiate communication | |
US20040125801A1 (en) | Intermediary device and forwarding method | |
WO2020240046A1 (en) | Transparent multiplexing of ip endpoints | |
CN105391813A (en) | Protocol for sessions traversal across firewall securely (SOKS) transparent proxy method and SOKS transparent proxy device | |
US10673813B2 (en) | Method for NAT traversal in VPN | |
JP2019522416A (en) | System and method for DNS request suppression | |
KR101996588B1 (en) | Network bridge apparatus and control method thereof to support arp protocols | |
Crutcher et al. | Computer Networks and Distributed Systems | |
Santos | Private realm gateway | |
Liao | RESEARCH PROJECT 2: USING TURN SERVERS AS PROXIES | |
US8572283B2 (en) | Selectively applying network address port translation to data traffic through a gateway in a communications network | |
Llorente Santos | Yksityisen alueen yhdyskäytävä |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): BW GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
122 | Ep: pct application non-entry in european phase |