Method and system for importing configuration of IEC104 protocol sensor equipment of gateway machine equipment

Abstract

The invention discloses a method and a system for configuration import of an IEC104 protocol sensor device of a gateway machine device. The method comprises the following steps: defining a sensor model in a gateway machine database through a model table and a model data point table, and configuring a communication node, a sensor and a data point; secondly, an XML equipment information file meeting the Q / GDW 11509-2015 standard is improved, the attribute of a model unique identification code ssid is added to a device tag, the attribute of a model data point alias refname is added to a four-remote tag, and a station end equipment information file is generated and stored; and finally, the IEC104 client analyzes the file, matches the model and the data point, automatically generates configuration and sets link information. The system comprises a sensor model library, a communication node configuration module and the like. The problem that manual configuration is tedious and prone to errors is solved, sensor configuration is automatically imported, efficiency and accuracy are improved, existing standards are compatible, and the method is suitable for an electric power system automation scene.

Description

Technical Field

[0001] The present invention relates to a method and system for importing IEC104 protocol sensor equipment configuration for gateway equipment, belonging to transformer substation technology. Background Art

[0002] IEC104 (IEC60870-5-104) is a commonly used communication protocol in the field of power system automation. By combining the IEC101 protocol with the TCP / IP transport layer functions, it enables the monitoring and control of power equipment (such as substation auxiliary equipment and generators). It is widely used in industries such as power and urban rail transit, especially in communications between substations and master stations. It uses the TCP / IP protocol to ensure reliable data transmission to maintain stable operation of the power system.

[0003] In IEC104 protocol transmission, an Information Object Address (IOA) is assigned to each sensor data point, and the four remote data types (telesignaling, telemetering, remote control, and remote adjustment) have corresponding IOA allocation ranges. However, from the client's perspective, it is difficult to clearly understand the correspondence between IOA addresses and specific sensor data points. When no specific configuration is specified, although the data type and value of each IOA can be known through the data summary, it is unclear which sensor and data information these IOAs correspond to. Because IEC104 servers typically support the connection of multiple sensors, the client must bind the IOA addresses of all data points of all sensors one by one, a tedious and error-prone task.

[0004] The Q / GDW 11509-2015 standard, "Technical and Interface Specifications for Substation Auxiliary Monitoring Systems," specifies the design requirements and interface specifications for substation auxiliary monitoring systems. Section A.3 of the standard defines the transmission format, process, and protocol details for device information files. This file format defines the IOA addresses and four remote control types for all auxiliary devices and data points connected to the IEC104 server. However, some sensor devices may have multiple data points for the same four remote control type. This file definition makes it difficult to determine the specific data point corresponding to the IOA address, requiring manual matching. Summary of the Invention

[0005] Purpose of the invention: In order to overcome the deficiencies in the prior art, the present invention provides a method and system for importing IEC104 protocol sensor device configurations into gateway devices. Based on compatibility with the Q / GDW 11509-2015 standard, the present invention improves the original XML file to solve the tedious operation problems of on-site point-to-point configuration and avoid on-site operation errors.

[0006] Technical solution: To achieve the above purpose, the technical solution adopted by the present invention is:

[0007] A method for importing IEC104 protocol sensor device configuration for a gateway device. First, a sensor model is defined for each type of sensor in the database of the gateway device, and the sensor model is managed through a model table and a model data point table. A model unique identification code is defined in the model table, and a data point four-remote type and a model data point alias are defined in the model data point table. A specific model data point of a specific type of sensor model is indicated by the model unique identification code and the model data point alias. Then, each sensor and sensor data point are configured in the gateway device based on the sensor model and the model data point. Then, the Q / GDW compliant data provided by the sensor is processed on the IEC104 server. 11509-2015 standard XML file format is modified, and the ssid attribute for identifying the unique identification code of the model is added to the device tag of the device information file, and the refname attribute for identifying the alias of the model data point is added to the four remote tags of the device information file to form a station-side device information file; then, the station-side device information file is stored in the file access path of the IEC104 service, and the gateway device is used as the carrier of the IEC104 server, waiting for the call of the IEC104 client; finally, the IEC104 client parses the called station-side device information file, matches the sensor model according to the ssid attribute, matches the model data point under the sensor model according to the refname attribute, and automatically generates the configuration of the sensor and sensor data point on the IEC104 client based on the matched sensor model and model data point, sets the sensor data point link information to the IEC104 protocol address corresponding to the four remote tags, and completes the import of the IEC104 protocol sensor device configuration. The method includes the following steps:

[0008] Step 1: Define a sensor model for each type of sensor in the database of the gateway device, and manage the sensor model through the model table and model data point table;

[0009] Step 2: Configure the communication node in the gateway device and write the configuration information of the communication node into the database configuration table; Step 3: Configure the sensor and sensor data point in the gateway device and write the configuration information of the sensor and sensor data point into the database configuration table;

[0010] Step 4. Modify the device information file provided by the sensor in the XML file format that complies with the Q / GDW 11509-2015 standard on the IEC104 server to form a station-side device information file, which is used to express the data capabilities of the IEC104 service. The specific modifications are: add the ssid attribute to the device tag of the device information file to identify the model unique identification code, and add the refname attribute to the four remote tags of the device information file to identify the model data point alias.

[0011] Step 5. Store the station device information file in the file access path of the IEC104 service; use the gateway device as the carrier of the IEC104 server and wait for the call of the IEC104 client;

[0012] Step 6. First, configure the IEC104 client to call the communication node of the IEC104 server, and then call the IEC104 server configuration file directory corresponding to the communication node;

[0013] Step 7: After receiving the request for the IEC104 server configuration file directory, the IEC104 server returns the IEC104 server configuration file directory list containing the station device information file name to the IEC104 client;

[0014] Step 8. The IEC104 client calls the station-end device information file according to the station-end device information file name;

[0015] Step 9: After receiving the call request for the station-side device information file, the IEC104 server starts to transmit the station-side device information file to the IEC104 client.

[0016] Step 10: The IEC104 client parses the received station device information file, matches the sensor model according to the ssid attribute, and matches the model data point under the sensor model according to the refname attribute;

[0017] Step 11. Based on the matched sensor model and model data point, the configuration of the sensor and sensor data point is automatically generated on the IEC104 client. At the same time, the link information of the sensor data point is set to the IEC104 protocol address corresponding to the four remote tags.

[0018] Specifically, in Step 1, the model ID, model name and model unique identification code are defined in the model table, and the model data point ID, model data point name, model ID, data point four remote types, data point link information and model data point alias are defined in the model data point table. The model unique identification code and model data point alias are used to indicate a specific model data point of a specific type of sensor model.

[0019] Specifically, in Step 2, the configuration information of the communication node includes a communication node ID, a communication node name, a communication address, a communication mode, and a communication protocol.

[0020] Specifically, in Step 3, the sensor and sensor data point are configured based on the sensor model and model data point; the configuration information of the sensor includes the sensor ID, sensor name, communication node ID, model ID and sensor communication parameters, and the configuration information of the sensor data point includes the sensor data point ID, sensor data point name, sensor ID, model data point ID and sensor data point link information.

[0021] A system for importing IEC104 protocol sensor device configuration for gateway equipment, including a sensor model library, a communication node configuration module, a gateway-side sensor configuration module, a station-side device information file module, a station-side device information file summoning and parsing module, and an uplink platform-side sensor configuration module;

[0022] The sensor model library is used to store each type of sensor model and the model data points contained therein, and manage the sensor models through the model table and the model data point table. The model unique identification code is defined in the model table, and the data point four remote types and model data point aliases are defined in the model data point table.

[0023] The communication node configuration module is used to configure the communication nodes for communication connections between the gateway device and the sensor and the uplink platform;

[0024] The gateway terminal sensor configuration module configures each sensor and the included sensor data points in the gateway terminal based on the sensor model and the model data points;

[0025] The station-end device information file module modifies the device information file in the XML file format provided by the sensor in accordance with the Q / GDW 11509-2015 standard, adds the ssid attribute for identifying the model unique identification code in the device tag of the device information file, adds the refname attribute for identifying the model data point alias in the four remote tags of the device information file, forms the station-end device information file, and stores the station-end device information file in the file access path of the IEC104 service;

[0026] The station-end device information file summoning and parsing module summons the IEC104 server-end configuration file directory and the station-end device information file, parses the station-end device information file, matches the sensor model according to the ssid attribute, and matches the model data point under the sensor model according to the refname attribute;

[0027] The sensor configuration module on the uplink platform side automatically generates the configuration of sensors and sensor data points on the IEC104 client according to the matched sensor models and model data points, and sets the sensor data point link information to the IEC104 protocol addresses corresponding to the four remote tags.

[0028] Specifically, in the sensor model library, the model ID, model name and model unique identification code are defined in the model table, and the model data point ID, model data point name, model ID, data point four remote types, data point link information and model data point alias are defined in the model data point table. The model unique identification code and model data point alias are used to indicate a specific model data point of a specific type of sensor model.

[0029] Specifically, in the communication node configuration module, the configuration information of the communication node is written into the database configuration table; the configuration information of the communication node includes the communication node ID, the communication node name, the communication address, the communication mode and the communication protocol.

[0030] Specifically, in the gateway-side sensor configuration module, the sensor configuration information includes sensor ID, sensor name, communication node ID, model ID and sensor communication parameters, and the sensor data point configuration information includes sensor data point ID, sensor data point name, sensor ID, model data point ID and sensor data point link information.

[0031] Specifically, the gateway device is used as the carrier of the IEC104 server, and the uplink platform is used as the carrier of the IEC104 client.

[0032] Beneficial effects: The method and system for importing IEC104 protocol sensor device configurations into a gateway device provided by the present invention realize automatic import of IEC104 protocol sensor configurations by defining a sensor model in the gateway device, improving the device information file format, and designing an automated configuration import process. Compared with the prior art, the present invention has the following beneficial effects: 1. It avoids the tedious operation of manually binding IOA addresses one by one, saving manpower and time costs; 2. It reduces the errors that may be caused by manual operations and improves the accuracy and reliability of the configuration; 3. It realizes the automatic generation of sensor configurations, improves work efficiency, and facilitates rapid deployment and maintenance of the system; 4. It is compatible with the Q / GDW 11509-2015 standard, facilitating integration and docking with existing systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 It is a structural block diagram of the system of the present invention;

[0034] Figure 2 Schematic diagram of the implementation process of the method of the present invention. DETAILED DESCRIPTION

[0035] The present invention will be described in detail below with reference to the accompanying drawings and specific embodiments.

[0036] like Figure 1The system shown is a system for importing IEC104 protocol sensor device configuration for gateway equipment, including a sensor model library, a communication node configuration module, a gateway-side sensor configuration module, a station-side device information file module, a station-side device information file summoning and parsing module, and an uplink platform-side sensor configuration module. In this case, the gateway equipment is used as the carrier of the IEC104 server, and the uplink platform is used as the carrier of the IEC104 client. Operations such as defining sensor models, configuring communication nodes, configuring sensors and sensor data points, improving device information files, storing files, and waiting for summoning are performed on the IEC104 server. Operations such as configuring communication nodes, summoning file directories, obtaining file directory lists, summoning station-side device information files, receiving and parsing files, and generating sensor configurations are performed on the IEC104 client. The following is a detailed description of the embodiments and the examples below. Figure 2 The present invention is further described.

[0037] Step 1. Sensor model and data table design

[0038] A sensor model is defined for each type of sensor in the database of the gateway device, and the sensor model is managed through a model table and a model data point table. As shown in Table 1, the model ID, model name, and model unique identification code (an identifier for distinguishing different sensor models) are defined in the model table. As shown in Table 2, the model data point ID, model data point name, model ID, data point four remote types, data point link information, and model data point alias are defined in the model data point table. The model unique identification code and model data point alias are used to indicate a specific model data point of a specific type of sensor model.

[0039] Table 1 Model table examples (including but not limited to)

[0040] Field type illustrate id Number Model ID, non-null, * name String Model Name ssid String Model unique identifier

[0041] Table 2 Examples of model data points (including but not limited to)

[0042]

[0043]

[0044] Step 2. Communication node configuration

[0045] A communication node is configured in the gateway device to establish a communication connection between the gateway device and the sensor and uplink platform, and the configuration information of the communication node is written into the database configuration table; as shown in Table 3, the configuration information of the communication node includes the communication node ID, communication node name, communication address, communication mode and communication protocol.

[0046] Table 3 Communication node configuration information example (including but not limited to)

[0047] Field type illustrate Id Number Communication node ID, non-null, * name String Communication node name Commaddr String Correspondence address Commmode Number Communication method Protocoltype Number Communication Protocol

[0048] Step 3: Sensor and sensor data point configuration

[0049] Based on the sensor model and model data points, each sensor and the included sensor data points are configured in the gateway device, and the configuration information is written into the database configuration table. As shown in Table 4, the sensor configuration information includes the sensor ID, sensor name, communication node ID, model ID, and sensor communication parameters. As shown in Table 5, the sensor data point configuration information includes the sensor data point ID, sensor data point name, sensor ID, model data point ID, and sensor data point link information.

[0050] Table 4 Sensor configuration information examples (including but not limited to)

[0051] Field type illustrate Id Number Sensor ID, non-null, * name String Sensor Name commnodeid Number Communication node ID modelid Number Model ID commaddr String Sensor communication parameters

[0052] Table 5 Sensor data point configuration information example (including but not limited to)

[0053]

[0054] Step 4. Modify the device information file

[0055] The device information file that complies with the Q / GDW 11509-2015 standard "Technical and Interface Specifications for Substation Auxiliary Monitoring Systems" is provided by the equipment in the station-side auxiliary system. After obtaining it, the IEC104 server (master station) can obtain the equipment (sensors) included in the station-side auxiliary system and the IOA address information under the equipment. Through Appendix A, Section A.3.2.1, we can understand that the transmitted XML file format is shown in Table 6. Table 7 shows the contents of the XML file format fragment provided in Table 6.

[0056] Table 6 Device information file example

[0057]

[0058] Table 7 Contents of the XML file format fragment in Table 6

[0059]

[0060]

[0061] From the examples in Table 6 and Table 7, we can see that after the master station obtains the device information file, it can know what device is connected, but it cannot know what IOA address a specific data point uses. It cannot automatically match the sensor model and model data point in the gateway device, and manual matching operations are required.

[0062] Assume that the IEC104 server and IEC104 client have agreed on the models and model information points of the temperature and humidity sensor and the water pump sensor as shown in Table 8:

[0063] Table 8 Example of IEC104 server and IEC104 client conventions

[0064]

[0065] Based on the design concept of this case, the XML file format device information file needs to be modified on the IEC104 server side to form a station-side device information file, which is used to express the data capabilities of the IEC104 service. The specific modifications are: retaining the tags in the original XML file, defining attributes for some tags, adding the ssid attribute to the device tag of the device information file to identify the model's unique identifier, and adding the refname attribute to the four remote tags in the device information file (such as yx_addr, yc_addr, yk_addr, and yt_addr) to identify the alias of the model data point. The station-side device information file formed by modifying the XML file in Table 6 is shown in Table 9.

[0066] Table 9 Example of station device information file

[0067]

[0068] The modified station-side device information file can map the sensor models of the IEC104 server and the IEC104 client.

[0069] Step 5: Store the station device information file and wait for the call

[0070] When generating the IEC104 server configuration, the IEC104 server enters the model unique identification code of the sensor and the model data point alias of the sensor data point as the Tag attribute in the XML file, generates the final station device information file (the file name is agreed with the master station) and saves it to the IEC104 server configuration file directory. The IEC104 server configuration file directory and the station device information file are stored in the file access path of the IEC104 service; the gateway device is used as the carrier of the IEC104 server, waiting for the call of the IEC104 client.

[0071] Step 6. IEC104 client calls the IEC104 server configuration file directory

[0072] First, configure the communication node that calls the IEC104 server on the IEC104 client, including IP, port number, communication protocol (IEC104), etc., and then call the IEC104 server configuration file directory corresponding to the communication node.

[0073] Step 7. The IEC104 server returns the IEC104 server configuration file directory list.

[0074] After receiving the request for the IEC104 server configuration file directory, the IEC104 server returns the IEC104 server configuration file directory list including the station device information file name to the IEC104 client.

[0075] Step 8. IEC104 client summons station device information file

[0076] The IEC104 client calls the station-side device information file according to the station-side device information file name (the file name agreed with the slave).

[0077] Step 9: IEC104 server transmits station device information file

[0078] After receiving the call request for the station-side device information file, the IEC104 server starts to transmit the station-side device information file to the IEC104 client.

[0079] Step 10: IEC104 client parses the station device information file

[0080] The IEC104 client parses the received station device information file, matches the sensor model according to the ssid attribute in the Device tag, and matches the model data points under the sensor model according to the refname attribute in the four remote tags.

[0081] Step 11: The IEC104 client automatically imports the IEC104 protocol sensor device configuration.

[0082] The IEC104 client automatically generates the configuration of sensors and sensor data points based on the matched sensor models and model data points, and at the same time sets the sensor data point link information to the IEC104 protocol address (IOA address) corresponding to the four remote tags.

[0083] At this point, the improved station-side device information file is generated through the IEC104 server-side configuration. After the IEC104 client establishes the server file, it actively calls the station-side device information file, which can automatically generate the connected sensor configuration, reducing manual entry operations, saving time and effort and avoiding misoperation.

[0084] like Figure 2 As shown in the figure, the operations of the IEC104 server include: (1) defining the sensor model: creating a model table and a model data point table in the database of the gateway device, and filling in the relevant information according to the above convention; (2) configuring the communication node: setting the ID, name, communication address, communication method and communication protocol of the communication node, and writing them into the database; (3) configuring the sensor and data point: configuring the temperature and humidity sensor and the water pump sensor and their data points according to the sensor model, and writing the relevant information into the database; (4) improving the device information file: generating the station-side device information file according to the above convention and the improved XML format, as shown in the previous example; (5) storing the file and waiting for the call: storing the generated station-side device information file in the file access path of the IEC104 service, starting the IEC104 server, and waiting for the call from the client.

[0085] like Figure 2 As shown in FIG, the operation of the IEC104 client includes: (1) configuring the communication node: configuring the node information for communication with the server on the IEC104 client, including IP address, port number and communication protocol, etc.; (2) calling the file directory: sending a file directory calling request to the IEC104 server; (3) obtaining the file directory list: the server returns the file directory list, and the client obtains the name of the station device information file from it; (4) calling the station device information file: according to the file name, sending a call request for the station device information file to the server; (5) receiving and parsing the file: the server transmits the file, and the client parses the file after receiving it; by parsing the ssid attributes "TTAH" and "TPMP" of the device tag in the XML file, in the model The corresponding temperature and humidity controller model and water pump controller model are matched in the table; by parsing the refname attributes "Tmp", "Hum", "State" and "Control" in the four remote tags, the corresponding model data points are matched in the model data point table of the corresponding model; (6) Generate sensor configuration: According to the matched model and model data point, the configuration of the sensor and sensor data point is automatically generated on the client, and the link information of the sensor data point is set to the IOA address corresponding to the four remote tags in XML, such as the temperature data point link information of the temperature and humidity sensor is "16385", the humidity data point link information is "16386", the water pump status data point link information of the water pump sensor is "1", and the water pump switch data point link information is "24577".

[0086] Through the above implementation process, the automatic import of IEC104 protocol sensor configuration is realized, eliminating the need for manual tedious matching and entry operations, thereby improving work efficiency and configuration accuracy.

[0087] The above shows and describes the basic principles, main features and advantages of the present invention. Those skilled in the art should understand that the above embodiments do not limit the present invention in any form, and any technical solutions obtained by equivalent replacement or equivalent transformation fall within the scope of protection of the present invention.

Claims

1. A method for importing IEC104 protocol sensor device configuration for a gateway device, characterized by: First, define the sensor model for each type of sensor in the database of the gateway device, manage the sensor model through the model table and model data point table, define the model unique identification code in the model table, and define the data point four remote types and model data point aliases in the model data point table; then, configure each sensor and sensor data point in the gateway based on the sensor model and model data point; then, the IEC104 server provides the sensor with Q / GDW compliant 11509-2015 standard XML file format is modified, and the ssid attribute for identifying the unique identification code of the model is added to the device tag of the device information file, and the refname attribute for identifying the alias of the model data point is added to the four remote tags of the device information file to form a station-side device information file; then, the station-side device information file is stored in the file access path of the IEC104 service, and the gateway device is used as the carrier of the IEC104 server, waiting for the call of the IEC104 client; finally, the IEC104 client parses the called station-side device information file, matches the sensor model according to the ssid attribute, matches the model data point under the sensor model according to the refname attribute, and automatically generates the configuration of the sensor and sensor data point on the IEC104 client based on the matched sensor model and model data point, and sets the sensor data point link information to the IEC104 protocol address corresponding to the four remote tags to complete the import of the IEC104 protocol sensor device configuration.

2. The method for importing IEC104 protocol sensor device configuration for a gateway device according to claim 1, characterized in that: The method comprises the following steps: Step 1: Define a sensor model for each type of sensor in the database of the gateway device, and manage the sensor model through the model table and model data point table; Step 2: Configure the communication node in the gateway device and write the configuration information of the communication node into the database configuration table; Step 3. Configure sensors and sensor data points in the gateway device, and write the configuration information of the sensors and sensor data points into the database configuration table; Step 4. Modify the device information file provided by the sensor in the XML file format that complies with the Q / GDW 11509-2015 standard on the IEC104 server to form a station-side device information file, which is used to express the data capabilities of the IEC104 service. The specific modifications are: add the ssid attribute to the device tag of the device information file to identify the model unique identification code, and add the refname attribute to the four remote tags of the device information file to identify the model data point alias. Step 5. Store the station device information file in the file access path of the IEC104 service; use the gateway device as the carrier of the IEC104 server and wait for the call of the IEC104 client; Step 6. First, configure the IEC104 client to call the communication node of the IEC104 server, and then call the IEC104 server configuration file directory corresponding to the communication node; Step 7: After receiving the request for the IEC104 server configuration file directory, the IEC104 server returns the IEC104 server configuration file directory list containing the station device information file name to the IEC104 client; Step 8. The IEC104 client calls the station-end device information file according to the station-end device information file name; Step 9: After receiving the call request for the station-side device information file, the IEC104 server starts to transmit the station-side device information file to the IEC104 client. Step 10: The IEC104 client parses the received station device information file, matches the sensor model according to the ssid attribute, and matches the model data point under the sensor model according to the refname attribute; Step 11. Based on the matched sensor model and model data point, the configuration of the sensor and sensor data point is automatically generated on the IEC104 client. At the same time, the link information of the sensor data point is set to the IEC104 protocol address corresponding to the four remote tags.

3. The method for importing IEC104 protocol sensor device configuration for a gateway device according to claim 1 or 2, characterized in that: In Step 1, the model ID, model name and model unique identification code are defined in the model table, and the model data point ID, model data point name, model ID, data point four remote types, data point link information and model data point alias are defined in the model data point table. The model unique identification code and model data point alias are used to indicate a specific model data point of a specific type of sensor model.

4. The method for importing IEC104 protocol sensor device configuration for a gateway device according to claim 2, characterized in that: In Step 2, the configuration information of the communication node includes the communication node ID, the communication node name, the communication address, the communication mode and the communication protocol.

5. The method for importing IEC104 protocol sensor device configuration for a gateway device according to claim 1 or 2, characterized in that: In Step 3, the sensor and sensor data point are configured based on the sensor model and model data point; the configuration information of the sensor includes the sensor ID, sensor name, communication node ID, model ID and sensor communication parameters, and the configuration information of the sensor data point includes the sensor data point ID, sensor data point name, sensor ID, model data point ID and sensor data point link information.

6. A system for importing IEC104 protocol sensor device configurations for gateway devices, characterized by: It includes sensor model library, communication node configuration module, gateway sensor configuration module, station device information file module, station device information file summoning and parsing module and uplink platform sensor configuration module; The sensor model library is used to store each type of sensor model and the model data points contained therein, and manage the sensor models through the model table and the model data point table. The model unique identification code is defined in the model table, and the data point four remote types and model data point aliases are defined in the model data point table. The communication node configuration module is used to configure the communication nodes for communication connections between the gateway device and the sensor and the uplink platform; The gateway terminal sensor configuration module configures each sensor and the included sensor data points in the gateway terminal based on the sensor model and the model data points; The station-end device information file module modifies the device information file in the XML file format provided by the sensor in accordance with the Q / GDW 11509-2015 standard, adds the ssid attribute for identifying the model unique identification code in the device tag of the device information file, adds the refname attribute for identifying the model data point alias in the four remote tags of the device information file, forms the station-end device information file, and stores the station-end device information file in the file access path of the IEC104 service; The station-end device information file summoning and parsing module summons the IEC104 server-end configuration file directory and the station-end device information file, parses the station-end device information file, matches the sensor model according to the ssid attribute, and matches the model data point under the sensor model according to the refname attribute; The sensor configuration module on the uplink platform side automatically generates the configuration of sensors and sensor data points on the IEC104 client according to the matched sensor models and model data points, and sets the sensor data point link information to the IEC104 protocol addresses corresponding to the four remote tags.

7. The system for importing IEC104 protocol sensor device configurations for gateway devices according to claim 6, characterized in that: In the sensor model library, the model ID, model name and model unique identification code are defined in the model table, and the model data point ID, model data point name, model ID, data point four remote types, data point link information and model data point alias are defined in the model data point table. The model unique identification code and model data point alias are used to indicate a specific model data point of a specific type of sensor model.

8. The system for importing IEC104 protocol sensor device configurations for gateway devices according to claim 6, characterized in that: In the communication node configuration module, the configuration information of the communication node is written into the database configuration table; the configuration information of the communication node includes the communication node ID, the communication node name, the communication address, the communication mode and the communication protocol.

9. The system for importing IEC104 protocol sensor device configurations for gateway devices according to claim 6, characterized in that: In the gateway-side sensor configuration module, the sensor configuration information includes sensor ID, sensor name, communication node ID, model ID and sensor communication parameters, and the sensor data point configuration information includes sensor data point ID, sensor data point name, sensor ID, model data point ID and sensor data point link information.

10. The system for importing IEC104 protocol sensor device configurations for gateway devices according to claim 6, characterized in that: The gateway device is used as the carrier of the IEC104 server, and the uplink platform is used as the carrier of the IEC104 client.

Images