Multi-device security management method and management system based on Internet of Things

Abstract

The present invention relates to the field of the Internet of Things (IoT) and discloses a multi-device security management method and management system based on the IoT. The method comprises: a device management module groups IoT devices within a management area according to IoT device group classification characteristics to obtain multiple IoT device groups; a device status detection device generates a device status management container for the IoT device group, obtains information about each IoT device in the IoT device group, generates an IoT device information list, and sends the list to the device status management container for the IoT device group; the device status management container for the IoT device group detects the hardware and software security of IoT devices in each IoT device group based on the IoT device information list, thereby completing the security management of multiple IoT devices. The present invention can implement targeted security management strategies and improve management flexibility and applicability.

Description

Technical Field

[0001] The present invention relates to the technical field of Internet of Things, and in particular to a multi-device security management method and management system based on the Internet of Things. Background Art

[0002] With the rapid development of IoT technology, an increasing number of devices are connected to the internet, forming a vast IoT ecosystem. These devices span a wide range of sectors, including smart homes, industrial monitoring, and smart cities. However, security issues with IoT devices are becoming increasingly prominent. Firstly, the diverse range of IoT devices, and the differences in security mechanisms and communication protocols between different manufacturers, make unified security management difficult. Secondly, IoT devices often have limited resources, such as processing power and storage space, making it difficult to deploy complex security protection mechanisms. Furthermore, IoT devices are widely distributed, operating in complex and volatile network environments, making them vulnerable to cyberattacks such as device intrusion and data tampering.

[0003] In existing IoT device security management methods, device grouping is relatively fixed, often based on simple device type or geographic location. This grouping method cannot fully adapt to the needs of different application scenarios.

[0004] Secondly, for devices distributed across different sub-regions, applying the same update strategy could cause some devices to fail or disrupt normal business operations due to factors such as network bandwidth and device load. Furthermore, the impact of software updates on device performance and the security risks involved in the update process were not fully considered when generating software update strategies.

[0005] Existing methods for hardware security testing primarily focus on isolated security checks on each device, failing to assess the overall security of the device group. When a hardware failure occurs on a device, troubleshooting is performed solely on that device, without considering the impact on the entire device group or how to leverage device redundancy to ensure overall system security. Furthermore, the troubleshooting process lacks intelligent classification and processing mechanisms, resulting in inefficient troubleshooting. Summary of the Invention

[0006] The purpose of the present invention is to overcome the shortcomings of the prior art and provide a multi-device security management method based on the Internet of Things, comprising the following steps:

[0007] Step 1: Based on the characteristics of the IoT device group classification, the device management module groups the IoT devices in the management area to obtain multiple IoT device groups;

[0008] Step 2: The device status detection device generates a device status management container for the IoT device group, obtains information about each IoT device in the IoT device group, generates an IoT device information list, and sends the list to the device status management container for the IoT device group.

[0009] Step 3: The device status management container of the IoT device group obtains the hardware security information of the IoT devices from the cloud data server based on the IoT device information list, and checks the hardware security of the IoT devices in each IoT device group. If all IoT device groups are secure, the process proceeds to step 4; otherwise, the process proceeds to step 6.

[0010] In step 4, the device status management container of the IoT device group obtains the software security information of each IoT device from the cloud data server based on the IoT device information list, and detects whether there is any software update information. If there is a software update, the software version data package and the estimated update time of the corresponding IoT device are sent to the IoT device software security management container, and a software update list is generated, and the process proceeds to step 5; otherwise, the process proceeds to step 7;

[0011] Step 5: Generate a software security update strategy based on the characteristics of the IoT device group classification, perform IoT device software updates, and proceed to step 7;

[0012] Step 6: Classify and troubleshoot IoT device faults based on IoT device hardware security information, and then return to step 4.

[0013] Step 7: Complete the security management of multiple IoT devices.

[0014] Furthermore, according to the characteristics of the IoT device group classification, the device management module groups the IoT devices to obtain multiple IoT device groups, including:

[0015] The IoT device group division feature is one of sub-area features, device type, and working period; each IoT device is grouped according to the IoT device group division feature to obtain multiple IoT device groups, and the basic device redundancy of each IoT device group is obtained respectively.

[0016] Furthermore, the obtaining of hardware security information of IoT devices in the cloud data server and detecting the hardware security of IoT devices in each IoT device group include:

[0017] According to the types of IoT devices contained in the management area, the hardware security information of the corresponding device type is obtained from the cloud data server, and the security status of the IoT devices in each IoT device group is obtained respectively. According to the security status of each IoT device in the IoT group, the device redundancy of the corresponding IoT device group is obtained according to the redundancy of the basic device. If the device redundancy of the corresponding IoT device group is greater than the device redundancy threshold, the IoT device group is safe; otherwise, it is unsafe.

[0018] Furthermore, the step of obtaining software security information of each IoT device from the cloud data server and detecting whether a software update is available includes:

[0019] According to the types of IoT devices contained in the management area, the software version information of the corresponding device type is obtained from the cloud data server and compared with the software version of each IoT device in the IoT device group. If the software version of an IoT device in the IoT device group is inconsistent with the software version of the corresponding device type obtained from the cloud data server, there is a software update.

[0020] Furthermore, the software version data package and the estimated update duration of the corresponding IoT device are sent to the IoT device software security management container to generate a software update list, including:

[0021] According to the IoT device types with inconsistent software versions, the software version data package of the corresponding IoT device type in the cloud data server is obtained, and the estimated update time is obtained. The software version data package and the estimated update time of the corresponding IoT device are sent to the IoT device software security management container to generate update information for the corresponding IoT device type; all update information of the corresponding IoT device type constitutes a software update list.

[0022] Furthermore, the software security update strategy is generated based on the characteristics of the IoT device group classification to perform IoT device software updates, including:

[0023] According to the characteristics of the IoT device group division, the update strategy corresponding to the characteristics of the IoT device group division is called on the cloud data server. According to the update strategy corresponding to the characteristics of the IoT device group division, combined with the software update list, the software of the IoT device is updated.

[0024] Furthermore, the IoT device fault classification and troubleshooting based on the IoT device hardware security information includes:

[0025] The IoT device security information is security features set for the corresponding IoT device type, and the security features include device operating temperature and device output data deviation.

[0026] Furthermore, the basic device redundancy of each IoT device group is obtained separately, including:

[0027] The basic device redundancy of the IoT device group is obtained by summing the redundancy of each IoT device type in the IoT device group and multiplying it by the security weight of each IoT device type.

[0028] The redundancy of the IoT device type is the ratio of the number of IoT devices of the same type to the number of IoT devices actually in use.

[0029] A multi-device security management system based on the Internet of Things, applying the multi-device security management method based on the Internet of Things, includes a device management module, a device status detection device, a cloud data server, an edge server, a data processing module, a communication module, and an early warning module;

[0030] The device management module, device status detection device, communication module and early warning module are respectively connected to the data processing module; the cloud data server and edge server are respectively connected to the communication module;

[0031] The edge server is used for software update.

[0032] The present invention has the following beneficial effects: By introducing multiple IoT device grouping features, the present invention can flexibly adapt to device management requirements in different application scenarios. Whether grouping based on device type, sub-region characteristics, or working hours, it can implement targeted security management strategies, improving management flexibility and applicability.

[0033] By leveraging the rich data resources in cloud data servers, the present invention can more comprehensively obtain hardware and software security information about devices. With the support of cloud data, the security status of devices can be more accurately assessed, potential security risks can be discovered in a timely manner, and appropriate measures can be taken to prevent and address them.

[0034] Generating software security update policies based on IoT device group characteristics makes the software update process more intelligent and organized. By considering device group characteristics such as network bandwidth and device load, updates can be avoided during periods of high device load or network congestion, minimizing the impact of updates on normal business operations. Furthermore, by integrating the software update list, devices are updated in an orderly manner, improving update efficiency.

[0035] Hardware safety detection and troubleshooting methods based on device redundancy enable more accurate assessment of the safety status of a device group. When a device fails, redundancy can be leveraged to assign tasks from the faulty device to a redundant device, ensuring continuous system availability. Furthermore, intelligent fault classification and troubleshooting methods improve the efficiency and accuracy of troubleshooting. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 This is a flowchart of a multi-device security management method based on the Internet of Things;

[0037] Figure 2 Schematic diagram of the process for detecting IoT device hardware security for each IoT device group. DETAILED DESCRIPTION

[0038] The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings, but the protection scope of the present invention is not limited to the following.

[0039] The features and performance of the present invention are further described in detail below with reference to the embodiments.

[0040] like Figure 1 As shown, the multi-device security management method based on the Internet of Things includes the following steps:

[0041] Step 1: Based on the characteristics of the IoT device group classification, the device management module groups the IoT devices in the management area to obtain multiple IoT device groups;

[0042] Step 2: The device status detection device generates a device status management container for the IoT device group, obtains information about each IoT device in the IoT device group, generates an IoT device information list, and sends the list to the device status management container for the IoT device group.

[0043] Step 3: The device status management container of the IoT device group obtains the hardware security information of the IoT devices from the cloud data server based on the IoT device information list, and checks the hardware security of the IoT devices in each IoT device group. If all IoT device groups are secure, the process proceeds to step 4; otherwise, the process proceeds to step 6.

[0044] In step 4, the device status management container of the IoT device group obtains the software security information of each IoT device from the cloud data server based on the IoT device information list, and detects whether there is any software update information. If there is a software update, the software version data package and the estimated update time of the corresponding IoT device are sent to the IoT device software security management container, and a software update list is generated, and the process proceeds to step 5; otherwise, the process proceeds to step 7;

[0045] Step 5: Generate a software security update strategy based on the characteristics of the IoT device group classification, perform IoT device software updates, and proceed to step 7;

[0046] Step 6: Classify and troubleshoot IoT device faults based on IoT device hardware security information, and then return to step 4.

[0047] Step 7: Complete the security management of multiple IoT devices.

[0048] According to the characteristics of the IoT device group classification, the device management module groups the IoT devices to obtain multiple IoT device groups, including:

[0049] The IoT device group division feature is one of sub-area features, device type, and working period; each IoT device is grouped according to the IoT device group division feature to obtain multiple IoT device groups, and the basic device redundancy of each IoT device group is obtained respectively.

[0050] like Figure 2 As shown, the method of obtaining hardware security information of IoT devices in a cloud data server and detecting the hardware security of IoT devices in each IoT device group includes:

[0051] According to the types of IoT devices contained in the management area, the hardware security information of the corresponding device type is obtained from the cloud data server, and the security status of the IoT devices in each IoT device group is obtained respectively. According to the security status of each IoT device in the IoT group, the device redundancy of the corresponding IoT device group is obtained according to the redundancy of the basic device. If the device redundancy of the corresponding IoT device group is greater than the device redundancy threshold, the IoT device group is safe; otherwise, it is unsafe.

[0052] The process of obtaining software security information of each IoT device from the cloud data server and detecting whether a software update is available includes:

[0053] According to the types of IoT devices contained in the management area, the software version information of the corresponding device type is obtained from the cloud data server and compared with the software version of each IoT device in the IoT device group. If the software version of an IoT device in the IoT device group is inconsistent with the software version of the corresponding device type obtained from the cloud data server, there is a software update.

[0054] The software version data package and the estimated update time of the corresponding IoT device are sent to the IoT device software security management container to generate a software update list, including:

[0055] According to the IoT device types with inconsistent software versions, the software version data package of the corresponding IoT device type in the cloud data server is obtained, and the estimated update time is obtained. The software version data package and the estimated update time of the corresponding IoT device are sent to the IoT device software security management container to generate update information for the corresponding IoT device type; all update information of the corresponding IoT device type constitutes a software update list.

[0056] The method of generating a software security update strategy based on the characteristics of IoT device group classification and performing IoT device software updates includes:

[0057] According to the characteristics of the IoT device group division, the update strategy corresponding to the characteristics of the IoT device group division is called on the cloud data server. According to the update strategy corresponding to the characteristics of the IoT device group division, combined with the software update list, the software of the IoT device is updated.

[0058] The IoT device fault classification and troubleshooting based on IoT device hardware security information includes:

[0059] The IoT device security information is security features set for the corresponding IoT device type, and the security features include device operating temperature and device output data deviation.

[0060] The basic device redundancy of each IoT device group is obtained separately, including:

[0061] The basic device redundancy of the IoT device group is obtained by summing the redundancy of each IoT device type in the IoT device group and multiplying it by the security weight of each IoT device type.

[0062] The redundancy of the IoT device type is the ratio of the number of IoT devices of the same type to the number of IoT devices actually in use.

[0063] A multi-device security management system based on the Internet of Things, applying the multi-device security management method based on the Internet of Things, includes a device management module, a device status detection device, a cloud data server, an edge server, a data processing module, a communication module, and an early warning module;

[0064] The device management module, device status detection device, communication module and early warning module are respectively connected to the data processing module; the cloud data server and edge server are respectively connected to the communication module;

[0065] The edge server is used for software update.

[0066] Specifically, this invention proposes a device grouping method based on IoT device grouping characteristics, including sub-region characteristics, device type, and operating hours. This grouping mechanism allows for flexible device grouping based on the needs of specific application scenarios, providing a foundation for subsequent security management policy formulation. For example, in smart home scenarios, device groups can be formed based on device type (e.g., lighting, temperature control, and security equipment); in industrial monitoring scenarios, groups can be formed based on operating hours (e.g., production hours and maintenance hours).

[0067] This invention fully leverages the rich data resources in cloud-based data servers to obtain hardware security information, software version information, and other information from the cloud during device status detection and security assessment. This cloud-based data allows for a more comprehensive assessment of the device's security status, improving the accuracy and efficiency of status detection. For example, when detecting software updates, it not only checks whether the device's current software version is consistent with the latest version in the cloud, but also retrieves security patch information from the cloud to determine whether an urgent update is required.

[0068] This invention generates software security update policies based on the characteristics of IoT device groups. When performing software updates, it fully considers device group characteristics, such as network bandwidth and device load. Through intelligent policy generation, it ensures smooth software updates and minimizes the impact on normal business operations. Furthermore, by integrating the software update list, it enables orderly software updates for IoT devices, improving update efficiency.

[0069] When testing hardware security, the present invention determines the device redundancy of the corresponding IoT device group based on the security status of each IoT device within the group and the redundancy of the underlying devices. This device redundancy assessment can determine the security status of the device group, and when the device redundancy falls below a threshold, timely troubleshooting measures are implemented. During the troubleshooting process, faults are classified based on the IoT device hardware security information, and corresponding troubleshooting methods are employed, improving troubleshooting efficiency.

[0070] Specifically, based on the sub-area characteristics, device type, working hours and other division characteristics, the IoT devices in the management area are grouped to obtain multiple IoT device groups, and the basic device redundancy of each IoT device group is obtained respectively.

[0071] Generate a device status management container for the IoT device group, obtain information about each IoT device in the group, and generate a list of IoT devices. Based on the list, retrieve the device's hardware and software security information from the cloud data server and perform hardware and software security testing and assessment on the device.

[0072] Check for software update information. If so, send the software version data package and the estimated update time for the corresponding IoT device to the IoT device software security management container to generate a software update list. Generate a software security update policy based on the characteristics of IoT device groups and perform IoT device software updates. Classify and troubleshoot IoT device faults based on IoT device hardware security information.

[0073] Select appropriate IoT device grouping features based on specific application scenarios and management requirements. For example, in a smart home scenario, you can select device type as a partitioning feature to group lighting, temperature control, and security equipment into different device groups. In an industrial monitoring scenario, you can select working hours as a partitioning feature to divide devices into daytime high-load operation groups and nighttime low-load maintenance groups.

[0074] The device management module groups IoT devices within the management area based on selected characteristics. For sub-area characteristics, devices can be grouped based on their geographic location (e.g., GPS coordinates, network IP address, etc.); for device type, devices can be grouped based on their type identifier (e.g., device model, device function description, etc.); and for operating hours, devices can be grouped based on their operating schedules (e.g., device operation logs, preset operating hours, etc.).

[0075] After obtaining each IoT device group, calculate the basic device redundancy of each device group. The calculation formula is:

[0076]

[0077] R base For basic equipment redundancy, n is the number of IoT device types in the device group, ri For the i Redundancy of IoT device types, wi For the i The security weight of each IoT device type is calculated based on the redundancy of the IoT device type. The redundancy of an IoT device type is the ratio of the number of IoT devices of the same type to the number of IoT devices actually in use. The security weight can be set based on the importance of the device type in security. For example, a higher security weight can be set for a critical device type.

[0078] The device status detection device generates a device status management container for each IoT device group. This container is used to store and manage the status information, security information, etc. of each IoT device in the device group.

[0079] The device status detection device obtains information about each IoT device in the IoT device group, including device identification, device type, device status parameters (such as device operating temperature, device output data, etc.), etc. This information is organized according to a predetermined format to generate an IoT device information list.

[0080] Based on the IoT device list, the device status management container retrieves hardware security information for each device type from the cloud data server. The cloud data server stores a database of hardware security characteristics for different device types, including the normal operating temperature range and the normal fluctuation range of device output data. The device status management container compares this hardware security information with the device's current hardware status parameters to determine whether the device has hardware security risks.

[0081] The device redundancy of the IoT device group is calculated based on the security status (safe or vulnerable) of each IoT device within the IoT group, combined with the redundancy of the underlying devices. If the device redundancy of the IoT device group exceeds the device redundancy threshold, the IoT device group is deemed safe; otherwise, it is deemed unsafe. The device redundancy threshold can be set based on the system's security requirements. For example, in critical systems, the device redundancy threshold can be set higher to ensure system reliability.

[0082] If the IoT device group is secure, the device status management container continues to retrieve software security information for each IoT device from the cloud data server, including software version information and security patch information. The container then compares the software version information retrieved from the cloud with the software version of each IoT device in the IoT device group. If the software version of any IoT device in the IoT device group is inconsistent with the software version of the corresponding device type retrieved from the cloud data server, a software update is determined.

[0083] When a software update is detected, the device status management container retrieves the software version data package for the IoT device type with the inconsistent software version from the cloud data server and determines the estimated update duration. This estimated update duration can be estimated based on factors such as the size of the software version data package, the device's processing power, and network bandwidth. The software version data package and the estimated update duration for the IoT device are sent to the IoT device software security management container, generating update information for the IoT device type. All update information for each IoT device type constitutes a software update list.

[0084] Based on the characteristics of IoT device groups, update policies tailored to these characteristics are invoked on the cloud data server. For example, for device groups divided by sub-region characteristics, an update policy tailored to the sub-region's network environment can be invoked; for device groups divided by device type, an update policy tailored to the characteristics of that device type can be invoked. Update policies include update sequence, update time period, and update method (e.g., full update, incremental update).

[0085] Combining the software update list with the generated software security update policy, IoT devices can be updated. During the update process, the update policy can be dynamically adjusted based on factors such as device load and network bandwidth to ensure a smooth update. For example, for groups of devices with low network bandwidth, a phased update approach can be implemented to avoid network congestion caused by updating a large number of devices simultaneously.

[0086] When an IoT device group is determined to be unsafe, fault classification is performed based on the IoT device hardware security information. Fault classification can be based on factors such as fault type and severity. For example, faults can be classified as device overheating or abnormal data output.

[0087] Based on the fault classification results, adopt appropriate troubleshooting methods. For device overheating, you can take measures such as reducing the device load and increasing cooling measures. For abnormal data output, you can restart the device or reset the software. During the troubleshooting process, you can leverage device redundancy to assign tasks from the faulty device to redundant devices of the same type to ensure normal system operation.

[0088] The system includes: a device management module for communicating with various IoT devices, collecting device information, performing device grouping operations, and sending control instructions.

[0089] The device status detection device is used to generate a device status management container, obtain device information, and perform device status detection and security assessment.

[0090] Cloud data servers store large amounts of device data, security information, software version information, etc., providing data support for device status detection, software updates, etc.

[0091] Edge servers are deployed at the edge of the network, close to IoT devices, to distribute and execute software updates, reducing the burden on cloud data servers and improving update efficiency.

[0092] The data processing module processes and analyzes the data obtained from the equipment management module, equipment status detection device, etc., providing a basis for the formulation of safety management strategies.

[0093] The communication module is used for communication between the device management module, device status detection device, cloud data server, edge server, etc. to ensure real-time data transmission.

[0094] The early warning module is used to issue early warning information when it detects safety hazards or failures in the equipment so that managers can take timely measures.

Claims

1. A multi-device security management method based on the Internet of Things, characterized in that: The steps include: Step 1: Based on the characteristics of the IoT device group classification, the device management module groups the IoT devices in the management area to obtain multiple IoT device groups; Step 2: The device status detection device generates a device status management container for the IoT device group, obtains information about each IoT device in the IoT device group, generates an IoT device information list, and sends the list to the device status management container for the IoT device group. The IoT device information includes device identification, device type, and device status parameters; Step 3: The device status management container of the IoT device group obtains the hardware security information of the IoT devices from the cloud data server based on the IoT device information list, and checks the hardware security of the IoT devices in each IoT device group. If all IoT device groups are secure, the process proceeds to step 4; otherwise, the process proceeds to step 6. In step 4, the device status management container of the IoT device group obtains the software security information of each IoT device from the cloud data server based on the IoT device information list, detects whether there is any software update information, and if so, sends the software version data package and the estimated update time of the corresponding IoT device to the IoT device software security management container, generates a software update list, and proceeds to step 5. Otherwise, go to step seven; Step 5: Generate a software security update strategy based on the characteristics of the IoT device group classification, perform IoT device software updates, and proceed to step 7; Step 6: Classify and troubleshoot IoT device faults based on IoT device hardware security information, and then return to step 4. Step 7: Complete the security management of multiple IoT devices; According to the characteristics of the IoT device group classification, the device management module groups the IoT devices to obtain multiple IoT device groups, including: The IoT device group division feature is one of a sub-region feature, a device type, and a working period; the IoT devices are grouped according to the IoT device group division feature to obtain a plurality of IoT device groups, and the basic device redundancy of each IoT device group is obtained respectively; The basic equipment redundancy is: R base For basic equipment redundancy, n is the number of IoT device types in the device group, ri For the i Redundancy of IoT device types, wi For the i The security weight of each IoT device type. The redundancy of an IoT device type is the ratio of the number of IoT devices of the same type to the number of IoT devices actually in use. The method of obtaining hardware security information of IoT devices in the cloud data server and detecting the hardware security of IoT devices in each IoT device group includes: Based on the types of IoT devices contained in the management area, the hardware security information of the corresponding device type is obtained from the cloud data server, and the security status of the IoT devices in each IoT device group is obtained respectively. The hardware security information includes the normal range of the device operating temperature and the normal fluctuation range of the device output data; based on the security status of each IoT device in the IoT group, the device redundancy of the corresponding IoT device group is obtained according to the redundancy of the basic device. If the device redundancy of the corresponding IoT device group is greater than the device redundancy threshold, the IoT device group is safe; otherwise, it is unsafe.

2. The multi-device security management method based on the Internet of Things according to claim 1 is characterized in that: The process of obtaining software security information of each IoT device from the cloud data server and detecting whether a software update is available includes: According to the types of IoT devices contained in the management area, the software version information of the corresponding device type is obtained from the cloud data server and compared with the software version of each IoT device in the IoT device group. If the software version of an IoT device in the IoT device group is inconsistent with the software version of the corresponding device type obtained from the cloud data server, there is a software update.

3. The multi-device security management method based on the Internet of Things according to claim 2 is characterized in that: The software version data package and the estimated update time of the corresponding IoT device are sent to the IoT device software security management container to generate a software update list, including: According to the IoT device types with inconsistent software versions, the software version data package of the corresponding IoT device type in the cloud data server is obtained, and the estimated update time is obtained. The software version data package and the estimated update time of the corresponding IoT device are sent to the IoT device software security management container to generate update information for the corresponding IoT device type; all update information of the corresponding IoT device type constitutes a software update list.

4. The multi-device security management method based on the Internet of Things according to claim 3 is characterized in that: The method of generating a software security update strategy based on the characteristics of IoT device group classification and performing IoT device software updates includes: According to the characteristics of the IoT device group division, the update strategy corresponding to the characteristics of the IoT device group division is called on the cloud data server. According to the update strategy corresponding to the characteristics of the IoT device group division, combined with the software update list, the software of the IoT device is updated.

5. The multi-device security management method based on the Internet of Things according to claim 1 is characterized in that: The IoT device fault classification and troubleshooting based on IoT device hardware security information includes: The IoT device security information is security features set for the corresponding IoT device type, and the security features include device operating temperature and device output data deviation.

6. The multi-device security management method based on the Internet of Things according to claim 1, characterized in that: The basic device redundancy of each IoT device group is obtained separately, including: The basic device redundancy of the IoT device group is obtained by summing the redundancy of each IoT device type in the IoT device group and multiplying it by the security weight of each IoT device type. The redundancy of the IoT device type is the ratio of the number of IoT devices of the same type to the number of IoT devices actually in use.

7. Multi-device security management system based on the Internet of Things, characterized by: The multi-device security management method based on the Internet of Things according to any one of claims 1 to 6 is applied, comprising a device management module, a device status detection device, a cloud data server, an edge server, a data processing module, a communication module and an early warning module; The device management module, device status detection device, communication module and early warning module are respectively connected to the data processing module; the cloud data server and edge server are respectively connected to the communication module; The edge server is used for software update.

Images