Infrastructure for an open digital services marketplace

• US 6,205,466 B1
• Filed: 07/17/1998
• Issued: 03/20/2001
• Est. Priority Date: 07/17/1998
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Bronstein, Alexandre, Gupta, Rajiv, Rozas, Guillermo, Krishnan, Venkatesh, Karp, Alan H., Kumar, Sandeep, Banerji, Arindam, Mak, Ernest, Chao, Chia-Chiang
• Primary Examiner(s): BANANKHAH, MAJID A
• Application Number:
  US09/118,248
• Time in Patent Office: 977 Days
• Field of Search: 709/101, 709/102, 709/103, 709/104, 709/216, 709/218, 709/223, 709/224, 709/226, 709/200, 707/1, 707/2, 707/200
• US Class Current: 718/104
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 21/6236 between heterogeneous systems
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G06F 9/468 Specific access rights for resources, e.g. using capability register
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing

Abstract

A software infrastructure for providing an open digital services marketplace including a naming manager that enables a requesting task to refer to a desired resource using a name which is local to the requesting task and a router that forwards the request to an appropriate handler for the desired resource and that enables at least one additional task to be invoked in response to the request. The infrastructure includes a permission manager that compares a set of access rights of the requesting task to the desired resource to a set of permissions associated with the desired resource such that the access rights are kept separately from the reference to the desired resource. The desired resource, the requesting task, the additional task, and a set of additional components used to handle the request are each modeled as a resource defined by a corresponding set of meta-data which includes a set of attributes and a reference to a grammar for interpreting the attributes.

Claims

1. An software infrastructure for an open digital services marketplace, comprising:

naming manager that enables a requesting task to refer to a desired resource using a name which is local to the requesting task by translating the name to a reference to the desired resource in response to a request from the requesting task that specifies the name;

router that forwards the request to an appropriate handler for the desired resource and that enables at least one additional task to be invoked in response to the request;

permission manager that compares a set of access rights of the requesting task to the desired resource to a set of permissions associated with the desired resource such that the access rights are kept separately from the reference to the desired resource;

wherein the desired resource, the requesting task, the additional task, and a set of additional components used to handle the request are each modeled as a resource defined by a corresponding set of meta-data, each set of meta-data having a set of attributes and a reference to a grammar for interpreting the attributes.

2. The software infrastructure of claim 1, wherein the additional task is a grant authorizer that determines whether a name binding contained in the request is to be delivered to the appropriate handler.

3. The software infrastructure of claim 1, wherein the additional task is a notify authorizer that maintains an audit trail of messages associated with the desired resource.

4. The software infrastructure of claim 1, wherein the additional task is an error handler that is to be used if the request causes an error.

5. The software infrastructure of claim 1, wherein the additional components include a key-ring associated with the requesting task which includes a set of keys that are used to unlock the permissions associated with the desired resource.

6. The software infrastructure of claim 5, wherein the router forwards unlocked ones of the permissions to the appropriate resource handler such that the appropriate resource handler is responsible for interpreting semantics of the permissions.

7. The software infrastructure of claim 1, wherein the additional components include the grammar for interpreting the attributes.

8. The software infrastructure of claim 1, wherein the access rights include a set of visibility fields that determine whether the requesting task has a right to use the desired resource.

9. The software infrastructure of claim 1, wherein the additional task is a failure limitation manager which collects reports of a failure associated with the desired resource and which performs an action to limit effects of the failure.

10. The software infrastructure of claim 9, wherein the action is to notify one or more other tasks that the desired resource is unavailable.

11. The software infrastructure of claim 9, wherein the action is to cause the appropriate resource handler to shut down and remove the desired resource from availability.

12. The software infrastructure of claim 1, wherein the grammar for interpreting the attributes is modeled as a resource defined by a corresponding set of meta-data.

13. The software infrastructure of claim 1, wherein the attributes enable a task to discover the corresponding resource using an attribute-based lookup.

14. The software infrastructure of claim 1, wherein the appropriate handler for the desired resource is a core proxy that translates between a local name for the desired resource used by the core proxy and a local name for the desired resource which is used by a task associated with a separate software infrastructure for an open digital services marketplace.

15. The software infrastructure of claim 14, wherein the separate software infrastructure is implemented on a separate computer system.

16. The software infrastructure of claim 1, wherein the appropriate resource handler makes the desired resource available by registering the meta-data for the desired resource.

17. The software infrastructure of claim 1, further comprising a handler that performs an attribute-based lookup on the meta-data to discover the desired resource in response to a request from a task that specifies a set of desired attributes and a grammar for interpreting the desired attributes.

18. The software infrastructure of claim 17, wherein the grammar for interpreting the desired attributes is modeled as a resource defined by a corresponding set of meta-data.

19. The software infrastructure of claim 1, further comprising a monitor that records the request in a monitor database.

20. An apparatus for an open digital services marketplace, comprising:

means for enabling a requesting task to refer to a desired resource using a name which is local to the requesting task by translating the name to a reference to the desired resource in response to a request from the requesting task that specifies the name;

means for forwarding the request to an appropriate handler for the desired resource and for invoking at least one additional task in response to the request;

means for comparing a set of access rights of the requesting task to the desired resource to a set of permissions associated with the desired resource such that the access rights are kept separately from the reference to the desired resource;

wherein the desired resource, the requesting task, the additional task, and a set of additional components used to handle the request are each modeled as a resource defined by a corresponding set of meta-data, each set of meta-data having a set of attributes and a reference to a grammar for interpreting the attributes.