Patent Grant
8332929
The invention relates to systems and processes for enforcing and monitoring a configuration management process for configurable elements in configurable computational systems.
Mechanisms currently exist for the management of configurable systems. These systems, referred to as Change/Configuration Management System (CMS) or Ticketing Systems define a business process or rules for making configuration changes. The configuration changes at issue are changes to configurable computation systems (CCS), which can be coupled together over a network or through other communication means. These CCSs can include but are not limited to servers, desktop system, personal computers, directory servers, database servers, work stations, programmable factory equipment, PDAs, cell phones, microchip, software, network devices, and virtual machines. Configuration change includes but not limited to content changes for files, permission changes on files, file creation, file deletion, registry key creation, registry key deletion, registry value changes, environment variable creation, environment variable deletion, environment variable value changes, virtual machine creation, virtual machine deletion, virtual machine restart, virtual machine settings changes, network configuration change, database settings changes and database data changes. With a CCS, a configuration change may effect one or more configurable elements (CEs). These CEs include but are not limited to files within a file system, registry settings, environment variables, databases, virtual machine settings, networked device configuration parameters, computationally controlled mechanical switches, and electronically controlled valve settings.
While using a CMS system defines a business process for making and managing changes to CCSs and the corresponding CEs, the CMS system does not automatically enforce, control, or monitor such changes. Human discipline, monitoring, encouragement, and other incentives have to be used to enforce a configuration management process. Thus, a system enforced by human implementation is subject to human nature and human imperfection. People will work around the system. Alternatively, due to human nature, error, or misunderstanding changes are made outside of the defined process, such as making changes at inappropriate times, or making other improper changes.
What is need is method and apparatus for automatically enforcing a defined process for making changes to a CE within a CCS, or monitoring the changes in a CCSs or CEs in relations to a define configuration management processes.
The invention allows for the enforcement and monitoring of a configuration management process as applied to configurable elements (CEs) within a configurable computing system (CCSs). Changes to CEs within CCSs are controlled by a selectable lock that only enable changes to the CEs when the rules for the change management process is met. Also, the invention provides a less restrictive configuration management process where changes are monitored and reconciled against configuration change requests and change authorization rules.
In a first aspect of the invention, a method of automatically enforcing a configuration change process for one or more configuration change requests to one or more configurable elements within a single or multiple configurable computational elements is disclosed. The method involves the steps of accessing the change process rules, analyzing the configuration change requests utilizing the rules, selectively authorizing the configuration changes to the configurable elements for the configurable elements that comply with the change process rules for the respective change request, and selectively enabling a lock to allow configuration changes on a configurable computational system containing the configurable elements. The analysis of the configuration change request can be based on the state of the configuration change request which can include external authorizations. The state of the external authorizations can be evaluated with the accessed change process rules. The selective authorization is based on the state of the configuration change request being evaluated utilizing the accessed change process rules.
In one embodiment, the analyzing of the configuration change request further utilizes current conditions in the determination of the selective authorization of configuration changes of CEs. These current conditions can include but are not limited to the current time, date, day of the week, and any electronically retrievable value representing a level or quantity such as an inventory value, and the mechanical state of a switch or valve.
In another embodiment of the invention, the configuration of the selective locks involves the authenticating the selective authorization of the configuration change of the configurable elements. Preferable, the authentication can be performed by an SSL key exchange.
In a further embodiment of the invention, the selective locks generate status information related to configuration changes in the CEs for the corresponding CCSs. The status information can include but is not limited to the status of the CE configuration change, whether the changes succeed or failed, and information relating to the failure of the configuration change.
In another embodiment of the present invention the status information is associated with configuration change request. The status change request can further be associated with the corresponding CEs. Further, an association can be made with the CCS, successful configuration changes, failed configuration changes, or the information regarding the failure of the configuration change.
In a further embodiment, the associated information is used to generate reports of at least the status of the configuration change requests, the changes to the CE, the configuration changes to the CCS.
In a second aspect of the present invention, a system for automatically enforcing a configuration change process for one or more configurable element (CE) within a configurable computation system (CCS) is disclosed. The system is comprised of means for managing a configuration change process for CEs within CCSs, means for generating a configuration change request, means for applying one or more configuration change rules to a configuration change request to generate a selective configuration change authorization of the one or more CEs, and means for selectively locking configuration changes in a CCS wherein the means for locking can selectively enable configuration changes to the one or more CE based on the selective configuration authorization. The means for managing a configuration change process can include standard configuration management systems (CMSs) which can also be referred to as ticketing systems. These CMS systems receive requests for a configuration change which then generate a configuration change ticket. Before a fully authorized ticket is generated, various authorization inputs are required. These inputs define a configuration management process to be followed. The means for applying authorization rules generates selective configuration authorization for one or more CEs based on configuration change authorization.
In one embodiment, wherein the means for applying the one or more configuration change rules further includes utilizing current conditions in the determination of the selective authorization of configuration changes of CEs. These current conditions can include but are not limited to the current time, date, day of the week, any electronically retrievable value representing a level or quantity such as an inventory value, and mechanical state of a switch or valve.
In another embodiment of the invention, the means for locking and unlocking the configuration includes authenticating the selective authorization of the configuration change of the CE. Preferable, the authentication can be performed by an SSL key exchange.
In a further embodiment of the invention, the means for selectively locking configuration changes in a CCS generates status information related to configuration changes in the configurable elements for the corresponding CCSs. The status information can include but is not limited to a change of configuration status of a CE, whether the change succeed or failed, and information relating to the failure cause of the configuration change.
In another embodiment of the present invention further comprises means for associating the status information with the configuration change request. The status information and change request can further be associated with the corresponding CEs. Further, associations can be made with elements including the CCSs, successful configuration changes, failed configuration changes, or the information regarding the failure of the configuration change.
In a further embodiment, the means for applying the one or more authorization rules generates reports comprising the associated status information, the configuration change requests, the configuration changes to the CE, the configuration changes to the CCS.
In another aspect of the present invention, a system for automatically monitoring a configuration change process for one or more CE within a CCS. The system is comprised of a means for selectively monitoring configuration changes to one or more CEs within a CCS, a means for managing a configuration change, and a means for processing the configuration change status information. The means for selectively monitoring configuration changes generates configuration change status information. The means for managing a configuration change process generates one or more configuration change requests. Further, the means for processing utilizes the configuration change status information, the one or more configuration change requests, and the one or more configuration change rules for the CEs. The processing associates the configuration changes with the configuration change requests and determines if the configuration changes complied with the one or more associated configuration change rules.
In one embodiment of the invention, the means for processing can include current conditions as part of the analysis. In another embodiment, the invention further comprises a means for generating reports where the configuration change status information is associated with at least one of the CE and the CCS.
In another aspect of the invention, a method of automatically monitoring a configuration change process for one or more configuration change requests to one or more CEs within at least one CCS is disclosed. The steps are comprised of generation configuration stat change information from a CCS and corresponding to on or more CEs, accessing one or more configuration change rules where the rules are associated with a configuration change to one or more CEs within a CCS. In one embodiment of the invention, the means for processing can include one or more current conditions as part of the analysis.
The invention is better understood by reading the following detailed description of an exemplary embodiments in conjunction with the accompanying drawings.
The following description of the invention is provided as an enabling teaching of the invention in its best, currently known embodiment. Those skilled in the relevant art will recognize that many changes can be made to the embodiment described, while still obtaining the beneficial results of the present invention. It will also be apparent that some of the desired benefits of the present invention can be obtained by selecting some of the features of the present invention without utilizing other features. Accordingly, those who work in the art will recognize that many modifications and adaptations to the present inventions are possible and can even be desirable in certain circumstances, and are a part of the present invention. Thus, the following description is provided as illustrative of the principles of the present invention and not in limitation thereof, since the scope of the present invention is defined by the claims.
The illustrative embodiments of the invention provide the means for enforcing, monitoring and reconciling a business management process for making configuration changes to configurable systems. The benefits of such a system are numerous. First, in the enforcement mode, configuration changes to configurable system such as servers, factory controllers, office automation systems can be controlled to prevent problems not limited to, loss of productivity because of down time at inappropriate times, and quality and performance issues caused by operations running with an improper configuration. Further, with Sarbanes-Oxley the regulatory environment demands stronger control over financial systems. Thus, being able to control changes to financial systems such as software packages and databases gives an organization higher confidence that business critical process are being followed and unauthorized changes are not made.
An illustrative embodiment of the present invention is shown in
The CMS 110 is used for generating a configuration change(s) authorization for one or more CEs 135 within one or more CCSs 130 according to a specific business process. Preferably the CMS 110 is configured with the change authorization requirements. For example, to authorize a change can require the authorization by two senior officers of a company. Input to the CCS 110 is a configuration change request 112 preferably corresponding to a configuration change to one or more CEs 135 within one or more CCSs 130. The change request 112 preferably generates a change ticket that requires authorizations before authorized implementation. Preferably, the change ticket is stored in the change ticket database 116. The change ticket database 116 stores information related to the authorization and completion of the configuration change request. The ticket can include authorization fields, and implementation status fields. Preferably, authorizations for the change ticket can be provided by an operator input(s) 114 or other automated means such as electronic inputs from other electronic devices (not shown) coupled to the CMS 110. If all of the configuration change rules are met, the change ticket is authorized notification is given to the analytics module 120. Preferably, the change tickets are stored in a change ticket database 116 contained within or coupled to the CMS 110. Thus, the CMS 110 and change ticket database 116 may contain a number of configuration change requests, in varying stages of authorization and implementation. The CMS 110 can be a separate server, a process running on a server with other applications, or running an application on a personal computer. The change ticket data 116 base can be networked and can be directly or indirectly accessible by the analytics module 120 over the network.
An analytics module 120 is coupled to the CMS 110. The analytics module 120 enforces the configuration change process of the CMS 110 by configuring the selectable configuration locks 132 on the CCSs 130 to selectively enable or disable configuration changes to the CEs 135. The analytics module 120 receives configuration change rules. These configuration change rules are associated with the one or more CCSs 130 and the one or more CEs 135 within a CCS 130. The configuration change rules are configured through the rule input 112, which is preferably coupled to the analytics module 120. Also, contemplated are configuration rules received from other sources. Alternatively, the configuration change rules can be read directly from the CMS 110, derived from information retrieved from the CMS 110, or through another source (not shown) coupled to the analytics module 120. The analytics module 120, receives configuration change ticket information from the CMS 110. Preferably, the configuration change ticket information can be either requested from the CMS 110. However, the information can automatically be sent by the CMS 110 to the analytics module 120. Also contemplated by the invention is the analytics module 120 directly accessing the change ticket database 116. The configuration change ticket is preferably processed according to rules specified during the rule input 122 to determine if all the criteria for the configuration change process for an associated CEs 135 or an associated CCS 130 are being met. Also contemplated are one or more subsets of the CEs 135 meeting the configuration change process rules and the configuration change authorization being limited to these CEs 135. Preferably, the subset of CEs meeting the configuration change rule criteria will be authorized for making the configuration change. If all the criteria of the rules are met, then the analytics module 120 authorizes configuration changes the CEs 135. Also contemplated is a means to bypass the rules for generation an authorization in emergency situations.
Optionally, the configuration authorizing rules used by the analytics module 120 can include current conditions 126 in the determination for the authorization for the configuration changes to the CE. Exemplary of a current condition is the current time, date, and the day of the week. Preferably, if the authorizing rules criteria are met but the current conditions are not met, the authorization of the configuration change can be delayed until the time, day of the week, or date condition is met. Also, contemplated is the sending of a message to the selective configuration lock 132 containing a time window during which configuration changes are enabled. Another illustrative use of current conditions is the checking an inventory and requiring that a specified inventory level be available before authorizing a configuration change that would increase the production rate of an item.
When the configuration change authorization for all or some of the CEs 135 is met, the analytics module 120 will send a selective authorization message to a selective configuration lock 132 on the corresponding CCS 130 for the CEs 135 to be changed. The message will cause the selective configuration lock 132 to enable changes to the selective CEs. The message can be sent over a network where the analytics module 120 and the CCS 130 are located on separate systems remote from one another. The disabling of configuration changes to the CEs can be based on time, the completion of the configuration change to the CE, or by a message from the analytics module 120. Alternatively, the analytics module 120 can be a process or subroutine operating within the same processing system as the CCS 130 where the configuration authorization message is sent through inter-process communication means.
The analytics module 120 can receive status information from the selective configuration locks 132 regarding the occurrence of the success or failure of a configuration change, and the reasons for failure. This status information is stored in a change database 125. The change database 125 can later be used to generate reports regarding the status of the success configuration changes and change tickets. The analytics module 120 can associate status changes into groups based on type of configuration change, failed changes, and failure status information. Further the analytics module 120 can associate the changes with the configuration ticket database 116 to reconcile configuration change requests. As part of the reconciliation, information can be passed from the analytics module 120 to the CMS 110 to automatically update the status information for the associated change ticket indicating the final result of the configuration change.
The CCS 130 is coupled with the analytics module 120 preferably through a network. The CCS 130 contains one or more CEs 135. The CCS 130 also includes a selective lock 132 which is configured to prevent changes to the CEs 135 unless enabled by the analytics module 120. Preferably, the selective enabling of the selective configuration lock 132 contains a time window during which the enabled configuration changes can be made. The time window can vary by each configuration change for each CE 135. It can be desirable that the configuration changes to the CEs 135 are performed in a specific order. Having non-overlapping time windows for each enabled CE 135 configuration change can enforce such a sequence. Further information regarding the operation of the selective configuration locks 132 can be found in the co-owned application Ser. No. 11/346,741 titled “Enforcing Automatic Opening and Closing of an Existing Workflow” which is incorporated by reference. In general, the selective configuration lock 132 can be a hook into the file system driver of the CCS 130 to monitor and control changes to files associated with the CEs 135 and further associated with the configuration change ticket resulting from a change request 112. The selective configuration lock 132 can also include catching and monitoring triggers caused by a database modification. The selective configuration lock 132 can generate information regarding the status of a configuration change to a CE 135. This information can include whether the configuration change succeeded or failed. Further, the information can include information regarding why the change failed. This can include but is not limited to, incompatible operating system, insufficient memory to do the change, and insufficient permission to access a file. Preferably, information generated by the selective lock 132 is sent to the analytics module 120 but alternatively can be sent directly to the change database 125 for later processing, reference, and report generation. Configuration changes 140 to the CEs 135 preferably do not come from the analytics module 120 but are made directly to the CCS 130 or alternatively over a network. Exemplary of this process would be the loading of an updated application where the application files are the CEs 135 to be changed.
To prevent monitoring or unauthorized control over the selective configuration locks 132, the communication between the analytics module 120 and the selective configuration locks 132 can be encrypted and authenticated. Any authentication and encryption techniques can be used. Preferably the authentication and encryption technique uses a secure socket layer (SSL) using SSL key exchange to authenticate the selective enabling of the selective configuration lock.
The information generated by the selectable configuration lock 132, preferably stored in the change database 125, can be used to generate a variety of reports. First, the information can be used to reconcile the change ticket database 116 with the changes made to the CEs 135 and thus generating change compliance reports. Further, compliance reports can be organized by but not limited to user, CCS 130, CE 135, time, and type of change.
A second illustrative embodiment of the present invention is shown in
The CMS 110 is used for generating an configuration changes(s) authorization for one or more CEs 135 within one or more CCSs 130 according to a specific business process. The operation of the CMS 110, the configuration change request 112 input to the CMS 110, the operator input 114, and the storage of the change request in the change ticket database 116, is the same as previously described for
An analytics module 220 is coupled to the CMS 110. The analytics module 220 is a post configuration change analysis tool that analyzes changes in the change ticket database 116 according to configuration change rules input into the analytics module 220, and determines at least which configuration changes complied with the change process rules, which changes did not comply with the rules, configuration change made without an associated configuration change request, which change tickets were not completed, and reasons that the configuration changes failed. The configuration change rules preferably can be configured into the analytics module 220 from the rule input 122 but can be received from other sources. Alternatively, the configuration change rules can be acquired directly from the CMS 110, derived from information retrieved from the CMS 110, or through a source (not shown) coupled to the analytics module 220. The analytics module 220, can receive configuration change request information from the CMS 110. Preferably, the analytics module 220 directly accesses the change ticket database 116. The CMS 110 can signal the analytics module 220 when a change has occurred to the change ticket database 116.
Also contemplated by the invention is a report 124 interface for an operator requesting and receiving reports related to, reconciling the change ticket database 116 and the information in the change database 125 to determine what configuration changes were made, determining which changes were made conforming to within the configuration change process, and which changes were made outside the configuration change process. Preferably, the configuration change ticket information is requested directly from the change ticket database 116 or from the CMS 110 alternatively after the configuration changes are made to the CEs 135 within a CCS 130. However, the change ticket information can automatically be sent by the CMS 110 to the analytics module 220, stored and processed when reconciliation reports are generated. During analysis of the change ticket database 116 and the change database 125, the configuration change ticket is preferably processed according to rules input by the rules input 122 to determine if all the criteria for configuration change process for the associated CEs 135 are met. Also contemplated is analysis and reporting on an individual CE 135 basis or on a CCS basis.
Optionally, the configuration authorizing rules used by the analytics module 120 can include current conditions 126 in analyzing the configuration changes to the CEs. Exemplary of a current condition is the current time and the day of the week. If the analytics module 220 are to use the current conditions, then the change information stored in the change database 125 must include current condition information. It is contemplated that the current condition information is provided by the analytics module 220 or that the configuration change monitor 232 provides this information.
Information sent between the analytics module 220 and the CMS 110, the configuration change monitor 232 and the CMS 110 can be sent over a network. Alternatively, the analytics module 220 can be a process or subroutine operating within the same processing system as the CCS 130 where communication is provided through inter-process or processor communication means.
The analytics module 220 is configured to receive status information from the CCS 130 sent by the configuration change monitor 232 regarding the occurrence of a configuration change, status regarding a failure of an attempted configuration changes, and status regarding a successful configuration change. This information can be stored in a change database 125. The change database 125 can later be utilized to generate reports reconciling the change ticket database 116 and the change database 125. As discussed for
The CCS 130 is coupled with the analytics module 220, preferably through a network. The CCS 130 contains one or more CEs 135. The CCS 130 also includes a configuration change monitor 232 which is configured to monitor changes to the CEs 135. Preferably, the change monitor 232 has access to the current conditions, such as date and time so that this information can be tagged to the status information generated. The status information which is generated can be sent as generated to the analytics module 220 or preferably directly to the change database 125. Also, contemplated is the ability of the change monitor 232 to store change information for later transfer to the analytics module 220 or change database 125. In general, the change monitor 232 can be a driver that is coupled to the file system of the CCS 130 to monitor and control changes to files associated with the CEs 135. The change monitor 232 can also include but is not limited to monitoring triggers generated by a database modification. The change monitor 232 can generate information regarding the status of a configuration change to a CE 135. This information can include whether the configuration change succeeded or failed. Further, when the change fails the information can include information regarding why the change failed. This can include but is not limited to, incompatible operating system, insufficient memory to do the change, and insufficient permission to access a file. Preferably, information generated by the selective lock 132 is sent to the analytics module 120 but alternatively or additionally can be sent directly to the change database 125 for later processing, reference, and report generation. Configuration changes 140 to the CEs 135 preferably do not come from the analytics module 120 but are made directly to the CCS 130 or over the network. Exemplary of this process is loading of an updated application where the application files are the CEs 135 to be changed.
A secure and authenticate channel can be used to communicated between the analytics module 220 and the change monitor 232. Any authentication and securing method can be implemented. Preferably the authentication scheme uses SSL (secure socket layer) using SSL key exchange to authenticate the analytic module 130.
The information generated by the change monitor 232, preferably stored in the change database 125, can be used to generate a variety of reports. First, the information can be used to reconcile the change ticket database with the changes made to the CEs 135 and thus generating change compliance reports. Further, compliance reports can be organized by user, system, type of configurable element, time, and type of change.
In a step 320, the information associated with the configuration change request is analyzed using the rules associated with the CEs and CCS effected by the configuration change request. As part of the analysis, external conditions can be utilized. These include conditions like the current time of day, the date, and the day of the week. The analysis can find that some, none, or all of the associated CE have conformed to the rules for a configuration change.
In a step 330, configuration changes are selectively authorized for the CEs within the CCSs corresponding to the configuration change request. The authorization is based on analysis of the configuration change request and the configuration change rules. The authorization is communicated to at least one selective-lock which is used to provide selective enabling of configuration changes to the associated CEs. The communication is preferably over a network but other means are contemplated. Also, contemplated are secure authenticated communications. SSL (secure socket layer) can be used to secure encrypted the communications and authenticated by the use of SSL keys exchange.
In a step 340, one or more selective locks corresponding to one or more CCSs are configured to selectively allow configuration changes to the selectively authorized CEs. The selective enabling of CE configuration changes is based upon the selective authorizations generated in the step 330.
In a step 350, the selective locks generate status information regarding configuration changes made to enabled CEs. This status information can include information about but not limited to when the change was made, whether the change succeeded or failed, and reasons for the success or failure. This information can be stored for later transmission to a central collection point, such as a database for later analysis and report generation. Also contemplated by the invention is the transmission of the status information over a network and through other processing elements before storage.
In a step 360, reports are generated based on the stored status information and the configuration change requests. The report generation can associate the status information with the associated configuration change request. Further, the report generation can associate the status information with the CE, CCS, or a combination of these.
In the step 420, the change configuration rules associated with the CEs corresponding to the status information generated in step 410 are identified. The one or more configuration change rules associated with a CE can be a subset of a larger set of rules. An exemplary embodiment of these rules is the requirement for authorization by specific people, the availability of inventory, and performing a configuration change in a specified time window and on a specified day or day of the week.
In a step 430, the information associated with the state of a configuration change request, the change ticket, is analyzed using the identified rules associated with the CEs and CCS and the associated status information generated in step 410. The change request state information or change ticket status information can be stored in a change ticket database. Part of the analysis, external conditions can be used. These include conditions like the current time of day, the date, and the day of the week. The analysis can determine that some, none, or all of the associated CE have conformed to the configuration change rules. Further, the processing determines whether there was a change configuration request. The results of such an analysis is saved in a form and structure such that the data can be used in the generation of reports associating status information with configuration change requests, CEs and CCSs.
In a step 440, reports are generated based on the stored status information and the configuration change requests. The report generation can associate status information with the associated configuration change. Further, the report generation can associate the status information with the CE, CCS, or a combination of these.
This application is a non-provisional which claims priority under 35 U.S.C. §119(e) of the co-owned U.S. Provisional Patent Application Ser. No. 60/879,826, filed Jan. 10, 2007, and entitled “SOFTWARE THAT MESSAGES CHANGE CONTROL” The Provisional Patent Application Ser. No. 60/879,826 filed Jan. 10, 2007, and entitled “SOFTWARE THAT MESSAGES CHANGE CONTROL” is also hereby incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4688169 | Joshi | Aug 1987 | A |
| 4982430 | Frezza et al. | Jan 1991 | A |
| 5155847 | Kirouac et al. | Oct 1992 | A |
| 5222134 | Waite et al. | Jun 1993 | A |
| 5390314 | Swanson | Feb 1995 | A |
| 5521849 | Adelson et al. | May 1996 | A |
| 5560008 | Johnson et al. | Sep 1996 | A |
| 5699513 | Feigen et al. | Dec 1997 | A |
| 5778349 | Okonogi | Jul 1998 | A |
| 5787427 | Benantar et al. | Jul 1998 | A |
| 5842017 | Hookway et al. | Nov 1998 | A |
| 5907709 | Cantey et al. | May 1999 | A |
| 5974149 | Leppek | Oct 1999 | A |
| 5987610 | Franczek et al. | Nov 1999 | A |
| 5987611 | Freund | Nov 1999 | A |
| 5991881 | Conklin et al. | Nov 1999 | A |
| 6073142 | Geiger et al. | Jun 2000 | A |
| 6141698 | Krishnan et al. | Oct 2000 | A |
| 6192401 | Modiri et al. | Feb 2001 | B1 |
| 6192475 | Wallace | Feb 2001 | B1 |
| 6256773 | Bowman-Amuah | Jul 2001 | B1 |
| 6275938 | Bond et al. | Aug 2001 | B1 |
| 6338149 | Ciccone, Jr. et al. | Jan 2002 | B1 |
| 6356957 | Sanchez, II et al. | Mar 2002 | B2 |
| 6393465 | Leeds | May 2002 | B2 |
| 6442686 | McArdle et al. | Aug 2002 | B1 |
| 6449040 | Fujita | Sep 2002 | B1 |
| 6453468 | D'Souza | Sep 2002 | B1 |
| 6460050 | Pace et al. | Oct 2002 | B1 |
| 6587877 | Douglis et al. | Jul 2003 | B1 |
| 6662219 | Nishanov et al. | Dec 2003 | B1 |
| 6748534 | Gryaznov et al. | Jun 2004 | B1 |
| 6769008 | Kumar et al. | Jul 2004 | B1 |
| 6769115 | Oldman | Jul 2004 | B1 |
| 6795966 | Lim et al. | Sep 2004 | B1 |
| 6832227 | Seki et al. | Dec 2004 | B2 |
| 6834301 | Hanchett | Dec 2004 | B1 |
| 6847993 | Novaes et al. | Jan 2005 | B1 |
| 6907600 | Neiger et al. | Jun 2005 | B2 |
| 6918110 | Hundt et al. | Jul 2005 | B2 |
| 6930985 | Rathi et al. | Aug 2005 | B1 |
| 6934755 | Saulpaugh et al. | Aug 2005 | B1 |
| 6988101 | Ham et al. | Jan 2006 | B2 |
| 6988124 | Douceur et al. | Jan 2006 | B2 |
| 7010796 | Strom et al. | Mar 2006 | B1 |
| 7024548 | O'Toole, Jr. | Apr 2006 | B1 |
| 7039949 | Cartmell et al. | May 2006 | B2 |
| 7065767 | Kambhammettu et al. | Jun 2006 | B2 |
| 7069330 | McArdle et al. | Jun 2006 | B1 |
| 7082456 | Mani-Meitav et al. | Jul 2006 | B2 |
| 7093239 | van der Made | Aug 2006 | B1 |
| 7124409 | Davis et al. | Oct 2006 | B2 |
| 7139916 | Billingsley et al. | Nov 2006 | B2 |
| 7152148 | Williams et al. | Dec 2006 | B2 |
| 7159036 | Hinchliffe et al. | Jan 2007 | B2 |
| 7177267 | Oliver et al. | Feb 2007 | B2 |
| 7203864 | Goin et al. | Apr 2007 | B2 |
| 7251655 | Kaler et al. | Jul 2007 | B2 |
| 7290266 | Gladstone et al. | Oct 2007 | B2 |
| 7302558 | Campbell et al. | Nov 2007 | B2 |
| 7330849 | Gerasoulis et al. | Feb 2008 | B2 |
| 7346781 | Cowle et al. | Mar 2008 | B2 |
| 7350204 | Lambert et al. | Mar 2008 | B2 |
| 7353501 | Tang et al. | Apr 2008 | B2 |
| 7363022 | Whelan et al. | Apr 2008 | B2 |
| 7370360 | van der Made | May 2008 | B2 |
| 7406517 | Hunt et al. | Jul 2008 | B2 |
| 7441265 | Staamann et al. | Oct 2008 | B2 |
| 7464408 | Shah et al. | Dec 2008 | B1 |
| 7506155 | Stewart et al. | Mar 2009 | B1 |
| 7506170 | Finnegan | Mar 2009 | B2 |
| 7546333 | Alon et al. | Jun 2009 | B2 |
| 7607170 | Chesla | Oct 2009 | B2 |
| 7657599 | Smith | Feb 2010 | B2 |
| 7685635 | Vega et al. | Mar 2010 | B2 |
| 7698744 | Fanton et al. | Apr 2010 | B2 |
| 7757269 | Roy-Chowdhury et al. | Jul 2010 | B1 |
| 7809704 | Surendran et al. | Oct 2010 | B2 |
| 7836504 | Ray et al. | Nov 2010 | B2 |
| 7908653 | Brickell et al. | Mar 2011 | B2 |
| 7937455 | Saha et al. | May 2011 | B2 |
| 8015563 | Araujo et al. | Sep 2011 | B2 |
| 20020069367 | Tindal et al. | Jun 2002 | A1 |
| 20020083175 | Afek et al. | Jun 2002 | A1 |
| 20020099671 | Mastin Crosbie et al. | Jul 2002 | A1 |
| 20030014667 | Kolichtchak | Jan 2003 | A1 |
| 20030023736 | Abkemeier | Jan 2003 | A1 |
| 20030033510 | Dice | Feb 2003 | A1 |
| 20030073894 | Chiang et al. | Apr 2003 | A1 |
| 20030074552 | Olkin et al. | Apr 2003 | A1 |
| 20030120601 | Ouye et al. | Jun 2003 | A1 |
| 20030120811 | Hanson et al. | Jun 2003 | A1 |
| 20030120935 | Teal et al. | Jun 2003 | A1 |
| 20030145232 | Poletto et al. | Jul 2003 | A1 |
| 20030163718 | Johnson et al. | Aug 2003 | A1 |
| 20030167399 | Audebert et al. | Sep 2003 | A1 |
| 20040003258 | Billingsley et al. | Jan 2004 | A1 |
| 20040015554 | Wilson | Jan 2004 | A1 |
| 20040051736 | Daniell | Mar 2004 | A1 |
| 20040054928 | Hall | Mar 2004 | A1 |
| 20040143749 | Tajalli et al. | Jul 2004 | A1 |
| 20040167906 | Smith et al. | Aug 2004 | A1 |
| 20040230963 | Rothman et al. | Nov 2004 | A1 |
| 20040243678 | Smith | Dec 2004 | A1 |
| 20040255161 | Cavanaugh | Dec 2004 | A1 |
| 20050018651 | Yan et al. | Jan 2005 | A1 |
| 20050108516 | Balzer et al. | May 2005 | A1 |
| 20050108562 | Khazan et al. | May 2005 | A1 |
| 20050114672 | Duncan et al. | May 2005 | A1 |
| 20050228990 | Kato et al. | Oct 2005 | A1 |
| 20050235360 | Pearson | Oct 2005 | A1 |
| 20050257207 | Blumfield et al. | Nov 2005 | A1 |
| 20050260996 | Groenendaal | Nov 2005 | A1 |
| 20050262558 | Usov | Nov 2005 | A1 |
| 20050273858 | Zadok et al. | Dec 2005 | A1 |
| 20050283823 | Okajo et al. | Dec 2005 | A1 |
| 20060004875 | Baron et al. | Jan 2006 | A1 |
| 20060015501 | Sanamrad et al. | Jan 2006 | A1 |
| 20060037016 | Saha et al. | Feb 2006 | A1 |
| 20060080656 | Cain et al. | Apr 2006 | A1 |
| 20060101277 | Meenan et al. | May 2006 | A1 |
| 20060133223 | Nakamura et al. | Jun 2006 | A1 |
| 20060136910 | Brickell et al. | Jun 2006 | A1 |
| 20060136911 | Robinson et al. | Jun 2006 | A1 |
| 20060195906 | Jin et al. | Aug 2006 | A1 |
| 20060236398 | Trakic et al. | Oct 2006 | A1 |
| 20070011746 | Malpani et al. | Jan 2007 | A1 |
| 20070039049 | Kupferman et al. | Feb 2007 | A1 |
| 20070050764 | Traut | Mar 2007 | A1 |
| 20070074199 | Schoenberg | Mar 2007 | A1 |
| 20070083522 | Nord et al. | Apr 2007 | A1 |
| 20070101435 | Konanka et al. | May 2007 | A1 |
| 20070136579 | Levy et al. | Jun 2007 | A1 |
| 20070169079 | Keller et al. | Jul 2007 | A1 |
| 20070192329 | Croft et al. | Aug 2007 | A1 |
| 20070220061 | Tirosh et al. | Sep 2007 | A1 |
| 20070253430 | Minami et al. | Nov 2007 | A1 |
| 20070271561 | Winner et al. | Nov 2007 | A1 |
| 20080005737 | Saha et al. | Jan 2008 | A1 |
| 20080005798 | Ross | Jan 2008 | A1 |
| 20080010304 | Vempala et al. | Jan 2008 | A1 |
| 20080034416 | Kumar et al. | Feb 2008 | A1 |
| 20080052468 | Speirs et al. | Feb 2008 | A1 |
| 20080120499 | Zimmer et al. | May 2008 | A1 |
| 20080163207 | Reumann et al. | Jul 2008 | A1 |
| 20080184373 | Traut et al. | Jul 2008 | A1 |
| 20080294703 | Craft et al. | Nov 2008 | A1 |
| 20080301770 | Kinder | Dec 2008 | A1 |
| 20090038017 | Durham et al. | Feb 2009 | A1 |
| 20090043993 | Ford et al. | Feb 2009 | A1 |
| 20090144300 | Chatley et al. | Jun 2009 | A1 |
| 20090150639 | Ohata | Jun 2009 | A1 |
| 20090249438 | Litvin et al. | Oct 2009 | A1 |
| 20100071035 | Budko et al. | Mar 2010 | A1 |
| 20100100970 | Roy-Chowdhury et al. | Apr 2010 | A1 |
| 20100114825 | Siddegowda | May 2010 | A1 |
| 20100281133 | Brendel | Nov 2010 | A1 |
| 20100293225 | Sebes et al. | Nov 2010 | A1 |
| 20110035423 | Kobayashi et al. | Feb 2011 | A1 |
| Number | Date | Country |
|---|---|---|
| EP 1 482 394 | Dec 2004 | EP |
| 2 037 657 | Mar 2009 | EP |
| WO 9844404 | Oct 1998 | WO |
| WO 0184285 | Nov 2001 | WO |
| WO 2006012197 | Feb 2006 | WO |
| WO 2006124832 | Nov 2006 | WO |
| WO 2008054997 | May 2008 | WO |
| WO 2011059877 | May 2011 | WO |
| WO 2012015485 | Feb 2012 | WO |
| WO 2012015489 | Feb 2012 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 60879826 | Jan 2007 | US |
