Intelligent fusion terminal multi-model multi-device adaptive registration method and system

Abstract

This invention provides a method and system for adaptive registration of multiple models and multiple devices for intelligent converged terminals, comprising: the intelligent converged terminal retrieving a configuration file in a file system based on a target file name; when a configuration file is found, reading the original content of the file from the configuration file; parsing the original content of the file to obtain multiple model data and device data associated with each model data; initiating a registration operation for each model data with a data center based on each model data; matching each device data with its associated model data to generate an association matching relationship; and initiating a registration operation for each device data with the data center based on the association matching relationship. This invention can adapt to multi-model and multi-device business scenarios, achieve adaptive and efficient registration of multiple models and multiple devices, and optimize the integrity of the registration process, enhancing the convenience, stability, and operational reliability of intelligent converged terminal registration services.

Description

Technical Field

[0001] This invention relates to the field of smart terminal data registration technology, specifically to a method and system for adaptive registration of multiple models and multiple devices in a smart fusion terminal. Background Technology

[0002] In the rapidly developing application scenarios of the intelligent converged terminal industry, terminals need to simultaneously access multiple business models and multiple terminal devices under each model. Unified registration and centralized management of multiple models and devices is the basic prerequisite for ensuring the coordinated operation of devices and the normal collection and transmission of data.

[0003] Existing traditional registration methods only support a single-model, multi-device registration architecture, which cannot adapt to the current business needs of multi-model parallel deployment. If multiple types of model data are forcibly integrated into a single model for device data collection, crosstalk between different model data is likely to occur, significantly reducing the data collection rate and causing devices with small data volumes to fail to collect data. At the same time, the existing registration process relies heavily on manual input of model and device information and manual binding of model-device associations, which is not only inefficient but also prone to matching errors. Furthermore, the lack of a model registration duplication verification mechanism can easily lead to redundant registration data and increase the load on the data center. In addition, the lack of a robust process exception handling mechanism makes the registration process prone to lag, abnormal suspension, and inability to terminate normally, making it difficult to meet the actual application requirements of large-scale, automated, and multi-model parallel registration for intelligent converged terminals. Summary of the Invention

[0004] To address the problems in existing technologies where intelligent fusion terminals only support single-model registration, failing to adapt to multi-model and multi-device registration scenarios, and prone to duplicate registrations and inaccurate device-model matching, resulting in incomplete registration processes, frequent freezes, and inability to terminate normally, this invention proposes an adaptive multi-model and multi-device registration method for intelligent fusion terminals, comprising:

[0005] The intelligent fusion terminal retrieves the configuration file in the file system based on the target file name, and when the configuration file is found, reads the original content of the file from the configuration file;

[0006] The original content of the file is parsed to obtain multiple model data and device data associated with each model data;

[0007] Based on the data from each model, a registration operation for the data from each model is initiated with the data center;

[0008] Match the data of each device with its associated model data to generate a matching relationship;

[0009] Based on the association and matching relationship, a registration operation for the data of each device is initiated with the data center.

[0010] Optionally, the step of initiating a registration operation for each model data with the data center based on each model data includes:

[0011] Iterate through the data of each model and compare it with the data center to see if the model data already exists.

[0012] If the model data already exists, skip this registration operation;

[0013] Otherwise, the registration interface of the data center is invoked to register the model data.

[0014] Optionally, the step of matching each device's data with its associated model data to generate an association matching relationship includes:

[0015] Based on the preset association mapping rules in the configuration file, each piece of device data is matched to the corresponding model data;

[0016] The matching results are integrated to obtain the correlation and matching relationship between the device data and the model data.

[0017] Optionally, the model data includes one or more of the following: model identifier, model name, and model definition;

[0018] The device data includes one or more of the following: device name, device identifier, device type, device communication parameters, and device communication address.

[0019] Optionally, the step of initiating a registration operation for the data of each device with the data center based on the association matching relationship includes:

[0020] The association matching relationship is traversed, and the device registration interface of the data center is called in turn to complete the registration operation of each device data.

[0021] Optionally, after initiating the registration operation for the data of each device with the data center based on the association matching relationship, the method further includes:

[0022] Receive the device registration result returned by the data center;

[0023] If registration is successful, the registration status of the device data is recorded as "registered".

[0024] If registration fails, the device registration interface of the data center will be called again. If it still fails after a preset number of retries, the registration of the device data will be terminated.

[0025] Optionally, the adaptive registration method further includes:

[0026] When the intelligent fusion terminal searches for the configuration file in the file system based on the target file name, if the corresponding configuration file is not found, it exits the registration process.

[0027] Optionally, the configuration file is a structured file in a preset format;

[0028] The preset format includes either JSON or XML format.

[0029] Based on the same inventive concept, this invention also provides an intelligent fusion terminal multi-model multi-device adaptive registration system, comprising:

[0030] The file retrieval module is used to retrieve configuration files in the file system based on the target file name through the intelligent fusion terminal. When a configuration file is retrieved, the original content of the file is read from the configuration file.

[0031] The file parsing module is used to parse the original content of the file to obtain multiple model data and device data associated with each model data.

[0032] The model registration module is used to initiate a registration operation for each model data with the data center based on the model data.

[0033] The device matching module is used to match the data of each device with its associated model data to generate a matching relationship.

[0034] The device registration module is used to initiate a registration operation for the data of each device with the data center based on the association matching relationship.

[0035] Optionally, the model registration module includes:

[0036] The model comparison submodule is used to traverse each model data and compare it with the data center to see if the model data already exists.

[0037] The registration judgment submodule is used to skip the current registration operation if the model data already exists; otherwise, it calls the registration interface of the data center to perform the registration operation on the model data.

[0038] Optionally, the device matching module includes:

[0039] The association mapping submodule is used to match each piece of device data to the corresponding model data based on the association mapping rules preset in the configuration file;

[0040] The data integration submodule is used to integrate the matching results and obtain the association and matching relationship between the device data and the model data.

[0041] Optionally, the model data includes one or more of the following: model identifier, model name, and model definition;

[0042] The device data includes one or more of the following: device name, device identifier, device type, device communication parameters, and device communication address.

[0043] Optionally, the device registration module is specifically used for:

[0044] The association matching relationship is traversed, and the device registration interface of the data center is called in turn to complete the registration operation of each device data.

[0045] Optionally, the adaptive registration system further includes: a registration verification module, comprising:

[0046] The result receiving submodule is used to receive the device registration results returned by the data center;

[0047] The result verification submodule is used to record the registration status of the device data as "registered" when registration is successful; if registration fails, it calls the device registration interface of the data center again, and if it still fails after a preset number of retries, it terminates the registration of the device data.

[0048] Optionally, the adaptive registration system further includes a registration exit module, specifically used for:

[0049] When the intelligent fusion terminal searches for the configuration file in the file system based on the target file name, if the corresponding configuration file is not found, it exits the registration process.

[0050] Optionally, the configuration file is a structured file in a preset format;

[0051] The preset format includes either JSON or XML format.

[0052] In another aspect, the present invention also provides an electronic device, comprising: at least one processor and a memory; the memory and the processor are connected via a bus;

[0053] The memory is used to store one or more programs;

[0054] When the one or more programs are executed by the at least one processor, the aforementioned intelligent fusion terminal multi-model multi-device adaptive registration method is implemented.

[0055] In another aspect, the present invention also provides a computer device readable storage medium having an executable program stored thereon, wherein when the executable program is executed, it implements the aforementioned intelligent fusion terminal multi-model multi-device adaptive registration method.

[0056] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0057] This invention provides a method and system for adaptive registration of multiple models and multiple devices in an intelligent fusion terminal, comprising: the intelligent fusion terminal retrieving a configuration file in a file system based on a target file name; when a configuration file is found, reading the original content of the file from the configuration file; parsing the original content of the file to obtain multiple model data and device data associated with each model data; initiating a registration operation for each model data to a data center based on each model data; matching each device data with its associated model data to generate an association matching relationship; and initiating a registration operation for each device data to the data center based on the association matching relationship. This invention, through the intelligent fusion terminal's automatic retrieval, reading, and parsing of configuration files in a preset format, enables automatic extraction of multiple model data and corresponding device data, eliminating the need for manual data entry and improving the registration efficiency of multiple models and multiple devices. By storing the model data... By comparing data against existing models and skipping duplicate registrations of already registered models, redundant interactions in the data center are reduced, thus lowering system resource consumption. Matching device data with corresponding model data based on the association between models and devices avoids errors caused by manual matching, ensuring accurate association between multiple models and multiple devices. Compared to the traditional single-model, multi-device registration mode, this invention adopts a multi-model, multi-device registration method. This allows for flexible configuration of downlink devices for a single application to collect multiple models, no longer limited to single-model application scenarios. It enables dynamic selection of the required device models and corresponding downlink devices using configuration files, supporting on-demand selection of device instances from multiple models. Devices can be flexibly combined according to region, type, and business needs to meet data aggregation requirements in complex scenarios. Ultimately, this achieves adaptive, efficient, and accurate registration of multiple models and devices, significantly improving the convenience, stability, and reliability of multi-device, multi-model registration for intelligent fusion terminals. Attached Figure Description

[0058] Figure 1 A flowchart illustrating a multi-model, multi-device adaptive registration method for an intelligent fusion terminal provided by the present invention;

[0059] Figure 2 This invention provides a schematic diagram of the structural composition of an intelligent fusion terminal multi-model multi-device adaptive registration system.

[0060] Figure 3 This is a schematic diagram of the structure of an electronic device provided by the present invention. Detailed Implementation

[0061] This invention proposes a method, system, device, and medium for adaptive registration of multiple models and devices in an intelligent fusion terminal. The specific embodiments of this invention will be further described in detail below with reference to the accompanying drawings.

[0062] Example 1:

[0063] This invention provides a method for adaptive registration of multiple models and multiple devices in an intelligent fusion terminal, as illustrated in the flowchart below. Figure 1 As shown, it includes:

[0064] Step 1: The intelligent fusion terminal searches for the configuration file in the file system based on the target file name. When the configuration file is found, the original content of the file is read from the configuration file.

[0065] Step 2: Parse the original content of the file to obtain multiple model data and device data associated with each model data;

[0066] Step 3: Based on the data of each model, initiate a registration operation for the data of each model with the data center;

[0067] Step 4: Match the data of each device with its associated model data to generate association matching relationships;

[0068] Step 5: Based on the association and matching relationship, initiate a registration operation for the data of each device in the data center.

[0069] In one implementation, step 1 above may further include:

[0070] When the intelligent converged terminal searches for the configuration file in the file system based on the target file name, if the corresponding configuration file is not found, it exits the registration process.

[0071] When searching for configuration files in the file system, you can search based on the file address of the configuration file. If the configuration file corresponding to the file address can be found, then the configuration file is read; otherwise, the process exits.

[0072] For example, the configuration file can be a structured file in a preset format;

[0073] The preset format may include: JSON format or XML format; in addition to JSON and XML, the preset format may also include: YAML format, INI format, and Properties format;

[0074] In this implementation, the retrieval logic is clear and explicit by searching for the configuration file according to the target file name and file address. At the same time, an exception handling mechanism is added to directly exit the registration process when the configuration file is not found, which can avoid the terminal from executing an invalid registration process and reduce the consumption of useless computing resources.

[0075] In one implementation, when parsing the original content of the file in step 2 above, the target configuration file is opened, the number of models and the data of each model in the file are extracted according to preset keywords, and the device data corresponding to each model is extracted according to different model categories.

[0076] For example, the model data mentioned above may include one or more of the following: model identifier, model name, and model definition;

[0077] The device data may include one or more of the following: device name, device identifier, device type, device communication parameters, and device communication address;

[0078] In this implementation, by parsing the configuration file content based on preset keywords, the number of models and data for each model can be accurately extracted, and the corresponding device data can be extracted independently according to model classification. The parsing logic is well-organized and the data extraction is highly targeted. At the same time, the specific constituent fields of model data and device data are clearly defined, which can standardize the data extraction scope, avoid interference from redundant information, improve file parsing efficiency and data extraction accuracy, and provide complete and standardized structured basic data for subsequent model registration and device-model association matching, ensuring the smooth and orderly progress of the overall adaptive registration process.

[0079] In one implementation, step 3 above, which involves initiating a registration operation for each model data with the data center, may include:

[0080] Iterate through the data of each model and compare it with the data center to see if the model data already exists.

[0081] If the model data already exists, skip this registration operation;

[0082] Otherwise, the registration interface of the data center is called to register the model data;

[0083] In this implementation, by traversing all model data and performing an existence comparison with the data center in advance, it is possible to identify model data that has already been registered and directly skip the registration process. Registration is only called on unregistered model data to complete the registration. This effectively avoids repeatedly initiating invalid registration requests, reduces unnecessary network interactions between the terminal and the data center, thereby saving communication resources and system computing overhead. At the same time, it can prevent redundant and duplicate model data from being generated in the data center, which is conducive to ensuring the uniqueness and regularity of model data in the data center.

[0084] In one implementation, step 4 above, which involves matching the data of each device with its associated model data to generate the association matching relationship, may include:

[0085] Based on the preset association mapping rules in the configuration file, each piece of device data is matched to the corresponding model data;

[0086] The matching results are integrated to obtain the association and matching relationship between the device data and the model data;

[0087] In this implementation, the matching of device data and corresponding model data is automatically completed by relying on the preset association mapping rules in the configuration file. There is no need for manual association binding, which can save the workload of manual configuration and avoid the association disorder caused by human matching errors. By uniformly integrating the matching results to form a standardized association matching relationship, the ownership relationship between devices and models can be clear and the correspondence can be well defined.

[0088] In one implementation, step 5 above, which involves initiating a registration operation for the data of each device with the data center based on the association matching relationship, may include:

[0089] Traverse the association and matching relationships, and sequentially call the device registration interface of the data center to complete the registration operation of each device data;

[0090] In this implementation, by matching device data with registered models based on model names, a device-model binding relationship with attached device communication parameter configuration is established, which can standardize the dimensions of associated configuration information. Based on the established association matching relationship, the data center device registration interface is called sequentially to complete batch registration. The registration process is promoted in an orderly manner by relying on the standardized binding relationship, which saves the tedious operation of manually configuring and initiating registration one by one. This is conducive to improving the efficiency of batch device registration and ensuring the accuracy of the binding relationship between devices and corresponding models.

[0091] In one implementation, after initiating the registration operation for the data of each device with the data center based on the association matching relationship, it may further include:

[0092] Receive the device registration result returned by the data center;

[0093] If registration is successful, the registration status of the device data is recorded as "registered".

[0094] If registration fails, the device registration interface of the data center will be called again. If it still fails after a preset number of retries, the registration of the device data will be terminated.

[0095] In this implementation, by receiving device registration results from the data center in real time, the registration status of successfully registered devices can be stored. For devices that fail to register, an interface retry request is automatically initiated, which can effectively avoid registration failures caused by accidental factors such as network fluctuations, thus improving the overall device registration success rate. At the same time, a preset limit on the number of retry attempts is set, and the registration process of the corresponding device is terminated in a timely manner after the limit is reached. This can prevent invalid and repeated requests from occupying network bandwidth and system resources for a long time, and will not drag down the overall batch registration process of multiple devices due to registration failure of a single device.

[0096] In summary, this invention addresses the problems of existing intelligent fusion terminals that only support single-model registration, failing to adapt to multi-model and multi-device registration scenarios, and prone to duplicate registrations and inaccurate device-model matching, resulting in incomplete registration processes, frequent freezes, and inability to terminate normally. It proposes an adaptive multi-model and multi-device registration method for intelligent fusion terminals. This method automatically retrieves and reads configuration files, accurately parses and extracts model and device data, and automatically associates and matches devices and models based on pre-configured mapping rules. Simultaneously, it incorporates registration result status recording, failure retry, and termination mechanisms to overcome the limitations of traditional single-model registration. This reduces the workload and human error associated with manual data entry and matching, ensuring the accuracy of device and model matching and association. Ultimately, it enables fully automated closed-loop operation of multi-model and multi-device registration, improving overall registration efficiency and process stability.

[0097] Example 2:

[0098] Based on the same inventive concept, this invention also provides an intelligent fusion terminal multi-model multi-device adaptive registration system, the structural composition of which is shown in the schematic diagram below. Figure 2 As shown, it includes:

[0099] The file retrieval module is used to retrieve configuration files in the file system based on the target file name through the intelligent fusion terminal. When a configuration file is retrieved, the original content of the file is read from the configuration file.

[0100] The file parsing module is used to parse the original content of the file to obtain multiple model data and device data associated with each model data.

[0101] The model registration module is used to initiate a registration operation for each model data with the data center based on the model data.

[0102] The device matching module is used to match the data of each device with its associated model data to generate a matching relationship.

[0103] The device registration module is used to initiate a registration operation for the data of each device with the data center based on the association matching relationship.

[0104] In one implementation, the model registration module may include:

[0105] The model comparison submodule is used to traverse each model data and compare it with the data center to see if the model data already exists.

[0106] The registration judgment submodule is used to skip the current registration operation if the model data already exists; otherwise, it calls the registration interface of the data center to perform the registration operation on the model data.

[0107] In one implementation, the device matching module may include:

[0108] The association mapping submodule is used to match each piece of device data to the corresponding model data based on the association mapping rules preset in the configuration file;

[0109] The data integration submodule is used to integrate the matching results and obtain the association and matching relationship between the device data and the model data.

[0110] For example, the model data may include one or more of the following: model identifier, model name, and model definition;

[0111] The device data may include one or more of the following: device name, device identifier, device type, device communication parameters, and device communication address.

[0112] In one implementation, the device registration module can specifically be used for:

[0113] The association matching relationship is traversed, and the device registration interface of the data center is called in turn to complete the registration operation of each device data.

[0114] In one implementation, the adaptive registration system may further include: a registration verification module, comprising:

[0115] The result receiving submodule is used to receive the device registration results returned by the data center;

[0116] The result verification submodule is used to record the registration status of the device data as "registered" when registration is successful; if registration fails, it calls the device registration interface of the data center again, and if it still fails after a preset number of retries, it terminates the registration of the device data.

[0117] In one implementation, the adaptive registration system may further include: a registration exit module, specifically used for:

[0118] When the intelligent fusion terminal searches for the configuration file in the file system based on the target file name, if the corresponding configuration file is not found, it exits the registration process.

[0119] For example, the configuration file can be a structured file in a preset format;

[0120] The preset format may include JSON format or XML format.

[0121] Example 3:

[0122] like Figure 3 As shown, the present invention also provides an electronic device, which may be a computer device, a microcontroller device, a smart mobile device, etc. The electronic device in this embodiment may include a processor, a memory, a transceiver component, etc. The memory, processor, and transceiver component are connected via a bus; the memory can be used to store executable programs, and an exemplary executable program may include instructions; the processor is used to execute the instructions stored in the memory. The memory can also be used to store data, which can be accessed and / or modified when instructions are executed.

[0123] The processor may be a Central Processing Unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. It is the computing and control core of the terminal, and it is suitable for implementing one or more instructions. Specifically, it is suitable for loading and executing one or more instructions in the storage medium to realize the corresponding method flow or corresponding function, so as to realize the steps of the intelligent fusion terminal multi-model multi-device adaptive registration method in the above embodiments.

[0124] Example 4:

[0125] Based on the same inventive concept, this invention also provides a readable storage medium, specifically an electronic device readable storage medium (Memory). This readable storage medium is a memory device within an electronic device used to store programs and data. It is understood that the storage medium here can include both built-in storage media within the electronic device and extended storage media supported by the electronic device. The storage medium provides storage space, which stores the terminal's operating system. Furthermore, this storage space also stores one or more instructions suitable for loading and execution by a processor. These instructions can be one or more executable programs (including program code). It should be noted that the storage medium here can be high-speed RAM or non-volatile memory, such as at least one disk storage device. Loading and executing one or more instructions stored in the storage medium by the processor can implement the steps of the intelligent fusion terminal multi-model multi-device adaptive registration method described in the above embodiments.

[0126] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0127] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0128] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1The function specified in one or more boxes.

[0129] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0130] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit its protection scope. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that after reading the present invention, they can still make various changes, modifications or equivalent substitutions to the specific implementation of the present application, but these changes, modifications or equivalent substitutions are all within the protection scope of the claims of the present application.

Claims

1. A method for adaptive registration of multiple models and multiple devices in an intelligent fusion terminal, characterized in that, include: The intelligent fusion terminal retrieves the configuration file in the file system based on the target file name, and when the configuration file is found, reads the original content of the file from the configuration file; The original content of the file is parsed to obtain multiple model data and device data associated with each model data; Based on the data from each model, a registration operation for the data from each model is initiated with the data center; Match the data of each device with its associated model data to generate a matching relationship; Based on the association and matching relationship, a registration operation for the data of each device is initiated with the data center.

2. The method as described in claim 1, characterized in that, The step of initiating a registration operation for each model's data with the data center based on that model data includes: Iterate through the data of each model and compare it with the data center to see if the model data already exists. If the model data already exists, skip this registration operation; Otherwise, the registration interface of the data center is invoked to register the model data.

3. The method as described in claim 1, characterized in that, The step of matching each device's data with its associated model data to generate a matching relationship includes: Based on the preset association mapping rules in the configuration file, each piece of device data is matched to the corresponding model data; The matching results are integrated to obtain the correlation and matching relationship between the device data and the model data.

4. The method as described in claim 1, characterized in that, The model data includes one or more of the following: model identifier, model name, and model definition; The device data includes one or more of the following: device name, device identifier, device type, device communication parameters, and device communication address.

5. The method as described in claim 1, characterized in that, The step of initiating a registration operation for the data of each device in the data center based on the association matching relationship includes: The association matching relationship is traversed, and the device registration interface of the data center is called in turn to complete the registration operation of each device data.

6. The method as described in claim 1, characterized in that, After initiating the registration operation for the data of each device with the data center based on the association matching relationship, the method further includes: Receive the device registration result returned by the data center; If registration is successful, the registration status of the device data is recorded as "registered". If registration fails, the device registration interface of the data center will be called again. If it still fails after a preset number of retries, the registration of the device data will be terminated.

7. The method as described in claim 1, characterized in that, Also includes: When the intelligent fusion terminal searches for the configuration file in the file system based on the target file name, if the corresponding configuration file is not found, it exits the registration process.

8. The method as described in claim 1, characterized in that, The configuration file is a structured file in a preset format; The preset format includes either JSON or XML format.

9. A smart fusion terminal multi-model multi-device adaptive registration system, characterized in that, include: The file retrieval module is used to retrieve configuration files in the file system based on the target file name through the intelligent fusion terminal. When a configuration file is retrieved, the original content of the file is read from the configuration file. The file parsing module is used to parse the original content of the file to obtain multiple model data and device data associated with each model data. The model registration module is used to initiate a registration operation for each model data with the data center based on the model data. The device matching module is used to match the data of each device with its associated model data to generate a matching relationship. The device registration module is used to initiate a registration operation for the data of each device with the data center based on the association matching relationship.

10. The system as described in claim 9, characterized in that, The model registration module includes: The model comparison submodule is used to traverse the data of each model and compare it with the data center to see if the model data already exists. The registration judgment submodule is used to skip the current registration operation if the model data already exists; otherwise, it calls the registration interface of the data center to perform the registration operation on the model data.

Images