Role permission configuration method and device and storage medium

Abstract

The invention discloses a role permission configuration method and device and a storage medium, and the method comprises the steps: registering a tenant, registering an application object of at least one application system belonging to the tenant, registering an associated role, registering at least one application role belonging to the application object, and registering user information of a user; the access authority of the application roles to the application objects is configured, at least one application role belongs to the associated roles, the user and the tenant are bound, and the application objects, the associated roles, the application roles and user information of at least one application system are registered in a unified mode; the access authority of the application role to the application object is uniformly configured, at least one application role is configured to belong to the associated role, the user and the tenant are bound, and the user does not need to perform authority maintenance of different application systems; when the user needs to access one or more application systems, the user only needs to log in with the unified user information instead of account information of different application systems, so that the access efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the field of computers, and in particular to a role authority configuration method, device and storage medium. Background Art

[0002] With the development of information technology and network technology, corporate organizational relationships are becoming more and more complex. The same person has different perspectives and rights under different organizational relationships within the enterprise. There are more and more internal application systems, and these application systems are independent of each other. Users need to configure the account information of each application system between each application system. Each application system must independently maintain permissions for the account information, which is very cumbersome and has low management and configuration efficiency. At the same time, when users access resources of different application systems, they need to log in using the account information of different application systems before they can access them, which is cumbersome and inefficient. Summary of the invention

[0003] In view of this, in order to solve at least one of the above technical problems, an object of the present invention is to provide a role authority configuration method, device and storage medium to improve configuration efficiency.

[0004] An embodiment of the present invention provides a method for configuring role permissions, including:

[0005] In response to the registration instruction, register the tenant, register the application object of at least one application system belonging to the tenant, register the associated role, register at least one application role belonging to the application object, and register the user information of the user;

[0006] In response to the configuration instruction, configure the access rights of the application role to the application object, configure at least one of the application roles to belong to the associated role, and bind the user to the tenant;

[0007] When a user logs in according to the user information and initiates an access request, the tenant is authenticated according to the access request, and the target application object is executed after the authentication passes.

[0008] Further, the registering of the application object of at least one application system belonging to the tenant includes:

[0009] Registering application information of at least one application; the application information at least includes an application code and the tenant to which the application belongs; each application has at least one application role;

[0010] Register resource information of at least one application resource; the resource information at least includes a resource access address and the application to which the application resource belongs.

[0011] Further, configuring the access rights of the application role to the application object includes:

[0012] The access rights of the application role to at least one application resource are configured; wherein the access rights include access rights to one application resource of the application or access rights to multiple application resources of the application.

[0013] Furthermore, the registration-associated role includes:

[0014] Register at least one platform role, and configure the tenant to which the platform role belongs and at least one application role belonging to the platform role;

[0015] Register at least one identity role, and configure the tenant to which the identity role belongs and at least one platform role to which the identity role belongs.

[0016] Further, configuring at least one of the application roles to belong to the associated role includes:

[0017] Configuring at least one of the application roles to belong to the platform role, and configuring the first role authority of the platform role to the at least one of the application roles;

[0018] Configuring a second role permission of the identity role for at least one of the platform roles;

[0019] The first role permission indicates that the platform role is allowed to use at least one of the application roles, and the second role permission indicates that the identity role is allowed to use at least one of the platform roles.

[0020] Further, the performing authority authentication on the tenant according to the access request includes:

[0021] Extract the token of the access request; the token includes the target tenant corresponding to the logged-in user, the application code, and the resource access address of the application resource;

[0022] Determine the target application according to the application code and determine the target application resource under the target application according to the resource access address; the target application object includes the target application and the target application resource;

[0023] According to the target tenant, query the target identity role corresponding to the target application under the target tenant, query all platform roles under the target identity role and all application roles under all platform roles;

[0024] Determine whether all the queried application roles have access rights to the target application resource.

[0025] Further, executing the target application object after the permission authentication is passed includes:

[0026] When at least one application role has access rights to the target application resources, the authority authentication is passed, and the target application resources under the target application are executed.

[0027] The embodiment of the present invention also provides a role authority configuration device, comprising:

[0028] A first response module, configured to respond to a registration instruction, register a tenant, register an application object of at least one application system belonging to the tenant, register an associated role, register at least one application role belonging to the application object, and register user information of the user;

[0029] A second response module is used to respond to the registration instruction, register the tenant, register the application object of at least one application system belonging to the tenant, register the associated role, register at least one application role belonging to the application object, and register the user information of the user;

[0030] When a user logs in according to the user information and initiates an access request, the tenant is authenticated according to the access request, and the target application object is executed after the authentication passes.

[0031] An embodiment of the present invention also provides a role authority configuration device, which includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set are loaded and executed by the processor to implement the method.

[0032] An embodiment of the present invention also provides a computer-readable storage medium, in which at least one instruction, at least one program, a code set or an instruction set is stored, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by a processor to implement the method.

[0033] The beneficial effects of the present invention are:

[0034] By responding to a registration instruction, registering a tenant, registering an application object of at least one application system belonging to the tenant, registering an associated role, registering at least one application role belonging to the application object, and registering the user information of the user, and responding to a configuration instruction, configuring the application role's access rights to the application object, configuring at least one application role to belong to the associated role, and binding the user to the tenant, the application object, associated role, application role, and user information of at least one application system can be uniformly registered, and the application role's access rights to the application object, configuring at least one application role to belong to the associated role, and binding the user to the tenant can be uniformly configured, so that the user does not need to tediously maintain the permissions of different application systems separately, which is conducive to simplifying the permission configuration process and improving configuration efficiency; in addition, when the user logs in according to the user information and initiates an access request, the tenant is authenticated according to the access request, and the target application object is executed after the permission authentication is passed. When the user needs to access the application objects of one or more application systems, he only needs to use unified user information to log in without the need for account information of different application systems, which is conducive to improving access efficiency.

[0035] For better understanding and implementation, the present invention is described in detail below with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 The figure is a flowchart of the steps of the role permission configuration method of the present invention. DETAILED DESCRIPTION

[0037] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0038] The terms "first", "second", "third" and "fourth" etc. in the specification and claims of the present application and the drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

[0039] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0040] like Figure 1 As shown, an embodiment of the present invention provides a role authority configuration method, including steps S100-S200:

[0041] S100 . In response to a registration instruction, register a tenant, register an application object of at least one application system belonging to the tenant, register an associated role, register at least one application role belonging to the application object, and register user information of the user.

[0042] In the embodiment of the present invention, a unified authentication system is designed to register basic information in response to a registration instruction. It should be noted that the registration instruction can be an instruction input by a configuration personnel through a keyboard, a mouse, a touch screen, etc. The unified authentication system is independent of each application system and is an architecture based on the RBAC model. Therefore, it does not depend on a specific application system and can run independently, and does not require modification of the application system, does not affect the normal operation of the application system, and only needs to expose the interface of the unified authentication system to the application system for use.

[0043] In the embodiment of the present invention, the platform supports multi-tenant mode, and different applications and other data are resource isolated according to tenants; basic information registration includes but is not limited to tenants, application objects, information of associated roles, and user information of users, etc. Optionally, registering a tenant includes but is not limited to setting a tenant ID and a tenant name; the user information of a registered user includes but is not limited to user ID, user code, user name, login account, login password, default tenant, etc.

[0044] Optionally, the application object includes an application and application resources under the application, and the application object of at least one application system registered belonging to the tenant in step S100 includes steps S110-S120:

[0045] S110. Register application information of at least one application.

[0046] In the embodiment of the present invention, the application information includes at least the application code, the tenant to which the application belongs (such as the tenant ID), the application ID, the application name, the application status, etc. Each application has at least one application role.

[0047] S120: Register resource information of at least one application resource.

[0048] In the embodiment of the present invention, each application may have at least one corresponding application resource, and the application resource includes but is not limited to menus, API interfaces, models, algorithms, etc.; the resource information at least includes the resource access address, the application to which the application resource belongs, the resource type, and the resource code. Among them, each application has at least one application role. When registering an application role, the application role ID, application role code, application role name, and the application to which it belongs can be set. The configuration personnel can uniformly configure the application role for one or more applications in the unified authentication system according to their own needs, without having to log in to different application systems to configure different applications separately, which is convenient and fast.

[0049] In the embodiment of the present invention, the association role can be used to associate with the application role. The application role belonging to the association role can be used through the association role. Optionally, the association role includes a platform role and an identity role. The registration of the association role in step S100 includes steps S130-S140:

[0050] S130: Register at least one platform role, and configure the tenant to which the platform role belongs and at least one application role belonging to the platform role.

[0051] Optionally, one or more platform roles can be registered on the unified authentication system, and each platform role is configured with the tenant to which the platform role belongs, one or more application roles to which the platform role belongs, the platform role ID, the platform role code, the platform role name, etc. It can be understood that the platform role is a collection of multiple application roles under one tenant, and can include one or more application roles under one application, or one or more application roles under multiple applications (cross-applications). Therefore, one or more application resources corresponding to one or more applications can be accessed through the platform role.

[0052] S140: Register at least one identity role, and configure the tenant to which the identity role belongs and at least one platform role to which the identity role belongs.

[0053] Optionally, you can register one or more identity roles on the unified authentication system, configure the tenant to which the identity role belongs, one or more platform roles to which the identity role belongs, the identity role ID, the identity role code, the identity role name, etc. It should be noted that the identity role can be directly configured with the user, indicating the role information of the user under the tenant, and all platform roles under the identity role can be used through the identity role.

[0054] S200: In response to the configuration instruction, configure the access rights of the application role to the application object, configure at least one application role to belong to the associated role, and bind the user to the tenant.

[0055] Similarly, the configuration instructions can be instructions input by the configuration personnel through keyboard, mouse, touch screen, etc., and the unified authentication system can perform corresponding configuration in response to the configuration instructions. It should be noted that when the user logs in according to the user information and initiates an access request, the tenant is authenticated according to the access request, and the target application object is executed after the authentication passes.

[0056] Optionally, configuring the access rights of the application role to the application object in step S200 includes step S210:

[0057] S210: Configure access rights of the application role to at least one application resource.

[0058] Optionally, the access rights include access rights to one application resource of the application or access rights to multiple application resources of the application. For example, the access rights to one application resource can be configured for the application role, and the application role only has access rights to one application resource, or the access rights to multiple application resources can be configured for the application role, and the application role has access rights to multiple application resources. This can be determined according to the needs of the configuration personnel, which is convenient and quick.

[0059] Optionally, configuring at least one application role to belong to the associated role in step S200 includes steps S220-S230:

[0060] S220: Configure at least one application role to belong to the platform role, and configure the first role permission of the platform role to the at least one application role.

[0061] Specifically, at least one application role is configured to belong to the platform role, for example, the corresponding application role ID can be configured under the corresponding platform role ID, and the first role permission of the platform role to at least one application role can be configured. It should be noted that the first role permission indicates that the platform role is allowed to use at least one application role.

[0062] S230: Configure the second role permission of the identity role for at least one platform role.

[0063] Specifically, a second role permission of the identity role to at least one platform role is configured, and the second role permission indicates that the identity role is allowed to use at least one platform role.

[0064] In an embodiment of the present invention, the user is bound to the tenant in step S200. The relationship between tenants and users is many-to-many. Through association and binding, one user can configure multiple tenants. When the user logs in through user information, the user can use the associated and bound tenant and use the tenant's permissions to use the role under the tenant to access the application and the application resources of the application.

[0065] In an embodiment of the present invention, when a user logs in according to user information and initiates an access request, specifically: when it is necessary to use an application and an application resource of the application, an access request is sent to the application system. At this time, based on the interface provided by the unified authentication system to the application system, the user can use the user information to log in to the unified authentication system, the unified authentication system obtains the access request, and then performs permission authentication on the tenant based on the access request.

[0066] Optionally, the request may be initiated by a user client, or by a microservice between applications, or by a remote call across applications, without specific limitation.

[0067] Optionally, the tenant is authenticated according to the access request, including steps S310-S340:

[0068] S310: Extract the access request token.

[0069] Optionally, the token includes the target tenant (eg, target tenant ID) corresponding to the logged-in user, the application code, and the resource access address of the application resource, etc. Optionally, S310 may be executed by the application system and then sent to the unified authentication system, or may be executed by the unified authentication system.

[0070] S320: Determine a target application according to the application code and determine a target application resource under the target application according to the resource access address.

[0071] It should be noted that the target application object includes a target application and a target application resource. Specifically, the target application to be accessed can be determined according to the application code, and the target application resource to be accessed under the target application can be determined according to the resource access address.

[0072] Optionally, if the target application object has been removed from the shelves, the removal information will be returned.

[0073] S330: query the target identity role corresponding to the target application under the target tenant according to the target tenant, query all platform roles under the target identity role, and query all application roles under all platform roles.

[0074] S340: Determine whether all the queried application roles have access rights to the target application resources.

[0075] Specifically, the target identity role corresponding to the target application under the target tenant can be queried according to the tenant ID of the target tenant, and all platform roles under the target identity role and all application roles under all platform roles can be queried. Then, all application roles are queried to see whether they have access rights to the target application resources. If all application roles do not have access rights to the target application resources, a failure message is returned.

[0076] In the embodiment of the present invention, when the authority authentication is passed, executing the target application object specifically includes S350:

[0077] S350: When at least one application role has access rights to the target application resources and the authority authentication is passed, the target application resources under the target application are executed.

[0078] Specifically, when at least one application role has access rights to the target application resource, a successful authentication message is returned, and then the application system can execute the target application object, thereby realizing the function that the user wants to use. It is understandable that when a user needs to use different application systems, in fact, he only needs to use the same user information to log in to the unified authentication system to perform permission authentication and determine whether he has the permission, which is convenient and fast; the configuration personnel only need to configure the access rights of all application systems of different users and tenants on the unified authentication system, which is highly efficient.

[0079] Compared with the prior art, the role authority configuration method of the embodiment of the present invention:

[0080] 1) Through a unified permission system - unified authentication system, users, tenants, identity levels, various roles, and application resources (menus, API interfaces) are used as independent objects to form a unified permission management system that supports multiple tenants and different systems and applications across tenants. This can achieve accurate permission verification control of unified resources and data under different tenant states for logged-in users, and unified management of all sources of user permissions. At the same time, it can achieve the effect of hot-swappable control of application system permissions, eliminating the problem of repeated account authentication and permissions at many enterprise and platform levels.

[0081] 2) When the enterprise's existing application system is connected, it only needs to register the new system to the unified authentication system, register the application resources of the new system and new application, and perform unified configuration distribution and recycling in the unified authentication system. When the user logs in to the unified authentication system, the unified authentication system verifies whether he has the authority to access the resource.

[0082] 3) You can set up a shared identity role to expose the identity role to other tenants, so that users in other tenants can also use the permissions of the application.

[0083] 4) Unify the entry and exit management of user information, permission information and other contents, and combine and call different application systems and applications as needed to form a large system with complex functions.

[0084] 5) The unified authentication system is an independent system. Therefore, it can be called at any time and arbitrarily for verification in the business program logic. In a single application, it can be directly intercepted and verified in the application. In a distributed system, verification can also be implemented at the gateway level. By exposing the interface to the application system, it can support application systems in any language.

[0085] The embodiment of the present invention also provides a role authority configuration device, comprising:

[0086] A first response module, configured to respond to a registration instruction, register a tenant, register an application object of at least one application system belonging to the tenant, register an associated role, register at least one application role belonging to the application object, and register user information of the user;

[0087] A second response module is used to respond to the registration instruction to register the tenant, register the application object of at least one application system belonging to the tenant, register the associated role, register at least one application role belonging to the application object, and register the user information of the user;

[0088] Among them, when the user logs in according to the user information and initiates an access request, the tenant is authenticated according to the access request, and the target application object is executed when the authentication passes.

[0089] The contents of the above method embodiments are all applicable to the present device embodiments. The functions specifically implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments, and will not be repeated herein.

[0090] An embodiment of the present invention also provides another role authority configuration device, which includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by the processor to implement the role authority configuration method of the aforementioned embodiment.

[0091] The contents of the above method embodiments are all applicable to the present device embodiments. The functions specifically implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments, and will not be repeated herein.

[0092] An embodiment of the present invention also provides a computer-readable storage medium, which stores at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by a processor to implement the role authority configuration method of the aforementioned embodiment.

[0093] The embodiment of the present invention also provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. The processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the role permission configuration method of the above embodiment.

[0094] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0095] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0096] In the several embodiments provided in the present 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 only schematic, for example, the division of units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point, the coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms. The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, each functional unit in each embodiment of the present application can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0097] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including multiple instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of each embodiment method of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store programs.

[0098] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some of the technical features therein by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A role authority configuration method, characterized in that: include: In response to the registration instruction, register the tenant, register the application object of at least one application system belonging to the tenant, register the associated role, register at least one application role belonging to the application object, and register the user information of the user; In response to the configuration instruction, configure the access rights of the application role to the application object, configure at least one of the application roles to belong to the associated role, and bind the user to the tenant; When a user logs in according to the user information and initiates an access request, the tenant is authenticated according to the access request, and the target application object is executed after the authentication passes.

2. The role authority configuration method according to claim 1, characterized in that: The application object registered in at least one application system belonging to the tenant includes: Registering application information of at least one application; the application information at least includes an application code and the tenant to which the application belongs; each application has at least one application role; Register resource information of at least one application resource; the resource information at least includes a resource access address and the application to which the application resource belongs.

3. The role authority configuration method according to claim 2 is characterized in that: The configuring the access rights of the application role to the application object includes: The access rights of the application role to at least one application resource are configured; wherein the access rights include access rights to one application resource of the application or access rights to multiple application resources of the application.

4. The role authority configuration method according to claim 1 is characterized in that: The registration-associated role includes: Register at least one platform role, and configure the tenant to which the platform role belongs and at least one application role belonging to the platform role; Register at least one identity role, and configure the tenant to which the identity role belongs and at least one platform role to which the identity role belongs.

5. The role authority configuration method according to claim 4 is characterized in that: The configuring at least one of the application roles to belong to the associated role includes: Configuring at least one of the application roles to belong to the platform role, and configuring the first role authority of the platform role to the at least one of the application roles; Configuring a second role permission of the identity role for at least one of the platform roles; The first role authority indicates that the platform role is allowed to use at least one of the application roles, and the second role authority indicates that the identity role is allowed to use at least one of the platform roles.

6. The role authority configuration method according to claim 4 is characterized in that: The performing authority authentication on the tenant according to the access request includes: Extract the token of the access request; the token includes the target tenant corresponding to the logged-in user, the application code, and the resource access address of the application resource; Determine the target application according to the application code and determine the target application resource under the target application according to the resource access address; the target application object includes the target application and the target application resource; According to the target tenant, query the target identity role corresponding to the target application under the target tenant, query all platform roles under the target identity role and all application roles under all platform roles; and determine whether all the queried application roles have access rights to the target application resources.

7. The role authority configuration method according to claim 6 is characterized in that: The executing the target application object after the permission authentication is passed includes: When at least one application role has access rights to the target application resources, the authority authentication is passed, and the target application resources under the target application are executed.

8. A role authority configuration device, characterized in that: include: A first response module, configured to respond to a registration instruction, register a tenant, register an application object of at least one application system belonging to the tenant, register an associated role, register at least one application role belonging to the application object, and register user information of the user; A second response module is used to respond to the registration instruction, register the tenant, register the application object of at least one application system belonging to the tenant, register the associated role, register at least one application role belonging to the application object, and register the user information of the user; When a user logs in according to the user information and initiates an access request, the tenant is authenticated according to the access request, and the target application object is executed after the authentication passes.

9. A role authority configuration device, characterized in that: The role authority configuration device includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement the method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that: The storage medium stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement the method as described in any one of claims 1-7.

Images