Data query method and device for target user, equipment and medium

Abstract

The invention relates to the technical field of data query, and provides a data query method and device for a target user, equipment and a medium. The method comprises the following steps: in response to detection of login of a target user, acquiring a key data asset type set and a key control element list corresponding to the target user according to a preset data permission acquisition rule; caching the key data asset type set and the key control element list into a preset cache space; in response to a received target data query request of a target user, determining a target data asset list from a preset cache space according to the target data query request and the key control element list; and rendering a target data asset list corresponding to the target data query request to target equipment. According to the data query method of the target user provided by the invention, the data management capability of a complex service system is improved, the user experience is optimized, and the system maintenance cost is reduced.

Description

Technical Field

[0001] The present disclosure relates to the field of data query technology, and more particularly to methods, devices, equipment and media for querying data of target users. Background Art

[0002] With the continuous development of technologies such as cloud computing, artificial intelligence, and the Internet of Things, the data processing capabilities of complex business systems have been significantly improved. These new technologies provide more possibilities and options for the design and implementation of algorithms.

[0003] Complex business systems usually involve multiple departments, multiple processes, and multiple data types, and the relationships between data are intricate. Traditional data processing methods often fail to meet the flexibility and scalability requirements of such systems for data viewing. Therefore, it is necessary to develop an extensible algorithm to cope with the diverse data viewing needs in complex business systems.

[0004] In complex business systems, the real-time and accuracy of data are equally important. On the one hand, the system needs to be able to process and analyze data in real time in order to quickly respond to market changes and user needs; on the other hand, data accuracy is also the basis for decision-making, and any slight error may lead to wrong decisions. Therefore, the design of the algorithm needs to find a balance between real-time and accuracy.

[0005] In the related technology, a general data permission system is built based on the user-position-data permission system. By binding roles to positions, and then binding positions to data scopes, where the data scope is a set of organizations, the relationship between users and resource scopes is achieved. However, the flexibility and efficiency of data viewing in complex business systems are low. Summary of the invention

[0006] In view of this, the embodiments of the present disclosure provide a data query method, apparatus, device and medium for a target user to solve the problems of low flexibility and efficiency in viewing data in complex business systems in the prior art.

[0007] According to a first aspect of an embodiment of the present disclosure, a method for querying data of a target user is provided, comprising: in response to detecting that a target user is logged in, obtaining a key data asset type set and a key control element list corresponding to the target user according to preset data permission acquisition rules; caching the key data asset type set and the above-mentioned key control element list into a preset cache space; in response to receiving a target data query request from the target user, determining a target data asset list from the preset cache space according to the above-mentioned target data query request and the key control element list; and rendering the target data asset list corresponding to the above-mentioned target data query request to a target device.

[0008] According to a second aspect of an embodiment of the present disclosure, a data query device for a target user is provided, comprising: a login unit, configured to, in response to detecting that the target user has logged in, obtain a key data asset type set and a key control element list corresponding to the target user according to preset data permission acquisition rules; a cache unit, configured to cache the key data asset type set and the above-mentioned key control element list into a preset cache space; a query unit, configured to, in response to receiving a target data query request from the target user, determine a target data asset list from the preset cache space according to the above-mentioned target data query request and the key control element list; and a rendering unit, configured to render the target data asset list corresponding to the above-mentioned target data query request to a target device.

[0009] According to a third aspect of an embodiment of the present disclosure, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the computer program.

[0010] According to a fourth aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, which stores a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0011] Compared with the prior art, the beneficial effects of the embodiments of the present disclosure are as follows: First, in response to detecting that a target user has logged in, a key data asset type set and a key control element list corresponding to the target user are obtained according to preset data permission acquisition rules. Secondly, the key data asset type set and the above-mentioned key control element list are cached in a preset cache space. Then, in response to receiving a target data query request from the target user, a target data asset list is determined from the preset cache space according to the above-mentioned target data query request and the key control element list. Finally, the target data asset list corresponding to the above-mentioned target data query request is rendered to the target device. The data query method for target users provided by the present disclosure improves the data management capabilities of complex business systems, optimizes user experience, and reduces system maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, 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 disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0013] Figure 1 is a schematic diagram of an application scenario of a data query method for a target user according to some embodiments of the present disclosure;

[0014] Figure 2 is a flow chart of some embodiments of the target user data query method according to the present disclosure;

[0015] Figure 3 is a schematic diagram of association relationships according to some embodiments of the target user data query method disclosed herein;

[0016] Figure 4 is a technical architecture diagram of some embodiments of the target user data query method according to the present disclosure;

[0017] Figure 5 is a data structure and functional safety structure diagram of some embodiments of the target user data query method according to the present disclosure;

[0018] Figure 6 is a deployment architecture diagram of some embodiments of the target user data query method according to the present disclosure;

[0019] Figure 7 is a schematic diagram of the structure of some embodiments of a target user data query device according to the present disclosure;

[0020] Figure 8 It is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. DETAILED DESCRIPTION

[0021] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0022] It should also be noted that, for ease of description, only the parts related to the invention are shown in the drawings. In the absence of conflict, the embodiments and features in the embodiments of the present disclosure can be combined with each other.

[0023] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0024] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0025] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0026] The present disclosure will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

[0027] Figure 1 It is a schematic diagram of an application scenario of a data query method for a target user according to some embodiments of the present disclosure.

[0028] exist Figure 1 In the application scenario, first, in response to detecting that the target user is logged in, the computing device 101 can obtain the key data asset type set 102 and the key control element list 103 corresponding to the target user according to the preset data permission acquisition rules. Secondly, the computing device 101 can cache the key data asset type set 102 and the above-mentioned key control element list 103 in the preset cache space 104. Then, in response to receiving the target data query request of the target user, the target data asset list 105 is determined from the preset cache space 104 according to the above-mentioned target data query request and the key control element list. Finally, the target data asset list 105 corresponding to the above-mentioned target data query request is rendered to the target device, as shown by the reference numeral 106.

[0029] It should be noted that the computing device 101 can be hardware or software. When the computing device 101 is hardware, it can be implemented as a distributed cluster consisting of multiple servers or terminal devices, or it can be implemented as a single server or a single terminal device. When the computing device 101 is embodied as software, it can be installed in the hardware devices listed above. It can be implemented as multiple software or software modules for providing distributed services, for example, or it can be implemented as a single software or software module. No specific limitation is made here.

[0030] It should be understood that Figure 1 The number of computing devices in the embodiment is only illustrative. Any number of computing devices may be provided according to implementation requirements.

[0031] Figure 2 Detailed description of the invention The invention is a flowchart of some embodiments of the method for querying data of a target user according to the present invention. Figure 2 The data query method for the target user can be Figure 1 The computing device 101 executes. Figure 2 As shown, the data query method of the target user includes:

[0032] Step S201, in response to detecting that a target user has logged in, a key data asset type set and a key control element list corresponding to the target user are obtained according to a preset data permission acquisition rule.

[0033] In some embodiments, Figure 3 As shown: A general data permission management and control system based on user-role-data subject-data permission control model-control elements. By binding users to roles, then binding roles to data subjects, then setting data subjects to data permission control models, and then binding to control elements, and at the same time binding data subjects to controlled data asset types, the relationship between users and data asset types is achieved.

[0034] Among them, data asset type refers to the object of the controlled data range. In a simple system, all data in the entire system can be treated as one data asset type. Complex business systems can classify data according to business fields. By merging and disassembling data asset types, data permission control and management requirements for different dimensions of data asset types in complex scenarios can be achieved.

[0035] A data subject is a combination of one or more authorization control objects and data asset types. The data permission control model is a way for the application system to determine the scope of data viewing based on business requirements. A unique data permission control model can be set for a data subject. The control element is the basis for viewing the effective scope of data permissions, including but not limited to specific users, teams, organizations, etc.

[0036] Step S201 also includes the following steps:

[0037] The first step is to obtain the target user's corresponding account and password information in response to detecting that the target user has logged in.

[0038] Here, after obtaining the account and password information corresponding to the target user, the application system verifies whether the above account and password are correct.

[0039] In the second step, if the account and password information corresponding to the above target user is correct, the key data asset type set and key control factor list corresponding to the target user are obtained according to the preset data permission acquisition rules.

[0040] Among them, the above-mentioned obtaining of the key data asset type set and the key control element list corresponding to the target user according to the preset data permission acquisition rules includes: first, obtaining the target role information corresponding to the target user; wherein each target role information has a corresponding data subject; secondly, according to the data subject corresponding to each of the above target role information, obtaining the key data asset type set and the corresponding data permission control model corresponding to the target user; finally, according to the above data permission control model, obtaining the key control element list.

[0041] Here, due to the correspondence between users and roles, the correspondence between roles and data subjects, and the correspondence between data subjects and data authority control models and control elements, a key control element list is obtained. The key control element list is a collection of control elements that the target user has authority over.

[0042] It should be noted that when determining the list of key control elements, there are the following specific rules:

[0043] If it is the user himself: then the unique ID of the currently logged in user is returned;

[0044] If it is the user and his subordinates: return the user, and recursively obtain the unique IDs of the user and all users reporting to him;

[0045] If it is a custom personnel: Get the control element details, this place gets a collection of a group of users.

[0046] In an exemplary embodiment of the present application, before obtaining the target role information corresponding to the target user, the method further includes:

[0047] Get user role setting information; the role setting information includes set and unset.

[0048] Here, it is determined whether the target user has set the role information. If not, the information is directly returned to the business system. If it has been set, jump to the step "obtain the target role information corresponding to the target user".

[0049] Step S202: Cache the key data asset type set and the key control element list into a preset cache space.

[0050] In some embodiments, the target user, data asset type, and the obtained list of authorized control elements are bound, and the binding relationship is recorded using the HashMap data type and stored in a preset cache space (using centralized cache Redis). The Key is the data asset type code and the user login account, and the Value is the list of authorized control elements.

[0051] Step S203, in response to receiving a target data query request from a target user, a target data asset list is determined from a preset cache space according to the target data query request and the key control element list.

[0052] In some embodiments, step S203 includes:

[0053] The first step is to obtain a user password corresponding to the target user in response to receiving a target data query request from the target user; the user password includes the user login account.

[0054] Here, in response to receiving the target data query request from the target user, the user password and other necessary parameters are carried. The above user password includes the user login account

[0055] The second step is to obtain the above-mentioned key control element list from the above-mentioned preset cache space according to the above-mentioned user login account.

[0056] Here, after receiving the user query instruction, the backend service obtains the user login account from the user password, and the data asset type directly obtains the key control element list corresponding to the requested data asset type of the current logged-in user from the preset cache space.

[0057] The third step is to obtain the target splicing instruction based on the above target data query request and the above key control element list.

[0058] Here, the backend service executes the query instruction after splicing the above-obtained list of key control factors into default conditions during the query operation.

[0059] Specifically, first, a target control element list is generated from the above key control requirement list according to the above target data query request; then, each target control element in the above target control element list is spliced ​​to obtain a target splicing instruction.

[0060] The fourth step is to obtain the target data asset list corresponding to the target data query request according to the above target splicing instruction.

[0061] According to the above target splicing instruction, each authorized data asset corresponding to the target user query request is obtained, that is, the target data asset list.

[0062] Step S204: Rendering the target data asset list corresponding to the target data query request to the target device.

[0063] In some embodiments, the query results are further processed according to business management requirements and returned to the front-end page; after the front-end obtains the data, it processes the page rendering logic and displays it back to the front-end user.

[0064] The following is an explanation of the target user data query method provided by this application from the perspective of technical architecture. Figure 4 As shown in the figure, in this technical architecture, data processing is a core link, which runs through the entire process of front-end, back-end, database and server. First, the front-end data processing process is as follows:

[0065] The user enters data or initiates a request on the front-end interface (which may be a web page, Android application, or iOS application).

[0066] The front-end application (built using technologies such as HTML, JavaScript, React, etc.) receives user input and performs preliminary data validation and formatting.

[0067] Front-end applications may also use some front-end libraries or frameworks to process user data, such as using Ajax for asynchronous data requests, or using state management libraries (such as Redux) to manage application status.

[0068] The data transmission process is as follows:

[0069] Once the front-end has processed the data, it will send the processed data to the back-end server over the network. During this process, the data may be transmitted through HTTP requests and encoded in formats such as JSON or XML.

[0070] Web servers such as Nginx or Apache may act as reverse proxies or load balancers, receiving and forwarding these requests to backend application servers.

[0071] The backend data processing flow is as follows:

[0072] After receiving the data sent by the front end, the back-end service (which may be a server based on Node.js, Java, Python and other technologies) will perform further processing.

[0073] The above processing includes but is not limited to data verification, business logic processing, data cleaning and conversion, etc. The back-end application may also interact with middleware such as databases and caches (such as Memcached and Redis) to access or process data.

[0074] If necessary, the backend can also use log analysis tools such as ELK Stack (Elasticsearch, Logstash, Kibana) to process and analyze data.

[0075] The database processing flow is as follows:

[0076] Databases (such as MongoDB, MySQL, etc.) are responsible for storing and managing data.

[0077] The back-end application will send query, update, delete and other requests to the database, and the database will process the data accordingly.

[0078] The results of database processing are returned to the back-end application, and then after necessary processing, they are sent to the front-end or used for other purposes.

[0079] Finally, the front-end receives user input, processes it, stores it in the database, and calculates it on the server side before returning the processing result to the front-end for display to the target user. In the above process, the various components communicate with each other through the network, and use middleware and services to optimize data processing efficiency and reliability.

[0080] In addition, if Figure 5 As shown, the data structure and function design are as follows:

[0081] The security and accuracy of data are the key to ensuring production safety and improving operational efficiency. Therefore, it is particularly important to design a data permission control system based on role-based access control. The data structure designed in this application ensures that each user can only access the necessary data within his or her scope of responsibility through clear role division and sophisticated permission management. According to the organizational structure and business needs, a series of roles are defined, such as production administrators, quality controllers, safety specialists, R&D personnel, etc. Each role should have a clear scope of responsibilities and authority boundaries to ensure the compliance and effectiveness of data access. In summary, the following functions are designed and implemented:

[0082] User management function: mainly used to create, maintain, modify and delete user accounts in the system. In the system, each user should have a unique identity and be associated with his or her actual role and responsibilities in the enterprise.

[0083] Provide a user registration interface to collect basic user information (such as name, department, contact information) and login credentials (such as user name, password). Provide user self-service functions such as password reset, personal information update, etc.

[0084] Role management function: used to define and manage roles in the system and assign corresponding permissions to these roles. In the system, different roles may represent different positions or responsibilities, such as production operator, quality controller, safety administrator, etc.

[0085] Provides a role management page to collect basic role information (such as name, description, etc.) and define the correspondence between roles and positions or departments. It also provides the function of role permission allocation, assigning specific permissions to each role, including data access permissions, operation permissions, etc. It supports fine-grained permission control to meet the high requirements of the chemical industry for operational safety and data confidentiality. It also provides the function of role binding or removing users. It specifies the role information for system users. It achieves the purpose of empowering users.

[0086] Data subject management function: mainly used to create, maintain, modify and delete data subjects in the system. In the system, different roles may represent different positions or responsibilities, such as production operator, quality controller, security administrator, etc. Each role can see different types of data assets, and precise differentiated control is required.

[0087] Provides a data subject management page, which mainly collects basic information of the data subject (name, description, etc.) and defines the correspondence between the data subject and the data asset type.

[0088] Data asset type management function: Data classification is complex and diverse, usually based on different dimensions and standards. According to business attribute classification, it can be roughly divided into production data, sales data, financial data, technical data and other categories. After vertical field segmentation, it can be divided into several categories. Users of different roles in the system have different viewing and control requirements for data classification. This function aims to record the classification of control data in the application system to facilitate refined control of data permissions.

[0089] Provides a data asset type management page, which mainly collects basic information about data asset types and provides related modification and deletion functions.

[0090] In summary, user management and role management functions play a vital role in the system. Through reasonable design and implementation, the security, manageability and flexibility of the system can be ensured, providing strong support for the digital transformation of enterprises.

[0091] In addition, if Figure 6 As shown in the figure, the above deployment architecture diagram shows a highly optimized and future-oriented system construction solution. The system is based on Kubernetes, the industry-leading container orchestration platform, which ensures efficient utilization and dynamic management of resources and provides strong support for the core business of the industry.

[0092] In terms of security, the architecture ensures system security through a multi-layer protection mechanism. Kubernetes' built-in access control, network isolation strategy, and certificate management functions provide a solid protection layer for containerized applications. In addition, the combination of Elasticsearch and Kibana as a log analysis and monitoring tool can capture and analyze system logs in real time, detect and respond to potential security threats in a timely manner, and further enhance the system's security protection capabilities.

[0093] In terms of high availability, the system uses redundant deployment and automatic recovery strategies to ensure that services can be quickly restored when any single point of failure occurs. Kubernetes' automatic scaling and failover mechanism, combined with the elastic configuration of virtual machine / containerized deployment service clusters, can ensure that when business demand grows or system pressure increases, resource supply is automatically increased to maintain high service availability. At the same time, the introduction of microservice management tools such as Istio has further improved the communication quality and reliability between services.

[0094] In terms of scalability, the modular design and loose coupling characteristics of the architecture make it easy to integrate new components and services into existing systems to meet the changing needs of the industry. Whether it is a new business service, ticket service, or any other customized function, it can be quickly deployed online through Kubernetes' flexible scheduling and resource configuration capabilities. This high degree of scalability provides unlimited possibilities for business development and innovation of enterprises.

[0095] In terms of advancement, the system fully demonstrates the latest achievements in cloud computing and containerization technologies. By using Docker for containerization and packaging, the deployment, configuration, and management processes of applications are simplified; and Kubernetes, as a leader in the field of container orchestration, provides strong support for the system's automated operation and maintenance, dynamic expansion, and fault recovery. In addition, the application of advanced data analysis tools such as Elasticsearch and Kibana enables the system to efficiently process and analyze massive amounts of data, providing strong support for corporate decision-making. In summary, this deployment architecture not only meets the industry's strict requirements for security, high availability, and scalability, but also demonstrates its technological advancement and foresight.

[0096] Compared with the prior art, the embodiments of the present disclosure have the following beneficial effects: the present application mainly solves the problem of flexibility and efficiency of data viewing in complex business systems. This type of algorithm has significant effects in the following aspects:

[0097] Flexible definition of data scope: In complex business systems, data is often distributed in different databases, data tables or data structures, and the relationship between data is complex and changeable. Traditional data viewing methods may not meet the diverse viewing needs of users, such as cross-table query, multi-dimensional analysis, real-time data update, etc. Scalable algorithms allow users to flexibly define the scope of data viewing according to specific needs, including but not limited to the scope of the organization, users, business types, etc.

[0098] Performance optimization: The amount of data in complex business systems is often very large, and direct query may lead to performance bottlenecks. This algorithm improves the efficiency and response speed of data query by optimizing query strategies, index design, data caching and other technical means, ensuring that users can obtain the required data in a short time.

[0099] Dynamic scalability: As the business develops, the amount and type of data may continue to increase, and the demand for data viewing will also change. Scalable algorithms can support dynamic adjustment of the data viewing range, adapting to new business needs without modifying the algorithm itself, reducing the maintenance cost and complexity of the system.

[0100] Security and permission control: During the data viewing process, it is necessary to ensure the security of the data and prevent the leakage of sensitive data. At the same time, different users may have different data viewing permissions. The algorithm needs to be integrated with the permission management system to implement fine-grained permission control to ensure that users can only view data within their permission range.

[0101] In summary, an algorithm that can be expanded to cope with the data viewing scope of complex business systems mainly solves the problems of data viewing flexibility, efficiency, dynamic scalability, concurrent access, security and permission control, and real-time data processing and analysis. This type of algorithm is of great significance for improving the data management capabilities of complex business systems, optimizing user experience, and reducing system maintenance costs and implementation costs.

[0102] All the above optional technical solutions can be arbitrarily combined to form optional embodiments of the present application, which will not be described one by one here.

[0103] The following are embodiments of the device disclosed herein, which can be used to execute the method embodiments disclosed herein. For details not disclosed in the device embodiments disclosed herein, please refer to the method embodiments disclosed herein.

[0104] Figure 7 Schematic diagram of the structure of some embodiments of the target user data query device according to the present disclosure. Figure 7 As shown, the data query device for the target user includes: a login unit 701, which is configured to obtain a key data asset type set and a key control element list corresponding to the target user according to a preset data permission acquisition rule in response to detecting that the target user has logged in; a cache unit 702, which is configured to cache the key data asset type set and the above-mentioned key control element list into a preset cache space; a query unit 703, which is configured to determine a target data asset list from a preset cache space according to the above-mentioned target data query request and the key control element list in response to receiving a target data query request from the target user; and a rendering unit 704, which is configured to render the target data asset list corresponding to the above-mentioned target data query request to the target device.

[0105] In some optional implementations of some embodiments, the login unit 701 is configured to: in response to detecting that a target user has logged in, obtain the account and password information corresponding to the target user; if the account and password information corresponding to the target user is correct, obtain the key data asset type set and key control element list corresponding to the target user according to preset data permission acquisition rules.

[0106] In some optional implementations of some embodiments, the above-mentioned obtaining the key data asset type set and the key control element list corresponding to the target user according to the preset data permission acquisition rules includes: obtaining the target role information corresponding to the target user; wherein each target role information has a corresponding data subject; according to the data subject corresponding to each of the above-mentioned target role information, obtaining the key data asset type set and the corresponding data permission control model corresponding to the target user; according to the above-mentioned data permission control model, obtaining the key control element list.

[0107] In some optional implementations of some embodiments, before obtaining the target role information corresponding to the target user, the apparatus is further configured to: obtain user role setting information; wherein the role setting information includes set and unset.

[0108] In some optional implementations of some embodiments, the query unit 703 is configured to: in response to receiving a target data query request from a target user, obtain a user password corresponding to the target user; the user password includes a user login account; based on the user login account, obtain the key control element list from the preset cache space; based on the target data query request and the key control element list, obtain a target splicing instruction; based on the target splicing instruction, obtain a target data asset list corresponding to the target data query request.

[0109] The target splicing instruction is obtained according to the target data query request and the key control element list, including: generating a target control element list from the key control requirement list according to the target data query request; splicing each target control element in the target control element list to obtain the target splicing instruction.

[0110] In some optional implementations of some embodiments, when caching the key data asset type set and the above-mentioned key control element list into a preset cache space, a HashMap data type is used for caching.

[0111] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean 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 the present disclosure.

[0112] Reference below Figure 8 , which shows an electronic device (eg, Figure 1 Schematic diagram of the structure of the computing device 101)800. Figure 8 The server shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0113] like Figure 8 As shown, the electronic device 800 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage device 808 into a random access memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the electronic device 800 are also stored. The processing device 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0114] Typically, the following devices may be connected to the I / O interface 805: input devices 806 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices 807 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 808 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 809. The communication device 809 may allow the electronic device 800 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 8 The electronic device 800 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead. Figure 8 Each block shown in the figure may represent one device, or may represent multiple devices as required.

[0115] In particular, according to some embodiments of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, some embodiments of the present disclosure include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In some such embodiments, the computer program can be downloaded and installed from the network through the communication device 809, or installed from the storage device 808, or installed from the ROM 802. When the computer program is executed by the processing device 801, the above-mentioned functions defined in the method of some embodiments of the present disclosure are executed.

[0116] It should be noted that the computer-readable medium in some embodiments of the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In some embodiments of the present disclosure, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In some embodiments of the present disclosure, the computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0117] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0118] The computer-readable medium may be included in the device; or it may exist independently without being installed in the electronic device. The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device: in response to detecting that the target user has logged in, obtains the key data asset type set and key control element list corresponding to the target user according to the preset data permission acquisition rules; caches the key data asset type set and the key control element list in the preset cache space; in response to receiving the target data query request of the target user, determines the target data asset list from the preset cache space according to the target data query request and the key control element list; renders the target data asset list corresponding to the target data query request to the target device.

[0119] Computer program code for performing the operations of some embodiments of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0120] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0121] The units described in some embodiments of the present disclosure may be implemented by software or by hardware. The described units may also be provided in a processor, for example, may be described as: a processor including a login unit, a cache unit, a query unit, and a rendering unit. Among them, the names of these units do not constitute a limitation on the unit itself in certain cases, for example, the login unit may also be described as "a unit that, in response to detecting that a target user has logged in, obtains a set of key data asset types and a list of key control elements corresponding to the target user according to preset data permission acquisition rules."

[0122] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0123] The above descriptions are only some preferred embodiments of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present disclosure is not limited to the technical solutions formed by a specific combination of the above-mentioned technical features, but should also cover other technical solutions formed by any combination of the above-mentioned technical features or their equivalent features without departing from the above-mentioned inventive concept. For example, the above-mentioned features are replaced with the technical features with similar functions disclosed in the embodiments of the present disclosure (but not limited to) and the technical solutions formed.

Claims

1. A data query method for a target user, characterized in that: The method comprises: In response to detecting that the target user has logged in, obtaining a key data asset type set and a key control element list corresponding to the target user according to a preset data permission acquisition rule; Cache the key data asset type set and the key control element list into a preset cache space; In response to receiving a target data query request from a target user, determining a target data asset list from a preset cache space according to the target data query request and the key control element list; The target data asset list corresponding to the target data query request is rendered to the target device.

2. The target user data query method according to claim 1, characterized in that: In response to detecting that the target user is logged in, obtaining a key data asset type set and a key control element list corresponding to the target user according to a preset data authority acquisition rule, including: In response to detecting that the target user has logged in, obtaining account and password information corresponding to the target user; If the account and password information corresponding to the target user is correct, the key data asset type set and key control element list corresponding to the target user are obtained according to the preset data permission acquisition rules.

3. The target user data query method according to claim 2, characterized in that: The step of obtaining a key data asset type set and a key control element list corresponding to a target user according to a preset data permission acquisition rule includes: Obtain target role information corresponding to the target user; wherein each target role information has a corresponding data subject; According to the data subject corresponding to each target role information, a key data asset type set and a corresponding data authority control model corresponding to the target user are obtained; According to the data authority control model, a list of key control elements is obtained.

4. The target user data query method according to claim 3, characterized in that: Before obtaining the target role information corresponding to the target user, the method further includes: Obtain user role setting information; wherein the role setting information includes set and unset.

5. The target user data query method according to claim 1, characterized in that: The step of responding to receiving a target data query request from a target user and determining a target data asset list from a preset cache space according to the target data query request and a key control element list includes: In response to receiving a target data query request from a target user, obtaining a user password corresponding to the target user; the user password includes a user login account; According to the user login account, obtaining the key control element list from the preset cache space; Obtaining a target splicing instruction according to the target data query request and the key control element list; According to the target splicing instruction, a target data asset list corresponding to the target data query request is obtained.

6. The target user data query method according to claim 5, characterized in that: The step of obtaining a target splicing instruction according to the target data query request and the key control element list includes: generating a target control element list from the key control requirement list according to the target data query request; Each target control element in the target control element list is spliced ​​to obtain a target splicing instruction.

7. The target user data query method according to claim 1, characterized in that: When caching the key data asset type set and the key control element list into a preset cache space, a HashMap data type is used for caching.

8. A data query device for a target user, characterized in that: The device comprises: A login unit, configured to, in response to detecting a target user logging in, obtain a key data asset type set and a key control element list corresponding to the target user according to a preset data authority acquisition rule; A cache unit, configured to cache the key data asset type set and the key control element list into a preset cache space; A query unit, configured to, in response to receiving a target data query request from a target user, determine a target data asset list from a preset cache space according to the target data query request and a key control element list; The rendering unit is configured to render the target data asset list corresponding to the target data query request to a target device.

9. An electronic 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, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images