专利摘要:
Safe bus devices use a safety protocol to transmit encapsulated safe data in an Industrial Ethernet message over an Ethernet-based fieldbus. However, the secure bus device is restricted to a specific combination of security protocol and Industrial Ethernet protocol. In order to be able to use a secure bus device 12, 14, 15i in a more flexible manner, it is provided that the Industrial Ethernet protocol for transmitting the safety-related data instead of the session layer 5 and / or presentation layer 6 implemented in the Industrial Ethernet protocol, the session layer 5 independent of the Industrial Ethernet protocol and / or uses the presentation layer 6 of the security protocol, whereby such a bus device 12, 14, 15i is independent of the Industrial Ethernet protocol.
公开号:AT512077A1
申请号:T1582/2011
申请日:2011-10-27
公开日:2013-05-15
发明作者:Franz Kaufleitner
申请人:Bernecker & Rainer Ind Elektronik Gmbh;
IPC主号:
专利说明:

BN-3439 AT • * · · ♦
Method and a bus device for transmitting safety-related data
The present invention relates to a method and a bus device for transmitting safety-related data of a safety protocol in a fieldbus via an Industrial Ethernet protocol. 5 Industrial Ethernet protocols, such as POWERLINK, Ethernet IP, ProfiNet, Ethercat, etc., are established in automation and are used for standardized data exchange between bus users in a fieldbus system. These protocols alone are not suitable, safety data, e.g. within the meaning of the international standard IEC 61508 or other safety standards. Usually this will be a security protocol, such as OpenSAFETY, ProfiSafe, CIPsafety, Safety over Ethercat, etc., which protects the data according to the safety requirements. The safety protocol protects the transmitted data against data errors, data loss and transmission errors in order to ensure correct data transmission within the scheduled transmission times. The security protocol has provided corresponding mechanisms for detecting and correcting any transmission errors. The data of the security protocol are encapsulated in a conventional Ethernet message. Such Industrial Ethernet protocols and security protocols are well known, which is why will not be discussed in more detail here. 20 data communication protocols follow the well-known OSI layer model. For all Industrial Ethernet protocols, layers 1 and 2, ie the physical transfer layer and the link layer, are the same. This means that basically all of these Industrial Ethernet protocols can be transmitted on the same ethernet-based fieldbus. The layers 3 and 4, ie the network layer and the transport layer, are present in a variety of standardized forms, such as z, B. TCP / IP or UDP / IP. The Industrial Ethernet protocols usually use these standardized layers 3 and 4, but can also use their own, specially developed layers 3 and 4. The layers 5 and 6, ie the session layer and the presentation layer, are, as a rule, already specified by the selected Industrial Ethernet protocol and thereby defined. Each Industrial Ethernet Proto-30 koli is subject to a standardization committee, which is responsible for the specification of these layers 5 and 6. These layers 5 and 6 are therefore not accessible to the users of the Industrial Ethernet protocols. In layer 7, the application layer, runs the software that accesses the Ethernet bus, e.g. the automation SW. A security protocol also runs in the application layer 7, i. all security-related mechanisms of the security protocol are implemented in the application layer 7 -1-
BN-3439 AT and safety-related data of the safety protocol are encapsulated in a message of the Industrial Ethernet protocol. In FIG. 1, this is explained by means of the security protocol OpenSAFETY, which is transmitted using the Industrial Ethernet protocol Ethemet / IP. OpenSAFETY is implemented in application layer 7 and uses here, for example, the standardized CIP (Common Industrial Protocol) of the known EtherNet / IP protocol in layers 5 and 6. The safety-oriented message of the OpenSAFETY protocol is encapsulated in a TCP / IP or UDP / IP message over an ethernet bus.
Due to the situation described above, it is possible that different secure-based protocols are transmitted on the same ethernet bus, since layers 1 and 2 are identical. When transmitting safety-related data in different Industrial Ethernet networks, however, adjustments in layers 5 and 6 may also be necessary in layer 7 and / or the implementation of an intermediate layer for data conversion. Direct communication between bus users who use the same security protocol (for example, OpenSAFETY) but different Industrial Ethernet protocols (such as Ethernet / IP or PROFINET) is also not possible. That is, a bus user on which OpenSAFETY is implemented for Ethernet / IP can not communicate with a subscriber who has implemented OpenSAFETY for PROFINET. Thus, the flexibility in the application of security protocols is very limited, or 20 special gateways must be provided that connect different buses together, but this is again consuming. Furthermore, a bus device that has implemented a specific security protocol must be developed for every imaginable Industrial Ethernet protocol, which leads to a multiplicity of variants of a bus device and requires considerable development and maintenance. 25 In addition, security protocols such as security protocols, e.g. OpenSAFETY, to implement the security mechanisms own layers 5 and 6. A secure message according to the chosen security protocol is thus packaged in a secure data frame, which also includes information of layers 5 and 6 of the security protocol. This secure message is then encapsulated in the selected 30 Industrial Ethernet protocol, in which the secure message again contains information of layers 5 and 6 of the Industrial Ethernet protocol. However, this results in an increased data overhead, which comprehensibly reduces the available data rate.
It is therefore an object of the present invention to overcome the above-mentioned disadvantages of known safety protocols that use an Industrial Ethernet protocol as a means of transport. -2-
BN-3439 AT
This object is achieved according to the invention by using the Industrial Ethernet protocol for transmitting the safety-related data instead of the session layer and / or presentation layer implemented in the Industrial Ethernet protocol, the session layer independent of the Industrial Ethernet protocol and / or the presentation layer of the security protocol. Thus, the transmission method or the bus device is independent of the specific nature of the Industrial Ethernet protocol and can thus be used without significant adjustments in any Industrial Ethernet protocol. Thus, a secure bus device that has implemented a particular security protocol need not be developed for any conceivable industrial Ethernet protocol, e.g. OpenSAFETY for PROFINET, OpenSAFETY for Ethemet / IP, etc., but it is sufficient if a secure bus device is developed once, because this is then replaceable in any Industrial Ethernet. This saves considerable development costs and such a bus device can be used extremely flexibly.
The subject invention will be described with reference to the schematic and exemplary Figures 1 to 3, which show an advantageous embodiment of the invention. It shows the
1 shows the layer model of an OpenSAFETY based security protocol according to the prior art,
FIG. 2 shows the layer model of an OpenSAFETY-based security protocol 20 according to the invention and FIG
Fig. 3 shows a typical embodiment of a fieldbus for an automation task.
The basic idea of the invention becomes clear in FIG. As before, the data communication according to the invention is shown according to the known layer model. The security protocol, here OpenSAFETY, with all necessary security mechanisms, is again implemented in the application layer 7. Instead of the standardized, non-open protocol CIP in layers 5 and 6, however, the security protocol 5 and presentation layer 6 of the security protocol also defined in the security protocol (OpenSAFETY) are now used. This is independent of the Industrial Ethernet protocol and advantageously an open standard, i. freely accessible to all users within the specifications of the open standard.
It may also be sufficient for the data communication to implement only the security layer 5 or the presentation layer 6. In this case, it is of course sufficient if only the security layer 5 or the presentation layer 35 6 of the security protocol is also used for the data communication. -3- »· t ··« · · ··: ϊ Ί; Ί *. ** ΒΝ-3439ΑΤ «···· · · ·· ♦« · ··· * * < ·····
3 shows a typical configuration of a fieldbus 10 in an automation environment. On a number of I / O units 15 sensors or actuators, not shown here, are connected in a manner known per se. The sensors and actuators communicate with control units 12, 13, which control the automation tasks. The communication 5 takes place via a field bus 11 to which all bus subscribers are connected. The I / O units 15 may be configured for direct communication with the controllers 12, 13, or it may be provided that a bus controller 14 handles the communication between the controllers 12, 13 and the individual I / O units 15, such as shown in Fig. 3. To do this, the bus controller 14 exchanges e.g. Via a data bus of a backplane data 10 with the I / O units 15 and connects the I / O units 15 to the field bus 11. The arrows shown in Fig. 3 are for better understanding, only the logical access of the control units on the I / O units 15, the communication takes place via the field bus 11.
The fieldbus 11 now operates secure controllers 12 that communicate with secure I / O units 15, or other secure bus subscribers. For this purpose, in the control unit 12 and 15 in the secure I / O units 15i or in the bus controller 14, a security protocol, e.g. OpenSAFETY implemented. The secure data is stored in fieldbus 11 in one of the Industrial Ethernet protocols used, e.g. PROFINET, independent protocol, such as OpenSAFETY over TCP / IP or UDP / IP (as shown in Figure 2), where "transmitting" means both transmitting and receiving data. In the field bus 11 can still further not secure bus participants, such as a non-secure controller 13 and non-secure I / O units 152 are operated. For this purpose, the Industrial Ethernet protocol, e.g. PROFINET, implemented.
In the case of a bus controller 14, both the security protocol and the industrial Ethernet protocol must be implemented on it in order to be able to communicate with both.
In the secure controller 12 and / or in the bus controller 14 and / or the secure I / O units 15i, or other secure bus devices, instead of the session layer and / or presentation layer (layers 5 and 6 in the OSI model) of the Industrial Ethernet protocol, implements the session protocol and / or presentation layer 30 of the security protocol independent of the Industrial Ethernet protocol. This makes the safe bus device independent of Industrial Ethernet and can be used in any Industrial Ethernet without major adjustments being required. That is, e.g. a device which is implemented as a security protocol OpenSAFETY and which also uses the layers 5 and 6 of the security protocol with any other bus device configured in this way over 35 can communicate with the fieldbus 11, regardless of the actual conditions of the -4- · »* ··» ························································································································································································································································ Ethernet protocol.
Of course, in addition to layers 5 and 6 of the security protocol, layers 5 and 6 of an Industrial Ethernet protocol could also be implemented in the bus device, eg. CIP of the Ethernet / IP protocol, as indicated in Figure 2. In this way, such a bus device could also communicate with conventional secure or non-secure bus devices which use the Industrial Ethernet protocol as the session layer and / or presentation layers. Thus, such a bus device is even more flexible in the applicability. -5-
权利要求:
Claims (2)
[1]
.rt © .Ί * < ε > 1. A method for transmitting safety-related data of a safety protocol in a fieldbus (11) via an Industrial Ethernet protocol, characterized in that the Industrial Ethernet protocol for transmitting the safety-related data instead of in Industrial Ethernet Protocol implemented session layer (5) and / or presentation layer (6), the use of the Industrial Ethernet protocol independent session layer (5) and / or the presentation layer (6) of the security protocol.
[2]
2. Bus device for a field bus (11) for transmitting safety-related data ei-10 nes safety protocol via an Industrial Ethernet protocol, characterized in that in the bus device (12, 14, 15-i), the security protocol is implemented and in the bus device (12, 14,15 ^ instead of the session layer (5) and / or presentation layer (6) of the Industrial Ethernet protocol, the session layer (5) independent of the Industrial Ethernet protocol and / or the presentation layer (6) of the security protocol is implemented.
类似技术:
公开号 | 公开日 | 专利标题
AT512077B1|2014-01-15|METHOD AND A BUS DEVICE FOR TRANSFERRING SAFETY-RELATED DATA
EP1368942B1|2006-05-24|Method and system for coupling data networks
EP3679691B1|2021-01-20|Data transmission method and communication network
EP1729454B1|2010-12-08|Apparatus and method for a combined transmission of input/output data in automation bus systems
DE102015105929A1|2016-10-20|Automation device for redundantly controlling a bus subscriber
DE102011015966B4|2017-07-06|automation system
EP1430689B1|2005-03-23|Receipt of data messages in communications systems comprising redundant network paths
DE102016107450A1|2017-10-05|Secure gateway
EP2913727B1|2016-09-21|Method for transmitting messages via a backplane of a modular industrial automation device
EP1430634B1|2006-06-07|Forwarding of data messages with double-node data replacement
EP3575899B1|2021-03-17|Automation system, operating method for automation system and computer program product
DE102011015484A1|2012-10-04|Method for synchronously controlling at least one subordinate network subscriber by a higher-level control unit via an asynchronously operating network segment
EP1307989A1|2003-05-07|Communication method
AT504739B1|2013-09-15|ARRANGEMENT AND PROCEDURE FOR SAFE DATA COMMUNICATION VIA AN UNCERTAIN NETWORK
DE102005029656B3|2006-10-05|Automation system bus subscriber`s coupling method for e.g. universal communication platform for barcode and identification system, involves building communication controller on freely programmable communication arithmetic and logic unit
DE102019114303B3|2020-09-17|Method for detecting network participants in an automation network and automation network
EP2988465A1|2016-02-24|Method for transmitting an IP data packet between automation modules
EP3518480A1|2019-07-31|Method for communicating data in an ethernet-based, in particular industrial network device for carrying out the method and computer program and computer-readable medium
EP2506521A1|2012-10-03|Communication in an automation network
EP3934192A1|2022-01-05|Method for establishing a connection between a communication device and a server and proxy
DE102007041621B4|2011-06-30|Method and device for stabilizing a data radio link
AT503207B1|2009-04-15|METHOD AND SYSTEM FOR TRANSFERRING DATA
EP1318630B1|2005-05-11|Matrices for controlling the device specific data transfer rates on a field bus
EP1371193A2|2003-12-17|Elektronischer schaltkreis und verfahren fur eine kommunikationsschnittstelle mit cut-through pufferspeicher
EP3435179A1|2019-01-30|Method for functionally secure exchange of information according to a safety standard
同族专利:
公开号 | 公开日
EP2587738B1|2014-08-06|
ES2495432T3|2014-09-17|
AT512077B1|2014-01-15|
US9021167B2|2015-04-28|
CN103095673B|2017-04-26|
CN103095673A|2013-05-08|
US20130111087A1|2013-05-02|
EP2587738A1|2013-05-01|
引用文献:
公开号 | 申请日 | 公开日 | 申请人 | 专利标题
CN1482782A|2003-06-20|2004-03-17|上海大学|Method and apparatus for protocol switch between MODBUS/TCP industrial Ethernet and device network field bus|
US20100082837A1|2008-09-30|2010-04-01|Relander Randi J|Method and apparatus for communications accelerator on cip motion networks|
KR20100060335A|2008-11-27|2010-06-07|삼성전자주식회사|Network apparatus and method for controlling the same|
US6999824B2|1997-08-21|2006-02-14|Fieldbus Foundation|System and method for implementing safety instrumented systems in a fieldbus architecture|
WO2004095716A2|2003-04-17|2004-11-04|Fieldbus Foundation|System and method for implementing safety instrumented systems in a fieldbus architecture|
CN1697448A|2005-04-21|2005-11-16|上海大学|Multi protocol conversion method and device between MODBUS/TCP industry Ethernet and field bus device network as well as field bus of PRofibus DP|
EP2211523B1|2009-01-23|2016-05-04|Siemens Aktiengesellschaft|Communication network and conversion module|
CN102801574B|2011-05-27|2016-08-31|阿里巴巴集团控股有限公司|The detection method of a kind of web page interlinkage, device and system|DE102011107318A1|2011-07-06|2013-01-10|Abb Ag|Method for configuring a communication interface module in a control or automation system|
DE102012009494B4|2012-05-14|2017-04-13|Balluff Gmbh|Control device for controlling a security device|
DE102012014681B4|2012-05-29|2017-01-26|Balluff Gmbh|Use of a lO link for connecting a power supply unit|
DE102012014682B4|2012-05-29|2017-02-09|Balluff Gmbh|fieldbus system|
EP2939374B1|2012-12-24|2017-07-26|Festo AG & Co. KG|Field unit and a method for operating an automation system|
DE102014114883A1|2014-10-14|2016-04-14|Beckhoff Automation Gmbh|Method and system for monitoring a first subscriber of a communication network|
CN104821948B|2015-05-08|2018-08-10|浙江大学|OpenSAFETY functional safety implementation methods based on POWERLINK|
US10165095B2|2015-06-22|2018-12-25|Rockwell Automation Technologies, Inc.|Active report of event and data|
法律状态:
2018-03-15| HC| Change of the firm name or firm address|Owner name: B&R INDUSTRIAL AUTOMATION GMBH, AT Effective date: 20180205 |
优先权:
申请号 | 申请日 | 专利标题
ATA1582/2011A|AT512077B1|2011-10-27|2011-10-27|METHOD AND A BUS DEVICE FOR TRANSFERRING SAFETY-RELATED DATA|ATA1582/2011A| AT512077B1|2011-10-27|2011-10-27|METHOD AND A BUS DEVICE FOR TRANSFERRING SAFETY-RELATED DATA|
ES12187091.9T| ES2495432T3|2011-10-27|2012-10-03|Procedure and a bus device for the transmission of safety-oriented data|
EP20120187091| EP2587738B1|2011-10-27|2012-10-03|Method and a bus device for transferring security-oriented data|
US13/661,698| US9021167B2|2011-10-27|2012-10-26|Method and a bus device for transmitting safety-oriented data|
CN201210414458.2A| CN103095673B|2011-10-27|2012-10-26|Method and a bus device for transferring security-oriented data|
[返回顶部]