Enterprise entity-oriented decoupling construction and fine-grained portrait authorization method and system

Abstract

The application is suitable for the technical field of data processing, and provides an enterprise entity-oriented decoupling construction and fine-grained portrait authorization method and system. The method comprises the following steps: first, acquiring multi-source heterogeneous enterprise data set information; then, based on the information, generating enterprise entity field set information; then, constructing multiple enterprise portrait dimension information; then, acquiring three-dimensional permission data structure information, and determining actual authorization level information of each enterprise portrait dimension information of a target user; finally, based on the actual authorization level information, generating exclusive enterprise portrait view information of the target user. The application can finely authorize the subdivided dimensions of the portrait, dynamically determine the visibility of each dimension, ensure that the same enterprise entity presents different users with differentiated and strictly compliant portrait views, meet the requirements of hierarchical classification and minimum necessary data security compliance, and effectively avoid excessive exposure of sensitive data.

Description

Technical Field

[0001] This application relates to the technical field of data processing, and more specifically, to a method and system for decoupling construction and fine-grained profiling authorization of enterprise entities. Background Technology

[0002] With the continuous advancement of business environment optimization and digitalization of government and enterprise services, building enterprise profiles based on multi-source heterogeneous data has become an important support for enterprise monitoring, policy dissemination, and precise services. Currently, mainstream enterprise profiling platforms rely on data governance to aggregate multi-source information such as business registration, operations, credit, and science and technology innovation data to build a basic database of enterprise entities, providing business personnel at all levels with the ability to query enterprise information and browse enterprise profiles.

[0003] Currently, existing enterprise profiling systems typically employ a static architecture that directly couples dimensional models with underlying entity fields. This makes it impossible to differentiate authorization based on the subdivided dimensions of the profile. The same enterprise entity can only present a unified view to different users, which is difficult to meet the hierarchical classification and minimum necessary data compliance requirements. This results in low reliability and requires further improvement. Summary of the Invention

[0004] Based on this, embodiments of this application provide a method and system for decoupled construction and fine-grained profiling authorization of enterprise entities, in order to solve the problem of low reliability in the prior art.

[0005] In a first aspect, embodiments of this application provide a method for decoupling construction and fine-grained profiling authorization of enterprise entities, the method comprising: Obtain information from multi-source heterogeneous enterprise datasets; Based on the information from the multi-source heterogeneous enterprise dataset, generate enterprise entity field set information; Based on the enterprise entity field set information, multiple enterprise profile dimensions are constructed; In response to a target user's request to access the profile of a target enterprise, a three-dimensional permission data structure is obtained. Based on the target user's current user identifier and current role identifier, the actual authorization level information of the target user for each of the enterprise profile dimensions is determined. The three-dimensional permission data structure uses user identifier, role identifier, and enterprise profile dimension information as index dimensions. The element value at the intersection of each dimension in the three-dimensional permission data structure is the authorization level information of any user for any enterprise profile dimension under a specified role. The authorization level information can be fully visible, de-identified visible, conditionally visible, or invisible. Based on the actual authorization level information, a unique enterprise profile view of the target user is generated.

[0006] Compared with existing technologies, the beneficial effects are as follows: The decoupled construction and fine-grained profiling authorization method for enterprise entities provided in this application allows the terminal device to first acquire multi-source heterogeneous enterprise dataset information, then quickly generate enterprise entity field set information based on the multi-source heterogeneous enterprise dataset information, and then effectively construct multiple enterprise profile dimensions based on the enterprise entity field set information. Then, in response to the target user's request to access the profile of the target enterprise, the actual authorization level information of the target user for each enterprise profile dimension information is reliably determined based on the target user's current user identifier information and current role identifier information. Finally, based on the actual authorization level information, the exclusive enterprise profile view information of the target user is effectively generated, thereby enabling differentiated authorization for the subdivided dimensions of the profile. The same enterprise entity presents targeted views to different users, meeting the hierarchical classification and minimum necessary data compliance requirements, greatly improving reliability, and to a certain extent solving the problem of low reliability in the current system.

[0007] Secondly, embodiments of this application provide a decoupled construction and fine-grained profiling authorization system for enterprise entities, the system comprising: Multi-source heterogeneous enterprise dataset information acquisition module: used to acquire information from multi-source heterogeneous enterprise datasets; Enterprise entity field set information generation module: used to generate enterprise entity field set information based on the multi-source heterogeneous enterprise dataset information; Enterprise profile dimension information construction module: used to construct multiple enterprise profile dimension information based on the enterprise entity field set information; Actual Authorization Level Information Determination Module: In response to a target user's request to access the profile of a target enterprise, this module obtains three-dimensional permission data structure information and determines the actual authorization level information of the target user for each of the enterprise profile dimensions based on the target user's current user identifier information and current role identifier information. The three-dimensional permission data structure information uses user identifier information, role identifier information, and enterprise profile dimension information as index dimensions. The element value at the intersection of each dimension in the three-dimensional permission data structure information is the authorization level information of any user under a specified role for any enterprise profile dimension. The authorization level information can be fully visible, anonymized, conditionally visible, or invisible. Exclusive Enterprise Profile View Information Generation Module: Used to generate exclusive enterprise profile view information for the target user based on the actual authorization level information.

[0008] Thirdly, embodiments of this application provide a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method described in the first aspect above.

[0009] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the method described in the first aspect above.

[0010] It is understood that the beneficial effects of the second to fourth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below.

[0012] Figure 1 This is a flowchart illustrating a decoupled construction and fine-grained profiling authorization method provided in an embodiment of this application; Figure 2 This is a flowchart illustrating step S200 in the decoupled construction and fine-grained profiling authorization method provided in an embodiment of this application; Figure 3 This is a flowchart illustrating step S300 in the decoupled construction and fine-grained profiling authorization method provided in an embodiment of this application; Figure 4 This is a flowchart illustrating step S320 in the decoupled construction and fine-grained profiling authorization method provided in an embodiment of this application; Figure 5 This is a flowchart illustrating step S400 in the decoupled construction and fine-grained profiling authorization method provided in an embodiment of this application; Figure 6 This is a flowchart illustrating step S500 in the decoupled construction and fine-grained profiling authorization method provided in an embodiment of this application; Figure 7 This is a block diagram of a decoupled construction and fine-grained profiling authorization system provided in an embodiment of this application; Figure 8 This is a schematic diagram of a terminal device provided in an embodiment of this application. Detailed Implementation

[0013] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0014] In the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0015] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0016] To illustrate the technical solution described in this application, specific embodiments are provided below.

[0017] Please see Figure 1 , Figure 1 This is a flowchart illustrating the decoupling construction and fine-grained profiling authorization method for enterprise entities provided in this application embodiment. In this embodiment, the execution subject of the decoupling construction and fine-grained profiling authorization method is a terminal device. It is understood that the types of terminal devices include, but are not limited to, tablet computers, laptops, Ultra-Mobile Personal Computers (UMPCs), netbooks, Personal Digital Assistants (PDAs), etc., and this application embodiment does not impose any restrictions on the specific type of terminal device.

[0018] Please see Figure 1 The decoupled construction and fine-grained profiling authorization method provided in this application includes, but is not limited to, the following steps: In S100, information on multi-source heterogeneous enterprise datasets is obtained.

[0019] Specifically, terminal devices can first acquire multi-source heterogeneous enterprise dataset information, thereby receiving raw enterprise data from multiple data sources as the data foundation for subsequent data governance and profile construction. The multi-source heterogeneous enterprise dataset information corresponds to multiple data sources, that is, the multi-source heterogeneous enterprise dataset information comes from at least two different data providers. The data providers can be at least two of the following: business registration system, tax collection and management system, social security management system, judicial disclosure platform, enterprise self-declaration platform, third-party credit reporting agency, and government service system. The data formats of the multi-source heterogeneous enterprise dataset information include at least two of the following: relational database table, JSON interface data, XML structured document, PDF unstructured document, and text public opinion data.

[0020] In S200, enterprise entity field set information is generated based on multi-source heterogeneous enterprise dataset information.

[0021] Specifically, after the terminal device obtains multi-source heterogeneous enterprise dataset information, it can effectively generate enterprise entity field set information based on the multi-source heterogeneous enterprise dataset information.

[0022] In some possible implementations, to generate enterprise entity field set information, please refer to [link / reference]. Figure 2 Step S200 includes, but is not limited to, the following steps: In S210, based on the information from the multi-source heterogeneous enterprise dataset, the original data structure information and original field definition information corresponding to each data source information are determined.

[0023] Specifically, the terminal device can determine the original data structure information and original field definition information corresponding to each data source information based on the multi-source heterogeneous enterprise dataset information, thereby realizing the parsing of the original data from each data source, identifying the data structure type of the original data and the field definition in each data table. The original data structure information can be structured, semi-structured, or unstructured; the original field definition information can be field name, data type, and field meaning.

[0024] In S220, for each data source information: based on the original data structure information and the original field definition information, the field mapping rule information is determined.

[0025] Specifically, after the terminal device determines the original data structure information and the original field definition information, the terminal device can perform this processing for each data source information: based on the original data structure information and the original field definition information, formulate mapping rules from the original fields to the standard fields for each data source, and reliably determine the field mapping rule information, wherein the field mapping rule information may include field name conversion rules, data type conversion rules, and field value format conversion rules.

[0026] In S230, the consistency information of business meaning among the original field definition information is determined based on the field caliber description information and field value logic information corresponding to each data source information.

[0027] Specifically, after the terminal device determines the field mapping rule information, it can quickly determine the consistency of business meaning between the original field definition information based on the field description information and field value logic information corresponding to each data source information.

[0028] For example, the terminal device uses the description of the scope of each field in each data source (e.g., the difference between "operating revenue (including tax)" and "operating revenue (excluding tax)") and the value logic (e.g., the difference between the group summary scope and the individual scope), and further obtains the value formula information, statistical range information, and calculation time point information of each field. This information is used as a multi-dimensional basis for determining the consistency of business meaning. When the field description, value logic, value formula, statistical range, and calculation time point are all the same, or although the expressions are different, they point to the same statistical meaning after being mapped by business rules, the terminal device can determine that the business meaning is consistent. When any of the above core elements (e.g., value logic or statistical range) is substantially different, the terminal device can determine that the business meaning is inconsistent. In one possible implementation, for fields with different expressions but whose consistency cannot be automatically determined, the terminal device can output a list of suspected aligned fields for manual confirmation by operations and maintenance personnel or for assisted matching using a preset business synonym library.

[0029] In S240, based on field mapping rule information and business meaning consistency information, original field definition information with the same business meaning is mapped to the same standard field definition information to generate standard field definition set information.

[0030] Specifically, after the terminal device determines the consistency information of business meaning, the terminal device can map the original field definition information with the same business meaning to the same standard field definition information based on the field mapping rule information and the consistency information of business meaning. For example, the original field definition information with the same business meaning but different field names and / or field formats from different data sources can be uniformly mapped to the same standard field definition information to reliably generate standard field definition set information.

[0031] In S250, each standard field definition in the standard field definition set information is sequentially cleaned, format standardized and converted, field regularized, missing value repaired and sensitive data desensitized to generate enterprise entity field set information.

[0032] Specifically, after the terminal device generates the standard field definition set information, the terminal device can sequentially perform data cleaning, format standardization conversion, field regularization, missing value repair, and sensitive data desensitization on each standard field definition information in the standard field definition set information to generate enterprise entity field set information, which includes multiple enterprise entity field information.

[0033] For example, the terminal device performs the following processing on the field data corresponding to each standard field definition information in the standard field definition set information: removing duplicate and invalid record information; performing format standardization conversion according to preset field format rules; performing field normalization according to preset field value rules; marking field data that exceeds the preset value range or does not conform to the preset value logic as abnormal field data and performing field value correction; filling missing values ​​in null fields according to the field type information and statistical distribution information of the same field; and performing corresponding level of desensitization processing on field data with a sensitivity level higher than the preset sensitivity threshold according to the corresponding sensitivity level. The desensitization processing includes at least one of blurring, replacement, and masking processing, thereby assembling the field data after all the above processing according to a unified data format to generate enterprise entity field set information.

[0034] It should be noted that the enterprise entity field set information includes multiple enterprise entity field information; in some possible implementations, the terminal device can also associate and store field metadata information for each field data in the enterprise entity field set information. This field metadata information may include field name information, data type information, business definition information, data source traceability information, update cycle information, and sensitivity level information.

[0035] In S300, multiple enterprise profile dimensions are constructed based on enterprise entity field set information.

[0036] Specifically, after the terminal device generates the enterprise entity field set information, the terminal device can efficiently construct multiple enterprise profile dimensions based on the enterprise entity field set information.

[0037] In some possible implementations, to construct multiple dimensions of enterprise profile information, please refer to [link / reference]. Figure 3 Step S300 includes, but is not limited to, the following steps: In S310, obtain dimension configuration instruction information.

[0038] Specifically, the terminal device can receive dimension configuration instruction information input from the business terminal. The dimension configuration instruction information includes dimension name information, dimension classification information, and dimension business definition information. For example, the dimension name information can be a financial performance dimension, the dimension classification information can be financial, risk, or science and technology innovation, and the dimension business definition information can be a set of indicators reflecting the company's solvency, profitability, and operational capabilities.

[0039] In S320, enterprise profile dimension instance information is generated based on dimension name information, dimension classification information, and dimension business definition information.

[0040] Specifically, after the terminal device obtains the dimension configuration instruction information, it can quickly generate enterprise profile dimension instance information based on the dimension name information, dimension classification information, and dimension business definition information.

[0041] In some possible implementations, to generate enterprise profile dimension instance information, please refer to [link / reference]. Figure 4 Step S320 includes, but is not limited to, the following steps: In S321, based on the dimension name information, the dimension unique identifier information of the enterprise profile dimension instance information is generated.

[0042] Specifically, the terminal device can generate unique dimension identifier information for enterprise profile dimension instance information based on the dimension name information. The unique dimension identifier information is used to describe a globally unique dimension identifier, such as DIM_FINANCE_001. The unique dimension identifier information is used to uniquely identify the enterprise profile dimension in the system.

[0043] In S322, dimension storage space information is created, and dimension storage space information is associated with dimension unique identifier information.

[0044] Specifically, after the terminal device generates the dimension unique identifier information, the terminal device can create dimension storage space information and associate the dimension storage space information with the dimension unique identifier information, thereby allocating the corresponding physical storage space for the enterprise profile dimension instance and establishing the association between the storage space and the dimension unique identifier.

[0045] In S323, based on the dimensional classification information, the classification affiliation information of the enterprise profile dimensional instance information in the preset dimensional classification directory system is determined.

[0046] Specifically, after the terminal device associates the dimension storage space information and the dimension unique identifier information, the terminal device can determine the classification information of the enterprise profile dimension instance information in the preset dimension classification directory system based on the dimension classification information, and thus classify the dimension instance under the corresponding category node in the preset dimension classification directory system.

[0047] For example, the dimension classification directory system can be a pre-defined multi-level classification tree structure. The dimension classification directory system can include multiple first-level classification nodes divided according to business domains, such as finance, risk, science and technology innovation, business, credit, and public opinion. Each first-level classification node contains at least one second-level classification node. When dimension classification information matches a certain first-level or second-level classification node, the terminal device assigns the dimension instance to that classification node. When dimension classification information cannot match an existing classification node, the terminal device creates a new classification node in the dimension classification directory system and assigns the dimension instance to the newly created classification node. For example, when the dimension classification information is "finance," the terminal device assigns the dimension instance to the "finance" classification node, and the dimension instance will be bound to the default configuration information of the classification attribute corresponding to the "finance" node.

[0048] In S324, the default configuration information for the classification attributes of the enterprise profile dimension instance information is determined based on the classification attribution information.

[0049] Specifically, after the terminal device determines the classification information, it can quickly determine the default configuration information of the classification attributes of the enterprise profile dimension instance information based on the classification information. The default configuration information of the classification attributes can include the default sensitivity level, default display template and default data refresh frequency of the dimension.

[0050] In S325, the dimension business definition information of the enterprise profile dimension instance information is determined based on the dimension business definition information.

[0051] Specifically, after the terminal device determines the default configuration information of the classification attributes, the terminal device can determine the dimension business definition information of the enterprise profile dimension instance information based on the dimension business interpretation information input by the business end. The dimension business definition information is used to clarify the business meaning and calculation scope of the enterprise profile dimension instance information.

[0052] In S326, the dimension display style configuration information of the enterprise profile dimension instance information is determined based on the dimension classification information.

[0053] Specifically, after the terminal device determines the dimensional business scope description information, the terminal device can determine the dimensional display style configuration information of the enterprise profile dimensional instance information based on the dimensional classification information.

[0054] For example, the terminal device can determine the display style configuration of a dimension based on the dimension classification information. Different categories correspond to different default display styles. For example, financial dimensions are displayed in charts by default, while risk dimensions are displayed in lists by default.

[0055] In S327, the dimension business definition description information, dimension display style configuration information, category attribute default configuration information, and dimension unique identifier information are associated and stored in the dimension storage space information to generate enterprise profile dimension instance information.

[0056] Specifically, after the terminal device determines the dimension display style configuration information, the terminal device can associate and store the dimension business description information, dimension display style configuration information, category attribute default configuration information, and dimension unique identifier information into the dimension storage space information to generate enterprise profile dimension instance information. This enables the storage of all the above-mentioned dimension metadata information into the storage space corresponding to the dimension, thus completing the creation of the enterprise profile dimension instance.

[0057] In S330, in response to field binding instruction information, binding mapping relationship information is generated based on enterprise profile dimension instance information and enterprise entity field set information.

[0058] Specifically, after the terminal device generates enterprise profile dimension instance information, the terminal device can respond to the field binding instruction information triggered by the business end to bind the enterprise profile dimension instance information with one or more enterprise entity field information in the enterprise entity field set information, and generate binding mapping relationship information. The binding mapping relationship information is used to describe the binding mapping relationship between the enterprise profile dimension instance information and one or more enterprise entity field information in the enterprise entity field set information. The binding mapping relationship information includes at least one of one-to-one mapping relationship information, one-to-many mapping relationship information, and many-to-one mapping relationship information.

[0059] In S340, the binding mapping relationship information and enterprise profile dimension instance information are associated and stored to generate enterprise profile dimension information.

[0060] Specifically, after the terminal device generates the binding mapping relationship information, the terminal device can associate and store the binding mapping relationship information and the enterprise profile dimension instance information to generate enterprise profile dimension information. In this way, the enterprise profile dimension information is used as a logical view layer unit independent of the underlying physical fields, thereby decoupling the dimensions from the underlying data fields.

[0061] In S400, in response to a target user's request to access the profile of a target enterprise, the system obtains three-dimensional permission data structure information and determines the actual authorization level of the target user for each dimension of the enterprise profile based on the target user's current user identifier information and current role identifier information.

[0062] Specifically, after the terminal device generates enterprise profile dimension information, it can respond to the target user's request to access the target enterprise's profile, effectively obtain the three-dimensional permission data structure information, and accurately determine the target user's actual authorization level information for each enterprise profile dimension information based on the target user's current user identification information and current role identification information.

[0063] In some possible implementations, please refer to [link to relevant documentation] for details on how to achieve the actual authorization level information. Figure 5 Step S400 includes, but is not limited to, the following steps: In S410, obtain the three-dimensional permission data structure information.

[0064] Specifically, the terminal device can obtain preset three-dimensional permission data structure information. The three-dimensional permission data structure information uses user identification information, role identification information, and enterprise profile dimension information as index dimensions, respectively. The element value at the intersection of each dimension in the three-dimensional permission data structure information is the authorization level information of any user under a specified role for any enterprise profile dimension.

[0065] In some possible implementations, the element values ​​in the three-dimensional permission data structure information can be dynamically generated based on a weighted aggregation of the base-state authorization value, the time decay correction factor, and the inheritance coverage correction factor. The base-state authorization value can be a basic authorization level value pre-set by the operations and maintenance personnel, serving as the benchmark value for permission calculation. The time decay correction factor can be a correction coefficient calculated according to a preset half-life exponential decay function based on the interval between the permission configuration time and the current time, used to reduce the permission value with the configuration duration, thus achieving automatic expiration management of temporary permissions. The inheritance coverage correction factor can be a correction coefficient calculated based on the permission configuration information of the target user's superior organization in its organizational hierarchy, used to achieve the inheritance of superior organization permissions to subordinate organization users, and to determine the coverage priority when there is a conflict in the same-level or cross-level permission configuration. For example, the terminal device uses the base-state authorization value as the benchmark value, and uses the time decay correction factor and the inheritance coverage correction factor as multiplicative weighting coefficients to perform weighted calculations on the base-state authorization value, dynamically generating the real-time authorization level value of each element in the three-dimensional permission data structure information, so that the permission data can be automatically updated with changes in configuration duration and organizational hierarchy.

[0066] In S420, based on the target user's current user identifier information and current role identifier information, and according to the three-dimensional permission data structure information, the authorization level vector information of the target user under the current role is determined.

[0067] Specifically, after the terminal device obtains the three-dimensional permission data structure information, it can extract the authorization level vector information of the target user under the current role by slicing along the user dimension and role dimension based on the target user's current user identification information and current role identification information. The authorization level vector information includes the target user's authorization level information for each enterprise profile dimension information. The authorization level information can be fully visible, de-identified visible, conditionally visible, or invisible.

[0068] In S430, the target enterprise profile dimension information is determined as the dimension information to be judged.

[0069] Specifically, after the terminal device determines the authorization level vector information, the terminal device can determine the target enterprise profile dimension information as the dimension information to be decided. The target enterprise profile dimension information is used to describe the enterprise profile dimension information where the authorization level information is conditionally visible. The conditionally visible level information is associated with decision condition information, which includes assertion expression information corresponding to at least one entity field value information of the target enterprise. For example, the assertion expression information can be "tax level = A" or "registered capital > 10 million".

[0070] In S440, retrieve the entity field value information corresponding to the target enterprise in the enterprise entity field set information.

[0071] Specifically, after the terminal device determines the dimension information to be judged, it can obtain the entity field value information corresponding to the target enterprise in the enterprise entity field set information based on the enterprise identifier of the target enterprise. This enables the terminal device to obtain the specific field values ​​of the target enterprise under each enterprise entity field information in the enterprise entity field set information. The entity field value information is used to describe the specific values ​​of each enterprise entity field information in the enterprise entity field set information under the target enterprise.

[0072] In S450, the entity field value information is substituted into the assertion expression information of the corresponding decision condition information in the dimension information to be decided for evaluation calculation, and the evaluation result information is generated.

[0073] Specifically, after the terminal device obtains the entity field value information, it can substitute the entity field value information into the assertion expression information of the corresponding judgment condition information in the dimension information to be judged, perform evaluation calculation, and generate evaluation result information, wherein the evaluation result information is a Boolean type evaluation result.

[0074] In S460, if the evaluation result is true, the actual authorization level information of the dimension information to be decided is determined as the fully visible level information.

[0075] Specifically, if the evaluation result is true, the terminal device can determine the actual authorization level information of the dimension information to be judged as the fully visible level information, indicating that the target enterprise meets the condition for visibility under this dimension, and therefore this dimension is actually visible to the current user.

[0076] In S470, if the evaluation result is false, the actual authorization level information of the dimension information to be decided is determined to be invisible level information.

[0077] Specifically, if the evaluation result is false, the terminal device can determine the actual authorization level of the dimension information to be judged as invisible, indicating that the target enterprise does not meet the condition for visibility under this dimension, so this dimension is actually invisible to the current user.

[0078] In S480, the actual authorization level information of the target user for each enterprise profile dimension is determined based on the fully visible level information, the de-identified visible level information, the invisible level information, the fully visible level information determined after evaluation, and the invisible level information determined after evaluation.

[0079] Specifically, after the terminal device determines the invisible level information, it can reliably determine the target user's actual authorization level information for each enterprise profile dimension based on the fully visible level information in the authorization level vector information, the de-identified visible level information in the authorization level vector information, the invisible level information in the authorization level vector information, the fully visible level information determined after evaluation, and the invisible level information determined after evaluation. Then, it merges the authorization level information corresponding to each enterprise profile dimension in the authorization level vector information with the actual authorization level information corresponding to the dimension information to be decided determined after evaluation, and generates the complete actual authorization level information output of the target user for each enterprise profile dimension.

[0080] In S500, a unique enterprise profile view of the target user is generated based on the actual authorization level information.

[0081] Specifically, after the terminal device determines the actual authorization level information, the terminal device can effectively generate a unique enterprise profile view of the target user based on the actual authorization level information.

[0082] In some possible implementations, to generate customized enterprise profile view information, please refer to [link / reference]. Figure 6 Step S500 includes, but is not limited to, the following steps: In S510, a set of legal dimension information is generated based on the enterprise profile dimension information corresponding to the fully visible level information and the enterprise profile dimension information corresponding to the de-identified visible level information.

[0083] Specifically, the terminal device can generate a set of legal dimensions based on the enterprise profile dimension information corresponding to the fully visible level information and the enterprise profile dimension information corresponding to the anonymized visible level information. This allows the device to filter out the enterprise profile dimension information with the fully visible or anonymized visible level authorization from the actual authorization level information and use it as the set of legal dimensions.

[0084] In S520, obtain the preset compliance constraint rule information.

[0085] Specifically, after the terminal device generates a set of legal dimension information, the terminal device can obtain preset compliance constraint rules information, which are used to constrain the display combination relationship between different enterprise profile dimension information.

[0086] For example, the compliance constraint rule information may include at least one of co-occurrence constraint information, mutual exclusion constraint information, and cardinality constraint information. The co-occurrence constraint information is used to stipulate that the first enterprise profile dimension and the second enterprise profile dimension must appear simultaneously or not appear simultaneously in the same profile view. The mutual exclusion constraint information is used to stipulate that the third enterprise profile dimension and the fourth enterprise profile dimension cannot appear simultaneously in the same profile view. The cardinality constraint information is used to stipulate that the total number of dimensions in the compliance dimension set is not less than a preset lower threshold and / or not higher than a preset upper threshold.

[0087] In S530, the legal dimension set information is filtered based on the compliance constraint rule information to generate the compliance dimension set information.

[0088] Specifically, after the terminal device obtains the compliance constraint rule information, it can filter the legal dimension set information based on the compliance constraint rule information to generate the compliance dimension set information.

[0089] For example, the terminal device encodes the visibility status of each enterprise profile dimension information in the legal dimension set information into a set of Boolean variables, encodes the compliance constraint rule information into Boolean constraint expressions, performs satisfiability calculation on the Boolean variables through a constraint solver, and filters out the target dimension set information that satisfies all compliance constraint rule information from the legal dimension set information as the compliance dimension set information.

[0090] In S540, for each enterprise profile dimension information in the compliance dimension set information: based on the enterprise entity field set information, obtain the enterprise entity field value information corresponding to the enterprise profile dimension information.

[0091] Specifically, after the terminal device generates the compliance dimension set information, the terminal device can perform the following processing on each enterprise profile dimension information in the compliance dimension set information: based on the enterprise entity field set information, obtain the enterprise entity field value information corresponding to the enterprise profile dimension information, that is, based on each enterprise profile dimension information in the compliance dimension set information, through the binding mapping relationship information corresponding to the dimension, trace and extract the specific field values ​​of each enterprise entity field bound to the dimension under the target enterprise from the enterprise entity field set information.

[0092] In S550, based on the actual authorization level information corresponding to each enterprise profile dimension information, the obtained enterprise entity field value information is processed by direct rendering or de-identified rendering to generate dimension rendering content information corresponding to each enterprise profile dimension information.

[0093] Specifically, after the terminal device obtains the enterprise entity field value information, it can perform direct rendering or de-identified rendering processing on the obtained enterprise entity field value information according to the actual authorization level information corresponding to each enterprise profile dimension information, and generate dimension rendering content information corresponding to each enterprise profile dimension information.

[0094] For example, for dimensions with an actual authorization level of full visibility, the terminal device can directly render the obtained enterprise entity field value information to display the complete data; for dimensions with an actual authorization level of de-identified visibility, the terminal device can perform de-identified rendering on the obtained enterprise entity field value information to display the de-identified data, such as blurring precise numbers into ranges or mask forms.

[0095] In S560, based on preset display layout information, multiple dimensions of rendered content information are combined and processed to generate a personalized enterprise profile view for the target user.

[0096] Specifically, after the terminal device generates dimensional rendering content information, it can combine and process the multiple dimensional rendering content information based on the preset display layout information to generate a unique corporate profile view for the target user. This allows the terminal device to combine the various dimensional rendering content information to generate a complete profile view page, which is then output to the target user.

[0097] The implementation principle of the decoupled construction and fine-grained profiling authorization method for enterprise entities in this application embodiment is as follows: The terminal device can first obtain multi-source heterogeneous enterprise dataset information, and then quickly generate enterprise entity field set information based on the multi-source heterogeneous enterprise dataset information. Then, based on the enterprise entity field set information, multiple enterprise profile dimensions are effectively constructed. Then, in response to the target user's request to access the profile of the target enterprise, the actual authorization level information of the target user for each enterprise profile dimension information is reliably determined based on the target user's current user identifier information and current role identifier information. Finally, based on the actual authorization level information, the exclusive enterprise profile view information of the target user is effectively generated, thereby enabling fine-grained authorization for the subdivided dimensions of the enterprise profile. According to the specific characteristics of the target user and the actual data characteristics of the target enterprise, the visibility of each dimension is dynamically determined. At the same time, under the constraints of compliance rules, the display combination between dimensions is automatically verified and filtered. When the combination of multiple dimensions does not meet the compliance requirements, it is automatically hidden, ensuring that the same enterprise entity presents differentiated and strictly compliant profile views to different users, meeting the hierarchical classification and minimum necessary data security compliance requirements, effectively avoiding excessive exposure of sensitive data, and improving reliability.

[0098] It should be noted that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0099] Embodiments of this application also provide a decoupled construction and fine-grained profiling authorization system for enterprise entities. For ease of explanation, only the parts relevant to this application are shown, such as... Figure 7 As shown, the system 70 includes: Multi-source heterogeneous enterprise dataset information acquisition module 71: used to acquire information from multi-source heterogeneous enterprise datasets; Enterprise Entity Field Set Information Generation Module 72: Used to generate enterprise entity field set information based on multi-source heterogeneous enterprise dataset information; Enterprise Profile Dimension Information Construction Module 73: Used to construct multiple enterprise profile dimension information based on enterprise entity field set information; Actual Authorization Level Information Determination Module 74: In response to a target user's request to access the profile of a target enterprise, the module obtains three-dimensional permission data structure information and determines the actual authorization level information of the target user for each enterprise profile dimension based on the target user's current user identifier information and current role identifier information. The three-dimensional permission data structure information uses user identifier information, role identifier information, and enterprise profile dimension information as index dimensions. The element value at the intersection of each dimension in the three-dimensional permission data structure information is the authorization level information of any user under a specified role for any enterprise profile dimension. The authorization level information can be fully visible, de-identified visible, conditionally visible, or invisible. Module 75 for generating exclusive enterprise profile view information: This module is used to generate exclusive enterprise profile view information for target users based on actual authorization level information.

[0100] Optionally, the multi-source heterogeneous enterprise dataset information corresponds to multiple data source information; the aforementioned enterprise entity field set information generation module 72 includes: The original field definition information determination submodule is used to determine the original data structure information and original field definition information corresponding to each data source information based on the information of multi-source heterogeneous enterprise datasets. Field mapping rule information determination submodule: used to determine field mapping rule information for each data source based on the original data structure information and the original field definition information; The Business Meaning Consistency Information Determination Submodule is used to determine the business meaning consistency information between various original field definitions based on the field definition information and field value logic information corresponding to each data source information. Standard field definition set information generation submodule: Based on field mapping rule information and business meaning consistency information, it maps original field definition information with the same business meaning to the same standard field definition information, and generates standard field definition set information. The Enterprise Entity Field Set Information Generation Submodule is used to perform data cleaning, format standardization conversion, field regularization, missing value repair, and sensitive data desensitization on each standard field definition information in the standard field definition set information to generate enterprise entity field set information, which includes multiple enterprise entity field information.

[0101] Optionally, the above-mentioned enterprise profile dimension information construction module 73 includes: Dimension configuration instruction information acquisition submodule: used to acquire dimension configuration instruction information, which includes dimension name information, dimension category information, and dimension business definition information; Enterprise Profile Dimension Instance Information Generation Submodule: This module generates enterprise profile dimension instance information based on dimension name information, dimension category information, and dimension business definition information. The binding mapping information generation submodule is used to generate binding mapping information in response to field binding instruction information, based on enterprise profile dimension instance information and enterprise entity field set information. The binding mapping information describes the binding mapping relationship between one or more enterprise entity field information in the enterprise profile dimension instance information and enterprise entity field set information. The binding mapping information includes at least one of one-to-one mapping relationship information, one-to-many mapping relationship information, and many-to-one mapping relationship information. Enterprise profile dimension information generation submodule: This module is used to associate and store the binding mapping relationship information and enterprise profile dimension instance information to generate enterprise profile dimension information.

[0102] Optionally, the above-mentioned enterprise profile dimension instance information generation submodule includes: Dimension Unique Identifier Information Generation Unit: Used to generate unique identifier information for enterprise profile dimension instance information based on dimension name information; Dimension storage space information creation unit: used to create dimension storage space information and associate dimension storage space information with dimension unique identifier information; Classification and attribution information determination unit: used to determine the classification and attribution information of enterprise profile dimension instance information in the preset dimension classification directory system based on dimension classification information; Category attribute default configuration information determination unit: used to determine the category attribute default configuration information of enterprise profile dimension instance information based on the category attribution information; Dimensional Business Definition Description Information Determination Unit: Used to determine the dimensional business definition description information of the enterprise profile dimensional instance information based on the dimensional business interpretation information; Dimension Display Style Configuration Information Determination Unit: Used to determine the dimension display style configuration information of enterprise profile dimension instance information based on dimension classification information; Enterprise profile dimension instance information generation unit: It is used to associate and store dimension business description information, dimension display style configuration information, category attribute default configuration information and dimension unique identifier information to dimension storage space information to generate enterprise profile dimension instance information.

[0103] Optionally, the above-mentioned actual authorization level information determination module 74 includes: The 3D permission data structure information acquisition submodule is used to acquire 3D permission data structure information. The 3D permission data structure information uses user identification information, role identification information and enterprise profile dimension information as index dimensions respectively. The element value at the intersection of each dimension in the 3D permission data structure information is the authorization level information of any user under a specified role for any enterprise profile dimension. The authorization level vector information determination submodule is used to determine the authorization level vector information of the target user under the current role based on the target user's current user identification information and current role identification information, according to the three-dimensional permission data structure information. The authorization level vector information includes the authorization level information of the target user for each enterprise profile dimension information. The authorization level information can be fully visible, de-identified visible, conditionally visible, or invisible. The pending judgment dimension information determination submodule is used to determine the target enterprise profile dimension information as pending judgment dimension information. The target enterprise profile dimension information is used to describe the enterprise profile dimension information with the authorization level information as the conditional visibility level information. The conditional visibility level information is associated with judgment condition information, which includes assertion expression information corresponding to at least one entity field value information of the target enterprise. Entity Field Value Information Acquisition Submodule: Used to acquire the entity field value information corresponding to the target enterprise in the enterprise entity field set information. The entity field value information describes the specific values ​​of each enterprise entity field in the enterprise entity field set information under the target enterprise. The evaluation result information generation submodule is used to substitute entity field value information into the assertion expression information of the corresponding judgment condition information in the dimension information to be judged, perform evaluation calculation, and generate evaluation result information. Fully Visible Level Information Determination Submodule: If the evaluation result is true, the actual authorization level information of the dimension information to be decided is determined as fully visible level information. The Invisible Level Information Determination Submodule is used to determine the actual authorization level information of the dimension information to be judged as invisible level information if the evaluation result is false. The actual authorization level information determination submodule is used to determine the actual authorization level information of the target user for each enterprise profile dimension based on the fully visible level information, the de-identified visible level information, the invisible level information, the fully visible level information determined after evaluation, and the invisible level information determined after evaluation in the authorization level vector information.

[0104] Optionally, the aforementioned dedicated enterprise profile view information generation module 75 includes: The legitimate dimension set information generation submodule is used to generate legitimate dimension set information based on the enterprise profile dimension information corresponding to the fully visible level information and the enterprise profile dimension information corresponding to the anonymized visible level information. The compliance constraint rule information acquisition submodule is used to acquire preset compliance constraint rule information, which is used to constrain the display combination relationship between different enterprise profile dimensions. The compliance dimension set information generation submodule is used to filter the legal dimension set information based on the compliance constraint rules and generate the compliance dimension set information. Enterprise Entity Field Value Information Acquisition Submodule: Used to retrieve the enterprise entity field value information corresponding to the enterprise profile dimension information based on the enterprise entity field set information for each enterprise profile dimension information in the compliance dimension set information; The dimension rendering content information generation submodule is used to perform direct rendering or desensitized rendering processing on the obtained enterprise entity field value information based on the actual authorization level information corresponding to each enterprise profile dimension information, and generate dimension rendering content information corresponding to each enterprise profile dimension information. The "Exclusive Enterprise Profile View Information Generation" submodule is used to combine and process multi-dimensional rendered content information based on preset display layout information to generate exclusive enterprise profile view information for the target user.

[0105] It should be noted that the information interaction and execution process between the above modules are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, which will not be repeated here.

[0106] This application also provides a terminal device, such as... Figure 8 As shown, the terminal device 80 in this embodiment includes: a processor 81, a memory 82, and a computer program 83 stored in the memory 82 and executable on the processor 81. When the processor 81 executes the computer program 83, it implements the steps described in the above-described embodiment of the decoupled construction and fine-grained profiling authorization method, for example... Figure 1 Steps S100 to S500 are shown; or, when processor 81 executes computer program 83, it implements the functions of each module in the above-described device, for example... Figure 7 The functions of the multi-source heterogeneous enterprise dataset information acquisition module 71 to the exclusive enterprise profile view information generation module 75 are shown.

[0107] The terminal device 80 can be a desktop computer, laptop, handheld computer, cloud server, or other computing device, and includes, but is not limited to, a processor 81 and a memory 82. Those skilled in the art will understand that... Figure 8This is merely an example of terminal device 80 and does not constitute a limitation on terminal device 80. It may include more or fewer components than shown, or combine certain components, or different components. For example, terminal device 80 may also include input / output devices, network access devices, buses, etc.

[0108] The processor 81 can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.; the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0109] The memory 82 can be an internal storage unit of the terminal device 80, such as a hard disk or memory of the terminal device 80. The memory 82 can also be an external storage device of the terminal device 80, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the terminal device 80. Furthermore, the memory 82 can include both internal storage units and external storage devices of the terminal device 80. The memory 82 can also store computer program 83 and other programs and data required by the terminal device 80. The memory 82 can also be used to temporarily store data that has been output or will be output.

[0110] One embodiment of this application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable file, or some intermediate form. The computer-readable medium can include any entity or device capable of carrying computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium, etc.

[0111] The above are all preferred embodiments of this application, and are not intended to limit the scope of protection of this application. Therefore, all equivalent changes made in accordance with the methods, principles and structures of this application should be covered within the scope of protection of this application.

Claims

1. A method for decoupled construction and fine-grained profiling authorization of enterprise entities, characterized in that, The method includes: Obtain information from multi-source heterogeneous enterprise datasets; Based on the information from the multi-source heterogeneous enterprise dataset, generate enterprise entity field set information; Based on the enterprise entity field set information, multiple enterprise profile dimensions are constructed; In response to a target user's request to access the profile of a target enterprise, a three-dimensional permission data structure is obtained. Based on the target user's current user identifier and current role identifier, the actual authorization level information of the target user for each of the enterprise profile dimensions is determined. The three-dimensional permission data structure uses user identifier, role identifier, and enterprise profile dimension information as index dimensions. The element value at the intersection of each dimension in the three-dimensional permission data structure is the authorization level information of any user for any enterprise profile dimension under a specified role. The authorization level information can be fully visible, de-identified visible, conditionally visible, or invisible. Based on the actual authorization level information, a unique enterprise profile view of the target user is generated.

2. The method according to claim 1, characterized in that, The multi-source heterogeneous enterprise dataset information corresponds to information from multiple data sources; The step of generating enterprise entity field set information based on the multi-source heterogeneous enterprise dataset information includes: Based on the information of the multi-source heterogeneous enterprise dataset, determine the original data structure information and original field definition information corresponding to each of the data source information; For each of the aforementioned data source information: determine the field mapping rule information based on the original data structure information and the original field definition information; Based on the field description information and field value logic information corresponding to each of the data source information, determine the consistency information of business meaning among the original field definition information; Based on the field mapping rule information and business meaning consistency information, the original field definition information with the same business meaning is mapped to the same standard field definition information to generate standard field definition set information; For each standard field definition in the standard field definition set information, data cleaning, format standardization conversion, field regularization, missing value repair, and sensitive data desensitization are performed sequentially to generate enterprise entity field set information, wherein the enterprise entity field set information includes multiple enterprise entity field information.

3. The method according to claim 2, characterized in that, The construction of multiple enterprise profile dimensions based on the enterprise entity field set information includes: Obtain dimension configuration instruction information, wherein the dimension configuration instruction information includes dimension name information, dimension category information, and dimension business definition information; Based on the dimension name information, dimension classification information, and dimension business definition information, generate enterprise profile dimension instance information; In response to the field binding instruction information, binding mapping relationship information is generated based on the enterprise profile dimension instance information and the enterprise entity field set information. The binding mapping relationship information is used to describe the binding mapping relationship between one or more enterprise entity field information in the enterprise profile dimension instance information and the enterprise entity field set information. The binding mapping relationship information includes at least one of one-to-one mapping relationship information, one-to-many mapping relationship information and many-to-one mapping relationship information. The binding mapping relationship information and the enterprise profile dimension instance information are associated and stored to generate enterprise profile dimension information.

4. The method according to claim 3, characterized in that, The step of generating enterprise profile dimension instance information based on the dimension name information, dimension classification information, and dimension business definition information includes: Based on the dimension name information, generate the dimension unique identifier information of the enterprise profile dimension instance information; Create dimension storage space information and associate the dimension storage space information with the dimension unique identifier information; Based on the dimensional classification information, determine the classification affiliation information of the enterprise profile dimensional instance information in the preset dimensional classification directory system; Based on the classification attribution information, determine the default configuration information of the classification attributes of the enterprise profile dimension instance information; Based on the dimensional business interpretation information, determine the dimensional business definition information of the enterprise profile dimensional instance information; Based on the dimensional classification information, determine the dimensional display style configuration information of the enterprise profile dimensional instance information; The dimension business description information, dimension display style configuration information, category attribute default configuration information, and dimension unique identifier information are associated and stored in the dimension storage space information to generate enterprise profile dimension instance information.

5. The method according to claim 1, characterized in that, In response to a target user's request to access the profile of a target enterprise, the process involves obtaining three-dimensional permission data structure information and determining the target user's actual authorization level for each dimension of the enterprise profile information based on the target user's current user identifier and current role identifier information, including: Obtain three-dimensional permission data structure information; Based on the target user's current user identifier information and current role identifier information, and according to the three-dimensional permission data structure information, the authorization level vector information of the target user under the current role is determined, wherein the authorization level vector information includes the target user's authorization level information for each enterprise profile dimension. The target enterprise profile dimension information is determined as the dimension information to be judged. The target enterprise profile dimension information is used to describe the enterprise profile dimension information with the authorization level information being the conditional visibility level information. The conditional visibility level information is associated with judgment condition information, which includes assertion expression information corresponding to at least one entity field value information of the target enterprise. Obtain the entity field value information corresponding to the target enterprise in the enterprise entity field set information, wherein the entity field value information is used to describe the specific values ​​of each enterprise entity field information in the enterprise entity field set information under the target enterprise; Substitute the entity field value information into the assertion expression information of the corresponding judgment condition information in the dimension information to be judged, perform evaluation calculation, and generate evaluation result information; If the evaluation result is true, then the actual authorization level information of the dimension information to be decided is determined as the fully visible level information; If the evaluation result is false, the actual authorization level information of the dimension information to be decided is determined to be invisible level information; Based on the fully visible level information, the de-identified visible level information, the invisible level information in the authorization level vector information, the fully visible level information determined after evaluation, and the invisible level information determined after evaluation, the actual authorization level information of the target user for each of the enterprise profile dimensions is determined.

6. The method according to claim 5, characterized in that, The step of generating a personalized enterprise profile view for the target user based on the actual authorization level information includes: Based on the enterprise profile dimension information corresponding to the fully visible level information and the enterprise profile dimension information corresponding to the anonymized visible level information, a set of legal dimension information is generated. Obtain preset compliance constraint rule information, wherein the compliance constraint rule information is used to constrain the display combination relationship between different enterprise profile dimension information; Based on the compliance constraint rule information, the legal dimension set information is filtered to generate compliance dimension set information; For each enterprise profile dimension in the compliance dimension set information: based on the enterprise entity field set information, obtain the enterprise entity field value information corresponding to the enterprise profile dimension information; Based on the actual authorization level information corresponding to each of the enterprise profile dimension information, the obtained enterprise entity field value information is subjected to direct rendering or de-identified rendering processing to generate dimension rendering content information corresponding to each of the enterprise profile dimension information. Based on the preset display layout information, the rendered content information of multiple dimensions is combined and processed to generate the exclusive enterprise profile view information of the target user.

7. A decoupled construction and fine-grained profiling authorization system for enterprise entities, characterized in that, The system includes: Multi-source heterogeneous enterprise dataset information acquisition module: used to acquire information from multi-source heterogeneous enterprise datasets; Enterprise entity field set information generation module: used to generate enterprise entity field set information based on the multi-source heterogeneous enterprise dataset information; Enterprise profile dimension information construction module: used to construct multiple enterprise profile dimension information based on the enterprise entity field set information; Actual Authorization Level Information Determination Module: In response to a target user's request to access the profile of a target enterprise, this module obtains three-dimensional permission data structure information and determines the actual authorization level information of the target user for each of the enterprise profile dimensions based on the target user's current user identifier information and current role identifier information. The three-dimensional permission data structure information uses user identifier information, role identifier information, and enterprise profile dimension information as index dimensions. The element value at the intersection of each dimension in the three-dimensional permission data structure information is the authorization level information of any user under a specified role for any enterprise profile dimension. The authorization level information can be fully visible, anonymized, conditionally visible, or invisible. Exclusive Enterprise Profile View Information Generation Module: Used to generate exclusive enterprise profile view information for the target user based on the actual authorization level information.

8. The system according to claim 7, characterized in that, The multi-source heterogeneous enterprise dataset information corresponds to information from multiple data sources; The enterprise entity field set information generation module includes: The original field definition information determination submodule is used to determine the original data structure information and original field definition information corresponding to each of the data source information based on the multi-source heterogeneous enterprise dataset information. Field mapping rule information determination submodule: used to determine field mapping rule information for each of the data source information, based on the original data structure information and the original field definition information; The Business Meaning Consistency Information Determination Submodule is used to determine the business meaning consistency information between the original field definition information based on the field caliber description information and field value logic information corresponding to each of the data source information. Standard field definition set information generation submodule: Based on the field mapping rule information and business meaning consistency information, it maps original field definition information with the same business meaning to the same standard field definition information to generate standard field definition set information; Enterprise entity field set information generation submodule: used to perform data cleaning, format standardization conversion, field regularization, missing value repair and sensitive data desensitization processing on each standard field definition information in the standard field definition set information in sequence to generate enterprise entity field set information, wherein the enterprise entity field set information includes multiple enterprise entity field information.

9. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1 to 6.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 6.

Images