|Publication number||USRE43051 E1|
|Application number||US 11/858,091|
|Publication date||Dec 27, 2011|
|Priority date||Mar 15, 2000|
|Also published as||US6948003|
|Publication number||11858091, 858091, US RE43051 E1, US RE43051E1, US-E1-RE43051, USRE43051 E1, USRE43051E1|
|Inventors||Peter Newman, Pawan Goyal|
|Original Assignee||Digital Asset Enterprises, L.L.C.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (150), Non-Patent Citations (84), Referenced by (5), Classifications (12), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This patent application is a reissue application for U.S. Pat. No. 6,948,003, issued from U.S. patent application Ser. No. 09/526,980, filed on Mar. 15, 2000.
This application is related to U.S. patent Ser. No. 09/452,286, entitled “Providing Quality of Service Guarantees to Virtual Hosts”, by Pawan Goyal et al., filed Nov. 30, 1999, and commonly assigned with the present application. The subject matter of related application U.S. patent Ser. No. 09/452,286 is incorporated by reference herein in its entirety.
1. Field of Invention
the present invention relates generally to providing private networking services, e.g., Intranet services, remotely, and more particularly, to allowing a service provider to locate and manage private network servers at the service provider's location, while connecting the servers to a customer's premises such that they appear to be local and private to the customer.
2. Background of the Invention
Networked computer resources are growing more popular as the benefits of sharing computing resources becomes evident. One of the fastest-growing segments of the Internet is the private network market. A private network is an interconnected group of computing resources accessible only by the network members. Security protocols are used to ensure that only authorized users have access to the network's resources, even where the network operates on the public network infrastructure and protocols. A private network, often belonging to a corporation, may be used to store web pages and other shared information. This information is maintained in a private space, generally screened off from external sources such as the Internet by a firewall which blocks unauthorized access. Such private networks are often referred to as intranets, local area networks (LAN) or wide area networks (WAN).
In a typical LAN implementation, a single location contains a group of individual user computers, as well as one or more dedicated host computers executing server programs to maintain the network's shared information. The private LAN is screened off from the Internet by a firewall, though users may access the Internet if needed. Network traffic intended for the network is allowed through the firewall only if authorized. The resources within the LAN all may communicate using private addresses. It is not necessary to use registered IP addresses for each resource because the system is screened off from the global Internet.
This model may be extended to multiple location sites. Computer networks that span relatively large geographical distances are typically referred to as WANs. In a private WAN, individual sites must be connected in a secure manner. A secure connection between WAN sites may be accomplished using a virtual private network. A virtual private network utilizes ordinary Internet protocols and may also use public communications mediums to connect; however, privacy is ensured through features such as tunneling (data encapsulation) or the use of leased lines. A leased line is a permanent connection between two points that is always active. Resources on a WAN may communicate using only private addresses because the network is screened off from the global Internet.
Private networks contain common elements. Each generally contains a dedicated local server to maintain the shared private network data, and a communications system for providing data communication services between machines on the private network. Communication takes place using a private address space. Because the address spaces for individual private networks need only be locally unique, the address spaces among several different private networks may overlap because the networks are isolated from each other. More specifically, in private intranets, two unrelated intranets at different companies may use the same local addresses for user computers. No conflict arises since the networks are not connected.
Data communications services and servers are not easy to configure, manage, and maintain. Thus, there is an incentive for the service providers that offer access to communications facilities to provide such private network services and servers as well, thereby relieving corporations from the burden of providing these services directly. Some examples of service providers are: Internet Service Providers (ISP), Application Service Providers, Network Service Providers, and Competitive Local Exchange Carriers (CLEC).
It is not economically feasible for a service provider to remotely manage servers located on a customer's premises, and support many different customers in this fashion. Rather a service provider would prefer to offer private network services to multiple customers while keeping all of the server host computers within a location of the service provider for ease of management. Accordingly, service providers typically dedicate a physical host computer as each individual customer's server, and maintain each host computer in the centralized facility. However, this means the service provider will have to own and maintain potentially large numbers of physical host computers, at least one for each customer's server or private network However, many customers will neither require nor be amenable to paying for the use of an entire host computer. Generally, only a fraction of the processing power, storage, and other resources of a host computer will be required to meet the needs of an individual customer.
Alternatively, a service provider may utilize one physical host computer to provide commercial host services to multiple customers. Using Transmission Control Protocol (TCP) and other transport protocols, a server application executing on a single physical host can be programmed to process requests made to multiple network addresses. Such functionality is known as virtual hosting.
In virtual hosting, each customer is assigned a network address (or domain name), and is provided with resources on a single, physical host computer, effectively sharing the host with other customers. A client computer requests data from a specific customer's host by targeting communication requests to the appropriate network address (or domain name). The virtual host server can service requests to multiple network addresses or domain names. Thus, the functionality of numerous hosts is provided by a single physical host computer, servicing requests made to a plurality of network addresses and domain names by multiple customers.
However, virtual hosting it is commonly performed today does not provide many of beneficial features of private networks. Service providers will have to be able to provide certain features of private networks before customers will be willing to outsource services related to the operation and maintenance of their private network. First, customers will want to ensure that their private data is inaccessible to other customers sharing the same host computers. For instance, if a service provider provides email outsourcing for both Company A and Company B on the same computer, Company A will want to ensure that the directories in which its email is stored are not accessible to Company B, and vice versa.
Additionally, customers will want to ensure that their services are not compromised due to problems originating with another customer. If a service provider uses a single host computer to provide server resources for both Company A and Company B, steps must be taken to ensure that overuse of the resources by Company A does not impact Company B's service. Additionally, faults, crashes, or similar problems caused by one customer must not compromise the service provided to another customer. Such performance degradation issues must be contained by the service provider to impact only the customer responsible for the problem, and not to impact any other customers.
Finally, companies A and B will want their servers to have IP addresses that belong to their own private address spaces. Using addresses from each company's own private address space offers more security because private IP addresses are not reachable over the public Internet. The use of private IP addresses guards against private servers becoming accessible from the public Internet by accidental misconfiguration of equipment. Also, public IP addresses are a limited resource; there is insufficient address space for private networks to consume addresses from the public address space. Furthermore, if a company connects a number of servers or corporate locations together they will wish to establish a virtual private network. To run the routing protocols required for communications within a virtual private network requires a coherent addressing scheme. Such a virtual private network is easier to manage from a private address space.
However, the use of private address schemes creates difficulties for the service provider. The service provider may now have several virtual servers assigned to the same IP address, because companies A and B may have overlapping address spaces, as is typical in private networks. This address overlap can cause the communication network to fail. Typically, one of the virtual servers would become unreachable due to this address overlap error.
Thus in order to satisfy customers' needs, a service provider desiring to provide private network services must be able to guarantee four different kinds of isolation. Functional isolation separates the data and functionality of each customer. Fault isolation protects one customer from the faults created by another customer. Performance isolation allows each customer to receive a performance commitment independent of the behavior of other customers. Address isolation allows each customer to choose the virtual server IP address that it wants to be associated with, independent of other customers.
Virtual hosting currently cannot provide these beneficial features of ordinary private servers. This is due to the inability of a virtual host to allocate appropriate amounts of computer resources of the physical host computer to servicing client requests made to specific virtual hosts, and hence to specific customers. A private virtual server, by contrast, is able to provide the functional, fault, and performance isolation that an ordinary virtual server cannot. A method for creating such a private virtual server is disclosed in the related application identified above, U.S. patent Ser. No. 09/452,286, entitled “Providing Quality of Service Guarantees to Virtual Hosts.”
However, a method and system is still needed to allow customers to use their own private address spaces to communicate with a remotely-located private virtual server maintained by a service provider, where the private virtual server addresses may overlap.
The present invention allows providers of virtual servers to properly differentiate and route transmissions using private addresses on a common host server. The term “private virtual server” as used herein is a virtual server that supports a private address space wherein the private address spaces of different private virtual servers may overlap.
Customers exchange privately-addressed transmissions with a service provider using tunnels to traverse the local or regional network connecting the customer with the service provider. The service provider receives the transmissions at a gateway into the service provider's data center. The service provider then routes the transmission to the private virtual server belonging to the customer that sent the transmission. The service provider also routes privately-addressed transmissions back to individual customers using tunnels. In this way, the service provider is able to implement a separate routing context on behalf of each individual customer.
The present invention allows for flexibility in designing a private virtual server that suits an individual customer's needs. For example, an individual customer may have multiple physical sites all utilizing the same private virtual server. Optionally, an individual customer may be assigned more than one private virtual server, for instance, if different divisions of an organization each wish to maintain their own private servers while making all the data available to the organization at large.
In one embodiment, the present invention comprises a multiplexing/demultiplexing mechanism capable of routing signals to and from one or more private virtual servers located on a physical host computer. Each private virtual server is associated with only one private network. The multiplexing/demultiplexing mechanism receives a privately addressed transmission and routes it to the private virtual server with which it is associated. The privately addressed transmission may then be processed within the private virtual server in the same manner as if the server was actually a physical server resident within a LAN. The multiplexing/demultiplexing mechanism also receives an outgoing transmission from a private virtual server and routes it back to the private network associated with it. Incoming and outgoing transmissions are addressed using a tunneling scheme. Tunneling allows privately-addressed transmissions to be transported over a network that uses global addresses and allows customers to address their private virtual server using a non-unique private address. As a result, all transmissions to and from a customer are sent only to the customer's respective private virtual server.
In another embodiment, the present invention includes more than one physical host computer. Each physical host computer contains one or more private virtual servers. Privately-addressed incoming transmissions are sent to the service provider's data center. The transmissions are placed on tunnels to traverse the local or regional network connecting the customer with the service provider. A tunnel switching mechanism is used to forward transmissions received at the service provider's data center to the proper physical host computer.
In another embodiment, the present invention is a method for locating and managing private network services in a data center location remote from private network users. The method comprises receiving a transmission addressed using a private address of a recipient, and routing the transmission to a private virtual server. The correct private virtual server is determined from the address of either the sender or the recipient of the transmission.
The foregoing merely summarizes aspects of the invention. The present invention is more completely described with respect to the following drawings and detailed description.
Reference will now be made in detail to several embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Wherever practicable, the same reference numbers will be used throughout the drawings to refer to the same or like parts. The figures depict preferred embodiments of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein.
As used herein, the terms “customer”, “user”, and “private network user” refer to individuals or groups of individuals accessing the same private virtual server. Typically, a private virtual server “user” is a group of individuals with a shared association. For example, “user” may collectively refer to the employees of a company, or to certain employees within a division of a company. One company (a “customer”) may have several different users, each corresponding to a different group within the company. Additionally, a “user” may also refer to a single individual.
In the present invention, customers send and receive data using a network. In one embodiment, the protocol used within each customer's network will be IP (Internet Protocol). The IP addressing format will also be assumed herein for purposes of illustration. However, it will be evident to one of skill in the art that a different network protocol could be used instead of IP within a customer's private network, for example, Open Systems Interconnection (OSI), Internetwork Packet Exchange (IPX), System Network Architecture (SNA), and Asynchronous Transfer Mode (ATM).
Data from customers 112 and 114 may optionally be aggregated 130 before being sent out over a local or regional network 140. Aggregation 130 is not required, but generally is done to concentrate data traffic for more efficient transmission over a network. For example, a customer site may aggregate the multiple data streams coming from various different users (clients) within the site before transmitting data onto a public network.
Aggregation 130 may also take place between customers and non-customers. This may occur when data transmission sites are located physically close together, to consolidate traffic flow onto the local or regional network 140. In another example, aggregation is also common in digital subscriber line (DSL) systems. A digital subscriber line access multiplexer (DSLAM) concentrates data traffic from multiple DSL loops onto the backbone network before connection to the rest of the local or regional network 140. Data directed to different destinations will be separated and individually routed within the local or regional network 140.
The local or regional network 140 connects a customer with a private virtual server system 100. The local or regional network 140 may be comprised of different types of interconnected networks. System 100 is capable of functioning with a wide variety of different local or regional networks 140, as will be evident to one of skill in the art.
Traffic from each individual customer 112 and 114 is aggregated 130 and transported across the local or regional network 140 until it reaches a service provider gateway 152. The service provider gateway 152 provides the connection into the service provider data center 150. The service provider gateway 152 direct traffic from each customer to the private virtual servers it owns and prevents traffic from reaching private virtual servers a customer does not own.
The service provider gateway 152 connects to a physical server machine 160. The physical server machine 160 may be any kind of computer adapted to support private virtual servers. It is to be understood that a service provider data center 150 will typically contain more than one physical server machine 160.
Located on the physical server machine 160 is a group of private virtual servers 162. In one embodiment, each private virtual server 162 is capable of implementing quality of service guarantees to individual customers. A service provider may implement different quality of service guarantees by allocating different percentages of the physical server machine 160 to servicing each of the private virtual servers 162. Thus the private virtual servers 162 may each consume a different percentage of the resources of physical server machine 160. This resource allocation may be dynamically changed by the service provider as required.
In one embodiment, the IP network address of each private virtual server 162 corresponds to a private address from the private address space of the respective customer assigned to the private virtual server. A private address is any locally-assigned address, which does not have to be unique within the global Internet. Conversely, a global address is a registered IP address that is unique within the public network system of communications. Generally, connecting a private network to a public network requires network address translation, which maps global addresses onto private addresses at the public/private network boundary. Private addresses are not routable in the public network, therefore transmissions cannot be sent to the private virtual servers 162 across the public network 120 using only their private addresses.
The network addresses for the private virtual servers are chosen to correspond to each customer's private address space. The private address spaces of customers 112 and 114 may overlap. Therefore, the network addresses for these customers' assigned virtual private servers may not be unique. It is possible for private virtual servers 162 to all be assigned the same network address.
Thus the use of private addresses for the private virtual servers creates two different problems: such private addresses cannot be used to transmit data directly across a public network, and there may be address overlap among the private virtual servers.
A solution to the problem of transporting privately-addressed transmissions is shown in
Customers 210 and 220 use tunnels to allow privately-addressed data transmissions to traverse the local or regional network 240. Customer 210 has a single tunnel 212 from customer 210's site to the service provider gateway 252. Similarly, customer 220 has a single tunnel 222 from customer 220's site to the service provider gateway 252. A tunnel is created by encapsulating a data transmission within a second type of addressing protocol. Transmissions, which use addresses that are unique only within a narrow scope, may thus be transported across a second network within a wider address scope. In this way, private IP addresses that are only unique within a private IP network are encapsulated for transport across the global public Internet. The origination of the tunnel, on the customer's side, must occur before traffic from multiple customers is aggregated. The numbers of customers and private virtual servers shown in
System 200 demonstrates how a customer can be communicatively coupled to a private virtual server system using privately-addressed transmissions. However, once privately-addressed transmissions are routed across a public network, the problem of potential address overlap among the destination private virtual servers still remains.
In another embodiment, the tunnels 312, 322, and 332 could be replaced with dedicated leased lines. A leased line is a permanent connection between two points set up by a telecommunications common carrier. A leased line is not part of the global public network, and therefore may carry privately-addressed traffic.
The physical server machine 360 contains three private virtual servers 362, as well as a multiplexing/demultiplexing mechanism 350. Incoming tunnels 312, 322, and 332 communicatively couple to the multiplexing/demultiplexing mechanism 350. The private virtual servers 362 may have overlapping IP addresses. A set of internal pointers 314 is used to direct traffic from the multiplexing/demultiplexing mechanism 350 to the correct private virtual server 362, thereby communicatively coupling the multiplexing/demultiplexing mechanism 350 to the private virtual servers 362.
The multiplexing/demultiplexing mechanism 350 performs the functions of separating incoming communication streams back into their original constituent streams, and merging multiple separate communication streams onto a single physical communications medium. In one embodiment, the multiplexing/demultiplexing mechanism 350 is implemented in the network interface card of the physical server machine 360. The multiplexing/demultiplexing mechanism 350 may be implemented in an application specific integrated circuit (ASIC) on the network interface card, or on the software driver.
Incoming tunneled transmissions are sent on a physical medium as packet flows. When the multiplexing/demultiplexing mechanism 350 demultiplexes an incoming set of packet flows, incoming packets are stored in a buffer and one of the fields in the packet header is used to select the incoming packet queue to which the buffer should be linked. An incoming packet queue is a list of pointers wherein each pointer points to a packet buffer. Thus packets arriving with different tunnel identifiers are linked to different incoming packet queues. There is one incoming packet queue per tunnel.
Outgoing transmissions sent by the various private virtual servers are also packet flows. Each private virtual server has its own outgoing packet queue. These packet queues are again implemented as lists of pointers to packet buffers. The scheduler in the network interface card selects which of the non-empty outgoing packet queues it should serve next. The scheduler takes the pointer from the head of the selected queue and transmits the packet from the buffer that is pointed to by the pointer.
The tunnel switching operations of the mutiplexing/demultiplexing mechanism 350 are shown in more detail in
The physical host computer 400 also includes a multiplexing/demultiplexing mechanism 410. Multiplexing/demultiplexing mechanism 410 has an internal pointer 430 directed at each IP stack 422. Multiplexing/demultiplexing mechanism 410 includes a lookup table 412 that includes a list of incoming tunnel identifiers and pointers to their associated IP stacks within the physical host computer 400. Lookup table 412 is created by software residing on the physical host computer 400, which associates each IP stack with a particular customer, and ensures that transmissions sent from a particular customer are only directed to that particular customer's private virtual server.
A data packet 452 enters the multiplexing/demultiplexing mechanism 410 using an incoming tunnel 450. The tunnel 450 is not an individual physical connection, but is a means of encapsulating the packet 452 to permit routing across a public network. Although only one incoming tunnel 450 is shown in
The tunnel identifying information of the incoming packet 452 identifies which customer sent the packet 452. Packet 452's incoming tunnel identifying information is stripped 446, and the tunnel identifying information is presented 444 to the lookup table 412. Lookup table 412 returns 442 an internal pointer 430 for the appropriate IP stack 422. Packet 452 is then routed 440 to the identified IP stack 422 using the internal pointer 430.
An alternative embodiment is to embed the internal pointer 430 in the control data structure that controls the operation of the tunnel. The control data structure is typically located on the network interface card. The network interface card is typically located on the physical server machine 400.
A packet 552 is originally sent from the IP stack 422 of one of the private virtual servers 420. The packet 552 is directed 530 to the multiplexing/demultiplexing mechanism 410. Upon arrival at the multiplexing/demultiplexing mechanism 410, the internal tunnel IP stack identifier is read 540, and this identifier is presented 542 to lookup table 512.
Lookup table 512 returns 544 the associated outgoing tunnel identifying information. The outgoing tunnel identifier is added 546 to packet 552. Packet 552 is then sent out using the appropriate outgoing tunnel 550. The outgoing tunnel 550 is associated with the customer assigned to the private virtual server 420, which originally sent the packet 552. Although only one outgoing tunnel is shown in
An alternative embodiment is for the IP stack 422 of each private virtual server 420 to encapsulate the packet 552 with the proper outgoing tunnel header and tunnel identifier, thereby creating the tunnel 550. In this embodiment, the lookup table 512 is not used. The multiplexer/demultiplexer mechanism 410 merges the encapsulated and identified packet streams together, and sends them out.
A service provider will typically own and manage multiple physical server machines. Additionally, customers may wish to purchase more than one private virtual server, for example, for separate divisions within the same company. A customer may also have multiple physical customer sites using the same private virtual server, wherein each customer site uses a different tunnel to communicate with the service provider. A tunnel switch supports these different configurations in a private virtual server system.
A tunnel switch comprises one or more physical interfaces, with each interface capable of carrying many multiplexed tunnels. A tunnel switch will typically be capable of supporting a number of different physical interface technologies and a number of different types of tunnels for each type of physical interface. A tunnel switch performs two separate services: switching tunnels, and switching packets within a tunnel.
In a switching tunnels service, all packets arriving on one incoming tunnel are forwarded to an outgoing tunnel. This may be implemented without looking into the headers of the packets themselves. The tunnel switch notes which tunnel and physical interface the packet arrived on. Given the identifier of the incoming tunnel and the incoming physical interface, the tunnel switch uses a lookup table to specify the outgoing tunnel and physical interface.
In a switching packets service, incoming tunnels are terminated at the tunnel switch. The packets within each tunnel are extracted and switched individually based upon the incoming physical interface, the incoming tunnel, and information from the header of the packet. A private virtual server system supporting multiple physical servers, multiple private virtual servers per customer, and multiple customer sites per private virtual server will support such a switching packets service in addition to supporting a switching tunnels service.
Each customer site is connected to the system 600 via an external tunnel that traverses the local or regional network 620 and communicatively couples to a tunnel switch 632. Customer site 612 uses external tunnel 622, customer site 614 uses external tunnel 624, and customer site 616 uses external tunnel 626. A tunnel switch 632 operates as the gateway to physical servers 640 and 650, and supports tunnels on multiple physical interfaces. Tunnel switch 632 is communicatively coupled to physical server 640 via a set of tunnels 634. Tunnel switch 632 is communicatively coupled to physical server 650 via a set of tunnels 636. Physical server 640 contains a multiplexing/demultiplexing mechanism 642, which is linked via a set of internal pointers 662 to a set of private virtual servers 660. Physical server 650 contains a multiplexing/demultiplexing mechanism 652, which is linked via a set of internal pointers 682 to a set of private virtual servers 680.
Tunnel switch 700 also includes a set of outgoing physical interfaces 732 carrying a set of outgoing tunnels 730 to a set of physical host computers 720. Physical interface 732A carries tunnels 730A and 730B to physical host computer 720A. Physical interface 732B carries tunnel 730C to physical host computer 720B. Physical interface 732C carries tunnels 730D and 730E to physical host computer 720C. The tunnel switch 700 includes a customer lookup table 800 and a set of customer forwarding tables 900. The features of the customer lookup table and customer forwarding tables will be discussed in more detail before fully explaining the functions of the tunnel switch 700.
The customer lookup table 800 associates external tunnel and physical interface identifiers with a particular customer. Each customer listed in the customer lookup table 800 has an associated customer forwarding table. For example, customer 1's information is contained in customer forwarding table 910, and customer 2's information is contained in customer forwarding table 920. When a customer communicates with a private virtual server, each data transmission will arrive on a particular physical interface using a particular tunnel.
Customer lookup table 800 contains four fields: incoming physical interface, incoming tunnel identifier, service, and customer identifier. Each incoming physical interface and incoming tunnel identifier entry will reference a unique customer identifier. This customer identifier provides an index to the correct customer forwarding table associated with this physical interface/tunnel identifier pair. For example, a transmission arriving on physical interface 712 and incoming tunnel 710B would be indexed to customer 1's customer forwarding table (table 910 from
Each customer forwarding table 910, 920 and 930 contains three fields: destination IP address, outgoing tunnel identifier, and outgoing physical interface. Based upon the destination IP address of a particular transmission, the proper outgoing tunnel and outgoing physical interface is determined. Using customer lookup table 910 as an example, transmissions with a destination IP address of the “main server” for customer I would be placed on outgoing tunnel 730A on physical interface 732A. In the opposite direction, transmissions with a destination IP address of “site 1” for customer 1 would be placed on outgoing tunnel 710E on physical interface 712.
The information in the customer forwarding tables 900 is segregated by customer because the private address spaces of different customers may overlap, and therefore the destination IP addresses on each individual customer forwarding table are not unique within the set of all customer forwarding tables. For example, “main server” of customer 1 and “server” of customer 2 may have the same IP address.
The service field in the customer lookup table 800 identifies whether only a tunnel switching service (TS) is required, or a packet switching service (PS) is required. If only a tunnel switching service is required, the associated customer forwarding table will contain only a single entry specifying the proper outgoing tunnel and outgoing physical interface. For example, customer lookup table 800 indexes transmissions arriving on physical interface 712 and incoming tunnel 710C to customer 2, and identifies these transmissions as requiring only a tunnel switching service Customer lookup table 920 associated with customer 2 directs all traffic to outgoing tunnel 730D on physical interface 732C.
The customer lookup table 800 and customer forwarding tables 900 allow the tunnel switch 700 to support a variety of different private network configurations. For example, customer lookup table 800 shows that customer 1 uses two different incoming tunnels: 710A and 710B. Customer forwarding table 910 shows that customer I also has two different destination IP addresses corresponding to two different private virtual servers: “main server” and “backup server.” Additionally, customer 1 has two different destination IP addresses corresponding to two different customer sites: “site 1” and “site 2.” However, customer forwarding table 920 shows that customer 2 has only one private virtual server (“server”). The example private network configurations referred to herein are merely illustrative. It will be understood by one of skill in the art that many different configurations are possible.
Referring back to
The customer lookup table 800 uses the physical interface and tunnel identifier to return 748 the correct customer forwarding table (910) for use with the packet 718. A group of customer forwarding tables 900 contains a customer forwarding table 910 that is associated with the customer that uses physical interface 712 and tunnel 710B. Packet 718's destination IP address, for example, “main server” is presented 750 to customer forwarding table 910.
From the information contained in customer forwarding table 910, the correct outgoing physical interface and tunnel identifier for packet 718 is identified 754. Referring to
Customers utilizing a private virtual server system may also be accessing the global Internet. In this case, both the private virtual server communications traffic and the Internet communications traffic are sent out on a public network. A method for separating the two traffic streams is required.
In one embodiment, shown in
Within the tunnel switch 1060, traffic addressed to the Internet is segregated out from traffic directed to the customer's private virtual server(s). The Internet traffic is sent out to the Internet 1030 via a public communications channel 1064. Internet responses back to the customer are returned in the same way that they were sent. The tunnel switch 1060 sends private virtual server traffic out on an internal tunnel 1062 to the physical server machine 1070 that holds the customer's private virtual server.
A variety of tunneling protocols may be used to create the tunnels used in the present invention. It is preferable to use a layer 2 tunneling protocol for security purposes. Layer 2 tunnels provide solid circuits that make it difficult to “spoof” a fake source address. Packets using a layer 3 tunneling protocol may be created with a fake IP address, allowing a packet to appear to come from a customer when in fact it was sent by an unauthorized third party. Tunnels using a layer 3 tunneling protocol require encryption so that an intruder cannot decode the information. Encryption is also required to protect against accidentally routing the traffic to an incorrect destination, because the encryption will prevent mis-directed traffic from being decoded. Preference for tunnel type depends upon the service provider's network architecture.
Typical examples of tunnel protocols include Asynchronous Transfer Mode virtual circuits (ATM VCs), frame relay virtual circuits (FR VCs), the Point-to-Point Protocol (PPP) across the Layer 2 Tunneling Protocol (L2TP), and IP security protocol (IPsec). ATM or frame relay virtual circuits may be delivered to a customer using Digital Subscriber Line (DSL) access. However, it will be evident to one of skill in the art that other tunneling protocols may be used to implement the tunnels of the present invention.
The customer site 1110 contains a group of computers 1112A, 1112B, and 1112C. The computers 1112 are representative of the customer's on-site private network. Such a private network could be comprised of more or fewer individual computers, as well as other types of equipment such as storage devices.
Components within a customer's on-site private network communicate using a private IP addressing scheme. A packet 1114 is a privately-addressed transmission sent using the local IP protocol of the customer site 1110. Packet 1114 is sent from customer 1110 to customer 1110's private virtual server. Packet 1114 has a destination address corresponding to a private virtual server of service provider 1150.
The on-site private network of devices 1112 is connected to a customer premise equipment box (CPE) 1120. Packet 114 is routed to CPE 1120. The CPE connects the customer site 1110 to a tunnel 1132, established between the customer site 1110 and the service provider site 1150. The tunnel functions as a bi-directional data pipe, and is typically established when a customer subscribes to a service provider providing a tunneling service. A fixed ATM tunnel is referred to as a permanent virtual circuit. The CPE divides the data of packet 1114 into cells (or packets) of a fixed size designated by the ATM protocol, and encapsulates them with a Virtual Channel Identifier (VCI) used to direct the cells through the data pipe. An ATM cell 1118 is created from the division and encapsulation of packet 1114.
Tunnel 1132 terminates at a tunnel switch 1160 of the service provider 1150. Tunnel switch 1160 is connected via a set of bi-directional ATM tunnels 1172 to a set of physical servers 1170. In another embodiment, two sets of unidirectional tunnels are used to provide a two-way connection between customer site 1110 and service provider 1150.
A set of incoming external tunnels 1132 terminates at the tunnel switch 1160. Tunnel 1132B carries the incoming ATM cell 1118. Referring back to
Customer forwarding table 1232B returns 1218 the identity of the outgoing tunnel required to reach the correct private virtual server destination (1250A) for ATM cell 1118. ATM cell 1118 is then placed 1220 on an internal tunnel 1172 to reach the private virtual server 1250A. Internal tunnel 1172 terminates at a multiplexing/demultiplexing mechanism 1290 of the physical host computer 1170, which contains private virtual server 1250A.
The VCI of ATM cell 1118 is stripped 1252, and the VCI is presented 1254 to lookup table 1260. The rest of the ATM cell 1118, including the original source/destination addresses and payload, is held until the original IP packet 1114 sent by a customer 1112 can be reassembled. The ATM protocol uses relatively small cells compared to other transmission protocols. Therefore multiple ATM cells may be required to reassemble the original pre-ATM-encapsulation packet 1114.
Once the original IP packet 1114 has been reassembled 1262, the location of the IP stack of the destination private virtual server 1250A is retrieved 1256 from lookup table 1260. Packet 1114 is routed 1280 to the IP stack of private virtual server 1250A.
Although the invention has been described in considerable detail with reference to certain embodiments, other embodiments are possible. As will be understood by those of skill in the art, the invention may be embodied in other specific forms without departing from the essential characteristics thereof For example, different protocols may be used to create tunnels. Accordingly, the present invention is intended to embrace all such alternatives, modifications and variations as fall within the spirit and scope of the appended claims and equivalents.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US3377624||Jan 7, 1966||Apr 9, 1968||Ibm||Memory protection system|
|US4177510||Dec 2, 1974||Dec 4, 1979||Compagnie Internationale pour l'Informatique, CII Honeywell Bull||Protection of data in an information multiprocessing system by implementing a concept of rings to represent the different levels of privileges among processes|
|US5189667||Jan 10, 1991||Feb 23, 1993||Kabushiki Kaisha Toshiba||Method and apparatus for controlling call processing based upon load conditions|
|US5212793||Sep 4, 1991||May 18, 1993||International Business Machines Corp.||Generic initiators|
|US5226160||Jul 18, 1989||Jul 6, 1993||Visage||Method of and system for interactive video-audio-computer open architecture operation|
|US5249290||Feb 22, 1991||Sep 28, 1993||At&T Bell Laboratories||Method of and apparatus for operating a client/server computer network|
|US5263147||Mar 1, 1991||Nov 16, 1993||Hughes Training, Inc.||System for providing high security for personal computers and workstations|
|US5325530||Jan 29, 1993||Jun 28, 1994||International Business Machines Corporation||Controller for sequential programming tools executed in a parallel computing environment|
|US5437032||Aug 19, 1994||Jul 25, 1995||International Business Machines Corporation||Task scheduler for a miltiprocessor system|
|US5528753||Jun 30, 1994||Jun 18, 1996||International Business Machines Corporation||System and method for enabling stripped object software monitoring in a computer system|
|US5572680||Aug 20, 1993||Nov 5, 1996||Fujitsu Limited||Method and apparatus for processing and transferring data to processor and/or respective virtual processor corresponding to destination logical processor number|
|US5584023||Dec 27, 1993||Dec 10, 1996||Hsu; Mike S. C.||Computer system including a transparent and secure file transform mechanism|
|US5603020||Aug 24, 1994||Feb 11, 1997||Fujitsu Limited||Method for detecting file names by informing the task of the identification of the directory antecedent to the file|
|US5623492||Mar 24, 1995||Apr 22, 1997||U S West Technologies, Inc.||Methods and systems for managing bandwidth resources in a fast packet switching network|
|US5636371||Jun 7, 1995||Jun 3, 1997||Bull Hn Information Systems Inc.||Virtual network mechanism to access well known port application programs running on a single host system|
|US5640595||Jun 29, 1993||Jun 17, 1997||International Business Machines Corporation||Multimedia resource reservation system with graphical interface for manual input of resource reservation value|
|US5692047||Dec 8, 1995||Nov 25, 1997||Sun Microsystems, Inc.||System and method for executing verifiable programs with facility for using non-verifiable programs from trusted sources|
|US5706097||Sep 13, 1996||Jan 6, 1998||Eastman Kodak Company||Index print with a digital recording medium containing still images, motion sequences, and sound sequences|
|US5706453||Feb 6, 1995||Jan 6, 1998||Cheng; Yang-Leh||Intelligent real-time graphic-object to database linking-actuator for enabling intuitive on-screen changes and control of system configuration|
|US5708774||Jul 23, 1996||Jan 13, 1998||International Business Machines Corporation||Automated testing of software application interfaces, object methods and commands|
|US5719854||Apr 5, 1996||Feb 17, 1998||Lucent Technologies Inc.||Efficiently providing multiple grades of service with protection against overloads in shared resources|
|US5727203||Mar 31, 1995||Mar 10, 1998||Sun Microsystems, Inc.||Methods and apparatus for managing a database in a distributed object operating environment using persistent and transient cache|
|US5748614||Jun 6, 1996||May 5, 1998||Siemens Aktiengesellschaft||Method for scheduling message cells leaving an ATM node|
|US5752003||Jul 14, 1995||May 12, 1998||3 Com Corporation||Architecture for managing traffic in a virtual LAN environment|
|US5761477||Dec 4, 1995||Jun 2, 1998||Microsoft Corporation||Methods for safe and efficient implementations of virtual machines|
|US5764889||Sep 26, 1996||Jun 9, 1998||International Business Machines Corporation||Method and apparatus for creating a security environment for a user task in a client/server system|
|US5781550||Feb 2, 1996||Jul 14, 1998||Digital Equipment Corporation||Transparent and secure network gateway|
|US5799173||May 21, 1997||Aug 25, 1998||International Business Machines Corporation||Dynamic workload balancing|
|US5809527||Dec 23, 1993||Sep 15, 1998||Unisys Corporation||Outboard file cache system|
|US5828893||Aug 21, 1995||Oct 27, 1998||Motorola, Inc.||System and method of communicating between trusted and untrusted computer systems|
|US5838686||Apr 22, 1994||Nov 17, 1998||Thomson Consumer Electronics, Inc.||System for dynamically allocating a scarce resource|
|US5838916||Mar 14, 1997||Nov 17, 1998||Domenikos; Steven D.||Systems and methods for executing application programs from a memory device linked to a server|
|US5842002||May 30, 1997||Nov 24, 1998||Quantum Leap Innovations, Inc.||Computer virus trap|
|US5845129||Mar 22, 1996||Dec 1, 1998||Philips Electronics North America Corporation||Protection domains in a single address space|
|US5850399||Mar 27, 1998||Dec 15, 1998||Ascend Communications, Inc.||Hierarchical packet scheduling method and apparatus|
|US5860004||Jul 3, 1996||Jan 12, 1999||Sun Microsystems, Inc.||Code generator for applications in distributed object systems|
|US5864683||Oct 12, 1994||Jan 26, 1999||Secure Computing Corporartion||System for providing secure internetwork by connecting type enforcing secure computers to external network for limiting access to data based on user and process access rights|
|US5889956||Jul 18, 1996||Mar 30, 1999||Fujitsu Network Communications, Inc.||Hierarchical resource management with maximum allowable allocation boundaries|
|US5889996||Dec 16, 1996||Mar 30, 1999||Novell Inc.||Accelerator for interpretive environments|
|US5892968||Oct 15, 1996||Apr 6, 1999||Hitachi, Ltd.||Multimedia data transferring method|
|US5905730||Mar 27, 1998||May 18, 1999||Ascend Communications, Inc.||High speed packet scheduling method and apparatus|
|US5905859||Jan 9, 1997||May 18, 1999||International Business Machines Corporation||Managed network device security method and apparatus|
|US5913024||Feb 9, 1996||Jun 15, 1999||Secure Computing Corporation||Secure server utilizing separate protocol stacks|
|US5915085||Feb 28, 1997||Jun 22, 1999||International Business Machines Corporation||Multiple resource or security contexts in a multithreaded application|
|US5915095||Aug 8, 1995||Jun 22, 1999||Ncr Corporation||Method and apparatus for balancing processing requests among a plurality of servers based on measurable characteristics off network node and common application|
|US5918018||Feb 9, 1996||Jun 29, 1999||Secure Computing Corporation||System and method for achieving network separation|
|US5920699||Nov 7, 1996||Jul 6, 1999||Hewlett-Packard Company||Broadcast isolation and level 3 network switch|
|US5933603||Jun 10, 1996||Aug 3, 1999||Emc Corporation||Video file server maintaining sliding windows of a video data set in random access memories of stream server computers for immediate video-on-demand service beginning at any specified location|
|US5937159||Mar 28, 1997||Aug 10, 1999||Data General Corporation||Secure computer system|
|US5956481||Feb 6, 1997||Sep 21, 1999||Microsoft Corporation||Method and apparatus for protecting data files on a computer from virus infection|
|US5978373||Jul 11, 1997||Nov 2, 1999||Ag Communication Systems Corporation||Wide area network system providing secure transmission|
|US5982748||Oct 3, 1996||Nov 9, 1999||Nortel Networks Corporation||Method and apparatus for controlling admission of connection requests|
|US5987524||Sep 30, 1997||Nov 16, 1999||Fujitsu Limited||Local area network system and router unit|
|US5991812||Mar 6, 1997||Nov 23, 1999||Controlnet, Inc.||Methods and apparatus for fair queuing over a network|
|US5999963||Nov 7, 1997||Dec 7, 1999||Lucent Technologies, Inc.||Move-to-rear list scheduling|
|US6016318||Jul 14, 1997||Jan 18, 2000||Nec Corporation||Virtual private network system over public mobile data network and virtual LAN|
|US6018527||Aug 13, 1996||Jan 25, 2000||Nortel Networks Corporation||Queue service interval based cell scheduler with hierarchical queuing configurations|
|US6023721||May 14, 1997||Feb 8, 2000||Citrix Systems, Inc.||Method and system for allowing a single-user application executing in a multi-user environment to create objects having both user-global and system global visibility|
|US6038608||Nov 25, 1997||Mar 14, 2000||Nec Corporation||Virtual LAN system|
|US6038609||Apr 2, 1998||Mar 14, 2000||Telefonaktiebolaget Lm Ericsson||Method, communication network and service access interface for communications in an open system interconnection environment|
|US6047325||Aug 24, 1998||Apr 4, 2000||Jain; Lalit||Network device for supporting construction of virtual local area networks on arbitrary local and wide area computer networks|
|US6055617||Aug 29, 1997||Apr 25, 2000||Sequent Computer Systems, Inc.||Virtual address window for accessing physical memory in a computer system|
|US6061349||May 2, 1997||May 9, 2000||Cisco Technology, Inc.||System and method for implementing multiple IP addresses on multiple ports|
|US6065118||Sep 24, 1996||May 16, 2000||Citrix Systems, Inc.||Mobile code isolation cage|
|US6075791||Oct 28, 1997||Jun 13, 2000||Lucent Technologies Inc.||System for guaranteeing data transfer rates and delays in packet networks|
|US6075938||Jun 10, 1998||Jun 13, 2000||The Board Of Trustees Of The Leland Stanford Junior University||Virtual machine monitors for scalable multiprocessors|
|US6078929||Jun 6, 1997||Jun 20, 2000||At&T||Internet file system|
|US6078957||Nov 20, 1998||Jun 20, 2000||Network Alchemy, Inc.||Method and apparatus for a TCP/IP load balancing and failover process in an internet protocol (IP) network clustering system|
|US6086623||Jun 30, 1997||Jul 11, 2000||Sun Microsystems, Inc.||Method and implementation for intercepting and processing system calls in programmed digital computer to emulate retrograde operating system|
|US6092178||Sep 3, 1998||Jul 18, 2000||Sun Microsystems, Inc.||System for responding to a resource request|
|US6094674||Jun 29, 1998||Jul 25, 2000||Hitachi, Ltd.||Information processing system and information processing method and quality of service supplying method for use with the system|
|US6101543||Oct 25, 1996||Aug 8, 2000||Digital Equipment Corporation||Pseudo network adapter for frame capture, encapsulation and encryption|
|US6108701||Jul 20, 1998||Aug 22, 2000||Lucent Technologies, Inc.||Soft switch extension for internet protocol applications|
|US6108759||Sep 17, 1997||Aug 22, 2000||Powerquest Corporation||Manipulation of partitions holding advanced file systems|
|US6122673||Jul 22, 1998||Sep 19, 2000||Fore Systems, Inc.||Port scheduler and method for scheduling service providing guarantees, hierarchical rate limiting with/without overbooking capability|
|US6154776||Mar 20, 1998||Nov 28, 2000||Sun Microsystems, Inc.||Quality of service allocation on a network|
|US6154778||May 19, 1998||Nov 28, 2000||Hewlett-Packard Company||Utility-based multi-category quality-of-service negotiation in distributed systems|
|US6161139||Feb 12, 1999||Dec 12, 2000||Encommerce, Inc.||Administrative roles that govern access to administrative functions|
|US6167520||Jan 29, 1997||Dec 26, 2000||Finjan Software, Inc.||System and method for protecting a client during runtime from hostile downloadables|
|US6172981||Oct 30, 1997||Jan 9, 2001||International Business Machines Corporation||Method and system for distributing network routing functions to local area network stations|
|US6189046||Mar 27, 1997||Feb 13, 2001||Hewlett-Packard Company||Mechanism and method for merging cached location information in a distributed object environment|
|US6192389||Mar 28, 1997||Feb 20, 2001||International Business Machines Corporation||Method and apparatus for transferring file descriptors in a multiprocess, multithreaded client/server system|
|US6192512||Sep 24, 1998||Feb 20, 2001||International Business Machines Corporation||Interpreter with virtualized interface|
|US6230203||Mar 14, 1997||May 8, 2001||Scientific-Atlanta, Inc.||System and method for providing statistics for flexible billing in a cable environment|
|US6240463||Nov 24, 1998||May 29, 2001||Lucent Technologies Inc.||Router placement methods and apparatus for designing IP networks with performance guarantees|
|US6247057||Oct 22, 1998||Jun 12, 2001||Microsoft Corporation||Network server supporting multiple instance of services to operate concurrently by having endpoint mapping subsystem for mapping virtual network names to virtual endpoint IDs|
|US6259699||Dec 30, 1997||Jul 10, 2001||Nexabit Networks, Llc||System architecture for and method of processing packets and/or cells in a common switch|
|US6266678||Dec 31, 1998||Jul 24, 2001||Computer Associates Think, Inc.||System and method for dynamically viewing contents of a data file|
|US6269404||Jan 5, 1999||Jul 31, 2001||3Com Corporation||Virtual network architecture for connectionless LAN backbone|
|US6279039||Apr 3, 1996||Aug 21, 2001||Ncr Corporation||Resource management method and apparatus for maximizing multimedia performance of open systems|
|US6279040||Apr 27, 1999||Aug 21, 2001||Industrial Technology Research Institute||Scalable architecture for media-on demand servers|
|US6282581||Mar 27, 1997||Aug 28, 2001||Hewlett-Packard Company||Mechanism for resource allocation and for dispatching incoming calls in a distributed object environment|
|US6282703||Oct 29, 1998||Aug 28, 2001||International Business Machines Corporation||Statically linking an application process with a wrapper library|
|US6286047||Sep 10, 1998||Sep 4, 2001||Hewlett-Packard Company||Method and system for automatic discovery of network services|
|US6298479||May 29, 1998||Oct 2, 2001||Sun Microsystems, Inc.||Method and system for compiling and linking source files|
|US6314558||Feb 16, 1999||Nov 6, 2001||Compuware Corporation||Byte code instrumentation|
|US6327622||Sep 3, 1998||Dec 4, 2001||Sun Microsystems, Inc.||Load balancing in a network environment|
|US6336138||Aug 25, 1998||Jan 1, 2002||Hewlett-Packard Company||Template-driven approach for generating models on network services|
|US6351775||May 30, 1997||Feb 26, 2002||International Business Machines Corporation||Loading balancing across servers in a computer network|
|US6353616||Dec 28, 1998||Mar 5, 2002||Lucent Technologies Inc.||Adaptive processor schedulor and method for reservation protocol message processing|
|US6363053||Feb 8, 1999||Mar 26, 2002||3Com Corporation||Method and apparatus for measurement-based conformance testing of service level agreements in networks|
|US6370583||Aug 17, 1998||Apr 9, 2002||Compaq Information Technologies Group, L.P.||Method and apparatus for portraying a cluster of computer systems as having a single internet protocol image|
|US6381228||Jan 15, 1999||Apr 30, 2002||Trw Inc.||Onboard control of demand assigned multiple access protocol for satellite ATM networks|
|US6385638||Sep 4, 1997||May 7, 2002||Equator Technologies, Inc.||Processor resource distributor and method|
|US6389448||May 5, 2000||May 14, 2002||Warp Solutions, Inc.||System and method for load balancing|
|US6393484||Apr 12, 1999||May 21, 2002||International Business Machines Corp.||System and method for controlled access to shared-medium public and semi-public internet protocol (IP) networks|
|US6425003||Jan 22, 1999||Jul 23, 2002||Cisco Technology, Inc.||Method and apparatus for DNS resolution|
|US6430622||Sep 22, 1999||Aug 6, 2002||International Business Machines Corporation||Methods, systems and computer program products for automated movement of IP addresses within a cluster|
|US6434631||Oct 15, 1999||Aug 13, 2002||Lucent Technologies Inc.||Method and system for providing computer storage access with quality of service guarantees|
|US6434742||May 10, 1999||Aug 13, 2002||Lucent Technologies Inc.||Symbol for automatically renaming symbols in files during the compiling of the files|
|US6438134||Aug 24, 1998||Aug 20, 2002||Alcatel Canada Inc.||Two-component bandwidth scheduler having application in multi-class digital communications systems|
|US6442164||Jun 3, 1999||Aug 27, 2002||Fujitsu Network Communications, Inc.||Method and system for allocating bandwidth and buffer resources to constant bit rate (CBR) traffic|
|US6457008||Aug 28, 1998||Sep 24, 2002||Oracle Corporation||Pluggable resource scheduling policies|
|US6463459||Jan 22, 1999||Oct 8, 2002||Wall Data Incorporated||System and method for executing commands associated with specific virtual desktop|
|US6470398||Apr 7, 1997||Oct 22, 2002||Compaq Computer Corporation||Method and apparatus for supporting a select () system call and interprocess communication in a fault-tolerant, scalable distributed computer environment|
|US6487578||Sep 29, 1997||Nov 26, 2002||Intel Corporation||Dynamic feedback costing to enable adaptive control of resource utilization|
|US6487663||Oct 19, 1998||Nov 26, 2002||Realnetworks, Inc.||System and method for regulating the transmission of media data|
|US6490670||Apr 24, 1998||Dec 3, 2002||International Business Machines Corporation||Method and apparatus for efficiently allocating objects in object oriented systems|
|US6499137||Nov 20, 1998||Dec 24, 2002||Microsoft Corporation||Reversible load-time dynamic linking|
|US6529950||Jun 17, 1999||Mar 4, 2003||International Business Machines Corporation||Policy-based multivariate application-level QoS negotiation for multimedia services|
|US6529985||Feb 4, 2000||Mar 4, 2003||Ensim Corporation||Selective interception of system calls|
|US6542167||Jan 28, 2000||Apr 1, 2003||Wind River Systems, Inc.||System and method for flexible software linking|
|US6553413||Jun 28, 2000||Apr 22, 2003||Massachusetts Institute Of Technology||Content delivery network using edge-of-network servers for providing content delivery to a set of participating content providers|
|US6560613||Feb 8, 2000||May 6, 2003||Ensim Corporation||Disambiguating file descriptors|
|US6578055||Jun 5, 2000||Jun 10, 2003||International Business Machines Corporation||Methods, system and computer program products for mirrored file access through assuming a privileged user level|
|US6578068||Aug 31, 1999||Jun 10, 2003||Accenture Llp||Load balancer in environment services patterns|
|US6580721||Aug 11, 1998||Jun 17, 2003||Nortel Networks Limited||Routing and rate control in a universal transfer mode network|
|US6625650||Jun 25, 1999||Sep 23, 2003||Intel Corporation||System for multi-layer broadband provisioning in computer networks|
|US6647422||Nov 10, 1998||Nov 11, 2003||Network Engineering Technologies, Inc.||Web server employing multi-homed, modular framework|
|US6658571||Feb 9, 1999||Dec 2, 2003||Secure Computing Corporation||Security framework for dynamically wrapping software applications executing in a computing system|
|US6680922 *||Jul 9, 1999||Jan 20, 2004||Malibu Networks, Inc.||Method for the recognition and operation of virtual private networks (VPNs) over a wireless point to multi-point (PtMP) transmission system|
|US6691312||Mar 17, 2000||Feb 10, 2004||University Of Massachusetts||Multicasting video|
|US6711607||Feb 4, 2000||Mar 23, 2004||Ensim Corporation||Dynamic scheduling of task streams in a multiple-resource system to ensure task stream quality of service|
|US6725456||Nov 29, 1999||Apr 20, 2004||Lucent Technologies Inc.||Methods and apparatus for ensuring quality of service in an operating system|
|US6754716||Feb 11, 2000||Jun 22, 2004||Ensim Corporation||Restricting communication between network devices on a common network|
|US6760775||Mar 6, 2000||Jul 6, 2004||At&T Corp.||System, method and apparatus for network service load and reliability management|
|US6779016||Feb 11, 2000||Aug 17, 2004||Terraspring, Inc.||Extensible computing system|
|US6820117||Oct 18, 1999||Nov 16, 2004||Sun Microsystems, Inc.||Bandwidth management|
|US6976258||Nov 30, 1999||Dec 13, 2005||Ensim Corporation||Providing quality of service guarantees to virtual hosts|
|US6976286||Oct 21, 2002||Dec 20, 2005||Edwin Sanabria||Motorized self-draining utility bucket|
|US6982984 *||Aug 28, 2001||Jan 3, 2006||Redback Networks Inc.||Method and apparatus for virtual private networks|
|US7061899 *||May 1, 2001||Jun 13, 2006||Hewlett-Packard Development Company, L.P.||Method and apparatus for providing network security|
|US7111163 *||Jul 10, 2000||Sep 19, 2006||Alterwan, Inc.||Wide area network using internet with quality of service|
|US7225259 *||Feb 21, 2001||May 29, 2007||Nokia Inc.||Service tunnel over a connectionless network|
|US7318152 *||Dec 9, 2005||Jan 8, 2008||Alterwan, Inc.||Wide area network using internet with high quality of service|
|US7441043 *||Dec 31, 2002||Oct 21, 2008||At&T Corp.||System and method to support networking functions for mobile hosts that access multiple networks|
|US7653074 *||Oct 26, 2005||Jan 26, 2010||Redback Networks Inc.||Method and apparatus for virtual private networks|
|US7672288 *||Mar 28, 2000||Mar 2, 2010||Nokia Networks Oy||Arrangement for secure communication and key distribution in a telecommunication system|
|US20030061338||Jun 25, 1999||Mar 27, 2003||Tony Stelliga||System for multi-layer broadband provisioning in computer networks|
|JP64002145A||Title not available|
|1||"Symbol Table," © 1997, 1998, [Retrieved online Apr. 4, 2003] http://216-239-33-100/search?q=cache:eASXK8qC--AC:www.caldera.com/developers/gabi/1998-04-29/ch4.s..., pp. 1-5.|
|2||"Symbol Table," © 1997, 1998, [Retrieved online Apr. 4, 2003] http://216-239-33-100/search?q=cache:eASXK8qC—-AC:www.caldera.com/developers/gabi/1998-04-29/ch4.s..., pp. 1-5.|
|3||Aho, A. V. and Ullman J. D., "Principles of Complier Design," Reading, MA, 1977, pp. vii-x, 359-362, 519-522.|
|4||Bach, M.J., "The Design of the Unix® Operating System," New Delhi, Prentice-Hall of India, 1989, pp. v-x, 19-37.|
|5||Boehm, B., "Managing Software Productivity and Reuse," IEEE Computer, vol. 32, No. 9, Sep. 1999, 3 pages.|
|6||Campbell, A. T. and S. Keshav, "Quality of Service in Distributed Systems," Computer Communications 21, 1998, pp. 291-293.|
|7||Corbato, F. J. et al., "An Experimental Timesharing System," Proceedings of the American Federation of Information Processing Societies Spring Joint Computer Conference, San Francisco, CA, May 1-3, 1962, pp. 335-344.|
|8||Deutsch, P. and C.A. Grant, "A Flexible Measurement Tool for Software Systems," Information Processing 71 [Proc. of the IFIP Congress], 1971, pp. 320-326.|
|9||Duffield, N. G. et al., "A Flexible Model for Resource Management in Virtual Private Networks," Computer Communication Review Conference, Computer Communication, ACM SIGCOMM'99 Conference, Cambridge, MA, Aug. 30, 1999-Sep. 3, 1999, pp. 95-108.|
|10||Edjlali, G. et al., "History-based Access Control for Mobile Code," Fifth ACM Conference on Computer and Communication Security, Nov. 3-5, 1998, 19 pages.|
|11||Egevang, K. and Francis P., RFC 1631, May 1994 [online], [retrieved Feb. 2, 2000]. retrieved from the Internet: .|
|12||Egevang, K. and Francis P., RFC 1631, May 1994 [online], [retrieved Feb. 2, 2000]. retrieved from the Internet: <URL: http://www.faqs.org/rfcs/rfc1631.html>.|
|13||Egevang, K. and P. Francis, "RFC 1631," May 1994, http://www.faqs.org/rfcs/rfc1631.html, [retrieved online Feb. 2, 2000].|
|14||Erlingsson, U. and Schneider, F. B., "SASI Enforcement of Security Policies: A Retrospective," Proc. New Security Paradigms Workshop, Apr. 2, 1999, pp. 1-17.|
|15||Erlingsson, U. and Schnieder, F. B., "IRM Enforcement of Java Stack Inspection," [online], Feb. 19, 2000, [retrieved on Apr. 2, 2002]. Retrieved from the Internet: http://cs-tr.cs.cornell.edu/Dienst/UI2.0/Show-Page/ncstrl.cornell/TR2000-1786.|
|16||Erlingsson, U. and Schnieder, F. B., "IRM Enforcement of Java Stack Inspection," [online], Feb. 19, 2000, [retrieved on Apr. 2, 2002]. Retrieved from the Internet: http://cs-tr.cs.cornell.edu/Dienst/UI2.0/Show—Page/ncstrl.cornell/TR2000-1786.|
|17||Evans, D. and Twyman, A., "Flexible Policy-Directed Code Safety," Proc. of 1999 IEEE Symposium on Security and Privacy, Oakland, CA, May 9-12, 1999, pp. 1-14.|
|18||Fraser, T. et al., "Hardening COTS Software with Generic Software Wrappers," Proc. of 1999 IEEE Symposium on Security and Privacy, 1999, 15 pages.|
|19||Goldberg, I. et al., "A Secure Environment for Untrusted Helper Applications (Confining the Wily Hacker)," Proc. of the Sixth USENIX UNIX Security Symposium, San Jose, CA, Jul. 1996, 14 pages.|
|20||Goldberg, R. P., "Survey of Virtual Machine Research," IEEE Computer, Jun. 1974, pp. 34-45.|
|21||Goyal, P. et al., "Start-time Fair Queuing: A Scheduling Algorithm for Integrated Services Packet Switching Networks," Proceedings of ACM SIGCOMM'96, San Francisco, CA, Aug. 1996, 14 pages.|
|22||Goyal, P., "Packet Scheudling Algorithms for Integrated Services Networks," PhD Dissertation, Unviersity of Texas, Austin, TX, Aug. 1997.|
|23||Goyal, P., et al., "A Hierarchical CPU Scheduler for Multimedia Operating Systems," Proceedings of the Second Symposium on Operating Systems Design and Implementations (OSDI'96), Seattle, WA, Oct. 1996, 15 pages.|
|24||Goyal, Pawan et al., "Generalized Guaranteed Rate Scheduling Algorithms: A Framework," IEEE/ACM Transactions on Networking, vol. 5, No. 4, Aug. 1997, pp. 561-571.|
|25||Huang, X. W. et al., "The Entrapid Protocol Development Environment," Proceedings of IEEE Infocom'99, Mar. 1999, 9 pages.|
|26||Jánosi, T., "Notes on ‘A Hierarchical CPU Scheduler for Multimedia Operating Systems’ by Pawan Goyal, Xingang Guo and Harrick Vin," [online], [retrieved on May 8, 2000]. Retrieved from the internet: <URL: http://cs.cornell.edu/Info/Courses/Spring-97/CS614/goy.html>.|
|27||Janosi, T., "Notes on ‘A Hierarchical CPU Scheduler for Multimedia Operating Systems’ by Pawan Goyal, Xingang Guo and Harrick Vin," http://cs.cornell.edu/Info/Courses/Spring-97/CS614/goy.html, [retrieved online May 8, 2000].|
|28||Jánosi, T., "Notes on 'A Hierarchical CPU Scheduler for Multimedia Operating Systems' by Pawan Goyal, Xingang Guo and Harrick Vin," [online], [retrieved on May 8, 2000]. Retrieved from the internet: .|
|29||Janosi, T., "Notes on 'A Hierarchical CPU Scheduler for Multimedia Operating Systems' by Pawan Goyal, Xingang Guo and Harrick Vin," http://cs.cornell.edu/Info/Courses/Spring-97/CS614/goy.html, [retrieved online May 8, 2000].|
|30||Jonsson, J., "Exploring the Importance of Preprocessing Operations in Real-Time Multiprocessor Scheduling," Proc. of the IEEE Real-Time Systems Symposium-Work-in-Progress session, San Francisco, CA, Dec. 4, 1997, pp. 31-34.|
|31||Jonsson, J., "Exploring the Importance of Preprocessing Operations in Real-Time Multiprocessor Scheduling," Proc. of the IEEE Real-Time Systems Symposium—Work-in-Progress session, San Francisco, CA, Dec. 4, 1997, pp. 31-34.|
|32||Keshav, S., "An Engineering Approach to Computer Networking: ATM Networks, the Internet, and the Telephone Network," Reading, MA, Addison-Wesley, 1997, pp. vii-xi, 85-115, 209-355, 395-444.|
|33||Laurie, B. and Laurie, P., "Apache the Definitive Guide," Sebastopol, CA, O'Reilly & Associates, Inc., Feb. 1999, pp. v-viii, 43-74.|
|34||Mallory, T and Kullberg, A., RFC 1141, Jan. 1990 [online], [retrieved Feb. 2, 2000]. retrieved from the Internet: .|
|35||Mallory, T and Kullberg, A., RFC 1141, Jan. 1990 [online], [retrieved Feb. 2, 2000]. retrieved from the Internet: <URL: http://www.faqs.org/rfcs/rfc1141.html>.|
|36||Mallory, T. and Kullberg, A., RFC 1141, Jan. 1990, http://www.faqs.org/rfcs/rfc1141.html, [retrieved online Feb. 2, 2000].|
|37||McDougall, R. et al., "Resource Management,", Upper Saddle River, NJ, Prentice Hall, 1999, pp. iii-xix, 135-191.|
|38||Mitra, Debasis et al., "Hierarchical Virtual Partitioning: Algorithms for Virtual Private Networking," Bell Labs Technical Journal, Spring, 1997, http://cm.bell-labs.com/cm/ms/who/mitra/paper/globe.ps.|
|39||Pandey, R. and Hashii, B., "Providing Fine-Grained Access Control for Mobile Programs Through Binary Editing," Technical Report TR98 08, University of California, Davis, CA, 1998, pp. 1-22.|
|40||Pending U.S. Appl. No. 09/452,286, filed Nov. 30, 1999, entitled "Providing Quality of Service Guarantees to Virtual Hosts".|
|41||Pending U.S. Appl. No. 09/498,450, filed Feb. 4, 2000, entitled "Dynamic Scheduling of Task Streams in a Multiple-Resource System to Ensure Task Stream Quality of Service".|
|42||Pending U.S. Appl. No. 09/499,098, filed Feb. 4, 2000, entitled "Selective Interception of System Calls".|
|43||Pending U.S. Appl. No. 09/500,212, filed Feb. 8, 2000, entitled "Disambiguating File Descriptors".|
|44||Pending U.S. Appl. No. 09/502,155, filed Feb. 11, 2000, entitled "Restricting Communication Between Network Devices on a Common Network".|
|45||Pending U.S. Appl. No. 09/503,975, filed Feb. 14, 2000, entitled "Restricting Communication of Selected Processes to a Set of Specific Network Addresses".|
|46||Plummer, D. C., An Ethernet Address Resolution Protocol - or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware, Nov. 1982, http://www.msg.net/kadow/answers/extras/rfc/rfc826.txt [retrieved from the Internet Jan. 17, 2000].|
|47||Plummer, D. C.,An Ethernet Address Resolution Protocol-or-Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware, Nov. 1982, [online], [retrieved on Jan. 17, 2000]. Retrieved from the Internet: .|
|48||Plummer, D. C.,An Ethernet Address Resolution Protocol—or—Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware, Nov. 1982, [online], [retrieved on Jan. 17, 2000]. Retrieved from the Internet: <URL:http://www.msg.net/kadow/answers/extras/rfc/rfc826.txt>.|
|49||Rijsinghani, A., RFC 1624, May 1994, [online], [retrieved Feb. 2, 2000]. retrieved from the internet: .|
|50||Rijsinghani, A., RFC 1624, May 1994, [online], [retrieved Feb. 2, 2000]. retrieved from the internet: <URL: http://www.faqs.org/rfcs/rfc1624.html>.|
|51||Rijsinghani, A., RFC 1624, May 1994, http://www.faqs.org/rfcs/rfc1624.html, [retrieved from the internet Feb. 2, 2000].|
|52||Ritchie, D. M., "The Evolution of the Unix Time-Sharing System," AT&T Bell Laboratories Technical Journal 63, No. 6, Part 2, Oct. 1984, (originally presented 1979), 11 pages.|
|53||Rubini, A., "LINUX Device Drivers," Sebastopol, CA, O'Reilly & Associates, Inc., 1998, pp. v-x, 13-40.|
|54||Rusling, D. A., "Files," http://www.cebaf.gov/~saw/linux/tlk-html/node49.html, [retrieved online Dec. 7, 1999].|
|55||Rusling, D. A., "Files," http://www.cebaf.gov/˜saw/linux/tlk-html/node49.html, [retrieved online Dec. 7, 1999].|
|56||Rusling, D. A., "Identifiers," http://www.ce-baf.gov/~saw/linux/tlk-html/node46.html, [retrieved online Dec. 7, 1999].|
|57||Rusling, D. A., "Identifiers," http://www.ce-baf.gov/˜saw/linux/tlk-html/node46.html, [retrieved online Dec. 7, 1999].|
|58||Rusling, D. A., "Linux Processes," http://www.cebatgov/~saw/linux/tlk-html/node45.html, [retrieved online Dec. 7, 1999].|
|59||Rusling, D. A., "Linux Processes," http://www.cebatgov/˜saw/linux/tlk-html/node45.html, [retrieved online Dec. 7, 1999].|
|60||Rusling, D. A., "Processes," http://www.cebaf.gov/ saw/linux/tlk-html/node44.html> [retrieved online Dec. 7, 1999].|
|61||Rusling, D. A., "Scheduling in Multiprocessor Systems," http://www.cebaf.gov/~saw/linux/tlk-html/node48.html, [retrieved online Dec. 7, 1999].|
|62||Rusling, D. A., "Scheduling in Multiprocessor Systems," http://www.cebaf.gov/˜saw/linux/tlk-html/node48.html, [retrieved online Dec. 7, 1999].|
|63||Rusling, D. A., "Scheduling," http://www.ce-baf.gov/~saw/linux/tlk-html/node47.html, [retrieved online Dec. 7, 1999].|
|64||Rusling, D. A., "Scheduling," http://www.ce-baf.gov/˜saw/linux/tlk-html/node47.html, [retrieved online Dec. 7, 1999].|
|65||Rusling, D. A., Files, [online], [retrieved on Dec. 7, 1999]. Retrieved from the Internet: .|
|66||Rusling, D. A., Files, [online], [retrieved on Dec. 7, 1999]. Retrieved from the Internet: <URL: http://www.cebaf.gov/˜saw/linux/tlk-html/node49.html>.|
|67||Rusling, D. A., Identifiers, [online], [retrieved on Dec. 7, 1999]. Retrieved from the Internet: .|
|68||Rusling, D. A., Identifiers, [online], [retrieved on Dec. 7, 1999]. Retrieved from the Internet: <URL: http://www.cebaf.gov/˜saw/linux/tlk-html/node46.html>.|
|69||Rusling, D. A., Linux Processes, [online], [retrieved on Dec. 7, 1999]. Retrieved from the Internet: .|
|70||Rusling, D. A., Linux Processes, [online], [retrieved on Dec. 7, 1999]. Retrieved from the Internet: <URL: http://www.cebaf.gov/˜saw/linux/tlk-html/node45.html>.|
|71||Rusling, D. A., Processes, [online], [retrieved on Dec. 7, 1999]. Retrieved from the Internet: .|
|72||Rusling, D. A., Processes, [online], [retrieved on Dec. 7, 1999]. Retrieved from the Internet: <URL: http://www.cebaf.gov/˜saw/linux/tlk-html/node44.html>.|
|73||Rusling, D. A., Scheduling in Multiprocessor Systems, [online], [retrieved on Dec. 7, 1999]. Retrieved from the Internet: .|
|74||Rusling, D. A., Scheduling in Multiprocessor Systems, [online], [retrieved on Dec. 7, 1999]. Retrieved from the Internet: <URL: http://www.cebaf.gov/˜saw/linux/tlk-html/node48.html>.|
|75||Rusling, D. A., Scheduling, [online], [retrieved on Dec. 7, 1999]. Retrieved from the Internet: .|
|76||Rusling, D. A., Scheduling, [online], [retrieved on Dec. 7, 1999]. Retrieved from the Internet: <URL: http://www.cebaf.gov/˜saw/linux/tlk-html/node47.html>.|
|77||Saltzer, J., H. and Schroeder, M. D., "The Protection of Information in Computer Systems," [online], 1973, [retrieved on Apr. 2, 2002]. Retrieved from the Internet: http://www.cs.virginia.edu~evans/cs551/saltzer/.|
|78||Saltzer, J., H. and Schroeder, M. D., "The Protection of Information in Computer Systems," [online], 1973, [retrieved on Apr. 2, 2002]. Retrieved from the Internet: http://www.cs.virginia.edu˜evans/cs551/saltzer/.|
|79||Stevens, R. W., "UNIX Network Programming vol. 1 Networking APIs: Sockets and XTI," Upper Saddle River, NJ, Prentice Hall, 1998, pp. v-xiv, 29-53, 85-110, 727-760.|
|80||Symbol Table, [online] copyright 1997, 1998, [Retrieved on Apr. 4, 2003] Retrieved from the internet <URL: http://216-239-33-100/search?q=cache:eASXK8qC--AC:www.caldera.com/developers/gabi/1998-04-29/ch4.s..., pp. 1-5.|
|81||Symbol Table, [online] copyright 1997, 1998, [Retrieved on Apr. 4, 2003] Retrieved from the internet <URL: http://216-239-33-100/search?q=cache:eASXK8qC—-AC:www.caldera.com/developers/gabi/1998-04-29/ch4.s..., pp. 1-5.|
|82||Tanenbaum, A. S. and Woodhull, A. S., "Operating Systems: Design and Implementation," Upper Saddle River, NJ, Prentice Hall, 1997, pp. vii-xiv, 1-46, 401-454.|
|83||U.S. Appl. No. 09/503,975, Goyal.|
|84||Wahbe, R. et al., "Efficient Software-Based Fault Isolation," Proc. of the Symposium on Operating System Principles, 1993, 14 pages.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8619771 *||Sep 30, 2009||Dec 31, 2013||Vmware, Inc.||Private allocated networks over shared communications infrastructure|
|US8924524||Jul 27, 2009||Dec 30, 2014||Vmware, Inc.||Automated network configuration of virtual machines in a virtual lab data environment|
|US20110022694 *||Jan 27, 2011||Vmware, Inc.||Automated Network Configuration of Virtual Machines in a Virtual Lab Environment|
|US20110075664 *||Sep 30, 2009||Mar 31, 2011||Vmware, Inc.||Private Allocated Networks Over Shared Communications Infrastructure|
|US20140029606 *||Jul 30, 2012||Jan 30, 2014||Baruch Sterman||Systems and methods for communicating a stream of data packets via multiple communications channels|
|International Classification||H04L29/08, H04L12/24, G06F15/173, G06F15/16|
|Cooperative Classification||H04L2212/00, H04L67/2814, H04L41/18, H04L41/5064|
|European Classification||H04L29/08N27D, H04L41/50J1, H04L41/18|
|Dec 13, 2010||AS||Assignment|
Owner name: ENSIM CORPORATION, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NEWMAN, PETER;GOYAL, PAWAN;REEL/FRAME:025496/0110
Effective date: 20000606
Owner name: DIGITAL ASSET ENTERPRISES, L.L.C., DELAWARE
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ENSIM CORPORATION;REEL/FRAME:025495/0602
Effective date: 20070607
|Mar 13, 2012||CC||Certificate of correction|
|Feb 25, 2013||FPAY||Fee payment|
Year of fee payment: 8
|Nov 23, 2015||AS||Assignment|
Owner name: CUFER ASSET LTD. L.L.C., DELAWARE
Free format text: MERGER;ASSIGNOR:DIGITAL ASSET ENTERPRISES, L.L.C.;REEL/FRAME:037118/0001
Effective date: 20150812