Method and system for gateway device iec104 protocol sensor device configuration import

Abstract

The application discloses a kind of for gateway machine equipment IEC104 protocol sensor equipment configuration import method and system, the method is first in gateway machine database by model table and model data point table definition sensor model, configuration communication node, sensor and data point;Again, the XML equipment information file that improves in line with Q / GDW 11509-2015 standard, in device label adds model unique identification code ssid attribute, four remote label adds model data point alias refname attribute, generates station end equipment information file and stores;Finally, IEC104 client parses file, matches model and data point, automatically generates configuration and sets link information.The system includes sensor model library, communication node configuration module and the like.The application solves the problem that manual configuration is complicated and error-prone, realizes sensor configuration automatic import, improves efficiency and accuracy, compatible with existing standard, applicable to power system automation scene.

Description

Technical Field

[0001] This invention relates to a method and system for importing IEC104 protocol sensor device configurations into gateway equipment, belonging to the field of substation technology. Background Technology

[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 function, it enables the monitoring and control of power equipment (such as substation auxiliary equipment, generators, etc.). It is widely used in industries such as power and urban rail transit, especially in communication between substations and master stations. It uses the TCP / IP protocol to ensure reliable data transmission in order to maintain the stable operation of the power system.

[0003] In the IEC 104 protocol transmission, each data point of a sensor is assigned an Information Object Address (IOA), and data of the four remote sensing types (remote signaling, telemetry, 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. Without specified configuration, although the data type and value of each IOA can be known through the data recall, it is unclear which sensor's data information these IOAs correspond to. Since the IEC 104 server typically supports multiple sensors, the client needs to bind IOA addresses to all data points of all sensors one by one, a tedious and error-prone task.

[0004] The Q / GDW 11509—2015 standard, "Technical Specifications and Interface Specifications for Substation Auxiliary Monitoring Systems," specifies the design requirements and interface specifications for substation auxiliary monitoring systems. Part A.3 details the transmission format, process, and protocol specifications for equipment information files. This document defines the IOA addresses and remote sensing types (I / O, remote control, remote monitoring, remote control) of all auxiliary devices and data points connected to the IEC104 server. However, some sensor devices with the same I / O type may involve multiple data points. It is difficult to determine the specific data point corresponding to the IOA address using this document definition, necessitating manual matching. Summary of the Invention

[0005] Purpose of the invention: In order to overcome the shortcomings of the existing technology, the present invention provides a method and system for importing IEC104 protocol sensor device configuration for gateway equipment. Based on compatibility with the Q / GDW 11509—2015 standard, the original XML file is improved to solve the problem of cumbersome point-to-point configuration on site and avoid errors in on-site operation.

[0006] Technical solution: To achieve the above objectives, the technical solution adopted by this invention is as follows:

[0007] A method for configuring and importing sensor devices according to the IEC104 protocol in a gateway device involves first defining sensor models for each type of sensor in the gateway device's database. Sensor models are managed through a model table and a model data point table. The model table defines a unique identifier for each model, and the model data point table defines the data point's remote sensing type and alias. The unique identifier and alias indicate a specific model data point for a specific sensor model. Then, based on the sensor models and data points, each sensor and its data point are configured in the gateway device. Finally, the IEC104 server provides Q / GDW compliance data for the sensors. The device information file, in the XML file format of the IEC 11509—2015 standard, is modified by adding an `ssid` attribute to the `device` tag to identify the unique identifier of the model, and a `refname` attribute to the `remote four-remote` tag to identify the alias of the model data points, thus forming the station-side device information file. Next, the station-side device information file is stored on the file access path of the IEC 104 service, with the gateway device acting as the carrier of the IEC 104 server, awaiting access from the IEC 104 client. Finally, the IEC 104 client parses the accessed station-side device information file, matching the sensor model based on the `ssid` attribute and the model data points under the sensor model based on the `refname` attribute. Based on the matched sensor model and model data points, the IEC 104 client automatically generates the configuration of the sensor and sensor data points, setting the sensor data point link information to the IEC 104 protocol address corresponding to the `remote four-remote` tag, completing the IEC 104 protocol sensor device configuration import. This method includes the following steps:

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

[0009] Step 2: Configure the communication nodes in the gateway device and write the configuration information of the communication nodes into the database configuration table; Step 3: Configure the 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.

[0010] Step 4: Modify the device information file provided by the sensor in the XML file format conforming to the Q / GDW 11509—2015 standard on the IEC104 server to form the station-side device information file, which is used to describe the data capabilities of the IEC104 service; the specific modifications are as follows: add the ssid attribute to the device tag of the device information file to identify the unique identifier of the model, and add the refname attribute to the four remote control tags of the device information file to identify the alias of the model data points;

[0011] Step 5: Store the station-side device information file on the file access path of the IEC104 service; use the gateway device as the carrier of the IEC104 service and wait for the IEC104 client to call;

[0012] Step 6: First, configure the communication node for summoning the IEC104 server in the IEC104 client, and then summon the IEC104 server configuration file directory of the corresponding communication node.

[0013] Step 7: After receiving the request for the IEC104 server configuration file directory, the IEC104 server returns a list of IEC104 server configuration file directories containing the names of the station equipment information files to the IEC104 client.

[0014] Step 8: The IEC104 client retrieves the station-side equipment information file based on the station-side equipment information file name;

[0015] Step 9: After receiving the request for the station equipment information file, the IEC104 server begins to transmit the station equipment information file to the IEC104 client.

[0016] Step 10: The IEC104 client parses the received station equipment information file, matches the sensor model based on the ssid attribute, and matches the model data points under the sensor model based on the refname attribute.

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

[0018] Specifically, in Step 1, the model ID, model name, and model unique identifier are defined in the model table, and the model data point ID, model data point name, model ID, data point remote sensing type, data point link information, and model data point alias are defined in the model data point table. The model unique identifier and model data point alias 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 the communication node ID, communication node name, communication address, communication method, and 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 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.

[0021] A system for importing IEC104 protocol sensor device configuration for gateway devices includes 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 retrieval 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 it contains. The sensor models are managed through the model table and the model data point table. The model table defines a unique identifier code for the model, and the model data point table defines the data point remote sensing type and the model data point alias.

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

[0024] The gateway-side sensor configuration module configures each sensor and its included sensor data points in the gateway device based on the sensor model and model data points.

[0025] The station-end equipment information file module modifies the equipment information file provided by the sensor in XML file format conforming to the Q / GDW 11509—2015 standard. It adds an ssid attribute to the device tag of the equipment information file to identify the unique identifier of the model, and adds a refname attribute to the four remote control tags of the equipment information file to identify the alias of the model data points, thus forming the station-end equipment information file, and stores the station-end equipment information file on the file access path of the IEC104 service.

[0026] The station-end equipment information file retrieval and parsing module retrieves the IEC104 server configuration file directory and the station-end equipment information file, parses the station-end equipment information file, matches the sensor model based on the ssid attribute, and matches the model data points under the sensor model based on the refname attribute.

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

[0028] Specifically, in the sensor model library, the model table defines model ID, model name and model unique identifier, and the model data point table defines model data point ID, model data point name, model ID, data point remote sensing type, data point link information and model data point alias. The model unique identifier and model data point alias 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, communication node name, communication address, communication method and 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. 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 for gateway devices provided by this invention, by defining sensor models in the gateway device, improving the device information file format, and designing an automated configuration import process, achieves automatic import of IEC104 protocol sensor configurations. Compared with the prior art, this 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 errors that may be caused by manual operation, improving the accuracy and reliability of configuration; 3. It realizes the automated generation of sensor configurations, improving work efficiency and facilitating rapid system deployment and maintenance; 4. It is compatible with the Q / GDW 11509—2015 standard, facilitating integration and interfacing with existing systems. Attached Figure Description

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

[0034] Figure 2 This is a schematic diagram illustrating the implementation process of the method of the present invention. Detailed Implementation

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

[0036] like Figure 1The diagram illustrates a system for importing IEC104 protocol sensor device configurations into a gateway device. The system includes 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 retrieval and parsing module, and an uplink platform-side sensor configuration module. In this case, the gateway device acts as the carrier of the IEC104 server, and the uplink platform acts as the carrier of the IEC104 client. The IEC104 server performs operations such as defining sensor models, configuring communication nodes, configuring sensors and sensor data points, improving device information files, storing files, and waiting for retrieval. The IEC104 client performs operations such as configuring communication nodes, retrieving file directories, obtaining file directory lists, retrieving station-side device information files, receiving and parsing files, and generating sensor configurations. The following section describes a specific embodiment... Figure 2 The present invention will be further described below.

[0037] Step 1: Sensor Model and Datasheet Design

[0038] In the database of the gateway device, a sensor model is defined for each type of sensor, and the sensor model is managed through the model table and the model data point table. As shown in Table 1, the model table defines the model ID, model name, and model unique identifier (to distinguish different sensor models). As shown in Table 2, the model data point table defines the model data point ID, model data point name, model ID, data point remote sensing type, data point link information, and model data point alias. The model unique identifier and model data point alias indicate a specific model data point of a specific type of sensor model.

[0039] Table 1. Examples of Model Representations (including but not limited to)

[0040] id Number Model ID, not null, * name String Model Name ssid String Model unique identifier

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

[0042]

[0043]

[0044] Step 2: Communication Node Configuration

[0045] Configure communication nodes in the gateway device to establish communication connections between the gateway device and the sensor and uplink platform. Write the configuration information of the communication nodes into the database configuration table. As shown in Table 3, the configuration information of the communication nodes includes the communication node ID, communication node name, communication address, communication method and communication protocol.

[0046] Table 3. Example of communication node configuration information (including but not limited to)

[0047] Id Number Communication node ID, not null, * name String Communication node name Commaddr String Communication address Commmode Number Communication methods Protocol type 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 its 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 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 sensor data point ID, sensor data point name, sensor ID, model data point ID, and sensor data point link information.

[0050] Table 4. Examples of sensor configuration information (including but not limited to)

[0051] Id Number Sensor ID, not null, * name String Sensor Name commnodeid Number Communication Node ID modelid Number Model ID commaddr String Sensor communication parameters

[0052] Table 5. Example of sensor data point configuration information (including but not limited to)

[0053]

[0054] Step 4: Modify the device information file

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

[0056] Table 6 Example of Equipment Information File

[0057]

[0058] The contents of the XML file format fragments in Tables 7 and 6

[0059]

[0060]

[0061] As shown in the examples in Tables 6 and 7, after the main station obtains the device information file, it can know what devices are connected, but it cannot know which IOA address a specific data point uses. It cannot automatically match the sensor model and model data points in the gateway device, and manual matching is required.

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

[0063] Table 8. Examples of Conventions for IEC104 Server and IEC104 Client

[0064]

[0065] Based on the design concept of this case, it is necessary to modify the XML file format device information file on the IEC104 server side to form a station-side device information file, which is used to describe the data capabilities of the IEC104 service. Specifically, the modifications are as follows: retain the tags in the original XML file, define attributes for some tags, add the ssid attribute to the device tag in the device information file to identify the unique identifier of the model, and add the refname attribute to the four remote access tags (such as yx_addr, yc_addr, yk_addr, yt_addr) in the device information file to identify the alias of the model data points. The station-side device information file formed after modifying the XML file in Table 6 is shown in Table 9.

[0066] Table 9 Example of Station Equipment Information File

[0067]

[0068] The modified station-side equipment information file enables the mapping of sensor models between the IEC104 server and the IEC104 client.

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

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

[0071] Step 6: The IEC104 client summons the IEC104 server configuration file directory.

[0072] First, configure the communication node for summoning the IEC104 server on the IEC104 client, including IP address, port number, communication protocol (IEC104), etc., and then summon the IEC104 server configuration file directory of the corresponding communication node.

[0073] Step 7: The IEC104 server returns a list of IEC104 server configuration file directories.

[0074] After receiving a request to access the IEC104 server configuration file directory, the IEC104 server returns a list of IEC104 server configuration file directories containing the names of station-side device information files to the IEC104 client.

[0075] Step 8: IEC104 Client Call Station Equipment Information File

[0076] The IEC104 client retrieves the station-side device information file (with the agreed-upon file name) based on the station-side device information file name.

[0077] Step 9: Transmit IEC104 server-side equipment information files to the station-side device.

[0078] After receiving the request to retrieve the station equipment information file, the IEC104 server begins transmitting the station equipment information file to the IEC104 client.

[0079] Step 10: IEC104 Client parses station-side device information file

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

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

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

[0083] Thus, the improved station-side equipment information file is generated through the IEC104 server configuration. After the IEC104 client establishes the server file, it actively summons the station-side equipment information file, which can automatically generate the configuration of the connected sensors, reducing manual data entry operations, saving time and effort and avoiding errors.

[0084] like Figure 2 As shown, the operations of the IEC104 server include: (1) Defining the sensor model: Create a model table and a model data point table in the database of the gateway device, and fill in the relevant information according to the above conventions; (2) Configuring the communication node: Set the ID, name, communication address, communication method and communication protocol of the communication node, and write it into the database; (3) Configuring the sensor and data point: Configure the temperature and humidity sensor and the water pump sensor and their data points according to the sensor model, and write the relevant information into the database; (4) Improving the equipment information file: Generate the station equipment information file according to the above conventions and the improved XML format, as shown in the previous example; (5) Storing the file and waiting for the client to call: Store the generated station equipment information file on the file access path of the IEC104 service, start the IEC104 server, and wait for the client to call.

[0085] like Figure 2 As shown, the operations of the IEC104 client include: (1) Configuring communication nodes: Configuring node information for communication with the server on the IEC104 client, including IP address, port number and communication protocol, etc.; (2) Summoning file directory: Sending a file directory summoning request to the IEC104 server; (3) Obtaining file directory list: The server returns a file directory list, from which the client obtains the name of the station-end device information file; (4) Summoning station-end device information file: Sending a summoning request for the station-end device information file to the server according to the file name; (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 table matches the corresponding temperature and humidity controller model and water pump controller model; by parsing the refname attributes "Tmp", "Hum", "State" and "Control" in the four remote labels, the corresponding model data points are matched in the model data point table of the corresponding model; (6) Generate sensor configuration: Based on the matched model and model data points, the configuration of the sensor and sensor data points is automatically generated on the client, and the link information of the sensor data points is set to the IOA address corresponding to the four remote labels in the XML. For example, the link information of the temperature data point of the temperature and humidity sensor is "16385", the link information of the humidity data point is "16386", the link information of the water pump status data point of the water pump sensor is "1", and the link information of the water pump switch data point is "24577".

[0086] Through the above implementation process, the automatic import of IEC104 protocol sensor configurations was achieved, eliminating the need for tedious manual matching and data entry operations, thus improving work efficiency and configuration accuracy.

[0087] The foregoing has shown and described 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 way, and all technical solutions obtained by equivalent substitution or equivalent transformation fall within the protection scope of the present invention.

Claims

1. A method for importing IEC104 protocol sensor device configuration for gateway devices, characterized in that: First, a sensor model is defined for each type of sensor in the gateway device's database. Sensor models are managed through a model table and a model data point table. A unique identifier is defined in the model table, and the data point type and alias are defined in the model data point table. Then, each sensor and its data point are configured in the gateway device based on the sensor model and data points. Next, the device information file provided by the sensor in the IEC104 server, conforming to the Q / GDW 11509—2015 standard XML file format, is modified. The system adds an SSID attribute to the tag to identify the unique identifier of the model, and adds a RefName attribute to the remote control tag in the device information file to identify the alias of the model data points, thus forming the station-end device information file. Next, the station-end device information file is stored on the file access path of the IEC104 service, with the gateway device acting as the carrier of the IEC104 server, awaiting the call from the IEC104 client. Finally, the IEC104 client parses the called station-end device information file, matches the sensor model based on the SSID attribute, matches the model data points under the sensor model based on the RefName attribute, and automatically generates the configuration of the sensor and sensor data points in the IEC104 client based on the matched sensor model and model data points. The sensor data point link information is set to the IEC104 protocol address corresponding to the remote control tag, completing the IEC104 protocol sensor device configuration import.

2. The method for importing IEC104 protocol sensor device configuration for gateway equipment according to claim 1, characterized in that: The method includes the following steps: Step 1: Define sensor models for each type of sensor in the database of the gateway device, and manage the sensor models through the model table and the 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 the 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 conforming to the Q / GDW 11509—2015 standard on the IEC104 server side to form the station-side device information file, which is used to describe the data capabilities of the IEC104 service; specifically, add the ssid attribute to the device tag of the device information file to identify the unique identifier of the model, and add the refname attribute to the four remote control tags of the device information file to identify the alias of the model data points; Step 5: Store the station-side device information file on the file access path of the IEC104 service; use the gateway device as the carrier of the IEC104 service and wait for the IEC104 client to call; Step 6: First, configure the communication node in the IEC104 client to call the IEC104 server, and then call the IEC104 server configuration file directory of the corresponding communication node. Step 7: After receiving the request for the IEC104 server configuration file directory, the IEC104 server returns a list of IEC104 server configuration file directories containing the names of the station equipment information files to the IEC104 client. Step 8: The IEC104 client retrieves the station-side equipment information file based on the station-side equipment information file name; Step 9: After receiving the request to retrieve the station equipment information file, the IEC104 server begins transmitting the station equipment information file to the IEC104 client. Step 10: The IEC104 client parses the received station equipment information file, matches the sensor model based on the ssid attribute, and matches the model data points under the sensor model based on the refname attribute. Step 11: Based on the matched sensor model and model data points, automatically generate the configuration of the sensor and sensor data points in the IEC104 client. At the same time, set the sensor data point link information to the IEC104 protocol address corresponding to the four remote label.

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

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

5. The method for importing IEC104 protocol sensor device configuration for gateway equipment according to claim 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 sensor ID, sensor name, communication node ID, model ID and sensor communication parameters. The configuration information of the sensor data point includes 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 configuration into a gateway device, characterized in that: It includes 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 retrieval and parsing module, and an uplink platform-side sensor configuration module; The sensor model library is used to store each type of sensor model and the model data points it contains. The sensor models are managed through the model table and the model data point table. The model table defines a unique identifier code for the model, and the model data point table defines the data point remote sensing type and the model data point alias. The communication node configuration module is used to configure the communication nodes for communication connections between the gateway device and the sensor and uplink platform. The gateway-side sensor configuration module configures each sensor and its included sensor data points in the gateway device based on the sensor model and model data points. The station-end equipment information file module modifies the equipment information file provided by the sensor in XML file format conforming to the Q / GDW 11509—2015 standard. It adds an ssid attribute to the device tag of the equipment information file to identify the unique identifier of the model, and adds a refname attribute to the four remote control tags of the equipment information file to identify the alias of the model data points, thus forming the station-end equipment information file, and stores the station-end equipment information file on the file access path of the IEC104 service. The station-end equipment information file retrieval and parsing module retrieves the IEC104 server configuration file directory and the station-end equipment information file, parses the station-end equipment information file, matches the sensor model based on the ssid attribute, and matches the model data points under the sensor model based on the refname attribute. The uplink platform sensor configuration module automatically generates the configuration of the sensor and sensor data points on the IEC104 client based on the matched sensor model and model data points, and sets the sensor data point link information to the IEC104 protocol address 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 table defines the model ID, model name, and model unique identifier, and the model data point table defines the model data point ID, model data point name, model ID, data point remote sensing type, data point link information, and model data point alias. The model unique identifier and model data point alias 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, communication node name, communication address, communication method and 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. 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 configuration for gateway equipment according to claim 6, characterized in that: The gateway device serves as the carrier of the IEC104 server, and the uplink platform serves as the carrier of the IEC104 client.

Images