User management system and method for realizing user management
By designing a user management system in the rail transit subway system, the unified management of user account information and permissions is realized, the cumbersome problems of multi-subsystem login and permission management are solved, seamless switching and real-time synchronization of user information is realized, and the Convenience and efficiency of management.
Patent Information
- Application Number
- CN202410960137.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-16
- Publication Date
- 2024-12-17
AI Technical Summary
In the rail transit subway system, users need to manage account information and permissions separately in multiple independent business subsystems, resulting in cumbersome and complex management. System administrators also need to manage them in each subsystem when empowerment and permission changes. If multiple operations are performed, there is risk of misoperation and difficulty in management.
Design a user management system, including a parent system and a subsystem. The parent system includes an account information management module, an account permission management module and a user management service module. The subsystem includes an account information registration and login interface module and an account information and permission type configuration module. Real-time communication and synchronization realize unified management of account information and permission types, avoiding repeated settings and management in each subsystem.
It realizes that users can manage account information and permissions in the parent system. Users can log in to other subsystems with relevant permissions with the same account, realize seamless switching and real-time synchronization between different subsystems, reducing the cumbersomeness of user information management. and differentiate, improve management convenience and efficiency.
Smart Images
Figure CN119150273A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of user management, and in particular to a user management system and a method for implementing user management thereof. Background Art
[0002] At present, rail transit business is increasing with development. The rail transit subway system includes business subsystems such as the integrated monitoring mother system and the emergency support system. However, since the mother system and each business subsystem are independent, when users use multiple business subsystems at the same time or cross-use, they find that the login process is very cumbersome. For system administrators, even if it is the same user, each system needs to manage its account information and account permission type separately. Moreover, user management is an important part of the internal management of rail transit operations, and its importance is self-evident. In the rail transit subway system, there will be many types of personnel operating. If all personnel have the same authority, there is a risk of misoperation.
[0003] For example, the same user must register an account and password in each system for logging in, but the user may not register all business subsystems at the same time, because some systems may not be used temporarily. However, when registering a new system later, the account and password may be different from the previous one due to various reasons. This means that when the user uses multiple business subsystems, he or she needs to record the account and password of each business subsystem separately.
[0004] For example, when a system administrator grants permissions to each user, he must perform the operation in all business subsystems separately, even if the permission type is the same, and he must go through the process multiple times. And when a user's permission type needs to be changed, it also needs to be changed multiple times in all business subsystems.
[0005] All of the above problems exist in reality and need to be solved urgently. Even the business subsystems carrying business modules are likely to continue to increase or expand in the future. If the relevant technical methods are still used, it will undoubtedly make things worse for both users and system administrators. Summary of the invention
[0006] The technical problem to be solved by the present invention is that, in view of at least one defect of the related technology mentioned in the above background technology: for the same user, each subsystem manages its account information and account authority type separately, and the login is cumbersome when using multiple subsystems, and the system administrator must also operate separately in each subsystem when performing authority management. A user management system and a method for implementing user management are provided.
[0007] The technical solution adopted by the present invention to solve the technical problem is: constructing a user management system, including a parent system and at least two subsystems;
[0008] The parent system includes:
[0009] An account information management module, the account information management module is used to store and manage the account information of the parent system and all the subsystems;
[0010] An account authority management module, the account authority management module is used to store and manage the authority types corresponding to the accounts of the parent system and all the subsystems; and
[0011] A user management service module, the user management service module is used to communicate with all the subsystems in real time, and control and schedule the account information management module and the account authority management module;
[0012] The subsystem includes:
[0013] The account information registration and login interface module is used to register and log in an account.
[0014] In some embodiments, the subsystem further comprises:
[0015] An account information and permission type configuration module, wherein the account information and permission type configuration module is used to synchronize information with the account information management module and the account permission management module.
[0016] In some embodiments, the parent system further comprises:
[0017] A communication interface module, wherein the communication interface module is used for connecting to an external application system.
[0018] The present invention also constructs a method for implementing user management using any of the above-mentioned user management systems, including an account registration step, which includes:
[0019] The account information registration and login interface module receives the account information for registration input by the user and sends it to the user management service module;
[0020] The user management service module controls and schedules the account information management module to perform comparison and verification;
[0021] After the comparison and verification process is completed, the user management service module sends the registration result to the account information registration and login interface module.
[0022] In some embodiments, when the subsystem further includes an account information and permission type configuration module, the account registration step further includes:
[0023] The user management service module synchronizes all account information in the account information management module to the account information and permission type configuration modules of all the subsystems.
[0024] The present invention also constructs a method for implementing user management using any of the user management systems described above, including a login step, which includes:
[0025] The account information registration and login interface module receives the account information input by the user for login and sends it to the user management service module;
[0026] The user management service module controls and schedules the account information management module to perform login verification;
[0027] After the verification process is completed, the user management service module sends the login result to the subsystem.
[0028] The present invention also constructs a method for implementing user management using any of the above-mentioned user management systems, including an account modification step, which includes:
[0029] After logging in through the subsystem, the user enters the account modification interface of the account information management module of the parent system;
[0030] The account modification interface receives and saves the modified account information;
[0031] The user management service module returns the account modification result to the subsystem.
[0032] The present invention also constructs a method for implementing user management using any of the user management systems described above, including a user authority configuration step, which includes:
[0033] After the account is registered, the account authority management module receives configuration instructions from the administrator to grant authority to the account.
[0034] In some embodiments, when the subsystem further includes an account information and permission type configuration module, the user permission configuration step further includes:
[0035] After the configuration is completed, the user management service module packages all account permission types in the account permission management module and synchronizes the account information and permission type configuration modules of all the subsystems.
[0036] The present invention also constructs a method for implementing user management in the user management system described in any one of the above, comprising an application expansion step:
[0037] The parent system communicates with the external application system through the communication interface module;
[0038] The parent system receives the request data packet sent by the external application system and parses it;
[0039] If the data format matches, verification is performed and the verification result is returned to the external application system;
[0040] The parent system sends the account information registration login interface module of the subsystem and the program installation package corresponding to the account information and permission type configuration module to the external application system;
[0041] After the external application system installs the program installation package, it generates the account information registration and login interface module and the account information and permission type configuration module;
[0042] The user management service module of the parent system communicates in real time with the account information registration and login interface module and the account information and permission type configuration module of the external application system.
[0043] By implementing the present invention, the following beneficial effects are achieved:
[0044] The present invention connects all subsystems to the parent system as a whole by making all subsystems communicate with each other, adding a user management service module, an account information management module and an account authority management module in the parent system, and adding an account information registration and login interface module in each subsystem at the same time. Account information and account authority management functions are no longer set in each subsystem, but all account information and account authority are unified in the parent system for unified management, thereby enabling users to log in to other subsystems with relevant authority based on the same account, thereby achieving seamless switching of user information between different subsystems, and achieving real-time synchronization and management and use of user information between different subsystems, avoiding the problems of cumbersome management of user information and information differences, greatly reducing the difficulty and cumbersomeness of user use, and also achieving the effect of automatic synchronization of each subsystem when account information is modified and account authority type is changed, and finally achieving comprehensive, efficient and convenient management of users. BRIEF DESCRIPTION OF THE DRAWINGS
[0045] The present invention will be further described below with reference to the accompanying drawings and embodiments, in which:
[0046] Figure 1 A logical structure diagram of a user management system according to an embodiment of the present invention is shown;
[0047] Figure 2 A flowchart showing an account registration step in a method for implementing user management by a user management system according to an embodiment of the present invention is shown;
[0048] Figure 3A flowchart showing a login step in a method for implementing user management in a user management system according to an embodiment of the present invention;
[0049] Figure 4 A flowchart showing an account modification step in a method for implementing user management by a user management system according to an embodiment of the present invention;
[0050] Figure 5 A flowchart showing the steps of configuring user rights in a method for implementing user management in a user management system according to an embodiment of the present invention;
[0051] Figure 6 A flow chart showing the application extension steps in a method for implementing user management in a user management system according to an embodiment of the present invention. DETAILED DESCRIPTION
[0052] In order to have a clearer understanding of the technical features, purposes and effects of the present invention, specific embodiments of the present invention are now described in detail with reference to the accompanying drawings.
[0053] It should be noted that the flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor do they have to be executed in the order described. For example, some operations / steps can be decomposed, while some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.
[0054] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.
[0055] like Figure 1 As shown, some embodiments of the present invention disclose a user management system, including a parent system and at least two subsystems. It can be understood that the at least two can be two, three or any number, specifically:
[0056] The parent system includes:
[0057] Account information management module, which is used to store and manage account information of the parent system and all subsystems;
[0058] An account authority management module, which is used to store and manage the authority types corresponding to the accounts of the parent system and all subsystems; and
[0059] User management service module, which is used to communicate with all subsystems in real time and control and schedule the account information management module and the account authority management module;
[0060] Subsystems include:
[0061] The account information registration and login interface module is used to register and log in an account. The account information registration and login interface module is deployed in the subsystem in the form of a plug-in and can be reused in different subsystems.
[0062] In some embodiments, the user management system is applied to a rail transit subway system, the parent system is a parent system for comprehensive monitoring in the rail transit subway system, and the subsystem is a business subsystem in the rail transit subway system, such as an emergency support system, etc. The rail transit subway system here is only an example and is not intended to be a limitation of this application. It may be other systems that require user management.
[0063] In some embodiments, in order to prevent the normal operation of the subsystem from being affected after the communication between the subsystem and the parent system is interrupted, the subsystem further includes:
[0064] The account information and permission type configuration module is used to synchronize information with the account information management module and the account permission management module. Even if the communication between the subsystem and the parent system is interrupted, the synchronized information in the subsystem can be used as a backup server for user management, so that the subsystem can operate normally.
[0065] In some embodiments, the parent system further comprises:
[0066] Communication interface module, the communication interface module is used for external application system. After the external application system is successfully connected to the parent system, the new external application system can be directly used as a subsystem.
[0067] In some embodiments, the account information management module, the account authority management module and the user management service module in the parent system are all arranged in the server of the parent system.
[0068] like Figure 2 As shown, some embodiments of the present invention disclose a method for implementing user management by the user management system described in any of the above embodiments, including an account registration step, which includes:
[0069] S11: The account information registration login interface module receives the account information for registration input by the user and sends it to the user management service module;
[0070] S12: The user management service module controls and compares and verifies with the scheduling account information management module;
[0071] S13: After the comparison and verification process is completed, the user management service module sends the registration result to the account information registration and login interface module.
[0072] Among them, the account information includes a user name and a password. In some embodiments, the account information registration and login interface module also receives verification information, and the verification information and account information are sent together to the user management service module. The user management service module controls and schedules the account information management module to compare and verify the verification information and account information, wherein the comparison and verification of the account information includes traversing whether there are duplicate user names, verifying whether the password setting format is correct, and at least one of the password strength levels. It can be understood that at least one can be one, two, three or any number.
[0073] If an error is found during the comparison and verification process, the user management service module will send a prompt message of registration failure to the subsystem through the network. If the comparison and verification are correct, a prompt message of registration success will be sent to the subsystem.
[0074] like Figure 2 As shown, in some embodiments, when the subsystem further includes the above-mentioned account information and permission type configuration module, the account registration step further includes:
[0075] S14: The user management service module synchronizes all account information in the account information management module to the account information and permission type configuration modules of all subsystems. Even if the communication between the subsystem and the parent system is interrupted, the synchronized information in the subsystem can be used as a backup server for user management, so that the subsystem can operate normally.
[0076] like Figure 3 As shown, some embodiments of the present invention disclose a method for implementing user management by the user management system described in any of the above embodiments, including a login step, which includes:
[0077] S21: The account information registration login interface module receives the account information input by the user for login and sends it to the user management service module. The account information includes the user name and password;
[0078] S22: The user management service module controls and schedules the account information management module to perform login verification;
[0079] S23: After the verification process is completed, the user management service module sends the login result to the subsystem. Specifically: if the verification is successful, the user management service module sends a prompt message of successful login to the subsystem, notifying the subsystem to allow login, and then the subsystem jumps the login interface to the system interface. If the verification is not successful, the user management service module sends a prompt message of unsuccessful login to the subsystem, such as prompting that the username or password is wrong.
[0080] The subsystem is the client and the parent system is the server. There are many ways for users to log in:
[0081] Method 1: On the application service of B / S (Browser / Server) architecture, a browser plug-in is installed on the client. The client uses the workflow engine and rule engine in the browser plug-in, combined with the information configured by the configuration center, to intercept and parse the login process information of different applications on the server, and finally generates the authentication information and permission information required for the single sign-on authentication of the corresponding client and server, and can transfer and compatible applications between subsystems. The advantages of this solution are convenient and flexible access, no intrusion on the business logic of the corresponding existing system, and greatly reducing the cost of accessing the single sign-on function between subsystems. At the same time, the client plug-in can be controlled online to ensure that the SSO single sign-on client uses the service in an authenticated, secure and controllable environment.
[0082] Method 2: In the application service of B / S architecture, each subsystem can realize the single sign-on function by accessing the CAS service based on the built CAS (Central Authentication Service), that is, the parent system. The advantage of this solution is that after the subsystem is configured for access according to the relevant access rules, each subsystem can complete the access to the parent system, and the client can realize the non-sensing operation, and the access is simple and convenient.
[0083] Method 3: Subsystems based on token authentication can implement single sign-on authentication through OAuth2, and are compatible with B / S service architecture and C / S service structure that use token authentication. Each subsystem logs in and authenticates by accessing the same authentication center (i.e., the parent system). After successful authentication, the resource interface of other subsystems can be accessed through the obtained token. Each service gateway verifies the legitimacy of the token and controls the access of related subsystems to related service interfaces.
[0084] like Figure 4 As shown, some embodiments of the present invention disclose a method for implementing user management by the user management system described in any of the above embodiments, including an account modification step, which includes:
[0085] S31: After logging in through the subsystem, the user enters the account modification interface of the account information management module of the parent system. The account modification interface is connected to the account information management module as part of the system plug-in;
[0086] S32: The account modification interface receives and saves the modified account information, wherein the modified account information includes at least one of identity information, user type, contact phone number, and contact email address. It can be understood that the at least one can be one, two, three, or any number;
[0087] S33: The user management service module returns the account modification result to the subsystem.
[0088] like Figure 4 As shown, in some embodiments, when the subsystem further includes the above-mentioned account information and permission type configuration module, the account modification step further includes:
[0089] S34: The user management service module synchronizes all account information in the account information management module to the account information and permission type configuration modules of all subsystems. Even if the communication between the subsystem and the parent system is interrupted, the synchronized information in the subsystem can be used as a backup server for user management, so that the subsystem can operate normally.
[0090] like Figure 5 As shown, some embodiments of the present invention disclose a method for implementing user management by the user management system described in any of the above embodiments, including a user authority configuration step, which includes:
[0091] S41: After the account is registered, the account authority management module receives a configuration instruction from an administrator to grant authority to the account.
[0092] In some embodiments, when the subsystem further includes the above-mentioned account information and permission type configuration module, the user permission configuration step further includes:
[0093] S42: After the configuration is completed, the user management service module packages all account permission types in the account permission management module and synchronizes them to the account information and permission type configuration modules of all subsystems.
[0094] Of course, depending on the user's permissions, the user can also log in directly to the parent system and perform the above registration, login and account modification in the parent system, or the administrator can modify the registration and user information of others through his own permissions. In either case, as long as the modification is successful, the user management service module will synchronize with the account information and permission type configuration module of the subsystem, and an automatic synchronization process can be realized without the need to modify each subsystem separately.
[0095] In specific implementation, there are also multiple ways to synchronize account information and permission types:
[0096] 1) API interface method: All subsystems are connected to the synchronous API interface of the parent system. Based on the encrypted transmission of user information and combined with configuration information, relevant account information and permission types are obtained in the parent system. All subsystems synchronize and update the newly added account information and permission types through the original user addition function.
[0097] 2) Directly connect to the database, by configuring the database connection configuration of all subsystems, to achieve direct reading and writing operations on account information and permission types in the parent system.
[0098] 3) User information file synchronization method, by configuring in the currently used subsystem, and then encrypting the account information and permission type in the parent system to generate user information files corresponding to different subsystems, and securely transmitting the user information files to the target subsystem based on SFTP or offline copy import, and then decrypting them in the target subsystem.
[0099] like Figure 6 As shown, when a new third-party external application system needs to be connected to the parent system, some embodiments of the present invention disclose a method for implementing user management by the user management system described in any of the above embodiments, including an application expansion step, which includes:
[0100] S51: The parent system communicates with the external application system through the communication interface module;
[0101] S52: The parent system receives the request data packet sent by the external application system and parses it;
[0102] S53: If the data format matches, verification is performed and the verification result is returned to the external application system;
[0103] S54: the parent system sends the account information registration login interface module of the subsystem and the program installation package corresponding to the account information and permission type configuration module to the external application system;
[0104] S55: After the external application system has installed the program installation package, it generates an account information registration and login interface module and an account information and permission type configuration module. At this time, the external application system serves as a subsystem;
[0105] S56: The user management service module of the parent system communicates in real time with the account information registration and login interface module of the external application system and the account information and permission type configuration module;
[0106] S57: The user management service module synchronizes all account information in the account information management module and all account permission types in the account permission management module to the account information and permission type configuration module of the external application system, so that the user can log in and use the external application system with the existing account information and permissions at any time in the future.
[0107] Some embodiments of the present invention disclose a method for implementing user management by the user management system described in any of the above embodiments, including an emergency step, which includes:
[0108] After the subsystem determines that the communication with the parent system is interrupted, the account information and permission type configuration module which synchronizes the account information and the permission type corresponding to the account is set as a backup server for user management.
[0109] It should be noted that the above-mentioned account registration steps, login steps, account modification steps, user authority configuration steps, application expansion steps and emergency steps can be combined arbitrarily to form a complete solution.
[0110] By implementing the present invention, the following beneficial effects are achieved:
[0111] The present invention connects all subsystems to the parent system as a whole by making all subsystems communicate with each other, adding a user management service module, an account information management module and an account authority management module in the parent system, and adding an account information registration and login interface module in each subsystem at the same time. Account information and account authority management functions are no longer set in each subsystem, but all account information and account authority are unified in the parent system for unified management, thereby enabling users to log in to other subsystems with relevant authority based on the same account, thereby achieving seamless switching of user information between different subsystems, and achieving real-time synchronization and management and use of user information between different subsystems, avoiding the problems of cumbersome management of user information and information differences, greatly reducing the difficulty and cumbersomeness of user use, and also achieving the effect of automatic synchronization of each subsystem when account information is modified and account authority type is changed, and finally achieving comprehensive, efficient and convenient management of users.
[0112] It can be understood that the above embodiments only express some implementation methods of the present invention, and the description thereof is relatively specific and detailed, but it cannot be understood as limiting the patent scope of the present invention. It should be pointed out that for ordinary technicians in this field, without departing from the concept of the present invention, the above embodiments or technical features can be freely combined, and several deformations and improvements can be made, which all belong to the protection scope of the present invention, that is, the embodiments described in "some embodiments" can be freely combined with any of the above and below embodiments; therefore, all equivalent changes and modifications made to the scope of the claims of the present invention should fall within the scope of the claims of the present invention.
Claims
1. A user management system, characterized in that: It includes a parent system and at least two subsystems; The parent system includes: An account information management module, the account information management module is used to store and manage the account information of the parent system and all the subsystems; An account authority management module, the account authority management module is used to store and manage the authority types corresponding to the accounts of the parent system and all the subsystems; and A user management service module, the user management service module is used to communicate with all the subsystems in real time, and control and schedule the account information management module and the account authority management module; The subsystem includes: The account information registration and login interface module is used to register and log in an account.
2. The user management system according to claim 1, characterized in that: The subsystem also includes: An account information and permission type configuration module, wherein the account information and permission type configuration module is used to synchronize information with the account information management module and the account permission management module.
3. The user management system according to claim 1 or 2, characterized in that: The parent system also includes: A communication interface module, wherein the communication interface module is used for connecting to an external application system.
4. A method for implementing user management by the user management system according to any one of claims 1 to 3, characterized in that: Includes account registration steps, which include: The account information registration and login interface module receives the account information for registration input by the user and sends it to the user management service module; The user management service module controls and schedules the account information management module to perform comparison and verification; After the comparison and verification process is completed, the user management service module sends the registration result to the account information registration and login interface module.
5. The method for implementing user management by the user management system according to claim 4, characterized in that: When the subsystem further includes an account information and permission type configuration module, the account registration step further includes: The user management service module synchronizes all account information in the account information management module to the account information and permission type configuration modules of all the subsystems.
6. A method for implementing user management by the user management system according to any one of claims 1 to 3, characterized in that: Includes a login step, which includes: The account information registration and login interface module receives the account information input by the user for login and sends it to the user management service module; The user management service module controls and schedules the account information management module to perform login verification; After the verification process is completed, the user management service module sends the login result to the subsystem.
7. A method for implementing user management by the user management system according to any one of claims 1 to 3, characterized in that: Includes account modification steps, which include: After logging in through the subsystem, the user enters the account modification interface of the account information management module of the parent system; The account modification interface receives and saves the modified account information; The user management service module returns the account modification result to the subsystem.
8. A method for implementing user management by a user management system according to any one of claims 1 to 3, characterized in that: Includes user permission configuration steps, which include: After the account is registered, the account authority management module receives configuration instructions from the administrator to grant authority to the account.
9. The method for implementing user management by the user management system according to claim 8, characterized in that: When the subsystem further includes an account information and permission type configuration module, the user permission configuration step further includes: After the configuration is completed, the user management service module packages all account permission types in the account permission management module and synchronizes the account information and permission type configuration modules of all the subsystems.
10. A method for implementing user management by the user management system according to claim 3, characterized in that: Includes application extension steps: The parent system communicates with the external application system through the communication interface module; The parent system receives the request data packet sent by the external application system and parses it; If the data format matches, verification is performed and the verification result is returned to the external application system; The parent system sends the account information registration login interface module of the subsystem and the program installation package corresponding to the account information and permission type configuration module to the external application system; After the external application system has installed the program installation package, it generates the account information registration and login interface module and the account information and permission type configuration module; The user management service module of the parent system communicates in real time with the account information registration and login interface module and the account information and permission type configuration module of the external application system.