Multi-level user access control system and method based on dynamic permission matrix
By combining the dynamic permission matrix generation module and the role management module, the problems of rigid hierarchical permissions and insufficient dynamic adaptability in traditional access control systems are solved. The automatic generation and real-time response of the permission matrix are realized, ensuring the integrity and security of the permission inheritance chain, supporting fine-grained permission allocation, and improving system response speed and security.
Patent Information
- Application Number
- CN202610181826.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-02-09
- Publication Date
- 2026-05-15
AI Technical Summary
Traditional access control systems suffer from rigid hierarchical permissions, insufficient dynamic adaptability, lack of multi-dimensional correlation, and real-time bottlenecks when dealing with complex organizational structures, resulting in redundant permission configurations, high maintenance costs, and increased security risks.
A multi-level user access control system based on a dynamic permission matrix is adopted. The permission management module defines many-to-many relationships between users, user groups, and roles, generates a dynamic permission matrix using a tree-like hierarchical structure, supports recursive inheritance of user group hierarchical relationships, and binds resource categories and operation types through the role management module to realize permission combination units.
It enables automatic generation and real-time response of permission matrices, reduces the need for manual configuration, ensures the integrity of permission inheritance chains, avoids permission conflicts, supports fine-grained permission allocation, and improves response speed and security in high-concurrency scenarios.
Smart Images

Figure CN122053157A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data processing technology, and in particular to a multi-level user access control system and method based on a dynamic permission matrix. Background Technology
[0002] While role mapping can simplify permission allocation in traditional access control systems, it still has significant drawbacks in practical applications: Rigid hierarchical permissions: Existing systems typically require explicit definition of permission inheritance rules for each level when handling user group structures. When organizational structures become more complex (such as multi-level departments in large enterprises), a large number of inheritance strategies need to be manually configured, resulting in high configuration redundancy and a significant increase in maintenance costs.
[0003] Insufficient dynamic adaptability: Permission changes require manual synchronization at each level, which can easily lead to incomplete permission coverage or conflicts (for example, when a subsidiary inherits permissions from the headquarters, there may be unauthorized or missing permissions).
[0004] The lack of multi-dimensional connections: the many-to-many relationship between users, user groups, and roles is decoupled from the organizational structure. Virtual groups (such as cross-departmental project groups) are difficult to bind dynamic permissions quickly, requiring the copying of permission templates, which violates the "principle of least privilege" and increases security risks.
[0005] Real-time bottleneck: The generation of the permission matrix relies on static pre-computation. When user group levels or role bindings change frequently, the system needs to completely reconstruct the permission table, and the response delay significantly affects the efficiency of large-scale systems.
[0006] Application content This application proposes a multi-level user access control system and method based on a dynamic permission matrix, aiming to at least partially solve one of the technical problems in related technologies.
[0007] On one hand, embodiments of this application provide a multi-level user access control system based on a dynamic permission matrix, the system comprising: The permission management module is used to respond to the first configuration operation of the target object, define the many-to-many relationship between users, user groups, and roles, and the user group hierarchy includes a tree-like hierarchical structure, where the permissions of a lower-level user group are a subset of the permissions of a higher-level user group. The dynamic permission matrix generation module is used to generate a dynamic permission matrix by recursively inheriting the user group hierarchy and role binding results; The user group management module is used to configure a many-to-many mapping relationship between users and user groups in response to a second configuration operation of the target object, and to associate user groups with organizational structure entities or virtual groups. The role management module is used to bind roles with resource categories and operation types to form permission combination units, with each role representing a set of permissions.
[0008] In some embodiments, when the permission management module defines many-to-many relationships between users, user groups, and roles in response to a first configuration operation of the target object, it specifically performs the following operations: The user groups are included downwards using a tree-like hierarchical structure, and then roles are assigned based on the many-to-many relationship between user groups and roles. Downward inclusion includes at least one of the following operations: Inherit a subset of roles from the parent user group by the child user group; Sub-user groups inherit all roles from their parent user groups and can assign additional roles to their sub-user groups.
[0009] In some embodiments, when the dynamic permission matrix generation module generates a dynamic permission matrix by recursively inheriting the user group hierarchy and role binding results, it specifically performs the following operations: Get all user groups to which the target user belongs, and then recursively get the role set of all parent user groups; The target user's directly bound role is merged with the user group inherited role obtained through the role set to obtain the target role set; When a target user is configured to perform a role revocation operation, the revoked role is removed from the target role set; A dynamic permission matrix for the target roles is generated based on the resource categories and operation types bound to each role in the target role set.
[0010] In some embodiments, the second configuration operation includes a user configuration operation and a user group configuration operation. When the user group management module configures the many-to-many mapping relationship between users and user groups in response to the second configuration operation of the target object, it is specifically used to perform the following operations: In response to user configuration operations, configure the initial mapping relationship of the user groups assigned to each user; In this case, each user is assigned to at least one user group; In response to user group configuration operations, configure the hierarchical second mapping relationship between various user groups; Each user group can be configured with at most one parent user group.
[0011] In some embodiments, when the role management module binds roles with resource categories and operation types to form permission combination units, it is specifically used to perform the following operations: Operation permissions are formed based on a combination of resource category and operation type; Among them, in operation permissions, operation type is configured based on access mode, and resource category is the access object of operation type. Resource category includes page function and process resource category. Assigning operation permissions to roles creates a permission combination unit for each role.
[0012] In some embodiments, the system further includes: The security service module is used to invoke and execute security services, which include authentication, real-time permission verification, data security filtering, and third-party system user identity conversion functions.
[0013] In some embodiments, the system further includes: The metadata storage module is used to store security metadata, including user passwords, role-resource mapping relationships, and user group hierarchy relationships.
[0014] On the other hand, embodiments of this application provide a multi-level user access control method based on a dynamic permission matrix, applied to the aforementioned multi-level user access control system based on a dynamic permission matrix. The method includes the following steps: The permission management module responds to the first configuration operation of the target object, defining many-to-many relationships between users, user groups, and roles. The user group hierarchy includes a tree-like hierarchical structure, where the permissions of a lower-level user group are a subset of the permissions of its parent user group. The dynamic permission matrix generation module generates a dynamic permission matrix by recursively inheriting the user group hierarchy and role binding results. The user group management module responds to the second configuration operation of the target object, configures the many-to-many mapping relationship between users and user groups, and associates user groups with organizational structure entities or virtual groups. The role management module binds roles with resource categories and operation types to form permission combination units, with each role representing a set of permissions.
[0015] In some embodiments, the method further includes the following steps: The security service module calls and executes security services, which include authentication, real-time permission verification, data security filtering, and third-party system user identity conversion functions.
[0016] In some embodiments, the method further includes the following steps: Security metadata is stored through a metadata storage module. This security metadata includes user passwords, role-resource mapping relationships, and user group hierarchy relationships.
[0017] On the other hand, embodiments of this application provide an electronic device, including: a processor and a memory; the memory is used to store a program; the processor executes the program to implement the above method.
[0018] On the other hand, embodiments of this application provide a computer storage medium storing a processor-executable program, which, when executed by a processor, is used to implement the above-described method.
[0019] The embodiments of this application include at least the following beneficial effects: This application provides a multi-level user access control system, method, electronic device, storage medium, and program product based on a dynamic permission matrix. This solution, through a permission management module responding to a first configuration operation of a target object, defines a many-to-many relationship between users, user groups, and roles. The user group hierarchy includes a tree-like hierarchical structure, where the permissions of lower-level user groups are subsets of the permissions of higher-level user groups. A dynamic permission matrix generation module generates a dynamic permission matrix by recursively inheriting the binding results of the user group hierarchy and roles. A user group management module, responding to a second configuration operation of the target object, configures a many-to-many mapping relationship between users and user groups, and associates user groups with organizational structure entities or virtual groups. A role management module binds roles with resource categories and operation types to form permission combination units, with each role representing a set of permissions. This application's embodiments automatically generate a permission matrix by recursively inheriting the user group hierarchy, eliminating the need for manual step-by-step configuration. Furthermore, the dynamic permission matrix responds in real-time to changes in user group topology (such as departmental restructuring) and role binding operations, ensuring the integrity of the permission inheritance chain and avoiding permission conflicts or security vulnerabilities caused by omissions in traditional solutions. In addition, this application simultaneously associates user groups with entity organizations (such as the finance department) and virtual groups (such as temporary audit groups), supporting fine-grained permission allocation through role-resource category-operation type binding combinations, satisfying the principle of least privilege. The dynamic matrix generation module based on a recursive algorithm only incrementally updates affected permission nodes (such as when modifying a user group's role binding), significantly reducing the time complexity of permission calculations and significantly improving response speed in high-concurrency scenarios compared to a full reconstruction solution. Attached Figure Description
[0020] The accompanying drawings are used to provide a further understanding of the technical solutions of this application and constitute a part of the specification. They are used together with the embodiments of this application to explain the technical solutions of this application and do not constitute a limitation on the technical solutions of this application.
[0021] Figure 1 A schematic diagram illustrating the module composition of a multi-level user access control system based on a dynamic permission matrix provided in an embodiment of this application; Figure 2 A schematic diagram of the overall conceptual model of access control provided in the embodiments of this application; Figure 3 A schematic diagram illustrating the composition architecture of the operation permissions provided in the embodiments of this application; Figure 4A schematic diagram illustrating the relationship between roles and operations provided in the embodiments of this application; Figure 5 A schematic diagram illustrating the compositional architecture of resource categories provided in embodiments of this application; Figure 6 A schematic diagram of the overall architecture of data center access control provided in this application embodiment; Figure 7 A schematic diagram illustrating an example architecture of the core object model provided in the embodiments of this application; Figure 8 A schematic diagram of the permission ER provided in the embodiments of this application; Figure 9 A flowchart illustrating a multi-level user access control method based on a dynamic permission matrix, provided in an embodiment of this application; Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation
[0022] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit it. In the following description, when referring to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this application; they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this application as detailed in the appended claims.
[0023] It is understood that the terms “first,” “second,” etc., used in this application may be used herein to describe various concepts, but unless otherwise stated, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another. For example, without departing from the scope of the embodiments of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the words “if,” “when,” or “in response to a determination” as used herein may be interpreted as “when…” or “when…” or “in response to a determination.”
[0024] As used in this application, the terms "at least one", "multiple", "each", "any", etc., "at least one" includes one, two or more, "multiple" includes two or more, "each" refers to each of the corresponding multiples, and "any" refers to any one of the multiples.
[0025] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.
[0026] In related technologies, although traditional access control systems can simplify permission allocation through role mapping, they still have significant drawbacks in practical applications: rigid hierarchical permissions, insufficient dynamic adaptability, lack of multi-dimensional association, and real-time bottlenecks.
[0027] In view of this, this application provides a multi-level user access control system, method, electronic device, storage medium, and program product based on a dynamic permission matrix. This solution, through a permission management module responding to a first configuration operation of a target object, defines a many-to-many relationship between users, user groups, and roles. The user group hierarchy includes a tree-like hierarchical structure, where the permissions of lower-level user groups are subsets of the permissions of higher-level user groups. A dynamic permission matrix generation module generates a dynamic permission matrix by recursively inheriting the binding results of the user group hierarchy and roles. A user group management module, responding to a second configuration operation of the target object, configures the many-to-many mapping relationship between users and user groups, and associates user groups with organizational structure entities or virtual groups. A role management module binds roles with resource categories and operation types to form permission combination units, with each role representing a set of permissions. This application's embodiments automatically generate a permission matrix by recursively inheriting the user group hierarchy, eliminating the need for manual step-by-step configuration. Furthermore, the dynamic permission matrix responds in real-time to changes in user group topology (such as departmental restructuring) and role binding operations, ensuring the integrity of the permission inheritance chain and avoiding permission conflicts or security vulnerabilities caused by omissions in traditional solutions. In addition, this application simultaneously associates user groups with entity organizations (such as the finance department) and virtual groups (such as temporary audit groups), supporting fine-grained permission allocation through role-resource category-operation type binding combinations, satisfying the principle of least privilege. The dynamic matrix generation module based on a recursive algorithm only incrementally updates affected permission nodes (such as when modifying a user group's role binding), significantly reducing the time complexity of permission calculations and significantly improving response speed in high-concurrency scenarios compared to a full reconstruction solution.
[0028] It should also be noted that the embodiments of this application can be applied to integrated information systems. Specifically, an integrated information system is a shared data and application platform for the entire organization, and openness and sharing are essential characteristics. Therefore, the security of the data center is even more crucial. Effective access control of the data center is necessary to achieve both openness and security. This application belongs to the field of information security technology, specifically relating to a multi-level user access control system based on a dynamic permission matrix, suitable for access control of information systems with complex organizational structures (such as government agencies, public institutions, and enterprise groups).
[0029] On the one hand, such as Figure 1 As shown in the figure, this application provides a multi-level user access control system 100 based on a dynamic permission matrix, which may include: The permission management module 110 is used to respond to the first configuration operation of the target object, define the many-to-many relationship between users, user groups, and roles, and the user group hierarchy includes a tree-like hierarchical structure, where the permissions of a lower-level user group are a subset of the permissions of a higher-level user group. The dynamic permission matrix generation module 120 is used to generate a dynamic permission matrix by recursively inheriting the user group hierarchy and role binding results; User group management module 130 is used to configure a many-to-many mapping relationship between users and user groups in response to a second configuration operation of the target object, and to associate user groups with organizational structure entities or virtual groups. The role management module 140 is used to bind roles with resource categories and operation types to form permission combination units, with each role representing a set of permissions; It should be noted that, in some embodiments, when the permission management module defines the many-to-many relationship between users, user groups, and roles in response to the first configuration operation of the target object, it is specifically used to perform the following operations: using a tree-like hierarchical structure to include user groups downwards, and then assigning roles through the many-to-many relationship between user groups and roles; wherein, including downwards includes at least one of the following operations: inheriting a subset of roles from the parent user group through the lower-level user group; inheriting all roles from the parent user group through the lower-level user group, and assigning additional roles to the lower-level user group.
[0030] For example, in some specific implementations, the permission management module is used to define users, user groups, roles, and their relationships, supporting a tree-like user group structure (the permissions of lower-level groups are subsets of those of higher-level groups). A user group can have multiple roles, and a role can be assigned to multiple user groups (a many-to-many relationship). The roles held by a user group are downward-inclusive, meaning that the roles held by a lower-level user group can only be a subset of those held by its parent group. Another allocation method is upward inheritance, where a lower-level user group can inherit all roles from its parent group and can acquire additional roles. This application embodiment uses a downward-inclusive approach for a unified overview, which is more intuitive and easier to understand. A tree-like user group structure generally corresponds to an enterprise's organizational structure, and in an enterprise's organizational structure, higher levels generally have more power; therefore, using a downward-inclusive approach is reasonable.
[0031] Furthermore, it's important to note that assigning roles to each user is primarily accomplished by assigning roles to user groups. Once a role is assigned to a group, it is effectively granted to all users within that group. System administrators cannot assign additional roles to users that are not already in their user group, but they are allowed to revoke some of the roles a user already possesses. Upon logging into the data center, the system automatically combines all of a user's permissions, allowing the user to easily access all applications they are authorized to use within the system.
[0032] It should be noted that, in some embodiments, when the dynamic permission matrix generation module generates a dynamic permission matrix by recursively inheriting the user group hierarchy and the binding results of roles, it is specifically used to perform the following operations: obtain all user groups to which the target user belongs, and then recursively obtain the role sets of all parent user groups; merge the directly bound roles of the target user with the user group inherited roles obtained through the role sets to obtain the target role set; when the target user is configured with a role revocation operation, remove the revoked role from the target role set; generate a dynamic permission matrix for the target role based on the resource category and operation type bound to each role in the target role set.
[0033] For example, in some specific implementations, the dynamic permission matrix generation module generates a dynamic permission matrix by calculating user permissions in real time and combining user group hierarchy relationships and role assignments. Specifically, the overall conceptual model of permission control is as follows: Figure 2 As shown: 1) Create a data center user account for each user in the data center for management and auditing purposes.
[0034] 2) Create several user groups. Hierarchical relationships can be defined between groups, but each user group can have at most one parent group. All users are assigned to these user groups. A user can be assigned to multiple user groups, forming a many-to-many relationship between users and user groups.
[0035] 3) Classify resources and establish hierarchical relationships, defining the types of operations for each resource category. Work with business users to determine which resources require value constraints and how to impose those constraints.
[0036] 4) Establish several roles and define the permissions (resources + operations) for each role, including database permissions, OLAP permissions, tool permissions, application permissions, and administrative permissions. Each role represents a permission combination, so the number of different roles should correspond to the number of different permission combinations.
[0037] 5) Assign roles to each user group. A user group can have multiple roles, and a role can be assigned to multiple user groups (many-to-many relationship). Roles held by a user group are subordinate to roles; that is, a lower-level user group can only possess a subset of the roles held by its parent user group. One assignment method is upward inheritance, where a lower-level user group can inherit all roles from its parent user group and can acquire additional roles. We believe that the downward inclusion method is more intuitive and easier to understand. The tree-like structure of user groups generally corresponds to the organizational structure of a company, and in a typical organizational structure, higher levels generally possess more power; therefore, the downward inclusion method is reasonable.
[0038] 6) Assign roles to each user. This process is primarily accomplished by assigning roles to user groups. Once a role is assigned to a group, it is effectively granted to all users within that group. System administrators cannot assign additional roles to users that are not already in their user group, but they are allowed to revoke some of the roles a user already possesses. Upon logging into the data center, the system automatically combines all of a user's permissions, allowing the user to easily access all applications they are authorized to use within the system.
[0039] In a comprehensive information system, user permissions are actually determined by roles; a role represents a set of permissions. Because of this, users of specific products (such as databases) cannot be directly mapped to data center users, but they can be mapped to roles. Considering these factors, we should establish a one-to-one correspondence between a user from each product and a data center role after each data center role is created. This way, whenever a user submits a service request to the data service layer, the data service layer can log in to the specific product using the product user and password corresponding to the user's current role, thus achieving identity transfer. It is crucial to note that the mapping between roles and specific product users, as well as user passwords, will be stored in the data center's security metadata for the data service layer's use. To ensure the security of these usernames and passwords, the relevant metadata tables storing this data are only accessible to the data service layer and are subject to strict encryption measures.
[0040] It should be noted that the second configuration operation includes user configuration operation and user group configuration operation. In some embodiments, when the user group management module configures the many-to-many mapping relationship between users and user groups in response to the second configuration operation of the target object, it is specifically used to perform the following operations: in response to the user configuration operation, configure the first mapping relationship of the user group assigned to each user; wherein, a user is assigned to at least one user group; in response to the user group configuration operation, configure the second mapping relationship between the upper and lower levels of each user group; wherein, a user group is configured with at most one upper-level user group.
[0041] For example, in some implementations, the user group management module supports many-to-many user-user group relationships, where user groups can be mapped to organizational structures (such as departments or positions) or virtual groups. Specifically, several user groups can be created, and hierarchical relationships can be defined between groups, but a user group can have at most one parent group. All users are assigned to these user groups. A user can be assigned to multiple user groups, forming a many-to-many relationship between users and user groups.
[0042] It should be noted that, in some embodiments, when the role management module binds roles with resource categories and operation types to form permission combination units, it is specifically used to perform the following operations: forming operation permissions based on the combination of resource categories and operation types; wherein, in the operation permissions, the operation type is configured based on the access mode, the resource category is the access object of the operation type, and the resource category includes page functions and process resource categories; and assigning operation permissions to roles as permission combination units for the corresponding roles.
[0043] For example, in some specific implementations, the role management module is implemented by binding roles with permissions (resource category + operation), with each role representing a combination of permissions (such as database permissions, workflow approval permissions). Specifically, this can be achieved as follows: 1. Each unit, department, and position has a corresponding user group, but the user group is not necessarily one of these units, departments, or positions; it could also be a virtual group. 2. When assigning user roles, user groups can be expanded indefinitely. No matter how many subjects are added, they will all eventually be mapped to the roles table, becoming multiple roles. Then, access control is assigned to these roles.
[0044] 3. For example Figure 3 As shown, operation permission = access mode + resource (resource class). Here, it can be considered as an "access object," a resource (resource class) controlled by the permission. Let's assume there's a "run" mode within the access modes. The combination of these two constitutes a valid operation (permission), which is then assigned to the role.
[0045] 4. For example Figure 4 As shown, based on resources and access patterns, there are many operations involved, which are essentially permissions. Therefore, we simply need to assign these permissions to roles. No matter how many objects there are, they are eventually broken down into multiple resource categories (just like subjects, each subject is broken down into multiple roles), and then combined with access patterns to form operations (permissions), which are finally assigned to roles.
[0046] The system's resource categories can be divided into two directions: page functions and process resource categories. These categories are designed as follows: Figure 5 As shown, the functional module table stores either "process" or "page function". The "functional module category" is used to distinguish whether this record is a "page function" or a "process". If a process has multiple approval operations, they are all placed in the resource category.
[0047] It should be noted that in some embodiments, the system may further include a security service module, which is used to call and execute security services, including authentication, real-time permission verification, data security filtering, and third-party system user identity conversion functions.
[0048] For example, in some specific implementations, the security service module is used to provide authentication, permission verification, security filtering, and third-party system user identity conversion functions. Specifically, the security service module can implement the third-party system identity conversion through the following logic: a) Based on the user's currently active role, extract the corresponding encrypted account credentials from the metadata storage module; b) Obtain the real credentials through the decryption engine and pass them to a third-party system; c) Perform security filtering on data returned by third-party systems according to the permission matrix.
[0049] It should be noted that in some embodiments, the system may further include: a metadata storage module for storing security metadata, including user passwords, role-resource mapping relationships, and user group hierarchy relationships.
[0050] For example, in some specific implementations, the metadata storage module is used to store security metadata such as user passwords (encrypted), role-resource mappings, and user group hierarchical relationships. Specifically, in the metadata storage module: user passwords can be stored using asymmetric encryption, with only the security service module having decryption permissions; role-resource mapping relationships can be stored using a triplet of role ID, resource category ID, and opcode; and user group hierarchical relationships can be stored using a parent-child node linked list structure.
[0051] To explain in detail the principles of the technical solution of this application, the overall process of this application will be described below with reference to some specific embodiments. It is easy to understand that the following is an explanation of the technical principles of this application and should not be regarded as a limitation of this application.
[0052] First, it should be noted that traditional access control technologies (such as role-based access control, RBAC) face the following problems in multi-level organizational structures: rigid permission allocation: static role permissions are difficult to adapt to dynamically changing organizational structures and resource needs; insufficient hierarchical control: unclear permission inheritance logic between user groups can easily lead to permission redundancy or vulnerabilities; coarse resource granularity: it is difficult to achieve fine-grained control of resource instances (such as page buttons and process nodes); and difficulty in integrating with third-party systems: it is impossible to uniformly manage permission allocation and identity mapping of heterogeneous systems.
[0053] The embodiments of this application aim to solve the above-mentioned problems by achieving precise, flexible, and secure access control through a dynamic permission matrix and multi-level user group design. Specifically, this system consists of the following core modules: (1) Permission Management Module: Defines users, user groups, roles and their relationships, and supports a tree-like user group structure (the permissions of the lower-level group are a subset of the permissions of the upper-level group).
[0054] like Figure 6 The diagram shown illustrates the overall architecture of data center access control proposed in this application. The main body of access control is the integrated information system users, including system administrators and business users; the object of access control is the controlled object, including controlled objects of third-party products. In this system, access control mainly consists of four parts: security metadata, security services, access control system, and third-party products. Among them: 1. Security Metadata: Stores all metadata information related to security control, including users, user groups, roles, product users, the mapping relationship between roles and product users, the association between roles and each controlled object, etc.
[0055] 2. Security Services: Security control components deployed on data center application servers. Provides authentication, secure access interfaces, security management interfaces, identity conversion logic from data center users to third-party product users, security filtering control logic, etc.
[0056] 3. Access Control System: A self-developed, unified access control tool, which allows system administrators to define, maintain, and assign permissions to users, user groups, and roles.
[0057] 4. Third-party products: The allocation of permissions for internal product resources is completed by the system administrator through the management tools provided by the product. Ideally, the product's permission allocation should be integrated into a data access control system for unified management, but this requires that the product provide a programming interface for access control, and that the granularity of the product's resource permission allocation meets the requirements of a data center.
[0058] User access to the integrated information system involves direct login to the data center. Users must provide a username and password, and authentication is completed through access to security metadata within the security services. All data center security metadata needs to store user information other than the password; therefore, the user password must be stored within the security metadata.
[0059] (2) Dynamic permission matrix generation module: calculates user permissions in real time and generates a dynamic permission matrix by combining user group hierarchy and role allocation.
[0060] like Figure 2 The figure shown is an overall conceptual model of access control provided in the embodiments of this application: 1) Create a data center user account for each user in the data center for management and auditing purposes.
[0061] 2) Create several user groups. Hierarchical relationships can be defined between groups, but each user group can have at most one parent group. All users are assigned to these user groups. A user can be assigned to multiple user groups, forming a many-to-many relationship between users and user groups.
[0062] 3) Classify resources and establish hierarchical relationships, defining the types of operations for each resource category. Work with business users to determine which resources require value constraints and how to impose those constraints.
[0063] 4) Establish several roles and define the permissions (resources + operations) for each role, including database permissions, OLAP permissions, tool permissions, application permissions, and administrative permissions. Each role represents a permission combination, so the number of different roles should correspond to the number of different permission combinations.
[0064] 5) Assign roles to each user group. A user group can have multiple roles, and a role can be assigned to multiple user groups (many-to-many relationship). Roles held by a user group are subordinate to roles; that is, a lower-level user group can only possess a subset of the roles held by its parent user group. One assignment method is upward inheritance, where a lower-level user group can inherit all roles from its parent user group and can acquire additional roles. We believe that the downward inclusion method is more intuitive and easier to understand. The tree-like structure of user groups generally corresponds to the organizational structure of a company, and in a typical organizational structure, higher levels generally possess more power; therefore, the downward inclusion method is reasonable.
[0065] 6) Assign roles to each user. This process is primarily accomplished by assigning roles to user groups. Once a role is assigned to a group, it is effectively granted to all users within that group. System administrators cannot assign additional roles to users that are not already in their user group, but they are allowed to revoke some of the roles a user already possesses. Upon logging into the data center, the system automatically combines all of a user's permissions, allowing the user to easily access all applications they are authorized to use within the system.
[0066] In a comprehensive information system, user permissions are actually determined by roles; a role represents a set of permissions. Because of this, users of specific products (such as databases) cannot be directly mapped to data center users, but they can be mapped to roles. Considering these factors, we should establish a one-to-one correspondence between a user from each product and a data center role after each data center role is created. This way, whenever a user submits a service request to the data service layer, the data service layer can log in to the specific product using the product user and password corresponding to the user's current role, thus achieving identity transfer. It is crucial to note that the mapping between roles and specific product users, as well as user passwords, will be stored in the data center's security metadata for the data service layer's use. To ensure the security of these usernames and passwords, the relevant metadata tables storing this data are only accessible to the data service layer and are subject to strict encryption measures.
[0067] (3) User group management module: Supports many-to-many user-user group relationships. User groups can be mapped to organizational structures (such as departments, positions) or virtual groups.
[0068] Based on the permission design principles of the RBAC (Role-Based Access Control) model, a core object model for the permission management system is established. For example... Figure 7 As shown, the basic elements included in the object model are: Users, Groups, Roles, Resource Classes, Access Modes, and Operators. The main relationships are: Permission Assignment (PA) and User Assignment (UA), described as follows: Controlled objects: These are the resources (Resource Classes) that the system needs to protect, and are objects that can be accessed. The following two issues need to be considered when defining resources: a) Resources have hierarchical and containment relationships. For example, a webpage is a resource, and objects such as buttons and text boxes on the webpage are also resources, which are child nodes of webpage nodes. If a button can be accessed, then the page must also be accessible.
[0069] (b) The resource concept mentioned here refers to a resource class, not a specific resource instance. Distinguishing between resource classes and resource instances, as well as the finer granularity of resources, helps define the management boundaries between the access control system and the application system. The access control system needs to manage permissions for resource classes, while the application system needs to manage permissions for specific resource instances.
[0070] Operations (Permissions): Complete the binding between resource categories and access policies.
[0071] User: The owner or subject of permissions. Users and permissions are separated and bound together through authorization management.
[0072] User group: A collection of users. In business logic, decisions can be made based on individual or group identity. The system downplays the concept of user groups, primarily focusing on individual user identities.
[0073] Role: The unit and carrier for assigning permissions. Roles support hierarchical permission implementation through inheritance. For example, the role of section chief can simultaneously hold the roles of section chief and different business personnel within the section.
[0074] Assign Role Permissions (PA): This implements the mapping of the relationship between operations and roles.
[0075] Assign User Roles (UAs): This implements the mapping of the relationship between users and roles.
[0076] In the system of this application embodiment, the access subjects are employees and user groups. For example... Figure 8 As shown, each entity has multiple roles. Each role may also belong to multiple entities simultaneously.
[0077] (4) Role Management Module: Roles are bound to permissions (resource category + operation), and each role represents a combination of permissions (such as database permissions, workflow approval permissions). Specifically, this can be implemented as follows: 1. Each unit, department, and position has a corresponding user group, but the user group is not necessarily one of these units, departments, or positions; it could also be a virtual group. 2. When assigning user roles, user groups can be expanded indefinitely. No matter how many subjects are added, they will all eventually be mapped to the roles table, becoming multiple roles. Then, access control is assigned to these roles.
[0078] 3. For example Figure 3 As shown, operation permission = access mode + resource (resource class). Here, it can be considered as an "access object," a resource (resource class) controlled by the permission. Let's assume there's a "run" mode within the access modes. The combination of these two constitutes a valid operation (permission), which is then assigned to the role.
[0079] 4. For example Figure 4 As shown, based on resources and access patterns, there are many operations involved, which are essentially permissions. Therefore, we simply need to assign these permissions to roles. No matter how many objects there are, they are eventually broken down into multiple resource categories (just like subjects, each subject is broken down into multiple roles), and then combined with access patterns to form operations (permissions), which are finally assigned to roles.
[0080] The system's resource categories can be divided into two directions: page functions and process resource categories. These categories are designed as follows: Figure 5 As shown, the functional module table stores either "process" or "page function". The "functional module category" is used to distinguish whether this record is a "page function" or a "process". If a process has multiple approval operations, they are all placed in the resource category.
[0081] (5) Security Service Module: Provides identity verification, permission verification, security filtering and third-party system user identity conversion functions.
[0082] (6) Metadata storage module: Stores secure metadata such as user passwords (encrypted), role-resource mapping, and user group hierarchy.
[0083] In some specific application scenarios, the system based on the embodiments of this application can implement the following method flow: 1. Permission Modeling: Classify resources into categories such as page functions and process nodes, define resource hierarchy relationships (e.g., button → page → module); bind operations (e.g., "read", "edit", "delete") to each type of resource, forming a set of operation permissions.
[0084] 2. Dynamic permission calculation: When a user logs in, the permissions of the parent group are recursively inherited based on the user group and role to generate a dynamic permission matrix; the permission matrix is updated in real time to ensure that the user can only access the currently authorized resource instance.
[0085] 3. Third-party system integration: By mapping roles to users in third-party systems, unified management of cross-system permissions can be achieved (programming interfaces need to be provided by the third party).
[0086] 4. Security Audit: Record user operation logs and use the permission matrix to detect abnormal access behavior.
[0087] In summary, this application belongs to the field of information security technology, specifically relating to a multi-level user access control system based on a dynamic permission matrix, applicable to permission management of information systems with complex organizational structures (such as government agencies, public institutions, and enterprise groups). In view of the shortcomings of existing technologies, the embodiments of this application implement the following technical features: 1. Dynamic permission matrix: A permission matrix is generated in real time based on the hierarchical relationship of user groups and role allocation, supporting dynamic adjustment and precise control of permissions. 2. Multi-level user group inheritance mechanism: User group permissions are inclusive downwards (lower-level group permissions are subsets of higher-level permissions), matching the needs of tree-like organizational structures. 3. Fine-grained resource management: Distinguishing between resource classes and resource instances, enabling button-level and process node-level control. 4. Cross-system identity mapping: Solving the problem of unified permission management for heterogeneous systems by binding roles with users of third-party systems.
[0088] Based on the above technical features, compared with the prior art, this application includes at least the following beneficial effects: precise control: supports permission management from coarse-grained (module) to fine-grained (button); dynamic adaptability: the permission matrix is updated in real time to meet the needs of dynamic adjustment of organizational structure; enhanced security: encrypted storage of user credentials, restriction of metadata access permissions, and prevention of unauthorized operations; compatibility expansion: can be integrated with heterogeneous systems, reducing the complexity of permission management across multiple platforms.
[0089] On the other hand, embodiments of this application also provide a multi-level user access control method based on a dynamic permission matrix, referring to... Figure 9 , Figure 9 A flowchart of a multi-level user access control method based on a dynamic permission matrix applied to a terminal, provided in an embodiment of this application, is included. The method may include the following steps: S100: Respond to the first configuration operation of the target object through the permission management module, and define the many-to-many relationship between users, user groups, and roles; The user group hierarchy includes a tree-like hierarchical structure, where the permissions of lower-level user groups are a subset of the permissions of higher-level user groups. S200: The dynamic permission matrix generation module generates a dynamic permission matrix by recursively inheriting the user group hierarchy and role binding results. S300, through the user group management module, respond to the second configuration operation of the target object, configure the many-to-many mapping relationship between users and user groups, and associate the user group with the organizational structure entity or virtual group; S400: By using the role management module, roles are bound to resource categories and operation types to form permission combination units; Each role represents a set of permissions.
[0090] In some embodiments, the method may further include the following steps: The security service module calls and executes security services, which include authentication, real-time permission verification, data security filtering, and third-party system user identity conversion functions.
[0091] In some embodiments, the method may further include the following steps: Security metadata is stored through a metadata storage module. This security metadata includes user passwords, role-resource mapping relationships, and user group hierarchy relationships.
[0092] It should be noted that the content of the system embodiments in this application is applicable to the method embodiments in this application. The specific process steps implemented in the method embodiments in this application are the same as those in the above system embodiments, and the beneficial effects achieved are also the same as those achieved by the above systems. It should be understood that the functional logic implemented by the specific modules of each part of the above system embodiments all fall within the protection scope of the method embodiments in this application, and will not be described in detail here.
[0093] On the other hand, this application also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the above-described method. This electronic device can be any smart terminal, including tablet computers, in-vehicle computers, etc.
[0094] It is understood that the content of the above method embodiments is applicable to this device embodiment. The specific functions implemented by this device embodiment are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.
[0095] like Figure 10 As shown, Figure 10 This illustration shows a specific example of the hardware structure of an electronic device 1000 according to one embodiment. The electronic device 1000 includes: The processor 1001 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application. The memory 1002 can be implemented as a read-only memory (ROM), static storage device, dynamic storage device, or random access memory (RAM). The memory 1002 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1002 and is called and executed by the processor 1001 using the network node population optimization method of the embodiments of this application. Input / output interface 1003 is used to implement information input and output; The communication interface 1004 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.). Bus 1005 transmits information between various components of the device (e.g., processor 1001, memory 1002, input / output interface 1003, and communication interface 1004); The processor 1001, memory 1002, input / output interface 1003 and communication interface 1004 are connected to each other within the device via bus 1005.
[0096] The electronic device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.
[0097] The content of the method embodiments in this application is applicable to the embodiments of this electronic device. The specific functions implemented by the embodiments of this electronic device are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above methods.
[0098] Another aspect of this application provides a computer-readable storage medium storing a program that is executed by a processor to implement the aforementioned method.
[0099] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD to ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such transmitted data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.
[0100] The content of the method embodiments in this application is applicable to the computer-readable storage medium embodiments. The specific functions implemented by the computer-readable storage medium embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above methods.
[0101] This application also discloses a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device can read the computer instructions from the computer-readable storage medium and execute the computer instructions, causing the computer device to perform the aforementioned method.
[0102] The content of the method embodiments in this application is applicable to the computer program product or computer program embodiment. The specific functions implemented by the computer program product or computer program embodiment are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above methods.
[0103] This application provides a multi-level user access control system, method, electronic device, storage medium, and program product based on a dynamic permission matrix. The solution uses a permission management module to respond to a first configuration operation of a target object, defining a many-to-many relationship between users, user groups, and roles. The user group hierarchy includes a tree-like hierarchical structure, where the permissions of lower-level user groups are subsets of the permissions of higher-level user groups. A dynamic permission matrix generation module generates a dynamic permission matrix by recursively inheriting the binding results of the user group hierarchy and roles. A user group management module responds to a second configuration operation of the target object, configuring the many-to-many mapping relationship between users and user groups, and associating user groups with organizational structure entities or virtual groups. A role management module binds roles with resource categories and operation types to form permission combination units, with each role representing a set of permissions. This application's embodiments automatically generate a permission matrix by recursively inheriting the user group hierarchy, eliminating the need for manual step-by-step configuration. Furthermore, the dynamic permission matrix responds in real-time to changes in user group topology (such as departmental restructuring) and role binding operations, ensuring the integrity of the permission inheritance chain and avoiding permission conflicts or security vulnerabilities caused by omissions in traditional solutions. In addition, this application simultaneously associates user groups with entity organizations (such as the finance department) and virtual groups (such as temporary audit groups), supporting fine-grained permission allocation through role-resource category-operation type binding combinations, satisfying the principle of least privilege. The dynamic matrix generation module based on a recursive algorithm only incrementally updates affected permission nodes (such as when modifying a user group's role binding), significantly reducing the time complexity of permission calculations and significantly improving response speed in high-concurrency scenarios compared to a full reconstruction solution.
[0104] The embodiments described in this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.
[0105] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of this application, and may include more or fewer steps than shown, or combine certain steps, or different steps.
[0106] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.
[0107] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.
[0108] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0109] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.
[0110] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0111] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0112] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0113] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes multiple instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0114] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.
Claims
1. A multi-level user access control system based on a dynamic permission matrix, characterized in that, include: The permission management module is used to respond to the first configuration operation of the target object, define the many-to-many relationship between users, user groups, and roles, and the user group hierarchy includes a tree-like hierarchical structure, where the permissions of a lower-level user group are a subset of the permissions of a higher-level user group. The dynamic permission matrix generation module is used to generate a dynamic permission matrix by recursively inheriting the user group hierarchy relationship and the role binding result; The user group management module is used to configure a many-to-many mapping relationship between the user and the user group in response to a second configuration operation of the target object, and to associate the user group with an organizational structure entity or virtual group. The role management module is used to bind the roles with resource categories and operation types to form permission combination units, with each role representing a set of permissions.
2. The multi-level user access control system based on a dynamic permission matrix according to claim 1, characterized in that, When the permission management module responds to the first configuration operation of the target object and defines the many-to-many relationship between users, user groups, and roles, it is specifically used to perform the following operations: The user groups are included downwards using the tree-like hierarchical structure, and roles are assigned based on the many-to-many relationship between the user groups and the roles. The downward containment includes at least one of the following operations: Inherit a subset of roles from the parent user group by the child user group; The lower-level user group inherits all the roles of the upper-level user group, and additional roles are assigned to the lower-level user group.
3. The multi-level user access control system based on a dynamic permission matrix according to claim 1, characterized in that, When generating a dynamic permission matrix by recursively inheriting the user group hierarchy and the role binding results, the dynamic permission matrix generation module specifically performs the following operations: Obtain all the user groups to which the target user belongs, and then recursively obtain the role sets of all parent user groups; The target user's directly bound role is merged with the user group inherited role obtained through the role set to obtain the target role set; When the target user is configured to perform a role recycling operation, the recycled role is removed from the target role set; The dynamic permission matrix of the target role is generated based on the resource category and operation type bound to each role in the target role set.
4. The multi-level user access control system based on a dynamic permission matrix according to claim 1, characterized in that, The second configuration operation includes a user configuration operation and a user group configuration operation. When the user group management module configures the many-to-many mapping relationship between the user and the user group in response to the second configuration operation of the target object, it is specifically used to perform the following operations: In response to the user configuration operation, configure a first mapping relationship for the user group assigned to each user; In this case, one of the users is assigned to at least one of the user groups; In response to the user group configuration operation, configure the hierarchical second mapping relationship between each user group; Each user group can be configured with at most one parent user group.
5. The multi-level user access control system based on a dynamic permission matrix according to claim 1, characterized in that, When the role management module binds the role with resource category and operation type to form a permission combination unit, it is specifically used to perform the following operations: Operation permissions are formed based on the combination of the resource category and the operation type; In the operation permissions, the operation type is configured based on the access mode, and the resource category serves as the access object of the operation type. The resource category includes page functions and process resource categories. The operation permissions are assigned to the roles as the permission combination units for the corresponding roles.
6. The multi-level user access control system based on a dynamic permission matrix according to any one of claims 1 to 5, characterized in that, The system also includes: The security service module is used to invoke and execute security services, which include identity verification, real-time permission verification, data security filtering, and third-party system user identity conversion functions.
7. The multi-level user access control system based on a dynamic permission matrix according to claim 1, characterized in that, The system also includes: The metadata storage module is used to store security metadata, including user passwords, role-resource mapping relationships, and user group hierarchy relationships.
8. A multi-level user access control method based on a dynamic permission matrix, characterized in that, Applied to the multi-level user access control system based on a dynamic permission matrix as described in any one of claims 1 to 7, the method includes the following steps: The permission management module responds to the first configuration operation of the target object, defining many-to-many relationships between users, user groups, and roles. The user group hierarchy includes a tree-like hierarchical structure, where the permissions of a lower-level user group are a subset of the permissions of its parent user group. The dynamic permission matrix generation module generates a dynamic permission matrix by recursively inheriting the user group hierarchy and the role binding results. In response to a second configuration operation of the target object via the user group management module, the many-to-many mapping relationship between the user and the user group is configured, and the user group is associated with an organizational structure entity or virtual group. The role management module binds the roles with resource categories and operation types to form permission combination units, with each role representing a set of permissions.
9. An electronic device, characterized in that, Including the processor and memory; The memory is used to store programs; The processor executes the program to implement the method as described in claim 8.
10. A computer storage medium storing a processor-executable program, characterized in that, The processor-executable program, when executed by the processor, is used to implement the method as described in claim 8.
