Equipment management method and system and storage medium

Abstract

The invention discloses a device management method and system and a storage medium, and the method comprises the steps: obtaining the message reporting number of Internet of Things platform devices, determining the devices with the message reporting number exceeding a threshold value, and obtaining a first list; obtaining each user account and each user account active condition recorded in the background to obtain a second list; according to an association relationship between the equipment in the first list and the user account in the second list, determining the equipment of which the activeness is lower than a preset value to obtain a third list; and the message reporting authority of the equipment in the third management list is managed, and the equipment in the third management list is forbidden if necessary, so that the cost is reduced.

Description

Technical Field

[0001] The present application relates to the field of information processing technology, and specifically provides a method, system and storage medium for device management. Background Art

[0002] With the continuous advancement of technology, cloud computing services can be divided into three levels: Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS), and Software-as-a-Service (SaaS). Among them, Alibaba Cloud IoT Platform, Tuya Cloud, Tencent IoT Platform, etc. are relatively well-known IoT platforms.

[0003] With the growth of devices and the saturation of the smart home market, the IoT platform has increased its resource usage, resulting in an increased burden, which in turn transfers the pressure to the enterprises or organizations using it, making them face new challenges in cost control. In response to this change, enterprises or organizations need to optimize their device management strategies to reduce unnecessary communication expenses.

[0004] Therefore, how to manage equipment and reduce costs has become a problem that needs to be solved urgently. Summary of the invention

[0005] The present application aims to provide a method for equipment management, aiming to solve the problems of improper equipment management and cost control.

[0006] According to a first aspect of the present disclosure, a method for device management is provided, comprising:

[0007] Obtain the number of messages reported by devices on the IoT platform, determine the devices whose message reports exceed a threshold, and obtain a first list;

[0008] Obtain each user account and the activity status of each user account recorded in the background to obtain a second list;

[0009] According to the association relationship between the devices in the first list and the user accounts in the second list, determine the devices whose activity is lower than a preset value, and obtain a third list;

[0010] Manage the message reporting permissions of the devices in the third list.

[0011] Optionally, the number of message reports from the IoT platform devices is obtained, and the devices whose message reports exceed a threshold are determined to obtain a first list, including:

[0012] The device reporting information is obtained through the IoT platform, forwarded to the distributed stream processing platform, and stored in a distributed file system. HQL is used to count the number of each device and the corresponding device reporting information.

[0013] Optionally, the number of message reports from the IoT platform devices is obtained, and the devices whose message reports exceed a threshold are determined to obtain a first list, including:

[0014] Pre-set a first time period and a threshold value, and count the amount of information reported by the device within the first time period;

[0015] The number of reported information is compared with the threshold. When the number of reported information is greater than the threshold, the device account and the number of reported information of the device are included in the first list.

[0016] Optionally, each user account and the activity status of each user account recorded in the background are obtained to obtain a second list, including:

[0017] User activity information includes but is not limited to active duration and interaction frequency;

[0018] Obtaining the active duration and interaction frequency of each user account, and if the active duration exceeds a preset duration threshold, and the interaction frequency exceeds a preset frequency threshold, obtaining a second list;

[0019] The second list is temporarily stored in the Redis cache, and the second list temporarily stored in Redis is periodically stored in the MySQL database.

[0020] Optionally, the second list includes at least one of the following sets: a monthly activity set corresponding to the user account, a weekly activity set corresponding to the user account, and a daily activity set corresponding to the user account;

[0021] Among them, the monthly active set is for a period of one month, and the user activity exceeds the preset first active threshold; the weekly active set is for a period of one week, and the user activity exceeds the preset second active threshold; the daily active set is for a period of one day, and the user activity exceeds the preset third active threshold.

[0022] Optionally, according to the association relationship between the devices in the first list and the user accounts in the second list, the devices whose activity is lower than a preset value are determined to obtain a third list, including:

[0023] When the device is connected to the Internet using a terminal, it is uploaded to the platform, and the platform will associate the device with the user account to obtain the binding relationship between the user and the device;

[0024] Through the first list, the second list and the binding relationship between the user and the device, a joint table query is performed to obtain the third list.

[0025] Optionally, the message reporting authority of the devices in the third list is managed, including:

[0026] The third list is read on the IoT platform, and the disabling operations are performed one by one. Meanwhile, the disabling status is synchronized to the IoT platform through API calls.

[0027] Optionally, after disabling a device in the third list, if the device restarts and reconnects to WIFI, the device ID is deleted from the third list, and then the device reported messages and the corresponding number of items are reacquired to determine whether the number of reported information items exceeds the threshold. If it exceeds the threshold, the device and the number of reported information items are included in the first list.

[0028] According to a second aspect of the present disclosure, a computing system is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, a device management method as described above is implemented.

[0029] According to a third aspect of the present disclosure, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is loaded and executed by a processor, any of the above-mentioned device management methods is adopted.

[0030] In summary, the method, system and storage medium of the present invention provide a more efficient and intelligent device management solution compared with the prior art. Through the first list of devices that need to be paid and the second list of user activity in the application, a third list of inactive devices with no actual user interaction is obtained. By managing the devices in the third list, device allocation and resource optimization are performed, and disabling the devices in the third list can achieve the effect of reducing costs.

[0031] The specific implementation methods of the present application are further described in detail below in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in describing the embodiments of the present application are briefly introduced below.

[0033] Figure 1 A schematic diagram of a device management method provided in an embodiment of the present application;

[0034] Figure 2 A schematic diagram of the hardware structure of a device management system provided in an embodiment of the present application;

[0035] Figure 3 A schematic diagram of the hardware structure of another device management system provided in an embodiment of the present application;

[0036] Figure 4A schematic diagram of a process flow included in a device management system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0037] The embodiments of the present application are described below in conjunction with the drawings in the present application. It should be understood that the implementation methods described below in conjunction with the drawings are exemplary descriptions for explaining the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions of the embodiments of the present application.

[0038] If there are descriptions involving "first" or "second" in the embodiments of the present application, the descriptions of "first" or "second" are only used for descriptive purposes and cannot be understood as indicating or suggesting their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" or "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in the field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by this application.

[0039] Figure 1 A flowchart of a device management method provided by an embodiment of the present disclosure.

[0040] like Figure 1 As shown, the method comprises the following steps:

[0041] Step 101, obtain the number of message reports from devices on the Internet of Things platform, determine the devices whose message reports exceed a threshold, and obtain a first list.

[0042] This step involves counting the number of reported information by devices that exceed the threshold, aiming to quickly identify those devices with a large number of reports. Since a fee will be charged for reporting more than the threshold, the devices in the first list are required to pay fees to the platform. The first list helps enterprises or organizations to clarify the reasons for paying fees. The IoT platform refers to the PaaS platform, mainly Alibaba Cloud IoT platform, Tuya Cloud, Tencent IoT platform, etc. In order to further optimize the device management process, steps can be added to classify the devices in the first list. The classification can be based on device type, department, reporting frequency, etc., to facilitate subsequent management and cost accounting. For example, device types can be divided into sensor type, controller type, actuator type, etc., or classified according to the department to which they belong, such as production line equipment, R&D test equipment, etc. Through such classification, enterprises or organizations can more effectively monitor and manage the operating status of equipment, while reasonably allocating resources and optimizing costs.

[0043] Cost accounting is performed on the classified devices. The fees payable for each device are calculated based on the amount of information reported by the device and the preset fee standards. The list records the fee information of each device in detail, including the device ID (Identity document), the amount of reported information, the fees payable, etc. The first list is provided to relevant companies or organizations so that they can pay the fees according to the content of the list. At the same time, the IoT platform will also charge fees based on the first list to ensure the economic efficiency of the platform operation. Through such a process, the automation of device management and the transparency of fee collection can be achieved, improving the efficiency and reliability of the entire system.

[0044] Obtain the number of messages reported by devices on the IoT platform, determine the devices whose message reports exceed the threshold, and obtain a first list, including:

[0045] The device reporting information is obtained through the IoT platform, forwarded to the distributed stream processing platform, and stored in a distributed file system. HQL is used to count the number of each device and the corresponding device reporting information.

[0046] That is, the device reported information is obtained through the IoT platform, and the reported information is forwarded to the Kafka middleware, and the distributed file system HDFS is stored, and the ID of each device and the number of corresponding device reported information are counted through HQL. Among them, Kafka middleware is a distributed message queue (Message Queue) based on the publish / subscribe mode, and can also be regarded as an open source distributed event streaming platform (Event Streaming Platform). It is widely used in the field of big data real-time processing. It allows the system to publish and subscribe to data streams in a high-throughput manner while ensuring low latency and high reliability of data. Kafka middleware is a messaging system that is suitable for various scenarios that require real-time data processing and messaging. HDFS (Hadoop Distributed File System) is a Hadoop distributed file system, one of the core components of Hadoop, and exists as the lowest-level distributed storage service. It is a file system used to store files and locate files through a directory tree; secondly, it is distributed and is implemented by many servers working together to realize its functions. The servers in the cluster have their own roles. Therefore, HDFS is a distributed file system with high fault tolerance, high scalability, and high performance, and is suitable for large-scale data storage and processing scenarios. HQL stands for Hive Query Language, which is a SQL-like query language defined in Hive. It supports the operation and management of large-scale data sets. Hive also provides the function of statistical information quantity to help users tune and optimize SQL.

[0047] Obtain the number of message reports from devices on the IoT platform, determine the devices whose message reports exceed a threshold, and obtain a first list, including presetting a first time period and a threshold, and counting the number of reported information from the devices within the first time period; comparing the number of reported information with the threshold, and when the number of reported information is greater than the threshold, the device account and the number of reported information of the device are included in the first list.

[0048] The first time period is generally set to one day, and can also be adjusted to a week, a month, or other time periods based on actual conditions. Such flexibility allows enterprises or organizations to optimize equipment management strategies based on the cyclical characteristics of their own businesses. For example, for equipment that requires periodic maintenance, a longer time period can be set to count reported information in order to better plan maintenance cycles and resource allocation. For equipment that requires real-time monitoring, a shorter time period can be set to ensure timely response to changes in equipment status. The threshold is generally set to 100, and the specific adjustment is based on the corresponding number of free platform items. The threshold is set to the maximum value of the platform's free number of items, that is, when the number of reported information of the device exceeds this threshold, the excess information will be charged. The first list contains the number of reported information, which is mainly used to preliminarily screen out devices whose number of reported messages exceeds the threshold.

[0049] In addition, for the equipment in the first list, a real-time early warning mechanism is established to monitor abnormal conditions of the equipment; the equipment operating status is divided into three levels: normal, early warning, and failure, and corresponding measures are taken according to different levels to provide remote early warning prompts for equipment in the early warning state. This can effectively prevent equipment failures and ensure the stable operation of the equipment. In addition, real-time data monitoring is performed on the equipment in the first list, its operating status is analyzed, and corresponding maintenance strategies are formulated based on the analysis results. This step ensures that the equipment can operate efficiently and that measures can be taken quickly when problems arise.

[0050] Step 102, obtaining each user account and the activity status of each user account recorded in the background to obtain a second list.

[0051] This step involves analyzing the user's background activity records in the application, including user login frequency, usage time, number of interactions, etc., to determine the user's active status.

[0052] Obtain each user account and the activity of each user account recorded in the background, and obtain a second list, including, user activity including but not limited to active duration and interaction frequency; obtain the active duration and interaction frequency of each user account, if the active duration exceeds the preset duration threshold, and the interaction frequency exceeds the preset frequency threshold, obtain the second list; the second list is temporarily stored in the Redis cache, and the second list temporarily stored in Redis is regularly stored in the Mysql database. Among them, due to different types of APPs, user patterns are different, so for a cycle, such as a social media application in a day, the duration threshold can be 20 minutes, and the frequency threshold of the interaction frequency can be 5 times. The use of Redis cache improves the speed and efficiency of data processing, because it can read and write data quickly and is suitable for processing large amounts of real-time data. Regularly storing data in the database ensures the persistence and security of the data and prevents data loss due to system failures. In addition, in this way, user activity can be effectively tracked and analyzed for a long time, providing data support for subsequent user behavior prediction and personalized services.

[0053] The database is a relational database. By regularly executing data synchronization tasks, the consistency of data between the Redis cache and the database is ensured. Since the data is stored in the database, in order to maintain the consistency of data between the Redis cache and the database, a relational database is selected. The database is the Mysql database, mainly because of its stability and reliability. It also supports complex query operations and has a mature transaction processing mechanism to ensure data consistency and integrity. In addition, the Mysql database also has good scalability and flexibility, and can adapt to the growing amount of data and user needs. By storing data in the Mysql database, the security and long-term availability of user activity data can be ensured, providing a solid foundation for data analysis and decision-making.

[0054] The second list includes at least one of the following sets: a monthly active set corresponding to the user account, a weekly active set corresponding to the user account, and a daily active set corresponding to the user account; wherein the monthly active set is for a period of one month, and the user activity exceeds the preset first active threshold; the weekly active set is for a period of one week, and the user activity exceeds the preset second active threshold; the daily active set is for a period of one day, and the user activity exceeds the preset third active threshold. The generation process of the second list includes: first, through the real-time data processing module of the device management system, the user behavior data is collected and analyzed in real time; second, the collected data is classified and summarized according to the user account to form a preliminary statistics of user activity; then, according to the preset active threshold, the user account whose activity reaches the standard is screened out; finally, these user accounts are grouped according to the periodicity of month, week, and day to form a monthly active set, a weekly active set, and a daily active set. In this way, active users in different periods can be quickly and accurately identified, providing accurate data support for subsequent user behavior analysis and personalized services.

[0055] Step 103, according to the association relationship between the devices in the first list and the user accounts in the second list, determine the devices whose activity is lower than a preset value, and obtain a third list.

[0056] By comparing and associating device IDs and user accounts, it is possible to determine which devices are used by active users, thus providing a basis for subsequent management measures.

[0057] According to the association between the devices in the first list and the user accounts in the second list, the devices whose activity is lower than the preset value are determined to obtain a third list, including uploading the devices to the platform when using the terminal to connect to the Internet. The platform will associate the devices with the user accounts to obtain the binding relationship between the user and the devices; through the first list, the second list and the binding relationship between the user and the device, a joint table query is performed to obtain the third list.

[0058] Since the third list is obtained by associating the first list and the second list, the third list may include device ID, user account and user activity, which can clearly show which devices are inactive. And the binding relationship between the device ID and the user account is obtained, that is, the device ID can be matched with the user account. Such information is of great significance for the maintenance, upgrade and user behavior analysis of the equipment. For example, by analyzing the third list, it can be found that the user use frequency of the application background of some devices is low or almost non-existent, which can be judged that it is only through the connection to the WIFI Internet to communicate with the Internet of Things platform, but the corresponding user does not use the terminal of the application and other smart terminals (such as: smart central control screen, smart speaker, etc.) to interact and control with the smart device. That is, the list of inactive devices can be screened out. Although the number of reported messages is greater than the threshold, it is only the basic background operation without actual user interaction. The third list can also be used as data support to help managers allocate equipment and optimize resources to improve overall operational efficiency.

[0059] Step 104: Manage the message reporting authority of the devices in the third list.

[0060] This step allows equipment managers to monitor the operating status of equipment in real time without having to visit the site in person, and to perform remote diagnosis and processing in a timely manner when abnormalities are found. In this way, managers can save a lot of time and resources while ensuring stable operation and rapid response of equipment. In addition, remote monitoring and fault diagnosis functions can also reduce downtime caused by equipment failures and improve equipment availability and reliability. Through the collection and analysis of real-time data, managers can evaluate the performance of equipment and formulate corresponding maintenance plans based on the analysis results, thereby achieving preventive maintenance and avoiding potential failures.

[0061] The message reporting authority of the devices in the third list is managed, including reading the third list on the IoT platform, performing disabling operations one by one, and synchronizing the disabling status to the IoT platform through API calls.

[0062] For the management of the third list, the active duration and interaction frequency recorded by the devices in the third list in the background can also be detected. When the duration and interaction frequency are lower than the threshold within a period, the disabling operation is enabled. The period can be one day, one week or one month, etc. The threshold can refer to the above. This helps to timely eliminate or maintain those devices that have not been used for a long time, reduce resource waste, and ensure that only active devices that actually contribute to the business are retained in the system. In this way, the efficiency of equipment use can be effectively improved, maintenance costs can be reduced, and potential risks caused by obsolete or damaged equipment can be avoided. In addition, the use of automated scripts also reduces the workload of managers, allowing them to devote more time and energy to other key tasks. Ultimately, this approach helps to build a more efficient, economical and sustainable device management environment. Among them, API calls refer to the calls of the application programming interface. It is a way of communication between software, allowing different software applications or components to exchange data or request services. Through API calls, one software can request a specific function or service provided by another software without knowing the internal implementation details of the function. This approach promotes modularity, scalability and interoperability, allowing developers to build more complex and powerful applications.

[0063] After disabling the devices in the third list, if the device restarts and reconnects to WIFI, the device ID will be deleted from the third list, and then the device reported messages and the corresponding number of messages will be re-obtained to determine whether the number of reported messages exceeds the threshold. If it exceeds the threshold, the device ID and the number of reported messages will be included in the first list.

[0064] like Figure 2 As shown, a computing system provided in an embodiment of the present application includes a communication interface, a bus, a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, a device management method such as any one of the above is implemented.

[0065] The processor, memory and communication interface may be connected via a bus.

[0066] The processor is the control center of the computing system, which can be a single processor or a general term for multiple processing elements. For example, the processor can be a general-purpose central processing unit (CPU) or other general-purpose processors. The general-purpose processor can be a microprocessor or any conventional processor. As an embodiment, the processor can include one or more CPUs, such as Figure 2The CPU 0 and CPU 1 shown in FIG. The memory may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0067] In one possible implementation, the memory may exist independently of the processor, and the memory may be connected to the processor via a bus to store instructions or program codes. When the processor calls and executes the instructions or program codes stored in the memory, the resource scheduling method provided in the following embodiment of the present invention can be implemented. In another possible implementation, the memory may also be integrated with the processor to form a communication interface for connecting the computing system to other devices via a communication network, and the communication network may be Ethernet, a wireless access network, a wireless local area network, etc. The communication interface may include a receiving unit for receiving data, and a sending unit for sending data. The bus may be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, or an extended industry standard architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 2 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus. Figure 3 FIG. 2 shows another hardware structure of the device management system in an embodiment of the present invention. Figure 3 As shown, the computing system may include a processor and a communication interface. The processor is coupled to the communication interface. The functions of the processor may refer to the description of the above processor. In addition, the processor also has a storage function and may function as the above memory. The communication interface is used to provide data to the processor. The communication interface may be an internal interface of the device management system or an external interface of the device management system (equivalent to the communication interface). It should be noted that Figure 2 (or Figure 3 The structure shown in ) does not constitute a limitation on the device management system, except Figure 2 (or Figure 3 ) In addition to the components shown in the figure, the computing system may include more or fewer components than shown, or combine certain components, or arrange the components differently. Figure 4As shown, a device management method provided by an embodiment of the present application includes the following steps: S201, obtain the first list: obtain the number of message reports from the IoT platform devices, determine the devices whose message reports exceed the threshold, including obtaining device report information through the PaaS platform, forwarding the report information to the kafka middleware, and storing the distributed file system HDFS, and counting the ID of each device and the number of corresponding device report information through HQL. S202, obtain the second list: obtain the user account of the application through the SaaS platform, and select HTTP as one of the communication methods. When data is transmitted between the SaaS platform and the application, the HTTP protocol can be used to send and receive requests and responses containing information such as user accounts; HTTP is the HyperText Transfer Protocol. Obtain the active duration and interaction frequency of each user account. If the user's activity exceeds the preset active threshold, it will be included in the second list; the second list is temporarily stored in the Redis cache, and the second list temporarily stored in Redis is regularly stored in the database. S203, get the third list: when the device is connected to the Internet using the terminal, it is uploaded to the platform, and the platform will associate the device ID with the user account to obtain the binding relationship between the user and the device; through the first list, the second list and the binding relationship between the user and the device, a table query is performed in the Mysql database of the SaaS platform to obtain the third list. S204, manage the third list: read the third list on the IoT platform, perform the disabling operation one by one, and synchronize the disabling status to the IoT platform through API calls. After disabling the device in the third list, if the device restarts and reconnects to WIFI, the device ID is deleted from the third list, and then the device report message and the corresponding number are obtained again to determine whether the number of reported information exceeds the threshold. If it exceeds the threshold, the device ID and the number of reported information are included in the first list. At the same time, it can also include updating the list information: after the device is disabled, the system will automatically update the third list, mark the status of the disabled device as "disabled", and record the disabling time. In addition, the management process can also be optimized: by analyzing the data in the third list, the device usage pattern and user behavior can be deeply analyzed, thereby optimizing the device allocation and management strategy. For example, for devices that have been inactive for a long time, you can consider maintenance, upgrading or replacement. Reports can also be generated: The system can generate device management reports based on the first to third lists, including key indicators such as device usage and activity, to provide data support for device management decisions. Security measures can also be taken: To protect user privacy and data security, the system uses encryption technology when processing user accounts and device IDs, and ensures that all data transmissions meet security standards. In addition, the system will conduct regular security audits to ensure the security and compliance of management processes.

[0068] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the system can be divided into different functional modules to complete all or part of the functions described above.

[0069] An embodiment of the present application provides a computer program product including instructions. When the computer program product is run on a computer, the computer is enabled to execute the device management method in the above method embodiment.

[0070] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. When the computer program is loaded and executed by a processor, any of the above-mentioned device management methods is adopted.

[0071] Among them, the computer-readable storage medium, for example, can be but not limited to an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory, a register, a hard disk, an optical fiber, a portable compact disk read-only memory (Compact Disc Read-Only Memory, CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above, or any other form of computer-readable storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and can write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC). In an embodiment of the present application, the computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it. The computing system, computer-readable storage medium, and computer program product in the embodiments of the present invention can be applied to the above method.

[0072] In summary, the method, system and storage medium of the present invention provide a more efficient and intelligent device management solution compared with the prior art. Through the first list of devices that need to be paid and the second list of user activity in the application, a third list of inactive devices with no actual user interaction is obtained. By managing the third list, device allocation and resource optimization are performed, and disabling the third list can achieve the effect of reducing costs.

[0073] Although the present application has been depicted and described as a method for device management, it should be understood that various changes, modifications and equivalent substitutions can be made to the present application without departing from the spirit and scope of the present application. Therefore, for technicians in the relevant fields, after understanding the basic ideas and specific implementation methods of the present application, many possible changes, modifications and equivalent substitutions can be made, and these changes, modifications and equivalent substitutions should be regarded as belonging to the protection scope of the present application.

Claims

1. A method for device management, characterized in that: Obtain the number of messages reported by devices on the IoT platform, determine the devices whose message reports exceed a threshold, and obtain a first list; Obtain each user account and the activity status of each user account recorded in the background to obtain a second list; According to the association relationship between the devices in the first list and the user accounts in the second list, determine the devices whose activity is lower than a preset value, and obtain a third list; Manage the message reporting permissions of the devices in the third list.

2. The device management method according to claim 1, characterized in that: Obtain the number of messages reported by devices on the IoT platform, determine the devices whose message reports exceed the threshold, and obtain a first list, including: The device reporting information is obtained through the IoT platform, forwarded to the distributed stream processing platform, and stored in a distributed file system. HQL is used to count the number of each device and the corresponding device reporting information.

3. The device management method according to claim 1, characterized in that: Obtain the number of messages reported by devices on the IoT platform, determine the devices whose message reports exceed the threshold, and obtain a first list, including: Presetting a first time period and a threshold, and counting the amount of information reported by the device within the first time period; The number of reported information is compared with the threshold. When the number of reported information is greater than the threshold, the device account and the number of reported information of the device are included in the first list.

4. The device management method according to claim 1, characterized in that: Obtain each user account and the activity status of each user account recorded in the background, and obtain a second list, including: The user activity information includes but is not limited to active duration and interaction frequency; Obtaining the active duration and interaction frequency of each user account, and if the active duration exceeds a preset duration threshold, and the interaction frequency exceeds a preset frequency threshold, adding the user account to the second list; The second list is temporarily stored in the Redis cache, and the second list temporarily stored in the Redis is periodically stored in the MySQL database.

5. The device management method according to claim 4, characterized in that: The second list includes at least one of the following sets: a monthly activity set corresponding to the user account, a weekly activity set corresponding to the user account, and a daily activity set corresponding to the user account; Among them, the monthly active set is for a period of one month, and the user activity exceeds the preset first active threshold; the weekly active set is for a period of one week, and the user activity exceeds the preset second active threshold; the daily active set is for a period of one day, and the user activity exceeds the preset third active threshold.

6. The device management method according to claim 1, characterized in that: According to the association relationship between the devices in the first list and the user accounts in the second list, the devices whose activity is lower than a preset value are determined, and a third list is obtained, including: When the device is connected to the Internet using a terminal, it is uploaded to the platform, and the platform will associate the device with the user account to obtain the binding relationship between the user and the device; Through the first list, the second list and the binding relationship between the user and the device, a joint table query is performed to obtain the third list.

7. The device management method according to claim 1, characterized in that: Manage the message reporting permissions of the devices in the third list, including: The third list is read on the IoT platform, disabling operations are performed one by one, and the disabling status is synchronized to the IoT platform through API calls.

8. The device management method according to claim 7, characterized in that: After disabling the devices in the third list, if the device restarts and reconnects to WIFI, the device ID will be deleted from the third list, and then the device reported messages and the corresponding number of messages will be re-obtained to determine whether the number of reported messages exceeds the threshold. If it exceeds the threshold, the device and the number of reported messages will be included in the first list.

9. A computing system comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the device management method according to any one of claims 1 to 8 is implemented.

10. A computer-readable storage medium having a computer program stored therein, characterized in that: When the computer program is loaded and executed by the processor, the device management method according to any one of claims 1 to 8 is adopted.

Images