Source: http://www.google.com/patents/US6496867?dq=5958006
Timestamp: 2016-06-30 22:48:56
Document Index: 660337912

Matched Legal Cases: ['arty 30', 'arty 30', 'arty 30', 'arty 30', 'arty 30', 'arty 30']

Patent US6496867 - System and method to negotiate private network addresses for initiating ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA method for initiating a tunneling association in a data network. The method includes negotiating private addresses, such as private Internet Protocol addresses, for the ends of the tunneling association. The negotiation is performed on a public network, such as the Internet, through a trusted-third-party...http://www.google.com/patents/US6496867?utm_source=gb-gplus-sharePatent US6496867 - System and method to negotiate private network addresses for initiating tunneling associations through private and/or public networksAdvanced Patent SearchPublication numberUS6496867 B1Publication typeGrantApplication numberUS 09/384,120Publication dateDec 17, 2002Filing dateAug 27, 1999Priority dateAug 27, 1999Fee statusPaidPublication number09384120, 384120, US 6496867 B1, US 6496867B1, US-B1-6496867, US6496867 B1, US6496867B1InventorsNurettin B. Beser, Michael BorellaOriginal Assignee3Com CorporationExport CitationBiBTeX, EndNote, RefManPatent Citations (15), Non-Patent Citations (29), Referenced by (146), Classifications (30), Legal Events (9) External Links: USPTO, USPTO Assignment, EspacenetSystem and method to negotiate private network addresses for initiating tunneling associations through private and/or public networks
US 6496867 B1Abstract
A method for initiating a tunneling association in a data network. The method includes negotiating private addresses, such as private Internet Protocol addresses, for the ends of the tunneling association. The negotiation is performed on a public network, such as the Internet, through a trusted-third-party without revealing the private addresses. The method provides for hiding the identity of the originating and terminating ends of the tunneling association from the other users of the public network. Hiding the identities may prevent interception of media flow between the ends of the tunneling association or eavesdropping on Voice-over-Internet-Protocol calls. The method increases the security of communication on the data network without imposing a computational burden on the devices in the data network.
We claim: 1. In a data network having a plurality of private networks and public networks, and a plurality of network devices, a method for initiating a tunneling association between an originating end of the tunneling association and a terminating end of the tunneling association, the method comprising the following steps:
receiving a request to initiate the tunneling association on a first network device, wherein the first network device is associated with the originating end of the tunneling association, and wherein the request includes a unique identifier for the terminating end of the tunneling association; informing a trusted-third-party network device of the request on a public network; associating a public network address for a second network device with the unique identifier for the terminating end of the tunneling association on the trusted-third-party network device, wherein the second network device is associated with the terminating end of the tunneling association; and negotiating a first private network address on the first network device and a second private network address on the second network device through the public network, wherein the first private network address is assigned to the originating end of the tunneling association and the second private network address is assigned to the terminating end of the tunneling association. 2. A computer readable medium having stored therein instructions for causing a central processing unit to execute the method of claim 1.
3. The method of claim 1 wherein the negotiating step further comprises:
negotiating the first private network address on the first network device and the second private network address on the second network device through the trusted-third-party network device. 4. The method of claim 1 wherein the negotiating step further comprises:
selecting the first private network address from a first pool of private addresses on the first network device; communicating the first private network address from the first network device to the second network device through the public network; selecting the second private network address from a second pool of private addresses on the second network device, wherein the second private network address is a different address than the first private network address; and communicating the second private network address from the second network device to the first network device through the public network. 5. The method of claim 1 wherein the negotiating step further comprises:
selecting a plurality of private network addresses from a pool of private addresses on the first network device; communicating the plurality of private network addresses from the first network device to the second network device through the public network; selecting the first private network address and the second private network address from the plurality of private addresses on the second network device, wherein the second private network address is a different address than the first private network address; and communicating the first private network address and the second private network address from the second network device to the first network device through the public network. 6. The method of claim 1 wherein the unique identifier for the terminating end of the tunneling association is any of a dial-up number, an electronic mail address, or a domain name.
7. The method of claim 1 wherein the associating step includes associating the public network address with a lower layer of a protocol stack for the second network device.
8. The method of claim 7 wherein the lower layer of the protocol stack for the second network device is an Internet Protocol layer.
9. The method of claim 1 wherein the first private network address and the second private network address are respectively associated with a higher layer of a protocol stack for the first network device and a higher layer of a protocol stack for the second network device.
10. The method of claim 9 wherein the higher layers of the protocol stacks are application layers.
11. The method of claim 9 wherein the first private network address and the second private network address are private Internet Protocol addresses.
12. The method of claim 1 wherein the receiving step includes receiving the request to initiate the tunneling association in a higher layer of a protocol stack for the first network device.
13. The method of claim 12 wherein the higher layer of the protocol stack for the first network device is an application layer.
14. The method of claim 1 wherein the originating end of the tunneling association and the terminating end of the tunneling association is any of a multimedia device or a telephony device.
15. The method of claim 1 wherein the first network device and the second network device is any of an edge router, a cable modem for a data-over-cable system, or a cable modem termination system for a data-over-cable system.
16. In a data network having a plurality of private networks and public networks, and a plurality of network devices, a method for establishing an end of a tunneling association through a first network device, the method comprising the following steps:
receiving a first message on the first network device from an originating end of a tunneling association, wherein the first message includes a first indicator that the first message is associated with a higher layer of a protocol stack for the first network device and a unique identifier for a terminating end of the tunneling association; assigning a first private network address to the originating end of the tunneling association, wherein the first private network address is associated with the higher layer of the protocol stack for the first network device; transmitting a second message to a trusted-third-party network device on a public network associated with a lower layer of the protocol stack for the first network device, wherein the second message includes a second indicator that the second message is associated with a higher layer of a protocol stack for the trusted-third-party network device and the unique identifier for the terminating end of the tunneling association; receiving a third message on the first network device from the public network, wherein the third message includes a third indicator that the third message is associated with the higher layer of the protocol stack for the first network device, a second private network address for the terminating end of the tunneling association, and a public network address for a second network device associated with the terminating end of the tunneling association; and associating the first private network address with the second private network address in the higher layer of the protocol stack for the first network device. 17. A computer readable medium having stored therein instructions for causing a central processing unit to execute the method of claim 16.
18. The method of claim 16 wherein the transmitting step further comprises:
constructing a payload for the second message in the higher layer of the protocol stack for the first network device; and directing the lower layer of the protocol stack for the first network device to encapsulate and transmit the second message. 19. The method of claim 16 wherein the lower layer of the protocol stack for the first network device is an Internet Protocol layer and the higher layer of the protocol stack for the first network device is an application layer.
20. The method of claim 16 wherein the originating end of the tunneling association is any of a multimedia device or a telephony device, and the first network device is any of an edge router, a cable modem for a data-over-cable system, or a cable modem termination system for a data-over-cable system.
21. In a data network having a plurality of private networks and public networks, and a plurality of network devices, a method for establishing an end of a tunneling association through a first network device, the method comprising the following steps:
receiving a first message on the first network device from a public network associated with a lower layer of a protocol stack for the first network device, wherein the first message includes a first indicator that the first message is associated with a higher layer of the protocol stack for the first network device, a first private network address for an originating end of the tunneling association, and a public network address for a second network device associated with the originating end of the tunneling association; assigning a second private network address to a terminating end of the tunneling association, wherein the second private network address is associated with the higher layer of the protocol stack for the first network device and the second private network address is a different address than the first private network address; transmitting a second message on the public network, wherein the second message includes a second indicator that the second message is associated with a higher layer of a protocol stack for the second network device and the second private network address; and associating the first private network address with the second private network address in the higher layer of the protocol stack for the first network device. 22. A computer readable medium having stored therein instructions for causing a central processing unit to execute the method of claim 21.
23. The method of claim 21 wherein the transmitting step further comprises:
constructing a payload for the second message in the higher layer of the protocol stack for the first network device; and directing the lower layer of the protocol stack for the first network device to encapsulate and transmit the second message. 24. The method of claim 21 wherein the lower layer of the protocol stack for the first network device is an Internet Protocol layer and the higher layer of the protocol stack for the first network device is an application layer.
25. The method of claim 21 wherein the terminating end of the tunneling association is any of a multimedia device or a telephony device, and the first network device is any of an edge router, a cable modem for a data-over-cable system, or a cable modem termination system for a data-over-cable system.
26. In a data network having a plurality of private networks and public networks, and a plurality of network devices, a method for mediating a tunneling association through a trusted-third-party network device, the method comprising the following steps:
receiving a first message on the trusted-third-party network device from a first network device on a public network associated with a lower layer of a protocol stack for the trusted-third-party network device, wherein the first network device is associated with an originating end of the tunneling association, and wherein the first message includes a first indicator that the first message is associated with a higher layer of the protocol stack for the trusted-third-party network device, a first private network address for the originating end of the tunneling association, a unique identifier for a terminating end of the tunneling association, and a first public network address for the first network device; associating a second public network address for a second network device with the unique identifier for the terminating end of the tunneling association on the trusted-third-party network device, wherein the second network device is associated with the terminating end of the tunneling association; transmitting a second message from the trusted-third-party network device to the second network device on the public network, wherein the second message includes a second indicator that the second message is associated with a higher layer of a protocol stack for the second network device, the first private network address, and the first public network address; receiving a third message on the trusted-third-party network device from the second network device on the public network, wherein the third message includes a third indicator that the third message is associated with a higher layer of a protocol stack for the trusted-third-party network device and a second private network address for the terminating end of the tunneling association; associating the first private network address with the second private network address in the higher layer of the protocol stack for the trusted-third-party network device; and transmitting a fourth message from the trusted-third-party network device to the first network device on the public network, wherein the fourth message includes a fourth indicator that the fourth message is associated with a higher layer of a protocol stack for the first network device, the second private network address, and the second public network address. 27. A computer readable medium having stored therein instructions for causing a central processing unit to execute the method of claim 26.
28. The method of claim 26 wherein the step of transmitting the second message further comprises:
constructing a payload for the second message in the higher layer of the protocol stack for the trusted-third-party network device; and directing the lower layer of the protocol stack for the trusted-third-party network device to encapsulate and transmit the second message. 29. The method of claim 26 wherein the step of transmitting the fourth message further comprises:
constructing a payload for the fourth message in the higher layer of the protocol stack for the trusted-third-party network device; and directing the lower layer of the protocol stack for the trusted-third-party network device to encapsulate and transmit the fourth message. 30. The method of claim 26 wherein the lower layer of the protocol stack for the trusted-third-party network device is an Internet Protocol layer and the higher layer of the protocol stack for the trusted-third-party network device is an application layer.
31. The method of claim 26 wherein the unique identifier for the terminating end of the tunneling association is any of a dial-up number, an electronic mail address, or a domain name.
32. The method of claim 26 wherein the trusted-third-party network device is an address supplier.
33. In a data network having a plurality of private networks and public networks, and a plurality of network devices, a method for mediating a tunneling association through a trusted-third-party network device, the method comprising the following steps:
receiving a first message on the trusted-third-party network device from a first network device on a public network associated with a lower layer of a protocol stack for the trusted-third-party network device, wherein the first network device is associated with an originating end of the tunneling association, and wherein the first message includes a first indicator that the first message is associated with a higher layer of the protocol stack for the trusted-third-party network device, a unique identifier for a terminating end of the tunneling association, and a first public network address for the first network device; associating a second public network address for a second network device with the unique identifier for the terminating end of the tunneling association on the trusted-third-party network device, wherein the second network device is associated with the terminating end of the tunneling association; and transmitting a second message from the trusted-third-party network device to the first network device on the public network, wherein the second message includes a second indicator that the second message is associated with a higher layer of a protocol stack for the first network device, and the second public network address. 34. A computer readable medium having stored therein instructions for causing a central processing unit to execute the method of claim 33.
35. The method of claim 33 wherein the step of transmitting the second message further comprises:
constructing a payload for the second message in the higher layer of the protocol stack for the trusted-third-party network device; and directing the lower layer of the protocol stack for the trusted-third-party network device to encapsulate and transmit the second message. 36. The method of claim 33 wherein the lower layer of the protocol stack for the trusted-third-party network device is an Internet Protocol layer and the higher layer of the protocol stack for the trusted-third-party network device is an application layer.
37. The method of claim 33 wherein the unique identifier for the terminating end of the tunneling association is any of a dial-up number, an electronic mail address, or a domain name.
38. The method of claim 33 wherein the trusted-third-party network device is an address supplier.
39. In a data network having a plurality of private networks and public networks, and a plurality of network devices, a method for initiating a Voice-over-Internet-Protocol association between an originating telephony device and a terminating telephony device, the method comprising the following steps:
receiving a request to initiate the Voice-over-Internet-Protocol association on a first network device, wherein the first network device is associated with the originating telephony device, and wherein the request includes a unique identifier for the terminating telephony device; informing a trusted-third-party network device of the request on a public network; associating a public Internet Protocol address for a second network device with the unique identifier for the terminating telephony device on the trusted-third-party network device, wherein the second network device is associated with the terminating telephony device; and negotiating a first private Internet Protocol address on the first network device and a second private Internet Protocol address on the second network device through the public network, wherein the first private Internet Protocol address is assigned to the originating telephony device and the second private Internet Protocol address is assigned to the terminating telephony device. 40. A computer readable medium having stored therein instructions for causing a central processing unit to execute the method of claim 39.
41. The method of claim 39 wherein the first network device and the second network device is any of a cable modem for a data-over-cable system or a cable modem termination system for a data-over-cable system.
The present invention relates to communications in data networks. More specifically, it relates to a method for initiating a tunneling association in a data network.
Computer users are becoming increasingly concerned about the privacy of their communications over the Internet. Privacy concerns are an important factor in the continued growth and acceptance of the Internet by society. As the use of the Internet increases, more and more sensitive information is being transmitted over this global network. Companies who cannot afford a private network often transfer sensitive corporate information over the Internet. Also, private citizens are increasingly relying on the Internet for banking and commercial transactions and frequently have to transfer private or personal information over the Internet, such as credit card numbers, social security numbers, or medical information.
Unfortunately, the Internet is not a very secure network. Information is transmitted over the Internet inside Internet Protocol (“IP”) packets. These packets typically pass through several routers between transmission by a source computer and reception by a destination computer. At each leg of their journey the packets can be intercepted and inspected. Moreover, the Internet Protocol that is used on global computer networks (such as the Internet) and on many private networks (such as intranets) is not a highly secure protocol. For example, because IP packets include a source address in a header, a hacker or cracker may intercept all IP packets from a particular source IP address. Consequently, the hacker may be able to accumulate all transmissions from the source.
Typically, it is easy to map users to source IP addresses. A determined hacker may extract the source IP address from an IP packet and deduce that they are coming from a computer whose IP address is already known. Knowing the location of the source, the hacker may then be able to deduce the identity of the user who sent the IP packet. Even if the hacker cannot exactly identify the user or computer, he may glean sufficient information as to its approximate physical or virtual location. In globally addressed IP subnets it is easy to determine the location or organization of the source computer. For example, an appropriate Domain Name Server (“DNS”) inquiry may correlate the IP address with a domain name, and domain names are typically descriptive of the user, location, or the user's organization.
Of course, the sender may encrypt the information inside the IP packets before transmission, e.g. with IP Security (“IPSec”). However, accumulating all the packets from one source address may provide the hacker with sufficient information to decrypt the message. Moreover, encryption at the source and decryption at the destination may be infeasible for certain data formats. For example, streaming data flows, such as multimedia or Voice-over-Internet-Protocol (“VoIP”), may require a great deal of computing power to encrypt or decrypt the IP packets on the fly. The increased strain on computer power may result in jitter, delay, or the loss of some packets. The expense of added computer power might also dampen the customer's desire to invest in VoIP equipment.
Nonetheless, even if the information inside the IP packets could be concealed, the hacker is still capable of reading the source address of the packets. Armed with the source IP address, the hacker may have the capability of tracing any VoIP call and eavesdropping on all calls from that source. One method of thwarting the hacker is to establish a Virtual Private Network (“VPN”) by initiating a tunneling connection between edge routers on the public network. For example, tunneling packets between two end-points over a public network is accomplished by encapsulating the IP packet to be tunneled within the payload field for another packet that is transmitted on the public network. The tunneled IP packets, however, may need to be encrypted before the encapsulation in order to hide the source IP address. Once again, due to computer power limitations, this form of tunneling may be inappropriate for the transmission of multimedia or VoIP packets.
Another method for tunneling is network address translation (see e.g., “The IP Network Address Translator”, by P. Srisuresh and K. Egevang, Internet Engineering Task Force (“IETF”), Internet Draft <draft-rfced-info-srisuresh-05.txt>, February 1998). However, this type of address translation is also computationally expensive, causes security problems by preventing certain types of encryption from being used, or breaks a number of existing applications in a network that cannot provide network address translation (e.g., File Transfer Protocol (“FTP”)). What is more, network address translation interferes with the end-to-end routing principal of the Internet that recommends that packets flow end-to-end between network devices without changing the contents of any packet along a transmission route (see e.g., “Routing in the Internet,” by C. Huitema, Prentice Hall, 1995, ISBN 0-131-321-927). Once again, due to computer power limitations, this form of tunneling may be inappropriate for the transmission of multimedia or VoIP packets.
It is therefore desirable to establish a tunneling association that hides the identity of the originating and terminating ends of the tunneling association from the other users of a public network. Hiding the identities may prevent a hacker from intercepting all media flow between the ends.
In accordance with preferred embodiments of the present invention, some of the problems associated with initiating a tunneling association are overcome. A method and system for initiating a tunneling association is provided. One aspect of the invention includes a method for initiating a tunneling association between an originating end of the tunneling association and a terminating end of the tunneling association. The method includes receiving a request to initiate the tunneling association on a first network device. The first network device is associated with the originating end of the tunneling association, and the request includes a unique identifier for the terminating end of the tunneling association. A trusted-third-party network device is informed of the request on a public network. A public network address for a second network device is associated with the unique identifier for the terminating end of the tunneling association on the trusted-third-party network device. The second network device is associated with the terminating end of the tunneling association. A first private network address on the first network device and a second private network address on the second network device are negotiated through the public network. The first private network address is assigned to the originating end of the tunneling association and the second private network address is assigned to the terminating end of the tunneling association.
For example, the method and system of the present invention may provide for the initiation of a Voice-over-Internet-Protocol association between an originating telephony device and a terminating telephony device. The method and system described herein may help ensure that the addresses of the ends of the tunneling association are hidden on the public network and may increase the security of communication without an increased computational burden.
FIG. 1 is a block diagram illustrating a network system;
FIG. 3 is a block diagram illustrating the structure of an Internet Protocol packet;
FIG. 4 is a flow diagram illustrating a method for initiating a tunneling association;
FIG. 5 is a flow diagram illustrating a method for initiating a Voice-over-Internet-Protocol association;
FIG. 6 is a block diagram illustrating the message flow of the method illustrated in FIG. 5;
FIG. 7 is a flow diagram illustrating a method for negotiating private network addresses;
FIG. 8 is a flow diagram illustrating a method for negotiating private Internet Protocol addresses;
FIG. 9 is a block diagram illustrating the message flow of the method illustrated in FIG. 8;
FIG. 10 is a flow diagram illustrating a method for negotiating private network addresses;
FIG. 11 is a flow diagram illustrating a method for negotiating private Internet Protocol addresses;
FIG. 12 is a block diagram illustrating the message flow of the method illustrated in FIG. 11;
FIG. 13 is a flow diagram illustrating a method for negotiating private Internet Protocol addresses;
FIG. 14 is a block diagram illustrating the message flow of the method illustrated in FIG. 13;
FIG. 15 is a flow diagram illustrating a method for negotiating private Internet Protocol addresses;
FIG. 16 is a block diagram illustrating the message flow of the method illustrated in FIG. 15; and
FIG. 17 is a block diagram illustrating a configuration of network devices.
FIG. 1 is a block diagram illustrating an exemplary data network 10 for an illustrative embodiment of the present invention. The data network 10 includes a public network 12 (e.g. the Internet or a campus network), a first network device 14, and a second network device 16. The public network 12 is public in the sense that it may be accessible by many users who may monitor communications on it. Additionally, there may be present multiple private networks 20. Also, a trusted-third-party network device 30 is connected to the public network 12. Data packets may be transferred to/from the first network device 14, the second network device 16, and the trusted-third-party network device 30 over the public network 12. For example, the three devices may be assigned public network addresses on the Internet. The first network device 14 and the second network device 16 may be modified routers or modified gateways. The trusted-third-party 30 may be a back-end service, a domain name server, or the owner/manager of database or directory services. Moreover, the trusted-third-party network device 30 may not be located in one physical location but may be distributed over several locations and the information may be replicated over the several locations. However, other data network types and network devices can also be used and the present invention is not limited to the data network an network devices described for an illustrative embodiment.
In one exemplary preferred embodiment of the present invention, the first network device 14 and/or the second network device 16 is an edge router. An edge router routes data packets between one or more networks such as a backbone network (e.g. public network 12) and Local Area Networks (e.g. private network 20). Edge routers include those provided by 3Com Corporation of Santa Clara, Calif., Lucent Technologies of Murray Hill, N.J., Livingston Enterprises, Inc. of Pleasanton, Calif., Ascend Communications of Alameda, Calif., Cisco Systems of San Jose, Calif., and others.
In another exemplary preferred embodiment of the present invention, the first or second network device (14 or 16) is a cable modem (“CM”) or cable modem termination system (“CMTS”). Cable modems and cable modem termination systems offer customers higher-speed connectivity to the Internet, an intranet, Local Area Networks (“LANs”) and other computer networks via cable television networks. CMs and CMTSs include those provided by 3Com Corporation of Santa Clara, Calif., Motorola Corporation of Arlington Heights, Ill., Hewlett-Packard Co. of Palo Alto, Calif., Bay Networks of Santa Clara, Calif., Scientific-Atlanta of Norcross, Ga., General Instruments of Horsham, Pa., and others.
The data network also includes network devices (24, 26) that are originating and terminating ends of data flow. In another exemplary preferred embodiment of the present invention, these network devices (24, 26) are telephony devices or multimedia devices. Multimedia devices include Web-TV sets and decoders, interactive video-game players, or personal computers running multimedia applications. Telephony devices include VoIP devices (portable or stationary) or personal computers running facsimile or audio applications. However, the ends of the data flow may be other types of network devices and the present invention is not restricted to telephony or multimedia devices.
Network devices and routers for preferred embodiments of the present invention include network devices that can interact with network system 10 based on standards proposed by the Institute of Electrical and Electronic Engineers (“IEEE”), International Telecommunications Union-Telecommunication Standardization Sector (“ITU”), Internet Engineering Task Force (“IETF”), or Wireless Application Protocol (“WAP”) Forum. However, network devices based on other standards could also be used. IEEE standards can be found on the World Wide Web at the Universal Resource Locator (“URL”) “www.ieee.org.” The ITU, (formerly known as the CCITT) standards can be found at the URL “www.itu.ch.” IETF standards can be found at the URL “www.ietf.org.” The WAP standards can be found at the URL “www.wapforum.org.”
It will be appreciated that the configuration and devices of FIG. 1 are for illustrative purposes only and the present invention is not restricted to network devices such as edge routers, cable modems, cable modem termination systems, domain name servers, and telephony or multimedia devices. Many other network devices are possible. Moreover, the configuration of data network 10 is not restricted to one public network 12 and one private network 20 as shown in FIG. 1. Many different configurations of the data network 10 with multiple public networks and/or multiple private networks at various positions in the data network 10 are possible.
An operating environment for network devices and modified routers of the present invention include a processing system with at least one high speed Central Processing Unit (“CPU”) and a memory. In accordance with the practices of persons skilled in the art of computer programming, the present invention is described below with reference to acts and symbolic representations of operations or instructions that are performed by the processing system, unless indicated otherwise. Such acts and operations or instructions are referred to as being “computer-executed” or “CPU executed.”
It will be appreciated that acts and symbolically represented operations or instructions include the manipulation of electrical signals or biological signals by the CPU. An electrical system or biological system represents data bits which cause a resulting transformation or reduction of the electrical signals or biological signals, and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPUs operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to the data bits.
FIG. 2 is a block diagram illustrating a protocol stack 50 for network devices in data network 10. As is known in the art, the Open System Interconnection (“OSI”) model is used to describe computer networks. The OSI model consists of seven layers including from lowest-to-highest, a physical, data-link, network, transport, session, presentation and application layer. The physical layer transmits bits over a communication link. The data link layer transmits error free frames of data. The network layer transmits and routes data packets.
The lowest layer of the protocol stack is the physical layer. The physical layer includes the physical media interfaces 52 that place signals on transmission media such as wires, coaxial cable, optical fiber, or transmit them as electromagnetic waves. The physical media interfaces 52 also read signals from the transmission media and present them to the data-link layer.
In the data-link layer is a Medium Access Control (“MAC”) layer 54. As is known in the art, the MAC layer 54 controls access to a transmission medium via the physical layer. For more information on the MAC layer protocol 54 see IEEE 802.3 for Ethernet and IEEE 802.14 for cable modems. However, other MAC layer protocols 54 could also be used and the present invention is not limited to IEEE 802.3 or IEEE 802.14.
Above both the data-link layer is an Internet Protocol (“IP”) layer 58. The IP layer 58, hereinafter IP 58, roughly corresponds to OSI layer 3, the network layer, but is typically not defined as part of the OSI model. As is known in the art, the IP 58 is a routing protocol designed to route traffic within a network or between networks. For more information on the IP 58 see RFC-791 incorporated herein by reference.
The Internet Control Message Protocol (“ICMP”) layer 56 is used for network management. The main functions of the ICMP layer 56, hereinafter ICMP 56, include error reporting, reachability testing (e.g., “pinging”) congestion control, route-change notification, performance, subnet addressing and others. Since the IP 58 is an unacknowledged protocol, datagrams may be discarded and the ICMP 56 is used for error reporting. For more information on the ICMP 56 see RFC-792 incorporated herein by reference.
Above the IP 58 and the ICMP 56 is a transport layer with a User Datagram Protocol layer 60 (“UDP”). The UDP layer 60, hereinafter UDP 60, roughly corresponds to OSI layer 4, the transport layer, but is typically not defined as part of the OSI model. As is known in the art, the UDP 60 provides a connectionless mode of communications with datagrams. For more information on the UDP 60 see RFC-768 incorporated herein by reference. The transport layer may also include a Transmission Control Protocol (“TCP”) layer (not illustrated in FIG. 2). For more information on TCP see RFC-793 incorporated herein by reference.
Above the transport layer is an application layer where the application programs that carry out desired functionality for a network device reside. For example, the application programs for the network device 26 may include printer application programs, while application programs for the network device 24 may include facsimile application programs.
In the application layer are typically a Simple Network Management Protocol (“SNMP”) layer 62, a Trivial File Protocol (“TFTP”) layer 64, a Dynamic Host Configuration Protocol (“DHCP”) layer 66 and a UDP manager 68. The SNMP layer 62 is used to support network management functions. For more information on the SNMP layer 62 see RFC-1157 incorporated herein by reference. The TFTP layer 64 is a file transfer protocol used to download files and configuration information. For more information on the TFTP layer 64 see RFC-1350 incorporated herein by reference. The DHCP layer 66 is a protocol for passing configuration information to hosts on an IP 58 network. For more information on the DHCP layer 66 see RFC-1541 incorporated herein by reference. The UDP manager 68 distinguishes and routes packets to an appropriate service. More or fewer protocol layers can also be used in the protocol stack 50.
One service that can be performed in the application layer is that of initiating and maintaining a virtual tunnel. Virtual tunneling techniques are known to those skilled in the art. Examples of virtual tunneling include Internet Encapsulation Protocol tunneling, Generic Route Encapsulation (“GRE”), and IP in IP tunneling. All three tunneling techniques are based on encapsulating a data packet of one protocol inside a data packet of another protocol. For more information on Internet Encapsulation Protocol tunneling see RFC-1241, on GRE see RFC-1701, and on IP in IP tunneling see RFC-1853, all of which are incorporated herein by reference. Another example of a virtual tunnel service is the Host Application Based Integrated Total Address Translation (“HABITAT”) system by the 3Com Corporation of Santa Clara, Calif.
Internet Protocol Data Packets
The IP 58 layer transmits and routes IP 58 packets. FIG. 3 is a block diagram illustrating the structure of an IP 58 packet. The IP 58 packet 80 includes a header field 82 and a payload field 84. The payload field 84 of the IP 58 packet 80 typically comprises the data that is sent from one network device to another. However, the payload field 84 may also comprise network management messages, such as ICMP 56 messages, or data packets of another protocol such as UDP 60, SNMP 62, TFTP 64, or DHCP 66. The header field 82 includes header beginning fields 86, a source address field 88, a destination address field 90, and header end fields 92. The header beginning fields 86 may include control information fields such as a version field, a header length field, a type of service field, a total length field, an identification field, a fragment offset field, a time-to-live field, a protocol field, a header checksum field, and other fields known to those skilled in the art. The header end fields 92 may include an options field and other fields known to those skilled in the art. For more information on the structure of an IP 58 packet 80 see RFC-791 incorporated herein by reference.
As is known in the art, the transfer of data from a transmitting network device to a receiving network device using the Internet Protocol is as follows: The data is broken into multiple UDP 60 datagrams in the transport layer of the protocol stack 50 of the transmitting network device. Each UDP 60 datagram is passed to the IP 58 layer for encapsulation. In the IP 58 layer, an IP 58 packet 80 is constructed with the payload field 84 consisting of the UDP 60 datagram. The IP 58 address of the transmitting network device is placed in the source address field 88 and the IP 58 address of the receiving network device is placed in the destination address field 90. The complete IP 58 packet is passed to the data-link layer where it is encapsulated in a MAC 54 frame. The physical layer receives the MAC 54 frame from the data-link layer and transmits it over a physical medium associated with its hardware.
On the receiving network device, the receiver on its physical layer is monitoring the physical media for activity. When activity is detected, the physical layer of the protocol stack 50 for the receiving network device examines the activity to discern whether the activity contains a MAC 54 frame. If so, the MAC 54 frame is passed up to the MAC 54 layer which ascertains whether the MAC 54 frame contains the MAC 54 address of the receiving network device in the destination address field of the MAC 54 header. If so, the MAC 54 header and trailer are removed and the IP 58 packet is passed to the network layer. The IP 58 layer examines the IP 58 packet and ascertains whether the IP 58 destination address field 90 contains the IP 58 address assigned to the receiving network device. If so, the IP 58 header field 82 is stripped off and the data in the payload field 84, i.e. the transmitted UDP 60 datagram, is passed to the transport layer of the protocol stack. The UDP 60 layer collects the UDP 60 datagrams and reconstitutes the original data.
Initiating a Tunneling Association
FIG. 4 is a flow diagram illustrating a Method 100 for initiating a tunneling association between an originating end and a terminating end of the tunneling association. The Method 100 includes receiving a request to initiate the tunneling connection on a first network device at Step 102. The first network device is associated with the originating end of the tunneling association. The request includes a unique identifier for the terminating end of the tunneling association. At Step 104, a trusted-third-party network device is informed of the request on a public network. A public network address for a second network device is associated with the unique identifier on the trusted-third-party network device at Step 106. The second network device is associated with the terminating end of the tunneling association. At Step 108, a first private network address on the first network device and a second private network address on the second network device are negotiated through the public network. The first private network address is assigned to the originating end of the tunneling association and the second private network address is assigned to the terminating end of the tunneling association. Method 100 may result in the establishment of a virtual tunneling association between the originating end and the terminating end of the tunneling association without revealing the identities of both ends of the tunneling association on the public network.
At Step 102 of Method 100, the first network device receives a request to initiate the tunneling connection. In one embodiment of the present invention, the request is received in a higher layer of a protocol stack for the first network device. For example, with reference to FIG. 2, the request may be received in the transport layer or the application layer of the protocol stack 50. In another exemplary preferred embodiment, the higher layer of the protocol stack that receives the request is the application layer. As discussed below, the application layer may have an interface to the originating end of the tunneling association and the request takes the form of an event on the interface. Alternatively, the request may take the form of a datagram that is passed up from the transport layer. In yet another exemplary preferred embodiment, the request includes an indicator that the request datagram is associated with this higher layer. For example, the indicator may be a distinctive sequence of bits at the beginning of a datagram that has been passed up from the network and transport layers. By methods known to those skilled in the art, the distinctive sequence of bits indicates to the tunneling application that it should examine the request message for its content and not ignore the datagram. However, the higher layer may be other than the transport or application layers, the protocol stack may be other than the OSI model of FIG. 2, and it should be understood that the present invention is not limited to these embodiments.
At Step 104 of Method 100, the trusted-third-party network device is informed of the request. In one exemplary preferred embodiment, the trusted-third-party network device is informed in a higher layer of a protocol stack for the trusted-third-party network device. For example, with reference to FIG. 2, the information may be received in the transport layer of the protocol stack 50 of the trusted-third-party network device. In another exemplary preferred embodiment, the higher layer of the protocol stack that receives the information is the application layer. An informing message may take the form of a datagram that is passed up from the transport layer. In yet another exemplary preferred embodiment, the informing message includes an indicator that the information datagram is associated with this higher layer. For example, the indicator may be a distinctive sequence of bits at the beginning of a datagram that has been passed up from the data-link, network, and transport layers. By methods known to those skilled in the art, the distinctive sequence of bits indicates to the tunneling application that it should examine the informing message for its content and not ignore the datagram. However, the higher layer may be other than the transport or application layers, the protocol stack may be other than the OSI model of FIG. 2, and it should be understood that the present invention is not limited to these embodiments.
At Step 106 of Method 100, a public network address for a second network device is associated with the unique identifier. In yet another exemplary preferred embodiment of the present invention, the public network address is associated with a lower layer of a protocol stack for the second network device. For example, with reference to FIG. 2, the public network address may be associated with the network or data-link of the protocol stack 50. In yet another exemplary preferred embodiment of the present invention, the lower layer is an IP 58 layer and the public network address is a globally addressable public IP 58 address. The second network device is accessible on the public network 12 by transmitting an IP 58 packet with the public IP 58 address for the second network device in the destination address field 90 (FIG. 3). Alternatively, the lower layer is a data-link layer such as a MAC 54 layer and the public network address is a MAC 54 address. However it should be understood that the lower layer of the protocol stack for the second network device may be other than the IP 58 or MAC 54 layer and that the present invention is not limited to these embodiments.
At Step 108 of Method 100, a first private network address and a second private network address are negotiated on the first network device and the second network device. In one exemplary preferred embodiment, the negotiation is carried out through the trusted-third-party network device, although it should be understood that the negotiation may occur without the involvement of the trusted-third-party network device and that the present invention is not limited by negotiation through the trusted-third-party network device. In general, the negotiation is carried out on a lower layer of a protocol stack for the network devices (14, 16, 30) that is associated with the public network. In another exemplary preferred embodiment of the present invention, these private network addresses are associated with higher layers of the protocol stacks for their respective network devices. For example, with reference to FIG. 2, the private network addresses may be associated with the transport layers or the application layers of the protocol stacks 50. In yet another exemplary preferred embodiment, the higher layers of the protocol stacks are application layers and the lower layers of the protocol stacks are IP 58 layers. A tunneling application in the application layer recognizes the private network addresses as being associated with the ends of the tunneling association. The private network addresses may be included as the payload in data packets and are passed up to the application layer from the transport layer. In yet another exemplary preferred embodiment of the present invention the private network addresses take the form of private Internet Protocol addresses. Many other formats for the private network addresses are possible but the choice of private Internet Protocol addresses may provide the advantage that the format and the application code are already familiar to those skilled in the art. However, the higher layers may be other than the transport or application layers, the protocol stacks may be other than the OSI model of FIG. 2, and it should be understood that the present invention is not limited to these embodiments.
Exemplary Initiation of a VoIP Association
FIG. 5 is a flow diagram illustrating a Method 110 for initiating a VoIP association between an originating telephony device 24 and a terminating telephony device 26. VoIP is described in ITU standard H.323. As is known in the art, H.323 is a protocol used for multimedia communications including voice. Method 110 includes receiving a request to initiate the VoIP association on a first network device 14 at Step 112. The first network device 14 is associated with the originating telephony device 24, and the request includes a unique identifier for the terminating telephony device 26. In one exemplary preferred embodiment of the present invention, the first network device 14 is any of a CM or a CMTS in a data-over-cable network. The CM or CMTS is assigned a globally addressable public IP 58 address which appears in an IP 58 packet header field 82 sent to/from the CM or CMTS. If the CM or CMTS transmits an IP 58 packet to another network device on the public network 12 (e.g. the Internet) the public IP 58 address will appear in the header field 82 in the source address field 88. Similarly, if the CM or CMTS receives an IP 58 packet from the public network 12, the public IP 58 address appears as the destination address field 90 in the header field 82 of the IP 58 packet. In another exemplary preferred embodiment, the first network device 14 is a set-top box adapted to connect to the originating telephony device 24.
The request to initiate the VoIP association is received on the first network device 14. For example, if the originating telephony device 24 is a phone that is physically connected to the first network device 14 the request may include an electrical signal measured by an interface to an application on the first network device 14 as a result of the phone going “off-hook”. The electrical signal may be the presence of a certain voltage level or the presence of a certain current flow through a loop by methods known to those skilled in the telephony arts. Alternatively, if the originating telephony device 24 is a data network device on a local area network or private network 20 which includes the first network device 14, the request may include an IP 58, ICMP 56, or MAC 54 message that indicates the initiation of a VoIP association.
Moreover, the request includes a unique identifier for the terminating telephony device 26. In another exemplary preferred embodiment of the present invention, the unique identifier is any of a dial-up number, an electronic mail address, or a domain name. For example, if the originating telephony device 24 is a phone that is physically connected to the first network device 14, a user may simply be required to lift a telephone handset from its cradle and dial a conventional E.164 dial-up telephone number. E.164 is an ITU recommendation for the assignment of telephone numbers on a worldwide basis. In this case, the request may be an “off-hook” electrical signal followed by a series of Dual Tone Multi-Frequency (“DTMF”) tones that represent a dial-up number for the terminating telephony device 26 on an application interface for the first network device. Alternatively, the dial-up number may be included as a string of characters in the payload of a data packet sent from the originating telephony device 24 to the first network device 14. Other possibilities are that the unique identifier is an electronic mail address or a domain name and may be used to initiate the VoIP association. For example, the user of the terminating telephony device 26 may have moved from one office to another office while still retaining the same electronic mail address. Rather than identifying the terminating user by the number assigned to a physical device in the office, it may be more appropriate to identify the user by the static electronic mail address. Similarly, a company may move premises while still retaining the same domain name and it may be more appropriate to identify the user by the static domain name. There are many other possibilities for the unique identifier, e.g. employee number, social security number, driver's license number, or even a previously assigned public IP 58 address. The electronic mail address, domain name, or other possible unique identifier may be included in the payload of an IP 58 or MAC 54 packet. It should be understood that many other choices of the request and unique identifier are possible and that the above-mentioned forms of the request and unique identifier do not limit the present invention.
At Step 114, a trusted-third-party network device 30 is informed of the request on the public network 12. The informing step may include one or multiple transfer of IP 58 packets across the public network 12. The public network 12 may include the Internet. For each transfer of a packet from the first network device 14 to the trusted-third-party network device 30, the first network device 14 constructs an IP 58 packet. The header 82 of the IP 58 packet includes the public network 12 address of the trusted-third-party network device 30 in the destination address field 90 and the public network 12 address of the first network device 14 in the source address field 88. At least one of the IP 58 packets includes the unique identifier for the terminating telephony device 26 that had been included in the request message. The IP 58 packets may require encryption or authentication to ensure that the unique identifier cannot be read on the public network 12.
A public IP 58 address for a second network device 16 is associated with the unique identifier for the terminating telephony device 26 at Step 116. The second network device 16 is associated with the terminating telephony device 26. This association of the public IP 58 address for the second network device 16 with the unique identifier is made on the trusted-third-party network device 30. In one exemplary preferred embodiment, the trusted-third-party network device 30 is a back-end service, a domain name server, or the owner/manager of database or directory services and may be distributed over several physical locations. In another exemplary preferred embodiment, the second network device 16 is any of a CM or CMTS in a data-over-cable network. The CM or CMTS is assigned a globally addressable public IP 58 address which appears in an IP 58 packet header field 82 sent to/from the CM or CMTS. In yet another exemplary preferred embodiment, the second network device 16 is a set-top box adapted to connect to the terminating telephony device 26.
For example, the trusted-third-party network device 30 may be a directory service, owned and operated by a telephone company, that retains a list of E.164 numbers of its subscribers. Associated with a E.164 number in the directory database is the IP 58 address of a particular second network device 16. The database entry may also include a public IP 58 addresses for the terminating telephony device 26. Many data structures that are known to those skilled in the art are possible for the association of the unique identifiers and IP 58 addresses for the second network devices 16. However, it should be understood that the present invention is not restricted to E.164 telephone numbers and directory services and many more unique identifiers and trusted-third-party network devices are possible.
At Step 118, a first private IP 58 address on the first network device 14 and a second private IP 58 address on the second network device are negotiated through the public network 12. Private IP 58 addresses are addresses that are reserved for use in private networks that are isolated from a public network such as the Internet. Private IP 58 addresses are not globally routable. As is known in the art, private IP 58 addresses typically include IP 58 addresses beginning with 10.0.0.0, 172.16.0.0, and 192.168.0.0. These private IP 58 addresses are assigned to the telephony devices (24, 26), viz., the first private IP 58 address is assigned to the originating telephony device 24 and the second private IP 58 address is assigned to the terminating telephony device 26. The assignment of private IP 58 addresses is discussed below. The negotiation ensures that neither the private nor any public IP 58 addresses for the ends of the VoIP association appear in the source 88 or destination 90 address fields of the IP 58 packets that comprise the negotiation. The IP 58 packets of the negotiation step 118 will only have source 88 or destination 90 address fields containing the IP 58 addresses of the first 14, second 16, or trusted-third-party 30 network device. In this manner the identities of the originating 24 and terminating 26 telephony devices are inside the payload fields 84 of the IP 58 packets and may be hidden from hackers on the public network 12. The negotiation may occur through the trusted-third-party network device 30 to further ensure the anonymity of the telephony devices (24, 26).
FIG. 6 is a block diagram illustrating a message flow 130 of the Method 110 illustrated in FIG. 5. Method Steps 112, 114, 116, and 118 of Method 110 (FIG. 5) are illustrated in FIG. 6. It should be understood that the message flow 130 may include more or fewer messages, that the steps of Method 110 and the message flow 130 may occur in a different order, and that the present invention is not restricted to the order of the message flow illustrated in FIG. 6.
Once negotiated, on the first network device 14 is recorded the first private IP 58 address for the originating telephony device 24, and on the second network device 16 is recorded the second private IP 58 address for the terminating telephony device 26. These IP 58 addresses may be stored in network address tables on the respective network devices, and may be associated with physical or local network addresses for the respective ends of the VoIP association by methods known to those skilled in the art.
Exemplary Negotiation of Private Network Addresses
The negotiating Step 108 of Method 100 (FIG. 4) distributes the first and second private network addresses to the first 14 and second 16 network devices. FIG. 7 is a flow diagram illustrating a Method 140 for negotiating private network addresses at Step 108 of FIG. 4. With reference to FIG. 7, the Method 140 includes selecting the first private network address from a first pool of private addresses on the first network device at Step 142. At Step 144, the first private network address is communicated from the first network device to the second network device through the public network. The second private network address is selected from a second pool of private addresses on the second network device at Step 146. The second private network address is a different address than the first private network address. At Step 148, the second private network address is communicated from the second network device to the first network device through the public network.
In one exemplary preferred embodiment of the present invention, the private network addresses are private IP 58 addresses and the communication between the first, second, and trusted-third-party network devices are IP 58 messages. FIG. 8 is a flow diagram illustrating a Method 150 for negotiating private IP 58 addresses. FIG. 9 is a block diagram illustrating a message flow 160 of the Method 150 illustrated in FIG. 8. Method Steps 152, 154, 156, and 158 of Method 150 (FIG. 8) are illustrated in FIG. 9. With reference to FIG. 8, the Method 150 includes selecting the first private IP 58 address from a first pool of private IP 58 addresses on the first network device 14 at Step 152. Once selected, the first private IP 58 address is removed from the first pool so that it cannot be selected for other tunneling associations through the first 14 or second 16 network device. The first pool includes private IP 58 addresses that have not been assigned to originating or terminating ends of tunneling associations through the first network device 14. The selected first private IP 58 address is assigned to the originating end of the tunneling association 24 on the first network device 14. The assignment of the private IP 58 addresses on the first 14 and second 16 network devices is discussed below.
At Step 154, the first private IP 58 address is communicated from the first network device 14 to the second network device 16 through the trusted-third-party network device 30 on the public network 12. With reference to FIG. 9, the first network device 14 constructs a first IP 58 packet 162 including the public IP 58 address of the first network device 14 in the source address field 88 and the public IP 58 address of the trusted-third-party network device 30 in the destination address field 90. Included in the payload field 84 of the first IP 58 packet 162 is the first private IP 58 address. Also included in the payload field 84 of the first IP 58 packet 162 is an identifier for the tunneling association, e.g. the unique identifier from the requesting Step 102 or the informing Step 104 of Method 100 (FIG. 4). The first IP 58 packet 162 is sent to the trusted-third-party network device 30 on the public network 12. The trusted-third-party network device 30 receives the first IP 58 packet 162, examines the payload 84, and determines that it includes the first private IP 58 address that has been assigned to the originating end of the tunneling association 24.
The trusted-third-party network device 30 has already determined that the terminating end of this tunneling association 26 is associated with the second network device 16 during the associating Step 106 of Method 100 (FIG. 4). The trusted-third-party network device 30 constructs a second IP 58 packet 164 with the public IP 58 address of the trusted-third-party network device 30 in the source address field 88 and the public IP 58 address of the second network device 16 in the destination address field 90. Included in the payload field 84 of the second IP 58 packet 164 are the first private IP 58 address and the public IP 58 address of the first network device 14. The second IP 58 packet 164 is sent to the second network device 16 on the public network 12. The second network device 16 receives the second IP 58 packet 164, examines the payload 84, and determines that it includes both the first private IP 58 address that has been assigned to the originating end of the tunneling association 24 and the public IP 58 address of the first network device 14.
The second private IP 58 address is selected from a second pool of private IP 58 addresses on the second network device 16 at Step 146. The second private IP 58 address is selected to be a different address than the first private IP 58 address that was received on the second network device 16 in the second IP 58 packet 164. Once selected, the first and second private IP 58 addresses are removed from the second pool so that they cannot be selected for other tunneling associations through the first 14 or second 16 network device. The second pool includes private IP 58 addresses that have not been assigned to originating or terminating ends of tunneling associations through the second network device 14. The selected second private IP 58 address is assigned to the terminating end of the tunneling association 26 on the second network device 16. The assignment of the private IP 58 addresses is discussed below.
At Step 158, the second private IP 58 address is communicated from the second network device 16 to the first network device 14 through the trusted-third-party network device 30 on the public network 12. The second network device 16 constructs a third IP 58 packet 166 including the public IP 58 address of the second network device 16 in the source address field 88 and the public IP 58 address of the trusted-third-party network device 30 in the destination address field 90. Included in the payload field 84 of the third IP 58 packet 166 is the second private IP 58 address. Also included in the payload field 84 of the third IP 58 packet 166 is an identifier for the tunneling association. For example, the identifier may be the first private IP 58 address, or the unique identifier from the requesting Step 102 or the informing Step 104 of Method 100 (FIG. 4). The third IP 58 packet 166 is sent to the trusted-third-party network device 30 on the public network 12. The trusted-third-party network device 30 receives the third IP 58 packet 166, examines the payload 84, and determines that it includes the second private IP 58 address that has been assigned to the terminating end of the tunneling association 26.
The trusted-third-party network device 30 constructs a fourth IP 58 packet 168 with the public IP 58 address of the trusted-third-party network device 30 in the source address field 88 and the public IP 58 address of the first network device 14 in the destination address field 90. Included in the payload field 84 of the fourth IP 58 packet 168 is the second private IP 58 address and the public IP 58 address of the second network device 16. The fourth IP 58 packet 168 is sent to the first network device 14 on the public network 12. The first network device 14 receives the fourth IP 58 packet 168, examines the payload 84, and determines that it includes both the second private IP 58 address that has been assigned to the terminating end of the tunneling association 26 and the public IP 58 address of the second network device 16.
The first 162, second 164, third 166, and fourth 168 IP 58 packets may also include indicators that the contents of the payload fields 84 are associated with higher layers of the protocol stacks 50 for the first 14, second 16, and trusted-third-party 30 network devices. In one exemplary preferred embodiment, the higher layers of the protocol stacks 50 are application layers. The contents of the payload fields 84 are received and decapsulated in lower layers of the protocol stacks 50, such as the IP 58 layers, passed up to the application layers of the protocol stacks 50, and examined in the application layers. For example, payloads are passed up from lower layers and the indicators direct the higher layers to examine the payloads. Additionally, the contents of the payload fields 84 can be constructed in the higher layers of the protocol stacks 50 which pass them down to the lower layers of the protocol stacks 50 for encapsulation and transmission on lower layers of the protocol stacks 50.
Following Method 160, the first network device 14 has obtained the public IP 58 address of the second network device 16, the first private IP 58 address, and the second private IP 58 address. Additionally, the second network device 16 has obtained the public IP 58 address of the first network device 14, the first private IP 58 address, and the second private IP 58 address. Both first 14 and second 16 network devices have obtained the private IP 58 addresses of the originating end of the tunneling association 24 that requested the initiation of the tunneling association and the terminating end of the tunneling association 26 that was associated with the unique identifier. It should be understood that the message flow 160 may include more or fewer messages and that the steps of Method 150 and the message flow 160 may occur in a different order. The present invention is not restricted to the order of the message flow illustrated in FIG. 9.
FIG. 10 is a flow diagram illustrating another Method 170 for negotiating private network addresses at Step 108 of FIG. 4. With reference to FIG. 10, the Method 170 includes selecting multiple private network addresses from a pool of private addresses on the first network device at Step 172. At Step 174, the multiple private network addresses are communicated from the first network device to the second network device through the trusted-third-party network device on the public network. The first and second private network addresses are selected from the multiple private network addresses on the second network device at Step 176. The second private network address is a different address than the first private network address. At Step 178, the first and second private network addresses are communicated from the second network device to the first network device through the trusted-third-party network device on the public network.
In another exemplary preferred embodiment of the present invention, the private network addresses are private IP 58 addresses and the communication between the first, second, and trusted-third-party network devices are IP 58 messages. FIG. 11 is a flow diagram illustrating a Method 180 for negotiating private IP 58 addresses. FIG. 12 is a block diagram illustrating a message flow 190 of the Method 180 illustrated in FIG. 11. Method Steps 182, 184, 186, and 188 of Method 180 (FIG. 11) are illustrated in FIG. 12. With reference to FIG. 11, the Method 180 includes selecting multiple private IP 58 addresses from a pool of private IP 58 addresses on the first network device 14 at Step 182. The pool includes private IP 58 addresses that have not been assigned to originating or terminating ends of tunneling associations through the first network device 14.
At Step 184, the multiple private IP 58 addresses are communicated from the first network device 14 to the second network device 16 through the trusted-third-party network device 30 on the public network 12. With reference to FIG. 12, the first network device 14 constructs a first IP 58 packet 192 including the public IP 58 address of the first network device 14 in the source address field 88 and the public IP 58 address of the trusted-third-party network device 30 in the destination address field 90. Included in the payload field 84 of the first IP 58 packet 192 are the multiple private IP 58 addresses. Also included in the payload field 84 of the first IP 58 packet 192 is an identifier for the tunneling association, e.g. the unique identifier from the requesting Step 102 or the informing Step 104 of Method 100 (FIG. 4). The first IP 58 packet 192 is sent to the trusted-third-party network device 30 on the public network 12. The trusted-third-party network device 30 receives the first IP 58 packet 192, examines the payload 84, and determines that it includes the multiple private IP 58 addresses.
The trusted-third-party network device 30 has already determined that the terminating end of this tunneling association 26 is associated with the second network device 16 during the associating Step 106 of Method 100 (FIG. 4). The trusted-third-party network device 30 constructs a second IP 58 packet 194 with the public IP 58 address of the trusted-third-party network device 30 in the source address field 88 and the public IP 58 address of the second network device 16 in the destination address field 90. Included in the payload field 84 of the second IP 58 packet 194 are the multiple private IP 58 addresses and the public IP 58 address of the first network device 14. The second IP 58 packet 194 is sent to the second network device 16 on the public network 12. The second network device 16 receives the second IP 58 packet 194, examines the payload 84, and determines that it includes both the multiple private IP 58 addresses and the public IP 58 address of the first network device 14.
The first and second private IP 58 addresses are selected from the multiple private IP 58 addresses on the second network device 16 at Step 186. The second private IP 58 address is selected to be a different address than the first private IP 58 address. Once selected, the first and second private IP 58 addresses are removed from any private address pool on the second network device 16 so that they cannot be selected for other tunneling associations through the first 14 or second 16 network device. The pool on the second network device 16 may include private IP 58 addresses that have not been assigned to originating or terminating ends of tunneling associations through the second network device 14. The selected second private IP 58 address is assigned to the terminating end of the tunneling association 26 on the second network device 16. The assignment of the private IP 58 addresses is discussed below.
At Step 188, the first and second private IP 58 addresses are communicated from the second network device 16 to the first network device 14 through the trusted-third-party network device 30 on the public network 12. The second network device 16 constructs a third IP 58 packet 196 including the public IP 58 address of the second network device 16 in the source address field 88 and the public IP 58 address of the trusted-third-party network device 30 in the destination address field 90. Included in the payload field 84 of the third IP 58 packet 196 are the first and second private IP 58 addresses. Also included in the payload field 84 of the third IP 58 packet 196 is an identifier for the tunneling association, e.g. the unique identifier from the requesting Step 102 or the informing Step 104 of Method 100 (FIG. 4). The third IP 58 packet 196 is sent to the trusted-third-party network device 30 on the public network 12. The trusted-third-party network device 30 receives the third IP 58 packet 196, examines the payload 84, and determines that it includes the first and second private IP 58 addresses, the second of which has been assigned to the terminating end of the tunneling association 26.
The trusted-third-party network device 30 constructs a fourth IP 58 packet 198 with the public IP 58 address of the trusted-third-party network device 30 in the source address field 88 and the public IP 58 address of the first network device 14 in the destination address field 90. Included in the payload field 84 of the fourth IP 58 packet 198 are the first and second private IP 58 addresses and the public IP 58 address of the second network device 16. The fourth IP 58 packet 198 is sent to the first network device 14 on the public network 12. The first network device 14 receives the fourth IP 58 packet 198, examines the payload 84, and determines that it includes the first and second private IP 58 addresses and the public IP 58 address of the second network device 16. The first and second private IP 58 addresses are removed from the pool of private IP addresses on the first network device 14 so that they cannot be selected for other tunneling associations through the first 14 or second 16 network device. The private IP address pool on the first network device 14 includes private IP 58 addresses that have not been assigned to originating or terminating ends of tunneling associations through the first 14 or second 16 network devices. The first private IP 58 address is assigned to the originating end of the tunneling association 24 on the first network device 14. The assignment of the private IP 58 addresses is discussed below.
The first 192, second 194, third 196, and fourth 198 IP 58 packets may also include indicators that the contents of the payload fields 84 are associated with higher layers of the protocol stacks 50 for the first 14, second 16, and trusted-third-party 30 network devices. In one exemplary preferred embodiment, the higher layers of the protocol stacks 50 are application layers. The contents of the payload fields 84 are received and decapsulated in lower layers of the protocol stacks 50, such as the IP 58 layers, passed up to the application layers of the protocol stacks 50, and examined in the application layers. For example, payloads are passed up from lower layers and the indicators direct the higher layers to examine the payloads. Additionally, the contents of the payload fields 84 can be constructed in the higher layers of the protocol stacks 50 which pass them down to the lower layers of the protocol stacks 50 for encapsulation and transmission on lower layers of the protocol stacks 50.
Following Method 190, the first network device 14 has obtained the public IP 58 address of the second network device 16, the first private IP 58 address, and the second private IP 58 address. Additionally, the second network device 16 has obtained the public IP 58 address of the first network device 14, the first private IP 58 address, and the second private IP 58 address. Both first 14 and second 16 network devices have obtained the private IP 58 addresses of the originating end of the tunneling association 24 that requested the initiation of the tunneling association and the terminating end of the tunneling association 26 that was associated with the unique identifier. It should be understood that the message flow 190 may include more or fewer messages and that the steps of Method 180 and the message flow 190 may occur in a different order. The present invention is not restricted to the order of the message flow illustrated in FIG. 12.
Referring back to FIG. 7, the Method 140 for negotiating private network addresses selected the first and second private network addresses respectively on the first 14 and second 16 network devices. In yet another exemplary preferred embodiment of the present invention, the private network addresses are private IP 58 addresses and the communication between the first, second, and trusted-third-party network devices are IP 58 messages. FIG. 13 is a flow diagram illustrating another Method 210 of negotiating private IP addresses. FIG. 14 is a block diagram illustrating a message flow 230 of the Method 210 illustrated in FIG. 13. Method Steps 212, 214, 216, 218, and 220 of Method 210 (FIG. 13) are illustrated in FIG. 14. With reference to FIG. 13, the Method 210 includes communicating the public IP 58 address for the second network device 16 to the first network device 14 at Step 212. The trusted-third-party network device 30 has already determined that the terminating end of this tunneling association 26 is associated with the second network device 16 during the associating Step 106 of Method 100 (FIG. 4).
With reference to FIG. 14, the trusted-third-party network device 30 constructs a first IP 58 packet 232 with the public IP 58 address of the trusted-third-party network device 30 in the source address field 88 and the public IP 58 address of the first network device 14 in the destination address field 90. Included in the payload field 84 of the first IP 58 packet 232 is the public IP 58 address of the second network device 16 which the trusted-third-party network device 30 has associated with the unique identifier for the terminating end of the tunneling association. Also included in the payload field 84 of the first IP 58 packet 232 is an identifier for the tunneling association, e.g. the unique identifier from the requesting Step 102 or the informing Step 104 of Method 100 (FIG. 4). The first IP 58 packet 232 is sent to the first network device 14 on the public network 12. The first network device 14 receives the first IP 58 packet 232, examines the payload 84, and determines that it includes the public IP 58 address of the second network device 16 that is associated with the unique identifier it had sent in the informing Step 104 of Method 100 (FIG. 4). The first IP 58 packet 232 may require encryption or authentication to ensure that the public IP 58 address of the second network device 16 cannot be read on the public network 12.
The first private IP 58 address is selected from a first pool of private IP 58 addresses on the first network device 14 at Step 214. Once selected, the first private IP 58 address is removed from the first pool so that it cannot be selected for other tunneling associations through the first 14 or second 16 network device. The first pool includes private IP 58 addresses that have not been assigned to originating or terminating ends of tunneling associations through the first network device 14. The selected first private IP 58 address is assigned to the originating end of the tunneling association 24 on the first network device 14. The assignment of the private IP 58 addresses on the first 14 and second 16 network devices is discussed below.
At Step 216, the first private IP 58 address is communicated from the first network device 14 to the second network device 16 through the public network 12. With reference to FIG. 14, the first network device 14 constructs a second IP 58 packet 234 including the public IP 58 address of the first network device 14 in the source address field 88 and the public IP 58 address of the second network device 16 in the destination address field 90. Included in the payload field 84 of the second IP 58 packet 234 is the first private IP 58 address. The second IP 58 packet 234 is sent to the second network device 16 on the public network 12. The second network device 16 receives the second IP 58 packet 234, examines the payload 84, and determines that it includes the first private IP 58 address that has been assigned to the originating end of the tunneling association 24.
The second private IP 58 address is selected from a second pool of private IP 58 addresses on the second network device 16 at Step 218. The second private IP 58 address is selected to be a different address than the first private IP 58 address that was received on the second network device 16 in the second IP 58 packet 234. Once selected, the first and second private IP 58 addresses are removed from the second pool so that they cannot be selected for other tunneling associations through the first 14 or second 16 network device. The second pool includes private IP 58 addresses that have not been assigned to originating or terminating ends of tunneling associations through the second network device 14. The selected second private IP 58 address is assigned to the terminating end of the tunneling association 26 on the second network device 16. The assignment of the private IP 58 addresses is discussed below.
At Step 220, the second private IP 58 address is communicated from the second network device 16 to the first network device 14 through the public network 12. The second network device 16 constructs a third IP 58 packet 236 including the public IP 58 address of the second network device 16 in the source address field 88 and the public IP 58 address of the first network device 14 in the destination address field 90. Included in the payload field 84 of the third IP 58 packet 236 is the second private IP 58 address. Also included in the payload field 84 of the third IP 58 packet 236 is an identifier for the tunneling association. For example, the identifier may be the first private IP 58 address, or the unique identifier from the requesting Step 102 or the informing Step 104 of Method 100 (FIG. 4). The third IP 58 packet 236 is sent to the first network device 14 on the public network 12. The first network device 14 receives the third IP 58 packet 236, examines the payload 84, and determines that it includes the second private IP 58 address that has been assigned to the terminating end of the tunneling association 26.
The first 232, second 234, and third 236, IP 58 packets may also include indicators that the contents of the payload fields 84 are associated with higher layers of the protocol stacks 50 for the first 14, second 16, and trusted-third-party 30 network devices. In one exemplary preferred embodiment, the higher layers of the protocol stacks 50 are application layers. The contents of the payload fields 84 are received and decapsulated in lower layers of the protocol stacks 50, such as the IP 58 layers, passed up to the application layers of the protocol stacks 50, and examined in the application layers. For example, payloads are passed up from lower layers and the indicators direct the higher layers to examine the payloads. Additionally, the contents of the payload fields 84 can be constructed in the higher layers of the protocol stacks 50 which pass them down to the lower layers of the protocol stacks 50 for encapsulation and transmission on lower layers of the protocol stacks 50.
Following Method 210, the first network device 14 has obtained the public IP 58 address of the second network device 16, the first private IP 58 address, and the second private IP 58 address. Additionally, the second network device 16 has obtained the public IP 58 address of the first network device 14, the first private IP 58 address, and the second private IP 58 address. Both first 14 and second 16 network devices have obtained the private IP 58 addresses of the originating end of the tunneling association 24 that requested the initiation of the tunneling association and the terminating end of the tunneling association 26 that was associated with the unique identifier. It should be understood that the message flow 210 may include more or fewer messages and that the steps of Method 210 and the message flow 230 may occur in a different order. The present invention is not restricted to the order of the message flow illustrated in FIG. 14.
Referring back to FIG. 10, the Method 170 for negotiating private network addresses selected the first and second private network addresses from multiple private addresses on the second network device 16. The multiple private addresses were selected from a pool on the first network device 14. In yet another exemplary preferred embodiment of the present invention, the private network addresses are private IP 58 addresses and the communication between the first, second, and trusted-third-party network devices are IP 58 messages. FIG. 15 is a flow diagram illustrating another Method 250 of negotiating private IP addresses. FIG. 16 is a block diagram illustrating a message flow 270 of the Method 250 illustrated in FIG. 15. Method Steps 252, 254, 256, 258, and 260 of Method 250 (FIG. 15) are illustrated in FIG. 16. With reference to FIG. 15, the Method 250 includes communicating the public IP 58 address for the second network device 16 to the first network device 14 at Step 252. The trusted-third-party network device 30 has already determined that the terminating end of this tunneling association 26 is associated with the second network device 16 during the associating Step 106 of Method 100 (FIG. 4).
With reference to FIG. 16, the trusted-third-party network device 30 constructs a first IP 58 packet 272 with the public IP 58 address of the trusted-third-party network device 30 in the source address field 88 and the public IP 58 address of the first network device 14 in the destination address field 90. Included in the payload field 84 of the first IP 58 packet 272 is the public IP 58 address of the second network device 16 which the trusted-third-party network device 30 has associated with the unique identifier for the terminating end of the tunneling association. Also included in the payload field 84 of the first IP 58 packet 272 is an identifier for the tunneling association, e.g. the unique identifier from the requesting Step 102 or the informing Step 104 of Method 100 (FIG. 4). The first IP 58 packet 272 is sent to the first network device 14 on the public network 12. The first network device 14 receives the first IP 58 packet 272, examines the payload 84, and determines that it includes the public IP 58 address of the second network device 16 that is associated with the unique identifier it had sent in the request to initiate the tunneling association. The first IP 58 packet 272 may require encryption or authentication to ensure that the public IP 58 address of the second network device 16 cannot be read on the public network 12.
Multiple private IP 58 addresses are selected from a pool of private IP 58 addresses on the first network device 14 at Step 254. The pool includes private IP 58 addresses that have not been assigned to originating or terminating ends of tunneling associations through the first network device 14.
At Step 256, the multiple private IP 58 addresses are communicated from the first network device 14 to the second network device 16 through the public network 12. With reference to FIG. 16, the first network device 14 constructs a second IP 58 packet 274 including the public IP 58 address of the first network device 14 in the source address field 88 and the public IP 58 address of the second network device 16 in the destination address field 90. Included in the payload field 84 of the second IP 58 packet 274 are the multiple private IP 58 addresses. The second IP 58 packet 274 is sent to the second network device 16 on the public network 12. The second network device 16 receives the second IP 58 packet 274, examines the payload 84, and determines that it includes the multiple private IP 58 addresses.
The first and second private IP 58 addresses are selected from the multiple private IP 58 addresses on the second network device 16 at Step 258. The second private IP 58 address is selected to be a different address than the first private IP 58 address. Once selected, the first and second private IP 58 addresses are removed from any private address pool on the second network device 16 so that they cannot be selected for other tunneling associations through the first 14 or second 16 network device. The pool on the second network device 16 may include private IP 58 addresses that have not been assigned to originating or terminating ends of tunneling associations through the second network device 14. The selected second private IP 58 address is assigned to the terminating end of the tunneling association 26 on the second network device 16. The assignment of the private IP 58 addresses is discussed below.
At Step 260, the first and second private IP 58 addresses are communicated from the second network device 16 to the first network device 14 through the public network 12. The second network device 16 constructs a third IP 58 packet 276 including the public IP 58 address of the second network device 16 in the source address field 88 and the public IP 58 address of the first network device 14 in the destination address field 90. Included in the payload field 84 of the third IP 58 packet 276 are the first and second private IP 58 addresses. Also included in the payload field 84 of the third IP 58 packet 276 is an identifier for the tunneling association. For example, the identifier may be the first or second private IP 58 address, or the unique identifier from the requesting Step 102 or the informing Step 104 of Method 100 (FIG. 4). The third IP 58 packet 276 is sent to the first network device 14 on the public network 12. The first network device 14 receives the third IP 58 packet 276, examines the payload 84, and determines that it the first and second private IP 58 addresses, the second of which has been assigned to the terminating end of the tunneling association 26.
The first 272, second 274, and third 276, IP 58 packets may also include indicators that the contents of the payload fields 84 are associated with higher layers of the protocol stacks 50 for the first 14, second 16, and trusted-third-party 30 network devices. In one exemplary preferred embodiment, the higher layers of the protocol stacks 50 are application layers. The contents of the payload fields 84 are received and decapsulated in lower layers of the protocol stacks 50, such as the IP 58 layers, passed up to the application layers of the protocol stacks 50, and examined in the application layers. For example, payloads are passed up from lower layers and the indicators direct the higher layers to examine the payloads. Additionally, the contents of the payload fields 84 can be constructed in the higher layers of the protocol stacks 50 which pass them down to the lower layers of the protocol stacks 50 for encapsulation and transmission on lower layers of the protocol stacks 50.
Following Method 250, the first network device 14 has obtained the public IP 58 address of the second network device 16, the first private IP 58 address, and the second private IP 58 address. Additionally, the second network device 16 has obtained the public IP 58 address of the first network device 14, the first private IP 58 address, and the second private IP 58 address. Both first 14 and second 16 network devices have obtained the private IP 58 addresses of the originating end of the tunneling association 24 that requested the initiation of the tunneling association and the terminating end of the tunneling association 26 that was associated with the unique identifier. It should be understood that the message flow 270 may include more or fewer messages and that the steps of Method 250 and the message flow 270 may occur in a different order. The present invention is not restricted to the order of the message flow illustrated in FIG. 16.
Exemplary Network Address Tables in the Application Layers
Following the above methods, the first network device 14 has the following network addresses: the public network address of the second network device 16, and the private network addresses assigned to the originating 24 and terminating 26 ends of the tunneling association. Similarly, the second network device 16 has the following network addresses: the public network address of the first network device 14, and the private network addresses assigned to the originating 24 and terminating 26 ends of the tunneling association.
The assignment of private network addresses to the ends of the tunneling association may also include transmitting the private network addresses to the network devices at the ends of the tunneling association where the private network addresses are stored on these end devices. For example, the originating network device 24 may store the private network addresses for the originating and terminating ends of the tunneling association on the originating network device 24. In this manner, any packet sent from the originating network device 24 to the first network device 14 may include the private network addresses of the originating and terminating ends of the tunneling association. Similarly, any packet sent from the terminating network device 26 to the second network device 16 may include the private network addresses of the originating and terminating ends of the tunneling association.
The network addresses are stored in network address tables respectively associated with the first 14 and second 16 network devices. The assignment of private network addresses to the ends of the tunneling association on the network devices, referred to above, includes the recording of the private network addresses in the network address tables. These network address tables allow for the translation from the private network addresses to the public network addresses. For example, the transmission of a packet from the originating network device 24 to the terminating network device 26, without revealing the identity of either end on the public network 12, requires that the packet is received on the first network device 14. The first network device 14 recognizes that the packet has come from the originating network device 24 and is destined for the terminating network device 26 by determining that the packet includes a private network address for the terminating network device 26. The first network device 14 examines the entry in its network address table that contains the private network address for the terminating network device 26 and determines that this private network address is associated with the public network address for the second network device 16. In this manner, the first network device 14 knows where to route the packet on the public network 12 by translating the private network address for the terminating network device 26 to the public network address for the second network device 16.
Additionally, the network address tables may allow for the translation from the private network addresses to forwarding network addresses. The forwarding network addresses are typically local area network addresses used for the routing of packets from the network devices to the ends of the tunneling association. In one exemplary preferred embodiment of the present invention, the forwarding network addresses are the MAC 54 addresses for the originating 24 and terminating 26 network devices. For example, the second network device 16 receives a packet from the public network 12 and recognizes it, from an indicator included in the packet or otherwise, that the payload should be passed up to a higher layer of the protocol stack 50 for examination. Upon examination, the second network device 16 recognizes that the packet is destined for the terminating end of the tunneling association 26 by determining that the packet includes the private network address for the terminating end 26. The second network device 16 examines the entry in its network address table that contains the private network address for the terminating end 26 and determines that this private network address is associated with the MAC 54 address for the terminating network device 26. In this manner, the second network device 16 knows where to route the packet on the local physical network by translating the private network address for the terminating end 26 to the physical network address for the terminating network device 26.
Examples of network address tables can be made with reference to FIG. 17. FIG. 17 illustrates an exemplary configuration 310 of network devices. In this exemplary configuration, edge devices DEV1 312, DEV2 314, and DEV3 316 are connected to public network 12. End devices END1 320 and END2 322 are connected to edge device DEV1 312. End device END3 324 is connected to edge device DEV2 314. End device END4 326 is connected to edge device DEV3 316. Examples of the public IP 58 addresses for the edge devices are presented in Table 1.
Public IP 58 address
DEV1 312
DEV2 314
135.232.86.143
DEV3 316
102.46.198.222
These public IP 58 addresses are globally routable through the public network 12. The end devices have MAC 54 addresses that are unique to the hardware on each end device. Examples of the MAC 54 addresses of the end devices are presented in Table 2.
MAC 54 address
END1 320
END2 322
END3 324
END4 326
00:c2:7b:6e:11:5b
As an example of a media flow, we suppose that END1 320 has established a tunneling association with END3 324 through edge devices DEV1 312 and DEV2 314, and that END2 322 has established a tunneling association with END4 326 through edge devices DEV1 312 and DEV3 316. Further details on a preferred media flow is described in our co-pending patent application filed concurrently, Ser. No. 09/385,118, “Method for Processing a Media Flow at an End of a Tunneling Association” which is fully incorporated herein by reference. The tunneling associations have been initiated by the Method 100 (FIG. 4) described above. Examples of the private IP 58 addresses that have been assigned to the ends of each tunneling association are presented in Table 3.
Private IP 58 address
10.0.189.23
10.0.189.156
10.0.45.63
10.0.196.104
The entries in the network address tables for each edge device associate the private addresses, the public network addresses, and the forwarding (MAC 54) addresses. For example, the network address table on edge device DEV1 312 is illustrated in Table 4a.
First private IP 58
Second private IP 58
[END1]
[END3]
[DEV2]
[END2]
[END4]
[DEV3]
The first entry in the network address table for DEV1 312 associates the MAC 54 address and the private IP 58 address for END1 320 with the private IP 58 address for END3 324 and the public IP 58 address for DEV2 314 at the other end of the END1/END3 tunneling association. The first private IP 58 address column records the private IP 58 addresses of the end devices that are associated with this edge device. In this case, the end devices are END1 320 and END2 322 that are associated with the edge device DEV1 312. The second private IP 58 address column records the private IP 58 addresses that are assigned to the end devices at the other ends of the tunneling associations.
An outgoing message from END1 320 is associated with the private IP 58 address for END1 320 at the transmitting end of the tunneling association between END1 320 and END3 324. The network address table associates this private IP 58 address with the private IP 58 address for END3 324 at the receiving end of this tunneling association. Moreover, in the same entry, the network address table associates the tunneling association END1/END3 with the public IP 58 address of the edge device DEV2 314 that is associated with END3 324. In this manner packets from END1 320 are routed on the public network 12 to DEV2 314. At the receiving end of this tunneling association, the network address table on DEV2 314 routes the packet to END3 324. For example, the network address table on DEV2 314 is illustrated in Table 4b.
[DEV1]
The entry in the network address table associates the MAC 54 address and the private IP 58 address for END3 324 with the private IP 58 address for END1 320 and the public IP 58 address for DEV1 312 at the other end of the END1/END3 tunneling association. The incoming packet is received on DEV2 314 and passed up to the higher layer, e.g. the application layer, for examination. DEV2 314 recognizes that the private IP 58 address for END3 324 is recorded in its network address table (Table 4b) and is associated with the MAC 54 address for END3 324. In this manner packets received from the public network 12 are routed to END3 324.
Similarly, the network address table on DEV3 316 is illustrated in Table 4c.
The entry in the network address table associates the MAC 54 address and the private IP 58 address for END4 326 with the private IP 58 address for END2 322 and the public IP 58 address for DEV1 312 at the other end of the END2/END4 tunneling association.
An outgoing message from END4 326 is associated with the private IP 58 address for END4 326 at the transmitting end of the tunneling association between END2 322 and END4 326. The network address table (Table 4c) associates this private IP 58 address with the private IP 58 address for END2 322 at the receiving end of this tunneling association. Moreover, in the same entry, the network address table associates the tunneling association END2/END4 with the public IP 58 address of the edge device DEV1 312 that is associated with END2 322. In this manner packets from END4 326 are routed on the public network 12 to DEV1 312. At the receiving end of this tunneling association, the network address table (Table 4a) on DEV1 312 routes the packet to END2 322. The incoming packet is received on DEV1 312 and passed up to the higher layer, e.g. the application layer, for examination. DEV1 312 recognizes that the private IP 58 address for END2 322 is recorded in its network address table (the second entry in Table 4a) and is associated with the MAC 54 address for END2 322. In this manner packets received from the public network 12 are routed to END2 322.
The entries in the network address tables, however, need not be in the particular order depicted in the above illustrations and need not be stored is a tabular form as depicted in Tables 4a-4c. Other orderings of the entries and ways of associating each member of the entries may be possible. Moreover, the network address tables need not be maintained in the application layer of the protocol stack 50 for the network devices.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5159592Oct 29, 1990Oct 27, 1992International Business Machines CorporationNetwork address management for a wired network supporting wireless communication to a plurality of mobile usersUS5227778Apr 5, 1991Jul 13, 1993Digital Equipment CorporationService name to network address translation in communications networkUS5550984Dec 7, 1994Aug 27, 1996Matsushita Electric Corporation Of AmericaSecurity system for preventing unauthorized communications between networks by translating communications received in ip protocol to non-ip protocol to remove address and routing services informationUS5636216Apr 8, 1994Jun 3, 1997Metricom, Inc.Method for translating internet protocol addresses to other distributed network addressing schemesUS5708655Jun 14, 1996Jan 13, 1998Telefonaktiebolaget L M Ericsson PublMethod and apparatus for addressing a wireless communication station with a dynamically-assigned addressUS5793763Nov 3, 1995Aug 11, 1998Cisco Technology, Inc.Security system for network address translation systemsUS5812819Jun 5, 1995Sep 22, 1998Shiva CorporationRemote access apparatus and method which allow dynamic internet protocol (IP) address managementUS5867660May 11, 1995Feb 2, 1999Bay Networks, Inc.Method and apparatus for communicating between a network workstation and an internetUS5872847Jul 30, 1996Feb 16, 1999Itt Industries, Inc.Using trusted associations to establish trust in a computer networkUS6018767 *Feb 24, 1998Jan 25, 20003Com CorporationMethod and system for managing subscription services with a cable modemUS6236652 *Nov 2, 1999May 22, 2001Airbiquity Inc.Geo-spacial Internet protocol addressingUS6253327 *Dec 2, 1998Jun 26, 2001Cisco Technology, Inc.Single step network logon based on point to point protocolUS6377982 *Aug 24, 1998Apr 23, 2002Lucent Technologies Inc.Accounting system in a networkUS6381646 *Nov 3, 1998Apr 30, 2002Cisco Technology, Inc.Multiple network connections from a single PPP link with partial network address translationUS6400722 *Aug 24, 1998Jun 4, 2002Lucent Technologies Inc.Optimum routing system* Cited by examinerNon-Patent CitationsReference1"Internet Engineering Task Force", Interne-Draft, Network Address Translation-Protocol Translation (NAT-PT), Jan. 1999, pp. 1 to 15.2"Internet Engineering Task Force", Internet Draft, A Multihoming solution using NATs, Nov. 1998, pp. 1 to 32.3"Internet Engineering Task Force", Internet Draft, Architectural Implications of NAT, Oct. 1998, pp. 1 to 14.4"Internet Engineering Task Force", Internet Draft, Distributed Network Address Translation, Oct. 1998, pp. 1 to 24.5"Internet Engineering Task Force", Internet Draft, Implications of NATs on the TCP/IP Architecture, Feb. 1999, pp. 1 to 7.6"Internet Engineering Task Force", Internet Draft, IP Relocation Through Twice Network Address Translators (RAT), Feb. 1999, pp. 1 to 20.7"Internet Engineering Task Force", Internet Draft, IP Security, Nov. 1997, pp. 1 to 12.8"Internet Engineering Task Force", Internet Draft, Mobile IP Extension for Private Internets Support, Feb. 1999, pp. 1 to 24.9"Internet Engineering Task Force", Internet Draft, Negotiated AddressReuse (NAR), May 1998, pp. 1 to 22.10"Internet Engineering Task Force", Internet Draft, Network Address Translation Issues with IPsec, Feb. 1998, pp. 1 to 12.11"Internet Engineering Task Force", Internet Draft, Reverse Twice Network Address Translators (RAT), Dec. 1998, pp. 1 to 24.12"Internet Engineering Task Force", Internet-Draft, DNS Extensions to Network Address Translators (DNS_ALG), Oct. 1998, pp. 1 to 27.13"Internet Engineering Task Force", Internet-Draft, IP Host Network Address (and Port) Translation, Nov. 1998, pp. 1 to 14.14"Internet Engineering Task Force", Internet-Draft, IP Network Address Translator (NAT) Terminology and Considerations, Oct. 1998,, pp. 1 to 28.15"Internet Engineering Task Force", Internet-Draft, NAT Bypass for End 2 End "Sensitive' Applications, Jan. 1998, pp. 1 to5.16"Internet Engineering Task Force", Internet-Draft, Security for IP Network Address Translator (NAT) Domains, Nov. 1998, pp. 1 to 11.17"Internet Engineering Task Force", Internet-Draft, The IP Network Address Translator (NAT), Feb. 1998, pp. 1 to 24.18"Internet Engineering Task Force", Internet-Draft, Traditional IP Network Address Translator (Traditional NAT), Oct. 1998, pp. 1 to 17.19"Internet Engineering Task Force", Request for Comments 1241, A Scheme for an Internet Encapsulation Protocol, Jul. 1991, pp. 1 to 17.20"Internet Engineering Task Force", Request for Comments 1631, The IP Network Address Translator (NAT), May 1994, pp. 1 to 10.21"Internet Engineering Task Force", Request for Comments 1701, Generic Routing Encapsulation (GRE), Oct. 1994, pp. 1 to 8.22"Internet Engineering Task Force", Request for Comments 1853, IP in IP Tunneling, Oct. 1995, pp. 1 to 8.23"Internet Engineering Task Force", Request for Comments 2663, IP Network Address Translator (NAT) Terminology and Considerations, Aug. 1999, pp. 1 to 30.24"Internet Engineering Task Force", Request for Comments 791, Internet Protocol, Sep. 1981, pp. 1 to 45.25"ITU-T Recommendation H.255.0", Series H: Audiovisual and Multimedia Systems (Transmission Multiplexing and Synchronization), Telecommunication Standardization Sector of ITU, International Telecommunication Union, Feb. 1998, 157 pages.26"ITU-T Recommendation H.323", Series H: Audiovisual and Multimedia Systems (Systems and Terminal Equipment for audiovisual Services), Telecommunication Standardization Sector of ITU, International Telecommunication Union, Feb. 1998, 125 pages.27"Internet Engineering Task Force", Interne-Draft, Network Address Translation—Protocol Translation (NAT-PT), Jan. 1999, pp. 1 to 15.28"Internet Engineering Task Force", Internet-Draft, NAT Bypass for End 2 End ‘Sensitive’ Applications, Jan. 1998, pp. 1 to5.29 *Lee et al., "The Next Genration of the Internet: Aspects of teh Internet Protocol Version 6", IEEE Network, Jan./Feb. 1988, pp. 28-33.** Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS6651100 *Mar 12, 2002Nov 18, 2003Lexmark International, Inc.Automatic negotiation of an internet protocol address for a network connected deviceUS6718331 *Dec 14, 2000Apr 6, 2004International Business Machines CorporationMethod and apparatus for locating inter-enterprise resources using text-based stringsUS6925487 *Jun 27, 2001Aug 2, 2005Polypix Inc.System and method for exchanging online information over private networkUS6970474 *Jun 21, 2000Nov 29, 2005Koninklijke Philips Electronics N.V.Personalized universal phone serviceUS7058714 *Aug 28, 2001Jun 6, 2006AlcatelSpecial gateway for multimedia networksUS7068647 *Jul 11, 2001Jun 27, 2006Voxpath Networks, Inc.System and method for routing IP packetsUS7103032 *Dec 20, 2000Sep 5, 2006Nec Infrontia CorporationTelephone controller for VoIPUS7133404Aug 10, 2001Nov 7, 2006Ip Dynamics, Inc.Communication using two addresses for an entityUS7136925 *May 22, 2000Nov 14, 2006Nokia CorporationSystem for processing wireless connections using connection handlesUS7143137 *Jun 13, 2002Nov 28, 2006Nvidia CorporationMethod and apparatus for security protocol and address translation integrationUS7206932Feb 14, 2003Apr 17, 2007Crystalvoice CommunicationsFirewall-tolerant voice-over-internet-protocol (VoIP) emulating SSL or HTTP sessions embedding voice data in cookiesUS7260650 *Nov 28, 2001Aug 21, 2007Cisco Technology, Inc.Method and apparatus for tunneling informationUS7269161 *Dec 26, 2000Sep 11, 2007Nec Infrontia CorporationTelephone controller for VoIPUS7305480 *Aug 14, 2001Dec 4, 2007Hitachi, Ltd.Method and system for persistent translation between protocolsUS7337219May 30, 2003Feb 26, 2008Aol Llc, A Delaware Limited Liability CompanyClassifying devices using a local proxy serverUS7353280 *Mar 19, 2001Apr 1, 2008Aol Llc, A Delaware Limited Liability CompanyHome-networkingUS7359973 *Mar 19, 2001Apr 15, 2008Aol Llc, A Delaware Limited Liability CompanyHome-networkingUS7366188Jan 21, 2004Apr 29, 2008Samsung Electronics Co., Ltd.Gateway for supporting communications between network devices of different private networksUS7369537Apr 3, 2003May 6, 2008Global Ip Solutions, Inc.Adaptive Voice-over-Internet-Protocol (VoIP) testing and selecting transport including 3-way proxy, client-to-client, UDP, TCP, SSL, and recipient-connect methodsUS7379465 *Dec 7, 2001May 27, 2008Nortel Networks LimitedTunneling scheme optimized for use in virtual private networksUS7383339Jul 31, 2002Jun 3, 2008Aol Llc, A Delaware Limited Liability CompanyLocal proxy server for establishing device controlsUS7389357 *Jan 20, 2004Jun 17, 2008Cisco Technology, Inc.Arrangement in an IP node for preserving security-based sequences by ordering IP packets according to quality of service requirements prior to encryptionUS7437457Sep 8, 2003Oct 14, 2008Aol Llc, A Delaware Limited Liability CompanyRegulating concurrent logins associated with a single accountUS7437548Sep 23, 2002Oct 14, 2008Nvidia CorporationNetwork level protocol negotiation and operationUS7448081Sep 22, 2006Nov 4, 2008At&T Intellectual Property Ii, L.P.Method and system for securely scanning network trafficUS7454525 *Dec 5, 2002Nov 18, 2008Cisco Technology, Inc.Enabling communication when signaling protocol packets contain embedded addresses subject to translationUS7533259 *Nov 4, 2003May 12, 2009Telecommunication Systems, Inc.Encapsulation of secure encrypted data in a deployable, secure communication system allowing benign, secure commercial transportUS7543332Feb 6, 2007Jun 2, 2009At&T CorporationMethod and system for securely scanning network trafficUS7558873Jul 7, 2009Nvidia CorporationMethod for compressed large sendUS7562386Jul 14, 2009At&T Intellectual Property, Ii, L.P.Multipoint server for providing secure, scaleable connections between a plurality of network devicesUS7568038 *Jul 28, 2009Oracle International CorporationCall centers for providing customer services in a telecommunications networkUS7574738Nov 6, 2002Aug 11, 2009At&T Intellectual Property Ii, L.P.Virtual private network crossovers based on certificatesUS7577835 *Aug 20, 2003Aug 18, 2009Telecommunication Systems, Inc.Deployable secure communication systemUS7596146 *Oct 4, 2004Sep 29, 2009Cisco Technology, Inc.Method for universal transport encapsulation for internet protocol network communicationsUS7620070Nov 17, 2009Nvidia CorporationPacket processing with re-insertion into network interface circuitryUS7626977Dec 19, 2003Dec 1, 2009Telecommunication Systems, Inc.Standard telephone equipment (STE) based deployable secure communication systemUS7660873 *Aug 16, 2004Feb 9, 2010General Electric CompanySystems and methods for communicating messagesUS7668306 *Feb 23, 2010Intel CorporationMethod and apparatus for connecting packet telephony calls between secure and non-secure networksUS7680102 *Jun 11, 2003Mar 16, 2010Flash Networks, Inc.Method and system for connecting manipulation equipment between operator's premises and the internetUS7707407Nov 20, 2003Apr 27, 2010Telecommunication Systems, Inc.Encryption of voice and data in a single data stream in a deployable, secure communication systemUS7760674Jul 20, 2010Hitachi, Ltd.Method of translating protocol at translator, method of providing protocol translation information at translation server, and address translation serverUS7913294Jun 24, 2003Mar 22, 2011Nvidia CorporationNetwork protocol processing for filtering packetsUS7937471 *May 3, 2011Inpro Network Facility, LlcCreating a public identity for an entity on a networkUS7949785Mar 31, 2003May 24, 2011Inpro Network Facility, LlcSecure virtual community network systemUS7957382Oct 13, 2006Jun 7, 2011Cisco Technology, Inc.Method and apparatus for handling embedded addresses in data sent through multiple network address translation (NAT) devicesUS7962644Jun 14, 2011Oracle International CorporationSystems and methods for handling a plurality of communicationsUS8014328Jul 16, 2010Sep 6, 2011Hitachi, Ltd.Method of translating protocol at translator, method of providing protocol translation information at translation server, and address translation serverUS8090843Jan 3, 2012Impro Network Facility, LLCCreating a public identity for an entity on a networkUS8090941Jan 3, 2012Telecommunication Systems, Inc.Deployable secure communication systemUS8107460Jan 31, 2012Voxpath Networks, Inc.System and method for IP telephony pagingUS8136152Apr 18, 2008Mar 13, 2012Worcester Technologies LlcMethod and system for securely scanning network trafficUS8209750Jun 26, 2012Telecommunication Systems, Inc.Encryption of voice and data in a single data stream in a deployable, secure communication systemUS8234358Aug 30, 2002Jul 31, 2012Inpro Network Facility, LlcCommunicating with an entity inside a private network using an existing connection to initiate communicationUS8346942Jan 1, 2013Oracle International CorporationCall centers for providing customer services in a telecommunications networkUS8359028Jun 15, 2010Jan 22, 2013Sprint Spectrum L.P.Mitigating the impact of handoffs through comparison of historical call lengthsUS8363647 *Jan 29, 2013Voxpath Networks, Inc.System and method for configuring an IP telephony deviceUS8391858Jun 15, 2010Mar 5, 2013Sprint Spectrum L.P.Mitigating the impact of handoffs through comparison of non-preferred wireless coverage areasUS8458341Jun 4, 2013Virnetx, Inc.System and method employing an agile network protocol for secure communications using secure domain namesUS8504696Dec 27, 2011Aug 6, 2013Virnetx, Inc.System and method employing an agile network protocol for secure communications using secure domain namesUS8504697Dec 28, 2011Aug 6, 2013Virnetx, Inc.System and method employing an agile network protocol for secure communications using secure domain namesUS8516117Apr 25, 2011Aug 20, 2013Virnetx, Inc.Agile network protocol for secure communications with assured system availabilityUS8516131Dec 23, 2011Aug 20, 2013Virnetx, Inc.System and method employing an agile network protocol for secure communications using secure domain namesUS8520574Aug 3, 2011Aug 27, 2013Hitachi, Ltd.Method of translating protocol at translator, method of providing protocol translation information at translation server, and address translation serverUS8521888Jan 4, 2012Aug 27, 2013Virnetx, Inc.System and method employing an agile network protocol for secure communications using secure domain namesUS8549107May 6, 2011Oct 1, 2013Oracle International CorporationSystems and methods for handling a plurality of communications for different companiesUS8554899May 17, 2012Oct 8, 2013Virnetx, Inc.Agile network protocol for secure communications using secure domain namesUS8560705Jan 3, 2012Oct 15, 2013Virnetx, Inc.System and method employing an agile network protocol for secure communications using secure domain namesUS8565129Sep 1, 2010Oct 22, 2013Sprint Spectrum L.P.Supporting simple IP with address translation in a proxy mobile IP gatewayUS8572247Mar 16, 2011Oct 29, 2013Virnetx, Inc.Agile network protocol for secure communications using secure domain namesUS8582749Dec 21, 2009Nov 12, 2013Intel CorporationMethod and apparatus for connecting packet telephony calls between secure and non-secure networksUS8583466Mar 21, 2006Nov 12, 2013Oracle International CorporationSystem and method for routing workflow items based on workflow templates in a call centerUS8621087 *Dec 8, 2009Dec 31, 2013Electronics And Telecommunications Research InstituteMethod for configuring closed user network using IP tunneling mechanism and closed user network systemUS8627061Aug 24, 2009Jan 7, 2014Apriva, LlcMethod and system for employing a fixed IP address based encryption device in a dynamic IP address based networkUS8649355Sep 1, 2010Feb 11, 2014Sprint Spectrum L.P.Supporting simple IP with address translation in a wireless communication deviceUS8804705 *Dec 28, 2012Aug 12, 2014Voxpath Networks, Inc.System and method for configuring an IP telephony deviceUS8843643Jul 25, 2013Sep 23, 2014Virnetx, Inc.System and method employing an agile network protocol for secure communications using secure domain namesUS8850009Jun 6, 2013Sep 30, 2014Virnetx, Inc.System and method employing an agile network protocol for secure communications using secure domain namesUS8850179Sep 14, 2007Sep 30, 2014Telecommunication Systems, Inc.Encapsulation of secure encrypted data in a deployable, secure communication system allowing benign, secure commercial transportUS8868705Sep 13, 2012Oct 21, 2014Virnetx, Inc.Agile network protocol for secure communications using secure domain namesUS8874771Aug 16, 2007Oct 28, 2014Virnetx, Inc.Agile network protocol for secure communications with assured system availabilityUS8885812Mar 15, 2006Nov 11, 2014Oracle International CorporationDynamic customer satisfaction routingUS8892724Oct 8, 2010Nov 18, 2014Sprint Spectrum L.P.Assigning a type of address based on expected port utilizationUS8904516Jun 6, 2013Dec 2, 2014Virnetx, Inc.System and method employing an agile network protocol for secure communications using secure domain namesUS8943201Oct 31, 2011Jan 27, 2015Virnetx, Inc.Method for establishing encrypted channelUS9027115Sep 10, 2014May 5, 2015Virnetx, Inc.System and method for using a registered name to connect network devices with a link that uses encryptionUS9027116Jul 9, 2012May 5, 2015Virnetx, Inc.Dynamic VPN address allocationUS9037713Apr 6, 2011May 19, 2015Virnetx, Inc.Agile network protocol for secure communications using secure domain namesUS9038163 *Jul 25, 2013May 19, 2015Virnetx, Inc.Systems and methods for connecting network devices over communication networkUS9077694Sep 13, 2012Jul 7, 2015Virnetx, Inc.Agile network protocol for secure communications using secure domain namesUS9077695May 28, 2013Jul 7, 2015Virnetx, Inc.System and method for establishing an encrypted communication link based on IP address lookup requestsUS9094399Jul 12, 2011Jul 28, 2015Virnetx, Inc.Method for establishing secure communication link between computers of virtual private networkUS9100375Sep 14, 2012Aug 4, 2015Virnetx, Inc.System and method employing an agile network protocol for secure communications using secure domain namesUS9131366 *Dec 19, 2008Sep 8, 2015Avaya Inc.Unifying virtualizations in a core network and a wireless access networkUS9185606Oct 12, 2012Nov 10, 2015Sprint Spectrum L.P.Assignment of wireless network resourcesUS9294729Jan 19, 2006Mar 22, 2016At&T Intellectual Property I, L.P.System and method for providing content over a television networkUS20010004361 *Dec 20, 2000Jun 21, 2001Yoshikazu KobayashiTelephone controller for VoIPUS20010005366 *Dec 26, 2000Jun 28, 2001Yoshikazu KobayashiTelephone controller for VoIPUS20010036192 *Mar 19, 2001Nov 1, 2001Chiles David ClydeHome-networkingUS20010044842 *May 16, 2001Nov 22, 2001Nec CorporationCommunication system, communication control method and control program storage mediumUS20020026515 *Aug 28, 2001Feb 28, 2002AlcatelData networkUS20020078000 *Dec 14, 2000Jun 20, 2002Ibm CorporationMethod and apparatus for locating inter-enterprise resources using text-based stringsUS20020111998 *Jun 27, 2001Aug 15, 2002Kim Jae HoonSystem and method for exchanging online information over private networkUS20020112071 *Jun 26, 2001Aug 15, 2002Kim Jae HoonSystem and method for exchanging online information along optimum pathUS20020141352 *Jul 11, 2001Oct 3, 2002Fangman Richard E.System and method for configuring an IP telephony deviceUS20020141389 *Jul 11, 2001Oct 3, 2002Fangman Richard E.System and method for routing IP packetsUS20020154624 *Aug 14, 2001Oct 24, 2002Hitachi. Ltd.Method of translating protecol at translator, method of providing protocol translation information at translation server, and address translation serverUS20030021275 *Mar 7, 2001Jan 30, 2003Mohammed ShabeerMobile data routingUS20030108041 *Dec 7, 2001Jun 12, 2003Nortell Networks LimitedTunneling scheme optimized for use in virtual private netwoksUS20030169859 *Mar 8, 2002Sep 11, 2003Strathmeyer Carl R.Method and apparatus for connecting packet telephony calls between secure and non-secure networksUS20030177238 *Mar 12, 2002Sep 18, 2003Bush James LesesneAutomatic negotiation of an internet protocol address for a network connected deviceUS20030191843 *Apr 4, 2002Oct 9, 2003Joel BalissatSecure network connection for devices on a private networkUS20030233452 *Jun 13, 2002Dec 18, 2003Nvidia Corp.Method and apparatus for security protocol and address translation integrationUS20030233454 *Jun 3, 2002Dec 18, 2003Alkhatib Hasan S.Creating a public identity for an entity on a networkUS20040109446 *Jul 21, 2003Jun 10, 2004Lg Electronics Inc.Calling method and system of flexible IP internet phoneUS20040168049 *Feb 13, 2004Aug 26, 2004In-Zoo LeeMethod for encrypting data of an access virtual private network (VPN)US20040218611 *Jan 21, 2004Nov 4, 2004Samsung Electronics Co., Ltd.Gateway for supporting communications between network devices of different private networksUS20050044358 *Aug 20, 2003Feb 24, 2005Steve AnspachDeployable secure communication systemUS20050058122 *Dec 19, 2003Mar 17, 2005Anspach Steve S.Standard telephone equipment (STE) based deployable secure communication systemUS20050058136 *Oct 4, 2004Mar 17, 2005Lothberg L. Peter J.Method for universal transport encapsulation for internet protocol network communicationsUS20050060539 *Nov 4, 2003Mar 17, 2005Steve AnspachEncapsulation of secure encrypted data in a deployable, secure communication system allowing benign, secure commercial transportUS20050060543 *Nov 20, 2003Mar 17, 2005Steve AnspachEncryption of voice and data in a single data stream in a deployable, secure communication systemUS20050182833 *Jan 20, 2004Aug 18, 2005Duffie John B.IiiArrangement in an IP node for preserving security-based sequences by ordering IP packets according to quality of service requirements prior to encryptionUS20050237955 *Jun 11, 2003Oct 27, 2005Yair ShapiraMethod and system for connecting manipulation equipment between operator's premises and the internetUS20060037069 *Aug 16, 2004Feb 16, 2006Fisher Gerald BSystems and methods for communicating messagesUS20070016947 *Sep 22, 2006Jan 18, 2007Joel BalissatMethod and system for securely scanning network trafficUS20070133521 *Dec 14, 2005Jun 14, 2007Mcmaster John PSystem and method for managing telecommunicationsUS20070169144 *Jan 19, 2006Jul 19, 2007Sbc Knowledge Ventures L.P.System and method for providing content over a television networkUS20070169187 *Feb 6, 2007Jul 19, 2007Joel BalissatMethod and system for securely scanning network trafficUS20070177578 *Jan 11, 2006Aug 2, 2007Anspach Steven SStandard telephone equipment (STE) based deployable secure cellular communication systemUS20070180514 *Feb 6, 2007Aug 2, 2007Joel BalissatMultipoint server for providing secure, scaleable connections between a plurality of network devicesUS20090077375 *Sep 14, 2007Mar 19, 2009Steve AnspachEncapsulation of secure encrypted data in a deployable, secure communication system allowing benign, secure commercial transportUS20090310535 *Dec 19, 2008Dec 17, 2009Nortel Networks LimitedUnifying Virtualizations in a Core Network and a Wireless Access NetworkUS20100202615 *Apr 20, 2010Aug 12, 2010Steve AnspachEncryption of voice and data in a single data stream in a deployable,secure communication systemUS20100293285 *Nov 18, 2010Hitachi, Ltd.Method of translating protocol at translator, method of providing protocol translation information at translation server, and address translation serverUS20110131647 *Jun 2, 2011Scott SandersVirtual Endpoint SolutionUS20110196945 *Aug 11, 2011Inpro Network Facility, LlcCreating a public identity for an entity on a networkUS20110213860 *Sep 1, 2011Ran EzerzerSystems and Methods for Handling a Plurality of Communications For Different CompaniesUS20110270996 *Dec 8, 2009Nov 3, 2011Electronics And Telecommunications Research InstituteMethod for configuring closed user network using ip tunneling mechanism and closed user network systemUS20130114589 *Dec 28, 2012May 9, 2013Voxpath Networks, IncSystem and method for configuring an ip telephony deviceUS20130198412 *Jan 18, 2013Aug 1, 2013Brother Kogyo Kabushiki KaishaCommunication apparatus, methods, and non-transitory computer-readable media for determining ip addresses for use in different networksUS20130311774 *Jul 25, 2013Nov 21, 2013Virnetx, Inc.System and method employing an agile network protocol for secure communications using secure domain namesUSRE41024Nov 7, 2008Dec 1, 2009Hasan AlkhatibCommunication using two addresses for an entityCN100401700CAug 13, 2004Jul 9, 2008中兴通讯股份有限公司Method for multimedia terminal point-to-point call inside two private networksCN100576847CNov 11, 2005Dec 30, 2009杭州华三通信技术有限公司Method for set-up direct link tunnel for user terminal and its communication method and serverEP1441483A2 *Jan 21, 2004Jul 28, 2004Samsung Electronics Co., Ltd.Gateway for supporting communications between network devices of different private networksWO2003102801A1 *May 29, 2003Dec 11, 2003Lexmark International, Inc.Host-based automatic ip address negotiation method* Cited by examinerClassifications U.S. Classification709/245, 709/227, 709/225International ClassificationH04L29/08, H04L29/06, H04L29/12, H04L12/46Cooperative ClassificationH04L63/0428, H04L29/12254, H04L61/2038, H04L12/4633, H04L61/35, H04L63/0272, H04L29/06, H04L29/12783, H04L29/06027, H04L69/24, H04L67/28, H04L67/2809, H04L69/329European ClassificationH04L63/04B, H04L61/35, H04L63/02C, H04L61/20B, H04L29/06, H04L29/08N27B, H04L29/12A3B, H04L12/46E, H04L29/12A6, H04L29/08N27Legal EventsDateCodeEventDescriptionAug 27, 1999ASAssignmentOwner name: 3COM CORPORATION, CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BESER, NURETTIN B.;BORELLA, MICHAEL S.;REEL/FRAME:010211/0445Effective date: 19990826Jun 19, 2006FPAYFee paymentYear of fee payment: 4Jun 17, 2010FPAYFee paymentYear of fee payment: 8Jul 6, 2010ASAssignmentOwner name: HEWLETT-PACKARD COMPANY, CALIFORNIAFree format text: MERGER;ASSIGNOR:3COM CORPORATION;REEL/FRAME:024630/0820Effective date: 20100428Jul 15, 2010ASAssignmentOwner name: HEWLETT-PACKARD COMPANY, CALIFORNIAFree format text: CORRECTIVE ASSIGNMENT TO CORRECT THE SEE ATTACHED;ASSIGNOR:3COM CORPORATION;REEL/FRAME:025039/0844Effective date: 20100428Dec 6, 2011ASAssignmentOwner name: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P., TEXASFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HEWLETT-PACKARD COMPANY;REEL/FRAME:027329/0044Effective date: 20030131May 1, 2012ASAssignmentOwner name: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P., TEXASFree format text: CORRECTIVE ASSIGNMENT PREVIUOSLY RECORDED ON REEL 027329 FRAME 0001 AND 0044;ASSIGNOR:HEWLETT-PACKARD COMPANY;REEL/FRAME:028911/0846Effective date: 20111010May 26, 2014FPAYFee paymentYear of fee payment: 12Nov 9, 2015ASAssignmentOwner name: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP, TEXASFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.;REEL/FRAME:037079/0001Effective date: 20151027RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services