# US 2013/0159238 A1 · Custom Rule Based Determination of Pricing Information

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

- Number: US 2013/0159238 A1
- Document ID: US20130159238A1
- Status: Published application
- Kind: A1
- Application number: 13/608,182
- Filed: 2012-09-10
- Published: 2013-06-20
- Earliest claimed: 2011-12-20
- Assignees: International Business Machines Corporation
- Inventors: Pawel J. Borkowski; Michal Klak; Maksymilian Kowalik; Bartlomiej T. Malecki
- Web page: https://patentgrep.com/patent/US20130159238A1

## CPC

- G06Q 30/0283: Price estimation or determination
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Determining a pricing information for an instance of an application program comprises: receiving a software discovery result for the application program instance; receiving at least one custom rule associated with an application program indicated in the software discovery result; evaluating, by a rule engine, one or more conditions of the received at least one custom rule on one or more parameter values of the received software discovery result; and in dependence on a result of the evaluation, processing the at least one custom rule, the processing comprising determining the pricing information for the application program instance.

## Claims

### Claim 1

A computer-implemented method for determining a pricing information for an instance of an application program, the application program instance running on a computer system, the method comprising:
receiving a software discovery result for the application program instance from a software discovery module, the received software discovery result comprising:
an indication of an application program from which the application program instance was instantiated; and
one or more values of parameters of the application program instance and/or of parameters of the computer system;
receiving, by a rule engine, at least one custom rule associated with the application program indicated in the software discovery result, the at least one custom rule comprising one or more conditions;
evaluating, by the rule engine, the one or more conditions of the received at least one custom rule on the parameter values of the received software discovery result; and
in dependence on a result of the evaluation, processing the at least one custom rule, the processing comprising determining the pricing information for the application program instance.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein the at least one custom rule is received from a location comprising one of: a relational database; a pricing rule server; a file in a file directory where the application program indicated in the software discovery result is installed; and a location indicated by a Uniform Resource Identifier.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein the association of the at least one custom rule and the application program is implemented by one of:
storing an identifier of the at least one custom rule and an identifier of the application program in an operating system registry of a the computer system hosting the software discovery module;
storing the identifier of the at least one custom rule in a file with a predefined name inside an installation directory of the application program;
storing the identifier of the at least one custom rule and the identifier of the application program in together in a single file; and
storing both the identifier of the at least one custom rule and the identifier of the application program in a relational database.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, further comprising:
providing an auditing module being operatively coupled to the rule engine, wherein:
the software discovery result and the at least one custom rule are received by the auditing module;
the auditing module is operable to execute default processing steps for calculating the pricing information for the application program instance; and
the at least one custom rule associated with the application program indicated in the software discovery result comprises a meta-language specification of custom processing steps to be executed by the auditing module for calculating the pricing information; and
in case the at least one custom rule was not received by the auditing module, executing the default processing steps to compute the pricing information and otherwise, executing the custom processing steps to compute the pricing information.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, further comprising:
determining, upon receipt of the software discovery result, if at least one custom rule associated with the software discovery result is received;
in case no associated custom rule is received, initiating execution of default processing steps for calculating the pricing information;
in case the at least one associated custom rule is received, executing a version check, the version check comprising at least one of:
checking if a version of the rule engine is sufficient for evaluating the custom rule; and
checking if a version of the software discovery module is sufficient for collecting all parameter values evaluated by the custom rule, wherein:
the version check returns a negative result if the version of the rule engine is not sufficient, the version of the software discovery module is not sufficient, or both the version of the rule engine and of the software discovery module are not sufficient; and
the version check returns a positive result otherwise;
in case the at least one associated custom rule is received and the version check returns a positive result, executing the evaluating of the one or more conditions; and
in case the at least one associated custom rule is received and the version check returns a negative result, returning an indication of the rule engine and/or the software discovery module as having caused the negative result.

### Claim 6 (depends on 5)

The computer-implemented method of claim 5, further comprising returning an audit report, the audit report comprising the result of the evaluation, the result being indicative of any deviation from a default pricing information.

### Claim 7 (depends on 6)

The computer-implemented method of claim 6, further comprising attaching the received at least one custom rule or an indication thereof to the audit report.

### Claim 8 (depends on 5)

The computer-implemented method of claim 5, wherein:
the received software discovery result comprises an indication of a running time, the running time being a time period ranging from an instantiation of the application program instance to the receipt of the software discovery result;
the received custom rule comprises an indication of a validity period during which the pricing information is to be calculated by custom program instructions; and
the method further comprises:
in case the at least one associated custom rule is received, executing a validity period check, the validity period check comprising:
determining a period of time by which the running time exceeds the validity period;
creating a copy of the software discovery result, the copy not being assigned to any one of the custom rules, the copy being indicative of the determined period of time;
executing the default processing steps for calculating a first evaluation result part, the default processing steps using the copy of the software discovery result as input, the first evaluation result part comprising default pricing information calculated for the determined period of time;
setting the running time of the received software discovery result to the validity period of the assigned at least one custom rule;
executing the at least one custom rule on the parameter values of the received software discovery result for calculating a second evaluation result part, the second evaluation result part comprising pricing information calculated selectively for the validity period; and
combining the first evaluation result part and the second evaluation result part for providing the result of the evaluation.

### Claim 9 (depends on 5)

The computer-implemented method of claim 5, wherein:
the at least one custom rule comprises a header and a body;
a version of the at least one custom rule is specified in the header of the custom rule; and
executing the version check comprises:
reading the version of the at least one custom rule from the header of the custom rule prior to the checking if the version of the rule engine is sufficient for evaluating the custom rule;
in case the version of the rule engine is not sufficient for evaluating the custom rule, outputting a first message being indicative of a need to update the rule engine; and
only in case the version of the rule engine is sufficient for evaluating the custom rule, checking if the version of the software discovery module is sufficient for the collecting.

### Claim 10 (depends on 9)

The computer-implemented method of claim 9, wherein checking if the version of the software discovery module is sufficient comprises:
determining a minimum set of parameters evaluated by the one or more conditions of the at least one custom rule by evaluating the body of the rule;
computing a minimum version of the software discovery module being sufficient for gathering the determined minimum set of parameters; and
in case the version of the software discovery module is lower than the computed minimum version, then determining that the version of the software discovery module is not sufficient and further outputting a second message being indicative of a need to update the software discovery module.

### Claim 11 (depends on 5)

The computer-implemented method of claim 5, the method further comprising:
parsing the meta-language specification of the custom processing steps for executing the custom processing steps, wherein the parsing is executed only in case the version check returns the positive result.

### Claim 12 (depends on 1)

The computer-implemented method of claim 1, the computer system being one of a plurality of computer systems respectively hosting one or more instances of one or more application programs.

### Claim 13 (depends on 5)

The computer-implemented method of claim 5, wherein checking if the version of the rule engine is sufficient comprises comparing the version of the custom rule with a version of the rule engine.

### Claim 14

A computer-readable storage medium comprising computer-interpretable instructions which, when executed by a processor, cause the processor to determine a pricing information for an instance of an application program, the application program instance running on a computer system, by performing:
receiving a software discovery result for the application program instance from a software discovery module, the received software discovery result comprising:
an indication of an application program from which the application program instance was instantiated; and
one or more values of parameters of the application program instance and/or of parameters of the computer system;
receiving, by a rule engine, at least one custom rule associated with the application program indicated in the software discovery result, the at least one custom rule comprising one or more conditions;
evaluating, by the rule engine, the one or more conditions of the received at least one custom rule on the parameter values of the received software discovery result; and
in dependence on a result of the evaluation, processing the at least one custom rule, the processing comprising determining the pricing information for the application program instance.

### Claim 15

A computer system for determining a pricing information for an instance of an application program, the computer system comprising:
an audit server (hosting a rule engine, the audit server being connected via a network to one or more computer systems, the computer systems respectively hosting one or more application program instances;
wherein the rule engine is adapted for:
receiving a software discovery result for a selected one of the application program instances from a software discovery module, the application program instances running on one or more computer systems, the received software discovery result comprising:
an indication of an application program from which the selected application program instance was instantiated; and
one or more values of parameters of the selected application program instance and/or of parameters of the computer system on which the selected application program instance is running;
receiving, by the rule engine, at least one custom rule associated with the application program indicated in the software discovery result, the at least one custom rule comprising one or more conditions;
evaluating, by the rule engine, the one or more conditions of the received at least one custom rule on the parameter values of the received software discovery result; and
in dependence on a result of the evaluation, processing the at least one custom rule, the processing comprising determining the pricing information for the selected application program instance.

### Claim 16 (depends on 15)

The computer system of claim 15, further comprising:
at least one software discovery module, the at least one software discovery module running on one of the computer systems, the at least one software discovery module being adapted for:
monitoring and gathering one or more values of parameters of the selected application program instance;
monitoring and gathering one or more parameters of the computer system on which the selected application program instance is running; and
sending the software discovery result comprising one or more parameter values of the selected application program instance and/or of the computer system to the rule engine.
