Patent Grant
8260918
This invention relates to the field of internet processors, and more specifically to a method and apparatus of delivering security services such as firewalls.
The service provider game has grown extremely crowded and fiercely competitive, with numerous players offering similar products and services. While having a large number of comparable services is arguably beneficial to the enterprise, it poses a host of potentially disastrous consequences for a service provider. If all competitors in a given market are offering services that are indistinguishable by the customer base, the burden of differentiation falls squarely on cost, with the least-cost competitor emerging “victorious”. Jockeying for the cost-leader position rapidly drives down service pricing, reducing margins to rubble and rendering the service a commodity. Furthermore, numerous offerings that are similar in attributes and cost make it very difficult to lock in customers.
Operational costs also present a significant challenge to service providers. Cumbersome, manual provisioning processes are the primary culprits. Customer orders must be manually entered and processed through numerous antiquated backend systems that have been pieced together. Once the order has been processed, a truck roll is required for onsite installation and configuration of Customer Premises Equipment (CPE), as well as subsequent troubleshooting tasks. This is a slow and expensive process that cuts into margins and forces significant up-front charges to be imposed on the customer. In order to be successful in today's market, service providers must leverage the public network to offer high-value, differentiated services that maximize margins while controlling capital and operational costs. These services must be rapidly provisioned and centrally managed so that time-to-market and, more importantly, time-to-revenue are minimized. Traditional methods of data network service creation, deployment, and management present significant challenges to accomplishing these goals, calling for a new network service model to be implemented.
Basic Internet access, a staple of service provider offerings, has been commoditized to the point that margins are nearly non-existent. This fact has driven service providers to look for new value-added features and services to layer over basic connectivity so that they are able to differentiate on factors other than cost. The most significant opportunity for differentiation is found in managed network services. Managed network services enable enterprise IT organizations to outsource time-consuming tactical functions so that they can focus strategic core business initiatives.
Enterprise customers are now demanding cost-effective, outsourced connectivity and security services, such as Virtual Private Networks (VPNs) and managed firewall services. Enterprise networks are no longer segregated from the outside world; IT managers are facing mounting pressure to connect disparate business units, satellite sites, business partners, and suppliers to their corporate network, and then to the Internet. This raises a multitude of security concerns that are often beyond the core competencies of enterprise IT departments. To compound the problem, skilled IT talent is an extremely scarce resource. Service providers, with expert staff and world-class technology and facilities, are well positioned to deliver these services to enterprise customers.
While IT managers clearly see the value in utilizing managed network services, there are still barriers to adoption. Perhaps the most significant of these is the fear of losing control of the network to the service provider. In order to ease this fear, a successful managed network service offering must provide comprehensive visibility to the customer, enabling them to view configurations and performance statistics, as well as to request updates and changes. Providing IT managers with powerful Customer Network Management (CNM) tools bolsters confidence in the managed network service provider and can actually streamline the service provisioning and maintenance cycle.
Customer Premises Equipment (CPE)-Based Managed Firewall Services
Data network service providers have traditionally rolled out managed network service offerings by deploying specialized CPE devices at the customer site. This CPE is either a purpose-built network appliance that, in addition to providing specific service features, may also serve some routing function, or a mid to high-end enterprise-class server platform, typically UNIX-based. In the case of a managed firewall solution, the CPE device provides services that may include VPN tunnel termination, encryption, packet filtering, access control listings, and log files. The CPE at each customer site is aggregated at a multiplexer via leased lines and/or public Frame Relay PVCs (permanent virtual circuits) at the service provider POP (point of presence), then into a high-end access router and across the WAN (wide area network).
In many cases, service providers and enterprise customers find it too expensive and cumbersome to deploy CPE-based security at every site, but rather deploy secure Internet access points at one or two of the largest corporate sites. In this model, all remote site Internet traffic is backhauled across the WAN to the secure access point and then out onto the Internet, resulting in increased traffic on the corporate network and performance sacrifices.
Service providers face significant challenges when deploying, managing and maintaining CPE-based managed firewall services. When a customer expresses interest in utilizing such a service, a consultation with experienced security professionals is required to understand the corporate network infrastructure and site-specific security requirements, yielding a complex set of security policies. This may be accomplished through a set of conference calls or a number of on-site visits. Once the security requirements and policies have been identified, the service provider must procure the CPE device. In some cases, the equipment vendor may provide some level of pre-configuration based upon parameters supplied by the service provider. While CPE vendors are driving towards delivering fully templatized, pre-configured systems that are plug-and-play by enterprise staff, most service providers still assume the responsibility for on-site, hands-on configuration, and a truck-roll to each of the customer sites is necessary. This is particularly true in server-based CPE systems, where a relatively high degree of technical sophistication and expertise is required to install and configure a UNIX-based system.
Typically, a mid-level hardware and security specialist is sent onsite, along with an account manager, to complete the CPE installation and configuration. This specialist may be a service provider employee or a systems integrator/Value-Added Reseller (VAR) who has been contracted by the service provider to complete CPE rollout. This complex process begins with physical integration of the CPE device into the customer network. In the case of a CPE appliance, where the OS and firewall/VPN software components have been pre-loaded, the tech can immediately proceed to the system configuration phase. Server-based CPE services, however, require the additional time-consuming step of loading the system OS and software feature sets, adding a further degree of complexity.
In the configuration phase, the tech attempts to establish contact between the CPE device and central management system at the service provider NOC (network operations center). In cases where the device has not been previously assigned an IP address, an out-of-band signaling mechanism is required to complete the connection, typically a modem and a POTS line. If the integration process has been successful, NOC staff should be able to take over the process, pushing specific policy configurations (and possibly an IP address) down to the CPE device through a browser-driven management interface. This entire process must be repeated for every enterprise site utilizing the managed firewall service.
Additionally, maintenance processes and costs for CPE-based managed firewall services can also be overwhelming to both the service provider and enterprise customers. Enterprises are forced to either keep cold spares onsite or be faced with periods of absent security when their firewall fails, a situation that is unacceptable to most of today's information intensive corporations. Service providers must have an inventory of spares readily available, as well as staff resources that can, if necessary, go onsite to repeat the system configuration process. Troubleshooting thousands of CPE devices that have been deployed at customer sites is an extremely formidable challenge, requiring extensive call center support resources, as well technicians that can be quickly deployed onsite.
As CPE-based firewall services have traditionally been deployed in private enterprise networks, the original management systems for these devices have difficulty scaling up to manage several large, multi-site service provider customers. CPE device vendors are scrambling to ramp up these systems to carrier-grade and scale. Firewall management systems are typically GUI-based (graphical user interface-based), browser-driven interfaces that run on industrial grade UNIX platforms in the service provider NOC. The management system interfaces with the CPE devices based on IP address. The CPE-based managed firewall model faces service providers with another issue: capital costs. In addition to the significant costs required to build out a POP/access infrastructure, including multiplexers and high-capacity access routers, the service provider must also assume the initial costs of the CPE device, including firewall and VPN software licensing charges. In many cases, these costs are passed on to the customer. This creates steep up-front costs that, coupled with per-site installation charges, can present a serious barrier to service adoption. In markets where several service providers are offering managed firewall services, a service provider may absorb the CPE cost to obtain a price leadership position, cutting deeply into margins.
The CPE-based model is also limited when rolling out services beyond the managed firewall offering. New services, such as intrusion detection, may require additional hardware and/or software. This results in higher capital costs, as well as another expensive truck roll.
Thus, there is a need for a method and apparatus of delivering a variety of network services, for example security services such as firewalls.
The present invention provides a flexible, scalable hardware and software platform that allows a service provider to easily provide internet services, virtual private network services, firewall services, etc., to a plurality of customers. This solution can be changes to provision each customer with more or less processing power and storage, according to individual changing needs a packet routing system includes a processor identifier as part of each packet to route the packets to a physical processor, and a logical queue identifier to route the packets to the destination object within that processor.
One aspect of the present invention provides a method of packet routing. The method includes connecting a plurality of processors in a network, assigning a unique processor identifier (PEID) to each of the processors, routing a first packet to a first one of the processors across the network, wherein each such packet includes a PEID value corresponding to a PEID of one of the processors, and wherein the routing to the first processor is based on the PEID value in the first packet, establishing a plurality of objects in the first processor, assigning a logical queue identifier (LQID) to a first one of the objects in the first processor, wherein each packet also includes an LQID value corresponding to an LQID of one of the objects, and routing the first packet to the first object based on the LQID value in the first packet.
Another aspect of the present invention provides a system for routing packets. This system includes a plurality of processors coupled to one another using a network, wherein each of the processors a unique processor identifier (PEID), wherein a first packet is routed into a first one of the processors across the network, wherein each such packet includes a PEID value corresponding to a PEID of one of the processors, and wherein the routing to the first processor is based on the PEID value in the first packet, a plurality of objects in the first processor, wherein each such object is assigned a logical queue identifier (LQID), wherein each packet also includes an LQID value corresponding to an LQID of one of the objects, and software for routing the first packet to the first object based on the LQID value in the first packet.
Still another aspect of the present invention provides a system for routing packets. This system includes a plurality of processors coupled to one another using a network, wherein each of the processors a unique processor identifier (PEID), wherein a first packet is routed into a first one of the processors across the network, wherein each such packet includes a PEID value corresponding to a PEID of one of the processors, and wherein the routing to the first processor is based on the PEID value in the first packet, and a plurality of objects in the first processor, wherein each such object is assigned a logical queue identifier (LQID), wherein each packet also includes an LQID value corresponding to an LQID of one of the objects, wherein the first packet is routed to the first object based on the LQID value in the first packet.
In the following detailed description of the preferred embodiments, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments in which the invention may be practiced. It is understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the present invention.
The leading digit(s) of reference numbers appearing in the Figures generally corresponds to the Figure number in which that component is first introduced, such that the same reference number is used throughout to refer to an identical component which appears in multiple Figures. Signals and connections may be referred to by the same reference number or label, and the actual meaning will be clear from its use in the context of the description.
In some embodiments, the present invention deploys one or more virtual private networks (VPNs) running on one or more carrier-class platforms that scale to provide cost-effective solutions for internet service providers (ISPs). In particular, security services such as firewalls can be provided by the ISPs for services they provide to their customers, wherein a plurality of customers are hosted on a single network of processors. An ISP is providing hosting services (e.g., hosting an internet web site for a customer) and routing (moving data to and from the internet) for their customers.
Further, by establishing secure connections between two ISP boxes 110 across the internet 99, a virtual private network or VPN 410 (see
In some embodiments, software 220 includes IP network operating system (IPNOS) 223, service management system (SMS) 221 (e.g., in some embodiments, this is the Invision™ software from CoSine Communications Inc., assignee of the present invention), and customer network management system (CNMS) 222 (e.g., in some embodiments, this is the InGage™ software from CoSine Communications Inc., assignee of the present invention). SMS 221 provides such services as configuration of blades 239, defining subscribers, determining services, and generation of IP security (IPSec) public/private key pairs. CNMS 222 provides such services as providing subscribers (customers) visibility to services. In some embodiments, CNMS software runs at least in part in a user's CPE or workstations, typically at a company's information services (IS) headquarters.
In some embodiments, IP server switch (IPSX) hardware 230 includes one or more scalable hardware enclosures, each having a plurality of service “blades” 239 (i.e., an insertable and removable printed circuit card having one or more processors, each having its own CPU and memory) each connected in a ring configuration (such as a counter-rotating dual ring 232). In some embodiments, three types of blades 239 are provided: control blade(s) 234, processor blade(s) 236, and access blade(s) 238. IPSX hardware also includes highly available, redundant, and hot-swappable hardware support 240 including power supplies 241 and fans 242.
In some embodiments, IPDSP 300 provides a VPN 410, using secure connections across the internet 99, to connect remote offices 301 to one another.
In some embodiments, system 401 at a first site (e.g., an ISP premises locally connected to a customer office) includes IPSX 201-1 having a VR 210 connected to CPE 117. This system 401 appears to the outside world as a single router having firewall services, server(s) and user(s), etc. These functions can be provided by either or both VR 210 and CPE 117, thus allowing a customer to outsource many or most of these services to the service provider and IPSX 201-1. Similarly, system 402 at a second site (e.g., another ISP premises locally connected to a remote office of the same customer) includes IPSX 201-2 having a VR 210 connected to CPE 119. This system 402 also appears to the outside world as a single router having firewall services, server(s) and user(s), etc. These functions can be provided by either or both VR 210 and CPE 119, thus allowing a customer to outsource many or most of these services to the service provider and IPSX 201-2.
In some embodiments, a single system chassis 831 provides a redundant back plane and blade-termination facilities 832. The access blades 238, processor blades 236, control blades 234, power supplies 241 and fan trays 242 are designed for hot-swappable operation—any of these components may be removed from service while the entire system remains operational. The metallic cross connect is a passive system that provides fail-over support to allow DS3 and DS1 access facilities to be switched from one access blade to another access blade should an access port or card fail. The phase 1 chassis provides 26 universal slots, each of which may be populated with control blades, access blades, and processor blades. To operate, the chassis must contain at least one control blade. Up to two control blades may be operational in a chassis at the same time. Access blades are added as input/output requirements grow, and processor blades are added as computation requirements scale.
In some embodiments, each system 230 supports up to twenty-five processing blades (PB) 236. Each processor blade 236 is designed to support three hundred Mbps of full duplex traffic while delivering IP services including application firewall, LT2P, PPTP, NAT, VPN router.
In some embodiments, each system 230 supports up to two control blades (CB) 234. CBs 234 provide overall system supervision, IP route calculation, software update management, and network management statistics logging services. When two CBs 234 are operational within a chassis 831, they remain synchronized such that should either CB 234 fail, the other CB 234 automatically takes over system operation. In this process all active services remain in progress. Each control blade 234 is hot swappable, so that when proper procedures are followed, a failed or malfunctioning CB 234 may be removed from on operational system 230 without bringing down any customer services.
In some embodiments, each CB 234 provides four Ethernet interfaces for management traffic. Each Ethernet interface has a distinct collision domain and may each be configured with a primary and secondary IP address. Ethernet interfaces designated for management use may be configured for primary and protected configurations, both sharing the same IP address, reducing ISP IP address requirements. The CB 234 Ethernet interfaces may be configured for fully meshed communications over diverse paths to diverse operating systems. Each CB 234 is also equipped with a random # seed generator for use in security applications.
In some embodiments, each system 230 supports up to twenty-five access blades (AB) 238. Access blades 238 provide physical line termination, hardware-assisted IP forwarding, hardware assisted encryption services, and hardware assisted queue management. Each access blade 238 is hot swappable, so that when proper procedures are followed, a failed or malfunctioning ab may be removed from on operational system 230 without bringing down any customer services. In some embodiments, 10/100 Ethernet-, DS3-, and OC3-type access blades are supported by system 230.
In some embodiments, a separate control ring 935 is provided, connected to all processors 930. Data passed on the control ring 935 allows control communications to be passed between processors, and in particular, allows the control blade to configure and control the other blades in IPSX 201. In other embodiments, ring 935 is omitted, and its function is overlaid on rings 933 and 934.
Logical Queue Identifiers
In some embodiments, rings 933 and 934 are packet-passing rings. Each packet 950 placed in the rings includes a data portion 953 and a processor element identifier (PEID 951) that identifies for each node 931 which processor that packet is destined for, for example a 16-bit PEID that specifies one of 65526 PEs. If the PEID matches a processor on its particular node, the node 931 passes the packet to the proper processor 930; if not, the packet is forwarded to the next node 931. In some embodiments, each packet also includes a logical queue identifier (LQID) that identifies a software entity (for example, an object group for a particular VR 210) residing on that processor 930 for which the packet is destined.
In some embodiments, every node 931 has a unique, globally unique (i.e., unique within an IPSX 201, or within an ISP having a plurality of IPSXs 201) PEID 951. In some embodiments, the way this is done is that one takes the blade ID (e.g., five bits) and you append the PE number, which is, for example, a eleven bits. Put that together in some fashion and you'll get a unique ID that is globally unique within some hardware configuration. Note that packets including this PEID 951 are routable. Just by looking at the PEID 951, the system 201 has a topological structure so that it can route based on purely the PEID 951. The next thing to keep in mind is that system 201 is managing multiple virtual context. Each VR 210 in a system 201 is a virtual router to which packet are to be directed. When packets come into node N 931 for example, system 201 needs to be able to steer it to the appropriate logical entity, i.e., to the appropriate context and to the object channel that it represents. Thus, a logical queue ID 952 is appended that is unique within the destination processor (PE) 930. If an object in a processor 930 on node 1930 wants to set up a channel to another object a processor 930 on node N 930, they need to use the LQID 952 and PEID 951 together represent the remote end of the object and so the system can map the corresponding object channel, defining the object channel that is going across the network. From a networking perspective, PEID 951 looks like your IP address that routes packets like an IP address. But once you go to a particular node 931, the LQID looks like the UDP (User Datagram Protocol, a TCP/IP protocol describing how messages reach programs within a destination computer) code number. So system 201 (e.g., SMS 221) essentially signals and negotiates the proper LQID to have a channel going between those ends. This allows all the traffic coming into a PE 930 to be steered along the appropriate object path to the appropriate object channel on that object.
In some embodiments, an object could be talking on another channel to another object, or to the same object, using a different channel. In which case each channel uses a different LQID 952, but the same PEID 951.
In some embodiments, system 201 sets up a shortcut that circumvents traffic that otherwise would be transmitted outside system 201 and then back in (e.g., traffic between two different VRs 210 supporting different customers). To set up such a shortcut, system 201 allocates a different LQID 952 for the shortcut. Thus, an object channel has the normal point-to-point path for normal traffic and has a multi-point-to-point path which is used for shortcut traffic. So when packets come in to the object it knows whether the packet came in on the normal path or on the shortcut path. Similarly, when the object wants to use a shortcut, it also needs to allocate a different LQID for its outbound shortcut traffic. One interesting distinction of shortcut paths is that the normal point-to-point is bidirectional and data can flow in both directions, but shortcuts data flow flows in only one direction. So a receive site can have any number of transferred sites. Any number of objects can be transmitting to the same receive site. That is why it is called multi-point-to-point.
Further, some embodiments have different levels of shortcuts. For example, a packet can be sequentially passed to successive destinations in some embodiments. Thus there can be a complex multistage path. The shortcuts can trickle down to the ultimate end, where the packet cascades. Further, if one object knows a shortcut, it can tell other objects about its shortcut. So the other object does not have to come to the first object and then be directed to the shortcut destination, but rather can directly use the shortcut it has learned about.
While service providers recognize the tremendous revenue potential of managed firewall services, the cost of deploying, managing and maintaining such services via traditional CPE-based methods is somewhat daunting. Service providers are now seeking new service delivery mechanisms that minimize capital and operational costs while enabling high-margin, value-added public network services that are easily provisioned, managed, and repeated. Rolling out a network-based managed firewall service is a promising means by which to accomplish this. Deploying an IP Service Delivery Platform in the service provider network brings the intelligence of a managed firewall service out of the customer premises and into the service provider's realm of control.
An IP Service Delivery Platform consists of three distinct components. The first is an intelligent, highly scalable IP Service Processing Switch. Next is a comprehensive Service Management System (SMS) to enable rapid service provisioning and centralized system management. The last component is a powerful Customer Network Management (CNM) system which provides enterprise customers with detailed network and service performance systems, enable self-provisioning, and eases IT managers fears of losing control of managed network services.
In a network-based managed firewall service model, the service provider replaces the high-capacity access concentration router at the POP with an IP Service Processing Switch. This is higher-capacity, more robust, and more intelligent access switch, with scalable processing up to 100+ RISC CPUs. Just as with the access router, additional customer access capacity is added via installing additional port access blades to the IP Service Processing Switch chassis. Unlike conventional access routers, however, additional processor blades are added to ensure wire-speed performance and service processing.
The intelligence resident in the IP Service Processing Switch eliminates the need to deploy CPE devices at each protected customer site. Deployment, configuration, and management of the managed firewall service all take place between the IP Service Processing Switch 230 and its Service Management System 221, which resides on a high-end UNIX platform at the service provider NOC. The customer also has the ability to initiate service provisioning and augmentation via a web-based Customer Network Management tool that typically resides at the customer's headquarters site. This is an entirely different service delivery paradigm, requiring minimal or no truck rolls or on-site intervention.
To roll out a managed network-based firewall service, the service provider's security staff provides a consultation to the enterprise, thereby gaining an understanding of the corporate network infrastructure and developing appropriate security policies (this is a similar process to the CPE model). Once this has been accomplished, the NOC security staff remotely accesses the IP Service Processing Switch (using the Service Management System 221) at the regional POP serving the enterprise customer, and the firewall service is provisioned and configured remotely.
This model enables the service provider to leverage the enterprise's existing services infrastructure (leased lines and Frame Relay PVCs) to deliver new, value-added services without the requirement of a truck roll. All firewall and VPN functionality resides on the IP Service Processing Switch at the POP, thus freeing the service provider from onsite systems integration and configuration and effectively hiding the technology from the enterprise customer. Firewall inspection and access control functions, as well as VPN tunneling and encryption, take place at the IP Service Processing Switch and across the WAN, while the enterprise's secure leased line or Frame Relay PVC (permanent virtual circuit) access link remains in place. The customer interface is between its router and the IP Service Processing Switch (acting as an access router), just as it was prior to the rollout of the managed firewall service. Additionally, the customer has visibility into and control over its segment of the network via the CNM that typically resides at the headquarters site.
The network-based firewall model also enables service providers to quickly and cost-effectively roll out managed firewall solutions at all enterprise customer sites. As a result, secure Internet access can be provided to every site, eliminating the performance and complexity issues associated with backhauling Internet traffic across the WAN to and from a centralized secure access point.
As the IP Service Delivery Platform is designed to enable value-added public network services, it is a carrier-grade system that is more robust and higher-capacity than traditional access routers, and an order of magnitude more scalable and manageable than CPE-based systems. The platform's Service Management System enables managed firewall services, as well as a host of other managed network services, to be provisioned, configured, and managed with point-and-click simplicity, minimizing the need for expensive, highly skilled security professionals and significantly cutting service rollout lead-times. The Service Management System is capable of supporting a fleet of IP Service Processing Switches and tens of thousands of enterprise networks, and interfaces to the platform at the POP from the NOC via IP address. Support for incremental additional platforms and customers is added via modular software add-ons. Services can be provisioned via the SMS system's simple point and click menus, as well as requested directly by the customer via the CNM system.
Deployment of a robust IP Service Delivery Platform in the carrier network enables service providers to rapidly turn-up high value, managed network-based services at a fraction of the capital and operational costs of CPE-based solutions. This enables service providers to gain a least-cost service delivery and support structure. Additionally, it enables them to gain higher margins and more market share than competitors utilizing traditional service delivery mechanisms—even while offering managed firewall services at a lower customer price point.
Business Case
This business case highlights the difference between traditional CPE-based managed firewall services (both appliance and server-based models) and managed, network-based firewall services. This comparison is based upon both capital costs and incremental operational or “soft” costs.
This business case is modeled around a theoretical North American service provider that is rolling out a managed firewall service. The service provider has ten regional Points of Presence (POPs) across the US, and a single Network Operations Center (NOC). The business case examines growth of the managed firewall service customer base yearly over a five-year period.
Assumptions
The cost benefits of a managed, network-based Firewall Service Model becomes apparent when Service Providers are deploying managed firewall services to more than twenty-nine enterprise sites. By examining the hardware and software costs alone, a network-based model becomes more cost effective to Service Providers as they begin to roll services to more than thirty sites.
A Check Point firewall solution (one based on Check Point hardware) would cost Service Providers $478,000 to support thirty enterprise sites; whereas, a network-based firewall solution using the IP Service Delivery supports thirty enterprise sites for $450,000 with the ability to support an additional twenty-five sites without an increase in cost. If the Service Provider wanted to deploy services to twenty-five additional sites using a Check Point solution, the total cost of support fifty-five sites would be $835,000—$385,000 more than the network-based IP Service Delivery Platform. The savings of the network-based solution would continue to scale as additional sites were added incrementally.
If the enterprise customer does not have a Cisco 7513 or a comparable router installed at these sites, Service Providers would be forced to incur even greater initial start-up costs with the Check Point solution. If routers were to be installed at each enterprise site, the network-based Firewall solution would become the more cost-effective alternative when Service Providers needed to roll out services to more than twenty-one enterprise sites.
Business Case—Models
This business case will explore four specific managed firewall service delivery architectures as described by interviewed service providers, systems integrators, and hardware/software vendors.
CPE-Based Models
Architecture: One Check Point/Nokia Appliance
This architecture employs a firewall/VPN CPE appliance, traditional access router, and software-based centralized management system to deliver a managed firewall solution. The specific components of this solution include:
Architecture Two: Check Point Server
This architecture employs a firewall/VPN CPE server, traditional access router, and software-based centralized management system to deliver a managed firewall solution. The specific components of this solution include:
Architecture Three: WatchGuard Appliance Model
This architecture employs a firewall VPN CPE appliance, traditional access router, and software-based centralized management system to deliver a managed firewall solution. The specific components of this solution include:
POP Infrastructure
Each of the three CPE-based architectures explored in this analysis employs an identical POP infrastructure. This access infrastructure is based on the Cisco 7513 router. The base configuration for the 7513 includes:
The RSP4 cards in this base configuration each consume one slot in the chassis, leaving 11 remaining for port adapters. An Ethernet card is added for software uploads. Ingress traffic is supported via dual-port channelized and/or dual-port unchannelized T3 cards (for dedicated T3 connections). Each channelized T3 port can support up to 128 DS0 or NxT1 channels Single-port OC-3 POS cards provide connectivity to the network uplink on the egress side. These cards each occupy a single slot. Each card requires a programmable Versatile Interface Processor (VIP2), as well as an additional 64 MB of DRAM and 8 MB of SRAM. The VIP2 and additional memory reside on the T3 OC-3 cards and do not consume additional slots.
As described in the assumptions, a traditional multiplexer exists at each POP to aggregate various sub-T1 customer access links up to the channelized T3 interfaces on the Cisco 7513 router. As the POP infrastructure installation and configuration processes are uniform across all managed firewall service models explored in this analysis, the costs associated with these processes will not be quantified.
Network-Based Model of the Present Invention—Architecture Four
IP Service Delivery Platform 300 that includes an IP Service Processing Switch (IPSX 230), a Service Management System (SMS 221) and a Customer Network Management System (CNMS 222).
This architecture employs an IP Service Processing Switch and a software-based centralized SMS to deliver a managed firewall solution. The specific components of this solution include:
POP Infrastructure
The POP access infrastructure in the network-based managed firewall service model is based on the CoSine Communications IPSX 9000 Service Processing Switch. The base configuration for the switch includes:
The following tables analyze the cost structure of all of the above models and projects these costs out over 5 years:
Pricing listed is based on information from January of 2000 and is subject to change.
Analysis
Analysis of the four service delivery architectures for deploying a managed firewall service reveals extremely compelling data in favor of implementing the network-based model based on the CoSine Communications IP Service Delivery Platform. Significant advantages are gained by utilizing this model in each of the following areas:
Operational “Soft” Costs
The network-based managed firewall solution eliminates most of the steep operational costs that are associated with deploying a CPE-based solution, specifically the per site truck roll and device installation charges. The CheckPoint server-based CPE deployment and installation operational costs alone exceed the total five-year capital equipment investment required in the CoSine Communications network-based model. These costs 1400 are shown in
Capital Costs
The network-based managed firewall solution has total capital costs that, over the five-year customer growth period of this study, are an order of magnitude less than the CPE-based solutions. The total capital costs for each solution are shown in
Time to Market, Time to Revenue
The network-based managed firewall solution enables service providers to greatly shorten the lead-time required to deploy the managed firewall service. The removal of the CPE component from the service offering eliminates the need to procure the device, eliminating a 1-2 week delay in service rollout. This also eliminates the 2-4 week delay that is associated with scheduling an onsite installation.
Complexity
The network-based managed firewall solution greatly reduces the complexity associated with deploying the service. The number of distributed devices is reduced from thousands of remote customer sites to only 10 already staffed POPs, simplifying management and maintenance significantly.
The network-based managed firewall service model creates a new source of revenue for service providers that is scalable, repeatable, and cost-effective. Leveraging centrally-managed services enables service providers to derive greater value from the existing basic access infrastructure. The network-based model eliminates expensive onsite installation and maintenance required of CPE-based solutions, and provides a foundation to deploy additional value-added services via the same delivery mechanism. Elimination of the CPE device also effectively hides the technology of the managed firewall solution from the customer, reducing internal network complexity and technical anxiety.
The CoSine Communications IP Service Delivery Platform 300 enables service providers to reap the benefits of deploying a network-based managed firewall service. The IPSX 9000 Service Processing Switch is a robust, high-availability platform that is capable of supporting hundreds of customer sites and network-based firewalls. The Invision Services Management System is capable of rapidly provisioning and managing thousands of managed firewall customers throughout an extensive nationwide network, enabling service providers to leverage volume security services driven by fewer staff resources. And the InGage™ Customer Network Management system empowers customer IT managers to view and augment managed network services. The IP Service Delivery Platform positions service providers to continuously deploy new value-added services to their customer base, maximizing revenues and creating customer lock-in.
Service providers utilizing the IP Service Delivery Platform 300 are to gain a significant competitive edge in deploying high-value IP-based services. The CoSine Communications solution of the present invention enables services providers to save up to 85% on the capital costs associated with deploying a managed firewall service over traditional CPE-based approaches. Additionally, the CoSine solution of the present invention virtually eliminates the steep operational “soft” costs that plague the CPE approach, which total $79-161 M in the 5-year model architecture. These savings add up to literally tens to hundreds of millions of dollars over a five-year period. Furthermore, as customer numbers and bandwidth requirements increase over time, so do the cost savings. This enables service providers to gain a cost-leadership position while greatly increasing revenues.
In closing, the IP Service Delivery Platform (IPSDP 300) is an ideal solution for service providers seeking to offer high value managed, network-based firewall services.
In some embodiments, a set of one or more management consultants to the networking industry help equipment vendors, service providers and enterprises make strategic decisions, mitigate risk and affect change through business and technology consulting engagements. This approach is tailored to each client's specific issues, objectives and budget.
These consultants are leaders in the networking industry and influence its direction though confidential engagements for industry leaders and through public appearances and trade magazine articles. These interactions assure clients that they will be among the first to know of the latest industry concepts and emerging technology trends.
Each consulting engagement is unique structured—no forced methodologies or canned reports are employed. An integrated client/management consultant case team respecting and soliciting the opinions of everyone is formed for each engagement.
The present invention provides a flexible, scalable hardware and software platform that allows a service provider to easily provide internet services, virtual private network services, firewall services, etc., to a plurality of customers. This solution can be changes to provision each customer with more or less processing power and storage, according to individual changing needs.
One aspect of the present invention provides a method of delivering security services. This method includes connecting a plurality of processors 930 in a ring configuration within a first processing system, establishing a secure connection between the processors in the ring configuration across an internet protocol (IP) connection to a second processing system to form a tunnel, and providing both router services and host services for a customer using the plurality of processors in the ring configuration and using the second processing system.
In some embodiments, one or more processors In some embodiments, to support a communications network, the plurality of processors includes one or more control processors, one or more access processors, and one or more processing processors.
In some embodiments, for each of a plurality of customers, a virtual router 210 is formed in the first processing system 401 and is operably connected to a virtual router 210 formed in the second system 402.
In some embodiments, for each of a plurality of customers, a virtual private network 410 is formed using a visual router 210 formed in the first processing system 401 and operably connected to a virtual router 210 formed in the second system 402.
In some embodiments, the connecting a plurality of processors in the ring configuration includes forming dual counter rotating ring connections 933 and 934, each connecting to each of the plurality of processors 930.
Another aspect of the present invention provides a system of delivering security services. This system 201 includes a plurality of processors 230 in a ring configuration within a first processing system 401, and means for establishing a secure connection 418 between the processors in the ring configuration 411 across an internet protocol (IP) connection to a second processing system 412 to form a tunnel, and for providing both router services and host services for a customer using the plurality of processors in the ring configuration 411 and using the second processing system 412.
In some embodiments, to support a communications network, the plurality of processors includes one or more control processors, one or more access processors, and one or more processing processors.
In some embodiments, for each of a plurality of customers, a virtual router is formed in the first processing system and is operably connected to a virtual router formed in the second system.
In some embodiments of this system, for each of a plurality of customers, a virtual private network is formed using a virtual router formed in the first processing system and operably connected to a virtual router formed in the second system.
In some embodiments of this system, the plurality of processors in the ring configuration includes dual counter rotating ring connections, each connecting to each of the plurality of processors.
Yet another aspect of the present invention provides a system 201 for delivering security services. This second system 201 includes a plurality of processors within a first processing system connected in a ring configuration, and a tunnel formed using a secure connection between the processors in the ring configuration across an internet protocol (IP) connection to a second processing system, wherein both router services and host services are provided for a customer using the plurality of processors in the ring configuration and using the second processing system.
In some embodiments of this second system, to support a communications network, the plurality of processors 930 includes one or more control processors 234, one or more access processors 238, and one or more processing processors 236. In some embodiments, one or more of these processors is packaged on a blade 239.
In some embodiments of this second system, for each of a plurality of customers, a virtual router 210 is formed in the first processing system 401 and is operably connected to a virtual router 210 formed in the second system 402.
In some embodiments of this second system, for each of a plurality of customers, a virtual private network 410 is formed using a virtual router 210 formed in the first processing system 401 and operably connected to a virtual router 210 formed in the second system 410.
In some embodiments of this second system, the plurality of processors 230 in the ring configuration includes dual counter rotating ring connections 932 and 933, each connecting to each of the plurality of processors 930.
Some embodiments of this second system further include a services management system 221 that provides changeable provisioning of processor capacity among a plurality of customers.
Some embodiments of this second system further include a services management system 221 that provides firewall protection for each of a plurality of customers.
Some embodiments of this second system further include a services management system 211 that provides provisioning of processor capacity among a plurality of customers, wherein each customer's resources are isolated from those of all the other customers.
One aspect of the present invention provides a method of packet routing. The method includes connecting a plurality of processors in a network, assigning a unique processor identifier (PEID) to each of the processors, routing a first packet to a first one of the processors across the network, wherein each such packet includes a PEID value corresponding to a PEID of one of the processors, and wherein the routing to the first processor is based on the PEID value in the first packet, establishing a plurality of objects in the first processor, assigning a logical queue identifier (LQID) to a first one of the objects in the first processor, wherein each packet also includes an LQID value corresponding to an LQID of one of the objects, and routing the first packet to the first object based on the LQID value in the first packet.
Some embodiments further include assigning a plurality of different LQIDs to the first object.
Some embodiments further include routing a plurality of packets, each having a different LQID, to the first object based on the LQID value in each respective packet.
In some embodiments, the first object is associated with a virtual router (VR).
Some embodiments further include establishing the first LQID with the first object to be used for point-to-point data traffic, and establishing a second LQID with the first object to be used for shortcut data traffic.
In some embodiments, the network is configured in a ring topology.
Another aspect of the present invention provides a system for routing packets. This system includes a plurality of processors coupled to one another using a network, wherein each of the processors a unique processor identifier (PEID), wherein a first packet is routed into a first one of the processors across the network, wherein each such packet includes a PEID value corresponding to a PEID of one of the processors, and wherein the routing to the first processor is based on the PEID value in the first packet, a plurality of objects in the first processor, wherein each such object is assigned a logical queue identifier (LQID), wherein each packet also includes an LQID value corresponding to an LQID of one of the objects, and software for routing the first packet to the first object based on the LQID value in the first packet.
In some embodiments, a plurality of different LQIDs are simultaneously assigned to the first object.
In some embodiments, the means for routing includes means for routing a plurality of packets, each having a different LQID, to the first object based on the LQID value in each respective packet.
In some embodiments, the first object is associated with a virtual router (VR).
In some embodiments, the first LQID is associated with the first object to be used for point-to-point data traffic, and a second LQID is associated with the first object to be used for shortcut data traffic.
In some embodiments, the network is configured in a ring topology.
Still another aspect of the present invention provides a system for routing packets. This system includes a plurality of processors coupled to one another using a network, wherein each of the processors a unique processor identifier (PEID), wherein a first packet is routed into a first one of the processors across the network, wherein each such packet includes a PEID value corresponding to a PEID of one of the processors, and wherein the routing to the first processor is based on the PEID value in the first packet, and a plurality of objects in the first processor, wherein each such object is assigned a logical queue identifier (LQID), wherein each packet also includes an LQID value corresponding to an LQID of one of the objects, wherein the first packet is routed to the first object based on the LQID value in the first packet.
Some embodiments further include a services management system that provides changeable provisioning of processor capacity among a plurality of customers.
Some embodiments further include a services management system that provides firewall protection for each of a plurality of customers.
It is understood that the above description is intended to be illustrative, and not restrictive. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. The scope of the invention should, therefore, be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.
This application is a Continuation of U.S. application Ser. No. 09/661,636 filed on Sep. 13, 2000. This application is also related to U.S. application Ser. No. 09/661,637 filed on Sep. 13, 2000. This application is also related to U.S. Provisional Application Ser. No. 60/232,516 filed on Sep. 13, 2000 and U.S. Provisional Application Ser. No. 60/232,577 filed on Sep. 13, 2000. All of which are hereby incorporated by reference for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4667287 | Allen et al. | May 1987 | A |
| 5371852 | Attanasio et al. | Dec 1994 | A |
| 5400331 | Lucak et al. | Mar 1995 | A |
| 5442708 | Adams et al. | Aug 1995 | A |
| 5473599 | Li et al. | Dec 1995 | A |
| 5490252 | Macera et al. | Feb 1996 | A |
| 5550816 | Hardwick et al. | Aug 1996 | A |
| 5581705 | Passint et al. | Dec 1996 | A |
| 5606668 | Shwed | Feb 1997 | A |
| 5633866 | Callon | May 1997 | A |
| 5745778 | Alfieri | Apr 1998 | A |
| 5812779 | Ciscon et al. | Sep 1998 | A |
| 5825772 | Dobbins et al. | Oct 1998 | A |
| 5825891 | Levesque et al. | Oct 1998 | A |
| 5835726 | Shwed et al. | Nov 1998 | A |
| 5841973 | Kessler et al. | Nov 1998 | A |
| 5875290 | Bartfal et al. | Feb 1999 | A |
| 5963555 | Takase et al. | Oct 1999 | A |
| 5964847 | Booth et al. | Oct 1999 | A |
| 5987521 | Arrowood et al. | Nov 1999 | A |
| 6014382 | Takihiro et al. | Jan 2000 | A |
| 6014669 | Slaughter et al. | Jan 2000 | A |
| 6032193 | Sullivan | Feb 2000 | A |
| 6047330 | Stracke | Apr 2000 | A |
| 6069895 | Ayandeh | May 2000 | A |
| 6085238 | Yuasa et al. | Jul 2000 | A |
| 6098110 | Witowski et al. | Aug 2000 | A |
| 6108699 | Molin | Aug 2000 | A |
| 6118791 | Fichou et al. | Sep 2000 | A |
| 6137777 | Vaid et al. | Oct 2000 | A |
| 6147976 | Shand et al. | Nov 2000 | A |
| 6169739 | Isoyama | Jan 2001 | B1 |
| 6169793 | Godwin et al. | Jan 2001 | B1 |
| 6173333 | Jolitz et al. | Jan 2001 | B1 |
| 6173399 | Gilbrech et al. | Jan 2001 | B1 |
| 6175867 | Taghadoss | Jan 2001 | B1 |
| 6192051 | Lipman et al. | Feb 2001 | B1 |
| 6212556 | Arunachalam | Apr 2001 | B1 |
| 6220768 | Barroux | Apr 2001 | B1 |
| 6226788 | Schoening et al. | May 2001 | B1 |
| 6243580 | Garner | Jun 2001 | B1 |
| 6249519 | Rangachar | Jun 2001 | B1 |
| 6260072 | Rodriguez-Moral | Jul 2001 | B1 |
| 6260073 | Walker et al. | Jul 2001 | B1 |
| 6278708 | Von Hammerstein et al. | Aug 2001 | B1 |
| 6286038 | Reichmeyer et al. | Sep 2001 | B1 |
| 6295297 | Lee | Sep 2001 | B1 |
| 6298130 | Galvin | Oct 2001 | B1 |
| 6304975 | Shipley | Oct 2001 | B1 |
| 6320859 | Momirov | Nov 2001 | B1 |
| 6330602 | Law et al. | Dec 2001 | B1 |
| 6338092 | Chao et al. | Jan 2002 | B1 |
| 6381644 | Munguia et al. | Apr 2002 | B2 |
| 6405262 | Vogel et al. | Jun 2002 | B1 |
| 6414595 | Scrandis et al. | Jul 2002 | B1 |
| 6434619 | Lim et al. | Aug 2002 | B1 |
| 6438612 | Ylonen et al. | Aug 2002 | B1 |
| 6449650 | Westfall et al. | Sep 2002 | B1 |
| 6453406 | Sarnikowski et al. | Sep 2002 | B1 |
| 6459682 | Ellesson et al. | Oct 2002 | B1 |
| 6463061 | Rekhter et al. | Oct 2002 | B1 |
| 6466976 | Alles et al. | Oct 2002 | B1 |
| 6493349 | Casey | Dec 2002 | B1 |
| 6496935 | Fink et al. | Dec 2002 | B1 |
| 6532088 | Dantu | Mar 2003 | B1 |
| 6542466 | Pashtan et al. | Apr 2003 | B1 |
| 6549954 | Lambrecht et al. | Apr 2003 | B1 |
| 6553423 | Chen | Apr 2003 | B1 |
| 6556544 | Lee | Apr 2003 | B1 |
| 6597956 | Aziz et al. | Jul 2003 | B1 |
| 6606315 | Albert et al. | Aug 2003 | B1 |
| 6608816 | Nichols | Aug 2003 | B1 |
| 6609153 | Salkewicz | Aug 2003 | B1 |
| 6614781 | Elliott et al. | Sep 2003 | B1 |
| 6629128 | Glass | Sep 2003 | B1 |
| 6631519 | Nicholson et al. | Oct 2003 | B1 |
| 6636516 | Yamano | Oct 2003 | B1 |
| 6639897 | Shiomoto et al. | Oct 2003 | B1 |
| 6658013 | de Boer et al. | Dec 2003 | B1 |
| 6668282 | Booth et al. | Dec 2003 | B1 |
| 6674756 | Rao et al. | Jan 2004 | B1 |
| 6687220 | Ayres | Feb 2004 | B1 |
| 6697359 | George | Feb 2004 | B1 |
| 6697360 | Gai et al. | Feb 2004 | B1 |
| 6701449 | Davis et al. | Mar 2004 | B1 |
| 6738371 | Ayres | May 2004 | B1 |
| 6738821 | Wilson et al. | May 2004 | B1 |
| 6769124 | Schoening et al. | Jul 2004 | B1 |
| 6775267 | Kung et al. | Aug 2004 | B1 |
| 6775284 | Calvignac et al. | Aug 2004 | B1 |
| 6778502 | Ricciulli | Aug 2004 | B2 |
| 6802068 | Guruprasad | Oct 2004 | B1 |
| 6816462 | Booth et al. | Nov 2004 | B1 |
| 6856676 | Pirot et al. | Feb 2005 | B1 |
| 6868082 | Allen et al. | Mar 2005 | B1 |
| 6883170 | Garcia | Apr 2005 | B1 |
| 6894994 | Grob et al. | May 2005 | B1 |
| 6901517 | Redmore | May 2005 | B1 |
| 6907039 | Shen | Jun 2005 | B2 |
| 6920580 | Cramer et al. | Jul 2005 | B1 |
| 6922774 | Meushaw et al. | Jul 2005 | B2 |
| 6938095 | Basturk et al. | Aug 2005 | B2 |
| 6938097 | Vincent | Aug 2005 | B1 |
| 6944128 | Nichols | Sep 2005 | B2 |
| 6944168 | Paatela et al. | Sep 2005 | B2 |
| 6954429 | Horton et al. | Oct 2005 | B2 |
| 6982984 | Asayesh et al. | Jan 2006 | B1 |
| 6985438 | Tschudin | Jan 2006 | B1 |
| 6990103 | Gollamundi | Jan 2006 | B1 |
| 6999454 | Crump | Feb 2006 | B1 |
| 7020143 | Zdan | Mar 2006 | B2 |
| 7028333 | Tuomenoksa et al. | Apr 2006 | B2 |
| 7039053 | Freed et al. | May 2006 | B1 |
| 7042843 | Ni | May 2006 | B2 |
| 7042848 | Santiago et al. | May 2006 | B2 |
| 7058716 | Sundaresan et al. | Jun 2006 | B1 |
| 7062642 | Langrind et al. | Jun 2006 | B1 |
| 7082477 | Sadhasivam et al. | Jul 2006 | B1 |
| 7096383 | Talaugon | Aug 2006 | B2 |
| 7096495 | Warrier et al. | Aug 2006 | B1 |
| 7111072 | Matthews | Sep 2006 | B1 |
| 7116665 | Balay | Oct 2006 | B2 |
| 7116679 | Ghahremani | Oct 2006 | B1 |
| 7159031 | Larkin et al. | Jan 2007 | B1 |
| 7161904 | Hussain | Jan 2007 | B2 |
| 7174372 | Sarkar | Feb 2007 | B1 |
| 7177311 | Hussain | Feb 2007 | B1 |
| 7181547 | Millet | Feb 2007 | B1 |
| 7181766 | Bendinelli et al. | Feb 2007 | B2 |
| 7203192 | Desai | Apr 2007 | B2 |
| 7221945 | Milford et al. | May 2007 | B2 |
| 7225259 | Ho et al. | May 2007 | B2 |
| 7263106 | Matthews | Aug 2007 | B2 |
| 7266120 | Chang | Sep 2007 | B2 |
| 7272643 | Sarkar | Sep 2007 | B1 |
| 7278055 | Talaugon | Oct 2007 | B2 |
| 7293355 | Lauffer et al. | Nov 2007 | B2 |
| 7316029 | Parker et al. | Jan 2008 | B1 |
| 7324489 | Iyer | Jan 2008 | B1 |
| 7337221 | Radi et al. | Feb 2008 | B2 |
| 7340535 | Alam | Mar 2008 | B1 |
| 7376125 | Hussain | May 2008 | B1 |
| 7376827 | Jiao | May 2008 | B1 |
| 7386010 | Solomon et al. | Jun 2008 | B2 |
| 7389358 | Matthews | Jun 2008 | B1 |
| 7463633 | Endo et al. | Dec 2008 | B2 |
| 8068503 | Desai et al. | Nov 2011 | B2 |
| 8107376 | Balay et al. | Jan 2012 | B2 |
| 8208409 | Millet | Jun 2012 | B2 |
| 8213347 | Balay et al. | Jul 2012 | B2 |
| 20010028636 | Skog et al. | Oct 2001 | A1 |
| 20010043571 | Jang et al. | Nov 2001 | A1 |
| 20010048661 | Clear et al. | Dec 2001 | A1 |
| 20010052013 | Munguia et al. | Dec 2001 | A1 |
| 20020062344 | Ylonen et al. | May 2002 | A1 |
| 20020066034 | Schlossberg et al. | May 2002 | A1 |
| 20020075901 | Perlmutter et al. | Jun 2002 | A1 |
| 20020097672 | Barbas et al. | Jul 2002 | A1 |
| 20020099849 | Alfieri et al. | Jul 2002 | A1 |
| 20020126672 | Chow et al. | Sep 2002 | A1 |
| 20020152373 | Sun | Oct 2002 | A1 |
| 20020186661 | Santiago et al. | Dec 2002 | A1 |
| 20020188657 | Traversat et al. | Dec 2002 | A1 |
| 20020188711 | Meyer et al. | Dec 2002 | A1 |
| 20020191604 | Mitchell et al. | Dec 2002 | A1 |
| 20030033401 | Poisson et al. | Feb 2003 | A1 |
| 20030043792 | Carpini et al. | Mar 2003 | A1 |
| 20030081559 | Matuoka et al. | May 2003 | A1 |
| 20030091021 | Trossen et al. | May 2003 | A1 |
| 20030108041 | Aysan | Jun 2003 | A1 |
| 20030115308 | Best et al. | Jun 2003 | A1 |
| 20030117954 | De Neve et al. | Jun 2003 | A1 |
| 20030131228 | Twomey | Jul 2003 | A1 |
| 20030169747 | Wang | Sep 2003 | A1 |
| 20030185221 | Deikman et al. | Oct 2003 | A1 |
| 20030185226 | Tang et al. | Oct 2003 | A1 |
| 20030200295 | Roberts et al. | Oct 2003 | A1 |
| 20030212735 | Hickok et al. | Nov 2003 | A1 |
| 20030223406 | Balay | Dec 2003 | A1 |
| 20030223418 | Desai et al. | Dec 2003 | A1 |
| 20030223456 | DiMambro | Dec 2003 | A1 |
| 20040006601 | Bernstein et al. | Jan 2004 | A1 |
| 20040042416 | Ngo et al. | Mar 2004 | A1 |
| 20040078772 | Balay | Apr 2004 | A1 |
| 20040095932 | Astarabadi et al. | May 2004 | A1 |
| 20040095934 | Cheng et al. | May 2004 | A1 |
| 20040141521 | George | Jul 2004 | A1 |
| 20040160900 | Lund et al. | Aug 2004 | A1 |
| 20040199567 | Lund | Oct 2004 | A1 |
| 20040199568 | Lund | Oct 2004 | A1 |
| 20040199569 | Kalkunte et al. | Oct 2004 | A1 |
| 20050047407 | Desai | Mar 2005 | A1 |
| 20050188106 | Pirbhai et al. | Aug 2005 | A1 |
| 20050213589 | Shih | Sep 2005 | A1 |
| 20060087969 | Santiago et al. | Apr 2006 | A1 |
| 20060140185 | Norman et al. | Jun 2006 | A1 |
| 20060265519 | Millet | Nov 2006 | A1 |
| 20070058648 | Millet | Mar 2007 | A1 |
| 20070064704 | Balay | Mar 2007 | A1 |
| 20070073733 | Matthews | Mar 2007 | A1 |
| 20070083528 | Matthews | Apr 2007 | A1 |
| 20070104119 | Sarkar | May 2007 | A1 |
| 20070109968 | Hussain | May 2007 | A1 |
| 20070110062 | Balay | May 2007 | A1 |
| 20070127382 | Hussain | Jun 2007 | A1 |
| 20070147368 | Desai | Jun 2007 | A1 |
| 20070291755 | Cheng et al. | Dec 2007 | A1 |
| 20080013470 | Kopplin | Jan 2008 | A1 |
| 20080016389 | Talaugon | Jan 2008 | A1 |
| 20080117917 | Balay | May 2008 | A1 |
| 20090225759 | Hussain et al. | Sep 2009 | A1 |
| 20120057460 | Hussain | Mar 2012 | A1 |
| 20120069850 | Desai | Mar 2012 | A1 |
| 20120072568 | Matthews | Mar 2012 | A1 |
| 20120099596 | Balay et al. | Apr 2012 | A1 |
| 20120131215 | Balay et al. | May 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| 0051290 | Aug 2000 | WO |
| 0076152 | Dec 2000 | WO |
| 0163809 | Aug 2001 | WO |
| 0223855 | Mar 2002 | WO |
| 0310323 | Dec 2003 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20070121579 A1 | May 2007 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 09661636 | Sep 2000 | US |
| Child | 11530901 | US |
