Integrated console environment for diagnostic instruments methods and apparatus
US-2016070862-A1 · Mar 10, 2016 · US
US2021182940A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2021182940-A1 |
| Application number | US-202117175440-A |
| Country | US |
| Kind code | A1 |
| Filing date | Feb 12, 2021 |
| Priority date | Nov 11, 2014 |
| Publication date | Jun 17, 2021 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A service provider system may implement an enterprise catalog service that manages software products and portfolios of software products on behalf of service provider customer organizations. A graph processing service of the enterprise catalog service may create a graph representation of the enterprise catalog service data, including principals, product listings, portfolios, and constraints (and the relationships between them) that may be used to manage access control, launch contexts, and searches within the enterprise catalog service. A primary (key-value) store may maintain an adjacency list and a secondary index of de-normalized edges. A secondary (document) store may maintain the de-normalized edges. In response to various queries directed to the graph processing service, the service may query the adjacency list or the secondary index. For example, one query may return a list of products that an end user can access, and another may return a count of products within a portfolio.
Opening claim text (preview).
What is claimed is: 1 . A system, comprising: a plurality of computing nodes that collectively provide services to an organization that is a customer of a service provider, each of the computing nodes comprising at least one processor and a memory, wherein one or more of the plurality of computing nodes implement an enterprise catalog service platform; wherein the enterprise catalog service platform comprises: a data storage component that stores a definitive view of a collection of data describing principals, portfolios, and product listings, relationships between them within the context of the platform, and constraints on them within the context of the platform, wherein a portfolio is a container comprising one or more product listings; and a graph processing service component; wherein the graph processing service component maintains: a graph representation of the collection of data, wherein the graph representation comprises an adjacency list in which each vertex represents a respective principal, respective group of principals, respective portfolio, or respective product listing and in which each edge represents a relationship between two vertices, and wherein the graph representation is maintained in a data storage component within the graph processing service component; and a search index for the collection of data that is maintained in a search engine component of the graph processing service component; wherein the graph processing service component is configured to: receive, from the data storage component, a communication feed indicating an update to the definitive view of the collection of data; modify, in response to receiving the communication feed, the graph representation of the collection of data; receive, from another component of the platform, a request for information that is directed to the collection of data; access the graph representation or the search index to obtain the requested information; and provide, to the other component of the platform, the requested information. 2 . The system of claim 1 , wherein the request for information comprises a request for an indication on whether or not a given principal is allowed to access a specified product listing. 3 . The system of claim 1 , wherein the request for information comprises a request for all constraints that are applicable when launching a specified product listing on behalf of a given principal for one or more paths from the given principal to the specified product listing. 4 . The system of claim 1 , wherein the request for information comprises a request to query the collection of data for information using search criteria specified in the request. 5 . The system of claim 1 , wherein the communication feed is received from the data storage component in response to a change made in the definitive view of the collection of data by an administrator of the customer organization; and wherein the change comprises the creation of a new product listing, portfolio, or constraint; the addition or removal of a product listing, principal, or constraint to a portfolio; the additional or removal of permission to access a product by a principal; the application of a constraint to a product listing; the sharing of a portfolio, product listing, or constraint with another entity; or the importing of a portfolio, product listing, or constraint from another entity. 6 . A method, comprising: performing, by one or more computers that implement a graph processing service component of an enterprise catalog service on behalf of a service provider: maintaining a graph representation of a collection of data describing principals, portfolios, and listings, relationships between them within the context of the enterprise catalog service, and constraints on them within the context of the enterprise catalog service, wherein a portfolio is a container comprising one or more listings; receiving, on behalf of another component of the enterprise catalog service, a request for information from the collection of data, wherein the requested information is usable by the other component to control access to a listing, to constrain a launch of a listing, or to provide results of a search to a member of a customer organization on whose behalf the graph representation of the collection of data is maintained; accessing the graph representation of the collection of data to obtain the requested information; and providing, to the other component of the platform, the requested information; wherein the graph representation comprises an adjacency list in which each vertex represents a respective principal, respective group of principals, respective portfolio, or respective listing and in which each edge represents a relationship between two vertices. 7 . The method of claim 6 , wherein an edge between a vertex representing a given principal and a vertex representing a given portfolio indicates that the given principal owns or has access to the given portfolio. 8 . The method of claim 6 , wherein an edge between a vertex representing a given principal and a vertex representing a given listing indicates that the given principal owns or has access to the given listing. 9 . The method of claim 6 , wherein an edge between a vertex representing a given portfolio and a vertex representing a given listing indicates that the given portfolio contains the given listing. 10 . The method of claim 6 , wherein the request for information comprises a request for a count of the listings included in a specified portfolio; wherein accessing the graph representation of the collection of data to obtain the requested information comprises performing a lookup operation on a vertex row in the graph representation that represents the portfolio to count edges in the vertex row, each of which represents a listing contained in the portfolio; and wherein returning the requested information comprises returning the count. 11 . The method of claim 6 , wherein the request for information comprises a request for a list of portfolios in which a specified listing is contained or a count of the portfolios in which the specified listing is contained; wherein accessing the graph representation of the collection of data to obtain the requested information comprises performing a lookup operation on each vertex row in the graph representation for a vertex that represents a portfolio to determine whether it includes an edge between the vertex and a vertex representing the specified listing; and wherein returning the requested information comprises returning a count of the number of vertex rows in which an edge between the corresponding portfolio and a vertex representing the specified listing was found or a respective identifier of each portfolio for which an edge between a vertex representing the portfolio and a vertex representing the specified listing was found. 12 . The method of claim 6 , wherein the request for information comprises a request for an indication of whether a given principal is authorized to access a specified listing or to obtain constraints to be applied when the specified listing is launched by the given principal; wherein accessing the graph representation of the collection of data to obtain the requested information comprises traversing the graph representation to determine whether at least one path exists between a vertex representing the given principal and a vertex representing the specified listing; and wherein returning the requested information comprises returning an indication of whether at least one path exists between the vertex representing the given principal and the vertex representing the spec
Managing shopping lists, e.g. compiling or processing purchase lists (shipping orders G06Q10/083; order filling G06Q10/087) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.