A multi-account front-end feedback method and system based on shared user IDs
By sharing user IDs and account identifiers, the problem of frequent user switching under multiple accounts is solved, and unified display of content from multiple accounts and efficient business operations are achieved.
Patent Information
- Application Number
- CN202310461716.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-04-26
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2043-04-26
AI Technical Summary
In existing technologies, users need to frequently switch between multiple account identities to complete different business operations, which increases system resource consumption and makes the operation cumbersome, and makes it impossible to integrate and display the content of multiple user accounts when a single user account is logged in.
By sharing user IDs, a personnel table is established, and user IDs, account identity identifiers, and user role identifiers are used to ensure that the identity of the account to which the business request operation belongs is determined, and to achieve a unified display of front-end feedback from multiple accounts.
It improves the coupling between different user accounts of the same user, simplifies user operations, reduces the frequency of account switching, and improves system efficiency and user experience.
Smart Images

Figure CN116485341B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of business flow operation and automation processing technology, and in particular to a multi-account front-end feedback method and system based on shared user IDs. Background Technology
[0002] In existing organizational structures, it's common for individuals to hold multiple positions and may need to work across various departments. Adopting digital office solutions requires users to use multiple accounts to handle tasks across different departments and roles. Managing these accounts essentially involves copying existing accounts from the personnel table, modifying only limited information such as user ID, job permissions, affiliated organization, and department, and then re-inserting them into the personnel table, creating additional virtual accounts for existing personnel.
[0003] For complex business processing systems, which involve numerous business workflow operations of various types, users typically rely heavily on the work arrangements retrieved and fed back by the front-end system, such as to-do lists and completed tasks, to correctly execute business workflow operations and perform query requests and transactions related to business data. Under current technology, the execution of various operations by the front-end system requires, based on the user's account identity, to retrieve corresponding information from the personnel table, such as the user's ID, job title and permissions, affiliated organization, and department, to determine the specific scope of the business operation and to determine execution restrictions.
[0004] For the common problem of implementing multiple accounts for a single user, existing technologies typically involve adding a new account and correspondingly adding a new user record to the system's personnel table, along with a brand new user ID. This approach is essentially no different from simply adding a new user; each user account is essentially an independent entity with completely independent business operations. Limited improvements include creating a relationship table between user accounts in addition to the existing personnel table, and allowing users to access other associated accounts while logged in with any account and manually switch login accounts. However, the actual business operations still depend on the permissions and scope of the logged-in account; the business operations of different accounts are not related at all, and many restrictions and inconsistencies remain for user operations in practical use.
[0005] Another improvement is still based on different user accounts (different user IDs). For specific query requests, the interface and menu list that the user can see are displayed in a way that combines the front-end feedback under the different permissions of each user account. After the user issues an operation request, the system backend traverses the list of user accounts with permissions under the corresponding menu and integrates the query results under all account permissions as the request response.
[0006] Therefore, when a person has multiple accounts, the front-end feedback (such as business menu views) they need to obtain under different account identities is usually different. Furthermore, during actual business processing in the system, workflow operations often rely on third-party open-source workflow engine components (such as activities). These components often record user ID information to distinguish the responsible party for workflow tasks. This inevitably means that users can only obtain feedback such as workflow tasks and completed tasks limited to the currently logged-in account in the front-end system, and can only perform business process operations corresponding to the current account. In other words, the scope of business module data is limited to the currently logged-in account. When a user needs to perform business operations belonging to another account, they must repeatedly log in to switch user accounts to ensure that data feedback and business operations are not confused.
[0007] For users, as a single natural person, they naturally want to minimize the cumbersome issues caused by operating multiple different user accounts, especially avoiding the need to repeatedly switch between different user accounts to complete different business operations, and avoiding missing any tasks under a specific account. While existing technologies attempt to improve information display through aggregation, these designs can achieve some global queries by traversing and aggregating the results of business form data queries. However, due to the reliance on third-party components such as workflow engines, many specific business operation functions are directly bound to user accounts (user IDs). This prevents the ability to process business operations for other related accounts simultaneously when a single user account is logged in. Furthermore, the system backend performing corresponding searches for an uncertain number of user accounts for each request would significantly increase system resource consumption and affect system execution efficiency.
[0008] Clearly, in practice, how to enable users to view various business data and work-related tasks under all associated account identities without switching user accounts, while ensuring that business operations can still be submitted based on the correct user account identity, is a technical problem that needs to be solved. Summary of the Invention
[0009] To address the shortcomings of existing technologies, this invention proposes a multi-account front-end feedback method and system based on shared user IDs. By sharing the same user ID among different user accounts, the coupling between different user accounts of the same user is improved. This solves the problem in existing technologies where relying on third-party workflow components and binding them to user IDs prevents the integrated display of content from multiple user accounts. At the same time, by attaching corresponding account identifiers to business data, the identity of the account to which the business request operation belongs is ensured.
[0010] To achieve the above objectives, the technical solution adopted by the present invention includes:
[0011] A multi-account front-end feedback method based on shared user IDs, characterized by comprising:
[0012] S1. Create a personnel table, which includes a unique user ID corresponding to a specific user;
[0013] S2. Determine whether a specific user has multiple different user accounts. When it is determined that a specific user does not have multiple different user accounts, use the user ID as the account identity identifier and user role identifier.
[0014] S3. When it is determined that a specific user has multiple different user accounts, it is further determined whether the multiple user accounts belong to the same business unit. When it is determined that the multiple user accounts belong to the same business unit, the user number is used as the account identity identifier.
[0015] S4. When it is determined that multiple user accounts do not belong to the same business unit, configure the account identity identifier for each business unit and establish the first association label between the account identity identifier and the corresponding user number.
[0016] S5. Determine if multiple user accounts belong to the same account identity. If it is determined that multiple user accounts do not belong to the same account identity, use the account identity as the user role identifier.
[0017] S6. When it is determined that multiple user accounts belong to the same account identity, configure the user role identity for each user account and establish a second association label between the user role identity and the corresponding account identity.
[0018] S7. Obtain the user request and identify the user ID based on the user request. The user request includes any one or more combinations of user ID, account identity identifier, and user role identifier.
[0019] S8. Retrieve and provide front-end feedback content for all corresponding user accounts based on the user ID.
[0020] Furthermore, the method also includes:
[0021] S9. Obtain the operation request for the front-end feedback content, identify the user account to which the operation request belongs, and execute the operation request according to the identified user account.
[0022] Furthermore, the user account to which the front-end feedback content corresponds to the identification operation request includes:
[0023] Identify the account identity identifier corresponding to the front-end feedback content;
[0024] Identify the user role identifier corresponding to the front-end feedback content.
[0025] Furthermore, the step of executing the operation request based on the identified user account includes:
[0026] Verify whether the operation request meets the permission requirements based on the user's role identifier;
[0027] Select the scope of the operation request based on the account identity identifier.
[0028] Furthermore, the step of identifying the user ID based on the user request includes:
[0029] Determine whether the user request includes a user ID. If the user request includes a user ID, use the user ID contained in the user request as the user ID.
[0030] When a user request does not include a user ID, it is further determined whether the user request includes an account identifier. When the user request includes an account identifier, the user ID is identified based on the account identifier.
[0031] When a user request does not include an account identity identifier, the user ID is identified based on the user role identifier.
[0032] Further, step S8 includes:
[0033] Retrieve all corresponding user accounts based on user ID;
[0034] The corresponding front-end feedback content is retrieved based on the user's account identity identifier and / or user role identifier.
[0035] This invention also relates to a multi-account front-end feedback system based on a shared user ID, characterized in that it includes:
[0036] The personnel table maintenance module is used to create a personnel table and maintain the user ID, account identity identifier, and user role identifier data in the personnel table;
[0037] The request identification module is used to identify the user ID based on the user's request.
[0038] The request feedback module is used to retrieve and provide front-end feedback content for all corresponding user accounts based on the user ID.
[0039] The operation feedback module is used to identify the user account to which the front-end feedback content corresponding to the operation request belongs, and to execute the operation request based on the identified user account.
[0040] The present invention also relates to a computer-readable storage medium, characterized in that the storage medium stores a computer program, which, when executed by a processor, implements the above-described method.
[0041] The present invention also relates to an electronic device, characterized in that it includes a processor and a memory;
[0042] The memory is used to store user ID, account identity identifier, and user role identifier;
[0043] The processor is used to execute the above method by invoking the user ID, account identity identifier, and user role identifier.
[0044] The present invention also relates to a computer program product, including a computer program and / or instructions, characterized in that the computer program and / or instructions, when executed by a processor, implement the steps of the above-described method.
[0045] The beneficial effects of this invention are as follows:
[0046] The multi-account front-end feedback method and system based on shared user IDs described in this invention improves the coupling between different user accounts of the same user by sharing the same user ID. This solves the problem in existing technologies where relying on third-party workflow components and binding them to user IDs prevents the integrated display of content from multiple user accounts. After logging into the system with any account, when selecting the panoramic view mode, the system displays a panoramic view of the page function menus available to the user under all account identities. Furthermore, it allows for the identification and control of account permissions for each page function menu, greatly facilitating the system user experience for users with multiple account identities and improving work efficiency. Simultaneously, the shared user ID can still serve as a unique identifier for interaction between multiple systems, without affecting cross-system interaction requests. By attaching corresponding account identifiers to business data, the front-end stores the correspondence between each menu under the user's display permissions and the corresponding current user account identity information, ensuring the identification of the account identity to which the business request operation belongs. Attached Figure Description
[0047] Figure 1 This is a schematic diagram of the multi-account front-end feedback method based on shared user IDs according to the present invention.
[0048] Figure 2 This is a schematic diagram of the multi-account front-end feedback system based on shared user IDs according to the present invention. Detailed Implementation
[0049] To better understand the content of this invention, a detailed description will be provided in conjunction with the accompanying drawings and embodiments.
[0050] The first aspect of this invention relates to a process flow as follows: Figure 1 The multi-account front-end feedback method based on shared user IDs shown includes:
[0051] S1. Create a personnel table, which includes a unique user ID corresponding to a specific user.
[0052] In existing technology, the system's personnel table stores information on all registered personnel in the system. Typically, the personnel table must have a user ID (userNo) as a unique identifier for each data record. Adding a new account to the personnel table generates a new user ID, thus creating a problem where the user ID cannot directly correspond to a real user.
[0053] In the technical solution of the present invention, the user number is stripped of its function as a unique identifier for data records, and is used as a unique identifier for the user. The same user number is used for any new account of the same user.
[0054] S2. Determine if a specific user has multiple different user accounts. If it is determined that a specific user does not have multiple different user accounts, use the user ID as the account identity identifier and user role identifier.
[0055] Typically, for users with only a single responsibility in the system, there is usually only one actual user account. Therefore, their user ID can still be used as the unique identifier of the corresponding data record in the user account without adding any extra system burden or verification steps.
[0056] S3. When it is determined that a specific user has multiple different user accounts, further determine whether the multiple user accounts belong to the same business unit. When it is determined that the multiple user accounts belong to the same business unit, use the user number as the account identity identifier.
[0057] S4. When it is determined that multiple user accounts do not belong to the same business unit, the corresponding account identity identifier is configured for each business unit, and a first association label between the account identity identifier and the corresponding user number is established.
[0058] When a single user holds multiple positions, it's necessary to consider that their different responsibilities may correspond to different business units, thus requiring corresponding identification. When multiple accounts belong to the same business unit, the user ID can be simply used as the account identifier (userAccountFlag).
[0059] When it is determined that there are multiple different business entities, it is necessary to re-establish the account identity identifier to distinguish it from the user number. At the same time, it is necessary to establish a correspondence between the account identity identifier and the user number, namely the first association label, so that users can freely choose the user number or the account identity identifier as the login credentials according to the situation. At the same time, it can be ensured that either choice can achieve the corresponding acquisition of all feedback information.
[0060] S5. Determine if multiple user accounts belong to the same account identity. If it is determined that multiple user accounts do not belong to the same account identity, use the account identity as the user role identifier.
[0061] Generally, which menus a user can see in a system is determined by the user's role, as the visibility of page menus is typically controlled by various roles defined within the system. Therefore, by assigning various roles to users, the range of page menus a user can see can be indirectly controlled. Similar to step S3 above, for applications that don't require multiple roles, the account identifier can still be used directly as the user role identifier (roleNo), thus achieving the technical effect of multiple different user accounts simultaneously having the same front-end feedback. This is particularly suitable for specific scenarios such as multi-user testing and does not incur additional system overhead.
[0062] S6. When it is determined that multiple user accounts belong to the same account identity, the user role identity is configured for each user account, and a second association label is established between the user role identity and the corresponding account identity.
[0063] Similar to step S4 above, in cases where there are multiple different user roles, it is necessary to re-establish user role identifiers that are different from the original user IDs and account identity identifiers, and establish a second association label between the user role identifier and the corresponding account identity identifier.
[0064] S7. Obtain the user request and identify the user ID based on the user request. The user request includes any one or more combinations of user ID, account identity identifier, and user role identifier.
[0065] The process of identifying the user ID can preferably include the following steps: determining whether the user request includes a user ID; if the user request includes a user ID, using the user ID included in the user request as the user ID; if the user request does not include a user ID, further determining whether the user request includes an account identity identifier; if the user request includes an account identity identifier, identifying the user ID based on the account identity identifier; if the user request does not include an account identity identifier, identifying the user ID based on the user role identifier.
[0066] S8. Retrieve and provide front-end feedback content for all corresponding user accounts based on the user ID. Specifically, after retrieving all corresponding user accounts based on the user ID, the front-end feedback content can be retrieved by categorizing the user accounts according to their account identity identifier and / or user role identifier.
[0067] When a user logs into the system, the system initializes and calculates the page menus that the user can display and presents the page view accordingly. Because there is a correspondence between menus and roles, and roles are associated with user IDs and user account identification information, the system can calculate the account identification information corresponding to each menu item. When initializing the page menus displayed to the user, the system synchronously returns the account identification information corresponding to each menu item to the front end.
[0068] S9. Obtain the operation request for the front-end feedback content, identify the user account to which the operation request belongs, and execute the operation request according to the identified user account.
[0069] Specifically, identifying the user account to which the front-end feedback content belongs for the operation request includes identifying the account identity identifier corresponding to the front-end feedback content and the user role identifier corresponding to the front-end feedback content. Then, the operation request is preferentially verified based on the user role identifier to determine whether it meets the permission requirements, and the execution scope of the operation request is selected based on the account identity identifier. This allows for the precise definition of the relevant list query scope and the applicable account identity for each business form based on the account identifier information belonging to each menu and business form cached on the front end.
[0070] In practice, when a user logs in and the system initializes the page menu, it returns the account identity information for each menu item. The front-end stores this information as a dynamic page cache for that user. Subsequently, whenever a user initiates a query or other business request under a specific menu item, this account identity information is passed as an additional parameter to the back-end. The back-end uses this information to define the scope of the data list query results for this request. Each record in the retrieved business order list contains the account identity applicable to that record. When a user opens each business order for specific data processing, this account identity information is also passed as an additional parameter to the back-end. Upon receiving this information, the back-end responds with the correct processing based on the received account identity information.
[0071] For example, a specific business request might belong to account USER1, and the account associated with USER1 belongs to organization A. When a user needs to perform some business co-signing operations and the business request needs to be sent to other departments within the same organization, the backend can know that it should be sent to a department under organization A, and not a department under organization B. This accurately defines the account identity applicable to each business request, ensuring the correct processing of business operations.
[0072] Another aspect of the present invention relates to a multi-account front-end feedback system based on a shared user ID, the structure of which is as follows: Figure 2 As shown, it includes:
[0073] The personnel table maintenance module is used to create a personnel table and maintain the user ID, account identity identifier, and user role identifier data in the personnel table;
[0074] The request identification module is used to identify the user ID based on the user's request.
[0075] The request feedback module is used to retrieve and provide front-end feedback content for all corresponding user accounts based on the user ID.
[0076] The operation feedback module is used to identify the user account to which the front-end feedback content corresponding to the operation request belongs, and to execute the operation request based on the identified user account.
[0077] By using this system, the aforementioned computational processing methods can be executed and the corresponding technical effects can be achieved.
[0078] Embodiments of the present invention also provide a computer-readable storage medium capable of implementing all the steps of the methods in the above embodiments, wherein the computer-readable storage medium stores a computer program that, when executed by a processor, implements all the steps of the methods in the above embodiments.
[0079] Embodiments of the present invention also provide an electronic device for performing the above-described method. As an implementation device for the method, the electronic device has at least a processor and a memory. In particular, the memory stores data and related computer programs required for performing the method, such as user ID, account identity identifier, and user role identifier. The processor calls the data and programs in the memory to execute all steps of the method and obtain the corresponding technical effect.
[0080] Preferably, the electronic device may include a bus architecture, which may include any number of interconnected buses and bridges. The bus will include various circuits linked together by one or more processors and memories. The bus may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface between the bus and the receiver and transmitter. The receiver and transmitter may be the same element, i.e., a transceiver, providing a unit for communicating with various other systems over a transmission medium. The processor is responsible for managing the bus and general processing, while the memory may be used to store data used by the processor during operation.
[0081] Additionally, the electronic device may further include components such as a communication module, an input unit, an audio processor, a display, and a power supply. The processor (or controller, operating control) used may include a microprocessor or other processor device and / or logic device, which receives input and controls the operation of various components of the electronic device; the memory may be one or more of a buffer, flash memory, hard drive, removable media, volatile memory, non-volatile memory, or other suitable devices, which can store the aforementioned data information, and may also store programs for executing the information, and the processor can execute the program stored in the memory to achieve information storage or processing, etc.; the input unit is used to provide input to the processor, for example, it can be a button or touch input device; the power supply is used to provide power to the electronic device; the display is used to display images and text, for example, it can be an LCD display. The communication module is a transmitter / receiver that transmits and receives signals via an antenna. The communication module (transmitter / receiver) is coupled to the processor to provide input signals and receive output signals, which can be the same as in conventional mobile communication terminals. Based on different communication technologies, multiple communication modules can be incorporated into the same electronic device, such as cellular network modules, Bluetooth modules, and / or wireless LAN modules. The communication module (transmitter / receiver) is also coupled to a speaker and microphone via an audio processor to provide audio output through the speaker and receive audio input from the microphone, thereby enabling typical telecommunications functions. The audio processor can include any suitable buffer, decoder, amplifier, etc. Furthermore, the audio processor is coupled to a central processing unit, enabling on-device recording via the microphone and on-device playback of stored sound via the speaker.
[0082] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0083] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A system that specifies functions in one or more boxes.
[0084] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including an instruction set implemented in a process. Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0085] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the functions specified in one or more boxes. Although preferred embodiments of the invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the invention.
[0086] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.
Claims
1. A multi-account front-end feedback method based on shared user IDs, characterized in that, include: S1. Establish a personnel table, which includes a unique user ID corresponding to a specific user; when the specific user has multiple different user accounts, the multiple different user accounts use the same user ID, which serves as a unique identifier for the specific user, but not as a unique identifier for the data records of the multiple different user accounts in the personnel table. S2. Determine whether a specific user has multiple different user accounts. When it is determined that a specific user does not have multiple different user accounts, use the user ID as the account identity identifier and user role identifier. S3. When it is determined that a specific user has multiple different user accounts, it is further determined whether the multiple user accounts belong to the same business unit. When it is determined that the multiple user accounts belong to the same business unit, the user number is used as the account identity identifier. S4. When it is determined that multiple user accounts do not belong to the same business unit, configure the account identity identifier for each business unit and establish the first association label between the account identity identifier and the corresponding user number. S5. Determine if multiple user accounts belong to the same account identity. If it is determined that multiple user accounts do not belong to the same account identity, use the account identity as the user role identifier. S6. When it is determined that multiple user accounts belong to the same account identity, configure the user role identity for each user account and establish a second association label between the user role identity and the corresponding account identity. S7. Obtain the user request and identify the user ID based on the user request. The user request includes any one or more combinations of user ID, account identity identifier, and user role identifier. S8. Retrieve and return front-end feedback content for all corresponding user accounts based on the user ID. The front-end feedback content includes page function menus. When initializing the page function menus displayed to the user, the account identity identifier and / or user role identifier information corresponding to each page function menu is synchronously returned to the front-end. The front-end stores the account identity identifier and / or user role identifier information as a dynamic page cache. When a user initiates a business request based on the page function menu, the account identity identifier information corresponding to the page function menu is passed to the back-end as an additional parameter. The back-end defines the data query scope involved in this business request based on the account identity identifier information.
2. The method as described in claim 1, characterized in that, The method further includes: S9. Obtain the operation request for the front-end feedback content, identify the user account to which the operation request belongs, and execute the operation request according to the identified user account.
3. The method as described in claim 2, characterized in that, The user accounts to which the front-end feedback content corresponds to the recognition operation request include: Identify the account identity identifier corresponding to the front-end feedback content; Identify the user role identifier corresponding to the front-end feedback content.
4. The method as described in claim 3, characterized in that, The operation request based on the identified user account includes: Verify whether the operation request meets the permission requirements based on the user's role identifier; Select the scope of the operation request based on the account identity identifier.
5. The method as described in claim 1, characterized in that, The process of identifying the user ID based on the user request includes: Determine whether the user request includes a user ID. If the user request includes a user ID, use the user ID contained in the user request as the user ID. When a user request does not include a user ID, further determine whether the user request includes an account identifier. If the user request includes an account identifier, identify the user ID based on the account identifier. When a user request does not include an account identity identifier, the user ID is identified based on the user role identifier.
6. A multi-account front-end feedback system based on shared user IDs, characterized in that, For implementing the method as described in any one of claims 1 to 5, comprising: The personnel table maintenance module is used to create a personnel table and maintain the user ID, account identity identifier, and user role identifier data in the personnel table; The request identification module is used to identify the user ID based on the user's request. The request feedback module is used to retrieve and provide front-end feedback content for all corresponding user accounts based on the user ID. The operation feedback module is used to identify the user account to which the front-end feedback content corresponding to the operation request belongs, and to execute the operation request based on the identified user account.
7. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, implements the method of any one of claims 1 to 5.
8. An electronic device, characterized in that, Including processor and memory; The memory is used to store user ID, account identity identifier, and user role identifier; The processor is configured to execute the method of any one of claims 1 to 5 by invoking the user ID, account identity identifier, and user role identifier.
9. A computer program product, comprising a computer program and / or instructions, characterized in that, When the computer program and / or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 5.
Citation Information
Patent Citations
Unified identification method, system and device based on multiple accounts and storage medium
CN111368013A
User role permission management method and device thereof, computer equipment and storage medium
CN111641627A
