Equipment digitization-oriented object model construction method and system

Abstract

The invention provides an equipment digitalization-oriented object model construction method and system. The method comprises the following steps: respectively constructing a general object model template library and a product object model template library; performing first matching with a product object model template library based on product information input by a user to obtain a first matching result; based on the first matching result, determining whether to perform second matching with a general object model template library to obtain a second matching result; and analyzing and processing the second matching result to generate a target object model, and the method solves the problems of low object model development efficiency, insufficient standardization and poor compatibility.

Description

Technical Field

[0001] This invention belongs to the field of Internet of Things (IoT) technology, specifically relating to a method and system for constructing object models for device digitization. Background Technology

[0002] The Internet of Things (IoT) system is the core abstract model for realizing the digitization of physical devices. It is used to uniformly describe the properties, services, and events of devices and serves as the foundation for data interaction and control command communication between devices and cloud platforms and application systems. However, its construction process mainly relies on manual completion by engineers from equipment manufacturers or system integrators. It requires the integration of expertise from multiple fields such as mechanical engineering, automation control, embedded systems, communication protocols, and industry standards, and faces the following challenges: Different models or types of devices often have similar functional modules (such as temperature acquisition, remote switching, fault alarms, etc.), but lack reuse mechanisms, resulting in repeated design and coding each time, leading to long development cycles and high labor costs; Different manufacturers or project teams lack unified modeling specifications, defining their own object model structures, resulting in inconsistent model semantics and chaotic field naming for similar devices, severely restricting cross-platform interoperability and system integration capabilities; When device functions are iterated, the object model needs to be rebuilt, lacking modular reuse capabilities; Object model design highly depends on expert experience, making it difficult for ordinary developers to get started quickly, limiting the scale and automation level of object model construction. Summary of the Invention

[0003] (a) Purpose of the invention The purpose of this invention is to provide a method and system for constructing object models for device digitization, which can improve the efficiency of object model construction, enhance standardization capabilities and lower the technical threshold, while solving the problems of low object model development efficiency, insufficient standardization and poor compatibility.

[0004] (II) Technical Solution To address the above problems, a first aspect of the present invention provides a method for constructing a device digitization object model, comprising: Construct a general object model template library and a product object model template library respectively; The first matching is performed based on the product information input by the user and the product model template library to obtain the first matching result; Based on the first matching result, determine whether to perform a second matching with the general object model template library, and obtain the second matching result; The second matching result is parsed and processed to generate the target object model.

[0005] Preferably, the step of determining whether to perform a second match with the general object model template library based on the first matching result, and obtaining the second matching result, includes: If the first matching result is a failure, a second matching is performed with the general object model template library to determine the matching status; If the first matching result is successful, the user must confirm whether to modify the matching product model template library.

[0006] Preferably, the step of parsing and processing based on the second matching result to generate the target object model includes: If the second matching result fails to match the object model template library, a custom product object model needs to be created to obtain the target object model; If the second matching result is a successful match with the object model template library, then the matched general object model template library and product object model template library will be combined accordingly to obtain the target object model; If the second matching result is to modify the matching product model template library, then continue to determine whether it is necessary to expand the product model template library, and obtain the target product model based on the expansion processing result; If the second matching result is that the matching product model template library is not modified, the target product model will be generated directly.

[0007] Preferably, the step of further determining whether to expand the product model template library, and obtaining the target product model based on the expansion determination result, includes: If expansion is required, it can be matched and combined with the general object model template library to obtain the target object model; If no expansion is needed, then proceed to determine whether to configure the parameters of the product model template library to obtain the target model.

[0008] Preferably, the construction of the general object model template library includes: Collect original physical model data of various deployed devices; Extract the core elements from the original object model data and construct an initial object model template library; The initial object model template library is normalized to obtain a general object model template library.

[0009] Preferably, the product model template library includes: Collect original product model data of various deployed equipment; Extract the core elements from the original product model data to construct an initial product model template library; After normalizing the initial product model template library, it is matched and associated with the general product model template library to generate a product model template library.

[0010] Preferably, the custom product object model includes an object model name, an object model identifier, an object model type, a data type, and a data definition.

[0011] A second aspect of the present invention provides a device modeling system for device digitization, comprising: A template module is built to create a general object model template library and a product object model template library, respectively. The first matching module is used to perform a first match between the product information input by the user and the product model template library to obtain the first matching result. The second matching module is used to determine whether to perform a second matching with the general object model template library based on the first matching result, and to obtain the second matching result; The generated object model module is used to parse and process the second matching result to generate the target object model.

[0012] Preferably, the second matching module is used for: If the first matching result is a failure, a second matching is performed with the general object model template library to determine the matching status; If the first matching result is successful, the user must confirm whether to modify the matching product model template library.

[0013] Preferably, the generated product model module is used for: If the second matching result fails to match the object model template library, a custom product object model needs to be created to obtain the target object model; If the second matching result is a successful match with the object model template library, then the matched general object model template library and product object model template library will be combined accordingly to obtain the target object model; If the second matching result is to modify the matching product model template library, then continue to determine whether it is necessary to expand the product model template library, and obtain the target product model based on the expansion processing result; If the second matching result is that the matching product model template library is not modified, the target product model will be generated directly.

[0014] (III) Beneficial Effects The above-mentioned technical solution of the present invention has the following beneficial technical effects: The present invention provides a method and system for constructing object models for equipment digitization. This method innovatively establishes a general object model library and a product object model template library. The product object model library satisfies product-level reuse, while the general object model library satisfies the most granular level of reuse, taking into account both efficiency and flexibility. This method first matches the user-input product information with the product object model template library. Based on the first matching result, it determines whether to perform a second matching with the general object model template library, obtaining the second matching result. Finally, the second matching result is parsed and processed to generate the target object model. This method, by constructing reusable general object model templates and extensible product-specific object model templates, forms a hierarchical modeling architecture, realizing standardized description, modular reuse, and cross-platform interoperability of object models, ultimately solving the problems of low object model development efficiency, insufficient standardization, and poor compatibility. Attached Figure Description

[0015] Figure 1 This is a flowchart of a device digitization-oriented object model construction method according to the present invention; Figure 2 This is a schematic diagram of a device digitization-oriented object model construction system according to the present invention; Figure 3 This is a flowchart of a specific embodiment of the object model construction method for device digitization of the present invention. Detailed Implementation

[0016] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to specific embodiments and the accompanying drawings. It should be understood that these descriptions are merely exemplary and not intended to limit the scope of the invention. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concept of the invention.

[0017] like Figure 1 As shown, the first aspect of this invention provides a method for constructing object models for device digitization. This method extracts common functional units in IoT systems through a data-driven approach, eliminates naming heterogeneity using semantic normalization technology, and constructs a standardized, reusable functional module library. In the actual modeling process, a complete object model definition for the target device is dynamically generated through template matching, combination selection, and parameter configuration. Specifically, this method includes: S1. Construct a general object model template library (general object model) and a product object model template library (product library). The product library is a template library built for products. Similar products can be directly reused, minimizing the need to build object models from scratch. The general object model, on the other hand, provides finer-grained reuse and serves two purposes: first, it supplements the product object model when users find that some new product object models are missing when building new product object models using the product template library; second, when users build a new product that is not in the product template library, they can combine it with the general object model to create a new product object model. The construction process of each template library is as follows: (1) Constructing a general object model template library includes: a) collecting original object model data of various deployed devices; b) extracting the core elements from the original object model data to construct an initial object model template library; c) normalizing the initial object model template library to obtain a general object model template library.

[0018] (2) Constructing a product property model template library includes: a) collecting original product property model data of various deployed equipment; b) extracting core elements from the original product property model data to construct an initial product property model template library; c) normalizing the initial product property model template library and matching and associating it with the general property model template library to generate a product property model template library.

[0019] S2, perform a first match between the product information input by the user and the product model template library to obtain the first matching result; S3, based on the first matching result, determine whether to perform a second matching with the general object model template library, and obtain the second matching result, which specifically includes: S31, If ​​the first matching result is a failure, then perform a second matching with the general object model template library to determine the matching status; S32, if the first matching result is a successful match, the user shall confirm whether to modify the matching product model template library.

[0020] S4, parse and process the second matching result to generate the target object model, specifically including: S41. If the second matching result fails to match the object model template library, a custom product object model needs to be created to obtain the target object model. The custom product object model includes object model name, object model identifier, object model type, data type, and data definition.

[0021] S42, If the second matching result is a successful match with the object model template library, then the matched general object model template library and product object model template library are combined accordingly to obtain the target object model; S43, if the second matching result is a modification operation on the matched product model template library, then it is further determined whether the product model template library needs to be expanded, and the target product model is obtained based on the expansion processing result. The further determination of whether the product model template library needs to be expanded, and the obtaining of the target product model based on the expansion determination result, includes: S431, if expansion is required, it is matched and combined with the general object model template library to obtain the target object model. There are two ways to expand the object model: a) retrieve the required object model from the general object model and add it to the new product object model; b) if the general object model cannot be retrieved, an atomic object model (attribute, function, or event) can be added directly. If the added atomic object model is selected to be synchronized to the general object model, a loop can be formed.

[0022] S432, if no extension is needed, continue to determine whether to configure the parameters of the product model template library to obtain the target model.

[0023] S44. If the second matching result is that the matching product model template library is not modified, then the target product model is generated directly.

[0024] Preferably, constructing a general object model template library also includes: after completing field-level semantic normalization, it can also be combined with manual review by domain experts to ensure the accuracy of the general object model. Similarly, constructing a product object model template library also includes: after completing the association of the general object model template library, combining the manual review of the product object model library by domain experts to ensure the accuracy of the product object model templates.

[0025] like Figure 2 As shown, a second aspect of the present invention provides a device model building system for device digitization, comprising: Module 21 is used to build a general object model template library and a product object model template library, respectively. The first matching module 22 is used to perform a first matching based on the product information input by the user and the product model template library to obtain the first matching result; The second matching module 23 is used to determine whether to perform a second matching with the general object model template library based on the first matching result, and to obtain a second matching result. The second matching module 23 is used for: 1) if the first matching result is a matching failure, then performing a second matching with the general object model template library to determine the matching status; 2) if the first matching result is a successful matching, then having the user confirm whether to modify the matched product object model template library.

[0026] The object model generation module 24 is used to parse and process the second matching result to generate the target object model. The object model generation module 24 is used to: 1) If the second matching result fails to match the object model template library, a custom product object model needs to be created to obtain the target object model; 2) If the second matching result successfully matches the object model template library, the matched general object model template library and the product object model template library are combined accordingly to obtain the target object model; 3) If the second matching result requires modification of the matched product object model template library, it is further determined whether the product object model template library needs to be expanded, and the target object model is obtained according to the expansion processing result; 4) If the second matching result does not require modification of the matched product object model template library, the target object model is directly generated.

[0027] The following is combined with Figure 3 The specific description of the object model construction method of the present invention is as follows: 1.1 Constructing a general object model template library This step aims to extract common functional units widely existing in IoT systems and construct a standardized, general-purpose object model template library as the atomic unit for object model construction. The construction process of the general-purpose object model template library includes the following steps: 1.1.1 Data Acquisition and Cleaning This method first collects device model data from various devices deployed in historical projects. This device model data includes, but is not limited to, device description files in JSON or TSL (Thing Specification Language) format. The data collection scope covers multiple typical IoT application scenarios such as smart parks, industrial sensing, and energy management.

[0028] 1.1.2 Extract Model The collected original object model data is parsed to extract functional definitions (attributes, services, events), and invalid or redundant fields are removed to form an initial object model corpus with a unified structure and controllable quality, providing data support for subsequent semantic analysis.

[0029] 1.1.3 Field-level semantic normalization processing To address the semantic heterogeneity caused by different manufacturers and systems using different field names for the same physical quantity (e.g., "temp", "temperature", "TempValue", etc. all represent temperature), this invention proposes a field-level semantic normalization method, which specifically includes the following technical steps: 1) Utilize stemming algorithms in natural language processing technology, and combine them with semantic dictionaries such as WordNet, to perform lemmatization and synonym mapping on field names, and identify semantically equivalent field identifiers; 2) Based on the standardization rules of physical units, the measurement units of the fields are uniformly converted and normalized (for example, "°C, degC, Celsius" are unified into "℃") to ensure the consistency of dimensions; 3) Construct a set of "semantic equivalence classes" to group field names and their unit combinations with the same semantic meaning under the same logical concept identifier, forming a standardized semantic mapping table. This normalization process effectively solves the naming heterogeneity problem across systems and devices, providing semantic consistency assurance for the extraction of general templates.

[0030] 1.1.4 Expert Review Based on the completion of field-level semantic normalization, the merged object model data is broken down into three types of atomic units: attributes, services, and events. Combined with manual review by domain experts, the accuracy of the general object model is ensured. The review status is recorded in the template library table using the `reviewed` field: -1 indicates review failed, 0 indicates no review, and 1 indicates review passed.

[0031] 1.1.5 Generate a standardized, universal object model template After manual review by domain experts, a standardized general object model template library is finally formed. Each general object model template is a record in the library, containing template ID, template name, template identifier, template category (1-attribute, 2-function, 3-event), data type (integer, decimal, string, bool, array, enum), data definition, and review status (-1: review failed, 0: unreviewed, 1: review passed). An example is shown in Table 1. Table 1 General Physical Model Template Library The meanings of each character in Table 1 are as follows: template_id: Template ID; name: Template name; identifier: Template identifier; type: Template category; data_type: Data type; specs: Data definition; reviewed: Review status (1: Review failed, 0: Not reviewed, 1: Review passed) current: electric current; decimal: decimal.

[0032] 1.2 Construction of Product Model Template Library This invention further provides a standardized product object model template library for specific equipment categories (such as smart streetlights, smoke detectors, air conditioner controllers, etc.). The first three steps of constructing the product object model template are based on the same principle as those of constructing a general object model, namely, data acquisition of original product object model data, extraction of original product object model data, semantic normalization processing, and then the following steps: 1.2.1 Related General Object Model Library The existing product object models are parsed, and their identifiers are normalized. Then, they are matched with a general object model library to associate them with the general object model IDs. This ensures that the identifiers and naming of both the product templates and the general object model templates are standardized and consistent. The data definitions of the product object models are parsed out. Although the data definition format is the same for each product object model, the numerical values ​​may differ. Therefore, each product object model template retains its own data definition.

[0033] 1.2.2 Expert Review Domain experts manually review the product model library to ensure the accuracy of the product model templates. The review status is recorded in the template library table using the reviewed field: -1 indicates that the review failed, 0 indicates that it was not reviewed, and 1 indicates that the review passed.

[0034] 1.2.3 Constructing a Product Model Library Each product model template is a record in the library, containing the template product ID, category ID, category name, and whether the review has been approved. An example is shown in Table 2 below: Table 2: Relationship between Product Templates and Categories The meanings of each character in Table 2 are as follows: template_proudct_id: template product ID; category_id: product category ID; category_name: Product category name.

[0035] The relationship table between the product template library and the general object model template includes the template product ID, object model ID, corresponding general object model template ID, and data definition, as shown in Table 3: Table 3 Relationship between Product Template Library and General Property Model Template Library The meanings of each character in Table 3 are as follows: template_proudct_id: Template product ID; model_id: Object model ID; template_id: General object model template ID; specs: Data definition.

[0036] In addition, the product template library supports categorization and management by equipment type, application scenario, or industry standard, facilitating quick retrieval and matching.

[0037] 1.3 Process for Generating Composite Object Models When a user creates a new product's object model, the system completes the construction of the target product's object model according to the following process: 1.3.1 Product Model Template Matching 1) The user enters the device model, category, or keywords. 2) The system performs fuzzy or precise matching in the product object model template library. If the matching fails, it proceeds to step 1.3.2, which combines general object models. If a matching template exists, the template content is displayed for the user to confirm. 3) If the user confirms that no modifications are needed, the final object model will be generated directly, and the process will end; otherwise, proceed to the next step to determine whether the object model needs to be expanded.

[0038] 4) If the extended object model is not required, proceed to step 1.3.3 to determine whether parameter adjustment is required; if the extended object model is required, proceed to step 1.3.2 to combine general object models.

[0039] 1.3.2 General Object Model Combination 1) Retrieve from the general object model template library If no suitable template is found or the current product template is incomplete and needs expansion, the system guides the user to select the required functional modules (attributes, services, events) from the general object model library to supplement it; if no suitable object model template is available, the user proceeds to the next step of customizing the product object model. If a general object model can be found, the user searches for the required template from the general template library to add attributes, services, or events, gradually combining them to create the product object model.

[0040] 2) Custom product model Users fill in information such as object model name, object model identifier, object model type, data type, and data definition to create a custom product object model. Upon successful creation, the system prompts the user whether to submit the custom module to the general library (which, after review, can be included in the public template library for knowledge preservation). The storage method for each specific object model of a product is shown below. Each product object model template is a record in the library, containing product ID, object model ID, object model name, object model identifier, object model type, data type, and data definition. The difference between this and the product object model template is that it essentially copies the object model template and places it within the product object model. This maintains the stability of published products and prevents them from being affected by updates to the general object model. An example is shown in Table 4. Table 4 Product Model Library The meanings of each character in Table 4 are as follows: product_id: product ID; model_id: product model ID. name: Product name; identifier: Object model identifier; type: Template type; data_type: Data type; specs: Data definition; current: Current; lighting_intensity: light intensity; voltage: voltage; decimal: decimal number integer: an integer.

[0041] After the custom model is created, determine whether parameter adjustment is needed. If so, proceed to 1.3.3 Parameter Adjustment; otherwise, proceed to 1.3.4 Generate Final Product Model.

[0042] 1.3.3 Parametric Adjustment For the selected template (whether general or product-specific), the system allows users to configure parameters according to the actual device parameters; the actual adjustment involves the data definition section. For example, adjustments can be made in the following way: (1) Modify the measurement range of the temperature sensor (original -40~120℃ → actual equipment is 0~85℃); (2) Adjust the timeout period for service calls; (3) Set the threshold conditions for event triggering; all parameter adjustments retain the template structure unchanged, only modifying the parameters in the data definition part to ensure semantic consistency.

[0043] 1.3.4 Generating the final product model After the user completes the template selection and parameter configuration, clicking "Publish" will cause the system to retrieve the corresponding object model list from the product object model library based on the product_id, generating the final standard object model definition. The system will then prompt the user to confirm whether to submit the custom module to the product template library.

[0044] This invention discloses a method and system for constructing object models for device digitization. This method effectively avoids redundant development through template reuse, reducing object model construction time by more than 60% and significantly improving development efficiency. Simultaneously, standardization and consistency are significantly enhanced by this method. A unified template library ensures consistency in the object model structure for similar devices, thereby improving cross-platform compatibility and system integration capabilities. Flexible expansion and customization are fully supported, and the modular design balances universality and personalized needs, making it suitable for diverse device scenarios. Furthermore, this application significantly lowers the technical threshold, allowing non-expert users to complete object model construction through a graphical interface, reducing reliance on professional backgrounds and promoting knowledge accumulation and sharing. The custom object models can also feed back into the template library, forming a positive cycle of "use—optimization—sharing," while facilitating maintenance and upgrades. When device functions change, only the corresponding templates or parameters need to be adjusted, without reconstructing the entire object model.

[0045] It should be understood that the specific embodiments described above are merely illustrative or explanatory of the principles of the invention and do not constitute a limitation thereof. Therefore, any modifications, equivalent substitutions, improvements, etc., made without departing from the spirit and scope of the invention should be included within the protection scope of the invention. Furthermore, the appended claims are intended to cover all variations and modifications falling within the scope and boundaries of the appended claims, or equivalent forms of such scope and boundaries. Those skilled in the art will understand that embodiments of the invention can be provided as methods, systems, or computer program products. Therefore, the invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the 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. These computer program instructions can also be stored in a computer-readable storage medium capable of directing a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means implemented in a process. Figure 1 One or more processes and / or boxes Figure 1The functions specified in one or more boxes. Those skilled in the art will understand that all or part of the steps in the methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it includes the flows of the embodiments of the methods described above. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc. The steps in the methods of the embodiments of the present invention can be adjusted, merged, and deleted according to actual needs. The modules in the system of the embodiments of the present invention can be merged, divided, and deleted according to actual needs.

Claims

1. A method for constructing a device-oriented digital physical model, characterized in that, The method comprises the steps of: respectively constructing a general object model template library and a product object model template library; performing first matching based on product information input by a user and the product object model template library to obtain a first matching result; determining whether to perform second matching with the general object model template library based on the first matching result to obtain a second matching result; analyzing and processing the second matching result to generate a target object model.

2. The device-oriented digitalized object model construction method according to claim 1, wherein, The step of determining whether to perform second matching with the general object model template library based on the first matching result to obtain a second matching result comprises: if the first matching result is a matching failure, performing second matching with the general object model template library to determine a matching state; if the first matching result is a matching success, confirming by the user whether to modify the matched product object model template library.

3. The device-oriented digitalized object model construction method according to claim 2, wherein, The step of analyzing and processing the second matching result to generate a target object model comprises: if the second matching result is a matching failure with the object model template library, creating a custom product object model to obtain the target object model; if the second matching result is a matching success with the object model template library, performing corresponding combination on the matched general object model template library and the product object model template library to obtain the target object model; if the second matching result is a modification operation on the matched product object model template library, continuing to determine whether to expand the product object model template library, and obtaining the target object model according to an expansion processing result; if the second matching result is not to modify the matched product object model template library, directly generating the target object model.

4. The device-oriented digitalized object model construction method according to claim 3, wherein, The step of continuing to determine whether to expand the product object model template library and obtaining the target object model according to an expansion determination processing result comprises: if expansion is needed, performing matching combination with the general object model template library to obtain the target object model; if expansion is not needed, continuing to determine whether to perform parameter configuration on the product object model template library to obtain the target model.

5. The device-oriented digitalized object model construction method according to claim 1, wherein, The step of constructing the general object model template library comprises: collecting original object model data of various types of deployed devices; extracting core elements in the original object model data to construct an initial object model template library; performing normalization processing on the initial object model template library to obtain the general object model template library.

6. The device-oriented digitalized object model construction method according to claim 5, wherein, The step of constructing the product object model template library comprises: collecting original product object model data of various types of deployed devices; extracting core elements in the original product object model data to construct an initial product object model template library; performing normalization processing on the initial product object model template library, and performing matching association with the general object model template library to generate the product object model template library.

7. The device-oriented digitalized object model construction method according to claim 5, wherein, The custom product object model comprises an object model name, an object model identifier, an object model type, a data type, and data definition.

8. A device-oriented digitalized object model construction system characterized by, The method comprises the steps of: constructing a template module for respectively constructing a general object model template library and a product object model template library; performing first matching based on product information input by a user and the product object model template library to obtain a first matching result; determining whether to perform second matching with the general object model template library based on the first matching result to obtain a second matching result; generating an object model module for analyzing and processing the second matching result to generate a target object model.

9. The device-oriented digitized object model building system of claim 8, wherein, The second matching module is configured to: If the first matching result is a matching failure, a second matching is performed with the general object model template library to determine a matching state; If the first matching result is a matching success, a user confirms whether to modify the matched product object model template library.

10. The device-oriented digitized object model building system of claim 9, wherein, The object model generation module is used for: If the second matching result is a matching failure with the object model template library, a custom product object model needs to be created to obtain a target object model; If the second matching result is a matching success with the object model template library, the matched general object model template library and the product object model template library are correspondingly combined to obtain the target object model; If the second matching result is a modification operation on the matched product object model template library, it is continuously determined whether the product object model template library needs to be expanded, and the target object model is obtained according to an expansion processing result; If the second matching result is that the matched product object model template library is not modified, the target object model is directly generated.

Images