Internet of Things distributed feature model interaction method, device, terminal and storage medium

Abstract

The present application relates to a distributed feature model interaction method, device, terminal and storage medium for the Internet of Things, wherein the method includes: after the system is initialized, the feature model is loaded, and the user distributed status information and distributed business data are loaded and stored; user status data, user business data and user resources are loaded and stored by means of component loading; the preset data is initialized to load the model data of user data and node information, and the user business data with user operable permissions of different nodes is filtered out; when a user business data classification request is received, the resource code and resource address are transmitted to the system container component through the feature model, and when the resource code is verified, the corresponding subsystem resources are displayed. The present application solves the problem that domain division, permissions, user and basic business data cannot be unified between different distributed subsystems of the Internet of Things.

Description

Technical Field

[0001] The present application relates to the field of Internet of Things technology, and in particular to an Internet of Things distributed feature model interaction method, device, terminal and storage medium. Background Art

[0002] The Internet of Things (IoT) system uses hardware devices or technologies such as information sensors to collect real-time data about objects or processes that require connection and interaction. Through access to various network protocols, it enables intelligent perception, identification, and management of these objects and processes. The IoT system primarily includes different subsystems, such as terminal access, terminal management, IoT application management, and rule engines. Due to the relatively complex business logic of each subsystem, independent service deployment is required between subsystems to ensure system stability. Reliable data transmission between systems is also required to ensure the complete availability of the IoT system. With the continuous development of the IoT, IoT subsystems are becoming increasingly complex, their functions are becoming increasingly complex, and the amount of IoT data is increasing. Therefore, the distributed deployment of IoT systems is urgently needed. Distributed deployment of IoT systems needs to meet the data domain requirements of different subsystems, and a reusable framework is also needed to achieve complete integration of different regions and subsystems.

[0003] The domain model is the product of domain analysis. Feature models, currently the primary manifestation of domain models, are a feature-based description and organization of domain requirements. Feature models organize features hierarchically, linking features at each level in a whole-part relationship. However, existing feature models of distributed IoT subsystems lack interaction, leading to issues such as inconsistent domain divisions, permissions, and user and basic business data across these subsystems. Summary of the Invention

[0004] The purpose of the embodiments of the present application is to propose an IoT distributed feature model interaction method, device, terminal and storage medium to solve the problems of domain unification, authority unification, user and basic business data unification between different IoT distributed subsystems.

[0005] In order to solve the above technical problems, the present invention provides an IoT distributed feature model interaction method, including:

[0006] After the system is initialized, the feature model is loaded, and the user distributed state information and distributed business data are loaded and stored, wherein the feature model includes the user distributed state model and the distributed business data model;

[0007] Load and store user status data, user business data, and user resources through component loading;

[0008] Initialize the preset data to load the model data of user data and node information, and filter out the user business data with user operation permissions for different nodes;

[0009] When a user service data classification requirement is received, the resource code and resource address are transmitted to the system container component through the feature model. When the resource code is verified, the subsystem resources corresponding to the user service data classification requirement are displayed.

[0010] In order to solve the above technical problems, the present invention provides an IoT distributed feature model interaction device, including:

[0011] A feature model loading unit, configured to load the feature model after system initialization, and load and store user distributed state information and distributed service data, wherein the feature model includes a user distributed state model and a distributed service data model;

[0012] A component loading unit is used to load and store user status data, user service data, and user resources by means of component loading;

[0013] The data screening unit is used to load the model data of user data and node information by initializing the preset data, and screening the user business data of the user's operational permissions for different nodes;

[0014] The subsystem resource display unit is used to transmit the resource code and resource address to the system container component through the feature model when receiving the user business data classification requirement, and when the resource code is verified, the subsystem resource corresponding to the user business data classification requirement is displayed.

[0015] To solve the above technical problems, a technical solution adopted by the present invention is: to provide an Internet of Things terminal, including one or more processors; a memory for storing one or more programs, so that one or more processors can implement any one of the above-mentioned Internet of Things distributed feature model interaction methods.

[0016] In order to solve the above technical problems, a technical solution adopted by the present invention is: a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements any one of the above-mentioned Internet of Things distributed feature model interaction methods.

[0017] The embodiment of the present invention provides an Internet of Things distributed feature model interaction method, device, terminal and storage medium. The method includes: after the system is initialized, the feature model is loaded, and the user distributed state information and distributed business data are loaded and stored; the user state data, user business data and user resources are loaded and stored by means of component loading; the preset data is initialized to load the model data of the user data and node information, and the user business data of the user operable permissions of different nodes are screened out; when the user business data classification requirement is received, the resource code and resource address are transmitted to the system container component through the feature model, and when the resource code is verified, the subsystem resources corresponding to the user business data classification requirement are displayed. The embodiment of the present application realizes the model interaction and data flow between the user distributed state model and the distributed business data model, and solves the problem that the domain division, permissions, and user and basic business data cannot be unified between different Internet of Things distributed subsystems. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the solutions in this application, a brief introduction will be given below to the drawings required for use in the description of the embodiments of this application. Obviously, the drawings described below are some embodiments of this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0019] Figure 1 A flowchart of an implementation of the distributed feature model interaction method for the Internet of Things provided by an embodiment of the present application;

[0020] Figure 2 This is a schematic diagram of the interactive relationship of the distributed feature model of the Internet of Things provided by the embodiment of the present application;

[0021] Figure 3 This is a flowchart of a sub-process in the distributed feature model interaction method for the Internet of Things provided by an embodiment of the present application;

[0022] Figure 4 This is a flowchart of a sub-process in the distributed feature model interaction method for the Internet of Things provided by an embodiment of the present application;

[0023] Figure 5 This is a schematic diagram of the IoT distributed feature model interaction device provided by an embodiment of the present application;

[0024] Figure 6 This is a schematic diagram of an Internet of Things terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0025] Unless otherwise defined, all technical and scientific terms used herein have the same meanings as commonly understood by those skilled in the art to which this application belongs. The terms used in the specification of the application are for the purpose of describing specific embodiments only and are not intended to limit this application. The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of this application or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.

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

[0027] 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 accompanying drawings.

[0028] It should be noted that the IoT distributed feature model interaction method provided in the embodiments of the present application is generally executed by an IoT terminal, and accordingly, the IoT distributed feature model interaction device is generally configured in the IoT terminal.

[0029] See also Figure 1 and Figure 2 , Figure 1 A specific implementation of the distributed feature model interaction method for the Internet of Things is shown. Figure 2 This is a schematic diagram of the interactive relationship of the distributed feature model of the Internet of Things provided in an embodiment of the present application.

[0030] It should be noted that the method of the present invention is not limited to the method of Figure 1 The process sequence shown is limited to the following steps:

[0031] S1: After the system is initialized, the feature model is loaded, and user distributed state information and distributed business data are loaded and stored, wherein the feature model includes a user distributed state model and a distributed business data model.

[0032] Specifically, in the embodiment of the present application, the system is first initialized and the feature model is initialized. The user distributed state model is then loaded and initialized according to the system node, thereby completing the initialization of the user authentication function. After the system initialization is completed, the system loads the user distributed state model and the distributed service data model, creates a state object, and completes the loading and storage of different user distributed state information and distributed service data according to different nodes.

[0033] In the embodiment of the present application, the description of the user distributed feature model is divided into the model structure and the changes within the model to describe the variability of the feature model. Its variability relationship includes mandatory (mandatory feature): when the parent feature X in the feature model is selected, the child feature Y must also appear at the same time. Optional (optional feature): an optional feature X is optional. During the construction process of the user distributed feature model, the feature can be selected or not. Alternative (exclusive OR group): the parent feature X of an exclusive OR group has multiple optional child features Y. During the construction process of the user distributed feature model, when the parent feature is selected, only one child feature can be selected and included in the final configuration result. Or (or group): during the construction process of the user distributed feature model, multiple features can be selected from the multiple child features Y of the parent feature X. Another category is used to describe the constraints of the feature model, which consists of requires (dependency) and excludes (mutual exclusion). Requires: a feature X depends on another feature Y. If feature X appears in the user distributed feature model, feature Y must appear in the model. Excludes: two features cannot appear in the same user distributed feature model.

[0034] Among them, the user distributed state model is used to construct the common state of users with different distributions; the structure of the user distributed state model includes two parent features: user information attributes and user region attributes. The sub-features of the user information attribute include user name, user organization, user authentication status, user permissions, and user basic information, among which user name, user authentication status, and user permissions are all required sub-features, and their relationship is or (or group). User basic information is an optional sub-feature. The sub-features of the user's region include the user's distributed node region information, whether the user's node status is activated, and the default region, among which user region information and whether the user's node status is activated are required sub-features, and the default region is an optional sub-feature, and their relationship is or (or group); the user information attribute and the user's region attribute are dependent.

[0035] The distributed business data model is used to construct user business data information for different distributed nodes. The structure of the distributed business data model includes two parent features: business data classification and business data index. The subfeatures of the business data classification include the business data resource relationship list, business data resource type, business data resource status, and business data resource details. The business data resource relationship list, business data resource type, and business data resource status are all mandatory subfeatures, with an OR relationship (or group relationship). Business data resource details are optional subfeatures. The subfeatures of the business data index include the business data resource code, business data permission code, business data node address information, business data category information, business data node opening method, and business data node notes. The business data resource code, business data permission code, and business data node address information are all mandatory subfeatures, with an OR relationship (or group relationship). Business data category information, business data node opening method, and business data node notes are optional subfeatures. The business data classification and business data index are dependent on each other. The distributed business data model classifies user business data types and marks their status based on the business data classification. The business data index is used to address and index corresponding resources for resource loading.

[0036] In the embodiments of the present application, the shared features of the distributed IoT subsystems constructed through the user distributed state model and the distributed business data model can realize the business requirements description and organization method of different subsystems, fully express the common feature knowledge and variability relationship of different distributed IoT subsystems, meet the basic functions of different subsystems, realize the reusability of different subsystem models, and solve the problem of repeated development and operation of basic data logic of different distributed subsystems and inability to effectively reuse. In addition, a reusable model is constructed based on the user distributed state model and the business data model, based on the distributed feature model of the IoT, which conforms to the shared features of each IoT subsystem. At the same time, in the construction of the distributed IoT system, the independent deployment of subsystems in different areas of the distributed IoT system, data isolation, and the complete availability of IoT system functions are guaranteed.

[0037] See also Figure 3 , Figure 3 A specific implementation method before step S1 is shown, which is described in detail as follows:

[0038] S1A: Initialize the system and feature models.

[0039] S1B: Load the initialized user distributed state model according to the system node to complete the initialization of the user authentication function.

[0040] Specifically, before implementing step S1, in the embodiment of the present application, the system is initialized and the feature model is initialized, and the user distributed state model is initialized according to the system node loading, thereby completing the initialization of the user authentication function.

[0041] S2: Load and store user status data, user business data, and user resources through component loading.

[0042] Furthermore, this application provides a specific implementation of step S2;

[0043] After the feature model is loaded, the various components of the feature model are loaded and installed. Among them, the top component is used to store and display user status model data, the side component is used to store and display user business data, and the container component is used to load user resources.

[0044] Specifically, after the user model is loaded, the various components of the feature model are loaded and installed. The top component stores and displays the user status model data, the side component stores and displays the user business data, and the Container component loads the corresponding user resources.

[0045] S3: Initialize the preset data to load the model data of user data and node information, and filter out the user business data of the user's operational permissions for different nodes.

[0046] See also Figure 4 , Figure 4 A specific implementation of step S3 is shown, which is described in detail as follows:

[0047] S31: Initialize the user node data and the authority data of the feature model and the data in the top component to load the model data of the user data and the node information.

[0048] S32: Classify and recursively filter the data corresponding to the feature model data according to the user node information and the user authority information, so as to filter out the user business data of the user's operable authority at different nodes.

[0049] Specifically, after each component is loaded, the feature model's user node data and associated permissions are initialized, and the top component data is initialized, completing the loading of the model data corresponding to the user data and node information. Based on the model interaction relationships, the user model and business model rules are loaded. Based on the user node information and user permission information, the corresponding business model data is recursively filtered and categorized to identify user business data with user-operable permissions for different nodes. This filtered business data includes the user resource code and resource address.

[0050] S4: When receiving the user's business data classification requirements, the resource code and resource address are transmitted to the system container component through the feature model. When the resource code is verified, the subsystem resources corresponding to the user's business data classification requirements are displayed.

[0051] Specifically, after the filtered business data contains user resource code and resource address, when the user clicks on different business data categories, the feature model passes the resource code and resource address to the system container component. The system container component matches the code with the internal code of the resource and displays the corresponding subsystem resources after verification.

[0052] Furthermore, this application also includes a specific implementation method, which is described in detail as follows:

[0053] After the feature model is loaded, the user status of different distributed nodes and the operation statistics of user business data are monitored through tracking.

[0054] Specifically, after the model is loaded, the user status and business data operation statistics of different distributed nodes are monitored to achieve a unified monitoring function for the user status and business data of different distributed nodes. This function stores the corresponding node user login information and user-related operation information, and monitors the relevant operation logs through the feature model embedding point. The embodiment of the present application provides a monitoring function based on a feature model, which can track the user status and business data of different distributed nodes and complete the monitoring of related general business log functions.

[0055] In a specific embodiment, a provincial or municipal company proposed the need to deploy an IoT distributed subsystem. This need requires the integration of the unified authentication function of the centralized node and the IoT terminal access, terminal management, IoT application management, rule engine and other different subsystem functions of the distributed node. It requires unified authentication of different nodes. At the same time, it is also necessary to load different subsystem function resources such as IoT terminal access and terminal management of the corresponding node according to the node user status and business configuration. By using the method of the embodiment of the present application, the user distributed state model and the user distributed business data model are uniformly reused in the centralized node and the distributed node. Through the unified model and model interaction rules, the domain division, authority, user and basic business data between subsystems are unified, which facilitates unified maintenance and data standardization. At the same time, different subsystem resources are dynamically loaded according to resource authority, and the distributed node subsystems are independently deployed to solve the problem of high coupling of different distributed sub-nodes causing difficulty in upgrading and operation.

[0056] In this embodiment, after the system is initialized, the feature model is loaded, and the user distributed state information and distributed business data are loaded and stored; user state data, user business data, and user resources are loaded and stored by means of component loading; the preset data is initialized to load the model data of the user data and node information, and the user business data of the user's operational permissions for different nodes are filtered out; when the user business data classification requirement is received, the resource code and resource address are transmitted to the system container component through the feature model, and when the resource code is verified, the subsystem resources corresponding to the user business data classification requirement are displayed. The embodiment of the present application realizes the model interaction and data flow between the user distributed state model and the distributed business data model, solving the problem that the domain division, permissions, and user and basic business data cannot be unified between different IoT distributed subsystems. The embodiment of the present application also solves the problem that the basic data logic of different distributed subsystems is repeatedly developed and maintained and cannot be effectively reused. The distributed feature model of the Internet of Things extracted by the embodiment of the present application conforms to the common characteristics of each subsystem of the Internet of Things, and at the same time realizes the construction of a distributed Internet of Things system, ensuring the independent deployment of subsystems in different areas of the distributed Internet of Things system, data isolation, and the complete availability of IoT system functions.

[0057] Please refer to Figure 5 , as a response to the above Figure 1 The present application provides an embodiment of a distributed feature model interaction device for the Internet of Things. Figure 1 Corresponding to the method embodiment shown, the device can be specifically applied to various Internet of Things terminals.

[0058] like Figure 5 As shown, the IoT distributed feature model interaction device of this embodiment includes: a feature model loading unit 51, a component loading unit 52, a data screening unit 53 and a subsystem resource display unit 54, wherein:

[0059] The feature model loading unit 51 is used to load the feature model after the system is initialized, and load and store the user distributed state information and distributed service data, wherein the feature model includes the user distributed state model and the distributed service data model;

[0060] The component loading unit 52 is used to load and store user status data, user service data and user resources by means of component loading;

[0061] The data screening unit 53 is used to load the model data of user data and node information by initializing the preset data, and to screen the user business data of the user's operational authority for different nodes;

[0062] The subsystem resource display unit 54 is used to transmit the resource code and resource address to the system container component through the feature model when receiving the user business data classification requirement. When the resource code is verified, the subsystem resource corresponding to the user business data classification requirement is displayed.

[0063] Among them, the user distributed state model is used to construct the common state of users in different distributions; the structure of the user distributed state model includes two parent features: user information attributes and user area attributes; the sub-features of the user information attributes include user name, user organization, user authentication status, user permissions, and user basic information, among which user name, user authentication status, and user permissions are all required sub-features; user basic information is an optional sub-feature; the sub-features of the user area include the user's distributed node area information, whether the user node status is activated, and the default area, among which user area information and whether the user node status is activated are required sub-features, and the default area is an optional sub-feature; the user information attributes and the user area attributes are dependent on each other.

[0064] Among them, the distributed business data model is used to construct user business data information of different distributed nodes; the structure of the distributed business data model includes two parent features: business data classification and business data index; the sub-features of the business data classification include business data resource relationship list, business data resource type, business data resource status, and business data resource details; among them, the business data resource relationship list, business data resource type, and business data resource status are all required sub-features; the business data resource details are optional sub-features; the sub-features of the business data index include business data resource code, business data permission code, business data node address information, business data category information, business data node opening method, and business data node remarks; among them, business data resource code, business data permission code, and business data node address information are all required sub-features; business data category information, business data node opening method, and business data node remarks are optional sub-features; business data classification and business data index are dependent relationships; the distributed business data model divides user business data types and marks status according to business data classification; the addressing index of the corresponding resources is completed through the business data index to load resources.

[0065] Furthermore, the feature model loading unit 51 further includes:

[0066] System initialization processing unit, used for initializing the system and feature model;

[0067] The user authentication unit is used to load the initialized user distributed state model according to the system node to complete the initialization of the user authentication function.

[0068] Furthermore, the component loading unit 52 includes:

[0069] The data storage unit is used to load and install the various components of the feature model after the feature model is loaded. Among them, the top component is used to store and display user status model data, the side component is used to store and display user business data, and the container component is used to load user resources.

[0070] Furthermore, the data screening unit 53 includes:

[0071] The model data loading unit is used to initialize the user node data and the authority data of the feature model and the data in the top component to load the model data of the user data and node information;

[0072] The business data screening unit is used to classify and recursively screen the data corresponding to the feature model data according to the user node information and the user authority information, so as to screen out the user business data of the user who has the operational authority for different nodes.

[0073] Furthermore, the IoT distributed feature model interaction device further includes:

[0074] The data monitoring unit is used to monitor the user status of different distributed nodes and the operation statistics of user business data through tracking after the feature model is loaded.

[0075] In this embodiment, after the system is initialized, the feature model is loaded, and the user distributed state information and distributed business data are loaded and stored; user state data, user business data, and user resources are loaded and stored by means of component loading; the preset data is initialized to load the model data of user data and node information, and the user business data of the user-operable permissions of different nodes are screened out; when the user business data classification requirement is received, the resource code and resource address are transmitted to the system container component through the feature model, and when the resource code is verified, the subsystem resources corresponding to the user business data classification requirement are displayed. The embodiment of the present application realizes the model interaction and data flow between the user distributed state model and the distributed business data model, and solves the problem that the domain division, permissions, and user and basic business data cannot be unified between different IoT distributed subsystems.

[0076] To solve the above technical problems, the present application also provides an Internet of Things terminal. Figure 6 , Figure 6 This is a basic structural block diagram of the Internet of Things terminal in this embodiment.

[0077] The IoT terminal 8 includes a memory 81, a processor 82, and a network interface 83 that are interconnected through a system bus. It should be noted that the figure only shows an IoT terminal 8 with three components: memory 81, processor 82, and network interface 83. However, it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the IoT terminal here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0078] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, Internet of Things terminal, air conditioner, or network device, etc.) to execute the methods of each embodiment of the present application.

[0079] Obviously, the embodiments described above are only some of the embodiments of the present application, rather than all of the embodiments. The preferred embodiments of the present application are given in the accompanying drawings, but they do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present application more thorough and comprehensive. Although the present application has been described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions described in the aforementioned specific embodiments, or to make equivalent replacements for some of the technical features therein. Any equivalent structure made using the contents of the present application specification and the accompanying drawings, directly or indirectly used in other related technical fields, is also within the scope of patent protection of the present application.

Claims

1. A distributed feature model interaction method for the Internet of Things, characterized in that: include: After the system is initialized, the feature model is loaded, and the user distributed state information and distributed business data are loaded and stored, wherein the feature model includes the user distributed state model and the distributed business data model; Load and store user status data, user business data, and user resources through component loading; Initialize the preset data to load the model data of user data and node information, and filter out the user business data with user operation permissions for different nodes; When a user service data classification requirement is received, the resource code and resource address are transmitted to the system container component through the feature model. When the resource code is verified, the subsystem resources corresponding to the user service data classification requirement are displayed.

2. The Internet of Things distributed feature model interaction method according to claim 1, characterized in that: The user distributed state model is used to construct the common state of users with different distributions; the structure of the user distributed state model includes two parent features, namely user information attributes and user area attributes; the sub-features of the user information attributes include user name, user organization, user authentication status, user permissions, and user basic information, among which the user name, the user authentication status, and the user permissions are all required sub-features; the user basic information is an optional sub-feature; the sub-features of the user area include user distributed node area information, whether the user node status is activated, and the default area, among which the user area information and whether the user node status is activated are required sub-features, and the default area is an optional sub-feature; the user information attributes and the user area attributes are dependent on each other.

3. The distributed feature model interaction method of the Internet of Things according to claim 1, characterized in that: The distributed business data model is used to construct user business data information of different distributed nodes; the structure of the distributed business data model includes two parent features, namely business data classification and business data index; the sub-features of the business data classification include a business data resource relationship list, a business data resource type, a business data resource status, and business data resource details; wherein the business data resource relationship list, the business data resource type, and the business data resource status are all required sub-features; the business data resource details are optional sub-features; the sub-features of the business data index include a business data resource code, a business data permission code, a business data node address information, business data category information, a business data node opening method, and a business data node note; wherein the business data resource code, the business data permission code, and the business data node address information are all required sub-features; the business data category information, the business data node opening method, and the business data node note are optional sub-features; the business data classification and the business data index are a dependent relationship; the distributed business data model divides user business data types and marks status according to the business data classification; and the addressing index of the corresponding resource is completed through the business data index to load the resource.

4. The distributed feature model interaction method of the Internet of Things according to claim 1, characterized in that: After the system is initialized, the feature model is loaded, and before the user distributed state information and distributed service data are loaded and stored, the method further includes: Initializing the system and the feature model; The user distributed state model initialized according to the system node loading is used to complete the initialization of the user authentication function.

5. The Internet of Things distributed feature model interaction method according to claim 1, characterized in that: The method of loading and storing user status data, user service data, and user resources by means of component loading includes: When the feature model is loaded, the various components of the feature model are loaded and installed, wherein the top component is used to store and display user status model data, the side component is used to store and display the user business data, and the container component is used to load the user resources.

6. The distributed feature model interaction method for the Internet of Things according to claim 5, characterized in that: The preset data is initialized to load the model data of user data and node information, and the user business data of the user's operational permissions for different nodes are screened out, including: Initializing the user node data and the authority data of the feature model and the data in the top component to load the model data of the user data and the node information; According to the user node information and the user authority information, the data corresponding to the feature model data is classified and recursively screened to screen out the user business data of the user operable authority of different nodes.

7. The distributed feature model interaction method for the Internet of Things according to any one of claims 1 to 6, characterized in that: The method further comprises: After the feature model is loaded, the user status of different distributed nodes and the operation statistics of the user business data are monitored through tracking.

8. An Internet of Things distributed feature model interaction device, characterized in that: include: A feature model loading unit, configured to load the feature model after system initialization, and load and store user distributed state information and distributed service data, wherein the feature model includes a user distributed state model and a distributed service data model; A component loading unit is used to load and store user status data, user service data, and user resources by means of component loading; The data screening unit is used to load the model data of user data and node information by initializing the preset data, and screening the user business data of the user's operational permissions for different nodes; The subsystem resource display unit is used to transmit the resource code and resource address to the system container component through the feature model when receiving the user business data classification requirement, and when the resource code is verified, the subsystem resource corresponding to the user business data classification requirement is displayed.

9. An Internet of Things terminal, characterized in that: The method comprises a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the method for interactive distributed feature models of the Internet of Things as described in any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, the distributed feature model interaction method for the Internet of Things according to any one of claims 1 to 7 is implemented.

Images