Label-based user and resource authority management method, device and equipment

By generating and associated user and resource tags and automatically allocating permissions, the problem of insufficient timeliness and reliability of manual configuration permission management methods in the existing technology is solved, and more efficient user and resource permission management is achieved.

CN119066633APending Publication Date: 2024-12-03BEIJING YOUTEJIE INFORMATION TECH
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411153419.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-21
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

In the prior art, manual user and resource permission management methods are difficult to adapt to dynamic changes, timeliness and reliability are insufficient, and cannot effectively meet the needs of data permission management.

Method used

By obtaining the attribute information and behavioral data of users and resources, generating user tags and resource tags, and semantic associations are performed to automatically assign permissions to improve the timeliness and reliability of permission management.

Benefits of technology

It realizes automatic matching between users and resources, improves the timeliness and reliability of permission management, and adapts to dynamically changing user and resource updates.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119066633A_ABST
    Figure CN119066633A_ABST
Patent Text Reader

Abstract

The embodiment of the invention discloses a label-based user and resource authority management method, device and equipment. The method comprises the following steps: acquiring user attribute information of a user in a database and behavior data of the user in network access, and generating a user tag according to the user attribute information and the behavior data; obtaining resource attribute information of the resource in the database, and generating a resource label according to the resource attribute information; performing semantic association on the user tag and the resource tag to obtain an association result of the user tag and the resource tag; and allocating a first target resource corresponding to the first target resource tag associated with the first target user tag to the first target user with the first target user tag according to the association result. According to the method, matching between the user and the resource is carried out through the user tag and the resource tag, authority management can be automatically carried out according to the relationship between the user and the resource, and the timeliness and reliability of authority management are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a tag-based user and resource authority management method, device and equipment. Background Art

[0002] As the amount of data in computer operations grows, companies have an increasing demand for data rights management, requiring rights management to be more efficient and flexible.

[0003] In the prior art, users and resources are usually managed by manual configuration. The fixed manual permission management method is difficult to adapt to the dynamic user update and resource update. In addition, the manual permission configuration method is not timely enough and the reliability is also slightly weak. Summary of the invention

[0004] The present invention provides a tag-based user and resource authority management method, device and equipment to improve the timeliness and reliability of user and resource authority management.

[0005] According to one aspect of the present invention, a tag-based user and resource authority management method is provided, the method comprising:

[0006] Acquire user attribute information of the user in the database and behavior data of the user in network access, and generate a user tag according to the user attribute information and the behavior data;

[0007] Obtain resource attribute information of the resource in the database, and generate a resource tag according to the resource attribute information;

[0008] Semantically associating the user tag with the resource tag to obtain an association result between the user tag and the resource tag;

[0009] According to the association result, a first target resource corresponding to a first target resource tag associated with the first target user tag is allocated to the first target user having the first target user tag.

[0010] Optionally, obtain the user's attribute information in the database and the user's behavior data during network access, including:

[0011] Obtain the user's building, user department, user role, and user level in the database as user attribute information;

[0012] The query frequency, query fields, and query filter items of the user in network access are obtained as behavior data.

[0013] Optionally, generating a user tag according to the user attribute information and the behavior data includes:

[0014] According to the user attribute information, a user cascade label arranged from upper to lower level is established: user building, user department, user role, and user level;

[0015] The query fields and query filter items whose query frequency is greater than the preset frequency threshold are used as user behavior labels;

[0016] The user cascade tag and the user behavior tag of the same user are combined to generate a user tag.

[0017] Optionally, obtaining resource attribute information of the resource in the database and generating a resource tag according to the resource attribute information includes:

[0018] Obtain the creator of the resource in the database, the creation department to which the creator belongs, the creation building to which the creation department belongs, and the resource category as resource attribute information;

[0019] Establish resource cascading labels arranged from top to bottom: create building, create department, and create person; use resource categories as resource data labels;

[0020] The resource cascade tag and resource data tag of the same resource are combined to generate a resource tag.

[0021] Optionally, semantically associating the user tag with the resource tag to obtain an association result of the user tag and the resource tag includes:

[0022] Semantically matching the user tag with each of the resource tags to determine corresponding semantic similarities;

[0023] When the semantic similarity is greater than or equal to a first preset similarity threshold, associating the corresponding user tag with the resource tag;

[0024] When the semantic similarity is less than a first preset similarity threshold, the creator role and creator level information of the creator are newly added to the resource tag, and the semantic similarity between the user tag and the resource tag is re-determined;

[0025] When the re-determined semantic similarity is greater than or equal to a second preset similarity threshold, the corresponding user tag is associated with the resource tag.

[0026] Optionally, after allocating, according to the association result, to a first target user having a first target user tag, a first target resource corresponding to a first target resource tag associated with the first target user tag, the method further includes:

[0027] Obtaining association configuration information of a second target user tag and a second target resource tag set by an administrator;

[0028] According to the association configuration information, a second target resource with a corresponding second target resource tag is allocated to a second target user with a second target user tag.

[0029] Optionally, the method further includes:

[0030] The user tag table records the tag information of each user supported by the database, and the user table records the tag information corresponding to each user;

[0031] The resource tag table records the tag information of each resource supported by the database, and the resource table records the tag information corresponding to each resource.

[0032] According to another aspect of the present invention, a user and resource authority management device based on tags is provided, the device comprising:

[0033] A user tag generation module, used to obtain user attribute information of the user in the database and behavior data of the user in network access, and generate a user tag according to the user attribute information and the behavior data;

[0034] A resource tag generation module, used to obtain resource attribute information of resources in the database and generate resource tags according to the resource attribute information;

[0035] An association result determination module, used to semantically associate the user tag with the resource tag to obtain an association result between the user tag and the resource tag;

[0036] The resource allocation module is used to allocate, according to the association result, a first target resource corresponding to a first target resource tag associated with the first target user tag to a first target user having a first target user tag.

[0037] According to another aspect of the present invention, there is provided an electronic device, the electronic device comprising:

[0038] at least one processor; and

[0039] a memory communicatively connected to the at least one processor; wherein,

[0040] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the tag-based user and resource permission management method described in any embodiment of the present invention.

[0041] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the tag-based user and resource permission management method described in any embodiment of the present invention when executed.

[0042] According to another aspect of the present invention, a computer program product is provided, including a computer program, wherein when the computer program is executed by a processor, the tag-based user and resource authority management method described in any embodiment of the present invention is implemented.

[0043] The technical solution of the embodiment of the present invention obtains user attribute information of the user in the database and behavior data in network access, and generates a user tag according to the user attribute information and behavior data; obtains resource attribute information of the resource in the database, and generates a resource tag according to the resource attribute information; semantically associates the user tag with the resource tag to obtain an association result between the user tag and the resource tag; and according to the association result, allocates a first target resource corresponding to a first target resource tag associated with the first target user tag to a first target user with a first target user tag, thereby solving the problem of authority management between users and resources. By matching users with resources through user tags and resource tags, authority management can be automatically performed according to the relationship between users and resources, thereby improving the timeliness and reliability of authority management.

[0044] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. 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 creative work.

[0046] Figure 1 is a flowchart of a tag-based user and resource authority management method provided according to Embodiment 1 of the present invention;

[0047] Figure 2 is a structural diagram of a tag-based user and resource authority management device provided according to Embodiment 2 of the present invention;

[0048] Figure 3 It is a structural schematic diagram of an electronic device for implementing the tag-based user and resource authority management method of an embodiment of the present invention. DETAILED DESCRIPTION

[0049] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings 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 should fall within the scope of protection of the present invention.

[0050] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0051] Embodiment 1

[0052] Figure 1 This is a flowchart of a tag-based user and resource authority management method provided according to the first embodiment of the present invention. This embodiment is applicable to the situation where an enterprise manages users and resources in a system accordingly. The method can be executed by a tag-based user and resource authority management device. The tag-based user and resource authority management device can be implemented in the form of hardware and / or software. The tag-based user and resource authority management device can be configured in an electronic device such as a computer. Figure 1 As shown, the method includes:

[0053] Step 110: Obtain the user attribute information of the user in the database and the behavior data of the user in network access, and generate a user tag according to the user attribute information and the behavior data.

[0054] Among them, the acquisition of user-related information is only obtained after the user's authorization, and the acquisition method is reasonable and legal. User attribute information includes but is not limited to: user building, user department, user role, user level, user age, and user gender. Behavioral data includes but is not limited to: user access to resources, such as access time, access frequency, access duration, access method, and access search information. User tags can consider user behavior data based on user attribute information, so that user permissions are increasingly in line with the user's actual access behavior and improve the reliability of permission allocation.

[0055] In an optional implementation of an embodiment of the present invention, user attribute information of a user in a database and behavioral data of a user in network access are obtained, including: obtaining the user building, user department, user role, and user level of the user in the database as user attribute information; obtaining the query frequency, query field, and query filter items of the user in network access as behavioral data.

[0056] The user building may be the building number of the user's office. The user department may be the functional department of the user in the enterprise application, such as the R&D department, product department, or finance department. The user role may be the technical position of the user in the enterprise, such as engineer, product manager, or finance manager. The user level may be the level of the user in the enterprise, such as junior, intermediate, or senior.

[0057] The query frequency can be the number of times a user has accessed a resource in the past week or month. The query field is the query keyword that the user uses when accessing a resource. The query filter item can be the filter word that the user sets when filtering resources.

[0058] In an optional implementation of an embodiment of the present invention, a user tag is generated based on user attribute information and behavior data, including: establishing user cascade tags arranged from superior to subordinate based on the user attribute information: user building, user department, user role, and user level; using query fields and query filter items whose query frequency is greater than a preset frequency threshold as user behavior tags; and merging the user cascade tag and user behavior tag of the same user to generate a user tag.

[0059] Specifically, the user cascade tag can be: user building->user department->user role->user level. The user tag generated by merging the user cascade tag and the user behavior tag can be: user building->user department->user role->user level->query field and query filter item.

[0060] Step 120: Obtain resource attribute information of the resource in the database, and generate a resource tag according to the resource attribute information.

[0061] Resource attribute information includes but is not limited to: resource creation information and resource category information. When generating resource tags, combining the creation information with the resource category information can make resource allocation more in line with the actual situation of the enterprise and improve the reliability of user and resource authority management.

[0062] In an optional implementation of an embodiment of the present invention, resource attribute information of a resource in a database is obtained, and a resource tag is generated based on the resource attribute information, including: obtaining the creator of the resource in the database, the creation department to which the creator belongs, the creation building to which the creation department belongs, and the resource category as resource attribute information; establishing resource cascade tags arranged from superior to subordinate as: creation building, creation department, and creator; using the resource category as a resource data tag; and merging the resource cascade tag and the resource data tag of the same resource to generate a resource tag.

[0063] Specifically, the resource cascade tag is Create Building -> Create Department -> Create Person. The resource tag generated by merging the resource cascade tag and the resource data tag is: Create Building -> Create Department -> Create Person -> Resource Category.

[0064] Step 130: semantically associate the user tag with the resource tag to obtain an association result of the user tag and the resource tag.

[0065] The semantic association may be to determine whether the meanings represented by the user tag and the resource tag are the same. If the user tag and the resource tag have the same meaning, the user tag and the resource tag may be associated. Specifically, the semantic association may be implemented by a semantic recognition model. Alternatively, the semantic association may be implemented by a similarity calculation algorithm. For example, the semantic association between the user tag and the resource tag is determined by a cosine similarity algorithm.

[0066] In an optional implementation of an embodiment of the present invention, a user tag is semantically associated with a resource tag to obtain an association result between the user tag and the resource tag, including: semantically matching the user tag with each resource tag to determine the corresponding semantic similarity; when the semantic similarity is greater than or equal to a first preset similarity threshold, associating the corresponding user tag with the resource tag; when the semantic similarity is less than the first preset similarity threshold, adding the creator role and creator level information of the creator to the resource tag, and redetermining the semantic similarity between the user tag and the resource tag; when the redetermined semantic similarity is greater than or equal to a second preset similarity threshold, associating the corresponding user tag with the resource tag.

[0067] Among them, semantic matching can determine the semantic similarity between the user tag and each resource tag through a semantic recognition model or a similarity algorithm. The first preset similarity threshold is greater than the second preset similarity threshold. When the semantic similarity is greater than the first preset similarity threshold, the user tag can be directly associated with the resource tag.

[0068] When the semantic similarity is less than the first preset similarity threshold, in order to avoid the similarity deviation caused by the misalignment of the user tag and the resource tag, and to avoid the irrationality of resource allocation due to the too small similarity threshold, the user tag and the resource tag can be further supplemented. In the supplementary judgment, the creator role and creator level information of the creator can be added to the resource tag, and the preset similarity threshold can be lowered. On the basis of the alignment of the resource tag and the user tag, the semantic similarity is recalculated, and when the recalculated semantic similarity is greater than or equal to the second preset similarity threshold, the user tag and the resource tag are aligned. Through supplementary judgment, on the basis of the alignment of the resource tag and the user tag, further tag matching is performed to improve the rationality of the permission setting.

[0069] Through two-step similarity calculation, for the case of misaligned labels, user labels and resource labels can be matched with a higher similarity; for the case of aligned labels, user labels and resource labels can be matched with a lower similarity; thus improving the rationality and accuracy of user and resource authority management. Exemplarily, the first preset similarity threshold can be a value between 85% and 100%; the second preset similarity threshold can be a value between 75% and 85%.

[0070] Step 140: According to the association result, a first target resource corresponding to a first target resource tag associated with the first target user tag is allocated to the first target user having the first target user tag.

[0071] In an optional implementation of an embodiment of the present invention, the method further includes: recording each user tag information supported by the database through a user tag table, and recording the tag information corresponding to each user through a user table; recording each resource tag information supported by the database through a resource tag table, and recording the tag information corresponding to each resource through a resource table.

[0072] Table 1

[0073] User Tag ID User Tags 1 Building A->R&D Department->R&D Engineer->Senior 2 Building B -> Product Department -> Product Manager -> Intermediate 3 Building A->R&D Department->Technical Consultant->Senior

[0074] Table 2

[0075] User ID username The ID of the user tag 1 User001 1,3 2 User 002 2

[0076] Table 1 is a user tag table provided according to the first embodiment of the present invention. Table 1 includes a user tag ID and corresponding specific user tags. Table 2 is a user table provided according to the first embodiment of the present invention. Table 2 includes a user ID, a user name, and the ID of the user tag possessed by the user. Table 3 is a resource tag table provided according to the first embodiment of the present invention. Table 3 includes a resource tag ID and corresponding specific resource tags. Table 4 is a resource table provided according to the first embodiment of the present invention. Table 4 includes a resource ID, a resource name, and the ID of the resource tag corresponding to the resource.

[0077] Table 3

[0078] Resource tag ID Resource Tags 1 Building A->R&D Department->User 3 2 Building B->Product Department->User 4 3 Building A->R&D Department->User 5

[0079] Table 4

[0080] Resource ID Resource Name The ID of the corresponding resource tag 1 Resource 001 1,3 2 Resource 002 2

[0081] By performing data maintenance in a memory or database through tables as exemplified in Tables 1 to 4, it is convenient for the device to scan when allocating resources to users, and to achieve fast user and resource authority management. For example, through the data in Tables 1 and 3, user tag 1 can be matched with resource tag 1; user tag 2 can be matched with resource tag 2; and user tag 3 can be matched with resource tag 3. According to Table 2, user 001 has user tags 1 and 3; according to the association results, resources corresponding to resource tags 1 and 3 can be allocated; according to Table 4, resource 001 can be allocated to user 001. According to Table 2, user 002 has user tag 2; according to the association results, resources corresponding to resource tag 2 can be allocated; according to Table 4, resource 002 can be allocated to user 002.

[0082] Based on the above implementation, optionally, after allocating a first target resource corresponding to a first target resource tag associated with the first target user tag to a first target user having a first target user tag according to the association result, the method further includes: obtaining association configuration information of a second target user tag and a second target resource tag set by an administrator; and allocating a second target resource corresponding to a second target resource tag to a second target user having a second target user tag according to the association configuration information.

[0083] The technical solution of the embodiment of the present invention can support manual permission setting on the basis of supporting automatic matching of users and resources, thereby improving the flexibility of permission setting. In a specific solution, a permission table of users and resources can be set. Table 5 is a permission table of users and resources provided according to the first embodiment of the present invention.

[0084] Table 5

[0085] Permission ID User ID Resource ID How to set permissions 1 1 1 0 2 2 2 0 3 1 2 1

[0086] According to the data in Table 5, according to automatic permission allocation (permission setting mode is 0), resource 1 can be allocated to user 1, and resource 2 can be allocated to user 2; according to administrator permission allocation (permission setting mode is 1), resource 2 can be allocated to user 1. When generating the permission table of users and resources, the permissions in the table can be deduplicated to avoid repeated permission settings. After the administrator sets the user permissions, permission deletion requests can also be sent to the administrator regularly to determine whether the permissions set by the administrator need to be deleted, so as to delete temporary permissions in time to ensure resource access security.

[0087] The technical solution of this embodiment obtains user attribute information of the user in the database and behavior data in network access, and generates a user tag according to the user attribute information and behavior data; obtains resource attribute information of the resource in the database, and generates a resource tag according to the resource attribute information; semantically associates the user tag with the resource tag to obtain an association result between the user tag and the resource tag; and according to the association result, allocates a first target resource corresponding to a first target resource tag associated with the first target user tag to a first target user with a first target user tag, thereby solving the problem of authority management between users and resources. By matching users with resources through user tags and resource tags, authority management can be automatically performed according to the relationship between users and resources, thereby improving the timeliness and reliability of authority management.

[0088] Embodiment 2

[0089] Figure 2 1 is a schematic diagram of a user and resource authority management device based on tags according to the second embodiment of the present invention. Figure 2 As shown, the device includes: a user tag generation module 210, a resource tag generation module 220, an association result determination module 230 and a resource allocation module 240. Among them:

[0090] The user tag generation module 210 is used to obtain the user attribute information of the user in the database and the behavior data of the user in the network access, and generate the user tag according to the user attribute information and the behavior data;

[0091] The resource tag generation module 220 is used to obtain resource attribute information of the resource in the database and generate a resource tag according to the resource attribute information;

[0092] The association result determination module 230 is used to semantically associate the user tag with the resource tag to obtain the association result of the user tag and the resource tag;

[0093] The resource allocation module 240 is configured to allocate, according to the association result, a first target resource corresponding to a first target resource tag associated with the first target user tag to the first target user having the first target user tag.

[0094] Optionally, the user tag generating module 210 includes:

[0095] A user attribute information acquisition unit, used to acquire the user building, user department, user role, and user level of the user in the database as user attribute information;

[0096] The behavior data acquisition unit is used to acquire the query frequency, query field, and query filter item of the user in network access as behavior data.

[0097] Optionally, the user tag generating module 210 includes:

[0098] A user cascade label generation unit, used to establish user cascade labels arranged from upper to lower levels according to user attribute information: user building, user department, user role, and user level;

[0099] A user behavior label generation unit, used to use the query fields and query filter items whose query frequency is greater than a preset frequency threshold as user behavior labels;

[0100] The user tag generation unit is used to merge the user cascade tag and the user behavior tag of the same user to generate a user tag.

[0101] Optionally, the resource tag generating module 220 includes:

[0102] A resource attribute information acquisition unit, used to acquire the creator of the resource, the creation department to which the creator belongs, the creation building to which the creation department belongs, and the resource category in the database as resource attribute information;

[0103] A resource cascade label establishment unit, used to establish resource cascade labels arranged from upper level to lower level: create building, create department, and create person;

[0104] A resource data label determination unit, used for using the resource category as a resource data label;

[0105] The resource tag generation unit is used to merge the resource cascade tag and the resource data tag of the same resource to generate a resource tag.

[0106] Optionally, the association result determination module 230 includes:

[0107] A first semantic similarity determination unit, used to semantically match the user tag with each resource tag to determine the corresponding semantic similarity;

[0108] A first associating unit, configured to associate the corresponding user tag with the resource tag when the semantic similarity is greater than or equal to a first preset similarity threshold;

[0109] A second semantic similarity determination unit is used to add the creator role and creator level information of the creator to the resource tag when the semantic similarity is less than the first preset similarity threshold, and to re-determine the semantic similarity between the user tag and the resource tag;

[0110] The second associating unit is used to associate the corresponding user tag with the resource tag when the re-determined semantic similarity is greater than or equal to a second preset similarity threshold.

[0111] Optionally, the device further includes:

[0112] An association configuration information acquisition module, configured to acquire association configuration information of a second target user tag and a second target resource tag set by an administrator after allocating a first target resource corresponding to a first target resource tag associated with the first target user tag to the first target user having the first target user tag according to the association result;

[0113] Another resource allocation module is used to allocate a second target resource with a corresponding second target resource tag to a second target user with a second target user tag according to the association configuration information.

[0114] Optionally, the device further includes:

[0115] A first information recording module is used to record the tag information of each user supported by the database through a user tag table, and to record the tag information corresponding to each user through a user table;

[0116] The second information recording module is used to record the label information of each resource supported by the database through the resource label table, and record the label information corresponding to each resource through the resource table.

[0117] The tag-based user and resource authority management device provided in the embodiment of the present invention can execute the tag-based user and resource authority management method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0118] In the technical solutions of the embodiments of the present invention, the collection, storage, use, processing, transmission, provision and disclosure of user personal information are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0119] Embodiment 3

[0120] Figure 3A schematic diagram of the structure of an electronic device 10 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0121] like Figure 3 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0122] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0123] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a tag-based user and resource authority management method.

[0124] In some embodiments, the tag-based user and resource permission management method can be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the tag-based user and resource permission management method described above can be performed. Alternatively, in other embodiments, the processor 11 can be configured to execute the tag-based user and resource permission management method by any other appropriate means (for example, by means of firmware).

[0125] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0126] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0127] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, 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 foregoing.

[0128] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0129] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by 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), a blockchain network, and the Internet.

[0130] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0131] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0132] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A tag-based user and resource authority management method, characterized in that: include: Acquire user attribute information of the user in the database and behavior data of the user in network access, and generate a user tag according to the user attribute information and the behavior data; Obtain resource attribute information of the resource in the database, and generate a resource tag according to the resource attribute information; Semantically associating the user tag with the resource tag to obtain an association result between the user tag and the resource tag; According to the association result, a first target resource corresponding to a first target resource tag associated with the first target user tag is allocated to the first target user having the first target user tag.

2. The method according to claim 1, characterized in that Obtain user attribute information in the database and behavior data during network access, including: Obtain the user's building, user department, user role, and user level in the database as user attribute information; The query frequency, query fields, and query filter items of the user in network access are obtained as behavior data.

3. The method according to claim 2, characterized in that Generating a user tag according to the user attribute information and the behavior data includes: According to the user attribute information, a user cascade label arranged from upper to lower level is established: user building, user department, user role, and user level; The query fields and query filter items whose query frequency is greater than the preset frequency threshold are used as user behavior labels; The user cascade tag and the user behavior tag of the same user are combined to generate a user tag.

4. The method according to claim 1, characterized in that: Obtaining resource attribute information of a resource in a database and generating a resource tag according to the resource attribute information includes: Obtain the creator of the resource in the database, the creation department to which the creator belongs, the creation building to which the creation department belongs, and the resource category as resource attribute information; Establish resource cascading labels arranged from top to bottom: create building, create department, and create person; use resource categories as resource data labels; The resource cascade tag and resource data tag of the same resource are combined to generate a resource tag.

5. The method according to claim 1, characterized in that The user tag is semantically associated with the resource tag to obtain an association result between the user tag and the resource tag, including: Semantically matching the user tag with each of the resource tags to determine corresponding semantic similarities; When the semantic similarity is greater than or equal to a first preset similarity threshold, associating the corresponding user tag with the resource tag; When the semantic similarity is less than a first preset similarity threshold, the creator role and creator level information of the creator are newly added to the resource tag, and the semantic similarity between the user tag and the resource tag is re-determined; When the re-determined semantic similarity is greater than or equal to a second preset similarity threshold, the corresponding user tag is associated with the resource tag.

6. The method according to claim 1, characterized in that After allocating, according to the association result, to the first target user having the first target user tag, the first target resource corresponding to the first target resource tag associated with the first target user tag, the method further includes: Obtaining association configuration information of a second target user tag and a second target resource tag set by an administrator; According to the association configuration information, a second target resource with a corresponding second target resource tag is allocated to a second target user with a second target user tag.

7. The method according to claim 1, characterized in that Also includes: The user tag table records the tag information of each user supported by the database, and the user table records the tag information corresponding to each user; The resource tag table records the tag information of each resource supported by the database, and the resource table records the tag information corresponding to each resource.

8. A user and resource authority management device based on tags, characterized in that: include: A user tag generation module, used to obtain user attribute information of the user in the database and behavior data of the user in network access, and generate a user tag according to the user attribute information and the behavior data; A resource tag generation module, used to obtain resource attribute information of resources in the database and generate resource tags according to the resource attribute information; An association result determination module, used to semantically associate the user tag with the resource tag to obtain an association result between the user tag and the resource tag; The resource allocation module is used to allocate, according to the association result, a first target resource corresponding to a first target resource tag associated with the first target user tag to a first target user having a first target user tag.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the tag-based user and resource permission management method described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the tag-based user and resource authority management method according to any one of claims 1 to 7 when executed.