Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.


  1. Advanced Patent Search
Publication numberUS20060015628 A1
Publication typeApplication
Application numberUS 11/155,301
Publication dateJan 19, 2006
Filing dateJun 16, 2005
Priority dateFeb 26, 1996
Also published asUS5870550, US6647422, US7386880, US20010011304, US20040133637, US20060015627, US20060047833, US20060047834
Publication number11155301, 155301, US 2006/0015628 A1, US 2006/015628 A1, US 20060015628 A1, US 20060015628A1, US 2006015628 A1, US 2006015628A1, US-A1-20060015628, US-A1-2006015628, US2006/0015628A1, US2006/015628A1, US20060015628 A1, US20060015628A1, US2006015628 A1, US2006015628A1
InventorsRalph Wesinger, Christopher Coley
Original AssigneeWesinger Ralph E Jr, Coley Christopher D
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Multi-homed web server
US 20060015628 A1
A multi-homed Web server is disclosed. The Web server may be embodied within a single physical machine that is configured to host a plurality of virtual hosts, where each of said virtual hosts appears as a distinct host to users of the Internet. The single physical machine may further include a corresponding configuration sub-file associated with each of the virtual hosts. Each of the configuration sub-files is linked to a master configuration file.
Previous page
Next page
1. A multi-homed Web server comprising:
a plurality of virtual hosts operable within a single physical machine, each of said virtual hosts appearing as a distinct host to users of the Internet;
each of said plurality of virtual hosts having a corresponding configuration sub-file, each of said configuration sub-files being linked to a master configuration file.
2. The multi-homed Web server of claim 1, wherein said master configuration file comprises a defaults file for providing extensibility to the Web server.
3. The multi-homed Web server of claim 2, wherein the defaults file is compiled as part of the Web server to define the functionality of the Web server.
4. The multi-homed Web server of claim 1, wherein said configuration files may be used to enable or disable different functions for each host.
5. The multi-homed Web server of claim 1, wherein each of said plurality of virtual hosts further comprises a corresponding log file.
6. The multi-homed Web server of claim 5, wherein information regarding incoming access requests for each of said plurality of virtual hosts are stored in said corresponding log file.
7. A multi-homed Web server comprising:
virtual host means operable within a single physical machine, the virtual host means appearing as a distinct host to users of the Internet;
configuration sub-file means operable with said virtual host means; and
master configuration means linked to said configuration sub-file means.
8. The multi-homed Web server of claim 7, wherein said master configuration file means further comprises a defaults file means for providing extensibility to the Web server.
9. The multi-homed Web server of claim 8, wherein the defaults file is compiled as part of the Web server to define the functionality of the Web server.
10. The multi-homed Web server of claim 7, wherein said configuration sub-file means further comprise means for enabling or disabling different functions for each host.
11. The multi-homed Web server of claim 7, wherein each of said plurality of virtual hosts further comprises a corresponding log file means.
12. The multi-homed Web server of claim 11, further comprising means for storing information regarding incoming access requests.
13. A multi-homed Web server comprising:
a single physical machine configured to host a plurality of virtual hosts, each of said virtual hosts appearing as a distinct host to users of the Internet;
the single physical machine further comprising a corresponding configuration sub-file associated with each of said plurality of virtual hosts; and
wherein each of said configuration sub-files is linked to a master configuration file.
14. The multi-homed Web server of claim 13, wherein said master configuration file comprises a defaults file for providing extensibility to the Web server.
15. The multi-homed Web server of claim 14, wherein the defaults file is compiled as part of the Web server to define the functionality of the Web server.
16. The multi-homed Web server of claim 13, wherein said configuration files may be used to enable or disable different functions for each host.
17. The multi-homed Web server of claim 13, wherein each of said plurality of virtual hosts further comprises a corresponding log file.
18. The multi-homed Web server of claim 17, wherein information regarding incoming access requests for each of said plurality of virtual hosts are stored in said corresponding log file.
  • [0001]
    This application is a continuation of co-pending U.S. patent application Ser. No. 09/189,697, filed Nov. 10, 1998, which is a divisional of U.S. patent application Ser. No. 08/607,068, filed Feb. 2, 1996, now issued as U.S. Pat. No. 5,870,550.
  • [0002]
    1. Field of the Invention
  • [0003]
    The present invention relates to Web servers, i.e., server software for delivering content through the World Wide Web.
  • [0004]
    2. State of the Art
  • [0005]
    The Internet, and in particular the content-rich World Wide Web (“the Web”), have experienced and continue to experience explosive growth. The Web is an Internet service that organizes information using hypermedia. Each document can contain embedded reference to images, audio, or other documents. A user browses for information by following references. Web documents are specified in HyperText Markup Language (HTML), a computer language used to specify the contents and format of a hypermedia document (e.g., a homepage). HyperText Transfer Protocol (HTTP) is the protocol used to access a Web document.
  • [0006]
    Web servers offer Web services to Web clients, namely Web browsers. Primarily, Web servers retrieve Web documents and send them to a Web browser, which displays Web documents and provides for user interaction with those documents. Unlike Web browsers, of which there are many, the number of commercially available Web server packages, although growing, remains small. Currently, popular Web servers include those available from Netscape Communications, National Center for Supercomputing Applications (NCSA), and CERN.
  • [0007]
    Ideally, a Web server should be able to respond to and expeditiously service every connection request it receives, regardless of the volume of requests. The job of getting the request to the server and the reply back to the requester falls to the telecommunications infrastructure. In reality, however, because of machine limitations, there is a limit to the number of requests the server can serve within a given period of time without slowing down the machine to an extent that, from the viewpoint of the users, is perceptible, irritating, or simply intolerable. Web servers have typically followed one of two extreme approaches, either “rationing service” by denying further requests once some limiting number of requests are already pending, or attempting to service all requests received and hence slowing the machine to a crawl during extremely busy periods.
  • [0008]
    Webs servers, most of which are written for UNIX, often run under INETD (“eye-net-D”), an Internet services daemon in UNIX. (A daemon is a UNIX process that remains memory resident and causes specified actions to be taken upon the occurrence of specified events.) Typically, if more than sixty connection requests occur within a minute, INETD will shut down service for a period of time, usually five minutes, during which service remains entirely unavailable. Such interruptions are clearly undesirable, both on the part of the client-requester and the content provider. In the case of other Web servers, when the server is brought up, some fixed number of copies of the server, e.g. 50, are started. Up to 50 simultaneous connections may therefore be handled. A request for a 51st connection, however, will be denied, even if many or all of the 50 existing connections are temporarily idle.
  • [0009]
    Other considerations further complicate the picture of what is desired from a Web server, including considerations such as cost, perception and the very dynamic nature of the Web and Web content. Typically, only large organizations, or smaller organizations having considerable technical expertise, have their own Web servers. Establishing and running a Web server can entail a significant and ongoing investment in time and money. The alternative is for a person or organization to pay an Internet Service Provider (ISP) to house its content on the Web and make it available through the ISP's Web server. Of course, most organizations (and people) would like to be perceived as not lacking in either money or expertise. In cyberspace, therefore, an important factor in how an organization is perceived is its Web address. A Web address of commands, in a manner of speaking, immediate attention and respect, whereas a Web address of does not, at least to the same extent.
  • [0010]
    For a person or organization to have the best of both worlds, i.e., house its content on someone else's server but have it appear to be their own, the server must provide the capability of multi-homing. A multi-homed server behaves as multiple servers in one, responding to requests to multiple addresses, e.g.,,, etc. Some existing servers are multi-homed. However, the multi-homing capabilities of existing servers are quite limited. For example, although different customers may have different needs and desire different levels of service, in existing multi-homed servers, as regards a particular physical machine, the core functionality offered by the server (whether extensive or more limited) is necessarily the same for each customer.
  • [0011]
    An entirely different question concerns the extensibility of Web servers. Because the Web is continually in flux, a Web server must provide a mechanism that allows for extensions to be added to the Web server, or face obsolescence. Presently, the commonly accepted mechanism for extending the capabilities of existing Web servers is one called the Common Gateway Interface (CGI). The CGI specification has emerged as a standard way to extend the services and capabilities of a Web server having a defined core functionality. CGI “scripts” are used for this purpose. CGI provides an Application Program Interface, supported by CGI-capable Web servers, to which programmers can write to extend the functionality of the server. CGI scripts, however, although they may be compiled, are typically interpreted, meaning that they run at least ten times slower, typically, than compiled binary code. As the complexity of the Web, and hence the amount of time spent by a Web server running CGI scripts, increases, the Web server unavoidably suffers a significant performance hit.
  • [0012]
    What is needed, then, is a Web server that overcomes the foregoing difficulties.
  • [0013]
    The present invention, generally speaking, provides a Web server having a multi-homed, modular framework. The modular framework allows extensions to the Web server to be easily compiled into the Web server, allowing the extensions to run natively as part of the server instead of incurring the overhead typical of CGI scripts, for example. The multi-homing capabilities of the Web server provide the appearance to Web users of multiple distinct and independent servers, allowing a small company or individual to create the same kind of Web presence enjoyed by larger companies. In effect, multiple virtual servers run on the same physical machine. The Web server as a whole is easily extensible to allow additional capabilities to be provided natively within the Web server itself. Furthermore, each virtual server is independently configurable in order to turn different capabilities on or off or to modify operation of the virtual server. The Web server is also provided with enhanced security features, built-in animation capability, and other features that afford maximum flexibility and versatility.
  • [0014]
    The present invention may be further understood from the following description in conjunction with the appended drawing. In the drawing:
  • [0015]
    FIG. 1 is a block diagram of one embodiment of the Web server of the present invention;
  • [0016]
    FIG. 2 is a block diagram illustrating the manner in which the present Web server handles connection requests;
  • [0017]
    FIG. 3 is an example of a database-like data structure that allows extensions to the Web server to be easily added so as to run natively as part of the Web server;
  • [0018]
    FIG. 4 is an example of a portion of the master configuration file of FIG. 1;
  • [0019]
    FIG. 5 is an example of a conventional Web server log entry;
  • [0020]
    FIG. 6 is an example of a Web server log entry in accordance with one aspect of the present invention; and
  • [0021]
    FIG. 7 is a block diagram illustrating in greater detail the structure of the present Web server.
  • [0022]
    Referring now to FIG. 1, an overview of the present Web server will be provided. The Web server is a software package that runs on a physical machine 100, e.g., a super-minicomputer such as a SunServer machine available from Sun Microsystems of Menlo Park, Calif., or on any of a wide variety of suitable UNIX platforms.
  • [0023]
    Conventionally, a Web server is provided with some fixed feature set. To provide additional capabilities, CGI scripts are used. Furthermore, the logical view of the Web server on the Web is the same as the physical view of the underlying hardware. That is, a single physical machine running a conventional Web server appears on the Web as a single logical machine.
  • [0024]
    The present Web server, on the other hand, although it runs on a single physical machine 100, appears on the Web as multiple virtual hosts VH1 through VHn. Each virtual host has a separate configuration sub-file (sub-database) C1, C2, etc., that may be derived from a master configuration file, or database, 110. A defaults file 111 is used to provide plug-in extensibility of the Web server. The defaults file is compiled as part of the Web server and expresses at the program level what the program is to do to provide various kinds of functionality. The configuration sub-files, on the other hand, are text files that may be used to enable or disable different functions for each virtual host.
  • [0025]
    Each virtual host also has its own separate log file L1, L2, etc. This feature allows for users of different hosts on the same machine to have access to up-to-the minute log information without allowing access to logs of other pages—a very useful feature for ISPs, for example. Each virtual host is capable of servicing many simultaneous connections. The number of allowable simultaneous connections is configurable and may be limited to a predetermined number, or may be limited not by number but only by the load currently experienced by the physical machine. The number of maximum allowable connections or the maximum allowable machine load may be specified in the configuration file.
  • [0026]
    As described in greater detail in connection with FIG. 5, each configuration file C1, C2, etc., may have an access rules database 113, including a Allow portion 115, a Deny portion 117, or both. Using the access rules database 113, the Web server is able to perform many of the functions of a conventional firewall, thereby enhancing network security.
  • [0027]
    The Web server is self-daemoning, meaning that it is not subject to the limitations ordinarily imposed by the usual Internet daemon, INETD. Referring to FIG. 2, when the Web server is brought up, it first reads in the master configuration file and then becomes a daemon and waits for connection requests. When a connection request is received, the Web server “forks a copy” of itself, using the forking capabilities of UNIX, to create a virtual host VHn to handle that connection request. When a parent process is forked to create a child process, the child process runs off the same base code as the parent process but using its own set of variables. In particular, the child process will typically use its own sub-database from within the master configuration database to determine the configuration of that particular virtual host. Child processes are created “on demand” as connection requests are received and complete running as service of those connection requests is completed.
  • [0028]
    As described in greater detail hereinafter, animation capabilities, instead of being an add-on feature provided through a CGI script, are built into the server itself. Hence, in FIG. 2, when a request is received on a connection to process an animation file 201, the child process VHn belonging to that connection is able to process the animation file directly.
  • [0029]
    Animation is one example of a recent enhancement now supported by some Web servers, although typically through CGI and not directly. Numerous and varied other enhancements are sure to follow. Hence, the present Web server, although it provides a default feature set, allows for that default feature set to be readily expanded.
  • [0030]
    The default feature set is defined in the defaults file 111, an example of which is shown in FIG. 3. The defaults file is, in effect, a database that matches different types of requests with modules available for handling those requests. The database is a table having, in the illustrated embodiment, four columns. In the first column is the file extension received as part of the request. Examples of file extensions are “ani” (animation), “cgi,” “html,” “shtml” (server-parsed HTML), etc. In the second column is a type identifier used internally by the Web server, e.g., TY.sub.—ANIMATION, TY.sub.—CGI, etc. In the third column is type information returned to the Web browser, e.g., “text/html,” “image/gif,” etc. In some instances, this type is not clearly defined in advance but depends on the module called to process the request. The type returned to the browser may therefore be NULL. Finally, in the fourth column is the module to be called to process the request, e.g., ProcessANI (an animation player), ProcessCGI, etc.
  • [0031]
    The defaults table of FIG. 3 serves as the foundation of a modular framework that allows extensions to the Web server to be easily added so as to run natively as part of the Web server. In one embodiment, extensions are added by modifying the source code file containing the defaults table, to add a new row to the table, for example, or to modify an existing row. A new module having new capabilities might be substituted for an existing module, for example. The defaults file is then recompiled and linked to the Web server. Preferably, a software development kit is provided with the Web server to facilitate this process.
  • [0032]
    Hence, a mechanism is established that allows modules to be added without the need to rebuild the entire Web server. In accordance with this mechanism, adding an additional server feature involves the following steps:
      • 1. Edit the defaults file (the list of processes) and add an entry for the specific file extension. Add the procedure name to be used for processing this new type. Add an “#include” file defining the procedure at the beginning of the defaults table.
      • 2. Write the procedure. The procedural call to the process will pass two parameters: a File Descriptor to send output to; and a file Name of the document/file to process. The procedure should be written accordingly.
      • 3. Compile the procedure, link it into the Web server, and test.
  • [0036]
    The modular framework just described governs the capabilities of the overall Web server. All customers may not want to pay for use of a high-performance Web server having a comprehensive feature set. The multi-homing capabilities of the present Web server, however, allows the same code to be configured differently for each of multiple virtual hosts, thereby catering to the preferences (and budgets) of different classes of customers. The effect is the same as offering a range of different Web server products of different capabilities, but with the distinct advantage that only a single code package need be produced and maintained.
  • [0037]
    Referring again to FIG. 1, apart from the defaults database, each virtual host has its own configuration sub-file C1, C2, etc. Within the configuration sub-file of each virtual host is a text-file database, not compiled, that is similar in concept to the database of FIG. 3. However, the process to be called for a particular type of request may vary, virtual host to virtual host, from the default process specified in the defaults database. On a virtual host that is configured to have a more limited feature set, for example, CGI scripts may not be allowed. Therefore, the process specified for CGI, instead of ProcessCGI, might be NULL. Similarly with other capabilities. The differences between the configuration database and the defaults database, instead of limiting the capabilities of the virtual host, may actually increase the capabilities of the virtual host. For example, for HTML requests, instead of the usual SendFile process, the process ProcSHTML may be specified. This configuration would allow all HTML files to include other files, cause execution of other programs, etc., resulting in a dynamic document rather than a static document.
  • [0038]
    Furthermore, the Web server may be a “client application” of a license server, described in U.S. patent application Ser. No. 08/607,081 AUTOMATED SYSTEM FOR MANAGEMENT OF LICENSED SOFTWARE now U.S. Pat. No. 5,790,664, filed on even date herewith, incorporated herein by reference. Using the system described in the foregoing application, features of the Web server may be enabled or disabled on a feature-by-feature and virtual host-by-virtual host basis.
  • [0039]
    An example of a portion of a master configuration file is shown in FIG. 4. Within the master configuration file database, different portions of the file form sub-databases for different virtual hosts. Each sub-database may specify a root directory for that particular virtual host.
  • [0040]
    Also as part of the configuration file of each virtual host, an access rules database may be provided governing access to the virtual host, i.e., which connections will be allowed and which connections will be denied. Many of the features more commonly included in a firewall may therefore be included in the Web server itself. The syntax of the access rules database is such as to allow great flexibility in specifying not only what machines are or are not to be allowed access but also when such access is allowed to occur. The access rules database may have an Allow portion, a Deny portion or both. If the access rules database has an Allow portion, only connections from machines matching the Allow rules will be allowed, regardless of whether there is also a Deny portion. If there is a Deny portion but no Allow portion, then connections from machines matching the Deny rules will be denied and all other connections will be allowed. Machines may be specified by name or by IP address, and may include “wildcards,” address masks, etc., for example:, *, 192.168.0.*,, and so on.
  • [0041]
    Time restrictions may be included in either the Allow rules or the Deny rules. For example, access may be allowed from 1 pm to 12 pm; alternatively, access may be denied from 12 pm to 1 am. Also, rules may be given identifiers, such as RULE1, RULE2, etc., and repeated elsewhere within the configuration sub-file of the virtual host.
  • [0042]
    All access rules must be satisfied in order to gain access to a virtual host. Depending on the virtual host, however, further levels of access scrutiny may be specified within the configuration sub-file. Each successive level of access scrutiny includes all previous levels. The first level of access scrutiny is that all rules must be satisfied, as previously described. The second level of access scrutiny is that the accessing machine must have a DNS (Domain Name Services) entry. Having a DNS entry lends at least some level of legitimacy to the accessing machine. The third level of access scrutiny is that the accessing machine must in addition have a reverse DNS entry. The fourth and most stringent level of access scrutiny is that the forward DNS entry and the reverse DNS entry must match.
  • [0043]
    If access is granted and a connection is opened, when the connection is later closed, a log entry is made recording information about that access. One important feature of the present Web server is that log entries identify the particular virtual host that was accessed. Another important feature is that log entries identify the “referrer,” i.e., the source of any link that may have been followed to get to the Web site that was accessed. The owner of a Web site may advertise that site through various different channels. In order to determine what works and what does not, in terms of generating hits on a Web site, one must know how someone came to access that Web site.
  • [0044]
    Referring to FIG. 5, conventional log entries are typically of a format similar to the one shown. The IP address or name 501 of the accessing machine is recorded, followed by the UserName 503, if any, entered during the course of the access, the date and time 505, the connection request 507 as it was received, an error code ERC (509) specifying any error that may have occurred, and a count 511 of the number of bytes transferred. As shown in FIG. 6, the present Web server logs in addition the identity of the virtual host (651) and the referrer (653). Log reports may be generated from this information, listing, for example, the top referrers generating hits to a Web site, etc. Log reports may be generated on a per-host basis or may be generated for the physical machine, i.e., all virtual hosts together.
  • [0045]
    Referring now to FIG. 7, the logical structure of the present Web server is shown in greater detail.
  • [0046]
    The main execution thread of the Web server is controlled by a daemon. In FIG. 7, the daemon includes elements 701, 703 and 705. Although the daemon mode of operation is the default mode, the same code can also be run interactively under the conventional INETD daemon. Hence, when the Web server is first brought up, command-line processing is performed in block 701 to determine the mode of operation (daemon or interactive), which configuration file to read, etc. For purposes of the present discussion, the daemon mode of operation, which is the default, will be assumed.
  • [0047]
    Immediately thereafter, the daemon changes user in block 703 so as to become an unprivileged user. This step of becoming an unprivileged user is a security measure that avoids various known security hazards encountered, for example, when CGI scripts or other programs are allowed to run.
  • [0048]
    Only after the daemon has read the specified configuration file and become an unprivileged user does the daemon actually become a daemon. By daemonizing after the configuration file (e.g., the master configuration file) has been read in, the configuration file in effect becomes “hard coded” into the program such that the program no longer has read it in. The daemon then waits to receive a connection request.
  • [0049]
    When a connection request is received, the daemon forks a copy of itself to handle the connection request. The daemon then uses a piece of code referred to herein as an INET Wrapper 710 to check on the local side of the connection and the remote side of the connection to determine, in accordance with the appropriate Allow and Deny databases, whether the connection is to be allowed.
  • [0050]
    First the address and name (if possible) are obtained of the virtual machine for which a connection is requested. Once the local host has been identified by name or at least by IP address, the master configuration database is scanned to see if a corresponding sub-database exists for that local host. If so, the sub-database is set as the configuration database of the local host so that the master configuration database need no longer be referred to. If no corresponding sub-database is found, then by default the master configuration database is used as the configuration database. There may be any number of virtual machines, all independently configurable and all running on the same physical machine. The determination of which virtual host the daemon child process is to become is made in block 705, under the heading of “multi-homing.”
  • [0051]
    Once the daemon child process has determined which host it is, the INET Wrapper is used to do checking on the remote host, i.e., the host requesting the connection. Recalling the different levels of access scrutiny described previously, first, the configuration database is consulted to determine the level of access scrutiny that will be applied. (The default level of access scrutiny is that no DNS entry is required.) Then, the address and name (if possible) are obtained of the machine requested the connection, and the appropriate level of access scrutiny is applied as determined from the configuration database.
  • [0052]
    If the remote host satisfies the required level of access scrutiny insofar as DNS entries are concerned, the INET Wrapper gets the Allow and Deny databases for the virtual host. First the Allow database is checked, and if there is an Allow database but the remote host is not found in it, the connection is denied. Then the Deny database is checked. If the remote host is found in the Deny database, then the connection is denied. All other rules must also be satisfied, regarding time of access, etc. If all the rules are satisfied, then the connection is allowed.
  • [0053]
    Once the connection has been allowed, the daemon invokes HTTP server code 720 that operates in large part in a similar manner as conventional Web server. The HTTP server code 720 processes commands by examining the filename extension associated with the command in block 721 and calling appropriate routines such as routines 723-726 to process those commands. When processing is completed, the connection is closed, if it has not already been closed implicitly.
  • [0054]
    Several features of the HTTP server code should be noted. The server includes code for handling both client and server proxies and redirects, all as part of the Web server. The server mode is determined in accordance with the configuration file of the virtual host handling the request. The configuration file may specify Client Proxy mode for the virtual host, in which case the virtual host proxies requests directed to the outside world, e.g., Web sites other than the present Web site. The configuration file may specify Server Proxy mode for the virtual host, in which case the virtual host proxies requests to access a different virtual host. The configuration file may specify Redirect mode, in which case the request is redirected to a different specified server, either a different virtual host on the same physical machine or a different physical machine altogether.
  • [0055]
    The animation player 726 of the present Web server also differs in significant respects from conventional animation players. Fundamentally, to the knowledge of the inventors, no other Web server incorporates an animation player as part of the native Web server code. By incorporating the animation player into the Web server itself, instead of adding the animation capabilities through the use of a CGI script, for example, animations may be handled much more efficiently. Furthermore, unlike conventional animation players, which typically just send a sequence of graphics, the present animation player provides full-fledge programming capability, including the ability to send one graphic at a specified time and then a next graphic at a next specified time. When a line is reached in the animation file that calls for a graphic to be displayed at a certain time, if that time has already passed, then that line is ignored by the animation player and the graphic is not sent. Instead the animation player tries to display the next graphic at the next specified time. In this manner, regardless of the speed of the connection, the playing time of the animation is always the same. On a slow connection, the user will see fewer frames, and on a fast connection the user will see more frames. The length of the animation will be the same. Also, labels may be included in the animation, and commands may be used to go to a specified label, or go to the beginning of the animation.
  • [0056]
    It will be appreciated by those of ordinary skill in the art that the invention can be embodied in other specific forms without departing from the spirit or essential character thereof. The foregoing description is therefore considered in all respects to be illustrative and not restrictive. The scope of the invention is indicated by the appended claims, and all changes which come within the meaning and range of equivalents thereof are intended to be embraced therein.
Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US4201889 *Mar 17, 1978May 6, 1980International Telephone And TelegraphDistributed control digital switching system
US4310727 *Feb 4, 1980Jan 12, 1982Bell Telephone Laboratories, IncorporatedMethod of processing special service telephone calls
US4565903 *Aug 3, 1983Jan 21, 1986At&T Bell LaboratoriesTelephone interexchange carrier selection
US4570217 *Mar 28, 1983Feb 11, 1986Allen Bruce SMan machine interface
US4665500 *Apr 11, 1984May 12, 1987Texas Instruments IncorporatedMultiply and divide unit for a high speed processor
US4730312 *Feb 21, 1986Mar 8, 1988San/Bar CorporationVoice, data or both over one telephone line in a T-1 carrier system
US4736364 *Mar 12, 1986Apr 5, 1988American Telephone And Telegraph Company, At&T Bell LaboratoriesSwitching system control arrangements
US4748658 *Jul 16, 1986May 31, 1988Bell Communications Research, Inc.Architecture for allocating resources in a telecommunications network
US4823338 *Aug 3, 1987Apr 18, 1989American Telephone And Telegraph CompanyVirtual local area network
US4896319 *Mar 31, 1988Jan 23, 1990American Telephone And Telegraph Company, At&T Bell LaboratoriesIdentification and authentication of end user systems for packet communications network services
US4914619 *Oct 19, 1987Apr 3, 1990International Business Machines CorporationApparatus and method for interconnecting an application of a transparent services access facility to remote source
US4916690 *May 6, 1988Apr 10, 1990Alcatel N.V.Division multiplex packet switching circuit using a circular shift register
US4924616 *Mar 24, 1989May 15, 1990Bell Ross APortable firearm rest
US4985889 *Feb 2, 1989Jan 15, 1991Sprint International Communications CorporationData packet switching
US4991204 *Nov 9, 1989Feb 5, 1991Nippon Telegraph And Telephone CorporationAdaptive routing control method
US4993014 *May 30, 1989Feb 12, 1991At&T Bell LaboratoriesDynamic shared facility system for private networks
US5003584 *Apr 16, 1990Mar 26, 1991At&T Bell LaboratoriesMethod and apparatus for the billing of value-added communication calls
US5016162 *Mar 30, 1988May 14, 1991Data General Corp.Contention revolution in a digital computer system
US5018191 *Oct 23, 1989May 21, 1991At&T Bell LaboratoriesSpecial service call routing
US5084867 *Sep 19, 1990Jan 28, 1992Fujitsu LimitedRouting method and routing system for switching system having a plurality of paths
US5086461 *Jan 23, 1990Feb 4, 1992Network Access CorporationApparatus and method for providing existing 1ESS and 1AESS telephone switching equipment with the capability of using the SS7 protocol
US5089954 *Aug 8, 1988Feb 18, 1992Bell Communications Research, Inc.Method for handling conversational transactions in a distributed processing environment
US5091903 *Aug 9, 1990Feb 25, 1992Alcatel N.V.Switching network and switching-network module for an atm system
US5101404 *Aug 21, 1989Mar 31, 1992Hitachi, Ltd.Signalling apparatus for use in an ATM switching system
US5115431 *Sep 28, 1990May 19, 1992Stratacom, Inc.Method and apparatus for packet communications signaling
US5185743 *Feb 7, 1991Feb 9, 1993Fujitsu LimitedSignaling cell switching system
US5193110 *Oct 9, 1990Mar 9, 1993Boston Technology, IncorporatedIntegrated services platform for telephone communication system
US5208811 *Nov 1, 1990May 4, 1993Hitachi, Ltd.Interconnection system and method for heterogeneous networks
US5214646 *Nov 13, 1991May 25, 1993Amnon YacobySystem and method for interconnecting local area networks
US5278889 *Jul 29, 1992Jan 11, 1994At&T Bell LaboratoriesVideo telephony dialing
US5282244 *Jun 24, 1991Jan 25, 1994At&T Bell LaboratoriesVirtual signaling network method
US5285441 *Mar 17, 1992Feb 8, 1994At&T Bell LaboratoriesErrorless line protection switching in asynchronous transer mode (ATM) communications systems
US5289472 *Feb 5, 1992Feb 22, 1994At&T Bell LaboratoriesMethod for the tranmission of message associated user-to-user information
US5291479 *Jul 16, 1991Mar 1, 1994Digital Technics, Inc.Modular user programmable telecommunications system with distributed processing
US5291492 *Dec 18, 1991Mar 1, 1994Unifi Communications CorporationExternally controlled call processing system
US5301270 *Dec 18, 1989Apr 5, 1994Anderson ConsultingComputer-assisted software engineering system for cooperative processing environments
US5311509 *Feb 6, 1992May 10, 1994International Business Machines CorporationConfigurable gigabits switch adapter
US5317562 *May 7, 1993May 31, 1994Stratacom, Inc.Method and apparatus for routing cell messages using delay
US5384771 *Aug 27, 1993Jan 24, 1995At&T Corp.Multimedia call configuration system
US5384840 *Oct 9, 1992Jan 24, 1995At&T Corp.Telecommunications system SS7 signaling interface with signal transfer capability
US5392402 *Jun 29, 1993Feb 21, 1995Bell Communications Research, Inc.Broadband intelligent telecommunications network and method employing a resource system to support network services
US5394393 *Aug 18, 1992Feb 28, 1995Thomson-CsfMethod for the routing of a packet of data in a digital transmission network
US5394402 *Jun 10, 1994Feb 28, 1995Ascom Timeplex Trading AgHub for segmented virtual local area network with shared media access
US5400339 *Mar 17, 1993Mar 21, 1995Fujitsu LimitedBidirectional communication apparatus for reducing transmitted data
US5412654 *Jan 10, 1994May 2, 1995International Business Machines CorporationHighly dynamic destination-sequenced destination vector routing for mobile computers
US5418783 *Dec 17, 1992May 23, 1995Mitsubishi Denki Kabushiki KaishaCommon channel signal extraction/insertion device
US5420857 *Feb 8, 1994May 30, 1995Sprint International Communications Corp.Connection establishment in a flat distributed packet switch architecture
US5420858 *May 5, 1993May 30, 1995Synoptics Communications, Inc.Method and apparatus for communications from a non-ATM communication medium to an ATM communication medium
US5420916 *Feb 22, 1993May 30, 1995Nec CorporationSignaling network having common signaling node for protocol conversion
US5483527 *Dec 21, 1994Jan 9, 1996At&T Corp.Terminal adapter for interfacing an ATM network with a STM network
US5485455 *Jan 28, 1994Jan 16, 1996Cabletron Systems, Inc.Network having secure fast packet switching and guaranteed quality of service
US5490251 *Aug 9, 1991Feb 6, 1996First Data Resources Inc.Method and apparatus for transmitting data over a signalling channel in a digital telecommunications network
US5491694 *Oct 5, 1994Feb 13, 1996Cabletron Systems, Inc.System and method for allocating a shared resource among competing devices
US5495484 *Oct 12, 1993Feb 27, 1996Dsc Communications CorporationDistributed telecommunications switching system
US5499290 *Jan 28, 1993Mar 12, 1996Bellsouth CorporationAIN non-call associated signalling for service nodes and service control points in a telephone system
US5502726 *Jan 31, 1992Mar 26, 1996Nellcor IncorporatedSerial layered medical network
US5504742 *Oct 20, 1993Apr 2, 1996Fujitsu LimitedBroadband ISDN remote multiplexer
US5506844 *May 20, 1994Apr 9, 1996Compression Labs, Inc.Method for configuring a statistical multiplexer to dynamically allocate communication channel bandwidth
US5509010 *Jun 25, 1993Apr 16, 1996At&T Corp.Communications signaling protocols
US5509123 *Mar 22, 1994Apr 16, 1996Cabletron Systems, Inc.Distributed autonomous object architectures for network layer routing
US5513178 *Jan 31, 1994Apr 30, 1996Fujitsu LimitedCell multiplexing apparatus in ATM network
US5592477 *Oct 5, 1995Jan 7, 1997Bell Atlantic Network Services, Inc.Video and TELCO network control functionality
US5598536 *Aug 9, 1994Jan 28, 1997Shiva CorporationApparatus and method for providing remote users with the same unique IP address upon each network access
US5600640 *Aug 25, 1993Feb 4, 1997Siemens AktiengesellschaftCall processing system for controlling connections in a communications system
US5600643 *Sep 23, 1993Feb 4, 1997Bell Communications Research, Inc.Broadband intelligent telecommunications network and method providing enhanced capabilities for customer premises equipment
US5606669 *May 23, 1995Feb 25, 1997International Business Machines CorporationSystem for managing topology of a network in spanning tree data structure by maintaining link table and parent table in each network node
US5608447 *May 27, 1994Mar 4, 1997Bell AtlanticFull service network
US5617540 *Jul 31, 1995Apr 1, 1997At&TSystem for binding host name of servers and address of available server in cache within client and for clearing cache prior to client establishes connection
US5619716 *Jun 6, 1995Apr 8, 1997Hitachi, Ltd.Information processing system having a configuration management system for managing the software of the information processing system
US5621728 *Mar 28, 1995Apr 15, 1997Bell Atlantic Network Services, Inc.Level 1 gateway controlling broadband communications for video dial tone networks
US5623601 *Nov 21, 1994Apr 22, 1997Milkway Networks CorporationApparatus and method for providing a secure gateway for communication and data exchanges between networks
US5623605 *Aug 29, 1994Apr 22, 1997Lucent Technologies Inc.Methods and systems for interprocess communication and inter-network data transfer
US5625670 *May 18, 1995Apr 29, 1997Ntp IncorporatedElectronic mail system with RF communications to mobile processors
US5713075 *Feb 15, 1996Jan 27, 1998Amsc Subsidiary CorporationNetwork engineering/systems engineering system for mobile satellite communication system
US5717747 *May 31, 1996Feb 10, 1998Lucent Technologies Inc.Arrangement for facilitating plug-and-play call features
US5721908 *Jun 7, 1995Feb 24, 1998International Business Machines CorporationComputer network for WWW server data access over internet
US5729545 *Jan 17, 1996Mar 17, 1998Lucent Technolgies Inc.Control of video dialtone connections
US5742604 *Mar 28, 1996Apr 21, 1998Cisco Systems, Inc.Interswitch link mechanism for connecting high-performance network switches
US5862391 *Apr 3, 1996Jan 19, 1999General Electric CompanyPower management control system
US5870550 *Feb 26, 1996Feb 9, 1999Network Engineering SoftwareWeb server employing multi-homed, moldular framework
US5878115 *May 8, 1996Mar 2, 1999Ericsson, Inc.Method and apparatus for providing different terminating call treatments based on service area
US5878347 *Jun 3, 1996Mar 2, 1999Ericsson, Inc.Routing a data signal to a mobile station within a telecommunications network
US5890064 *Mar 13, 1996Mar 30, 1999Telefonaktiebolaget L M Ericsson (Publ)Mobile telecommunications network having integrated wireless office system
US5892900 *Aug 30, 1996Apr 6, 1999Intertrust Technologies Corp.Systems and methods for secure transaction management and electronic rights protection
US6011790 *Jun 7, 1996Jan 4, 2000Bell Mobility Cellular Inc.Wireless terminal data network communication
US6016318 *Jul 14, 1997Jan 18, 2000Nec CorporationVirtual private network system over public mobile data network and virtual LAN
US6018658 *Jan 16, 1996Jan 25, 2000Alcatel EspacePersonal communications via low-orbiting moving and geostationary satellites
US6035105 *Jan 2, 1996Mar 7, 2000Cisco Technology, Inc.Multiple VLAN architecture system
US6044264 *Oct 31, 1995Mar 28, 2000Nokia Telecommunications OyMethod for activating intelligent network services in a mobile communication system, and a mobile communication system
US6195357 *Sep 24, 1996Feb 27, 2001Intervoice Limited PartnershipInteractive information transaction processing system with universal telephony gateway capabilities
US6366586 *May 20, 1998Apr 2, 2002Sprint Communications Company L.P.Method, system and apparatus for telecommunications control
US6366893 *Nov 5, 1996Apr 2, 2002Nokia Telecommunications OySystem, a method and an apparatus for performing an electric payment transaction in a telecommunication network
US6370126 *May 12, 1995Apr 9, 2002Inmarsat, Ltd.Mobile satellite communications system with local and global network
US6675146 *May 31, 2001Jan 6, 2004Digimarc CorporationAudio steganography
US6985937 *May 11, 2000Jan 10, 2006Ensim CorporationDynamically modifying the resources of a virtual server
US20060015627 *Jun 16, 2005Jan 19, 2006Graphon CorporationMulti-homed Web server
US20060047833 *Jun 16, 2005Mar 2, 2006Graphon CorporationMulti-homed web server
US20060047834 *Jun 16, 2005Mar 2, 2006Graphon CorporationMulti-homed Web server
Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US8117298Jul 21, 2010Feb 14, 2012Graphon CorporationMulti-homed web server
US8346861Dec 30, 2011Jan 1, 2013Graphon CorporationWeb server with animation player
US8346890Dec 30, 2011Jan 1, 2013Graphon CorporationMulti-homed web server with compiled animation server
US8356073Dec 30, 2011Jan 15, 2013Graphon CorporationMulti-homed web server with animation player and programmable functionality
US8359368Dec 30, 2011Jan 22, 2013Graphon CorporationMulti-homed web server with animation player
US8364754Dec 30, 2011Jan 29, 2013Graphon CorporationMulti-homed web server with compiled animation server and programmable functionality
US8370453Dec 30, 2011Feb 5, 2013Graphon CorporationModular multi-homed web server with compiled animation server
US8370476Dec 30, 2011Feb 5, 2013Graphon CorporationModular multi-homed web server with animation player
US20060047834 *Jun 16, 2005Mar 2, 2006Graphon CorporationMulti-homed Web server
U.S. Classification709/229
International ClassificationH04L29/06, G06F17/30, H04L29/12, G06F21/00, G06F1/00, G06F15/16
Cooperative ClassificationH04L69/164, H04L67/02, H04L69/16, H04L61/2514, H04L63/0281, H04L61/256, G06F21/42, H04L63/18, H04L29/12386, H04L61/30, H04L29/12367, H04L29/12009, H04L29/12066, G06F17/3089, H04L29/06, H04L63/02, H04L63/0807, H04L29/12783, H04L61/2521, H04L29/1249, H04L63/0227, H04L61/1511, H04L29/12594, H04L63/0263, H04L61/35
European ClassificationH04L29/06, H04L63/02B6, H04L61/25A8, H04L29/06J, H04L29/12A4A1B, H04L63/08A, H04L61/25A1B, H04L63/02D, H04L29/12A2A1, H04L29/12A6, G06F21/42, H04L29/12A4A2, H04L61/30, H04L63/02B, H04L61/25A2, H04L61/15A1, H04L29/12A4A8, H04L29/06J9, H04L63/18, H04L61/35, G06F17/30W7, H04L29/12A, H04L29/08N1, H04L29/12A5