Multi-device linkage triggering methods, devices, equipment, storage media and products

Abstract

This application discloses a method, apparatus, device, storage medium, and product for triggering multi-device linkage, relating to the field of industrial internet technology. The method includes: an OPC-UA server establishing communication connections with a first device and a second device respectively; determining linkage rules between the two devices through a linkage model; and triggering linkage events for the two devices according to the linkage rules. This application improves the basic OPC-UA specification by integrating a linkage model within the server and connecting the first and second devices to the server, effectively enhancing the intelligence level of industrial automation systems and strengthening the interoperability between devices. By determining linkage rules between devices through the linkage model and then triggering linkage events between multiple devices according to the linkage rules, direct interaction and collaboration between multiple device nodes are achieved, reducing dependence on external devices and thus realizing a more efficient and flexible multi-device collaborative work scheme.

Description

Technical Field

[0001] This application relates to the field of industrial internet technology, and in particular to a method, apparatus, device, storage medium and product for triggering multi-device linkage. Background Technology

[0002] With the rapid development of the Industrial Internet, the interoperability and real-time performance of industrial automatic control systems have become increasingly important throughout the production process. Currently, automated equipment on industrial production lines is controlled and communicated through various industrial bus protocols and real-time Ethernet protocols. Although most of these industrial bus protocols and real-time Ethernet protocols are standardized by IEC 61158 / 61784, the lack of unified interface standards limits the interoperability between systems, preventing devices from working together. The Open Platform Communications Unified Architecture (OPC-UA) is a secure, reliable, and manufacturer- and platform-independent standard for industrial communication data interaction. It defines a basic, universal information model, including real-time data access, alarm monitoring, event handling, and historical data access. It also clearly defines the interfaces between clients and servers, as well as between servers, and supports field-level communication between devices from different manufacturers based on the OPC-UA FX (Field Data Interaction) specification.

[0003] The existing OPC-UA basic specification mainly focuses on modeling the attributes, methods, and events of node objects themselves, without mentioning the interaction and collaborative processing between nodes. The extended field-level data interaction specification mainly describes the data exchange between node objects between controllers. The data processing after the interaction relies on the device's internal private protocols and lacks a collaborative workflow, making it impossible to achieve effective collaborative work among multiple devices in complex application scenarios. Summary of the Invention

[0004] The main purpose of this application is to provide a method, apparatus, device, storage medium and product for triggering multi-device linkage, which aims to solve the technical problem that the existing OPC-UA basic specification cannot achieve efficient multi-device collaborative work.

[0005] To achieve the above objectives, this application proposes a multi-device linkage triggering method, which is applied to an OPC-UA server. The OPC-UA server includes a linkage model, and the method includes:

[0006] Communication connections are established with the first and second devices respectively using the OPC-UA protocol;

[0007] The linkage rules between the first device and the second device are determined through the linkage model.

[0008] According to the linkage rules, a linkage event is triggered on the first device and / or the second device.

[0009] In one embodiment, the OPC-UA-FX field layer model of the OPC-UA server includes a linkage model, which includes a linkage trigger type and a linkage mode enumeration type. The linkage trigger type inherits from the basic object type of OPC-UA, and the linkage mode enumeration type inherits from the basic data type of OPC-UA.

[0010] In one embodiment, the attributes in the linkage trigger type include subscription node attributes, linkage mode attributes, periodic attributes, remote server attributes, and event attributes;

[0011] The step of determining the linkage rules between the first device and the second device through the linkage model includes:

[0012] The first device is identified as the data source node through the subscription node attributes, and the data in the first device is monitored;

[0013] When the data in the first device is detected to meet the preset conditions, the execution mode of the linkage is determined by the linkage mode attribute and the linkage mode enumeration type.

[0014] The time interval for triggering the linkage event is determined based on the aforementioned periodic attribute;

[0015] Based on the remote server attributes, the OPC-UA server address where the second device is located is used as the cross-server linkage address corresponding to the first device;

[0016] Based on the event attributes, determine the action to be executed when the linkage event is triggered, and obtain the linkage rules between the first device and the second device.

[0017] In one embodiment, the linkage mode enumeration type includes continuous time comparison mode type, number comparison mode type and extreme value comparison mode type;

[0018] The step of determining the execution mode of linkage through the linkage mode attribute and the linkage mode enumeration type when the data in the first device is detected to meet the preset conditions includes:

[0019] When the linkage mode attribute is the continuous time comparison mode type, the linkage execution mode is to continuously monitor the data in the first device within a preset time period;

[0020] When the linkage mode attribute is the number comparison mode type, the linkage execution mode is to monitor the occurrence number of preset events in the data of the first device;

[0021] When the linkage mode attribute is the extreme value comparison mode type, the linkage execution mode is to perform numerical monitoring of the data in the first device.

[0022] In one embodiment, before the step of triggering a linkage event on the first device and / or the second device according to the linkage rule, the method further includes:

[0023] The linkage trigger type and the linkage mode enumeration type are instantiated by the node objects of the first device and the second device, respectively, to obtain the first device event object and the second device event object.

[0024] In one embodiment, the step of triggering a linkage event for the first device and / or the second device according to the linkage rule includes:

[0025] When the linkage mode attribute is the continuous time comparison mode type, and when the preset condition is met within the preset time period, a linkage event is triggered on the first device through the first device event object, and / or a linkage event is triggered on the second device through the second device event object;

[0026] When the linkage mode attribute is the number comparison mode type, and when the number of occurrences of the preset event is detected to reach the preset number threshold, a linkage event is triggered on the first device through the first device event object, and / or a linkage event is triggered on the second device through the second device event object;

[0027] When the linkage mode attribute is the extreme value comparison mode type, and when the data in the first device is detected to be greater than the maximum threshold or the data in the first device is less than the minimum threshold, a linkage event is triggered on the first device through the first device event object, and / or a linkage event is triggered on the second device through the second device event object.

[0028] Furthermore, to achieve the above objectives, this application also proposes a multi-device linkage triggering device, which includes:

[0029] A communication connection establishment module is used to establish communication connections with the first device and the second device respectively via the OPC-UA protocol;

[0030] The linkage rule determination module is used to determine the linkage rules between the first device and the second device through the linkage model.

[0031] The linkage event triggering module is used to trigger linkage events for the first device and / or the second device according to the linkage rules.

[0032] In addition, to achieve the above objectives, this application also proposes a multi-device linkage triggering device, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the multi-device linkage triggering method described above.

[0033] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the multi-device linkage triggering method described above.

[0034] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the multi-device linkage triggering method described above.

[0035] This application provides a method for triggering multi-device linkage. An OPC-UA server establishes communication connections with a first device and a second device via the OPC-UA protocol. A linkage model determines the linkage rules between the first and second devices. Linkage events are triggered on the first and / or second devices according to these rules. This application improves the basic OPC-UA specification by integrating a linkage model within the OPC-UA server and connecting the first and second devices to the server. This effectively enhances the intelligence level of industrial automation systems and strengthens interoperability between devices. By determining the linkage rules between devices through the linkage model and then triggering linkage events between multiple devices according to these rules, direct interaction and collaboration between multiple device nodes are achieved, reducing dependence on external devices and thus realizing a more efficient and flexible multi-device collaborative work scheme. Attached Figure Description

[0036] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0037] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1This is a flowchart illustrating an embodiment of the multi-device linkage triggering method of this application.

[0039] Figure 2 This is an overall block diagram of the multi-device linkage triggering method of this application;

[0040] Figure 3 This is a flowchart illustrating Embodiment 2 of the multi-device linkage triggering method of this application;

[0041] Figure 4 This is a diagram of the OPC-UA server architecture for the integrated linkage model in this application;

[0042] Figure 5 This is a schematic diagram of the OPC-UA linkage model in this application;

[0043] Figure 6 This is a flowchart illustrating Embodiment 3 of the multi-device linkage triggering method of this application;

[0044] Figure 7 This is a diagram of the OPC-UA address space data structure supporting the linkage model in this application;

[0045] Figure 8 This is a schematic diagram of a multi-device interaction scenario for the multi-device linkage triggering method of this application;

[0046] Figure 9 This is an example diagram of the fan control linkage of the multi-device linkage triggering method of this application;

[0047] Figure 10 This is a schematic diagram of the module structure of the multi-device linkage triggering device in an embodiment of this application;

[0048] Figure 11 This is a schematic diagram of the hardware operating environment involved in the multi-device linkage triggering method in this application embodiment.

[0049] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0050] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0051] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0052] The main solution of this application embodiment is: the method is applied to an OPC-UA server, the OPC-UA server includes a linkage model, and the method includes: establishing communication connections with a first device and a second device respectively through the OPC-UA protocol; determining linkage rules between the first device and the second device through the linkage model; and triggering linkage events for the first device and / or the second device according to the linkage rules.

[0053] The existing OPC-UA basic specification mainly focuses on modeling the attributes, methods, and events of node objects themselves, without mentioning the interaction and collaborative processing between nodes. The extended field-level data interaction specification mainly describes the data exchange between node objects between controllers. The data processing after the interaction relies on the device's internal private protocols and lacks a collaborative workflow, making it impossible to achieve effective collaborative work among multiple devices in complex application scenarios.

[0054] This application provides a solution in which an OPC-UA server establishes communication connections with a first device and a second device respectively via the OPC-UA protocol; determines the linkage rules between the first and second devices through a linkage model; and triggers linkage events for the first and / or second devices according to the linkage rules. This application improves the basic OPC-UA specification by integrating a linkage model within the OPC-UA server and connecting the first and second devices to the server, effectively enhancing the intelligence level of industrial automation systems and strengthening the interoperability between devices. By determining the linkage rules between devices through the linkage model and then triggering linkage events between multiple devices according to the linkage rules, direct interaction and collaboration between multiple device nodes are achieved, reducing dependence on external devices and thus realizing a more efficient and flexible multi-device collaborative work scheme.

[0055] It should be noted that the executing entity of the method in this embodiment can be a computing service device with multi-device linkage triggering, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone; or it can be a multi-device linkage triggering device with the same or similar functions. This embodiment and the following embodiments will be described using a multi-device linkage triggering device as an example.

[0056] Based on this, the embodiments of this application provide a multi-device linkage triggering method, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the multi-device linkage triggering method of this application.

[0057] In this embodiment, the method is applied to an OPC-UA server, which includes a linkage model. The multi-device linkage triggering method includes steps S10 to S30:

[0058] Step S10: Establish communication connections with the first device and the second device respectively through the OPC-UA protocol.

[0059] It should be noted that this embodiment improves the OPC-UA basic specification to achieve efficient multi-device collaboration, adding a linkage model related to industrial automation to support direct interaction and collaborative processing between nodes. See reference... Figure 2 , Figure 2 This is an overall block diagram of the multi-device linkage triggering method of this application. The system includes multiple devices and at least one OPC-UA server, each of which integrates a linkage model. Multiple devices (taking two as an example, device 1 and device 2) connect to the OPC-UA server via the OPC-UA standard. The server acts as middleware between the devices, receiving and processing messages and commands sent by the devices. SCADA (Supervisory Control and Data Acquisition) is a computer-based control system used to collect, analyze, and process real-time data from industrial processes.

[0060] Understandably, devices communicate via the OPC-UA protocol for exchanging event messages. Data transmission and processing are implemented using the OPEN62541 open-source program. Within the same OPC-UA server, communication between device nodes uses the OPC-UA client / server (C / S) model, while communication between device nodes across servers uses the OPC-UA publish / subscribe (PubSub) model.

[0061] Step S20: Determine the linkage rules between the first device and the second device through the linkage model.

[0062] It is understood that this embodiment integrates a linkage model in the OPC-UA server. The linkage model is used to determine the linkage relationship between multiple devices (e.g., a first device and a second device) and trigger linkage events. For example, a linkage rule could be that when the temperature data of the first device reaches 40 degrees Celsius, the second device needs to be linked to turn on its fan for cooling; or it could be that when the temperature data of the first device remains below 38 degrees Celsius, the second device needs to be linked to turn off its fan, etc. There are no restrictions here.

[0063] Step S30: Trigger a linkage event for the first device and / or the second device according to the linkage rules.

[0064] It should be understood that after setting the linkage rules between the first device and the second device through the linkage model, linkage events can be triggered for the first device and / or the second device according to the linkage rules. Taking the temperature detection mentioned above as an example, when the temperature data of the first device reaches 40 degrees, the triggering event can be that the first device sends a high temperature warning message, or it can be that the second device turns on the fan.

[0065] This embodiment provides a multi-device linkage triggering method. An OPC-UA server establishes communication connections with a first device and a second device via the OPC-UA protocol. A linkage model determines the linkage rules between the first and second devices. Linkage events are triggered on the first and / or second devices according to these rules. This application improves the basic OPC-UA specification by integrating a linkage model within the OPC-UA server and connecting the first and second devices to the server. This effectively enhances the intelligence level of industrial automation systems and strengthens interoperability between devices. By determining the linkage rules between devices through the linkage model and then triggering linkage events between multiple devices according to these rules, direct interaction and collaboration between multiple device nodes are achieved, reducing dependence on external devices and thus realizing a more efficient and flexible multi-device collaborative work scheme.

[0066] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in Embodiment 1 above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 3 The OPC-UA-FX field layer model of the OPC-UA server includes a linkage model, which includes a linkage trigger type and a linkage mode enumeration type. The linkage trigger type inherits from the basic object type of OPC-UA, and the linkage mode enumeration type inherits from the basic data type of OPC-UA.

[0067] It is worth noting that this can be used as a reference. Figure 4 The integrated OPC-UA server architecture will be described below. Figure 4 This is a diagram of the OPC-UA server architecture for integrating the linkage model in this application. A linkage model can be added to the OPC-UA-FX field layer model of the OPC-UA server to identify linkage rules between devices and trigger linkage events. OPC-UA servers can also send inter-server linkage messages based on the OPC-UA PubSub mode to achieve automated linkage between devices across servers.

[0068] It should be noted that the linkage model adds a linkage trigger type and a linkage mode enumeration type. The linkage trigger type inherits from OPC-UA's base object type `BaseObjectType`, used to define the specific implementation of the linkage logic and to achieve fine-grained control over the linkage through multiple properties. The linkage mode enumeration type inherits from OPC-UA's base data type `BaseDataType`, used to describe the mode selection for different linkage operations. `BaseObjectType` and `BaseDataType` are basic types in OPC-UA, serving as the general base classes for object types and data types, respectively. The newly defined extended classes all inherit from these base classes, ensuring model compatibility and standardization.

[0069] In one feasible implementation, please refer to Figure 5 , Figure 5 This is a schematic diagram of the OPC-UA linkage model in this application. The attributes in the linkage trigger type include subscription node attributes, linkage mode attributes, periodic attributes, remote server attributes, and event attributes; step S20 may include steps S201~S205:

[0070] Step S201: The first device is identified as the data source node through the subscription node attributes, and the data in the first device is monitored.

[0071] Understandably, subscription nodes are used to define data source nodes and serve as input to the linkage logic. When the data on a subscription node changes or meets specific conditions, a linkage operation is triggered. This can be a node on the same device or a node on different devices, thus achieving cross-device linkage control. For example, a first device can be designated as the data source node, and the data on that first device can be monitored.

[0072] Step S202: When the data in the first device is detected to meet the preset conditions, the execution mode of the linkage is determined by the linkage mode attribute and the linkage mode enumeration type.

[0073] Understandably, the linkage mode defines the execution mode of the linkage. When the data in the first device of the subscription node meets the preset conditions (which could be a change in the data), it is defined through the execution mode and linkage mode enumeration type, allowing different linkage schemes to be flexibly configured and switched. The specific value of the linkage mode can be one of the linkage mode enumeration types.

[0074] In one feasible implementation, the linkage mode enumeration type includes a continuous time comparison mode type, a number comparison mode type, and an extreme value comparison mode type; step S202 may include steps S2021~S2023:

[0075] Step S2021: When the linkage mode attribute is the continuous time comparison mode type, the linkage execution mode is to continuously monitor the data in the first device within a preset time period.

[0076] It should be noted that the linkage mode enumeration type can include the continuous time comparison mode type. In this mode, the linkage execution mode is to perform a time continuity check on the monitored variable, for example, to monitor whether the temperature data in the first device changes or exceeds a threshold within one minute.

[0077] Step S2022: When the linkage mode attribute is the number comparison mode type, the linkage execution mode is to monitor the occurrence number of preset events in the data of the first device.

[0078] Understandably, the linkage mode enumeration type can also include a count comparison mode type. In this mode, the linkage execution mode is to cumulatively compare the occurrence count of a specific event, and trigger the linkage when a preset count threshold is reached. This mode is suitable for linkage scenarios that require event counting. For example, counting whether the number of times the temperature exceeds 40 degrees Celsius exceeds 3 times.

[0079] Step S2023: When the linkage mode attribute is the extreme value comparison mode type, the linkage execution mode is to perform numerical monitoring of the data in the first device.

[0080] It should be understood that extreme value comparison refers to a scenario where the value is compared with the maximum or minimum value. The linkage mode enumeration type can also include an extreme value comparison mode type. In this mode, the linkage execution mode is to compare the extreme values ​​(maximum or minimum values) of the monitoring data. When a specific threshold is reached or exceeded, the linkage is triggered. This is suitable for extreme monitoring and security threshold triggering scenarios.

[0081] Step S203: Determine the time interval for triggering the linkage event based on the periodic attribute.

[0082] Understandably, the period attribute is used to set the trigger time interval to ensure that linked tasks execute according to the predetermined time period. In continuous time comparison mode, the period is the sliding window time. Therefore, the time interval for triggering linked events can be determined based on the period attribute.

[0083] Step S204: Based on the remote server attributes, use the OPC-UA server address where the second device is located as the cross-server linkage address corresponding to the first device.

[0084] It should be noted that the remote server Uri property is used to support cross-server linkage operations and is applicable to scenarios where linkage control is required between different OPC-UA servers to achieve linkage of devices across networks and systems. Considering that when multiple devices are linked and interacted in this application, the multiple devices can be connected to the same OPC-UA server or in different OPC-UA servers. Therefore, cross-server linkage operations can be supported through the remote server property. For example, the OPC-UA server address where the second device is located can be used as the cross-server linkage address corresponding to the first device by the remote server property.

[0085] Step S205: Determine the actions to be executed when the linkage event is triggered according to the event property, and obtain the linkage rule between the first device and the second device.

[0086] It can be understood that the actions to be executed when the linkage event is triggered are determined according to the event property. For example, the actions to be executed can be sending messages, outputting alarms, logs, and executing changes in associated node data. Thus, the linkage rule between the first device and the second device obtained includes subscribed nodes, linkage mode, period, remote server, and specific execution events.

[0087] In this embodiment, by defining the linkage trigger type, defining the specific implementation of the linkage logic, and also defining the linkage mode enumeration type to describe the mode selection of different linkage operations, fine control of the linkage is achieved through multiple properties such as the subscribed node property, linkage mode property, period property, remote server property, and event property in the linkage trigger type.

[0088] Based on the first embodiment of this application, in the third embodiment of this application, the same or similar content as in the above-mentioned first embodiment can be referred to the above introduction and will not be elaborated hereinafter. On this basis, please refer to Figure 6 , before step S30, step S29 can also be included:

[0089] Step S29: Instantiate the linkage trigger type and the linkage mode enumeration type respectively through the node objects of the first device and the second device to obtain the first device event object and the second device event object. <00OO204>

[0090] It can be understood that an OPC-UA address space data structure supporting the triggering of linkage events can be constructed according to the linkage trigger type and the linkage mode enumeration type. The node object can construct various types of linkage trigger functions by instantiating the linkage trigger type. Each node object can instantiate one or more linkage trigger types and configure different linkage modes and trigger conditions according to the actual application scenario. The constructed OPC-UA address space data structure can be referred to Figure 7The node objects of the first and second devices can be instantiated with linkage trigger types respectively. When instantiating the linkage trigger type, the corresponding linkage mode enumeration type is instantiated to obtain the first device event object and the second device event object.

[0091] In one feasible implementation, step S30 may include steps S301 to S303:

[0092] Step S301: When the linkage mode attribute is the continuous time comparison mode type, and when the preset condition is met within the preset time period, a linkage event is triggered on the first device through the first device event object, and / or a linkage event is triggered on the second device through the second device event object.

[0093] It should be noted that in systems supporting the OPC-UA linkage model, each device enables various object nodes to execute linkage tasks according to associated linkage rules. During OPC-UA communication, devices can establish linkage rules and trigger linkage events to achieve multi-device collaboration. A linkage event consists of the following parts: event source, event object, event type, and event action. The event source is the subscription node ID in the linkage model, which can be a device node within the server or a device node across servers. The execution of linkage rules is triggered by monitoring data changes in the subscription node. The event object is the object instantiated by the device in step S29 above under the linkage model support, such as the first device event object and the second device event object. The event object uses the data changes from the event source as input, processes them according to the linkage rules, and generates output data changes. The interaction scenario can be referenced. Figure 8 , Figure 8 This diagram illustrates a multi-device interaction scenario for the multi-device linkage triggering method of this application. The event type is based on linkage rules, defining the execution type of the linkage event and determining its processing method. When the linkage mode attribute in the linkage rules is a continuous time comparison mode type, and the data in the first device meets preset conditions within a preset duration (e.g., the temperature remains above 40 degrees Celsius for one minute), a linkage event is triggered on the first device via the first device event object (e.g., sending a high-temperature warning to the second device), and / or, a linkage event is triggered on the second device via the second device event object (e.g., the second device turns on its fan).

[0094] Step S302: When the linkage mode attribute is the number comparison mode type, and when the number of occurrences of the preset event is detected to reach the preset number threshold, a linkage event is triggered on the first device through the first device event object, and / or a linkage event is triggered on the second device through the second device event object.

[0095] It is understandable that when the linkage mode attribute is a number comparison mode type and the number of times a preset event is detected reaches a preset number threshold (for example, the number of times the temperature is higher than 40 degrees reaches 3 times), a linkage event is triggered on the first device through the first device event object, and / or a linkage event is triggered on the second device through the second device event object.

[0096] Step S303: When the linkage mode attribute is the extreme value comparison mode type, and when the data in the first device is detected to be greater than the maximum threshold or the data in the first device is less than the minimum threshold, a linkage event is triggered on the first device through the first device event object, and / or a linkage event is triggered on the second device through the second device event object.

[0097] It should be understood that when the linkage mode attribute is the extreme value comparison mode type and the data in the first device is detected to be greater than the maximum threshold (40 degrees) or less than the minimum threshold (30 degrees), a linkage event (which may be an alarm message) is triggered on the first device through the first device event object, and / or a linkage event is triggered on the second device through the second device event object (for example, when it is higher than the maximum threshold, it may be to turn on the fan, and when it is lower than the minimum threshold, it may be to turn off the fan).

[0098] In this embodiment, a flexible and scalable linkage control model is constructed through linkage trigger types and linkage mode enumeration types. This model can adapt to complex working scenarios in industrial automation where multiple devices need to coordinate control, such as periodic task scheduling, remote monitoring linkage, and event-driven response control. By standardizing the definition of linkage modes, linkage models are added to the OPC-UA basic model. The model provides multiple linkage modes (such as continuous time comparison, count comparison, and extreme value comparison), making the linkage logic richer and easier to configure, and adaptable to complex and diverse scenario requirements. It also optimizes the configuration and management between devices, simplifies the network structure, and greatly improves the maintainability and reliability of the system. Furthermore, this structure allows for flexible configuration of the linkage logic according to requirements to adapt to specific needs in different application environments, thereby improving the overall operating efficiency of the system.

[0099] For example, to aid in understanding the implementation flow of the multi-device linkage triggering method obtained by combining this embodiment with the above embodiments, the present invention will be described in detail below with reference to specific examples. However, this example is only one embodiment of the present invention and should not be used to limit the scope of protection of the present invention. Please refer to... Figure 9 , Figure 9 This is an example diagram of the fan control linkage of the multi-device linkage triggering method of this application, specifically:

[0100] This example demonstrates a fan control system based on an OPC-UA linkage model, enabling intelligent collaborative operation between OPC-UA server devices. This embodiment includes two OPC-UA servers, A and B, connected to a temperature sensor on device A and a fan system on device B, respectively. It also includes two linkage trigger rules. By setting specific linkage rules, this system can automatically control the operating status of the fan on device B when certain conditions are met, thereby optimizing system operating efficiency and environmental management.

[0101] First, configure two OPC-UA servers: Server A and Server B. Server A's URI is opc.tcp: / / 192.168.1.201:4840, connecting to the temperature sensor of device A; Server B's URI is opc.tcp: / / 192.168.1.202:4840, connecting to the fan system of device B. For example... Figure 9 As shown, linkage rules are modeled for the fan of device B on OPC-UA server B. The fan of device B communicates through the Uri of the OPC-UA server where device A is located (opc.tcp: / / 192.168.1.201:4840). By correctly configuring the Uri of these two servers, the system can achieve efficient and stable communication across OPC-UA servers.

[0102] Secondly, a subscription node is set up, which serves as the input to the linkage logic. The temperature sensor node of device A is selected as the subscription node, and the fan of device B periodically subscribes to the temperature information from the temperature sensor of device A. This temperature information will be used as the input to the linkage logic of the fan of device B. By ensuring the real-time nature of the data subscription, the system can react quickly to temperature changes, thereby optimizing the fan's control strategy.

[0103] Then, based on monitoring requirements, two linkage trigger rules are set. First linkage rule 1; Event: Fan start; Subscription conditions: Device B's fan subscribes to temperature sensor data from Device A, and the linkage trigger parameters are set according to the requirements of the linkage trigger type. With the subscription node set up, and after a continuous comparison for 1 minute, if the temperature of Device A continuously exceeds 40°C as subscribed through OPC-UA server A (opc.tcp: / / 192.168.1.201:4840), Device B will automatically trigger the fan to start. The purpose of this operation is to lower the ambient temperature, ensuring the entire system operates within a reasonable temperature range, thereby preventing equipment damage or efficiency reduction due to overheating. Second linkage rule 2; Event: Fan shutdown; With the subscription node set up, and after a continuous comparison for 1 minute, if the temperature of Device A drops below 38°C, Device B will trigger the fan to shut down. This avoids excessive fan operation, reduces energy consumption, and extends the equipment's lifespan.

[0104] Finally, in the linkage triggering of the first linkage rule 1 and the second linkage rule 2, the linkage system sets different temperature thresholds for the fan start-up and shutdown. Specifically, the fan start-up temperature is set at 40°C, while the fan shutdown temperature is set at 38°C. By setting a temperature difference threshold between these two temperatures, frequent fan start-up and shutdown caused by slight temperature fluctuations are effectively avoided.

[0105] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the multi-device linkage triggering method of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0106] This application also provides a multi-device linkage triggering device, please refer to... Figure 10 The multi-device linkage triggering device includes:

[0107] The communication connection establishment module 10 is used to establish communication connections with the first device and the second device respectively via the OPC-UA protocol;

[0108] The linkage rule determination module 20 is used to determine the linkage rules between the first device and the second device through the linkage model;

[0109] The linkage event triggering module 30 is used to trigger linkage events for the first device and / or the second device according to the linkage rules.

[0110] The multi-device linkage triggering device provided in this application, employing the multi-device linkage triggering method described in the above embodiments, can solve the technical problem. Compared with the prior art, the beneficial effects of the multi-device linkage triggering device provided in this application are the same as those of the multi-device linkage triggering method described in the above embodiments, and other technical features in the multi-device linkage triggering device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0111] This application provides a multi-device linkage triggering device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the multi-device linkage triggering method in the above embodiment 1.

[0112] The following is for reference. Figure 11The diagram illustrates a structure suitable for implementing a multi-device linkage triggering device in the embodiments of this application. The multi-device linkage triggering device in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 11 The multi-device linkage triggering device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0113] like Figure 11 As shown, the multi-device linkage triggering device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the multi-device linkage triggering device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows multi-device linkage triggering devices to communicate wirelessly or wiredly with other devices to exchange data. While the figures show multi-device linkage triggering devices with various systems, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0114] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0115] The multi-device linkage triggering device provided in this application, employing the multi-device linkage triggering method described in the above embodiments, can solve the technical problem of multi-device linkage triggering. Compared with the prior art, the beneficial effects of the multi-device linkage triggering device provided in this application are the same as those of the multi-device linkage triggering method described in the above embodiments, and other technical features of this multi-device linkage triggering device are the same as those disclosed in the method of the previous embodiment, and will not be repeated here.

[0116] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0117] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0118] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the multi-device linkage triggering method described in the above embodiments.

[0119] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0120] The aforementioned computer-readable storage medium may be included in a multi-device linkage triggering device; or it may exist independently and not be assembled into a multi-device linkage triggering device.

[0121] The aforementioned computer-readable storage medium carries one or more programs. When the aforementioned one or more programs are executed by a multi-device linkage triggering device, the multi-device linkage triggering device: establishes communication connections with a first device and a second device respectively via the OPC-UA protocol; determines the linkage rules between the first device and the second device through the linkage model; and triggers a linkage event for the first device and / or the second device according to the linkage rules.

[0122] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0123] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0124] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0125] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described multi-device linkage triggering method, thereby solving the technical problem. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the multi-device linkage triggering method provided in the above embodiments, and will not be repeated here.

[0126] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the multi-device linkage triggering method described above.

[0127] The computer program product provided in this application can solve the technical problem. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as the beneficial effects of the multi-device linkage triggering method provided in the above embodiments, and will not be repeated here.

[0128] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A multi-device linkage triggering method, characterized in that, The method is applied to an OPC-UA server, which includes a linkage model. The OPC-UA-FX field layer model of the OPC-UA server includes a linkage model. The linkage model includes a linkage trigger type and a linkage mode enumeration type. The linkage trigger type inherits from the basic object type of OPC-UA. The attributes in the linkage trigger type include subscription node attributes, linkage mode attributes, periodic attributes, remote server attributes, and event attributes. The linkage mode enumeration type inherits from the basic data type of OPC-UA. The linkage mode enumeration type includes continuous time comparison mode type, number comparison mode type, and extreme value comparison mode type. The method includes: Communication connections are established with the first and second devices respectively using the OPC-UA protocol; The linkage rules between the first device and the second device are determined through the linkage model. Trigger a linkage event for the first device and / or the second device according to the linkage rules; The step of determining the linkage rules between the first device and the second device through the linkage model includes: The first device is identified as the data source node through the subscription node attributes, and the data in the first device is monitored; When the linkage mode attribute is the continuous time comparison mode type, the linkage execution mode is to continuously monitor the data in the first device within a preset time period; When the linkage mode attribute is the number comparison mode type, the linkage execution mode is to monitor the occurrence number of preset events in the data of the first device; When the linkage mode attribute is the extreme value comparison mode type, the linkage execution mode is to perform numerical monitoring of the data in the first device; The time interval for triggering the linkage event is determined based on the aforementioned periodic attribute; Based on the remote server attributes, the OPC-UA server address where the second device is located is used as the cross-server linkage address corresponding to the first device; Based on the event attributes, determine the action to be executed when the linkage event is triggered, and obtain the linkage rules between the first device and the second device.

2. The method as described in claim 1, characterized in that, Before the step of triggering a linkage event for the first device and / or the second device according to the linkage rule, the method further includes: The linkage trigger type and the linkage mode enumeration type are instantiated by the node objects of the first device and the second device, respectively, to obtain the first device event object and the second device event object.

3. The method as described in claim 2, characterized in that, The step of triggering a linkage event for the first device and / or the second device according to the linkage rules includes: When the linkage mode attribute is the continuous time comparison mode type, and when the preset condition is met within the preset time period, a linkage event is triggered on the first device through the first device event object, and / or a linkage event is triggered on the second device through the second device event object; When the linkage mode attribute is the number comparison mode type, and when the number of occurrences of the preset event is detected to reach the preset number threshold, a linkage event is triggered on the first device through the first device event object, and / or a linkage event is triggered on the second device through the second device event object; When the linkage mode attribute is the extreme value comparison mode type, and when the data in the first device is detected to be greater than the maximum threshold or the data in the first device is less than the minimum threshold, a linkage event is triggered on the first device through the first device event object, and / or a linkage event is triggered on the second device through the second device event object.

4. A multi-device linkage triggering device, characterized in that, The multi-device linkage triggering device is used to execute the multi-device linkage triggering method as described in any one of claims 1 to 3, and the multi-device linkage triggering device includes: A communication connection establishment module is used to establish communication connections with the first device and the second device respectively via the OPC-UA protocol; The linkage rule determination module is used to determine the linkage rules between the first device and the second device through the linkage model. The linkage event triggering module is used to trigger linkage events for the first device and / or the second device according to the linkage rules.

5. A multi-device linkage triggering device, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the multi-device linkage triggering method as described in any one of claims 1 to 3.

6. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the multi-device linkage triggering method as described in any one of claims 1 to 3.

7. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the steps of the multi-device linkage triggering method as described in any one of claims 1 to 3.

Images