Abstract:
Disclosed is a method that defines a standard configuration useful for scaling services independently. This method makes efficient use of the Network, Server and Storage layers of a computing infrastructure in such a way that services can be clustered. These clustered services allow for redundancy in hardware and software and take full advantage of the hardware and software to increase customer performance and throughput. By making appropriate use of inexpensive servers, network attached storage, virtual local area networks, content switching and service clustering, Internet services can be scaled incrementally as customer demand grows. This method is efficient and relatively affordable.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS  
         [0001]    Not Applicable  
         STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT  
         [0002]    Not Applicable  
         REFERENCE TO SEQUENCE LISTING, A TABLE, OR A COMPUTER PROGRAM LISTING COMPACT DISK APPENDIX  
         [0003]    Not Applicable  
         BACKGROUND OF THE INVENTION  
         [0004]    1. Technical Field of Invention  
           [0005]    Clustered Services Architecture describes a configuration of computing devices that allow for the delivery of reliable services to Internet users. This configuration deals with the problems of service scalability, performance, redundancy and fault tolerance. This configuration works with computing technologies such as virtual local area networking, network attached storage, distributed computing and clustering of services.  
           [0006]    2. Description of Related Art  
           [0007]    U.S. Patent Documents  
                                                           6,122,756   September 2000   Baxter, et al.           5,862,312   January 1999   Mann, et al.           5,202,980   April 1993   Morita, et al.           6,128,277   October 2000   Bruck, et al.           5,361,347   November 1994   Glider, et al.           5,841,775   November 1998   Huang           6,253,230   June 2001   Couland, et al.           6,141,759   October 2000   Braddy                      
 
           [0008]    The Problem: Building the Best Architecture to Deliver Internet Services  
           [0009]    An Internet Service Provider (ISP) delivers Internet services to businesses and consumers. Internet services are applications that are offered to users over the Internet. These services include, but are not limited to, dial-up IP, email, chat, portal, electronic commerce and news. When building architecture to deliver these Internet services, the following issues arise:  
           [0010]    It is difficult to scale the infrastructure to support growing user bases and additional Internet services.  
           [0011]    Services rely on computer hardware and computer hardware fails quite often, creating costly downtime.  
           [0012]    Due to the nature of Internet services and increasing savvy of Internet users, security is difficult to manage.  
           [0013]    Finding technical talent capable of managing the system resources is increasingly difficult.  
           [0014]    Two Typical Approaches  
           [0015]    Enterprise Solutions  
           [0016]    The use of enterprise class hardware and software is becoming the standard for building architecture to support Internet services. The term enterprise typically refers to larger corporations, so enterprise hardware and software is geared toward larger corporations.  
           [0017]    Enterprise platforms have a number of features that benefit the service provider market. Enterprise hardware platforms scale easily. Additional modules that carry additional capacity or functionality can be added to most enterprise hardware platforms. Due to technology advances such as hot swapping hardware, it becomes practical to scale the enterprise hardware platform. Also, redundancy of hardware minimizes potential system downtime.  
           [0018]    Enterprise software platforms are deployed on enterprise hardware platforms. They rely on the enterprise hardware for scale. Enterprise software platforms can be tuned and optimized for these hardware platforms. Various enterprise hardware and software must be tightly integrated to provide architecture capable of delivering Internet services.  
           [0019]    The largest benefit to using enterprise class hardware and software are the corporate alliances that the enterprise solution providers bring with them. These alliances bring network, storage, server and software companies together to provide a solution for vertical market segments. There are several enterprise solutions for the service provider market.  
           [0020]    [0020]FIG. 1, provides a typical example of an enterprise solution geared towards the service provider market. The architecture described is capable of providing Internet services in a reliable manner. The servers are standard enterprise servers clustered together with software. The storage is arranged in a standard Storage Area Networks (SAN) design. The router and switch are assumed fault-tolerant and could be duplicated for redundancy. This architecture (hardware and software) can be purchased within a six hundred thousand dollar price point.  
           [0021]    It would appear that an enterprise solution would be the best option for delivering Internet services in a reliable manner; however, it is an extremely expensive option.  
           [0022]    Due to extreme cost concerns, it is difficult for the service provider industry to make use of enterprise solutions. Service providers require hardware and software solutions that grow incrementally so that the cost of their architecture will only be incurred as their customer base and revenues grow. Due to these cost concerns, a completely new architecture should be built so that the service provider can grow incrementally.  
           [0023]    Teamwork Approach  
           [0024]    Due to the price of enterprise solutions, service providers have turned to integrating existing low-end hardware and software in order to deliver reliable Internet services.  
           [0025]    Service providers have recognized that enterprise solutions are overkill for their needs. The margin on low-end hardware and software is much less than enterprise hardware and software, so the price point for low-end hardware and software is decreasing daily. This makes low-end hardware and software integration appear to be a lucrative option for the service provider market.  
           [0026]    The teamwork approach to creating architecture capable of providing Internet services is extremely labor intensive. A strong team of engineers can integrate low-end hardware in order to provide architecture for a service provider. They can build a system to provide reliable Internet services by using a combination of inexpensive servers, storage and network devices.  
           [0027]    Scaling is simply a matter of adding more low-end hardware to the mix. The team develops methods for capacity planning and performance monitoring in order to incrementally scale the architecture. They also devise a monitoring procedure and will respond quickly to system failures.  
           [0028]    A strong team of engineers can also integrate existing custom off the shelf (COTS) software in order to deliver reliable Internet services. There is a variety of low-end software that will provide Internet services. In fact, much of this software is available from various public domain sources. This software can be integrated with external scripts and programs written by the service provider&#39;s engineering staff in order to provide a full suite of Internet services.  
           [0029]    While there is a large savings from utilizing low-end hardware and software, the teamwork approach is not without significant costs. This approach is extremely labor intensive. Good engineering talent is very expensive in today&#39;s technical market place.  
           [0030]    Since the individual technology companies have not formed alliances to deliver lower-end solutions, there is no standard for this approach. Due to the lack of standardization, greater effort is required to design, deploy, and administer this architecture. As this type of architecture grows, the engineering staff resource requirements, and cost of those resources will grow exponentially.  
           [0031]    Summary of Two Typical Approaches  
           [0032]    Enterprise solutions and teamwork solutions are both good approaches for deploying infrastructure to support service provider offerings. However, each option is not without costly downsides.  
           [0033]    Enterprise solutions bring best of breed hardware and software together in a standard way to provide Internet services. This standardization enables ease of scale and administration thus limiting the necessity for large amounts of engineering staff resources. However, enterprise solutions are extremely pricey due to the high cost of enterprise class hardware and software.  
           [0034]    The teamwork solution makes use of the lower end hardware and software, but it requires large amounts of engineering staff resources due to the lack of corporate alliances and standardization. Since engineering staff is quite expensive and difficult to obtain, this option will be extremely pricey and very time consuming.  
           [0035]    [0035]FIG. 2, summarizes the individual PROS and CONS of each approach.  
           [0036]    The key to leveraging the advantages of each approach, is standardization. Lower-end hardware and software can be integrated to accomplish the same end goal as standard enterprise solutions. However, standardization is critical to create ease of scale and administration and to reduce costs by limiting the need for large amounts of technical staff. A company should take the initiative to create a standard platform that integrates the lower-end hardware and software from best of breed hardware and software manufacturers. This integration should be geared towards a standard platform for the service provider industry.  
         BRIEF SUMMARY OF THE INVENTION  
         [0037]    Clustered Services Architecture (CSA) defines a standard architecture for the service provider market. This approach integrates best of breed hardware and software to provide an architecture capable of delivering Internet services in a reliable manner. CSA combines the benefits of enterprise solutions and the teamwork approach in a much more cost efficient way. The CSA:  
           [0038]    scales independently and incrementally as the customer base and service offerings grow. uses lower-end hardware and software from best of breed hardware and software manufacturers. and is designed to fit the specific needs of the service provider market.  
           [0039]    At the heart of CSA are two methods, each with important benefits: the Well Defined Architecture and Services Clustering. The Well Defined Architecture standardizes the hardware in CSA. It is a standard architecture for integrating lower-end hardware from best of breed hardware manufacturers for service providers. This architecture uses open system standards throughout the integration process, ensuring that there is no dependency on a particular hardware vendor. It is possible to use any hardware vendor that adheres to the open standard.  
           [0040]    The second method is known as Services Clustering. Services Clustering defines the software architecture component of CSA. This method sets standards for the deployment of the back-end and front-end software required to enable Internet services. This method groups services together to make efficient use of the standard hardware architecture (Well Defined Architecture). 
       
    
    
     BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING  
       [0041]    For a fuller understanding of the present invention, reference is made to the following detailed description taken in conjunction with the accompanying drawing figures wherein like reference character denote corresponding parts throughout the several views and wherein:  
         [0042]    [0042]FIG. 1 is an example of a typical enterprise architecture;  
         [0043]    [0043]FIG. 2 is a summary of the PROs and CONs of existing approaches to problem;  
         [0044]    [0044]FIG. 3 describes the three layers of the well-defined architecture;  
         [0045]    [0045]FIG. 4 details the difference between services clustering and non-clustering; 
     
    
     DETAILED DESCRIPTION OF THE INVENTION  
       [0046]    Clustered Services Architecture (CSA) defines a standard architecture for the service provider market.  
         [0047]    This approach integrates best of breed hardware and software to provide an architecture capable of delivering Internet services in a reliable manner. CSA combines the benefits of enterprise solutions and the teamwork approach in a much more cost efficient way. The CSA:  
         [0048]    scales independently and incrementally as the customer base and service offerings grow. uses lower-end hardware and software from best of breed hardware and software manufacturers. and is designed to fit the specific needs of the service provider market.  
         [0049]    At the heart of CSA are two methods, each with important benefits: the Well Defined Architecture and Services Clustering. The Well Defined Architecture standardizes the hardware in CSA. It is a standard architecture for integrating lower-end hardware from best of breed hardware manufacturers for service providers. This architecture uses open system standards throughout the integration process, ensuring that there is no dependency on a particular hardware vendor. It is possible to use any hardware vendor that adheres to the open standard.  
         [0050]    The second method is known as Services Clustering. Services Clustering defines the software architecture component of CSA. This method sets standards for the deployment of the back-end and front-end software required to enable Internet services. This method groups services together to make efficient use of the standard hardware architecture (Well Defined Architecture).  
         [0051]    Well Defined Architecture  
         [0052]    The Well Defined Architecture standardizes the three layers of hardware necessary to deliver reliable Internet services. Each hardware layer works together to provide a complete hardware architecture for service providers. The three layers are:  
         [0053]    Network Layer—a combination of network resources that enables the customer to access the services (i.e. switches and routers).  
         [0054]    Server Layer—a combination of server equipment that serves the services to the customer (i.e.  
         [0055]    Unix servers).  
         [0056]    Storage Layer—a combination of disk resources that stores information that the services require.  
         [0057]    The well-defined architecture is designed to make efficient use of the system resources. This architecture makes use of proven technology to tightly integrate the three tiers. Each tier can scale independently and operate efficiently.  
         [0058]    Network Layer  
         [0059]    The Well Defined Architecture standardizes the Network Layer with two technologies.  
         [0060]    Virtual Local Area Networks (VLAN) are used at Open System Interconnection (OSI) Layer  2  and  3  (Data Link and Network) in order to make efficient use of the network resources.  
         [0061]    Switching on a network inherently speeds up network performance.  
         [0062]    VLAN&#39;s allow for an inexpensive, flexible way to modify logical groups in changing environments.  
         [0063]    VLAN&#39;s operate independently of the physical medium; which will allow the network to be upgraded with no impact to the existing Internet services.  
         [0064]    VLAN&#39;s also add additional data security to the Network Tier.  
         [0065]    Load Direction and Content Switching is used at OSI Layer  2 , 3 , 5  and  7  (Data Link, Network, Session and Application). Load Direction is used to direct Internet service users to one server from a pool of servers. Content switching:  
         [0066]    allows the users to be directed to the most available server in the pool.  
         [0067]    enables persistence such that the user is continuously directed back to the server initially chosen for a finite period of time.  
         [0068]    Server Tier  
         [0069]    CSA approaches the Server Tier with a technology called ensoRAIS (ensoport.com, Inc.&#39;s Redundant Array of Inexpensive Servers). This technology is based on using a group of inexpensive servers as opposed to a small number of enterprise class servers. Each server has an exact replica of the software required to host a service. Because of this, users can access any of the servers and utilize the Internet services. Each server in the ensoRAIS design is configured exactly like every other server. In the event that more server resources are necessary, it is easy to add another server to the configuration without impacting the existing traffic on the current servers.  
         [0070]    Storage Tier  
         [0071]    CSA standardizes the Storage Tier with Network Attached Storage (NAS) technology. Network Attached Storage introduces a high-performance, highly reliable device that is dedicated to providing storage over a network. NAS devices have a single purpose operating system that reduces the overhead of reading and writing data from the storage medium. Adding more disks can scale these devices. They operate independently of the server that requires the information that they store.  
         [0072]    Within CSA, the server layer accesses information from the NAS devices using Network File System (NFS). NFS maintains file integrity so that files will not be corrupted when multiple machines attempt to access them at the same time.  
         [0073]    [0073]FIG. 3, provides a graphical representation of hardware that used at each of the three hardware layers.  
         [0074]    Services Clustering  
         [0075]    While the Well Defined Architecture standardizes the hardware requirement, Services Clustering standardizes the software requirement. This method “clusters” the services, that is to say, it groups the services together to make the most efficient use of the standard architecture (The Well Defined Architecture). The key to Services Clustering is the Service Package and Service Management.  
         [0076]    Service Package  
         [0077]    The service package is one copy of all of the software required to deliver every Internet service offered by the service provider. Each Internet service will require one or more pieces of software in order to operate. For example Internet email will require a mail transport agent software, a message access software and a web software. Similarly, Internet Chat will require a back-end chat daemon software and a front-end chat client. Using CSA, we create an Internet service package that includes all of the software required for email and all of the software required for chat. We then load this package onto every machine at the Server Layer of the Well Defined Architecture.  
         [0078]    The Content Switching at the Network Layer of the Well Defined Architecture directs users to the least loaded machine running the service package. For example, if a user wanted to use Internet Chat, they would be directed to the least loaded machine at the Service Layer. Because the software required to use chat is loaded on every machine at the Server Layer, every machine is capable of providing the service.  
         [0079]    [0079]FIG. 4, details the difference between using Services Clustering to offer Internet services and a non-clustered approach.  
         [0080]    Service Management  
         [0081]    Service Management maintains independent server configurations and automatically installs updates (i.e. Security Patches, Bug Fixes, etc...) all software included in the Service Package. This is accomplished through the use of remote software distribution. A gold copy of the service package is maintained, updated and tested. After testing in a vanilla environment, updates can be easily pushed to the Server Layer of the Well Defined Architecture.  
         [0082]    Creating a package of all software required to run all Internet services offered by the service provider is not difficult, but the configuration of each software package must differ slightly on each machine. For example, each server will have a different hostname and that hostname must be stored in a configuration file. Service Management resolves this issue by maintaining configuration files for all software on a machine independent basis. By maintaining a simple database of configuration files, changes to configuration files can be tracked and updated automatically.  
         [0083]    Benefits  
         [0084]    CSA is an extremely efficient model designed primarily for the service provider market. The primary benefits gained from CSA include cost savings, staff resource reduction, scalability, and fault tolerance.  
         [0085]    Cost Savings  
         [0086]    The use of CSA standard by a service provider will greatly reduce the initial investment in infrastructure hardware. Because of the Well Defined Architecture, the service provider is able to purchase only the computer hardware needed to begin offering Internet services. The service provider can then incrementally add additional hardware to each layer of the Well Defined Architecture as the hardware is needed. By incurring infrastructure cost incrementally, the service provider will be able to build profits faster and turn more resources back into growing the business and enhancing value to the customer.  
         [0087]    Staffing Resource Reduction  
         [0088]    Standardizing hardware (Well Defined Architecture) and utilizing Service Management (Services Clustering), have the benefit of minimizing technical staffing requirements.  
         [0089]    Overall administration is made easier because all hardware at each layer of the Well Defined Architecture is configured in exactly the same manner. Service Management keeps configuration differences and changes in a centralized location for easy administration. It also allows for a centralized software upgrade strategy. By making overall administration easy, the service provider can shift resources and staff to value added activities and positions such as sales and customer care.  
         [0090]    Scalability  
         [0091]    The CSA is incrementally scalable due to the modularity in the Well Defined Architecture and the Service Package offered by Services Clustering. The Well Defined Architecture allows the service provider to incrementally add hardware to each hardware layer as additional resources and capacity is required. By creating a Service Package that consolidates all software required for every Internet service offered, the service provider can add hardware resources to the Server Layer in real time without impacting current users. Increasing demand for internet services in markets around the world makes incremental scalability one of the most important benefits of CSA.  
         [0092]    Fault Tolerance  
         [0093]    Fault Tolerance is accomplished by CSA through redundancy. Redundancy is accomplished by the modularity in the Well Defined Architecture and the Service Package offered by Services Clustering. The Well Defined Architecture breaks each hardware layer into an independent group. The individual pieces of hardware required at each layer are redundant. By loading the one Service Package on all machines at the Server Layer, several machines can fail and users will be directed to the remaining (normal functioning) servers until hardware failure can be resolved. The service provider will ensure customer satisfaction by meeting extremely high Quality of Service levels and system uptimes.  
         [0094]    Summary  
         [0095]    Clustered Services Architecture is a cost and time efficient solution for deploying service provider architecture. This solution provides scalability, fault tolerance and reduces staffing requirements. The key to this solution is standardization and the ability to add hardware and software incrementally.