Element metadata modeling method, apparatus, device, and medium

Abstract

The application relates to the technical field of data modeling, and discloses an element metadata modeling method, device, equipment and medium, the method comprising: establishing an element template hierarchical model, wherein the element template hierarchical model comprises a sub-element model and a composite element model; configuring atomic capabilities in the sub-element model through a capability definition node; organizing an e-BOM structure in the composite element model through an assembly structure node; establishing a life cycle activity model, and defining an action object node and a capability reference node of the life cycle activity model, wherein the action object node points to the sub-element model in the e-BOM structure, and the capability reference node references the atomic capabilities of the sub-element model; and arranging the atomic capabilities based on the action object node and the capability reference node to form a capability calling relationship of the composite element model. The application guarantees the consistency of a digital twin and a physical entity structure.

Description

Technical Field

[0001] This invention relates to the field of data modeling technology, and in particular to a method, apparatus, device and medium for modeling element metadata. Background Technology

[0002] With the rapid development of the Industrial Internet and digital twin technologies, digital modeling of physical entities has become a key technology for realizing full lifecycle management of equipment. In industrial scenarios, complex equipment is usually assembled from dozens of atomic components, including sensors, controllers, actuators, protective housings, support structures, communication modules, etc., requiring the establishment of a unified metadata model to describe its structure, capabilities, and behavior.

[0003] Currently, existing IoT platforms and digital twin modeling technologies typically use device object models as the core, describing devices as a collection of attributes, telemetry, events, and commands. This approach is suitable for relatively simple single devices, but when a device is assembled from multiple atomic components, traditional flat object models struggle to express the true internal composition hierarchy, assembly paths, positional constraints, and quantity constraints. They cannot clearly describe which component assembles which, which depends on which, or which can be replaced. Furthermore, traditional device object models often define overall machine capabilities at the device level, such as temperature reading, pressure reading, valve opening, and motor starting, making it impossible to trace which atomic component a particular telemetry or command originates from. This results in unclear capability sources, and when the device is replaced, repaired, upgraded, or partially replaced, the overall machine-level capability definition can easily deviate from the actual physical structure. In addition, existing BOMs or e-BOMs are mainly used for manufacturing, procurement, or material management, typically only representing a list of materials. They cannot be directly used as capability location paths during digital twin operation, nor can they resolve issues such as which component assembles which, which is orchestrated and scheduled, or the granularity at which activities affect the device. Furthermore, in existing technical solutions, complex equipment can be arbitrarily modeled in different projects, leading to model inconsistencies, difficulties in reuse, and high governance costs. In terms of lifecycle activity management, existing technologies typically manage activities such as equipment inspection, maintenance, control, replacement, and testing separately from the equipment structure, making it difficult to accurately apply them to a specific BOM granularity. When an activity needs to act on a specific sub-component, there is a lack of a clear target location mechanism, resulting in a lack of basis for activity orchestration and execution.

[0004] In summary, existing modeling techniques cannot guarantee the consistency between digital twins and physical entity structures. When physical equipment undergoes component replacement, partial repair, or structural changes, the digital twin struggles to synchronously reflect the changes in the real physical structure, leading to problems such as difficulty in tracing the source of capabilities, inaccurate targeting of lifecycle activities, and high costs for model reuse and governance. Summary of the Invention

[0005] This invention provides a method, apparatus, device, and medium for modeling element metadata, in order to solve the technical problem that existing modeling technologies cannot guarantee the consistency between digital twins and physical entity structures.

[0006] Firstly, a method for modeling element metadata is provided, including: Establish a hierarchical model of element templates, which includes a sub-element model and a composite element model; In the sub-element model, atomic capabilities are configured through capability definition nodes; In the composite element model, the e-BOM structure is organized through assembly structure nodes; Establish a lifecycle activity model and define the target node and capability reference node of the lifecycle activity model, wherein the target node points to the sub-element model in the e-BOM structure, and the capability reference node references the atomic capability of the sub-element model; The atomic capabilities are arranged based on the target node and the capability reference node to form the capability call relationship of the composite element model.

[0007] Secondly, an element metadata modeling apparatus is provided, including: Establishment unit, used to establish element template hierarchical model, wherein the element template hierarchical model includes sub-element model and composite element model; Configuration unit, used to configure atomic capabilities in the sub-element model through capability definition nodes; Organizational units are used to organize the e-BOM structure in the composite element model through assembly structure nodes; A definition unit is established to establish a lifecycle activity model and to define the target node and capability reference node of the lifecycle activity model, wherein the target node points to the sub-element model in the e-BOM structure and the capability reference node references the atomic capability of the sub-element model; The orchestration unit is used to orchestrate the atomic capabilities based on the target node and the capability reference node to form the capability call relationship of the composite element model.

[0008] Thirdly, a wearable device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above-described element metadata modeling method.

[0009] Fourthly, a computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, implements the steps of the above-described element metadata modeling method.

[0010] In the above-mentioned scheme implemented by the element metadata modeling method, device, equipment and medium, an element template hierarchical model can be established, wherein the element template hierarchical model includes a sub-element model and a composite element model; in the sub-element model, atomic capabilities are configured through capability definition nodes; in the composite element model, the e-BOM structure is organized through assembly structure nodes. A lifecycle activity model is established, and the target nodes and capability reference nodes of the lifecycle activity model are defined. The target nodes point to the sub-element models in the e-BOM structure, and the capability reference nodes reference the atomic capabilities of the sub-element models. Based on the target nodes and capability reference nodes, the atomic capabilities are arranged to form the capability invocation relationship of the composite element model. In this invention, by establishing a hierarchical element template model, sub-element models and composite element models are distinguished, separating the modeling dimensions of atomic physical components from those of complex devices. Atomic capabilities are configured through capability definition nodes in the sub-element models, making capability attribution clear and traceable. The e-BOM structure is organized through assembly structure nodes in the composite element model, ensuring that the assembly relationship of the digital twin is consistent with the physical entity. The target nodes of the lifecycle activity model point to the sub-element models in the e-BOM structure, and the capability reference nodes reference the atomic capabilities of the sub-element models, enabling lifecycle activities to be precisely applied to specific physical components. Based on the target nodes and capability reference nodes, the atomic capabilities are arranged to form the capability invocation relationship of the composite element model, ensuring that the capability source corresponds to the physical structure. When physical equipment undergoes component replacement or partial repair, the digital twin can be updated synchronously through the e-BOM structure, maintaining the ownership of atomic capabilities and accurately locating the objects affected by lifecycle activities, thereby ensuring the consistency between the digital twin and the physical entity structure. Attached Figure Description

[0011] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a flowchart illustrating an element metadata modeling method according to an embodiment of the present invention; Figure 2 yes Figure 1 A schematic diagram of a specific implementation of step S110; Figure 3 A flowchart illustrating an element metadata modeling method provided in another embodiment of the present invention; Figure 4 A flowchart illustrating an element metadata modeling method provided in another embodiment of the present invention; Figure 5 This is a schematic block diagram of an element metadata modeling device according to an embodiment of the present invention; Figure 6 This is a schematic block diagram of a computer device provided in an embodiment of the present invention. Detailed Implementation

[0013] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0014] The element metadata modeling method provided in this invention can be applied to clients and / or servers. Clients can be, but are not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices. Servers can be implemented using independent servers or server clusters composed of multiple servers. Currently, existing modeling technologies suffer from the technical problem of failing to guarantee the consistency between the digital twin and the physical entity structure. To address this problem, this invention proposes an element metadata modeling method. This method establishes a hierarchical model of element templates, distinguishing between sub-element models and composite element models, thus separating the modeling dimensions of atomic physical components from those of complex devices. In the sub-element model, atomic capabilities are configured through capability definition nodes, making capability attribution clear and traceable. In the composite element model, the e-BOM structure is organized through assembly structure nodes, ensuring consistency between the assembly relationship of the digital twin and the physical entity. The target nodes of the lifecycle activity model point to the sub-element models in the e-BOM structure, and the capability reference nodes reference the atomic capabilities of the sub-element models, enabling lifecycle activities to precisely target specific physical components. Based on the target nodes and capability reference nodes, atomic capabilities are orchestrated to form the capability invocation relationship of the composite element model, ensuring that the capability source corresponds to the physical structure. When physical equipment undergoes component replacement or partial repair, the digital twin can be synchronously updated through the e-BOM structure, maintaining the original atomic capability attribution and accurately locating the objects affected by lifecycle activities, thereby ensuring the consistency between the digital twin and the physical entity structure. The invention will now be described in detail through specific embodiments.

[0015] Please see Figure 1 As shown, Figure 1 A flowchart of an element metadata modeling method provided in an embodiment of the present invention includes the following steps: S110-S150.

[0016] S110. Establish an element template hierarchical model, which includes a sub-element model and a composite element model.

[0017] In this embodiment, as Figure 2 As shown, step S110 includes steps S111-S112: S111, defining indivisible or no-further-disassembly-required atomic physical components as the sub-element models; S112, defining the complex device assembled from multiple sub-element models or sub-e-BOM templates as the composite element model, wherein the sub-e-BOM template is the engineering assembly structure template of the lower-level composite element model. It should be noted that the atomic physical components refer to the smallest physical units with independent functions that are not recommended for further disassembly, such as sensors, actuators, controllers, communication modules, power modules, etc. The complex device refers to a complete functional unit formed by multiple atomic physical components or lower-level composite devices through physical connections or logical associations, such as intelligent pump stations, valve systems, control cabinets, etc. Each composite element model organizes the e-BOM structure through assembly structure nodes, ensuring that the assembly relationship of the digital twin is consistent with the physical entity. It should also be noted that when the composite element model needs to reference other composite devices, hierarchical assembly is achieved by attaching the sub-e-BOM template, rather than directly referencing the composite element model itself, thereby supporting the recursive reuse of templates.

[0018] Understandably, this hierarchical definition approach separates the modeling dimensions of atomic physical components from those of complex devices. When components of the physical device are replaced or undergo partial repairs, the digital twin can be updated synchronously through the e-BOM structure, while the affiliation of atomic capabilities remains unchanged, thus ensuring the consistency between the digital twin and the physical entity structure.

[0019] In one embodiment, such as this embodiment, the sub-element model is created based on a sub-element template, and the composite element model is created based on a composite element template. Both the sub-element template and the composite element template have a template identifier and a template name. The step of creating the sub-element model based on the sub-element template includes: copying the atomic capabilities configured in the capability definition node of the sub-element template to the capability definition node of the sub-element model, and assigning a model identifier and actual parameters to the sub-element model. The step of creating the composite element model based on the composite element template includes: copying the e-BOM structure organized in the assembly structure node of the composite element template to the assembly structure node of the composite element model, and assigning a model identifier and assembly position parameters to the composite element model. It should be noted that the template identifier (templateId) and template name (templateName) are used to uniquely identify the template type. The template is a type definition specification, and the model is an instantiated object of the template; the two are designed separately to support batch reuse. It should also be noted that atomic capabilities include attributes such as capabilityId, capabilityType, name, inputSchema, outputSchema, unit, protocolMapping, permissionRule, and statusRule. Model identifiers are used to distinguish different instances under the same template; actual parameters include runtime data such as device serial number, installation location, and calibration parameters, allowing the same template to generate multiple sub-element model instances with different parameters. The e-BOM structure includes fixed assembly modules, hook nodes, constraints, etc., supporting multi-level recursive assembly. Assembly location parameters include information such as the physical location, connection relationship, and installation direction of each sub-element template or sub-e-BOM template in the composite device, allowing the same template to generate multiple composite element model instances with different assembly configurations.

[0020] Understandably, in this embodiment, the design of separating the template and the model has the following technical advantages: the template is used to define type specifications, supporting standardization and reuse; the model is used to describe specific instances, supporting parameterization and differentiation. When the template is updated, it can be batch-synchronized to all models created based on the template, ensuring data consistency. Simultaneously, the actual parameters of the model can be modified independently without affecting the template and other instances, supporting flexible configuration. When components are replaced or partial repairs are performed on the physical device, only the corresponding model instance needs to be updated, without modifying the template, thus ensuring the consistency between the digital twin and the physical entity structure.

[0021] S120. Configure atomic capabilities in the sub-element model through capability definition nodes.

[0022] In this embodiment, the sub-element model includes at least the following fields: templateId, templateName, classification, identityRules, capabilities, dataSources, mappingRules, and lifecycleActivities. The capabilities field, as a capability definition node, stores the atomic capability definitions that can be referenced by the sub-element model. Each atomic capability has attributes such as capabilityId, capabilityType, name, inputSchema, outputSchema, unit, protocolMapping, permissionRule, and statusRule, making capability attribution clear and traceable. It should be noted that telemetry describes measurement data reported by the device, such as temperature and pressure values; command describes control commands that can be issued to the device, such as start and stop; event describes alarms or status changes actively reported by the device, such as fault alarms and threshold exceedances; and property describes the device's readable / writable status or parameters, such as device model and firmware version.

[0023] S130. In the composite element model, the e-BOM structure is organized by assembly structure nodes.

[0024] In this embodiment, the composite element model includes at least the following fields: templateId, templateName, classification, assemblyModules, identityRules, lifecycleActivities, validationRules, and versionInfo. The assemblyModules field serves as an assembly structure node, used to organize the e-BOM structure and express multi-level recursive assembly relationships. It should be noted that the e-BOM (Engineering Bill of Materials) structure refers to the hierarchical assembly relationship structure organized through assembly structure nodes in the composite element model, including fixed assembly modules, attachment nodes, and constraints. The e-BOM structure not only expresses material composition relationships but also links with atomic capabilities, lifecycle activities, instance attachments, and rule validation, serving as the capability location path during digital twin runtime.

[0025] In one embodiment, such as this embodiment, the assembly structure node includes multiple fixed assembly modules. The sub-element template or sub-e-BOM template is attached to the fixed assembly module through a hooking node, and constraints are configured for the hooking node. The sub-e-BOM template is the assembly structure part of the lower-level composite element template, used to express multi-level recursive assembly relationships. It's important to note that the fixed assembly module is not simply a display group, but rather serves as the foundational structure for template validity verification, capability scope, lifecycle activity binding, and instance attachment. It includes a protection module, a support module, a control module, and an execution module. The protection module carries sub-element templates or sub-e-BOM templates related to equipment protection, such as shells, shielding, waterproofing, dustproofing, explosion-proofing, isolation, and protective covers. The support module carries sub-element templates or sub-e-BOM templates related to support and positioning, such as brackets, bases, guide rails, structural components, installation accessories, and spatial components. The control module carries sub-element templates or sub-e-BOM templates related to control and communication, such as controllers, gateways, PLCs, communication units, computing units, and edge nodes. The execution module carries sub-element templates or sub-e-BOM templates that directly sense or influence the physical world, such as sensors, actuators, motors, valves, pumps, switches, and data acquisition terminals. Each fixed assembly module can recursively nest sub-element templates or sub-e-BOM templates, supporting multi-level expansion. Understandably, each assembly layer is constrained by module type, quantity, location, and referencing rules to ensure that similar composite equipment has a consistent structural framework across different projects. When components of the physical equipment are replaced, the digital twin can locate the change position through fixed assembly modules and synchronously update the e-BOM structure, thereby ensuring the consistency between the digital twin and the physical entity structure.

[0026] It should also be noted that the attachment node is the specific connection point of the assembly relationship, used to specify the type of element that can be attached at that location. When attaching a child element template, it indicates that an atomic physical component is assembled at that location. When attaching a child e-BOM template, it indicates that a lower-level composite device is assembled at that location, supporting multi-level recursive assembly.

[0027] It should be further explained that the constraints include parent-child relationship constraints, template attachment constraints, quantity constraints, and position constraints. Among them, the parent-child relationship constraint defines the hierarchical relationship between the attachment node and the fixed assembly module; the template attachment constraint restricts the types of templates that can be attached to prevent incorrect references; the quantity constraint specifies the range of the number of elements that can be attached; and the position constraint specifies the physical installation position, orientation, and connection relationship of the elements.

[0028] It should be further explained that when a composite device needs to reference other composite devices, this is done through a connector e-BOM template, rather than directly referencing the composite element template itself. This design supports recursive template reuse, avoids circular references, and maintains the clarity and traceability of the assembly structure.

[0029] Understandably, the combination design of fixed assembly modules and attachment nodes has the following technical effects: First, it provides a standardized assembly skeleton to ensure that the structure of similar equipment models is consistent; second, it supports flexible element attachment to adapt to different project configuration requirements; third, it prevents incorrect assembly and circular references through constraint condition verification; and fourth, it supports multi-level recursion to express the real hierarchical structure of complex equipment.

[0030] S140. Establish a lifecycle activity model and define the target node and capability reference node of the lifecycle activity model, wherein the target node points to the sub-element model in the e-BOM structure, and the capability reference node references the atomic capability of the sub-element model.

[0031] In this embodiment, based on the business activities of the sub-element model or the composite element model in the lifecycle stages, a six-dimensional structure is used to describe the business activities, resulting in the lifecycle activity model. The six-dimensional structure includes time dimension, organization dimension, space dimension, state dimension, object dimension, and capability dimension. It should be noted that the lifecycle stages include research and development, design, manufacturing, assembly, testing, operation, maintenance, and decommissioning, etc., and each stage contains several business activities, such as inspection, maintenance, control, replacement, and testing.

[0032] It should also be noted that a six-dimensional structure (T / O / P / S / E / A) is used to describe business activities, resulting in a lifecycle activity model. T (Time) defines the timing or triggering conditions of business activities, supporting timed triggering, event triggering, or conditional triggering. O (Organization) defines the organizational or role permissions that can execute business activities, such as maintenance personnel, manufacturers, or third-party service providers. P (Place) defines the spatial scope or location restrictions for business activity execution, such as equipment site, remote center, or specific area. S (State) defines the state or stage transition of the model before and after business activity execution, such as switching from running state to maintenance state. E (Entity) specifies the target model affected by the business activity, recording the target element path, BOM node ID, sub-element template ID, or template ID, pointing to the sub-element model in the e-BOM structure through the affected object node. A (Ability) references the capability identifier of the sub-element model required to execute the business activity, recording the capability identifier, instruction identifier, or telemetry identifier, and calling atomic capabilities through the capability reference node. Understandably, the design of the six-dimensional structure (T / O / P / S / E / A) strongly links lifecycle activities with the equipment structure. Activities can be precisely applied to the specified BOM granularity, avoiding execution deviations caused by the separation of activities and structure management in traditional technologies, thereby ensuring the consistency between the digital twin and the physical entity structure.

[0033] It should also be noted that the target node points to the sub-element model in the e-BOM structure, specifying the concrete physical component on which the business activity acts. The target node records the target element path, BOM node ID, and sub-element template ID, allowing the activity to act precisely at a specified BOM granularity, such as a particular sensor, actuator, or controller, rather than just at the system-wide level. The capability reference node references the atomic capabilities of the sub-element model, declaring the capabilities required for the execution of the business activity. The capability reference node records capability identifiers, instruction identifiers, or telemetry identifiers, corresponding to the atomic capabilities configured in the capability definition node of the sub-element model, achieving a declarative binding between activities and capabilities.

[0034] S150. Arrange the atomic capabilities based on the target node and the capability reference node to form the capability call relationship of the composite element model.

[0035] In this embodiment, the target node locates the specific physical component affected by the business activity, while the capability reference node declares the atomic capabilities required to execute the activity. Through their collaboration, the composite element model does not need to redefine capabilities within itself, but instead declaratively calls the atomic capabilities of the sub-element models in the assembly structure through lifecycle activities. This orchestration method ensures that capability sources correspond to the physical structure. When components of the physical device are replaced, the digital twin can synchronously update the capability call relationships through the e-BOM structure without modifying the composite element model definition, thereby ensuring the consistency between the digital twin and the physical entity structure and reducing model maintenance costs.

[0036] Figure 3 This is a flowchart illustrating an element metadata modeling method provided in another embodiment of the present invention, as shown below. Figure 3 As shown, in this embodiment, the method includes steps S210-S270, and steps S210-S250 are the same as steps S110-S150. That is, in this embodiment, the method further includes steps S260-S270 after step S250.

[0037] S260. Before the sub-element template or the composite element template is saved or published, or before the sub-element model or the composite element model is saved or instantiated, perform circular reference detection on the reference relationship between the sub-element template, the composite element template, the sub-element model and the composite element model. S270. If a circular reference exists, the save, publish, or instantiation operation is prohibited, and the circular reference path information is output.

[0038] In this embodiment, circular reference detection is a key verification mechanism to ensure the legality of template and model structures. Detection occurs before saving or publishing sub-element templates or composite element templates, or before saving or instantiating sub-element models or composite element models. The detection targets include the reference relationships between sub-element templates, composite element templates, sub-element models, and composite element models, with a focus on detecting whether a closed-loop dependency is formed when a composite element template references other composite element templates through a sub-e-BOM template. It should be noted that circular reference detection uses a graph traversal algorithm to construct a directed graph of reference relationships between templates or models, detecting whether a path originating from a node, traversing several reference edges, and returning to that node exists. If a circular reference exists, saving, publishing, or instantiation operations are prohibited, and the circular reference path information is output, such as template A → template B → template C → template A, to help locate the root cause of the problem. Furthermore, the technical effect of circular reference detection is to prevent infinite loops in structure unfolding, instance generation, and activity orchestration caused by circular dependencies between templates or models; and to detect and block erroneous references at an early stage, reducing the cost of later repairs. Ensure consistency between the digital twin and the physical entity structure to avoid the model failing to be instantiated or executed correctly due to circular references.

[0039] Figure 4 A flowchart illustrating an element metadata modeling method provided in another embodiment of the present invention is shown below. Figure 4 As shown, in this embodiment, the method includes steps S310-S390, and steps S310-S350 are the same as steps S110-S150. That is, in this embodiment, the method further includes steps S360-S390 after step S350.

[0040] S360. When the lifecycle activity model is saved or published, the target object node in the lifecycle activity model is parsed to determine the target sub-element model. S370. Read the set of atomic capability identifiers configured in the capability definition node of the target sub-element model, and detect whether the capability identifier declared by the capability reference node exists in the set of atomic capability identifiers; S380. If the capability identifier declared by the capability reference node exists in the atomic capability identifier set, then save or publish the lifecycle activity model. S390. If the capability identifier declared by the capability reference node does not exist in the atomic capability identifier set, then the saving or publishing of the lifecycle activity model is prevented, and an exception message is output.

[0041] In this embodiment, capability reference verification is a key verification mechanism to ensure the legality of the lifecycle activity model. Verification occurs when the lifecycle activity model is saved or published, ensuring capability validity verification is completed before the activity goes live. The verification steps include: First, parsing the target node in the lifecycle activity model to determine the target sub-element model. The target node records the target element path, BOM node ID, and sub-element template ID; parsing this information allows locating the specific sub-element model. Second, reading the set of atomic capability identifiers configured in the capability definition node of the target sub-element model. This set contains the capabilityId of all atomic capabilities defined in the sub-element model. Then, determining whether the capability identifier declared by the capability reference node exists in the set of atomic capability identifiers. If the capability identifier declared by the capability reference node exists in the set of atomic capability identifiers, it means the capability referenced by the lifecycle activity is correctly defined in the target sub-element model, allowing the lifecycle activity model to be saved or published. If the capability identifier declared by the capability reference node does not exist in the set of atomic capability identifiers, it means the lifecycle activity references an undefined or incorrect capability, preventing the saving or publication of the lifecycle activity model and outputting an error message, such as "Capability identifier XXX is not defined in the target sub-element model," to help locate the root cause of the problem. It should be noted that the technical effects of capability reference verification are: preventing lifecycle activities from referencing non-existent or incorrect capabilities, thus avoiding activity execution failures; detecting and blocking capability reference errors in the early stages, reducing later repair costs; and ensuring that the capability source corresponds to the physical structure. When physical devices undergo component replacement, capability reference verification can simultaneously verify the capability definition of the new component, thereby ensuring the consistency between the digital twin and the physical entity structure.

[0042] To facilitate understanding, taking a smart pumping station in an industrial setting as an example, the specific implementation process of the element metadata modeling method is explained as follows: A smart pumping station is a complex device assembled from multiple atomic physical components, including sensors, actuators, controllers, protective housings, and support structures. First, sub-element templates are created, including templates for temperature sensors, pressure sensors, electric valves, pump motors, and PLC controllers. The capabilities field of each sub-element template is configured with atomic capability definitions, such as temperature reading, pressure reading, valve opening, valve closing, motor starting, motor stopping, data acquisition, and command issuance. Each capability includes attributes such as capabilityId, capabilityType, name, inputSchema, and outputSchema.

[0043] Then, a composite element template for the intelligent pumping station is created, and the e-BOM structure is organized by assembling structural nodes, including four types of fixed assembly modules. The protection module is attached to the protective shell template, the support module is attached to the base bracket template, the control module is attached to the PLC controller template, and the execution module is attached to the temperature sensor, pressure sensor, electric valve, and water pump motor templates. Each attachment node is configured with constraints, such as quantity constraints and position constraints. Before saving or publishing the composite element template, a circular reference check is performed to detect whether closed-loop dependencies exist between templates. If a circular reference exists, saving is prohibited, and the circular reference path information is output. In this embodiment, the intelligent pumping station template does not reference other composite element templates, and the check passes.

[0044] Subsequently, when creating instance models based on the template, child element models copy the capabilities field and assign modelId and actual parameters, while composite element models copy the assemblyModules field and assign assembly position parameters. A lifecycle activity model is created for the intelligent pump station, such as periodic inspection activities, using a six-dimensional structure. The time dimension is defined as a daily 8 AM scheduled trigger; the organization dimension is defined as maintenance personnel permissions; the space dimension is defined as the equipment site; the state dimension is defined as switching from running state to inspection state; the object dimension points to temperature and pressure sensor instances; and the capability dimension declares temperature and pressure reading capabilities.

[0045] Finally, capability reference verification is performed when saving or publishing the lifecycle activity model. The target sub-element model is located by parsing the target node, and the set of atomic capability identifiers in its capabilities field is read. The existence of the capability identifiers declared by the capability reference node in the set is checked. If they exist, saving is allowed; otherwise, saving is prevented and an exception message is output. When the temperature sensor of the smart pump station is replaced, only the modelId and actual parameters of the sub-element model instance are updated; the capabilities field remains unchanged, the e-BOM structure synchronously reflects the change, and the capability references of the lifecycle activity do not need to be modified. The digital twin maintains consistency with the physical entity structure, the source of capabilities is clearly traceable, and seamless synchronization is achieved when components are replaced.

[0046] The element metadata modeling method in this invention has the following beneficial effects: By establishing a hierarchical model of element templates, distinguishing between molecular element models and composite element models, the modeling dimensions of atomic physical components and complex equipment are separated, solving the problem that traditional flat models cannot express multi-level material composition relationships. By configuring atomic capabilities in the capability definition nodes of sub-element models, capability attribution is clear and traceable, avoiding the problem of unclear capability sources caused by centralized definition of whole-machine capabilities in traditional technologies. By organizing the e-BOM structure in the assembly structure nodes of the composite element model, the assembly relationship of the digital twin is consistent with the physical entity, supporting multi-level recursive assembly. Through the target node and capability reference node of the lifecycle activity model, business activities can be precisely applied to the specified BOM granularity, achieving a strong association between activities and equipment structure. Through circular reference detection and capability reference verification mechanisms, erroneous references are detected and blocked during the saving or publishing phase, preventing infinite loops and activity execution failures. When physical equipment undergoes component replacement or partial repair, the digital twin can be synchronously updated through the e-BOM structure, and the capability call relationship is automatically kept valid without modifying templates and activity definitions, reducing model maintenance costs and ensuring the consistency between the digital twin and the physical entity structure.

[0047] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0048] The software tools or components not belonging to our company that appear in the embodiments of this application are merely examples and do not represent actual use.

[0049] In one embodiment, an element metadata modeling device 200 is provided, which corresponds one-to-one with the element metadata modeling method in the above embodiments. As shown in Figure 5, the element metadata modeling device 200 includes a creation unit 201, a configuration unit 202, an organization unit 203, a definition creation unit 204, and an arrangement unit 205. Detailed descriptions of each functional module are as follows: Establishment unit 201 is used to establish an element template hierarchical model, wherein the element template hierarchical model includes a sub-element model and a composite element model; Configuration unit 202 is used to configure atomic capabilities in the sub-element model through capability definition nodes; Organization unit 203 is used to organize the e-BOM structure in the composite element model through assembly structure nodes; Establish definition unit 204 for establishing a lifecycle activity model and defining the target node and capability reference node of the lifecycle activity model, wherein the target node points to the sub-element model in the e-BOM structure, and the capability reference node references the atomic capability of the sub-element model; The orchestration unit 205 is used to orchestrate the atomic capabilities based on the target node and the capability reference node to form the capability call relationship of the composite element model.

[0050] In one embodiment, the establishment unit 201 is specifically used for: The atomic physical components that cannot be further divided or do not need to be further divided are defined as the sub-element model; The complex device assembled from multiple sub-element models or sub-e-BOM templates is defined as the composite element model, wherein the sub-e-BOM template is the engineering assembly structure template of the lower-level composite element model.

[0051] In one embodiment, the definition unit 204 is specifically used for: Based on the business activities of the sub-element model or the composite element model in the life cycle stage, a six-dimensional structure is used to describe the business activities to obtain the life cycle activity model, wherein the six-dimensional structure includes time dimension, organization dimension, space dimension, state dimension, object dimension and capability dimension.

[0052] In one embodiment, the element metadata modeling apparatus 200 further includes: The first detection unit is used to perform circular reference detection on the reference relationship between the sub-element template, the composite element template, the sub-element model and the composite element model before the sub-element template or the composite element template is saved or published, or before the sub-element model or the composite element model is saved or instantiated. The first output unit is used to prevent the execution of the save, publish, or instantiation operation if a circular reference exists, and to output the circular reference path information; The parsing unit is used to parse the target object node in the lifecycle activity model when the lifecycle activity model is saved or published, so as to determine the target sub-element model. The second detection unit is used to read the set of atomic capability identifiers configured in the capability definition node of the target sub-element model, and to detect whether the capability identifier declared by the capability reference node exists in the set of atomic capability identifiers. The save and publish unit is used to save or publish the lifecycle activity model if the capability identifier declared by the capability reference node exists in the atomic capability identifier set; The second output unit is used to prevent saving or publishing the lifecycle activity model and output an exception message if the capability identifier declared by the capability reference node does not exist in the atomic capability identifier set.

[0053] The aforementioned element metadata modeling device can be implemented as a computer program, which can, for example... Figure 6 It runs on the computer device shown.

[0054] Please see Figure 6 , Figure 6 This is a schematic block diagram of a computer device provided in an embodiment of the present invention. The computer device 300 is a device capable of performing element metadata modeling.

[0055] See Figure 6 The computer device 300 includes a processor 302, a memory, and a network interface 305 connected via a system bus 301. The memory may include a non-volatile storage medium 303 and internal memory 304.

[0056] The non-volatile storage medium 303 can store an operating system 3031 and a computer program 3032. When the computer program 3032 is executed, it causes the processor 302 to execute an element metadata modeling method.

[0057] The processor 302 provides computing and control capabilities to support the operation of the entire computer device 300.

[0058] The internal memory 304 provides an environment for the execution of the computer program 3032 in the non-volatile storage medium 303. When the computer program 3032 is executed by the processor 302, the processor 302 can execute an element metadata modeling method.

[0059] This network interface 305 is used for network communication with other devices. Those skilled in the art will understand that... Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present invention and does not constitute a limitation on the computer device 300 to which the present invention is applied. The specific computer device 300 may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0060] The processor 302 is used to run a computer program 3032 stored in a memory to implement any embodiment of the above-described element metadata modeling method.

[0061] It should be understood that, in this embodiment of the invention, the processor 302 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. The general-purpose processor may be a microprocessor or any conventional processor.

[0062] It will be understood by those skilled in the art that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a storage medium, which is a computer-readable storage medium. The computer program is executed by a processor in the computer system to implement the process steps of the embodiments of the above methods.

[0063] Therefore, the present invention also provides a storage medium. This storage medium can be a computer-readable storage medium. The storage medium stores a computer program. When executed by a processor, the computer program causes the processor to perform any embodiment of the above-described element metadata modeling method.

[0064] The storage medium can be any computer-readable storage medium capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory (ROM), magnetic disk, or optical disk.

[0065] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0066] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0067] The steps in the method of this invention can be adjusted, merged, or reduced in order according to actual needs. The units in the device of this invention can be merged, divided, or reduced according to actual needs. Furthermore, the functional units in the various embodiments of this invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0068] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device to execute all or part of the steps of the methods described in the various embodiments of the present invention.

[0069] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0070] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Since these modifications and variations fall within the scope of the claims and their equivalents, this invention also intends to include these modifications and variations.

[0071] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for modeling element metadata, characterized in that, include: Establish a hierarchical model of element templates, which includes a sub-element model and a composite element model; In the sub-element model, atomic capabilities are configured through capability definition nodes; In the composite element model, the e-BOM structure is organized through assembly structure nodes; Establish a lifecycle activity model and define the target node and capability reference node of the lifecycle activity model, wherein the target node points to the sub-element model in the e-BOM structure, and the capability reference node references the atomic capability of the sub-element model; The atomic capabilities are arranged based on the target node and the capability reference node to form the capability call relationship of the composite element model.

2. The element metadata modeling method as described in claim 1, characterized in that, The steps for establishing a hierarchical model of element templates include: The atomic physical components that cannot be further divided or do not need to be further divided are defined as the sub-element model; The complex device assembled from multiple sub-element models or sub-e-BOM templates is defined as the composite element model, wherein the sub-e-BOM template is the engineering assembly structure template of the lower-level composite element model.

3. The element metadata modeling method as described in claim 1, characterized in that, The sub-element model is created based on the sub-element template, and the composite element model is created based on the composite element template. Both the sub-element template and the composite element template have a template identifier and a template name. The steps of creating the sub-element model based on the sub-element template include: copying the atomic capabilities configured in the capability definition node of the sub-element template to the capability definition node of the sub-element model, and assigning a model identifier and actual parameters to the sub-element model; The steps of creating the composite element model based on the composite element template include: copying the e-BOM structure organized in the assembly structure node of the composite element template to the assembly structure node of the composite element model, and assigning a model identifier and assembly position parameters to the composite element model.

4. The element metadata modeling method as described in claim 3, characterized in that, The assembly structure node includes multiple fixed assembly modules. The sub-element template or sub-e-BOM template is attached to the fixed assembly module through a hooking node, and constraints are configured for the hooking node. The sub-e-BOM template is the assembly structure part of the lower-level composite element template and is used to express multi-level recursive assembly relationships.

5. The element metadata modeling method as described in claim 3, characterized in that, The method further includes: Before the sub-element template or the composite element template is saved or published, or before the sub-element model or the composite element model is saved or instantiated, a circular reference detection is performed on the reference relationship between the sub-element template, the composite element template, the sub-element model and the composite element model; If a circular reference exists, the save, publish, or instantiation operations are prohibited, and the circular reference path information is output.

6. The element metadata modeling method as described in claim 1, characterized in that, The steps for establishing a lifecycle activity model include: Based on the business activities of the sub-element model or the composite element model in the life cycle stage, a six-dimensional structure is used to describe the business activities to obtain the life cycle activity model, wherein the six-dimensional structure includes time dimension, organization dimension, space dimension, state dimension, object dimension and capability dimension.

7. The element metadata modeling method according to any one of claims 1 to 6, characterized in that, The method further includes: When the lifecycle activity model is saved or published, the target object node in the lifecycle activity model is parsed to determine the target sub-element model; Read the set of atomic capability identifiers configured in the capability definition node of the target sub-element model, and check whether the capability identifier declared by the capability reference node exists in the set of atomic capability identifiers; If the capability identifier declared by the capability reference node exists in the atomic capability identifier set, then the lifecycle activity model is saved or published; If the capability identifier declared by the capability reference node does not exist in the atomic capability identifier set, then saving or publishing the lifecycle activity model will be prevented, and an exception message will be output.

8. An element metadata modeling device, characterized in that, include: Establishment unit, used to establish element template hierarchical model, wherein the element template hierarchical model includes sub-element model and composite element model; Configuration unit, used to configure atomic capabilities in the sub-element model through capability definition nodes; Organizational units are used to organize the e-BOM structure in the composite element model through assembly structure nodes; A definition unit is established to establish a lifecycle activity model and to define the target node and capability reference node of the lifecycle activity model, wherein the target node points to the sub-element model in the e-BOM structure and the capability reference node references the atomic capability of the sub-element model; The orchestration unit is used to orchestrate the atomic capabilities based on the target node and the capability reference node to form the capability call relationship of the composite element model.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the element metadata modeling method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the element metadata modeling method as described in any one of claims 1 to 7.

Images