A cloud-edge-end collaborative Internet of Things management and scheduling system and data interaction method

Abstract

The present invention belongs to the field of cloud-edge-end Internet of Things application technology, and in particular, relates to a cloud-edge-end collaborative Internet of Things management and scheduling system and a data interaction method. It includes a cloud service layer and an edge information layer; the cloud service layer is composed of a cloud tag service component, a cloud data management component, and a cloud resource scheduling component; the edge information layer includes multiple edge service terminals, and the edge service terminals are composed of an edge resource service component, an edge tag service component, a data sharing component, and an edge data management component; based on the current cloud-edge-end Internet of Things structure, this application provides a method for reducing the pressure of cloud data storage and transmission, optimizing data transmission delay, and through data distributed storage and management and data cache sharing mechanisms, to minimize the data interaction operation content required in the process of providing services to users, reduce the amount of data transmission across terminals and regions, thereby improving the response speed of the system and terminals, and enhancing the real-time performance of services.

Description

Technical Field

[0001] The present invention belongs to the field of cloud-edge-terminal Internet of Things application technology, and in particular relates to a cloud-edge-terminal collaborative Internet of Things management and scheduling system and a data interaction method. Background Art

[0002] With the continuous development of IoT technology, the intelligent control and use of various types of devices and resources in the IoT through cloud services can effectively reduce the operation and maintenance costs of the IoT and reduce the demand for human resources. Among them, cloud-edge technology can effectively reduce the computing pressure of the cloud, realize near-end computing, and improve the operating efficiency of the IoT management and scheduling system in the context of dealing with huge IoT devices and changing device structures. During the operation of the cloud-edge IoT management and scheduling system, it is necessary to build data information related to various devices and operation processes in the IoT, so that the cloud server and each edge terminal can confirm the status information from the basic equipment to the overall system. With the upgrade of the IoT structure and continuous management and scheduling, the basic data generated is also increasing. Therefore, an efficient data interaction processing solution is needed to reduce the difficulty of data storage and maintenance in the system, while improving the efficiency of data interaction. Summary of the invention

[0003] The purpose of the present invention is to provide a cloud-edge collaborative Internet of Things management and scheduling system and a corresponding data interaction method based on actual needs for improving data exchange efficiency in the Internet of Things management and scheduling process and reducing system resource consumption.

[0004] To achieve the above purpose, the present invention adopts the following technical solution.

[0005] The present application provides a cloud-edge-end collaborative IoT management and scheduling system, including a cloud service layer and an edge information layer;

[0006] The cloud service layer is composed of cloud tag service components, cloud data management components, and cloud resource scheduling components; the edge information layer includes multiple edge service terminals, which are composed of edge resource service components, edge tag service components, data sharing components, and edge data management components;

[0007] The cloud tag service component creates a data tag library for tagging terminals, IoT resources and their attributes based on IoT structure information, and implements the addition, deletion and modification of tag information;

[0008] The cloud data management component stores and maintains important cloud resource data, and extracts data and sends it to the data sharing component according to the instructions of the cloud resource scheduling component;

[0009] The cloud resource scheduling component extracts the corresponding data tags from the data tag library according to the resource access request message uploaded by the edge information layer, and sends the tags to the tag service component according to the demand, or sends the cloud resource data to the data sharing component;

[0010] The edge resource service component reads the resource requirements of the user side, verifies the legitimacy of the user, and establishes a data transmission channel with the user;

[0011] The tag service component parses user resource access requests, extracts data tag information and sends resource extraction instructions internally, data sharing requests externally, and resource access requests to the cloud;

[0012] The data sharing component establishes temporary storage for frequently called shared resources or cloud resources;

[0013] The edge data management component stores and maintains inherent data or necessary data within the service scope of the edge service terminal.

[0014] A further improvement or preferred implementation of the aforementioned cloud-edge collaborative IoT management and scheduling system also includes a device perception layer, which includes resource perception devices and control execution devices; the resource perception device is used to collect IoT resources and status information and upload it to the cloud tag service component.

[0015] A further improvement or preferred implementation of the aforementioned cloud-edge-end collaborative IoT management and scheduling system, wherein the data tag at least includes an edge service terminal tag, an IoT device tag, a user tag, and an application service tag;

[0016] The edge service terminal tag information includes the edge service terminal ID, the cloud system ID of the management side, the terminal location information, and the terminal server network information (including network type and availability status); the IoT device tag information includes the device type, the edge service terminal ID to which the device belongs, device attributes, device address, and attribute parameters; the user tag information includes the user identity ID, user category, edge service terminal ID, and user verification information; the application service tag information includes the application service ID, application service management end ID, and application service deployment status.

[0017] A further improvement or preferred implementation of the aforementioned cloud-edge collaborative IoT management and scheduling system, the data tag information includes: obtaining the ID of the device or terminal from the unique MAC address of the hardware determined in the network structure formed by the TCP / IP protocol; and device type and device attribute information determined by a code compiled based on the product electronic code coding standard.

[0018] The present application also provides a data interaction method for the aforementioned Internet of Things management and scheduling system, comprising the following steps:

[0019] A1, user a initiates a resource access request, which is directly uploaded to the resource service component A1 of the edge service terminal A. The resource service component A1 verifies the legitimacy of the identity of user a and assigns a corresponding user identity to it;

[0020] A2, label service component A2 determines the resource reading permission based on the determined user identity of user a, and searches for the corresponding resource location from the data label library stored in label service component A2 according to the resource access request message submitted by user a;

[0021] A3, if all resources can be obtained based on the current edge service terminal A, it means that all resources involved in the resource access request message are stored in the edge data management component A4 in the edge service terminal A or temporarily stored in the data sharing component A3; the label service component A1 extracts the corresponding data label and initiates an instruction to extract the corresponding resource from the edge data management component A4 or the data sharing component A3, and the data sharing component A3 sends the corresponding resource to the edge data management component A4 after receiving the instruction;

[0022] A4. If all resources cannot be obtained based on the current edge service terminal A, it means that some resources involved in the resource access request message are stored in one or more edge service terminals B. Then, while obtaining the data in the current edge service terminal A based on steps A2 and A3, the tag service component A2 determines whether it is necessary to initiate a data sharing request to other edge service terminals based on the resource reading permission of the current user a. If it is determined that a data sharing request is to be initiated, the data tags corresponding to the resources that do not exist in the edge service terminal A are extracted from the resource access request message. The resources involved in these non-existent data tags may be stored in the cloud data management component or the edge service terminal B. In the data sharing component B3 or the edge data management component B4, the tag service component A2 determines the edge data management component B4 (which may be one or more) containing the required external resources based on the data tag, locates the edge service terminal B, and sends all the required external data tag information to the tag service component B2. The tag service component B2 verifies the legitimacy of the identity of the edge service terminal A and determines its resource reading authority. If the authority is satisfied, it extracts the resource information contained in the tag information belonging to the edge data management component B4, retrieves whether the resources involved in the remaining tag information exist in the data sharing component B3, and feeds back the result to the tag service component A2;

[0023] If all resources are included in the edge service terminal B, the label service component B2 sends a resource call message to the edge data management component B4 and the data sharing component B3. The data sharing component B3 extracts the corresponding resources and sends them to the edge data management component B4. After combining, they are passed to the edge service component A1 through the edge service component B1. The edge service component A1 sends all resources to the user a, and caches the resources extracted by the data sharing component B3 in the data sharing component A3.

[0024] If all located edge service terminals B cannot provide all resources, the tag service component A2 further confirms the information of the retrieved resources to the cloud server;

[0025] A5. The cloud server searches the cloud data tag library according to the data tag information uploaded by the tag service component A2 to find the required resources. If the required resources are found to be located at a certain edge service terminal C, the corresponding information location and tag information are fed back to the edge service terminal. The tag service component A2 updates its own tag information library accordingly and initiates a data sharing request to the edge service terminal, and executes according to the mode of step A4. If the required resources are found to be located in the cloud data management component, the resource reading permission of the edge service terminal A is verified. If it is passed, the resources of the cloud data management component are called and sent to the data sharing component A3.

[0026] Further improvement or specific implementation steps of the data interaction method of the aforementioned Internet of Things management and scheduling system, the resource data transmitted from the cloud data management component to the data sharing component and between any data sharing components also includes a pre-deletion flag code given by the cloud data management component, and the pre-deletion flag code represents the time limit that the resource message can be saved after arriving at the data sharing component or the number of times the resource can be transmitted or read.

[0027] Further improvement or specific implementation steps of the data interaction method of the aforementioned Internet of Things management and scheduling system, the verification of the legitimacy of the user or terminal identity, and the assignment of a corresponding user identity to the user, specifically refers to: configuring the client on the user side and the edge service terminal side, configuring the verification server on the cloud, after the data requester initiates a resource access request, the edge resource service component or the cloud resource service component verifies the request content and the requester's identity information, if the verification is successful, the authorization license information is issued through the client, the client requests data access rights from the verification server through the received authorization license information, the verification server verifies the client identity and authorization license information, if successful, the corresponding data access rights are granted, otherwise, the authorization is not granted and the corresponding information is fed back to the client; the client obtains the corresponding data from the data end based on the corresponding data access rights under authorization, the data end confirms the validity of the data access rights to the verification server, if valid, the data transmission is executed, if invalid, the corresponding message is fed back to the client.

[0028] Further improvement or specific implementation steps of the data interaction method of the aforementioned Internet of Things management and scheduling system also include steps for adjusting the edge service terminal to which the user belongs, for transferring the service area of ​​one edge service terminal to the service area of ​​another edge service terminal when the user's location or service content changes, so that the user has a shorter data transmission link or a more matching service relationship; specifically:

[0029] When the location of user a or the service content of user a changes, the edge service terminal A collects reference attributes related to the location of user a and the service content, and determines the matching degree between user a and the location or service content of edge service terminal A according to the preset matching degree. If the matching degree is lower than a certain threshold, the reference attributes are uploaded to the cloud server; the cloud server determines the best edge service terminal B according to the reference attributes, and sends a transfer request to edge service terminal B. Edge service terminal B verifies the identity and data authority of user a. If the verification is passed, a transfer message is sent to edge service terminal A. Edge service terminal A transfers the attribute parameters and service content information of user a to edge service terminal B, and edge service terminal B provides subsequent services. If the verification of user a fails, a message is fed back to the cloud server, and the cloud server re-searches for the best edge service terminal other than edge service terminal B.

[0030] Its beneficial effects are:

[0031] The cloud-edge collaborative IoT management and scheduling system and its data interaction method of the present application are designed based on the current cloud-edge-end network structure. While making full use of the capabilities of the cloud and edge servers themselves, without making major changes to the existing IoT structure, it provides a system solution and interaction method that can effectively optimize large-capacity data sharing and caching interactions within the IoT. This solution can significantly reduce the cost of data interaction between the cloud and edge and the pressure of data storage and maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 It is a structural flow diagram of the cloud-edge-end collaborative Internet of Things management and scheduling system and its data interaction method. DETAILED DESCRIPTION

[0033] The present invention is described in detail below in conjunction with specific embodiments.

[0034] The cloud-edge-end collaborative IoT management and scheduling system and its data interaction method of the present application mainly aim to provide a method for reducing the pressure of cloud data storage and transmission, optimizing data transmission delay, and minimizing the data interaction operation content required in the user service process through data distributed storage and management and data cache sharing mechanism, thereby reducing the amount of data transmission across terminals and regions, thereby improving the response speed of the system and terminals and enhancing the real-time performance of services.

[0035] like Figure 1 As shown, the cloud-edge-end collaborative IoT management and scheduling system of the present application is mainly divided into a cloud service layer and an edge information layer; the cloud service layer is composed of a cloud tag service component, a cloud data management component, and a cloud resource scheduling component; the edge information layer includes multiple edge service terminals, and the edge service terminals are composed of an edge resource service component, an edge tag service component, a data sharing component, and an edge data management component;

[0036] It is easy to know that the service layer and information layer described in this application are mainly divided from the level of their organizational structure management. In the actual operation process, the above-mentioned service layer and information layer are generally constructed by several software and hardware facilities in the Internet of Things network structure, and there may be components or service contents at different levels located in the same hardware device or cloud virtual equipment space.

[0037] The cloud tag service component creates a data tag library for tagging terminals, IoT resources and their attributes based on IoT structure information, and implements the addition, deletion and modification of tag information;

[0038] In the actual implementation process, data tags are usually specified based on the necessary parameters, attributes and other necessary contents required by the corresponding data information of the corresponding equipment, terminal and service items during historical operation or operation and use. As the most common IoT management and control equipment, data tags at least include edge service terminal tags, IoT device tags, user tags and application service tags.

[0039] Among them, the edge service terminal tag information at least includes the edge service terminal ID, the management side cloud system ID, the terminal location information, the terminal server network and other information (including network type, available status); the IoT device tag information at least includes the device type, the edge service terminal ID to which the device belongs, the device attributes, the device address, attribute parameters and other information; the user tag information at least includes the user identity ID, user category, the edge service terminal ID to which it belongs, user verification information and other information; the application service tag information at least includes the application service ID, the application service management end ID, the application service deployment status and other information.

[0040] To simplify the data structure, for various types of equipment in the network structure, the ID information in the data tag information can obtain the ID of the device or terminal using the unique MAC address of the hardware determined in the network structure composed of the TCP / IP protocol; for attribute tag data, the device type and device attribute information can be determined based on the code compiled based on the product electronic code coding standard.

[0041] The cloud data management component stores and maintains important cloud resource data, extracts data according to the instructions of the cloud resource scheduling component, and sends it to the data sharing component;

[0042] The cloud resource scheduling component extracts the corresponding data tags from the data tag library according to the resource access request message uploaded by the edge information layer, and sends the tags to the tag service component according to the demand, or sends the cloud resource data to the data sharing component;

[0043] The edge resource service component reads the resource requirements of the user side, verifies the legitimacy of the user, and establishes a data transmission channel with the user;

[0044] The tag service component parses user resource access requests, extracts data tag information and sends resource extraction instructions internally, data sharing requests externally, and resource access requests to the cloud;

[0045] The data sharing component establishes temporary storage for frequently called shared resources or cloud resources;

[0046] The edge data management component stores and maintains inherent data or necessary data within the service scope of the edge service terminal.

[0047] In particular, in order to obtain the basic data required for data tags, during the specific implementation, a device perception layer can also be established according to actual needs. The device perception layer includes resource perception devices and control execution devices; the resource perception devices are used to collect IoT resources and status information and upload them to the cloud tag service component, so that the cloud tag service component can analyze and extract the data to establish corresponding data tags. The control execution device is mainly used to determine the device status attributes and for the execution of specific operations.

[0048] Based on the above foundation, the present application also provides a data interaction method for the aforementioned Internet of Things management and scheduling system, such as Figure 1 As shown, it specifically includes the following steps:

[0049] A1, user a initiates a resource access request, which is directly uploaded to the resource service component A1 of the edge service terminal A. The resource service component A1 verifies the legitimacy of the identity of user a and assigns a corresponding user identity to it;

[0050] A2, label service component A2 determines the resource reading permission based on the determined user identity of user a, and searches for the corresponding resource location from the data label library stored in label service component A2 according to the resource access request message submitted by user a;

[0051] A3, if all resources can be obtained based on the current edge service terminal A, it means that all resources involved in the resource access request message are stored in the edge data management component A4 in the edge service terminal A or temporarily stored in the data sharing component A3; the label service component A1 extracts the corresponding data label and initiates an instruction to extract the corresponding resource from the edge data management component A4 or the data sharing component A3, and the data sharing component A3 sends the corresponding resource to the edge data management component A4 after receiving the instruction;

[0052] A4. If all resources cannot be obtained based on the current edge service terminal A, it means that some resources involved in the resource access request message are stored in one or more edge service terminals B. Then, while obtaining the data in the current edge service terminal A based on steps A2 and A3, the tag service component A2 determines whether it is necessary to initiate a data sharing request to other edge service terminals based on the resource reading permission of the current user a. If it is determined that a data sharing request is to be initiated, the data tags corresponding to the resources that do not exist in the edge service terminal A are extracted from the resource access request message. The resources involved in these non-existent data tags may be stored in the cloud data management component or the edge service terminal B. In the data sharing component B3 or the edge data management component B4, the tag service component A2 determines the edge data management component B4 (which may be one or more) containing the required external resources based on the data tag, locates the edge service terminal B, and sends all the required external data tag information to the tag service component B2. The tag service component B2 verifies the legitimacy of the identity of the edge service terminal A and determines its resource reading authority. If the authority is satisfied, it extracts the resource information contained in the tag information belonging to the edge data management component B4, retrieves whether the resources involved in the remaining tag information exist in the data sharing component B3, and feeds back the result to the tag service component A2;

[0053] If all resources are included in the edge service terminal B, the label service component B2 sends a resource call message to the edge data management component B4 and the data sharing component B3. The data sharing component B3 extracts the corresponding resources and sends them to the edge data management component B4. After combining, they are passed to the edge service component A1 through the edge service component B1. The edge service component A1 sends all resources to the user a, and caches the resources extracted by the data sharing component B3 in the data sharing component A3.

[0054] If all located edge service terminals B cannot provide all resources, the tag service component A2 further confirms the information of the retrieved resources to the cloud server;

[0055] A5. The cloud server searches the cloud data tag library according to the data tag information uploaded by the tag service component A2 to find the required resources. If the required resources are found to be located at a certain edge service terminal C, the corresponding information location and tag information are fed back to the edge service terminal. The tag service component A2 updates its own tag information library accordingly and initiates a data sharing request to the edge service terminal, and executes according to the mode of step A4. If the required resources are found to be located in the cloud data management component, the resource reading permission of the edge service terminal A is verified. If it is passed, the resources of the cloud data management component are called and sent to the data sharing component A3.

[0056] Furthermore, in order to ensure the security of cloud resources and data temporarily retained in data sharing components, and at the same time reduce the data storage and maintenance pressure of edge service terminals, the resource data transmitted from the cloud data management component to the data sharing component and between any data sharing components also includes a pre-deletion flag code given by the cloud data management component. The pre-deletion flag code represents the time limit that the resource message can be saved after arriving at the data sharing component or the number of times the resource can be transmitted or read.

[0057] The pre-deletion flag code can be used to control the time and number of times cloud data is called or retained in the data sharing component, avoiding the long-term continuous storage of important data in the edge service terminal, thereby improving data security.

[0058] In the above steps, the legitimacy of the user or terminal identity is verified, and the corresponding user identity is assigned to the user. It is mainly used to implement the legitimacy verification of the request end and the data end based on the identity authentication process, and to realize the control requirements for data call permissions.

[0059] As a preferred implementation, it can be implemented in the following manner: configure the client on the user side and the edge service terminal side, configure the verification server on the cloud, after the data requester initiates a resource access request, the edge resource service component or the cloud resource service component verifies the request content and the identity information of the requester, if the verification is successful, the authorization permission information is issued through the client, the client requests data access permission from the verification server through the received authorization permission information, the verification server verifies the client identity and authorization permission information, if successful, the corresponding data access permission is granted, otherwise, it is not authorized and the corresponding information is fed back to the client; the client obtains the corresponding data from the data end based on the corresponding data access permission under authorization, the data end confirms the validity of the data access permission to the verification server, if valid, data transmission is executed, if invalid, the corresponding message is fed back to the client.

[0060] During the operation of the Internet of Things management and control system, users appear in the service areas of different edge service terminals, or use services or data content provided by different edge service terminals. In order to avoid redundant data forwarding and transmission content, improve the efficiency of data transmission, and enhance the real-time nature of service content, in addition to the aforementioned steps, this embodiment also includes a step for adjusting the edge service terminal to which the user belongs, which is used to transfer the service area of ​​one edge service terminal to the service area of ​​another edge service terminal when the user's location or service content changes, so that it has a shorter data transmission link or a more matching service relationship;

[0061] Specifically: when the location of user a or the service content of user a changes, the edge service terminal A collects reference attributes related to the location of user a and the service content, and determines the matching degree between user a and the location or service content of edge service terminal A according to the preset matching degree. If the matching degree is lower than a certain threshold, the reference attributes are uploaded to the cloud server; the cloud server determines the best edge service terminal B according to the reference attributes, and sends a transfer request to edge service terminal B. Edge service terminal B verifies the identity and data permissions of user a. If the verification is successful, a transfer message is sent to edge service terminal A. Edge service terminal A transfers the attribute parameters and service content information of user a to edge service terminal B, and edge service terminal B provides subsequent services. If the verification of user a fails, a message is fed back to the cloud server, and the cloud server re-searches for the best edge service terminal other than edge service terminal B.

[0062] Based on the above steps, different edge service terminals can be used flexibly to provide services to users according to their actual locations or the distribution of the services or data they need, thereby effectively reducing the time required for data transmission across edges, reducing the number of data verification and forwarding, improving service efficiency, and realizing IoT control management in a more reasonable and effective manner.

[0063] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention, rather than to limit the scope of protection of the present invention. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solution of the present invention can be modified or replaced by equivalents without departing from the essence and scope of the technical solution of the present invention.

Claims

1. An Internet of Things management and scheduling system for cloud-edge-end collaboration, characterized in that: Includes cloud service center layer and edge information layer; The cloud service center layer is composed of cloud tag service components, cloud data management components, and cloud resource scheduling components; the edge information layer includes multiple edge service terminals, which are composed of edge resource service components, edge tag service components, data sharing components, and edge data management components; The cloud tag service component creates a data tag library for tagging terminals, IoT resources and their attributes based on IoT structure information, and implements the addition, deletion and modification of tag information; The cloud data management component stores and maintains important cloud resource data, and extracts data and sends it to the data sharing component according to the instructions of the cloud resource scheduling component; The cloud resource scheduling component extracts the corresponding data tags from the data tag library according to the resource access request message uploaded by the edge information layer, and sends the tags to the tag service component according to the demand, or sends the cloud resource data to the data sharing component; The edge resource service component reads the resource requirements of the user side, verifies the legitimacy of the user, and establishes a data transmission channel with the user; The tag service component parses user resource access requests, extracts data tag information and sends resource extraction instructions internally, data sharing requests externally, and resource access requests to the cloud; The data sharing component establishes temporary storage for frequently called shared resources or cloud resources; The edge data management component stores and maintains the inherent data or necessary data within the service scope of the edge service terminal; It also includes a device perception layer, which includes resource perception devices and control execution devices; the resource perception devices are used to collect IoT resources and status information and upload them to the cloud tag service component.

2. The IoT management and scheduling system for cloud-edge-end collaboration according to claim 1 is characterized in that: The data tags include at least edge service terminal tags, IoT device tags, user tags, and application service tags; The edge service terminal tag contains the edge service terminal ID, the management side cloud system ID, the terminal location information, and the terminal server network information; the IoT device tag information contains the device type, the edge service terminal ID to which the device belongs, the device attributes, the device address, and the attribute parameters; the user tag information contains the user identity ID, user category, the edge service terminal ID to which it belongs, and the user verification information; The application service tag information includes the application service ID, application service management terminal ID, and application service deployment status.

3. The IoT management and scheduling system for cloud-edge-end collaboration according to claim 1 is characterized in that: The data tag information includes: obtaining the device or terminal ID from the unique MAC address of the hardware determined in the network structure formed by the TCP / IP protocol; and determining the device type and device attribute information based on the code compiled based on the product electronic code coding standard.

4. The data interaction method based on the Internet of Things management and scheduling system in claim 1 is characterized in that: The steps include: A1, user a initiates a resource access request, which is directly uploaded to the resource service component A1 of the edge service terminal A. The resource service component A1 verifies the legitimacy of the identity of user a and assigns a corresponding user identity to it; A2, label service component A2 determines the resource reading permission based on the determined user identity of user a, and searches for the corresponding resource location from the data label library stored in label service component A2 according to the resource access request message submitted by user a; A3, if all resources can be obtained based on the current edge service terminal A, it means that all resources involved in the resource access request message are stored in the edge data management component A4 in the edge service terminal A or temporarily stored in the data sharing component A3; the label service component A2 extracts the corresponding data label and initiates an instruction to extract the corresponding resource from the edge data management component A4 or the data sharing component A3, and the data sharing component A3 sends the corresponding resource to the edge data management component A4 after receiving the instruction; A4. If all resources cannot be obtained based on the current edge service terminal A, it means that some resources involved in the resource access request message are stored in one or more edge service terminals B. Then, while obtaining the data in the current edge service terminal A based on steps A2 and A3, the tag service component A2 determines whether it is necessary to initiate a data sharing request to other edge service terminals based on the resource reading permission of the current user a. If it is determined that a data sharing request is to be initiated, the data tags corresponding to the resources that do not exist in the edge service terminal A are extracted from the resource access request message. The resources involved in these non-existent data tags are stored in the cloud data management component or the edge service terminal B. In the data sharing component B3 or edge data management component B4 in terminal B, the tag service component A2 determines the edge data management component B4 containing the required external resources based on the data tag, locates the edge service terminal B, and sends all the required external data tag information to the tag service component B2. The tag service component B2 verifies the legitimacy of the identity of the edge service terminal A and determines its resource reading authority. If the authority is satisfied, it extracts the resource information in the edge data management component B4 contained in the tag information, retrieves whether the resources involved in the remaining tag information exist in the data sharing component B3, and feeds back the result to the tag service component A2; If all resources are included in the edge service terminal B, the label service component B2 sends a resource call message to the edge data management component B4 and the data sharing component B3. The data sharing component B3 extracts the corresponding resources and sends them to the edge data management component B4. After combining, they are passed to the resource service component A1 through the edge service component B1. The resource service component A1 sends all resources to the user a, and caches the resources extracted from the data sharing component B3 in the data sharing component A3. If all located edge service terminals B cannot provide all resources, the tag service component A2 further confirms the information of the retrieved resources to the cloud server; A5. The cloud server searches the cloud data tag library according to the data tag information uploaded by the tag service component A2 to find the required resources. If the required resources are found to be located at a certain edge service terminal C, the corresponding information location and tag information are fed back to the edge service terminal. The tag service component A2 updates its own tag information library accordingly and initiates a data sharing request to the edge service terminal, and executes according to the mode of step A4. If the required resources are found to be located in the cloud data management component, the resource reading permission of the edge service terminal A is verified. If it is passed, the resources of the cloud data management component are called and sent to the data sharing component A3.

5. The data interaction method of the Internet of Things management and scheduling system according to claim 4 is characterized in that: The resource data transmitted from the cloud data management component to the data sharing component and between any data sharing components also includes a pre-deletion flag code given by the cloud data management component. The pre-deletion flag code represents the time limit for which the resource message can be saved after arriving at the data sharing component or the number of times the resource can be transmitted or read.

6. The data interaction method of the Internet of Things management and scheduling system according to claim 4 is characterized in that: The verification of the legitimacy of the user or terminal identity and the assignment of a corresponding user identity to the user specifically refers to: configuring a client on the user side and the edge service terminal side, configuring a verification server on the cloud, and after the data requester initiates a resource access request, the edge resource service component or the cloud resource service component verifies the request content and the identity information of the requester. If the verification is successful, the authorization permission information is issued through the client, and the client requests data access permission from the verification server through the received authorization permission information. The verification server verifies the client identity and authorization permission information, and if successful, grants the corresponding data access permission, otherwise, does not authorize and feeds back the corresponding information to the client; the client obtains the corresponding data from the data terminal based on the corresponding data access permission under authorization, and the data terminal confirms the validity of the data access permission to the verification server. If valid, data transmission is executed, and if invalid, the corresponding message is fed back to the client.

7. The data interaction method of the Internet of Things management and scheduling system according to claim 4 is characterized in that: The method further includes a step of adjusting the edge service terminal to which the user belongs, for transferring the service area of ​​one edge service terminal to the service area of ​​another edge service terminal when the user's location or service content changes, so as to provide the user with a shorter data transmission link or a more matching service relationship; specifically: When the location of user a or the service content of user a changes, the edge service terminal A collects the location of user a and the reference attributes related to the service content, and determines the matching degree between user a and the location of the edge service terminal A or the service content according to the preset matching degree. If the matching degree is lower than a certain threshold, the reference attributes are uploaded to the cloud server; The cloud server determines the best edge service terminal B based on the reference attributes and sends a transfer request to the edge service terminal B. The edge service terminal B verifies the identity and data permissions of user a. If the verification is successful, it sends a transfer message to the edge service terminal A. The edge service terminal A transfers the attribute parameters and service content information of user a to the edge service terminal B. Service terminal B provides subsequent services. If user a fails the verification, it will feedback the message to the cloud server. The cloud server then searches again for the best edge service terminal other than edge service terminal B.

Images