Processing a request in accordance with original rules and configurations

Patent metadata

Field	Value
Publication number	US-11023830-B2
Application number	US-201414485535-A
Country	US
Kind code	B2
Filing date	Sep 12, 2014
Priority date	Jun 30, 2014
Publication date	Jun 1, 2021
Grant date	Jun 1, 2021

Abstract

System and methods process a received request consistently over extended time by determining the request type and creating metadata with current rules and configuration information for the request type. A system stores the metadata, for instance in a versioning system, and may create a metadata snapshot associated with the request. Through the metadata, the system uses the correct version of rules and configurations to consistently process the request in accordance with the time the request was originally received.

First claim

I claim:

1. A method for consistently processing a request received at a first time on a computer system including multiple applications, wherein an application has a first version requiring a first configuration and can handle a first request type, the method comprising:
receiving a request;
determining if the request is of the first request type, wherein the first request type is subject to procedures that require interactions with outside partners including a verification, a confirmation, and a payment, and wherein an interaction takes at least two days;
determining metadata for the request based on the first request type, wherein the metadata includes information about the first configuration and captures at least a first rule and a second rule which are consecutively applicable to the request;
tagging a snapshot to the request, wherein the snapshot includes the first rule and the second rule at a time of receiving the request;
storing the metadata along with the request;
forwarding the request for first processing according to the first rule;
while retaining rule version information in the stored metadata, related to the first request type replacing the second rule by a third rule that was not valid at the first time;
keeping the second rule accessible and maintaining the second rule;
receiving a result from the first processing of the request;
retrieving the stored metadata for the request; and
processing the result on the computer system using the second rule according to the rule version information in the stored metadata.

2. The method of claim 1 , comprising storing the metadata in a versioning system.

3. The method of claim 1 , wherein the metadata includes a reference indicating the second rule.

4. The method of claim 1 , wherein the metadata includes a version of the second rule.

5. The method of claim 1 , wherein the metadata includes a timestamp.

6. The method of claim 1 , wherein the metadata includes a reference to a software application adapted to process the request.

7. The method of claim 1 , wherein the metadata includes pre-generated information.

8. The method of claim 1 , wherein the request includes an order.

9. The method of claim 1 , wherein the request includes a message.

10. The method of claim 1 , wherein the request includes a query.

11. The method of claim 1 , wherein the request is hierarchical.

12. The method of claim 11 , wherein the processing of the request by at least one of the first and second rules triggers a related request with related metadata.

13. The method of claim 12 , wherein the related metadata is at least in part different than the stored metadata.

14. The method of claim 12 , further comprising:
receiving the related request;
storing the related metadata;
creating a related snapshot of the related metadata, wherein the related snapshot includes related metadata version information;
associating the related request and the related snapshot; and
using the related metadata version information from the related snapshot to process the related request in accordance with the related metadata version.

15. The method of claim 1 , wherein the processing of the request by at least one of the first and second rules is performed by an enterprise software system.

16. A system for consistently processing a request received at a first time, comprising:
an application server coupled with a data storage device and adapted to receive requests from a user device via at least one network, the application server including multiple applications, wherein an application has a first version requiring a first configuration and can handle a first request type, wherein the first request type is subject to procedures that require interactions with outside partners including a verification, a confirmation, and a payment, and wherein an interaction takes at least two days;
wherein the application server is programmed to perform a method comprising:
receiving a request from the user device;
determining if the request is of the first request type;
determining metadata for the request based on the first request type, wherein the metadata includes information about the first configuration and captures at least a first rule and a second rule which are consecutively applicable to the request;
tagging a snapshot to the request, wherein the snapshot includes the first rule and the second rule at a time of receiving the request;
storing the metadata along with the request in a database;
forwarding the request for first processing according to the first rule;
while retaining rule version information in the stored metadata, related to the first request type replacing the second rule by a third rule that was not valid at the first time;
keeping the second rule accessible and maintaining the second rule;
receiving a result from the first processing of the request;
retrieving the stored metadata from the database; and
processing the result on the application server using the second rule according to the rule version information in the stored metadata.

17. A tangible, non-transitory, computer-readable information storage medium including instructions adapted to direct a processor to perform an operation, the operation comprising:
at a first time, receiving a request on a computer system including multiple applications, wherein an application has a first version requiring a first configuration and can handle a first request type, wherein the first request type is subject to procedures that require interactions with outside partners including a verification, a confirmation, and a payment, and wherein an interaction takes at least two days;
determining if the request is of the first request type;
based on the first request type, determining metadata for the request, wherein the metadata includes information about the first configuration and captures at least a first rule and a second rule which are consecutively applicable to the request;
tagging a snapshot to the request, wherein the snapshot includes the first rule and the second rule at a time of receiving the request;
storing the metadata along with the request;
forwarding the request for first processing according to the first rule;
while retaining rule version information in the stored metadata, related to the first request type replacing the second rule by a third rule that was not valid at the first time;
keeping the second rule accessible and maintaining the second rule;
receiving a result from the first processing of the request;
retrieving the stored metadata for the request; and
processing the result on the computer system using the second rule according to the rule version information in the stored metadata; and
delivering results of the request processing.

Assignees

• Oracle Int Corp

Inventors

• Sao Saurav

Classifications

• G06F16/9574

  of access to content, e.g. by caching · CPC title

• G06F16/188

  Virtual file systems · CPC title

• G06F16/176

  Support for shared access to files; File sharing support · CPC title

• G06Q10/10

  Office automation; Time management · CPC title

• G06Q10/06 Primary

  Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling · CPC title