Database system with methods for controlling object interaction by establishing database contracts between objects

• US 5,535,383 A
• Filed: 03/17/1994
• Issued: 07/09/1996
• Est. Priority Date: 03/17/1994
• Status: Expired due to Term

• Current Assignee: Sybase Incorporated (SAP SE)
• Original Assignee: Sybase Incorporated (SAP SE)
• Inventors: Gower, Stefan F.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): WANG, PETER
• Application Number:
  US08/214,375
• Time in Patent Office: 845 Days
• Field of Search: 395/600, 395/650, 380/25, 380/4, 364/401
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A method for ensuring reliable interactions between principals within a database or between databases. The method involves the creation of database contracts which are, in essence, binding constraints on the behavior of entities within a database system that can be enforced by the system. A database contract is formed when two or more principals agree on the terms and conditions of the contract, and a monitor puts in to place the constraints necessary to enforce the agreed-upon terms and conditions after determining that each of the principals has the requisite authority and ability to carry out the contract.

Claims

1. In a computer system comprising a database of objects, a computer-implemented method for controlling objects of said database so that interaction between the objects occurs within constraints specified by the objects themselves, the method comprising:

defining a database contract to comprise a set of constraints which govern interaction of one object with another in said computer system;

initiating a database contract between first and second objects of said database, by sending an offer object from said first object to said second object, said offer object including conditions which must be met before a database contract can exist between the two objects;

if said conditions are acceptable to said second object, sending an acceptance object from said second object to said first object;

determining by a monitor of said computer system whether said first and second objects each has sufficient authority to enter into said database contract, said monitor having no authority over said first and second objects other than monitoring authority of objects to enter database contracts and monitoring compliance of objects which have entered database contracts;

upon receipt by said first object of an acceptance object with sufficient authority, establishing said database contract between said first and second objects of said database, so that interaction between said first and second objects is controlled by said set of constraints of said database contract, said set of constraints of said database contract being enforced by said monitor; and

monitoring by said monitor compliance of each of said first and second objects with said set of constraints to ensure each object'"'"'s performance of the database contract.

2. The method of claim 1 wherein the monitor determines whether each respective one of said first and second objects has sufficient authority and ability by ascertaining whether such respective objects are acting within their respective roles, each role specifying what extent its respective object can enter into a database contract with another object.

3. The method of claim 1 wherein the monitor determines whether each respective one of said first and second objects has sufficient authority and ability by ascertaining whether such respective objects have sufficient respective grants to satisfy all the constraints of the database contract.

4. The method of claim 1 wherein the monitor determines whether each respective one of said first and second objects has sufficient respective grants to satisfy all the constraints of the database contract and has sufficient authority and ability by ascertaining whether such respective objects are acting within their respective roles, each role specifying what extent its respective object can enter into a database contract with another object.

5. The method of claim 1 wherein the monitor prevents establishment of said database contract when one or more of said first and second objects lacks sufficient respective authority.

6. The method of claim 1 wherein the monitor establishes a trigger which is activated if a constraint is violated.

7. The method of claim 6 wherein the trigger activates a notification procedure.

8. The method of claim 1 wherein the database contract exists for the purposes of executing a database procedure.

9. The method of claim 2 wherein said respective roles specify that the respective first and second objects have certain respective grants.

10. The method of claim 1 wherein said set of constraints of the database contract include expiration of the database contract after a preset time.

11. The method of claim 10 wherein the preset time follows a future time established upon occurrence of a future event.

12. A computer-implemented method of establishing a binding relationship between two autonomous objects within a database system, said object being referred to as principals, said binding relationship pertaining to handling of information within the database system, where the binding relationship is enforced by a monitor also contained within the system, said monitor having authority over said principals for verifying requisite authority of each principal, verifying requisite ability of each principal to comply, and verifying compliance of each principal which has entered into a binding relationship, said method comprising the steps of:

sending from a first principal contained within a database within the system an offer which includes terms and conditions of a proposed binding relationship, said terms and conditions specifying constraints necessary for the proposed binding relationship, said offer being received by a second principal contained within the same or a different database within the system;

if said second principal agrees to said terms and conditions of said proposed binding relationship, sending from the second principal to said first principal an acceptance of the offer;

determining by said monitor whether each respective principal has requisite authority to enter into the proposed binding relationship and requisite ability to comply with said terms and conditions of the proposed binding relationship; and

if each respective one of said first and second principals has requisite authority to enter into said proposed binding relationship and requisite ability to comply with the terms and conditions of said proposed binding relationship, establishing said proposed binding relationship between said first and second principals, and, thereafter enforcing said terms and conditions specified as necessary to ensure the performance of the established binding relationship.

13. The method of claim 12 wherein the monitor determines whether each respective principal has said requisite authority and said requisite ability by ascertaining whether such respective principals are acting within their respective roles, each role specifying what extent its respective principal can enter into a binding relationship with another principal.

14. The method of claim 12 wherein the monitor determines whether each respective principal has said requisite authority and said requisite ability by ascertaining whether such respective principals have requisite respective grants to satisfy all the terms and conditions of the proposed binding relationship.

15. The method of claim 12 wherein the monitor determines whether each respective principal has requisite respective grants to satisfy all the terms and conditions of the proposed binding relationship and has said requisite authority and said requisite ability by ascertaining whether such respective principals are acting within their respective roles, each role specifying what extent its respective principal can enter into a binding relationship with another principal.

16. The method of claim 12 wherein the monitor prevents establishment of said proposed binding relationship when one or more of the respective principals lacks said requisite respective authority.

17. The method of claim 12 wherein the monitor establishes a trigger which is activated if a constraint is violated.

18. The method of claim 17 wherein the trigger activates a notification procedure.

19. The method of claim 12 wherein the proposed binding relationship is for the purposes of executing a database procedure.

20. The method of claim 13 wherein requisite respective roles specify that the respective principals have certain respective grants.

21. The method of claim 12 wherein the terms and conditions of the proposed binding relationship include expiration of said binding relationship after a preset time.

22. The method of claim 21 wherein the preset time follows a future time established upon occurrence of a future event.

23. In a computer system, a computer-implemented method for controlling interaction between first and second objects, each object having authority independent of the other, the method comprising:

creating at said first object a set of constraints dictating how said first and second object can interact in said computer system;

communicating said set of constraints to said second object;

determining at said second object whether to accept said set of constraints;

if said constraints are acceptable, determining whether said first and second objects have sufficient authority to enter into a relationship with each other; and

if said first and second objects have sufficient authority to enter into a relationship with each other, establishing said relationship between said first and second objects, by;

storing information in said computer system information indicating that said set of constraints dictate how said first and second object can legally interact in said computer system; and

monitoring interaction between said first and second objects, for ensuring that said constraints are not violated wherein said monitoring step is performed by a monitor object which is independent of said first and second objects.

24. The method of claim 23, wherein said monitoring step is performed by a monitor object which is independent of both said first and second objects, so that said relationship can be established even when said first and second objects are each mutually suspicious of one another.

25. The method of claim 24, wherein said monitor object only has authority to determine whether objects have sufficient authority to enter into relationships with other objects and to determine whether objects do not violate constraints of relationships which they enter into.

26. The method of claim 23, wherein said set of constraints is communicated to said second object as an offer object.

27. The method of claim 23, wherein no object in the system has authority to force another object to interact in a manner which was not first agreed upon by the other object.

28. The method of claim 23, wherein at least one of said objects has authority by virtue of delegation of authority from another object.

29. The method of claim 23, further comprising:

determining whether said first and second objects each has sufficient ability to comply with said set of constraints.

30. The method of claim 23, wherein said set of constraints includes execution of an arbitrary procedure in the system, upon occurrence of a particular event.