WO2024140916A1

WO2024140916A1 - Internet of things permission matrix model and interaction method thereof

Info

Publication number: WO2024140916A1
Application number: PCT/CN2023/142773
Authority: WO
Inventors: 赵金鹏; 钱长杰; 丁霞; 朱明�
Original assignee: 天翼物联科技有限公司
Priority date: 2022-12-29
Filing date: 2023-12-28
Publication date: 2024-07-04
Also published as: CN116094787A

Abstract

The application discloses an Internet of Things permission matrix model and an interaction method thereof, and can be widely applied to the technical field of Internet of Things. The Internet of Things permission matrix model comprises: distributed platform management, the distributed platform management being used for managing information of each platform in a Internet of Things system; permission code management, the permission code management being used for managing permission codes in the Internet of Things system; menu management, the menu management being used for managing menu organization level information in the Internet of Things system; a tenant permission group, the tenant permission group being used for managing associated tenant permission information in the Internet of Things system; universal role management, the universal role management being used for maintaining the universal role type and a permission code of the universal role in the Internet of Things system. By means of the present Internet of Things permission matrix model, convenient maintenance of the system permission matrix can be implemented, so as to simplify the permission configuration process, allow an operator to conveniently maintain the default permission of each post role, and improve the operation efficiency.

Description

Internet of Things Permission Matrix Model and Its Interaction Method

Technical Field

The present application relates to the technical field of Internet of Things, and in particular to an Internet of Things permission matrix model and an interaction method thereof.

Background technique

In the related technologies, in the process of developing IoT systems, the functions are becoming more and more abundant, and each menu button and interface has important significance. At the same time, the roles of people involved in the system are becoming more and more extensive, and different groups of people need to use some or all functions in the IoT system. However, the permission configuration process in the current system is relatively technical, which makes it difficult for users to modify.

Summary of the invention

The present application aims to solve at least one of the technical problems existing in the prior art. To this end, the present application proposes an Internet of Things permission matrix model and an interaction method thereof, which can simplify the permission configuration process.

On the one hand, the embodiment of the present application provides an Internet of Things permission matrix model, including:

Distributed platform management, which is used to manage the information of each platform in the Internet of Things system;

Permission code management, which is used to manage permission codes in the Internet of Things system;

Menu management, the menu management is used to manage menu organization level information of the Internet of Things system;

A tenant permission group, which is used to manage the associated tenant permission information in the Internet of Things system;

Universal role management, which is used to maintain universal role types and universal role permission codes in the Internet of Things system.

In some embodiments, the management of information of each platform in the Internet of Things system includes:

Manage the name and identification information of each platform in the IoT system.

In some embodiments, managing the permission code in the Internet of Things system includes:

Manage the function menu permissions, button permissions, and interface permissions used for access in the IoT system.

In some embodiments, the menu organization level information includes a menu level, a button level, or an interface level.

In some embodiments, managing the associated tenant permission information in the IoT system includes:

When a new tenant successfully applies for registration, a tenant permission group corresponding to the new tenant is generated, and a corresponding general role is generated in the tenant permission group.

On the other hand, an embodiment of the present application provides an interactive method of an Internet of Things permission matrix model, comprising the following steps:

Initialize general role permissions;

Distributed platform permissions initialization;

Configure extended permissions.

In some embodiments, the general role permission initialization includes:

Collect menu codes, button codes and role codes of common characters;

Configuring the menu code, the button code and the role code to the Internet of Things authority matrix model;

After entering the centralized platform, the menu code, the button code and the role code are verified for validity.

In some embodiments, the distributed platform permission initialization includes:

After completing the creation of a new distributed platform, determine the platform that needs to reuse permissions and export the platform permission matrix file;

The platform permission matrix file is imported into the newly created distributed platform to generate corresponding menus, buttons, interfaces, general roles and permission codes.

In some embodiments, configuring the extended permissions includes:

When new functions are added to the IoT system, permissions are synchronized in the general roles.

In some embodiments, the permission synchronization includes checking partial or full role synchronization, incremental or full synchronization, synchronization of all tenants or part of tenants, and synchronization to a distributed platform.

The IoT permission matrix model provided in the embodiment of the present application has the following beneficial effects:

By setting up distributed platform management, permission code management, menu management, tenant permission groups and general role management in the IoT permission matrix model, convenient maintenance of the system permission matrix can be achieved, thereby simplifying the permission configuration process, making it easier for operators to maintain the default permissions of each position role and improving operational efficiency.

Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application.

BRIEF DESCRIPTION OF THE DRAWINGS

The present application is further described below with reference to the accompanying drawings and embodiments, wherein:

FIG1 is a schematic diagram of an Internet of Things permission matrix model according to an embodiment of the present application;

FIG2 is a flow chart of an interactive method of an Internet of Things permission matrix model according to an embodiment of the present application;

FIG3 is a schematic diagram of the interaction among the centralized platform, the authority matrix model and the distributed platform according to an embodiment of the present application.

Detailed ways

The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be understood as limiting the present application.

In the description of the present application, it should be understood that descriptions involving orientation, such as up, down, front, back, left, right, etc., indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present application.

In the description of this application, "several" means more than one, "many" means more than two, "greater than", "less than", "exceed", etc. are understood to exclude the number itself, and "above", "below", "within", etc. are understood to include the number itself. If there is a description of "first" or "second", it is only used for the purpose of distinguishing technical features, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features.

In the description of this application, unless otherwise clearly defined, terms such as setting, installing, connecting, etc. should be understood in a broad sense, and technicians in the relevant technical field can reasonably determine the specific meanings of the above terms in this application based on the specific content of the technical solution.

In the description of the present application, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

Among the related technologies, the application of IoT has become more and more common in today's society and has penetrated into the daily life of the frontline. As the intermediate link for uploading IoT device data and sending and transmitting application client instructions, the importance of IoT system has become more and more prominent.

During the development of the Internet of Things system, the functions are becoming more and more abundant. Each menu button and interface has its important significance. At the same time, the roles of the people involved in the system are becoming more and more extensive. Different people need to use some or all of the functions in the Internet of Things system.

In order to solve the complex permission definition in the IoT system and the subsequent permission allocation control after the system function expansion, it is particularly important to realize the allocation of relevant permissions for specific and non-specific roles to view and operate. At the same time, the relevant permissions of distributed platforms in different provinces are similar, so how to quickly allocate specific permissions is also very important.

Based on this, referring to Figure 1, an embodiment of the present application provides an Internet of Things permission matrix model, including distributed platform management, permission code management, menu management, tenant permission groups and general role management.

Specifically, distributed platform management is used to manage the information of each platform in the IoT system, such as the name and Identification information. The platform includes the centralized platform and each distributed platform.

Permission code management is used to manage the permission codes of various functions in the IoT system, and is used to actually control the function menu permissions, button permissions or interface permissions that users can access and use, including permission code names, permission codes, etc.

Menu management is used to manage the menu organization level information of the IoT system. In this embodiment, the menu in the IoT system includes a menu organization level, covering multiple levels of dimensions, and the menu organization level information includes menu level, button level, and interface level. Create fields including name, type, resource code, permission code, sort, and remarks.

The tenant permission group is used to manage the associated tenant permission information in the IoT system. In this embodiment, when a new tenant successfully applies for registration, a tenant permission group will be automatically generated, and the corresponding general role will be generated by default in the tenant permission group and the general role permissions will be automatically maintained. Tenants are supported to customize roles within the permission range of the general role, and customized role permissions are granted to tenant members. When granting roles, operators are supported to grant permissions at the menu level, button interface level, and permission code. The system defaults to the permission code corresponding to the menu, button, and interface.

General role management is used to maintain general role types and permission codes related to general roles in the IoT system.

Based on the IoT permission matrix model shown in FIG1 , as shown in FIG2 , the embodiment of the present application provides an interaction method of the IoT permission matrix model, including but not limited to the following steps:

Step S210, initializing general role permissions;

In an embodiment of the present application, when the general role permissions are initialized, the menu codes, button codes, and role codes of the general roles can be collected; the menu codes, button codes, and role codes are configured to the Internet of Things permission matrix model; and after entering the intensive platform, the menu codes, button codes, and role codes are checked for validity. It can be understood that the interactive method provided in the embodiment of the present application includes providing a set of permission matrix model tables, involving id (id corresponding to menus, buttons, and interfaces), organizational structure levels (menu levels, button levels, interface levels), general roles, and role codes. After collecting the menu, button, and interface permission matrices related to each general role, this embodiment maintains them in the model. Then log in to the intensive platform, select the system to be imported (such as the operation background, console, etc.) on the permission maintenance page, and the system performs data validity verification. After the verification is successful, the permission matrix import is completed to achieve the maintenance of the default permissions of each general role.

Step S220: Distributed platform permissions are initialized;

In an embodiment of the present application, after completing the construction of a new distributed platform, this embodiment determines the platform that needs to reuse permissions and exports the platform permission matrix file; then imports the platform permission matrix file into the new distributed platform to generate corresponding menus, buttons, interfaces, general roles and permission codes. It can be understood that intensive or distributed platforms support the export and import of permission matrix models. After the newly built distributed platform is built, first select the platform that needs to reuse permissions, click the system permission matrix menu in the corresponding system, export the platform permission matrix file, including the corresponding general roles, role codes and corresponding menus, buttons, interface id related information, complete the import in the newly built distributed platform, and after successful verification, the corresponding menus, buttons, and interface ids will be automatically generated. Buttons, interfaces, common roles and corresponding permission codes.

Step S230: configure extended permissions.

In an embodiment of the present application, when a new function is determined for the IoT system, permission synchronization is performed at the general role. Among them, permission synchronization includes checking some or all role synchronization, incremental or full synchronization, synchronization of all tenants or some tenants, and synchronization to a distributed platform. It is understandable that when the IoT system expands and develops new functions, permission synchronization is supported at the general role. Among them, permission synchronization supports checking some or all role synchronization, incremental or full synchronization, synchronization of all tenants or some tenants, and synchronization to a distributed platform.

In some embodiments, when the interaction method of FIG. 2 is performed on the centralized platform, the authority matrix model, and the distributed platform, as shown in FIG. 3 , the following steps are included but are not limited to:

System initialization, initializing the basic initial capabilities of the system, such as the IAM function module;

The operator creates an authorization code in the IAM module and selects the corresponding authorization code management system;

Operators create menus, buttons, and interfaces in menu management and maintain their corresponding permission codes;

Operation personnel configure default roles in general role management, such as tenant administrator, tenant member, operation administrator, operation specialist, and other general roles.

The operator performs permission matrix maintenance and first exports the permission matrix model of the system, including id, menu, button, interface organization structure, general role and role code. In the exported permission matrix model table, the permissions required by each role are maintained and imported into the system.

Operation personnel can update and maintain permissions for configured general roles and permissions. Click on the page to view the menu organization structure, button interface organization structure, and permission code, and check the corresponding menus, buttons, and interfaces for each general role according to operation requirements. The system automatically adds the respective permission codes to the role.

After the distributed platform is built, the operator exports its permission matrix model in the centralized platform or other distributed platforms, and imports it into the new distributed platform to complete the distributed platform's menus, common roles, permission codes and other permission initialization work.

For new features developed for the IoT system, operators can click the Sync button in General Role Management and select partial or full roles, incremental or full permissions, all or some tenants, and which distributed platforms to synchronize to.

In some exemplary scenarios, a company proposes to deploy a new distributed system in a certain province. The operator exports the permission matrix model in the intensive platform, confirms that the menu, button, and interface permissions of the common roles involved in the permission matrix are correct, and then imports them into the newly built distributed system, thus completing the permission initialization of the new distributed system.

At the same time, after the permissions are initialized, auditors will regularly audit the permissions of each role in subsequent operations. Auditors only need to export the platform's permission matrix and check whether each role's sensitive permissions such as editing, exporting, and reviewing are compliant. During the audit process, the role's non-compliant menus, buttons, and interface permissions can be eliminated, and the compliant permission matrix can be re-imported into the system. The system automatically replaces the role's original permissions with new permissions.

It can be seen that the embodiment of the present application provides an interactive method for the Internet of Things permission matrix model. By maintaining a set of permission matrices of an intensive platform, including setting various permission codes, role management, and menu button interface management of the intensive platform, the permission matrix configuration can be completed. Then, the role permissions can be initialized after the creation of a new tenant on the intensive platform, and the differentiated configuration of the common role permissions between tenants can be realized. At the same time, it can solve the problem that all role permissions need to be re-maintained after the existing distributed system is built.

In addition, the permission matrix built can help operators get rid of the technical configuration method in the existing permission configuration process, and solve the differences in the correspondence between the permission code and the menus, buttons, and interfaces visible to actual users. This will enable operators to configure what they see is what they get, ensuring the accuracy and convenience of permission configuration.

In summary, this embodiment has the following beneficial effects:

First, through the construction of the IoT distributed permission matrix model, convenient maintenance of the system permission matrix can be achieved, which makes it convenient for operators to maintain the default permissions of various job roles and improve operational efficiency.

Second, after the permission matrix model is built, the permission matrix model can be exported, and regular permission audits can be conducted to reclaim excess permissions and grant compliance permissions after the audit.

Third, the permission matrix model can also realize the permission initialization work such as menus, buttons, interfaces, permission codes, etc. of the new distributed platform, greatly improving operational efficiency.

Fourthly, the permission matrix interaction method supports checking based on the menu, button, and interface organizational structure. The system automatically assigns the corresponding permission code to the checked one, which can reduce the inconsistency between the permission code checked by the current system operator and the actual required permissions, so that what you see is what you get.

Fifth, the permission matrix interaction method supports diversified synchronization operations of permissions, including incremental/full permission synchronization, synchronization of permissions of all tenants/partial tenants, etc., which greatly simplifies the tedious work of empowering operators.

The embodiments of the present application are described in detail above in conjunction with the accompanying drawings, but the present application is not limited to the above embodiments. Various changes can be made within the knowledge of ordinary technicians in the relevant technical field without departing from the purpose of the present application. In addition, the embodiments of the present application and the features in the embodiments can be combined with each other without conflict.

Claims

An Internet of Things permission matrix model, including:

Distributed platform management, which is used to manage the information of each platform in the Internet of Things system;

Permission code management, which is used to manage permission codes in the Internet of Things system;

Menu management, the menu management is used to manage menu organization level information of the Internet of Things system;

A tenant permission group, which is used to manage the associated tenant permission information in the Internet of Things system;

Universal role management, which is used to maintain universal role types and universal role permission codes in the Internet of Things system.
According to the IoT authority matrix model of claim 1, the management of information of each platform in the IoT system includes:

Manage the name and identification information of each platform in the IoT system.
According to the Internet of Things permission matrix model of claim 1, wherein the management of permission codes in the Internet of Things system comprises:

Manage the function menu permissions, button permissions, and interface permissions used for access in the IoT system.
According to the Internet of Things permission matrix model according to claim 1, wherein the menu organization level information includes menu level, button level or interface level.
According to the IoT permission matrix model of claim 1, the step of managing the associated tenant permission information in the IoT system comprises:

When a new tenant successfully applies for registration, a tenant permission group corresponding to the new tenant is generated, and a corresponding general role is generated in the tenant permission group.
An interactive method for an Internet of Things permission matrix model, comprising the following steps:

Initialize general role permissions;

Distributed platform permissions initialization;

Configure extended permissions.
According to the interactive method of the Internet of Things permission matrix model according to claim 6, wherein the general role permission initialization includes:

Collect menu codes, button codes and role codes of common characters;

Configuring the menu code, the button code and the role code to the Internet of Things authority matrix model;

After entering the centralized platform, the menu code, the button code and the role code are checked for validity.
According to the interactive method of the Internet of Things permission matrix model according to claim 6, wherein the distributed platform permission initialization includes:

After completing the creation of a new distributed platform, determine the platform that needs to reuse permissions and export the platform permission matrix file;

The platform permission matrix file is imported into the newly created distributed platform to generate corresponding menus, buttons, interfaces, general roles and permission codes.
According to the interactive method of the Internet of Things permission matrix model according to claim 6, wherein the configuring of the extended permissions comprises:

When new functions are added to the IoT system, permissions are synchronized in the general roles.
According to the interactive method of the Internet of Things permission matrix model according to claim 9, the permission synchronization includes checking some or all role synchronization, incremental or full synchronization, synchronization of all tenants or some tenants, and synchronization to a distributed platform.