A method and system for graphical configuration of data relationships among multiple entities

Abstract

The application relates to the technical field of graphical configuration, and discloses a kind of graphical configuration method and system of data relationship between multiple entities, comprising: importing several control entities in graphical interface, and allocating unique entity identification number for each control entity;In response to user operation, create publishing data object for selected control entity, each publishing data object contains unique data object identification number and user-defined attribute;Through drag operation, the publishing data object of source control entity is associated to target control entity, and the corresponding subscription data object is automatically generated in target control entity, and visual connection is established;When user edits selected control entity, the control entity is automatically locked and other users are prohibited from editing until the editing operation is completed, a kind of graphical configuration system of data relationship between multiple entities is realized, data object unique identification number is formulated, data object interlocking rule is guaranteed, and it is refused to move when logical error occurs, to provide solution for multiple entities using data.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of graphical configuration, and particularly relates to a graphical configuration method and system for data relationship among multiple entities. BACKGROUND

[0002] With the deepening of the tide of intelligent manufacturing, 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 the core paradigm to improve system flexibility and response efficiency. Traditional industrial control systems are derived from the early centralized control model of one master and multiple slaves, and their data interaction mechanism mainly relies on network variable transmission technology. This communication method based on pre-defined address mapping, although stable in simple topology, is difficult to adapt to the growing demand for distributed control. When the system scale expands to dozens or even hundreds of control entities (such as PLCs, edge computing nodes, and intelligent sensors), the data dependency relationship between entities becomes exponentially complex. Engineers have to define variable addresses, data types, and transmission periods one by one through tedious text tables, and then use offline configuration tools to burn 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 a multi-window parallel user interface, the underlying logic still requires engineers to repeatedly switch between discrete configuration windows and manually check variable mapping relationships, as if searching for associated clues in a broken jigsaw puzzle.

[0003] The more serious challenge is the lack of real-time collaboration capability. Existing configuration tools generally lack multi-user collaboration support, and when multiple engineers debug different subsystems in parallel, parameter override conflicts are likely to occur. The root of this problem is as follows: first, the data sharing relationship lacks intuitive expression. Text lists and programming scripts cannot clearly show the global topology of "which controller produces data and which controller consumes data", and engineers must cross-check multiple documents to clarify the data flow, with 40% of the debugging time consumed in relationship sorting. Second, the error-proofing mechanism is weak. Existing systems lack pre-checking capabilities for risks such as "multiple sources writing to the same variable" and "data type implicit conversion errors", and errors are often exposed at runtime, extending the on-site debugging period by 30%-50%. Third, dynamic expansion is difficult. New control entities need to be manually reconstructed with global variable address tables, and the scope of changes is difficult to assess.

[0004] Although modern communication protocols such as OPC UA attempt to improve interoperability through information model standardization, their configuration processes still heavily rely on professional programming skills and fail to address the engineering usability problem of the "last mile". In recent years, although some research attempts to introduce graphical configuration means, they are mostly limited to single entity internal logic design (such as ladder diagram programming), and there is still no systematic solution to the key pain point of cross-entity data relationship collaboration. This technical gap is becoming a bottleneck restricting the landing of distributed systems such as flexible manufacturing and smart grid - when the control system needs to dynamically respond to order changes or equipment status, the reconstruction cost and risk of traditional configuration mode are difficult to bear. Therefore, a new configuration paradigm that can intuitively present multi-entity data relationships, support collaborative editing, and have self-validation capabilities is urgently needed, which is the starting point for the breakthrough of the present invention. SUMMARY

[0005] The purpose of the present application is to solve the above-mentioned shortcomings in the prior art, and to provide a graphical configuration method and system for data relationship between multiple entities. The data object concept is introduced, and the data to be published is materialized as a data object. The control entity generates the data object and publishes it to the control entity that uses the data. The connection between the two establishes a visual association. At the same time, the present application establishes a locking mechanism for multiple users. The control entity being edited by the current user is automatically locked and identified, and other users cannot edit it, thereby avoiding unintended modifications.

[0006] In one aspect, a graphical configuration method for data relationship between multiple entities is provided, comprising the following steps:

[0007] S1: importing multiple control entities in a graphical interface, the control entities including PLC controllers, edge computing nodes and intelligent sensing devices, and assigning a unique entity identification number to each control entity;

[0008] S2: selecting a source control entity from the imported control entities in response to production line configuration requirements, and creating a published data object for the source control entity, the published data object being presented in the form of a draggable graphic element, each published data object containing a unique data object identification number with industrial semantics and user-defined attributes;

[0009] S3: associating the published data object of the source control entity to a target control entity through a dragging operation, and automatically generating a corresponding subscription data object in the target control entity, so that the subscription data object is integrated into the target entity in the form of a splicable graphic element, and a visual connection of real-time data flow is established;

[0010] Wherein, 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 until the editing operation is completed.

[0011] Further, in step S1, the importing a plurality of source control entities in the graphical interface comprises:

[0012] The graphical interface comprises a control entity object list and a configuration area to provide a production line topology layer, and the control entities are automatically laid out according to physical positions;

[0013] A plurality of control entities are imported in the configuration area of the graphical interface through a drag operation, and a desired control entity is clicked to newly create or edit a publishing data object according to a requirement.

[0014] Further, in step S3, the associating specifically comprises:

[0015] S31: in response to a drag operation starting instruction, applying a cross-device operation lock to the source control entity and the target control entity, locking the entity pair formed by the source control entity and the target control entity, and generating an operation log with a time stamp;

[0016] S32: dragging a target data object from a publishing data object list of the source control entity to the target control entity;

[0017] S33: automatically generating a subscription data object list in the target control entity, integrating and displaying the subscription data object in the form of a splicable graph element visually associated with the publishing graph element, establishing a dynamic visual connection, and recording data object attributes and source entity identification numbers;

[0018] S34: automatically configuring a range rule and a security level rule of the subscription data object based on attributes of the publishing data object.

[0019] Further, in step S2, the creating a publishing data object comprises:

[0020] The source control entity automatically forms an entity publishing data object list and a system data object resource table after adding the publishing data object, and names an alias for each data object according to control management requirements;

[0021] The publishing data object list declares data object quantity, length, and publishing period;

[0022] The system-level data object resource table includes a survival time threshold, a version number, and a cross-network segment routing identifier of a global data object.

[0023] Preferably, the publishing data object comprises data element attributes and data object attributes;

[0024] The data element attributes comprise a data element list with engineering units and format definition;

[0025] The attribute defined by the user of the data object includes a periodical publishing policy of dead zone management, a source control entity identification number and a user-defined attribute.

[0026] In step S33, the dynamic visualization connection line maps the data stream state in real time, and different connection line color changes are set to represent the data transmission state, including normal transmission, data update delay exceeding a threshold value, and communication interruption.

[0027] Further, in step S31, the cross-device operation lock includes:

[0028] The other users are prohibited from editing the data objects of the source control entity and the target control entity, and the system-level data object resource table associated with the source control entity is prohibited from being modified;

[0029] The lock lasts until the drag operation is completed and the subscription data object check is passed, and then the lock is released.

[0030] Preferably, step S3 further includes:

[0031] When the subscription data object is deleted, the subscription data object element in the target control entity is removed by dragging, and an association check is triggered. If the object is referenced by the control logic, a breakpoint report is forced to be generated;

[0032] When the publishing data object is deleted, all associated subscription data objects are automatically released, and an industrial-level invalidation instruction is sent to all subscription entities to activate a preset safety value.

[0033] More preferably, each control entity includes at least one dual-channel heartbeat publishing data object for broadcasting the survival state and working state of the control entity, wherein the main channel broadcasts the device survival state and CPU load rate, and the backup channel transmits fault codes and event sequence records SOE.

[0034] Further, the entity identification number includes a device location code, and the coding rule is: production line number-station number-device type code. The entity identification number is automatically assigned in ascending order according to the import order.

[0035] Further, in step S34, the range rule includes: a single subscription data object is allowed to be associated with only one publishing data object, and a single publishing data object is allowed to be associated with multiple subscription data objects.

[0036] The safety level rule includes: the safety level of the subscription data object must be greater than that of the publishing data object.

[0037] When a rule conflict occurs in the data object association operation, a hierarchical alarm is triggered and the operation is prohibited, wherein,

[0038] The primary rule conflict is out-of-range, and if the range rule is not met, the data is scaled and a warning is marked:

[0039] The secondary rule conflict is security level downgrade, and if the security level rule is not met, the association is immediately blocked and the safety PLC is notified.

[0040] In another aspect, a graphical configuration system for data relationship between multiple entities is provided, comprising:

[0041] An entity configuration initialization module is configured to import multiple control entities in a graphical interface, the control entities including PLC controllers, edge computing nodes and intelligent sensing devices, and assign a unique entity identification number to each control entity;

[0042] A data object definition module is configured to select a source control entity from the imported control entities and create a published data object for the source control entity in response to production line configuration requirements, the published data object being presented in the form of a draggable graph element, each published data object containing a unique data object identification number with industrial semantics and user-defined attributes;

[0043] A visual relationship construction module is configured to associate the published data object of the source control entity to a target control entity through a dragging operation, automatically generate a corresponding subscription data object in the target control entity, integrate the subscription data object to the target entity in the form of a splicable graph element, and establish a visual connection of real-time data flow;

[0044] A collaborative editing lock module is configured to automatically lock a control entity and prohibit other users from editing when a user edits production line control logic and selects the control entity, until the editing operation is completed.

[0045] In addition, a computer-readable storage medium is provided, which stores a computer program, the program being executed by a processor to implement the graphical configuration method for data relationship between multiple entities according to any one of the above aspects.

[0046] Meanwhile, an electronic device is provided, comprising: one or more processors; a storage device configured to store 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 relationship between multiple entities according to any one of the above aspects.

[0047] Compared with the prior art, the present application has the following advantages:

[0048] The present application defines data objects between multiple control entities in a system and establishes a mechanism for sharing data objects between entities in a many-to-many manner, thereby achieving unified definition of data in a system and solving the problem of cumbersome definition of data sharing between entities.

[0049] The application realizes the WYSIWYG of the data object attribute by embodying the data object as a graph element that can be dragged and spliced, and then uses a connection line to design the visual subscription relationship of the data object, to establish a visual association between the data object producer and consumer, to realize the WYSIWYG, to improve the configuration efficiency, and to facilitate error finding.

[0050] The application limits the operation of other users when the current user edits one or more control entities, formulates rules for the sharing of data objects, and realizes the prevention of errors. BRIEF DESCRIPTION OF DRAWINGS

[0051] The accompanying drawings are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and are used to explain the application, and do not limit the application. In the drawings:

[0052] Figure 1 A graphical configuration method of data relationship between multiple entities of the application is shown in the flow chart.

[0053] Figure 2 A graphical interface instance of the application is shown in the diagram.

[0054] Figure 3 A data object attribute diagram of the application is shown in the diagram.

[0055] Figure 4 A relationship diagram between a subscription data object and a published data object of the application is shown in the diagram.

[0056] Figure 5 An operation flow diagram of the graphical configuration method of the overall data relationship between multiple entities of the application is shown in the diagram.

[0057] Figure 6 A graphical configuration system diagram of the data relationship between multiple entities of the application is shown in the diagram. DETAILED DESCRIPTION

[0058] To make the purpose, technical scheme and advantages of the embodiments of the application clearer, the technical scheme of the embodiments of the application will be described clearly and completely below with reference to the drawings in the embodiments of the application. Obviously, the described embodiments are some embodiments of the application, but not all the embodiments of the application. Based on the embodiments in the application, all other embodiments obtained by those skilled in the art without creative work fall within the scope of protection of the application.

[0059] The present application aims at the huge data interaction demand between multiple control entities in a multi-agent cooperative control system, and considers that the existing conventional list and programming mode have problems such as non-intuitive data sharing, easy error, exponentially increasing debugging workload and the like. The present application adopts a graphical and visual interface to realize intuitive configuration of data sharing relationship. Meanwhile, the present application introduces a data object concept, and organizes shared data according to data objects and synchronously declares between data producers and users through a drag mode. The present application also formulates a data object unique identification number and data object interlocking rule to reduce human error possibility, and ensures that the user refuses to act when a logic error occurs and prompts the error, thereby providing a perfect solution for multiple entity data use.

[0060] In the present application, the control entity includes data producers and consumers, and is composed of an actual controller or a virtual program segment. The control entity is a carrier of the data object;

[0061] The publishing data object is a data segment, and the control entity is used as the smallest unit for publishing data, which is composed of a data object ID, an alias, data and data description. The publishing data object is generated by a source control entity and published to one or several target control entities through communication, and the target control entity uses the data of the publishing data object by running control logic;

[0062] The data object is a data segment, and is used as the smallest unit for interacting data between control entities. Each data object has a unique identification number. The control entity needs to provide the unique identification number when using the data of the data object. Each data object can independently define a transceiver mechanism, thereby ensuring minimization of the influence of the transceiver behavior on the control entity;

[0063] The subscribing data object is a data segment, and the control entity is used as the smallest unit for obtaining real-time data from other source control entities. Each subscribing data object is generated by a unique source control entity, and is a publishing data object of the source control entity;

[0064] The publishing data object list is a list of publishing data objects generated by the control entity, and is used to declare the number of data objects to be published by the control entity, the length of each data object, the publishing period and the like information;

[0065] The subscribing data object list is a list of data objects prepared to be received by the control entity, and is used to declare the number of data objects from other control entities used by the control entity, the length of each data object, the publishing period and the like information.

[0066] The specific implementation of the present application is described below in combination with the drawings and embodiments.

[0067] Embodiment 1

[0068] The specific configuration method of the present application is to allocate data objects between a plurality of cooperatively running control entities through a connection in a graphical interface, wherein the graphical interface is provided with at least two control entities generating or using data, each control entity is newly created or edited by a user according to needs, and the published data objects are provided. Figure 1 As shown in the technical scheme of the graphical configuration method of data relationship between a plurality of entities provided in the embodiment, the steps include:

[0069] S1: importing a plurality of control entities in a graphical interface, the control entities including PLC controllers, edge computing nodes and intelligent sensing devices, and assigning a unique entity identification number to each control entity;

[0070] S2: selecting a source control entity in the imported control entities in response to a production line configuration requirement, and creating a published data object for the source control entity, the published data object being in the form of a dragable graphic element, each published data object containing a unique data object identification number with industrial semantics and a user-defined attribute;

[0071] S3: associating the published data object of the source control entity to a target control entity through a drag operation, automatically generating a corresponding subscription data object in the target control entity, integrating the subscription data object to the target entity in the form of a splicable graphic element, and establishing a visual connection of real-time data flow;

[0072] Wherein, when a user edits a production line control logic and selects a control entity, the control entity is automatically locked and other users are prohibited from editing until the editing operation is completed.

[0073] Firstly, in step S1, the graphical interface is as shown in Figure 2 The importing of a plurality of source control entities in the graphical interface further includes:

[0074] The graphical interface includes a control entity object list and a configuration area to provide a production line topology layer, and the control entities are automatically laid out according to physical positions.

[0075] A plurality of control entities are imported in the configuration area of the graphical interface through a drag operation, and the required control entities are newly created or edited according to needs.

[0076] The entity identification number includes a device location code, and the coding rule is: production line number-station number-device type code, and the entity identification number is automatically assigned in ascending order according to the import order.

[0077] In the embodiment, the control entity is automatically assigned a 16-bit entity identification number after being dragged into the configuration area using a mouse, and the entity identification number starts from 1 and is automatically increased by 1 for each drag operation.

[0078] Then, in step S2, the creating publishing data object further comprises:

[0079] The source control entity automatically forms the entity publishing data object list and the system data object resource table after adding the publishing data object, and names an alias for each data object according to the control management requirement;

[0080] The publishing data object list declares the data object quantity, length and publishing period;

[0081] The system-level data object resource table includes the survival time threshold, version number and cross-network segment routing identifier of the global data object.

[0082] The publishing data object includes data element attributes and data object attributes;

[0083] The data element attributes include a data element list with engineering units and format definition;

[0084] The attributes defined by the data object user include the dead zone management period publishing strategy, source control entity identifier and user-defined attributes.

[0085] Specifically, in the embodiment, the configuration control entity includes:

[0086] The control entity dragged into the configuration area supports joining the publishing data object by mouse click, and each control entity can join up to 65535 publishing data objects. The embodiment adopts a unified allocation identifier strategy for all data objects to avoid data object duplication. The control entity automatically forms the entity publishing data object list and the system data object resource table after adding the publishing data object, and the user can name an alias for each data object according to the control management requirement.

[0087] In addition, the data object configured for the control entity specifically includes:

[0088] Each data object includes data elements and attributes, and the attributes are data element attributes and data object attributes. The data element attributes include a data element list, data element format, data object publishing strategy (period publishing, event publishing, etc.), control entity identifier and other up to 200 custom attributes. After the control entity is dragged to the configuration area, the control entity is locked by the current user when selected by mouse click, and cannot be edited by others. The current user can add publishing data objects and modify control data object attributes. The control entity automatically establishes a publishing data object list when adding the first publishing data object. The attributes of the data object are as shown in Figure 3 .

[0089] Preferably, each of the control entities comprises at least one dual-channel heartbeat publishing data object for broadcasting the survival state and working state of the control entity, wherein the main channel broadcasts the survival state and CPU load rate, and the standby channel transmits the fault code and sequence of events (SOE). The remaining publishing data objects are established by mouse selection.

[0090] Then, the dragging association of step S3 is performed, specifically including:

[0091] S31: In response to the dragging operation start instruction, a cross-device operation lock is applied to the source control entity and the target control entity, the entity pair formed by the source control entity and the target control entity is locked, and a time-stamped operation log is generated;

[0092] S32: A target data object is dragged from the publishing data object list of the source control entity to the target control entity;

[0093] S33: A subscription data object list is automatically generated in the target control entity, the subscription data object is displayed in the form of a splicable graph element visually associated with the publishing graph element, a dynamic visual connection is established, and the data object attribute and source entity identification number are recorded;

[0094] S34: The range rule and the security level rule of the subscription data object are automatically configured based on the attribute of the publishing data object.

[0095] In step S31, the cross-device operation lock includes:

[0096] Other users are prohibited from editing the data objects of the source control entity and the target control entity, and the system-level data object resource table associated with the source control entity pair is prohibited from being modified;

[0097] The lock is released after the dragging operation is completed and the subscription data object is verified.

[0098] In step S33, the dynamic visual connection real-time maps the data flow state, and different line color changes are set to represent the data transmission state, including normal transmission, data update delay exceeding a threshold, and communication interruption.

[0099] Step S3 involves deleting the subscription data object or the publishing data object, specifically including:

[0100] When the subscription data object is deleted, the subscription data object in the target control entity is removed by dragging, and an association verification is triggered. If the object is referenced by the control logic, a breakpoint report is forcibly generated;

[0101] When the publishing data object is deleted, all associated subscription data objects are automatically released, and industrial-level invalidation instructions are sent to all subscription entities to activate preset security values.

[0102] In addition, in step S34, the range rule includes that a single subscription data object is allowed to be associated with only one publishing data object, and a single publishing data object is allowed to be associated with multiple subscription data objects.

[0103] The security level rule includes that the security level of the subscription data object must be greater than that of the publishing data object.

[0104] When a rule conflict occurs in a data object association operation, a hierarchical alarm is triggered and the operation is prohibited from being executed, wherein,

[0105] A primary rule conflict is a range overrun. If the range rule is not met, the data is forced to be scaled and a warning is marked:

[0106] A secondary rule conflict is a security level downgrade. If the security level rule is not met, the association is immediately blocked and a safety PLC is notified.

[0107] Specifically, in the embodiment, each control entity provides a subscription data object list for registering data objects required by the control entity to implement a computing function and recording attributes of the data objects. The subscription data list is established by dragging a publishing data entity to a target control entity with a mouse.

[0108] The management establishment process is as follows: a control entity is selected as a source control entity and another control entity is selected as a target control entity with a mouse click. The source control entity and the target control entity are immediately locked after being selected, and the entity pair is displayed in a distinctive color on the interface. Other users cannot select the two control entities, and the data objects involved in the control entities cannot be selected in the data object summary table. The source control entity list displays publishing data objects established by the user in the control entity. The user can complete the relationship establishment of the data objects by dragging the data objects to the target control entity with a mouse, and a subscription data object list is established at the same time.

[0109] To prevent the subscription data object from being modified by multiple source control entities, thereby causing unexpected modifications. A subscription data object corresponds to only one publishing data object. A publishing data object can be simultaneously published to multiple subscription data objects for use. The specific structure is shown in Figure 4 .

[0110] Secondly, the deletion of the association between the control entity data objects comprises: when a user considers that the subscription data object of the control entity is no longer needed, the control entity is selected by a mouse, at this time, the control entity is locked, which is represented by a bright identification color on the interface, and other users cannot select it. The user can delete the unwanted subscription data object by dragging it with the mouse.

[0111] The deletion of the publication data of the control entity data object comprises: when a user considers that the publication data object of the control entity is no longer needed, the control entity is selected by a mouse, at this time, the control entity is locked, which is represented by a bright identification color on the interface, and other users cannot select it. The user can delete the unwanted publication data object by dragging it with the mouse, and the entity using the data object automatically deletes the deletion of the data object.

[0112] In summary, the specific configuration method of the application is to allocate data objects between a plurality of cooperatively running control entities through a connection line in a graphical interface, wherein the graphical interface is generated by at least two control entities that generate or use data, each control entity is newly created or edited by a user according to needs, and the publication data object is provided. The specific operation steps of the whole process are as shown in Figure 5 .

[0113] On the other hand, the embodiment also provides a graphical configuration system of data relationship between multiple entities, as shown in Figure 6 , comprising:

[0114] An entity configuration initialization module is configured to import a plurality of control entities in a graphical interface, wherein the control entities comprise PLC controllers, edge computing nodes and intelligent sensing devices, and a unique entity identification number is allocated to each control entity;

[0115] A data object definition module is configured to select a source control entity in the imported control entities and create a publication data object for it in response to the production line configuration demand, wherein the publication data object is presented in the form of a draggable graph element, each publication data object contains a unique data object identification number with industrial semantics and user-defined attributes;

[0116] A visual relationship construction module is configured to associate the publication data object of the source control entity to the target control entity through a dragging operation, and automatically generate a corresponding subscription data object in the target control entity, so that the subscription data object is integrated into the target entity in the form of a splicable graph element, and a visual connection line of real-time data flow is established;

[0117] A collaborative editing lock module is configured to automatically lock the control entity when a user edits the production line control logic and selects the control entity, and prohibit other users from editing until the editing operation is completed.

[0118] It should be noted that the steps in the graphical configuration method of the data relationship among multiple entities provided in the embodiments can be implemented based on corresponding modules in the graphical configuration system of the data relationship among multiple entities, and those skilled in the art can refer to the technical solutions of the system to implement the step flow of the method, that is, the embodiments in the system can be understood as preferred examples of implementing the method, and details are not described here.

[0119] In addition to implementing the system and each device thereof provided in the present application in a pure computer readable program code manner, the system and each device thereof provided in the present application can also be implemented in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers and embedded microcontrollers, etc. by logically programming the method steps to achieve the same functions. Therefore, the system and each device thereof provided in the present application can be considered as a hardware component, and the devices included therein for implementing various functions can also be considered as structures in the hardware component; the devices for implementing various functions can also be considered as both software modules implementing the method and structures in the hardware component.

[0120] Finally, it should be noted that: the above description is only the preferred embodiments of the present application, the protection scope of the present application is not limited to the above-mentioned embodiments, and any technical solution falling within the concept of the present application is within the protection scope of the present application. It should be noted that for ordinary skilled in the art, some improvements and refinements without departing from the principles of the present application are also considered as the protection scope of the present application.

[0121] The technical features of the above-described embodiments can be combined arbitrarily, and in order to make the description concise, all possible combinations of the technical features in the above-described embodiments are not described, however, as long as the combinations of the technical features do not exist contradictory, they should be considered as the scope of the present application.

Claims

1. A method for graphical configuration of data relationships between multiple entities, characterized in that, The method comprises the following steps: S1: importing a plurality of control entities in a graphical interface, the control entities comprising a PLC controller, an edge computing node and an intelligent sensing device, and assigning a unique entity identification number to each control entity; S2: selecting a source control entity from the imported control entities in response to a production line configuration requirement, and creating a publication data object for the source control entity, the publication data object being presented in the form of a draggable graph element, each publication data object containing a unique data object identification number with industrial semantics and user-defined attributes; S3: associating the publication 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, integrating the subscription data object to the target control entity in the form of a splicable graph element, and establishing a visual connection of real-time data flow; In step S3, the association specifically comprises: S31: in response to a dragging operation start instruction, applying a cross-device operation lock to the source control entity and the target control entity, locking the entity pair formed by the source control entity and the target control entity, and generating a time-stamped operation log; S32: dragging a target data object from the publication data object list of the source control entity to the target control entity; S33: automatically generating a subscription data object list in the target control entity, the subscription data object being integrated and displayed in the form of a splicable graph element visually associated with the publication data object, establishing a dynamic visual connection, and recording the data object attributes and the source entity identification number; S34: automatically configuring the range rules and safety level rules of the subscription data object based on the attributes of the publication data object; Wherein, when a user edits the production line control logic and selects a control entity, the control entity is automatically locked and editing by other users is prohibited until the editing operation is completed.

2. The method of claim 1, wherein, In step S1, the importing of a plurality of source control entities in the graphical interface further comprises: The graphical interface comprises a control entity object list and a configuration area to provide a production line topology layer, and the control entities are automatically laid out according to physical positions; A plurality of control entities are imported in the configuration area of the graphical interface through a dragging operation, and the required control entities are clicked to newly create or edit publication data objects as required.

3. The method of claim 2, wherein, In step S2, the creation of the publication data object further comprises: The source control entity automatically forms an entity publication data object list and a system data object resource table after adding the publication data object, and names an alias for each data object according to control management requirements; The publication data object list declares the number, length and publication period of the data objects; The system data object resource table comprises a survival time threshold, a version number and a cross-network segment routing identification of a global data object.

4. The method of claim 3, wherein, The publication data object comprises data element attributes and data object attributes; The data element attributes comprise a data element list with engineering units and format definition; The user-defined attributes of the data object comprise a periodical publication policy for dead zone management, a source control entity identification number and user-defined attributes.

5. The method of claim 1, wherein, In step S33, the dynamic visualization connection line maps the data stream state in real time, and represents the data transmission state by setting different connection color changes, including normal transmission, data update delay exceeding a threshold, and communication interruption.

6. The method of graphical configuration of data relationships among multiple entities of claim 1, wherein, In step S31, the cross-device operation lock comprises: Prohibiting other users from editing the data objects of the source control entity and the target control entity, and prohibiting modification of the system-level data object resource table associated with the source control entity pair; The lock lasts until the drag operation is completed and the subscription data object check is passed, and is released.

7. The method of claim 1, wherein, Step S3 further comprises: When the subscription data object is deleted, the subscription data object primitive in the target control entity is removed by dragging, and an association check is triggered, and if the object is referenced by control logic, a breakpoint report is forced to be generated; When the publishing data object is deleted, all associated subscription data objects are automatically released, and an industrial-level invalidation instruction is sent to all subscription entities, and a preset safety value is activated.

8. The method of graphical configuration of data relations among multiple entities according to claim 3, wherein, Each of the control entities comprises at least one dual-channel heartbeat publishing data object for broadcasting the survival state and working state of the control entity, wherein the main channel broadcasts the device survival state and CPU load rate, and the backup channel transmits fault codes and event sequence records SOE.

9. The method of graphical configuration of data relations among multiple entities according to claim 1, wherein, The entity identification number comprises a device location code, and the coding rule is: production line number-station number-device type code, and the entity identification number is automatically incremented and allocated in the import order.

10. The method of graphical configuration of data relationships among multiple entities of claim 1, wherein, In step S34, the range rule comprises: a single subscription data object is allowed to be associated with only one publishing data object, and a single publishing data object is allowed to be associated with multiple subscription data objects; The safety level rule comprises: the safety level of the subscription data object must be greater than that of the publishing data object; When a rule conflict occurs in the data object association operation, a hierarchical alarm is triggered and the operation is prohibited, wherein, The first rule conflict is range overrun, and if the range rule is not met, the data is forced to be scaled and a warning is marked: The second rule conflict is safety level degradation, and if the safety level rule is not met, the association is immediately blocked and a safety PLC is notified.

11. A graphical configuration system for data relationships between multiple entities, characterized by Comprise: An entity configuration initialization module for importing a plurality of control entities in a graphical interface, the control entities comprising PLC controllers, edge computing nodes and intelligent sensing devices, and assigning a unique entity identification number to each control entity; A data object definition module for selecting a source control entity in the imported control entities in response to production line configuration requirements, and creating a publishing data object for the source control entity, the publishing data object being presented in the form of a draggable primitive, each publishing data object containing a unique data object identification number with industrial semantics and user-defined attributes; A visualization relationship construction module for associating the publishing data object of the source control entity to the target control entity through a drag operation, automatically generating a corresponding subscription data object in the target control entity, integrating the subscription data object to the target control entity in the form of a splicable primitive, and establishing a visualization connection line of real-time data flow; The collaborative editing locking module is used for automatically locking a control entity and prohibiting other users from editing when a user edits the production line control logic and selects the control entity, until the editing operation is completed; In the visualization relationship construction module, the association specifically comprises the following steps: In response to a drag operation starting instruction, a cross-device operation lock is applied to the source control entity and the target control entity, an entity pair formed by the source control entity and the target control entity is locked, and a time-stamped operation log is generated; A target data object is dragged from a list of published data objects of a source control entity to a target control entity; A list of subscribed data objects is automatically generated in the target control entity, the subscribed data objects are displayed in the form of splicable graph elements visually associated with the published data objects, a dynamic visualization connection is established, and data object attributes and a source entity identification number are recorded; Range rules and security level rules of the subscribed data objects are automatically configured based on attributes of the published data objects.

12. A computer readable storage medium having stored thereon a computer program, characterized in that, The program, when executed by a processor, implements the graphical configuration method of data relationships among multiple entities as claimed in any one of claims 1-10.

13. An electronic device, comprising: Comprise: One or more processors; A storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors implement the graphical configuration method of data relationships among multiple entities as claimed in any one of claims 1-10.

Images