CN108009422B

CN108009422B - Multi-domain division method and system based on multi-level user grouping management

Info

Publication number: CN108009422B
Application number: CN201711097388.1A
Authority: CN
Inventors: 张凌; 张帆
Original assignee: South China University of Technology SCUT
Current assignee: South China University of Technology SCUT
Priority date: 2017-11-09
Filing date: 2017-11-09
Publication date: 2020-05-22
Anticipated expiration: 2037-11-09
Also published as: CN108009422A

Abstract

The invention discloses a multi-domain division method and a system based on multi-level user grouping management, wherein the method comprises the following steps: constructing a multi-level user grouping management model according to the actual organization structure relationship of the users; performing multi-user domain division on the basis of packet management; assigning a domain administrator to each user domain; and filtering the user query according to the user domain division result, and limiting the management range of the domain administrator. The invention can fit the actual user management model, simplify the user management, and is beneficial to realizing the virtualization of a single system into a plurality of independent user systems on the basis of multi-domain division, thereby realizing the simple and efficient management of the users of the enterprise-level system.

Description

Multi-domain division method and system based on multi-level user grouping management

Technical Field

The invention relates to the technical field of user management, in particular to a multi-domain division method and a multi-domain division system based on multi-level user grouping management.

Background

In recent decades, with the development of network technology, the popularity of information technology has become higher and higher, and the network not only provides a convenient and cheap way for information sharing, but also changes the life style of people. Because the network has the characteristics of convenient resource sharing, simple access mode and the like, more and more online platform systems appear, and simultaneously, tens of thousands of users also have great challenge to the user management of the online platform systems.

In combination with the user organization mode in real life, the user management modes of the conventional online system are roughly as follows: the method is divided into a user group management mode and a user label management mode according to the organization mode of users; the management is classified into multi-layer management and single-layer management (flat management) according to the hierarchical depth of the management. The different user management modes have respective characteristics and use scenes and have respective disadvantages.

Efficient and flexible enterprise user management is particularly important for enterprise-level systems. Therefore, a new management method integrating the advantages of multiple user management methods is urgently needed. The management method can maintain the actual hierarchical relationship of the enterprise users and effectively reduce the maintenance cost caused by the complex user structure. On the other hand, the filtering display of the user structure is realized through a multi-domain division method, and on the basis, a single system can be virtualized into a plurality of independently managed systems by combining other modules of the system, such as authority, storage and the like. Based on the consideration of the requirements, the invention provides a management scheme of user domains.

Disclosure of Invention

The invention aims to overcome the defects of the prior art, provides a multi-domain division method and a multi-domain division system based on multi-level user grouping management, and realizes simple and efficient management of users of an enterprise-level system.

In order to achieve the purpose, the technical scheme provided by the invention comprises the following steps:

a multi-domain division method based on multi-level user grouping management comprises the following steps:

1) establishing a multi-level user organization relationship according to the managed user organization structure, namely establishing a multi-level user organization structure, which comprises dividing different organizations and groups and maintaining the relationships among the organizations, the groups and the groups, and specifically comprises the following steps:

analyzing the actual user structure required to be managed by a system user, and dividing users according to the potential purpose and requirement of user management;

dividing users based on a common grouping management mode, realizing a multi-level grouping structure in an organization nesting mode, and establishing corresponding organizations from a high level to a bottom level one by one according to the level relation of the organization and the department where the users are located;

creating a specific user group in the organization or creating a next-level organization;

merging users according to the groups where the users actually are, wherein the users in the groups do not have grades and orders, and in addition, one-to-many user-group relationship is supported;

the user refers to each specific user, the user group refers to a set of users, the user groups cannot be nested in the user groups, the organizations refer to sets of the user groups, nesting relations can exist among the organizations, and the organizations can contain a plurality of sub-organizations and also can contain a plurality of user groups, but cannot contain specific users;

2) on the basis of the established multi-level user organization structure, multi-domain division of users is carried out according to management needs, namely user domains are determined, and the method specifically comprises the following steps:

defining a user management mode and specific requirements, determining a hierarchical structure of a user domain to be set, and determining a nested domain relation in the user domain;

on the basis of the established multi-level user organization structure, positioning nodes needing to set up a user domain and setting the nodes into the user domain, wherein the process of dividing the user domain does not relate to the setting sequence problem of nested user domains;

the division of the user domain depends on the organization node, the user domain can only be set on the organization node, and the division of the user domain can not be carried out on the user group node or the user node;

the granularity of user domain division is determined by a system user according to management requirements, and the method does not limit the division granularity;

wherein the user domain refers to a logical partition with certain visibility rules for a user hierarchy, comprising:

the same multi-level user organization structure can set up a plurality of different user domains at different organization nodes, and the user domains can have a flat or nested relationship;

only one user domain can be set up by the same organization node;

if the user domain does not contain the nested user domain, all the users contained in the whole user domain are visible mutually;

users are not visible between user domains in a same level or non-nested relationship;

if one or more nested subdomains are contained in the user domain, users directly belonging to the domain are mutually visible, users not directly belonging to the domain are visible to the users directly belonging to the domain, and users directly belonging to a parent domain are not visible to the subdomain users;

3) selecting a user in the user domain as a manager of the user domain, specifically as follows:

acquiring all member users in the user domain, and selecting one or more administrators to be responsible for managing the user domain among the users, wherein the selected administrators must directly belong to the current user domain, and no other limitation is imposed on the selection method of the administrators.

A multi-domain partitioning system based on multi-level user grouping management, comprising:

the user management unit is used for creating and deleting the system users and maintaining the user information, wherein a system administrator is responsible for creating the users, and the users are responsible for maintaining the basic information;

the user organization structure management unit is used for managing the user organization structure in the visible range, including the operations of adding, deleting and modifying the nodes of the organization structure and the group structure, and managing the members of the group in the visible range;

the domain management unit is used for creating a new domain, modifying the information of the existing domain and deleting the domain in the visible range;

the domain administrator configuration unit is used for managing role authorization, role recovery and administrator inquiry of each domain administrator;

and the user query filtering unit is used for filtering the return information according to the domain of the operation user and the visible rule when the user structure is queried, and is also responsible for judging the relationship and the visibility among multiple users.

Compared with the prior art, the invention has the following advantages and beneficial effects:

1. the user management model provided by the invention supports a multi-level and multi-branch user organization architecture, and has the characteristics of flexible configuration and strong practicability.

2. The organization structure based on the grouping management makes the user management hierarchy clear, and simultaneously, batch user operation can be conveniently carried out.

3. A domain management mode is added on the basis of grouping management, so that the hierarchical depth of management is effectively reduced, the maintenance cost is reduced, and the efficiency is improved.

4. The action object of the invention is mainly an online system which takes an enterprise-level system as a representative and has distinct hierarchical user organization structure characteristics, and the online system is fit with the structure of enterprise user organization and meets the requirements of practical application.

Drawings

Fig. 1 is a schematic diagram of system constituent elements and interrelations between the elements involved in the present embodiment.

Fig. 2 is a schematic diagram of user role classification related to the user management module in this embodiment.

Fig. 3 is a schematic diagram of module division of the user management related function in the present embodiment.

Fig. 4 is a schematic structural diagram of an organization based on multi-level user grouping management provided in this embodiment.

Fig. 5 is a flowchart illustrating providing different management functions for users with different roles in this embodiment.

Fig. 6 is a schematic diagram of a node creation flow based on multi-level user grouping management according to this embodiment.

Fig. 7 is a schematic diagram of a user management process in a user group based on multi-level user grouping management according to this embodiment.

Fig. 8 is a schematic flowchart of the domain to which the user query belongs and acquiring other user organizational structures within the visible range according to this embodiment.

Detailed Description

The invention will be further described with reference to the following examples.

Fig. 1 is a schematic diagram of system constituent elements and interrelations between the elements involved in the present embodiment. As shown in fig. 1, the system of the present embodiment includes five components: organization 101, user group(s) 102, user 103, domain 104, and domain administrator 105. The organization is a set formed by a plurality of user groups or sub-organizations, and the organization can be nested to form a multi-level structure. The whole multi-level user structure exists in a tree structure, and the organization serves as a branch structure in the user tree. Meanwhile, an organization may contain groups of users, but the organization cannot directly contain users; a user group (group) is a collection of multiple users. The user groups act as leaf structures in the user tree and as carriers for specific users. The user group only contains one or more users and cannot contain other elements; users, i.e. ordinary system users, each user may belong to one or more user groups at the same time or not belong to any user group; the domain refers to a logical division with certain visibility rules for a user hierarchy, and the organization and the sub-structure are set into one domain on the basis of a certain organization; an administrator is an administrator within a domain and selects one or more users from the domain to act as administrators for the domain.

Fig. 2 is a schematic diagram of user role classification related to a user management module in this embodiment, and as shown in the right diagram, user roles in the system are mainly classified into four categories: system administrators, domain administrators, other administrators, and general users.

The system administrator 201 is an initial administrator of the entire system, and is responsible for basic work such as configuration of an initial user structure of the system, user domain division, and domain management allocation to each domain. In addition, the system administrator has the highest management capability for other modules.

When the system is started for the first time, the system automatically creates an initial system administrator according to the configuration file, and creates other users or administrators through the account of the system administrator. The system administrator may be independent of any user organization, i.e. does not need to join any user group.

The domain administrator 202 is an administrator within each domain, assigned by a system administrator, and must belong to the domain being managed, to a member of one or more groups within the domain. The domain administrator has administrative rights to the organizational structure within the domain.

Other administrators 203 refer to administrator roles within the system that are not relevant to user management. These administrators are used for other modules within the system and are not described in detail.

Ordinary users 204 refer to legitimate users within the system that do not have any administrator role. The ordinary users can use the service functions provided by the system, but do not have the capability of the system. All ordinary users can obtain the role of the administrator through a legal way, and the role is called the administrator.

Fig. 3 is a schematic diagram of module division of the user management related function in the present embodiment. The system comprises: a user management module 301, a user organization structure management module 302, a domain management module 303, a domain administrator configuration management module 304, a user query filtering module 305, and other functional modules 306.

The user management module is mainly responsible for basic user management functions, including functions of user creation, modification and deletion, user login authentication, user information inquiry and the like. This module provides the most basic user management behavior capability for the system.

The user organization structure management module is used for carrying out grouping management on the discrete users of the system on the basis of basic user management. The module can establish the organization structure of users in the system and bind the users into a designated group for unified management.

The domain management module and the domain administrator configuration management module are used for realizing multi-domain management. The domain management module can create a designated user domain on the basis of the system organization structure, and a domain administrator configures the management module to assign a corresponding administrator to the domain to take charge of the user management in the domain.

The user query filtering module is used for general user organization structure query. For all legal users of the system, the user structure of the user can be checked after logging in the system. The user query filtering module filters a user structure which can be seen by the current user according to the user group to which the user belongs and the domain configured in the system, and returns the filtered query result to the user.

The other function module refers to a function module other than the user management.

Fig. 4 is a schematic structural diagram of an organization based on multi-level user grouping management provided in this embodiment. As shown in fig. 4, the user organization structure may be divided into a plurality of hierarchies and a plurality of organizations according to the rules of the enterprise staff position level, the department relationship, and the like. The user tree structure includes: root tissue 401; organization, such as rectangular structure 402, structure 403, structure 404 in FIG. 4; user groups, such as

oval structures

405, 406, 407 in fig. 4. Meanwhile, each user may belong to one or more user groups. The personnel organizational structure of the whole enterprise can be used by a system administrator at the beginning of the system, a rough user structure framework is built, the whole user organizational structure is divided into domains, a corresponding domain administrator is arranged for each domain, and the domain administrator manages users of the managed domains more carefully.

In this embodiment, the domain administrator sets the structure 402 as a domain, and the domain name is the same as the organization name; the structure 403 is then set to the nested subdomains, with the domain name being the same as the organization name. Thus, all of the sub-structures contained by structure 402 may be merged in the development domain, while all of the sub-structures contained by structure 403 may be merged in the product line A domain. Wherein, because the product line A domain is used as the sub-domain of the research and development part domain, for the users in the product line A domain, the product line A domain is used as the direct domain, and the research and development part domain is used as the upper indirect domain.

Therefore, the invention provides a management mode for user domain division and intra-domain autonomy. The mode has the advantages that the system administrator is not responsible for the management of all users of the whole system any more, but responsible for the division of the rough system organization structure, and issues the divided management authority to each domain administrator, so that the management depth and difficulty of the system administrator are greatly reduced.

Fig. 5 is a flowchart illustrating providing different management functions for users with different roles in this embodiment. All system users log in the system through a uniform system entrance. And the user with the administrator role can enter the corresponding management interface through the management end entrance on the system interface. Judging whether the user has the role of a system administrator through the step 501, and after the judgment is successful, the system administrator can set a basic user structure in the step 502 to construct the user structure in the whole system from the beginning; in step 503, the user domains may be divided, and the system user structure may be subdivided into a plurality of user domains for management according to the management requirement; in step 504, a corresponding domain administrator may be assigned to each user, and the administrative authority in the domain may be issued to the domain administrator. Whether the user has the role of a domain administrator is judged through the step 505, and after the judgment is successful, the domain administrator can manage the user structure in a more detailed way within the management range of the domain administrator in the step 506; the sub-domain division may continue and a sub-domain administrator may be assigned at step 507. After a common user, instead of an administrator, logs in the system, the user structure and other related users to which the user belongs can be obtained according to the division of the user structure by the administrator, and the system is used in combination with other functions of the system on the basis.

The above-mentioned user structure in the whole system is built from nothing to nothing, and the domain administrator can manage the user structure more finely in its management scope, including on the basis of the existing user directory structure or on the root directory structure initialized by the system, creating the required organization structure, creating the user group and adding members to the user group. The creation user organization must establish a lower level organization at an existing organization node or a root node, and all organizations must take an existing organization structure as a parent structure and cannot create discrete organization nodes apart from the existing organization structure. Similarly, the created user group also has to take the existing organization structure as the parent structure, meanwhile, the user groups cannot be nested, so the user groups at the lower level can be created only under the organization node. Fig. 6 is a schematic diagram of a node creation flow based on multi-level user grouping management according to this embodiment. As shown in fig. 6, after logging in the system, a user having administrator authority, whether a system administrator or a domain administrator, enters the management interface, and can see a visible user structure of the current user, where the user structure serves as a visible management scope of the current operator. Within this visibility management scope, the administrator can create a new user organization or group of users.

When the administrator needs to create a new organization or group of users, step 601, it needs to first select an existing node as the parent organization of the new organization or group of users, step 602, it needs to confirm that the parent node must be the node of the organization type, and then, step 603, it creates the needed new organization or group of users.

When all the user organization structures are constructed, discrete users in the system need to be associated to corresponding user groups. This process may be understood as a user joining one or more groups of users. This process also requires administrator participation, and fig. 7 is a schematic diagram of a user management flow in a user group based on multi-level user grouping management provided by this embodiment. After entering the management interface, the administrator can manage the user groups in the management range, including: in step 701, a user group to be managed is selected, and in step 702, users are added to the user group, one or more users in the group are removed, and information of the users in the group is edited and modified.

The foregoing is a detailed description of the basic principles and general flow of user management by system administrators and domain administrators. The goal of user management is to build a multi-level group management user organization structure for user structure queries and user relationship queries that occur at various times within the system.

When a legal user logs in the system, the user structure of the legal user in the system needs to be obtained, and the user structure and other users with certain association are obtained. The above-mentioned user structure and other users with certain association include: department relationships on enterprise personnel relationships, department relationships on workflows, social relationships, and the like. After the user obtains the relevant user structure and the user, other functions of the system can be conveniently used, such as: sharing function to realize communication in the system.

Fig. 8 is a schematic flowchart of the domain to which the user query belongs and acquiring other user organizational structures within the visible range according to this embodiment. In step 801, after a valid user logs into the system, the user enters a user organization relationship viewing module. In step 802, the system searches for the user group where the user is located according to the ID information of the current user. In step 803, the system traverses each user group, searches from the user group to the upper structure, and determines whether each upper organization is defined as a domain, and in step 804, finds the first organization defined as a domain, and takes the domain as the domain to which the user belongs. In step 805, the system returns all the organizational structures contained in the domain and the user to the current user.

The above-mentioned embodiments are merely preferred embodiments of the present invention, and the scope of the present invention is not limited thereto, so that the changes in the shape and principle of the present invention should be covered within the protection scope of the present invention.

Claims

1. A multi-domain division method based on multi-level user grouping management is characterized by comprising the following steps:

the organization refers to the set of the user groups, nesting relations can exist among the organizations, and the organization can contain a plurality of sub-organizations and also can contain a plurality of user groups, but can not contain specific users;

the granularity of the user domain division is determined by a system user according to the management requirement;

wherein the user domain refers to a logical partition with visibility rules for a user hierarchy, comprising:

the same multi-level user organization structure can set a plurality of different user domains at different organization nodes, and the user domains can have a flat or nested relationship;

only one user domain can be set up by the same organization node;

acquiring all member users in the user domain, and selecting one or more administrators to be responsible for managing the user domain, wherein the selected administrators must directly belong to the current user domain.