USRE43057E1 - Method and apparatus for facilitating peer-to-peer application communication - Google Patents
Method and apparatus for facilitating peer-to-peer application communication Download PDFInfo
- Publication number
- USRE43057E1 USRE43057E1 US11/299,236 US29923605A USRE43057E US RE43057 E1 USRE43057 E1 US RE43057E1 US 29923605 A US29923605 A US 29923605A US RE43057 E USRE43057 E US RE43057E
- Authority
- US
- United States
- Prior art keywords
- address
- application
- realm
- external
- internal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased, expires
Links
Images
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
-
- 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/2557—Translation policies or rules
-
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
Definitions
- This invention relates to devices for handling communications between applications exchanging data over the Internet. More particularly, this invention relates to a Network Address Translation (NAT) device and a system and method using such NAT device for facilitating peer-to-peer commu-nication of data over the Internet.
- NAT Network Address Translation
- a Network Address Translation (NAT) device 20 of the conventional kind is usually placed within an Internet Protocol (IP) network at the border between two disparate address realms 50 and 30 .
- IP Internet Protocol
- One realm 50 may be a private organization's internal network 10 and the other realm 30 may be the public global Internet.
- IP Internet Protocol
- the problem addressed by such a conventional device is that an organization may require a large internal network, with many devices on it, each device requiring a unique IP address. In view of the currently available address space for unique IP addresses (2 32 available addresses) and present address allocation patterns, this organization may be unable to have allocated to it a sufficient number of official IP addresses, by the authorities that assign such addresses. Therefore, the organization is effectively forced to make up internally valid addresses for its own internal network.
- IP addresses are unique addresses. Any application on the Global Internet sending data to these addresses may rely on that data arriving at the entrance to the organization's internal network. That is, the Global Internet infrastructure will correctly deliver data to the organization, and then (as is the normal case with IP) rely on the organization to locate the right end point endpoint application inside the organization for final delivery.
- NAT NetworkAddress Translator
- the organization's NAT will usually have the ability to use the same official address for multiple internal applications.
- Data arriving for a specific official IP address, say, X may be further distinguished by belonging to one of several data streams, say A, B and C.
- the NAT may have assigned address X, stream A to a specific data stream for one application, while address X streams B and C belong to two different, other applications.
- the stream identifiers are called port numbers.
- a stream of data in an IP network is uniquely identified by the so-called “5-tuple”, which consists of 5 separate numeric quantities:
- Every data item (packet) in an IP network has these 5 numeric identifiers in it.
- the two IP addresses identify, more or less, the source and destination applications.
- the protocol identifies which of the mechanisms for ensuring reliable transport of data are being used. For present purposes the protocol is ignored, because it is not something a NAT does much with.
- the source and destination ports (items 3 and 4 above) identify which application within the network sent and is to receive, respectively, this packet.
- a conventional Network Address Translator (e.g., a Private Internet Exchange (PIX), made by Cisco Systems, Inc. of San Jose, Calif.) as viewed by this document operates by altering these five numeric identifiers within a packet.
- a NAT device resides at the boundary between two address realms, usually, but not always, the Global Internet and an organization's private network, where these two networks have incompatible IP addressing schemes.
- a NAT device uses intelligent re-writing of the four source/destination elements within each packet flowing through it, to present to each of the two networks a false but compatible view of the other network's IP addressing scheme.
- Each NAT must have a set of rules defining the internal address-external address pairing it will use for address translation.
- a useful NAT must build these pairings to allow internal applications to make effective use of available external addresses, which will be limited if the external realm requires official IP addresses.
- a conventional NAT device associated with an internal network supports, essentially, two concurrent modes of operation. The first allows data transactions from applications on the internal network outwards to the Global Internet (for example, a corporate user accessing a web page). This is an Internal Client to External Server access. The second allows applications on the Global Internet to access specific services on specific devices on the internal network (for example, a customer accessing an organization's web site). This is External Client to Internal Server access.
- the way in which the conventional NAT device builds the address pairing that allows the first and second type of access are somewhat different.
- a conventional NAT device implements the first mode as follows: when the initial packet of a data transaction arrives on the NAT device outbound, the NAT device examines the source address and port (which identify the internal device and the application that originated the packet). The NAT then chooses from its pool of available official addresses and ports an externally-valid IP address and port to use in place of the internally-valid source address and port in the packet. The mapping from the internally-valid source address and port to the externally-valid source address and port is maintained somehow within the NAT, for example, in a table defining the correspondence rule. Finally, the NAT modifies the internally-valid source address and port fields in the outbound packet, and sends it on.
- the destination address and port in the reply packet will match the externally-valid source address and port (because in a reply, naturally, the sender address and the recipient address change places, exactly as with, say, a postal letter).
- the NAT uses this incoming externally-valid source address and port to locate the internally-valid source address and port from the initial, outbound packet.
- the NAT uses the located, internally valid source address and port to replace the destination address and port in this incoming reply packet. Now the incoming reply packet has the correct internally-valid destination address and port for delivery to the device and application which sent the initial outbound packet.
- a conventional NAT device implements the second mode using fixed internal-external address correspondence configuration information, defined by the person administrating the NAT.
- the initial packet will be incoming, arriving at the NAT from the outside, with some destination information containing an IP address among those officially allocated, because these externally-valid addresses are the only IP addresses the Global Internet can use to deliver packets to the target organization with the NAT.
- the NAT at the target organization consults its configuration information to determine which (fixed) internally-valid destination IP address and port it should use to replace the externally valid destination address and port contained in the incoming packet.
- an application say, a web server
- the NAT might be configured to recognize that packets addressed to IP address M (officially assigned and externally-valid), port Y should be re-addressed to the internally-valid address, device A/port X.
- Another application at the target organization might be running on another internal device, externally identified as device B, at port Z, and the NAT might use an internal-external address pairing for this application using the same internal address A and some other port, again according to some fixed, pre-defined configuration data.
- the difficulty is that the first mode only allows Internal Clients to send data to (and thereafter receive data from) External Servers, while the second only allows External Clients to send data to (and thereafter receive replies from) a small set of Internal Servers at fixed IP addresses and ports, pre-defined in the NAT associated with the Internal Servers. Transactions in which an External Client connects to a just-created Internal Server at a just-allocated port number are not supported.
- U.S. Pat. No. 6,055,236 is silent on the symmetrical issue of providing addresses for Client-side information, focusing entirely on advertising externally useful addresses for servers and saying nothing regarding external addresses to be used by clients.
- SOCKS is an Internet Engineering Task Force (IETF) standard, which provides a mechanism by which an application can query an application fire wall firewall as to an externally useful address which it can advertise to a remote client application.
- IETF Internet Engineering Task Force
- SOCKS is this application's proxy, which provides services similar to a NAT, but operates quite differently. Rather than re-writing the packet contents as it flows through the device, SOCKS (like any application proxy) will terminate two communication channels, and logically connect them together at a high layer inside itself. For example, a server on the inside of a network might start its service, and then make a request to a SOCKS application at the edge of the network.
- the SOCKS application will start a “thin” server on its host, at the network edge, and then inform the original server of the address and port at which the “thin” server may be found.
- the original server can communicate this information to the client, which connects to the “thin” server which SOCKS is operating.
- SOCKS will then connect to the original server as a client, and then copy data received from the external client to the original server, as well as copying data received from the original server back out to the external client.
- SOCKS is not a NAT and does not operate packet-by-packet, which has certain performance and scaling implications. For more information on SOCKS, see http://www.socks.nec.com.
- IP networks it is expected that there will be an increase in use of IP networks to send data that consists of digitized voice, sound or video (“media” content). What is needed is a method and apparatus for network address translation facilitating peer-to-peer data exchange, including media transmission, over the Internet and other IP networks.
- This invention comprises a network address translation device for facilitating communication between a first application in a first address realm and a second application in a different address realm.
- the device uses an address translator for translating an address valid in the first address realm into an address valid in the second address realm, based on a translation rule and for translating the address valid in the second address realm into the address valid in the first realm. It also uses an address manager for establishing a translation rule by associating an address valid in the first address realm with an address valid in the second address realm.
- control channel communicating with the address manager for receiving from the first application a request for an address valid in the second address realm to be associated with a specified address valid in the first realm and for providing the first application access to the address valid in the second address realm to facilitate communication of the address valid in the second realm to the second application.
- the applications are entities connected for IP telephony.
- the address manager establishes more complex translation rules such that an externally valid destination address could be translated into an internally valid address of one value or a different value depending on the incoming source address.
- Specific remote addresses, larger sets of remote addresses, or any remote address at all could be used as the triggers for the use of special, more complex NAT rules.
- an application is programmed to control, within specified ranges, the translation rules established by the address manager.
- FIG. 1 is a block diagram showing a NAT device as used in a prior art network to connect an internal network with multiple devices or applications to the Internet.
- FIG. 2 is a block diagram showing a NAT device performing address translation according to the prior art.
- FIG. 3 is a block diagram showing a NAT device accord-ing to an embodiment of the present invention for facilitating communication between an application in the address realm served by the NAT and an application in another address realm.
- a system using the present invention is useful for, at least, the new class of Internet applications that operate in a peer-to-peer (two or more devices located anywhere and communicating essentially symmetrically) fashion as opposed to the traditional model in which one device is at a well-known location (IP address), and the other may or may not be located at a well-known location (IP address).
- IP address well-known location
- the new generation of Internet Applications such as IP Telephony, Instant Messaging, and so on, allow users on networks in different address realms to connect directly to one another's computers to share data or to collaborate, or just to chat in a continuous, real-time interaction.
- each user's computer will set up an application that might be termed a micro-server, and then communicate to the other computer, located in a different address realm, an IP address and port at which that micro-server can be reached. (This is the “just-created Internal Server” at the “just-allocated port number” which a conventional NAT device does not handle).
- each user's computer launches a client application to connect to the micro-server in the other's address realm.
- the respective client applications must then be put in possession of an address at which the micro-server on the other computer in the other's address realm can be reached. Thereafter, two-way communication between the two client/micro-server pairs can commence, using the NAT to handle the different address realms.
- FIG. 1 shows the context in which a conventional NAT is used.
- the general problem usually to be solved is that of a large internal network 10 , existing in a realm 50 of un-official, or un-assigned, IP addresses, which are unknown to, or will not be correctly routed by, the Global Internet.
- the NAT device 20 is deployed at the interconnect point (or points) of the internal network 10 to the Global Internet 30 .
- the NAT 20 uses a small pool of officially assigned addresses, the NAT 20 creates the illusion, to the Global Internet 30 , of a small network of devices using the officially assigned IP addresses, and provides some access to the Global Internet 30 to many or all of the devices within the internal network 10 .
- FIG. 2 shows the basic address translation functions of a conventional NAT 120 .
- Host A 110 is part of an address realm 100 serviced by conventional NAT 120 .
- Application A 1 121 is running on Host A. It has a destination or terminating address that is internally valid and is used to get incoming message packets routed to it.
- Application A 1 also may have an originating address that is used to identify Application A 1 as the source of message packets that Application A 1 originates.
- an IP message packet includes a five part IP header.
- an outgoing packet 130 that Application A 1 desires to send to Host R 210 in a remote, external address realm will have the following components in its IP header 140 :
- Host R's reply packet 250 will use externally valid IP addresses in its address header 260 .
- the NAT 120 will need to translate these externally valid addresses into internally valid IP addresses for its address realm 100 .
- the NAT will use hardware and software 122 that apply its translation rules, stored in any form, such as a correspondence table 124 .
- the result transmitted to Host A from Host R is an internally valid packet 150 with appropriately-translated address header 160 that has an internally valid destination address and port, (i.e., the terminating address for Application A 1 ). This permits the internally valid packet 150 with data content 162 to reach Application A 1 .
- micro-servers for the peer-to-peer communication facilitated by the present invention reside, potentially, on any host device within an organization's internal network. These micro-servers generally will be assigned a random, available port number by the underlying operating system (in an operating system specific way) as the port to use for its service; this will be a number currently not in use by any other application on the host device where the micro-servers server runs. Indeed, there is no reason the micro-server needs to reside on the same device as the application communicating the micro-server's address, nor is there a need for the micro-server's client in the other address realm to reside on the same device as the device to which the micro-server's address is to be communicated to set up data exchange. However, if this separation does occur, some intra-network communication must occur so that all the applications will know all the address and port information they need to know.
- client-to-peer applications we will refer to the class of applications discussed herein as “peer-to-peer applications,” which is intended to cover all applications in which two applications communicate over a network in an essentially symmetric fashion, where neither application is clearly a server or a client in the sense of an application providing a service or receiving a service, respectively; rather, both applications perform the same or similar functions on behalf of the other.
- client to mean an application which initiates a data transfer session
- server to mean an application which accepts the initiation of a data transfer session from a client. This is convenient terminology, which helps to define in which direction the initial data packet passing between two applications passes. This initiation step is important for a discussion of NAT behavior.
- client will mean the application or device sending the initial session packet of a data transfer
- server will mean the application or device to which that initial packet is directed.
- IP Telephony is an important example of a peer-to-peer application.
- each end point endpoint application acts as a client by initiating a so-called “media” connection to send packets containing digitized voice to the other, which receives the packets containing digitized voice as a server.
- the relationship is more or less symmetrical, as digitized voice normally passes in both directions.
- a micro-server on an internal network will usually need to communicate its host device's IP address to a remote client (the other IP telephone, or some other device, such as a virtual PBX or other IP telephony gateway acting on behalf of the other telephone).
- the micro-server's internally valid network address won't work for a client on the Global Internet, because this address is not an officially assigned IP address.
- the conventional NAT would still have no procedures or rules for what to do with the first reply packet as sent by the remote client application. That is, unless, the NAT itself took part in this discovery or computation of the official IP address in the initial packet, the NAT will have no translation rule associating the internal network address and any official IP address in an incoming message.
- Efficient peer-to-peer application communication between different address realms requires that the applications (for simplicity, we will confine discussion to two applications exchanging data between them, as opposed to a one-to-many or many-to-many exchange) have access to the official, externally-valid IP address information that will be used in their communication.
- a first application needs to have access to (1) the externally-valid address information others will use to reach it, so that such first application can communicate that address information to a second application in another address realm, and (2) the externally valid address of the second application.
- each of the first and second applications has two addresses: an originating address A O , used to identify the device and port of a sending application as the source of an outbound message packet, and a separate terminating address, A T , used to identify another device and port that will receive inbound message packets.
- a O originating address
- a T separate terminating address
- each of the first and second applications has access to the originating and terminating addresses of the counterpart with which it wants to have peer-to-peer communication.
- FIG. 3 shows a system for facilitating improved communication between two peer applications in different address realms.
- Host A 110 and Host B 310 are both part of address realm 100 .
- Host A has one or more applications running in it.
- Application A 1 121 and Application A 2 122 are shown. Each has an internally valid terminating address and internally valid originating address.
- Host B may also have one or more applications running in it.
- Application B 1 321 and Application B 2 322 are shown.
- Host A and Host B may be on the same network or otherwise connected so that there is a channel 370 (e.g., connection to a common communication network) for communication between Host A and Host B. Additional hosts may also be present in this address realm 100 but are not shown.
- Improved NAT 320 serves the address realm 100 .
- Improved NAT 320 has two functional sections. One is the address translation section 322 , which performs the conventional address translation functions as discussed with respect to NAT 120 in FIG. 2 . The other is the address manager section 324 .
- An IP message channel 360 connects Host A 110 to the address translation section. This channel 360 is used when an application on Host A or any other host served by NAT 320 needs to send out an outgoing message and requires internally valid addresses translated into externally valid addresses. The channel 360 is also used when an incoming message has arrived with an externally valid address, the NAT 320 has translated the externally valid addresses in an incoming message into internally valid addresses and needs to send on the message to the appropriate application in address realm 100 .
- the address translation section 322 is connected to the “outside” address realms.
- FIG. 3 shows a Global Internet realm 400 connected to address translation section 322 .
- Within address realm 400 is another address realm 200 containing Host R 410 and Host S 510 that may host other applications (Applications R 1 , R 2 , S 1 and S 2 are shown by way of example) with which Host A or Host B may communicate.
- Channel 470 e.g., a common network connection
- a control channel 350 connects Host A 110 (and indirectly Host B 310 ) to the address manager section 324 .
- the control channel 350 is used when an application on Host A or any other host served by NAT 320 needs to communicate with NAT 320 to request services of the address manager 324 .
- the address manager can perform several services for a requesting application. First, a requesting application can present an internally-valid address (either an originating address or a terminating address), and ask the address manager 324 to provide an externally valid address paired with the internally valid address and give the address translation section 322 access to this pairing. This can be done so that the address translation section 322 will use this correspondence as its translation rule for incoming and outgoing message packets.
- an application may cause the address manager 324 to add additional or more complex translation rules to those used in the NAT 320 , going beyond simple internal/external pairings. For example, instead of just performing an unconditional substitution of a corresponding internally-valid destination address or port for a specified externally-valid destination address or port found in an incoming message, a more complex translation rule can be built by the address manager 324 at an application's request. A rule could be formulated so that the address translation section 322 checks the incoming source address and/or port and applies a different translation rule depending on the content of that field.
- externally valid address A E in a packet received at NAT 320 is translated into internally valid address A 11 , if a certain source address is present in the packet; but no translation is done and the packet is discarded if that source address is not present. This may be useful for security.
- an externally valid destination port number P E could be translated into an internally valid port number of one value P 11 , or a different value P 12 depending on the incoming source address.
- Specific remote addresses, larger sets of remote addresses, or any remote source address at all could be used as the triggers for the use of special NAT rules.
- an application could specify to the address manager 324 required or desired characteristics for an externally-valid address requested for association with an internally-valid address. This could be useful to let an application specify that the external IP address to result from translation must be a particular IP address or within a specified range of IP addresses.
- the application could establish a NAT rule that would require that the message packet be directed or forced to a particular external server in the public Global Internet that, in turn, would direct the message to a particular private network where a certain type of transmission or billing could occur before the packet was forwarded again into a public Global Internet.
- control channel 350 and the address manager section 324 represent a flexible facility for providing applications both information that they do not get with a conventional NAT and the power to establish certain translation rules for the address translation section 322 of the NAT.
- the address manager 324 can be implemented in hardware or software or a combination of both. For example, it may desirable that the address manager 324 have its own microprocessor and memory for storing the code that determines what services and functions are available in response to control messages from an application. It will further be seen that each application that communicates with the address manager 324 requires hardware and/or software that permits requests to be made over the control channel 350 and requested information or status information returned to the application.
- control channel 350 the function of the control channel 350 and communications between an application and the address manager section 324 and address translation section 322 in several different example situations can be explained. Each example is presented in reference to FIG. 3 .
- Host A 110 in address realm 100 starts a micro-server, an Application A 1 121 that has the purpose of communicating address information to Host R 410 , in address realm 200 outside of address realm 100 , which address information Host R 410 can use to connect to the micro-server, Application A 1 .
- the following steps occur:
- the external Host R 410 in address realm 200 starts a microserver, e.g., an Application R 1 421 .
- Application A 1 has the intention of communicating address information to Host R, in address realm 200 outside of address realm 100 , which address information Host R can use to validate an incoming connection from Host A.
- the following steps occur:
- Host A and Host B make use of a communication channel 370 between them.
- Host A could be a virtual PBX with applications that could address a variety of services (e.g., directory assistance, telephone number to IP address association) needed by an IP telephone or could be some other form of IP telephony gateway.
- services e.g., directory assistance, telephone number to IP address association
- Host B 310 in address realm 100 starts a micro-server, e.g., an Application B 1 321 that has the purpose of communicating address information to Host R, in address realm 200 outside of address realm 100 , which address information Host R (which will act as the client) can use to connect to the micro-server, Application B 1 .
- a micro-server e.g., an Application B 1 321 that has the purpose of communicating address information to Host R, in address realm 200 outside of address realm 100 , which address information Host R (which will act as the client) can use to connect to the micro-server, Application B 1 .
- Address information Host R which will act as the client
- the following steps occur:
- Application A 1 contacts the NAT device 320 over the control channel 350 to inform the address manager 324 of the internally valid IP address and port Application B 1 is using;
- Host R 410 and Host S 510 make use of a communication channel 470 between them. This permits an application on Host R 410 to act as a proxy for an application on Host S 510 .
- Host R 410 could be a virtual PBX with applications that could address a variety of services (e.g., directory assistance, telephone number to IP address association) needed by an IP telephone or could be some other form of IP telephony gateway.
- Host S 510 in address realm 100 starts a micro-server, e.g., an Application 51 .
- Application B 1 has the intention of communicating address information to Host S 510 , in address realm 200 outside of address realm 100 , which address information Host S 510 can use to validate an incoming connection from Host B.
- the following steps occur:
- Application B 1 321 then initiates the connection by sending an outgoing packet addressed to Host S, Application S 1 521 , which packet arrives at the address translation section 322 of NAT device 320 .
- SIP Session Initiation Protocol
- Phone A Assume that someone, using a SIP telephone designated Phone A wishes to make a telephone call to someone else, possibly identified by a telephone number, or some other identifier such as an email address. The person making the call would enter the desired target party by typing in the phone number or other identifier.
- Phone A doesn't know anything about where the target party is, but it does know where a smarter device called a proxy server is.
- Phone A therefore formulates an INVITE message which includes information about who the target is, some other information and—significantly—destination information about where Phone A expects to receive media packets from the target whenever the target is located, rung, and picks up the phone. Phone A will typically supply this information in the form of its own IP address, and a port number. Let us imagine that these are 1 . 1 . 1 . 1 , and 1111 , respectively.
- the proxy server contacted by Phone A will probably send the INVITE on to other proxy server devices, following some network search path, until the target is located.
- the INVITE message originally formulated by Phone A is delivered to the target, which we will designate as Phone B.
- Phone B will presumably ring for a while, and (with luck) someone will pick it up.
- Phone B replies with an OK message, which includes a variety of information, including the destination address at which Phone B expects to receive media. Let's imagine this is IP address 2 . 2 . 2 . 2 , port number 2222 .
- Phone B may begin to send media packets with digitized voice to 1 . 1 . 1 . 1 / 1111 immediately, because it received this information in the INVITE message.
- the OK message returns (through the proxy servers) to Phone A, that phone may begin to send similar media packets to 2 . 2 . 2 . 2 / 2222 .
- Digital audio data is being sent in both directions at this point, and conversation presumably ensues.
- the target phone is eventually located by the proxy servers inside some NAT device.
- the source phone is located inside some NAT device.
- neither phone is located “inside” a NAT device, but the media traffic between them needs to traverse a network located inside a NAT device.
- all NAT devices are of the kind discuss in FIG. 3 .
- proxy server will provide to other proxy servers in the network, as well as to the phones involved, the illusion that there are no NAT devices. Because this can be done successfully, you can actually have many NAT devices working with many proxy servers, each convinced that it is the only NAT, and each convincing the rest of the network that, in effect, “there is no NAT here.”
- Target Phone is Inside a NAT
- the target phone, Phone B which is inside the address realm of a NAT, will have no problem sending data to the originating phone, because a NAT generally provides things “inside” with the ability to simply send traffic out to anywhere, by addressing it to the outside address.
- the difficulty is in sorting out what to tell the originating phone, because the target phone is “inside” a NAT, it cannot be reached from the outside without some help from the NAT.
- the target phone does not use a globally routably IP address; it probably uses a private IP address, an address the rest of the world has no idea how to deliver packets to. Only devices on the target phone's local network can address data to the target phone's actual IP address with any hope of having data delivered to it.
- a proxy server within the target phone's network must be involved. Of course, it will always be involved anyway, because it has responsibility for routing the INVITE to the correct phone within the local network, to complete the call.
- This proxy server will also process the OK response from the target phone.
- the target phone writes its address and port, 2 . 2 . 2 . 2 / 2222 , into this OK message.
- 2 . 2 . 2 . 2 is not a useful address for the originating phone, because it is private and only internally valid.
- the proxy server must, therefore, obtain a different, externally valid address, and replace the address (and possibly port) contained in the OK message before sending it back toward the originating phone.
- the proxy server will make a request to the NAT device of the target phone, a “Server Address/Port Allocation/Discovery” request.
- the NAT will reply with an address and port, say 3 . 3 . 3 . 3 / 3333 , by which devices on the other side (the “outside”) of the NAT device may reach a device at 2 . 2 . 2 . 2 / 2222 (the target phone).
- the proxy server re-writes the OK message to indicate 3 . 3 . 3 . 3 / 3333 instead of 2 . 2 . 2 . 2 / 2222 , and sends this new OK message off to Phone A.
- the proxy server near Phone A (which is now the phone “inside” the NAT, and which has a private IP address useful only within its local network) must re-write the INVITE message after querying the NAT device for an externally valid address. Perhaps the 1 . 1 . 1 . 1 / 1111 address is re-written under the requested NAT rule to 4 . 4 . 4 . 4 / 4444 ( 1 . 1 . 1 . 1 is assumed to be a private IP address, while 4 . 4 . 4 . 4 is not, in this case).
- a media packet from Phone A proceeds outwards through the NAT device unchanged, while a media packet from Phone B, outside the NAT will be addressed to 4 . 4 . 4 . 4 / 4444 , will arrive at the NAT device and be translated to 1 . 1 . 1 . 1 / 1111 , and finally delivered to Phone A inside.
- the network with the NAT devices is a transit network—perhaps a long-distance carrier for IP telephones.
- this network is taking part in the processing and routing of INVITE and OK messages. Perhaps this network provides person-location services, as well as media handling.
- the Ingress Proxy Server performs the same “Server Address/Port Discovery” as in the earlier examples, to discover an address that a device inside the transit network could use to reach Phone A. Let us assume that it performs this operation on a specific NAT device, designated NAT A, which is at the egress point from the transit network to Phone A. Say NAT A returns an address/port, which is 10 . 10 . 10 . 10 / 1010 . This is a private address, useful within the transit network, which things inside that transit network could use to reach Phone A.
- any message packets within the transit network addressed to 10 . 10 . 10 . 10 / 1010 would be routed by the network to NAT A, which would translate the addresses to 1 . 1 . 1 . 1 / 1111 . and send them on to Phone A.
- the INVITE message (now indicating that Phone A wished to receive media at 10 . 10 . 10 . 10 / 1010 ) is sent on across the transit network.
- another proxy server which we will call the Egress Proxy Server because it will handle the INVITE on the way out of the transit network, will receive this INVITE.
- This Egress Proxy Server will perform yet another request, on another NAT device (say, NAT B) well situated to provide traffic to and from Phone B, to discover an address by which things “outside” NAT B may reach the end point currently contained in the INVITE— 10 . 10 . 10 . 10 / 1010 .
- NAT B should respond with some address, say 20 . 20 . 20 . 20 / 2020 .
- the INVITE is then sent on to Phone B, which will send media packets to address 20 . 20 . 20 . 20 / 2020 , per the contents of the INVITE.
- the media packets will travel to address 20 . 20 . 20 . 20 , which will, assuming correct network configuration, cause it to arrive at NAT B, where it will be translated to 10 . 10 . 10 . 10 / 1010 , and thence to NAT A.
- NAT A will translate it to 1 . 1 . 1 . 1 / 1111 , and send it on to Phone A.
- Second the Egress Proxy Server will ask NAT B for an address by which things inside the transit network may reach Phone B (at 2 . 2 . 2 . 2 / 2222 ). Perhaps NAT B will return the address 40 . 40 . 40 . 40 / 4040 .
- the OK message will be re-written by the Egress Proxy Server to indicate this, and be sent on to the Ingress Proxy Server.
- This Proxy Server will ask NAT A for an address by which things outside (say, Phone A) may reach address 40 . 40 . 40 . 40 / 4040 .
- NAT A might return the address 50 . 50 . 50 . 50 / 5050 .
- the OK will be re-written again to indicate this, and be sent on to Phone A, which will then send all its media packets to address 50 . 50 . 50 . 50 / 5050 .
- the upshot is that Phone B sends its media packets to 20 . 20 . 20 . 20 / 2020 , and Phone A will send its media packets to 50 . 50 . 50 . 50 / 5050 , and all the addresses eventually get translated so that the media packets arrive at the right place at the end of the day.
- IP addresses such as 20 . 20 . 20 . 20 and 50 . 50 . 50 . 50 can be forced by applications that the ability to control a NAT and selected to be addresses that belong to the transit network itself, guaranteeing that the packet from the two phones arrive at suitable ingress points to the transit network itself, guaranteeing that the transit network actually handles the media data, and furthermore guaranteeing the ingress point for each media stream. Without this, there is no way the transit network has a priori control over how the media packets get from one of the phones to the other.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Small-Scale Networks (AREA)
Abstract
Description
-
- 1) Source IP address
- 2) Destination IP address
- 3) Source Port Number
- 4) Destination Port Number
- 5) Transport Protocol
-
- 1) Source IP address
- 2) Destination IP address
- 3) Source Port Number
- 4) Destination Port Number
- 5) Transport Protocol
This IP header is followed bydata 142, which may be media. When Application A1 presentsoutgoing message 130 toNAT 120, theNAT 120 must replace any internally valid addresses and port numbers with externally valid addresses and port numbers. TheNAT 120 may have hardware andsoftware 122 that apply its translation rules, stored in any form, such as a correspondence table 124. Typically,Application A1 121 is in possession only of its internally valid Source IP address and Source Port Number (its originating address) and theNAT 120 must translate these as inserted in anyoutgoing message 130 into an externallyvalid address header 240 forpacket 230 before transmitting them on to HostR 210. If we assume for simplicity that Host R is in anaddress realm 200 that uses official IP addresses, no NAT or address translation is needed for it to deliverpacket 230 with the externallyvalid address header 240 to the specified destination IP address and port in Host R'saddress realm 200.
-
- 1.
Application A1 121 contacts theNAT device 320 over thecontrol channel 350 to inform theaddress manager 324 of the internally valid IP address and port Application A1 is using; - 2.
Application A1 121 receives from theaddress manager 324 in return an externally valid IP address and a port number which theNAT device 320 will translate to the internally valid terminating address provided by Application A1 in its request. - 3. Application A1 (which we must assume has the ability to address an IP message packet to Host R, Application R1 421) then sends an IP message packet via the
address translation section 322 ofNAT 320. The data portion of the packet contains the externally valid IP address and a port number to informHost R 410,Application R1 421 how to send packets to Application A1. - 4.
Application R1 421 atHost R 410 sends a connection request per the externally valid IP address and a port number Application A1 gave it, which (being correctly addressed to an official IP address) arrives at theNAT 320, where the externally valid address is translated to Application A1's internally valid address and port. - 5.
NAT 320 sends the reply packet fromApplication R1 421 on toApplication A1 121 on Host A.
Client Address/Port Allocation and Discovery Example:
- 1.
-
- 1.
Application R1 421 sends a packet to Host A requiring from Host A,Application A1 121, information about from which IP address and port the connection fromApplication A1 121 will originate. This originating address information is useful for security and may be required by Application R1 for its own purposes, such as compliance with a communication protocol. - 2.
Application A1 121 on Host A contacts theNAT device 320 over thecontrol channel 350 to inform theaddress manager 324 of the internally valid IP address and port Application A1 will use to communicate with the micro-server on Host R. - 3.
Application A1 121 receives from theaddress manager 324 in return an externally valid IP address and a port number into which theNAT device 320 will translate the internally valid originating address provided by Application A1 in its request. - 4. Application A1 121 (which we must assume has the ability to address an IP message packet to Host R, Application R1) then sends an IP message packet via the
address translation section 322 ofNAT 320. The data portion of the packet contains the externally valid IP address and a port number to inform Host R,Application R1 421 from what IP address and port packets fromApplication A1 121 will originate. - 5.
Application A1 121 then initiates the connection by sending an outgoing packet addressed to Host R,Application R1 421, which packet arrives at theaddress translation section 322 ofNAT device 320. - 6. The
address translation section 322 ofNAT device 320 translates the packet's source address and port (which indicate Application A1's internal IP address and port) to the externally valid version of these (which was passed to Application A1 in step 3 and which Application A1 sent to Application R1 in step 4). - 7. The
address translation section 322 sends the packet on to Host R, Application R1 with the source information Application R1 now expects.
Server Address/Port Alocation and Discovery with Separate Requestor/Server Example:
- 1.
-
- 1.
Application A1 121 communicates with Application B1 overchannel 370 to discover what internally valid address and port can be used to contactApplication B1 321. - 2.
Application A1 121 needs to contact Application R1 inaddress realm 200 to provide Application R1 externally valid address information for Application B1.
- 1.
-
- 3.
Application A1 121 receives from theaddress manager 324 in return an externally valid IP address and a port number which theNAT device 320 will translate to the internally valid terminating address for Application B1 provided by Application A1 in its request. - 4. Application A1 121 (which we must assume has the ability to address an IP message packet to Host R, Application R1 421) then sends an IP message packet via the
address translation section 322 ofNAT 320. The data portion of the packet contains the externally valid IP address and a port number to inform Host R,Application R1 421, how to send packets toApplication B1 321. - 5.
Application R1 421 at Host R sends a connection request per the externally valid IP address and a portnumber Application A1 121 gave it, which (being correctly addressed to an official IP address) arrives at theNAT 320, where the externally valid address is translated to Application B1's internally valid address and port. - 6.
NAT 320 sends the reply from Application R1 on to Application B1 on Host B.
Client Address/Port Allocation and Discovery With Client/Servers Separated From Negotiating Entities Example:
- 3.
-
- 1.
Application R1 421 sends a packet to Host A 110 requiring from Host A,Application A1 121 information about from which IP address and port the connection withApplication B1 321 will originate. This originating address information is useful for security and may be required by Application S1 for its own purposes, such as compliance with a communication protocol - 2.
Application A1 121 communicates withApplication B1 321 overchannel 370 to discover what internally valid address and port will be used byApplication B1 321 tocontact Application S1 521. - 3.
Application A1 121 on Host A contacts theNAT device 320 over thecontrol channel 350 to inform theaddress manager 324 of the internally valid IP address and port Application B1 will use to communicate with the micro-server onHost S 510. - 4.
Application A1 121 receives in return from theaddress manager 324 an externally valid IP address and a port number into which theNAT device 320 will translate the internally valid originating address provided byApplication A1 121 in its request. - 5. Application A1 121 (which we must assume has the ability to address an IP message packet to Host R, Application R1 421) then sends an IP message packet via the
address translation section 322 ofNAT 320. The data portion of the packet contains the externally valid IP address and a port number to inform Host R,Application R1 421 from what IP address and port packets fromApplication B1 321 will originate. - 6.
Application R1 421 will communicate withApplication S1 521 viacommunication channel 470 to communicate toApplication S1 521 the IP address andport Application B1 321 will use to communicate toApplication S1 521.
- 1.
-
- 8. The
address translation section 322 ofNAT device 320 translates the packet's source address and port (which indicate Application B1's internal IP address and port) to the externally valid version of these (which was passed toApplication A1 121 in step 4 and which Application A1 sent toApplication R1 421 in step 5. - 9. The
address translation section 322 sends the packet viaHost R 410 on to Host S,Application S1 521 with the source information Application S1 now expects.
- 8. The
Claims (109)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/299,236 USRE43057E1 (en) | 2000-09-13 | 2005-12-09 | Method and apparatus for facilitating peer-to-peer application communication |
US13/340,938 USRE44593E1 (en) | 2000-09-13 | 2011-12-30 | Method and apparatus for facilitating peer-to-peer application communication |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/661,070 US6661799B1 (en) | 2000-09-13 | 2000-09-13 | Method and apparatus for facilitating peer-to-peer application communication |
US11/299,236 USRE43057E1 (en) | 2000-09-13 | 2005-12-09 | Method and apparatus for facilitating peer-to-peer application communication |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/661,070 Reissue US6661799B1 (en) | 2000-09-13 | 2000-09-13 | Method and apparatus for facilitating peer-to-peer application communication |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/661,070 Continuation US6661799B1 (en) | 2000-09-13 | 2000-09-13 | Method and apparatus for facilitating peer-to-peer application communication |
Publications (1)
Publication Number | Publication Date |
---|---|
USRE43057E1 true USRE43057E1 (en) | 2012-01-03 |
Family
ID=24652085
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/661,070 Ceased US6661799B1 (en) | 2000-09-13 | 2000-09-13 | Method and apparatus for facilitating peer-to-peer application communication |
US11/299,236 Ceased USRE43057E1 (en) | 2000-09-13 | 2005-12-09 | Method and apparatus for facilitating peer-to-peer application communication |
US13/340,938 Expired - Lifetime USRE44593E1 (en) | 2000-09-13 | 2011-12-30 | Method and apparatus for facilitating peer-to-peer application communication |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/661,070 Ceased US6661799B1 (en) | 2000-09-13 | 2000-09-13 | Method and apparatus for facilitating peer-to-peer application communication |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/340,938 Expired - Lifetime USRE44593E1 (en) | 2000-09-13 | 2011-12-30 | Method and apparatus for facilitating peer-to-peer application communication |
Country Status (7)
Country | Link |
---|---|
US (3) | US6661799B1 (en) |
EP (3) | EP1323261B1 (en) |
JP (1) | JP4908724B2 (en) |
CN (2) | CN100512165C (en) |
AU (1) | AU2001287054A1 (en) |
DE (2) | DE60127276T2 (en) |
WO (1) | WO2002023822A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100268763A1 (en) * | 2007-10-08 | 2010-10-21 | Juha Antero Rasanen | Methods, Apparatuses, System, and Related Computer Program Product for Policy Control |
Families Citing this family (113)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2800224B1 (en) * | 1999-10-21 | 2002-12-27 | Ibm | METHOD AND SYSTEM FOR CATCHING HTTP DATA TRANSPORTED WITH SOCKS DATA IN IP DATAGRAMS |
AU2001271263A1 (en) * | 2000-06-30 | 2002-01-14 | Net2Phone | System, method, and computer program product for resolving addressing in a network including a network address translator |
US6661799B1 (en) | 2000-09-13 | 2003-12-09 | Alcatel Usa Sourcing, L.P. | Method and apparatus for facilitating peer-to-peer application communication |
US6870841B1 (en) * | 2000-09-18 | 2005-03-22 | At&T Corp. | Controlled transmission across packet network |
US20020062336A1 (en) * | 2000-11-22 | 2002-05-23 | Dan Teodosiu | Resource coherency among resources cached in a peer to peer environment |
US7072982B2 (en) * | 2000-11-22 | 2006-07-04 | Microsoft Corporation | Universal naming scheme for peer to peer resources |
US7594030B2 (en) * | 2000-11-22 | 2009-09-22 | Microsoft Corporation | Locator and tracking service for peer to peer resources |
US20020085550A1 (en) * | 2000-12-28 | 2002-07-04 | Steven Rhodes | Scalable switch |
US7054304B2 (en) * | 2001-01-19 | 2006-05-30 | Terited International , Inc. | Method and protocol for managing broadband IP services in a layer two broadcast network |
US7293108B2 (en) * | 2001-03-15 | 2007-11-06 | Intel Corporation | Generic external proxy |
US20020138552A1 (en) * | 2001-03-21 | 2002-09-26 | Debruine Timothy S. | Method and system for optimizing private network file transfers in a public peer-to-peer network |
US6983319B1 (en) * | 2001-04-06 | 2006-01-03 | Permeo Technologies, Inc. | Dynamic port management |
US7272650B2 (en) * | 2001-04-17 | 2007-09-18 | Intel Corporation | Communication protocols operable through network address translation (NAT) type devices |
US20030041175A2 (en) * | 2001-05-03 | 2003-02-27 | Singhal Sandeep K | Method and System for Adapting Short-Range Wireless Access Points for Participation in a Coordinated Networked Environment |
US7283526B2 (en) * | 2001-07-19 | 2007-10-16 | International Business Machines Corporation | Method and system for providing a symmetric key for more efficient session identification |
WO2003028340A1 (en) * | 2001-08-30 | 2003-04-03 | Siemens Aktiengesellschaft | Pre- processing of nat addresses |
US7228337B1 (en) * | 2001-09-11 | 2007-06-05 | Cisco Technology, Inc. | Methods and apparatus for providing a network service to a virtual machine |
US7269663B2 (en) * | 2001-09-28 | 2007-09-11 | Intel Corporation | Tagging packets with a lookup key to facilitate usage of a unified packet forwarding cache |
US8095668B2 (en) * | 2001-11-09 | 2012-01-10 | Rockstar Bidco Lp | Middlebox control |
US7006436B1 (en) * | 2001-11-13 | 2006-02-28 | At&T Corp. | Method for providing voice-over-IP service |
US7278157B2 (en) * | 2002-03-14 | 2007-10-02 | International Business Machines Corporation | Efficient transmission of IP data using multichannel SOCKS server proxy |
KR100496734B1 (en) * | 2002-05-02 | 2005-06-22 | 김철동 | Method for delivering data using network |
US7243141B2 (en) | 2002-05-13 | 2007-07-10 | Sony Computer Entertainment America, Inc. | Network configuration evaluation |
US7676579B2 (en) | 2002-05-13 | 2010-03-09 | Sony Computer Entertainment America Inc. | Peer to peer network communication |
KR20030088253A (en) * | 2002-05-14 | 2003-11-19 | (주)크라베르 | Remote computer connection and management system by using a personal terminal based on peer to peer protocol and the method thereof |
US6801528B2 (en) * | 2002-07-03 | 2004-10-05 | Ericsson Inc. | System and method for dynamic simultaneous connection to multiple service providers |
DE10230684A1 (en) * | 2002-07-08 | 2004-01-29 | Siemens Ag | Network with search functions integrated in communication components |
US7836205B2 (en) * | 2002-07-11 | 2010-11-16 | Hewlett-Packard Development Company, L.P. | Method and device for use with a virtual network |
EP1383294A1 (en) * | 2002-07-16 | 2004-01-21 | Siemens Aktiengesellschaft | Method for mapping addresses in packet networks and control device for communication networks |
US8224985B2 (en) * | 2005-10-04 | 2012-07-17 | Sony Computer Entertainment Inc. | Peer-to-peer communication traversing symmetric network address translators |
DE10244710A1 (en) * | 2002-09-25 | 2004-04-08 | Siemens Ag | Protocol selection procedure for transmission of data packets |
TW200412101A (en) * | 2002-12-23 | 2004-07-01 | Shaw-Hwa Hwang | Directly peer-to peer transmission protocol between two virtual network |
US7899932B2 (en) * | 2003-01-15 | 2011-03-01 | Panasonic Corporation | Relayed network address translator (NAT) traversal |
WO2004063843A2 (en) * | 2003-01-15 | 2004-07-29 | Matsushita Electric Industrial Co., Ltd. | PEER-TO-PEER (P2P) CONNECTION DESPITE NETWORK ADDRESS TRANSLATOR (NATs) AT BOTH ENDS |
JP4110977B2 (en) * | 2003-01-21 | 2008-07-02 | 松下電器産業株式会社 | server |
KR100514196B1 (en) * | 2003-02-14 | 2005-09-13 | 삼성전자주식회사 | System and method for Controlling network address translation and session |
DE10321227A1 (en) | 2003-05-12 | 2004-12-09 | Siemens Ag | Process for data exchange between network elements |
US7251745B2 (en) * | 2003-06-11 | 2007-07-31 | Availigent, Inc. | Transparent TCP connection failover |
JP4115354B2 (en) * | 2003-07-04 | 2008-07-09 | 富士フイルム株式会社 | Peer-to-peer communication system |
KR101248090B1 (en) * | 2003-12-01 | 2013-03-27 | 인터디지탈 테크날러지 코포레이션 | Session initiation protocol(sip) based user initiated handoff |
CN100454882C (en) * | 2003-12-19 | 2009-01-21 | 华为技术有限公司 | A breakout routing method for multi-ISP local area network |
CA2557550A1 (en) * | 2004-03-09 | 2005-09-22 | Clique Communications Llc | System and method for peer-to-peer connection of clients behind symmetric firewalls |
US20060007912A1 (en) * | 2004-07-06 | 2006-01-12 | Heng-Chien Chen | Ip-based pbx system and connecting method thereof |
US8990311B2 (en) * | 2004-07-27 | 2015-03-24 | International Business Machines Corporation | Enhanced instant message connectivity |
US20060023646A1 (en) * | 2004-07-30 | 2006-02-02 | George David A | Method and apparatus for anonymous data transfers |
US20060023727A1 (en) * | 2004-07-30 | 2006-02-02 | George David A | Method and apparatus for anonymous data transfers |
US8542813B2 (en) * | 2004-11-02 | 2013-09-24 | Cisco Technology, Inc. | Method and system for providing a camp-on service in telecommunications |
US20060104259A1 (en) * | 2004-11-15 | 2006-05-18 | Cisco Technology, Inc. | System and method for executing a multi-modal transfer in a session initiation protocol (SIP) environment |
US7853696B2 (en) * | 2004-11-19 | 2010-12-14 | Cisco Technology, Inc. | System and method for providing an eCamp feature in a session initiation protocol (SIP) environment |
US7639681B2 (en) * | 2004-11-23 | 2009-12-29 | Microsoft Corporation | System and method for a distributed server for peer-to-peer networks |
US7656878B2 (en) * | 2004-12-03 | 2010-02-02 | Cisco Technology, Inc. | System and method for providing enhanced caller ID in a session initiation protocol (SIP) environment |
US20060146790A1 (en) * | 2004-12-30 | 2006-07-06 | Cisco Technology, Inc. | System and method for providing reach me cover me feature in a session initiation protocol (SIP) environment |
US8254552B2 (en) * | 2005-01-06 | 2012-08-28 | Cisco Technology, Inc. | System and method for providing a recovery mode in a session initiation protocol (SIP) environment |
CN100426769C (en) * | 2005-01-12 | 2008-10-15 | 腾讯科技(深圳)有限公司 | Method for establishing pier-to-pier direct channels |
JP4708036B2 (en) * | 2005-01-21 | 2011-06-22 | パナソニック株式会社 | Communication system, information processing apparatus, server, and information processing method |
US7778404B2 (en) * | 2005-01-27 | 2010-08-17 | Cisco Technology, Inc. | System and method for providing a dial plan conversion in a session initiation protocol (SIP) environment |
US7899175B2 (en) * | 2005-01-27 | 2011-03-01 | Cisco Technology, Inc. | System and method for providing a dial plan conversion in a session initiation protocol (SIP) environment |
US7912046B2 (en) * | 2005-02-11 | 2011-03-22 | Microsoft Corporation | Automated NAT traversal for peer-to-peer networks |
US7853001B2 (en) * | 2005-04-08 | 2010-12-14 | Cisco Technology, Inc. | Method and system for providing a camp-on service |
US7769156B2 (en) * | 2005-04-27 | 2010-08-03 | Cisco Technology, Inc. | System and method for providing a reverse camp-on feature in a communications environment |
US7684434B2 (en) * | 2005-05-03 | 2010-03-23 | Cisco Technology, Inc. | System and method for providing a presence based Camp-On feature in a communications environment |
KR100743055B1 (en) | 2005-05-16 | 2007-07-26 | 주식회사 프리챌 | Search method for search inside fire-wall, and system for enabling the method |
US7894597B2 (en) | 2005-10-12 | 2011-02-22 | Cisco Technology, Inc. | Categorization of telephone calls |
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 |
US8102985B2 (en) * | 2005-11-11 | 2012-01-24 | Cisco Technology, Inc. | Method and system for providing a camp-on hold service |
EP1793564A1 (en) * | 2005-11-30 | 2007-06-06 | Thomson Telecom Belgium | Device and method to detect applications running on a local network for automatically performing the network address translation |
US20070162552A1 (en) * | 2006-01-10 | 2007-07-12 | Cisco Technology, Inc. | Method and system for providing an instant messaging camp-on service |
US20070189294A1 (en) * | 2006-01-28 | 2007-08-16 | Sadler Jonathan B | Methods and Apparatus for Signaling Between Independent Control Networks |
US8280961B2 (en) * | 2006-02-09 | 2012-10-02 | Cisco Technology, Inc. | Method and system for providing a camp-on service for a network service |
US20070189329A1 (en) * | 2006-02-14 | 2007-08-16 | Nokia Corporation | System for combining networks of different addressing schemes |
US7764669B2 (en) * | 2006-02-27 | 2010-07-27 | Cisco Technology, Inc. | System and method providing for interoperability of session initiation protocol (SIP) and H.323 for secure realtime transport protocol (SRTP) session establishment |
US7778274B2 (en) * | 2006-02-27 | 2010-08-17 | Cisco Technology, Inc. | System and method for providing a compatibility feature in a session initiation protocol (SIP) environment |
US20070201459A1 (en) * | 2006-02-27 | 2007-08-30 | Cisco Technology, Inc. | System and method for providing status notification for conventional telephony devices in a session initiation protocol environment |
US7596150B2 (en) * | 2006-02-27 | 2009-09-29 | Cisco Technology, Inc. | System and method for consolidating media signaling to facilitate internet protocol (IP) telephony |
US7701971B2 (en) * | 2006-02-27 | 2010-04-20 | Cisco Technology, Inc. | System and method for providing a compatibility feature in a session initiation protocol (SIP) environment |
US7995559B2 (en) * | 2006-02-27 | 2011-08-09 | Cisco Technology, Inc. | System and method for interworking communication protocols to provide supplementary services |
US7729482B2 (en) * | 2006-02-27 | 2010-06-01 | Cisco Technology, Inc. | Method and system for providing communication protocol interoperability |
US20070201367A1 (en) * | 2006-02-27 | 2007-08-30 | Cisco Technology, Inc. | System and method for interworking H.323 flow control with SIP |
US9967129B1 (en) | 2006-03-09 | 2018-05-08 | Cisco Technology, Inc. | System and method for communicating call information in a sessions initiation protocol (SIP) environment |
US20070226299A1 (en) * | 2006-03-24 | 2007-09-27 | Cisco Technology, Inc. | Method and system for providing an instant messaging quorum monitoring service |
US8036360B1 (en) | 2006-04-28 | 2011-10-11 | Cisco Technology, Inc. | System and method for hook state notification |
US8495231B1 (en) | 2006-05-16 | 2013-07-23 | Cisco Technology, Inc. | System and method for remote call control |
US8015305B1 (en) | 2006-06-28 | 2011-09-06 | Cisco Technology, Inc. | System and method for implementing a session initiation protocol feature |
CA2657094C (en) * | 2006-07-07 | 2018-05-01 | Fringland Ltd. | Identifying network entities in a peer-to-peer network |
US8139566B2 (en) * | 2006-07-21 | 2012-03-20 | Cisco Technology, Inc. | System and method for establishing a communication session between two endpoints that do not both support secure media |
US7769009B1 (en) * | 2006-12-11 | 2010-08-03 | Sprint Communications Company L.P. | Automatic peer to peer mobile device data replication |
WO2008074122A1 (en) * | 2006-12-21 | 2008-06-26 | Bce Inc. | Method and system for managing internal and external calls for a group of communication clients sharing a common customer identifier |
US7995478B2 (en) | 2007-05-30 | 2011-08-09 | Sony Computer Entertainment Inc. | Network communication with path MTU size discovery |
US7933273B2 (en) * | 2007-07-27 | 2011-04-26 | Sony Computer Entertainment Inc. | Cooperative NAT behavior discovery |
US8112516B2 (en) | 2007-08-23 | 2012-02-07 | Cisco Technology, Inc. | Selective user notification based on IP flow information |
CN101127720B (en) * | 2007-09-25 | 2010-09-01 | 中兴通讯股份有限公司 | Method for guaranteeing network address translation and reachability of internal local address |
CN101132424B (en) * | 2007-09-29 | 2011-08-31 | 杭州华三通信技术有限公司 | Network address conversion method and device thereof |
US7856501B2 (en) * | 2007-12-04 | 2010-12-21 | Sony Computer Entertainment Inc. | Network traffic prioritization |
JP5222573B2 (en) * | 2008-01-29 | 2013-06-26 | 株式会社日立製作所 | Server computer and network processing method |
US7856506B2 (en) | 2008-03-05 | 2010-12-21 | Sony Computer Entertainment Inc. | Traversal of symmetric network address translator for multiple simultaneous connections |
US8239550B2 (en) | 2008-05-14 | 2012-08-07 | Nokia Corporation | Methods, apparatuses, and computer program products for facilitating establishing a communications session |
US8560604B2 (en) | 2009-10-08 | 2013-10-15 | Hola Networks Ltd. | System and method for providing faster and more efficient data communication |
CN102137171A (en) * | 2010-01-22 | 2011-07-27 | 正文科技股份有限公司 | Network address translating method, translator and communication system for multimedia streaming |
NO2571207T3 (en) * | 2010-05-11 | 2018-08-04 | ||
JP2012156957A (en) * | 2011-01-28 | 2012-08-16 | Hitachi Ltd | Network system, control device, computer and network device |
US9667713B2 (en) * | 2011-03-21 | 2017-05-30 | Apple Inc. | Apparatus and method for managing peer-to-peer connections between different service providers |
US20130138813A1 (en) * | 2011-11-28 | 2013-05-30 | Microsoft Corporation | Role instance reachability in data center |
WO2014001871A1 (en) * | 2012-06-27 | 2014-01-03 | Ciphergraph Networks Inc. | System and method for facilitating communication between multiple networks |
US9621495B1 (en) * | 2012-12-10 | 2017-04-11 | Jeffrey Brian Shumate | Anonymous messaging proxy |
US9241044B2 (en) | 2013-08-28 | 2016-01-19 | Hola Networks, Ltd. | System and method for improving internet communication by using intermediate nodes |
CN104541491B (en) * | 2014-06-30 | 2017-10-17 | 华为技术有限公司 | Method for pushing, device and the terminal of Webpage |
US11057446B2 (en) | 2015-05-14 | 2021-07-06 | Bright Data Ltd. | System and method for streaming content from multiple servers |
EP3767495B1 (en) | 2017-08-28 | 2023-04-19 | Bright Data Ltd. | Method for improving content fetching by selecting tunnel devices |
EP4177771A1 (en) | 2019-02-25 | 2023-05-10 | Bright Data Ltd. | System and method for url fetching retry mechanism |
WO2020202135A2 (en) | 2019-04-02 | 2020-10-08 | Luminati Networks Ltd. | System and method for managing non-direct url fetching service |
US10986173B1 (en) * | 2019-04-25 | 2021-04-20 | Edjx, Inc. | Systems and methods for locating server nodes for edge devices using latency-based georouting |
US11916995B1 (en) * | 2019-11-04 | 2024-02-27 | Edjx, Inc. | Systems and methods for locating microserver nodes in proximity to edge devices using georouting |
US11089083B1 (en) * | 2019-11-04 | 2021-08-10 | Edjx, Inc. | Systems and methods for locating microserver nodes in proximity to edge devices using georouting |
Citations (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5227778A (en) | 1991-04-05 | 1993-07-13 | Digital Equipment Corporation | Service name to network address translation in communications network |
JPH1056482A (en) | 1996-08-12 | 1998-02-24 | Nippon Telegr & Teleph Corp <Ntt> | Interwork equipment |
US5732078A (en) | 1996-01-16 | 1998-03-24 | Bell Communications Research, Inc. | On-demand guaranteed bandwidth service for internet access points using supplemental user-allocatable bandwidth network |
US5781550A (en) | 1996-02-02 | 1998-07-14 | Digital Equipment Corporation | Transparent and secure network gateway |
US5793763A (en) | 1995-11-03 | 1998-08-11 | Cisco Technology, Inc. | Security system for network address translation systems |
US5883891A (en) | 1996-04-30 | 1999-03-16 | Williams; Wyatt | Method and apparatus for increased quality of voice transmission over the internet |
JPH11150566A (en) | 1997-11-14 | 1999-06-02 | Hitachi Ltd | Internetwork device |
US6006272A (en) | 1998-02-23 | 1999-12-21 | Lucent Technologies Inc. | Method for network address translation |
JP2000059430A (en) | 1998-08-07 | 2000-02-25 | Matsushita Electric Works Ltd | Network address conversion method and its system |
US6038233A (en) | 1996-07-04 | 2000-03-14 | Hitachi, Ltd. | Translator for IP networks, network system using the translator, and IP network coupling method therefor |
US6047325A (en) | 1997-10-24 | 2000-04-04 | Jain; Lalit | Network device for supporting construction of virtual local area networks on arbitrary local and wide area computer networks |
US6055236A (en) | 1998-03-05 | 2000-04-25 | 3Com Corporation | Method and system for locating network services with distributed network address translation |
US6058431A (en) | 1998-04-23 | 2000-05-02 | Lucent Technologies Remote Access Business Unit | System and method for network address translation as an external service in the access server of a service provider |
JP2000138696A (en) | 1998-10-29 | 2000-05-16 | Mitsubishi Materials Corp | Network address converter and its recoding medium |
US6094676A (en) | 1997-05-30 | 2000-07-25 | Hilgraeve Incorporated | Method and apparatus for peer-to-peer communication |
JP2000209278A (en) | 1999-01-12 | 2000-07-28 | Fujitsu Ltd | Router and packet relay system using the router |
JP2000224219A (en) | 1999-01-29 | 2000-08-11 | Internatl Business Mach Corp <Ibm> | Method and system for operating virtual private network |
US6128664A (en) | 1997-10-20 | 2000-10-03 | Fujitsu Limited | Address-translating connection device |
US6128298A (en) | 1996-04-24 | 2000-10-03 | Nortel Networks Corporation | Internet protocol filter |
US6141749A (en) | 1997-09-12 | 2000-10-31 | Lucent Technologies Inc. | Methods and apparatus for a computer network firewall with stateful packet filtering |
US6141341A (en) | 1998-09-09 | 2000-10-31 | Motorola, Inc. | Voice over internet protocol telephone system and method |
US6581108B1 (en) | 1999-11-30 | 2003-06-17 | Lucent Technologies Inc. | Managing multiple private data networks using network and payload address translation |
US6717949B1 (en) * | 1998-08-31 | 2004-04-06 | International Business Machines Corporation | System and method for IP network address translation using selective masquerade |
US6772210B1 (en) * | 2000-07-05 | 2004-08-03 | Nortel Networks Limited | Method and apparatus for exchanging communications between telephone number based devices in an internet protocol environment |
US6779035B1 (en) | 2000-03-06 | 2004-08-17 | Microsoft Corporation | Application programming interface and generalized network address translator for translation of transport-layer sessions |
US20050180433A1 (en) | 2004-02-18 | 2005-08-18 | Alcatel | Bandwidth controller, network and IP subnetwork management process |
US20050286538A1 (en) | 2004-06-29 | 2005-12-29 | Alcatel | Method and call server for establishing a bi-directional peer-to-peer communication link |
US7224687B2 (en) | 2002-02-28 | 2007-05-29 | Lucent Technologies Inc. | Method and apparatus for voice over IP network address translation |
EP1793533A1 (en) | 2000-09-13 | 2007-06-06 | Alcatel USA Sourcing, L.P. | Method an apparatus for facilitating peer-to-peer application communication |
US20080101389A1 (en) | 2006-10-26 | 2008-05-01 | Alcatel Lucent | Network address translation (nat) traversal equipment for signal messages conforming to the sip protocol by redundancy of address information |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6477179B1 (en) * | 1997-05-09 | 2002-11-05 | Sony Corporation | Data receiving device and data receiving method |
WO1999022567A2 (en) * | 1997-11-04 | 1999-05-14 | Koninklijke Philips Electronics N.V. | Communication network with increased routing flexibility |
-
2000
- 2000-09-13 US US09/661,070 patent/US6661799B1/en not_active Ceased
-
2001
- 2001-09-04 DE DE60127276T patent/DE60127276T2/en not_active Expired - Lifetime
- 2001-09-04 AU AU2001287054A patent/AU2001287054A1/en not_active Abandoned
- 2001-09-04 EP EP01966550A patent/EP1323261B1/en not_active Expired - Lifetime
- 2001-09-04 DE DE60138058T patent/DE60138058D1/en not_active Expired - Lifetime
- 2001-09-04 JP JP2002527139A patent/JP4908724B2/en not_active Expired - Lifetime
- 2001-09-04 EP EP09003817.5A patent/EP2068499B1/en not_active Expired - Lifetime
- 2001-09-04 EP EP07005187A patent/EP1793533B8/en not_active Expired - Lifetime
- 2001-09-04 CN CNB018175201A patent/CN100512165C/en not_active Expired - Lifetime
- 2001-09-04 WO PCT/US2001/027382 patent/WO2002023822A1/en active IP Right Grant
- 2001-09-04 CN CN200910145424.6A patent/CN101668051B/en not_active Expired - Lifetime
-
2005
- 2005-12-09 US US11/299,236 patent/USRE43057E1/en not_active Ceased
-
2011
- 2011-12-30 US US13/340,938 patent/USRE44593E1/en not_active Expired - Lifetime
Patent Citations (34)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5227778A (en) | 1991-04-05 | 1993-07-13 | Digital Equipment Corporation | Service name to network address translation in communications network |
US5793763A (en) | 1995-11-03 | 1998-08-11 | Cisco Technology, Inc. | Security system for network address translation systems |
US5732078A (en) | 1996-01-16 | 1998-03-24 | Bell Communications Research, Inc. | On-demand guaranteed bandwidth service for internet access points using supplemental user-allocatable bandwidth network |
US5781550A (en) | 1996-02-02 | 1998-07-14 | Digital Equipment Corporation | Transparent and secure network gateway |
US6128298A (en) | 1996-04-24 | 2000-10-03 | Nortel Networks Corporation | Internet protocol filter |
US5883891A (en) | 1996-04-30 | 1999-03-16 | Williams; Wyatt | Method and apparatus for increased quality of voice transmission over the internet |
US6038233A (en) | 1996-07-04 | 2000-03-14 | Hitachi, Ltd. | Translator for IP networks, network system using the translator, and IP network coupling method therefor |
JPH1056482A (en) | 1996-08-12 | 1998-02-24 | Nippon Telegr & Teleph Corp <Ntt> | Interwork equipment |
US6094676A (en) | 1997-05-30 | 2000-07-25 | Hilgraeve Incorporated | Method and apparatus for peer-to-peer communication |
US6141749A (en) | 1997-09-12 | 2000-10-31 | Lucent Technologies Inc. | Methods and apparatus for a computer network firewall with stateful packet filtering |
US6128664A (en) | 1997-10-20 | 2000-10-03 | Fujitsu Limited | Address-translating connection device |
US6047325A (en) | 1997-10-24 | 2000-04-04 | Jain; Lalit | Network device for supporting construction of virtual local area networks on arbitrary local and wide area computer networks |
JPH11150566A (en) | 1997-11-14 | 1999-06-02 | Hitachi Ltd | Internetwork device |
US6006272A (en) | 1998-02-23 | 1999-12-21 | Lucent Technologies Inc. | Method for network address translation |
US6055236A (en) | 1998-03-05 | 2000-04-25 | 3Com Corporation | Method and system for locating network services with distributed network address translation |
US6058431A (en) | 1998-04-23 | 2000-05-02 | Lucent Technologies Remote Access Business Unit | System and method for network address translation as an external service in the access server of a service provider |
USRE38902E1 (en) | 1998-04-23 | 2005-11-29 | Lucent Technologies Inc. | System and method for network address translation as an external service in the access server of a service provider |
JP2000059430A (en) | 1998-08-07 | 2000-02-25 | Matsushita Electric Works Ltd | Network address conversion method and its system |
US6717949B1 (en) * | 1998-08-31 | 2004-04-06 | International Business Machines Corporation | System and method for IP network address translation using selective masquerade |
US6141341A (en) | 1998-09-09 | 2000-10-31 | Motorola, Inc. | Voice over internet protocol telephone system and method |
US6765920B1 (en) | 1998-10-29 | 2004-07-20 | Mitsubishi Materials Corporation | Network address converting apparatus and storage medium |
JP2000138696A (en) | 1998-10-29 | 2000-05-16 | Mitsubishi Materials Corp | Network address converter and its recoding medium |
JP2000209278A (en) | 1999-01-12 | 2000-07-28 | Fujitsu Ltd | Router and packet relay system using the router |
US6832322B1 (en) * | 1999-01-29 | 2004-12-14 | International Business Machines Corporation | System and method for network address translation integration with IP security |
JP2000224219A (en) | 1999-01-29 | 2000-08-11 | Internatl Business Mach Corp <Ibm> | Method and system for operating virtual private network |
US6615357B1 (en) | 1999-01-29 | 2003-09-02 | International Business Machines Corporation | System and method for network address translation integration with IP security |
US6581108B1 (en) | 1999-11-30 | 2003-06-17 | Lucent Technologies Inc. | Managing multiple private data networks using network and payload address translation |
US6779035B1 (en) | 2000-03-06 | 2004-08-17 | Microsoft Corporation | Application programming interface and generalized network address translator for translation of transport-layer sessions |
US6772210B1 (en) * | 2000-07-05 | 2004-08-03 | Nortel Networks Limited | Method and apparatus for exchanging communications between telephone number based devices in an internet protocol environment |
EP1793533A1 (en) | 2000-09-13 | 2007-06-06 | Alcatel USA Sourcing, L.P. | Method an apparatus for facilitating peer-to-peer application communication |
US7224687B2 (en) | 2002-02-28 | 2007-05-29 | Lucent Technologies Inc. | Method and apparatus for voice over IP network address translation |
US20050180433A1 (en) | 2004-02-18 | 2005-08-18 | Alcatel | Bandwidth controller, network and IP subnetwork management process |
US20050286538A1 (en) | 2004-06-29 | 2005-12-29 | Alcatel | Method and call server for establishing a bi-directional peer-to-peer communication link |
US20080101389A1 (en) | 2006-10-26 | 2008-05-01 | Alcatel Lucent | Network address translation (nat) traversal equipment for signal messages conforming to the sip protocol by redundancy of address information |
Non-Patent Citations (26)
Title |
---|
"Microsoft's Invalidity Contentions Under Patent Rule 3-3 And Document Production Under Patent Rule 3-4" Alcatel USA Resources, Inc., v. Microsoft Corporation, Civil Action No. 6:06-CV-499 (E.D. Tex., Tyler Division, Aug. 7, 2007) 42 pages. Redacted. |
"Microsoft's Invalidity Contentions Under Patent Rule 3-3 And Document Production Under Patent Rule 3-4" Alcatel USA Resources, Inc., v. Microsoft Corporation, Civil Action No. 6:06-CV-499 (E.D. Tex., Tyler Division, Aug. 7, 2007) Appendix A-IETF Negotiated Address Reuse ("[NAR]") 24 pages. |
"Microsoft's Invalidity Contentions Under Patent Rule 3-3 And Document Production Under Patent Rule 3-4" Alcatel USA Resources, Inc., v. Microsoft Corporation, Civil Action No. 6:06-CV-499 (E.D. Tex., Tyler Division, Aug. 7, 2007) Appendix B-UPnP Layer3Forwarding:0.3 Service Template ("[L3F]" 22 pages. |
"Microsoft's Invalidity Contentions Under Patent Rule 3-3 And Document Production Under Patent Rule 3-4" Alcatel USA Resources, Inc., v. Microsoft Corporation, Civil Action No. 6:06-CV-499 (E.D. Tex., Tyler Division, Aug. 7, 2007) Appendix C-IETF IP Network Address Translator Application Programming Interface ("NAT-API") 27 pages. |
"Microsoft's Invalidity Contentions Under Patent Rule 3-3 And Document Production Under Patent Rule 3-4" Alcatel USA Resources, Inc., v. Microsoft Corporation, Civil Action No. 6:06-CV-499 (E.D. Tex., Tyler Division, Aug. 7, 2007) Appendix D-U.S. Pat. No. 6,779,035 B1 32 pages. |
Biggs, B. "A SIP Application Level Gateway for Network Address Translation draft-biggs-sip-nat-00.txt" The Internet Engineering Task Force (IETF), Mar. 2000, 8 pages. |
Borella et al. "Realm Specific IP: Protocol Specification" draft-ietf-nat-rsip-protocol-02.txt, The Internet Engineering Task Force (IETF), Aug. 1999, 27 pages. |
Crocker et al. "Universal Plug and Play Internet Gateway Usage Scenarios" UPnP(TM) Forum, Aug. 19, 2000, 6 pages. |
Crocker et al. "Universal Plug and Play Internet Gateway Usage Scenarios" UPnP™ Forum, Aug. 19, 2000, 6 pages. |
Eun-Sang Lee et al., "An Expanded NAT with Server Connection Ability", IEEE pp. 1391-1394 (1999). |
Iyer et al., Layer3Forwarding:0.3 Service Template For Universal Plug and Play Version 1.0, UPnP(TM) Proposed Service Template, UPnP(TM) Forum, Aug. 5, 2000, 15 pages. |
Iyer et al., Layer3Forwarding:0.3 Service Template For Universal Plug and Play Version 1.0, UPnP™ Proposed Service Template, UPnP™ Forum, Aug. 5, 2000, 15 pages. |
Leech at al. "Socks Protocol Version 5" RFC 1928, The Internet Engineering Task Force (IETF), Mar. 1996, 9 pages. |
Lo J. et al, "IP Host Network Address ( and Port) Translation", URL:http://www.watersprings.org/pub/id/draft-ietf-nat-hnat-00.txt>, Nov. 1998, pp. 1-14. |
Montenegro, G. "Negotiated Address Reuse (NAR)" draft-montenegro-aatn-nar-00.txt The Internet Engineering Task Force (IETF), 1998, 21 pages. |
NAT Working Group, Internet Draft (Informational), P. Srisuresh, Campio Communications, Jul. 2000. |
Network address translation. Retrieved from http:en/wikipedia.org on Nov. 17, 2005. 4 pages. |
Packet-based multimedia communications systems, International Telecommunication Union, Recommendation H.323, Feb. 1998, 117 pages. |
Postel et al. "File Transfer Protocol (FTP)" RFC 959, The Internet Engineering Task Force (IETF), Oct. 1985, 69 pages. |
Rosenberg et al. "Getting SIP through.txt" draft-rosenberg-sip-firewalls-00.txt, The Internet Engineering Task Force (IETF), Feb. 22, 2000, 27 pages. |
Schulzrinne, H. et al., "Internet Telephony: Architecture and Protocols-An IETF Perspective", Computer Networks and ISDN Systems, North Holland Publishing, Amsterdam, NL, vol. 31, No. 3., Feb. 11, 1999, pp. 237-255. |
SIP Components. Retrieved from http://www.cisco.com on Nov. 25, 2005 1 page. |
SIP Overview Retrieved from http://www.cs.columbia.edu/sip/overview.html on Nov. 23, 2005. 2 pages. |
Srisuresh et al. "IP Network Address Translator (NAT) Terminology and Considerations" draft-ietf-nat-terminology-01.txt, The Internet Engineering Task Force (IETF), Oct. 1998, 26 pages. |
Srisuresh et al. "IP Network Address Translator Application Programming Interface" draft-ietf-nat-api-00.txt, The Internet Engineering Task Force (IETF), Nov. 1998, 23 pages. |
Srisuresh et al. "The IP Network Address Translator (NAT)" draft-rfced-info-srisuresh-05.txt, The Internet Engineering Task Force (IETF), Feb. 1998, 21 pages. |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100268763A1 (en) * | 2007-10-08 | 2010-10-21 | Juha Antero Rasanen | Methods, Apparatuses, System, and Related Computer Program Product for Policy Control |
US8356092B2 (en) * | 2007-10-08 | 2013-01-15 | Nokia Siemens Networks Oy | Methods, apparatuses, system, and related computer program product for policy control |
Also Published As
Publication number | Publication date |
---|---|
US6661799B1 (en) | 2003-12-09 |
EP1793533A1 (en) | 2007-06-06 |
EP2068499B1 (en) | 2015-08-26 |
USRE44593E1 (en) | 2013-11-12 |
EP1323261A4 (en) | 2005-02-23 |
DE60127276D1 (en) | 2007-04-26 |
EP1323261A1 (en) | 2003-07-02 |
EP1793533B1 (en) | 2009-03-18 |
AU2001287054A1 (en) | 2002-03-26 |
EP1323261B1 (en) | 2007-03-14 |
CN101668051B (en) | 2014-07-02 |
JP4908724B2 (en) | 2012-04-04 |
DE60127276T2 (en) | 2007-12-20 |
WO2002023822A1 (en) | 2002-03-21 |
CN1531801A (en) | 2004-09-22 |
JP2004509517A (en) | 2004-03-25 |
EP1793533B8 (en) | 2009-07-01 |
CN100512165C (en) | 2009-07-08 |
DE60138058D1 (en) | 2009-04-30 |
EP2068499A1 (en) | 2009-06-10 |
CN101668051A (en) | 2010-03-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
USRE43057E1 (en) | Method and apparatus for facilitating peer-to-peer application communication | |
US9860215B2 (en) | Firewall interface configuration to enable bi-directional VoIP traversal communications | |
US8468259B2 (en) | Middlebox control | |
US6360265B1 (en) | Arrangement of delivering internet protocol datagrams for multimedia services to the same server | |
JP3891195B2 (en) | Data communication method | |
WO2007041417A1 (en) | Peer-to-peer communication traversing symmetric network address translators | |
Paulsamy et al. | Network convergence and the NAT/Firewall problems | |
KR100438182B1 (en) | Method of different IP-address attaching for gatekeeper and NAT-PT | |
JP2002009846A (en) | Communication system employing multimedia proxy server | |
Koski et al. | The sip-based system used in connection with a firewall | |
Sisalem et al. | SIP and IPv6: why and how? | |
Itoh et al. | A study on the applicability of MIDCOM method and a solution to its topology discovery problem | |
Mellouk et al. | A new methodology to adapt SIP Protocol for voice traffic transported over IP Network | |
De Marco et al. | SIP-H323: a solution for interworking saving existing architecture |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: ALCATEL-LUCENT USA INC., NEW JERSEY Free format text: MERGER;ASSIGNOR:ALCATEL USA SOURCING, INC.;REEL/FRAME:027152/0547 Effective date: 20081101 |
|
AS | Assignment |
Owner name: ALCATEL LUCENT, FRANCE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ALCATEL-LUCENT USA INC.;REEL/FRAME:027192/0982 Effective date: 20111101 |
|
AS | Assignment |
Owner name: ALCATEL USA SOURCING, INC., TEXAS Free format text: CHANGE OF NAME;ASSIGNOR:ALCATEL USA SOURCING, L.P.;REEL/FRAME:027196/0671 Effective date: 20061231 |
|
CC | Certificate of correction | ||
RF | Reissue application filed |
Effective date: 20111230 |
|
AS | Assignment |
Owner name: CREDIT SUISSE AG, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:LUCENT, ALCATEL;REEL/FRAME:029821/0001 Effective date: 20130130 Owner name: CREDIT SUISSE AG, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:ALCATEL LUCENT;REEL/FRAME:029821/0001 Effective date: 20130130 |
|
AS | Assignment |
Owner name: ALCATEL USA SOURCING, L.P., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ARAVOX TECHNOLOGIES, INC.;REEL/FRAME:030921/0917 Effective date: 20021220 Owner name: ARAVOX TECHNOLOGIES, MINNESOTA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOLITOR, ANDREW T.;REEL/FRAME:030921/0670 Effective date: 20001127 |
|
AS | Assignment |
Owner name: ALCATEL LUCENT, FRANCE Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG;REEL/FRAME:033868/0001 Effective date: 20140819 |