Online undisturbed loading configuration method and device of industrial communication gateway and storage medium

Abstract

The invention provides an online undisturbed loading configuration method and device of an industrial communication gateway and a storage medium. The method comprises the following steps: acquiring new configuration data, and storing or downloading the new configuration data to a local configuration data directory of an industrial communication gateway to cover original configuration data; in response to a triggering operation on the undisturbed reloading command, receiving the undisturbed reloading command, and comparing configuration data in an industrial communication gateway running memory with new configuration data in a local configuration data directory to identify a configuration change item; and according to the identified configuration change item and an undisturbed overload strategy corresponding to a preset configuration change item, undisturbed overload operation corresponding to the undisturbed overload strategy is executed, and the configuration change item comprises a link, equipment, a label, a link configuration parameter and an equipment configuration parameter. According to the invention, the configuration data can be loaded and updated in an online undisturbed manner, communication interruption is avoided, and the stability and efficiency of an industrial automation system are improved.

Description

Technical Field

[0001] The present application relates to the field of industrial automation technology, and in particular to an online non-intrusive loading configuration method, device and storage medium for an industrial communication gateway. Background Art

[0002] In industrial automation systems, the access of many external devices usually relies on industrial communication gateways. The industrial communication gateway accesses external devices or external systems and PLCs (programmable logic controllers) in the south and provides data access services in the north to ensure real-time data transmission and processing.

[0003] The configuration and update process of the industrial communication gateway in the existing technology often causes system interruption or temporary stop of data transmission. This is mainly because when loading new configuration data, the existing connection and communication parameters need to be adjusted, and the device or link may need to be restarted, resulting in communication interruption. This interruption not only affects the normal operation of the system, but may also cause data loss or delay, seriously affecting the stability and efficiency of the industrial automation system.

[0004] Therefore, how to load and update configuration data online without affecting the normal operation of industrial communication gateways to achieve dynamic adjustment of link and device parameters is the main problem faced by existing technologies. This technical demand needs to be solved urgently to ensure the stability and continuity of industrial automation systems. Summary of the invention

[0005] In view of this, an embodiment of the present application provides an online non-intrusive loading configuration method, device and storage medium for an industrial communication gateway to solve the problem in the prior art that when updating the configuration of the industrial communication gateway, it is necessary to restart the device or link, resulting in communication interruption and affecting the stability and efficiency of the industrial automation system.

[0006] According to a first aspect of an embodiment of the present application, a method for online non-disruptive loading configuration of an industrial communication gateway is provided, comprising: obtaining new configuration data, and saving or downloading the new configuration data to a local configuration data directory of the industrial communication gateway to overwrite the original configuration data; in response to a trigger operation on a non-disruptive reload command, receiving a non-disruptive reload command, and comparing the configuration data in the running memory of the industrial communication gateway with the new configuration data in the local configuration data directory to identify configuration change items; according to the identified configuration change items, according to the non-disruptive reload policy corresponding to the preset configuration change items, executing a non-disruptive reload operation corresponding to the non-disruptive reload policy, wherein the configuration change items include links, devices, tags, link configuration parameters, and device configuration parameters.

[0007] According to a second aspect of an embodiment of the present application, there is provided an online non-intrusive loading configuration device for an industrial communication gateway, comprising: an acquisition module, configured to acquire new configuration data, and save or download the new configuration data to a local configuration data directory of the industrial communication gateway to overwrite the original configuration data; an identification module, configured to respond to a trigger operation on a non-intrusive reload command, receive a non-intrusive reload command, compare the configuration data in the running memory of the industrial communication gateway with the new configuration data in the local configuration data directory to identify configuration change items; a loading module, configured to perform a non-intrusive reload operation corresponding to a non-intrusive reload policy corresponding to a preset configuration change item according to the identified configuration change item, wherein the configuration change item includes links, devices, labels, link configuration parameters, and device configuration parameters.

[0008] According to a third aspect of an embodiment of the present application, a computer-readable storage medium is provided, which stores a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0009] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0010] By acquiring new configuration data, and saving or downloading the new configuration data to the local configuration data directory of the industrial communication gateway to overwrite the original configuration data; in response to the triggering operation of the non-intrusive reload command, receiving the non-intrusive reload command, comparing the configuration data in the running memory of the industrial communication gateway with the new configuration data in the local configuration data directory to identify the configuration change items; according to the identified configuration change items, according to the non-intrusive reload strategy corresponding to the preset configuration change items, executing the non-intrusive reload operation corresponding to the non-intrusive reload strategy, wherein the configuration change items include links, devices, tags, link configuration parameters and device configuration parameters. The present application can load and update configuration data online without disturbance, avoid communication interruption, and improve the stability and efficiency of the industrial automation system. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0012] Figure 1 It is a schematic diagram of the structural framework of the industrial communication gateway involved in the actual scenario of the embodiment of the present application;

[0013] Figure 2It is a flowchart of an online non-intrusive loading configuration method for an industrial communication gateway provided in an embodiment of the present application;

[0014] Figure 3 It is a structural diagram of an online non-intrusive loading configuration device for an industrial communication gateway provided in an embodiment of the present application;

[0015] Figure 4 It is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0016] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0017] In the field of industrial automation, the access of various external devices (such as sensors, controllers, PLCs, etc.) usually relies on industrial communication gateways. The industrial communication gateway is responsible for accessing these external devices or systems in the south direction, and provides data access services in the north direction to ensure real-time data transmission and processing.

[0018] Current industrial communication gateways often cause system interruptions or brief stops in data transmission during configuration and update processes. This is mainly because when loading new configuration data, existing connection and communication parameters must be adjusted, which may require restarting the device or link, resulting in communication interruptions. This interruption not only affects the normal operation of the system, but may also cause data loss or delays.

[0019] Therefore, how to load and update configuration data online without disturbing the normal operation of the industrial communication gateway to achieve dynamic adjustment of link and device parameters is the main problem faced in the existing technology.

[0020] In view of the problems existing in the prior art, this application proposes an online non-disturbance loading configuration method for industrial communication gateways. This application classifies incremental configuration into link-level parameter modification, device-level parameter modification, link addition and deletion, device addition and deletion, etc., and implements differentiated online non-disturbance loading configuration processing strategies based on the principle of minimum disturbance for various situations; this application is also applicable to single-machine non-disturbance loading, redundant dual-machine non-disturbance loading, cluster non-disturbance loading, etc.

[0021] Before introducing the technical solution of the present application in detail, the structure of the industrial communication gateway involved in the technical solution of the present application in actual scenarios is first introduced in detail with reference to the accompanying drawings and specific embodiments. Figure 1 Schematic diagram of the structural framework of the industrial communication gateway involved in the actual scenario of the embodiment of the present application. Figure 1 As shown, the industrial communication gateway may specifically include the following contents:

[0022] 1. Data service layer:

[0023] Data access service: Provides data access capabilities for Customer A, Customer B, and Customer C.

[0024] Internal real-time database: used to store real-time data.

[0025] Internal historical database: used to store historical data.

[0026] Driver framework management: manage the framework of various drivers.

[0027] Internal high-speed software line: connects and supports data transmission and processing at all levels.

[0028] 2. Internal affairs layer:

[0029] Manages internal data processing and task allocation between the data service layer and the application protocol layer.

[0030] 3. Application protocol layer:

[0031] Modbus RTU driver: implements Modbus protocol based on serial communication.

[0032] Modbus TCP driver: implements Modbus protocol based on TCP / IP network.

[0033] IEC104 driver: implements the IEC104 protocol for power system monitoring and control communications.

[0034] Ethernet 103 driver: implements the IEC 60870-5-103 protocol based on Ethernet.

[0035] Timing driver: realizes time synchronization and calibration of equipment.

[0036] 4. General transport layer:

[0037] Communication base class: basic class that supports various communication protocols and realizes data transmission, reception and conversion.

[0038] 5. Motherboard layer:

[0039] Serial port mainboard: supports communication with serial port devices.

[0040] Wireless motherboard: supports communication with wireless devices.

[0041] Ethernet Mainboard: Supports communication with Ethernet devices.

[0042] Custom motherboard: supports communication with devices with specific requirements.

[0043] 6. On-site equipment:

[0044] Serial port device: connect and communicate through the serial port motherboard.

[0045] Wireless devices: connect and communicate via wireless motherboard.

[0046] Ethernet Device: Connects and communicates via the Ethernet motherboard.

[0047] Custom devices: connect and communicate through a custom motherboard.

[0048] Furthermore, the basic operation process of the industrial communication gateway is as follows:

[0049] 1) Customer requests data access:

[0050] Clients A, B, and C request data through the data access service.

[0051] 2) Data processing and storage:

[0052] The data access service obtains data from an internal real-time database or an internal historical database.

[0053] 3) Driver framework management:

[0054] Select the corresponding driver module according to different communication protocols (such as Modbus RTU, Modbus TC IEC104, Ethernet 103, timing driver).

[0055] 4) Protocol conversion and data transmission:

[0056] The communication base class of the general transport layer converts and transmits data according to the protocol requirements.

[0057] 5) Device communication:

[0058] Communicate with field devices through the corresponding motherboard layer (serial port motherboard, wireless motherboard, Ethernet motherboard, custom motherboard).

[0059] Figure 1 The specific structure of the industrial communication gateway involved in the technical solution of this application in actual scenarios is demonstrated, and the above embodiments introduce in detail the functions and roles of each layer and module. This structural design ensures that the industrial communication gateway can support multiple communication protocols in a complex industrial automation environment, provide stable and efficient data access services, and support the access and communication of various external devices.

[0060] Based on the structural framework of the above-mentioned industrial communication gateway, the contents of the technical solution of the present application are described in detail below in conjunction with the accompanying drawings and specific embodiments.

[0061] Figure 2 It is a flow chart of the online non-intrusive loading configuration method of the industrial communication gateway provided in the embodiment of the present application. Figure 2 The online non-intrusive loading configuration method of the industrial communication gateway can be executed by the industrial communication gateway. Figure 2 As shown, the online non-intrusive loading configuration method of the industrial communication gateway may specifically include:

[0062] S201, obtaining new configuration data, and saving or downloading the new configuration data to the local configuration data directory of the industrial communication gateway to overwrite the original configuration data;

[0063] S202, in response to a triggering operation on a non-intrusive reload command, receiving a non-intrusive reload command, comparing configuration data in a running memory of the industrial communication gateway with new configuration data in a local configuration data directory to identify a configuration change item;

[0064] S203, according to the identified configuration change items, according to the preset non-disturbance reload policy corresponding to the configuration change items, perform a non-disturbance reload operation corresponding to the non-disturbance reload policy, wherein the configuration change items include links, devices, labels, link configuration parameters and device configuration parameters.

[0065] In some embodiments, when the configuration change item is a link configuration parameter, according to the preset non-bumping reload policy corresponding to the configuration change item, performing a non-bumping reload operation corresponding to the non-bumping reload policy includes:

[0066] Obtain link configuration parameters that need to be modified, classify the types of link configuration parameters according to preset link configuration parameter types, and perform a non-disturbance reload operation on the link configuration parameters according to the non-disturbance reload strategy corresponding to the preset link configuration parameter type; wherein the link configuration parameter type includes link configuration parameters involving the increase or decrease of the number of parameters, and link configuration parameters not involving the increase or decrease of the number of parameters.

[0067] Specifically, the link configuration parameters that need to be modified are collected, and are distinguished and processed according to the types of link configuration parameters. In actual applications, the link configuration parameters include but are not limited to the following parameters: link IP address, port number, serial port number, baud rate, data bit, stop bit, check bit, single link mode, parallel redundant mode, cross redundant mode, reconnection timeout, reconnection interval, number of retries and number of offline times.

[0068] Furthermore, the link configuration parameters involving the addition or deletion of the number of parameters may include the following parameters: addition or deletion of the link IP address, modification of the port number, single link mode, parallel redundancy / cross redundancy. The link configuration parameters not involving the addition or deletion of the number of parameters may include the following parameters: serial port number, baud rate, data bit, stop bit, check bit modification, reconnection timeout, reconnection interval, number of retries, and number of offline times.

[0069] For example, in one example, according to different types of the above link configuration parameters, the following corresponding processing measures can be taken respectively:

[0070] For the modification of link IP address, port number, single link mode, parallel redundant mode, and cross redundant mode, reload the relevant link parameters, use thread lock to ensure consistency during the modification process, record logs after the modification is completed, and wait for the new parameters to take effect after the link is interrupted; it should be noted that the reason for using the trigger timing of link interruption is: assuming that there are 4 IPs that can be connected to the device under the link, each IP can be retried 3 times, and the communication link will be reported offline only after 3*4 reconnection failures. Link interruption means that the IP of the device currently communicating is interrupted, and the IP connection will inevitably be retried again. At this time, the link will not be reported offline.

[0071] For modification of the serial port number, baud rate, data bit, stop bit, and check bit, reload the relevant link parameters, directly modify the parameter values ​​in the memory, restart the serial port mainboard, and use a joint operation strategy to disable, close, and re-enable all relevant links in turn to ensure that the modification takes effect;

[0072] To modify the reconnection timeout, reconnection interval, number of retries, and number of offline times, directly modify the parameter values ​​in the memory without using thread locks.

[0073] In some embodiments, when the link configuration parameter type is a link configuration parameter involving the addition or deletion of the number of parameters, a non-disruptive reload operation is performed on the link configuration parameter according to a non-disruptive reload strategy corresponding to a predetermined link configuration parameter type, including:

[0074] Reload the link configuration parameters involving the increase or decrease in the number of parameters, and use the thread lock to lock the current link. Modify the link configuration parameters involving the increase or decrease in the number of parameters in the running memory of the industrial communication gateway, and release the thread lock after the modification is completed. Record the modification operation log, and when the current link is automatically reconnected after interruption, the modified link configuration parameters automatically take effect.

[0075] Specifically, reload the link configuration parameters that involve the addition and deletion of the number of parameters (such as the addition and deletion of the link IP address, the modification of the port number, the single link mode, parallel redundancy / cross redundancy). Due to the addition and deletion of the number of parameters, a thread lock is required when modifying the parameter values ​​in the memory; after modifying the parameter values ​​in the memory, only logs are recorded, and no other actions are required, because if the current link is online, the new parameter value will take effect in the subsequent automatic reconnection after the current link is disconnected.

[0076] For example, in one example, first reload the link configuration parameters: determine the type of link configuration parameters that need to be modified, such as the addition, deletion, or modification of link IP addresses, port number modification, single link mode, parallel redundant mode, or cross redundant mode. Reload these link configuration parameters involving the addition or deletion of parameter quantities into the system memory.

[0077] Next, use a thread lock: When modifying the link configuration parameters in the memory, use a thread lock to lock the current link to ensure that no data contention or inconsistency occurs during the modification process.

[0078] Furthermore, modify the parameter value in the memory: After locking the current link, make changes in the running memory of the industrial communication gateway, including the following situations:

[0079] Add, delete, and modify link IP addresses: write new IP addresses into memory or delete IP addresses that are no longer in use.

[0080] Port number modification: Write the new port number into the memory.

[0081] Single link mode, parallel redundancy mode, cross redundancy mode: modify the working mode parameters of the link, and add or delete related redundancy configurations.

[0082] Furthermore, release the thread lock and record the log:

[0083] After the modification is completed, release the thread lock to ensure that other operations can continue. Record the log of the modification operation, including the modification content, timestamp, and operator information, for subsequent review and troubleshooting.

[0084] Further, wait for the link to automatically reconnect:

[0085] Since the current link may still be online, no other action is needed immediately. The system will wait for the current link to be disconnected. During the automatic reconnection process after the link is disconnected, the new parameter value will automatically take effect and the configuration update will be completed.

[0086] Take the addition, deletion and modification of link IP addresses as an example. For example, if you need to modify the IP address of a link from 192.168.1.1 to 192.168.1.2, after locking the link, write 192.168.1.2 to the memory and delete the record of 192.168.1.1. Record the modification operation log, including the old IP address, the new IP address after modification, the modification time and the operator.

[0087] Take port number modification as an example, for example, if the port number of a link is changed from 502 to 503, after locking the link, port number 503 is written to the memory and the record of port number 502 is deleted. The modification operation log is recorded, including the old port number, the new port number after modification, the modification time, and the operator.

[0088] Take single link mode, parallel redundant mode, and cross redundant mode as examples. For example, if a link is changed from single link mode to parallel redundant mode, after locking the link, modify the working mode parameters of the link, add or delete related redundant configurations. Record the modification operation log, including the old mode, the new mode after modification, the modification time, and the operator.

[0089] Through the method of the present embodiment described above, the non-disruptive reload operation of the link configuration parameters involving the addition and deletion of the number of parameters can be realized, ensuring that the industrial communication gateway dynamically loads and updates the configuration data without affecting the normal operation. The method uses thread locks to ensure consistency during data modification, and makes the new configuration parameters effective through an automatic reconnection mechanism, thereby ensuring the stability of the system and the continuity of data.

[0090] In some embodiments, when the link configuration parameter type is a link configuration parameter that does not involve the addition or deletion of the number of parameters, a non-disturbance reload operation is performed on the link configuration parameter according to a non-disturbance reload strategy corresponding to a predetermined link configuration parameter type, including:

[0091] Reload the link configuration parameters that do not involve the increase or decrease of the number of parameters, and modify the link configuration parameters that do not involve the increase or decrease of the number of parameters in the running memory of the industrial communication gateway. After the modification is completed, restart the serial port mainboard, and perform the joint operations of disabling, closing, and re-enabling on all links in sequence to make the modified link configuration parameters take effect.

[0092] Specifically, reload the link configuration parameters that do not involve the addition or deletion of the number of parameters (such as serial port number, baud rate, data bit, stop bit, check bit modification, reconnection timeout, reconnection interval, number of retries, and number of offline times). Since it does not involve the addition or deletion of the number of parameters, the parameter values ​​in the memory can be modified directly without using a thread lock; however, after modifying the parameter values ​​in the memory, the serial port motherboard must be restarted, otherwise the parameters will not take effect.

[0093] For example, in one example, first reload the link configuration parameters: determine the link configuration parameter types that need to be modified that do not involve the number of parameters added or deleted, such as serial port number, baud rate, data bit, stop bit, parity bit, reconnection timeout, reconnection interval, number of retries, and number of offline times. Reload these link configuration parameters into the system memory.

[0094] Next, modify the parameter values ​​in the memory: directly modify the link configuration parameter values ​​that do not involve the addition or deletion of parameter quantities in the running memory of the industrial communication gateway. This includes the following situations:

[0095] Serial port number: Write the new serial port number into the memory.

[0096] Baud Rate: Write the new baud rate value to memory.

[0097] Data Bits: The number of new data bits to write into memory.

[0098] Stop Bits: Write the new stop bit value to memory.

[0099] Check Digit: Writes the new check digit setting to memory.

[0100] Reconnection timeout: Write the new reconnection timeout value into the memory.

[0101] Reconnection interval: Write the new reconnection interval value into the memory.

[0102] Retry count: Write the new retry count value to memory.

[0103] Offline times: Write the new offline times value into the memory.

[0104] Furthermore, restart the serial port mainboard: After the parameter values ​​in the memory are modified, the serial port mainboard must be restarted to make the new configuration parameters take effect.

[0105] Furthermore, a joint operation is performed: the joint operations of disabling, closing, and re-enabling are performed sequentially on all links to ensure that the modified link configuration parameters take effect.

[0106] Take the modification of the serial port number, baud rate, data bit, stop bit, and check bit as an example. For example, the serial port number of a link is changed from COM1 to COM2, the baud rate is changed from 9600 to 115200, the data bit is changed from 8 to 7, the stop bit is changed from 1 to 2, and the check bit is changed from no check to odd check. The new serial port number, baud rate, data bit, stop bit, and check bit are written to the corresponding positions in the memory respectively. Record the modification operation log, including the modification content, timestamp, and operator information.

[0107] Take the modification of the reconnection timeout, reconnection interval, number of retries, and number of offline times as an example. For example, the reconnection timeout of a link is changed from 30 seconds to 20 seconds, the reconnection interval is changed from 10 seconds to 5 seconds, the number of retries is changed from 3 times to 5 times, and the number of offline times is changed from 5 times to 3 times. The new reconnection timeout, reconnection interval, number of retries, and number of offline times are written to the corresponding locations in the memory respectively. The modification operation log is recorded, including the modification content, timestamp, and operator information.

[0108] Furthermore, after modifying the parameter values ​​in the memory, restart the serial port motherboard to apply the new parameters. Send a restart command through the system command or control interface to ensure that the serial port motherboard restarts and loads the new configuration parameters. Perform the following joint operations of disabling, shutting down, and re-enabling on all links in sequence:

[0109] Disable link: Stop the operation of the link.

[0110] Close link: Disconnect the link.

[0111] Re-enable link: Restart the link to restore it to normal operation.

[0112] For example, in another example, taking the modification of the slogan, baud rate, data bit, stop bit, and check bit as an example, the implementation process of the above parameter modification is as follows:

[0113] Collect all the links whose parameters are modified (assuming there are N links):

[0114] Step 1: Traverse these N links

[0115] Forbidden link i (0≤i<N)

[0116] Close Link i

[0117] Step 2: Traverse these N links again

[0118] Open the link with new parameters

[0119] Unban link i

[0120] It should be noted that the joint operation of N links is necessary: ​​assuming that among the modified links, the serial port numbers of the two links A and B are swapped, if the joint operation is not performed, one of the new links will inevitably be opened repeatedly.

[0121] Through the method of the present embodiment described above, a non-disruptive reload operation of link configuration parameters that do not involve the addition or deletion of parameter quantities can be achieved, ensuring that the industrial communication gateway dynamically loads and updates configuration data without affecting normal operation. This method ensures that the new configuration parameters take effect by directly modifying the parameter values ​​in the memory, restarting the serial port motherboard, and performing joint operations, thereby ensuring the stability of the system and the continuity of data.

[0122] In some embodiments, when the configuration change item is a device configuration parameter, according to the preset non-bumping reload policy corresponding to the configuration change item, a non-bumping reload operation corresponding to the non-bumping reload policy is performed, including:

[0123] When the device configuration parameters are parameters related to communication transactions, the device initialization function is modified to be repeatedly callable, and new device configuration parameters are obtained. When the device is in an idle state, the device is locked using a thread lock, and the device initialization function is re-executed to reload and apply the new device configuration parameters.

[0124] When the device configuration parameters are parameters unrelated to the communication transaction, the device configuration parameters that need to be modified are obtained, and the device configuration parameters that need to be modified are modified in the running memory of the industrial communication gateway.

[0125] Specifically, the modification of device configuration parameters is divided into the following situations and implemented differently:

[0126] Scenario 1: Parameter modification related to communication transactions

[0127] These parameters include: slave device address, communication timeout, transmission delay, addition, deletion and modification of read requests, device type, time calibration start and stop, fixed-point time calibration, time calibration address modification, time calibration cycle modification, test frame addition, deletion and modification, return request addition, deletion and modification, fixed value group addition, deletion and modification, CRC (cyclic redundancy check) high and low order in the message, and automatic forwarding function.

[0128] To modify this type of parameters, the existing driver's device initialization function Init() method must be modified to be callable repeatedly. Re-execute the device Init(). Note that you need to wait until the device is idle before executing Init(). Device idle means that the device is not in any send / receive transaction activities. Therefore, it is necessary to use a thread lock. Taking the Modbus driver as an example, you can directly use the recursive lock in the Modbus protocol class in Init(). This can prevent the driver from still performing concurrent receive or send transaction activities during Init().

[0129] By modifying the initialization function of the device driver so that it can be called multiple times during device operation and re-initialized when the device is idle, the communication transaction-related parameters can be modified without disruption. This method ensures the stability of the device and the consistency of data during parameter modification, and avoids data conflicts or errors caused by concurrent operations. The use of a thread lock mechanism further ensures the security and effectiveness of the initialization process.

[0130] Scenario 2: Parameter modification not related to communication transaction

[0131] These parameters include: driver name, driver alias. Obviously, the modification of these parameters will not affect the communication between the driver and the underlying device.

[0132] For the modification of such parameters, since the modification of these parameters does not involve the increase or decrease of quantity and will not affect the communication between the driver and the underlying device, the parameter value in the memory can be modified directly without using thread locks to synchronize the modification process.

[0133] In actual applications, first collect all the parameters that need to be modified, including the driver name and driver alias. Next, record the device information that needs to be modified. Then, modify the parameters in the memory, such as directly modifying the device parameters in the memory, including the driver name and driver alias. Since the modification of these parameters does not involve the addition or deletion of quantities and does not affect the communication between the driver and the underlying device, they can be modified directly without using thread locks. Finally, record the log of the modification operation, including the specific modification content, timestamp, and operator information, for subsequent reference and troubleshooting.

[0134] By directly modifying the driver name and driver alias in the memory, the device parameters can be modified quickly and easily. Since the modification of these parameters will not affect the communication between the driver and the underlying device, there is no need to use thread locks to ensure data consistency. This method is simple to operate and can effectively reduce the system interruption time and ensure the stable operation of the industrial communication gateway. At the same time, by recording logs, the modification operations can be tracked and monitored to ensure the transparency and traceability of the modification process.

[0135] In some embodiments, when the configuration change item is a link, according to the preset non-bumping reload policy corresponding to the configuration change item, performing a non-bumping reload operation corresponding to the non-bumping reload policy includes:

[0136] When deleting a link, traverse each device under the link, set the tag status of all devices under the link to invalid, stop the operation of all devices under the link, set the device status to prohibited, stop the operation of the link, and set the link status to prohibited;

[0137] When a new link is added, a new link is created and basic communication parameters of the new link are configured. Devices are added to the new link and all devices under the new link are initialized. The new link is started to start link work.

[0138] Specifically, when you need to delete a link, perform the following steps:

[0139] 1) Traverse each device under the link:

[0140] Traverse all devices under the link to be deleted and obtain the device list.

[0141] 2) Set the device tag status to invalid:

[0142] Set the tag status of all devices in the link to invalid, marking these devices as no longer in use. For example, set the tag status of device A, device B, and device C to invalid.

[0143] 3) Stop the equipment:

[0144] Stop all devices in the link to ensure that they no longer transmit data or communicate. For example, stop device A, device B, and device C.

[0145] 4) Set the device status to disabled:

[0146] Set the status of all devices in the link to disabled to prevent them from starting again. For example, set the status of device A, device B, and device C to disabled.

[0147] 5) Stop link operation:

[0148] Stop the link so that it no longer receives or sends data. For example, stop link 1.

[0149] 6) Set the link status to disabled:

[0150] Set the link status to disabled to ensure that the link is no longer used. For example, set the link 1 status to disabled.

[0151] Furthermore, when a new link needs to be added, perform the following steps:

[0152] 1) Create a new link:

[0153] Create a new link instance and configure the basic communication parameters of the new link. For example, create link 2 and set its IP address, port number, link mode and other parameters.

[0154] 2) Add a device to the new link:

[0155] Add the devices to be connected to the new link and initialize them. For example, add devices D, E, and F to link 2.

[0156] 3) Initialize all devices under the link:

[0157] Initialize all devices under the new link and set basic parameters of the devices (such as device address, communication parameters, etc.). Reinitialize the OPC UA address space to ensure that the devices can register and communicate correctly. For example, initialize device D, device E, and device F, and reinitialize the OPC UA address space.

[0158] 4) Start link work:

[0159] Start the new link and put it into normal communication and data transmission state. For example, start the work (StartWork) of link 2 to ensure that it starts to receive and send data.

[0160] In a specific example, deleting a link may include the following operations: Assume that link 1 needs to be deleted, and there are devices A, B, and C under the link. Traverse the device list and set the tag status of devices A, B, and C to invalid. Stop the operation of devices A, B, and C, and set their status to prohibited. Stop the operation of link 1, and set the status of link 1 to prohibited.

[0161] In another specific example, adding a new link may include the following operations: Assume that link 2 needs to be added, and devices D, E, and F are added. Create link 2 and configure its basic communication parameters (such as IP address, port number, etc.). Add devices D, E, and F to link 2 and initialize them. Reinitialize the OPC UA address space to ensure that devices D, E, and F can register and communicate correctly. Start link 2 to enable it to enter normal operation.

[0162] Through the method of the above embodiment, the non-disruptive reload operation of the link configuration change can be realized, ensuring that the industrial communication gateway dynamically loads and updates the link configuration data without affecting the normal operation. The method includes specific operation steps for deleting links and adding new links, and ensures the stability of the system and the continuity of data by setting the device tag status, stopping the device operation, initializing the device and starting the link operation.

[0163] In some embodiments, when the configuration change item is a device, according to the preset non-bumpy reload policy corresponding to the configuration change item, a non-bumpy reload operation corresponding to the non-bumpy reload policy is performed, including:

[0164] When deleting a device, traverse each device to be deleted under the link, set the tags of all devices to be deleted under the link to invalid, stop all devices to be deleted under the link, and set the status of all devices to be deleted under the link to prohibited;

[0165] When a new device is added, the currently running link is suspended, the new device is added to the link, and the new device is initialized. After the device is initialized, the link is restarted and the communication status of the link and the new device is checked.

[0166] Specifically, when you need to delete a device, perform the following steps:

[0167] 1) Traverse each device that needs to be deleted under the link:

[0168] Get a list of all devices that need to be deleted under the link.

[0169] 2) Set the device tag to invalid:

[0170] Set the tag status of all devices to be deleted under the link to invalid, marking these devices as no longer in use. For example, set the tag status of device X, device Y, and device Z to invalid.

[0171] 3) Stop the equipment:

[0172] Stop all devices that need to be deleted on the link to ensure that they no longer transmit data and communicate. For example, stop the operation of device X, device Y, and device Z.

[0173] 4) Set the device status to disabled:

[0174] Set the status of all devices to be deleted under the link to disabled to prevent them from starting again. For example, set the status of device X, device Y, and device Z to disabled.

[0175] Furthermore, when a new device needs to be added, perform the following steps:

[0176] 1) Apply to suspend the link:

[0177] Apply to suspend the currently running link to ensure that the existing communication tasks are not affected during the operation of the new device.

[0178] 2) Execute the pause link:

[0179] Pause the operation of the link, stop data transmission and communication activities. For example, suspend the operation of link A.

[0180] 3) Add a new device to the link:

[0181] Add new devices to the link. For example, add devices M, N, and O to link A.

[0182] 4) Initialize the new device:

[0183] Initialize the new device and set the basic parameters of the device (such as device address, communication parameters, etc.). Reinitialize the OPC UA address space to ensure that the new device can register and communicate correctly. For example, initialize device M, device N, and device O, and reinitialize the OPC UA address space.

[0184] 5) Restart the link:

[0185] After the device is initialized, restart the link to restore normal communication and data transmission. For example, restart the work of link A (StartWork).

[0186] 6) Check the communication status:

[0187] Check the communication status of the link and the new device to ensure that they can transmit data normally. For example, ensure that device M, device N, and device O can communicate normally in link A.

[0188] In a specific example, deleting a device may include the following operations: Assume that it is necessary to delete device X, device Y, and device Z under link A. Traverse the device list and set the tag status of device X, device Y, and device Z to invalid. Stop the operation of device X, device Y, and device Z, and set their status to prohibited.

[0189] In another specific example, adding a new device may include the following operations: Assume that you need to add device M, device N, and device O to link A. Apply to pause link A and ensure that the pause operation does not affect the ongoing critical communication tasks. Pause the operation of link A and stop data transmission and communication activities. Add device M, device N, and device O to link A and initialize them. Reinitialize the OPC UA address space to ensure that device M, device N, and device O can register and communicate correctly. Restart the operation of link A to restore it to normal operation. Check the communication status of link A and device M, device N, and device O to ensure that they can transmit data normally.

[0190] Through the method of the above embodiment, non-disruptive reload operation of device configuration changes can be achieved, ensuring that the industrial communication gateway dynamically loads and updates device configuration data without affecting normal operation. The method includes specific operation steps for deleting devices and adding new devices, and ensures system stability and data continuity by setting device tag status, stopping device operation, initializing devices, and restarting link operation.

[0191] In some embodiments, when the configuration change item is a tag, according to the preset non-bumping reload policy corresponding to the configuration change item, a non-bumping reload operation corresponding to the non-bumping reload policy is performed, including:

[0192] When deleting a tag, the delete attribute of the deleted tag is set to true, and the deleted tag is retained in the running memory of the industrial communication gateway;

[0193] When adding a new tag, the currently running link is suspended, all devices to which the new tag belongs are initialized, and the link is restarted after the initialization is completed.

[0194] Specifically, when you need to delete a tag, perform the following steps:

[0195] 1) Set the tag deletion properties:

[0196] Set the delete attribute of the tags to be deleted to true, marking these tags as deleted. For example, if you want to delete tags T1, T2, and T3, set the delete attribute of tags T1, T2, and T3 to true.

[0197] 2) Keep the label in memory:

[0198] The deleted tags are retained in the running memory of the industrial communication gateway and are not actually deleted from the memory. This step ensures that the deleted tags are still available when they need to be restored or queried.

[0199] Furthermore, when a new tag needs to be added, perform the following steps:

[0200] 1) Apply to suspend the link:

[0201] Apply to suspend the currently running link to ensure that the existing communication tasks are not affected during the operation of adding new tags.

[0202] 2) Execute the pause link:

[0203] Pause the operation of the link, stop data transmission and communication activities. For example, suspend the operation of link B.

[0204] 3) Initialize the device to which the newly added tag belongs:

[0205] Initialize all devices to which the newly added tags belong to ensure that the devices can correctly identify and process the new tags. For example, devices D, E, and F to which the newly added tags T4, T5, and T6 belong need to be initialized.

[0206] 4) Restart the link:

[0207] After the device initialization is completed, restart the link to restore normal communication and data transmission. For example, restart the work of link B (StartWork).

[0208] In a specific example, in an industrial communication system, some unused monitoring tags need to be deleted, such as tags T1, T2, and T3 of temperature sensors. The deletion attribute of these tags is set to true and retained in memory for subsequent query or recovery.

[0209] For example, deleting a label may include the following operations: Assume that you need to delete labels T1, T2, and T3 under link B. Set the delete attribute of labels T1, T2, and T3 to true and mark them as deleted. Keep labels T1, T2, and T3 in the running memory without actually deleting them so that they can be restored or queried later when needed.

[0210] In another specific example, when expanding system functions, new monitoring tags need to be added, such as tags T4, T5, and T6 for pressure sensors. Apply to suspend the relevant links, initialize the devices to which the tags belong, and restart the links so that the system can normally identify and process the newly added tag data.

[0211] For example, adding new tags may include the following operations: Assume that you need to add tags T4, T5, and T6 to link B. Apply to suspend link B and ensure that the suspension operation does not affect the ongoing critical communication tasks. Suspend the operation of link B and stop data transmission and communication activities. Initialize devices D, E, and F to which the newly added tags T4, T5, and T6 belong, and ensure that these devices can correctly identify and process the new tags. Restart the operation of link B to restore it to normal operation.

[0212] Through the method of the above embodiment, a non-disruptive reload operation of tag configuration changes can be achieved, ensuring that the industrial communication gateway dynamically loads and updates tag configuration data without affecting normal operation. The method includes specific operation steps for deleting tags and adding tags, and ensures system stability and data continuity by setting tag deletion attributes, retaining tags in memory, pausing links, initializing devices, and restarting links.

[0213] Based on the above method for non-intrusive loading configuration, the embodiment of the present application provides a specific implementation process of non-intrusive loading configuration in three different modes. The implementation process of the non-intrusive loading configuration scheme in these three different modes is described in detail below in combination with specific embodiments, which may specifically include the following contents:

[0214] Mode 1: Standalone mode

[0215] 1. The new configuration data is successfully saved or successfully downloaded to the local configuration data directory of the gateway, overwriting the old configuration data.

[0216] 2. Trigger a non-intrusive reload command (externally or manually).

[0217] 3. After receiving the non-intrusive reload command, the gateway compares the configuration in the current running gateway memory with the configuration data in the gateway local disk, and identifies the changes: 1) deleting a link; 2) adding a link; 3) adding a device (the link is an existing one); 4) deleting a device (the link is an existing one); 5) deleting a label (the device is an existing one); 6) adding a label (the device is an existing one); 7) modifying the link configuration parameters; 8) modifying the device configuration parameters.

[0218] 4. Perform non-intrusive reload: 1) Delete link - set all device labels under the link to invalid, stop all devices under the link and set the devices to prohibited, stop the link and set the link to prohibited; 2) Add a new link - initialize the link, initialize all devices under the link, and start link work StartWork(); 3) Add a new device (the link is an existing one) - apply to pause the link, execute the link pause, initialize all new devices, and restart the link work; 4) Delete device (the link is an existing one) - prohibit all deleted devices under the link; 5) Delete tag (the device is an existing one) - set the deletion attribute of the deleted tag to true, but do not delete it from the memory; 6) Add a new tag (the device is an existing one) - apply to pause the link, execute the link pause, initialize all devices to which the new tag belongs, and restart the link work; 7) Modify link configuration parameters - refer to the content of the aforementioned embodiment; 8) Modify device configuration parameters - refer to the content of the aforementioned embodiment.

[0219] Mode 2: Redundancy mode

[0220] When the gateway is in redundant working mode (IO-A—actual master, IO-B—actual backup), it is necessary to perform non-disruptive reload respectively. For example, the specific implementation process is as follows:

[0221] In the first step, the modified new configuration data of IO-A and IO-B are successfully saved or successfully downloaded to the local configuration data directory of the gateway, overwriting the old configuration data.

[0222] The second step is to perform IO-B non-disturbance reload in stand-alone mode.

[0223] In the third step, IO-A first determines the status of IO-B. If it is good, it first switches its own (IO-A) link to the backup link, and then upgrades the IO-B link to the master link.

[0224] The fourth step is to perform IO-A non-disturbance reload in stand-alone mode. The non-disturbance reload method in stand-alone mode will not be repeated here.

[0225] Step 5: IO-A determines its own status. If it is good, it first switches the IO-B link to the backup status, and then upgrades the IO-A link to the master status.

[0226] Step 6: traverse all links that need to perform non-intrusive reloading, and execute steps 2 to 5 for each link in turn.

[0227] At this point, the whole machine is reloaded without disturbance in redundant mode.

[0228] It should be noted that when the primary and standby redundant machines perform data synchronization, they must synchronize on a device-by-device basis, and before synchronization, the online data version number of each device must be checked. When the online data version of the synchronized data is inconsistent with the synchronized data, the synchronized data will not be synchronized. The advantage of refining the version verification granularity of data synchronization to the device-by-device basis is that during data synchronization, the primary and standby machines can each independently reload data without interference based on the stand-alone mode, without introducing other intermediate state conversions (such as switching to the test machine state or the suspended state to avoid data misuse during switching).

[0229] Mode 3: Cluster Mode

[0230] The cluster mode is equivalent to N independent single-machine modes. For the non-disturbance reloading method in the single-machine mode, please refer to the content of the aforementioned embodiment, which will not be repeated here.

[0231] According to the technical solution provided in the embodiments of the present application, the technical solution of the present application has at least the following advantages:

[0232] 1. No need to rely on high-performance software and hardware:

[0233] The method of the present application does not require high-performance software and hardware support to achieve online non-intrusive loading configuration. This means that the system can be directly applied on existing hardware and software platforms without the need for additional hardware upgrades or expensive software licenses, thereby reducing implementation costs.

[0234] 2. Applicable to any software / hardware platform:

[0235] The method of the present application has wide applicability and can be applied to various software and hardware platforms. This platform independence enables the method to be widely applied to various industrial communication systems, providing great flexibility and compatibility.

[0236] 3. Incremental configuration classification and differentiated processing strategy:

[0237] This application divides incremental configuration into link-level parameter modification, device-level parameter modification, link addition and deletion, device addition and deletion, etc. For different configuration changes, the principle of minimum disturbance is adopted to implement differentiated online non-disturbance loading configuration processing strategies. Through this classification processing method, the impact of configuration updates on the normal operation of the system can be minimized to the greatest extent, ensuring the stability and continuity of the system.

[0238] 4. Applicable to various loading situations:

[0239] The method of the present application is not only applicable to single-machine non-disturbance loading, but also to redundant dual-machine non-disturbance loading and cluster non-disturbance loading. In single-machine mode, it is possible to implement configuration updates for a single industrial communication gateway; in redundant mode, the configuration update of the redundant system is achieved through active-standby switching and synchronization; in cluster mode, the stable upgrade of the entire cluster system is achieved by performing configuration updates on each node one by one.

[0240] 5. Minimum disturbance principle:

[0241] By adopting the principle of minimum disturbance, the method of the present application can load and update configuration data online without affecting the normal operation of the system. This method can ensure that the system does not interrupt data transmission and communication during the configuration update process, thereby improving the reliability and availability of the system.

[0242] In summary, the online non-intrusive loading configuration method for the industrial communication gateway provided by this application is efficient, flexible, and platform-independent. Through classification processing and differentiation strategies, it is possible to dynamically update the system configuration in various application scenarios to ensure the stable operation of the system and the continuity of the data. These technical effects make this method have broad application prospects and significant technical advantages in industrial automation systems.

[0243] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0244] Figure 3 Schematic diagram of the structure of the online non-intrusive loading configuration device of the industrial communication gateway provided in the embodiment of the present application. Figure 3 As shown, the online non-intrusive loading configuration device of the industrial communication gateway includes:

[0245] The acquisition module 301 is configured to acquire new configuration data and save or download the new configuration data to a local configuration data directory of the industrial communication gateway to overwrite the original configuration data;

[0246] The identification module 302 is configured to receive the non-intrusive reload command in response to a triggering operation on the non-intrusive reload command, compare the configuration data in the running memory of the industrial communication gateway with the new configuration data in the local configuration data directory to identify the configuration change item;

[0247] The loading module 303 is configured to perform a non-disturbance reload operation corresponding to the non-disturbance reload strategy according to the identified configuration change items and the preset non-disturbance reload strategy corresponding to the configuration change items, wherein the configuration change items include links, devices, labels, link configuration parameters and device configuration parameters.

[0248] In some embodiments, when the configuration change item is a link configuration parameter, Figure 3 The loading module 303 obtains the link configuration parameters that need to be modified, divides the types of link configuration parameters according to preset link configuration parameter types, and performs a non-disturbance reload operation on the link configuration parameters according to the non-disturbance reload strategy corresponding to the preset link configuration parameter type; wherein the link configuration parameter type includes link configuration parameters involving the increase or decrease of the number of parameters, and link configuration parameters not involving the increase or decrease of the number of parameters.

[0249] In some embodiments, when the link configuration parameter type is a link configuration parameter involving the addition or deletion of the number of parameters, Figure 3 The loading module 303 reloads the link configuration parameters involving the increase or decrease of the number of parameters, and uses the thread lock to lock the current link, modifies the link configuration parameters involving the increase or decrease of the number of parameters in the running memory of the industrial communication gateway, and releases the thread lock after the modification is completed, records the modification operation log, and when the current link is automatically reconnected after interruption, the modified link configuration parameters automatically take effect.

[0250] In some embodiments, when the link configuration parameter type is a link configuration parameter that does not involve adding or deleting the number of parameters, Figure 3 The loading module 303 reloads the link configuration parameters that do not involve the increase or decrease of the number of parameters, and modifies the link configuration parameters that do not involve the increase or decrease of the number of parameters in the running memory of the industrial communication gateway, and restarts the serial port mainboard after the modification is completed, and performs the joint operations of disabling, closing, and re-enabling on all links in sequence to make the modified link configuration parameters take effect.

[0251] In some embodiments, when the configuration change item is a device configuration parameter, Figure 3The loading module 303 modifies the initialization function of the device to be repeatedly callable when the device configuration parameters are parameters related to the communication transaction, and obtains new device configuration parameters. When the device is in an idle state, the device is locked using a thread lock, and the initialization function of the device is re-executed to reload and apply the new device configuration parameters. When the device configuration parameters are parameters unrelated to the communication transaction, the device configuration parameters that need to be modified are obtained, and the device configuration parameters that need to be modified are modified in the running memory of the industrial communication gateway.

[0252] In some embodiments, when the configuration change item is a link, Figure 3 When deleting a link, the loading module 303 traverses each device under the link, sets the tag status of all devices under the link to invalid, stops the operation of all devices under the link, sets the status of the devices to prohibited, stops the operation of the link, and sets the status of the link to prohibited; when adding a new link, creates a new link, configures the basic communication parameters of the new link, adds devices to the new link, initializes all devices under the new link, and starts the new link to start link work.

[0253] In some embodiments, when the configuration change item is a device, Figure 3 When deleting a device, the loading module 303 traverses each device that needs to be deleted under the link, sets the labels of all devices that need to be deleted under the link to invalid, stops all devices that need to be deleted under the link, and sets the status of all devices that need to be deleted under the link to prohibited; when adding a new device, pauses the currently running link, adds the new device to the link, initializes the new device, restarts the link after the device is initialized, and checks the communication status of the link and the new device.

[0254] In some embodiments, when the configuration change item is a tag, Figure 3 When deleting a tag, the loading module 303 sets the deletion attribute of the deleted tag to true, and retains the deleted tag in the running memory of the industrial communication gateway; when adding a new tag, the currently running link is paused, all devices belonging to the newly added tags are initialized, and the link is restarted after the initialization is completed.

[0255] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0256] Figure 4 Schematic diagram of an electronic device 4 provided in an embodiment of the present application. Figure 4As shown, the electronic device 4 of this embodiment includes: a processor 401, a memory 402, and a computer program 403 stored in the memory 402 and executable on the processor 401. When the processor 401 executes the computer program 403, the steps in the above-mentioned method embodiments are implemented. Alternatively, when the processor 401 executes the computer program 403, the functions of the modules / units in the above-mentioned device embodiments are implemented.

[0257] The electronic device 4 may be a desktop computer, a notebook, a PDA, a cloud server, or other electronic device. The electronic device 4 may include, but is not limited to, a processor 401 and a memory 402. Those skilled in the art will appreciate that Figure 4 The electronic device 4 is merely an example and does not limit the electronic device 4 , and may include more or less components than those shown in the figure, or different components.

[0258] The processor 401 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0259] The memory 402 may be an internal storage unit of the electronic device 4, for example, a hard disk or memory of the electronic device 4. The memory 402 may also be an external storage device of the electronic device 4, for example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 4. The memory 402 may also include both an internal storage unit and an external storage device of the electronic device 4. The memory 402 is used to store computer programs and other programs and data required by the electronic device.

[0260] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0261] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium (e.g., a computer-readable storage medium). Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. The computer program may include computer program code, which may be in source code form, object code form, executable file or some intermediate form. Computer-readable storage media may include: any entity or device capable of carrying computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc.

[0262] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. An online non-intrusive loading configuration method for an industrial communication gateway, characterized in that: include: Obtain new configuration data, and save or download the new configuration data to a local configuration data directory of the industrial communication gateway to overwrite the original configuration data; In response to a trigger operation on a non-intrusive reload command, receiving a non-intrusive reload command, comparing configuration data in the running memory of the industrial communication gateway with new configuration data in the local configuration data directory to identify configuration changes; According to the identified configuration change items, according to the preset non-disturbance reload policy corresponding to the configuration change items, a non-disturbance reload operation corresponding to the non-disturbance reload policy is performed, wherein the configuration change items include links, devices, labels, link configuration parameters and device configuration parameters.

2. The method according to claim 1, characterized in that When the configuration change item is a link configuration parameter, performing a bumpless reload operation corresponding to the bumpless reload policy according to the preset bumpless reload policy corresponding to the configuration change item includes: Obtain link configuration parameters that need to be modified, classify the types of the link configuration parameters according to preset link configuration parameter types, and perform a non-disturbance reload operation on the link configuration parameters according to the non-disturbance reload strategy corresponding to the preset link configuration parameter type; wherein the link configuration parameter type includes link configuration parameters involving the increase or decrease of the number of parameters, and link configuration parameters not involving the increase or decrease of the number of parameters.

3. The method according to claim 2, characterized in that When the link configuration parameter type is a link configuration parameter involving the addition or deletion of the number of parameters, performing a non-bumping reload operation on the link configuration parameter according to a predetermined non-bumping reload strategy corresponding to the link configuration parameter type includes: The link configuration parameters involving the increase or decrease in the number of parameters are reloaded, and the current link is locked using a thread lock. The link configuration parameters involving the increase or decrease in the number of parameters are modified in the running memory of the industrial communication gateway, and the thread lock is released after the modification is completed. The modification operation log is recorded, and when the current link is automatically reconnected after being interrupted, the modified link configuration parameters automatically take effect.

4. The method according to claim 2, characterized in that When the link configuration parameter type is a link configuration parameter that does not involve the addition or deletion of the number of parameters, performing a non-disturbance reload operation on the link configuration parameter according to a predetermined non-disturbance reload strategy corresponding to the link configuration parameter type includes: The link configuration parameters that do not involve the increase or decrease of the number of parameters are reloaded, and the link configuration parameters that do not involve the increase or decrease of the number of parameters are modified in the running memory of the industrial communication gateway. After the modification is completed, the serial port mainboard is restarted, and the joint operations of disabling, closing, and re-enabling are performed on all links in sequence to make the modified link configuration parameters take effect.

5. The method according to claim 1, characterized in that When the configuration change item is a device configuration parameter, performing a bumpless reload operation corresponding to the bumpless reload strategy according to the preset bumpless reload strategy corresponding to the configuration change item includes: When the device configuration parameter is a parameter related to a communication transaction, the initialization function of the device is modified to be repeatedly callable, and new device configuration parameters are obtained. When the device is in an idle state, the device is locked using a thread lock, and the initialization function of the device is re-executed to reload and apply the new device configuration parameters. When the device configuration parameter is a parameter unrelated to the communication transaction, the device configuration parameter that needs to be modified is obtained, and the device configuration parameter that needs to be modified is modified in the running memory of the industrial communication gateway.

6. The method according to claim 1, characterized in that When the configuration change item is a link, performing a bumpless reload operation corresponding to the bumpless reload strategy according to the preset bumpless reload strategy corresponding to the configuration change item includes: When deleting a link, traverse each device under the link, set the tag status of all devices under the link to invalid, stop the operation of all devices under the link, set the device status to prohibited, stop the operation of the link, and set the link status to prohibited; When a new link is added, a new link is created, and basic communication parameters of the new link are configured. A device is added to the new link, and all devices under the new link are initialized, and the new link is started to start link work.

7. The method according to claim 1, characterized in that When the configuration change item is a device, performing a non-bumpy reload operation corresponding to the non-bumpy reload policy according to the preset non-bumpy reload policy corresponding to the configuration change item includes: When deleting a device, traverse each device to be deleted under the link, set the tags of all devices to be deleted under the link to invalid, stop all devices to be deleted under the link, and set the status of all devices to be deleted under the link to prohibited; When a new device is added, the currently running link is suspended, the new device is added to the link, and the new device is initialized. After the device is initialized, the link is restarted, and the communication status of the link and the new device is checked.

8. The method according to claim 1, characterized in that When the configuration change item is a tag, performing a non-bumpy reload operation corresponding to the non-bumpy reload strategy according to the preset non-bumpy reload strategy corresponding to the configuration change item includes: When deleting a tag, setting the deletion attribute of the deleted tag to true, and retaining the deleted tag in the running memory of the industrial communication gateway; When adding a new tag, the currently running link is suspended, all devices to which the new tag belongs are initialized, and the link is restarted after the initialization is completed.

9. An online non-intrusive loading configuration device for an industrial communication gateway, characterized in that: include: An acquisition module is configured to acquire new configuration data, and save or download the new configuration data to a local configuration data directory of the industrial communication gateway to overwrite the original configuration data; an identification module configured to respond to a trigger operation on the non-intrusive reload command, receive the non-intrusive reload command, compare the configuration data in the running memory of the industrial communication gateway with the new configuration data in the local configuration data directory to identify the configuration change item; The loading module is configured to perform a non-disturbance reload operation corresponding to the non-disturbance reload strategy preset according to the identified configuration change item, wherein the configuration change item includes a link, a device, a label, a link configuration parameter and a device configuration parameter.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

Images