Decomposition of resource discovery roles, parts, and transport modeslc

US12073264B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12073264-B2
Application numberUS-202117544565-A
CountryUS
Kind codeB2
Filing dateDec 7, 2021
Priority dateDec 7, 2021
Publication dateAug 27, 2024
Grant dateAug 27, 2024

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

In an example embodiment, three roles are defined for each of the following: resource discovery: provider, aggregator, and consumer. The provider is the one whose resource information will be shared. Rather than the provider needing to implement the complicated API, however, an aggregator may provide that role. The aggregator defines the API and is able to gather resource information from potentially multiple providers (and also, in some embodiments, other aggregators). The consumer then accesses the aggregator to obtain resource information rather than directly accessing the provider.

First claim

Opening claim text (preview).

What is claimed is: 1. A system comprising: at least one hardware processor; and a computer-readable medium storing instructions that, when executed by the at least one hardware processor, cause the at least one hardware processor to perform operations comprising: accessing, at a resource discovery aggregator, one or more resource discovery documents hosted by one or more resource discovery providers, each of the one or more resource discovery providers exposing a configuration file at a configuration file location known to the resource discovery aggregator, the configuration file containing a resource discovery document location, one or more transport modes, comprising a pull transport mode, supported by the corresponding resource discovery aggregator, and a plurality of access strategies for each of at least one of the one or more resource discovery documents, each access strategy including security information to be used when accessing a corresponding resource discovery document, the resource discovery aggregator using the configuration file location to access the one or more resource discovery documents at one or more document locations different than the configuration file location, each resource discovery document indicating one or more capabilities of the corresponding resource discovery provider, the resource discovery aggregator being a different entity than the one or more resource discovery providers; the configuration file location including a uniform resource identifier (URI); storing, at the resource discovery aggregator, information from the one or more resource discovery documents; receiving, from a resource discovery consumer, a request for capability information; in response to the receiving, retrieving the capability information from the stored information; and sending the capability information to the resource discovery consumer. 2. The system of claim 1 , wherein the one or more capabilities includes metadata indicating application program interface capabilities of the corresponding resource discovery provider. 3. The system of claim 2 , wherein the application program interface capabilities include one or more tenant-specific customizations of application program interfaces of the corresponding resource discovery provider. 4. The system of claim 1 , wherein at least one of the resource discovery providers is also a resource discovery aggregator. 5. A method comprising: accessing, at a resource discovery aggregator, one or more resource discovery documents hosted by one or more resource discovery providers, each of the one or more resource discovery providers exposing a configuration file at a configuration file location known to the resource discovery aggregator, the configuration file containing a resource discovery document location, one or more transport modes, comprising a pull transport mode, supported by the corresponding resource discovery aggregator, and a plurality of access strategies for each of at least one of the one or more resource discovery documents, each access strategy including security information to be used when accessing a corresponding resource discovery document, the resource discovery aggregator using the configuration file location to access the one or more resource discovery documents at one or more document locations different than the configuration file location, each resource discovery document indicating one or more capabilities of the corresponding resource discovery provider, the resource discovery aggregator being a different entity than the one or more resource discovery providers; the configuration file location including a uniform resource identifier (URI); storing, at the resource discovery aggregator, information from the one or more resource discovery documents; receiving, from a resource discovery consumer, a request for capability information; in response to the receiving, retrieving the capability information from the stored information; and sending the capability information to the resource discovery consumer. 6. The method of claim 5 , wherein the one or more capabilities includes metadata indicating application program interface capabilities of the corresponding resource discovery provider. 7. The method of claim 6 , wherein the application program interface capabilities includes one or more tenant-specific customizations of application program interfaces of the corresponding resource discovery provider. 8. The method of claim 5 , wherein at least one of the resource discovery providers is also a resource discovery aggregator. 9. A non-transitory machine-readable medium storing instructions which, when executed by one or more processors, cause the one or more processors to perform operations comprising: accessing, at a resource discovery aggregator, one or more resource discovery documents hosted by one or more resource discovery providers, each of the one or more resource discovery providers exposing a configuration file at a configuration file location known to the resource discovery aggregator, the configuration file containing a resource discovery document location, one or more transport modes, comprising a pull transport mode, supported by the corresponding resource discovery aggregator, and a plurality of access strategies for each of at least one of the one or more resource discovery documents, each access strategy including security information to be used when accessing a corresponding resource discovery document, the resource discovery aggregator using the configuration file location to access the one or more resource discovery documents at one or more document locations different than the configuration file location, each resource discovery document indicating one or more capabilities of the corresponding resource discovery provider, the resource discovery aggregator being a different entity than the one or more resource discovery providers; the configuration file location including a uniform resource identifier (URI); storing, at the resource discovery aggregator, information from the one or more resource discovery documents; receiving, from a resource discovery consumer, a request for capability information; in response to the receiving, retrieving the capability information from the stored information; and sending the capability information to the resource discovery consumer. 10. The non-transitory machine-readable medium of claim 9 , wherein the one or more capabilities includes metadata indicating application program interface capabilities of the corresponding resource discovery provider. 11. The non-transitory machine-readable medium of claim 10 , wherein the application program interface capabilities includes one or more tenant-specific customizations of application program interfaces of the corresponding resource discovery provider. 12. The non-transitory machine-readable medium of claim 9 , wherein at least one of the resource discovery providers is also a resource discovery aggregator. 13. A system comprising: at least one hardware processor; and a computer-readable medium storing instructions that, when executed by the at least one hardware processor, cause the at least one hardware processor to perform operations comprising: accessing, at a resource discovery aggregator, one or more resource discovery documents hosted by one or more resource discovery providers, each of the one or more resource discovery providers exposing a configuration file at a configuration file location known to the resource discovery aggregator, the configuration file containing a resource discovery document location, one or more transport modes, comprising a push transport mode,

Assignees

Inventors

Classifications

  • Remote procedure calls [RPC]; Web services · CPC title

  • G06F9/541Primary

    via adapters, e.g. between incompatible applications · CPC title

  • G06F9/50Primary

    Allocation of resources, e.g. of the central processing unit [CPU] · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12073264B2 cover?
In an example embodiment, three roles are defined for each of the following: resource discovery: provider, aggregator, and consumer. The provider is the one whose resource information will be shared. Rather than the provider needing to implement the complicated API, however, an aggregator may provide that role. The aggregator defines the API and is able to gather resource information from poten…
Who is the assignee on this patent?
Sap Se
What technology area does this patent fall under?
Primary CPC classification G06F9/541. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Aug 27 2024 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 5 related publications on this page (citations in our corpus or others sharing the same primary CPC).