Object model registration method, Internet of Things cloud platform, Internet of Things device and computer program product

Abstract

The invention discloses an object model registration method, an Internet of Things cloud platform, Internet of Things equipment and a computer program product, and relates to the technical field of Internet of Things, the object model registration method is applied to the Internet of Things cloud platform, and the method comprises the following steps: receiving an object model registration request sent by the Internet of Things equipment; extracting target object model information from the object model registration request; according to the target object model information, the target object model is registered to the Internet of Things cloud platform, the Internet of Things equipment is associated with the target object model on the Internet of Things cloud platform, and the target object model is obtained through local design based on object model design rules of the Internet of Things cloud platform. According to the invention, the problem that the production of the Internet of Things equipment is inconvenient due to strong coupling between hardware production and cloud platform design in the development process of the traditional Internet of Things equipment can be solved.

Description

Technical Field

[0001] The present application relates to the technical field of Internet of Things, and in particular to a method for registering a physical model, an Internet of Things cloud platform, an Internet of Things device, and a computer program product. Background Art

[0002] With the rapid development of IoT technology, more and more smart devices are connected to the Internet, forming a huge IoT system. In the IoT system, the object model plays a vital role. It is a standard template that describes the functions, properties and services of IoT devices, and is used to achieve interoperability between devices and consistency of data exchange.

[0003] Currently, in the traditional IoT device development process, device manufacturers usually need to design and register object models on the IoT cloud platform, then download the designed object models to the local computer, burn them into the IoT devices, and then connect the IoT devices to the IoT cloud platform to associate the IoT devices with the registered object models.

[0004] However, this approach leads to a tight coupling between the production of IoT devices and the physical model design of the cloud platform. On the one hand, when designing physical models, equipment manufacturers are limited by the tools and frameworks provided by the IoT cloud platform, making it difficult to design highly customized physical models based on actual needs. On the other hand, during the iterative adjustment of physical models, since the design of physical models must be completed on the IoT cloud platform, each time the equipment manufacturer modifies the physical model, it needs to log in to the cloud platform again to make changes and wait for the IoT cloud platform to confirm the physical model design before the modified and adjusted physical model can be burned into the IoT device. This is time-consuming, not conducive to rapid iteration and flexible adjustment, and increases the cycle from design to market launch of IoT devices. Summary of the invention

[0005] The main purpose of this application is to provide a physical model registration method, an IoT cloud platform, an IoT device and a computer program product, aiming to solve the technical problem that in the traditional IoT device development process, the strong coupling between hardware production and cloud platform design leads to inconvenience in IoT device production.

[0006] To achieve the above purpose, the present application provides a method for registering a physical model, which is applied to an Internet of Things cloud platform and includes:

[0007] After receiving the object model registration request sent by the Internet of Things device, extracting the target object model information from the object model registration request;

[0008] According to the target object model information, the target object model is registered to the Internet of Things cloud platform, and the Internet of Things device is associated with the target object model on the Internet of Things cloud platform, wherein the target object model is designed locally based on the object model design rules of the Internet of Things cloud platform.

[0009] In one embodiment, the target object model information includes a target object model ID, and the step of registering the target object model to the IoT cloud platform according to the target object model information, and associating the IoT device with the target object model on the IoT cloud platform includes:

[0010] According to the target object model ID, detecting whether the target object model has been registered to the Internet of Things cloud platform;

[0011] When it is determined that the target object model has not been registered to the IoT cloud platform, the target object model is registered to the IoT cloud platform according to the target object model information, and the IoT device is associated with the target object model on the IoT cloud platform.

[0012] In one embodiment, the step of detecting whether the target object model has been registered to the IoT cloud platform according to the target object model ID includes:

[0013] Among the object models registered on the IoT cloud platform, detecting whether there is an object model whose object model ID is the same as the target object model ID;

[0014] If it is detected that there is no object model with the same object model ID as the target object model ID, it is determined that the target object model is not registered in the Internet of Things cloud platform;

[0015] If an object model having an object model ID identical to the target object model ID is detected, it is determined that the target object model has been registered to the Internet of Things cloud platform.

[0016] In one embodiment, the target object model information further includes a target version number, and the method further includes:

[0017] In the case where it is determined that the target object model has been registered on the IoT cloud platform, detecting whether the version number of the target object model registered on the IoT cloud platform includes the target version number;

[0018] If it is detected that the version number of the target object model registered on the IoT cloud platform includes the target version number, the IoT device is associated with the target object model with the target version number on the IoT cloud platform.

[0019] In one embodiment, after the step of detecting whether the version number of the target object model registered on the IoT cloud platform includes the target version number, the method further includes:

[0020] If it is detected that the version number of the target object model registered on the IoT cloud platform does not include the target version number, the target object model with the target version number is registered to the IoT cloud platform based on the target object model information, and the IoT device is associated with the target object model with the target version number on the IoT cloud platform.

[0021] In addition, the present application provides a method for registering a physical model, which is applied to an IoT device and includes:

[0022] Sending an object model registration request to an Internet of Things cloud platform, so that the Internet of Things cloud platform extracts target object model information from the object model registration request, registers the target object model to the Internet of Things cloud platform according to the target object model information, and associates the Internet of Things device with the target object model on the Internet of Things cloud platform;

[0023] The target object model is designed locally based on the object model design rules of the Internet of Things cloud platform.

[0024] In one embodiment, the target object model information is determined by a physical model file pre-burned in the IoT device, and the physical model file is a configuration file corresponding to the target object model.

[0025] In addition, to achieve the above-mentioned purpose, the present application also provides an Internet of Things cloud platform, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the computer program is executed by the processor, the steps of the object model registration method as applied to the Internet of Things cloud platform as mentioned above are implemented.

[0026] In addition, to achieve the above-mentioned purpose, the present application also provides an Internet of Things device, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein when the computer program is executed by the processor, the steps of the object model registration method as applied to the Internet of Things device as mentioned above are implemented.

[0027] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the steps of the object model registration method as applied to the Internet of Things cloud platform or the Internet of Things device as mentioned above.

[0028] The present application provides a method for registering a physical model, an Internet of Things cloud platform, an Internet of Things device, and a computer program product. The method for registering a physical model is applied to the Internet of Things cloud platform. After receiving a physical model registration request sent by an Internet of Things device, the present application extracts target physical model information from the physical model registration request, and then registers the target physical model to the Internet of Things cloud platform according to the target physical model information, and associates the Internet of Things device with the target physical model on the Internet of Things cloud platform, wherein the target physical model is designed locally based on the physical model design rules of the Internet of Things cloud platform, so that the present application can design the target physical model based on the physical model design rules of the Internet of Things cloud platform locally, and then produce the Internet of Things device according to the target physical model, and burn the target physical model into the Internet of Things device, and then the Internet of Things device uploads the target physical model to the Internet of Things cloud platform after establishing a connection with the Internet of Things platform, completes the registration and association of the target physical model, and then realizes the decoupling between hardware production and cloud platform design, so that the design and modification of the physical model are not strictly restricted by the Internet of Things cloud platform, and the device manufacturer can flexibly and independently adjust the design of the physical model according to actual needs, so that the Internet of Things device can better adapt to different application scenarios.

[0029] In addition, designing physical models locally can effectively reduce dependence on the IoT cloud platform, reduce the risk of confidential information leakage during data transmission, and reduce production downtime caused by waiting for confirmation from the IoT cloud platform, so as to iterate and upgrade IoT devices more quickly and significantly speed up the speed of putting IoT devices into market operation, so as to better adapt to the ever-changing market environment. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0031] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the structures shown in these drawings without paying any creative work.

[0032] Figure 1 A flowchart of the first embodiment of the object model registration method of the present application is provided;

[0033] Figure 2 A flowchart of the second embodiment of the object model registration method of the present application is provided;

[0034] Figure 3A flowchart of the third embodiment of the object model registration method of the present application is provided;

[0035] Figure 4 An architectural diagram provided for a specific embodiment of the present application;

[0036] Figure 5 A flowchart provided for a specific embodiment of the present application;

[0037] Figure 6 A schematic diagram of the device structure of the hardware operating environment involved in the method for registering a thing model applied to the Internet of Things cloud platform in an embodiment of the present application;

[0038] Figure 7 Schematic diagram of the device structure of the hardware operating environment involved in the method for registering a thing model for an Internet of Things device in an embodiment of the present application.

[0039] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0040] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0041] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0042] Currently, in the traditional IoT device development process, device manufacturers usually need to design and register object models on the IoT cloud platform, then download the designed object models to the local computer, burn them into the IoT devices, and then connect the IoT devices to the IoT cloud platform to associate the IoT devices with the registered object models.

[0043] However, this approach leads to a tight coupling between the production of IoT devices and the physical model design of the cloud platform. On the one hand, when designing physical models, equipment manufacturers are limited by the tools and frameworks provided by the IoT cloud platform, making it difficult to design highly customized physical models based on actual needs. On the other hand, during the iterative adjustment of physical models, since the design of physical models must be completed on the IoT cloud platform, each time the equipment manufacturer modifies the physical model, it needs to log in to the cloud platform again to make changes and wait for the IoT cloud platform to confirm the physical model design before the modified and adjusted physical model can be burned into the IoT device. This is time-consuming, not conducive to rapid iteration and flexible adjustment, and increases the cycle from design to market launch of IoT devices.

[0044] In response to the above technical problems, the first technical solution of the present application is: after receiving the object model registration request sent by the Internet of Things device, extract the target object model information from the object model registration request; according to the target object model information, register the target object model to the Internet of Things cloud platform, and associate the Internet of Things device with the target object model on the Internet of Things cloud platform, wherein the target object model is designed locally based on the object model design rules of the Internet of Things cloud platform.

[0045] The present application can design a target object model by using the object model design rules based on the local IoT cloud platform, then produce IoT devices according to the target object model, and burn the target object model into the IoT devices. After the IoT devices establish a connection with the IoT platform, they upload the target object model to the IoT cloud platform to complete the registration and association of the target object model, thereby achieving the decoupling between hardware production and cloud platform design, so that the design and modification of the object model are not strictly restricted by the IoT cloud platform. Equipment manufacturers can flexibly and independently adjust the design of the object model according to actual needs, thereby enabling IoT devices to better adapt to different application scenarios.

[0046] In addition, designing physical models locally can effectively reduce dependence on the IoT cloud platform, reduce the risk of confidential information leakage during data transmission, and reduce production downtime caused by waiting for confirmation from the IoT cloud platform, so as to iterate and upgrade IoT devices more quickly and significantly speed up the speed of putting IoT devices into market operation, so as to better adapt to the ever-changing market environment.

[0047] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0048] Please refer to Figure 1 , Figure 1 A flowchart of the first embodiment of the object model registration method of the present application is provided.

[0049] In this embodiment, the method is applied to the Internet of Things cloud platform, including steps S100 to S200:

[0050] Step S100, after receiving the object model registration request sent by the IoT device, extracting the target object model information from the object model registration request;

[0051] Step S200, registering the target object model to the IoT cloud platform according to the target object model information, and associating the IoT device with the target object model on the IoT cloud platform, wherein the target object model is designed locally based on the object model design rules of the IoT cloud platform.

[0052] Those skilled in the art will know that the IoT cloud platform refers to a service platform built on cloud computing technology, which is specifically designed to provide management and control functions for IoT (Internet of Things) devices. The IoT cloud platform is a comprehensive service platform that integrates a variety of services and tools. It not only provides the infrastructure required to manage and control IoT devices, but also provides developers with development tools and corresponding application programming interfaces so that developers can easily develop and deploy IoT applications, making the deployment and management of IoT projects simpler and more efficient. IoT devices refer to smart devices that have networking capabilities and can communicate with the IoT cloud platform.

[0053] It should be noted that the object model is a standardized template or description used in IoT technology to describe the functional characteristics of IoT devices. It defines the services that IoT devices can provide, the properties they have, and the operations they can perform. Object models usually include the following aspects:

[0054] Properties: Represents the status information of IoT devices, such as temperature, humidity, switch status, etc.

[0055] Services: Functions that IoT devices can provide, such as turning lights on and off, adjusting brightness, etc.

[0056] Events: Specific events that occur in IoT devices, such as alarms, failures, etc.

[0057] Those skilled in the art will know that the role of the physical model is to:

[0058] Standardization: Provide a unified language to describe the functional characteristics of different IoT devices to facilitate interoperability between IoT devices.

[0059] Interoperability: enables IoT devices produced by different device manufacturers to work together in the same IoT ecosystem.

[0060] Data consistency: Ensure the consistency and predictability of IoT device data to facilitate data processing and analysis.

[0061] In this embodiment, the object model registration request refers to a request sent by the IoT device to the IoT cloud platform, requesting that the object model currently used by the IoT device (i.e., the target object model) be registered with the IoT cloud platform, and establishing an association between the IoT device and the object model. The object model registration request usually includes a device identifier, object model information, and other metadata, where the object model information refers to detailed information describing the functional characteristics of the IoT device, including attributes, services, and events.

[0062] Specifically, the object model information may include:

[0063] List of attributes: Status information that IoT devices can report, such as temperature, humidity, etc.

[0064] Service list: operations or functions that IoT devices can provide, such as switch control, adjustment settings, etc.

[0065] Event list: specific events that may be triggered by IoT devices, such as alarms, fault notifications, etc.

[0066] Data format: The structure and format of data that describes attributes and services.

[0067] Operation instructions: The commands and parameter definitions that IoT devices can respond to.

[0068] In this embodiment, the object model information is used for object model registration. In this embodiment, by carrying the object model information in the object model registration request, the IoT cloud platform extracts the object model information from the object model registration request after receiving it, and parses the object model information to determine the attribute list, service list, event list and other information of the IoT device, thereby creating an object model entry on the IoT cloud platform according to the attribute list, service list, event list and other information of the IoT device, and completing the registration of the object model.

[0069] It should be noted that, in this embodiment, the target object model information is the object model information carried in the object model registration request, which is used for registration of the target object model, and the target object model is the object model currently used by the IoT device that is required to be registered to the IoT cloud platform in the object model registration request.

[0070] In addition, it should be noted that the object model design rules refer to a series of regulations and standards that must be followed when designing object models to ensure the consistency, readability, and interoperability of object models. Object model design rules are usually formulated by the IoT cloud platform and provided to developers as guidelines for designing object models.

[0071] Those skilled in the art will know that in traditional physical model design, developers need to create an account on the IoT cloud platform, log in to the IoT cloud platform through the account, and define the design physical model through the physical model design tool or framework provided by the IoT cloud platform. After the design is completed, it needs to be submitted to the IoT cloud platform, and the IoT cloud platform needs to wait for confirmation that the physical model design complies with the physical model design rules and follows the corresponding rules and standards before the designed physical model can be registered with the IoT cloud platform, exported as a physical model file, and burned into the IoT device.

[0072] In this traditional physical model design, developers need to rely on the tools and frameworks provided by the IoT cloud platform. When the tools of the IoT cloud platform are not flexible enough, developers cannot fully customize the physical model according to actual needs, which limits the flexibility and freedom of physical model design. In addition, every time the physical model is modified, the developer needs to log in to the IoT cloud platform to operate, and needs to wait for the cloud platform to confirm whether the physical model design complies with the physical model design rules. This greatly increases the cycle from design to production of IoT devices. Especially when the physical model needs to be updated and iterated frequently, it will seriously slow down the iteration and upgrade of IoT devices, causing IoT devices to lose competitiveness in the market and be eliminated.

[0073] In addition, this traditional physical model design is heavily dependent on the IoT cloud platform. If problems or maintenance upgrades occur on the IoT cloud platform during the physical model design process, developers will not be able to complete the design and update of the physical model in a timely manner. At the same time, there is also the risk of confidential information leakage during data transmission.

[0074] In this embodiment, after the IoT device establishes a connection with the IoT cloud platform, the IoT device sends an object model registration request carrying the target object model information to the IoT cloud platform. After receiving the object model registration request, the IoT cloud platform parses the request data packet and extracts the target object model information therefrom, thereby parsing the target object model information, extracting definitions such as attributes, services and events, and verifying them according to the object model design rules. After the verification is passed, an object model entry corresponding to the target object model is created, which contains all the definition information of the object model, that is, the definitions of attributes, services and events extracted by parsing the target object model information, and completes the registration of the target object model. Then, a reference to the object model entry corresponding to the target object model is added to the device entry corresponding to the IoT device, thereby associating the IoT device with the target object model on the IoT platform.

[0075] Compared with the traditional object model design, this embodiment extracts the target object model information from the object model registration request after receiving the object model registration request sent by the Internet of Things device, and then registers the target object model to the Internet of Things cloud platform according to the target object model information, and associates the Internet of Things device with the target object model on the Internet of Things cloud platform, wherein the target object model is designed locally based on the object model design rules of the Internet of Things cloud platform, so that this embodiment can design the target object model based on the object model design rules of the Internet of Things cloud platform locally, and then produce the Internet of Things device according to the target object model, and burn the target object model into the Internet of Things device, and then the Internet of Things device uploads the target object model to the Internet of Things cloud platform after establishing a connection with the Internet of Things platform, completes the registration and association of the target object model, and then realizes the decoupling between hardware production and cloud platform design, so that the design and modification of the object model are not strictly restricted by the Internet of Things cloud platform, and the equipment manufacturer can flexibly and independently adjust the design of the object model according to actual needs, so that the Internet of Things device can better adapt to different application scenarios.

[0076] In addition, designing physical models locally can effectively reduce dependence on the IoT cloud platform, reduce the risk of confidential information leakage during data transmission, and reduce production downtime caused by waiting for confirmation from the IoT cloud platform, so as to iterate and upgrade IoT devices more quickly and significantly speed up the speed of putting IoT devices into market operation, so as to better adapt to the ever-changing market environment.

[0077] Please refer to Figure 2 , Figure 2 A flowchart of the second embodiment of the object model registration method of the present application is provided.

[0078] In this embodiment, the same or similar contents as those in the above embodiments can be referred to the above introduction and will not be described in detail later.

[0079] In this embodiment, the target object model information includes a target object model ID, and the step of registering the target object model to the IoT cloud platform according to the target object model information and associating the IoT device with the target object model on the IoT cloud platform includes steps S210 to S220:

[0080] Step S210, detecting whether the target object model has been registered to the IoT cloud platform according to the target object model ID;

[0081] It should be noted that the object model ID (Identity) is an identifier used to uniquely identify an object model, similar to the unique ID of a device, ensuring the uniqueness of each object model on the IoT cloud platform. The target object model ID is an identifier used to uniquely identify the target object model.

[0082] In this embodiment, when the device manufacturer designs the physical model locally based on the physical model design rules of the IoT cloud platform, an exclusive physical model ID is assigned to each physical model. The uniqueness of the physical model ID can be guaranteed by prior negotiation between the device manufacturer and the operator of the IoT cloud platform, or by generating a UUID (Universally Unique Identifier) ​​as the physical model ID.

[0083] Therefore, in this embodiment, after the IoT cloud platform extracts the target object model ID from the object model registration request, it can query the database of the IoT cloud platform based on the target object model ID to determine whether the target object model has been registered in the IoT platform.

[0084] Specifically, in a feasible implementation manner, step S210 may include steps S211 to S213:

[0085] Step S211, detecting whether there is a physical model with the same physical model ID as the target physical model ID among the physical models registered on the IoT cloud platform;

[0086] Step S212: if it is detected that there is no object model with the same object model ID as the target object model ID, it is determined that the target object model has not been registered to the IoT cloud platform;

[0087] Step S213: If it is detected that there is an object model whose object model ID is the same as the target object model ID, it is determined that the target object model has been registered with the Internet of Things cloud platform.

[0088] In this embodiment, the database of the IoT cloud platform can be queried to detect whether there is a physical model whose physical model ID is the same as the target physical model ID among the physical models registered on the IoT cloud platform. If not, it is determined that the target physical model has not been registered on the IoT cloud platform. If so, it is determined that the target physical model has been registered on the IoT cloud platform.

[0089] This implementation method detects whether the same object model ID exists through database query, quickly determines whether the object model has been registered, improves detection efficiency, ensures the uniqueness of each object model on the IoT cloud platform, prevents repeated registration of the same object model, and avoids data redundancy.

[0090] Step S220, when it is determined that the target object model has not been registered with the IoT cloud platform, register the target object model with the IoT cloud platform according to the target object model information, and associate the IoT device with the target object model on the IoT cloud platform.

[0091] This embodiment detects whether the target object model has been registered through the target model ID, and if it is determined that the target object model has not been registered to the IoT cloud platform, the target object model is registered to the IoT cloud platform according to the target object model information, thereby ensuring the uniqueness of the object model and the consistency of the data, preventing repeated registration of the same object model, and avoiding data redundancy. At the same time, after registering the target object model to the IoT cloud platform, this embodiment also logically associates the IoT device with the target object model on the IoT cloud platform, so that the IoT device can work normally according to the functional characteristics defined by the target object model, and perform efficient data interaction with the cloud platform.

[0092] Furthermore, in a feasible implementation manner, the target object model information further includes a target version number, and the method further includes steps S230 to S240:

[0093] Step S230, when it is determined that the target object model has been registered on the IoT cloud platform, detecting whether the version number of the target object model registered on the IoT cloud platform includes the target version number;

[0094] It should be noted that the version number is used to identify different versions of the same object model, and the target version number is the version number of the target object model currently used by the IoT device. It is not difficult to understand that in actual applications, depending on market changes and application scenarios, the same object model usually has multiple versions of iterative updates, and different versions correspond to different version numbers. Since the new version is not necessarily compatible with the old version, after the new version is released, the old version has not been completely eliminated and discarded. At this time, on the IoT cloud platform, the same object model will have multiple versions at the same time. Through the version control function of the IoT cloud platform, multiple versions can be managed and controlled.

[0095] When determining that the target object model has been registered on the IoT cloud platform, this embodiment takes into account possible version updates and queries the database of the IoT cloud platform to detect whether there is a version with the same version number as the target version number among the versions of the target object model registered on the IoT cloud platform. That is, it detects whether the version number of the target object model registered on the IoT cloud platform includes the target version number, thereby determining whether the version of the target object model currently used by the IoT device has been registered on the IoT cloud platform.

[0096] Step S240: If it is detected that the version number of the target object model registered on the IoT cloud platform includes the target version number, the IoT device is associated with the target object model of the target version number on the IoT cloud platform.

[0097] In this embodiment, by querying the database of the IoT cloud platform, if it is detected that the version number of the target object model registered on the IoT cloud platform includes the target version number, that is, in the version of the target object model registered on the IoT cloud platform, it is detected that there is a version with the same version number as the target version number, then it is determined that the version of the target object model currently used by the IoT device has been registered on the IoT cloud platform. At this time, the IoT device can be directly associated with the target object model with the target version number on the IoT cloud platform to ensure that the version of the target object model currently used by the IoT device is consistent with the version of the target object model associated with the IoT device on the IoT cloud platform, preventing the IoT device from using an old or new version of the target object model, ensuring smooth data exchange between the IoT device and the IoT cloud platform, avoiding data mismatch problems, and enhancing interoperability and compatibility between IoT devices with the same object model and the same version.

[0098] Furthermore, in a feasible implementation manner, after the step of detecting whether the version number of the target object model registered on the IoT cloud platform includes the target version number, the method further includes step S250:

[0099] Step S250, if it is detected that the version number of the target object model registered on the IoT cloud platform does not include the target version number, the target object model of the target version number is registered to the IoT cloud platform according to the target object model information, and the IoT device is associated with the target object model of the target version number on the IoT cloud platform.

[0100] In this embodiment, by querying the database of the IoT cloud platform, if it is detected that the version number of the target object model registered on the IoT cloud platform does not include the target version number, that is, in the version of the target object model registered on the IoT cloud platform, it is detected that there is no version with the same version number as the target version number, then it is determined that the version of the target object model currently used by the IoT device has not been registered on the IoT cloud platform. At this time, it is necessary to first register the target object model with the target version number to the IoT cloud platform according to the target object model information, that is, through the version management function of the IoT cloud platform, in the object model entry corresponding to the target object model in the IoT cloud platform, add the version of the target object model currently used by the IoT device, and then associate the IoT device with the target object model with the target version number on the IoT cloud platform, to ensure that the version of the target object model currently used by the IoT device is consistent with the version of the target object model associated with the IoT device on the IoT cloud platform, to prevent the IoT device from using an old or new version of the target object model, to ensure smooth data exchange between the IoT device and the IoT cloud platform, to avoid data mismatch problems, and to enhance the interoperability and compatibility between IoT devices with the same object model and the same version.

[0101] Please refer to Figure 3 , Figure 3 This is a flow chart of the third embodiment of the object model registration method of the present application.

[0102] In this embodiment, the same or similar contents as those in the above embodiments can be referred to the above introduction and will not be described in detail later.

[0103] In this embodiment, the method is applied to an IoT device, and includes step S300:

[0104] Step S300, sending an object model registration request to the Internet of Things cloud platform, so that the Internet of Things cloud platform can extract the target object model information from the object model registration request, register the target object model to the Internet of Things cloud platform according to the target object model information, and associate the Internet of Things device with the target object model on the Internet of Things cloud platform.

[0105] The target object model is designed locally based on the object model design rules of the Internet of Things cloud platform.

[0106] In this embodiment, the target object model information is determined by a physical model file pre-burned in the IoT device, and the physical model file is a configuration file corresponding to the target object model.

[0107] It should be noted that, in this embodiment, the equipment manufacturer designs the target object model locally based on the object model design rules of the IoT cloud platform, and then exports the target object model as a object model file, and burns the object model file into the IoT device. After the IoT device establishes a connection with the IoT platform, it sends a object model registration request, uploads the target object model to the IoT cloud platform, completes the registration of the target object model, and associates the IoT device with the target object model.

[0108] In this embodiment, after establishing a connection with the IoT platform, the IoT device can parse the pre-burned physical model file to extract detailed information describing the functional characteristics of the IoT device (such as properties, services, and events, etc.), and attach it to the physical model registration request as the physical model information and send it to the IoT cloud platform. It can also directly read the pre-burned physical model file, attach it to the physical model registration request as the physical model information and send it to the IoT cloud platform.

[0109] It is worth mentioning that the object model information may include the object model ID and version number of the target object model, that is, the target object model ID and the target version number. It is not difficult to understand that the target object model ID and the target version number are detailed information of the attribute class function characteristics, among which the target object model ID is mainly used to prevent repeated registration of the target object model, and the target version number is mainly used to prevent repeated registration of the version of the target object model.

[0110] Through the object model registration method provided in this embodiment, the equipment manufacturer can locally design the target object model based on the object model design rules of the Internet of Things cloud platform, and then produce the Internet of Things device according to the target object model, and burn the target object model into the Internet of Things device. Then, after the Internet of Things device establishes a connection with the Internet of Things platform, it uploads the target object model to the Internet of Things cloud platform to complete the registration and association of the target object model, thereby realizing the decoupling between hardware production and cloud platform design, so that the design and modification of the object model are not strictly restricted by the Internet of Things cloud platform. The equipment manufacturer can flexibly and independently adjust the design of the object model according to actual needs, so that the Internet of Things device can better adapt to different application scenarios.

[0111] In addition, designing physical models locally can effectively reduce dependence on the IoT cloud platform, reduce the risk of confidential information leakage during data transmission, and reduce production downtime caused by waiting for confirmation from the IoT cloud platform, so as to iterate and upgrade IoT devices more quickly and significantly speed up the speed of putting IoT devices into market operation, so as to better adapt to the ever-changing market environment.

[0112] In order to facilitate understanding of the technical concept or technical principle of the above-mentioned embodiment of the object model registration method of the present application, a specific embodiment is listed:

[0113] like Figure 4 As shown, in this specific embodiment, the factory (ie, the equipment manufacturer) independently designs and manufactures the object model (ie, the target object model) locally, and burns it into the device (ie, the IoT device), and then the device reports the object model to the cloud server (ie, the IoT cloud platform).

[0114] like Figure 5 As shown, in this specific embodiment, the overall process is as follows:

[0115] Step 1: Create object model files according to the rules.

[0116] In this specific embodiment, the device manufacturer (i.e., the device manufacturer) makes the object model by itself according to the platform object model rules (i.e., the object model design rules of the IoT cloud platform), without having to create it in advance on the cloud server. That is, the target object model is designed locally based on the object model design rules of the IoT cloud platform.

[0117] Step 2: Burn the physical model file to the device.

[0118] In this specific embodiment, the factory burns the prepared physical model file to the device for subsequent registration with the cloud server.

[0119] Step 3: The device is online.

[0120] Step 4: The device is online successfully.

[0121] In this specific embodiment, after the physical model file is successfully burned to the device, the device initiates a connection request to the designated cloud server, requesting to go online. The cloud server verifies the connection request and establishes a connection with the device after the verification is passed, and the device goes online successfully.

[0122] Step 5: Analyze the object model file.

[0123] Step 6: Register the object model to the server.

[0124] In this specific embodiment, after the device establishes a connection with the cloud server, the device parses the burned object model file, and appends the parsed information (i.e., the object model information) to the object model registration request, and sends the object model registration request to the cloud server to register the object model to the cloud server, and complete the mapping of the device-side and cloud-side object models. That is, the target object model information is determined by the object model file pre-burned in the IoT device, and the object model registration request is sent to the IoT cloud platform, so that the IoT cloud platform can extract the target object model information from the object model registration request, register the target object model to the IoT cloud platform according to the target object model information, and associate the IoT device with the target object model on the IoT cloud platform.

[0125] Step 7: The object model is successfully registered.

[0126] Step 8: The device interacts with the cloud based on the object model.

[0127] In this specific embodiment, after the object model is successfully registered, the cloud server feeds back registration success information to the device, and the device begins to interact with the cloud server based on the registered and associated object model (attributes, functions, events).

[0128] It should be noted that the above examples are only used to assist in understanding the present application and do not constitute a limitation on the object model registration method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0129] In addition, please refer to Figure 6 , Figure 6 Schematic diagram of the device structure of the hardware operating environment involved in the object model registration method applied to the Internet of Things cloud platform in the embodiment of the present application.

[0130] The present application also provides an Internet of Things cloud platform, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the steps of the object model registration method in the above-mentioned embodiment.

[0131] Reference below Figure 6 , which shows a schematic diagram of the structure of an IoT cloud platform suitable for implementing the embodiments of the present application. The IoT cloud platform in the embodiments of the present application may include but is not limited to Alibaba Cloud IoT, Tencent Cloud IoT, Baidu Tiangong IoT Platform, JD Zhilian Cloud, Xiaomi IoT, Google Cloud IoT, Cisco IoT, etc., or any IoT cloud platform that can implement the above functions. Figure 6 The IoT cloud platform shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present application.

[0132] like Figure 6 As shown, the IoT cloud platform may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which may perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the IoT cloud platform are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems may be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the IoT cloud platform to communicate with other devices wirelessly or wired to exchange data. Although the figure shows an IoT cloud platform with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or provided instead.

[0133] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0134] The IoT cloud platform provided by the present application adopts the object model registration method applied to the IoT cloud platform in the above embodiment, which can solve the technical problem that the strong coupling between hardware production and cloud platform design leads to inconvenience in the production of IoT devices in the traditional IoT device development process. Compared with the prior art, the beneficial effects of the IoT cloud platform provided by the present application are the same as the beneficial effects of the object model registration method applied to the IoT cloud platform provided by the above embodiment, and the other technical features in the IoT cloud platform are the same as the features of the object model registration method applied to the IoT cloud platform disclosed in the above embodiment method, which will not be repeated here.

[0135] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0136] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0137] In addition, please refer to Figure 7 , Figure 7 Schematic diagram of the device structure of the hardware operating environment involved in the method for registering a thing model for an Internet of Things device in an embodiment of the present application.

[0138] The present application also provides an Internet of Things device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the steps of the object model registration method in the above-mentioned embodiment.

[0139] Reference below Figure 7 , which shows a schematic diagram of the structure of an Internet of Things device suitable for implementing the embodiments of the present application. The Internet of Things devices in the embodiments of the present application may include but are not limited to smart home devices, industrial automation equipment, medical and health equipment, agricultural equipment, logistics and storage equipment, transportation equipment, energy management equipment, security equipment, educational equipment, etc., or any Internet of Things device that can achieve the above functions. Figure 7 The IoT device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of the present application.

[0140] like Figure 7As shown, the IoT device may include a processing device 2001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 2002 or a program loaded from a storage device 2003 to a random access memory (RAM: Random Access Memory) 2004. In RAM2004, various programs and data required for the operation of the IoT device are also stored. The processing device 2001, ROM2002, and RAM2004 are connected to each other via a bus 2005. An input / output (I / O) interface 2006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 2006: an input device 2007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 2008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 2003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 2009. The communication device 2009 can allow the IoT device to communicate with other devices wirelessly or by wire to exchange data. Although the IoT device with various systems is shown in the figure, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.

[0141] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 2003, or installed from a ROM 2002. When the computer program is executed by the processing device 2001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0142] The IoT device provided by the present application adopts the physical model registration method applied to the IoT device in the above embodiment, which can solve the technical problem that the strong coupling between hardware production and cloud platform design leads to inconvenience in the production of IoT devices in the traditional IoT device development process. Compared with the prior art, the beneficial effects of the IoT device provided by the present application are the same as the beneficial effects of the physical model registration method applied to the IoT device provided by the above embodiment, and the other technical features in the IoT device are the same as the features of the physical model registration method applied to the IoT device disclosed in the above embodiment method, which will not be repeated here.

[0143] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0144] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0145] In addition, the present application also provides a storage medium, which is a computer-readable medium having computer-readable program instructions (i.e., computer programs) stored thereon. When the computer-readable program instructions are executed by a processor, a method for registering a physical model applied to an IoT cloud platform or an IoT device as described in the above-mentioned embodiment is implemented.

[0146] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0147] The above-mentioned computer-readable storage medium may be included in the IoT cloud platform or the IoT device; or it may exist independently without being assembled into the IoT cloud platform or the IoT device.

[0148] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the IoT cloud platform, the IoT cloud platform: after receiving the object model registration request sent by the IoT device, extract the target object model information from the object model registration request; register the target object model to the IoT cloud platform according to the target object model information, and associate the IoT device with the target object model on the IoT cloud platform, wherein the target object model is designed locally based on the object model design rules of the IoT cloud platform.

[0149] When the above one or more programs are executed by the IoT device, the IoT device: sends a physical model registration request to the IoT cloud platform, so that the IoT cloud platform can extract the target physical model information from the physical model registration request, register the target physical model to the IoT cloud platform according to the target physical model information, and associate the IoT device with the target physical model on the IoT cloud platform; wherein the target physical model is designed locally based on the physical model design rules of the IoT cloud platform.

[0150] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0151] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0152] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0153] The computer-readable storage medium provided by the present application stores computer-readable program instructions (i.e., computer programs) for executing the steps of the above-mentioned object model registration method, which can solve the technical problem that the strong coupling between hardware production and cloud platform design leads to inconvenience in the production of Internet of Things devices in the traditional Internet of Things device development process. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the object model registration method applied to the Internet of Things cloud platform or Internet of Things device provided by the above-mentioned embodiment, and will not be repeated here.

[0154] In addition, an embodiment of the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the object model registration method applied to an IoT cloud platform or an IoT device in the above embodiment.

[0155] The computer program product provided by this application can solve the technical problem that the strong coupling between hardware production and cloud platform design in the traditional IoT device development process leads to inconvenience in the production of IoT devices. Compared with the prior art, the beneficial effects of the computer program product provided by the embodiment of this application are the same as the beneficial effects of the object model registration method applied to the IoT cloud platform or IoT device provided by the above embodiment, which will not be repeated here.

[0156] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A method for registering a physical model, characterized in that: The method is applied to the Internet of Things cloud platform, including: After receiving the object model registration request sent by the Internet of Things device, extracting the target object model information from the object model registration request; According to the target object model information, the target object model is registered to the Internet of Things cloud platform, and the Internet of Things device is associated with the target object model on the Internet of Things cloud platform, wherein the target object model is designed locally based on the object model design rules of the Internet of Things cloud platform.

2. The object model registration method according to claim 1, characterized in that: The target object model information includes a target object model ID. The step of registering the target object model to the Internet of Things cloud platform according to the target object model information and associating the Internet of Things device with the target object model on the Internet of Things cloud platform includes: According to the target object model ID, detecting whether the target object model has been registered to the Internet of Things cloud platform; When it is determined that the target object model has not been registered to the IoT cloud platform, the target object model is registered to the IoT cloud platform according to the target object model information, and the IoT device is associated with the target object model on the IoT cloud platform.

3. The object model registration method according to claim 2, characterized in that: The step of detecting whether the target object model has been registered to the Internet of Things cloud platform according to the target object model ID includes: Among the object models registered on the IoT cloud platform, detecting whether there is an object model whose object model ID is the same as the target object model ID; If it is detected that there is no object model with the same object model ID as the target object model ID, it is determined that the target object model is not registered in the Internet of Things cloud platform; If an object model having an object model ID identical to the target object model ID is detected, it is determined that the target object model has been registered to the Internet of Things cloud platform.

4. The object model registration method according to claim 3, characterized in that: The target object model information also includes a target version number, and the method further includes: In the case where it is determined that the target object model has been registered on the IoT cloud platform, detecting whether the version number of the target object model registered on the IoT cloud platform includes the target version number; If it is detected that the version number of the target object model registered on the IoT cloud platform includes the target version number, the IoT device is associated with the target object model with the target version number on the IoT cloud platform.

5. The object model registration method according to claim 4, characterized in that: After the step of detecting whether the version number of the target object model registered on the IoT cloud platform includes the target version number, the method further includes: If it is detected that the version number of the target object model registered on the IoT cloud platform does not include the target version number, the target object model with the target version number is registered to the IoT cloud platform based on the target object model information, and the IoT device is associated with the target object model with the target version number on the IoT cloud platform.

6. A method for registering an object model, characterized in that: The method is applied to an IoT device, including: Sending an object model registration request to an Internet of Things cloud platform, so that the Internet of Things cloud platform extracts target object model information from the object model registration request, registers the target object model to the Internet of Things cloud platform according to the target object model information, and associates the Internet of Things device with the target object model on the Internet of Things cloud platform; The target object model is designed locally based on the object model design rules of the Internet of Things cloud platform.

7. The object model registration method according to claim 6, characterized in that: The target object model information is determined by a physical model file pre-burned in the IoT device, and the physical model file is a configuration file corresponding to the target object model.

8. An Internet of Things cloud platform, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the object model registration method according to any one of claims 1 to 5.

9. An Internet of Things device, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the computer program is executed by the processor, the steps of the object model registration method according to any one of claims 6 to 7 are implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the object model registration method according to any one of claims 1 to 5, or 6 to 7 are implemented.

Images