Constraint-based training data generation
US-2024265138-A1 · Aug 8, 2024 · US
US12271504B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12271504-B2 |
| Application number | US-202318157242-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 20, 2023 |
| Priority date | Jan 20, 2023 |
| Publication date | Apr 8, 2025 |
| Grant date | Apr 8, 2025 |
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 method for managing a data protection module includes: obtaining client metadata associated with client environment (CE) data protection modules, in which the client metadata includes first product configuration information; obtaining vendor metadata associated with a vendor environment (VE) data protection module, in which the vendor metadata includes second product configuration information; analyzing the client metadata and vendor metadata to extract relevant data; obtaining product features that are commonly utilized by at least one user of the CE data protection modules; making a first determination that a mismatch exists between the client metadata and vendor metadata; generating a ranked list of the product features that are commonly utilized; identifying a product feature that has the highest rank in the ranked list; making a second determination that the mismatch is a vendor-related mismatch; and sending a recommendation to a user of the VE data protection module to manage the mismatch.
Opening claim text (preview).
What is claimed is: 1. A method for managing a data protection module, the method comprising: obtaining client metadata associated with a plurality of client environment (CE) data protection modules, wherein the client metadata comprises at least first product configuration information; obtaining vendor metadata associated with a vendor environment (VE) data protection module, wherein the vendor metadata comprises at least second product configuration information; analyzing the client metadata and the vendor metadata to extract relevant data; obtaining, based on the relevant data, a plurality of product features that are commonly utilized by at least one user of the plurality of CE data protection modules; making, based on the relevant data, a first determination that a mismatch exists between the client metadata and the vendor metadata; generating, in response to the first determination, a ranked list of the plurality of product features that are commonly utilized, wherein the ranked list comprises product features ordered based on their respective feature utilization levels; identifying, based on the ranked list, a product feature that has the highest rank in the ranked list; making, based on the first determination, a second determination that the mismatch is a vendor-related mismatch; and sending, based on the second determination, a recommendation to a user of the VE data protection module to manage the vendor-related mismatch. 2. The method of claim 1 , wherein the product feature is a cloud disaster recovery policy, wherein the cloud disaster recovery policy is configured to recover a network-attached storage device that is utilized by the at least one user. 3. The method of claim 1 , wherein the product feature is a centralized protection policy, wherein the centralized protection policy is configured to protect a virtual machine, wherein the virtual machine provides at least one computer-implemented service to the at least one user. 4. The method of claim 1 , wherein the first product configuration information specifies at least one selected from a group consisting of a type of each of a plurality of assets, a number of each type of the plurality of assets, a size of each of the plurality of assets, a type of an operating system, and a number of each type of a plurality of data protection policies, wherein the plurality of data protection policies comprises at least the product feature, wherein the product feature is a cloud disaster recovery policy. 5. The method of claim 1 , wherein the second product configuration information specifies at least one selected from a group consisting of a type of each of a plurality of assets, a number of each type of the plurality of assets, a size of each of the plurality of assets, a type of an operating system, and a number of each type of a plurality of data protection policies, wherein the plurality of data protection policies comprises at least the product feature, wherein the product feature is a centralized protection policy. 6. The method of claim 1 , wherein the feature utilization level of the product feature specifies at least a number of a plurality of users that utilizes the product feature, wherein the plurality of users comprises the at least one user. 7. The method of claim 1 , wherein the relevant data specifies at least a number of each type of a plurality of assets and a size of each of the plurality of assets. 8. The method of claim 1 , wherein the vendor-related mismatch specifies that the VE data protection module is under-testing with respect to the product feature. 9. The method of claim 1 , wherein the recommendation specifies an increase in a number of a plurality of tested assets with respect to the product feature on a testbed. 10. A method for managing a data protection module, the method comprising: obtaining client metadata associated with a plurality of client environment (CE) data protection modules, wherein the client metadata comprises at least first product configuration information; obtaining vendor metadata associated with a vendor environment (VE) data protection module, wherein the vendor metadata comprises at least second product configuration information; analyzing the client metadata and the vendor metadata to extract relevant data; obtaining, based on the relevant data, a plurality of product features that are commonly utilized by at least one user of the plurality of CE data protection modules; making, based on the relevant data, a first determination that a mismatch exists between the client metadata and the vendor metadata; generating, in response to the first determination, a ranked list of the plurality of product features that are commonly utilized, wherein the ranked list comprises product features ordered based on their respective feature utilization levels; identifying, based on the ranked list, a product feature that has the highest rank in the ranked list; making, based on the first determination, a second determination that the mismatch is a client-related mismatch; and sending, based on the second determination, a recommendation to a user of the VE data protection module to manage the client-related mismatch. 11. The method of claim 10 , wherein the product feature is a cloud disaster recovery policy, wherein the cloud disaster recovery policy is configured to recover a network-attached storage device that is utilized by the at least one user. 12. The method of claim 10 , wherein the product feature is a centralized protection policy, wherein the centralized protection policy is configured to protect a virtual machine, wherein the virtual machine provides at least one computer-implemented service to the at least one user. 13. The method of claim 10 , wherein the first product configuration information specifies at least one selected from a group consisting of a type of each of a plurality of assets, a number of each type of the plurality of assets, a size of each of the plurality of assets, a type of an operating system, and a number of each type of a plurality of data protection policies, wherein the plurality of data protection policies comprises at least the product feature, wherein the product feature is a cloud disaster recovery policy. 14. The method of claim 10 , wherein the second product configuration information specifies at least one selected from a group consisting of a type of each of a plurality of assets, a number of each type of the plurality of assets, a size of each of the plurality of assets, a type of an operating system, and a number of each type of a plurality of data protection policies, wherein the plurality of data protection policies comprises at least the product feature, wherein the product feature is a centralized protection policy. 15. The method of claim 10 , wherein the feature utilization level of the product feature specifies at least a number of a plurality of users that utilizes the product feature, wherein the plurality of users comprises the at least one user. 16. The method of claim 10 , wherein the relevant data specifies at least a number of each type of a plurality of assets and a size of each of the plurality of assets. 17. The method of claim 10 , wherein the client-related mismatch specifies that the VE data protection module is over-testing with respect to the product feature. 18. A system for managing a data protection module, the system comprising: a processor comprising circuitry; memory comprising instructions, which when executed perform a method, the method comprising: obtaining client metadata
Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses · CPC title
Hypervisor-specific management and integration aspects · CPC title
using ranking · CPC title
Isolation or security of virtual machine instances · CPC title
to a system of files or objects, e.g. local or distributed file system or database · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.