Data loss prevention framework using cloud infrastructure
US-2024176905-A1 · May 30, 2024 · US
US9690812B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9690812-B2 |
| Application number | US-201313764696-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 11, 2013 |
| Priority date | May 4, 2012 |
| Publication date | Jun 27, 2017 |
| Grant date | Jun 27, 2017 |
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.
According to one aspect of the present disclosure, a method and technique for data quality management is disclosed. The method includes: deploying, into a runtime environment with a data stream analytic module, an ingress quality specification (IQS) module associated with the analytic module; receiving, by the IQS module, the data stream; analyzing, by the IQS module, a subset of data of the data stream to determine if the subset of data meets a quality expectation of the analytic module; annotating the subset of data to indicate a quality status based on whether the subset of data meets the quality expectation of the analytic module; and outputting the data stream to the analytic module.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: deploying, into a runtime environment upstream from an analytic module, an ingress quality specification (IQS) module; receiving, by the IQS module, a data stream; analyzing, by the IQS module, a subset of data of the data stream to determine if the subset of data meets a quality expectation of the analytic module; annotating the subset of data to indicate a quality status based on whether the subset of data meets the quality expectation of the analytic module; outputting the data stream with the annotated subset of data to the analytic module; receiving, by the analytic module, the data stream, the analytic module analyzing the data stream to assess an operating characteristic of an upstream device; determining, by the analytic module, the quality status of the subset of data; and responsive to determining that the quality status indicates that the subset of data does not meet the quality expectation, omitting the subset of data from an analysis of the data stream by the analytic module. 2. The method of claim 1 , further comprising receiving a selection of the IQS module from a plurality of IQS modules associated with the analytic module. 3. The method of claim 1 , further comprising: selecting, by the IQS module, a portion of the data stream as the subset of data; and applying, by the IQS module, a predicate to the subset of data. 4. The method of claim 3 , further comprising flagging data of the subset passing the predicate. 5. The method of claim 4 , further comprising flagging data of the subset failing the predicate. 6. The method of claim 1 , further comprising determining, by the IQS module, whether the selected subset of data of the data stream includes a minimum quantity of data samples based on the quality expectation of the analytic module. 7. A method, comprising: deploying, into a runtime environment an analytic module, the analytic module configured to analyze a data stream associated with an upstream object and output an analysis of the object; deploying, into the runtime environment upstream from the analytic module, an ingress quality specification (IQS) module; receiving, by the IQS module, the data stream; analyzing, by the IQS module, a subset of data of the data stream to determine if the subset of data meets a quality expectation of the analytic module; annotating the subset of data via an additional field of the data to indicate a quality status based on whether the subset of data meets the quality expectation of the analytic module; outputting the data stream with the annotated subset of data to the analytic module; receiving, by the analytic module, the data stream; determining, by the analytic module, the quality status of the subset of data; and responsive to determining that the quality status indicates that the subset of data does not meet the quality expectation, omitting the subset of data from an analysis of the data stream by the analytic module. 8. The method of claim 7 , further comprising receiving a selection of the IQS module from a plurality of IQS modules associated with the analytic module. 9. The method of claim 7 , further comprising: selecting, by the IQS module, a portion of the data stream as the subset of data; and applying, by the IQS module, a predicate to the subset of data. 10. The method of claim 9 , further comprising flagging data of the subset passing the predicate. 11. The method of claim 10 , further comprising flagging data of the subset failing the predicate. 12. A method, comprising: deploying, into a runtime environment with a data stream analytic module, an ingress quality specification (IQS) module associated with the analytic module; receiving, by the IQS module, the data stream; analyzing, by the IQS module, a subset of data of the data stream to determine if the subset of data meets a quality expectation of the analytic module; annotating the subset of data to indicate a quality status based on whether the subset of data meets the quality expectation of the analytic module; outputting the data stream with the annotated subset of data to the analytic module; receiving, by the analytic module, the data stream from the IQS module; identifying, by the analytic module, data not meeting the quality expectation based on the annotations; and omitting, by the analytic module, from its analysis of the subset data the data not meeting the quality expectation. 13. The method of claim 12 , further comprising receiving a selection of the IQS module from a plurality of IQS modules associated with the analytic module. 14. The method of claim 12 , further comprising: selecting, by the IQS module, a portion of the data stream as the subset of data; and applying, by the IQS module, a predicate to the subset of data. 15. The method of claim 14 , further comprising flagging data of the subset passing the predicate. 16. The method of claim 15 , further comprising flagging data of the subset failing the predicate.
Ensuring data consistency and integrity · CPC title
Data stream processing; Continuous queries · CPC title
Indexing; Data structures therefor; Storage structures · CPC title
Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors · CPC title
Annotation, e.g. comment data or footnotes · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.