A business data management method, system, computer device and storage medium

By obtaining and configuring control metadata and entity control rules in the business data management system, matching user characteristic data to execute data requests, the problem of inaccurate query results in the prior art is solved, and global management and data of user permissions are realized Improved safety.

CN113553344BActive Publication Date: 2024-11-29GUANGZHOU YUNYI TECH CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202110759895.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-07-05
Publication Date
2024-11-29
Estimated Expiration
2041-07-05

AI Technical Summary

Technical Problem

When the prior art processes business information with huge amounts of data, the query results are not accurate and comprehensive enough, making it difficult to quickly obtain the information required by users.

Method used

By obtaining controllable metadata in the pending business data, adding control data identifiers, collecting and adding entity metadata tables, managing users to configure target control entities and entity control rules, and matching contents in the target entity metadata table based on user characteristic data , execute data requests to realize global management of user permissions.

Benefits of technology

Improve the security and reliability of data management, avoid unnecessary data leakage, and ensure the accuracy and comprehensiveness of query results.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113553344B_ABST
    Figure CN113553344B_ABST
Patent Text Reader

Abstract

The present invention provides a business data management method, system, computer device and storage medium. The business data management method includes: obtaining controllable metadata in the business data to be processed, adding a control data identifier to the controllable metadata, collecting controllable metadata according to the control data identifier, and adding the collected controllable metadata to the entity metadata table; obtaining the target control entity configured by the management user according to the needs of the current business, obtaining the entity control rules set by the management user for the target control entity, and the target control entity corresponds to at least one entity metadata table; obtaining the data request input by the target user, the data request includes the user feature data of the target user, obtaining at least part of the content in the entity metadata table of the target control entity that matches the user feature data according to the entity control rules, and executing the data request on at least part of the content. The present invention improves the security and reliability of data management.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of data management, and in particular to a business data management method, system, computer equipment and storage medium. Background Art

[0002] With the rapid development of PC Internet and mobile Internet, many companies have developed rapidly and carried out large-scale business expansion by taking advantage of the dividends of consumer Internet. The business expansion speed is fast enough and the business complexity is getting higher and higher. When processing huge amounts of business information, how to quickly, accurately and comprehensively obtain the information queried by users is an urgent problem that needs to be solved. Summary of the invention

[0003] The technical problem to be solved by the present invention is that the query results provided to users are not accurate and comprehensive enough. In view of the above-mentioned defects of the prior art, a business data management method, system, computer device and storage medium are provided.

[0004] The technical solution adopted by the present invention to solve its technical problem is: to provide a business data management method, including: obtaining controllable metadata in the business data to be processed, adding a control data identifier to the controllable metadata, collecting the controllable metadata according to the control data identifier, and adding the collected controllable metadata to an entity metadata table; obtaining a target control entity configured by a management user according to the needs of the current business, obtaining an entity control rule set by the management user for the target control entity, the target control entity corresponding to at least one of the entity metadata tables; obtaining a data request input by a target user, the data request including user feature data of the query user, obtaining at least part of the content in the entity metadata table of the target control entity that matches the user feature data according to the entity control rule, and executing the data request on the at least part of the content.

[0005] Among them, the step of obtaining the entity control rules set by the management user for the target control entity includes: scanning the function data to be processed, obtaining the data management function, obtaining the calling instruction input by the management user, and calling the target management function in the data management function that matches the calling instruction to generate the entity control rules.

[0006] Wherein, after the step of calling the target management function in the data management function that matches the calling instruction to generate the entity management rule, it includes: storing the entity management rule in the Redis cluster and the local virtual storage center.

[0007] Among them, the entity control rules include at least one control condition group, each of which includes at least one control condition; the control conditions include: the type and value of the controlled field, the value method and logical operator; the type and value of the controlled field include control characteristic data, and the value method includes a control function.

[0008] Among them, the step of obtaining at least part of the content in the entity metadata table of the target controlled entity that matches the user characteristic data according to the entity control rules includes: determining whether the control characteristic data and the user characteristic data match, and if so, obtaining at least part of the content in the entity metadata table of the target controlled entity that matches the user characteristic data; if not, displaying a prompt message of insufficient authority to the target user.

[0009] Among them, the step of determining whether the control feature data and the user feature data match includes: obtaining a request link according to the data request, the request link includes at least one distributed application, and obtaining the control feature data corresponding to each of the distributed applications; and determining in sequence according to the request order of the request link whether the user feature data matches the control feature data corresponding to each of the distributed applications.

[0010] Wherein, after the step of obtaining the query request input by the user, the method further includes: parsing the syntax of the data request, and calling a syntax adapter matching the syntax to parse the query request.

[0011] The technical solution adopted by the present invention to solve its technical problem is: to provide a business data management system, including: an acquisition module, used to obtain controllable metadata in the business data to be processed, add a control data identifier to the controllable metadata, collect the controllable metadata according to the control data identifier, and add the collected controllable metadata to the entity metadata table; a control module, used to obtain the target control entity configured by the management user according to the current business needs, obtain the entity control rules set by the management user for the target control entity, and the target control entity corresponds to at least one of the entity metadata tables; an execution module, used to obtain a data request input by a target user, the query data request includes user feature data of the query user, obtain at least part of the content in the entity metadata table of the target control entity that matches the user feature data according to the entity control rules, and execute the data request on the at least part of the content.

[0012] Another technical solution adopted by the present invention to solve its technical problem is: to provide a computer device, including a memory and a processor, the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the method as described above.

[0013] Another technical solution adopted by the present invention to solve its technical problem is: providing a storage medium storing a computer program, wherein when the computer program is executed by a processor, the processor executes the steps of the above method.

[0014] The beneficial effect of the present invention lies in that, compared with the prior art, the present invention obtains the target control entity configured by the management user according to the current business needs and the entity control rules corresponding to the target control entity, obtains the user feature data of the target user, obtains at least part of the content in the entity metadata table of the target control entity that matches the user feature data according to the entity control rules, and executes the data request input by the target user on at least part of the content, thereby realizing global management of user permissions, avoiding unnecessary data leakage, and improving the security and reliability of data management. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0016] Figure 1 It is a flowchart of a first embodiment of the business data management method provided by the present invention;

[0017] Figure 2 It is a schematic diagram of a page for selecting a controlled entity provided by the present invention;

[0018] Figure 3 It is a schematic diagram of a page for setting entity control rules provided by the present invention;

[0019] Figure 4 It is a schematic diagram of a page for setting control conditions provided by the present invention;

[0020] Figure 5 It is a structural diagram of an embodiment of a business data management system provided by the present invention;

[0021] Figure 6 is a schematic structural diagram of an embodiment of a computer device provided by the present invention;

[0022] Figure 7 It is a structural schematic diagram of an embodiment of the storage medium provided by the present invention. DETAILED DESCRIPTION

[0023] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0024] See also Figure 1 , Figure 1 1 is a flow chart of a first embodiment of a business data management method provided by the present invention. The business data management method provided by the present invention comprises the following steps:

[0025] S101: Acquire controllable metadata in the business data to be processed, add a control data identifier to the controllable metadata, collect the controllable metadata according to the control data identifier, and add the collected controllable metadata to the entity metadata table.

[0026] In a specific implementation scenario, the data middle-office system may have multiple APIs (Application Program Interface) at the same time, and the multiple APIs are connected to multiple different users respectively. At the same time, there may be multiple users uploading, downloading, and transferring a large amount of pending business data through multiple APIs. These pending business data include controllable metadata. Controllable metadata is a preset number of types of metadata, and controllable data identifiers can be added to the controllable metadata according to the data characteristics of the metadata. The data characteristics can be the characteristics of the controllable metadata itself, such as the content described by the controllable metadata, such as the order amount, and can also be characteristics obtained based on the sender of the controllable metadata, the API interface used for transmission, etc., such as the identity of the user who uploaded the controllable metadata, the organization to which he belongs, the project corresponding to the controllable metadata, whether the controllable metadata is public data, etc.

[0027] Specifically, controllable metadata can be obtained based on pre-set keyword characters or strings, for example, the 16-bit data after characters ABC is controllable metadata, or the string including characters ABC is controllable metadata. Controllable metadata can also be obtained based on a preset string structure, for example, a string structure of 8 digits + 8 letters is controllable metadata. Controllable metadata can also be obtained based on fixed character positions, for example, the 8th to 16th bits of data in the received data to be processed are controllable metadata. Furthermore, in combination with the services corresponding to each API interface, the corresponding acquisition rules for the data to be processed received from each API interface can be set.

[0028] In one implementation scenario, the data middle platform system includes multiple business data centers, each of which corresponds to different business content, such as a business data center corresponding to a store, a business data center corresponding to an order, etc. When scanning the data to be processed, the business data center corresponding to the controllable metadata can be obtained, and the business data center corresponding to the controllable metadata is used as the data feature of the controllable metadata.

[0029] Collect controllable metadata according to the control data identifier, and add the collected controllable metadata to the entity metadata table. The entity metadata table can be set according to the controllable entity, and each controllable entity corresponds to at least one control data identifier. It can be understood that a controllable metadata may correspond to multiple types of data characteristics. For example, the sender belongs to organization A, the target metadata corresponds to project B, and it is the relevant data of the store. The control data identifier is added according to all the data characteristics. In other words, a controllable metadata can have one or more control data identifiers, that is, a controllable metadata can be added to one or more entity metadata tables.

[0030] In this implementation scenario, the content of the added control data identifier can be annotated according to the preset annotation rules, and multiple types of data features can correspond to one or more target metadata annotations, which are set according to actual usage requirements. The data middle platform system uses the same annotation rules to annotate all controllable metadata to avoid confusion. When the annotation rules need to be modified, the previous target metadata annotations will be globally modified according to the modified annotation rules.

[0031] S102: Acquire a target control entity configured by a management user according to current business requirements, and acquire entity control rules set by the management user for the target control entity. The target control entity corresponds to at least one entity metadata table.

[0032] In a specific implementation scenario, each entity metadata table has a corresponding control entity, and each target control entity corresponds to at least one entity metadata table. The management user is a user who has management entity control rules. The management user configures the target control entity according to the current business needs. For example, at least one can be selected as the target control entity from one or more control entities corresponding to the current entity metadata table by checking or other methods. At the same time or after selecting the target control entity, the entity control rules are set for the target control entity. The entity control rules are used to control the permissions required when the entity metadata table is accessed, called, modified, and updated. Please refer to Figure 2 , Figure 2 It is a schematic diagram of a page for selecting a controlled entity provided by the present invention.

[0033] Specifically, the entity control rule includes at least one data management function. The management function can be manually uploaded by the user, or preset in the system, or obtained by scanning and reporting. In an implementation scenario, the function data to be processed is obtained, the function data to be processed is scanned, and the data management function in the function data to be processed is obtained. The data management function can be obtained by a method similar to the method of obtaining controllable metadata. Furthermore, a function management identifier can be added to the data management function to mark the purpose of the data management function, the target control entity, the required calculation parameters, etc.

[0034] The management user inputs a call instruction to call the target management function in the data management function that matches the call instruction to generate an entity management rule. For example, you can directly select a data management function as the target management function and use the target management function as the entity management rule. You can also select multiple data management functions as the target management function and limit the logical relationship between each target management function. Please refer to Figure 3 , Figure 3 It is a schematic diagram of a page for setting entity control rules provided by the present invention.

[0035] In one implementation scenario, the entity control rules are stored in the Redis cluster and the local virtual storage center of at least one business data center. Storing the entity control rules in the Redis cluster using a distributed storage method can effectively improve the efficiency of data transmission, thereby effectively improving the performance of verification. In addition, the entity control rules are stored in the Redis cluster and the local virtual storage center of at least one business data center. If the Redis cluster crashes, permission control can be performed through the entity control rules stored in the local virtual storage center. If the local virtual storage center crashes, permission control can be performed through the entity control rules of the Redis cluster.

[0036] In an implementation scenario, each business data center in the data middle platform system is configured with its own permission verification data. The entity control rules of a business data center can be packaged into one or more permission packages, and the one or more permission packages can be provided to other business data centers for permission control by exposing the API interface of the microservice and the local operation function of the business center. In other words, entity control rules can be set only in one business data center to generate at least one permission package, while other business data centers can call at least part of the permission package through the interface to implement the verification function. In this way, a low-coupling, high-cohesion system architecture of the data middle platform system can be realized, and centralized control of the verification function can be achieved.

[0037] In other implementation scenarios, the entity control rule includes at least one control condition group, each condition group includes at least one control condition, the control conditions in each condition group are in a logical and relationship, and the condition groups are in a logical or relationship. The control conditions include: the type and value of the controlled field, the value method and the logical operator. The type and value of the controlled field include control feature data, and the value method includes the target management function. Users can set the control feature data and target management function corresponding to each control condition by clicking, checking, dragging, entering a name, searching, etc. Please refer to Figure 4 , Figure 4 It is a schematic diagram of a page for setting control conditions provided by the present invention.

[0038] Specifically, the target control entity can be a store, the type of the controlled field is the organization ID, the value of the controlled field is the organization to which the target user belongs, and the value selection method selects an objective function. The generated control condition is that the target user can only see the information of the store corresponding to his or her organization.

[0039] In other implementation scenarios, after receiving a data request, the syntax of the data request is parsed, and a syntax adapter matching the syntax is called to parse the data request.

[0040] S103: Obtain a data request input by a target user, where the data request includes user feature data of the target user, obtain at least part of the content in the entity metadata table of the target controlled entity that matches the user feature data according to the entity control rule, and execute the data request on at least part of the content.

[0041] In a specific implementation scenario, a data request input by a target user is obtained, and the data request includes user feature data of the target user, and the target user is different from the management user. The user feature data includes user identity information, user attribute information, and permission rule information. Among them, the user identity information includes the user's personal identity identifier, the user attribute information includes the user's organization, the user's position in the organization, and the permission rule information includes different user identity information and different user attribute information corresponding to the permission range.

[0042] Compare the entity control rules with the user feature data to obtain the user rights of the target user. If the control feature data matches the user feature data, obtain at least part of the content in the entity metadata table of the target control entity that matches the user feature data, and execute the data request. If the control feature data does not match the user feature data, display a prompt message indicating insufficient rights to the target user. The target user can modify his or her own user feature data, or apply to the management user to request the management user to modify the entity control rules, thereby achieving the purpose of executing the data request.

[0043] For example, if the organization to which the target user belongs is Organization A, then according to the entity control rules, the target user has the right to view all information; if the organization to which the target user belongs is Organization B, then according to the entity control rules, the target user can only view information related to Organization B; if the organization to which the target user belongs is Organization C, then according to the entity control rules, the target user cannot view any information.

[0044] In other implementation scenarios, a data request may correspond to the need to access and call multiple different distributed applications. A query link may be obtained according to the data request. The data link includes at least one distributed application. The query link may be determined according to the relationship of at least one distributed application. Distributed applications A and B need to be called to respond to the query request. If distributed application A needs to use the feedback result of distributed application B as input, or is given based on the feedback result of distributed application B, then the query link is BA. If distributed application A and distributed application B are independent of each other, then the query link is one of BA or AB.

[0045] Obtain the entity control rules corresponding to each distributed application. To improve the efficiency of verification, the entity control rules are obtained from the Redis cluster first. Obtain the context variable of the target user, obtain the target control entity and at least one entity metadata table corresponding to the target control entity according to the context variable, determine whether the data request corresponds to the target control entity, and if so, obtain the entity control rules of the target control entity, parse the entity control rules, execute the authorization function corresponding to the entity control rules, generate an injection SQL (Structured Query Language) template, and store the SQL template in the Redis cluster and the local virtual storage center.

[0046] In other implementation scenarios, if the data request corresponds to the target control entity, the control data identifier of the target control entity is obtained, and the control data identifier is stored in the Redis cluster and the local virtual storage center. Further, the Redis cluster and the local virtual storage center synchronize the control data identifier to the basic data center to record the query content.

[0047] If the current distributed application passes the verification comparison, the data request and the user feature data corresponding to the data request are sent to the next distributed application in the data link, so that the next distributed application can perform verification comparison and provide feedback according to the data request if the verification passes. And so on, traverse all distributed applications in the query link. When all distributed applications in the data link are traversed, it is determined that the verification comparison has passed.

[0048] In other implementation scenarios, multiple verification and comparison methods are supported, for example, verification can be performed through RPC (Remote Procedure Call Protocol) and Spring Cloud, and verification and comparison can also be performed through REST (Representational State Transfer).

[0049] In this implementation scenario, the data request includes at least one operation of query, view, modify, download, and delete.

[0050] In an implementation scenario, the target control entity configured by the management user according to the needs of the current business is an order, and the entity control rule set by the management user for the target control entity is that the store manager of each store can view the orders of his own store. Target user X is the store manager of store Y, and the data request input by target user X is to view order information. According to the user characteristic data of target user X, the store information of store Y is obtained and displayed. Target user Z is an employee of store Y, and the data request input by target user Z is to view order information. According to the user characteristic data of target user Z, the employee of store Y is displayed, and the prompt message of insufficient authority is displayed.

[0051] From the above description, it can be seen that in this embodiment, the target control entity configured by the management user according to the current business needs and the entity control rules corresponding to the target control entity are obtained, the user feature data of the target user is obtained, and at least part of the content in the entity metadata table of the target control entity that matches the user feature data is obtained according to the entity control rules, and the data request input by the target user is executed on at least part of the content, so as to realize global management of user permissions, avoid unnecessary data leakage, and improve the security and reliability of data management.

[0052] See also Figure 5 , Figure 5 The business data management system 10 includes: an acquisition module 11 , a control module 12 , and an execution module 13 .

[0053] The acquisition module 11 is used to obtain the controllable metadata in the business data to be processed, add a control data identifier to the controllable metadata, collect the controllable metadata according to the control data identifier, and add the collected controllable metadata to the entity metadata table. The control module 12 is used to obtain the target control entity configured by the management user according to the needs of the current business, and obtain the entity control rules set by the management user for the target control entity. The target control entity corresponds to at least one entity metadata table. The execution module 13 is used to obtain the data request input by the target user. The query data request includes querying the user's user feature data, obtaining at least part of the content in the entity metadata table of the target control entity that matches the user feature data according to the entity control rules, and executing the data request on at least part of the content.

[0054] The entity control rules include at least one control condition group, each condition group includes at least one control condition; the control conditions include: the type and value of the controlled field, the value method and the logical operator; the type and value of the controlled field include control characteristic data, and the value method includes the target management function.

[0055] The execution module 13 is also used to determine whether the entity management rules and the user feature data match. If so, obtain at least part of the content in the entity metadata table of the target management entity that matches the user feature data; if not, display insufficient authority prompt information to the target user.

[0056] The execution module 13 is also used to obtain a data link according to a data request, the data link includes at least one distributed application, and obtain the entity management and control rules corresponding to each distributed application; according to the request order of the request link, it is determined in turn whether the user feature data matches the entity management and control rules corresponding to each distributed application.

[0057] The control module 12 is also used to scan the function data to be processed, obtain the data management function, obtain the calling instruction input by the management user, and call the target management function in the data management function that matches the calling instruction to generate entity control rules.

[0058] The management and control module 12 is also used to store entity management and control rules in the Redis cluster and the local virtual storage center.

[0059] The execution module 13 is also used to parse the syntax of the data request and call a syntax adapter that matches the syntax to parse the query request.

[0060] From the above description, it can be seen that in this embodiment, the business data management system obtains the target management entity configured by the management user according to the current business needs and the entity management rules corresponding to the target management entity, obtains the user feature data of the target user, obtains at least part of the content in the entity metadata table of the target management entity that matches the user feature data according to the entity management rules, and executes the data request input by the target user on at least part of the content, thereby realizing global management of user permissions, avoiding unnecessary data leakage, and improving the security and reliability of data management.

[0061] See also Figure 6 , Figure 6 2 is a schematic diagram of a computer device according to an embodiment of the present invention. The image processing device 20 includes a processor 21 and a memory 22. The processor 21 is coupled to the memory 22. The memory 22 stores a computer program, and the processor 21 executes the computer program when working to implement the following. Figure 1 The detailed method can be found in the above, which will not be described here.

[0062] See also Figure 7 , Figure 7 The storage medium 30 stores at least one computer program 31, which is used to be executed by the processor to implement the following. Figure 1 In one embodiment, the computer readable storage medium 30 may be a storage chip, a hard disk, a mobile hard disk, a USB flash drive, an optical disk, or other readable and writable storage tools in the terminal, or a server, etc.

[0063] Different from the prior art, the present invention obtains the target control entity configured by the management user according to the current business needs and the entity control rules corresponding to the target control entity, obtains the user feature data of the target user, obtains at least part of the content in the entity metadata table of the target control entity that matches the user feature data according to the entity control rules, and executes the data request input by the target user on at least part of the content, so as to realize global management of user permissions, avoid unnecessary data leakage, and improve the security and reliability of data management.

[0064] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the program can be stored in a non-volatile computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in the present application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0065] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0066] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A business data management method, characterized in that: include: Acquire controllable metadata in the business data to be processed, add a control data identifier to the controllable metadata, collect the controllable metadata according to the control data identifier, and add the collected controllable metadata to the entity metadata table; Acquire a target control entity configured by a management user according to current business requirements, and acquire an entity control rule set by the management user for the target control entity, wherein the target control entity corresponds to at least one entity metadata table; Obtaining a data request input by a target user, wherein the data request includes user feature data of the target user; Acquire a data link according to the data request, where the data link includes at least one distributed application, and acquire entity management and control rules corresponding to each distributed application; Determining in sequence according to the request order of the data link whether the user characteristic data matches the entity management and control rules corresponding to each of the distributed applications; If the user feature data matches the entity management and control rules corresponding to each of the distributed applications, at least part of the content in the entity metadata table of the target management and control entity matching the user feature data is obtained, and the data request is executed on the at least part of the content.

2. The business data management method according to claim 1, characterized in that: The entity control rule includes at least one control condition group, and each condition group includes at least one control condition; The control conditions include: the type and value of the controlled field, the value method and the logical operator; The type and value of the controlled field include control characteristic data, and the value selection method includes a target management function.

3. The business data management method according to claim 2, characterized in that: The step of acquiring at least part of the content in the entity metadata table of the target management and control entity that matches the user feature data includes: Determine whether the entity management and control rule matches the user characteristic data, and if so, obtain at least part of the content in the entity metadata table of the target management and control entity that matches the user characteristic data; If not, a prompt message indicating insufficient authority is displayed to the target user.

4. The business data management method according to claim 2, characterized in that: The step of obtaining the entity control rules set by the management user for the target control entity includes; Scan the function data to be processed, obtain the data management function, obtain the calling instruction input by the management user, and call the target management function in the data management function that matches the calling instruction to generate the entity management rule.

5. The data management method according to claim 4, characterized in that: After the step of calling the target management function in the data management function that matches the calling instruction to generate the entity management rule, the method further comprises: The entity management and control rules are stored in the Redis cluster and the local virtual storage center.

6. The data management method according to claim 1, characterized in that: After the step of obtaining the data request input by the target user, the following steps are included: The syntax of the data request is parsed, and a syntax adapter matching the syntax is called to parse the data request.

7. A business data management system, characterized in that: include: An acquisition module, used for acquiring controllable metadata in the business data to be processed, adding a control data identifier to the controllable metadata, collecting the controllable metadata according to the control data identifier, and adding the collected controllable metadata to the entity metadata table; A management and control module, used to obtain a target management and control entity configured by a management user according to current business requirements, and obtain an entity management and control rule set by the management user for the target management and control entity, wherein the target management and control entity corresponds to at least one entity metadata table; an execution module, configured to obtain a data request input by a target user, wherein the data request includes user feature data of the target user, Acquire a data link according to the data request, where the data link includes at least one distributed application, and acquire entity management and control rules corresponding to each distributed application; Determining in sequence according to the request order of the data link whether the user characteristic data matches the entity management and control rules corresponding to each of the distributed applications; If the user feature data matches the entity management and control rules corresponding to each of the distributed applications, at least part of the content in the entity metadata table of the target management and control entity matching the user feature data is obtained, and the data request is executed on the at least part of the content.

8. A computer device, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: A computer program is stored, and when the computer program is executed by a processor, the processor is caused to execute the steps of the method according to any one of claims 1 to 6.

Citation Information

Patent Citations

  • Management and control method of service authority, management and control system of service authority, and computer readable medium

    CN110968851A