Automatic provisioning and onboarding of offline or disconnected machines
US-12182236-B2 · Dec 31, 2024 · US
US2022012239A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2022012239-A1 |
| Application number | US-202017011802-A |
| Country | US |
| Kind code | A1 |
| Filing date | Sep 3, 2020 |
| Priority date | Jul 9, 2020 |
| Publication date | Jan 13, 2022 |
| 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 data analytics system configured to perform operations is disclosed. The operations can include creating, in response to instructions received from a user, a first pipeline. This pipeline can be configured to extract data from an append-only first data store, extract identifying characteristics from the extracted data, provide the identifying characteristics to an identity service, and receive a tenancy identifier from the identity service. The pipeline can further be configured to create a data object in a second data store using the extracted data; create a tenancy object in a metadata store, the tenancy object associated with the data object, the metadata store implementing a hierarchical data object ownership graph; and associate the tenancy object with a parent object in the hierarchical data object ownership graph. The data analytics system can then tear down the first pipeline.
Opening claim text (preview).
What is claimed is: 1 . A data analytics system, comprising: at least one processor; and at least one non-transitory computer-readable medium containing instructions that, when executed by the at least one processor, cause the data storage system to perform operations comprising: creating, in response to instructions received from a user, a first pipeline configured to: extract data from an append-only first data store; extract identifying characteristics from the extracted data; provide the identifying characteristics to an identity service; receive a tenancy identifier from the identity service; create a data object in a second data store using the extracted data; create a tenancy object in a metadata store, the tenancy object associated with the data object, the metadata store implementing a hierarchical data object ownership graph; and associate the tenancy object with a parent object in the hierarchical data object ownership graph; and tearing down the first pipeline following completion of creation of the data object, creation of the tenancy object, and association of the tenancy object with the parent object. 2 . The system of claim 1 , wherein: the extracted data is received from a client and the identifying characteristics comprise an organization code contained in the extracted data. 3 . The system of claim 2 , wherein: the pipeline is configured with: location information specifying a location of the organization code; or a function for generating an organization code using the extracted data. 4 . The system of claim 2 , wherein: the pipeline is configured with format information specifying a format of the organization code 5 . The system of claim 1 , wherein: the association between the tenancy object and the data object is based, at least in part, upon a dependence of a logical or physical location of the data object on the tenancy identifier. 6 . The system of claim 1 , wherein: a user permitted to access a parent object in the hierarchical data object ownership graph is permitted to access data objects associated with all child tenancies of the parent object in the hierarchical data object ownership graph. 7 . The system of claim 6 , wherein: the method further comprises receiving instructions to disassociate the tenancy object with the parent object and associate the tenancy object with a second parent object in the hierarchical data object ownership graph. 8 . The system of claim 1 , wherein: the metadata store implements the hierarchical data object ownership graph by associating a tag representing the parent object with the tenancy object. 9 . A data storage method, comprising: creating, in response to instructions received from a user, a first pipeline configured to: extract data from an append-only first data store; extract identifying characteristics from the extracted data; provide the identifying characteristics to an identity service; receive a tenancy identifier from the identity service; create a data object in a second data store using the extracted data; create a tenancy object in a metadata store, the tenancy object associated with the data object, the metadata store implementing a hierarchical data object ownership graph; and associate the tenancy object with a parent object in the hierarchical data object ownership graph; and tearing down the first pipeline following completion of creation of the data object, creation of the tenancy object, and association of the tenancy object with the parent object. 10 . The data storage method of claim 9 , wherein: the extracted data is received from a client and the identifying characteristics comprise an organization code contained in the extracted data. 11 . The data storage method of claim 10 , wherein: the pipeline is configured with: location information specifying a location of the organization code; or a function for generating an organization code using the extracted data. 12 . The data storage method of claim 10 , wherein: the pipeline is configured with format information specifying a format of the organization code 13 . The data storage method of claim 9 , wherein: the association between the tenancy object and the data object is based, at least in part, upon a dependence of a logical or physical location of the data object on the tenancy identifier. 14 . The data storage method of claim 9 , wherein: a user permitted to access a parent object in the hierarchical data object ownership graph is permitted to access data objects associated with all child tenancies of the parent object in the hierarchical data object ownership graph. 15 . The data storage method of claim 14 , wherein: the method further comprises receiving instructions to disassociate the tenancy object with the parent object and associate the tenancy object with a second parent object in the hierarchical data object ownership graph. 16 . The data storage method of claim 9 , wherein: the metadata store implements the hierarchical data object ownership graph by associating a tag representing the parent object with the tenancy object. 17 . A non-transitory computer-readable medium containing instructions that, when executed by at least one processor of a data analytics system, cause the data analytics system to perform operations comprising: creating, in response to instructions received from a user, a first pipeline configured to: extract data from an append-only first data store, the extracted data received from a client; extract identifying characteristics from the extracted data, the identifying characteristics comprising an organization code contained in the extracted data; provide the identifying characteristics to an identity service; receive a tenancy identifier from the identity service; create a data object in a second data store using the extracted data; create a tenancy object in a metadata store, the tenancy object associated with the data object, the metadata store implementing a hierarchical data object ownership graph, the hierarchical data object ownership graph enabling a user permitted to access a parent object in the hierarchical data object ownership to access data objects associated with all child tenancies of the parent object in the hierarchical data object ownership graph; and associate the tenancy object with a parent object in the hierarchical data object ownership graph; and tearing down the first pipeline following completion of creation of the data object, creation of the tenancy object, and association of the tenancy object with the parent object. 18 . The non-transitory computer-readable medium of claim 17 , wherein: the association between the tenancy object and the data object is based, at least in part, upon a dependence of a logical or physical location of the data object on the tenancy identifier. 19 . The non-transitory computer-readable medium of claim 17 , wherein: the operations further comprise receiving instructions to disassociate the tenancy object with the parent object and associate the tenancy object with a second parent object in the hierarchical data object ownership graph. 20 . The non-transitory computer-readable medium of claim 17 , wherein: the metadata store implements the hierarchical data object ownership graph by associating a tag representing the parent object with the tenancy object.
to perform operations for flow control · CPC title
Schema design and management · CPC title
Query processing support for facilitating data mining operations in structured databases · CPC title
Distributed queries · CPC title
Access rights, e.g. capability lists, access control lists, access tables, access matrices · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.