WO2021031518A1 - 一种数据兼容性网关系统 - Google Patents

一种数据兼容性网关系统 Download PDF

Info

Publication number
WO2021031518A1
WO2021031518A1 PCT/CN2020/070991 CN2020070991W WO2021031518A1 WO 2021031518 A1 WO2021031518 A1 WO 2021031518A1 CN 2020070991 W CN2020070991 W CN 2020070991W WO 2021031518 A1 WO2021031518 A1 WO 2021031518A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
opc
communication
gateway
industrial
Prior art date
Application number
PCT/CN2020/070991
Other languages
English (en)
French (fr)
Inventor
孙茂杰
李福存
张楠
谷庆
邵淑炜
黄昭
Original Assignee
江苏金恒信息科技股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 江苏金恒信息科技股份有限公司 filed Critical 江苏金恒信息科技股份有限公司
Priority to GB2006718.7A priority Critical patent/GB2580848B/en
Publication of WO2021031518A1 publication Critical patent/WO2021031518A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/24—Negotiation of communication capabilities

Definitions

  • This application relates to the field of industrial information and communication technology, and in particular to a data compatibility gateway system.
  • Gateway also known as network connector and protocol converter, is a device that realizes network interconnection above the network layer.
  • OPC DA OPC DA
  • COM/DCOM components Component Object
  • Model/Distributed Component Object Model component object model/distributed component object model
  • COM/DCOM components are only limited to Windows systems. Therefore, industrial communication gateways developed based on the Linux kernel cannot be compatible with devices that only support OPC DA communication standards.
  • a protocol conversion component needs to be added to the device, that is, the data in the OPC DA communication standard device is re-parsed through the protocol conversion component, and then sent to the industrial communication gateway device through a network connection.
  • This method requires the adaptation of protocol conversion components for each device, that is, the arrangement of interface docking and analysis methods for the data communication of the device.
  • This application provides a data compatibility gateway system to solve the problem that industrial communication gateways developed based on the Linux kernel are compatible with only OPC DA communication standard equipment.
  • This application provides a data compatibility gateway system, which includes an industrial communication gateway based on the Linux kernel, and a compatible module integrated in the industrial communication gateway; the compatible module is based on the Windows kernel and can parse the data of the OPC DA communication standard and Run Windows-based applications independently;
  • the industrial communication gateway is configured to receive communication data, and according to the communication standard of the communication data, send OPC DA communication standard data to the compatibility module;
  • the compatibility module is configured to receive data of the OPC DA communication standard, and parse and send the data of the OPC DA communication standard to the industrial communication gateway.
  • the industrial communication gateway and the compatible module are connected via Ethernet, and the compatible module includes a processor, a memory, and an Ethernet interface independent of the industrial communication gateway;
  • the data of the OPC DA communication standard received through the Ethernet interface is parsed by the processor in the memory; and the parsed data is sent to the industrial communication gateway through the Ethernet interface.
  • the data compatibility gateway system further includes multiple OPC servers and clients connected to the industrial communication gateway;
  • OPC servers are placed in multiple industrial sites to collect or generate data; multiple clients have built-in industrial applications; the client uses the industrial communication gateway to obtain the data collected or generated by the OPC server, and through the built-in The application processes the acquired data.
  • the industrial communication gateway is further configured to: obtain a communication standard type supported by any of the OPC server and any of the clients; and,
  • the compatible module is further configured to: initiate a connection to the industrial communication gateway; and parse the data packet sent by the industrial communication gateway, and start a service that meets the type of communication standard supported by the client, so as to convert the parsed data Provided to the client through the opened service;
  • the industrial communication gateway is configured to establish a connection with the compatible module; and, perform source address conversion on the data packet sent by the OPC server, and send the converted data packet to the compatible module.
  • the industrial communication gateway has a built-in Netfilter module; the data packet obtained through the OPC server is first sent to the Linux kernel of the industrial communication gateway, and then the source address of the data packet is converted by the Netfilter module.
  • the industrial communication gateway is further configured to perform port mapping after the compatibility module opens a service that meets the communication standard type supported by the client, so that the received data packet is forwarded to the Compatible modules.
  • the industrial communication gateway is further configured to determine whether the type of communication standard supported by the OPC server and the client is a non-OPC DA communication standard; if both are non-OPC DA communication standards, the communication standard through the industrial communication gateway
  • the Linux kernel parses the data packet; and,
  • the industrial communication gateway is further configured to traverse all the gateway tasks of the current industrial communication gateway, whether there is a gateway task that applies the OPCDA communication standard; if not, control the compatible module to enter a sleep state.
  • this application provides a data compatibility gateway system, including an industrial communication gateway based on the Linux kernel and a compatible module integrated in the industrial communication gateway; wherein the industrial communication gateway is configured to receive communication data, and According to the communication standard of the communication data, the data of the OPC DA communication standard is sent to the compatible module.
  • the compatible module is based on the Windows kernel, can parse OPC DA communication standard data and run Windows-based applications independently, and is configured to receive OPC DA communication standard data, and analyze and send OPC DA communication standard data to the industrial communication gateway .
  • the built-in compatible module in the industrial communication gateway based on Linux kernel it can realize the two-way compatibility of OPC DA communication standard and non-OPC DA communication standard data, solve the industrial communication gateway based on Linux kernel development, and compatible only support OPC DA communication standard equipment The problem.
  • Figure 1 is a schematic structural diagram of a data compatibility gateway system according to this application.
  • Figure 2 is a schematic diagram of the data transfer process of the application data compatibility gateway
  • FIG. 3 is a schematic structural diagram of an industrial communication gateway of this application.
  • Figure 4 is a schematic diagram of the application process for judging the communication standard type
  • Figure 5 is a schematic diagram of the data conversion process of the application data compatibility gateway system.
  • Fig. 1 is a schematic structural diagram of a data compatibility gateway system of this application. It can be seen from Fig. 1 that the data compatibility gateway system provided by this application includes an industrial communication gateway based on the Linux kernel and a compatible module integrated in the industrial communication gateway; the compatible module is based on the Windows kernel and can analyze OPCDA communication Standard data and independent running of Windows-based applications;
  • the industrial communication gateway is configured to receive communication data, and according to the communication standard of the communication data, send OPC DA communication standard data to the compatible module; the compatible module is configured to receive The data of the OPC DA communication standard and the data of the OPC DA communication standard are analyzed and sent to the industrial communication gateway.
  • a compatible module supporting Windows is integrated in the industrial communication gateway based on the Linux kernel.
  • the industrial communication gateway based on the Linux kernel and the Windows module are connected via Ethernet.
  • the communication gateway will directly process all non-OPC DA communication standard data, and the data related to the OPC DA communication standard will be completed by the Windows module.
  • the industrial communication gateway and the compatible module are connected via Ethernet, and the compatible module includes a processor, a memory, and an Ethernet interface independent of the industrial communication gateway;
  • the data of the OPC DA communication standard received by the network interface is parsed by the processor in the memory; and the parsed data is sent to the industrial communication gateway through the Ethernet interface.
  • the compatible module has independent data processing capabilities to analyze and transform data, and can further install applications in the Windows environment in the compatible module to assist in data processing and increase the expansion of the compatible module Features.
  • the data compatibility gateway system also includes multiple OPC servers and clients connected to the industrial communication gateway; multiple OPC servers are located in multiple industrial sites to collect or generate data; multiple clients An industrial application is built in the terminal; the client obtains the data collected or generated by the OPC server through the industrial communication gateway, and processes the acquired data through the built-in application.
  • the OPC server can be production equipment, control equipment, or management equipment used in actual industrial production.
  • Various data generated in the actual production process can be aggregated and transformed through the OPC server to be sent to the industrial communication gateway.
  • the industrial communication gateway then forwards the data to the corresponding client for processing to complete the purpose of industrial control.
  • the control subject of the actual control process is also different, so it is used as OPC
  • the server device can also be used as a client device at the same time, that is, the client device can also be a production device, a control device, or a management device used in actual industrial production.
  • the client can also be other types of equipment, such as computers and mobile terminals.
  • the industrial communication gateway is further configured to: obtain the communication standard type supported by any one of the OPC server and any one of the client; and determine whether the communication standard type supported by the OPC server and the client is Consistent; if they are inconsistent, convert the data obtained from the OPC server into data of the communication standard supported by the client. That is, in practical applications, as shown in Figure 4, the entire industrial communication gateway can execute the following program steps:
  • S102 Determine whether the communication standard types supported by the OPC server and the client are consistent
  • the industrial communication gateway can obtain the communication standard types supported by the OPC server and client by analyzing the historical records of the data communication standard types that the OPC server and client have transmitted, or by registering information of the OPC server and the client. According to the obtained type, it can be judged whether the communication standard types supported by the OPC server and the client are consistent. Wherein, if the type of communication standards supported by the OPC server and the client are the same, for example, the OPC server only supports the OPC DA communication standard, and the client also only supports the OPC DA communication standard. Generally, no industrial communication gateway is required for data conversion.
  • OPC server For OPC server and client, the types of communication standards supported are inconsistent. For example, OPC server only supports OPC DA communication standard, client supports OPC UA communication standard; OPC server only supports OPC DA communication standard, client only supports such as Modbus protocol, etc. Non-OPC communication standard; OPC server supports OPC UA communication standard, client only supports OPC DA communication standard; OPC server supports OPC UA communication standard, client application only supports non-OPC communication standards such as Modbus protocol, etc., which can be passed through industrial communication gateway
  • the conversion of the data communication standard is performed, that is, the data obtained from the OPC server is converted into the data of the communication standard supported by the client.
  • the compatible module is further configured to: initiate a connection to the industrial communication gateway; and parse the data packet sent by the industrial communication gateway, and start a service that meets the type of communication standard supported by the client, In order to provide the parsed data to the client through the opened service; the industrial communication gateway is configured to establish a connection with the compatible module; and to perform source address conversion on the data packet sent by the OPC server, and The data packet after the source address conversion is sent to the compatible module.
  • the industrial communication gateway has a built-in Netfilter module; the data packet obtained through the OPC server is first sent to the Linux kernel of the industrial communication gateway, and then the source address of the data packet is converted by the Netfilter module. Further, the industrial communication gateway is further configured to perform port mapping after the compatibility module opens a service that complies with the communication standard type supported by the client, so that the received data packet is forwarded to the compatible Module, as shown in Figure 5.
  • the OPC server only supports the OPC DA communication standard, and the client supports the OPC UA communication standard, since the OPC DA communication standard is only applicable to the Windows platform, the data sent by the OPC server needs to be converted to satisfy the customer The communication standard requirements of the end.
  • the roles of the communication gateway are OPC DA client and OPC UA server.
  • the compatibility module based on the Windows kernel will actively initiate a connection to the OPC DA service (the Linux part of the communication gateway).
  • the data packet transmitted by the OPC server will first be sent to the Linux kernel of the industrial communication gateway, and the source address translation (SNAT translation) of the data packet will be performed through the built-in Netfilter module of the Linux system, and then sent to the OPCDA server.
  • SNAT translation source address translation
  • the OPC DA service After the OPC DA service receives the connection request, it will reply to the communication gateway.
  • the reply will be captured by the Linux kernel first.
  • the Netfilter module forwards the packet to the compatible module based on the previous SNAT conversion result. After several handshake negotiations, the compatible module of the communication gateway completes the connection with the OPCDA service.
  • the compatible module After the connection is completed, the compatible module will parse all the data and open a service that complies with the OPC UA communication standard at the same time, so that the data processed by the compatible module will be provided to the outside according to the OPC UA communication standard.
  • the compatible module After the compatible module completes the creation of the OPC UA service, the Linux part of the industrial communication gateway will complete port mapping, so that data packets received by a custom port of the industrial communication gateway are forwarded to the OPC UA service running on the compatible module. Port.
  • the client application only supports the OPC DA communication standard.
  • the role of the communication gateway is the client of OPC UA and the server of OPC DA.
  • the Linux module in the industrial communication gateway will actively initiate a connection to the OPC UA service. After several handshake negotiations, the Linux module of the communication gateway completes the connection with the OPC UA service.
  • the Linux module will parse all data and start a service that complies with the OPC UA communication standard. All data will be provided in the OPC UA communication standard.
  • the compatible module based on the Windows platform will start an OPC UA client to connect to the OPC UA service created by the Linux module.
  • the compatible module will parse all the data and open a service that complies with the OPC DA communication standard. All data will be provided in the OPC DA communication standard.
  • the Linux module After the compatible module completes the creation of the OPC DA service, the Linux module will complete the port mapping, so that the data packet received by the TCP/135 port of the communication gateway is forwarded to the TCP/135 port of the compatible module, and when connecting according to the subsequent client handshake, The negotiated communication port is mapped to the port to complete the communication.
  • the communication standard supported by the OPC server is different from the communication standard supported by the client.
  • the OPC UA communication standard is a platform-independent communication standard form, while the OPC DA communication standard is only applicable to the Windows platform. Therefore, the client cannot directly process the data transmitted by the OPC server.
  • the compatible module in the industrial communication gateway of the present application the data of the OPC DA communication standard can be converted to the OPC UA communication standard, so as to achieve the purpose of communication without changing the original communication form of the OPC server or client device. Therefore, the data compatible gateway provided by the present application can ensure the communication of industrial data during the transition period of industrial hardware equipment upgrade, be compatible with old equipment, and reduce equipment investment.
  • the communication standards shown in the foregoing embodiments all include OPC DA, a communication standard that only supports the Windows platform. Therefore, a compatible module is required to perform corresponding conversions for the transmitted data to complete the communication.
  • the data compatible gateway system provided by this application can also be adapted to communication situations of other types of communication standards. Therefore, in some embodiments of this application, the industrial communication gateway is also configured to: determine the OPC server Whether the communication standard type supported by the client is a non-OPC DA communication standard; if both are non-OPC DA communication standards, the data packet is parsed through the Linux kernel of the industrial communication gateway; and the service that meets the communication standard type supported by the client is opened , To send the parsed data packet to the client through the opened service.
  • the role of the communication gateway is the OPC DA client and OPC DA server.
  • the compatibility module based on the Windows platform will actively initiate a connection to the OPC DA service, and the data packet will be sent to the Linux kernel of the communication gateway.
  • the Netfilter module in the Linux system will perform SNAT conversion on the data packet and send it to the OPC DA service.
  • the OPC DA service will reply to the industrial communication gateway after receiving the connection request. The reply will be captured by the Linux kernel first, and the Netfilter module will forward the packet to the compatible module according to the previous SNAT translation. After several handshake negotiations, the compatible module of the communication gateway completes the connection with the OPC DA server.
  • the compatible module based on the Windows platform will parse all the data and start a service that complies with the OPC DA communication standard. All data will be provided in the OPC DA communication standard.
  • the Linux module will complete the port mapping, so that the data packet received by the TCP/135 port of the communication gateway is forwarded to the TCP/135 port of the Windows module, and negotiated according to the subsequent client handshake connection The communication port is port mapped to complete the communication.
  • the industrial communication gateway is also based on the Linux platform, and the industrial communication gateway as a gateway device requires preliminary data processing, therefore, in this embodiment, even the OPC server and the client support the OPCDA communication standard In a scenario, a compatible module is still needed to parse the data.
  • the industrial communication gateway is also configured to traverse all the gateway tasks of the current industrial communication gateway , Whether there is a gateway task that applies the OPC DA communication standard; if not, control the compatible module to enter the sleep state.
  • the OPC server supports the OPC UA communication standard
  • the client also supports the scenario of the OPC UA communication standard.
  • the roles of the communication gateway are the OPC UA client and the OPC UA server.
  • the Linux module in the industrial communication gateway will actively initiate a connection to the OPC UA service. After several handshake negotiations, the Linux module of the communication gateway completes the connection with the OPC UA service. After the connection is completed, the Linux module will parse all data and start a service that complies with the OPC UA communication standard. All data will be provided in the OPC UA communication standard. In this scenario, if there is no other project applied to OPC DA, the compatible module can be put to sleep.
  • the OPC server supports the OPC UA communication standard, and the client only supports scenarios that are not OPC communication standards such as the Modbus protocol.
  • the role of the communication gateway is OPC UA client and Modbus Slave.
  • the Linux module of the communication gateway will actively initiate a connection to the OPC UA service. After several handshake negotiations, the Linux module of the communication gateway completes the connection with the OPC UA service. After the connection is completed, the Linux module will parse the data, and then package the data with the Modbus protocol and provide it to the client application. In this scenario, if there is no other project applied to OPC DA, the Windows module can be hibernated.
  • this application provides a data compatibility gateway system, including an industrial communication gateway based on the Linux kernel and a compatible module integrated in the industrial communication gateway; wherein the industrial communication gateway is configured to receive communication data, and According to the communication standard of the communication data, the data of the OPC DA communication standard is sent to the compatible module.
  • the compatible module is based on the Windows kernel, can parse the data of the OPC DA communication standard and run Windows-based applications independently, and is configured to receive the data of the OPC DA communication standard, and parse and send the data of the OPC DA communication standard to the industrial communication gateway .
  • the built-in compatible module in the industrial communication gateway based on Linux kernel it can realize the two-way compatibility of OPC DA communication standard and non-OPC DA communication standard data, solve the industrial communication gateway based on Linux kernel development, and compatible only support OPC DA communication standard equipment The problem.

Abstract

本申请提供一种数据兼容性网关系统，包括基于Linux内核的工业通信网关和集成在工业通信网关中的兼容模块；其中，工业通信网关被配置为接收通信数据，以及根据通信数据的通信标准，将OPC DA通信标准的数据发送至兼容模块。兼容模块基于Windows内核，能够解析OPC DA通信标准的数据以及独立运行基于Windows的应用程序，并且被配置为接收OPC DA通信标准的数据，以及将OPC DA通信标准的数据解析并发送给工业通信网关。通过在基于Linux内核的工业通信网关中内置兼容模块，可以实现对OPC DA通信标准和非OPC DA通信标准的数据双向兼容，解决基于Linux内核开发的工业通信网关，兼容仅支持OPC DA通信标准设备的问题。

Description

一种数据兼容性网关系统
本申请要求在2019年8月19日提交中国专利局、申请号为201910761564.X、发明名称为“一种数据兼容性网关系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及工业信息通信技术领域，尤其涉及一种数据兼容性网关系统。
背景技术
网关又称网间连接器、协议转换器，是一种在网络层以上实现网络互连的设备。目前，大多数工业通信网关是基于Linux内核开发的，但由于OPC DA(OLE for Process Control Data Access，用于过程控制的对象连接与嵌入数据访问)通信标准对于COM/DCOM组件的依赖(Component Object Model/Distributed Component Object Model，部件对象模型/分布式部件对象模型)，而COM/DCOM组件又仅仅局限于Windows系统，因此基于Linux内核开发的工业通信网关无法兼容仅支持OPC DA通信标准的设备。
为了兼容仅支持OPC DA通信标准的设备，需要在设备中增加协议转换的组件，即通过协议转换组件将OPC DA通信标准设备中的数据进行重新解析，再通过网络连接发送给工业通信网关设备。这种方法需要针对每一个设备分别进行协议转换组件的适配，即针对设备的数据通信情况进行接口对接和解析方式的布置。
可见，为适应兼容性而进行的布置，其接口对接和解析配置都需要大量的硬件设备支持。而受限于协议转换组件的数据转换方式，数据解析和转换的效率很低。并且，在大型工业通信系统中，存在多种通信标准，使得传统兼容性方法很难应用到工业系统中，因此，如何使基于Linux内核开发的工业通信网关，兼容仅支持OPC DA通信标准的设备，成为本领域亟待解决的技术问题。
发明内容
本申请提供了一种数据兼容性网关系统，以解决基于Linux内核开发的工业通信网关，兼容仅支持OPC DA通信标准设备的问题。
本申请提供一种数据兼容性网关系统，包括基于Linux内核的工业通信网关，以及集成在所述工业通信网关中的兼容模块；所述兼容模块基于Windows内核，能够解析OPC DA通信标准的数据以及独立运行基于Windows的应用程序；
所述工业通信网关被配置为接收通信数据，以及根据所述通信数据的通信标准，将OPC DA通信标准的数据发送至所述兼容模块；
所述兼容模块被配置为接收OPC DA通信标准的数据，以及将OPC DA通信标准的数据解析并发送给所述工业通信网关。
可选的，所述工业通信网关与所述兼容模块通过以太网连接，所述兼容模块包括独立于所述工业通信网关的处理器、存储器和以太网接口；
通过所述以太网接口接收的OPC DA通信标准的数据，在所述存储器中被所述处理器解析；以及，解析后的数据通过以太网接口发送给所述工业通信网关。
可选的，所述数据兼容性网关系统还包括连接所述工业通信网关的多个OPC服务器和客户端；
多个OPC服务器分置于多个工业现场，以采集或生成数据；多个客户端中内置工业应用程序；所述客户端通过所述工业通信网关获取OPC服务器采集或生成的数据，并通过内置的应用程序处理获取的数据。
可选的，所述工业通信网关还被配置为：获取任一所述OPC服务器和任一所述客户端所支持的通信标准类型；以及，
判断所述OPC服务器和所述客户端所支持的通信标准类型是否一致；若不一致，将从OPC服务器获取的数据，转化为所述客户端所支持通信标准的数据。
可选的，兼容模块被进一步配置为：向工业通信网关发起连接；以及，解析工业通信网关发送的数据包，并开启符合所述客户端所支持通信标准类型的服务，以将解析后的数据通过开启的服务提供给所述客户端；
所述工业通信网关被配置为与所述兼容模块建立连接；以及，对所述OPC服务器发送的数据包进行源地址转换，并将源地址转换后的数据包发送给所述兼容模块。
可选的，所述工业通信网关内置Netfilter模块；通过所述OPC服务器获取的数据包，先发送至所述工业通信网关的Linux内核，再通过所述Netfilter模块将数据包进行源地址转换。
可选的，所述工业通信网关还被配置为：在所述兼容模块开启符合所述客户端所支持通信标准类型的服务后，进行端口映射，使接收的数据包通过端口映射转发至所述兼容模块。
可选的，所述工业通信网关还被配置为：判断所述OPC服务器和所述客户端所支持通信标准类型是否为非OPC DA通信标准；若均是非OPC DA通信标准，通过工业通信网关的Linux内核解析数据包；以及，
开启符合客户端所支持通信标准类型的服务，以通过开启的服务向客户端发送解析后的数据包。
可选的，所述工业通信网关还被配置为：遍历当前工业通信网关的全部网关任务中，是否存在应用OPC DA通信标准的网关任务；若不存在，控制兼容模块进入休眠状态。
由以上技术方案可知，本申请提供一种数据兼容性网关系统，包括基于Linux内核的工业通信网关，以及集成在工业通信网关中的兼容模块；其中，工业通信网关被配置为接收通信数据，以及根据通信数据的通信标准，将OPC DA通信标准的数据发送至兼容模块。兼容模块基于Windows内核，能够解析OPC DA通信标准的数据以及独立运行基于Windows的应用程序，并且被配置为接收OPC DA通信标准的数据，以及将OPC DA通信标准的数据解析并发送给工业通信网关。通过在基于Linux内核的工业通信网关中内置兼容模块，可以实现对OPC DA通信标准和非OPC DA通信标准的数据双向兼容，解决基于Linux内核开发的工业通信网关，兼容仅支持OPC DA通信标准设备的问题。
附图说明
图1为本申请一种数据兼容性网关系统的结构示意图；
图2为本申请数据兼容性网关的数据传递流程示意图；
图3为本申请一种工业通信网关的结构示意图；
图4为本申请判断通信标准类型的流程示意图；
图5为本申请数据兼容性网关系统数据转换流程示意图。
具体实施方式
下面将详细地对实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下实施例中描述的实施方式并不代表与本申请相一致的所有实施方式。仅是与权利要求书中所详述的、本申请的一些方面相一致的系统和方法的示例。
参见图1，为本申请一种数据兼容性网关系统的结构示意图。由图1可知，本申请提供的数据兼容性网关系统，包括基于Linux内核的工业通信网关，以及集成在所述工业通信网关中的兼容模块；所述兼容模块基于Windows内核，能够解析OPC DA通信标准的数据以及独立运行基于Windows的应用程序；
如图2所示，所述工业通信网关被配置为接收通信数据，以及根据所述通信数据的通信标准，将OPC DA通信标准的数据发送至所述兼容模块；所述兼容模块被配置为接收OPC DA通信标准的数据，以及将OPC DA通信标准的数据解析并发送给所述工业通信网关。
在本申请提供的技术方案中，在基于Linux内核的工业通信网关中，集成一个支持Windows的兼容模块。在所述数据兼容性网关系统的内部，基于Linux内核的工业通信网关与Windows模块通过以太网连接。通信网关将直接处理所有非OPC DA通信标准的数据，而涉及OPC DA通信标准的数据将由Windows模块来完成。
进一步地，如图3所示，所述工业通信网关与所述兼容模块通过以太网连接，所述兼容模块包括独立于所述工业通信网关的处理器、存储器和以太网接口；通过所述以太网接口接收的OPC DA通信标准的数据，在所述存储器中被所述处理器解析；以及，解析后的数据通过以太网接口发送给所述工业通信网关。即在实际应用中，兼容模块拥有独立的数据处理能力，以便对数据进行解析、转化处理，并且可以通过在兼容模块中进一步安装Windows环境下的应用程序，辅助进行数据处理，增加兼容模块的扩展功能。
实际工业生产中，所述数据兼容性网关系统还包括连接所述工业通信网关的多个OPC服务器和客户端；多个OPC服务器分置于多个工业现场，以采集或生成数据；多个客户端中内置工业应用程序；所述客户端通过所述工业通信网关获取OPC服务器采集或生成的数据，并通过内置的应用程序处理获取的数据。
OPC服务器可以是实际工业生产中应用的生产设备、控制设备或管理设备等，实际生产过程产生的各种数据可以通过OPC服务器进行统一汇总、转化，以发送到工业通信网关中。工业通信网关再将数据转发给相应的客户端进行处理，完成工业控制的目的，显然本申请提供的技术方案中，由于具体的工业控制方法不同，实际控制过程的控制主体也不同，因此作为OPC服务器的设备同时也可以作为客户端设备，即客户端设备也可以是实际工业生产中应用的生产设备、控制设备或管理设备等。此外，客户端作为工业过程的实际控制设备，还可以是其他类型设备，例如计算机、移动终端等。
所述工业通信网关还被配置为：获取任一所述OPC服务器和任一所述客户端所支持的通信标准类型；以及，判断所述OPC服务器和所述客户端所支持的通信标准类型是否一致； 若不一致，将从OPC服务器获取的数据，转化为所述客户端所支持通信标准的数据。即在实际应用中，如图4所示，整个工业通信网关可以执行以下程序步骤：
S101：获取OPC服务器和客户端所支持的通信标准类型；
S102：判断所述OPC服务器和所述客户端所支持的通信标准类型是否一致；
S103：如果所述OPC服务器和所述客户端所支持的通信标准类型不一致，将从OPC服务器获取的数据，转化为所述客户端所支持通信标准的数据。
实际应用中，工业通信网关可以通过分析OPC服务器和客户端曾经传输的数据通信标准类型的历史记录，或者通过OPC服务器和客户端的注册信息，来获取OPC服务器和客户端所支持的通信标准类型。根据获取的类型可以判断OPC服务器和客户端所支持的通信标准类型是否一致。其中，如果所述OPC服务器和所述客户端所支持的通信标准类型一致，例如：OPC服务器仅支持OPC DA通信标准，客户端也仅支持OPC DA通信标准，一般无需工业通信网关进行数据转化。
对于OPC服务器和客户端所支持的通信标准类型不一致，例如，OPC服务器仅支持OPC DA通信标准，客户端支持OPC UA通信标准；OPC服务器仅支持OPC DA通信标准，客户端仅支持如Modbus协议等非OPC通信标准；OPC服务器支持OPC UA通信标准，客户端仅支持OPC DA通信标准；OPC服务器支持OPC UA通信标准，客户端应用仅支持如Modbus协议等非OPC通信标准等，可以通过工业通信网关进行数据通信标准的转化，即，将从OPC服务器获取的数据，转化为所述客户端所支持通信标准的数据。
对于需要进行数据通信标准转化的情况，兼容模块被进一步配置为：向工业通信网关发起连接；以及，解析工业通信网关发送的数据包，并开启符合所述客户端所支持通信标准类型的服务，以将解析后的数据通过开启的服务提供给所述客户端；所述工业通信网关被配置为与所述兼容模块建立连接；以及，对所述OPC服务器发送的数据包进行源地址转换，并将源地址转换后的数据包发送给所述兼容模块。
其中，所述工业通信网关内置Netfilter模块；通过所述OPC服务器获取的数据包，先发送至所述工业通信网关的Linux内核，再通过所述Netfilter模块将数据包进行源地址转换。进一步地，所述工业通信网关还被配置为：在所述兼容模块开启符合所述客户端所支持通信标准类型的服务后，进行端口映射，使接收的数据包通过端口映射转发至所述兼容模块，如图5所示。
例如，在实际应用中，如果OPC服务器仅支持OPC DA通信标准，客户端支持OPC UA通信标准，由于OPC DA通信标准只适用于Windows平台，因此需要对OPC服务器发送的数据进行转换，才能满足客户端的通信标准要求。
在该情景下，通信网关的角色是OPC DA客户端与OPC UA服务器。实际传输过程中，首先，基于Windows内核的兼容模块会主动向OPC DA服务(通信网关的Linux部分)发起连接。OPC服务器传输来的数据包将先发送给工业通信网关的Linux内核，并通过Linux系统内置的Netfilter模块，将数据包进行源地址转换(SNAT转换)，再发送给OPC DA服务器。OPC DA服务在接收到连接请求后，将会回复通信网关，该回复将先由Linux内核捕获，Netfilter模块根据之前的SNAT转换结果，将该数据包转发给兼容模块。并经过几次握手协商后，通信网关的兼容模块与OPC DA服务完成连接。
完成连接后，兼容模块将会解析所有数据，同时开启一个符合OPC UA通信标准的服 务，使兼容模块处理的数据将会以OPC UA通信标准向外提供。在兼容模块完成OPC UA服务的创建后，工业通信网关中的Linux部分将会完成端口映射，使工业通信网关的某自定义端口接收的数据包，转发至兼容模块上运行的OPC UA服务所监听的端口。
又例如，实际应用中，如果OPC服务器支持OPC UA通信标准，客户端应用仅支持OPC DA通信标准。在该情景下，通信网关的角色是OPC UA的客户端与OPC DA的服务器。首先，工业通信网关中的Linux模块会主动向OPC UA服务发起连接，经过几次握手协商，通信网关的Linux模块与OPC UA服务完成连接。
完成连接后，Linux模块将会解析所有数据，同时开启一个符合OPC UA通信标准的服务，所有数据将会以OPC UA通信标准提供。在Linux模块完成OPC UA服务的创建后，基于Windows平台的兼容模块将会启动一个OPC UA客户端来连接Linux模块创建的OPC UA服务。兼容模块将会解析所有数据，同时开启一个符合OPC DA通信标准的服务，所有数据将会以OPC DA通信标准提供。在兼容模块完成OPC DA服务的创建后，Linux模块将会完成端口映射，使通信网关的TCP/135端口接收的数据包转发至兼容模块的TCP/135端口，并根据后续客户端握手连接时，协商的通信端口，进行端口映射，以完成通信。
上述示例中，OPC服务器支持的通信标准，与客户端支持的通信标准不同，其中OPC UA通信标准是一种与平台无关的通信标准形式，而OPC DA通信标准只适用于Windows平台。因此客户端无法直接处理OPC服务器传输的数据。通过本申请的工业通信网关中的兼容模块，可以将OPC DA通信标准的数据与OPC UA通信标准进行转化，从而在不改变OPC服务器或客户端设备原本通信形式的前提下，达到通信的目的。因此，本申请提供的数据兼容网关，可以在工业硬件设备升级过渡时期保证工业数据的通信，兼容老旧设备，减少设备投入。
上述实施例示出的通信标准中都包含OPC DA这一仅支持Windows平台的通信标准，因此，需要兼容模块针对传输的数据进行相应的转化才能完成通信。实际应用中，本申请提供的数据兼容网关系统还可以适用于其他类型的通信标准的通信情形，因此在本申请的部分实施例中，所述工业通信网关还被配置为：判断所述OPC服务器和所述客户端所支持通信标准类型是否为非OPC DA通信标准；若均是非OPC DA通信标准，通过工业通信网关的Linux内核解析数据包；以及，开启符合客户端所支持通信标准类型的服务，以通过开启的服务向客户端发送解析后的数据包。
例如，对于OPC服务器仅支持OPC DA通信标准，客户端也仅支持OPC DA通信标准的情景，由于都涉及到OPC DA通信标准，因此在该情景下，通信网关的角色是OPC DA客户端与OPC DA服务器。
首先，基于Windows平台的兼容模块会主动向OPC DA服务发起连接，数据包将先发送给通信网关的Linux内核。Linux系统中的Netfilter模块会将数据包进行SNAT转换，再发送给OPC DA服务，OPC DA服务收到连接请求后将会回复工业通信网关。该回复将先由Linux内核捕获，Netfilter模块根据之前的SNAT转换，将该数据包转发给兼容模块。经过几次握手协商，通信网关的兼容模块与OPC DA服务器完成连接。
完成连接后，基于Windows平台的兼容模块将会解析所有数据，同时开启一个符合OPC DA通信标准的服务，所有数据将会以OPC DA通信标准提供。在Windows模块完成OPC DA服务的创建后，Linux模块将会完成端口映射，使通信网关的TCP/135端口接收的数据包 转发至Windows模块的TCP/135端口，并根据后续客户端握手连接时协商的通信端口进行端口映射以完成通信。
上述示例中，由于工业通信网关也是基于Linux平台，并且工业通信网关作为网关设备需要对数据进行初步处理，因此，在本实施例中，即便是OPC服务器与客户端都是支持OPC DA通信标准的情景，依然需要兼容模块将数据进行解析。
另外，在实际应用中，如果所述OPC服务器和所述客户端所支持通信标准类型均为非OPC DA通信标准，所述工业通信网关还被配置为：遍历当前工业通信网关的全部网关任务中，是否存在应用OPC DA通信标准的网关任务；若不存在，控制兼容模块进入休眠状态。
例如，OPC服务器支持OPC UA通信标准，客户端也支持OPC UA通信标准的情景，在该情景下，通信网关的角色是OPC UA客户端与OPC UA服务器。
工业通信网关中的Linux模块会主动向OPC UA服务发起连接，经过几次握手协商，通信网关的Linux模块与OPC UA服务完成连接。完成连接后，Linux模块将会解析所有数据，同时开启一个符合OPC UA通信标准的服务，所有数据将会以OPC UA通信标准提供。此情景下，若无其他应用到OPC DA的工程，可将兼容模块休眠。
又例如，OPC服务器支持OPC UA通信标准，客户端仅支持如Modbus协议等非OPC通信标准的情景。在该情景下，通信网关的角色是OPC UA客户端与Modbus Slave。
通信网关的Linux模块会主动向OPC UA服务发起连接，经过几次握手协商，通信网关的Linux模块与OPC UA服务完成连接。完成连接后，Linux模块将会解析数据，然后将会把数据以Modbus协议进行封包提供给客户端应用。此情景下，若无其他应用到OPC DA的工程，可将Windows模块休眠。
由以上技术方案可知，本申请提供一种数据兼容性网关系统，包括基于Linux内核的工业通信网关，以及集成在工业通信网关中的兼容模块；其中，工业通信网关被配置为接收通信数据，以及根据通信数据的通信标准，将OPC DA通信标准的数据发送至兼容模块。兼容模块基于Windows内核，能够解析OPC DA通信标准的数据以及独立运行基于Windows的应用程序，并且被配置为接收OPC DA通信标准的数据，以及将OPC DA通信标准的数据解析并发送给工业通信网关。通过在基于Linux内核的工业通信网关中内置兼容模块，可以实现对OPC DA通信标准和非OPC DA通信标准的数据双向兼容，解决基于Linux内核开发的工业通信网关，兼容仅支持OPC DA通信标准设备的问题。
本申请提供的实施例之间的相似部分相互参见即可，以上提供的具体实施方式只是本申请总的构思下的几个示例，并不构成本申请保护范围的限定。对于本领域的技术人员而言，在不付出创造性劳动的前提下依据本申请方案所扩展出的任何其他实施方式都属于本申请的保护范围。

Claims (6)

  1. 一种数据兼容性网关系统，其特征在于，包括基于Linux内核的工业通信网关，以及集成在所述工业通信网关中的兼容模块；所述兼容模块基于Windows内核，能够解析OPC DA通信标准的数据以及独立运行基于Windows的应用程序；
    所述工业通信网关被配置为接收通信数据，以及根据所述通信数据的通信标准，将OPC DA通信标准的数据发送至所述兼容模块；
    所述兼容模块被配置为接收OPC DA通信标准的数据，以及将OPC DA通信标准的数据解析并发送给所述工业通信网关；
    所述数据兼容性网关系统还包括连接所述工业通信网关的多个OPC服务器和客户端；
    多个OPC服务器分置于多个工业现场，以采集或生成数据；多个客户端中内置工业应用程序；所述客户端通过所述工业通信网关获取OPC服务器采集或生成的数据，并通过内置的应用程序处理获取的数据；
    所述工业通信网关还被配置为：通过分析OPC服务器和客户端曾经传输的数据通信标准类型的历史记录，或者通过OPC服务器和客户端的注册信息获取任一所述OPC服务器和任一所述客户端所支持的通信标准类型；以及，
    判断所述OPC服务器和所述客户端所支持的通信标准类型是否一致；若不一致，将从OPC服务器获取的数据，转化为所述客户端所支持通信标准的数据；
    兼容模块被进一步配置为：向工业通信网关发起连接；以及，解析工业通信网关发送的数据包，并开启符合所述客户端所支持通信标准类型的服务，以将解析后的数据通过开启的服务提供给所述客户端；
    所述工业通信网关被配置为与所述兼容模块建立连接；以及，对所述OPC服务器发送的数据包进行源地址转换，并将源地址转换后的数据包发送给所述兼容模块。
  2. 根据权利要求1所述的数据兼容性网关系统，其特征在于，所述工业通信网关与所述兼容模块通过以太网连接，所述兼容模块包括独立于所述工业通信网关的处理器、存储器和以太网接口；
    通过所述以太网接口接收的OPC DA通信标准的数据，在所述存储器中被所述处理器解析；以及，解析后的数据通过以太网接口发送给所述工业通信网关。
  3. 根据权利要求1所述的数据兼容性网关系统，其特征在于，所述工业通信网关内置Netfilter模块；通过所述OPC服务器获取的数据包，先发送至所述工业通信网关的Linux内核，再通过所述Netfilter模块将数据包进行源地址转换。
  4. 根据权利要求1所述的数据兼容性网关系统，其特征在于，所述工业通信网关还被配置为：在所述兼容模块开启符合所述客户端所支持通信标准类型的服务后，进行端口映射，使接收的数据包通过端口映射转发至所述兼容模块。
  5. 根据权利要求1所述的数据兼容性网关系统，其特征在于，所述工业通信网关 还被配置为：判断所述OPC服务器和所述客户端所支持通信标准类型是否为非OPC DA通信标准；若均是非OPC DA通信标准，通过工业通信网关的Linux内核解析数据包；以及，
    开启符合客户端所支持通信标准类型的服务，以通过开启的服务向客户端发送解析后的数据包。
  6. 根据权利要求5所述的数据兼容性网关系统，其特征在于，所述工业通信网关还被配置为：遍历当前工业通信网关的全部网关任务中，是否存在应用OPC DA通信标准的网关任务；若不存在，控制兼容模块进入休眠状态。
PCT/CN2020/070991 2019-08-19 2020-01-08 一种数据兼容性网关系统 WO2021031518A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
GB2006718.7A GB2580848B (en) 2019-08-19 2020-01-08 Data compatible gateway system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910761564.XA CN110278148B (zh) 2019-08-19 2019-08-19 一种数据兼容性网关系统
CN201910761564.X 2019-08-19

Publications (1)

Publication Number Publication Date
WO2021031518A1 true WO2021031518A1 (zh) 2021-02-25

Family

ID=67966078

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/070991 WO2021031518A1 (zh) 2019-08-19 2020-01-08 一种数据兼容性网关系统

Country Status (2)

Country Link
CN (1) CN110278148B (zh)
WO (1) WO2021031518A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110278148B (zh) * 2019-08-19 2020-01-31 江苏金恒信息科技股份有限公司 一种数据兼容性网关系统
CN111275378A (zh) * 2020-01-15 2020-06-12 吉利汽车研究院（宁波）有限公司 一种基于仓储控制系统的数据处理系统、数据处理方法及存储介质
CN114205328B (zh) * 2021-12-11 2023-06-02 英赛克科技（北京）有限公司 一种opc数据转发方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014066593A2 (en) * 2012-10-28 2014-05-01 The Mathworks, Inc. Self-testing graphical component algorithm specification
US20160294617A1 (en) * 2015-04-01 2016-10-06 Schneider Electric Industries Sas Method for configuring a web services gateway and web services gateway
CN108052086A (zh) * 2017-12-28 2018-05-18 珠海格力智能装备技术研究院有限公司 数据采集系统
CN108293017A (zh) * 2015-12-08 2018-07-17 霍尼韦尔国际公司 用于使用物联网边缘安全网关的装置和方法
CN108833269A (zh) * 2018-06-26 2018-11-16 中国兵器装备集团自动化研究所 一种面向工业现场的智能物联网关
CN110278148A (zh) * 2019-08-19 2019-09-24 江苏金恒信息科技股份有限公司 一种数据兼容性网关系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107222575B (zh) * 2017-07-13 2019-08-06 英赛克科技（北京）有限公司 实现工控设备间opc通信的方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014066593A2 (en) * 2012-10-28 2014-05-01 The Mathworks, Inc. Self-testing graphical component algorithm specification
US20160294617A1 (en) * 2015-04-01 2016-10-06 Schneider Electric Industries Sas Method for configuring a web services gateway and web services gateway
CN108293017A (zh) * 2015-12-08 2018-07-17 霍尼韦尔国际公司 用于使用物联网边缘安全网关的装置和方法
CN108052086A (zh) * 2017-12-28 2018-05-18 珠海格力智能装备技术研究院有限公司 数据采集系统
CN108833269A (zh) * 2018-06-26 2018-11-16 中国兵器装备集团自动化研究所 一种面向工业现场的智能物联网关
CN110278148A (zh) * 2019-08-19 2019-09-24 江苏金恒信息科技股份有限公司 一种数据兼容性网关系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
FANG XIN: "Design and Development of Security Gateway for Control System Based on Dual Board Architecture", CHINESE MASTER'S THESES FULL-TEXT DATABASE, 1 March 2017 (2017-03-01), pages 1 - 72, XP055782204 *
HE CHONGBO: "Research and Implementation of Server Middleware Based on OPC UA-DA", MASTER THESIS, 28 February 2014 (2014-02-28), pages 1 - 63, XP009526150 *

Also Published As

Publication number Publication date
CN110278148A (zh) 2019-09-24
CN110278148B (zh) 2020-01-31

Similar Documents

Publication Publication Date Title
WO2021031518A1 (zh) 一种数据兼容性网关系统
US8140688B2 (en) Method and system for establishing connections between nodes in a communication network
JP2003134142A (ja) 相異なるミドルウェアを使用するホームネットワーク上のデバイス間のメッセージの受け渡しを可能にするゲートウェイ、ホームネットワークシステム及びメッセージ受け渡し方法
WO2014082577A1 (zh) 实现远程调试的方法及系统
CN102984237B (zh) 一种基于socket连接的数据传输系统及方法
CN110677432A (zh) 一种网络协议内部代理转发方法、装置、介质及终端设备
CN111294399A (zh) 一种数据传输方法和装置
CN105554540A (zh) 一种网络接口在条件接收卡中的实现方法和装置
CN102811230B (zh) 一种基于应用集成的资源调用方法和系统
CN110417875B (zh) 一种云服务器之间的对接方法、系统、设备及存储介质
EP3065387A1 (en) Method and device for achieving matching between acquisition system and analysis system
GB2580848A (en) Data compatible gateway system
CN111880769B (zh) 一种适用于物联网应用系统接口的抽象描述方法及其应用
CN114089711B (zh) 工业设备控制管理方法、电子设备及存储介质
CN110661850A (zh) 一种边缘计算方法、系统、计算机设备和存储介质
CN210274135U (zh) 一种远程连接系统
CN113472637A (zh) 一种lora网关
CN102325187A (zh) 一种整合多种功能服务的系统及方法
CN112272202A (zh) 一种管理软件服务端与系统内部组件的通信方法及系统
CN117857191A (zh) 一种tcp安全通信代理方法及系统
CN115037639B (zh) 边缘数据平台接口信息的处理方法、装置、设备及介质
US20090097470A1 (en) Methods and systems for communicating data
CN100384144C (zh) 一种组合设备及其管理维护方法
CN102065028B (zh) 一种网关设备以及报文处理方法
CN113055471B (zh) 一种保持长期存活、数据交互的管理方法和系统

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 202006718

Country of ref document: GB

Kind code of ref document: A

Free format text: PCT FILING DATE = 20200108

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20855275

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20855275

Country of ref document: EP

Kind code of ref document: A1