User transition method, device and equipment between deployable computing units

Abstract

The invention provides a method, a device and equipment for user transition between deployable computing units. The method comprises the following steps: determining an employee role of a user from various employee roles; according to a pre-generated jump request, calling a user set allowing jump and a deployable calculation unit range corresponding to the employee role from a system database; if it is judged that the user hits the user set allowed to jump and the first deployable computing unit and a predetermined second deployable computing unit are in a deployable computing unit range, acquiring permission configuration information of the user from the first deployable computing unit; creating a new user in the second deployable computing unit, and configuring the permission configuration information to the new user; and after configuration of the permission configuration information of the new user is completed, the user is directed to the target operation interface on the second deployable computing unit to complete transition of the user between the deployable computing units, so that the user transition efficiency between the deployable computing units is improved.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular to a method, apparatus and device for user migration between deployable computing units. Background Technology

[0002] Currently, in IoT platforms built on container orchestration technology, the multi-deployable compute unit (MDC) architecture has become the mainstream application deployment model. Each MDC carries different business functions and services. In actual operational scenarios, users need to switch between multiple MDCs to complete complex business processes.

[0003] In existing technologies, traditional user migration methods between deployable computing units require users to manually create user accounts and perform user login and login verification in the new deployable computing unit when migrating from one deployable computing unit to another to complete the subsequent user migration.

[0004] However, in the existing technology, the process of manually creating user accounts and performing user login and login verification to complete subsequent user migration is cumbersome, which reduces the efficiency of user migration between deployable computing units. Summary of the Invention

[0005] This application provides a user migration method, apparatus, and device between deployable computing units to solve the problem that manually creating user accounts and performing user login and login verification to complete subsequent user migration is cumbersome and reduces the efficiency of user migration between deployable computing units.

[0006] In a first aspect, this application provides a user hopping method between deployable computing units, applied to electronic devices, comprising:

[0007] In response to the user's navigation operation on the first deployable computing unit, a navigation request is generated, and the second deployable computing unit to which the user should navigate is determined.

[0008] The user's employee role is determined from a set of preset employee roles;

[0009] The system retrieves a pre-configured permission fence policy from the system database based on the jump request. The permission fence policy includes at least the set of users allowed to jump and the range of deployable computing units corresponding to the employee role.

[0010] If it is determined that the user matches the set of users allowed to jump, and the first deployable computing unit and the second deployable computing unit are within the range of the deployable computing units, then the permission configuration information corresponding to the user is obtained from the first deployable computing unit;

[0011] Create any new user within the second deployable computing unit and configure the permission configuration information for the new user;

[0012] After configuring the permission information for the new user, the user is directed to the target operation interface on the second deployable computing unit to complete the user's transition between deployable computing units.

[0013] In one possible design, if it is determined that the user matches the set of users allowed to jump, and the first deployable computing unit and the second deployable computing unit are within the scope of the deployable computing unit, then the permission configuration information corresponding to the user is obtained from the first deployable computing unit, including: obtaining the user's identity information, the first basic information of the first deployable computing unit, and the second basic information of the second deployable computing unit; determining whether the user's identity information matches the set of users; if it is determined that the user's identity information matches the set of users, then determining whether the first deployable computing unit and the second deployable computing unit are within the scope of the deployable computing unit based on the first basic information and the second basic information; if it is determined that the first deployable computing unit and the second deployable computing unit are within the scope of the deployable computing unit, then the permission configuration information corresponding to the user is obtained from the first deployable computing unit.

[0014] In one possible design, after configuring the permission information for the new user, directing the user to the target operation interface on the second deployable computing unit to complete the user's transition between deployable computing units includes: after configuring the permission information for the new user, generating the new user's target login information on the first deployable computing unit; after skipping the verification of the target login information, directing the user to the target operation interface on the second deployable computing unit according to a preset interface to complete the user's transition between deployable computing units.

[0015] In one possible design, after configuring the permission information for the new user, generating the target login information for the new user on the first deployable computing unit includes: generating the target login information for the new user on the first deployable computing unit after configuring the permission information for the new user; and issuing a corresponding short-term access credential to the second deployable computing unit; correspondingly, after skipping the verification of the target login information, directing the user to a target operation interface on the second deployable computing unit according to a preset interface to complete the user's transition between deployable computing units includes: after skipping the verification of the target login information, directing the user to a target operation interface on the second deployable computing unit according to a preset interface and the short-term access credential to complete the user's transition between deployable computing units; and destroying the short-term access credential after the transition between deployable computing units is completed.

[0016] In one possible design, the configuration process of the permission fence policy includes: determining multiple types of employee roles and multiple deployable computing units; determining the set of users allowed to jump to each type of employee role; determining the range of deployable computing units corresponding to each type of employee role based on the multiple deployable computing units; and configuring the permission fence policy based on the multiple types of employee roles, each set of users allowed to jump to, and each range of deployable computing units.

[0017] In one possible design, the method further includes: acquiring multiple deployable computing units at different business stages; acquiring the permission rules corresponding to each deployable computing unit; configuring permissions for the corresponding deployable computing units according to the permission rules to obtain the jump permissions and operation permissions corresponding to each deployable computing unit; and configuring the permission fence policy according to the jump permissions and operation permissions corresponding to each deployable computing unit.

[0018] In one possible design, the step of generating a jump request and determining the second deployable computing unit to which the user should jump in response to a user's jump operation on the operation interface of the first deployable computing unit includes: generating login information in response to any user's login operation on the operation interface of the first deployable computing unit; verifying the login information to determine whether the user has login permissions; if the user is determined to have login permissions, then generating a jump request and determining the second deployable computing unit to which the user should jump in response to the user's jump operation on the operation interface.

[0019] Secondly, this application provides a user transition device that can be deployed between computing units, applied to electronic devices, including:

[0020] The generation module is used to respond to the user's jump operation on the operation interface of the first deployable computing unit, generate a jump request, and determine the second deployable computing unit to jump to.

[0021] The first determining module is used to determine the user's employee role from a set of preset employee roles;

[0022] The retrieval module is used to retrieve a pre-configured permission fence policy from the system database according to the jump request, wherein the permission fence policy includes at least the set of users allowed to jump and the range of deployable computing units corresponding to the employee role;

[0023] The first acquisition module is used to acquire the permission configuration information corresponding to the user from the first deployable computing unit if it is determined that the user hits the set of users allowed to jump, and the first deployable computing unit and the second deployable computing unit are within the range of the deployable computing unit;

[0024] The first configuration module is used to create any new user within the second deployable computing unit and configure the permission configuration information for the new user;

[0025] The orientation module is used to, after configuring the permission configuration information of the new user, direct the user to the target operation interface on the second deployable computing unit, so as to complete the user's transition between deployable computing units.

[0026] Thirdly, this application provides an electronic device, including: at least one processor and a memory;

[0027] The memory stores computer-executed instructions;

[0028] The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the user transition method between deployable computing units as described in the first aspect above and various possible designs of the first aspect.

[0029] Fourthly, this application provides a computer storage medium storing computer execution instructions, which, when executed by a processor, implement the user transition method between deployable computing units as described in the first aspect and various possible designs of the first aspect.

[0030] The user migration method, apparatus, and device provided in this application, in response to a user's jump operation on the operation interface of the first deployable computing unit, generate a jump request and determine the second deployable computing unit to which the user should jump; determine the user's employee role from a preset range of employee roles; retrieve the set of users allowed to jump and the range of deployable computing units corresponding to the employee role from the system database according to the jump request; if it is determined that the user matches the set of users allowed to jump, and that the first and second deployable computing units are within the range of deployable computing units, then obtain the user's corresponding permission configuration information from the first deployable computing unit; create any new user in the second deployable computing unit and configure the permission configuration information for the new user; after completing the permission configuration information for the new user, redirect the user to the target operation interface on the second deployable computing unit to complete the user's migration between deployable computing units. By automatically performing user migration based on permission configuration information, there is no need to manually create user accounts and perform user login and login verification, which improves the efficiency of user migration between deployable computing units. Attached Figure Description

[0031] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0032] Figure 1 A schematic diagram illustrating an application scenario for the user hopping method between deployable computing units provided in this embodiment of the application.

[0033] Figure 2 A flowchart illustrating the user hop method between deployable computing units provided in this application embodiment. Figure 1 ;

[0034] Figure 3 A flowchart illustrating the user hop method between deployable computing units provided in this application embodiment. Figure 2 ;

[0035] Figure 4 A schematic diagram of the structure of a user transition device between deployable computing units provided in an embodiment of this application;

[0036] Figure 5 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0037] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0038] The collection, storage, use, processing, transmission, provision, and disclosure of user data and other information involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0039] Currently, in IoT platforms built on container orchestration technology, the multi-deployable compute unit (MDU) architecture has become the mainstream application deployment model. Each MDU carries different business functions and services. In actual operation scenarios, users need to switch between multiple MDUs to complete complex business processes. In existing technologies, traditional user migration methods between MDUs require users to manually create a user account, log in, and verify login credentials in the new MDU to complete the migration. However, this manual user account creation and login verification process is cumbersome and reduces the efficiency of user migration between MDUs.

[0040] To address the aforementioned technical problems, this application proposes the following technical concept: Considering the user, the first deployable computing unit, the jump request, and the second deployable computing unit to which the user is to jump, after determining that the user matches a preset user set and that the first and second deployable computing units are within the preset deployable computing unit range, the inventor obtains the user's corresponding permission configuration information based on the first deployable computing unit; a new user is created within the second deployable computing unit, and the permission configuration information is configured for the new user; after configuring the permission configuration information for the new user, the user is directed to the target operation interface on the second deployable computing unit, thereby completing the user's jump between deployable computing units and improving the efficiency of user jumps between deployable computing units.

[0041] Figure 1 This is a schematic diagram illustrating an application scenario of the user transition method between deployable computing units provided in the embodiments of this application.

[0042] like Figure 1 As shown, the scene includes a display terminal 101 and an electronic device 102.

[0043] The display terminal 101 can be a display screen or a personal computer or other terminal.

[0044] Electronic device 102 can be a standalone device or a cluster of multiple devices.

[0045] Electronic device 102, in response to a user's jump operation on the operation interface of the first deployable computing unit on display terminal 101, generates a jump request and determines the second deployable computing unit to which the user should jump; determines the user's employee role from a preset range of employee roles; retrieves the set of users allowed to jump and the range of deployable computing units corresponding to the employee role from the system database according to the jump request; if it is determined that the user matches the set of users allowed to jump, and that the first and second deployable computing units are within the range of deployable computing units, then obtains the user's corresponding permission configuration information from the first deployable computing unit; creates any new user in the second deployable computing unit and configures the permission configuration information for the new user; after completing the permission configuration information for the new user, directs the user to the target operation interface of the second deployable computing unit on display terminal 101 to complete the user's transition between deployable computing units. A detailed embodiment is described below.

[0046] Figure 2 A flowchart illustrating the user hop method between deployable computing units provided in this application embodiment. Figure 1 The execution entity in this embodiment can be Figure 1 The electronic devices shown in the illustrated embodiments are not specifically limited in this embodiment. Figure 2 As shown, the method includes:

[0047] S201: In response to the user's jump operation on the operation interface of the first deployable computing unit, a jump request is generated, and the second deployable computing unit to be jumped to is determined.

[0048] Specifically, step S201 includes steps a~c:

[0049] Step a: In response to any user's login operation on the operating interface of the first deployable computing unit, generate login information.

[0050] For example, the user is pod1-user1.

[0051] For example, the user interface is the physical network interface logged in by a certain enterprise.

[0052] In this embodiment, the first deployable computing unit can be a POD or other computing units.

[0053] Among them, POD is the smallest deployable computing unit in container orchestration systems such as Kubernetes. It contains one or more containers with shared storage, network and runtime specifications, and is used to encapsulate tightly coupled containerized applications.

[0054] For example, the first deployable computing unit is used for data storage.

[0055] In this embodiment, login information is a credential used to verify identity and access the system or services.

[0056] The login information includes username, mobile phone number, and password.

[0057] Step b: Verify the login information to determine whether the user has login privileges.

[0058] For example, the username and password are validated to determine whether the user has login privileges.

[0059] Step c: If it is determined that the user has login permission, then in response to the user's navigation operation, a navigation request is generated, and the second deployable computing unit to be navigated to is determined.

[0060] In this embodiment, the second deployable computing unit can be a POD or other computing units.

[0061] For example, the second deployable computing unit is used for data analysis.

[0062] In addition, a third deployable computing unit can be installed as needed; for example, the third deployable computing unit is used for data display.

[0063] S202: Determine the user's employee role from the preset multiple employee roles.

[0064] In this embodiment, the various employee roles include ordinary employees, ordinary administrators, and senior administrators.

[0065] For example, the employee role is either a regular employee or a senior administrator.

[0066] S203: Retrieve the pre-configured permission fence policy from the system database based on the redirection request. The permission fence policy includes at least the set of users allowed to redirect for the employee role and the range of deployable computing units.

[0067] In this embodiment, the permission fence policy is an access control mechanism that restricts the scope of user or system operations through predefined rules. Its core is the principle of least privilege, that is, only granting the minimum privileges required to complete a specific task.

[0068] For example, the scope of deployable computing units for ordinary employees is limited to the first and second deployable computing units, and they only have basic operation permissions for the first and second deployable computing units; the scope of deployable computing units for senior administrators is the first, second, and third deployable computing units, and they have full operation permissions for the first, second, and third deployable computing units.

[0069] S204: If it is determined that the user hits the set of users allowed to jump, and the first deployable computing unit and the second deployable computing unit are within the range of deployable computing units, then obtain the user's corresponding permission configuration information from the first deployable computing unit.

[0070] Specifically, step S204 includes steps a~d:

[0071] Step a: Obtain the user's identity information, the first basic information of the first deployable computing unit, and the second basic information of the second deployable computing unit.

[0072] In this embodiment, the basic information may include information such as number, name, and function.

[0073] Step b: Determine whether the user's identity information matches the user set.

[0074] Step c: If the user identity information matches the user set, then determine whether the first deployable computing unit and the second deployable computing unit are within the range of deployable computing units based on the first basic information and the second basic information.

[0075] Furthermore, if it is determined that the first deployable computing unit and the second deployable computing unit are not within the scope of deployable computing units, the redirection request will be rejected and the user will be prompted with insufficient permissions.

[0076] In this embodiment, the prompt message can be a pop-up window, voice message, or other prompts.

[0077] Step d: If it is determined that the first deployable computing unit and the second deployable computing unit are within the scope of deployable computing units, then obtain the user's corresponding permission configuration information from the first deployable computing unit.

[0078] In this embodiment, the permission configuration information includes detailed permission data such as the resources that the user can access and the operations that can be performed.

[0079] For example, the resources accessible to ordinary employees are the first deployable computing unit and the second deployable computing unit, and the operations they can perform are data storage and data analysis.

[0080] S205: Create any new user within the second deployable computing unit and configure the permission information for the new user.

[0081] For example, the new user is pod2-user.

[0082] S206: After completing the permission configuration information for the new user, the user is directed to the target operation interface on the second deployable computing unit to complete the user's transition between deployable computing units.

[0083] Specifically, step S206 includes steps a~b:

[0084] Step a: After completing the permission configuration information for the new user, generate the target login information for the new user on the first deployable computing unit.

[0085] In this embodiment, the target login information can use the same data as the login information.

[0086] Specifically, step a includes a1 to a2:

[0087] Step a1: After configuring the permission information for the new user, generate the target login information for the new user on the first deployable computing unit; and,

[0088] Step a2: Issue a corresponding short-term access credential to the second deployable computing unit.

[0089] In this embodiment, the short-term access credential is a temporary identity authentication credential, characterized by short validity period, restricted permissions, and dynamic generation.

[0090] Step b: After skipping the verification of the target login information, the user is directed to the target operation interface on the second deployable computing unit according to the preset interface, so as to complete the user's transition between deployable computing units.

[0091] Specifically, after bypassing the verification of the target login information through a specific interface and protocol, the user is directed to the target operation interface on the second deployable computing unit according to the preset interface, so as to complete the user's transition between deployable computing units.

[0092] Specifically, step b includes b1~b2:

[0093] Step b1: After skipping the verification of the target login information, the user is directed to the target operation interface on the second deployable computing unit according to the preset interface and short-term access credentials, so as to complete the user's transition between deployable computing units.

[0094] In this embodiment, the preset interface can be an API interface or other interfaces.

[0095] In this embodiment, short-term access credentials can be considered as replacing the verification of the target login information.

[0096] Step b2: After the transition of the deployable computing unit is complete, destroy the short-term access credentials.

[0097] In addition, for example, when a regular employee attempts to jump to the third deployable computing unit, it will be detected that the regular employee's identity does not meet the jump requirements from the second deployable computing unit to the third deployable computing unit, and the jump request will be rejected with an insufficient permission prompt.

[0098] For example, when a senior administrator navigates to the third deployable computing unit, the system detects that the senior administrator's identity meets the navigation requirements from the second to the third deployable computing unit. Subsequently, a user named pod3-user2 is created in the third deployable computing unit and granted full access permissions. After bypassing the senior administrator's login verification, the senior administrator successfully enters the third deployable computing unit to perform data display and related management operations.

[0099] Furthermore, if a user needs to return to the first deployable computing unit from the second or third deployable computing unit, the same steps described above can be used.

[0100] In summary, the user migration method between deployable computing units provided in this embodiment generates a jump request in response to a user's jump operation on the operation interface of the first deployable computing unit and determines the second deployable computing unit to which the user should jump. It then determines the user's employee role from a set of preset employee roles; retrieves the set of users allowed to jump and the range of deployable computing units corresponding to the employee role from the system database based on the jump request; if the user matches the set of users allowed to jump, and the first and second deployable computing units are within the range of deployable computing units, it obtains the user's corresponding permission configuration information from the first deployable computing unit; creates any new user in the second deployable computing unit and configures the permission configuration information for the new user; after configuring the permission configuration information for the new user, it directs the user to the target operation interface on the second deployable computing unit to complete the user's migration between deployable computing units. By automatically performing user migration based on permission configuration information, it eliminates the need for manually creating user accounts and performing user login and login verification, thus improving the efficiency of user migration between deployable computing units.

[0101] Furthermore, the user hopping method between deployable computing units provided in this embodiment obtains the user's identity information, the first basic information of the first deployable computing unit, and the second basic information of the second deployable computing unit; determines whether the user's identity information matches the user set; if the user's identity information matches the user set, it determines whether the first and second deployable computing units are within the scope of deployable computing units based on the first and second basic information; if the first and second deployable computing units are within the scope of deployable computing units, it obtains the user's corresponding permission configuration information from the first deployable computing unit. Through multiple permission checks, strict control over user hopping is achieved, ensuring that only users with the corresponding permissions can jump between deployable computing units, thus protecting system data security.

[0102] In addition, the user migration method between deployable computing units provided in this embodiment, by skipping the verification of the target login information, directs the user to the target operation interface on the second deployable computing unit according to the preset interface and short-term access credentials, so as to complete the user's migration between deployable computing units. This makes the migration process virtually imperceptible to the user and ensures the smoothness of the operation.

[0103] Figure 3 A flowchart illustrating the user hop method between deployable computing units provided in this application embodiment. Figure 2 In the embodiments of this application, in Figure 2 Based on the provided embodiments, a detailed explanation of the specific implementation method for configuring the permission fence policy in S203 is given. For example... Figure 3 As shown, the method includes:

[0104] S301: Define multiple employee roles and multiple deployable computing units.

[0105] In this embodiment, the discussion of multiple employee roles has been explained in detail in step S202, and will not be repeated here.

[0106] S302: Determine the set of users that are allowed to jump to each type of employee role.

[0107] In this embodiment, the set of users allowed to jump is determined based on requirements.

[0108] S303: Determine the range of deployable computing units corresponding to each type of employee role based on multiple deployable computing units.

[0109] In this embodiment, the discussion on the range of deployable computing units has been explained in detail in step S203, and will not be repeated here.

[0110] S304: Configure permission fence policies based on multiple employee roles, each set of users allowed to jump, and each deployable computing unit range.

[0111] In addition, the configuration process for another permission fence policy also includes steps a~d:

[0112] Step a: Obtain multiple deployable computing units at different business stages.

[0113] For example, different business stages can be data storage, data analysis, or data visualization.

[0114] Step b: Obtain the permission rules corresponding to each deployable computing unit.

[0115] For example, in an IoT platform, the deployable computing unit corresponding to data storage is only allowed to store sensor data, while the deployable computing unit corresponding to data analysis can only perform data cleaning and transformation operations.

[0116] The corresponding permission rules are for storing sensor data or for data cleaning and transformation operations.

[0117] Step c: Configure permissions for the corresponding deployable computing units according to the permission rules to obtain the jump permissions and operation permissions corresponding to each deployable computing unit.

[0118] Step d: Configure permission fence policies based on the jump permissions and operation permissions corresponding to each deployable computing unit.

[0119] In summary, the user migration method between deployable computing units provided in this embodiment determines multiple types of employee roles and multiple deployable computing units; determines the set of users allowed to migrate to each type of employee role; determines the scope of deployable computing units corresponding to each type of employee role based on multiple deployable computing units; and configures permission fence policies based on multiple types of employee roles, each set of users allowed to migrate to, and each scope of deployable computing units. By configuring permission fence policies, unified management and dynamic allocation of user permissions between deployable computing units are achieved, ensuring the synergy and stability of business processing under a multi-deployable computing unit architecture.

[0120] In summary, the user migration method between deployable computing units provided in this embodiment obtains multiple deployable computing units at different business stages; obtains the permission rules corresponding to each deployable computing unit; configures permissions for the corresponding deployable computing units according to the permission rules to obtain the jump permissions and operation permissions corresponding to each deployable computing unit; and configures a permission fence policy according to the jump permissions and operation permissions corresponding to each deployable computing unit. Through the subdivision of permissions at business stages, when users migrate between multiple deployable computing units, they can only access the deployable computing units related to the current business stage, thus avoiding unauthorized operations.

[0121] Figure 4 This is a schematic diagram of the structure of a user transition device between deployable computing units provided in an embodiment of this application. Figure 4 As shown, the user transition device between deployable computing units includes: a generation module 401, a first determination module 402, a retrieval module 403, a first acquisition module 404, a first configuration module 405, and a direction module 406.

[0122] The generation module 401 is used to generate a jump request in response to the user's jump operation on the operation interface of the first deployable computing unit, and to determine the second deployable computing unit to be jumped to.

[0123] The first determining module 402 is used to determine the user's employee role from a set of preset employee roles;

[0124] The retrieval module 403 is used to retrieve a pre-configured permission fence policy from the system database according to the jump request, wherein the permission fence policy includes at least the set of users allowed to jump corresponding to the employee role and the range of deployable computing units;

[0125] The first acquisition module 404 is used to acquire the user's corresponding permission configuration information from the first deployable computing unit if it is determined that the user hits the set of users allowed to jump, and the first deployable computing unit and the second deployable computing unit are within the range of deployable computing units.

[0126] The first configuration module 405 is used to create any new user within the second deployable computing unit and configure permission configuration information for the new user.

[0127] The orientation module 406 is used to direct the user to the target operation interface on the second deployable computing unit after the permission configuration information of the new user is completed, so as to complete the user's transition between deployable computing units.

[0128] In one possible implementation, obtaining module 404 specifically includes:

[0129] The first acquisition unit is used to acquire the user's identity information, the first basic information of the first deployable computing unit, and the second basic information of the second deployable computing unit.

[0130] The first judgment unit is used to determine whether the user identity information matches the user set;

[0131] The second judgment unit is used to determine whether the first deployable computing unit and the second deployable computing unit are within the range of deployable computing units based on the first basic information and the second basic information if the user identity information is determined to match the user set.

[0132] The second acquisition unit is used to acquire the user's corresponding permission configuration information from the first deployable computing unit if it is determined that the first deployable computing unit and the second deployable computing unit are within the scope of deployable computing units.

[0133] In one possible implementation, the orientation module 406 specifically includes:

[0134] The generation unit is used to generate the target login information of the new user on the first deployable computing unit after the permission configuration information of the new user is completed.

[0135] The redirection unit is used to redirect the user to the target operation interface on the second deployable computing unit according to a preset interface after skipping the verification of the target login information, so as to complete the user's transition between deployable computing units.

[0136] In one possible implementation, the generation unit specifically includes:

[0137] The generation unit is used to generate the target login information for the new user on the first deployable computing unit after configuring the permission information for the new user; and...

[0138] The issuing unit is used to issue corresponding short-term access credentials to the second deployable computing unit.

[0139] Accordingly, the orientation unit specifically includes:

[0140] The redirection unit is used to redirect the user to the target operation interface on the second deployable computing unit after skipping the verification of the target login information, based on the preset interface and short-term access credentials, so as to complete the user's transition between deployable computing units.

[0141] The destruction unit is used to destroy short-term access credentials after the transition of a deployable computing unit is completed.

[0142] One possible implementation also includes:

[0143] The second determination module is used to determine multiple types of employee roles and multiple deployable computing units;

[0144] The third determination module is used to determine the set of users who are allowed to jump to each type of employee role;

[0145] The fourth determination module is used to determine the range of deployable computing units corresponding to each type of employee role based on multiple deployable computing units;

[0146] The second configuration module is used to configure permission fence policies based on multiple employee roles, the set of users allowed to jump to, and the scope of each deployable computing unit.

[0147] One possible implementation also includes:

[0148] The first acquisition module is used to acquire multiple deployable computing units at different business stages;

[0149] The second acquisition module is used to acquire the permission rules corresponding to each deployable computing unit;

[0150] The third configuration module is used to configure permissions for the corresponding deployable computing units according to the permission rules, so as to obtain the jump permissions and operation permissions corresponding to each deployable computing unit.

[0151] The fourth configuration module is used to configure permission fence policies based on the jump permissions and operation permissions corresponding to each deployable computing unit.

[0152] In one possible implementation, the generation module 401 specifically includes:

[0153] The first generation unit is used to generate login information in response to any user's login operation on the operation interface of the first deployable computing unit;

[0154] The verification unit is used to verify the login information to determine whether the user has login privileges.

[0155] The second generation unit is used to generate a redirection request in response to the user's redirection operation on the operation interface if it is determined that the user has login permissions, and to determine the second deployable computing unit to which the user should be redirected.

[0156] The apparatus provided in this embodiment can be used to execute the technical solutions of the above method embodiments. Its implementation principle and technical effects are similar, and will not be described again here.

[0157] Figure 5 This is a schematic diagram of the hardware structure of the electronic device provided in an embodiment of this application. Figure 5As shown, the electronic device of this embodiment includes: a processor 501 and a memory 502; the memory stores computer execution instructions; at least one processor executes the computer execution instructions stored in the memory, causing at least one processor to execute the user transition method between deployable computing units as described above.

[0158] Alternatively, the memory 502 can be either standalone or integrated with the processor 501.

[0159] When the memory 502 is set up independently, the electronic device also includes a bus 503 for connecting the memory 502 and the processor 501.

[0160] This application also provides a computer storage medium storing computer execution instructions. When the processor executes the computer execution instructions, the above-described user transition method between deployable computing units is implemented.

[0161] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described user transition method between deployable computing units.

[0162] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or modules, and may be electrical, mechanical, or other forms.

[0163] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to implement the solution of this embodiment according to actual needs.

[0164] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The unit composed of the above modules can be implemented in hardware or in the form of hardware plus software functional units.

[0165] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application.

[0166] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly manifested as execution by a hardware processor, or execution by a combination of hardware and software modules within the processor.

[0167] The memory may include high-speed RAM, and may also include non-volatile storage (NVM), such as at least one disk storage device, and may also be a USB flash drive, external hard drive, read-only memory, disk or optical disc, etc.

[0168] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0169] The aforementioned storage media can be implemented from any type of volatile or non-volatile storage device or a combination thereof, such as Static Random-Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The storage media can be any available medium accessible to general-purpose or special-purpose computers.

[0170] An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Alternatively, the storage medium can be an integral part of the processor. Both the processor and the storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and storage medium can exist as discrete components in an electronic device or host device.

[0171] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0172] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A user hop method between deployable computing units, characterized in that, Applied to electronic devices, including: In response to the user's navigation operation on the first deployable computing unit, a navigation request is generated, and the second deployable computing unit to which the user should navigate is determined. The user's employee role is determined from a set of preset employee roles; The system retrieves a pre-configured permission fence policy from the system database based on the jump request. The permission fence policy includes at least the set of users allowed to jump and the range of deployable computing units corresponding to the employee role. If it is determined that the user matches the set of users allowed to jump, and the first deployable computing unit and the second deployable computing unit are within the range of the deployable computing units, then the permission configuration information corresponding to the user is obtained from the first deployable computing unit; Create any new user within the second deployable computing unit and configure the permission configuration information for the new user; After configuring the permission information for the new user, the user is directed to the target operation interface on the second deployable computing unit to complete the user's transition between deployable computing units.

2. The method according to claim 1, characterized in that, If it is determined that the user matches the set of users allowed to redirect, and the first deployable computing unit and the second deployable computing unit are within the scope of the deployable computing unit, then the permission configuration information corresponding to the user is obtained from the first deployable computing unit, including: Obtain the user's identity information, the first basic information of the first deployable computing unit, and the second basic information of the second deployable computing unit; Determine whether the user identity information matches the user set; If it is determined that the user identity information matches the user set, then it is determined whether the first deployable computing unit and the second deployable computing unit are within the range of the deployable computing unit based on the first basic information and the second basic information; If it is determined that the first deployable computing unit and the second deployable computing unit are within the scope of the deployable computing unit, then the permission configuration information corresponding to the user is obtained from the first deployable computing unit.

3. The method according to claim 1, characterized in that, After configuring the permission information for the new user, the step of directing the user to the target operation interface on the second deployable computing unit to complete the user's transition between deployable computing units includes: After configuring the permission information for the new user, the target login information for the new user is generated on the first deployable computing unit; After skipping the verification of the target login information, the user is directed to the target operation interface on the second deployable computing unit according to the preset interface, so as to complete the user's transition between deployable computing units.

4. The method according to claim 3, characterized in that, After configuring the permission information for the new user, the step of generating the target login information for the new user on the first deployable computing unit includes: After configuring the permission information for the new user, the target login information for the new user is generated on the first deployable computing unit; and... Issue a corresponding short-term access credential to the second deployable computing unit; Accordingly, after skipping the verification of the target login information, redirecting the user to the target operation interface on the second deployable computing unit according to a preset interface to complete the user's transition between deployable computing units includes: After skipping the verification of the target login information, the user is directed to the target operation interface on the second deployable computing unit according to the preset interface and the short-term access credential, so as to complete the user's transition between deployable computing units; After the transition of the deployable computing unit is completed, the short-term access credential is destroyed.

5. The method according to claim 1, characterized in that, The configuration process for the permission fence policy includes: Define multiple employee roles and multiple deployable computing units; Determine the set of users allowed to redirect to each type of employee role; The range of deployable computing units corresponding to each type of employee role is determined based on the multiple deployable computing units; Configure the permission fence policy based on the various employee roles, the sets of users allowed to jump to, and the scope of each deployable computing unit.

6. The method according to claim 5, characterized in that, Also includes: Acquire multiple deployable computing units at different business stages; Obtain the permission rules corresponding to each deployable computing unit; Configure permissions for the corresponding deployable computing units according to the permission rules to obtain the jump permissions and operation permissions corresponding to each deployable computing unit; Configure the permission fence policy according to the jump permissions and operation permissions corresponding to each deployable computing unit.

7. The method according to claim 1, characterized in that, The step of responding to a user's navigation operation on the first deployable computing unit's interface, generating a navigation request, and determining the second deployable computing unit to which the user should navigate, includes: In response to any user's login operation on the operating interface of the first deployable computing unit, login information is generated; The login information is verified to determine whether the user has login privileges. If it is determined that the user has login privileges, then in response to the user's navigation operation on the interface, a navigation request is generated, and the second deployable computing unit to be navigated to is determined.

8. A user transfer device capable of deploying between computing units, characterized in that, Applied to electronic devices, including: The generation module is used to generate a jump request in response to the user's jump operation on the operation interface of the first deployable computing unit, and to determine the second deployable computing unit to jump to. The first determining module is used to determine the user's employee role from a set of preset employee roles; The retrieval module is used to retrieve a pre-configured permission fence policy from the system database according to the jump request, wherein the permission fence policy includes at least the set of users allowed to jump and the range of deployable computing units corresponding to the employee role; The first acquisition module is used to acquire the permission configuration information corresponding to the user from the first deployable computing unit if it is determined that the user hits the set of users allowed to jump, and the first deployable computing unit and the second deployable computing unit are within the range of the deployable computing unit; The first configuration module is used to create any new user within the second deployable computing unit and configure the permission configuration information for the new user. The orientation module is used to, after configuring the permission information of the new user, direct the user to the target operation interface on the second deployable computing unit, so as to complete the user's transition between deployable computing units.

9. An electronic device, characterized in that, include: At least one processor and memory; The memory stores computer-executed instructions; The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the user hop method between deployable computing units as described in any one of claims 1 to 7.

10. A computer storage medium, characterized in that, The computer storage medium stores computer execution instructions, and when the processor executes the computer execution instructions, it implements the user transition method between deployable computing units as described in any one of claims 1 to 7.

Images