Resource management method and device, equipment and storage medium

The resource management method addresses the inefficiencies of traditional access control systems by determining user access rights based on organization and position requirements, enhancing security and efficiency in government collaboration scenarios.

CN119066710APending Publication Date: 2024-12-03JD DIGITS HAIYI INFORMATION TECHNOLOGY CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

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

AI Technical Summary

Technical Problem

Existing resource access management systems face challenges in managing complex and dynamic personnel turnover in government collaboration scenarios, leading to security risks and inefficient permission management due to the limitations of ACL, RBAC, and ABAC technologies.

Method used

A resource management method that determines user access rights based on organization and position requirements, using a comparison of user role information with permission requirements to ensure only authorized users can access target resources, and dynamically adjusts permissions in response to personnel changes.

Benefits of technology

This approach enhances data security, reduces maintenance costs, and improves management efficiency by ensuring fine-grained, flexible, and secure access control, adapting to frequent personnel changes in government collaboration scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119066710A_ABST
    Figure CN119066710A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a resource management method and device, equipment and a storage medium. The method comprises the steps that based on an access request, sent by a user, of a target resource, permission requirements corresponding to the target resource are obtained, and the permission requirements at least comprise user organization requirements and user post requirements; and determining role information of the user, wherein the role information at least indicates a target organization to which the user belongs and a target post of the user in the target organization. And based on a comparison result of the role information of the user and the permission requirement, determining the access permission of the user to the target resource. Through the process, refinement and flexibility of authority management can be realized, and the management efficiency is greatly improved while the resource security is ensured.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Example embodiments of the present disclosure generally relate to the field of computers, and more particularly, to a resource management method, apparatus, device, and storage medium. Background Art

[0002] Resource access management involves the management of a large number of applications and data, and needs to meet diverse permission requirements. However, due to frequent personnel turnover, resource access management is complex and updates are not timely, which poses a major security risk. Summary of the invention

[0003] In a first aspect of the present disclosure, a resource management method is provided. The method may include: based on an access request for a target resource sent by a user, obtaining a permission requirement corresponding to the target resource, wherein the permission requirement includes at least a user organization requirement and a user position requirement. Determining the user's role information, wherein the role information indicates at least the target organization to which the user belongs and the user's target position in the target organization. Based on a comparison result between the user's role information and the permission requirement, determining the user's access rights to the target resource.

[0004] In a second aspect of the present disclosure, a resource management device is provided. The device may include: a permission requirement acquisition module, configured to acquire the permission requirements corresponding to the target resource based on the access request of the target resource sent by the user, and the permission requirements at least include the requirements of the organization to which the user belongs and the requirements of the user's position. A role information determination module, configured to determine the role information of the user, and the role information at least indicates the target organization to which the user belongs and the target position of the user in the target organization. An access permission determination module, configured to determine the user's access rights to the target resource based on the comparison result of the user's role information and the permission requirements.

[0005] In a third aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory, the at least one memory is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit. When the instructions are executed by the at least one processing unit, the electronic device executes the method of the first aspect.

[0006] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein a computer program is stored on the medium, and when the computer program is executed by a processor, the method of the first aspect is implemented.

[0007] In a fifth aspect of the present disclosure, a computer program product or computer program is provided, the computer program product or computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from a computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method provided in various optional ways in one aspect of the embodiment of the present application. In other words, when the computer instructions are executed by the processor, the method provided in various optional ways in one aspect of the embodiment of the present application is implemented.

[0008] It should be understood that the content described in this section is not intended to limit the key features or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:

[0010] Figure 1 A schematic diagram showing an example environment in which embodiments of the present disclosure can be implemented;

[0011] Figure 2 A flowchart showing a method for managing resources according to some embodiments of the present disclosure is shown;

[0012] Figure 3 A schematic diagram showing a resource management method according to some embodiments of the present disclosure;

[0013] Figure 4 A schematic diagram of organization entity mapping rules according to some embodiments of the present disclosure is shown;

[0014] Figure 5 A schematic structural block diagram showing a resource management device according to some embodiments of the present disclosure; and

[0015] Figure 6 A block diagram of an electronic device in which one or more embodiments of the present disclosure may be implemented is shown. DETAILED DESCRIPTION

[0016] 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.

[0017] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may also be included below.

[0018] Herein, unless explicitly stated, executing a step “in response to A” does not mean executing the step immediately after “A” but may include one or more intermediate steps.

[0019] It is understandable that the data involved in this technical solution (including but not limited to the data itself, the acquisition, use, storage or deletion of the data) shall comply with the requirements of relevant laws, regulations and relevant provisions.

[0020] It is understandable that before using the technical solutions disclosed in the various embodiments of the present disclosure, the types, scopes of use, usage scenarios, etc. of the information involved in the present disclosure should be informed to relevant users and their authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations. The relevant users may include any type of right holders, such as individuals, enterprises, and groups.

[0021] For example, in response to receiving an active request from a user, a prompt message is sent to the relevant user to clearly prompt the relevant user that the operation requested to be performed will require obtaining and using the information of the relevant user, so that the relevant user can independently choose whether to provide information to software or hardware such as an electronic device, application, server or storage medium that executes the operation of the technical solution of the present disclosure based on the prompt message.

[0022] As an optional but non-limiting implementation, in response to receiving an active request from a relevant user, a prompt message is sent to the relevant user, for example, in the form of a pop-up window, in which the prompt message may be presented in text form. In addition, the pop-up window may also carry a selection control for the user to select "agree" or "disagree" to provide information to the electronic device.

[0023] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that meet relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0024] Figure 1 A schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented is shown. In the example environment 100 , an electronic device 110 can support the operation of a target application 120 . A user 140 can access a target resource 130 via the target application 120 .

[0025] The target application 120 can provide various types of data resources, and various types of data resources can correspond to the target resource 130. The data resource can be a content instance created by the user 140 or other users. For example, the data resource can be unstructured content. For example, documents (for example, word documents, PDF documents, presentations, spreadsheet documents, etc.), emails, messages (for example, conversation messages on instant messaging service components), calendars, schedules, tasks, audio, video, images, etc. The data resource can also be structured content. For example, data tables, forms, etc. In some embodiments, the electronic device 110 communicates with a server to implement the provision of services for the target application 120.

[0026] The electronic device 110 can be any type of mobile terminal, fixed terminal or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, personal communication systems (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, television receivers, radio broadcast receivers, e-book devices, gaming devices, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. In some embodiments, the electronic device 110 can also support any type of interface for the user (such as "wearable" circuits, etc.). The server can be various types of computing systems / servers that can provide computing power, including but not limited to mainframes, edge computing nodes, computing devices in cloud environments, and the like.

[0027] It should be understood that the structure and functionality of environment 100 are described for exemplary purposes only and do not imply any limitation on the scope of the present disclosure.

[0028] The government collaboration scenario is a scenario where access control is strict and authority management is extremely important. In the government collaboration scenario, units and departments of different levels and different businesses have a strict division of responsibilities. Even in the same transaction, authority will be strictly divided according to differences in personnel positions, management or execution functions. For example, in grassroots governance affairs, multiple functional departments often jointly execute business. For example, government officials working at the grassroots level of the street are mainly responsible for the execution of tasks and the summary and reporting of information, while government officials in vertical management units or departments are mainly responsible for management and coordination. In this process, due to different roles, the functions of the government system that each party can use and the coverage of the data obtained are different.

[0029] Compared with collaborative scenarios such as company operations, in government collaboration scenarios, once information leakage occurs, important information such as residents' personal information and government affairs records may be illegally obtained and used by others, leading to major problems such as the destruction of public security and the theft of people's property. In the scenario of government collaboration, business needs and processes are rapidly iterated, organizational relationships are complex, and the number of participants is large. Therefore, it is necessary to design a secure, controllable, flexible and efficient permission access control system to ensure that personnel permissions can be adjusted dynamically, timely and automatically in response to frequent changes in personnel organizational relationships and when organizational adjustments occur from time to time, thereby meeting the security management of resources.

[0030] Conventional permission access control systems are mainly based on access control list (ACL) technology, role-based access control (RBAC) technology and attribute-based access control (ABAC) technology.

[0031] First, let's take ACL technology as an example. This technology binds permissions to specific users, ensuring that permissions can be flexibly authorized to different users, and that permissions of a certain user can be quickly queried and obtained. However, in special scenarios such as government collaboration scenarios, due to the large number of people involved, positions and functions change dynamically. For ACL technology, it is extremely difficult to maintain the continuous addition and deletion of authorization records.

[0032] Let's take RBAC technology as an example. This technology binds permissions to roles, assigns roles to users, and implements batch authorization. In some complex scenarios, RBAC is difficult to implement fine-grained access control. For example, for the role of director, for the same resource, Director A has access but Director B does not. If you rely on RBAC technology, when there are a large number of participants, you need to maintain each participant. This results in excessive consumption of storage resources.

[0033] Finally, let's take ABAC technology as an example. This technology does not grant permissions directly to users, but uses policies to determine whether the current user's attributes meet the access requirements. The policy technology of ABAC technology is expressed as a complex Boolean operation of multiple different attributes, and the user's attributes are the smallest logical judgment unit of ABAC technology. When judging whether a user has the right to access protected resources, ABAC technology needs to judge whether the attributes of various elements such as users, resources, operations, and environments meet the formulated policies. In the government scenario, the operation of ABAC technology depends on attribute sets, resource attribute sets, and rule bases. Take XX City as an example. XX City has 400,000 civil servants. If ABAC is used for access control, it is necessary to maintain a separate attribute set for each of these 400,000 civil servants. Both the creation and maintenance of sets consume huge resources.

[0034] To this end, an embodiment of the present disclosure provides a resource management method. In this method, based on an access request for a target resource sent by a user, the permission requirements corresponding to the target resource are obtained, and the permission requirements at least include the organization requirements to which the user belongs and the user's position requirements. The user's role information is determined, and the role information at least indicates the target organization to which the user belongs and the user's target position in the target organization. Based on the comparison result of the user's role information and the permission requirements, the user's access rights to the target resource are determined.

[0035] Through the above process, the refinement and flexibility of permission management in government collaboration scenarios are achieved. Through strict permission requirements and role information comparison, it is ensured that only users who meet specific conditions can access target resources. Specifically, by obtaining and comparing the user's organization and position information, it is possible to accurately determine whether the user meets the access permission requirements, thereby effectively preventing unauthorized access. At the same time, based on the dynamic comparison of role information and permission requirements, the system can automatically adjust user permissions to adapt to frequent personnel changes and improve management efficiency. In the end, this method not only improves data security, but also greatly reduces maintenance costs, and achieves high efficiency and reliability of permission management.

[0036] Figure 2 FIG. 2 shows an example process 200 of a resource management method according to some embodiments of the present disclosure. For ease of discussion, reference will be made to Figure 1 The process 200 is described in the context of FIG. The process 200 may be implemented in the electronic device 110. After receiving the access request of the user, the electronic device determines whether the user has the corresponding access authority through authority evaluation.

[0037] In block 201 , the electronic device 110 obtains the permission requirement corresponding to the target resource based on the access request of the target resource sent by the user, where the permission requirement at least includes the organization requirement to which the user belongs and the position requirement of the user.

[0038] The target resource may refer to specific data or applications that the user wants to access. The user may be a government official. After receiving the access request for the target resource sent by the user, the electronic device 110 may first obtain the permission requirements corresponding to the target resource, such as the organization requirements and the user position requirements corresponding to accessing the target resource.

[0039] The user's organization requirement can indicate that users who access the target resource must belong to a specific organization or department. For example, only staff members of the Education Bureau can access the data in the education system. The user's position requirement can indicate that users who access the target resource must be in a specific position. For example, only staff members above a certain position level in the Education Bureau can access certain specific data.

[0040] In block 202, the electronic device 110 determines the role information of the user, which at least indicates the target organization to which the user belongs and the target position of the user in the target organization. The role information may indicate the identity of the user, and the role information may at least include the target organization to which the user belongs and the position of the user.

[0041] For example, the target organization to which the user belongs may indicate the specific department or unit to which the user belongs. For example, a user belongs to the Education Bureau of XX City. The position of the user may indicate the specific position of the user in the organization. For example, a user is the director of the Education Bureau of XX City, or a grassroots government official of the Marriage Registration Office of XX District.

[0042] The user's role information can be information uploaded by the user during the registration process, information changed by an administrator after the user joins the company or changes positions, or information recorded in a user data system within a government organization, etc.

[0043] In block 203, the electronic device 110 determines the user's access rights to the target resource based on the comparison result of the user's role information and the permission requirement. The electronic device 110 compares the user's role information with the permission requirement. The comparison process may include organization matching and position matching. If all are matched successfully, the user's access rights to the target resource can be determined. On the contrary, if any one of them cannot be matched, the access rights are revoked.

[0044] Exemplarily, organization matching may include checking whether the organization to which the user belongs meets the organization requirements of the target resource. For example, whether the user belongs to a department that is authorized to access. Position matching may include checking whether the user's position meets the position requirements of the target resource. Based on the comparison result, the electronic device 110 determines whether to grant the user access rights to the target resource. If the user's role information fully meets the permission requirements, the access right is granted, otherwise the access request is denied. The access rights may include at least one of read-only permission, read-write permission, and delete permission.

[0045] Through the above process, the relationship between the organization and position to which the user belongs is established, and the organization and position are set as the basic role. The electronic device 110 is based on the role rather than the user in the process of determining the access rights. In other words, when a government official is transferred to a new position, as the role information corresponding to the government official changes, the government official will not be able to access the access rights corresponding to the old position, but will have the access rights corresponding to the new position. Similarly, when the organization of the government official changes, the access rights will also change automatically.

[0046] By clearly matching permission requirements with role information, the fine-grained management problem of resource access control is effectively solved, ensuring that only users who meet specific conditions can access sensitive resources. The shortcomings of traditional methods in frequent permission changes and complex management are solved, and the complexity of manual review and management is reduced by automatically matching permission requirements with role information.

[0047] The electronic device 110 determines that the user obtains access rights in response to the target organization to which the user belongs being included in the scope of the user's organization requirements and the position level corresponding to the user's target position in the target organization is not lower than the position level corresponding to the user's position requirements.

[0048] Figure 3 A schematic diagram of a resource management method principle 300 according to some embodiments of the present disclosure is shown. For government personnel 140, it is necessary to determine basic attributes 310 related to the government personnel 140. The basic attributes 310 include associations 312 between organizations and positions. The construction of the basic attributes 310 and the allocation of access control policies can be completed by the administrator 340 or by using a machine learning model trained with relevant samples.

[0049] For example, d1 to d n It can be represented as an organizational entity, such as the government functional departments such as the Civil Affairs Bureau and the Finance Bureau. D can represent the set of all organizational entities, D = {d1, d2, ..., d n}, d i ∈D.

[0050] t1 to t n It can be represented as the position of the government official 140, such as director, director, section officer, etc. T can represent the set of all positions, T = {t1, t2, ..., t n}, t i ∈T.

[0051] Since the target resource access request sent is a government official (user), the association 311 of government officials, organizations, and positions can also be constructed. For example, a government official can be represented as u. The entity organization to which government official u belongs can be represented as ud, and the position corresponding to government official u can be represented as ut.

[0052] The access policy corresponding to the association 311 of government officials, organizations, and positions is the organization- and position-based access control policy 321 in the access control policy 320. The core of the organization- and position-based access control policy 321 is the triple (p, d, t) consisting of authority, organization, and position. The triple represents the organizational requirements and position requirements that must be met to have authority p, that is, only government official u whose organization is d and whose position level is at least t has authority p.

[0053] For example, if user A's organization is the Education Bureau of XX City, and the scope of the authority requirement is all the Education Bureau units in XX City, then user A's organization meets the requirement. If user A's position in the Education Bureau is director, and the position requirement corresponding to the target resource is director, then user A meets both the user's organization requirement and the user's position requirement. Then user A will be granted access to the target resource. On the contrary, if user A fails to meet one of the requirements, for example, user A's position in the Education Bureau is a clerk, or user A does not belong to the Education Bureau, then it can be determined that user A does not meet the conditions and will not be granted access to the target resource.

[0054] Through the above process, unauthorized access is effectively prevented based on a strict organization and position level matching mechanism, thereby achieving access control for resources that need to be protected.

[0055] For government collaboration scenarios that are mainly based on territorial management and supplemented by vertical management. Local governments at all levels are fully responsible for local management. On the one hand, governments at all levels are divided according to administrative regions, and local functional departments need to accept the management of local governments at the same level. On the other hand, some functional departments (such as customs and finance) need to accept the business function management of the corresponding functional departments at the superior level. Therefore, government collaboration scenarios present the characteristics of multiple management. Taking the county education bureau as an example, it needs to accept the management of the municipal education bureau and obey the management of the county government. Therefore, government collaboration scenarios usually operate in a multi-department joint governance mode with one department co-ordinating and several relevant departments participating.

[0056] The territorial management organizational form from the central government to the local government naturally forms a standard tree-shaped organizational structure. Different organizational entities have access rights to corresponding data resources. However, in the scenario of multi-department co-governance, a certain organizational entity also needs access rights to corresponding data resources from other organizational entities based on government needs. In addition, government officials usually belong to only one department organization and have a fixed position. Government officials are usually users who need to access resources, and access control to resources ultimately needs to be implemented by government officials. There are employees in the same position within or between organizational entities.

[0057] Based on the above facts and current situation, the target organization to which the user belongs can be determined using the standard organizational structure, thereby determining the access rights to the target resource. In some embodiments, determining the organization to which the user belongs includes: obtaining the organizational entity to which the user belongs. According to the organizational entity mapping rule, the organizational entity is mapped to a node in the standard organizational structure, the node indicates an organization in the standard organizational structure, and the organization corresponding to the node is used as the target organization to which the user belongs.

[0058] The standard organizational structure can correspond to abstracting a large number of organizational entities into an abstract hierarchical tree consisting of dozens of nodes. Figure 4 A schematic diagram of the principle of an organizational entity mapping rule 400 according to some embodiments of the present disclosure is shown. The organizational entity mapping rule can be a rule for mapping an organizational entity to a standard organizational structure based on factors such as function, hierarchy, and scope of responsibility. For example, the organizational entity 1 corresponding to user A is a department of the XX City Education Bureau, and the actual organizational entity 2 corresponding to user B is a department of the XX City Education Commission.

[0059] By using the organizational entity mapping rules, organizational entity 1 and organizational entity 2 are mapped to corresponding nodes in the standard organizational structure based on the functions and levels corresponding to organizational entity 1 and the functions and levels corresponding to organizational entity 2. For example, the mapping results of organizational entity 1 and organizational entity 2 are both the XX municipal education department nodes in the standard organizational structure.

[0060] Through the above process, different organizational entities can be mapped to corresponding nodes in the standard organizational structure. Figure 3 As shown, a standard organizational structure 313 in the basic attributes 310 can be determined. That is, even if the organizational entities are different, the standard organizational structure can unify their management, thereby improving the efficiency and accuracy of authority management.

[0061] The following is a detailed description of the process of performing mapping according to the organizational entity mapping rules. In some embodiments, the electronic device 110 first obtains a standard organizational structure, which includes multiple levels, each level includes at least one node, and the organizational level corresponding to the node at the upper level is higher than the organizational level corresponding to the node at the lower level. According to the organizational entity mapping rules, the organizational entity is mapped to the corresponding node in the standard organizational structure to obtain the target organization to which the user belongs.

[0062] The standard organizational structure usually includes multiple levels. The root node of the standard organizational structure is located at the top level, and the top level can be used as the highest level. Sorted from the top level, it can be the second level, the third level, and so on. The second level can be the second level, and the third level is the third level. Each level includes at least one node, and the node represents the organizational unit of the standard organizational structure. There is a hierarchical relationship between the nodes, and the level of the upper level node is higher than the lower level node. For example, the organization corresponding to the node in the top level can manage or lead the organization corresponding to the node in the second level. For example, the node in the top level can be a national department, the node in the second level can be a provincial department, the node in the third level can be a municipal department, the node in the fourth level can be a district department, and so on.

[0063] The organizational entity mapping rule maps the actual organizational entity to which the user belongs to the corresponding node in the standard organizational structure according to its function, level, and scope of responsibility. For example, if the organizational entity is a department of the XX Municipal Education Bureau, whose function is education and whose level is municipal, it can be mapped to the node corresponding to the municipal education department in the standard organizational structure and used as the target organization to which the user belongs.

[0064] Through the organizational entity mapping rules, the actual complex organizational structure is mapped to standardized organizational nodes based on factors such as functions, levels and scope of responsibilities. The purpose of this is to simplify the authority management process, ensure that the system can handle diverse organizational structures efficiently and flexibly, and provide a consistent management method.

[0065] As mentioned above, the permission requirements include at least the requirements of the organization to which the user belongs and the requirements of the user's position. In addition, the permission requirements may also include the hierarchical requirements corresponding to the organization to which the user belongs in the standard organizational structure. Based on this, the electronic device 110 determines the user's access rights by: obtaining the target level corresponding to the target organization to which the user belongs, and the target level indicates the level corresponding to the target organization to which the user belongs in the standard organizational structure. In response to the target level satisfying the hierarchical requirements, and the position level corresponding to the user's target position in the target organization is not lower than the position level corresponding to the user's position requirements, it is determined that the user obtains access rights.

[0066] Combination Figure 3As shown, after completing the mapping of the standard organizational structure, the access control policy 322 based on the standard organizational structure can be used to determine the access rights. The core of the access control policy 322 based on the standard organizational structure is a four-tuple (p, root, a, t) consisting of authority, root node, abstract level and position. The four-tuple represents the authority p and the conditions that must be met to have the authority p. Specifically, only the government personnel u whose position level is not lower than t and whose subordinate organizational entities are under the jurisdiction of the organization root and whose organizational entity level in the standard organizational structure is not lower than a has the authority p.

[0067] Through the previous mapping process, the target organization to which the user belongs has been determined as a node in the target hierarchy in the standard organizational structure. The hierarchy requirement is the minimum level standard required to access the target resource. If the user's target hierarchy meets or exceeds the hierarchy requirement, the next step of evaluation is continued; otherwise, the access request is denied.

[0068] Taking the user's target level meeting or exceeding the level requirements as an example, the user's target position in the target organization can be confirmed. The position level corresponding to the target position needs to meet the minimum position level specified in the user's position requirements. For example, if the user's position requirement is "director level", then the user's target position level must be equal to or higher than the director level. If the user's target level meets the level requirements, and the user's target position level is not lower than the position level corresponding to the user's position requirements, the electronic device 110 determines that the user can obtain access rights.

[0069] Through this dual verification mechanism based on target level and position level, the electronic device 110 can accurately determine the user's access rights. This not only ensures the strictness and security of access control, but also improves the efficiency of system management and avoids confusion in authority management caused by position changes or organizational adjustments.

[0070] The above embodiment describes the role of establishing a standard organizational structure from the perspective of determining the access rights of users. The role of establishing a standard organizational structure is described below from the perspective of the functional attribute requirements of the organization to which the user belongs. The creation of the functional attribute requirements of the organization to which the user belongs can be completed by the electronic device 110 or by other devices. Next, the creation of the functional attribute requirements of the organization to which the user belongs is completed by the electronic device 110 as an example.

[0071] In determining the access request scenario, the electronic device 110 may first determine the first-level requirement corresponding to the target resource, the first-level requirement indicating a given level in the standard organizational structure, the standard organizational structure including multiple levels, each level including at least one node, the node indicating an organization in the standard organizational structure. According to the organizational entity mapping rule, the node in the given level is mapped to at least one organizational entity to correspond to the organizational requirement of the user.

[0072] In the access request creation scenario, the electronic device 110 first determines the first level requirement corresponding to the target resource in the standard organizational structure. The first level requirement defines the lowest level that can access the target resource. For example, the target resource requires that the organization to which the user belongs is at least a municipal department in order to obtain access rights.

[0073] Based on the determined lowest level that can access the target resource, the organizational entity mapping rules mentioned in the above example are used to reversely map the nodes in the lowest level to at least one organizational entity. Exemplarily, take the target resource as a grassroots governance application as an example. The lowest level corresponding to the target resource is the district-township-street under XX City. Based on this, the execution mapping can be based on factors such as functions, levels, and scope of responsibilities, and authorization can be executed to government officials at all street levels under XX City. Alternatively, the lowest level corresponding to the target resource is XX District under XX, and the execution mapping can be based on factors such as functions, levels, and scope of responsibilities, and authorization can be executed to government officials in XX District under XX City.

[0074] Through the above process, unified management of permissions can be completed conveniently, and an efficient solution can be provided for batch configuration and recovery of permissions.

[0075] As mentioned above, the permission requirements include at least the requirements of the organization to which the user belongs and the requirements of the user's position. In addition, the permission requirements also include the functional attribute requirements of the organization to which the user belongs, and the functional attribute requirements indicate the geographical area requirements corresponding to the organization to which the user belongs, and the functional level requirements corresponding to the organization to which the user belongs. Based on this, the target geographical area and target functional level corresponding to the target organization to which the user belongs are determined, and the target geographical area and target functional level are part of the role information. In response to the target geographical area including the scope of the geographical area requirements, and the target functional level corresponding to the target organization to which the user belongs is not lower than the functional level corresponding to the functional level requirements, it is determined that the user obtains access rights.

[0076] Combination Figure 3 As shown, the functional attribute may correspond to the standard functional structure 314 in the basic attribute 310. The functional attribute may be in the form of a label. For example, the organizational entity may be divided according to its function, such as the Finance Bureau, the Civil Affairs Bureau, and so on. The Civil Affairs Bureau may divide the relevant subordinate functional organizations such as funeral, elderly care, and marriage according to different businesses. The District Civil Affairs Bureau needs to accept the business guidance of the Municipal Civil Affairs Bureau, but the District Government is its direct superior organization.

[0077] In the standard organizational structure, the Municipal Civil Affairs Bureau and the District Marriage Registration Office are not connected. Therefore, through the functional attributes, the vertical management system in the administrative management system can be realized. For example, the functional attribute of the Education Bureau is education-related. There is a corresponding level relationship between different functional attributes. For example, the level corresponding to the functional attribute of civil affairs is higher than the level corresponding to the functional attribute of marriage. The organization corresponding to the higher-level functional attribute can guide and manage the organization corresponding to the lower-level functional attribute.

[0078] In addition to levels, functional attributes also include geographical areas. Taking the Education Bureau as an example, the geographical area corresponding to the XX City Education Bureau is XX City, and the geographical area corresponding to the XXX District Education Bureau is XX District. If XXX District is located in XX City, then the XX City Education Bureau can supervise and guide the XXX District Education Bureau.

[0079] The access control policy corresponding to the functional attribute can be an access control policy based on intelligence. The core of the access control policy based on intelligence is a triple (p, r, l) consisting of authority, geographical location, and functional level. The triple represents the authority p and the conditions required to have authority p. This policy shows that government official u must meet two conditions before he can have authority p. One of the conditions is that the corresponding geographical area of ​​the organization to which government official u belongs covers the minimum geographical area corresponding to r. For example, if the minimum geographical area corresponding to r is a certain city (such as the Municipal Health Bureau), then if the corresponding geographical area of ​​the organization to which government official u belongs (such as the Provincial Health Department) covers a certain city, then the condition is met. In other words, if the target geographical area corresponding to the target organization to which the user belongs includes the range required by the geographical area, then the condition is met. The second condition is that the functional level corresponding to the organization to which government official u belongs meets or is above functional level l. For example, functional level l is marriage (such as the marriage registration office), if the corresponding functional level of the organization to which government official u belongs (such as the Civil Affairs Bureau) is higher than marriage, then the condition is met.

[0080] That is, if the target geographical area corresponding to the target organization to which the user belongs meets the geographical area requirement, and the target functional level corresponding to the target organization to which the user belongs is not lower than the functional level corresponding to the functional level requirement, the electronic device 110 can determine that the user obtains access rights.

[0081] The permission requirement may also include a user identity attribute requirement. The access permission determination process based on the identity attribute requirement may include: obtaining a user identity attribute of the user, the user identity attribute being part of the role information. In response to the user identity attribute satisfying the user identity attribute requirement, determining that the user obtains the access permission.

[0082] User identity attribute requirements may include job titles, certification qualifications, professional skills, etc. The electronic device 110 needs to verify whether the user's identity attributes meet the identity attribute requirements for resource access. For example, some resources may only be open to users with specific titles or certification qualifications. Taking the medical system as an example, some advanced medical resources are only open to users with the title of "attending physician", while general medical resources are also open to users with the title of "resident physician". When the user's title is upgraded from resident physician to attending physician, he or she can automatically obtain permission to access advanced medical resources. When the user's identity attributes meet the identity attribute requirements, the electronic device 110 can determine that the user obtains access rights. By verifying the user's identity attributes, the accuracy of permission granting is ensured.

[0083] Figure 5 A schematic structural block diagram of a resource management device 500 according to some embodiments of the present disclosure is shown. Each module / component in the device 500 may be implemented by hardware, software, firmware or any combination thereof.

[0084] As shown in the figure, the device 500 includes a permission requirement acquisition module 501, which is configured to acquire the permission requirements corresponding to the target resource based on the access request of the target resource sent by the user, and the permission requirements at least include the requirements of the organization to which the user belongs and the requirements of the user's position. A role information determination module 502 is configured to determine the role information of the user, and the role information at least indicates the target organization to which the user belongs and the target position of the user in the target organization. An access permission determination module 503 is configured to determine the user's access rights to the target resource based on the comparison result of the user's role information and the permission requirements.

[0085] In some embodiments of the present disclosure, the access permission determination module 503 may be specifically configured to: determine that the user obtains access permission in response to the target organization to which the user belongs being included in the scope required by the organization to which the user belongs, and the position level corresponding to the target position of the user in the target organization is not lower than the position level corresponding to the user's position requirements.

[0086] In some embodiments of the present disclosure, the role information determination module 502 may be specifically configured to: obtain the organizational entity to which the user belongs, map the organizational entity to a node in the standard organizational structure according to the organizational entity mapping rule, the node indicates an organization in the standard organizational structure, and use the organization corresponding to the node as the target organization to which the user belongs.

[0087] In some embodiments of the present disclosure, the role information determination module 502 may also be specifically configured to: obtain a standard organizational structure, the standard organizational structure includes multiple levels, each level includes at least one node, and the organizational level corresponding to the node at the upper level is higher than the organizational level corresponding to the node at the lower level. According to the organizational entity mapping rule, the organizational entity is mapped to the corresponding node in the standard organizational structure to obtain the target organization to which the user belongs.

[0088] In some embodiments of the present disclosure, the permission requirements also include the hierarchical requirements of the organization to which the user belongs in the standard organizational structure, so the access permission determination module 503 can be specifically configured to: obtain the target hierarchical level corresponding to the target organization to which the user belongs, and the target hierarchical level indicates the hierarchical level corresponding to the target organization to which the user belongs in the standard organizational structure. In response to the target hierarchical level meeting the hierarchical requirements, and the position level corresponding to the target position of the user in the target organization is not lower than the position level corresponding to the user's position requirements, it is determined that the user obtains access permissions.

[0089] In some embodiments of the present disclosure, a permission requirement creation module may be further included, which may be configured to: determine the first-level requirements corresponding to the target resource, the first-level requirements indicating a given level in the standard organizational structure, the standard organizational structure including multiple levels, each level including at least one node, the node indicating an organization in the standard organizational structure. According to the organizational entity mapping rule, the node in the given level is mapped to at least one organizational entity to correspond to the organizational requirements of the user.

[0090] In some embodiments of the present disclosure, the permission requirement also includes the functional attribute requirement of the organization to which the user belongs, and the functional attribute requirement indicates the geographical area requirement corresponding to the organization to which the user belongs, and the functional level requirement corresponding to the organization to which the user belongs. Thus, the access permission determination module 503 can be specifically configured to: determine the target geographical area and target functional level corresponding to the target organization to which the user belongs, and the target geographical area and target functional level are part of the role information. In response to the target geographical area including the scope of the geographical area requirement, and the target functional level corresponding to the target organization to which the user belongs is not lower than the functional level corresponding to the functional level requirement, it is determined that the user obtains access permission.

[0091] In some embodiments of the present disclosure, the permission requirement also includes a user identity attribute requirement. Therefore, the access permission determination module 503 can be specifically configured to: obtain a user identity attribute of the user, the user identity attribute being part of the role information. In response to the user identity attribute being included in the scope of the user identity attribute requirement, determine that the user obtains access permission.

[0092] Figure 6 1 shows a block diagram of an electronic device 600 in which one or more embodiments of the present disclosure may be implemented. It should be understood that Figure 6 The electronic device 600 shown is merely exemplary and should not constitute any limitation on the functionality and scope of the embodiments described herein. Figure 6 The electronic device 600 shown may include or be implemented as Figure 1 electronic device 110, or Figure 5 Device 500.

[0093] like Figure 6 As shown, the electronic device 600 is in the form of a general electronic device. The components of the electronic device 600 may include, but are not limited to, one or more processors or processing units 610, a memory 620, a storage device 630, one or more communication units 640, one or more input devices 650, and one or more output devices 660. The processing unit 610 may be an actual or virtual processor and is capable of performing various processes according to a program stored in the memory 620. In a multi-processor system, multiple processing units execute computer executable instructions in parallel to improve the parallel processing capability of the electronic device 600.

[0094] The electronic device 600 typically includes a plurality of computer storage media. Such media may be any accessible media that is accessible to the electronic device 600, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 620 may be a volatile memory (e.g., registers, caches, random access memory (RAM)), a non-volatile memory (e.g., a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 630 may be a removable or non-removable medium, and may include a machine-readable medium, such as a flash drive, a disk, or any other medium, which may be capable of being used to store information and / or data and may be accessed within the electronic device 600.

[0095] The electronic device 600 may further include additional removable / non-removable, volatile / non-volatile storage media. Figure 6 As shown in , a disk drive for reading or writing from a removable, non-volatile disk (e.g., a "floppy disk") and an optical drive for reading or writing from a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to the bus (not shown) by one or more data media interfaces. The memory 620 may include a computer program product 625 having one or more program modules that are configured to perform various methods or actions of various embodiments of the present disclosure.

[0096] The communication unit 640 implements communication with other electronic devices through a communication medium. Additionally, the functions of the components of the electronic device 600 can be implemented with a single computing cluster or multiple computing machines that can communicate through a communication connection. Therefore, the electronic device 600 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.

[0097] The input device 650 may be one or more input devices, such as a mouse, a keyboard, a tracking ball, etc. The output device 660 may be one or more output devices, such as a display, a speaker, a printer, etc. The electronic device 600 may also communicate with one or more external devices (not shown) through the communication unit 640 as needed, such as a storage device, a display device, etc., communicate with one or more devices that allow a user to interact with the electronic device 600, or communicate with any device that allows the electronic device 600 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).

[0098] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.

[0099] According to an exemplary implementation of the present disclosure, a computer program product or a computer program is provided, the computer program product or the computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes Figure 2 The methods provided in the various optional methods are therefore not described in detail here.

[0100] Various aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of the methods, devices, equipment, and computer program products implemented according to the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer-readable program instructions.

[0101] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0102] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable data processing apparatus, or other device implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0103] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple implementations of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of a module, program segment or instruction includes one or more executable instructions for realizing the logical function of the specification. In some implementations as replacements, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse 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 realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.

[0104] The above descriptions of various implementations of the present disclosure are exemplary, non-exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described implementations. The selection of terms used herein is intended to best explain the principles of the implementations, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the various implementations disclosed herein.

Claims

1. A resource management method, comprising: Based on the access request of the target resource sent by the user, obtaining the permission requirement corresponding to the target resource, wherein the permission requirement at least includes the organization requirement to which the user belongs and the position requirement of the user; Determine role information of the user, where the role information at least indicates a target organization to which the user belongs and a target position of the user in the target organization; Based on the comparison result of the role information of the user and the permission requirement, the access permission of the user to the target resource is determined.

2. The method according to claim 1, wherein determining the access rights of the user to the target resource comprises: In response to the target organization to which the user belongs being included in the scope required by the organization to which the user belongs and the position level corresponding to the target position of the user in the target organization is not lower than the position level corresponding to the user position requirement, it is determined that the user obtains the access permission.

3. The method according to claim 1, wherein determining the target organization to which the user belongs comprises: Obtaining the organizational entity to which the user belongs; as well as According to the organizational entity mapping rule, the organizational entity is mapped to a node in the standard organizational structure, the node indicates an organization in the standard organizational structure, and the organization corresponding to the node is used as the target organization to which the user belongs.

4. The method according to claim 3, wherein mapping the organizational entity comprises: Acquire a standard organizational structure, wherein the standard organizational structure includes multiple levels, each level includes at least one node, and the organizational level corresponding to the node at the upper level is higher than the organizational level corresponding to the node at the lower level; as well as According to the organizational entity mapping rule, the organizational entity is mapped to a corresponding node in the standard organizational structure to obtain the target organization to which the user belongs.

5. The method according to claim 1, wherein the permission requirement further includes a hierarchical requirement corresponding to the organization to which the user belongs in a standard organizational structure, and determining the user's access rights to the target resource includes: Acquire a target level corresponding to the target organization to which the user belongs, where the target level indicates a level corresponding to the target organization to which the user belongs in the standard organizational structure; as well as In response to the target level satisfying the level requirement and the position level corresponding to the target position of the user in the target organization is not lower than the position level corresponding to the user position requirement, it is determined that the user obtains the access permission.

6. The method according to claim 1, wherein the user's organization requirement is created by: Determining a first level requirement corresponding to the target resource, the first level requirement indicating a given level in a standard organizational structure, the standard organizational structure comprising a plurality of levels, each level comprising at least one node, the node indicating an organization in the standard organizational structure; and According to the organization entity mapping rule, the nodes in the given level are mapped to at least one organization entity to correspond to the organization to which the user belongs.

7. The method according to claim 1, wherein the permission requirement further includes a functional attribute requirement of the organization to which the user belongs, the functional attribute requirement indicating a geographical area requirement corresponding to the organization to which the user belongs, and a functional level requirement corresponding to the organization to which the user belongs; And determining the access rights of the user to the target resource includes: Determine a target geographical area and a target functional level corresponding to a target organization to which the user belongs, wherein the target geographical area and the target functional level are part of the role information; and In response to the target geographical area including the range of the geographical area requirement, and the target functional level corresponding to the target organization to which the user belongs is not lower than the functional level corresponding to the functional level requirement, it is determined that the user obtains the access permission.

8. The method according to claim 1, wherein the permission requirement further includes a user identity attribute requirement, and determining the user's access rights to the target resource comprises: Acquire a user identity attribute of the user, where the user identity attribute is a part of the role information; as well as In response to the user identity attribute being included in a range of the user identity attribute requirement, it is determined that the user obtains the access right.

9. A resource management device, comprising: The permission requirement acquisition module is configured to acquire the permission requirement corresponding to the target resource based on the access request of the target resource sent by the user, and the permission requirement at least includes the user's organization requirement and the user's position requirement; A role information determination module, configured to determine the role information of the user, the role information at least indicating a target organization to which the user belongs and a target position of the user in the target organization; The access permission determination module is configured to determine the user's access permission to the target resource based on a comparison result between the user's role information and the permission requirement.

10. An electronic device comprising: at least one processing unit; as well as At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to any one of claims 1 to 8 when executed by the at least one processing unit.

11. A computer-readable storage medium having a computer program stored thereon, wherein the computer program can be executed by a processor to implement the method according to any one of claims 1 to 8.

12. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the method according to any one of claims 1 to 8 is implemented.

Citation Information

Cited By

  • User authority management method and device and storage medium

    CN121256821A