Data governance method, device, storage medium, equipment and program product
By automatically comparing the user-inputted business intent text with preset governance constraints, a data governance strategy is generated, which solves the problem of strategy omissions in data governance, achieves the integrity and compliance of the strategy, and improves the efficiency of data governance.
Patent Information
- Application Number
- CN202611315567.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-27
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, data governance personnel often overlook certain requirements when translating governance requirements into technical strategies, resulting in incomplete strategies and a lack of automated verification methods, making it difficult to ensure the integrity and compliance of data governance strategies.
By acquiring the user's input of business intent text and the preset governance constraints of the target business, the system automatically compares and verifies the user's expressed natural language governance intent with the structured governance constraints, generates a first verification result to determine the data governance strategy, and ensures the integrity of the strategy.
It enables the coverage and integrity verification of business intent text, discovers governance requirements omitted by users, ensures the integrity and compliance of generated data governance strategies, reduces the workload of manual translation, and improves data governance efficiency.
Smart Images

Figure CN123115111A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of electronic information technology, and more specifically, to a data management method, apparatus, storage medium, device, and program product. Background Technology
[0002] In the field of data governance, governance requirements are typically presented in the form of natural language text. These natural language governance requirements need to be manually understood by data engineers or governance personnel, translated into specific technical strategies, and then deployed to the data system for implementation.
[0003] However, when governance personnel translate governance requirements into technical strategies, the sheer number of requirements and the complexity of the business scenarios involved can easily lead to omissions of certain requirements. These omissions are often difficult to detect during manual review, and the issue of strategy completeness becomes particularly prominent when business scenarios are complex or governance requirements are frequently updated. Summary of the Invention
[0004] To address the aforementioned technical problems, this disclosure provides a data governance method, apparatus, storage medium, device, and program product.
[0005] In a first aspect, this disclosure provides a data governance method, the method comprising: Obtain the business intent text input by the user; the business intent text is used to represent the user's primary management intent for the target business. Obtain multiple preset governance constraints corresponding to the target service; Based on the multiple preset governance constraints, the business intent text is validated to obtain a first validation result; the first validation result is used to characterize whether the business intent text satisfies the multiple preset governance constraints. Based on the first verification result, the data governance strategy for the target business is determined.
[0006] Optionally, the step of validating the business intent text based on the plurality of preset governance constraints to obtain a first validation result includes: Extract the set of governance elements from the business intent text; The first verification result is determined based on the set of governance elements and the multiple preset governance constraints.
[0007] Optionally, determining the first verification result based on the set of governance elements and the plurality of preset governance constraints includes: If the set of governance elements includes the plurality of preset governance constraints, then the first verification result is determined to include the business intent text satisfying the plurality of preset governance constraints; or... If the set of governance elements does not contain the plurality of preset governance constraints, the first verification result is determined to include the business intent text not satisfying the plurality of preset governance constraints.
[0008] Optionally, the method further includes: If the first verification result includes the business intent text not satisfying the multiple preset governance constraints, a first adjustment suggestion corresponding to the business intent text is generated. The first adjustment suggestion is used to indicate that there is a governance intent that needs to be supplemented in the business intent text. The governance intent that needs to be supplemented is determined based on the preset governance constraints that the business intent text does not satisfy.
[0009] Optionally, determining the data governance strategy for the target business based on the first verification result includes: If the first verification result includes the business intent text satisfying the multiple preset governance constraints, the data governance strategy is determined based on the set of governance elements.
[0010] Optionally, the method further includes: Based on the business intent text and the existing governance policy, a second verification result is determined. The second verification result is used to characterize whether there is a conflict between the business intent text and the existing governance policy. The step of determining the data governance strategy for the target business based on the first verification result includes: The data governance strategy is determined based on the first verification result and the second verification result.
[0011] Optionally, determining the second verification result based on the business intent text and existing governance policies includes: Determine whether there is mutual exclusion of actions and / or mutual exclusion of conditions between the business intent text and the existing governance policy; mutual exclusion of actions indicates that there is a conflict between the first governance action indicated by the business intent text and the second governance action indicated by the existing governance policy; mutual exclusion of conditions is used to indicate that there is a conflict between the first execution condition for executing the first governance action and the second execution condition for executing the second governance action. If it is determined that there is mutual exclusion of actions and / or mutual exclusion of conditions between the business intent text and the existing governance policy, the second verification result is determined to include a conflict between the business intent text and the existing governance policy; or... If it is determined that there is no mutual exclusion of actions or conditions between the business intent text and the existing governance policy, the second verification result is determined to include that there is no conflict between the business intent text and the existing governance policy.
[0012] Optionally, the method further includes: If the second verification result includes a conflict between the business intent text and an existing governance policy, a second adjustment suggestion corresponding to the business intent text is generated. The second adjustment suggestion is used to indicate that there is a governance intent in the business intent text that needs to be adjusted. The governance intent that needs to be adjusted is determined based on the existing governance policy that is in conflict.
[0013] Optionally, determining the data governance strategy based on the first verification result and the second verification result includes: If the first verification result includes the business intent text satisfying the multiple preset governance constraints, and the second verification result includes the business intent text not conflicting with existing governance strategies, then the data governance strategy is determined based on the set of governance elements.
[0014] Optionally, when the first verification result includes the business intent text satisfying the plurality of preset governance constraints, and the second verification result includes no conflict between the business intent text and existing governance strategies, determining the data governance strategy based on the set of governance elements includes: If the first verification result includes the business intent text satisfying the multiple preset governance constraints, and the second verification result includes the business intent text having no conflict with existing governance policies, a manual verification result is obtained. The manual verification result is the result of the user verifying the business intent text based on the first verification result and the second verification result. If the manual verification result indicates that the business intent text verification has passed, the data governance strategy is determined based on the set of governance elements.
[0015] Optionally, the method further includes: Acquire the data to be processed; If the data service to be processed is consistent with the service type of the target service corresponding to the data governance strategy, data governance is performed on the data service to be processed according to the data governance strategy.
[0016] Optionally, the method further includes: The data governance results are periodically obtained; the data governance results are the governance results of the data services to be processed according to the data governance strategy. If it is determined that the data governance result does not meet the intent constraints of the business intent text, a third adjustment suggestion is generated. The third adjustment suggestion is used to prompt the user to adjust the data business and / or data governance strategy to be processed.
[0017] Optionally, determining that the data governance result does not satisfy the intent constraints of the business intent text includes: Determine the second governance intent corresponding to the data governance result; If the second governance intent exceeds the constraints of the first governance intent, it is determined that the data governance result does not meet the intent constraints of the business intent text.
[0018] Secondly, this disclosure provides a data governance apparatus, the apparatus comprising: The acquisition module is configured to acquire the business intent text input by the user; the business intent text is used to represent the user's first governance intent for the target business; and acquire multiple preset governance constraints corresponding to the target business. The verification module is configured to verify the business intent text according to the plurality of preset governance constraints and obtain a first verification result; the first verification result is used to characterize whether the business intent text satisfies the plurality of preset governance constraints. The determination module is configured to determine the data governance strategy of the target service based on the first verification result.
[0019] Thirdly, this disclosure provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the data governance method described in the first aspect above.
[0020] Fourthly, this disclosure provides an electronic device, comprising: a memory storing a computer program thereon; and a processor for executing the computer program in the memory to implement the steps of the data governance method described in the first aspect.
[0021] Fifthly, this disclosure provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the data governance method described in the first aspect.
[0022] The above technical solution first obtains the user-inputted business intent text, which represents the user's first governance intent for the target business. Then, it obtains multiple preset governance constraints corresponding to the target business. Next, it verifies the business intent text based on these preset constraints, obtaining a first verification result. This first verification result indicates whether the business intent text satisfies the preset governance constraints. Finally, it determines the data governance strategy for the target business based on the first verification result. In other words, by obtaining the user-inputted business intent text and the preset governance constraints corresponding to the target business, the system can automatically compare and verify the user's expressed natural language governance intent with the structured governance constraints, thereby proactively identifying any governance requirements missed by the user and verifying the completeness of the business intent text coverage. Furthermore, by generating a first verification result indicating whether the business intent text satisfies the preset governance constraints, and determining the data governance strategy based on this first verification result, the system effectively ensures that the generated data governance strategy has high completeness.
[0023] Other features and advantages of this disclosure will be described in detail in the following detailed description section. Attached Figure Description
[0024] The accompanying drawings are provided to further illustrate the present disclosure and form part of the specification. They are used together with the following detailed description to explain the present disclosure, but do not constitute a limitation thereof. In the drawings: Figure 1 This is a flowchart illustrating a data governance method according to an exemplary embodiment.
[0025] Figure 2 This is a schematic diagram illustrating an intent to cover integrity verification according to an exemplary embodiment.
[0026] Figure 3 This is a block diagram illustrating a data management apparatus according to an exemplary embodiment.
[0027] Figure 4 This is a block diagram illustrating another data management apparatus according to an exemplary embodiment.
[0028] Figure 5 This is a block diagram illustrating another data management apparatus according to an exemplary embodiment.
[0029] Figure 6 This is a block diagram illustrating an electronic device according to an exemplary embodiment. Detailed Implementation
[0030] The specific embodiments of this disclosure will be described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for illustration and explanation only and are not intended to limit this disclosure.
[0031] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily construed as referring to a specific order or sequence. Furthermore, in the description with reference to the accompanying drawings, the same reference numerals in different drawings denote the same elements.
[0032] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.
[0033] In the description of this disclosure, unless otherwise stated, "multiple" means two or more, and other quantifiers are similar; "at least one," "one or more," or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one 'a' can represent any number of 'a's; as another example, one or more of a, b, and c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple; "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. The character " / " indicates that the preceding and following related objects are in an "or" relationship.
[0034] Although operations or steps are described in a specific order in the accompanying drawings in the embodiments of this disclosure, it should not be construed as requiring these operations or steps to be performed in the specific order or serial order shown, or requiring all of the shown operations or steps to be performed to obtain the desired result. In the embodiments of this disclosure, these operations or steps may be performed serially; they may be performed in parallel; or a portion of these operations or steps may be performed.
[0035] Before introducing the data governance methods, apparatus, storage media, devices, and program products provided in this disclosure, the application scenarios involved in the various embodiments of this disclosure will first be introduced. This disclosure can be applied to data governance scenarios. In the field of data governance, governance requirements are usually put forward in the form of natural language text. For example, the legal department may put forward governance requirements such as "customer mobile phone numbers should be anonymized for non-customer service roles" or "data involving minors needs additional protection." These governance requirements in natural language form need to be manually understood by data engineers or governance personnel and translated into specific technical strategies, such as database anonymization rules, row-level access control policies, or classification and tagging rules, before being deployed to the data system for execution.
[0036] With the rapid growth of enterprise data volume and the increasing refinement of governance requirements, this manual translation model faces growing challenges. Especially in complex data governance scenarios involving multiple business systems and various data types, governance personnel need to handle a large number of governance requirements simultaneously and ensure that each requirement is accurately and completely translated into technical strategies.
[0037] In response, the inventors discovered through long-term practice that the above method has the following problems: First, when translating governance requirements into technical policies, governance personnel often rely on personal experience to judge the completeness of the policies due to the large number of requirements and the complexity of the business scenarios involved. This can easily lead to omissions of certain governance requirements. For example, governance personnel may focus on anonymization requirements but overlook data retention period requirements or cross-border transfer restrictions. Such omissions are difficult to detect during manual review because existing verification methods can only check for grammatical errors or logical contradictions in the written policies, and cannot identify governance requirements that should have been included but were not. The issue of policy completeness is particularly prominent when business scenarios are complex or governance requirements are frequently updated.
[0038] Second, due to the lack of automated verification methods, the completeness and compliance of data governance strategies heavily rely on the personal experience and expertise of governance personnel. For the same set of governance requirements, different governance personnel may generate governance strategies with different coverage, leading to inconsistent governance results.
[0039] Third, when regulations or internal rules change, existing solutions cannot promptly identify whether existing governance strategies lack new regulatory requirements, whether historical strategies have coverage gaps, or whether existing governance strategies still meet governance requirements under new regulations, making it difficult to ensure the continued compliance of governance strategies.
[0040] To address the aforementioned technical problems, this invention provides a data governance method, apparatus, storage medium, device, and program product. By acquiring the user-inputted business intent text and obtaining the preset governance constraints corresponding to the target business, it can automatically compare and verify the user's expressed natural language governance intent with the structured governance constraints, thereby proactively identifying governance requirements omitted by the user and verifying the completeness of the business intent text coverage. Furthermore, it generates a first verification result characterizing whether the business intent text meets the preset governance constraints, and determines the data governance strategy based on this first verification result, effectively ensuring that the generated data governance strategy has high completeness.
[0041] The specific embodiments of the present invention will now be described in detail with reference to the accompanying drawings.
[0042] Figure 1 This is a flowchart illustrating a data governance method according to an exemplary embodiment, such as... Figure 1 As shown, the method may include the following steps: In step S101, the business intent text input by the user is obtained.
[0043] The business intent text represents the user's initial governance intent regarding the target business. This text refers to the user's governance expectations for the target business, expressed in natural language. For example, a user might enter descriptions such as "Customer phone numbers should be completely invisible to non-customer service roles" or "Data involving minors requires additional protection" on the data governance platform's interface. The target business refers to the specific business scenario for which the user expects data governance, such as a customer information management system, log analysis system, or user profiling system. The initial governance intent refers to the user's original governance expectation, i.e., the semantic content expressed by the business intent text.
[0044] Specifically, users can input business intent text through the interactive interface provided by the data governance platform. This interface may include a text input box, a voice input interface, or a file upload interface. Users can input business intent text through keyboard input, voice-to-text conversion, or by uploading a document containing governance intent. After obtaining the business intent text, it is stored in memory or a database and associated with the current user's identity information and the input time.
[0045] In some embodiments, after obtaining the business intent text, the business intent text can be preprocessed. This preprocessing includes, but is not limited to: removing irrelevant punctuation and stop words, performing word segmentation and part-of-speech tagging on the text, and identifying key entities and action words in the text. For example, for the business intent text "Customer mobile phone numbers should be completely invisible to non-customer service roles," preprocessing can identify "customer mobile phone number" as the governance object, "non-customer service role" as the subject condition, and "completely invisible" as the governance action.
[0046] Furthermore, semantic understanding can be performed on business intent text to identify the user's primary governance intent. This semantic understanding can employ deep learning model-based methods, such as using a predictive language model to encode the business intent text and extract its semantic vectors, thereby determining the user's expressed governance intent.
[0047] In step S102, multiple preset governance constraints corresponding to the target service are obtained.
[0048] The pre-defined governance constraints refer to pre-established criteria used to assess the completeness of governance intentions. These pre-defined governance constraints can be a set of rules pre-established based on laws, regulations, industry standards, or internal company rules. For example, for business scenarios involving personal information, pre-defined governance constraints could include "personal information should be anonymized," "access to personal information should be restricted," and "a retention period should be set for personal information." These multiple pre-defined governance constraints correspond to the specific data business; that is, different data businesses can correspond to different sets of pre-defined governance constraints.
[0049] Specifically, based on the business type of the target business that the user currently expects to govern, preset governance constraints corresponding to the target business can be retrieved from a pre-established constraint database. This constraint database stores the correspondence between different business types and governance constraints. For example, for businesses involving personal information processing, the corresponding preset governance constraints may include "de-identification requirements," "access control requirements," "retention period requirements," and "cross-border transmission restrictions," etc.
[0050] In step S103, the business intent text is validated according to the multiple preset governance constraints to obtain the first validation result.
[0051] The first verification result is used to characterize whether the business intent text meets the multiple preset governance constraints.
[0052] Specifically, these multiple preset governance constraints can be used as the basis for verification to perform a coverage integrity check on the business intent text. This check is used to determine whether the business intent text entered by the user covers all necessary governance constraints, thereby identifying governance requirements that the user may have overlooked. During the verification process, a set of governance elements can first be extracted from the business intent text. Then, the extracted set of governance elements is compared with the preset governance constraints to determine whether the governance elements in the set cover all preset governance constraints. For example, if the preset governance constraints include "de-identification requirements" and "retention period requirements," but the business intent text only mentions de-identification and not retention period, then the first verification result indicates that the business intent text does not meet the preset governance constraints.
[0053] The first verification result is used to characterize whether the business intent text meets the multiple preset governance constraints. This first verification result can include two states: "satisfied" and "not satisfied." In the case of "not satisfied," the first verification result can further indicate which specific preset governance constraints are not covered, so that adjustment suggestions can be generated subsequently.
[0054] In step S104, the data governance strategy for the target service is determined based on the first verification result.
[0055] Specifically, when the first verification result indicates that the business intent text meets all preset governance constraints, a data governance strategy for the target business can be generated based on the set of governance elements in the business intent text. This data governance strategy may include specific governance rules, such as, but not limited to, de-identification rules, access control rules, and data retention rules. The generated governance strategy is stored in a strategy library and associated with the target business. It can also be distributed to the data governance execution engine, which applies these rules in real time during data access or data processing.
[0056] By acquiring the user-inputted business intent text and corresponding preset governance constraints, the system automatically performs coverage and integrity checks on the business intent text. This effectively identifies governance requirements missed by the user, avoiding data security risks caused by incomplete governance intent and ensuring the completeness and compliance of the generated data governance strategy. Simultaneously, automated verification and strategy generation reduce the workload of manually translating governance requirements line by line, improving the efficiency of data governance.
[0057] By employing the above method, and acquiring the user's input business intent text and the corresponding preset governance constraints, the system can automatically compare and verify the user's expressed natural language governance intent with the structured governance constraints. This proactively identifies any governance requirements missed by the user, thereby verifying the completeness of the business intent text coverage. Furthermore, a first verification result is generated, indicating whether the business intent text meets the preset governance constraints. Based on this first verification result, a data governance strategy is determined, effectively ensuring the high completeness of the generated data governance strategy.
[0058] The specific implementation of step S103 above will be explained in detail below. Step S103, based on the multiple preset governance constraints, verifies the business intent text to obtain the first verification result, which may include the following steps: In step S1031, the set of governance elements in the business intent text is extracted.
[0059] Specifically, natural language processing technology can be used to parse business intent text and extract governance elements related to data governance from it.
[0060] For example, the governance elements may include, but are not limited to, the governance object (i.e., the data assets or data fields that need to be governed, such as "customer mobile phone number", "ID number", "minor data"), the governance action (i.e., the type of operation that needs to be performed on the governance object, such as "de-identification", "row-level filtering", "category tagging", "access denial"), the subject conditions (i.e., the subject scope to which the governance action applies, such as "non-customer service role", "administrator", "external user"), and the scenario information (i.e., the business scenario to which the governance action applies, such as "cross-border transfer", "data retention", "data sharing").
[0061] In some embodiments, rule-based or machine learning-based methods can be used to extract governance elements from business intent text.
[0062] For example, business intent text can be input into a large language model and compiled into a structured data format through restricted grammar parsing. This restricted grammar parsing means constraining the output of the large language model to a fixed data structure format (schema), thereby fundamentally eliminating the unparseable problems caused by free text. Specifically, when calling the large language model, restricted parsing can be implemented in the following ways: specifying the output format as JSON (JavaScript Object Notation) in the model inference request and predefining the field names, data types, and value ranges of the output JSON; or using the large language model's function calling functionality to constrain the output to a predefined function parameter structure; or adding a layer of structure validation after model inference to verify the format of the model output, rejecting output that does not conform to the preset schema and triggering regeneration.
[0063] The fixed data structure format includes at least the following fields: governance object description field, governance action field, and subject condition field. Optionally, it may also include constraint field, exception field, and governance clause reference field. Taking the user input "Customer mobile phone number should be completely invisible to non-customer service roles" as an example, after restricted parsing and compilation, the following structured data can be obtained: Governance object: Customer mobile phone number (which can be further aligned to the semantic tag "PII.PHONE"); Governance action: Completely invisible (can be mapped to a desensitization action, with a desensitization level of full mask); Subject condition: Non-customer service role.
[0064] Then, a set of governance elements can be extracted from the compiled structured data. This set of governance elements includes at least one of the following: governance objects, governance actions, and subject conditions. Specifically, the governance object description field in the structured data can be mapped to the governance object in the governance elements; the governance action field in the structured data can be mapped to the governance action in the governance elements; and the subject condition field in the structured data can be mapped to the subject condition in the governance elements.
[0065] Furthermore, during the compilation process, the description of the governance object in the business intent text can be aligned to a preset semantic tag system (which can be used to build data governance strategies), so that when performing data governance later, the data governance strategy that needs to be called can be quickly located through semantic tags.
[0066] Specifically, a semantic tag dictionary can be pre-built, and then the description of the governance object in the business intent text can be matched with tags in the semantic tag dictionary. This matching can employ at least one of the following methods: vector retrieval (converting the governance object description into a vector representation and retrieving the most similar tag from the vector index of the semantic tag dictionary) or synonym matching (matching words in the governance object description with tag names or tag aliases based on a pre-built thesaurus). If the match is successful (similarity reaches a preset threshold), the governance object is associated with the corresponding semantic tag. If the match fails (similarity is below the preset threshold or no tag can be matched), the user can be prompted through the user interface to clarify the specific type of the governance object.
[0067] Additionally, during the compilation process, determinate attributes (intent_props) can be extracted synchronously from the business intent text for subsequent intent offset determination in application scenarios. Each determinate attribute has a clearly defined value range, enabling automatic determination in subsequent steps.
[0068] Specifically, the determinate attribute may include at least one of the following: upper bound of disclosure, irreversibility, identifiability level, and covered object set. The upper bound of disclosure represents the upper limit of the information exposure level. Its value is mapped to a preset disclosure level order, which can be arranged from low to high information exposure level, in the following order: deny, full mask (0 bits visible), partially visible (k bits visible, the larger k is, the higher), and plaintext. For example, the upper bound of disclosure corresponding to the intent "customer's mobile number is completely invisible" is full mask (0 bits visible). Irreversibility represents whether the data after governance can be restored, and its value is a Boolean value (true or false). For example, the irreversibility corresponding to the intent "customer's mobile number is completely invisible" is true. The identifiability level represents whether the data after governance can still identify a specific individual, and its value is a preset enumeration type. The covered object set represents the scope of data objects that the business intent needs to govern. Its value is a tag criterion expression, which can be evaluated as a specific set of data objects on the target business's assets. For example, tag... PII.PHONE represents all data objects that are tagged with PII.PHONE.
[0069] The compiled business intent text can be presented to users in two formats simultaneously, facilitating both human review and machine processing. Specifically, it can include a natural language summary format (the governance expectations for the target business expressed in natural language, i.e., the business intent text) and structured data (i.e., a collection of governance elements consisting of various fields and their values presented in tables, key-value pairs, or JSON format after compilation).
[0070] In step S1032, the first verification result is determined based on the set of governance elements and the multiple preset governance constraints.
[0071] In this step, the extracted set of governance elements can be compared with the preset governance constraints to determine whether the set of governance elements covers all preset governance constraints. Coverage means that the governance elements contain governance requirements corresponding to the preset governance constraints. For example, if the preset governance constraints include "de-identification requirements," then the set of governance elements should contain governance actions related to de-identification; if the preset governance constraints include "access control requirements," then the set of governance elements should contain subject condition information.
[0072] Specifically, if the set of governance elements includes the multiple preset governance constraints, the first verification result is determined to include that the business intent text satisfies the multiple preset governance constraints; or, if the set of governance elements does not include the multiple preset governance constraints, the first verification result is determined to include that the business intent text does not satisfy the multiple preset governance constraints.
[0073] For example, the preset governance constraints can be matched one by one with the governance elements in the governance element set. If a governance element corresponding to all preset governance constraints can be found in the governance element set, the business intent text is determined to satisfy all preset governance constraints, and the first verification result is "satisfied". For example, suppose the preset governance constraints include "de-identification processing requirements" and "access control requirements". If the governance elements extracted from the business intent text include "de-identification" (corresponding to the de-identification processing requirements) and "non-customer service role" (corresponding to the access control requirements), then the governance element set is determined to contain all preset governance constraints, and the first verification result is "satisfied". If the governance element set lacks a governance element corresponding to any preset governance constraint, then the business intent text is determined not to satisfy the preset governance constraints, and the first verification result is "not satisfied". For example, suppose the preset governance constraints include "de-identification processing requirements", "access control requirements", and "retention period requirements". If the governance elements extracted from the business intent text include "de-identification" and "non-customer service role", but do not involve retention period-related content, then the governance element set is determined not to contain all preset governance constraints, and the first verification result is "not satisfied".
[0074] Furthermore, the set of governance elements that does not include the multiple preset governance constraints can be further divided into the set of governance elements that does not include all the preset governance constraints (i.e., none of them are satisfied), and the set of governance elements that does not include some of the preset governance constraints (i.e., some of them are not satisfied).
[0075] In some embodiments, if the first verification result includes the business intent text not satisfying the plurality of preset governance constraints, a first adjustment suggestion corresponding to the business intent text is generated. This first adjustment suggestion is used to indicate that there is a governance intent in the business intent text that needs to be supplemented, and this supplementary governance intent is determined based on the preset governance constraints that the business intent text does not satisfy.
[0076] For example, if the preset governance constraints include "data anonymization requirements," "access control requirements," and "retention period requirements," but the governance elements corresponding to the business intent text only contain anonymization and access control-related content and lack retention period-related content, then the generated first adjustment suggestion could include: "Your business intent text lacks governance requirements regarding data retention period; it is recommended to supplement the data retention period and destruction strategy." Specifically, this first adjustment suggestion can be presented to the user through a user interface using text, icons, or highlighted annotations. After supplementing and modifying the business intent text according to the adjustment suggestion, the user can re-execute the above verification steps until the verification passes.
[0077] In some embodiments, if the first verification result includes the business intent text satisfying the multiple preset governance constraints, the data governance strategy is determined based on the set of governance elements.
[0078] For example, when the first verification result indicates that the business intent text meets all preset governance constraints, the extracted set of governance elements can be converted into a data governance strategy. Specifically, this conversion may include determining the target of the strategy based on the governance objects in the governance elements, determining the action type of the strategy based on the governance actions in the governance elements, determining the scope of application of the strategy based on the subject conditions in the governance elements, and determining the effective conditions of the strategy based on the scenario information in the governance elements.
[0079] For example, for the business intent text "Customer mobile number should be completely invisible to non-customer service roles," the extracted governance elements include the governance object "customer mobile number," the governance action "completely invisible" (corresponding to data masking), and the subject condition "non-customer service role." The data governance strategy generated based on these governance elements can include: performing data masking on the customer mobile number field, with the masking rule being "completely invisible." This strategy applies to data access requests from non-customer service roles.
[0080] Figure 2 This is a schematic diagram illustrating an intent to cover integrity verification according to an exemplary embodiment, such as... Figure 2As shown, firstly, the user-inputted business intent text can be obtained as the starting data for validation. This business intent text represents the user's initial governance intent regarding the target business. Next, a set of governance elements E is extracted from the business intent text. Specifically, based on the preset governance constraints (i.e., the governance ontology, which includes a mapping relationship of "scenario-element-required clauses"), the elements to be governed can be extracted from the business intent text to form an element set E. These governance elements include, but are not limited to: governance object, subject conditions, governance actions, and scenario information. Then, coverage detection is performed on the business intent text. Specifically, each governance element in the extracted set of governance elements E can be mapped to the preset governance constraints, and the coverage status of each element can be marked. According to the mapping results, each governance element is marked as one of the following three states: Covered: The governance element set contains the governance requirements corresponding to the preset governance constraints. Partially Covered: The governance element set contains some of the governance requirements corresponding to the preset governance constraints, but not completely. Covered: The governance element set does not contain any of the governance requirements corresponding to the preset governance constraints. Further, based on the coverage mapping results, gap detection can be performed on each governance element to generate a gap list. The gap detection is divided into deterministic gaps and suggestive gaps. Specifically, for governance requirements that are mandatory in the preset governance constraints, if they are not included in the governance element set, it is a deterministic gap; for governance requirements that are suggested but not mandatory in the preset governance constraints, if they are not included in the governance element set, it is a suggestive gap. A deterministic gap can be marked as "blocked," and the user will be returned with the first verification result and the first adjustment suggestion, meaning the user needs to supplement the requirement before continuing. A suggestive gap can be marked as "suggested," allowing the user to decide whether to supplement it, without mandatory blocking. For example, in the "minor data" scenario, if the preset governance conditions explicitly require a "retention period limit," but the governance element set does not cover this requirement, a deterministic gap is generated, indicating "missing retention period limit clause"; if an element is a recommended requirement, a suggestive gap is generated, marked as "suggested supplementation."
[0081] Through the above verification process, we can proactively identify governance requirements that users have overlooked, transforming the missed intentions from invisible to an explicit list of gaps, and providing users with clear directions for supplementation, thereby ensuring the integrity and compliance of the governance strategy.
[0082] In some embodiments, a conflict detection step may be included to further detect whether the current business intent text conflicts with an existing governance policy. Specifically, a second verification result can be determined based on the business intent text and the existing governance policy. This second verification result characterizes whether the business intent text conflicts with the existing governance policy. The data governance policy is then determined based on the first verification result and the second verification result.
[0083] The existing governance strategy refers to a governance strategy that is currently in effect in the target business or other businesses. These strategies are stored in a strategy repository, and each strategy includes information such as strategy identifier, strategy content, scope of effect, and creation time.
[0084] Before generating a new data governance strategy, the business intent text can be compared with existing governance strategies to detect any conflicts. A conflict occurs when the governance action indicated by the business intent text contradicts the governance action indicated by an existing governance strategy under the same conditions. Then, the data governance strategy can be determined based on the first and second verification results. In other words, when determining the data governance strategy, it is necessary to consider not only whether the business intent text covers all preset governance constraints (i.e., the first verification result), but also whether the business intent text conflicts with existing governance strategies (i.e., the second verification result). A data governance strategy will only be generated if both the first and second verification results meet the conditions.
[0085] Specifically, determining the second verification result based on the business intent text and the existing governance policy includes: determining whether there is mutual exclusion of actions and / or mutual exclusion of conditions between the business intent text and the existing governance policy.
[0086] The mutual exclusion of actions indicates a conflict between the first governance action indicated by the business intent text and the second governance action indicated by the existing governance policy. For example, the business intent text requires anonymizing customer mobile phone numbers, while the existing governance policy requires that customer mobile phone numbers be visible in plaintext. These two governance actions contradict each other under the same conditions, constituting mutual exclusion. Similarly, the business intent text requires allowing finance roles to access payroll data, while the existing governance policy requires denying finance roles access to payroll data, also constituting mutual exclusion. The conditional mutual exclusion is used to indicate a conflict between the first execution condition for executing the first governance action and the second execution condition for executing the second governance action. For example, the effective condition of the business intent text is "user role is customer service," while the effective condition of the existing governance policy is "user role is not customer service," these two conditions conflict.
[0087] If it is determined that there is mutual exclusion of actions and / or mutual exclusion of conditions between the business intent text and the existing governance policy, the second verification result is determined to include a conflict between the business intent text and the existing governance policy; or, if it is determined that there is no mutual exclusion of actions and mutual exclusion of conditions between the business intent text and the existing governance policy, the second verification result is determined to include a conflict between the business intent text and the existing governance policy.
[0088] If it is determined that there is mutual exclusion of actions and / or conditions between the business intent text and the existing governance policy, the second verification result is determined to include a conflict between the business intent text and the existing governance policy. If it is determined that there is no mutual exclusion of actions and conditions between the business intent text and the existing governance policy, the second verification result is determined to include no conflict between the business intent text and the existing governance policy.
[0089] Furthermore, if the second verification result includes a conflict between the business intent text and an existing governance strategy, a second adjustment suggestion corresponding to the business intent text can also be generated.
[0090] The second adjustment suggestion is used to indicate that there is a governance intent in the business intent text that needs to be adjusted. The governance intent that needs to be adjusted is determined based on the existing governance policy that is in conflict.
[0091] For example, suppose the business intent text requires the phone number to be displayed in anonymized form for customer service roles, while an existing governance policy requires the phone number to be displayed in plain text for customer service roles, creating a conflict. The generated second adjustment suggestion could include: "Your business intent text conflicts with an existing governance policy regarding 'customer service role access to phone number.' The existing governance policy requires plain text display, while your intent requires anonymized display. We suggest you adjust your intent or modify the existing governance policy to eliminate the conflict." This second adjustment suggestion can be presented to the user through the user interface using text, icons, or highlighted text. After modifying the business intent text according to the adjustment suggestion, the user can re-execute the conflict detection step.
[0092] The above steps, based on the first verification result and the second verification result, determine the data governance strategy, which may include: when the first verification result shows that the business intent text satisfies the multiple preset governance constraints, and the second verification result shows that there is no conflict between the business intent text and the existing governance strategy, the data governance strategy is determined based on the set of governance elements.
[0093] In other words, a data governance strategy is generated only when the business intent text passes the coverage integrity check (satisfies all preset governance constraints) and the conflict detection (does not conflict with existing governance strategies). The simultaneous fulfillment of these two conditions ensures that the newly generated governance strategy is both complete and consistent.
[0094] Furthermore, to ensure the reliability of the final generated data governance strategy, a manual review step can be added. Specifically, if the first verification result shows that the business intent text meets the multiple preset governance constraints, and the second verification result shows that there is no conflict between the business intent text and the existing governance strategy, a manual verification result is obtained. This manual verification result is the result of the user verifying the business intent text based on the first and second verification results. If the manual verification result indicates that the business intent text has passed verification, the data governance strategy is determined according to the set of governance elements.
[0095] In other words, the first verification result (coverage integrity verification report) and the second verification result (conflict detection report) can be presented to the user. The user reviews the business intent text based on these verification results to confirm whether the governance requirements of the business intent text are complete, whether there are any undetected conflicts with existing policies, and whether it meets actual business needs. After review, the user submits a manual verification result through the user interface, which includes whether the verification passed or failed. If the manual verification result indicates that the business intent text has passed verification, the data governance strategy is determined based on the set of governance elements. If the manual verification result indicates that the verification has failed, the user can be prompted to modify the business intent text, and the verification and validation process will be re-executed after modification. By setting up a manual verification step, human judgment can be introduced on top of automatic verification, further improving the accuracy and rationality of the governance strategy.
[0096] After manual verification, in order to facilitate subsequent audits and retrieval of verification records, one embodiment of this disclosure may further include a configuration graph construction step, which is used to store and associate the generation process of data governance strategies and related information in a structured graph model.
[0097] Specifically, when the manual verification result indicates that the business intent text has passed verification—that is, when the first verification result indicates that the business intent text meets the preset governance constraints, the second verification result indicates that there is no conflict between the business intent text and the existing governance strategy, and the manual verification has passed—then manual verification information is obtained. This manual verification information includes at least one of the following: reviewer, review time, and review result. The reviewer refers to the identity identifier of the operator who manually reviews the business intent text, such as a user account or employee number. The review time refers to the timestamp of the completion of the manual verification operation. The review result refers to the conclusion of the manual verification, including verification passed or verification failed. After obtaining the manual verification information, a configuration diagram can be constructed based on the structured specifications of the business intent text, the governance element set, and the manual verification information. This configuration diagram is a structured graph model used to associate and store the various elements involved in the data governance strategy generation process and their relationships.
[0098] For example, this configuration graph may include business intent nodes, governance element nodes, review nodes, and policy nodes. The business intent node corresponds to the user-inputted business intent text, recording the intent identifier and intent content. The governance element node corresponds to the second governance element extracted from the business intent text, recording the type and content of each governance element. The review node corresponds to manually verified information, recording the reviewer, review time, and review result. The policy node corresponds to the finally determined governance policy, recording the policy identifier, policy type, and policy content. Nodes in this configuration graph can be linked by the following edges: a compilation edge between the business intent node and the governance element node, representing the relationship where the business intent is compiled into structured data; a verification edge between the governance element node and the review node, representing the relationship where the governance element is manually verified; and a generation edge between the governance element node and the policy node, representing the relationship where the governance element is converted into a policy. The configuration graph constructed in this way is stored in a structured form in a graph database, supporting subsequent audit queries and policy traceability. Once the configuration graph is constructed, it can be used to quickly trace the source of a governance policy. For example, starting from the policy node, it can trace back along the generation and compilation edges to the business intent node and the review node, thereby obtaining the original business intent text, manual verification information and structured data corresponding to the policy. This provides a structured data foundation for subsequent audit traceability and improves the traceability and transparency of data governance decisions.
[0099] Furthermore, if auditors need to query the configuration diagram, they can enter the corresponding audit question. After receiving the audit question entered by the user (e.g., auditor), the constructed configuration diagram is queried in response to the audit question.
[0100] Specifically, the audit question can be parsed into a graph query statement for the configuration graph. First, semantic analysis can be performed on the audit question to extract key elements, including governance objects, governance actions, and query targets (such as "policy content" or "approver"). Based on these extracted key elements, a corresponding graph query statement is generated. This query statement is used to find paths and nodes related to the governance objects and governance actions in the configuration graph. For example, for the audit question "What is the current de-identification policy for the customer's mobile phone number? Who approved it?", the key elements "customer's mobile phone number," "de-identification policy," and "approver" are extracted, and a graph query statement is generated to find specification nodes, policy nodes, and approval nodes related to "customer's mobile phone number" in the configuration graph. Next, query results matching the audit question are obtained from the configuration graph. These results include node information, edge information, and their relationships related to the audit question. For example, for the above audit question, the query results could include: the specification identifier corresponding to the customer's mobile phone number, the type of governance action, constraints, the corresponding policy content, and the approver information and approval time for that specification. Finally, the query results can be returned to the user in a structured format. This structured form may include at least one of the following: a node path diagram (showing the complete path from the business intent node to the policy node), a node information list (listing the details of each node related to the audit issue), and an edge relationship description (describing the relationship between each node).
[0101] After obtaining the query results, a corresponding audit report can be generated based on these results for users to review. Through the aforementioned audit Q&A and audit report generation process, auditors' query requests can be responded to quickly, relevant governance decision information can be automatically retrieved from the configuration diagram, and traceable audit reports can be generated. This improves the efficiency and accuracy of data governance audits and effectively reduces the time and manpower costs of compliance audits.
[0102] Once the data governance strategy is deployed, it can be applied to specific scenarios, specifically, acquiring data services to be processed. These data services refer to specific instances of data services for which the data governance strategy needs to be applied, such as a specific database query request, a data file to be shared, or a data analysis task to be processed. If the data service to be processed matches the business type of the target business corresponding to the data governance strategy, data governance will be performed on the data service to be processed according to the data governance strategy.
[0103] In other words, the first step is to determine whether the data service to be processed matches the business type of the target business corresponding to the data governance strategy. This business type can include a business domain identifier, a data category identifier, or a business scenario identifier. If the business type of the data service to be processed matches the target business of the data governance strategy, data governance can be performed on the data service to be processed according to the data governance strategy.
[0104] In some application scenarios, after a data governance strategy is generated and deployed, the execution process can be further monitored to determine whether intent deviation has occurred during the application. Specifically, this can include the following steps: Step A1: Periodically obtain the data governance results.
[0105] The data governance result refers to the governance outcome of the data business to be processed according to the data governance strategy. For example, the data governance result may include the execution log of the de-identification rules, the effectiveness record of the access control policy, and the execution status of data classification and tagging.
[0106] In this step, the frequency of obtaining data governance results can be preset by the user, such as once every 24 hours, once a week, or once a month. Data governance results can also be obtained through event triggers, such as when the data governance strategy changes, when new data assets are added, or when an abnormal event is detected.
[0107] Step A2: If it is determined that the data governance result does not meet the intent constraints of the business intent text, a third adjustment suggestion is generated. This third adjustment suggestion is used to prompt the user to adjust the data business and / or data governance strategy to be processed.
[0108] The intent constraint refers to the minimum requirement of governance expectations expressed in the business intent text, which can be determined based on the determinate attributes described above. For example, if the business intent text requires "customer's mobile phone number to be completely invisible," then the intent constraint is "the disclosure level of customer's mobile phone number is zero." If the data governance result shows that the last four digits of the customer's mobile phone number are actually disclosed, then the data governance result is determined not to meet the intent constraint.
[0109] In this step, the generated third adjustment suggestion can include specific adjustment directions and content. For example, if it is detected that the anonymization rule has been changed from "completely invisible" to "retain the last four digits", the third adjustment suggestion can include: "It has been detected that the anonymization rule for customer mobile phone numbers has been changed from 'completely invisible' to 'retain the last four digits,' which exceeds the constraint of the original intent 'completely invisible.' It is recommended to restore the anonymization rule to 'completely invisible.'" By periodically obtaining data governance results and comparing them with the intent constraints of the business intent text, deviations that occur during the execution of the governance strategy can be detected in a timely manner, ensuring that the governance effect continues to conform to the user's original governance intent.
[0110] The following details the specific implementation method for determining whether a data governance result does not meet the intent constraints of the business intent text. First, determine the second governance intent corresponding to the data governance result. This second governance intent refers to the intent corresponding to the actual governance effect reflected by the data governance result. For example, if the data governance result shows the anonymization rule as "retain the last four digits," the second governance intent can be understood as "partially visible customer mobile phone number"; if the data governance result shows the anonymization rule as "completely invisible," the second governance intent can be understood as "completely invisible customer mobile phone number." Specifically, the second governance intent can be determined by analyzing the actual effective configuration in the data governance result. For example, the currently effective anonymization rules, access control rules, and other configuration information can be obtained from the data governance execution engine, and then the governance intent corresponding to the actual governance effect can be derived backwards based on this configuration information. Afterwards, if the second governance intent exceeds the constraint range of the first governance intent, it can be determined that the data governance result does not meet the intent constraints of the business intent text. The constraint range of the first governance intent refers to the boundary of the governance effect in the business intent text, which can be determined through the decidable attribute. In one scenario, the configuration may have changed, causing the data governance strategy to deviate from the intent constraints of the business intent text. For example, if the business intent text requires "completely invisible," the constraint is "disclosure level is zero"; if the business intent text requires "visible only to customer service roles," the constraint is "visible roles are limited to customer service." If the second governance intent exceeds the constraint of the first governance intent—for example, if the first governance intent requires "completely invisible," while the second governance intent is "partially visible"—then the data governance result can be determined to not meet the intent constraints, and a corresponding third adjustment suggestion can be generated to remind the user to adjust the data governance strategy. In another scenario, the configuration has not changed, but the environment has changed. The data governance strategy has not deviated from the intent constraints of the business intent text, but because the data to be processed is not tagged, it fails to match the data governance strategy successfully. For example, the user intent is "data involving minors requires additional protection," and a corresponding data governance strategy is generated accordingly. This strategy implements additional access restrictions and retention controls on data objects tagged with MINOR. However, during the policy's implementation, a new "Youth Activity Registration Form" was added to the business system. This form contained a large amount of information about minors, but it was not tagged with MINOR during creation and did not trigger any classification or tagging process. Because the form lacked a MINOR tag, the data governance policy could not identify that the form belonged to "minor data," resulting in the form not being included in the policy's coverage and failing to be subject to the necessary access restrictions and retention controls.At this point, due to environmental changes (new data tables that are not marked), the actual governance effect has deviated from the user's original intention that "minors' data needs extra protection," creating a governance blind spot. Corresponding third adjustment suggestions can be generated to remind users to adjust the data services to be processed.
[0111] In this way, in practical applications, the actual governance effect can be automatically compared with the original governance intent, and deviations from the governance strategy during implementation can be detected in a timely manner, thereby ensuring the continuous compliance of data governance.
[0112] By employing the above method, and acquiring the user's input business intent text and the corresponding preset governance constraints, the system can automatically compare and verify the user's expressed natural language governance intent with the structured governance constraints. This proactively identifies any governance requirements missed by the user, thereby verifying the completeness of the business intent text coverage. Furthermore, a first verification result is generated, indicating whether the business intent text meets the preset governance constraints. Based on this first verification result, a data governance strategy is determined, effectively ensuring the high completeness of the generated data governance strategy.
[0113] Figure 3 This is a block diagram illustrating a data management apparatus according to an exemplary embodiment, such as... Figure 3 As shown, the device 200 includes: The acquisition module 201 is configured to acquire the business intent text input by the user; the business intent text is used to represent the user's first governance intent for the target business; and acquire multiple preset governance constraints corresponding to the target business. The verification module 202 is configured to verify the business intent text according to the multiple preset governance constraints and obtain a first verification result; the first verification result is used to characterize whether the business intent text meets the multiple preset governance constraints. The determination module 203 is configured to determine the data governance strategy for the target business based on the first verification result.
[0114] Optionally, the verification module 202 is configured to extract the set of governance elements from the business intent text; and determine the first verification result based on the set of governance elements and the multiple preset governance constraints.
[0115] Optionally, the verification module 202 is configured to determine that the first verification result includes the business intent text satisfying the multiple preset governance constraints when the set of governance elements contains the multiple preset governance constraints; or, when the set of governance elements does not contain the multiple preset governance constraints, determine that the first verification result includes the business intent text not satisfying the multiple preset governance constraints.
[0116] Optionally, such as Figure 4 As shown, the device 200 also includes: The generation module 204 is configured to generate a first adjustment suggestion corresponding to the business intent text when the first verification result includes the business intent text not meeting the multiple preset governance constraints. The first adjustment suggestion is used to indicate that there is a governance intent that needs to be supplemented in the business intent text. The governance intent that needs to be supplemented is determined based on the preset governance constraints that the business intent text does not meet.
[0117] Optionally, the determining module 203 is configured to determine the data governance strategy based on the set of governance elements when the first verification result includes the business intent text satisfying the multiple preset governance constraints.
[0118] Optionally, the determining module 203 is further configured to determine the second verification result based on the business intent text and the existing governance policy, wherein the second verification result is used to characterize whether there is a conflict between the business intent text and the existing governance policy; and to determine the data governance policy based on the first verification result and the second verification result.
[0119] Optionally, the determining module 203 is configured to determine whether there is action mutual exclusion and / or condition mutual exclusion between the business intent text and the existing governance policy; the action mutual exclusion indicates that there is a conflict between the first governance action indicated by the business intent text and the second governance action indicated by the existing governance policy, and the condition mutual exclusion is used to indicate that there is a conflict between the first execution condition for executing the first governance action and the second execution condition for executing the second governance action; if it is determined that there is action mutual exclusion and / or condition mutual exclusion between the business intent text and the existing governance policy, the second verification result is determined to include that there is a conflict between the business intent text and the existing governance policy; or, if it is determined that there is no action mutual exclusion and condition mutual exclusion between the business intent text and the existing governance policy, the second verification result is determined to include that there is no conflict between the business intent text and the existing governance policy.
[0120] Optionally, the generation module 204 is further configured to generate a second adjustment suggestion corresponding to the business intent text if there is a conflict between the second verification result, including the business intent text and the existing governance policy. The second adjustment suggestion is used to indicate that there is a governance intent in the business intent text that needs to be adjusted, and the governance intent that needs to be adjusted is determined based on the existing governance policy that is in conflict.
[0121] Optionally, the determining module 203 is configured to determine the data governance strategy based on the set of governance elements when the first verification result includes the business intent text satisfying the multiple preset governance constraints, and the second verification result includes the business intent text not conflicting with existing governance strategies.
[0122] Optionally, the determining module 203 is configured to, when the first verification result includes the business intent text satisfying the multiple preset governance constraints, and the second verification result includes the business intent text not conflicting with existing governance strategies, obtain a manual verification result, the manual verification result being the result of the user verifying the business intent text based on the first verification result and the second verification result; and when the manual verification result indicates that the business intent text has passed verification, determine the data governance strategy based on the set of governance elements.
[0123] Optionally, the acquisition module 201 is also configured to acquire data services to be processed; like Figure 5 As shown, the device 200 also includes: The governance module 205 is configured to perform data governance on the data service to be processed according to the data governance strategy when the service type of the data service to be processed is consistent with the target service corresponding to the data governance strategy.
[0124] Optionally, the acquisition module 201 is further configured to periodically acquire data governance results; the data governance results are the governance results of the data services to be processed according to the data governance strategy. The generation module 204 is also configured to generate a third adjustment suggestion if it is determined that the data governance result does not meet the intent constraints of the business intent text. The third adjustment suggestion is used to prompt the user to adjust the data business and / or data governance strategy to be processed.
[0125] Optionally, determining that the data governance result does not meet the intent constraints of the business intent text includes: Determine the second governance intent corresponding to the data governance result; If the second governance intent exceeds the constraints of the first governance intent, it is determined that the data governance result does not meet the intent constraints of the business intent text.
[0126] Using the aforementioned device, by acquiring the user's input business intent text and obtaining the preset governance constraints corresponding to the target business, the device can automatically compare and verify the user's expressed natural language governance intent with the structured governance constraints. This proactively identifies governance requirements that the user may have overlooked, thereby verifying the completeness of the business intent text coverage. Furthermore, it generates a first verification result indicating whether the business intent text meets the preset governance constraints. Based on this first verification result, a data governance strategy is determined, effectively ensuring that the generated data governance strategy has high completeness.
[0127] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.
[0128] Figure 6 This is a block diagram illustrating an electronic device 300 according to an exemplary embodiment. Figure 6 As shown, the electronic device 300 may include a processor 301 and a memory 302. The electronic device 300 may also include one or more of a multimedia component 303, an input / output (I / O) interface 304, and a communication component 305.
[0129] The processor 301 controls the overall operation of the electronic device 300 to complete all or part of the steps in the data management method described above. The memory 302 stores various types of data to support the operation of the electronic device 300. This data may include, for example, instructions for any application or method operating on the electronic device 300, and application-related data such as contact data, sent and received messages, pictures, audio, video, etc. The memory 302 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The multimedia component 303 may include a screen and audio components. The screen may be, for example, a touchscreen, and the audio component is used to output and / or input audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signals may be further stored in memory 302 or transmitted via communication component 305. The audio component also includes at least one speaker for outputting audio signals. I / O interface 304 provides an interface between processor 301 and other interface modules, such as a keyboard, mouse, buttons, etc. These buttons may be virtual or physical buttons. Communication component 305 is used for wired or wireless communication between the electronic device 300 and other devices. Wireless communication may include Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G, or 4G, or a combination thereof; therefore, the corresponding communication component 305 may include a Wi-Fi module, a Bluetooth module, or an NFC module.
[0130] In an exemplary embodiment, the electronic device 300 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the data management method described above.
[0131] In another exemplary embodiment, a computer-readable storage medium including program instructions is also provided, which, when executed by a processor, implement the steps of the data management method described above. For example, the computer-readable storage medium may be the memory 302 including the program instructions described above, which may be executed by the processor 301 of the electronic device 300 to complete the data management method described above.
[0132] In another exemplary embodiment, a computer program product is also provided, which includes a computer program executable by a processor, which, when executed by the processor, implements the steps of the data governance method described above.
[0133] The preferred embodiments of this disclosure have been described in detail above with reference to the accompanying drawings. However, this disclosure is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this disclosure, various simple modifications can be made to the technical solutions of this disclosure, and these simple modifications all fall within the protection scope of this disclosure.
[0134] It should also be noted that the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, this disclosure will not describe the various possible combinations separately.
[0135] Furthermore, various different embodiments of this disclosure can be combined in any way, as long as they do not violate the spirit of this disclosure, they should also be regarded as the content disclosed in this disclosure.
Claims
1. A data governance method, characterized in that, The method includes: Obtain the business intent text input by the user; the business intent text is used to represent the user's primary management intent for the target business. Obtain multiple preset governance constraints corresponding to the target service; Based on the multiple preset governance constraints, the business intent text is validated to obtain a first validation result; the first validation result is used to characterize whether the business intent text satisfies the multiple preset governance constraints. Based on the first verification result, the data governance strategy for the target business is determined.
2. The method according to claim 1, characterized in that, The step of validating the business intent text based on the multiple preset governance constraints to obtain a first validation result includes: Extract the set of governance elements from the business intent text; The first verification result is determined based on the set of governance elements and the multiple preset governance constraints.
3. The method according to claim 2, characterized in that, The step of determining the first verification result based on the set of governance elements and the multiple preset governance constraints includes: If the set of governance elements includes the plurality of preset governance constraints, then the first verification result is determined to include the business intent text satisfying the plurality of preset governance constraints; or... If the set of governance elements does not contain the plurality of preset governance constraints, the first verification result is determined to include the business intent text not satisfying the plurality of preset governance constraints.
4. The method according to claim 1, characterized in that, The method further includes: If the first verification result includes the business intent text not satisfying the multiple preset governance constraints, a first adjustment suggestion corresponding to the business intent text is generated. The first adjustment suggestion is used to indicate that there is a governance intent that needs to be supplemented in the business intent text. The governance intent that needs to be supplemented is determined based on the preset governance constraints that the business intent text does not satisfy.
5. The method according to claim 2, characterized in that, The step of determining the data governance strategy for the target business based on the first verification result includes: If the first verification result includes the business intent text satisfying the multiple preset governance constraints, the data governance strategy is determined based on the set of governance elements.
6. The method according to claim 2, characterized in that, The method further includes: Based on the business intent text and the existing governance policy, a second verification result is determined. The second verification result is used to characterize whether there is a conflict between the business intent text and the existing governance policy. The step of determining the data governance strategy for the target business based on the first verification result includes: The data governance strategy is determined based on the first verification result and the second verification result.
7. The method according to claim 6, characterized in that, The step of determining the second verification result based on the business intent text and existing governance policies includes: Determine whether there is mutual exclusion of actions and / or mutual exclusion of conditions between the business intent text and the existing governance policy; mutual exclusion of actions indicates that there is a conflict between the first governance action indicated by the business intent text and the second governance action indicated by the existing governance policy; mutual exclusion of conditions is used to indicate that there is a conflict between the first execution condition for executing the first governance action and the second execution condition for executing the second governance action. If it is determined that there is mutual exclusion of actions and / or mutual exclusion of conditions between the business intent text and the existing governance policy, the second verification result is determined to include a conflict between the business intent text and the existing governance policy; or... If it is determined that there is no mutual exclusion of actions or conditions between the business intent text and the existing governance policy, the second verification result is determined to include that there is no conflict between the business intent text and the existing governance policy.
8. The method according to claim 7, characterized in that, The method further includes: If the second verification result includes a conflict between the business intent text and an existing governance policy, a second adjustment suggestion corresponding to the business intent text is generated. The second adjustment suggestion is used to indicate that there is a governance intent in the business intent text that needs to be adjusted. The governance intent that needs to be adjusted is determined based on the existing governance policy that is in conflict.
9. The method according to claim 6, characterized in that, The step of determining the data governance strategy based on the first verification result and the second verification result includes: If the first verification result includes the business intent text satisfying the multiple preset governance constraints, and the second verification result includes the business intent text not conflicting with existing governance strategies, then the data governance strategy is determined based on the set of governance elements.
10. The method according to claim 9, characterized in that, When the first verification result shows that the business intent text satisfies the multiple preset governance constraints, and the second verification result shows that there is no conflict between the business intent text and existing governance strategies, the data governance strategy determined based on the set of governance elements includes: If the first verification result includes the business intent text satisfying the multiple preset governance constraints, and the second verification result includes the business intent text having no conflict with existing governance policies, a manual verification result is obtained. The manual verification result is the result of the user verifying the business intent text based on the first verification result and the second verification result. If the manual verification result indicates that the business intent text verification has passed, the data governance strategy is determined based on the set of governance elements.
11. The method according to any one of claims 1 to 10, characterized in that, The method further includes: Acquire the data to be processed; If the data service to be processed is consistent with the service type of the target service corresponding to the data governance strategy, data governance is performed on the data service to be processed according to the data governance strategy.
12. The method according to claim 11, characterized in that, The method further includes: The data governance results are periodically obtained; the data governance results are the governance results of the data services to be processed according to the data governance strategy. If it is determined that the data governance result does not meet the intent constraints of the business intent text, a third adjustment suggestion is generated. The third adjustment suggestion is used to prompt the user to adjust the data business and / or data governance strategy to be processed.
13. The method according to claim 12, characterized in that, The determination that the data governance result does not meet the intent constraints of the business intent text includes: Determine the second governance intent corresponding to the data governance result; If the second governance intent exceeds the constraints of the first governance intent, it is determined that the data governance result does not meet the intent constraints of the business intent text.
14. A data governance device, characterized in that, The device includes: The acquisition module is configured to acquire the business intent text input by the user; the business intent text is used to represent the user's first governance intent for the target business; and acquire multiple preset governance constraints corresponding to the target business. The verification module is configured to verify the business intent text according to the plurality of preset governance constraints and obtain a first verification result; the first verification result is used to characterize whether the business intent text satisfies the plurality of preset governance constraints. The determination module is configured to determine the data governance strategy of the target service based on the first verification result.
15. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the program implements the steps of the method described in any one of claims 1 to 13.
16. An electronic device, characterized in that, include: A memory on which computer programs are stored; A processor for executing the computer program in the memory to implement the steps of the method according to any one of claims 1 to 13.
17. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program performs the steps of the method according to any one of claims 1 to 13.
