A cross-tenant customized address book method for enterprise-level Internet of Things platform

Abstract

The present application relates to a method for customizing a cross-tenant address book on an enterprise-level IoT platform, which creates a new sub-tenant under a source tenant, customizes the address book function page, creates a new organizational structure tree, mounts a certain organizational node of the "source tenant" on a certain node, and renders the new organizational structure in real time. This is achieved by linking the organizational structures under different tenants and only saving the relationship view; the organizational structure under the source organization is not real data under the sub-tenant, but a reference connection, so there will be no redundancy and low cost; the data of the sub-tenant will be updated in real time because of the reference to the source data, without delay; the source data will not be transferred and is still under the source tenant, so it is safer; the view stores the association relationship, so the underlying operation of checking is simplified, and the custom page will be displayed in real time after checking.

Description

Technical Field

[0001] The present disclosure relates to the field of Internet of Things communication technology, and in particular to a method for customizing a cross-tenant address book on an enterprise-level Internet of Things platform and an electronic device. Background Art

[0002] In many pass platforms that support multi-tenancy, especially the enterprise-level IoT operating system platform (iSysCore OS enterprise-level IoT platform) where the present invention is located, there may be a demand for one enterprise to collaborate with several other enterprises to complete a project, so it is possible that a project of Party A's company will contact departments under multiple enterprises.

[0003] In the existing technology, although the communication solutions for multi-tenants of the IoT platform, such as WeChat for Enterprise and DingTalk, can achieve a certain degree of multi-tenant application communication, many software products on the market either do not support multi-tenant and cross-tenant logic; or cannot guarantee that new custom address books can be generated in real time, such as WeChat for Enterprise and DingTalk, because they all copy the tenant organizational structure and the corresponding users to the new tenant. The more complex the structure and the more users there are, the longer the waiting time.

[0004] Therefore, the current implementation solutions on the market still have the following shortcomings:

[0005] Difficult to implement: Most pass platforms cannot handle complex cross-tenant business scenarios;

[0006] High cost: After copying the organizational structure of the source organization to the new tenant, a lot of redundant data will be generated, which results in high maintenance costs.

[0007] Delay: When the same organization information or organization members change under different tenants, it is difficult for other tenants to perceive it efficiently and in real time.

[0008] Unsafe: The data of the source tenant is copied to the new tenant, which may cause security risks;

[0009] Low efficiency: When customizing a new architecture, the page may freeze, the interface may time out, and data loading may be slow due to the large amount of data from the source tenant. Summary of the invention

[0010] In order to solve the above problems, the present application proposes a method, system and electronic device for cross-tenant customized address book on an enterprise-level Internet of Things platform.

[0011] On the one hand, the present application proposes a method for customizing a cross-tenant address book on an enterprise-level Internet of Things platform, which is characterized by comprising the following steps:

[0012] S1, collect original data sets of different tenants and applications;

[0013] S2. Parse and read the mapping relationship between the data of each tenant and the application in the original data set, and build a corresponding view data set based on the mapping relationship between the data of each tenant and the application, so that the view data set displays the mapping relationship between the data of each tenant and the application through a view;

[0014] S3. By customizing the tenant address book, the view data set is regenerated into a new address book tree of each tenant and application and rendered and output.

[0015] Preferably, in step S3, the method for configuring the custom tenant address book includes:

[0016] Start creating a cross-tenant collaboration team and enter the custom address book page;

[0017] Create a new tenant and apply to the platform for permission to associate the tenant:

[0018] If the platform does not agree to the request, the creation fails and you need to modify it and reapply;

[0019] If the platform agrees to the request, proceed to the next step;

[0020] Set up a new tenant address book: Check the organizational structure of the corresponding tenant in the tenant list, and generate a custom address book for the new tenant based on the checked items;

[0021] Send the new tenant's custom address book to the backend, perform backend data operations, configure the communication for the new tenant's custom address book, and obtain the custom tenant address book;

[0022] The configuration is complete and the subtenant is created.

[0023] Preferably, the custom address book page uses virtual directory technology to display the tree structure.

[0024] Preferably, in step S4, after generating the custom address book tree of the new tenant, the following is further included:

[0025] The customized address book is sent to the front end, and the front end dynamically displays the customized address book.

[0026] Preferably, the sending of the customized address book of the new tenant to the background, performing background data operation, performing communication configuration for the customized address book of the new tenant, and obtaining the customized tenant address book includes:

[0027] Reading the view data about the new tenant in the custom address book;

[0028] Determine the communication root node of the new tenant according to the mapping relationship between the new tenant and the data of the tenant and the application shown in the view data of the new tenant;

[0029] The communication root node of the new tenant is saved in the organization tenant relationship table, and the root node identifier of the new tenant is changed in the system organization table to complete the communication configuration of the new tenant, obtain the custom tenant address book of the new tenant and save it to the database cluster.

[0030] Preferably, S3, by customizing the tenant address book, regenerating a new address book tree of each tenant and application from the view data set and rendering and outputting it, includes:

[0031] Start a scheduled task for new tenant communications;

[0032] Read the custom tenant address book of the new tenant, and query the communication IDs of other tenants and organizations associated with the new tenant ID through the new tenant ID from the address book tree of the new tenant;

[0033] Traverse the communication ID of the organization and get the sub-organization;

[0034] Render the sub-tree of the sub-organization as the entire address book tree, and query to obtain the address book tree of the new tenant;

[0035] Query completed.

[0036] In another aspect, the present application provides an electronic device, comprising:

[0037] processor;

[0038] a memory for storing processor-executable instructions;

[0039] Wherein, the processor is configured to implement the method for customizing a cross-tenant address book on an enterprise-level Internet of Things platform when executing the executable instructions.

[0040] On the other hand, the present application further proposes a computer-readable storage medium, in which executable instructions are stored. When the executable instructions are executed, a method for customizing a cross-tenant address book for an enterprise-level Internet of Things platform is implemented.

[0041] Technical effects of the present invention:

[0042] The enterprise-level Internet of Things operating system platform of the present invention customizes the address book across tenants by creating a new sub-tenant under the source tenant, customizing the address book function page, creating a new organizational structure tree, mounting a certain organizational node of the "source tenant" on a certain node, and rendering the new organizational structure in real time.

[0043] The present invention can achieve the following technical effects:

[0044] The present invention uses clever view thinking to link the organizational structures under different tenants and only save the relationship view to achieve this;

[0045] The organizational structure under the source organization is not real data under the subtenant, but a reference connection, so it does not cause redundancy and low cost;

[0046] The data of the subtenant will be updated in real time without delay because of the reference to the source data;

[0047] The source data will not be transferred and remains under the source tenant, so it is more secure;

[0048] The view stores the association relationship, so the underlying operation of checking is simplified, and the custom page will be displayed in real time after checking.

[0049] Further features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate exemplary embodiments, features, and aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.

[0051] Figure 1 The following is an instruction set operating system architecture diagram of the Internet of Things operating system of the present invention;

[0052] Figure 2 A schematic diagram of a database model showing different multi-tenant and application scenarios;

[0053] Figure 3 The figure shows a schematic diagram of the address book tree structure based on tenant-defined communication of the present invention;

[0054] Figure 4 A schematic diagram of the configuration process of a customized tenant address book of the present invention is shown;

[0055] Figure 5 A schematic diagram showing the background data operation flow of the communication configuration of the present invention is shown;

[0056] Figure 6 A schematic diagram showing a process of querying a new tenant's address book according to the present invention;

[0057] Figure 7 It is a schematic diagram showing the application of the electronic device of the present invention. DETAILED DESCRIPTION

[0058] Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. The same reference numerals in the accompanying drawings represent elements with the same or similar functions. Although various aspects of the embodiments are shown in the accompanying drawings, the drawings are not necessarily drawn to scale unless otherwise specified.

[0059] The word “exemplary” is used exclusively herein to mean “serving as an example, example, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.

[0060] In addition, in order to better illustrate the present disclosure, numerous specific details are given in the following specific embodiments. It should be understood by those skilled in the art that the present disclosure can also be implemented without certain specific details. In some examples, means, components and circuits well known to those skilled in the art are not described in detail in order to highlight the main purpose of the present disclosure.

[0061] Terminology explanation:

[0062] IoT operating system: Its system architecture is as follows Figure 1 As shown in Figure 1, the IoT operating system is an important part of the new generation of information technology. Its English name is IOT (Internet of Things). As the name suggests, "the Internet of Things is the Internet of Things connecting everything."

[0063] iSysCore OS: One of the IoT operating system software released by Hangzhou Instruction Set Intelligent Technology Co., Ltd.

[0064] Multi-tenancy: Multi-tenancy technology (English: multi-tenancy technology) or multi-leasing technology, is a software architecture technology that explores and implements how to share the same system or program components in a multi-user environment while still ensuring the isolation of data between users.

[0065] Operation and maintenance platform: The operation and maintenance platform deployed in the cloud service is a platform software that integrates operation and maintenance related functions.

[0066] Organizational Structure: The organizational structure divides the organization into different departments and functions, each with clear responsibilities and tasks.

[0067] Address book: Collaborative office software displays the organizational structure hierarchy of the enterprise as an organizational tree. Select the corresponding organization to display the personnel information under the organization on the right. This structure is called an address book, similar to enterprise WeChat, DingTalk, etc.

[0068] View: A view in a computer database is a virtual table whose contents are defined by a query. Like a real table, a view contains a series of named columns and rows of data. However, a view does not exist as a stored set of data values ​​in the database. The row and column data come from the table referenced by the query that defines the view, and are generated dynamically when the view is referenced.

[0069] Example 1

[0070] The enterprise-level IoT operating system platform of the present invention customizes the address book across tenants by creating a new sub-tenant under the source tenant, customizing the address book function page, creating a new organizational structure tree, and mounting a certain organizational node of the "source tenant" on a certain node, and rendering the new organizational structure in real time. It can solve the following problems:

[0071] Solve the problem of cross-tenant collaboration required for multi-tenant i SysCore OS enterprise-level IoT platform;

[0072] Solve the problem of platform-customized organizational structure (address book), which can combine different organizational structures under multiple tenants into a new sub-tenant organizational structure (address book), and generate it in real time;

[0073] Solve the problem of ensuring synchronization in subtenants when the information of an organization (including organizational structure and personnel) is changed in the source tenant.

[0074] The application principle of the present invention will be described in detail below.

[0075] On the one hand, the present application proposes a method for customizing a cross-tenant address book on an enterprise-level Internet of Things platform, which is characterized by comprising the following steps:

[0076] S1, collect original data sets of different tenants and applications;

[0077] S2. Parse and read the mapping relationship between the data of each tenant and the application in the original data set, and build a corresponding view data set based on the mapping relationship between the data of each tenant and the application, so that the view data set displays the mapping relationship between the data of each tenant and the application through a view;

[0078] S3. By customizing the tenant address book, the view data set is regenerated into a new address book tree of each tenant and application and rendered and output.

[0079] As attached Figure 2 As shown in Figure 1, the multi-tenant model describes the mapping relationship between tenants and their data. Different multi-tenant models will affect the design, management, and maintenance of databases and applications.

[0080] The three most common ones are:

[0081] One tenant one database mode ( Figure 2 , left image);

[0082] One tenant one space naming mode ( Figure 2 (middle figure in );

[0083] Tenant shared database mode ( Figure 2 (right picture in the figure).

[0084] The present invention adopts an application-shared database mode (i.e., a tenant-shared database mode), where different tenants and applications of the entire enterprise-level Internet of Things platform share a set of database clusters.

[0085] like Figure 3 As shown, the present invention first uses the view mode to visualize the tenant relationship and obtain a view data set. Then, the tenant relationship in the view data set is used to generate a virtual tree structure model of a new organizational structure, that is, an address book tree. Through the address book tree, the communication node information of other tenants or applications related to the tenant can be intuitively queried, realizing a cross-tenant custom address book method for an enterprise-level Internet of Things operating system platform.

[0086] like Figure 4 As shown, preferably, in step S3, the method for configuring the custom tenant address book includes:

[0087] Start creating a cross-tenant collaboration team and enter the custom address book page;

[0088] Create a new tenant and apply to the platform for permission to associate the tenant:

[0089] If the platform does not agree to the request, the creation fails and you need to modify it and reapply;

[0090] If the platform agrees to the request, proceed to the next step;

[0091] Set up a new tenant address book: Check the organizational structure of the corresponding tenant in the tenant list, and generate a custom address book for the new tenant based on the checked items;

[0092] Send the new tenant's custom address book to the backend, perform backend data operations, configure the communication for the new tenant's custom address book, and obtain the custom tenant address book;

[0093] The configuration is complete and the subtenant is created.

[0094] Administrators can log in to the platform to create a new tenant's address book network, configure communications, and customize the communication directory tree for new tenants. The tenant's application permissions can be reviewed based on the pre-configured permission rules on the platform. If the review fails, the corresponding permission requirements can be fed back to the tenant.

[0095] For custom address book pages, you can use virtual directory technology to display the tree structure. Figure 3 The displayed address book tree, in order to use the view to visualize the communication network of the tenant, adopts the tree structure of the view mode to display the communication network of the (new or target) tenant, that is, the address book tree.

[0096] To generate a virtual tree structure model using virtual directory technology, you can refer to the following steps:

[0097] 1. Demand analysis and planning

[0098] Clarify requirements: First, you need to clarify the specific requirements of the virtual tree structure model, including the purpose of the model, the type of data that needs to be included, access rights, etc.

[0099] Plan the structure: plan the levels and nodes of the virtual tree structure according to the requirements, and determine the root node, child nodes, and the relationship between nodes.

[0100] 2. Data preparation and processing

[0101] Collect data: Collect the data that needs to be included in the virtual tree structure. This data may come from different sources such as databases, file systems, cloud storage, etc.

[0102] Data processing: Clean, organize and format the collected data for use in subsequent steps. This may include operations such as data deduplication, type conversion, and field mapping.

[0103] 3. Virtual Directory Design

[0104] Define virtual directories: Define the levels and nodes of virtual directories according to the planned structure. Virtual directories do not store data directly, but serve as references or pointers to actual data locations.

[0105] Set access permissions: Set appropriate access permissions for each node in the virtual directory to ensure that only authorized users or systems can access specific data.

[0106] 4. Construct a virtual tree structure

[0107] Create the root node: First, create the root node of the virtual tree structure, which is the starting point of the entire structure.

[0108] Add child nodes: According to the planned structure, add child nodes level by level and set the parent-child relationship between nodes. Each child node can contain a reference or pointer to the actual data.

[0109] Configure properties: Configure necessary properties for each node, such as name, description, type, access rights, etc.

[0110] 5. Mapping the actual data

[0111] Establish a mapping relationship: Establish a mapping relationship between the nodes of the virtual directory and the actual data location. This can be achieved through configuration files, database tables, API calls, etc.

[0112] Verify mapping: Ensure that each node is correctly mapped to the actual data location and that the data can be accessed through the virtual directory.

[0113] 6. Testing and Optimization

[0114] Functional testing: Perform functional testing on the virtual tree structure model to verify whether it meets the requirements, including data access, permission control, node operation and other aspects.

[0115] Performance testing: Evaluate the performance of the virtual tree structure model, such as access speed, response time, etc., and optimize it based on the test results.

[0116] Continuous optimization: Based on feedback and demand changes in actual applications, the virtual tree structure model is continuously optimized to improve its usability and efficiency.

[0117] 7. Deployment and maintenance

[0118] Deployment model: Deploy the constructed virtual tree structure model to the target environment, such as server, cloud platform, etc.

[0119] Develop maintenance plans: Develop regular maintenance plans, including data updates, structural adjustments, permission reviews, etc., to ensure the continued effective operation of the virtual tree structure model.

[0120] Through the above steps, you can use virtual directory technology to generate a virtual tree that meets specific needs.

[0121] After generating the custom address book tree of the new tenant, the backend may send the custom address book to the frontend, and the frontend may dynamically display the custom address book.

[0122] During the background data operation, the main task is to configure the root node of the new tenant and its communication node ID (or id) in the system organization.

[0123] like Figure 5 As shown, preferably, the sending of the customized address book of the new tenant to the background, performing background data operations, performing communication configuration for the customized address book of the new tenant, and obtaining the customized tenant address book includes:

[0124] Reading the view data about the new tenant in the custom address book;

[0125] Determine the communication root node of the new tenant according to the mapping relationship between the new tenant and the data of the tenant and the application shown in the view data of the new tenant;

[0126] The communication root node of the new tenant is saved in the organization tenant relationship table, and the root node identifier of the new tenant is changed in the system organization table to complete the communication configuration of the new tenant, obtain the custom tenant address book of the new tenant and save it to the database cluster.

[0127] The database has pre-stored relevant data tables, as follows:

[0128] sys_tenant system tenant table;

[0129] sys_rental_info system organization table;

[0130] sys_tenant_rental_ref organizes the tenant relationship table;

[0131] sys_tenant_user tenant user relationship table;

[0132] Sys_rental_relationship system organization closure table;

[0133] sys_user user table.

[0134] The process of constructing a custom address book in the present invention is not to completely copy the department information and user information in the organizational structure of the selected source tenant to the database, but to reconstruct the table design by analogy with the thinking of abstract mysql view. After creating a sub-tenant, only the root node of the address book selected by the source tenant is saved in the sys_tenant_rental_ref data table, and then in the sys_rental_info table, is_ref is set to 1 to indicate that this root node exists in other sub-tenants, and the configuration is completed. Therefore, even if tens of thousands of data are called, only the data of a few root nodes are actually operated, and the execution speed is very fast. Because only the configured data is stored in the database, the speed of querying the address book is also very fast.

[0135] Therefore, after the configuration of the address book tree for the new tenant is completed, the system can start to execute the corresponding scheduled tasks (automatically executed according to the system set time, using asynchronous initiation), and the cache middleware redis and the search engine es related to the new tenant's users, and update the original data after adding the tenant Ids (a list of user and tenant relationships, including several tenant ids, represented in plural here) in the user information to ensure the user's cross-tenant permissions. Therefore, the number of users has not increased, and the consumption of server performance has been greatly reduced.

[0136] Preferably, S3, by customizing the tenant address book, regenerating a new address book tree of each tenant and application from the view data set and rendering and outputting it, includes:

[0137] Start a scheduled task for new tenant communications;

[0138] Read the custom tenant address book of the new tenant, and query the communication IDs of other tenants and organizations associated with the new tenant ID through the new tenant ID from the address book tree of the new tenant;

[0139] Traverse the communication ID of the organization and get the sub-organization;

[0140] Render the sub-tree of the sub-organization as the entire address book tree, and query to obtain the address book tree of the new tenant;

[0141] Query completed.

[0142] like Figure 6 As shown in the figure, when querying the new tenant's address book, in the process of querying the custom organizational structure tree, querying the configured root node is very fast, and then the process of querying the self-description and rendering the entire tree is completed.

[0143] By traversing and querying the tenant ID in the new tenant's address book tree, you can query the set of other tenants and organization relationships related to the current tenant through the tenant ID. Because the corresponding address book tree is built based on the current tenant's custom communication options (that is, custom address book) based on virtual directory technology in the early stage, it is possible to quickly traverse and find the IDs of other tenants and organizations associated with the current tenant based on the view of the address book tree, and build an ID set.

[0144] It is also very fast to query the child nodes through the root node using the closure table. Therefore, the method of the present invention + the design of the closure table can be used to render different tenants with the lowest loss and efficiently under the cross-tenant collaboration requirements, thereby realizing a cross-tenant customized address book method for an enterprise-level Internet of Things operating system platform.

[0145] Based on the above scheme, the present invention can be implemented in the iSysCoreOS enterprise-level Internet of Things platform for tenant products that need to be customized across tenants.

[0146] Obviously, those skilled in the art should understand that the implementation of all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the above-mentioned embodiments. Those skilled in the art can understand that the implementation of all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the above-mentioned embodiments. Among them, the storage medium can be a disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), a flash memory (Flash Memory), a hard disk (Hard Disk Drive, abbreviated as: HDD) or a solid-state drive (SSD), etc.; the storage medium can also include a combination of the above-mentioned types of memory.

[0147] Example 2

[0148] Based on the implementation principle of Example 1, on the other hand, the present application further proposes a computer-readable storage medium, in which executable instructions are stored. When the executable instructions are executed, a method for customizing a cross-tenant address book on an enterprise-level Internet of Things platform is implemented.

[0149] The modules or steps of the present invention described above can be implemented by a general-purpose computing system, they can be concentrated on a single computing system, or distributed on a network composed of multiple computing systems, and optionally, they can be implemented by a program code executable by a computing system, so that they can be stored in a storage system and executed by the computing system, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0150] Example 3

[0151] like Figure 7 As shown, further, in another aspect, the present application also proposes an electronic device, including:

[0152] processor;

[0153] a memory for storing processor-executable instructions;

[0154] Among them, the processor is configured to implement a method for customizing a cross-tenant address book on an enterprise-level Internet of Things platform as described in Example 1 when executing the executable instructions.

[0155] The electronic device of the embodiment of the present disclosure includes a processor and a memory for storing instructions executable by the processor. The processor is configured to implement a method for customizing a cross-tenant address book on an enterprise-level Internet of Things platform as described in the first embodiment above when executing the executable instructions.

[0156] Here, it should be noted that the number of processors can be one or more. At the same time, the electronic device of the embodiment of the present disclosure may also include an input system and an output system. Among them, the processor, memory, input system and output system may be connected through a bus or in other ways, which are not specifically limited here.

[0157] As a computer-readable storage medium, the memory can be used to store software programs, computer executable programs and various modules, such as the program or module corresponding to the method for cross-tenant customized address book of an enterprise-level IoT platform in the embodiment of the present disclosure. The processor executes various functional applications and data processing of the electronic device by running the software programs or modules stored in the memory.

[0158] The input system can be used to receive input numbers or signals. The signal can be a key signal related to user settings and function control of the device / terminal / server. The output system can include display devices such as display screens.

[0159] The embodiments of the present disclosure have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The selection of terms used herein is intended to best explain the principles of the embodiments, practical applications, or technical improvements in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A method for customizing a cross-tenant address book on an enterprise-level Internet of Things platform, characterized in that: The steps include: S1, collect original data sets of different tenants and applications; S2. Parse and read the mapping relationship between the data of each tenant and the application in the original data set, and construct a corresponding view data set based on the mapping relationship between the data of each tenant and the application, so that the view data set displays the mapping relationship between the data of each tenant and the application through a view; S3. By customizing the tenant address book, the view data set is regenerated into a new address book tree of each tenant and application and rendered and output.

2. According to claim 1, a method for customizing a cross-tenant address book on an enterprise-level Internet of Things platform is characterized in that: In step S3, the method for configuring the custom tenant address book includes: Start creating a cross-tenant collaboration team and enter the custom address book page; Create a new tenant and apply to the platform for permission to associate the tenant: If the platform does not agree to the request, the creation fails and you need to modify it and reapply; If the platform agrees to the request, proceed to the next step; Set up a new tenant address book: Check the organizational structure of the corresponding tenant in the tenant list, and generate a custom address book for the new tenant based on the checked items; Send the new tenant's custom address book to the backend, perform backend data operations, configure the communication for the new tenant's custom address book, and obtain the custom tenant address book; The configuration is complete and the subtenant is created.

3. According to claim 2, a method for customizing a cross-tenant address book on an enterprise-level Internet of Things platform is characterized in that: The custom address book page uses virtual directory technology to display the tree structure.

4. According to claim 2, a method for customizing a cross-tenant address book on an enterprise-level Internet of Things platform is characterized in that: In step S4, after generating the custom address book tree of the new tenant, the following steps are also included: The customized address book is sent to the front end, and the front end dynamically displays the customized address book.

5. According to claim 2, a method for customizing a cross-tenant address book on an enterprise-level Internet of Things platform is characterized in that: The sending of the customized address book of the new tenant to the background, performing background data operations, performing communication configuration for the customized address book of the new tenant, and obtaining the customized tenant address book includes: Reading the view data about the new tenant in the custom address book; Determine the communication root node of the new tenant according to the mapping relationship between the new tenant and the data of the tenant and the application shown in the view data of the new tenant; The communication root node of the new tenant is saved in the organization tenant relationship table, and the root node identifier of the new tenant is changed in the system organization table to complete the communication configuration of the new tenant, obtain the custom tenant address book of the new tenant and save it to the database cluster.

6. According to claim 5, a method for customizing a cross-tenant address book on an enterprise-level Internet of Things platform is characterized in that: S3. By customizing the tenant address book, the view data set is regenerated into a new address book tree of each tenant and application and rendered and output, including: Start a scheduled task for new tenant communications; Read the custom tenant address book of the new tenant, and query the communication IDs of other tenants and organizations associated with the new tenant ID through the new tenant ID from the address book tree of the new tenant; Traverse the communication ID of the organization and get the sub-organization; Render the sub-tree of the sub-organization as the entire address book tree, and query to obtain the address book tree of the new tenant; Query completed.

7. An electronic device, characterized in that: include: processor; a memory for storing processor-executable instructions; Wherein, the processor is configured to implement a method for customizing a cross-tenant address book for an enterprise-level Internet of Things platform according to any one of claims 1-6 when executing the executable instructions.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores executable instructions, and when the executable instructions are executed, a method for customizing a cross-tenant address book for an enterprise-level Internet of Things platform according to any one of claims 1 to 6 is implemented.

Images