Device cycle management method and apparatus based on internet of things technology

Abstract

The present application provides a device cycle management method based on an Internet of Things technology. The method is applied to an Internet of Things platform, the Internet of Things platform is used for managing infrastructures, and the Internet of Things platform is separately connected to Internet of Things devices and Internet of Things applications. Cycle configuration information configured by a user is acquired, a target Internet of Things device meeting a constraint condition is configured to report attribute information on the basis of a cycle in the configuration information, and cycle range configuration can be performed on a large number of Internet of Things devices by configuring the priority, time condition and the like of the cycle. Thus, dynamic adjustment and multi-dimensional computation for the cycles of the Internet of Things devices are implemented, the waste of computing resources and network resources is reduced, and the deployment and management difficulty of a complex Internet of Things system is reduced.

Description

A device cycle management method and device based on Internet of Things technology

[0001] This disclosure claims priority to Chinese patent application No. 202311421616.1, filed on October 30, 2023, entitled “A method and device for managing equipment telemetry cycles based on Internet of Things technology”, and Chinese patent application No. 202410575731.2, filed on May 8, 2024, entitled “A method and device for managing equipment cycles based on Internet of Things technology”, the entire contents of which are incorporated by reference into this disclosure. Technical Field

[0002] The present application relates to the field of Internet of Things technology, and in particular to a device cycle management method and apparatus based on Internet of Things technology. Background Art

[0003] In the practical application of IoT technology, edge device capabilities are defined based on the object model, which includes device attributes, commands, services, events, and corresponding responses. This information is transmitted between edge devices and the IoT platform through connections. The object model provides detailed definitions of attribute value constraints, such as the valid range of integer values, valid enumeration of status values, value type, and length.

[0004] However, there is no definition for the collection and reporting of attributes. As the business continues to expand, the number of IoT devices continues to increase, and the IoT system expands, it is difficult to manage the attribute cycle of IoT devices. Unreasonable cycle management will result in huge waste of network bandwidth and server computing resources.

[0005] Summary of the Invention

[0006] This application provides a device cycle management method and device based on Internet of Things technology. By defining the cycle, the Internet of Things platform issues the corresponding cycle management, so that the edge device can report its attributes according to the cycle under the corresponding cycle management, thereby realizing unified management of the edge device cycle and meeting the usage requirements of multiple business scenarios.

[0007] In the first aspect, the present application provides a cycle management method based on Internet of Things technology, which is applied to an Internet of Things platform, wherein the Internet of Things platform runs on an infrastructure. At the same time, the infrastructure is connected to Internet of Things devices and application-side devices respectively. The Internet of Things devices are used to transmit data to the Internet of Things platform, and Internet of Things applications run on the application-side devices. The method specifically includes the following steps: obtaining first cycle configuration information sent by the Internet of Things application, the first cycle configuration information including a first device constraint and a first cycle; and determining a target Internet of Things device from multiple Internet of Things devices based on the first device constraint; and then sending the first cycle to the target Internet of Things device.

[0008] In the solution provided in this application, the IoT platform should have the ability to define cycles. In one implementation method, users can input cycle configuration information on the application-side device, and the cycle configuration information is obtained by the IoT platform. The target IoT device that meets the constraint conditions among the connected IoT devices is determined through the device constraint conditions in the cycle configuration information, and the IoT cycle is issued so that the target IoT device can report attributes to the IoT platform according to the cycle. The IoT platform supports the provision of cycle configuration capabilities, so that users can directly configure the cycle through the IoT application running on the application-side device deployed locally or the application-side device deployed in the cloud. The platform can create and issue the cycle to the target device based on the cycle configuration information, thereby realizing multi-dimensional, multi-level priority, and controllable range to define the cycle, and more comprehensively realizing dynamic adjustment of the cycle of IoT devices to cope with more complex business scenarios, reduce the occupation of network resources, improve efficiency, and reduce repeated configuration.

[0009] In another possible implementation of the first aspect, the IoT platform obtains first-period configuration information sent by the IoT application, and creates a first-period policy based on the first-period configuration information, wherein the first-period policy includes a first device constraint and a first period. Furthermore, the IoT platform determines a target IoT device from IoT devices connected to the IoT platform based on the first device constraint. After determining the target IoT device, the IoT platform sends the first-period policy to the target IoT device, instructing the target IoT device to report its attribute information according to the first period.

[0010] In combination with the first aspect, in a possible implementation provided by the application, the first cycle configuration information also includes a first priority, and the first priority is used to indicate the priority of the first cycle. The method also includes the following specific steps: the Internet of Things platform sends the first priority to the target Internet of Things device; obtains the second cycle configuration information sent by the Internet of Things application, the second cycle configuration information includes a second device constraint, a second cycle and a second priority, and the second priority is used to indicate the priority of the second cycle; according to the second device constraint, determines the target Internet of Things device from the multiple Internet of Things devices; sends the second priority and the second cycle to the target Internet of Things device; when the first priority is higher than the second priority, the target Internet of Things device uses the first cycle associated with the first priority to report attribute information; and / or, when the second priority is higher than the first priority, the target Internet of Things device uses the second cycle associated with the second priority to report attribute information.

[0011] In the solution provided by this application, users can enter multiple cycle configurations through an IoT application. Each cycle configuration includes corresponding constraints and cycles. The IoT platform determines the corresponding target IoT device based on each constraint. When the same target IoT device meets the constraints of multiple cycle configurations, the IoT platform can create a cycle configuration list and send it to the target IoT device. Multiple cycles can then be sent to the target IoT device in sequence. This allows the target IoT device to store multiple cycle configurations simultaneously. The target IoT device then determines the target cycle based on its policy and its own business operations and reports its attributes to the IoT platform. In other words, the IoT platform provides the ability to simultaneously configure multiple cycles for a single IoT device, simplifying the configuration process. This allows the IoT device to determine the target cycle to execute based on the decision factors included in the policy, maximizing adaptability to various business scenarios and providing flexible configuration, making cycle management more scenario-adaptive. Furthermore, when entering cycle configuration information, users can also configure cycle priority information. This priority information indicates the priority of the cycle when the IoT platform creates the cycle. When multiple cycles exist or when multiple cycles are in a cycle list, the priority ranking can be used to determine which cycle to execute first. This allows you to configure multiple cycles at once to a target IoT device, which then determines the target cycle to execute based on the cycle's priority. Specifically, if the first priority is higher than the second, the target IoT device will report attribute information during the first cycle; or if the second priority is higher than the first, the device will report attribute information during the second cycle. This enables multi-dimensional, multi-level configurable cycles for different application and business scenarios, improving cycle configuration efficiency.

[0012] In combination with the first aspect, in a possible implementation method provided in the application, the first device constraint condition includes a first device computing power condition. Based on the first device constraint condition, a target IoT device is determined from multiple IoT devices. Specifically, the IoT platform determines the target IoT device that meets the first device computing power condition from multiple IoT devices based on the first device computing power condition.

[0013] In the solution provided in this application, in order to further adapt to the large-scale configuration of a large number of IoT devices, by configuring constraints, specific target IoT devices can be clearly identified to execute the corresponding cycle. Among them, users can limit the IoT devices that execute the corresponding cycle by configuring constraints as device computing power conditions, thereby realizing cycle configuration for IoT devices with different computing power conditions.

[0014] Priority Priority

[0015] In combination with the first aspect, in a possible implementation method provided in the application, the first cycle configuration information also includes a first time condition, which is used to indicate the effective time of the target IoT device executing the first cycle. Furthermore, the second cycle configuration information also includes a second time condition, which is used to indicate the effective time of the target IoT device executing the second cycle.

[0016] In the solution provided by the present application, when the user inputs the cycle configuration information, the time condition of the cycle can be synchronously configured, and the time condition indicates the effective time when the cycle is executed on the target IoT device. When the target IoT device obtains multiple cycles, and includes time conditions corresponding to multiple cycles, the target IoT device can determine the target cycle to be executed based on the priority and time conditions corresponding to the multiple cycles. In this way, when there is a priority conflict among multiple cycles, the target cycle to be executed can be determined according to the time condition, or when the time conditions of multiple cycles conflict, the target cycle to be executed can be determined according to the priority, further meeting multi-dimensional business scenarios and business needs.

[0017] In combination with the first aspect, in a possible implementation method provided in the application, the Internet of Things platform receives multiple reporting information sent by the target Internet of Things device, each of the multiple reporting information includes attribute information and time information of the target Internet of Things device, and determines the cycle of the target Internet of Things device based on the multiple reporting information.

[0018] In the solution provided by this application, when an IoT device reports attributes to the IoT platform according to the target cycle, it also reports time information. Based on multiple reported information, the IoT platform can determine the cycle of the reported information based on the time information in the multiple reported information, thereby determining the actual execution cycle of the target IoT device and judging whether there is a delay and whether the execution cycle is reasonable. Prompts and warnings can be given to users based on the cycle, and corresponding cycle delay information can be provided to users in a visual way, allowing users to adjust the cycle based on the delay information. This enables supervision and feedback on the execution of the cycle, improving the effectiveness of cycle execution.

[0019] On the second aspect, the present application provides a cycle management method based on Internet of Things technology, which is applied to Internet of Things devices, wherein the Internet of Things devices are connected to the infrastructure, the infrastructure is connected to the application-side devices, and an Internet of Things platform runs on the infrastructure, and an Internet of Things application runs on the application-side devices. Furthermore, the Internet of Things platform is used to receive a first cycle configuration request sent by the Internet of Things application. The method specifically includes the following steps: obtaining the first cycle sent by the Internet of Things platform, and further, sending the attribute information of the Internet of Things device to the Internet of Things platform according to the first cycle.

[0020] In the solution provided in this application, IoT devices report their attributes to the cloud management platform according to the cycle issued by the physical network platform. This allows IoT devices to report attributes according to the cycle issued by the platform, allowing them to report attributes according to the configured cycle during business execution. This reduces system management costs and deployment difficulties, and meets users' needs for unified periodic configuration of IoT devices based on actual business needs.

[0021] In combination with the first aspect, in a possible implementation method provided in the application, the Internet of Things platform is also used to receive the second cycle configuration information sent by the Internet of Things application. Specifically, the Internet of Things device obtains the second cycle sent by the Internet of Things platform, determines the target cycle based on the first cycle and the second cycle, and sends the attribute information of the Internet of Things device to the Internet of Things platform based on the target cycle.

[0022] In the solution provided by this application, users can configure multiple cycles for an IoT device through the IoT platform for different business scenarios and business environments. After receiving multiple cycles or a list of cycles sent by the IoT platform, the IoT device calculates the cycle that matches the current business scenario or business attributes and reports attributes according to the cycles included in the cycle. This improves the flexibility of cycle configuration and increases the resilience of the entire IoT system, achieving efficient device business management.

[0023] In combination with the first aspect, in a possible implementation method provided in the application, the IoT device also obtains a first priority and a second priority, where the first priority is used to indicate the priority of the first cycle, and similarly, the second priority is used to indicate the priority of the second cycle.

[0024] In the solution provided in this application, after receiving multiple cycles, the IoT device can determine the cycle in the target cycle to be executed based on the priorities corresponding to the multiple cycles, so that when different business scenarios or its own attribute information changes, the qualified cycle can be calculated based on the priority and executed.

[0025] In combination with the first aspect, in a possible implementation method provided in the application, the IoT device determines the target period based on the first period and the second period. Specifically, based on the first priority and the second priority, when the first priority is higher than the second priority, the first period is determined as the target period, or based on the first priority and the second priority, when the second priority is higher than the first priority, the second period is determined as the target period.

[0026] In the solution provided in this application, when the user sets different levels of priority information when configuring the cycle, the IoT device can make a judgment based on the priorities of multiple cycles received and report attributes according to the cycle with the highest priority.

[0027] In combination with the first aspect, in a possible implementation method provided in the application, the first period also includes a first time condition, and the second period also includes a second time condition. Further, based on the first time condition, the first period is determined to be the effective time of the target period; based on the second time condition, the second period is determined to be the effective time of the target period.

[0028] In the solution provided in this application, the IoT device can also calculate the effective time of the cycle based on the time conditions included in the cycle. At the same time, when there are multiple cycles, in addition to judging based on priority, it can also be judged based on time conditions. This satisfies the IoT device to execute different cycles in different business scenarios such as executing business and collecting data, as well as in different time stages, to achieve comprehensive management and improve the overall efficiency of the system.

[0029] In combination with the first aspect, in a possible implementation method provided in the application, further, multiple reporting information is sent, each of the multiple reporting information includes attribute information and time information, and the multiple reporting information is used to instruct the Internet of Things platform to determine the cycle of the Internet of Things device.

[0030] In the solution provided in this application, the IoT platform actively reports or pushes reporting information. In addition to reporting attributes according to the periodicity in the cycle, reporting time information helps the IoT platform monitor and manage the periodic execution of IoT devices.

[0031] The third aspect or any implementation of the third aspect is an implementation of the device corresponding to the first aspect or any implementation of the first aspect. The description in the first aspect or any implementation of the first aspect is applicable to the third aspect or any implementation of the third aspect and will not be repeated here.

[0032] The fourth aspect or any implementation of the fourth aspect is an implementation of the device corresponding to the first aspect or any implementation of the first aspect. The description in the first aspect or any implementation of the first aspect is applicable to the fourth aspect or any implementation of the fourth aspect and will not be repeated here.

[0033] In a fifth aspect, the present application provides an Internet of Things system, which includes: an Internet of Things platform and an Internet of Things device, wherein the Internet of Things platform runs on an infrastructure, and the infrastructure is also connected to the Internet of Things device and the application-side device respectively, and the Internet of Things application runs on the application-side device. Based on this, the Internet of Things platform is used for the first cycle configuration information sent by the Internet of Things application, and the first cycle configuration information includes a first device constraint and a first cycle. The Internet of Things platform is also used to determine the target Internet of Things device from multiple Internet of Things devices based on the first device constraint, and send the first cycle to the target Internet of Things device; with respect to the Internet of Things device, it is used to obtain the first priority, first cycle, second priority, and second cycle sent by the Internet of Things platform, and is also used to use the first cycle associated with the first priority to report attribute information when the first priority is higher than the second priority; and / or use the second cycle associated with the second priority to report attribute information when the second priority is higher than the first priority.

[0034] In a sixth aspect, the present application provides a computing device cluster comprising at least one computing device, each computing device comprising a processor and a memory; the processor of at least one computing device is used to execute instructions stored in the memory of at least one computing device, so that the computing device cluster executes the above-mentioned first aspect and a method combined with any one of the implementation methods of the above-mentioned first aspect.

[0035] In the seventh aspect, the present application provides a computing device cluster, including at least one computing device, each computing device including a processor and a memory; the processor of at least one computing device is used to execute instructions stored in the memory of at least one computing device, so that the computing device cluster executes the above-mentioned second aspect and a method combined with any one of the implementation methods of the above-mentioned second aspect.

[0036] In an eighth aspect, the present application provides a computer program product comprising instructions, which, when executed by a computer device cluster, enables the computer device cluster to execute the above-mentioned first aspect and a method combined with any one of the implementation modes of the above-mentioned first aspect.

[0037] In a ninth aspect, the present application provides a computer program product comprising instructions, which, when executed by a computer device cluster, enables the computer device cluster to execute the second aspect and a method combined with any one of the implementation modes of the second aspect.

[0038] In a tenth aspect, the present application provides a computer-readable storage medium comprising computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the above-mentioned first aspect and a method combined with any one of the implementation methods of the above-mentioned first aspect.

[0039] In an eleventh aspect, the present application provides a computer-readable storage medium comprising computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the above-mentioned second aspect and a method combined with any one of the implementation methods of the above-mentioned second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] FIG1 is a schematic diagram of an application scenario of a device cycle management method based on Internet of Things technology provided in an embodiment of the present application;

[0041] FIG2 is a flow chart of a device cycle management method based on Internet of Things technology provided in an embodiment of the present application;

[0042] FIG3 is another flow chart of a device cycle management method based on Internet of Things technology provided in an embodiment of the present application;

[0043] FIG4 is another flow chart of a device cycle management method based on Internet of Things technology provided in an embodiment of the present application;

[0044] FIG5 is another flow chart of a device cycle management method based on Internet of Things technology provided in an embodiment of the present application;

[0045] FIG6 is a schematic diagram of an architecture of a device cycle management method based on Internet of Things technology provided in an embodiment of the present application;

[0046] FIG7 is another schematic diagram of the architecture of the device cycle management method based on Internet of Things technology provided in an embodiment of the present application;

[0047] FIG8 is a schematic diagram of an interface for monitoring the execution cycle of an IoT device provided in an embodiment of the present application;

[0048] FIG9 is a schematic structural diagram of an Internet of Things platform provided in an embodiment of the present application;

[0049] FIG10 is a schematic structural diagram of an Internet of Things device provided in an embodiment of the present application;

[0050] FIG11 is a schematic diagram of the structure of a computing device provided in an embodiment of the present application;

[0051] FIG12 is a schematic diagram of the structure of another computing device provided in an embodiment of the present application;

[0052] FIG13 is a schematic diagram of the structure of a computing device cluster provided in an embodiment of the present application;

[0053] FIG14 is a schematic diagram of the structure of another computing device cluster provided in an embodiment of the present application;

[0054] FIG15 is a schematic diagram of the structure of another computing device cluster provided in an embodiment of the present application. DETAILED DESCRIPTION

[0055] In the description of this application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in this application is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.

[0056] In the description of this application, unless otherwise specified, "plurality" means two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.

[0057] In addition, to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or execution order, and the words "first" and "second" do not necessarily mean different.

[0058] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0059] It will be understood that the “embodiment” mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, the various embodiments throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It will be understood that in the various embodiments of the present application, the size of the sequence number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

[0060] It is understood that some optional features in the embodiments of the present application may, in certain scenarios, be implemented independently of other features, such as the solution on which they are currently based, to solve corresponding technical problems and achieve corresponding effects. They may also be combined with other features in certain scenarios as needed. Accordingly, the devices provided in the embodiments of the present application may also implement these features or functions accordingly, which will not be described in detail here.

[0061] In this application, unless otherwise specified, the same or similar parts between the various embodiments can be referenced to each other. In this application, unless otherwise specified and there is no logical conflict between the various embodiments, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. Different embodiments can be combined to form new embodiments based on their inherent logical relationships. The following implementation methods of this application do not constitute a limitation on the scope of protection of this application.

[0062] To facilitate understanding of the technical solutions of the embodiments of the present application, a brief introduction to the relevant technologies of the embodiments of the present application is given below:

[0063] Internet of Things (IoT) technology: The Internet of Things (IoT) refers to the real-time collection of acoustic, optical, thermal, electrical, mechanical, chemical, biological, and location-based information from any object or process requiring monitoring, connection, and interaction, using various devices and technologies, including information sensors, radio frequency identification (RFID), global positioning systems (GPS), infrared sensors, and laser scanners. This information is then collected through various network access options to achieve ubiquitous connectivity between objects and between objects and people, enabling intelligent perception, identification, and management of objects and processes. The IoT is an information carrier based on the internet and traditional telecommunications networks, enabling all independently addressable, common physical objects to form an interconnected network.

[0064] IoT platform: Connects to IoT devices or IoT gateways, supports data reporting from IoT devices / gateways, and provides data for users to view, or allows users to issue control commands to IoT devices / gateways. In some cases, the IoT platform is also referred to as a cloud platform, cloud server, or network-side server. The IoT platform can also connect to business applications for user access.

[0065] An IoT device can be any device that completes one or more of the processes in the aforementioned information interaction. An IoT device can be a smart TV, augmented reality (AR) device, virtual reality (VR) device, tablet computer, smart speaker, smart light, smart watch, smart bracelet, edge device, business device, smart machine tool, smart camera, sensor, radar, etc. In the following embodiments, no limitation is imposed on the specific form of the IoT device.

[0066] In the embodiment of the present application, the IoT devices can be divided into directly connected IoT devices and edge IoT devices. Directly connected IoT devices are IoT devices that are directly connected to the IoT access platform, and edge IoT devices are IoT devices that are not directly connected to the IoT access platform but are indirectly connected to the IoT access platform through edge IoT gateway devices or the like.

[0067] Application-side devices: In some scenarios, application-side devices run business systems or IoT applications built by users for their business needs and connected to the IoT platform. In other scenarios, application-side devices are devices provided by the cloud platform and run on cloud infrastructure. Application-side devices enable users to access the IoT platform, control IoT devices, and obtain relevant information about them. IoT applications run on application-side devices.

[0068] Object Model: An object model abstracts and models the properties, methods, and timing of IoT device functions, forming a standardized data model to facilitate interoperability and data exchange between devices. For example, different types of smart lights have similar properties, including on / off states and similar functional logic. Therefore, the on / off function of smart lights can be standardized as the object model for the smart light.

[0069] Attributes: Attributes are used to describe the specific information and status of a device during operation, such as the cooling temperature of an air conditioner or the on / off status of a light. Device attributes can be used to create a corresponding physical model for the device.

[0070] The attributes of a thing model are readable, writable, and reportable. This means that IoT device attributes can be read by applications, set and distributed to IoT devices via the IoT platform or application, and reported to the IoT device. IoT devices can also report attribute information to the IoT platform or application. IoT device attributes can include any of the three characteristics: readable, writable, and reportable. Attributes of a thing model can include multiple fields, such as name, identifier, data type, value range, data length, unit, read / write permissions, and parameter descriptions. These fields are not specifically defined here.

[0071] To facilitate the description of an IoT-based device lifecycle management method according to an embodiment of the present invention, please refer to FIG1 . FIG1 illustrates an application scenario of the IoT-based device lifecycle management method according to an embodiment of the present invention. The IoT system architecture includes IoT devices, infrastructure, and application-side devices. IoT platform 22 is built on infrastructure 20. IoT devices include IoT devices 31, 32, and 33, which are directly connected to IoT platform 22, as well as IoT devices 34, 35, and 36, which are connected to IoT platform 22 via IoT device 32. IoT devices are used to collect IoT data and process IoT services. The infrastructure running the IoT platform is also connected to application-side devices for interaction with these devices. The IoT platform can send messages to IoT applications running on application-side devices, allowing them to process IoT services. Users can also access and configure the IoT platform through application-side devices. IoT devices collect information about their surrounding environment and generate device data. IoT devices send messages containing device data to the IoT platform running on the infrastructure via a transmission link formed by an edge gateway and edge devices. The IoT platform running on the infrastructure transmits messages to IoT applications so that the IoT applications can process IoT services based on the messages. The application-side devices can be user-created devices or run on the infrastructure.

[0072] For example, in the daily management of campus buildings, the control objectives and reporting cycles for electromechanical equipment vary across different scenarios. For example, lighting system control requires differentiating between daily, holiday, emergency, and troubleshooting scenarios. Generally, configuration details provide real-time monitoring of each device's current status and attribute data. In the overall space operation and maintenance monitoring, managers need to confirm that equipment is operating within the "expected" state. After configuring a temperature control target on the IoT platform, managers need to verify that the room's temperature meets the desired target. In addition to checking the temperature value on the configuration page, they also need to confirm that the temperature is up to date (i.e., within the specified cycle). Different scenarios have different cycle requirements, so cycles need to be prioritized and have different effective times to meet these requirements. Current cycle management methods, such as fixed cycles and heartbeat timers, are unable to adapt to rapidly changing application scenarios when faced with complex IoT systems and large numbers of device changes. Frequent changes not only significantly increase costs but also lead to excessive resource waste.

[0073] To solve the above problems, the present application provides a device cycle management method based on IoT technology, which is applied to the IoT platform in the IoT system. Users can configure the cycle of IoT devices connected to the IoT platform through the IoT application on the application-side device. When there are multi-dimensional and multi-level requirements in the business scenario, the cycle configuration of different IoT devices can be achieved by configuring the priority, constraints, and time conditions of the cycle, or when there are multiple cycles for the same IoT device, the cycle to be executed can be determined based on the time conditions and priority, and the attributes can be reported accurately according to the cycle.

[0074] Please refer to FIG2 , which is a flow chart of a device cycle management method based on Internet of Things technology provided by an embodiment of the present application. Specifically:

[0075] S301. Obtain first cycle configuration information sent by the Internet of Things application, where the first cycle configuration information includes a first target device constraint and a first cycle.

[0076] The IoT platform obtains the first cycle configuration information sent by the IoT application. Users can log in to the IoT platform through the physical network application deployed on the application-side device, enter the information on the IoT platform or call the IoT platform through the application programming interface (API) to configure the cycle configuration information of the IoT device connected to the IoT platform. The cycle configuration information may include the cycle, and may also include the cycle priority, constraints, time conditions, and effective range information. Among them, the priority can indicate the priority of the cycle, as shown in Table 1, which is a cycle priority table. Specifically:

[0077] Table 1 Periodic priority table

[0078] In one embodiment of the present application, regarding the definition of cycles, the platform supports multiple levels of settings.

[0079] 1. Cluster level, or tenant instance level;

[0080] 2. Product dimension: set the cycle by product or product attribute granularity;

[0081] 3. Device dimension: set the cycle according to the specified device or the attribute granularity of the specified device;

[0082] 4. Dynamic calculation: determine the cycle based on the current scene conditions of the device.

[0083] Each level of settings has different priorities, which are defined from 0 to 9. The priorities received by IoT devices or gateway devices can be shown in Table 1. Table 1 is a periodic priority table. IoT devices or gateway devices can calculate the priority of periodic reporting based on the received period according to the priority in the table and the properties of the periodic reporting device.

[0084] Based on this, the definition of the cycle is multi-dimensional and multi-level, which can meet the use of more business scenarios. After the definition and configuration are completed, the IoT platform / gateway follows the definition of the cycle. From the platform's perspective, it allows the device that implements the cycle configuration to perform attribute reporting cycle checks to meet the monitoring of the basic operation of the device and the link reachability.

[0085] Furthermore, the size of the cycle will have different performance impacts on devices and platforms. The IoT platform can configure necessary constraints on the cycle. For example, the constraints include:

[0086] 1. On the device side, maximum and minimum cycle constraints are supported, where the minimum value is determined based on the device's existing computing power (cores, power consumption). In other words, the corresponding cycle can be issued to IoT devices that meet the device's computing power conditions. This avoids high consumption caused by periodic reporting of IoT devices, and the appropriate cycle is issued based on the actual situation of the IoT device.

[0087] 2. On the platform side, support for configuring maximum and minimum cycle constraints, where the maximum cycle is evaluated based on the platform's predictive analysis requirements.

[0088] The constraint condition may also include a first effective range condition. For example, the effective range condition is calculated using the basic attributes, tags, and dynamic attributes of the device as factors, including but not limited to:

[0089] 1. Device product identification, used to identify the IoT device and distinguish it from other IoT devices, such as ID information, device number, etc.

[0090] 2. The space where the equipment is located, such as building, floor, space, area, cluster, etc.

[0091] 3. The location of the device, including latitude and longitude, altitude, and other positioning information;

[0092] 4. The network address of the device, such as the IP address or Media Access Control Address (MAC);

[0093] 5. Device label: A category or type of IoT device can be distinguished based on the device label, such as temperature sensor devices, controller devices, electromechanical devices, etc.

[0094] 6. Equipment asset information, including asset number, administrator, department, etc.;

[0095] 7. Equipment factory information, including manufacturer identifier, manufacturer name, factory model, equipment factory information, etc.;

[0096] 8. Device firmware version, including firewall version, software version, etc.

[0097] 9. Device status: online or offline, frozen, faulty, alarming, expired, etc.

[0098] 10. Dynamic properties of the device, such as temperature and humidity of the sensor.

[0099] In one embodiment of the present application, when configuring periodic configuration information, users can, in addition to configuring the period, also configure constraints to clearly specify the target IoT devices to which the periodic configuration information refers. Based on the aforementioned multiple effective range conditions, targeted configuration information such as the device product ID can be used to control the target IoT devices, achieving precise constraint effects. Furthermore, by calculating and determining the IoT devices capable of executing the corresponding period based on the computing power, network capabilities, and actual needs of the IoT platform and IoT devices, the effectiveness of the configuration is ensured.

[0100] Equipment Constraint Cycle

[0101] S302. Determine a target IoT device based on the first device constraint condition, where the IoT device includes the target IoT device.

[0102] The IoT platform determines the target IoT devices based on the first device constraint in the first cycle. Exemplarily, the constraint includes computing power, storage, and network conditions that meet the cycle. That is, based on the computing power, storage, and network conditions in the constraint, the target IoT device range that meets the constraint is determined. In another example of the present application, the constraint may include a first effective range condition. The IoT platform determines the target IoT devices by calculating the values ​​corresponding to each dynamic factor in the first effective range condition, or the degree of match with the corresponding effective range condition.

[0103] Exemplary configuration methods for the effective range conditions include:

[0104] 1. ALL / None indicates direct matching and is used in scenarios where a period is directly assigned to a device. In this configuration, when any condition in the effective range matches an IoT device attribute, the IoT device is determined to be the target IoT device.

[0105] 2. Equal value matching, configured in the form of {factor}:{value}, supports multiple factor combinations, and improves configurability.

[0106] 3. Expressions: Based on a Domain-Specific Language (DSL) expression language, factors are included in the calculation process as expression variables to implement complex multi-factor logic judgment scenarios. The DSL can be implemented in open source languages ​​such as Groovy, Java, JavaScript, and Python, or customized, and this application does not limit this.

[0107] In one embodiment of the present application, the platform configures three periods based on the effective range conditions:

[0108] Cycle 1: Scope: ALL

[0109] Cycle 2: Scope:ZoneID:{sz.b01.room19}

[0110] Cycle 3: Scope:Exp(self.properties.oncall=true)

[0111] For example, take IoT device 32 as an example:

[0112] When IoT device 32 is in room {sz.b01.room19}:

[0113] When the oncall attribute of the IoT device 32 is true, it is determined that the IoT device 32 meets cycle 3, and the IoT device 32 is the target IoT device of cycle 3;

[0114] When the oncall attribute of the IoT device 32 is false, it is determined that the IoT device 32 meets cycle 2, and the IoT device 32 is the target IoT device of cycle 2;

[0115] When the oncall attribute of the IoT device 32 cannot be determined, it is determined that the IoT device 32 meets cycle 2, and the IoT device 32 is the target IoT device of cycle 2;

[0116] When IoT device 32 is in room {sz.b01.room20}:

[0117] When the oncall attribute of the IoT device 32 is true, it is determined that the IoT device 32 meets cycle 3, and the IoT device 32 is the target IoT device of cycle 3;

[0118] When the oncall attribute of the IoT device 32 is false, it is determined that the IoT device 32 meets cycle 1, and the IoT device 32 is the target IoT device of cycle 1;

[0119] When the oncall attribute of the IoT device 32 cannot be determined, it is determined that the IoT device 32 meets cycle 1, and the IoT device 32 is the target IoT device of cycle 1.

[0120] Especially when there are multiple IoT devices, by configuring constraints, the target IoT devices corresponding to the constraints can be clearly identified, which facilitates batch management of the cycles of massive IoT devices. Especially in scenarios such as repeated business and repeated attribute characteristics, through multi-dimensional constraint configuration, efficient configuration and management of the IoT device cycle can be achieved, improving the overall system management efficiency and meeting the cycle configuration requirements of multi-dimensional and multi-business scenarios.

[0121] S303. Send a first cycle to the target IoT device, where the first cycle is used to instruct the target IoT device to report attribute information of the target IoT device according to the first cycle.

[0122] After the IoT platform determines the target IoT device based on the constraints, it sends the first cycle to the target IoT device. After receiving the first cycle, the target IoT device reports the attribute information of the IoT device to the IoT platform. The attribute information may include the device attributes of the IoT device, and may also include the business attributes of the IoT device in executing the business according to the object model. The business attributes include the collected data, the results of executing the business, etc., and may also include the object model attributes of the IoT device.

[0123] Further, in conjunction with the IoT system structure in FIG1 , please continue to refer to FIG3 , which is another flow chart of the device cycle management method based on IoT technology provided in an embodiment of the present application, specifically:

[0124] S401. Obtain periodic configuration information: first periodic configuration information.

[0125] The Internet of Things platform 22 obtains the first cycle configuration information of the periodic configuration information sent by the Internet of Things application 30. The first cycle configuration information of the periodic configuration information is input by the user through the Internet of Things application 30 calling the Internet of Things platform 22. The first cycle configuration information of the periodic configuration information includes the first constraint condition, the first period, the priority of the first period, the time condition of the first period, etc.

[0126] S402. Determine the target IoT device based on the first device constraint in the first cycle configuration information.

[0127] Based on the first device constraint in the first-period configuration information, IoT platform 22 determines, from among multiple IoT devices, that the target IoT device that meets the first device constraint is IoT device 31. Exemplarily, IoT platform 22 determines, based on the first device constraint, that the computing power, network capabilities, and storage capabilities of IoT device 31 meet the requirements of the first period. Based on this, IoT platform 22 further determines, based on the effective scope conditions configured in the first device constraint, that IoT device 31 meets the effective scope requirements.

[0128] By calculating the effective scope conditions on the IoT platform and determining the target IoT devices that meet the constraints, and leveraging the computing power of the infrastructure where the IoT platform is located, the calculation results can be quickly obtained, enabling rapid determination of target IoT devices in scenarios with massive IoT devices, thereby improving system efficiency.

[0129] It is worth noting that in the embodiments of the present application, the computing power requirements, network requirements, storage requirements and effective scope conditions in the constraints can be configured simultaneously, separately, or in any combination, and the present application does not limit this.

[0130] S403. Send the first cycle to the target IoT device.

[0131] The IoT platform 22 sends a first cycle to the IoT device 31 .

[0132] S404. According to the first cycle, send attribute information to the Internet of Things platform.

[0133] The IoT device 31 sends attribute information to the IoT platform 22 according to the first cycle.

[0134] S405. Determine the cycle of the target IoT device based on multiple reported information.

[0135] In addition to sending attribute information to the IoT platform 22 according to the first cycle, the user can also configure the time information that the target IoT device reports when sending the attribute information in the first cycle configuration information. This time information can be a timestamp added when the target IoT device sends the attribute information. The IoT platform 22 can determine the actual cycle of the IoT device 31 based on the time information in the multiple reports sent by the IoT device 31. For example, the cycle execution status can be obtained by comparing the difference between the time information in two adjacent reports with the first cycle. When the difference is greater than the first cycle or less than the first cycle, it indicates that there is a delay or other failure in the execution of the first cycle by the IoT device 31. By feeding back the cycle execution status to the IoT application, the user can make timely adjustments to improve the stability of the system.

[0136] Furthermore, when the user configures multiple periodic configuration information at the same time, the IoT platform can determine the target IoT device based on the multiple periodic configuration information. For details, please refer to FIG4 , which is another flow chart of the device periodic management method based on IoT technology provided in an embodiment of the present application:

[0137] S406. Obtain periodic configuration information: second periodic configuration information.

[0138] The Internet of Things platform 22 obtains the second period configuration information of the period configuration information. The second period configuration information of the period configuration information is input by the user through the Internet of Things application 30 calling the Internet of Things platform 22. The second period configuration information of the period configuration information includes the corresponding second constraint condition, the second period, the priority of the second period, the time condition of the second period, etc.

[0139] It is worth noting that the user can configure or input multiple period configuration information at one time through the Internet of Things application 30, or can independently configure a single period configuration information, and the application does not impose any limitation on this.

[0140] S407. Determine the target IoT device based on the second device constraint in the second cycle.

[0141] The implementation of step S409 by the Internet of Things platform 22 is basically similar to that in step S403, and this application will not go into details.

[0142] S408. Send the second cycle and the second priority to the target IoT device.

[0143] In one embodiment of the present application, the IoT platform 22 may directly send the second cycle to the IoT device 31 , and the IoT device 31 may update the stored cycle.

[0144] In another embodiment of the present application, the IoT platform 22 establishes a period list for the target IoT device based on the IoT device 31, determines the stored first period and second period as the period list of the IoT device 31, sends the period list to the IoT device 31, and the IoT device 31 updates its own stored period.

[0145] S409. Determine a target period based on the first period and the second period.

[0146] The IoT device 31 determines the target cycle based on the first cycle and the second cycle. Based on this, the IoT device 31 can compare the first priority of the first cycle and the second priority of the second cycle and execute the cycle with the highest priority. For example:

[0147] Period 1 (Priority 4): Period: 120s

[0148] Period 2 (Priority 5): Period: 60s

[0149] Period 3 (Priority 6): Period: 15s

[0150] When the IoT device 31 has cycles 1, 2, and 3, the IoT device 31 determines that cycle 3 has the highest priority by comparing the priorities. Based on this, the IoT device 31 adopts cycle 3 (15s) and determines 120s as the target cycle.

[0151] In an embodiment provided in the present application, the IoT platform also sends a first time condition of a first cycle and a second time condition of a second cycle to the target IoT device. Exemplarily, the first time condition can be a time interval including the effective time and expiration time of the first cycle.

[0152] For example,

[0153] Period 1 (Priority 4): Period: 120s, effective time interval: 8:00-18:00;

[0154] Period 2 (Priority 5): Period: 60s, effective time interval: 8:00-18:00;

[0155] Period 3 (Priority 6): Period: 15s, effective time interval: 18:00-00:00;

[0156] When IoT device 31 has Cycle 1, Cycle 2, and Cycle 3, the effective time intervals can be compared first. If the effective time intervals conflict, the cycle priorities can be further compared. Since the effective time intervals of Cycle 1 and Cycle 2 conflict, the priority comparison determines that Cycle 2 has the highest priority. Based on this, IoT device 31 adopts Cycle 2 (60s) and determines 120s as the target period. If the effective time does not conflict, the corresponding cycle is executed based on the effective time interval. Therefore, when IoT device 31 is at 18:00, Cycle 3 is determined as the target period and the corresponding cycle of 15s is executed.

[0157] In another embodiment provided herein, the effective range condition can also be calculated by the IoT device 31. When multiple cycles exist, the cycle with the highest priority is calculated first, along with the effective time and effective range. If a high-priority cycle within the effective time is not effective, the cycle with the next higher priority is calculated. The IoT device has its own attribute detection function and will factor the associated attributes into the calculation process based on the configuration of the rule.

[0158] In this way, the cycle to be executed can be adjusted in real time according to the changes in the properties of the device itself, without the need for calculation through the Internet of Things platform 22, thereby improving the timeliness of the cycle calculation and reducing latency.

[0159] For example,

[0160] Cycle 1 (Priority 4): Scope: ALL, Period: 120s, Effective Time Range: 8:00-18:00;

[0161] Cycle 2 (Priority 5): Scope: ZoneID: {sz.b01.room19}, Period: 60s, Effective Time Range: 8:00-18:00;

[0162] Cycle 3 (priority 6): Scope: Exp(self.properties.oncall = true), Period: 15s, Effective time interval: 18:00-00:00;

[0163] When IoT device 31 is in room {sz.b01.room19}:

[0164] When the device's oncall attribute is true and the device's current time attribute is between 18:00 and 00:00, cycle 3 (15s) is used;

[0165] When the device's oncall attribute is false and the device's current time attribute is between 8:00 and 18:00, cycle 2 (60s) is used;

[0166] When the oncall attribute of the device is true and the current time attribute of the device is between 8:00-18:00, cycle 2 (60s) is used.

[0167] When IoT device 31 is in room {sz.b01.room20}:

[0168] When the device's oncall attribute is true and the device's current time attribute is between 18:00 and 00:00, cycle 3 (15s) is used;

[0169] When the device's oncall attribute is false and the device's current time attribute is between 8:00 and 18:00, cycle 1 (120s) is used;

[0170] When the oncall attribute of the device is false and the current time attribute of the device is between 18:00 and 00:00, all cycles will not take effect.

[0171] S410. Send attribute information to the IoT platform according to the target period.

[0172] The IoT device 31 sends attribute information to the IoT platform 22 according to the target period.

[0173] S411. Determine the cycle of the target IoT device based on multiple reported information.

[0174] In addition to sending attribute information to IoT platform 22 according to the first cycle, IoT device 31 can also configure the time information that the target IoT device reports along with the attribute information according to the target cycle. This time information can be a timestamp added when the target IoT device sends the attribute information. IoT platform 22 can determine the actual cycle of IoT device 31 based on the time information in the multiple reports sent by IoT device 31. By feeding back the execution status of this cycle to the IoT application, users can make timely adjustments to improve system stability.

[0175] Furthermore, from the perspective of the IoT device, when at least one cycle sent by the IoT platform is obtained, the target cycle to be executed is determined. For details, please refer to FIG5 , which is another flow chart of the device cycle management method based on IoT technology provided in an embodiment of the present application:

[0176] S501. Obtain the first cycle sent by the Internet of Things platform.

[0177] S502. According to the first cycle, send the attribute information of the IoT device to the IoT platform.

[0178] For example, IoT device 31 sends attribute information to IoT platform 22 based on a first cycle. When IoT platform 22 issues a single cycle and IoT device 31 does not store other cycles, the first cycle can be determined as the target cycle, and the timing or validity range conditions of the first cycle are used to determine whether to send attribute information to IoT platform 22 based on the first cycle. When IoT platform 22 issues multiple cycles, or a cycle list including at least multiple cycles, the target cycle to be executed is determined based on the priority, validity range conditions, and time conditions of the multiple cycles. The attribute information is then sent to IoT platform 22 based on the target cycle within the target cycle.

[0179] Please continue to refer to FIG6 , which is a schematic diagram of an architecture of a device cycle management method based on Internet of Things technology provided by an embodiment of the present application. Specifically:

[0180] In the data center scenario, IoT devices include sensors 31 and edge gateways 32 that are directly connected to the IoT platform 22, as well as sensors 321, 322, and 323, as well as early warning devices 34 that are connected to the IoT platform 22 through the edge gateway 32. When the platform detects a major abnormality warning, it is necessary to quickly adjust the cycle to quickly obtain relevant information about each core device in the data center. For example, when there is a fire warning, sudden weather, or a critical facility failure, the warroom mechanism needs to be activated. During the entire warroom process, real-time data collection is required for each core electromechanical equipment in the data center. At this time, the cycle is the shortest, occupying a large amount of network bandwidth and throughput. However, under normal circumstances, such a long cycle is not required to avoid excessive waste of network resources.

[0181] Through the method of this application, in this scenario, the IoT platform 22 sends the configured cycle to the edge gateway 32:

[0182] 1. The default policy, period = 60s, represents the period of normal status;

[0183] 2. Warroom strategy, period = 5s, representing the period of emergency status.

[0184] In normal mode, the warroom device status is off; at this time, the gateway selects the default policy after calculation, with a period of 60 seconds.

[0185] In emergency mode, the warroom state is turned on through cloud / edge linkage. At this time, the gateway calculates that the DSL policy is in effect and has a higher priority, so it selects the warroom period, which is 5 seconds.

[0186] For example, in the cloud-edge-end based Warroom collaborative perception scenario, Warroom can be a device generated based on scene abstraction, which can be regarded as an early warning device 34, wherein the early warning device 34 is used to carry the status attributes of Warroom, and its status can be set through direct control of the cloud; in addition, a rule-based triggering method can be realized based on cloud linkage and edge linkage.

[0187] This embodiment can improve system reliability and ensure timely response to early warning events by combining dynamic periodic configuration with edge-based dynamic adjustment by the gateway / device.

[0188] Please continue to refer to FIG7 , which is another schematic diagram of the architecture of the device lifecycle management method based on the Internet of Things technology provided by an embodiment of the present application. Specifically:

[0189] In building control scenarios, the networking model of building IoT systems primarily uses a gateway-controller-electromechanical device node topology model. In terms of networking protocols, there are a variety of options, such as Building Automation and Control Networks (BACnet), Internet Protocol (IP), Multi-Service Transport Platform (MSTP), Modbus, Transmission Control Protocol (TCP), RTU, OPC-UA, and MQTT. For example, in Figure 7, edge gateway 32 communicates with electromechanical device 321 via TCP, edge gateway 32 communicates with electromechanical device 322 via OPC-UA, and edge gateway 32 communicates with electromechanical device 323 via MQTT.

[0190] Building managers monitor the operating status of equipment in real time through equipment, space, and system configurations. Generally speaking, the current real-time status and attribute data of each device can be monitored in real time through the configuration details. In the operation and maintenance monitoring of the entire space plane, managers need to confirm whether the equipment is in an "expected" state. For example, after the manager configures the temperature control target through the platform, he needs to check whether the temperature of the room has reached the expected state. At this time, in addition to checking the temperature value through the configuration page, he also needs to confirm that the temperature value is the latest state (that is, within the specified period). Combined with the cycle management method provided by this patent, the configuration application can realize dynamic rendering prompts for the real-time attributes of the equipment, such as making sufficient prompts for attributes that have not been reported for more than a period, so as to avoid misjudgment by managers. When an anomaly is detected, the manager can further take timely measures to troubleshoot.

[0191] In building scenarios, different electromechanical devices can be configured with independent cycles based on their type. Considering the networking of BA scenarios, electromechanical devices are connected using direct connections or gateway-controller relay modes. Data reporting and cycle management can be simplified by integrating the platform's Software Development Kit (SDK).

[0192] After electromechanical equipment is connected to the platform, the smart building application subscribes to its attribute reporting data. The platform calculates the delay marker for the attribute reporting cycle based on the equipment's cycle and pushes this information to the smart building application. When the smart building application renders the device / system / space configuration on the interface, it can determine whether the equipment is experiencing delays based on the platform's calculated cycle and perform corresponding visualization, allowing management personnel to observe the data directly.

[0193] Specifically, please refer to FIG8 , which is a schematic diagram of an interface for monitoring the execution cycle of an IoT device provided in an embodiment of the present application:

[0194] Through this diagram, users can obtain the actual situation of IoT devices during the execution cycle through IoT applications. The interface diagram includes IoT devices and the cycle execution status of each IoT device in the entire system. The execution status is determined by the IoT platform based on the time information in the reported information sent by each IoT device.

[0195] For example, in a smart building scenario, the cycle detection interface includes electromechanical equipment 31, electromechanical equipment 32, electromechanical equipment 33, electromechanical equipment 34, and the cycle execution status corresponding to each electromechanical equipment. When there is a delay in the cycle of the electromechanical equipment, a prompt "Cycle delay: 1s" is displayed; when the cycle of the electromechanical equipment is executed normally without delay, a prompt "Cycle normal" is displayed.

[0196] In this way, users can quickly understand the cycle execution status of IoT devices and make timely adjustments to the cycles of electromechanical equipment with delays and problems.

[0197] The present application provides an Internet of Things system, which includes: an Internet of Things platform and Internet of Things devices, wherein the Internet of Things platform runs on an infrastructure, and the infrastructure is also connected to the Internet of Things devices and application-side devices respectively, and the application-side devices run Internet of Things applications. Based on this, the Internet of Things platform is used to obtain cycle configuration information sent by the Internet of Things application, and to create a cycle based on the cycle configuration information. It is also used to determine the target Internet of Things device based on the constraints in the cycle configuration information and send the cycle to the target Internet of Things device; the Internet of Things device is used to obtain the cycle sent by the Internet of Things platform, and is also used to send attribute information of the Internet of Things device to the Internet of Things platform based on the cycle.

[0198] The present application also provides an Internet of Things platform. Please refer to Figure 9 below, which is a schematic diagram of the structure of an Internet of Things platform provided by the present application. The details are as follows:

[0199] An acquisition module 221 is configured to acquire first cycle configuration information sent by an IoT application, where the first cycle configuration information includes a first device constraint and a first cycle.

[0200] A determination module 223 is configured to determine a target IoT device from a plurality of IoT devices based on the first device constraint condition;

[0201] The sending module 224 is used to send the first cycle to the target IoT device.

[0202] The present application also provides an Internet of Things device. Please refer to Figure 10 below, which is a schematic diagram of the structure of an Internet of Things device provided by the present application. The details are as follows:

[0203] An acquisition module 311 is used to acquire a first cycle sent by the Internet of Things platform;

[0204] The sending module 312 is used to send the attribute information of the Internet of Things device to the Internet of Things platform according to the first cycle.

[0205] It is worth noting that the above modules can all realize corresponding technical functions, and the embodiments of this application do not limit this.

[0206] The various modules in IoT platform 22 are described as examples. Acquisition module 221, determination module 223, and sending module 224 can all be implemented via software or hardware. For example, the implementation of acquisition module 221 will be described below, using acquisition module 221 as an example. Similarly, the implementation of determination module 223 and sending module 224 can refer to the implementation of acquisition module 221.

[0207] As an example of a software functional unit, the acquisition module 221 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Furthermore, the computing instance may be one or more. For example, the acquisition module 221 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed in the same area or in different areas. Furthermore, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same availability zone or in different availability zones, each availability zone including one data center or multiple geographically close data centers. Typically, a region may include multiple availability zones.

[0208] As an example of a hardware functional unit, the acquisition module 221 may include at least one computing device, such as a server. Alternatively, the acquisition module 221 may be implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0209] It should be noted that, in other embodiments, the acquisition module 221 can be used to execute any step in the device life cycle management method based on the Internet of Things technology, the determination module 223 can be used to execute any step in the device life cycle management method based on the Internet of Things technology, and the sending module 224 can be used to execute any step in the device life cycle management method based on the Internet of Things technology. The steps that the acquisition module 221, the determination module 223, and the sending module 224 are responsible for implementing can be specified as needed. The full functions of the Internet of Things platform are realized by respectively implementing different steps in the device life cycle management method based on the Internet of Things technology through the acquisition module 221, the determination module 223, and the sending module 224.

[0210] The implementation method of each module in the Internet of Things device 31 is similar to the implementation method of the acquisition module 311 and the sending module 312 in the Internet of Things platform 22, and will not be repeated in this application.

[0211] The above details the method, IoT platform, and system of the embodiments of the present application. To facilitate better implementation of the above solutions of the embodiments of the present application, correspondingly, related equipment for cooperating in implementing the above solutions is also provided below.

[0212] This application provides a computing device. Please refer to Figure 11 below, which is a schematic diagram of the structure of a computing device provided in an embodiment of this application. Computing device 300 includes a bus 307, a processor 308, a memory 306, and a communication interface 309. Processor 308, memory 306, and communication interface 309 communicate with each other via bus 307. Computing device 300 can be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in computing device 300.

[0213] Bus 307 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, among others. Buses may be classified as address buses, data buses, control buses, and the like. For ease of illustration, FIG11 shows a single line, but this does not imply a single bus or type of bus. Bus 307 may include a path for transmitting information between various components of computing device 300 (e.g., memory 306, processor 308, and communication interface 309).

[0214] The processor 308 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0215] The memory 306 may include volatile memory, such as random access memory (RAM). The processor 308 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0216] Memory 306 stores executable program code, which processor 308 executes to implement the functions of acquisition module 221, determination module 223, and sending module 224, thereby implementing the device lifecycle management method based on IoT technology. Specifically, memory 306 stores instructions for the IoT platform to execute the device lifecycle management method based on IoT technology.

[0217] The communication interface 309 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 300 and other devices or a communication network.

[0218] The present application provides another computing device. Please refer to Figure 12 below. Figure 12 is a structural diagram of another computing device provided in an embodiment of the present application. Computing device 400 includes: a bus 407, a processor 408, a memory 406 and a communication interface 409. The processor 408, the memory 406 and the communication interface 409 communicate with each other via bus 407. Computing device 400 can be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in computing device 400. Among them, the implementation of bus 407, processor 408 and communication interface 409 is similar to that of each structure in computing device 300. Reference can be made to computing device 300 and this application will not go into details.

[0219] Specifically, memory 406′ stores executable program code, which processor 308 executes to implement the functions of acquisition module 311 and sending module 312, thereby implementing the device lifecycle management method based on IoT technology. In other words, memory 406 stores instructions for the IoT platform to execute the device lifecycle management method based on IoT technology.

[0220] Embodiments of the present application also provide a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smartphone.

[0221] Please refer to Figure 13 below, which is a schematic diagram of the structure of a computing device cluster provided in an embodiment of the present application. As shown in Figure 13, the computing device cluster includes at least one computing device 300. Memory 306 in one or more computing devices 300 in the computing device cluster may store instructions for executing the device lifecycle management method based on IoT technology on the same IoT platform.

[0222] In some possible implementations, one or more computing devices 300 in the computing device cluster can also be used to execute some of the instructions of the IoT platform for executing the device lifecycle management method based on IoT technology. In other words, a combination of one or more computing devices 300 can jointly execute the instructions of the IoT platform for executing the device lifecycle management method based on IoT technology.

[0223] It should be noted that the memory 306 in different computing devices 300 in the computing device cluster can store different instructions for executing some functions of the IoT platform. In other words, the instructions stored in the memory 306 in different computing devices 300 can implement the functions of one or more of the acquisition module 221, determination module 223, and sending module 224.

[0224] In some possible implementations, the memory 306 of one or more computing devices 300 in the computing device cluster may also store partial instructions for executing the device lifecycle management method based on IoT technology. In other words, the combination of one or more computing devices 300 can jointly execute instructions for executing the device lifecycle management method based on IoT technology.

[0225] Please refer to Figure 14 below, which is a structural diagram of another computing device cluster provided in an embodiment of the present application. As shown in Figure 14, two computing devices 300A and 300B are connected via a communication interface 309. The memory in the computing device 300A stores instructions for executing the acquisition module 221 and the sending module 224. The memory in the computing device 300B stores instructions for the determination module 223 of the function to be executed. In other words, the memories 306 of the computing devices 300A and 300B jointly store instructions for the Internet of Things platform to execute the device lifecycle management method based on the Internet of Things technology.

[0226] The connection method between the computing device clusters shown in FIG14 can be based on the fact that the device lifecycle management method based on IoT technology provided by this application requires a large amount of data transmission to the acquisition module 221 and the sending module 224. Considering the data transmission volume, in order to avoid the computing device 300A from being overloaded, the function of the determination module 223 is transferred to the computing device 300B.

[0227] It should be understood that the functionality of the computing device 300A shown in FIG14 may also be accomplished by multiple computing devices 300. Similarly, the functionality of the computing device 300B may also be accomplished by multiple computing devices 300.

[0228] Please refer to Figure 15 below, which is a structural diagram of another computing device cluster provided by an embodiment of the present application. In some possible implementations, one or more computing devices in the computing device cluster can be connected via a network. The network can be a wide area network or a local area network, etc. Figure 15 shows a possible implementation. As shown in Figure 15, two computing devices 300C and 300D are connected via a network. Specifically, the network is connected through the communication interface in each computing device. In this type of possible implementation, the memory 306 in the computing device 300C stores instructions for executing the acquisition module 221 and the sending module 224. At the same time, the memory 306 in the computing device 300D stores instructions for executing the determination module 223.

[0229] The connection method between the computing device clusters shown in Figure 15 can be based on the consideration that the device lifecycle management method based on Internet of Things technology provided in this application requires a large amount of data transmission and needs to be connected through a network. The execution of these functions is relatively independent. In order to achieve the best storage and computing performance, it is considered to entrust the function of the determination module 223 to the computing device 300D for execution.

[0230] It should be understood that the functions of the computing device 300C shown in FIG15 may also be completed by multiple computing devices 300. Similarly, the functions of the computing device 300D may also be completed by multiple computing devices 300.

[0231] In some possible implementations, the memory 306 of one or more computing devices 300 in the computing device cluster may also store partial instructions for executing the device lifecycle management method based on IoT technology. In other words, the combination of one or more computing devices 300 can jointly execute instructions for executing the device lifecycle management method based on IoT technology.

[0232] The present application also provides a computer program product including instructions. The computer program product may be software or a program product including instructions that can be executed on a computing device or stored on any available medium. When the computer program product is executed on at least one computing device, the at least one computing device executes the aforementioned method for device lifecycle management based on IoT technology, as applied to an IoT platform.

[0233] The present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center that contains one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the above-mentioned device cycle management method applied to the Internet of Things platform for executing Internet of Things technology-based management.

[0234] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the protection scope of the technical solutions of the embodiments of the present application.

[0235] Those skilled in the art will clearly understand that the specific working process of the system, Internet of Things platform or unit described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0236] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

[0237] The present application also provides a computer program product including instructions. The computer program product may be software or a program product including instructions that can be executed on a computing device or stored on any available medium. When the computer program product is executed on at least one computing device, the at least one computing device executes the aforementioned method for device lifecycle management based on IoT technology, as applied to an IoT platform.

[0238] The present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center that contains one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the above-mentioned device cycle management method applied to the Internet of Things platform for executing Internet of Things technology-based management.

[0239] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the protection scope of the technical solutions of the embodiments of the present application.

[0240] Those skilled in the art will clearly understand that the specific working processes of the above-described systems, management platforms or units can refer to the corresponding processes in the aforementioned method embodiments, which will not be repeated here.

[0241] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A cycle management method based on Internet of Things technology, characterized in that: The method is applied to an Internet of Things platform, the Internet of Things platform runs on an infrastructure, the Internet of Things platform is connected to a plurality of Internet of Things devices and an application-side device respectively, the Internet of Things device is used to transmit data to the Internet of Things platform, and an Internet of Things application runs on the application-side device, and the method includes: Acquire first cycle configuration information sent by the Internet of Things application, where the first cycle configuration information includes a first device constraint and a first cycle; Determine a target IoT device from the plurality of IoT devices according to the first device constraint condition; The first cycle is sent to the target IoT device.

2. The method according to claim 1, characterized in that The first cycle configuration information further includes a first priority, where the first priority is used to indicate a priority of the first cycle. The method further includes: Sending the first priority to the target IoT device; Acquire second cycle configuration information sent by the Internet of Things application, where the second cycle configuration information includes a second device constraint, a second cycle, and a second priority, where the second priority is used to indicate a priority of the second cycle; Determining the target IoT device from the plurality of IoT devices according to the second device constraint condition; Sending the second priority and the second period to the target IoT device; In a case where the first priority is higher than the second priority, the target IoT device reports the attribute information using a first period associated with the first priority; and / or When the second priority is higher than the first priority, the target IoT device reports the attribute information using a second period associated with the second priority.

3. The method according to claim 1 or 2, characterized in that: The first device constraint condition includes a first device computing power condition, and determining a target IoT device from the plurality of IoT devices according to the first device constraint condition includes: According to the first device computing power condition, a target IoT device that meets the first device computing power condition is determined from the multiple IoT devices.

4. The method according to any one of claims 1 to 3, characterized in that: The first cycle configuration information also includes a first time condition, which is used to indicate the effective time of the target IoT device executing the first cycle; the second cycle configuration information also includes a second time condition, which is used to indicate the effective time of the target IoT device executing the second cycle.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: Receive multiple reporting information sent by the target IoT device, each of the multiple reporting information includes attribute information and time information of the target IoT device; Determine the period of the target Internet of Things device according to the multiple reporting information.

6. An Internet of Things platform, characterized in that: The Internet of Things platform runs on the infrastructure, and the Internet of Things platform is connected to the Internet of Things device and the application side device respectively. The Internet of Things device is used to transmit data to the Internet of Things platform, and the Internet of Things application runs on the application side device. The Internet of Things platform includes: An acquisition module, the acquisition module is used to acquire first cycle configuration information sent by the Internet of Things application, the first cycle configuration information including a first device constraint and a first cycle; A determination module, the determination module being configured to determine a target IoT device from the plurality of IoT devices according to the first device constraint condition; A sending module, wherein the sending module is used to send the first cycle to the target Internet of Things device.

7. The Internet of Things platform according to claim 6, characterized in that: The first cycle configuration information further includes a first priority, where the first priority is used to indicate a priority of the first cycle. Then: The sending module is further used to send the first priority to the target IoT device; The acquisition module is further used to acquire second cycle configuration information sent by the Internet of Things application, where the second cycle configuration information includes a second device constraint, a second cycle, and a second priority, where the second priority is used to indicate the priority of the second cycle; The determination module is further configured to determine the target IoT device from the plurality of IoT devices according to the second device constraint condition; The sending module is further used to send the second priority and the second period to the target Internet of Things device; In a case where the first priority is higher than the second priority, the target IoT device reports the attribute information using a first period associated with the first priority; and / or When the second priority is higher than the first priority, the target IoT device reports the attribute information using a second period associated with the second priority.

8. The Internet of Things platform according to claim 6 or 7, characterized in that: The first device constraint condition includes a first device computing power condition, and the target IoT device is determined from the plurality of IoT devices according to the first device constraint condition. The determination module is specifically used to determine, according to the first device computing power condition, a target IoT device that meets the first device computing power condition from among the multiple IoT devices.

9. The Internet of Things platform according to any one of claims 6 to 8, characterized in that: The first cycle configuration information also includes a first time condition, which is used to indicate the effective time of the target IoT device executing the first cycle; the second cycle configuration information also includes a second time condition, which is used to indicate the effective time of the target IoT device executing the second cycle.

10. The Internet of Things platform according to any one of claims 6 to 9, characterized in that: The IoT platform also includes: A receiving module, the receiving module is further used to receive multiple reporting information sent by the target Internet of Things device, each of the multiple reporting information includes attribute information and time information of the target Internet of Things device; then, The determination module is further used to determine the cycle of the target IoT device according to the multiple reporting information.

11. An Internet of Things system, characterized in that: The Internet of Things system includes: An Internet of Things platform, the Internet of Things platform is used for the first cycle configuration information sent by the Internet of Things application, the first cycle configuration information including a first device constraint and a first cycle, and is further used to determine a target Internet of Things device from the multiple Internet of Things devices according to the first device constraint, and send the first cycle to the target Internet of Things device; An Internet of Things device, the Internet of Things device is used to obtain the first priority, the first period, the second priority and the second period sent by the Internet of Things platform, and is also used to report attribute information using the first period associated with the first priority when the first priority is higher than the second priority; and / or When the second priority is higher than the first priority, the attribute information is reported using a second period associated with the second priority.

12. A computing device cluster, characterized in that: comprising at least one computing device, each computing device comprising a processor and a memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to any one of claims 1 to 5.

13. A computer program product comprising instructions, characterized in that When the instructions are executed by a computer device cluster, the computer device cluster executes the method according to any one of claims 1 to 5.

14. A computer-readable storage medium, characterized in that: The method comprises computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster performs the method according to any one of claims 1 to 5.

Images