A method for replacing a device in situ, an internet of things platform and a medium

Abstract

The application discloses a kind of equipment in situ replacement method, internet of things platform and medium, it is related to equipment replacement technical field.The equipment function is highly abstracted, even if new and old equipment model is different, appearance is different, as long as function is consistent or new equipment contains all functions of old equipment, it is considered that the equipment can be seamlessly compatible, and not directly programming to equipment.Only need to match the new equipment with the old equipment thing model, the replacement of equipment can be quickly completed.The application defines the thing model for describing the function of the equipment, decouples the control logic of the equipment from the thing model to achieve the replaceability of the equipment.When the equipment needs to be replaced, only need to delete the thing model of the old equipment in the system and add the thing model of the new equipment, the system will automatically regenerate the control logic according to the thing model of the new equipment, so that the new equipment can seamlessly replace the old equipment.The application can realize the in situ replacement of different models, different versions and different brands of equipment.

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 market promotion in recent years and the significant increase in device shipments, it is inevitable that devices will fail and need to be replaced during long-term use. Device replacement is a common service in after-sales support. However, during the replacement process, the following situations often occur, resulting in a poor after-sales support experience and even customer complaints. These are mainly reflected in:

[0003] 1. After users replace their devices, many of the original functions cannot be used normally and require a lot of configuration, which takes a long time.

[0004] 2. The device used by the user is an old model that the company has stopped producing. 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 functions not being able to be used normally and facing complaints. Summary of the Invention

[0005] 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 one only requires replacing the physical model and regenerating the control logic, thereby realizing in-situ replacement of equipment of different models, versions and brands.

[0006] In a first aspect, the present invention provides a method for in-situ replacement of a device, comprising:

[0007] Physical model configuration process: The physical model is configured according to the functions of the device. 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 interconnected functional units, including the service type siid, the attribute set piids, and the function set fiids. When the service type siid is a specified value, it represents a physical service. When the service type siid is a value other than the specified value, it represents a logical service.

[0008] Object model comparison process: The original device object model is obtained from the server and compared with the target device object model. First, the device types in the two device tables are determined to be consistent. If they are consistent, the service type siid, attribute set piids, and function set fiids values ​​in each service table of the target device object model are determined to contain the service type siid, attribute set piids, and function set fiids values ​​in each service table of the original device object model. If they are, it is determined that the target device can replace the original device.

[0009] 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.

[0010] Furthermore, 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 terminal, and then obtaining the corresponding object model as the object model of the original device according to the device unique ID.

[0011] Furthermore, 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, 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.

[0012] 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.

[0013] Furthermore, the device business data replacement specifically includes: after receiving the device replacement instruction, the business data backup function of the original device is turned on 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 period is obtained through version comparison.

[0014] In a second aspect, the present invention provides an IoT platform for in-situ device replacement, comprising:

[0015] A physical model configuration module configured to configure a physical model based on the functions of a device, the physical model comprising 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 a set of interconnected 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. When the service type siid is a value other than the specified value, it represents a logical service.

[0016] 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. It first determines whether the device types in the two device tables are consistent. If they are consistent, it then determines 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 do, it is determined that the target device can replace the original device.

[0017] The device replacement module is used to execute the 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 values ​​in the service table.

[0018] Furthermore, 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 terminal, and then obtaining the corresponding object model as the original device object model according to the device unique ID.

[0019] Furthermore, 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, 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.

[0020] 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 turned on 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.

[0021] 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.

[0022] The technical solutions provided in the embodiments of the present invention have at least the following technical effects:

[0023] By defining the functions and attribute information of products, devices of different brands and categories are abstracted into a unified conceptual model, forming a standard "physical model" that 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, even if the new equipment is of a different model, version, or brand, it can be replaced as long as the physical model comparison can include the relevant capabilities of the old equipment. 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, enabling rapid replacement and smooth transition of equipment. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 Schematic diagram of the framework of the system of the present invention;

[0025] Figure 2 is an overall flow chart of the method in embodiment 1 of the present invention;

[0026] Figure 3 This is a diagram showing the overall architecture of device replacement in a smart home application scenario according to the first embodiment of the present invention;

[0027] Figure 4 Schematic diagram of the device data replacement process in Embodiment 1 of the present invention;

[0028] Figure 5 Schematic diagram of the device file replacement process in the first embodiment of the present invention;

[0029] Figure 6 This is a schematic diagram of a file backup process in Embodiment 1 of the present invention;

[0030] Figure 7 This is a schematic diagram of the process of selecting a device for replacement in the first embodiment of the present invention;

[0031] Figure 8 This is a schematic diagram of the device in-situ replacement rule verification in Example 1 of the present invention;

[0032] Figure 9 This is a schematic diagram of the structure of the Internet of Things platform in Example 2 of the present invention. DETAILED DESCRIPTION

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

[0034] It should be noted that the terms "first", "second", etc. in the specification and claims of this 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 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 variations thereof 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.

[0035] 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 solution 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 solutions. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0036] Invention ideas

[0037] The present invention designs a method for in-situ replacement of equipment, which highly abstracts the functions of the equipment. Even if the old and new equipment are of 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 being programmed directly for the equipment. Therefore, it is only necessary to match the physical models of the new and old equipment to quickly complete the replacement of the 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 based on the physical model of the new equipment, so that the new equipment can seamlessly replace the old equipment.

[0038] The design of the object model takes into account the functions and attributes of devices, as well as the relationships and interactions between devices. First, standard device functions and attributes are defined. Second, the relationships between devices are modeled, such as scenario control and linkage control. Finally, the interaction methods between devices are defined, such as data transmission formats and communication protocols.

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

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

[0041] DID: The unique ID of the device. Each device must generate a unique ID according to the specified format. Manufacturer code + device type + machine code (can be MAC or SN, etc.).

[0042] Attribute piid: Generally used to describe device operation related information, such as software version number, etc. Attributes support reading, writing, reporting, etc.

[0043] Function FIID: Based on upstream and downstream functions, 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.

[0044] Physical service siid=0: This is also known as the device information service, which primarily describes general device information, such as manufacturer and version. If the device's logical service is dynamically generated, the basic information for the dynamic service must be defined in the extended information of the physical service. A device has only one physical service.

[0045] Logical service siid = non-zero: This collectively refers to a device's multiple services, excluding physical services. Specifically, this could be a lighting service, curtain service, etc. Logical services can be expanded to define service categories and device binding information based on their characteristics (controller / actuator).

[0046] Extensions are optional in services. Extended information extends the general description with specific functionality. Currently, physical services extend the description of dynamic service information, and logical services extend the description of controller-bound actuators.

[0047] The profile definition specification of the physical model is as follows:

[0048] 1. Equipment table:

[0049]

[0050] ProfileId is the unique version ID of the profile used by the device to interact with the IoT. Once a device is published, the profile content associated with ProfileId remains unchanged. If the content description changes, a new ProfileId is added.

[0051] Service Table

[0052] 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.

[0053] 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.

[0054] Property Table

[0055] Function Table

[0056] The method of the present invention can be applied to all scenarios where devices need to be replaced in situ. 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 embodiment of the present invention is first introduced. Figure 1 As shown in the figure, the system is roughly divided into three parts: the Internet of Things platform (also known as the IOT platform, or the cloud), devices, and user terminals (such as mobile phones with APPs installed). Both devices and user terminals are connected to the Internet of Things platform.

[0057] Example 1

[0058] This embodiment provides a method for replacing a device in situ, such as Figure 2 Shown, incl.

[0059] S1. Object model configuration process: Configure an object model based on the device's functions (the configuration of an object model is not limited to devices of the same brand; devices of different models, versions, and brands can all be configured with corresponding object models based on their functions). The object 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 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 (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.

[0060] 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 included, it is determined that the target device can replace the original device (if the attributes and functions are consistent with the original device, or include all the attributes and functions of the original device and there are new ones, they are all considered included).

[0061] The following two examples further illustrate the comparison logic of the physical model:

[0062] The service number (SIID) is inconsistent and does not meet the replacement requirements. Taking the switch panel as an example, the device table of a 2-way hidden switch is as follows:

[0063]

[0064] The service table for switch lights of 2-way hidden switches is as follows:

[0065]

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

[0067]

[0068] 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.

[0069] The service table for switch lights of 3-way hidden switches is as follows:

[0070]

[0071] 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, and 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.

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

[0073]

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

[0075]

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

[0077]

[0078] The device table of manufacturer B's ZigBee curtain motor is as follows:

[0079]

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

[0081]

[0082] Among them, although the manufacturers are "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 focuses on whether the functions of the products are consistent, and does not pay attention to the brand, manufacturer, model, etc.

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

[0084]

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

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

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

[0088] 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 values ​​in the service table.

[0089] 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.

[0090] The device business data replacement specifically includes: after receiving the device replacement instruction, the business data backup function of the original device is turned on 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 period is obtained through version comparison, so that the replaced device is consistent with the original device.

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

[0092] 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 failure of the original device function, and filter 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 that the replacement data parsing process is smooth. The process of device data replacement is as follows Figure 4 As shown, it can be executed according to the following process:

[0093] (1) Check whether the device can connect to the cloud.

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

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

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

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

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

[0099] (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.

[0100] The process of replacing device files is as follows Figure 5 As shown, it can be executed according to the following process:

[0101] (1) Click the device to be replaced, and the cloud will return a list of replaceable devices through model comparison.

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

[0103] (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.

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

[0105] File backup: The device can choose to turn on or off the backup function. 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 according to the functional module. 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 properties / infrared configuration / advertisement / 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, and finally generates a checklist. The process can be as follows Figure 6Device replacement version control: Based on the business type, whenever the business data changes, the device is notified to change the home information. The device pulls the business data incrementally 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. The Internet of Things (IoT) platform then determines whether the device is replaceable. If the user confirms the replacement, the device replacement begins. The IoT platform then determines in real time whether the replacement has timed out and notifies the user of the replacement result. During this process, the IoT platform uses a standardized object model definition. Even if the old and new devices are different models, versions, or brands, the replacement can be performed as long as the object model comparison can include the relevant capabilities of the old device. The IoT platform also implements version control and backups during the replacement process, and performs a rollback in the event of anomalies.

[0106] The rule verification principle of physical model comparison is as follows Figure 8 As shown in the figure, in-situ replacement based on the physical model is not restricted by containers, software, or hardware. Only the type of the original device and the physical model definition are required. Rule verification conditions are mainly categorized by device type, service type, number of services, and functional attribute relationships. Generally speaking, the new device's functions should include all those of the original device. When the new device's functional attributes are fewer than those of the original device, additional verification conditions can be applied.

[0107] Device replacement includes direct-connect device replacement and sub-device replacement, and must comply with certain rules and procedures to ensure data security and device stability during the device replacement process.

[0108] 1. Same-category replacement: The two devices to be replaced must be of the same category, that is, the same software product model. This ensures compatibility between the new and old devices and avoids unnecessary problems.

[0109] 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 problems or incompatibility issues after replacement.

[0110] 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.

[0111] 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.

[0112] 5. Automatic deletion: After the device is successfully replaced, the old device will be automatically deleted. Once the old device is deleted, it cannot be reversed and the old device must be manually added back by the user.

[0113] 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.

[0114] Example 2

[0115] The present invention provides an IoT platform for in-situ device replacement, such as Figure 9 Shown, including:

[0116] A physical model configuration module configured to configure a physical model based on the functions of a device, the physical model comprising 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 a set of interconnected 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. When the service type siid is a value other than the specified value, it represents a logical service.

[0117] 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. It first determines whether the device types in the two device tables are consistent. If they are consistent, it then determines 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 do, it is determined that the target device can replace the original device.

[0118] The device replacement module is used to execute the 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 values ​​in the service table.

[0119] Preferably, 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 terminal, and then obtaining the corresponding object model as the original device object model according to the device unique ID.

[0120] 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 based on the user's selection operation.

[0121] 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. 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 turned on 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.

[0122] Example 3

[0123] The third embodiment 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 perform the method of the above method embodiment.

[0124] 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 device. 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 one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. 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 integrated. 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 (DVD)), or a semiconductor medium (e.g., a solid state drive (SSD)).

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

[0126]

[0127] 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" to facilitate 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 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, enabling rapid replacement and smooth transition of equipment.

[0128] 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: The physical model is configured according to the functions of the device. 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 interconnected functional units, including the service type siid, the attribute set piids, and the function set fiids. When the service type siid is a specified value, it represents a physical service. When the service type siid is a value other than the specified value, it represents a logical service. Object model comparison process: The original device object model is obtained from the server and compared with the target device object model. First, the device types in the two device tables are determined to be consistent. If they are consistent, the service type siid, attribute set piids, and function set fiids values ​​in each service table of the target device object model are determined to contain the service type siid, attribute set piids, and function set fiids values ​​in each service table of the original device object model. 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, wherein: 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 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, and all devices that can replace the original device are displayed for user selection. The target device object model is determined based on the user's selection operation.

4. The method according to claim 1, wherein: 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 turned on 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 period 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 based on the functions of a device, the physical model comprising 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 a set of interconnected 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. 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. It first determines whether the device types in the two device tables are consistent. If they are consistent, it then determines 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 do, it is determined that the target device can replace the original device. The device replacement module is used to execute the 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 values ​​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 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 based on 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 turned on 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 period is 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