Definition and distribution of business rules while enforcing syntactic and semantic validation

• US 7,577,904 B1
• Filed: 03/28/2002
• Issued: 08/18/2009
• Est. Priority Date: 03/28/2001
• Status: Expired due to Fees

• Current Assignee: MModal IP LLC (3M Company)
• Original Assignee: Vianeta Communication (3M Company)
• Inventors: Obilisetty, Sridhar
• Primary Examiner(s): Hong; Stephen S
• Assistant Examiner(s): Stork; Kyle R
• Application Number:
  US10/113,011
• Time in Patent Office: 2,700 Days
• Field of Search: 715/513, 715/708, 715/500, 715/517, 715/523, 715/530, 715/205, 715/234, 715/235, 715/236, 715/237, 715/255, 709/223, 709/204, 340/5.52
• US Class Current: 715/234
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A method and system that provides for the definition and distribution of business rules is disclosed. The method provides for receiving login information that is used to initiate an authentication process, making an authentication based on the received login information, receiving server communicated XML (Extensible Markup Language) business rules and DTD (document type definition), modifying a business rule based on input from the authenticated source, and the validating of the modified business rule. Moreover, the method and system of the present invention provides for the sending of a new XML business rule to a server. The new business rule is created as a declarative object instead of a programming object.

Claims

1. A method for definition and distribution of business rules, said method comprising computer implemented steps of:

receiving at a user terminal from a server a current set of business rules, the current set of business rules being a programming object, which are written in XML (Extensible Markup Language) with document schema files, wherein the server is remote to the user terminal, and wherein the current set of business rules reflects at least a portion of a valid set of business rules stored on the server when the current set of business rules is received;

receiving login information at the user terminal to initiate an authentication process of a user;

authenticating the user based at least in part on the received login information to determine whether the user is an authenticated user, wherein the authenticated user has privileges to modify the current set of business rules but does not have privileges to modify the valid set of business rules;

modifying, when the user is the authenticated user, the current set of business rules based on received inputs from the authenticated user to obtain a new set of business rules;

validating the new set of business rules against the valid set of business rules stored on the server; and

replacing the current set of business rules with the new set of business rules on the server when the new set of business rules is valid,

wherein the new set of business rules is created as a declarative object instead of a programming object.

2. The method of claim 1, wherein the new set of business rules is validated locally.

3. The method of claim 2, wherein the new set of business rules is validated locally using Document Type Definition (DTD) files.

4. The method of claim 1, wherein the authenticating step determines privileges.

5. The method of claim 1, wherein the business rules are defined in a DTD file.

6. The method of claim 5, wherein business logic is changed by changing a rule in the DTD file.

7. The method of claim 6, wherein a rule consists of a tag, an optional condition set, and an action set.

8. The method of claim 7, wherein the condition set defines conditions that make a rule true.

9. The method of claim 8, wherein the action set defines actions that are performed if all the conditions in the condition set are true.

10. The method of claim 9, wherein a rule is automatically true if it has no condition set.

11. The method of claim 10, wherein the action set is performed if all conditions are true but is ignored otherwise.

12. The method of claim 1, wherein the server is connected to clients via internet.

13. The method of claim 12, wherein the user logs into one of the clients.

14. The method of claim 1, wherein the new set of business rules are validated remotely on the server.

15. A computer usable medium having computer useable code embodied therein for causing a computer to perform operations comprising:

receiving from a server a current set of business rules, the current set of business rules being a programming object, which are written in XML (Extensible Markup Language) with document schema files, wherein the server is connected to client via internet, and a user logs into one of the clients, and wherein the current set of business rules reflects at least a portion of a valid set of business rules stored on the server when the current set of business rules is received;

receiving login information for the user to initiate an authentication process;

authenticating the user based at least in part on the received login information to determine whether the user is an authenticated user, wherein the authenticated user has privileges to modify the current set of business rules but does not have privileges to modify the valid set of business rules;

modifying, when the user is the authenticated user, the current set of business rules based on received inputs from the authenticated user to obtain a new set of business rules;

validating the new set of business rules locally on the client or remotely on the server against the valid set of business rules stored on the server; and

replacing the current set of business rules with the new set of business rules on the server when the new set of business rules is valid,

wherein the new set of business rules is created as a declarative object instead of a programming object.

16. The medium of claim 15, wherein the authentication process determines privileges.

17. The medium of claim 16, wherein business rules are defined in a DTD file.

18. The medium of claim 17, wherein business logic is changed by changing a rule in the DTD file.

19. The medium of claim 18, wherein a rule consists of a tag, an optional condition set, and an action set.

20. The medium of claim 19, wherein the condition set defines conditions that make a rule true.

21. The medium of claim 20, wherein the action set defines actions that are performed if all the conditions in the condition set are true.

22. The medium of claim 21, wherein a rule is automatically true if it has no condition set.

23. The medium of claim 22, wherein the action set is performed if all conditions are true but is ignored otherwise.

24. A computer system comprising:

a bus;

a computer readable memory unit coupled to said bus; and

a processor coupled to said bus for executing a method for implementing an application comprising;

receiving from a server a current set of business rules, the current set of business rules being a programming object, which are written in XML (Extensible Markup Language) with document schema files, wherein the server is connected to client via internet, and a user logs into one of the clients, and wherein the current set of business rules reflects at least a portion of a valid set of business rules stored on the server when the current set of business rules is received;

receiving login information for the user to initiate an authentication process;

authenticating the user based at least in part on the received login information to determine whether the user is an authenticated user, wherein the authenticated user has privileges to modify the current set of business rules but does not have privileges to modify the valid set of business rules;

modifying, when the user is the authenticated user, the current set of business rules based on received inputs from the authenticated user to obtain a new set of business rules;

validating the new set of business rules locally on the client or remotely on the server against the valid set of business rules stored on the server; and

replacing the current set of business rules with the new set of business rules on the server when the new set of business rules is valid,

wherein the new set of business rules is created as a declarative object instead of a programming object.

25. The computer system of claim 24, wherein the authentication process determines privileges.

26. The computer system of claim 25, wherein business rules are defined in a DTD file.

27. The computer system of claim 26, wherein business logic is changed by changing a rule in the DTD file.

28. The computer system of claim 27, wherein a rule consists of a tag, an optional condition set, and an action set.

29. The computer system of claim 28, wherein the condition set defines conditions that make a rule true.

30. The computer system of claim 29, wherein the action set defines actions that are performed if all the conditions in the condition set are true.

31. The computer system of claim 30, wherein a rule is automatically true if it has no condition set.

32. The computer system of claim 31, wherein the action set is performed if all conditions are true but is ignored otherwise.