Equipment in-situ replacement method, Internet of Things platform and medium

Abstract

The invention discloses an equipment in-situ replacement method, an Internet of Things platform and a medium, and relates to the technical field of equipment replacement. Through high abstraction of equipment functions, even if new and old equipment are different in model and appearance, as long as the functions are consistent or the new equipment comprises all functions of the old equipment, the equipment can be considered to be seamlessly compatible instead of being programmed directly for the equipment. And the replacement of the equipment can be quickly completed only by matching the physical model of the new equipment with the physical model of the old equipment. According to the method, the object model used for describing the functions of the equipment is defined, and the control logic of the equipment and the object model are decoupled, so that the replaceability of the equipment is realized. When the equipment needs to be replaced, the physical model of the old equipment only needs to be deleted in the system, the physical model of the new equipment is added, and the system can automatically regenerate the control logic according to the physical model of the new equipment, so that the new equipment can seamlessly replace the old equipment. According to the invention, in-situ replacement of equipment of different models, different versions and different brands can be realized.

Description

Technical Field

[0001] The present invention relates to the technical field of device replacement, and in particular to a method for in-situ replacement of a device, an Internet of Things platform and a medium. Background Art

[0002] With the vigorous promotion of the market in recent years, the shipment volume of equipment has increased significantly. During the long-term use of users, it is inevitable that equipment failures need to be replaced. Equipment replacement is a common business in after-sales support. However, during the replacement process, the following situations often occur, which makes the entire after-sales support experience very bad and even causes customer complaints, mainly reflected in: 1. After the user replaces the device, many of the original functions cannot be used normally, and a lot of configuration is required, which takes a long time.

[0003] 2. The device used by the user is an old model that the company has discontinued. The company cannot find a device of the same model to replace it for the time being, and the company's newly iterative equipment cannot be replaced in situ, resulting in the user's inability to use the device normally and facing complaints. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide a method, an Internet of Things platform and a medium for in-situ replacement of equipment. By highly abstracting the equipment functions to form a physical model and decoupling the control logic of the equipment from the physical model, the replacement of old equipment with new equipment only requires replacing the physical model and regenerating the control logic, thereby realizing in-situ replacement of equipment of different models, versions and brands.

[0005] In a first aspect, the present invention provides a method for in-situ replacement of a device, comprising: Physical model configuration process: according to the function of the device, the physical model is configured, the physical model includes a device table and at least two service tables, the device table is used to describe the device type and the service set of the device, the service table is used to describe the set of mutually related functional units, including service type siid, attribute set piids and function set fiids; when the service type siid is a specified value, it represents a physical service, and when the service type siid is a value other than the specified value, it represents a logical service; Object model comparison process: obtain the object model of the original device through the server and compare it with the object model of the target device. First, determine whether the device types in the two device tables are consistent. If they are consistent, then determine whether the values ​​of the service type siid, attribute set piids, and function set fiids in each service table of the object model of the target device contain the values ​​of the service type siid, attribute set piids, and function set fiids in each service table of the object model of the original device. If they are, it is determined that the target device can replace the original device. Device replacement process: When it is determined that the target device can replace the original device and the user's device replacement instruction is obtained, the device object model file replacement and device business data replacement are executed through the server; after the object model file replacement is completed, the control logic is regenerated according to the service type siid, attribute set piids and function set fiids values ​​in the service table.

[0006] Furthermore, the process of acquiring the object model of the original device includes: acquiring the device unique ID of the original device reported by the user end, and then acquiring the corresponding object model as the object model of the original device according to the device unique ID.

[0007] Furthermore, after the object model of the original device is obtained, the object model of the original device is compared with the object models in the server device library, and all devices that can replace the original device are displayed for user selection, and the target device object model is determined according to the user's selection operation.

[0008] Furthermore, it also includes a lifecycle version management process: when the device performs business data backup, a unique version number is generated based on the current business data, and then uploaded to the server. The server generates an incremental data file through version comparison and saves it.

[0009] Furthermore, the device business data replacement specifically includes: after receiving the device replacement instruction, the business data backup function of the original device is enabled by default; when the business data of the original device is updated, the business data backup is performed, and the server generates an incremental data file; after the target device is replaced, the business data is first obtained from the original device, and then the incremental data files generated during the replacement are obtained through version comparison.

[0010] In a second aspect, the present invention provides an IoT platform for in-situ replacement of devices, comprising: A physical model configuration module, configured to configure a physical model according to the function of a device, wherein the physical model includes a device table and at least two service tables, wherein the device table is used to describe a device type and a service set of the device, and the service table is used to describe a set of mutually related functional units, including a service type siid, an attribute set piids, and a function set fiids; when the service type siid is a specified value, it represents a physical service, and when the service type siid is a value other than the specified value, it represents a logical service; The object model comparison module is used to obtain the object model of the original device through the server and compare it with the object model of the target device, first determine whether the device types in the two device tables are consistent, and if they are consistent, then determine whether the values ​​of the service type siid, attribute set piids, and function set fiids in each service table of the object model of the target device contain the values ​​of the service type siid, attribute set piids, and function set fiids in each service table of the object model of the original device, and if they are, determine that the target device can replace the original device; The device replacement module is used to execute device object model file replacement and device business data replacement through the server when it is determined that the target device can replace the original device and the user's device replacement instruction is obtained; after the object model file replacement is completed, the control logic is regenerated according to the service type siid, attribute set piids and function set fiids value in the service table.

[0011] Furthermore, in the object model comparison module, the process of obtaining the object model of the original device includes: obtaining the device unique ID of the original device reported by the user end, and then obtaining the corresponding object model as the object model of the original device according to the device unique ID.

[0012] Furthermore, in the object model comparison module, after obtaining the original device object model, the original device object model is compared with the object model in the server device library, all devices that can replace the original device are displayed for user selection, and the target device object model is determined according to the user's selection operation.

[0013] Furthermore, it also includes a lifecycle version management module, which is used to generate a unique version number based on the current business data when the device performs business data backup, and then upload it to the server. The server generates and saves incremental data files through version comparison; in the device replacement module, the device business data replacement specifically includes: after receiving the device replacement instruction, the business data backup function of the original device is enabled by default; when the business data of the original device is updated, the business data backup is performed, and the server generates incremental data files; after the target device is replaced, the business data is first obtained from the original device, and then the incremental data files generated during the replacement period are obtained through version comparison.

[0014] In a third aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in the first aspect.

[0015] The technical solution provided in the embodiments of the present invention has at least the following technical effects: By defining the functions and attribute information of the products, devices of different brands and categories are abstracted into a unified conceptual model to form a standard "physical model", which makes it easier for different parties to use the same language to describe, control and understand product functions. Through the unified and standardized physical model definition, when replacing equipment, the new equipment is a different model, version, or brand of equipment. As long as the physical model comparison can include the relevant capabilities of the old equipment, it can be replaced. Physical model comparison can help users quickly find replaceable equipment and ensure that the replaced equipment has the same functions and attribute information as the original equipment. In the in-situ replacement solution for equipment, physical models play a key role and can achieve rapid replacement and smooth transition of equipment. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 It is a schematic diagram of the framework of the system of the present invention; Figure 2 is an overall flow chart of the method in Embodiment 1 of the present invention; Figure 3 This is a general architecture diagram of device replacement in a smart home application scenario in Embodiment 1 of the present invention; Figure 4 This is a schematic diagram of a device data replacement process in Embodiment 1 of the present invention; Figure 5 This is a schematic diagram of a device file replacement process in Embodiment 1 of the present invention; Figure 6 This is a schematic diagram of a file backup process in Embodiment 1 of the present invention; Figure 7 A schematic diagram of a process for selecting a device to replace in Embodiment 1 of the present invention; Figure 8 This is a schematic diagram of the verification of the equipment in-situ replacement rule in the first embodiment of the present invention; Fig. 9 This is a schematic diagram of the structure of the Internet of Things platform in Embodiment 2 of the present invention. DETAILED DESCRIPTION

[0017] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0018] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or server that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0019] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or scheme described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0020] Invention ideas The present invention designs a method for in-situ replacement of equipment, which highly abstracts the functions of the equipment. Even if the new and old equipment have different models and appearances, as long as the functions are consistent or the new equipment contains all the functions of the old equipment, the equipment is considered to be seamlessly compatible, rather than directly programming the equipment. Therefore, the replacement of the equipment can be quickly completed by simply matching the physical models of the new equipment with the old equipment. Specifically, the present invention decouples the control logic of the equipment from the physical model by defining a physical model for describing the functions of the equipment to achieve the replaceability of the equipment. When the equipment needs to be replaced, it is only necessary to delete the physical model of the old equipment in the system and add the physical model of the new equipment. The system will automatically regenerate the control logic according to the physical model of the new equipment, so that the new equipment can seamlessly replace the old equipment.

[0021] The design of the physical model takes into account the functions and attribute information of the equipment, as well as the associations and interaction methods between equipment. First, the standard equipment functions and attribute information are defined; second, the associations between equipment are modeled, such as scene control, linkage control, etc.; finally, the interaction methods between equipment are defined, such as data transmission format, communication protocol, etc.

[0022] Device: The device itself is composed of multiple services.

[0023] Service: A service represents a collection of interconnected functional units, such as physical information service, curtain service, lighting service, etc. A service includes attributes, functions, and extensions, which are used to describe the specific functions of the service.

[0024] did: The unique ID of the device itself. Each device must generate a unique ID in the specified format. Manufacturer code + device type + machine code (can be mac or SN, etc.).

[0025] Attribute piid: Generally used to describe device operation related information, such as software version number, etc. Attributes support reading, writing, reporting, etc. Function fiid: According to the upstream and downstream, it can be divided into: functions controlled by external applications and functions actively reported by the device (status feedback, event reporting). Multiple function fiids can also be combined into a function group fgiid.

[0026] Physical service siid=0: also known as device information service, mainly used to describe general device information, such as manufacturer, version, etc. If the logical service of the device is dynamically generated, the basic information of the dynamic service needs to be defined in the extended information of the physical service. A device has only one physical service.

[0027] Logical service siid=non-0: It is a general term for multiple services of a device except physical services. Specifically, it can be lighting service, curtain service, etc. Logical services can extend the definition of service classification and device binding information according to characteristics (controller / actuator).

[0028] Extension: It is an optional item in the service. The extended information is the information of some specific functions extended in the general description. Currently, the description of dynamic service information is extended in physical service, and the description of controller binding actuator is extended in logical service.

[0029] The profile definition specification of the physical model is as follows: 1. Equipment table:

[0030] ProfileId is the unique version ID of the profile for the device to interact with IOT. Once the device is released, the profile content under profileId cannot be changed. Once the content description changes, profileId will be added.

[0031] Service Table

[0032] The serviceType field in the service table represents the service type. 0x0000 is a physical service, and the others are logical services. Physical services are used to describe common device information in a service set, and logical services are used to describe other services in a service set except physical services.

[0033] The piids field in the service table represents a set of attributes, and each attribute piid is defined by the attribute table; the fiids field in the service table represents a set of attributes, and each function fiid is defined by the function table.

[0034] Attribute table

[0035] Function Table

[0036] The method of the present invention can be applied to all scenarios where an in-situ device replacement is required. However, in order to further illustrate the technical solution, the present invention will take the replacement of smart home devices as an example. Before introducing the specific embodiments, the system framework corresponding to the method of the present invention is first introduced. Figure 1 As shown, the system is roughly divided into three parts: Internet of Things platform (i.e. IOT platform, or cloud), devices and user terminals (such as mobile phones with APP installed). Both devices and user terminals are connected to the Internet of Things platform.

[0037] Embodiment 1 This embodiment provides a method for replacing a device in situ. Figure 2 Shown, incl.

[0038] S1. Physical model configuration process: physical models are configured according to the functions of the device (the physical model configuration is not limited to the devices of the same brand. Devices of different models, different versions and different brands can all be configured with corresponding physical models according to their functions). The physical model includes a device table and at least two service tables. The device table is used to describe the device type and the service set of the device. The service table is used to describe the set of mutually related functional units, including service type siid, attribute set piids and function set fiids. When the service type siid is a specified value (in this embodiment, the specified value is 0), it represents a physical service. When the service type siid is a value other than the specified value, it represents a logical service. S2. Object model comparison process: obtain the object model of the original device through the server and compare it with the object model of the target device. First, determine whether the device types in the two device tables are consistent. If they are consistent, then determine whether the values ​​of the service type siid, attribute set piids, and function set fiids in each service table of the object model of the target device contain the values ​​of the service type siid, attribute set piids, and function set fiids in each service table of the object model of the original device. If they are contained, it is determined that the target device can replace the original device (consistent with the attributes and functions of the original device, or including all the attributes and functions of the original device and there are new ones, which are considered to be included).

[0039] The following two examples further explain the comparison logic of the physical model: The service number (SIID) is inconsistent and does not meet the replacement requirements. Taking the switch panel as an example, the equipment table of a 2-way hidden switch is as follows:

[0040] The switch type lamp execution service table of 2-way hidden switch is as follows:

[0041] The equipment table for 3-way hidden switch is as follows:

[0042] It can be seen that the logical service of the 3-way hidden switch is different from that of the 2-way hidden switch, so the 3-way hidden switch cannot replace the 2-way hidden switch.

[0043] The switch type lamp execution service table of 3-way hidden switch is as follows:

[0044] It can be seen that the siid values ​​in the switch type light execution service table of the 3-way hidden switch are 2,3,4, while the siid values ​​in the switch type light execution service table of the 2-way hidden switch are 2,3, which further illustrates that their service functions are different.

[0045] The functions (fiid) are inconsistent, but they meet the replacement requirements. Taking curtains as an example, the device table of ZigBee curtain motors of manufacturer A is as follows:

[0046] The physical service table of the ZigBee curtain motor of manufacturer A is as follows:

[0047] The curtain execution service table of the ZigBee curtain motor of manufacturer A is as follows:

[0048] The device table of the ZigBee curtain motor of manufacturer B is as follows:

[0049] The curtain execution service table of the ZigBee curtain motor of manufacturer B is as follows:

[0050] Among them, although the manufacturers are different, "B" and "A", the value of piid is 0x00004. Therefore, different manufacturers are consistent after being abstracted by the object model. The object model only pays attention to whether the functions of the products are consistent, and does not pay attention to the brand, manufacturer, model, etc.

[0051] The curtain execution service table of the ZigBee curtain motor of manufacturer B is as follows:

[0052] Among them, the attribute piid in the table of manufacturer B is the same as that of manufacturer A. Although the function fiid has an additional stroke increment control (fiid=0x812A), the function fiid of manufacturer A is included in the table of manufacturer B. Therefore, although the function (fiid) of the ZigBee curtain motor of manufacturer B is inconsistent, it meets the replacement requirements.

[0053] In a possible implementation, the process of obtaining the object model of the original device includes: obtaining the device unique ID (ie, did, directDid) of the original device reported by the user end, and then obtaining the corresponding object model as the object model of the original device according to the device unique ID, such as Figure 7 shown.

[0054] Preferably, in order to facilitate users to understand which devices can be used to replace existing devices, after obtaining the original device object model, the original device object model is compared with the object model in the server device library, and all devices that can replace the original device are displayed for user selection, and the target device object model is determined based on the user's selection operation.

[0055] S3, device replacement process: when it is determined that the target device can replace the original device and the user's device replacement instruction is obtained, the device object model file replacement and device business data replacement are executed through the server; after the object model file replacement is completed, the control logic is regenerated according to the service type siid, attribute set piids and function set fiids value in the service table.

[0056] In a preferred implementation, a lifecycle version management process is also included: when the device performs business data backup, a unique version number is generated based on the current business data, and then uploaded to the server. The server generates an incremental data file through version comparison and saves it.

[0057] The device business data replacement specifically includes: after receiving the device replacement instruction, the business data backup function of the original device is enabled by default; when the business data of the original device is updated, the business data backup is performed, and the server generates an incremental data file; after the target device is replaced, the business data is first obtained from the original device, and then the incremental data file generated during the replacement is obtained through version comparison, so that the replaced device is consistent with the original device.

[0058] The overall architecture diagram of IoT platform device replacement in a smart home application scenario is as follows: Figure 3 As shown (home application, community application, operation and maintenance application, and file system are all sub-modules under the Internet of Things platform, and the Internet of Things platform can also be called IOT platform or cloud), it includes three modules: device replacement, file backup, and device replacement life cycle version control.

[0059] Device replacement: includes device data replacement and device file replacement. In a specific embodiment, firstly, the infrared configuration, attribute and attribute association configuration, scene, timing, linkage, group, arming and disarming, super model room and other functions are replaced, and then the device-related configuration (such as community business advertisements) is copied. Finally, the cloud will update the replacement status, configuration, and invalidation of the original device function, and filter out the irreplaceable attributes, and send them to the corresponding gateway. If an abnormal situation occurs, a replacement rollback operation is required. The incremental file backup part of each step will be recorded to ensure the smooth process of replacing data and parsing data. The process of device data replacement is as follows: Figure 4 As shown, it can be executed according to the following process: (1) Check whether the device can connect to the cloud.

[0060] (2) Perform cache lock judgment to ensure data integrity.

[0061] (3) Enable the rollback mechanism to restore to the previous state when necessary.

[0062] (4) Turn on the replacement and copy data switches to prepare for the device replacement operation.

[0063] (5) Determine whether the device ID can be replaced or deleted, set a timeout, and synchronize the data to the new device.

[0064] (6) Reply to the operation result. If successful, the original device will be restored to factory settings.

[0065] (7) Modify the new device to have the same functional information as the original device, report it to the cloud, and update the status of the replaced device. The process of replacing device files is as follows Figure 5 As shown, it can be executed according to the following process: (1) Click the device to be replaced, and the cloud returns a list of replaceable devices through model comparison.

[0066] (2) Select the device to be replaced and request the device to confirm whether the current status allows replacement.

[0067] (3) The cloud synchronizes the data of the old device to the new device, generates incremental files based on the business data version in the backup record of the old device, and uploads them to the file system.

[0068] (4) Notify the device to download the old device backup file and incremental file for data analysis and synchronization.

[0069] File backup: The device can choose to turn the backup function on or off. The backup function is turned on by default after the upgrade. When the configuration changes, the device will wait for half an hour by default before backing up and reporting. The device backup reporting event adopts the backup method based on functional modules. If the gateway configuration is more than the cloud, the gateway needs to be cleaned up. Here, the device backup verification of the object model is required. The directly connected device obtains the scene / timing / linkage / group / arming and disarming incremental data, device attributes / infrared configuration / advertising / super model room full data, dynamic service list and sub-device list (for device-side data comparison) through the version information in the backup record. Finally, a checklist is generated. The process can be as follows Figure 6 Device replacement version control: According to the business type segmentation, whenever the business data changes, the device is notified to change the home information. The device incrementally pulls business data through the version number and generates the corresponding backup file. When the device is replaced, if the business data on the device is inconsistent with the cloud, an incremental file is generated through version comparison. Figure 7 As shown, users can select the device to be replaced through the App. At this time, the Internet of Things platform (IOT platform) will determine whether the device is replaceable. If the user confirms the replacement after the judgment, the device will be replaced. At this time, the IOT platform will determine in real time whether the replacement has timed out and prompt the user with the replacement result. In this process, the IOT platform uses a unified and standardized object model definition. Even if the new and old devices are of different models, versions, and brands, they can be replaced as long as the object model is compared to include the relevant capabilities of the old device. In addition, the IOT platform will implement version control and backup during the replacement process, and will perform a replacement rollback operation in the event of an abnormal situation.

[0070] The rule verification principle of physical model comparison is as follows: Figure 8 As shown. Based on the in-situ replacement of the physical model, there are no restrictions on containers, software, or hardware. You only need to know the type of the original device and the physical model definition. The rule verification conditions are mainly divided into device type, service type, number of services, and functional attribute relationship. Generally speaking, the functions of the new device should include all the functions of the original device. When the functional attributes of the new device are less than those of the original device, additional verification conditions can be performed.

[0071] Device replacement includes direct-connected device replacement and sub-device replacement, which must meet certain rules and procedures to ensure data security and device stability during the device replacement process.

[0072] 1. Replacement of the same category: The two devices to be replaced must be of the same category, that is, the same software product model. This can ensure the compatibility of the new device with the old device and avoid unnecessary problems.

[0073] 2. Version upgrade reminder: When the version of the new device to be replaced is lower than that of the old device, the system will prompt the user to upgrade the new device to avoid functional deficiencies or incompatibility issues after replacement.

[0074] 3. Device addition: Both the old and new devices to be replaced must be added to the IOT platform before they can replace each other.

[0075] 4. In-situ replacement: When the old device needs to be replaced, the in-situ replacement method is adopted, that is, the new device defaults to the same node as the old device.

[0076] 5. Automatic deletion: After the device is replaced successfully, the old device will be automatically deleted. Once the old device is deleted, it is irreversible and the old device needs to be manually added back by the user.

[0077] 6. Network management: If the new device is a gateway, it needs to establish a communication network with the sub-devices and become the manager of the network. This can avoid users manually waking up low-power devices to re-network, improving user convenience.

[0078] Embodiment 2 The present invention provides an Internet of Things platform for in-situ replacement of devices, such as Fig. 9 As shown, including: A physical model configuration module, configured to configure a physical model according to the function of a device, wherein the physical model includes a device table and at least two service tables, wherein the device table is used to describe a device type and a service set of the device, and the service table is used to describe a set of mutually related functional units, including a service type siid, an attribute set piids, and a function set fiids; when the service type siid is a specified value, it represents a physical service, and when the service type siid is a value other than the specified value, it represents a logical service; The object model comparison module is used to obtain the object model of the original device through the server and compare it with the object model of the target device, first determine whether the device types in the two device tables are consistent, and if they are consistent, then determine whether the values ​​of the service type siid, attribute set piids, and function set fiids in each service table of the object model of the target device contain the values ​​of the service type siid, attribute set piids, and function set fiids in each service table of the object model of the original device, and if they are, determine that the target device can replace the original device; The device replacement module is used to execute device object model file replacement and device business data replacement through the server when it is determined that the target device can replace the original device and the user's device replacement instruction is obtained; after the object model file replacement is completed, the control logic is regenerated according to the service type siid, attribute set piids and function set fiids value in the service table.

[0079] Preferably, in the object model comparison module, the process of obtaining the object model of the original device includes: obtaining the device unique ID of the original device reported by the user end, and then obtaining the corresponding object model as the object model of the original device according to the device unique ID.

[0080] Preferably, in the object model comparison module, after obtaining the original device object model, the original device object model is compared with the object models in the server device library, all devices that can replace the original device are displayed for user selection, and the target device object model is determined according to the user's selection operation.

[0081] Preferably, it also includes a lifecycle version management module, which is used to generate a unique version number based on the current business data when the device performs business data backup, and then upload it to the server, and the server generates and saves incremental data files through version comparison; in the device replacement module, the device business data replacement specifically includes: after receiving the device replacement instruction, the business data backup function of the original device is enabled by default; when the business data of the original device is updated, the business data backup is performed, and the server generates incremental data files; after the target device is replaced, the business data is first obtained from the original device, and then the incremental data files generated during the replacement period are obtained through version comparison.

[0082] Embodiment 3 Embodiment 3 of the present invention further provides a computer storage medium on which a computer program is stored. When the computer program is executed by a computer, the computer is enabled to execute the method of the above method embodiment.

[0083] When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integration. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a solid state drive (solid state disk, SSD)), etc.

[0084] Compared with the prior art, the embodiments of the present invention can significantly improve the after-sales quality, as shown in the following table:

[0085] The present invention abstracts devices of different brands and categories into a unified conceptual model by defining the functions and attribute information of the products, forming a standard "physical model", which facilitates different parties to use the same language to describe, control and understand product functions. Through the unified and standardized physical model definition, when replacing equipment, the new equipment is a device of a different model, version, or brand. As long as the physical model is compared to include the relevant capabilities of the old equipment, it can be replaced. Physical model comparison can help users quickly find replaceable equipment and ensure that the replaced equipment has the same functions and attribute information as the original equipment. In the in-situ replacement solution of equipment, the physical model plays a key role and can achieve rapid replacement and smooth transition of equipment.

[0086] The specific implementation methods described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific implementation method of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for in-situ replacement of equipment, characterized in that: include: Physical model configuration process: according to the function of the device, the physical model is configured, the physical model includes a device table and at least two service tables, the device table is used to describe the device type and the service set of the device, the service table is used to describe the set of mutually related functional units, including service type siid, attribute set piids and function set fiids; when the service type siid is a specified value, it represents a physical service, and when the service type siid is a value other than the specified value, it represents a logical service; Object model comparison process: obtain the object model of the original device through the server and compare it with the object model of the target device. First, determine whether the device types in the two device tables are consistent. If they are consistent, then determine whether the values ​​of the service type siid, attribute set piids, and function set fiids in each service table of the object model of the target device contain the values ​​of the service type siid, attribute set piids, and function set fiids in each service table of the object model of the original device. If they are, it is determined that the target device can replace the original device. Device replacement process: When it is determined that the target device can replace the original device and the user's device replacement instruction is obtained, the device object model file replacement and device business data replacement are executed through the server; after the object model file replacement is completed, the control logic is regenerated according to the service type siid, attribute set piids and function set fiids values ​​in the service table.

2. The method according to claim 1, characterized in that: The process of obtaining the object model of the original device includes: obtaining the device unique ID of the original device reported by the user end, and then obtaining the corresponding object model as the object model of the original device according to the device unique ID.

3. The method according to claim 1 or 2, characterized in that: After the object model of the original device is obtained, the object model of the original device is compared with the object model in the server device library, and all devices that can replace the original device are displayed for user selection, and the object model of the target device is determined based on the user's selection operation.

4. The method according to claim 1, characterized in that: It also includes the lifecycle version management process: when the device performs business data backup, a unique version number is generated based on the current business data, and then uploaded to the server. The server generates an incremental data file through version comparison and saves it.

5. The method according to claim 4, characterized in that: The device business data replacement specifically includes: after receiving the device replacement instruction, the business data backup function of the original device is enabled by default; when the business data of the original device is updated, the business data backup is performed, and the server generates an incremental data file; after the target device is replaced, the business data is first obtained from the original device, and then the incremental data file generated during the replacement is obtained through version comparison.

6. An IoT platform for in-situ device replacement, characterized in that: include: A physical model configuration module, configured to configure a physical model according to the function of a device, wherein the physical model includes a device table and at least two service tables, wherein the device table is used to describe a device type and a service set of the device, and the service table is used to describe a set of mutually related functional units, including a service type siid, an attribute set piids, and a function set fiids; when the service type siid is a specified value, it represents a physical service, and when the service type siid is a value other than the specified value, it represents a logical service; The object model comparison module is used to obtain the object model of the original device through the server and compare it with the object model of the target device, first determine whether the device types in the two device tables are consistent, and if they are consistent, then determine whether the values ​​of the service type siid, attribute set piids, and function set fiids in each service table of the object model of the target device contain the values ​​of the service type siid, attribute set piids, and function set fiids in each service table of the object model of the original device, and if they are, determine that the target device can replace the original device; The device replacement module is used to execute device object model file replacement and device business data replacement through the server when it is determined that the target device can replace the original device and the user's device replacement instruction is obtained; after the object model file replacement is completed, the control logic is regenerated according to the service type siid, attribute set piids and function set fiids value in the service table.

7. The Internet of Things platform according to claim 6, characterized in that: In the object model comparison module, the process of obtaining the original device object model includes: obtaining the device unique ID of the original device reported by the user end, and then obtaining the corresponding object model as the original device object model according to the device unique ID.

8. The Internet of Things platform according to claim 6 or 7, characterized in that: In the object model comparison module, after obtaining the object model of the original device, the object model of the original device is compared with the object models in the server device library, all devices that can replace the original device are displayed for user selection, and the target device object model is determined according to the user's selection operation.

9. The Internet of Things platform according to claim 6, characterized in that: It also includes a lifecycle version management module, which is used to generate a unique version number based on the current business data when the device performs business data backup, and then upload it to the server. The server generates and saves the incremental data file through version comparison; In the device replacement module, the device business data replacement specifically includes: after receiving the device replacement instruction, the business data backup function of the original device is enabled by default; when the business data of the original device is updated, the business data backup is performed, and the server generates an incremental data file; after the target device is replaced, the business data is first obtained from the original device, and then the incremental data files generated during the replacement are obtained through version comparison.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images