The invention relates to a method of and system for change management control, analysis, and monitoring of logical groups including of system components and configuration items. The change management is based on configuration item change information generated by configuration item monitoring devices. The change information is analyzed against configuration item change rules, and interrelationship information between configuration items, system components, and between system components.
Current state-of-the-art configuration management systems are based on, names of a file, creation dates of files, registries, and environment variable within an application or a suite of applications. However, these relationships are limited in only defining a relationship between components within an application, or a suite of applications.
What is needed is a method of defining change relationships in a manner that extends beyond an application component relationship to include the additional dimension of change and rules for changing configuration items including but not limited to time a change was made, the user making the change, the content of the change, and the impact of a change. Additionally, what is needed is the ability to correlated multiple change management specifications defining different system viewpoints. Further needed is a change control system where the integral relationship, logical groups of system components and configuration items can be specified for which configuration item change information can be utilized for management, control, monitoring, and analysis. What is also is needed is a configuration management system does not define relationships in terms of the configuration change dimensions such as time when a change can be made, the change value, the program that made the change, the user that made the change, the severity of a change and the analysis of a change from multiple viewpoints.
A first aspect of the invention is a system for change management. The system includes means of generating configuration item change information, an information structure that defines change rules for configuration items including relationships between system components, and means for processing the configuration item change information according to the information structure.
The means for generating configuration item change information can be but is not limited to software operating as an application, process, driver, or a software hook into an operating system. This means of generating configuration item change information can monitor, control by the prevention or timing of changes, and generate configuration item change information that can include but is not limited to the status of the change, the time of the change, the process making the change, and the user making the change, or a reason for failure of a change.
The information structure describes the configuration items that can be part of a system, a logical group or a combination of the two. Further, the information structure describes change rules for configuration items, system components, logical groups, or a combination thereof. A change rule can apply to a single configuration item, a plurality of configuration items, a system component, a logical group, or a combination thereof. Additionally, the information structure contains interrelationship information of a configuration item with one or more system components, and interrelationship information between system components.
The system includes means for interpreting the configuration item change information according to the information structure. This means for interpreting the configuration item change information can include but is not limited to determining if the configuration change violated a rule. This step can include interpretation of change failures. The means of interpretation also includes mapping of a change in a configuration item to a system component where the system component is part of a logical group defining a system view.
In one embodiment of the invention, the system comprises a plurality of system components where each system component comprises one or more configuration items. Exemplar of configuration items are computer files, computer registries, databases, and can include configuration of mechanical devices. Exemplar of system components are computer applications, a computer system, computational logic, a configurable mechanical device, a network device, a storage array, a server, server cluster, and a processing center.
In a further embodiment, the invention comprises of one or more logical groups consisting of at least one system component and a configuration item. These logical groups can have overlapping system components and overlapping configuration items.
In one aspect of the invention, the system further comprises means for generating a notification of the changes in the configuration items when the configuration item change information is processed in accordance with the information structure. This notification can include but is not limited to violations of the change rules in the information structure. Further, the notification can report the status of changes. The means for notification can include but is not limited to the generation of reports, email, SMS text messages, pages, SNMP (Simple Network Management Protocol) messages, and automated phone messages. SNMP messages can be generated by calling the Network Management TRAP function which generates an interne or interprocess communication message. The message can contain information or an indication regarding the cause of the TRAP invocation. Other standard or custom network management protocols are also contemplated. A socket can be setup for interprocess or inter-computer communication of the notifications.
In another embodiment of the system for change management, an indicator is provided as part of the interrelationship information of the information structure which characterizes the relative importance of the change between a configuration item and the one or more system components. Additionally, the information structure can contain an indicator that characterizes the importance of the interrelationship between other components. The indicators provide a relative effect of a change on the logical group system component or configuration item. Exemplary of such an indicator are the use of values between 1 and 10, or the use of words such as “slight”, “moderate”, and “severe.”
In another embodiment of the system, the means for generating configuration item change information is an application coupled to a least one of the system components or configuration items. This application can be, but is not limited to, a program operating as an application, process, driver, or hook into an operating system. This application can monitor, control configuration item changes, and generate configuration item change information that can include but is not limited to the status of the change, the time of the change, the process making the change, and the user making the change. Also contemplated is monitoring at a system or logical group level.
In yet another embodiment of the system, the configuration items comprise one or more computer files, computer registries, databases, virtual machine settings, or a combination thereof.
In another embodiment of the system, configuration item change information provides information on a file creation, a file deletion, file change data, registry creation, registry deletion, the registry change value, change of a virtual machine setting, a database change, a user making the change, a time of the change, a program making the change, an operational program making the change, or a combination thereof.
In a second aspect of the invention, a method of change management disclosed. The method comprises the steps of generating change information and processing the change information according to the logical groups, system components, or configuration items specified in an information structure. The information structure contains information change rules for configuration items, system components, and logical groups. Further, the information structure contains information on the interrelationship between a configuration item within a logical group and system components. Further it can include relationships between a configuration item and another configuration item. For example, a financial program might be dependent on a database system component where the general dependency is known but not down to a fine grain level such as whether the program is dependent on a specific table in a database application. Additionally, the information structure contains information on the interrelationship between system components and between logical groups. These system components can reside within the same logical group or outside the logical group.
In a further embodiment of the second aspect of the invention, the method further comprises the step of generating one or more notifications according to the processing of the change information in accordance with the information structure. The notifications can include but are not limited to generating, a text or graphic report, an email, an SMS text message, a page, a SNMP (Simple Network Management Protocol) message, an automated phone message, or a combination thereof. SNMP messages can be generated by calling the Network Management TRAP function which generates an internet or interprocess communication message. The message can contain information or an indication regarding the cause of the TRAP invocation.
In another embodiment of the method of change management, the information structure change rules used in the processing of the change data comprise at least one parameter selected from the group consisting of users that can make the configuration change, programs allowed to make the configuration change, a time window during which the change can be made, allowable data for the change, or a data range for the change, and any combination thereof.
In yet another embodiment of the method of change management, the processing of change information utilizes an indicator associated with interrelationship information between the at least one or more of the configuration items, other configuration items and the system components, and an indication the interrelationship information between the system component and a second system component to characterize the effect of the change information on the logical group. Further it can contain an indication of the interrelationship information between logical groups.
In yet another embodiment of the method of change management, the configuration items are selected from the group consisting of files, registries, databases, virtual machines, and a combination thereof. Configuration item change information comprises, file creation, file deletion, file data, registry creation, registry deletion, a registry change value, change of a virtual machine setting, a virtual machine setting, a database change, a user who made the change, a time of the change, a program making the change, or a combination thereof. The method for generating the change information can be a change monitoring application coupled to at least one of the configuration items and one of the system components. The change monitoring application can be a program, process, or a component of an operating system.
In another embodiment of the method of change management, the means for generating change information further controls changes to the configuration items in accordance with one or more configuration parameters. The configuration parameters can specify but are not limited to the time of the configuration change, the program making the change, the user making the change, or a range of change values.
In another aspect of the invention, a change management analysis system is disclosed. The system comprises means of generating simulated configuration item change information, an information structure, and a means of processing the configuration item change information for one or more logical groups, system components, or configuration items according the information structure. The information structure contains logical groups of system components and configuration items. Each logical group comprises at least one of change rule information for at least one configuration item, interrelationship information between the configuration item(s) and one or more system components, and interrelationship information between system components. Also, the system components can contain at least one change rule. Means of generating simulated configuration item changes can include an application that allows a user to select one or more changes to a configuration item or a system component specified within the information structure. Means of processing the simulated configuration item changes by logical groups or system components and provides changes in accordance to the information structure. The inventor contemplates any type of processing system including but not limited to servers, blade processors, personal computers, and mobile computational devices.
A third aspect of the invention is for a method of generating an information structure. The information structure comprises one or more logical groups containing a least change rule information for the at least one configuration item, interrelationship information between a configuration item and a system component, or interrelationship information between two system components. Further, the information structure can include change rule information for one or more system components. A method of generating an information structure includes the steps of processing a plurality of logical group information structures describing a logical group. One or more system components or configuration items. The processing determines the associations between each logical group. The information structure comprises at least one of change rule information for the at least one configuration item, interrelationship information between the at least one configuration item and one or more system components, and interrelationship information between one or more system components. The processing generates an information structure including a plurality of logical groups or system components. Each logical group contains at least one element selected from the group of change rule information for the at least one configuration item, interrelationship information between the at least one configuration item and one or more system components, and interrelationship information between one or more system components. Alternatively, the information structure can contain system components that contain at least one element selected from the group of change rule information for the at least one configuration item, interrelationship information between the at least one configuration item and interrelationship information between one or more system components.
The invention is better understood by reading the following detailed description of an exemplary embodiment 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 adaptions to the present inventions are possible and may 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. The scope of the present invention is defined by the claims.
The present invention provides multiple advantages over the prior art. Configuration item change management can be used to manage, control, monitor, and analyze the consequence of changes over a more complex systems than can be implemented with the current state-of-the-art systems. Also, the management, control, monitoring, and analysis of the system components and configuration items can be tailored to logical group, system components, and configuration items to match differing interests. This abstracts the monitoring and analysis and removes the fine grain reporting of configuration item changes that might be difficult to interpret. Further, the system management can be performed based on relationships other than that a configuration item belongs to a group of configuration items. Relationships between system elements can also include relationships between system components and other system components and configuration items. Complex management relationships can be created, monitored, and or controlled. The management can be based on the creation, deletion, and change value of a file, registry, environment variable, or database. Additional change parameter rules can be included in the change management system including the control of or monitoring or the user making the change, the program making the change, the server making the change, the server cluster making the change, or even changes to a virtual machine. As a result, the effect of fine grain changes can be controlled, analyzed and monitored, and the effects reported at an abstraction level consistent with a the interest, control, and responsibility.
A system component 110 can comprise one or more configuration items 112. Exemplar of a system component 110 is a computer application, a computer, computational logic, a configurable mechanical device, a network device, a storage array, a server, server cluster, or a processing center. Configuration items 112 include but are not limited to files, databases, registries, environment variables, virtual machine settings, or mechanical valve settings. The system component 110 also includes a configuration change controller 114 which monitors or controls a change in a configuration item 112. The change controller 114 can include but is not limited to a software program or other programmable logic coupled or integrated into to an operating system to monitor, prevent, or control changes to configuration items such as files, registries, and databases. The Non-Provisional Patent Application “Method and Apparatus for Process Enforced Configuration Management” filed Jan. 9, 2008 to Rishi Bhargava et al and the Provisional Patent Application Ser. No. 60/879,826 filed Jan. 10, 2007, and entitled “SOFTWARE THAT MESSAGES CHANGE CONTROL” is are hereby incorporated by reference in their entirety.
The change controller 114 generates informational messages regarding changes or attempted changes to configuration items 112 and controls access to the configuration item. These messages can contain information about but are not limited to, the program that made the change, the values that were changed, the time of the change, the user making the change, the computer/server/cluster from which the change was made, and the database being used. These messages are sent to configuration change server 130 which provides means for processing and analyzing configuration changes according to an information structure 138. The information structure can contain one or more change rules and information on interrelationships between two or more system components 110 and interrelationships between system components 110 and configuration items 112. The change management application 137 is shown as a part of separate server 130. Also within the contemplation of the invention is the configuration change application 137 running on a computer/servers with other applications or within a virtual machine running on a computer (not shown) and shared with other applications.
The change controller 114 and the configuration change server 130 are illustrated as being coupled by a network 150. Other means of communication are also contemplated. Communication between the change controller 114 and the configuration change application 137 can use but is not limited to operating system sockets, pipes, and all types of wired, optical, and wireless networks.
The change configuration server 130 includes a central processing unit (CPU) 132, program memory 133, a non-volatile storage 134, and input and output logic 136 for communication with the change controller 114 and notification means 140. The change configuration server 130 provides means for processing change information received over the network 150 and/or storing for the change information on the non-volatile storage 134. The change information is processed according to the rules and relationships specified in the information structure 138. While depicted as a separated processing unit, the configuration change server 130 can be part of a server providing other functions such as a file server or an application server. Also contemplated by the invention, is the use of other computational systems for implementing a change configuration server including but not limited to blade servers, desktop computers, thin clients, or other computational devices.
The non-volatile system 134 is depicted as part of the change configuration server 130 but other configurations of non-volatile memory are contemplated. The storage device can 134 be externally coupled or can be network attached storage (not shown). Stored within the storage system is configuration change information received from the configuration change controllers 114 over the network 150. However, it is within the contemplation of the invention for the configuration change information to be directly processed by the CPU without storage on non-volatile storage 134. The storage device 130 also contains an information structure 138 containing information regarding rules for changes to configuration items 112, configuration relationships between configuration items 112 and other configuration items 112, a configuration relationships between configuration items 112 and system components 110, and configuration relationships between system components 110.
A set of one or more rules and relationships form a logical group which represents one view of a system. The information structure 138 can contain multiple logical groups 120, 120′. A logical group 120, 120′ forms an exemplary view of the system that contains the system components 110 and configuration items 112 in which a person or organization can be interested. For example, a CFO might be concerned with whether anything in the financial accounting system changed during the year-end closing. In this example, the CEO logical group may be limited to the Oracle® accounting software, the finance cluster of servers, and the Oracle® database components. Alternatively, the interest of the manager for the Oracle® database could be limited to the database configuration items and all of the hardware on which the database runs with could involve other servers. This would form a different logical group than the logical group for the CFO. Note that the logical groups 120, 120′ can overlap in their system components 110 and configuration items 112.
In another utilization of the information structure 200, simulated configuration item change information 339-
A third utilization of the information structure 200 is used to control configuration changes in the configuration items 112-
Within the logical group 210, the configuration items 220 shown include but are not limited to files, environment variables, and registry settings. Parameters are associated with each configuration item. The parameters can specify limitations to the configuration changes including but not limited to, a time window in which the change can be made, the users allowed to make the change, the programs allowed to make the change, and a range of values for the change. A logical group can also include an external system components 240 which interrelates with another logical group 210. The interrelationship with the external system components can include but is not limited to, a processor rebooting, a new version of a database, a change in any component of the database, and a change in the operating system. These interrelationship reflects a dependency at a higher level as oppose to a dependancy at the level of files, and registry settings. The exemplary information structure 200 is shown using a language like extendable markup language (XML) to describe the rules for two different logical groups. However, other description languages or means for defining information structures are contemplated.
The change configuration server 330 includes a central processing unit (CPU) 332, and program memory 333, and a non-volatile storage means 334, and input and output logic 336 for communication with the configuration change application 337, the change information simulator 310 and the means for notification 140. The change configuration server 330 functions as described above in 130-
The change information is sent to a central place for aggregation and analysis. The information can be sent over any communication means including but not limited wired networks, wireless networks or through computer software communication channels such as sockets, pipes, and shared memory.
The configuration change items include but are not limited to files, registry directory settings, databases, virtual machine settings, processor reboot, and process spawning and death. The types of changes tracked include but are not limited to file creation, file deletion, file data, registry creation, registry deletion, a registry change value, a virtual machine setting change, a virtual machine setting value, a database change, a user making a change, a time of the change, a program making the change, and any combination thereof.
In a second step 420, the change information is processed according to an information structure 138-
In a step 430, notifications are generated from the processing of the change information data (139-
In a first step 510, a plurality of logical group information structures is processed to determine the associations between the logical groups. As an example of these associations, one logical group may have specified a dependency on a first application. The first application may be dependent on another system component or configuration items that is not part of the logical group. As part of the generation of logical groups dependencies, these sub-dependencies are determined for incorporation into the information structure and associated with the logical groups. A complete tree of dependencies can be determined and incorporated into the information structure for each logical group.
In a second step 520, an information structure is generated from the dependencies determined in the processing step 510. The information structure can contain information for a plurality of a logical group or system components. For each logical group, the information structure will contain at least one of; a change rule for one or more configuration items, interrelationship information between at least one configuration item and one or more system components, interrelationship of a system group a one or more configuration items, and interrelationship information between one or more system components. For each system component, the information structure will contain at least one of; a change rule for one or more configuration items, interrelationship information between at least one system component and one or more configuration items, and interrelationship information with one or more system components. Preferably, this information structure is stored on a non-volatile memory device such as but not limited to a hard drive or flash memory 134-
This application claims benefit of priority under 35 U.S.C. section 119(e) of U.S. Provisional Patent Application Ser. 61/001,449 filed Oct. 31, 2007, entitled APPLICATION CHANGE CONTROL which is incorporated by reference.
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 |
5987611 | Freund | Nov 1999 | A |
5991881 | Conklin et al. | Nov 1999 | 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 |
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 |
7506170 | Finnegan | Mar 2009 | B2 |
7546333 | Alon et al. | Jun 2009 | B2 |
7607170 | Chesla | Oct 2009 | B2 |
7657599 | Smith | Feb 2010 | B2 |
7698744 | Fanton et al. | Apr 2010 | B2 |
7757269 | Roy-Chowdhury et al. | Jul 2010 | B1 |
7870387 | Bhargava et al. | Jan 2011 | B1 |
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 |
20030023736 | Abkemeier | Jan 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 |
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 et al. | Dec 2004 | A1 |
20040255161 | Cavanaugh | Dec 2004 | A1 |
20050018651 | Yan et al. | Jan 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 |
20060085785 | Garrett | Apr 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 |
20070253430 | Minami et al. | Nov 2007 | A1 |
20070271561 | Winner et al. | Nov 2007 | A1 |
20080005798 | Ross | Jan 2008 | A1 |
20080052468 | Speirs et al. | Feb 2008 | A1 |
20080082977 | Araujo et al. | Apr 2008 | A1 |
20080120499 | Zimmer et al. | May 2008 | A1 |
20080163207 | Reumann et al. | Jul 2008 | A1 |
20080163210 | Bowman 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 |
20090144300 | Chatley et al. | Jun 2009 | A1 |
20090150639 | Ohata | Jun 2009 | A1 |
20090249438 | Litvin et al. | Oct 2009 | A1 |
20100100970 | 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 |
20110077948 | Sharma et al. | Mar 2011 | A1 |
20110093842 | Sebes | Apr 2011 | A1 |
20110093950 | Bhargava et al. | Apr 2011 | A1 |
20110119760 | Sebes et al. | May 2011 | A1 |
20110138461 | Bhargava et al. | Jun 2011 | A1 |
Number | Date | Country |
---|---|---|
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 | |
---|---|---|---|
61001449 | Oct 2007 | US |