# US 2006/0155891 A1 · Method relating to rule-regulated software configuration

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2006/0155891 A1
- Document ID: US20060155891A1
- Status: Published application
- Kind: A1
- Application number: 11/028,260
- Filed: 2005-01-04
- Published: 2006-07-13
- Earliest claimed: 2005-01-04
- Assignees: Sap SE
- Inventors: Yuh-Cherng Wu
- Web page: https://patentgrep.com/patent/US20060155891A1

## CPC

- G06F 9/44505: {Configuring for program initiating, e.g. using registry, configuration files}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method relating to rule-regulated configuration of software includes receiving an unsuccessful configuration that a sender computer system sends to a recipient computer system upon software being unsuccessfully configured in the sender computer system. Validation rules for configuring the software allowed the unsuccessful configuration. The validation rules are modified in the recipient computer system using the using the unsuccessful configuration. The modified validation rules are provided to the sender computer system. Several sender systems may routinely report new configurations to the recipient computer system. The rules may be modified upon creating a variation of the configuration and determining whether it successfully configures the software. The variation may involve using a probabilistic distribution.

## Claims

### Claim 1

A method relating to rule-regulated configuration of software, the method comprising:
receiving an unsuccessful configuration that a sender computer system sends to a recipient computer system upon software being unsuccessfully configured in the sender computer system, wherein validation rules for configuring the software allowed the unsuccessful configuration;
modifying, in the recipient computer system, the validation rules using the unsuccessful configuration; and
providing the modified validation rules to the sender computer system.

### Claim 2 (depends on 1)

The method of claim 1, wherein the sender computer system retrieved the validation rules from the recipient computer system in preparation for configuring the software.

### Claim 3 (depends on 1)

The method of claim 1, wherein modifying the validation rules comprises at least one selected from the group consisting of: adding a rule prohibiting the unsuccessful configuration, removing a rule allowing the unsuccessful configuration, and combinations thereof.

### Claim 4 (depends on 1)

The method of claim 1, further comprising performing a simulation in the recipient computer system upon receiving the unsuccessful configuration, wherein modifying the validation rules is based on the simulation.

### Claim 5 (depends on 4)

The method of claim 4, wherein the simulation comprises creating a variation of the unsuccessful configuration and determining whether the variation successfully configures the software.

### Claim 6 (depends on 5)

The method of claim 5, wherein the unsuccessful configuration comprises several parameters for configuring the software, at least some of the parameters being provided with values in the unsuccessful configuration.

### Claim 7 (depends on 6)

The method of claim 6, wherein the variation comprises a change in at least one of the values.

### Claim 8 (depends on 7)

The method of claim 7, wherein the change is based on a probabilistic distribution generated for the parameter to which the at least one value is provided.

### Claim 9 (depends on 8)

The method of claim 8, wherein the probabilistic distribution is based on previously recorded configurations that the recipient computer system has received from any of several sender computer systems.

### Claim 10 (depends on 8)

The method of claim 8, wherein the probabilistic distribution for the parameter is heuristically assigned.

### Claim 11 (depends on 6)

The method of claim 6, wherein the variation comprises a change in which the at least some of the parameters are.

### Claim 12 (depends on 11)

The method of claim 11, wherein the variation comprises fewer value-provided parameters than the unsuccessful configuration.

### Claim 13 (depends on 1)

The method of claim 1, further comprising receiving a successful configuration that any of several sender systems sends to the recipient computer system, and modifying the modified validation rules in the recipient computer system using the successful configuration.

### Claim 14 (depends on 13)

The method of claim 13, further comprising performing a simulation in the recipient computer system upon receiving the successful configuration, wherein modifying the modified validation rules is based on the simulation.

### Claim 15 (depends on 14)

The method of claim 14, wherein the simulation comprises creating a variation of the successful configuration and determining whether the variation successfully configures the software.

### Claim 16 (depends on 15)

The method of claim 15, wherein the successful configuration comprises several parameters for configuring the software, at least some of the parameters being provided with values in the successful configuration.

### Claim 17 (depends on 16)

The method of claim 16, wherein the variation comprises a change in at least one of the values.

### Claim 18 (depends on 17)

The method of claim 17, wherein the change is based on a probabilistic distribution generated for the parameter to which the at least one value is provided.

### Claim 19 (depends on 18)

The method of claim 18, wherein the probabilistic distribution is based on previously recorded configurations that the recipient computer system has received from any of the several sender computer systems.

### Claim 20 (depends on 16)

The method of claim 16, wherein the variation comprises a change in which the at least some of the parameters are.

### Claim 21 (depends on 20)

The method of claim 20, wherein the variation comprises more value-provided parameters than the successful configuration.

### Claim 22 (depends on 1)

The method of claim 1, wherein several sender computer systems apply the validation rules in configuring the software, further comprising providing the modified validation rules to the several sender computer systems.

### Claim 23

A computer program product tangibly embodied in an information carrier, the computer program product including instructions that, when executed, cause a processor to perform operations comprising:
receiving an unsuccessful configuration that a sender computer system sends to a recipient computer system upon software being unsuccessfully configured in the sender computer system, wherein validation rules for configuring the software allowed the unsuccessful configuration;
modifying, in the recipient computer system, the validation rules using the unsuccessful configuration; and
providing the modified validation rules to the sender computer system.
