System and method for accumulating a historical component context

• US 20070180108A1
• Filed: 04/04/2007
• Published: 08/02/2007
• Est. Priority Date: 12/12/2002
• Status: Abandoned Application

• Current Assignee: Jana Sedivy, Mark Newman, W Edwards
• Original Assignee: Jana Sedivy, Mark Newman, W Edwards
• Inventors: Newman, Mark, Edwards, W., Sedivy, Jana
• Application Number:
  US11/784,164
• Publication Number:
  US 20070180108A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation

Abstract

System and method for accumulating a historical component context. A request that includes a component context and an operation from a requester component is received. A contextual access policy that includes contextual access permissions to the request is applied. A contextual validation is checked that the request satisfies at least one of the contextual access permissions. The operation is performed upon the successful contextual validation of the request. The request is stored as historical component context.

Claims

1. A method for accumulating a historical component context, comprising:

receiving a request comprising a component context and an operation from a requester component;

applying a contextual access policy comprising contextual access permissions to the request;

checking as a contextual validation that the request satisfies at least one of the contextual access permissions;

performing the operation upon the successful contextual validation of the request; and

storing the request as historical component context.

2. The method according to claim 1, further comprising:

applying a property access policy comprising property access permissions to the request;

checking as a property validation that the request satisfies at least one of the property access permissions; and

only performing the operation upon the successful contextual validation and the successful property validation of the request.

3. The method according to claim 1, wherein the request is associated with a component and includes a certificate, comprising:

authenticating said component using the certificate.

4. The method according to claim 1, wherein said request is associated with a component comprising:

comparing said request to a user specified override.

5. The method according to claim 1, wherein the context access permissions are stored as an access entry and comprise one or more of a read, write, and modify permissions.

6. The method according to claim 1, further comprising:

reconstructing a prior configuration for a service that used the requester component and a service component; and

presenting the prior configuration for the service for selection by a user.

7. The method according to claim 1, wherein the component context comprises one or more of a time, location, cause, or identification of the requester component.

8. The method according to claim 1, wherein the component context comprises one or more of a context history collection and a property history collection.

9. The method according to claim 1, wherein the requester component can modify its own properties and the modifications are accumulated in the historical component context.

10. A computer-readable storage medium holding code for performing the method according to claim 1.

11. A system for accumulating a historical component context, comprising:

a receiver mechanism to receive a request comprising a component context and an operation from a requester component;

a contextual security mechanism to apply a contextual access policy comprising contextual access permissions to the request received by the receiver mechanism;

a contextual permission mechanism to check as a contextual validation that the request satisfies at least one of the contextual access permissions;

an operation mechanism to perform the operation upon the successful contextual validation of the request; and

a storage mechanism to store the request as historical component context.

12. The system according to claim 11, further comprising:

a property security mechanism to apply a property access policy comprising property access permissions to the request;

a property permission mechanism to check as a property validation that the request satisfies at least one of the property access permissions; and

a property operation mechanism to only perform the operation upon the successful contextual validation and the successful property validation of the request.

13. The system according to claim 11, wherein the request is associated with a component and includes a certificate comprising:

an authentication mechanism to authenticate said component using the certificate.

14. The system according to claim 11, wherein said request is associated with a component further comprising:

a comparison mechanism to compare the request to a user specified override.

15. The system according to claim 11, wherein the context access permissions are stored as an access entry and comprise one or more of a read, write, and modify permissions.

16. The system according to claim 11, further comprising:

a configuration reconstruction mechanism to reconstruct a prior configuration for a service that used the requester component and a service component; and

a configuration presentation mechanisms to present the prior configuration for the service for selection by a user.

17. The system according to claim 11, wherein the component context comprises one or more of a time, location, cause, or identification of the requester component.

18. The system according to claim 11, wherein the component context comprises one or more of a context history collection and a property history collection.

19. The system according to claim 11, wherein the requester component can modify its own properties and the modifications are accumulated in the historical component context.

20. An apparatus for accumulating a historical component context, comprising:

means for receiving a request comprising a component context and an operation from a requester component;

means for applying a contextual access policy comprising contextual access permissions to the request;

means for checking as a contextual validation that the request satisfies at least one of the contextual access permissions;

means for performing the operation upon the successful contextual validation of the request; and

storing the request as historical component context.