One embodiment of the present invention provides a computer system for processing communications in a virtual private network. The computer system operates in a selective mode, in which only communications transiting the virtual private network are processed according to specified virtual private network parameters, such as encryption, compression and authentication algorithms. virtual private network communications passing between a public network and a private network are thus received and processed according to the algorithms, while other communications bypass the computer system. Multiple private networks may be served by a single computer system.
|
15. An apparatus for facilitating secure communications between members of a virtual private network, comprising:
a first communication port coupled to a first local network and a public network; a first storage area containing a first series of instructions for transforming a communication packet received from the public network; a processor for processing a received communication packet according to said first series of executable instructions; and a set of local addresses not assigned to virtual private network members coupled to said first local network; wherein a first communication packet directed from a remote member of the virtual private network to a first member of the virtual private network in said first local network is received at the apparatus with a remote source address corresponding to the remote member; and wherein the remote source address is replaced with a local address from the set of local addresses before the first communication packet is forwarded to said first local network.
32. A computer readable storage medium storing instructions that, when executed by a computer, cause the computer to perform a method of operating a virtual private network unit to facilitate secure communications between virtual private network members over a public network, the method comprising:
coupling the virtual private network unit to a first local network via a first data channel; coupling the virtual private network unit to a first public network via the first data channel; maintaining a set of addresses in the first local network that are not assigned to members of the virtual private network residing in the first local network; receiving a first data packet over the first data channel from a first member of the virtual private network in the first local network, wherein the first data packet is addressed to a second member of the virtual private network with a first address from the set of addresses; replacing the first address with a remote address corresponding to the second member; forwarding the first data packet over the first data channel to the public network.
26. A method of operating a virtual private network unit in a virtual private network to selectively process communications across a public network between members of the virtual private network, comprising:
operating the virtual private network unit in a selective mode, in which the virtual private network unit only receives communications from members of the virtual private network; receiving a virtual private network communication at the virtual private network unit, wherein the communication comprises a source address corresponding to a remote client and a destination address corresponding to a member of the virtual private network connected to a local network; maintaining a set of local addresses not assigned to virtual private network members connected to the local network; processing the communication to replace the source address with a local address from the set of local addresses; and forwarding the communication to the local network for delivery to the virtual private network member; wherein the virtual private network unit is coupled to the public network and the local network through a single communication port.
1. A method of operating a virtual private network unit to facilitate secure communications between virtual private network members over a public network, comprising:
coupling the virtual private network unit to a first local network via a first data channel; coupling the virtual private network unit to a first public network via the first data channel; maintaining a set of addresses in the first local network that are not assigned to members of the virtual private network residing in the first local network; receiving a first data packet over the first data channel from a first member of the virtual private network in the first local network, wherein the first data packet is addressed to a second member of the virtual private network with a first address from the set of addresses; replacing the first address with a remote address corresponding to the second member; transforming the first data packet in accordance with pre-determined rules for transforming data packets sent between members of the virtual private network; and forwarding the transformed first data packet over the first data channel to the public network for delivery to the remote address.
28. A method of operating a virtual private network unit within a virtual private network to facilitate the exchange of secure communications across a public network, comprising:
coupling the virtual private network unit to a first local network via a first data channel; coupling the virtual private network unit to the public network via the first data channel; maintaining a set of addresses in the first local network that are not assigned to members of the virtual private network residing in the local network; receiving a first communication over the first data channel, the first communication being directed between a local member of the virtual private network within the first local network and a remote member of the virtual private network; if the first communication is directed from the remote member to the local member, in the communication, replacing a remote address corresponding to the remote member with a first address from the set of addresses; if the first communication is directed from the local member to the remote member, in the communication, replacing a first address from the set of addresses with a remote address corresponding to the remote member; and forwarding the communication over the first data channel.
31. A computer readable storage medium storing instructions that, when executed by a computer, cause the computer to perform a method of operating a virtual private network unit in a virtual private network to selectively process communications across a public network between members of the virtual private network, the method comprising:
operating the virtual private network unit in a selective mode, in which the virtual private network unit only receives communications from members of the virtual private network; receiving a virtual private network communication at the virtual private network unit, wherein the communication comprises a source address corresponding to a remote client and a destination address corresponding to a member of the virtual private network connected to a local network; maintaining a set of local addresses not assigned to virtual private network members connected to the local network; processing the communication to replace the source address with a local address from the set of local addresses; and forwarding the communication to the local network for delivery to the virtual private network member; wherein the virtual private network unit is coupled to the public network and the local network through a single communication port.
30. A communication system for facilitating secure communications over a public network between members of a virtual private network, comprising:
a local network comprising a first member of the virtual private network; a virtual private network unit operating in a selective mode, in which the virtual private network unit only receives communications from members of the virtual private network; a pool of addresses in the local network that are not assigned to members of the virtual private network residing in the local network; a first communication link coupling the local network and the public network; and a second communication link coupling the virtual private network unit to the first communication link; wherein a communication directed between the first member of the virtual private network and a second member of the virtual private network is received by the virtual private network unit over the second communication link with a first address from the pool of addresses, modified in accordance with a pre-determined series of rules, and forwarded by the virtual private network unit over the second communication link; and wherein the virtual private network unit replaces the first address from the pool of addresses with a remote address corresponding to the second member.
33. A computer readable storage medium storing instructions that, when executed by a computer, cause the computer to perform a method of operating a virtual private network unit within a virtual private network to facilitate the exchange of secure communications across a public network, the method comprising:
coupling the virtual private network unit to a first local network via a first data channel; coupling the virtual private network unit to the public network via the first data channel; maintaining a set of addresses in the first local network that are not assigned to members of the virtual private network residing in the local network; receiving a first communication over the first data channel, the first communication being directed between a local member of the virtual private network within the first local network and a remote member of the virtual private network; if the first communication is directed from the remote member to the local member, in the communication, replacing a remote address corresponding to the remote member with a first address from the set of addresses; if the first communication is directed from the local member to the remote member, in the communication, replacing a first address from the set of addresses with a remote address corresponding to the remote member; and forwarding the communication over the first data channel.
2. The method of
receiving a secure data packet over the first data channel from the public network; processing the secure data packet in accordance with pre-determined rules for processing secure data packets sent between members of the virtual private network; and forwarding the processed data packet over the first data channel to the first local network.
3. The method of
disassembling the secure data packet; and recovering a second data packet.
4. The method of
5. The method of
6. The method of
7. The method of
8. The method of
coupling a source address to the first data packet, the source address corresponding to the virtual private network unit; and coupling a destination address to the first data packet, the destination address corresponding to a second virtual private network unit.
9. The method of
10. The method of
coupling the virtual private network unit to a second local network via a second data channel; receiving a second data packet from a third member of the virtual private network in the second local network over the second data channel, wherein the second data packet is addressed to a fourth member of the virtual private network; transforming the second data packet in accordance with said pre-determined rules for transforming data packets sent between members of the virtual private network; and transmitting the transformed second data packet toward the fourth member of the virtual private network; wherein the first and second data channels comprise separate and distinct signal conductors.
11. The method of
12. The method of
14. The method of
operating the virtual private network unit in a selective mode, in which the virtual private network unit only receives communications from members of the virtual private network.
16. The apparatus of
a second storage area containing a second series of instructions for transforming a communication packet received from said first local network; wherein a second communication packet received through said first communication port from said first local network is processed in accordance with said second series of instructions and then forwarded through said first communication port toward a member of the virtual private network not in said first local network.
17. The apparatus of
18. The apparatus of
19. The apparatus of
20. The apparatus of
21. The apparatus of
a second communication port coupled to a second local network; wherein a second communication packet received through said second communication port from said second local network is processed in accordance with a second series of instructions.
22. The apparatus of
23. The apparatus of
24. The apparatus of
25. The apparatus of
27. The method of
receiving a response from the local network sent from the virtual private network member, the response being directed to the local address; processing the response to replace the local address with the source address; and forwarding the response to the public network for delivery to the remote client.
29. The method of
operating the virtual private network unit in a selective mode, in which the virtual private network unit only receives communications from members of the virtual private network.
|
|||||||||||||||||||||||||||||||||||||||||||
This application is a continuation-in-part of U.S. Pat. No. 6,226,751 (Ser. No. 09/062,507, filed Apr. 17, 1998) and is related to U.S. Pat. No. 6,079,020 (Ser. No. 09/013,743, filed Jan. 27, 1998).
The present invention relates to the field of data communications. More specifically, the present invention relates to a device for processing communications and a method of configuring such a device to selectively encrypt communications depending upon whether they are being passed between members of a virtual private network.
Organizations rely heavily upon their ability to communicate data electronically between their members, representatives, employees, etc. Such communications typically include electronic mail and some form of file sharing or file transfer. In a centralized, single site organization, these communications are most commonly facilitated by a local area network (LAN) installed and/or operated by the organization.
Preventing unauthorized access to data traversing an enterprise's single site LAN is relatively straightforward. As long as intelligent network management and adequate physical security are maintained, unauthorized access to the data passing across the LAN can be prevented. It is when the enterprise spans multiple sites that external security threats become a considerable problem.
For distributed enterprises wishing to communicate data electronically, several options exist but each has associated disadvantages. One option is to interconnect the various offices or sites with dedicated, or private, communication connections, often referred to as leased lines. This is a traditional method used by organizations to implement a wide area network (WAN). The disadvantages of implementing an enterprise-owned and controlled WAN are obvious: they are expensive, cumbersome and frequently underutilized if configured to handle the peak capacity requirements of the enterprise. The obvious advantage is that the lines are dedicated for use by the enterprise and are therefore reasonably secure from eavesdropping or tampering by other parties.
One alternative to using dedicated communication lines is to exchange data communications over the emerging public network space. For example, in recent years the Internet has evolved from a tool primarily used by scientists and academics into an efficient mechanism for global communications. The Internet provides electronic communication paths between millions of computers by interconnecting the various networks upon which those computers reside. It has become commonplace, even routine, for enterprises (including those in non-technical fields) to provide Internet access to at least some portion of the computers within the enterprises. For many organizations, Internet access facilitates communications with customers and potential business partners and promotes communications between geographically distributed members of the organization as well.
Distributed enterprises have discovered that the Internet is a convenient mechanism for enabling electronic communications between their geographically-separated members. For example, even remote sites within an enterprise can connect to the Internet through Internet Service Providers (ISP). Once they have access to the Internet, the various members of the enterprise can communicate among the enterprise's distributed sites and with other Internet sites as well. A significant disadvantage of using this form of intra-enterprise communications is the general lack of security afforded communications traversing public networks such as the Internet. The route by which a data communication travels from one point on the Internet to another point can vary on a per packet basis, and is therefore essentially indeterminate. Furthermore, the data protocols for transmitting information over the constituent networks of the Internet are widely known, thus leaving electronic communications susceptible to interception and eavesdropping, the danger of which increases as packets are replicated at most intermediate hops. Of potentially greater concern is the fact that communications can be modified in transit or even initiated by or routed to an impostor. With these disconcerting risks, most enterprises are unwilling to subject their proprietary and confidential communications to the exposure of the public network space. For many organizations, therefore, it is common to not only have Internet access available at each site, but also to maintain existing dedicated communications paths for internal enterprise communications, with all of the attendant disadvantages described above.
To address the need for means of passing secure communications, "virtual private networks" (VPNs) have been developed. A VPN allows an organization to communicate securely across an underlying public network, such as the Internet, even with remote sites. Virtual private networks typically include one or more virtual private network units, sometimes known as VPN service units or VSUs. VPN service units translate or exchange data packets between the public network and the organization's private WAN or LAN. Virtual private network units may reside in a number of locations, such as within an ISP or telephone company network or on the WAN or LAN side of a routing apparatus that connects the enterprise's network to the Internet. Thus, VPN units in known forms of virtual private networks generally receive and process all data traffic passed between an enterprise site (whether local or remote) and the public network. Within one enterprise network, a VSU may serve multiple network segments.
To ensure secure data communications between members of a single VPN, which may comprise one or more VPN groups, a VPN unit operates according to a number of parameters. The parameters include various compression, encryption, decryption and authentication algorithms, as well as parameters concerning security associations and access control. Parameters in effect for one VPN may differ from those used in another VPN, and may also vary between different groups within each VPN.
As described above, known VPN units typically form part of the data path connecting an enterprise's private LAN to the public network over which secure data communications are to be passed. This mode of operation presents at least two problems, however. First, because it forms part of the path along which all inter-network traffic travels, such a VPN unit constitutes a single point of failure. In other words, if a VPN unit fails all communications between the private and public networks connected to the unit are disrupted, not just the VPN traffic. As a second consequence of being part of the path for all data communications, those communications that need not be secured are still received and processed by the VPN unit, even though they are not VPN traffic. Therefore, current VPN unit configurations cannot help delaying all data communications, including those that are not being passed between members of a VPN.
An additional disadvantage to the current method of configuring VPNs and VPN units is that a VPN unit cannot be "hot-swapped." In other words, an installed VPN unit cannot be replaced without disrupting all data communications between the private and public networks. Further, each individual VPN unit is presently capable of processing communications for only a single private network that is connected to a public network through the VPN unit. A separate VPN unit is thus generally required for each private network.
There is, therefore, a need in the art for a VPN unit that can be configured to operate as part of a virtual private network without receiving and processing all data communications passing between the interconnected public and private networks. There also exist requirements for a VPN unit that can be replaced without disrupting all data communications and a VPN unit capable of serving multiple private networks. Methods of operating VPN units such as these, and methods of operating a VPN comprising such VPN units are also needed.
The present invention provides a virtual private network (VPN) unit for selectively processing secure communications for members of a virtual private network. One embodiment of the present invention is used in a VPN operating over a public data network connected to an organization's private network (e.g., a LAN or WAN). The organization's private network includes one or more endstations that are members of the VPN. In this first embodiment, a VPN unit serving the VPN member endstations contains a processor, storage memories, and a communication port. A method of configuring the VPN unit is also provided, whereby VPN communications (e.g., communications requiring secure transmission between members of a VPN) are processed by the VPN unit but other communications bypass it.
The VPN unit is linked by a communication port to an interconnection between the public network and the private network. Data communications sent from the private network are received and processed by the VPN unit if they are to be secured for transmission across the VPN (i.e., they constitute VPN traffic). Data communications sent from the private network bypass the VPN unit, however, and pass directly to the public network if they are not VPN traffic. Conversely, communications directed to the private network from the public network are delivered to the VPN unit if they constitute VPN traffic but otherwise pass directly to the private network.
To enable this selective mode of operation in a present embodiment of the invention, the VPN unit is configured to exchange VPN traffic with the public network in tunnel format. VPN data packets adhering to tunnel format comprise a header and a body. The header includes source and destination addresses corresponding to the VPN units serving the origination and destination VPN members, respectively. The body comprises the original data packet generated by the originating VPN member, including the addresses of the origination and destination endstations. The source VPN unit receives the original packet from the originating VPN member, appends the header, and encrypts the body before transmitting the VPN packet toward its destination. The destination VPN unit receives the VPN packet from the public network, removes the header, decrypts the body, and forwards the original packet toward the destination endstation.
A VPN unit operating in this selective mode of operation will not be a single point of failure for all data traffic passing between the organization's private network and the public network, and can be replaced without disrupting non-VPN traffic. Advantageously, non-VPN traffic bypasses the VPN unit, thereby avoiding any delay that may be imparted by the VPN unit. In an alternative embodiment of the invention, multiple private networks are connected to a single VPN unit.
Configuration Parameters--parameters sent to a VPN unit to configure the VPN unit to appropriately handle communications between members of VPNs.
Group of Nodes--a group of nodes on a public network. In one variation, these nodes belong to the same local network. In another variation, these nodes are specified by at least one net/mask pair.
Local Address--an address on the same private network (or local network), wherein the private network is separated logically or physically from a public data network.
Local Network--a private network (or a local network) separated logically or physically from a public data network.
Net/Mask Pair--a specification for a group of network addresses including a network ID and a network address mask.
Network Group--same as group of nodes.
Non-local Address--an address on a different private network (or local network), wherein private networks are separated logically or physically from a public data network.
VPN traffic--communications intended to be transmitted within a virtual private network.
The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein. For example, the present invention is described predominantly in terms of utilizing the Internet as a communications medium. However, the concepts discussed herein are broad enough to accomplish the implementation of secure virtual private networks over other public or relatively unsecure communications media. In addition, although the invention is implemented in the form of a virtual private network unit, the concepts and methods of the invention are readily adaptable to communication devices performing other functions.
Throughout this detailed description, numerous specific details are set forth, such as particular encryption or key management protocols, in order to provide a thorough understanding of the present invention. To one skilled in the art, however, it will be understood that the present invention may be practiced without such specific details. In other instances, well-known control structures and system components have not been shown in detail in order not to obscure the present invention.
The present invention is not limited to any one particular implementation technique. Those of ordinary skill in the art will be able to implement the invention with various technologies without undue experimentation once the functionality to be carried out by such components is described. In many instances, components implemented by the present invention are described at an architectural, functional level. Many of the elements may be configured using well-known structures, particularly those designated as relating to various compression or encryption techniques. Additionally, for logic to be included within the system of the present invention, functionality and flow diagrams are described in such a manner that those of ordinary skill in the art will be able to implement the particular methods without undue experimentation. It should also be understood that the techniques of the present invention may be implemented using a variety of technologies. For example, the VPN unit to be described further herein may be implemented in software running on a computer system, or implemented in hardware utilizing either a combination of microprocessors or other specially designed application specific integrated circuits, programmable logic devices, or various combinations thereof.
Headquarters local area network (LAN) 110, including three endstations 111, 112 and 113, is coupled to public network 100 through router 114. In
Branch LAN 120, which includes endstations 121, 122 and 123, is connected to public network 100 through VPN unit 125 and router 124. LAN 130 is coupled to public network 100 through router 134. LAN 130 comprises VPN unit 135 and a plurality of computers, illustratively 131 and 132. In addition, LANs (which may, alternatively, comprise segments of LAN 130) 170, 180 connect to public network 100 through VPN unit 135 and LAN 130.
Data communications within headquarters LAN 110, branch LAN 120, LAN 130 and other LANs or LAN segments participating in a virtual private network may adhere to any of a wide variety of network protocols, the most common of which are Ethernet and Token Ring. In one embodiment of the invention, however, a VPN unit may be configured to require a particular protocol (e.g., Ethernet).
VPN units 145 and 155 couple remote clients 140 and 150, respectively, to public network 100. Remote clients are systems coupled to public network 100 from remote locations. It is frequently desirable for members of an enterprise who are travelling or working from home or other remote locations to exchange data with members of the enterprise situated at other locations. For example, remote clients 140 and 150 may communicate with headquarters LAN 110 over long distance telephone lines or other point-to-point links. As another example, client 140 may, from one remote location, communicate through VPN units 145 and 155 with client 150, at another remote location, without the participation of other VPN units or members of LANs 110, 120 or 130.
Advantageously, remote clients 140 and 150 have access to public network 100 through local Internet service providers (ISPs). In one embodiment, VPN units 145 and 155 are implemented as hardware modules. In another embodiment, VPN units 145 and 155 are implemented as software modules within remote clients 140 and 150, respectively.
For purposes of the present invention, each of VPN units 115, 125, 135, 145 and 155 serves its remote client or local area network to enable the exchange of secure communications among the remote clients and stations within the local area networks via the Internet (or other public network). VPN units 115, 125, 135, 145 and 155 include operating systems 116, 126, 136, 146 and 156, respectively, which control the operation of the respective VPN units. An illustrative internal structure of VPN unit 115 is described in more detail below with reference to FIG. 5.
Note that while VPN unit 115 is simply coupled to an interconnection between headquarters LAN 110 and public network 100, VPN unit 125 comprises an integral part of the communication path between branch LAN 120 and public network 100. Therefore, in the embodiment of the invention depicted in
VPN management station 160 illustratively has control over all VPN units participating in the management station's virtual private network. In a present embodiment of the invention, VPN management station 160 issues commands and configuration information to VPN units 115, 125, 135, 145 and 155 through public network 100. Although
VPN management station 160 may be implemented in software running on a computer system, or alternatively may be implemented in hardware utilizing a combination of microprocessors or other specially designed application specific integrated circuits, programmable logic devices, or various combinations thereof. VPN management station 160 illustratively maintains a database concerning the VPN units it manages, to include various information such as configuration data, VPN unit identities, etc. The database may be located on the management station or another computer system coupled to the management station.
According to an embodiment of the invention, VPN unit 115 is configured to send and receive data communications between members of a virtual private network that includes one or more endstations attached to headquarters LAN 110. However, VPN unit 115 only receives and processes data directed to or from a VPN member located within LAN 110 when the data are to be secured while in transit (e.g., the data constitutes VPN traffic). Because not all communications passing between headquarters LAN 110 and public network 100 constitute VPN traffic, only a portion of the data packets passed between the interconnected networks are received by VPN unit 115. VPN communications directed from LANs 110, 120 and 130 to VPN members external to the originating LAN are encrypted before being passed to the public network, while those passed in the other direction are decrypted before being passed to the destination LAN. In a present embodiment of the invention, however, a VPN unit operating in selective mode, such as VPN unit 115, does not receive or process communications that are not VPN traffic.
To enable this selective mode of operation, VPN traffic sent or received by endstations within headquarters LAN 110 conform to a "tunnel" format. In this tunnel format, data packets generated by an endstation in LAN 110 are received by VPN unit 115 where they are encrypted and encapsulated within VPN packets addressed to the VPN unit serving the destination endstation. Conversely, when VPN unit 115 receives a VPN packet from public network 100, it strips off the destination address (which corresponds to VPN unit 115), decrypts the remainder, and forwards the packet to LAN 110 for delivery to the appropriate station.
In this embodiment of the invention, a VPN unit operating in selective mode is linked to a LAN/public network interconnection through a network communication port. The VPN unit may have multiple network communication ports. In one alternative embodiment of the invention in which a selective mode VPN unit has two or more network communication ports, the VPN unit connects to multiple private or public networks and/or interconnections between a private and a public network. Illustratively, each connection is through a different network communication port, although in other alternative embodiments, multiple network connections are made through a single port. The VPN unit in an alternative embodiment, therefore, services endstations within two distinct LANs, allowing them all to participate in virtual private networks.
LANs for the different sites (e.g., headquarters LAN 110, branch LAN 120, LAN 130) illustrated in
Data packets conveyed between the various endstations and remote clients illustrated in
The placement of the various VPN units in the overall system architecture illustrated in
VPN units maintain lookup tables for identifying members of specific virtual private networks and groups within a particular virtual private network. When VPN traffic is sent between source and destination endstations that are both members of the same VPN, the VPN unit serving the source endstation processes the data packet, encrypts it, compresses it (if necessary), and adds authentication information as needed. Likewise, the receiving VPN unit that serves the destination endstation will determine that a received data packet is VPN traffic being propagated between members of a particular VPN. The receiving VPN unit authenticates, decrypts and decompresses the packet (as necessary) before forwarding it toward the destination endstation. Secure data communications are thus enabled in a manner that is transparent to end users.
When a VPN unit receives a packet from a remote client that is unknown to it (e.g., not currently authenticated), the system attempts to authenticate the remote client before forwarding traffic from that client. Illustratively, the VPN unit issues a challenge to the remote client, requiring the remote client to authenticate itself. If authentication is successful, the system dynamically retrieves configuration information for the remote client from a database and further traffic from that client will be processed according to the retrieved configuration information. As described above in the case of remote clients 140 and 150, VPN units 145 and 155 may be implemented in software that operates in conjunction with the communication software used to connect the remote client to an Internet Service Provider (ISP).
Additional disclosure concerning virtual private networks and VPN units, including their operation and configuration, is provided in a related application having U.S. Ser. No. 09/065,899, which was filed on Apr. 23, 1998 and is hereby incorporated by reference.
As mentioned above, VPN units may transmit VPN traffic in either tunnel or transport format. When configured according to the transport format, a data packet is routed according to the addresses of the originating and destination endstations (or remote clients). In tunnel mode, by contrast, a data packet is routed to/from the VPN units serving the communicating endstations or remote clients. In other words, the header information (which is used to route a packet through public network 100) differs according to the selected mode of transmission. Advantageously, VPN units operating in selective mode, as described above, process VPN traffic in tunnel format.
In
Data sections 218, 238 contain data being delivered to the destination endstation. Illustratively, data section 218 of transport data packet 210 contains the data that endstation 132 wishes to communicate to endstation 121 (e.g., text of an e-mail message). Data section 238 of tunnel data packet 230 illustratively includes the entire packet as originated by endstation 112, including IP addresses corresponding to the origination and destination endstations. As described below, in a present embodiment of the invention the bodies of VPN data packets (e.g., bodies 220, 240) are encrypted prior to transmission by the sending VPN unit, in both the transport and tunnel mode of operation.
Advantageously, an entity that intercepts data packet 230 can only learn the identity of the VPN units that are handling the packet on behalf of the communicating endstations. An entity that intercepts data packet 210, however, may be able to ascertain the true identity of the communicants.
It can be seen in
A VPN unit sending tunnel format packets, such as VPN unit 115 operating in selective mode, secures a packet received from an originating endstation by encrypting the entire original packet and appending a header consisting of addresses corresponding to itself and the VPN unit serving the destination endstation. In selective mode, instead of receiving and processing all traffic passed between interconnected public and private networks, a VPN unit illustratively only receives communications that constitute VPN traffic; "normal" traffic bypasses the VPN unit.
Parameters and configuration data such as the form of packets (e.g., transport or tunnel) to be used within a particular VPN are stored in lookup tables maintained in each VPN unit. In a present embodiment of the invention, the lookup table associated with the VPN to which a data packet's origination and destination endstations belong also identifies the algorithms to be applied to encrypt or compress the packet. For example, the lookup table associated with a particular VPN will indicate whether or not data packets transferred between members of the VPN are to be compressed and, if so, the specific compression algorithm to be used. Many compression algorithms are known, but in one embodiment of the invention LZW compression is used. The lookup table additionally identifies the authentication and any key management protocol information that is used.
The particular packet processing algorithms to be used for communications within a VPN may vary, so long as the lookup tables in both the sending and receiving VPN units identify equivalent algorithms. It is assumed that the lookup tables maintained by all of the VPN units within a VPN are consistent, i.e., that the tables within each VPN unit report the same membership for each VPN. However, as an alternative to lookup tables, VPN units may be programmed to use the same algorithms for all VPNs.
In
If the packet does not constitute VPN traffic, it is forwarded in state 320 as ordinary Internet traffic, through router 114 to Internet 100. In one embodiment of the invention, network address translation (NAT) is performed on the packet before it is forwarded to Internet 100. In yet another embodiment of the invention, the packet is filtered for access control purposes to ensure that the originating endstation is authorized to communicate with the intended destination endstation. One skilled in the art of networking will understand that by bypassing VPN unit 115, ordinary traffic does not suffer any delay that may be imposed upon packets processed by the VPN unit. From state 320, the system proceeds to end state 370.
If, however, the packet constitutes VPN traffic, it is directed or routed to VPN unit 115 in state 330, possibly by a router such as router 114. Router 114 may, for such purposes, maintain its own lookup table in order to determine when packets are to be routed to VPN unit 115 and when they are to be forwarded directly to public network 100. VPN unit 115 then processes the data packet in state 340 to apply the specified combination of compression, encryption and authentication algorithms. VPN unit 115 may also, in state 340, apply VPN policy rules, perform network address translation and/or filter the packet to enforce access control. Note that VPN unit. 115 may serve multiple VPNs, and that a particular network address may be a member of multiple VPNs.
In state 350, VPN unit 115 adds the header that characterizes data packets constructed according to the tunnel format. Specifically, and as shown in tunnel mode data packet 230 (in FIG. 2), VPN unit 115 inserts its address as the source of the tunnel mode packet and the address of the VPN unit serving the destination endstation as the destination of the packet. The identity and address of the appropriate destination VPN unit are illustratively retrieved from a lookup table in VPN unit 115. Finally, in state 360 the tunnel mode packet is forwarded toward the destination VPN unit over the public data network (e.g., through router 114). The sending procedure then ends at state 370.
Because VPN unit 115 is operating in a selective mode of operation, in the illustrated embodiment, VPN traffic to and from the endstations it serves adheres to the tunnel format, which is described above. Therefore, as demonstrated in packet 230 (in FIG. 2), a packet received from Internet 100 in the illustrated method cannot be VPN traffic if the destination address in its header is that of an endstation in LAN 110. It will be recalled that, in tunnel mode, not only is all outgoing VPN traffic from LAN 110 delivered to VPN unit 115 for encapsulation and delivery to Internet 100, but all VPN traffic destined for stations within LAN 110 is first received by VPN unit 115.
If the destination address of the packet received from Internet 100 is an endstation in LAN 110, then in state 420 the packet is forwarded to LAN 110 for delivery to the endstation as normal Internet traffic. NAT and/or filtering, as described above in conjunction with
If, however, the packet constitutes VPN traffic, in which case the destination address in its header corresponds to VPN unit 115, the packet is delivered to VPN unit 115 in state 430. Any suitable routing device situated between Internet 100 and LAN 110 (or even within LAN 110), including router 114, may make the determination in box 410 as to whether a data packet received from Internet 110 constitutes VPN traffic or not, and thereby route the packet accordingly.
In state 430, VPN unit 115 receives a packet determined to be VPN traffic. In state 440 VPN unit 115 strips the header from the VPN packet in preparation for recovering the original data packet. Then, in state 450, VPN unit 115 recovers the original data by applying the decompression and decryption algorithms in effect for the VPN to which the originating and destination endstations belong. VPN unit 115 may also apply access control rules (e.g., filtering), network address translation and/or any VPN policy rules. The reconstructed packet is then forwarded to the destination endstation in state 460. The system then proceeds to state 470, which is an end state.
When a VPN unit operates in selective mode, as does VPN unit 115 in an embodiment of the invention illustrated in
A client IP address pool is a pool of IP addresses (in the illustrated embodiment, they are local IP addresses) that are dynamically assigned by a VPN unit to remote clients and/or endstations external to the private network(s) served by the VPN unit. Illustratively, pool addresses are assigned only after traffic has been received (and authenticated) from a remote client or external endstation. In addition, in a present embodiment of the invention address assignments expire after a period of time and may then be re-assigned to another entity.
With a client IP address pool, communications directed to addresses in the pool are delivered to the VPN unit. Thus, by assigning an address from the pool to a remote station, the VPN unit receives communications sent to the remote station from endstations served by the VPN unit. When the VPN unit receives a communication from a local endstation directed to a pool address assigned to a remote station, the VPN unit processes the communication in accordance with the appropriate VPN protocol(s) and then forwards the communication to the remote station. VPN traffic sent from the remote station for endstations served by the VPN unit are addressed and delivered to the VPN unit, illustratively in accordance with the tunnel packet format described above.
In an alternative embodiment of the invention, a VPN unit employs a pool of remote addresses rather than local addresses. In such a case, however, the routing architecture serving the remote network having the remote addresses must be configured to route communications addressed to the remote addresses to the VPN unit.
In start state 500 remote client 150 initiates VPN traffic destined for endstation 113. As described above, VPN unit 155 processes and encapsulates the traffic in tunnel format in state 502 and forwards it to VPN unit 115. In state 504, the traffic is conveyed across Internet 100 and is received by router 114, which broadcasts an Address Resolution Protocol (ARP) message to determine where the traffic (addressed to 10.1.0.10) should be delivered. As stated above, router 114 as pictured in
One skilled in the art will recognize that ARP requests are merely one method by which router 114 may identify the proper recipient of communications having local destination addresses. Alternative methods may be employed without exceeding the scope of the invention.
In state 506, VPN unit 115 responds to the ARP request and router 114 forwards the traffic to VPN unit 115. VPN unit 115 de-encapsulates and processes (e.g., authenticates, decrypts and decompresses) the traffic in state 508 to recover the original communication. In state 508, the VPN unit may apply filtering rules (e.g., to enforce an access control policy). VPN unit 115 then, in state 510, changes the source address of the original traffic from the actual IP address of remote client 150 to the next available address in its client IP address pool (e.g., 10.1.0.99) and forwards the traffic to endstation 113. By changing the remote client's source address, return traffic from endstation 113 will be addressed to 10.1.0.99, which ensures that the traffic will be delivered to VPN unit 115.
In state 512, endstation 113 receives the communication from client 150 and generates return traffic to destination address 10.1.0.99. Router 114 receives the return traffic in state 514 and broadcasts an ARP message for address 10.1.0.99. In state 516, VPN unit 115, standing in for remote client 150, responds to the ARP message and router 114 forwards the return traffic to VPN unit 115.
VPN unit 115 then processes the return traffic in state 518 to encapsulate it and apply any necessary encryption, compression and authentication algorithms. VPN unit 115 also replaces the local IP address of the return traffic with the origination address of the original traffic. In end state 520, the return traffic is forwarded to Internet 100 for routing and delivery to VPN unit 155 and client 150.
VPN unit 115 includes processor 600, which is coupled to RAM 602, for executing instructions stored in RAM 602. VPN unit 115 also includes storage memories 604, 608, which take the form of non-volatile flash PROMs in one embodiment of the invention. In an alternative embodiment of the invention, VPN unit 115 includes a single storage memory. In
Pointer memory 610 includes pointer 612 and other data as described below. In a present embodiment of the invention, pointer memory 610 is coupled to battery 613 in order to preserve the contents of pointer memory 610 in the event of loss of power to VPN unit 115. As described above, VPN units are not limited to a single network communication such as port 614 in FIG. 6. VPN unit 115 may thus include additional network communication ports for communicating with additional networks other than public network 100.
Storage memory 604 illustratively stores boot code, data, and an operating system program. Upon initializing, booting or rebooting VPN unit 115, the boot code is loaded into RAM 602 for execution by processor 600. VPN unit 115 may, for example, be rebooted in response to a command received from a local console through local communication port 616 or a command received from VPN management station 160 (from
Data stored in storage memory 604 illustratively includes certification data for authenticating VPN unit 115 to VPN management station 160. When VPN unit 115 is to be configured by VPN management station 160, as described below, VPN unit 115 and VPN management station 160 authenticate themselves to each other. This dual authentication process prevents an impostor from masquerading as one or the other and thereby corrupting VPN unit 115 or another element of a virtual private network.
Storage memory 608 illustratively includes configuration data and an alternate operating system program. Configuration data includes information used to operate VPN unit 115, such as: an IP address of the unit, IP addresses of VPN members (e.g., endstations in LAN 110 served by VPN unit 115) that will be exchanging data through the unit, the encryption algorithm to be used for VPN traffic, the authentication algorithm to be used, whether or not to compress data, SNMP (Simple Network Management Protocol) data used to manage the unit (e.g., name and physical description of VPN unit 115), etc. The contents of configuration data are, in one embodiment of the invention, updated when VPN unit 115 is configured or reconfigured by VPN management station 160.
After executing the boot code retrieved from storage memory 604, processor 600 loads (into RAM 602) and executes instructions according to an operating system program from either of storage memories 604, 608. The storage memory from which an operating system program is to be retrieved the next time VPN unit 115 is booted is identified by pointer 612, which is stored in pointer memory 610. Therefore, pointer 612 usually identifies the storage memory from which the currently executing operating system program was retrieved.
In an embodiment of the present invention, pointer memory 610 also stores some of the contents of the configuration data residing in storage memory 608. Illustratively, when VPN unit 115 is configured or reconfigured by VPN management station 160, configuration data essential to the continued operation of VPN unit 115 (e.g., the IP address of VPN unit 115, default route for communicating with the VPN management station) are copied into pointer memory 610. Doing so helps ensure the continued operation of VPN unit 115 during the configuration or reconfiguration process.
Network communication port 614 couples VPN unit 115 to the interconnection of LAN 110 and public network 100. VPN unit 115 thus receives and transmits VPN traffic through network communication port 614. As mentioned above, network communication port 614 is also the receiving point for configuration information sent from VPN management system 160. Local communication port 616 connects VPN unit 115 to a local console, from which the unit may also be configured.
Packet processing module 618 applies configuration parameters to process packets transiting VPN unit 115. Illustratively, the packet processing module determines whether and/or how a packet is to be encrypted, whether it is to be formatted in tunnel or transport mode, how it is to be addressed, etc.
In state 704, the system manager issues commands to create and define group objects for various groups of entities connected to public network 100. In a present embodiment, a group object includes an attribute identifying the VPN unit(s) associated with the group and the net/mask pairs the group defines. The entities within a group may be nodes on a computer network that are addressed by IP address identifiers. The entities may also be system users that are identified by user IDs.
The system manager then proceeds to state 706, in which the system manager identifies remote clients that are to be members of a VPN. Illustratively, a client object is created for each remote client supported by VPN management station 160. A client object comprises a number of attributes, including a listing of the virtual private network(s) the client belongs to and the NSID/MKID identifier for the remote client. In one embodiment, the NSID, or name space ID, is the MD5 hash of a user name, and the MKID is the master key ID of the domain.
The system manager then proceeds to state 708, in which the system manager issues a command to create a VPN object. Illustratively, a VPN object is created for each virtual private network supported by VPN management station 160. A VPN object comprises a number of attributes, including encryption, authentication and compression algorithms, a list of groups, and a list of remote clients included in the corresponding VPN. In state 710, the system manager defines the authentication, encryption and compression algorithms to be associated with each VPN. Next, the system manager proceeds to state 712. In state 712, the system manager assembles groups of entities and remote clients into a VPN. States 710 and 712 are repeated for each VPN that the system manager desires to create.
The system manager then proceeds to state 714. In state 714, the system manager defines access control rules for VPN units. Access control rules specify the types of communications allowed to pass through a VPN unit and, for VPN units operating in selective mode, that VPN traffic is to be passed in tunnel format. Next, the system manager proceeds to state 716.
In state 716, the system manager specifies address translation rules for each VPN unit. These address translation rules support static translation, dynamic translation and port translation. For example, the rules make it possible to use the same address for two different nodes that are located on different local area networks that are coupled to the public network through VPN units. The VPN units use the address translation rules to translate the same local addresses into different public network addresses. Address translation rules also facilitate mapping multiple local addresses to a single public network address. In one embodiment, this is accomplished by using the same public network address with different port identifiers for different local addresses. The system manager then proceeds to state 718, which is an end state.
As mentioned above, VPN unit 115 periodically receives configuration instructions from VPN management station 160. Illustratively, these commands include requests to: install a new operating system program; configure a VPN (e.g., set up a new VPN, edit an existing VPN, delete a VPN); change an encryption, authentication or compression algorithm; select tunnel or transport format for VPN traffic; store a static route configuration; store or edit a lookup table; reboot the VPN unit; etc.
In an embodiment of the present invention, configuration requests received by a VPN unit are satisfied by a configuration module, which illustratively takes the form of a background operating system process executed by the VPN unit's processor 600. In this embodiment, a configuration module executing on VPN unit 115 monitors network communication port 614 to detect configuration requests sent by VPN management station 160. A configuration module in another embodiment monitors local communication port 616 instead of, or in addition to, network communication port 614, for configuration requests sent from a local console.
The configuration module temporarily stores the contents of configuration requests into RAM 602 as the requests are received. At the end of a pre-specified period of time (e.g., 30 seconds), the new or altered configuration data is stored in long-term storage memory (e.g., a configuration data storage area within storage memory 608, from FIG. 5). As described above, essential configuration data may also be stored in other memory (e.g., pointer memory 610) for redundancy and continuity of operation.
The procedure commences with start state 800. In state 802 a configuration request ordering the configuration of a VPN is received from the local console through local communication port 616. In an alternative procedure in which the configuration request is received from VPN management station 160 via network communication port 614, VPN unit 115 and VPN management station 160 authenticate themselves to each other before proceeding.
In state 804, VPN unit 115 receives an identifier corresponding to the VPN being configured. The identifier may correspond to a new VPN or an existing VPN. VPN unit 115 then receives various VPN configuration data for use in the chosen VPN. In state 806, VPN unit 115 receives the configuration data to be applied to the identified VPN. The configuration data illustratively includes the encryption, compression and algorithms for the VPN, and a specification as to whether transport or tunnel formatting is to be applied to VPN data packets.
In state 808, VPN unit 115 is apprised of the local addresses to be included in the VPN. The local addresses correspond to endstations within the private network(s) served by VPN unit 115 that are members of the VPN. VPN unit 115 is also provided with a plurality of IP addresses (preferably local addresses) to be used as a client IP address pool (as described above). In state 810, VPN unit 115 receives the remote addresses corresponding to members of the VPN external to the private network(s) served by VPN unit 115.
The new configuration data is then stored in state 812, illustratively in storage memory 608. Upon successful receipt and storage of the configuration request and the accompanying data, VPN unit 115 acknowledges the request in state 814 and the procedure exits in end state 816.
The foregoing descriptions of embodiments of the invention have been presented for purposes of illustration and description only. They are not intended to be exhaustive or to limit the invention to the forms disclosed. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art.
In particular, a single VPN unit may be configured, as described above, to serve multiple private networks. In such an embodiment, each private network may have its own route to public network 100, but share the one VPN unit. The VPN unit advantageously operates in selective mode, so that only VPN traffic is routed through it. Non-VPN traffic bypasses the VPN unit. Alternatively, each of a plurality of private networks served by a single VPN unit share a single path between the VPN unit and public network 100.
Arrow, Leslie J., Hoke, Mark R.
| Patent | Priority | Assignee | Title |
| 10003576, | Dec 10 2003 | SONICWALL US HOLDINGS INC | Rule-based routing to resources through a network |
| 10135827, | Dec 10 2003 | SONICWALL US HOLDINGS INC | Secure access to remote resources over a network |
| 10187387, | Oct 30 1998 | VirnetX, Inc. | Method for establishing connection between devices |
| 10218782, | Dec 10 2003 | SonicWALL Inc. | Routing of communications to one or more processors performing one or more services according to a load balancing function |
| 10225146, | Dec 07 2009 | Amazon Technologies, Inc. | Using virtual networking devices to manage routing information |
| 10313350, | Dec 10 2003 | SonicWALL Inc. | Remote access to resources over a network |
| 10382595, | Jan 29 2014 | SMART SECURITY SYSTEMS LLC | Systems and methods for protecting communications |
| 10419287, | Dec 07 2009 | Amazon Technologies, Inc. | Using virtual networking devices and routing information to associate network addresses with computing nodes |
| 10511573, | Oct 30 1998 | VirnetX, Inc. | Agile network protocol for secure communications using secure domain names |
| 10637839, | May 24 2012 | SMART SECURITY SYSTEMS LLC | Systems and methods for protecting communications between nodes |
| 10728089, | Dec 10 2008 | Amazon Technologies, Inc. | Providing access to configurable private computer networks |
| 10735516, | Feb 15 2019 | SIGNIANT INC | Cloud-based authority to enhance point-to-point data transfer with machine learning |
| 10735812, | Feb 08 2006 | AT&T Intellectual Property I, L.P. | Interactive program manager and methods for presenting program content |
| 10778659, | May 24 2012 | SMART SECURITY SYSTEMS LLC | System and method for protecting communications |
| 10868715, | Dec 10 2008 | Amazon Technologies, Inc. | Providing local secure network access to remote services |
| 10868723, | Dec 07 2009 | Amazon Technologies, Inc. | Using virtual networking devices and routing information to associate network addresses with computing nodes |
| 10951586, | Dec 10 2008 | Amazon Technologies, Inc. | Providing location-specific network access to remote services |
| 11194930, | Apr 27 2018 | DataTrendz, LLC | Unobtrusive systems and methods for collecting, processing and securing information transmitted over a network |
| 11290320, | Dec 10 2008 | Amazon Technologies, Inc. | Providing access to configurable private computer networks |
| 11463412, | Mar 29 2022 | UAB 360 IT | Protected configuration of a virtual private network server |
| 11516080, | Dec 07 2009 | Amazon Technologies, Inc. | Using virtual networking devices and routing information to associate network addresses with computing nodes |
| 11601401, | Mar 29 2022 | UAB 360 IT | Secure configuration of a virtual private network server |
| 11641342, | Mar 29 2022 | UAB 360 IT | Protected configuration of a virtual private network server |
| 11698991, | Apr 27 2018 | DataTrendz, LLC | Unobtrusive systems and methods for collecting, processing and securing information transmitted over a network |
| 11757843, | Mar 29 2022 | UAB 360 IT | Protected configuration of a virtual private network server |
| 11765134, | Mar 29 2022 | UAB 360 IT | Secure configuration of a virtual private network server |
| 11777905, | Mar 29 2022 | UAB 360 IT | Secure configuration of a virtual private network server |
| 11811871, | Feb 15 2019 | Signiant Inc. | Cloud-based authority to enhance point-to-point data transfer with machine learning |
| 11831496, | Dec 10 2008 | Amazon Technologies, Inc. | Providing access to configurable private computer networks |
| 11870644, | Dec 07 2009 | Amazon Technologies, Inc. | Exchange of routing information to support virtual computer networks hosted on telecommunications infrastructure network |
| 12101299, | Mar 29 2022 | UAB 360 IT | Protected configuration of a virtual private network server |
| 12170650, | Mar 29 2022 | UAB 360 IT | Secure configuration of a virtual private network server |
| 6845452, | Mar 12 2002 | Cisco Technology, Inc | Providing security for external access to a protected computer network |
| 6907532, | Mar 04 2000 | Telefonaktiebolaget LM Ericsson (publ) | Communication node, communication network and method of recovering from a temporary failure of a node |
| 6920502, | Apr 13 2000 | AEP NETWORKS, INC | APPARATUS AND ACCOMPANYING METHODS FOR PROVIDING, THROUGH A CENTRALIZED SERVER SITE, AN INTEGRATED VIRTUAL OFFICE ENVIRONMENT, REMOTELY ACCESSIBLE VIA A NETWORK-CONNECTED WEB BROWSER, WITH REMOTE NETWORK MONITORING AND MANAGEMENT CAPABILITIES |
| 7006502, | Dec 17 1998 | GOLDMAN SACHS SPECIALTY LENDING GROUP L P | System using stream specification and action specification stored in policy cache to process the flow of data packets by appropriate action processor |
| 7010702, | Jun 12 1997 | AVAYA Inc | Architecture for virtual private networks |
| 7013342, | Dec 10 2001 | GEN DIGITAL INC | Dynamic tunnel probing in a communications network |
| 7036143, | Sep 19 2001 | Cisco Technology, Inc. | Methods and apparatus for virtual private network based mobility |
| 7043753, | Mar 12 2002 | Cisco Technology, Inc | Providing security for external access to a protected computer network |
| 7072964, | Aug 31 1999 | ANXEBUSINESS CORP | System and method for interconnecting multiple virtual private networks |
| 7076633, | Mar 28 2001 | Virtuozzo International GmbH | Hosting service providing platform system and method |
| 7076797, | Oct 05 2001 | Microsoft Technology Licensing, LLC | Granular authorization for network user sessions |
| 7096495, | Mar 31 2000 | Intel Corporation | Network session management |
| 7099948, | Feb 16 2001 | Virtuozzo International GmbH | Virtual computing environment |
| 7117530, | Dec 07 1999 | GOLDMAN SACHS SPECIALTY LENDING GROUP L P | Tunnel designation system for virtual private networks |
| 7130629, | Mar 08 2000 | Cisco Technology, Inc. | Enabling services for multiple sessions using a single mobile node |
| 7131141, | Jul 27 2001 | AT&T Corp. | Method and apparatus for securely connecting a plurality of trust-group networks, a protected resource network and an untrusted network |
| 7133404, | Aug 11 2000 | LF CAPITAL PARTNERS, LLC | Communication using two addresses for an entity |
| 7181535, | Dec 24 1998 | Gula Consulting Limited Liability Company | Addressing method and name and address server in a digital network |
| 7185365, | Mar 27 2002 | Intel Corporation | Security enabled network access control |
| 7240202, | Mar 16 2000 | Apple Inc | Security context sharing |
| 7246373, | Sep 19 2001 | Cisco Technology, Inc. | Methods and apparatus for virtual private network based mobility |
| 7251824, | Dec 19 2000 | Intel Corporation | Accessing a private network |
| 7269639, | Dec 13 2000 | CISCO TECHNOLOGY, INC A CALIFORNIA CORP | Method and system to provide secure in-band management for a packet data network |
| 7283537, | Jun 15 2000 | NEC Corporation | Network system and packet data transmission method |
| 7289994, | Oct 18 1999 | Fisher-Rosemount Systems, Inc. | Interconnected zones within a process control system |
| 7349951, | May 12 2003 | Hewlett-Packard Development Company, L.P. | Systems and methods for accessing a printing service |
| 7370348, | Jul 30 1999 | Intel Corporation | Technique and apparatus for processing cryptographic services of data in a network system |
| 7401354, | Jan 29 1999 | International Business Machines Corporation | System and method for network address translation integration with IP Security |
| 7420976, | Dec 17 1998 | GOLDMAN SACHS SPECIALTY LENDING GROUP L P | System directing flow of packets by-passing policy-based application for processing by policy engine according to action specification in policy cache |
| 7421736, | Jul 02 2002 | Lucent Technologies Inc. | Method and apparatus for enabling peer-to-peer virtual private network (P2P-VPN) services in VPN-enabled network |
| 7426384, | Jul 13 2004 | Vodafone Group PLC | Network communication system including a database of codes and corresponding telephone numbers |
| 7426565, | Feb 16 2001 | Virtuozzo International GmbH | Virtual computing environment |
| 7447188, | Jun 22 2004 | Cisco Technology, Inc. | Methods and apparatus for supporting mobile IP proxy registration in a system implementing mulitple VLANs |
| 7457289, | Dec 16 2002 | Cisco Technology, Inc. | Inter-proxy communication protocol for mobile IP |
| 7469323, | Mar 28 2001 | Virtuozzo International GmbH | Hosting service platform system and method |
| 7471661, | Feb 20 2002 | Cisco Technology, Inc. | Methods and apparatus for supporting proxy mobile IP registration in a wireless local area network |
| 7505432, | Apr 28 2003 | Cisco Technology, Inc. | Methods and apparatus for securing proxy Mobile IP |
| 7519834, | Jan 24 2003 | RPX CLEARINGHOUSE LLC | Scalable method and apparatus for transforming packets to enable secure communication between two stations |
| 7526557, | Jun 30 2004 | SIGNIANT, INC | System and method for transferring data in high latency firewalled networks |
| 7526658, | Jan 24 2003 | RPX CLEARINGHOUSE LLC | Scalable, distributed method and apparatus for transforming packets to enable secure communication between two stations |
| 7535907, | Apr 08 2005 | CAVIUM INTERNATIONAL; MARVELL ASIA PTE, LTD | TCP engine |
| 7552310, | Mar 28 2001 | Virtuozzo International GmbH | Virtualization and hosting service platform system and method |
| 7571463, | Jan 24 2003 | AVAYA LLC | Method an apparatus for providing a scalable and secure network without point to point associations |
| 7594262, | Sep 04 2002 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | System and method for secure group communications |
| 7617527, | Jun 12 1997 | Avaya Inc. | Architecture for virtual private networks |
| 7620707, | Jun 30 2004 | DATTO, LLC | Remote computer management when a proxy server is present at the site of a managed computer |
| 7644437, | Dec 20 2001 | Microsoft Technology Licensing, LLC | Method and apparatus for local area networks |
| 7650424, | Apr 04 2000 | WSOU Investments, LLC | Supporting mobile hosts on an internet protocol network |
| 7673048, | Feb 24 2003 | Cisco Technology, Inc. | Methods and apparatus for establishing a computerized device tunnel connection |
| 7675923, | Nov 24 2004 | Google Technology Holdings LLC | Home network bridge-based communications method and apparatus |
| 7698388, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Secure access to remote resources over a network |
| 7703132, | Jan 25 2002 | Microsoft Technology Licensing, LLC | Bridged cryptographic VLAN |
| 7765581, | Dec 10 1999 | Oracle America, Inc | System and method for enabling scalable security in a virtual private network |
| 7770222, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Creating an interrogation manifest request |
| 7773604, | Dec 17 1998 | GOLDMAN SACHS SPECIALTY LENDING GROUP L P | System directing flow of packets by-passing policy-based application for processing by policy engine according to action specification in policy cache |
| 7779469, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Provisioning an operating environment of a remote computer |
| 7818796, | Dec 20 2001 | Microsoft Technology Licensing, LLC | Bridged cryptographic VLAN |
| 7827547, | Jun 30 2004 | DATTO, LLC | Use of a dynamically loaded library to update remote computer management capability |
| 7827590, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Controlling access to a set of resources in a network |
| 7836205, | Jul 11 2002 | Hewlett Packard Enterprise Development LP | Method and device for use with a virtual network |
| 7869436, | Oct 13 2005 | Cisco Technology, Inc. | Methods and apparatus for connecting to virtual networks using non supplicant authentication |
| 7877080, | Dec 20 2001 | Microsoft Technology Licensing, LLC | Public access point |
| 7882558, | Dec 07 1999 | GOLDMAN SACHS SPECIALTY LENDING GROUP L P | Tunnel designation system for virtual private networks |
| 7886354, | Dec 20 2001 | Microsoft Technology Licensing, LLC | Method and apparatus for local area networks |
| 7895431, | Sep 10 2004 | CAVIUM INTERNATIONAL; MARVELL ASIA PTE, LTD | Packet queuing, scheduling and ordering |
| 7921211, | Oct 30 1998 | VirnetX, Inc. | Agile network protocol for secure communications using secure domain names |
| 7925693, | Jan 24 2000 | ZHIGU HOLDINGS LIMITED | NAT access control with IPSec |
| 7933990, | Oct 30 1998 | VirnetX, Inc. | Agile network protocol for secure communications with assured system availability |
| 7937471, | Jun 03 2002 | F POSZAT HU, L L C | Creating a public identity for an entity on a network |
| 7945654, | Oct 30 1998 | VirnetX, Inc. | Agile network protocol for secure communications using secure domain names |
| 7949785, | Mar 31 2003 | Intellectual Ventures I LLC | Secure virtual community network system |
| 7986937, | Jan 25 2002 | Microsoft Technology Licensing, LLC | Public access point |
| 7987274, | Oct 30 1998 | Virnetx, Incorporated | Method for establishing secure communication link between computers of virtual private network |
| 7996539, | Oct 30 1998 | VIRNETX INC | Agile network protocol for secure communications with assured system availability |
| 8005983, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Rule-based routing to resources through a network |
| 8041761, | Dec 23 2002 | NetApp, Inc | Virtual filer and IP space based IT configuration transitioning framework |
| 8051181, | Oct 30 1998 | VirnetX, Inc. | Method for establishing secure communication link between computers of virtual private network |
| 8090843, | Jun 03 2002 | F POSZAT HU, L L C | Creating a public identity for an entity on a network |
| 8102758, | Mar 05 2007 | Cisco Technology, Inc.; Cisco Technology, Inc | Analyzing virtual private network failures |
| 8146148, | Nov 19 2003 | Cisco Technology, Inc. | Tunneled security groups |
| 8161162, | Jun 30 2004 | DATTO, LLC | Remote computer management using network communications protocol that enables communication through a firewall and/or gateway |
| 8194654, | Jul 29 1996 | Cisco Technology, Inc. | Virtual dial-up protocol for network communication |
| 8200794, | Jun 30 2004 | DATTO, LLC | Primitive functions for use in remote computer management |
| 8224971, | Dec 28 2009 | Amazon Technologies, Inc. | Using virtual networking devices and routing information to initiate external actions |
| 8234358, | Aug 30 2002 | F POSZAT HU, L L C | Communicating with an entity inside a private network using an existing connection to initiate communication |
| 8255973, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Provisioning remote computers for accessing resources |
| 8259676, | Apr 28 2003 | Cisco Technology, Inc. | Methods and apparatus for securing proxy mobile IP |
| 8286203, | Dec 19 2003 | AT&T Intellectual Property I, L P | System and method for enhanced hot key delivery |
| 8301769, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Classifying an operating environment of a remote computer |
| 8312129, | Dec 28 2009 | Amazon Technologies, Inc. | Using virtual networking devices to connect managed computer networks |
| 8347377, | Dec 20 2001 | Microsoft Technology Licensing, LLC | Bridged cryptographic VLAN |
| 8370488, | Dec 28 2009 | Amazon Technologies, Inc. | Using virtual networking devices to manage routing communications between connected computer networks |
| 8392608, | Dec 07 2009 | Amazon Technologies, Inc. | Using virtual networking devices to manage network configuration |
| 8422467, | Feb 20 2002 | Cisco Technology, Inc. | Methods and apparatus for supporting proxy mobile IP registration in a wireless local area network |
| 8423669, | Jun 16 2000 | Fujitsu Limited | Communication device having VPN accommodation function |
| 8438254, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Providing distributed cache services |
| 8458341, | Oct 30 1998 | VirnetX, Inc. | System and method employing an agile network protocol for secure communications using secure domain names |
| 8489767, | Jun 16 2000 | Fujitsu Limited | Communication device having VPN accommodation function |
| 8504665, | Jun 30 2004 | DATTO, LLC | Management of a device connected to a remote computer using the remote computer to effect management actions |
| 8504696, | Oct 30 1998 | VirnetX, Inc. | System and method employing an agile network protocol for secure communications using secure domain names |
| 8504697, | Oct 30 1998 | VirnetX, Inc. | System and method employing an agile network protocol for secure communications using secure domain names |
| 8516117, | Oct 30 1998 | VirnetX, Inc. | Agile network protocol for secure communications with assured system availability |
| 8516131, | Oct 30 1998 | VirnetX, Inc. | System and method employing an agile network protocol for secure communications using secure domain names |
| 8521888, | Oct 30 1998 | VirnetX, Inc. | System and method employing an agile network protocol for secure communications using secure domain names |
| 8554899, | Oct 30 1998 | VirnetX, Inc. | Agile network protocol for secure communications using secure domain names |
| 8560705, | Oct 30 1998 | VirnetX, Inc. | System and method employing an agile network protocol for secure communications using secure domain names |
| 8571038, | Oct 24 2007 | LANTRONIX, INC | Method to tunnel UDP-based device discovery |
| 8572247, | Oct 30 1998 | VirnetX, Inc. | Agile network protocol for secure communications using secure domain names |
| 8572249, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Network appliance for balancing load and platform services |
| 8578003, | Dec 10 2008 | Amazon Technologies, Inc. | Providing access to configurable private computer networks |
| 8590032, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Rule-based routing to resources through a network |
| 8601550, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Remote access to resources over a network |
| 8613041, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Creating rules for routing resource access requests |
| 8615796, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Managing resource allocations |
| 8661158, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Smart tunneling to resources in a network |
| 8667145, | Jun 30 2004 | Signiant, Inc. | System and method for transferring data in high latency firewalled networks |
| 8687485, | Sep 12 2003 | RPX CLEARINGHOUSE LLC | Method and apparatus for providing replay protection in systems using group security associations |
| 8700775, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Routing of communications to a platform service |
| 8793353, | Oct 24 2007 | LANTRONIX, INC | Systems and methods for creation of reverse virtual internet protocol addresses |
| 8819758, | Apr 25 1995 | AT&T Intellectual Property I, L P | System and method for providing television services |
| 8843643, | Oct 30 1998 | VirnetX, Inc. | System and method employing an agile network protocol for secure communications using secure domain names |
| 8844020, | Dec 10 2008 | Amazon Technologies, Inc. | Establishing secure remote access to private computer networks |
| 8850009, | Oct 30 1998 | VirnetX, Inc. | System and method employing an agile network protocol for secure communications using secure domain names |
| 8868705, | Oct 30 1998 | VirnetX, Inc. | Agile network protocol for secure communications using secure domain names |
| 8874771, | Oct 30 1998 | VirnetX, Inc. | Agile network protocol for secure communications with assured system availability |
| 8904516, | Oct 30 1998 | VirnetX, Inc. | System and method employing an agile network protocol for secure communications using secure domain names |
| 8914839, | Apr 25 1995 | AT&T Intellectual Property I, L P | System and method for providing television services |
| 8914872, | Jun 15 1999 | SSH Communications Security OYJ | Revealing occurrence of network address translations |
| 8914873, | Jun 15 1999 | SSH Communications Security OYJ | Revealing address information in systems where network address translations occur |
| 8918858, | Jun 15 1999 | SSH Communications Security OYJ | Communications across a network address translator |
| 8930475, | Mar 30 2012 | Signiant Inc.; SIGNIANT INC | Systems and methods for secure cloud-based media file sharing |
| 8943201, | Oct 30 1998 | VirnetX, Inc. | Method for establishing encrypted channel |
| 8959384, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Routing of communications to one or more processors performing one or more services according to a load balancing function |
| 8966542, | Apr 25 1995 | AT&T Intellectual Property I, L.P. | System and method for providing media content and interactive content |
| 8973126, | Jun 15 1999 | SSH Communications Security OYJ | Determining occurrence of a network address translation |
| 8973127, | Jun 15 1999 | SSH Communications Security OYJ | Communications across a network address translator |
| 8995301, | Dec 07 2009 | Amazon Technologies, Inc. | Using virtual networking devices to manage routing cost information |
| 9027115, | Oct 30 1998 | VirnetX, Inc. | System and method for using a registered name to connect network devices with a link that uses encryption |
| 9036504, | Dec 07 2009 | Amazon Technologies, Inc. | Using virtual networking devices and routing information to associate network addresses with computing nodes |
| 9037713, | Oct 30 1998 | VirnetX, Inc. | Agile network protocol for secure communications using secure domain names |
| 9038163, | Oct 30 1998 | VirnetX, Inc. | Systems and methods for connecting network devices over communication network |
| 9071578, | Jun 15 1999 | SSH Communications Security OYJ | Maintaining network address translations |
| 9077694, | Oct 30 1998 | VirnetX, Inc. | Agile network protocol for secure communications using secure domain names |
| 9077695, | Oct 30 1998 | VirnetX, Inc.; VIRNETX, INC | System and method for establishing an encrypted communication link based on IP address lookup requests |
| 9094399, | Oct 30 1998 | VirnetX, Inc. | Method for establishing secure communication link between computers of virtual private network |
| 9094421, | Dec 28 2009 | Amazon Technologies, Inc. | Using virtual networking devices to connect managed computer networks |
| 9100375, | Oct 30 1998 | VirnetX, Inc. | System and method employing an agile network protocol for secure communications using secure domain names |
| 9137102, | Dec 28 2009 | Amazon Technologies, Inc. | Using virtual networking devices to manage routing communications between connected computer networks |
| 9137209, | Dec 10 2008 | Amazon Technologies, Inc | Providing local secure network access to remote services |
| 9172678, | Jun 28 2011 | AT&T Intellectual Property I, L.P.; AT&T INTELLECTUAL PROPERTY I, L P , A NEVADA PARTNERSHIP | Methods and apparatus to improve security of a virtual private mobile network |
| 9185075, | Mar 30 2001 | Juniper Networks, Inc. | Internet security system |
| 9197538, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Rule-based routing to resources through a network |
| 9203747, | Dec 07 2009 | Amazon Technologies, Inc. | Providing virtual networking device functionality for managed computer networks |
| 9210041, | Dec 07 2009 | Amazon Technologies, Inc. | Using virtual networking devices to manage network configuration |
| 9218106, | Feb 08 2006 | AT&T Intellectual Property I, L.P. | Interactive program manager and methods for presenting program content |
| 9219679, | Dec 07 2009 | Amazon Technologies, Inc. | Using virtual networking devices to manage routing cost information |
| 9268656, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Routing of communications to one or more processors performing one or more services according to a load balancing function |
| 9300670, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Remote access to resources over a network |
| 9374341, | Dec 10 2008 | Amazon Technologies, Inc. | Establishing secure remote access to private computer networks |
| 9374346, | Oct 30 1998 | VirnetX, Inc. | Agile network protocol for secure communications using secure domain names |
| 9385994, | Mar 30 2001 | Juniper Networks, Inc. | Network security device |
| 9386000, | Oct 30 1998 | VirnetX, Inc. | System and method for establishing a communication link |
| 9397927, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Rule-based routing to resources through a network |
| 9407456, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Secure access to remote resources over a network |
| 9413657, | Jun 16 2000 | Fujitsu Limited | Communication device having VPN accommodation function |
| 9413766, | Oct 30 1998 | VIRNETX, INC | Method for establishing connection between devices |
| 9438564, | Sep 18 2012 | GOOGLE LLC | Managing pooled VPN proxy servers by a central server |
| 9467398, | Dec 28 2009 | Amazon Technologies, Inc. | Using virtual networking devices to connect managed computer networks |
| 9479426, | Oct 30 1998 | VIRNETZ, INC. | Agile network protocol for secure communications with assured system availability |
| 9497040, | Dec 28 2009 | Amazon Technologies, Inc. | Using virtual networking devices and routing information to initiate external actions |
| 9521037, | Dec 10 2008 | Amazon Technologies, Inc. | Providing access to configurable private computer networks |
| 9524167, | Dec 10 2008 | Amazon Technologies, Inc | Providing location-specific network access to remote services |
| 9537829, | Jun 28 2011 | AT&T Intellectual Property I, L.P. | Methods and apparatus to improve security of a virtual private mobile network |
| 9544646, | Dec 19 2003 | AT&T Intellectual Property I, L.P. | System and method for enhanced hot key delivery |
| 9544648, | Feb 08 2006 | AT&T Intellectual Property I, L.P. | Interactive program manager and methods for presenting program content |
| 9577876, | Dec 28 2009 | Amazon Technologies, Inc. | Using virtual networking devices to manage routing communications between connected computer networks |
| 9596216, | Mar 30 2012 | Signiant Inc. | Systems and methods for secure cloud-based media file sharing |
| 9628489, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Remote access to resources over a network |
| 9645509, | Nov 10 2008 | ASML NETHERLANDS B V | Scanner model representation with transmission cross coefficients |
| 9667534, | Jul 10 2000 | AlterWAN, Inc. | VPN usage to create wide area network backbone over the internet |
| 9667594, | Jun 15 1999 | SSH Communications Security OYJ | Maintaining network address translations |
| 9692799, | Jul 30 2012 | Signiant Inc. | System and method for sending and/or receiving digital content based on a delivery specification |
| 9722871, | Dec 07 2009 | Amazon Technologies, Inc. | Using virtual networking devices and routing information to associate network addresses with computing nodes |
| 9736234, | Dec 10 2003 | QUEST SOFTWARE INC F K A DELL SOFTWARE INC ; Aventail LLC | Routing of communications to one or more processors performing one or more services according to a load balancing function |
| 9742857, | Aug 24 2012 | Citrix Systems, Inc. | Systems and methods for supporting a network profile |
| 9756018, | Dec 10 2008 | Amazon Technologies, Inc. | Establishing secure remote access to private computer networks |
| 9769021, | Dec 07 2009 | Amazon Technologies, Inc. | Using virtual networking devices to manage routing cost information |
| 9819649, | Oct 30 1998 | VirnetX, Inc. | System and method employing an agile network protocol for secure communications using secure domain names |
| 9830330, | Mar 30 2012 | Signiant Inc. | Systems and methods for secure cloud-based media file sharing |
| 9860283, | Oct 30 1998 | VIRNETX, INC | Agile network protocol for secure video communications with assured system availability |
| 9900214, | Dec 07 2009 | Amazon Technologies, Inc. | Using virtual networking devices to manage network configuration |
| 9906534, | Dec 10 2003 | SonicWALL Inc. | Remote access to resources over a network |
| 9967240, | Oct 30 1998 | VIRNETX, INC | Agile network protocol for secure communications using secure domain names |
| 9985800, | Jul 10 2000 | AlterWAN, Inc. | VPN usage to create wide area network backbone over the internet |
| 9998335, | Dec 07 2009 | Amazon Technologies, Inc. | Emulating virtual router device functionality in virtual computer networks |
| ER1619, | |||
| RE41024, | Aug 11 2000 | LF CAPITAL PARTNERS, LLC | Communication using two addresses for an entity |
| Patent | Priority | Assignee | Title |
| 5835726, | Dec 15 1993 | Check Point Software Technologies Ltd | System for securing the flow of and selectively modifying packets in a computer network |
| 5950195, | Sep 18 1996 | McAfee, LLC | Generalized security policy management system and method |
| 6079020, | Jan 27 1998 | AVAYA Inc | Method and apparatus for managing a virtual private network |
| 6154839, | Apr 23 1998 | AVAYA Inc | Translating packet addresses based upon a user identifier |
| 6173399, | Jun 12 1997 | AVAYA Inc | Apparatus for implementing virtual private networks |
| 6175917, | Apr 23 1998 | AVAYA Inc | Method and apparatus for swapping a computer operating system |
| 6182226, | Mar 18 1998 | JPMORGAN CHASE BANK, N A ; MORGAN STANLEY SENIOR FUNDING, INC | System and method for controlling interactions between networks |
| 6226751, | Apr 17 1998 | AVAYA Inc | Method and apparatus for configuring a virtual private network |
| 6353614, | Mar 05 1998 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Method and protocol for distributed network address translation |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Nov 05 1998 | HOKE, MARK R | VPNET TECHNOLOGIES, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 009591 | /0321 | |
| Nov 06 1998 | ARROW, LESLIE J | VPNET TECHNOLOGIES, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 009591 | /0321 | |
| Nov 09 1998 | VPNet Technologies, Inc. | (assignment on the face of the patent) | / | |||
| Apr 05 2002 | Avaya Technology Corp | BANK OF NEW YORK, THE | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 012761 | /0977 | |
| Oct 04 2005 | Avaya Technology Corp | Avaya Technology LLC | CONVERSION FROM CORP TO LLC | 022071 | /0420 | |
| Oct 26 2007 | Avaya, Inc | CITICORP USA, INC , AS ADMINISTRATIVE AGENT | SECURITY AGREEMENT | 020166 | /0705 | |
| Oct 26 2007 | VPNET TECHNOLOGIES, INC | CITICORP USA, INC , AS ADMINISTRATIVE AGENT | SECURITY AGREEMENT | 020166 | /0705 | |
| Oct 26 2007 | OCTEL COMMUNICATIONS LLC | CITIBANK, N A , AS ADMINISTRATIVE AGENT | SECURITY AGREEMENT | 020156 | /0149 | |
| Oct 26 2007 | Avaya, Inc | CITIBANK, N A , AS ADMINISTRATIVE AGENT | SECURITY AGREEMENT | 020156 | /0149 | |
| Oct 26 2007 | OCTEL COMMUNICATIONS LLC | CITICORP USA, INC , AS ADMINISTRATIVE AGENT | SECURITY AGREEMENT | 020166 | /0705 | |
| Oct 26 2007 | Avaya Technology LLC | CITICORP USA, INC , AS ADMINISTRATIVE AGENT | SECURITY AGREEMENT | 020166 | /0705 | |
| Oct 26 2007 | Avaya Technology LLC | CITIBANK, N A , AS ADMINISTRATIVE AGENT | SECURITY AGREEMENT | 020156 | /0149 | |
| Oct 26 2007 | VPNET TECHNOLOGIES, INC | CITIBANK, N A , AS ADMINISTRATIVE AGENT | SECURITY AGREEMENT | 020156 | /0149 | |
| Jun 25 2008 | Avaya Technology LLC | AVAYA Inc | REASSIGNMENT | 021158 | /0310 | |
| Feb 11 2011 | AVAYA INC , A DELAWARE CORPORATION | BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLATERAL AGENT, THE | SECURITY AGREEMENT | 025863 | /0535 | |
| Mar 07 2013 | Avaya, Inc | BANK OF NEW YORK MELLON TRUST COMPANY, N A , THE | SECURITY AGREEMENT | 030083 | /0639 | |
| Jan 24 2017 | VPNET TECHNOLOGIES, INC | CITIBANK, N A , AS ADMINISTRATIVE AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 041576 | /0001 | |
| Jan 24 2017 | AVAYA INTEGRATED CABINET SOLUTIONS INC | CITIBANK, N A , AS ADMINISTRATIVE AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 041576 | /0001 | |
| Jan 24 2017 | AVAYA Inc | CITIBANK, N A , AS ADMINISTRATIVE AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 041576 | /0001 | |
| Jan 24 2017 | Octel Communications Corporation | CITIBANK, N A , AS ADMINISTRATIVE AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 041576 | /0001 | |
| Nov 28 2017 | THE BANK OF NEW YORK MELLON TRUST, NA | AVAYA Inc | BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL FRAME 025863 0535 | 044892 | /0001 | |
| Nov 28 2017 | CITIBANK, N A | OCTEL COMMUNICATIONS LLC FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION | BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL FRAME 041576 0001 | 044893 | /0531 | |
| Nov 28 2017 | THE BANK OF NEW YORK MELLON TRUST COMPANY, N A | AVAYA Inc | BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL FRAME 030083 0639 | 045012 | /0666 | |
| Nov 28 2017 | CITIBANK, N A | AVAYA Inc | BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL FRAME 041576 0001 | 044893 | /0531 | |
| Nov 28 2017 | CITIBANK, N A | AVAYA INTEGRATED CABINET SOLUTIONS INC | BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL FRAME 041576 0001 | 044893 | /0531 | |
| Nov 28 2017 | CITIBANK, N A | VPNET TECHNOLOGIES, INC | BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL FRAME 041576 0001 | 044893 | /0531 | |
| Nov 28 2017 | The Bank of New York | AVAYA INC FORMERLY KNOWN AS AVAYA TECHNOLOGY CORP | BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL FRAME 012761 0977 | 044892 | /0822 | |
| Dec 15 2017 | CITICORP USA, INC | SIERRA HOLDINGS CORP | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 045032 | /0213 | |
| Dec 15 2017 | CITICORP USA, INC | Avaya, Inc | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 045032 | /0213 | |
| Dec 15 2017 | ZANG, INC | CITIBANK, N A , AS COLLATERAL AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 045124 | /0026 | |
| Dec 15 2017 | VPNET TECHNOLOGIES, INC | CITIBANK, N A , AS COLLATERAL AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 045124 | /0026 | |
| Dec 15 2017 | OCTEL COMMUNICATIONS LLC | CITIBANK, N A , AS COLLATERAL AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 045124 | /0026 | |
| Dec 15 2017 | AVAYA Inc | CITIBANK, N A , AS COLLATERAL AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 045124 | /0026 | |
| Dec 15 2017 | ZANG, INC | GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 045034 | /0001 | |
| Dec 15 2017 | AVAYA Inc | GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 045034 | /0001 | |
| Dec 15 2017 | OCTEL COMMUNICATIONS LLC | GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 045034 | /0001 | |
| Dec 15 2017 | AVAYA INTEGRATED CABINET SOLUTIONS LLC | GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 045034 | /0001 | |
| Dec 15 2017 | CITICORP USA, INC | OCTEL COMMUNICATIONS LLC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 045032 | /0213 | |
| Dec 15 2017 | CITICORP USA, INC | Avaya Technology, LLC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 045032 | /0213 | |
| Dec 15 2017 | VPNET TECHNOLOGIES, INC | GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 045034 | /0001 | |
| Dec 15 2017 | CITICORP USA, INC | VPNET TECHNOLOGIES, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 045032 | /0213 | |
| Dec 15 2017 | AVAYA INTEGRATED CABINET SOLUTIONS LLC | CITIBANK, N A , AS COLLATERAL AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 045124 | /0026 | |
| Apr 03 2023 | CITIBANK, N A , AS COLLATERAL AGENT | AVAYA HOLDINGS CORP | RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124 FRAME 0026 | 063457 | /0001 | |
| Apr 03 2023 | CITIBANK, N A , AS COLLATERAL AGENT | AVAYA Inc | RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124 FRAME 0026 | 063457 | /0001 | |
| Apr 03 2023 | CITIBANK, N A , AS COLLATERAL AGENT | AVAYA MANAGEMENT L P | RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124 FRAME 0026 | 063457 | /0001 | |
| Apr 03 2023 | CITIBANK, N A , AS COLLATERAL AGENT | AVAYA INTEGRATED CABINET SOLUTIONS LLC | RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124 FRAME 0026 | 063457 | /0001 | |
| May 01 2023 | GOLDMAN SACHS BANK USA , AS COLLATERAL AGENT | AVAYA MANAGEMENT L P | RELEASE OF SECURITY INTEREST IN PATENTS REEL FRAME 045034 0001 | 063779 | /0622 | |
| May 01 2023 | GOLDMAN SACHS BANK USA , AS COLLATERAL AGENT | INTELLISIST, INC | RELEASE OF SECURITY INTEREST IN PATENTS REEL FRAME 045034 0001 | 063779 | /0622 | |
| May 01 2023 | GOLDMAN SACHS BANK USA , AS COLLATERAL AGENT | AVAYA Inc | RELEASE OF SECURITY INTEREST IN PATENTS REEL FRAME 045034 0001 | 063779 | /0622 | |
| May 01 2023 | GOLDMAN SACHS BANK USA , AS COLLATERAL AGENT | AVAYA INTEGRATED CABINET SOLUTIONS LLC | RELEASE OF SECURITY INTEREST IN PATENTS REEL FRAME 045034 0001 | 063779 | /0622 | |
| May 01 2023 | GOLDMAN SACHS BANK USA , AS COLLATERAL AGENT | OCTEL COMMUNICATIONS LLC | RELEASE OF SECURITY INTEREST IN PATENTS REEL FRAME 045034 0001 | 063779 | /0622 | |
| May 01 2023 | GOLDMAN SACHS BANK USA , AS COLLATERAL AGENT | VPNET TECHNOLOGIES, INC | RELEASE OF SECURITY INTEREST IN PATENTS REEL FRAME 045034 0001 | 063779 | /0622 | |
| May 01 2023 | GOLDMAN SACHS BANK USA , AS COLLATERAL AGENT | ZANG, INC FORMER NAME OF AVAYA CLOUD INC | RELEASE OF SECURITY INTEREST IN PATENTS REEL FRAME 045034 0001 | 063779 | /0622 | |
| May 01 2023 | GOLDMAN SACHS BANK USA , AS COLLATERAL AGENT | HYPERQUALITY, INC | RELEASE OF SECURITY INTEREST IN PATENTS REEL FRAME 045034 0001 | 063779 | /0622 | |
| May 01 2023 | GOLDMAN SACHS BANK USA , AS COLLATERAL AGENT | HYPERQUALITY II, LLC | RELEASE OF SECURITY INTEREST IN PATENTS REEL FRAME 045034 0001 | 063779 | /0622 | |
| May 01 2023 | GOLDMAN SACHS BANK USA , AS COLLATERAL AGENT | CAAS TECHNOLOGIES, LLC | RELEASE OF SECURITY INTEREST IN PATENTS REEL FRAME 045034 0001 | 063779 | /0622 |
| Date | Maintenance Fee Events |
| Apr 29 2004 | ASPN: Payor Number Assigned. |
| Aug 10 2007 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
| Sep 10 2007 | R2551: Refund - Payment of Maintenance Fee, 4th Yr, Small Entity. |
| Sep 10 2007 | STOL: Pat Hldr no Longer Claims Small Ent Stat |
| May 06 2010 | ASPN: Payor Number Assigned. |
| May 06 2010 | RMPN: Payer Number De-assigned. |
| Aug 03 2011 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
| Aug 19 2015 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
| Date | Maintenance Schedule |
| Mar 02 2007 | 4 years fee payment window open |
| Sep 02 2007 | 6 months grace period start (w surcharge) |
| Mar 02 2008 | patent expiry (for year 4) |
| Mar 02 2010 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Mar 02 2011 | 8 years fee payment window open |
| Sep 02 2011 | 6 months grace period start (w surcharge) |
| Mar 02 2012 | patent expiry (for year 8) |
| Mar 02 2014 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Mar 02 2015 | 12 years fee payment window open |
| Sep 02 2015 | 6 months grace period start (w surcharge) |
| Mar 02 2016 | patent expiry (for year 12) |
| Mar 02 2018 | 2 years to revive unintentionally abandoned end. (for year 12) |