Graphical configuration method and system for data relationship among multiple entities

Abstract

The invention relates to the technical field of graphical configuration, and discloses a graphical configuration method and system for a data relationship among multiple entities, and the method comprises the steps: importing a plurality of control entities into a graphical interface, and distributing a unique entity identification number for each control entity; in response to a user operation, creating published data objects for the selected control entity, each published data object comprising a unique data object identification number and a user-defined attribute; associating a published data object of the source control entity to a target control entity through a dragging operation, automatically generating a corresponding subscription data object in the target control entity, and establishing a visual connection line; when the user edits and selects the control entity, the control entity is automatically locked and other users are forbidden to edit until the editing operation is finished, so that the graphical configuration system for the data relationship among the multiple entities is realized, the unique identification number of the data object and the interlocking rule of the data object are formulated, and the action refusal when a logic error occurs is ensured; and a solution is provided for multiple entities to use data.

Description

Technical Field

[0001] This invention relates to the field of graphical configuration technology, and in particular to a graphical configuration method and system for data relationships between multiple entities. Background Technology

[0002] With the deepening of the intelligent manufacturing wave, modern industrial control systems are undergoing a major transformation from centralized to distributed architecture. In complex application scenarios such as communication systems and industrial automation devices, multi-agent collaborative control has become a core paradigm for improving system flexibility and response efficiency. Traditional industrial control systems evolved from the early master-slave centralized control model, and their data interaction mechanism mainly relies on network variable transmission technology. This communication method based on predefined address mapping, while stable in simple topologies, is difficult to adapt to the ever-increasing demand for distributed control. When the system scales up to dozens or even hundreds of control entities (such as PLCs, edge computing nodes, and smart sensors), the data dependencies between entities become exponentially more complex. Engineers have to define variable addresses, data types, and transmission cycles one by one through tedious text tables, and then use offline configuration tools to burn the parameters to each independent device. This "back-to-back" configuration mode is essentially an extension of the single-machine era—even though modern development environments provide multi-window parallel user interfaces, the underlying logic still requires engineers to repeatedly switch between discrete configuration windows and manually check variable mapping relationships, like searching for clues in a fragmented jigsaw puzzle.

[0003] A more serious challenge lies in the lack of real-time collaboration capabilities. Existing configuration tools generally lack multi-user collaboration support, and parameter coverage conflicts are highly likely to occur when multiple engineers debug different subsystems in parallel. The root causes of this problem are: First, the lack of intuitive expression of data sharing relationships. Text lists and programming scripts cannot clearly show the global topology of "which controller generates data and which controllers consume data." Engineers must cross-reference multiple documents to clarify the data flow, with 40% of debugging time consumed in the relationship analysis stage. Second, weak error prevention mechanisms. Existing systems lack the ability to pre-detect risks such as "multiple sources writing to the same variable" and "implicit data type conversion errors." Errors are often only exposed at runtime, extending the on-site debugging cycle by 30%-50%. Third, difficulty in dynamic expansion. Adding new control entities requires manual reconstruction of the global variable address table, and the scope of impact of changes is difficult to assess.

[0004] While modern communication protocols such as OPC UA attempt to improve interoperability through information model standardization, their configuration processes still heavily rely on specialized programming skills, failing to address the "last mile" problem of engineering usability. Although recent research has attempted to introduce graphical configuration methods, these are mostly limited to single-entity internal logic design (such as ladder diagram programming), lacking a systematic solution to the critical pain point of cross-entity data relationship collaboration. This technological gap is becoming a bottleneck restricting the implementation of distributed systems such as flexible manufacturing and smart grids—when control systems need to dynamically respond to order changes or equipment status, the reconstruction costs and risks of traditional configuration models are unbearable. Therefore, a new configuration paradigm that can intuitively present multi-entity data relationships, support collaborative editing, and possess self-verification capabilities is urgently needed, which is the starting point for the technological breakthrough of this invention. Summary of the Invention

[0005] The purpose of this invention is to address the shortcomings of the existing technology by providing a graphical configuration method and system for data relationships between multiple entities. It introduces the concept of a data object, visualizing the data to be published as a data object. Control entities generate data objects and publish them to the control entities using the data, establishing a visual association between them. Furthermore, this invention establishes a locking mechanism for multi-user use; the control entity being edited by the current user is automatically locked and marked, preventing other users from editing it, thus avoiding potential unintended modifications.

[0006] On the one hand, a graphical configuration method for data relationships between multiple entities is provided, including the following steps: S1: Import multiple control entities into the graphical interface. The control entities include PLC controllers, edge computing nodes, and intelligent sensing devices, and assign a unique entity identifier to each control entity. S2: In response to production line configuration requirements, select the source control entity in the imported control entities and create a published data object for it. The published data object is presented in the form of draggable primitives. Each published data object contains a unique data object identifier with industrial semantics and user-defined attributes. S3: By dragging and dropping, the published data object of the source control entity is associated with the target control entity. The corresponding subscription data object is automatically generated in the target control entity, and the subscription data object is integrated into the target entity in the form of splicable primitives, and a visual connection of real-time data flow is established. Specifically, when a user edits the production line control logic and selects a control entity, the control entity is automatically locked and other users are prohibited from editing it until the editing operation is completed.

[0007] Further, in step S1, importing multiple source control entities into the graphical interface includes: The graphical interface includes a list of control entity objects and a configuration area, which provide a production line topology layer and control the automatic layout of entities according to their physical locations. Import several control entities in the configuration area of ​​the graphical interface by dragging and dropping. Click on the required control entities to create or edit and publish data objects for them.

[0008] Further, in step S3, the association specifically includes: S31: In response to the drag-and-drop operation start command, apply a cross-device operation lock to the source control entity and the target control entity, lock the entity pair formed by the source control entity and the target control entity, and generate an operation log with a timestamp. S32: Drag and drop the target data object from the list of published data objects of the source control entity to the target control entity; S33: Automatically generate a list of subscribed data objects in the target control entity. The subscribed data objects are integrated and displayed in the form of splicable elements that are visually associated with the published elements. Establish dynamic visual connections and record the data object attributes and source entity identifiers. S34: Automatically configure the range rules and security level rules for subscribed data objects based on the attributes of published data objects.

[0009] Further, in step S2, creating and publishing the data object includes: After adding published data objects, the source control entity automatically generates an entity published data object list and a system data object resource table, and names each data object with an alias according to control and management requirements. The list of published data objects declares the number, length, and publication cycle of the data objects. The system-level data object resource table includes records of the lifetime threshold, version number, and cross-network segment routing identifier of global data objects.

[0010] Preferably, the published data object includes data element attributes and data object attributes; The data element attributes include a list of data elements with engineering units and a format definition; The user-defined attributes of the data object include the periodic release strategy for dead zone management, the source control entity identifier, and user-defined attributes.

[0011] In step S33, the dynamic visualization connection maps the data stream status in real time. Different connection color changes are used to represent the data transmission status, which includes normal transmission, data update delay exceeding a threshold, and communication interruption.

[0012] Further, in step S31, the cross-device operation lock includes: Other users are prohibited from editing the data objects of the source control entity and the target control entity, and are also prohibited from modifying the system-level data object resource table associated with the source control entity. The lock remains in effect until the drag-and-drop operation is complete and the subscribed data object passes validation.

[0013] Preferably, step S3 further includes: When deleting the subscription data object, the subscription data object element in the target control entity is removed by dragging and dropping, and the association verification is triggered. If the object is referenced by the control logic, a breakpoint report is forcibly generated. When the published data object is deleted, all associated subscribed data objects are automatically unlinked, and an industrial-grade failure command is sent to all subscribed entities to activate the preset security value.

[0014] More preferably, each of the control entities includes at least one dual-channel heartbeat broadcast data object for broadcasting the liveness and working status of the control entity, wherein the main channel broadcasts the device liveness and CPU load rate, and the backup channel transmits fault codes and event sequence records (SOE).

[0015] Furthermore, the entity identifier includes a device location code, with the coding rule being: production line number - workstation number - device type code. The entity identifier is automatically incremented according to the import order.

[0016] Furthermore, in step S34, the range rule includes: a single subscription data object is only allowed to be associated with one published data object, and a single published data object is allowed to be associated with multiple subscription data objects; The security level rules include: the security level of the subscribed data object must be higher than that of the published data object; When a rule conflict occurs in a data object association operation, a tiered alert is triggered and the operation is prohibited. A Level 1 rule conflict indicates a range exceeding limits. If the range rule is not met, data scaling will be forced and a warning will be displayed. Level 2 rule conflicts result in a security level downgrade. If the security level rules are not met, the association will be immediately blocked and the security PLC will be notified.

[0017] On the other hand, a graphical configuration system for data relationships between multiple entities is provided, including: The entity configuration initialization module is used to import multiple control entities into the graphical interface. The control entities include PLC controllers, edge computing nodes and intelligent sensing devices, and assign a unique entity identifier to each control entity. The data object definition module is used to select a source control entity from the imported control entities in response to production line configuration requirements and create a published data object for it. The published data object is presented in the form of draggable primitives. Each published data object contains a unique data object identifier with industrial semantics and user-defined attributes. The visualization relationship building module is used to associate the published data objects of the source control entity with the target control entity through drag-and-drop operations, automatically generate the corresponding subscription data objects in the target control entity, integrate the subscription data objects into the target entity in the form of splicable primitives, and establish a visual connection for the real-time data flow. The collaborative editing lock module is used to automatically lock the control entity and prevent other users from editing it when a user is editing the production line control logic and selecting the control entity, until the editing operation is completed.

[0018] In addition, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the graphical configuration method for data relationships between multiple entities as described in any of the preceding claims.

[0019] Meanwhile, an electronic device is provided, comprising: one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement the graphical configuration method for data relationships between multiple entities as described above.

[0020] Compared with the prior art, the beneficial effects of the present invention are: This invention defines data objects among multiple control entities within a system and establishes a mechanism for many-to-many sharing relationships between data objects among entities, thereby achieving a unified definition of data within a system and solving the problem of cumbersome definition for data sharing among entities. This invention visualizes data objects as draggable and splicable graphic elements, enabling a WYSIWYG view of data object attributes. Then, it uses a connection method to visually design the subscription relationship of data objects, establishing a visual association between data object producers and consumers, achieving WYSIWYG, improving configuration efficiency, and facilitating error finding. This invention prevents errors by restricting the operations of other users and establishing rules for sharing data objects when the current user is editing one or more control entities. Attached Figure Description

[0021] The accompanying drawings are provided to further illustrate the invention and form part of the specification. They are used in conjunction with embodiments of the invention to explain the invention and do not constitute a limitation thereof. In the drawings: Figure 1This is a flowchart of a graphical configuration method for data relationships between multiple entities according to the present invention; Figure 2 This is an example diagram of a graphical interface of the present invention; Figure 3 This is a schematic diagram of a data object attribute according to the present invention; Figure 4 This is a schematic diagram illustrating the relationship between a subscription data object and a publish data object according to the present invention; Figure 5 This is a schematic diagram illustrating the operation flow of a graphical configuration method for overall multi-entity data relationships according to the present invention. Figure 6 This is a schematic diagram of a graphical configuration system for data relationships between multiple entities according to the present invention. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0023] This invention addresses the massive data interaction needs among multiple control entities in multi-agent collaborative control systems. It considers the problems of conventional list-based and programming-based methods, such as unintuitive data sharing, susceptibility to errors, and exponentially increasing debugging workload. It employs a graphical, visual interface to intuitively configure data sharing relationships. Furthermore, this invention introduces the concept of data objects, allowing shared data to be organized according to data objects through drag-and-drop, with simultaneous declarations between data producers and users. To reduce the possibility of human error, this invention also establishes unique identifiers for data objects and interlocking rules for data objects, ensuring that users are prevented from operating and receive error messages when logical errors occur, providing a comprehensive solution for data usage by multiple entities.

[0024] In this invention, the control entity includes both data producers and consumers, and is composed of an actual controller or a virtual program. The control entity is the bearer of data objects; A published data object is a data fragment, the smallest unit used by a control entity to publish data. It consists of a data object ID, alias, data, and data description. A published data object is generated by a source control entity and published to one or more target control entities through communication. The target control entities use the data of the published data object by running control logic. A data object is a data fragment, the smallest unit used for data interaction between control entities, and each data object has a unique identifier. Control entities must provide this unique identifier when using data object data. Each data object can independently define its sending and receiving mechanisms, thereby minimizing the impact of sending and receiving actions on the control entity. A subscribed data object is a data fragment, the smallest unit used by a control entity to obtain real-time data from other source control entities. Each subscribed data object is generated by a unique source control entity and is the source control entity's published data object. The list of published data objects is a list of data objects that the controlling entity generates to publish. It is used to declare information such as the number of data objects that the controlling entity will publish, the length of each data object, and the publication cycle. The list of subscribed data objects is a list of data objects that the controlling entity is prepared to receive. It is used to declare information such as the number of data objects from other controlling entities used by the controlling entity, the length of each data object, and the publication cycle.

[0025] The specific embodiments of the present invention will be described below with reference to the accompanying drawings and examples.

[0026] Example 1 The specific configuration method of this invention involves allocating data objects among multiple collaboratively operating control entities via connections within a graphical interface. The graphical interface consists of at least two control entities that generate or use data. Each control entity allows the user to create or edit published data objects as needed, providing the published data objects. For example... Figure 1 As shown in this embodiment, a graphical configuration method for data relationships between multiple entities is provided, comprising the following steps: S1: Import multiple control entities into the graphical interface. The control entities include PLC controllers, edge computing nodes, and intelligent sensing devices, and assign a unique entity identifier to each control entity. S2: In response to production line configuration requirements, select the source control entity in the imported control entities and create a published data object for it. The published data object is presented in the form of draggable primitives. Each published data object contains a unique data object identifier with industrial semantics and user-defined attributes. S3: By dragging and dropping, the published data object of the source control entity is associated with the target control entity. The corresponding subscription data object is automatically generated in the target control entity, and the subscription data object is integrated into the target entity in the form of splicable primitives, and a visual connection of real-time data flow is established. Specifically, when a user edits the production line control logic and selects a control entity, the control entity is automatically locked and other users are prohibited from editing it until the editing operation is completed.

[0027] First, in step S1, the graphical interface is as follows: Figure 2 As shown, importing multiple source control entities into the graphical interface further includes: The graphical interface includes a list of control entity objects and a configuration area, which provide a production line topology layer and control the automatic layout of entities according to their physical locations. Import several control entities in the configuration area of ​​the graphical interface by dragging and dropping. Click on the required control entities to create or edit and publish data objects for them.

[0028] The entity identifier includes the equipment location code, and the coding rule is: production line number - workstation number - equipment type code. The entity identifier is automatically incremented according to the import order.

[0029] In this embodiment, after the control entity is dragged into the configuration area using the mouse, a 16-bit entity identifier is automatically assigned. The entity identifier starts from 1 and automatically increments by 1 for each address dragged.

[0030] Next, in step S2, the creation of the published data object further includes: After adding published data objects, the source control entity automatically generates an entity published data object list and a system data object resource table, and names each data object with an alias according to control and management requirements. The list of published data objects declares the number, length, and publication cycle of the data objects. The system-level data object resource table includes records of the lifetime threshold, version number, and cross-network segment routing identifier of global data objects.

[0031] The published data object includes data element attributes and data object attributes; The data element attributes include a list of data elements with engineering units and a format definition; The user-defined attributes of the data object include the periodic release strategy for dead zone management, the source control entity identifier, and user-defined attributes.

[0032] Specifically, in this embodiment, the configuration control entity includes: After a control entity is dragged and dropped into the configuration area, it can be added to publish data objects by clicking on the control entity. Each control entity can have up to 65,535 published data objects added. This embodiment adopts a unified identifier allocation strategy for all data objects to avoid data object duplication. After a control entity adds published data objects, an entity's published data object list and a system data object resource table are automatically generated. Users can name each data object with an alias according to control management needs.

[0033] In addition, configuring data objects for control entities specifically includes: Each data object consists of two parts: data elements and attributes. Attributes are divided into data element attributes and data object attributes. Data element attributes include a list of data elements and their format. Data objects include publishing strategies (periodic publishing, event publishing, etc.), control entity identifiers, and up to 200 other custom attributes. When a control entity is dragged and dropped into the configuration area and selected by clicking the mouse, the control entity is locked by the current user and cannot be edited by others. The current user can add publishing data objects and modify the attributes of control data objects. Adding the first publishing data object to a control entity automatically creates a list of publishing data objects. The attributes of a data object are as follows: Figure 3 As shown.

[0034] Preferably, each control entity includes at least one dual-channel heartbeat broadcast data object for broadcasting the entity's liveness and operational status. The primary channel broadcasts the device liveness and CPU load rate, while the backup channel transmits fault codes and Event Sequence Records (SOEs). The remaining broadcast data objects are created by mouse selection.

[0035] Next, proceed with the drag-and-drop association in step S3, which specifically includes: S31: In response to the drag-and-drop operation start command, apply a cross-device operation lock to the source control entity and the target control entity, lock the entity pair formed by the source control entity and the target control entity, and generate an operation log with a timestamp. S32: Drag and drop the target data object from the list of published data objects of the source control entity to the target control entity; S33: Automatically generate a list of subscribed data objects in the target control entity. The subscribed data objects are integrated and displayed in the form of splicable elements that are visually associated with the published elements. Establish dynamic visual connections and record the data object attributes and source entity identifiers. S34: Automatically configure the range rules and security level rules for subscribed data objects based on the attributes of published data objects.

[0036] In step S31, the cross-device operation lock includes: Other users are prohibited from editing the data objects of the source control entity and the target control entity, and are also prohibited from modifying the system-level data object resource table associated with the source control entity. The lock remains in effect until the drag-and-drop operation is complete and the subscribed data object passes validation.

[0037] In step S33, the dynamic visualization connection maps the data stream status in real time. Different connection color changes are used to represent the data transmission status, which includes normal transmission, data update delay exceeding a threshold, and communication interruption.

[0038] Step S3 involves deleting the subscribed or published data object, specifically including: When deleting the subscription data object, the subscription data object is removed from the target control entity by dragging and dropping, and an association check is triggered. If the object is referenced by the control logic, a breakpoint report is forcibly generated. When the published data object is deleted, all associated subscribed data objects are automatically unlinked, and an industrial-grade failure command is sent to all subscribed entities to activate the preset security value.

[0039] Furthermore, in step S34, the range rules include: a single subscription data object is only allowed to be associated with one published data object, and a single published data object is allowed to be associated with multiple subscription data objects; The security level rules include: the security level of the subscribed data object must be higher than that of the published data object; When a rule conflict occurs in a data object association operation, a tiered alert is triggered and the operation is prohibited. A Level 1 rule conflict indicates a range exceeding limits. If the range rule is not met, data scaling will be forced and a warning will be displayed. Level 2 rule conflicts result in a security level downgrade. If the security level rules are not met, the association will be immediately blocked and the security PLC will be notified.

[0040] Specifically, in this embodiment, each control entity provides a list of subscribed data objects. This list is used to register the data objects required by the control entity to perform computational functions and to record the attributes of those data objects. The subscribed data list is created by dragging and dropping publishing data entities onto the target control entity.

[0041] The management setup process is as follows: Select one control entity as the source control entity and another as the target control entity. Once selected, the source and target control entities are immediately locked and highlighted in a different color on the interface. Other users cannot select these two control entities, nor can they select any data objects associated with these control entities in the data object summary table. The source control entity list displays the published data objects created by the user within that control entity. Users can establish data object relationships by dragging and dropping data objects onto the target control entity, simultaneously creating a list of subscribed data objects.

[0042] To prevent subscribed data objects from being modified by multiple source control entities, thus causing unexpected changes, each subscribed data object corresponds to only one published data object. However, a published data object can be simultaneously published to multiple subscribed data objects. The specific structure is as follows: Figure 4 As shown.

[0043] Secondly, the deletion of associations between control entity data objects includes: when a user deems a control entity's subscription data object no longer needed, they can select the control entity with the mouse. The control entity is then locked and displayed in a bright color on the interface, making it unselectable by other users. Users can then delete unwanted subscription data objects by dragging and dropping them with the mouse.

[0044] Deleting published data for a controlling entity involves the following steps: When a user deems a published data object for a controlling entity no longer needed, they can select the controlling entity with the mouse. The controlling entity is then locked and highlighted in a bright color on the interface, making it unselectable by other users. Users can also delete unwanted published data objects by dragging and dropping them with the mouse. Entities that used these data objects will automatically delete the deleted data object.

[0045] In summary, the specific configuration method of this invention involves allocating data objects among multiple collaboratively operating control entities via connections within a graphical interface. The graphical interface consists of at least two control entities that generate or use data. Each control entity allows the user to create or edit published data objects as needed. The specific operation steps of the entire process are as follows: Figure 5 As shown.

[0046] On the other hand, this embodiment also provides a graphical configuration system for data relationships between multiple entities, such as... Figure 6 As shown, it includes: The entity configuration initialization module is used to import multiple control entities into the graphical interface. The control entities include PLC controllers, edge computing nodes and intelligent sensing devices, and assign a unique entity identifier to each control entity. The data object definition module is used to select a source control entity from the imported control entities in response to production line configuration requirements and create a published data object for it. The published data object is presented in the form of draggable primitives. Each published data object contains a unique data object identifier with industrial semantics and user-defined attributes. The visualization relationship building module is used to associate the published data objects of the source control entity with the target control entity through drag-and-drop operations, automatically generate the corresponding subscription data objects in the target control entity, integrate the subscription data objects into the target entity in the form of splicable primitives, and establish a visual connection for the real-time data flow. The collaborative editing lock module is used to automatically lock the control entity and prevent other users from editing it when a user is editing the production line control logic and selecting the control entity, until the editing operation is completed.

[0047] It should be noted that the steps in the graphical configuration method for data relationships between multiple entities provided in this embodiment can be implemented based on the corresponding modules in the graphical configuration system for data relationships between multiple entities. Those skilled in the art can refer to the technical solution of the system to implement the steps of the method. That is, the embodiments in the system can be understood as preferred examples of implementing the method, and will not be elaborated here.

[0048] Besides implementing the system and its various devices provided by this invention in purely computer-readable program code, the same functions can be achieved by logically programming the method steps, making the system and its various devices of this invention appear as logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, the system and its various devices provided by this invention can be considered as a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component; alternatively, the devices for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0049] Finally, it should be noted that the above description is only a preferred embodiment of the present invention, and the scope of protection of the present invention is not limited to the above embodiments. All technical solutions falling within the scope of the present invention's concept are within the scope of protection of the present invention. It should be pointed out that for those skilled in the art, any improvements and modifications made without departing from the principle of the present invention should also be considered within the scope of protection of the present invention.

[0050] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

Claims

1. A graphical configuration method for data relationships between multiple entities, characterized in that, Includes the following steps: S1: Import multiple control entities into the graphical interface. The control entities include PLC controllers, edge computing nodes, and intelligent sensing devices, and assign a unique entity identifier to each control entity. S2: In response to production line configuration requirements, select the source control entity in the imported control entities and create a published data object for it. The published data object is presented in the form of draggable primitives. Each published data object contains a unique data object identifier with industrial semantics and user-defined attributes. S3: By dragging and dropping, the published data object of the source control entity is associated with the target control entity. The corresponding subscription data object is automatically generated in the target control entity, and the subscription data object is integrated into the target entity in the form of splicable primitives, and a visual connection of real-time data flow is established. Specifically, when a user edits the production line control logic and selects a control entity, the control entity is automatically locked and other users are prohibited from editing it until the editing operation is completed.

2. The graphical configuration method for data relationships between multiple entities according to claim 1, characterized in that, In step S1, importing multiple source control entities into the graphical interface further includes: The graphical interface includes a list of control entity objects and a configuration area, which provide a production line topology layer and control the automatic layout of entities according to their physical locations. Import several control entities in the configuration area of ​​the graphical interface by dragging and dropping. Click on the required control entities to create or edit and publish data objects for them.

3. The graphical configuration method for data relationships between multiple entities according to claim 1, characterized in that, In step S3, the association specifically includes: S31: In response to the drag-and-drop operation start command, apply a cross-device operation lock to the source control entity and the target control entity, lock the entity pair formed by the source control entity and the target control entity, and generate an operation log with a timestamp. S32: Drag and drop the target data object from the list of published data objects of the source control entity to the target control entity; S33: Automatically generate a list of subscribed data objects in the target control entity. The subscribed data objects are integrated and displayed in the form of splicable elements that are visually associated with the published elements. Establish dynamic visual connections and record the data object attributes and source entity identifiers. S34: Automatically configure the range rules and security level rules for subscribed data objects based on the attributes of published data objects.

4. The graphical configuration method for data relationships between multiple entities according to claim 2, characterized in that, In step S2, creating and publishing the data object further includes: After adding published data objects, the source control entity automatically generates an entity published data object list and a system data object resource table, and names each data object with an alias according to control and management requirements. The list of published data objects declares the number, length, and publication cycle of the data objects. The system-level data object resource table includes records of the lifetime threshold, version number, and cross-network segment routing identifier of global data objects.

5. The graphical configuration method for data relationships between multiple entities according to claim 4, characterized in that, The published data object includes data element attributes and data object attributes; The data element attributes include a list of data elements with engineering units and a format definition; The user-defined attributes of the data object include the periodic release strategy for dead zone management, the source control entity identifier, and user-defined attributes.

6. The graphical configuration method for data relationships between multiple entities according to claim 3, characterized in that, In step S33, the dynamic visualization connection maps the data stream status in real time. Different connection color changes are used to represent the data transmission status, which includes normal transmission, data update delay exceeding a threshold, and communication interruption.

7. The graphical configuration method for data relationships between multiple entities according to claim 3, characterized in that, In step S31, the cross-device operation lock includes: Other users are prohibited from editing the data objects of the source control entity and the target control entity, and are also prohibited from modifying the system-level data object resource table associated with the source control entity. The lock remains in effect until the drag-and-drop operation is complete and the subscribed data object passes validation.

8. The graphical configuration method for data relationships between multiple entities according to claim 3, characterized in that, Step S3 further includes: When deleting the subscription data object, the subscription data object element in the target control entity is removed by dragging and dropping, and the association verification is triggered. If the object is referenced by the control logic, a breakpoint report is forcibly generated. When the published data object is deleted, all associated subscribed data objects are automatically unlinked, and an industrial-grade failure command is sent to all subscribed entities to activate the preset security value.

9. The graphical configuration method for data relationships between multiple entities according to claim 4, characterized in that, Each of the control entities includes at least one dual-channel heartbeat broadcast data object for broadcasting the liveness and working status of the control entity. The main channel broadcasts the device liveness and CPU load rate, while the backup channel transmits fault codes and event sequence records (SOE).

10. The graphical configuration method for data relationships between multiple entities according to claim 1, characterized in that, The entity identifier includes the equipment location code, and the coding rule is: production line number - workstation number - equipment type code. The entity identifier is automatically incremented according to the import order.

11. The graphical configuration method for data relationships between multiple entities according to claim 3, characterized in that, In step S34, the range rules include: a single subscription data object is only allowed to be associated with one publishing data object, and a single publishing data object is allowed to be associated with multiple subscription data objects; The security level rules include: the security level of the subscribed data object must be higher than that of the published data object; When a rule conflict occurs in a data object association operation, a tiered alert is triggered and the operation is prohibited. A Level 1 rule conflict indicates a range exceeding limits. If the range rule is not met, data scaling will be forced and a warning will be displayed. Level 2 rule conflicts result in a security level downgrade. If the security level rules are not met, the association will be immediately blocked and the security PLC will be notified.

12. A graphical configuration system for data relationships between multiple entities, characterized in that, include: The entity configuration initialization module is used to import multiple control entities into the graphical interface. The control entities include PLC controllers, edge computing nodes and intelligent sensing devices, and assign a unique entity identifier to each control entity. The data object definition module is used to select a source control entity from the imported control entities in response to production line configuration requirements and create a published data object for it. The published data object is presented in the form of draggable primitives. Each published data object contains a unique data object identifier with industrial semantics and user-defined attributes. The visualization relationship building module is used to associate the published data objects of the source control entity with the target control entity through drag-and-drop operations, automatically generate the corresponding subscription data objects in the target control entity, integrate the subscription data objects into the target entity in the form of splicable primitives, and establish a visual connection for the real-time data flow. The collaborative editing lock module is used to automatically lock the control entity and prevent other users from editing it when a user is editing the production line control logic and selecting the control entity, until the editing operation is completed.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the graphical configuration method for data relationships between multiple entities as described in any one of claims 1-11.

14. An electronic device, characterized in that, include: One or more processors; A storage device for storing one or more programs, which, when executed by one or more processors, cause the one or more processors to implement a graphical configuration method for data relationships between multiple entities as described in any one of claims 1-11.

Images