US20210075838A1 - Control Method, Apparatus, Computer Program, Computer-Readable Medium and Method for Communicating Data in an Industrial Network - Google Patents
Control Method, Apparatus, Computer Program, Computer-Readable Medium and Method for Communicating Data in an Industrial Network Download PDFInfo
- Publication number
- US20210075838A1 US20210075838A1 US16/965,970 US201916965970A US2021075838A1 US 20210075838 A1 US20210075838 A1 US 20210075838A1 US 201916965970 A US201916965970 A US 201916965970A US 2021075838 A1 US2021075838 A1 US 2021075838A1
- Authority
- US
- United States
- Prior art keywords
- field bus
- stream
- network
- data
- avb
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 70
- 238000004590 computer program Methods 0.000 title claims abstract description 5
- 230000005540 biological transmission Effects 0.000 claims description 25
- 230000008569 process Effects 0.000 claims description 9
- 230000006855 networking Effects 0.000 claims description 8
- 239000000872 buffer Substances 0.000 claims description 4
- 230000006854 communication Effects 0.000 description 14
- 238000004891 communication Methods 0.000 description 14
- 230000007246 mechanism Effects 0.000 description 8
- 230000006870 function Effects 0.000 description 6
- 230000000694 effects Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000013439 planning Methods 0.000 description 4
- 238000013461 design Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000003745 diagnosis Methods 0.000 description 2
- 230000000712 assembly Effects 0.000 description 1
- 238000000429 assembly Methods 0.000 description 1
- 230000007175 bidirectional communication Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
- 230000005641 tunneling Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/80—Responding to QoS
-
- H04L65/4069—
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
- G05B19/4185—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by the network communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
- H04L12/462—LAN interconnection over a bridge based backbone
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/02—Capturing of monitoring data
- H04L43/026—Capturing of monitoring data using flow identification
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0852—Delays
- H04L43/0858—One way delays
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1083—In-session procedures
- H04L65/1093—In-session procedures by adding participants; by removing participants
-
- H04L65/608—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Definitions
- the invention relates to a control method, an apparatus, a computer program, a computer-readable medium and a method for communicating data in a network, in particular an industrial network, in which data are transmitted between at least two devices, at least one device of which is on a field bus.
- PLCs programmable logic controllers
- a PLC is generally connected to the machine, the system or a process via sensors providing a plurality of input values and actuators receiving a plurality of control values.
- Actuators may be, for example, in the form of contactors, electric valves and modules for drive controllers.
- the sensors and actuators are arranged close to the process(es) to be automated in order to capture the required measured values at the relevant locations and to be able to act on the process at required locations.
- the position of the actuators is also determined by the structure of the machine or system.
- control system receives measured values captured by the sensors from the latter, calculates (inter alia) control values for the actuators based on the measured values and transmits the control values to the actuators.
- communication networks “field buses”, have been developed.
- IEC International Electrotechnical Commission
- a simple bus system is generally distinguished by the fact that the individual devices connected to it are connected to one another via a bus line.
- a bus network has typically been laid from the control system, in particular the PLC, to all sensors and actuators which constitute field devices.
- Further devices for example, operating and/or display devices, can also be connected to the control system via a field bus to transmit data from or for the devices.
- PROFIBUS is mentioned as an example of such a physical bus system.
- Ethernet for Ethernet, see Institute of Electrical and Electronics Engineers (IEEE) standard 802, in particular IEEE 802.3
- PROFINET RT for example.
- IEEE Institute of Electrical and Electronics Engineers
- the communication network in the form of the field bus and based on Ethernet is still considered to be a single logical cable (bus network).
- the available bandwidth generally 100 Mbit/s
- the available bandwidth is usually permanently divided into a half (generally 50 Mbit/s) for real-time data and a further half (generally 50 Mbit/s) for other traffic. Compliance with the bandwidth must then be ensured by the design of the real-time application.
- Network devices detect the real-time data based on proprietary expansions or by using special addresses and assign these to the corresponding resources.
- a stream is a protected, unidirectional communication connection from a device, which is also referred to as a talker and forms a data source, to one or more devices, which are also referred to as listeners and constitute the data sinks, i.e., receivers.
- Time Sensitive Networking denotes a series of standards that expands the bridging standard IEEE 802.1Q with mechanisms for transmitting real-time-critical data via Ethernet networks.
- the standards mentioned include, for example, time synchronization (IEEE 802.1As-Rev), frame pre-emption (IEEE 802.1Qbu) and reservation (IEEE 802.1Qca, IEEE 802.1Qcc) as well as other standards.
- a registration and a reservation are performed to obtain guarantees of a loss-free real-time transfer of data frames and a punctual delivery from the network.
- a reservation is performed, in particular, via a stream reservation protocol (SRP).
- SRP stream reservation protocol
- Multiple listeners per stream was introduced in AVB in order to reduce the number of real-time data flows from a source (talker) to a plurality of destinations (listeners). Specifically, it is possible to transmit data from one talker to a plurality of listeners using only one stream.
- the European patent application which traces back to the applicant and has the file reference EP 18 15 4319 also discloses a stream reservation model which enables “multiple talkers per listener”, specifically the transmission of data from a plurality of talkers to one listener using only one stream.
- US 2013/070788 A1 discloses a method for interchanging data between two devices of a network, which uses a communication protocol with an interface according to the OPC-UA standard to interchange the data.
- the communication protocol comprises an interface according to the Stream Reservation Protocol (SRP) standard or Multiple Stream Registration Protocol (MSRP) standard according to IEEE 802.1Qat, with the result that the data can be interchanged between the two devices via both interfaces in a predefined period of time.
- SRP Stream Reservation Protocol
- MSRP Multiple Stream Registration Protocol
- US 2017331719A1 relates to a method for configuring a communication path, which is performed in a first communication node of a vehicle network.
- the method comprises receiving a first frame that requests the configuration of a communication path that is used to transmit a data stream.
- the method also comprises configuring a directory of the first communication node based on an item of information in the first frame if a second frame having a data stream identifier identical to a data stream identifier of the first frame is not received.
- the method also comprises incrementing a hop number of the first frame and transmitting the first frame which has the incremented hop number.
- a method for communicating data in a network in particular an industrial network, in which data are transmitted between at least two devices, at least one device of which is on a field bus, where the data are transmitted at least in sections via an AVB or TSN network in which at least one stream has been or is configured for the field bus, where resources have been and/or are reserved for the at least one stream at one or more nodes, in particular switches and/or bridges, of the network, and data frames that come (emanate) from at least one device on the field bus and/or are intended for at least one device on the field bus are transmitted via the at least one stream.
- the invention also provides for the or each field bus to be connected to the AVB or TSN network via at least one connection node, where the at least one connection node has a field bus port in the direction of the respective field bus and a stream port in the direction of the AVB or TSN network, and the at least one connection node is configured to assign, in particular prefix, at least one stream parameter, in particular a designated stream address and/or a VLAN ID and/or a priority, to data frames that arrive at the field bus port and to remove at least one stream parameter, in particular a designated stream address and/or a VLAN ID and/or a priority, from data frames that arrive at the stream port.
- the at least two devices are preferably devices/components of an industrial automation application, such as field devices and/or control devices, where a control device may be, in particular, formed as a programmable logic controller (PLC).
- Field devices may be, for example, in the form of I/O devices, which comprise one or more sensors and/or actuators, or are assigned thereto or are connected thereto.
- the invention is based on the concept of using the new standardized Ethernet mechanisms to map one or more logical field buses (in particular as an entire system) to a communication path in an Ethernet network. This makes it possible, in particular, to continue to use existing concepts of field bus technology. Existing devices can continue to be used together with the new standards, in particular AVB or its expansion TSN.
- not all existing devices for instance sensors and/or actuators, are preferably individually connected to the AVB or TSN network, but rather a plurality of devices remain on an existing field bus or a part/segment of an existing field bus, in particular, and are connected to one or more further field bus devices, which are on at least one further field bus part or segment, via the AVB or TSN network and via (a) stream(s).
- the field bus or (if there are a plurality) the field buses may be physical field buses (for example, PROFIBUS) and/or logical field buses (for example, PROFINET) based on an Ethernet network without an AVB or TSN expansion.
- PROFIBUS physical field buses
- PROFINET logical field buses
- the devices or components can still communicate in accordance with the existing standard belonging to the field bus.
- Ethernet data frames (according to IEEE 802, in particular IEEE 802.3) are still transmitted within the field bus, for instance, without an AVB or TSN expansion, i.e., not via a stream.
- Physical field buses, such as PROFIBUS include other codings for the data frames which can likewise still be used within the (respective) field bus or (respective) field bus segment. The field bus devices therefore need not be changed for the AVB or TSN network which complies with the new standards.
- At least one stream i.e., a protected connection with secure, reserved resources and, in particular, a defined latency
- the AVB or TSN network is accordingly a network which supports the configuration of streams by means of resource reservation.
- All parameters needed to configure the stream(s) are generally present in the engineering of a field bus anyway, in particular in the TIA portal, and can be used in a simple manner.
- the packet size, number of packets, the bandwidth, the update cycle, the transmission interval and the latency are mentioned as examples of these parameters.
- the (respective) logical field bus is already contained in the engineering programs for configuring the subscribers. In the case of PROFINET, for example, this can be performed in the TIA portal.
- the logical connection of planned assemblies in the hardware configurator produces a logical field bus.
- the logical bus system usually has a name and, for internal use, a unique ID (for example, a Universally Unique Identifier (UUID)).
- UUID Universally Unique Identifier
- the data rate of the physical bus or of the underlying Ethernet network (without an AVB or TSN expansion), which represents the logical bus can be adjusted, for example. Data frames of the respective field bus can be assigned to one or more streams using the name or the unique ID.
- Associated field bus segments or field bus devices can also be identified using a field bus name and/or an associated unique ID.
- the latency requirement of very time-critical applications can also be complied with in the field buses by using pre-emption (IEEE 802.1Qbu) in a TSN network.
- pre-emption IEEE 802.1Qbu
- the time needed to transmit a frame with the maximum volume of data would be approximately 125 microseconds, which is already greater than a short bus cycle of 64 microseconds.
- AVB and TSN technology is available in comparatively inexpensive network components, in particular as a result of the use which has already been effected in the automotive sector and/or the origin of AVB (Audio Video Bridging) from home networks.
- AVB Audio Video Bridging
- AVB or TSN mechanisms streams
- the use in accordance with the invention of one or more streams results in a robust, guaranteed transmission with secure resources and guarantees the compliance with a required latency for real-time applications.
- the data to be transmitted are protected from an excessive effect from other real-time applications and/or other applications in the network by virtue of the reservation. Other applications then have only a slight but accurately known effect on the transmission time, in particular. As a result of the resource reservation, real-time data are not lost.
- the packet selection can be limited to the packets belonging to the (respective) field bus.
- This recognition can be performed, for example, by resorting to the Ethertype.
- the Ethertype is a defined part of an Ethernet data frame and defines the protocol that transmits the data and processes them at the destination after reception. In the case of PROFINET RT for example, the Ethertype is 0x8892.
- the at least one stream is preferably configured in an automated manner for the or each field bus.
- resources are reserved in a manner known per se before the actual transmission of the data at one or more nodes of the network, which is preferably performed using a reservation protocol.
- a reservation protocol for the real-time flow makes it possible to perform the complex configuration automatically in the network, in which case the topology present in each case is used.
- Resources that have been and/or are reserved may be, for example, address table entries, frame buffers, transmit time slices, bandwidth, jitter, latency etc.
- address table entries and/or frame buffers and/or bandwidth have been and/or are reserved as resources for the at least one stream at one or more nodes of the network. At least one address table entry and a frame buffer and bandwidth have been and/or are particularly preferably reserved at at least one node.
- Data frames can be assigned to a tunnel or stream at the end points on the basis of the protocol.
- the frame ID i.e., the ID within the Ethernet data frames
- the frame ID can also be additionally used. This makes it possible to select a separate tunnel, i.e., a stream, for each service of a field bus, in particular a PROFINET service.
- the stream(s) can be automatically configured in a simple manner, in particular by using a reservation protocol and/or resorting to parameters from existing field bus engineering, in particular a TIA portal, which facilitates handling and enables use by users even without special IT knowledge.
- one or more streams can be used to transmit data between two or more devices within a field bus and/or to transmit data between devices that are on two or more different field buses, i.e., between two or more field buses, and/or to transmit data between devices, at least one of which is on a field bus and at least one of which is not on a field bus.
- an AVB or TSN network should be understood as meaning a network that complies with one or more Audio Video Bridging (AVB) or Time Sensitive Networking (TSN) standards, in particular comprises one or more AVB-enabled or TSN-enabled nodes, such as switches and/or bridges.
- the network or the nodes is/are configured, in particular, to comply with one or more AVB or TSN standards.
- the AVB standards include, in particular, IEEE 802.1AS, IEEE 802.1Qat, IEEE 802.1Qav, IEEE 802.1BA, and the TSN standards include, for example, time synchronization (IEEE 802.1AS-Rev), frame pre-emption (IEEE 802.1Qbu) and reservation (IEEE 802.1Qca, IEEE 802.1Qcc) as well as other standards.
- IEEE 802.1AS-Rev time synchronization
- IEEE 802.1Qbu frame pre-emption
- IEEE 802.1Qca IEEE 802.1Qcc
- field buses can still exist as logical field buses.
- the user can consider communication to be a bus, as before, and can logically connect the devices to one another.
- Transmission in the AVB or TSN Ethernet network is protected via the stream(s) and can no longer be disrupted by other applications.
- the field bus(es) also become visible as a connection in the AVB or TSN network through the reservation of at least one stream, which also makes it possible to diagnose faults and resource bottlenecks in the AVB or TSN network in a very simple manner.
- the logical field bus(es) become(s) visible in the diagnosis of the AVB or TSN network in the form of at least one stream, preferably in the form of precisely two streams for bidirectional communication.
- Each stream, in particular each transmission direction of the tunneled communication (logical bus) can then be discerned in the network management with the resources used. For example, bridges with an insufficient number of FDB entries can thus be recognized in the AVB or TSN network.
- This diagnosis for streams is part of the SRP reservation protocol (in IEEE 802.1Q).
- the transmission of data frames via the at least one stream is, in particular, such that compliance with the bandwidth is guaranteed by means of a shaper, in particular in accordance with IEEE 802.1.
- a maximum latency can be guaranteed on the way at each node, for instance, each bridge.
- a break is made, for example, during the transmission or forwarding of each data frame, in an AVB or TSN stream via the Credit Based Shaper (CBS) in accordance with IEEE 802.1Qav, the length of which break depends on the size of the data frame and the reserved bandwidth. In this case, the longer the break, the larger the data frame transmitted or forwarded before the break, i.e., the greater the forwarded or transmitted volume of data.
- the relationship is linear, in particular, in this case.
- the length of the break corresponds, in particular, to the length of the time needed to transmit the respective data frame multiplied by a factor dependent on the reserved bandwidth. If, for example, 25% of the bandwidth is reserved for a stream, then a break is made, in particular, after each data frame, which break is three times as long as the time needed to transmit it. If 50% is reserved, then the break is as long as the transmission time and so on.
- the factor for the length of the break is known based on the reservation and is permanently configured. This procedure guarantees that the bandwidth is complied with. Frames that arrive at a node, in particular a bridge or a switch, of the AVB or TSN network, can always be immediately forwarded.
- a field bus segment may also comprise an individual device or may be given by such a device. This means that data can also be interchanged, for example, between a field bus segment, on which two or more devices are present, and an individual field bus device via a stream.
- two or more field buses, on which there is at least one device in each case, are provided, and at least one stream assigned to the respective field bus has been or is configured for each field bus in the AVB or TSN network, where resources have been and/or are reserved for each stream at one or more nodes, in particular switches and/or bridges, of the network, and data frames which come (emanate) from at least one device on the respective field bus and/or are intended for at least one device on the respective field bus are transmitted via the respective at least one stream in the AVB or TSN network.
- a plurality of logical field buses can also be combined in the network, for each of which 50 Mbit/s, for example, is then assumed as the maximum bandwidth for a real-time data transmission.
- a plurality of field buses can therefore also be connected via a network.
- Secure resources then exist for each field bus in the faster AVB-based or TSN-based network by virtue of streams. The reservation can be performed, for example, based on the maximum physical field bus speed in the TSN backbone network.
- a low latency can be achieved via a faster link speed and it is optionally possible to resort to pre-emption for real-time applications, in particular with a comparatively short cycle, for example below 250 microseconds.
- At least two streams are particularly preferably configured for the or each field bus and, in particular, data frames are transmitted in the direction of the respective field bus via at least one stream and data frames that come (emanate) from the respective field bus are transmitted via at least one further stream.
- the entire data transmission can then be performed in both directions, in particular, using two or more streams for which resources have been or are reserved at one or more nodes on the stream network path, in particular switches and/or bridges.
- data frames that comprise, as useful data, measured values captured by sensors of an automation system or data representing said measured values and/or actuating values intended for actuators of an automation system or data representing the actuating values are transmitted via a stream, in particular.
- data for configuring the network and one or more devices on a field bus, in particular sensors and/or actuators, and/or data for periodically monitoring one or more devices on a field bus are transmitted.
- the at least one stream is or has been configured for the or each field bus by resorting to configuration data relating to the (respective) field bus, in particular configuration data relating to the TIA portal of the (respective) field bus.
- configuration data which are generally present in the engineering of a field bus anyway can be used in a simple manner.
- the packet size, number of packets, the bandwidth, the update cycle, the transmission interval and the latency are mentioned as examples of these parameters.
- Data between one or more devices on the respective field bus or field bus segment and the or each connection node can be transmitted according to the existing field bus standard, for example, via Ethernet without an AVB or TSN expansion (in particular according to IEEE 802.3) in the case of PROFINET.
- a logical configuration is preferably provided in the connection node(s) and makes it possible to connect the field bus to the (respective) stream; for example, a PRU is integrated in the respective connection node.
- a PRU is a programmable function in a device having at least two ports, which function can manipulate received frames or frames to be transmitted before further internal processing or transmission, depending on the program, and can add, change and/or remove contents.
- the program of the PRU can ensure that all arriving frames that must be transmitted via a tunnel can be recognized as a stream in the superordinate AVB or TSN network. Data frames of an AVB or TSN stream can be recognized, in particular, via the destination address used and/or the VLAN ID and/or VLAN priority.
- At least one stream parameter is preferably provided by the or each connection node in a header of data frames from the field bus which arrive at the field bus port, or a (stream) header having one or more stream parameters is prefixed to the respective data frame.
- connection node practically forms a connector between the (respective) field bus (network) and the AVB or TSN network in which at least one stream has been or is configured, or a network path belonging to the (respective) stream which can also be referred to as a stream network path.
- the at least one connection node undertakes the function of a proxy, in particular, and/or (respectively) forms an end point of the (respective) stream.
- the connection node(s) is/are preferably a two-port or multiport device that has at least one port in the field bus and has at least one further port in the direction of the stream network path.
- connection nodes makes it possible to smoothly convert field bus data frames, which may be, for example, in the form of Ethernet (without AVB or TSN expansion) frames or data frames with another coding, into stream-enabled data frames, in particular with a designated stream address and/or a VLAN tag, in particular a VLAN ID and/or a priority, and/or other stream parameters that are generally in a frame header, and vice versa.
- the respective stream data frame then comprises, in particular, the header and useful data that follow the header and are also referred to as “payload”.
- the “payload” of the stream data frame then corresponds, in particular, to the field bus data frame. In the opposite direction, at least one stream parameter or a header is removed, in particular.
- connection node or its function is integrated in a device, for instance a control device, for example in the form of a PLC.
- connection node is preferably provided for each field bus, and at least two connection nodes are preferably provided for each field bus.
- connection nodes are provided, they preferably form nodes at which resources have been and/or are reserved for the at least one stream.
- connection node(s) and/or possibly existing further nodes are preferably in the form of AVB-enabled or TSN-enabled nodes. They may (each) be, for example, an AVB-enabled or TSN-enabled bridge and/or an AVB-enabled or TSN-enabled switch or other AVB-enabled or TSN-enabled devices.
- the at least one port of the connection node in the direction of the network is preferably an AVB or TSN port.
- one or more devices of the or each field bus have been connected to the field bus port of one connection node and one or more further devices of the or each field bus have been connected to the field bus port of the other connection node.
- connection of the respective device to the respective field bus port may be direct or indirect (via one or more further components), for example, via one or more field bus nodes, in particular switches and/or bridges, of the respective field bus.
- the computer-readable medium may be, for example, a CD-ROM or a DVD or a USB or a flash memory. It should be noted that a computer-readable medium should not be solely understood as meaning a physical medium, but rather such a medium may also be available, for example, in the form of a data stream and/or a signal representing a data stream.
- FIG. 1 shows a purely schematic illustration of the logical arrangement of an Ethernet-based PROFINET field bus of an industrial automation system in accordance with the invention
- FIG. 2 shows a purely schematic illustration of a field bus of an industrial automation system, for which two streams have been configured in a TSN network in accordance with the invention
- FIG. 3 shows a purely schematic illustration of a connection node in the form of a two-port device, for example, with an integrated PRU in accordance with the invention
- FIG. 4 shows a purely schematic illustration of a device having an integrated connection node in accordance with the invention
- FIG. 5 shows a purely schematic illustration of an Ethernet data frame coming/emanating from a field bus, as it arrives at the field bus port of a connection node or is transmitted by the connection node, and a stream data frame, as it arrives at the stream port of a connection node or is transmitted by the connection node in accordance with the invention
- FIG. 6 shows a purely schematic illustration of the data transmitted in a field bus in accordance with the invention
- FIG. 7 shows a purely schematic illustration of a TSN network which connects three field buses to one another in accordance with the invention
- FIG. 8 shows a purely schematic illustration of a TSN network which connects two field bus segments and an individual field device to one another in accordance with the invention
- FIG. 9 shows a purely schematic illustration of data arriving at the field bus port of a connection node and a stream data frame leaving the connection node in accordance with the invention.
- FIG. 10 shows a purely schematic illustration of four field bus data frames arriving at the field bus port of a connection node and the associated stream data frame in accordance with the invention
- FIG. 11 shows a purely schematic illustration for forwarding the stream data frames in the TSN network in accordance with the invention
- FIG. 12 shows a purely schematic illustration for forwarding field bus data frames in a network having a higher bandwidth in predefined time windows in accordance with the invention.
- FIG. 13 is a flowchart of the method in accordance with the invention.
- FIG. 1 shows a purely schematic illustration of four devices of an industrial automation system for a technical process not illustrated any further in the figures, which devices are connected to one another, for the purpose of interchanging data with one another, via an Ethernet-based field bus 1 , specifically a PROFINET field bus.
- an Ethernet-based field bus 1 specifically a PROFINET field bus.
- the logical bus based on an Ethernet network not illustrated any further in FIG. 1 is shown.
- the four devices are a programmable logic controller 2 , which is referred to as a PLC below, a display apparatus in the form of a screen 3 , an operator panel 4 and an input/output device, that is to say an I/O device 5 , which comprises one or more sensors and/or actuators of the automation system that are not illustrated in the figure or is connected to such (a) sensor(s) and/or such (an) actuator(s).
- an I/O device 5 which comprises one or more sensors and/or actuators of the automation system that are not illustrated in the figure or is connected to such (a) sensor(s) and/or such (an) actuator(s).
- the one screen 3 , the one operator panel 4 and, in particular, the one I/O device 5 are shown by way of example and many other field devices, in particular I/O devices 5 , are or can be connected to the field bus 1 .
- data are interchanged in a manner known per se between the PLC 2 and the field devices 3 , 4 , 5 .
- measured values captured by sensors are transmitted from the I/O devices 5 to the PLC 2 and control values for actuators of the automation system, which are determined by the PLC inter alia based on the measured values, are transmitted from the PLC 2 to I/O devices 5 .
- Data are also transmitted from the PLC 2 to the screen 3 in order to be visualized there for a user, and data which represent user commands, in particular, are transmitted from the operator panel 4 to the PLC 2 .
- FIG. 2 shows the PLC 2 , the screen 3 , the operator panel 4 and the I/O device 5 , where the field bus 1 has been subdivided into two segments 1 a , 1 b and the two field bus segments 1 a , 1 b are connected to one another via a TSN network 6 .
- the TSN network 6 is schematically indicated via a cloud in FIG. 2 , as are the field bus segment networks.
- two streams 7 , 8 for fast, secure data transmission with a guaranteed quality, in particular latency have been configured in the TSN network 6 between devices 2 , 3 on one field bus segment 1 a and devices 4 , 5 on the other field bus segment 1 b.
- Resources have been reserved for each of the two streams 7 , 8 for the purpose of configuring the streams at a plurality of nodes, switches of the TSN network 6 in the present case.
- the two streams 7 , 8 have been configured in an automated manner by resorting to configuration data relating to the field bus 1 . All parameters needed to configure the streams 6 , 7 are available in the engineering of the field bus 1 anyway, specifically in the TIA portal, and can be easily used. The packet size, number of packets, the resulting bandwidth, the update cycle, the transmission interval and the latency are mentioned as examples of these parameters.
- Data frames that come (emanate) from the PLC 2 and/or data frames that come (emanate) from the screen 3 are transmitted in the direction of the field bus segment 1 b via the stream 7
- data frames that come (emanate) from the operator panel 4 and/or data frames that come (emanate) from the I/O device 5 are transmitted in the direction of the field bus segment 1 a via the stream 8 .
- connection nodes 9 , 10 are provided in the present case.
- Each of the two field bus segments 1 a , 1 b is connected to the TSN network 6 via a connection node 9 , 10 in each case, specifically the segment 1 a via the connection node 9 and the segment 1 b via the connection node 10 .
- connection nodes 9 , 10 are in the form of two-port devices and have a field bus port 11 in the direction of the respective field bus segment 1 a , 1 b and a stream port 12 in the direction of the TSN network 6 .
- the ports 11 , 12 can be gathered from FIG. 3 that shows, by way of example, an enlarged, purely schematic illustration of a connection node 9 , 10 in the form of a two-port device.
- FIG. 2 shows only the field bus ports 11 , but not the stream ports 12 in the direction of the TSN network 6 .
- connection node 9 , 10 can also be directly integrated in a device 2 , 3 , 4 , 5 , which then can be directly connected to the TSN network 6 .
- This alternative configuration is illustrated in a purely schematic manner in FIG. 4 .
- the device 2 , 3 , 4 , 5 then has a stream port 12 , via which it can be connected to a TSN network 6 .
- This configuration can be used, in particular, in that situation in which two field bus segments 1 a , 1 b are not connected to one another via a stream, but rather a field bus 1 or a field bus segment 1 a , 1 b , for example, is connected to a device 2 , 3 , 4 , 5 which is not on a field bus 1 .
- connection nodes 9 , 10 which configuration makes it possible to convert field bus data frames into stream data frames and to convert stream data frames into field bus data frames; specifically, an accordingly configured PRU which is not illustrated in the figures is integrated in each of the two connection nodes 9 , 10 and manipulates the packets in a targeted manner via its program and adds or removes the required identification of the data frames (cf. FIG. 5 ).
- connection nodes 9 , 10 are configured to prefix a header 14 containing stream parameters, specifically a designated stream address 15 , a source address 16 , a VLAN ID 17 and a priority 18 , to Ethernet data frames 13 which are transmitted by devices 2 , 3 , 4 , 5 from the respective field bus segment 1 a , 1 b and arrive at the field bus port 11 of the respective connection node 9 , 10 and to forward them via the respective stream port 12 .
- the Ethernet frame 13 with the prefixed stream header 14 forms a TSN stream data frame 19 , as illustrated in the right-hand half of FIG. 5 .
- the Ethernet data frame 13 in turn comprises, in a manner prefixed to said data, a designated address 21 , a source address 22 , an Ethertype 23 and, after the useful data 20 , a CRC 24.
- connection nodes 9 , 10 provide a new CRC 25. Both connection nodes 9 , 10 are configured to prefix stream parameters to data frames that are transmitted by devices 2 , 3 , 4 , 5 from the respective field bus segment 1 a , 1 b and arrive at the field bus port of the respective connection node 9 , 10 and to remove stream parameters from data frames that arrive at the stream port.
- connection nodes 9 , 10 are also both configured to remove the stream header 14 containing the designated stream address 15 , the source address 16 , the VLAN ID 17 and the priority 18 from TSN stream data frames 19 that arrive at their stream port 12 via a stream 7 , 8 and to forward data frames 13 without the removed parameters, i.e., Ethernet data frames 13 , to the respective field bus segment 1 a , 1 b via the field bus port 11 .
- connection node 9 , 10 is illustrated by way of example between the field bus data frame 13 and the stream data frame 19 in FIG. 5 , and arrows 26 are used to indicate that the data frames 13 , 19 are accordingly manipulated for both communication directions.
- the Stream Reservation Protocol which is standardized as IEEE 802.1Qat, was specifically resorted to for the reservation for both directions.
- the data to be transmitted are protected from an excessive effect from other real-time applications and/or other applications in the network by virtue of the reservation.
- Other applications have only a slight but accurately known effect on the transmission time, in particular.
- real-time data are not lost.
- data are transmitted via Ethernet.
- data are transmitted specifically from the respective device 2 , 3 , 4 , 5 to a field bus switch 27 of the respective field bus segment 1 a , 1 b and from the respective field bus segment 1 a , 1 b to the respective connection node 9 , 10 assigned to the field bus segment 1 a , 1 b.
- FIG. 2 indicates, in a purely schematic manner, the use of the bandwidth for the TSN network, on the one hand, and for the field bus network, on the other hand, via “speech bubbles” adjoining the TSN network 6 and the network of the field bus segment 1 b.
- a link bandwidth B link a bandwidth B 50% , which corresponds to half of the link bandwidth, and an actually used bandwidth By below B 50% are depicted for the field bus network (right-hand “speech bubble”).
- a bandwidth of 100 Mbit/s is available and is permanently divided into a half B 50% (50 Mbit/s) for real-time data and a further half (generally 50 Mbit/s) for other traffic.
- the situation is such that a maximum class bandwidth BK max is available and there is a stream bandwidth B stream that is below the class bandwidth.
- the stream bandwidth may have been taken, in particular, either from the configuration of the field bus 1 , in particular the TIA configuration, for example may be 10 Mbit/s, or can be defined as a standard value of 50 Mbit/s by the system definition, in particular in the case of PROFINET.
- a plurality of field buses 1 may also be located in a TSN network 6 and streams 7 , 8 may have been configured for the plurality of field buses 1 in the TSN network 6 .
- a constellation for more than one field bus 1 is shown by way of example and in a purely schematic manner in FIG. 6 . Identical components are provided with identical reference numerals therein. It should be noted that the field bus segments 1 a , 1 b are not illustrated in FIG. 6 , but rather only three pairs of connection nodes 9 , 10 between which two streams 7 , 8 have been respectively configured in opposite directions for a respective field bus 1 having field bus segments 1 a , 1 b connected via the streams. For each individual field bus of the three field buses 1 each with two segments 1 a , 1 b , it is the case that the arrangement is like that in FIG. 2 .
- the network path for the horizontally hatched pair of connection nodes 9 , 10 and for the vertically hatched pair of connection nodes 9 , 10 is the same; specifically, the streams 7 , 8 for both pairs of connection nodes and therefore associated field buses 1 run via the same two TSN switches 28 of the TSN network 6 .
- the streams 7 , 8 of the third field bus 1 also pass via the left-hand switch of these two TSN switches 28 . Reservations for all six streams 7 , 8 are therefore present at this TSN switch 28 which is at the bottom left in FIG. 6 , reservations for four streams 7 , 8 are present at the TSN switch 28 at the bottom right and reservations only for two streams 7 , 8 are present at the upper switch 28 .
- TSN network 6 may comprise any other desired number of switches 28 and the reservations may also be different.
- a field bus segment may also be formed by an individual device 2 , 3 , 4 , 5 assigned to the field bus 1 . It is therefore also possible for two or more field bus segments 1 a , 1 b and further devices 2 , 3 , 4 , 5 to be connected via a TSN network 6 and for streams 7 , 8 to be able to be configured in said network.
- a constellation in which two field bus segments 1 a , 1 b and a further field bus device 3 are connected via the TSN network 6 and communicate via the TSN network 6 is illustrated purely by way of example and in a schematic manner in FIGS. 7 and 8 . Identical reference signs have again been used in these figures.
- connection nodes 9 , 10 , 29 are provided for the field bus 1 and three streams 7 , 8 , 30 are configured in the TSN network 6 .
- FIG. 7 shows only the connection nodes 9 , 10 , 29 and streams 7 , 8 , 30 for the three field buses 1 , one of which has three field bus segments 1 a , 1 b , 1 c connected via the TSN network 6 and to which three connection nodes 9 , 10 , 29 are therefore assigned and for which three streams 7 , 8 , 30 have been configured.
- FIG. 8 shows the situation of only one field bus 1 from FIG. 7 , specifically the field bus 1 with three segments 1 a , 1 b , 1 c , where the third field bus segment 1 c is formed by an individual device, specifically a screen 3 .
- a stream 7 , 8 , 30 leaves from each field bus segment 1 a , 1 b , 1 c and is used to respectively transmit data to the two other field bus segments 1 a , 1 b , 1 c (cf. also the arrows in FIG. 7 and FIG. 8 ).
- This is a multiple listener per talker constellation, and the Stream Reservation Protocol (SRP), which supports this, was resorted to for the resource reservation in the exemplary embodiment illustrated.
- SRP Stream Reservation Protocol
- FIG. 9 shows a purely schematic illustration of data 31 that are transmitted in the field bus 1 , in particular to a connection node 9 , 10 , 29 or from such a connection node (indicated by the double-headed arrow 32 ), a connection node 9 , 10 , 29 with a field bus port 11 to the right of the data 30 and a stream data frame 19 with a stream header 14 and a useful data region or “payload” 13 and a CRC 25 again to the right of said connection node.
- the connection of the connection node 9 , 10 , 29 to the TSN network 6 is also schematically indicated in FIG. 6 via a cloud.
- FIGS. 10 and 11 illustrate the frame forwarding in more detail, where FIG. 10 schematically illustrates four field bus data frames arriving in succession at a connection node 9 , 10 , 29 against the time t.
- the field bus data frames are denoted FD 0 , FD 1 , FD 2 and FD 3 in FIG. 10 .
- the field bus data frames FD 0 , FD 1 , FD 2 , FD 3 can arrive with the maximum possible bandwidth.
- stream data frames (which are given by the field bus data frames “packed” in a stream-enabled manner) which are denoted SD 0 , SD 1 , SD 2 and SD 3 .
- a preceding stream data frame is indicated to the left of the first stream data frame SD 0 using a dashed line. It is seen that the stream data frames SD 0 , SD 1 , SD 2 , SD 3 have a shorter extent in the direction of the time axis 34 , which can be attributed to the higher bandwidth in the TSN network 6 in comparison with the field bus network.
- the stream data frames SD 0 , SD 1 , SD 2 , SD 3 can be transmitted with the higher bandwidth.
- FIG. 11 again illustrates the four stream data frames SD 0 , SD 1 , SD 2 , SD 3 , in which case it is outlined underneath that the forwarding is carried out in such a manner that a break P 0 , P 1 , P 2 , P 3 is made after the transmission of each stream data frame SD 0 , SD 1 , SD 2 , SD 3 , the length of which break depends on the transmitted volume of data, which is indicated in the FIG as the size G 0 , G 1 , G 2 , G 3 of the respective stream data frame SD 0 , SD 1 , SD 2 , SD 3 , and the bandwidth which is reserved for the respective stream 7 , 8 , 30 .
- the break following each data frame SD 0 , SD 1 , SD 2 , SD 3 is three times as long as the transmission time for the frame SD 0 , SD 1 , SD 2 , SD 3 .
- the larger the respective stream data frame SD 0 , SD 1 , SD 2 , SD 3 the longer the break P 0 , P 1 , P 2 , P 3 as well. Compliance with the bandwidth is guaranteed using the respective break. If the bandwidth was previously complied with, then the next frame SD 0 , SD 1 , SD 2 , SD 3 can always be transmitted directly when it arrives.
- This procedure corresponds to the AVB or TSN model with reserved traffic for streams using the CBS (Credit Based Shaper) mechanism (IEEE 802.1Qav).
- CBS Cell Based Shaper
- IEEE 802.1Qav Network resources, inter alia the bandwidth, are reserved for the streams.
- the “credit” is indicated in FIG. 11 below the respective stream SD 0 , SD 1 , SD 2 , SD 3 using the “jagged” line, which credit must “recover” to zero again from the negative range during the break after the transmission of a frame SD 0 , SD 1 , SD 2 , SD 3 so that the next frame SD 0 , SD 1 , SD 2 , SD 3 can be transmitted.
- FIG. 12 An alternative for transmitting field bus data frames FD 0 , FD 1 , FD 2 , FD 3 in a network with a higher bandwidth, which is known to the applicant and does not provide these advantages, is illustrated (again in a purely schematic manner) in FIG. 12 .
- FIG. 12 shows four field bus data frames FD 0 , FD 1 , FD 2 , FD 3 in a field bus network with a lower bandwidth and underneath in a network with a higher bandwidth.
- the field bus data frames FD 0 , FD 1 , FD 2 , FD 3 are not, as described with reference to FIG. 11 , transmitted via streams with resources secured via reservations, but rather a fixed time window F for transmitting the frames FD 0 , FD 1 , FD 2 , FD 3 is provided in each network cycle 35 .
- FIG. 13 is a flowchart of the method for communicating data in a network.
- the method comprises transmitting data between a plurality of devices 2 , 3 , 4 , 5 , as indicated in step 1310 .
- at least one device of the plurality of devices 2 , 3 , 4 , 5 is on a field bus 1 .
- the data at least is transmitted in sections via either an Audio Video Bridging (AVB) and/or a Time Sensitive Networking (TSN) network 6 in which at least one stream 7 , 8 , 30 has been or is configured for the field bus 1 , as indicated in step 1320 .
- AVB Audio Video Bridging
- TSN Time Sensitive Networking
- resources have been and/or are reserved for the at least one stream 7 , 8 , 30 at at least one connection node 9 , 10 , 29 of the network 6 .
- data frames 13 that either emanate from at least one device on the field bus and/or are intended for at least one device on the field bus are transmitted via the at least one stream 7 , 8 , 30 , as indicated in step 1330 .
- the or each field bus 1 are connected to either the AVB and/or the TSN network 6 via the at least one connection node 9 , 10 , 29 , as indicated in step 1340 .
- the at least one connection node 9 , 10 , 29 includes a field bus port 12 in a direction of a respective field bus 1 and a stream port ( 12 ) in the direction of either the AVB and/or the TSN network 6 and the at least one connection node 9 , 10 , 29 is configured to assign at least one stream parameter comprising either a designated stream address 15 , a VLAN ID 17 and/or a priority 18 to data frames 13 that arrive at the field bus port 11 and to remove at least one stream parameter comprising either the designated stream address 15 , the VLAN ID and/or the priority 18 from data frames 19 that arrive at the stream port 12 .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computing Systems (AREA)
- General Business, Economics & Management (AREA)
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Automation & Control Theory (AREA)
- Quality & Reliability (AREA)
- Manufacturing & Machinery (AREA)
- General Engineering & Computer Science (AREA)
- Cardiology (AREA)
- Environmental & Geological Engineering (AREA)
- Small-Scale Networks (AREA)
- Programmable Controllers (AREA)
Abstract
Description
- This is a U.S. national stage of application No. PCT/EP2019/051506 filed 22 Jan. 2019. Priority is claimed on European Application Nos. 18154319 filed 31 Jan. 2018 and Ser. No. 18/184,095 filed 18 Jul. 2018, the contents of which are incorporated herein by reference in their entirety.
- The invention relates to a control method, an apparatus, a computer program, a computer-readable medium and a method for communicating data in a network, in particular an industrial network, in which data are transmitted between at least two devices, at least one device of which is on a field bus.
- In industrial automation, special control systems, in particular programmable logic controllers (PLCs), are used to control or regulate machines, systems or industrial processes, for example, in an automated manner. A PLC is generally connected to the machine, the system or a process via sensors providing a plurality of input values and actuators receiving a plurality of control values.
- Pressure and temperature sensors, incremental encoders and filling level sensors are mentioned purely by way of example for sensors. Actuators may be, for example, in the form of contactors, electric valves and modules for drive controllers. The sensors and actuators are arranged close to the process(es) to be automated in order to capture the required measured values at the relevant locations and to be able to act on the process at required locations. The position of the actuators is also determined by the structure of the machine or system.
- During operation, the control system receives measured values captured by the sensors from the latter, calculates (inter alia) control values for the actuators based on the measured values and transmits the control values to the actuators. In order to avoid having to lay a separate cable to the control system for each sensor and/or actuator, communication networks, “field buses”, have been developed.
- Standards relating to field buses for industrial applications are, for example, International Electrotechnical Commission (IEC) 61158, IEC 61784-1 to IEC 61784-5.
- This started with simple bus systems. A simple bus system is generally distinguished by the fact that the individual devices connected to it are connected to one another via a bus line. In this case, a bus network has typically been laid from the control system, in particular the PLC, to all sensors and actuators which constitute field devices. Further devices, for example, operating and/or display devices, can also be connected to the control system via a field bus to transmit data from or for the devices. PROFIBUS is mentioned as an example of such a physical bus system.
- Nowadays, many field buses are based on Ethernet (for Ethernet, see Institute of Electrical and Electronics Engineers (IEEE) standard 802, in particular IEEE 802.3), as is the case with PROFINET RT, for example. If necessary, proprietary expansions are provided to achieve a desired performance/quality in the transmission. However, the entire logical basic concept with a bus between the controller and the sensors/actuators has remained in the engineering. The communication network in the form of the field bus and based on Ethernet is still considered to be a single logical cable (bus network). The available bandwidth (generally 100 Mbit/s) is usually permanently divided into a half (generally 50 Mbit/s) for real-time data and a further half (generally 50 Mbit/s) for other traffic. Compliance with the bandwidth must then be ensured by the design of the real-time application. Network devices detect the real-time data based on proprietary expansions or by using special addresses and assign these to the corresponding resources.
- The previous conventional field buses therefore cannot be integrated into new, standardized Ethernet networks without any problems. In particular, as a result of the known Audio Video Bridging (AVB) and Time Sensitive Networking (TSN) expansions, the networks would be powerful enough, however, to comply with the requirements, in particular those imposed on real-time data transmission.
- In particular, the use of a plurality of field buses in an Ethernet network is problematic.
- Industrial field buses (for example PROFINET) have hitherto been designed for 100 Mbit/s Ethernet networks. The applicant is aware that a bus topology is assumed for the entire Ethernet network during project planning. It is also assumed during design that all resources in the network can be used exclusively. If one of these assumptions does not apply, then resource planning must be performed manually, which is associated with considerable effort and requires extensive experience. To the applicant's knowledge, there has previously been no mechanism that compares the planning with reality and monitors the planned limits and reacts in the event of a violation. As a result, the entire network can fail. Protection during operation is not possible because the resource planning in the network is not known.
- Increasingly higher bandwidths are available as a result of the further development of Ethernet. However, the field buses are typically designed only for 100 Mbit/s networks. The higher bandwidths result in the desire to use a plurality of field bus systems in an Ethernet network. However, there is no protection of a logical field bus without adapting the individual systems. All real-time applications share the resources equally.
- Within the scope of IEEE standardization, the Ethernet technology (see IEEE 802) was expanded with mechanisms for achieving a guaranteed QoS (“Quality of Service”) in the AVB (Audio Video Bridging) working group. Here, a new type of traffic was defined, the “streams”, which can be used to guarantee quality (QoS) in a network. A stream according to these standards is a protected, unidirectional communication connection from a device, which is also referred to as a talker and forms a data source, to one or more devices, which are also referred to as listeners and constitute the data sinks, i.e., receivers.
- Time Sensitive Networking (TSN) denotes a series of standards that expands the bridging standard IEEE 802.1Q with mechanisms for transmitting real-time-critical data via Ethernet networks. The standards mentioned include, for example, time synchronization (IEEE 802.1As-Rev), frame pre-emption (IEEE 802.1Qbu) and reservation (IEEE 802.1Qca, IEEE 802.1Qcc) as well as other standards.
- Before the data are actually transmitted via a stream, a registration and a reservation are performed to obtain guarantees of a loss-free real-time transfer of data frames and a punctual delivery from the network. For a stream, a reservation is performed, in particular, via a stream reservation protocol (SRP). Each stream has its own address in order to monitor forwarding.
- “Multiple listeners per stream” was introduced in AVB in order to reduce the number of real-time data flows from a source (talker) to a plurality of destinations (listeners). Specifically, it is possible to transmit data from one talker to a plurality of listeners using only one stream. The European patent application which traces back to the applicant and has the
file reference EP 18 15 4319 also discloses a stream reservation model which enables “multiple talkers per listener”, specifically the transmission of data from a plurality of talkers to one listener using only one stream. - US 2013/070788 A1 discloses a method for interchanging data between two devices of a network, which uses a communication protocol with an interface according to the OPC-UA standard to interchange the data. Here, the communication protocol comprises an interface according to the Stream Reservation Protocol (SRP) standard or Multiple Stream Registration Protocol (MSRP) standard according to IEEE 802.1Qat, with the result that the data can be interchanged between the two devices via both interfaces in a predefined period of time.
- US 2017331719A1 relates to a method for configuring a communication path, which is performed in a first communication node of a vehicle network. The method comprises receiving a first frame that requests the configuration of a communication path that is used to transmit a data stream. The method also comprises configuring a directory of the first communication node based on an item of information in the first frame if a second frame having a data stream identifier identical to a data stream identifier of the first frame is not received. The method also comprises incrementing a hop number of the first frame and transmitting the first frame which has the incremented hop number.
- It is an object of the present invention to provide a method for communicating data, in particular, between components or devices of an industrial automation application, where the method enables reliable real-time communication, can be performed with a reasonable amount of effort at the same time and also enables, in particular, the further use of existing concepts of field bus technology.
- This and other objects and advantages are achieved in accordance with the invention by a method for communicating data in a network, in particular an industrial network, in which data are transmitted between at least two devices, at least one device of which is on a field bus, where the data are transmitted at least in sections via an AVB or TSN network in which at least one stream has been or is configured for the field bus, where resources have been and/or are reserved for the at least one stream at one or more nodes, in particular switches and/or bridges, of the network, and data frames that come (emanate) from at least one device on the field bus and/or are intended for at least one device on the field bus are transmitted via the at least one stream.
- The invention also provides for the or each field bus to be connected to the AVB or TSN network via at least one connection node, where the at least one connection node has a field bus port in the direction of the respective field bus and a stream port in the direction of the AVB or TSN network, and the at least one connection node is configured to assign, in particular prefix, at least one stream parameter, in particular a designated stream address and/or a VLAN ID and/or a priority, to data frames that arrive at the field bus port and to remove at least one stream parameter, in particular a designated stream address and/or a VLAN ID and/or a priority, from data frames that arrive at the stream port.
- The at least two devices are preferably devices/components of an industrial automation application, such as field devices and/or control devices, where a control device may be, in particular, formed as a programmable logic controller (PLC). Field devices may be, for example, in the form of I/O devices, which comprise one or more sensors and/or actuators, or are assigned thereto or are connected thereto.
- In other words, the invention is based on the concept of using the new standardized Ethernet mechanisms to map one or more logical field buses (in particular as an entire system) to a communication path in an Ethernet network. This makes it possible, in particular, to continue to use existing concepts of field bus technology. Existing devices can continue to be used together with the new standards, in particular AVB or its expansion TSN. In this case, not all existing devices, for instance sensors and/or actuators, are preferably individually connected to the AVB or TSN network, but rather a plurality of devices remain on an existing field bus or a part/segment of an existing field bus, in particular, and are connected to one or more further field bus devices, which are on at least one further field bus part or segment, via the AVB or TSN network and via (a) stream(s).
- The field bus or (if there are a plurality) the field buses may be physical field buses (for example, PROFIBUS) and/or logical field buses (for example, PROFINET) based on an Ethernet network without an AVB or TSN expansion.
- Within the respective field bus or part/segment of the field bus, the devices or components can still communicate in accordance with the existing standard belonging to the field bus. In the case of a PROFINET field bus, Ethernet data frames (according to IEEE 802, in particular IEEE 802.3) are still transmitted within the field bus, for instance, without an AVB or TSN expansion, i.e., not via a stream. Physical field buses, such as PROFIBUS, include other codings for the data frames which can likewise still be used within the (respective) field bus or (respective) field bus segment. The field bus devices therefore need not be changed for the AVB or TSN network which complies with the new standards.
- In accordance with the invention, at least one stream, i.e., a protected connection with secure, reserved resources and, in particular, a defined latency, is configured in the AVB or TSN network. The AVB or TSN network is accordingly a network which supports the configuration of streams by means of resource reservation.
- All parameters needed to configure the stream(s) are generally present in the engineering of a field bus anyway, in particular in the TIA portal, and can be used in a simple manner. The packet size, number of packets, the bandwidth, the update cycle, the transmission interval and the latency are mentioned as examples of these parameters.
- In particular, the (respective) logical field bus is already contained in the engineering programs for configuring the subscribers. In the case of PROFINET, for example, this can be performed in the TIA portal. The logical connection of planned assemblies in the hardware configurator produces a logical field bus. In order to configure general network parameters, the logical bus system usually has a name and, for internal use, a unique ID (for example, a Universally Unique Identifier (UUID)). If necessary, the data rate of the physical bus or of the underlying Ethernet network (without an AVB or TSN expansion), which represents the logical bus, can be adjusted, for example. Data frames of the respective field bus can be assigned to one or more streams using the name or the unique ID. As a result, it is possible to adapt or configure the stream used as the “tunnel” in the AVB or TSN Ethernet network, which is used by the present invention. Associated field bus segments or field bus devices can also be identified using a field bus name and/or an associated unique ID.
- In particular, the latency requirement of very time-critical applications, for example, can also be complied with in the field buses by using pre-emption (IEEE 802.1Qbu) in a TSN network. At 100 Mbit/s, for example, the time needed to transmit a frame with the maximum volume of data would be approximately 125 microseconds, which is already greater than a short bus cycle of 64 microseconds.
- AVB and TSN technology is available in comparatively inexpensive network components, in particular as a result of the use which has already been effected in the automotive sector and/or the origin of AVB (Audio Video Bridging) from home networks. As a result of the use in accordance with the invention of comparatively cost-effective and standardized AVB or TSN mechanisms (streams), it is possible to dispense with other mechanisms for tunneling a data transmission in Ethernet networks, for instance VXLAN, Mac-in-Mac, SPB-V, which have hitherto been available only in more expensive hardware components and also do not provide any resource protection.
- The use in accordance with the invention of one or more streams results in a robust, guaranteed transmission with secure resources and guarantees the compliance with a required latency for real-time applications. The data to be transmitted are protected from an excessive effect from other real-time applications and/or other applications in the network by virtue of the reservation. Other applications then have only a slight but accurately known effect on the transmission time, in particular. As a result of the resource reservation, real-time data are not lost.
- In order to be able to connect Ethernet devices that are in a field bus, i.e., are integrated in a field bus, in a transparent manner, the packet selection can be limited to the packets belonging to the (respective) field bus. This recognition can be performed, for example, by resorting to the Ethertype. In this case, the Ethertype is a defined part of an Ethernet data frame and defines the protocol that transmits the data and processes them at the destination after reception. In the case of PROFINET RT for example, the Ethertype is 0x8892.
- The at least one stream is preferably configured in an automated manner for the or each field bus.
- In order to obtain one or more protected connections, i.e., one or more streams, resources are reserved in a manner known per se before the actual transmission of the data at one or more nodes of the network, which is preferably performed using a reservation protocol. Using a reservation protocol for the real-time flow makes it possible to perform the complex configuration automatically in the network, in which case the topology present in each case is used.
- Resources that have been and/or are reserved may be, for example, address table entries, frame buffers, transmit time slices, bandwidth, jitter, latency etc.
- In one preferred embodiment, address table entries and/or frame buffers and/or bandwidth have been and/or are reserved as resources for the at least one stream at one or more nodes of the network. At least one address table entry and a frame buffer and bandwidth have been and/or are particularly preferably reserved at at least one node.
- Data frames can be assigned to a tunnel or stream at the end points on the basis of the protocol. In the case of PROFINET, for example, the frame ID, i.e., the ID within the Ethernet data frames, can also be additionally used. This makes it possible to select a separate tunnel, i.e., a stream, for each service of a field bus, in particular a PROFINET service.
- The stream(s) can be automatically configured in a simple manner, in particular by using a reservation protocol and/or resorting to parameters from existing field bus engineering, in particular a TIA portal, which facilitates handling and enables use by users even without special IT knowledge.
- Within the scope of the method in accordance with the invention, one or more streams can be used to transmit data between two or more devices within a field bus and/or to transmit data between devices that are on two or more different field buses, i.e., between two or more field buses, and/or to transmit data between devices, at least one of which is on a field bus and at least one of which is not on a field bus.
- One or more streams are configured in an AVB or TSN network. In this case, an AVB or TSN network should be understood as meaning a network that complies with one or more Audio Video Bridging (AVB) or Time Sensitive Networking (TSN) standards, in particular comprises one or more AVB-enabled or TSN-enabled nodes, such as switches and/or bridges. The network or the nodes is/are configured, in particular, to comply with one or more AVB or TSN standards. The AVB standards include, in particular, IEEE 802.1AS, IEEE 802.1Qat, IEEE 802.1Qav, IEEE 802.1BA, and the TSN standards include, for example, time synchronization (IEEE 802.1AS-Rev), frame pre-emption (IEEE 802.1Qbu) and reservation (IEEE 802.1Qca, IEEE 802.1Qcc) as well as other standards.
- The method in accordance with the invention provides a plurality of advantages. On the one hand, field buses can still exist as logical field buses. The user can consider communication to be a bus, as before, and can logically connect the devices to one another.
- Transmission in the AVB or TSN Ethernet network is protected via the stream(s) and can no longer be disrupted by other applications. In addition, it is not necessary to change the terminals. Rather, existing terminals or systems, in particular of an industrial automation application, can still be used without any problems. At the same time, it is possible to resort to the new, standardized Ethernet mechanisms of AVB or TSN.
- As a result of the method in accordance with the invention, the field bus(es) also become visible as a connection in the AVB or TSN network through the reservation of at least one stream, which also makes it possible to diagnose faults and resource bottlenecks in the AVB or TSN network in a very simple manner. In particular, the logical field bus(es) become(s) visible in the diagnosis of the AVB or TSN network in the form of at least one stream, preferably in the form of precisely two streams for bidirectional communication. Each stream, in particular each transmission direction of the tunneled communication (logical bus), can then be discerned in the network management with the resources used. For example, bridges with an insufficient number of FDB entries can thus be recognized in the AVB or TSN network. This diagnosis for streams is part of the SRP reservation protocol (in IEEE 802.1Q).
- The transmission of data frames via the at least one stream is, in particular, such that compliance with the bandwidth is guaranteed by means of a shaper, in particular in accordance with IEEE 802.1. As a result of the guaranteed compliance with the bandwidth, a maximum latency can be guaranteed on the way at each node, for instance, each bridge. A break is made, for example, during the transmission or forwarding of each data frame, in an AVB or TSN stream via the Credit Based Shaper (CBS) in accordance with IEEE 802.1Qav, the length of which break depends on the size of the data frame and the reserved bandwidth. In this case, the longer the break, the larger the data frame transmitted or forwarded before the break, i.e., the greater the forwarded or transmitted volume of data. The relationship is linear, in particular, in this case. The length of the break corresponds, in particular, to the length of the time needed to transmit the respective data frame multiplied by a factor dependent on the reserved bandwidth. If, for example, 25% of the bandwidth is reserved for a stream, then a break is made, in particular, after each data frame, which break is three times as long as the time needed to transmit it. If 50% is reserved, then the break is as long as the transmission time and so on. The factor for the length of the break is known based on the reservation and is permanently configured. This procedure guarantees that the bandwidth is complied with. Frames that arrive at a node, in particular a bridge or a switch, of the AVB or TSN network, can always be immediately forwarded.
- Provision is particularly preferably made for at least one stream to have been or to be configured between two segments of a field bus, in which case a plurality of devices are preferably on at least one field bus segment. In the simplest case, a field bus segment may also comprise an individual device or may be given by such a device. This means that data can also be interchanged, for example, between a field bus segment, on which two or more devices are present, and an individual field bus device via a stream.
- In a further preferred embodiment of the method in accordance with the invention, two or more field buses, on which there is at least one device in each case, are provided, and at least one stream assigned to the respective field bus has been or is configured for each field bus in the AVB or TSN network, where resources have been and/or are reserved for each stream at one or more nodes, in particular switches and/or bridges, of the network, and data frames which come (emanate) from at least one device on the respective field bus and/or are intended for at least one device on the respective field bus are transmitted via the respective at least one stream in the AVB or TSN network.
- If the bandwidth of the AVB or TSN network allows, for example, if a gigabit network is available, then a plurality of logical field buses can also be combined in the network, for each of which 50 Mbit/s, for example, is then assumed as the maximum bandwidth for a real-time data transmission. Within the scope of the method in accordance with the invention, a plurality of field buses can therefore also be connected via a network. Secure resources then exist for each field bus in the faster AVB-based or TSN-based network by virtue of streams. The reservation can be performed, for example, based on the maximum physical field bus speed in the TSN backbone network. A low latency can be achieved via a faster link speed and it is optionally possible to resort to pre-emption for real-time applications, in particular with a comparatively short cycle, for example below 250 microseconds.
- At least two streams are particularly preferably configured for the or each field bus and, in particular, data frames are transmitted in the direction of the respective field bus via at least one stream and data frames that come (emanate) from the respective field bus are transmitted via at least one further stream. The entire data transmission can then be performed in both directions, in particular, using two or more streams for which resources have been or are reserved at one or more nodes on the stream network path, in particular switches and/or bridges.
- It is possible to recognize whether at least one stream is available for one direction and/or at least one stream is available for the other direction, in particular, from the fact that there is at least one stream ID (for each direction).
- Within the scope of the method in accordance with the invention, data frames that comprise, as useful data, measured values captured by sensors of an automation system or data representing said measured values and/or actuating values intended for actuators of an automation system or data representing the actuating values are transmitted via a stream, in particular. Alternatively or additionally, data for configuring the network and one or more devices on a field bus, in particular sensors and/or actuators, and/or data for periodically monitoring one or more devices on a field bus are transmitted.
- In a further preferred embodiment of the method in accordance with the invention, the at least one stream is or has been configured for the or each field bus by resorting to configuration data relating to the (respective) field bus, in particular configuration data relating to the TIA portal of the (respective) field bus. The configuration data which are generally present in the engineering of a field bus anyway can be used in a simple manner. The packet size, number of packets, the bandwidth, the update cycle, the transmission interval and the latency are mentioned as examples of these parameters.
- Data between one or more devices on the respective field bus or field bus segment and the or each connection node can be transmitted according to the existing field bus standard, for example, via Ethernet without an AVB or TSN expansion (in particular according to IEEE 802.3) in the case of PROFINET.
- Provision may also be made for the or each field bus to be connected to the AVB or TSN network via at least two connection nodes, and for each connection node to have a field bus port in the direction of the respective field bus and a stream port in the direction of the AVB or TSN network, and for each connection node to be configured to assign, in particular prefix, at least one stream parameter, in particular a designated stream address and/or a VLAN ID and/or a priority, to data frames which arrive at the field bus port and/or to remove at least one stream parameter, in particular a designated stream address and/or a VLAN ID and/or a priority, from data frames which arrive at the stream port.
- A logical configuration is preferably provided in the connection node(s) and makes it possible to connect the field bus to the (respective) stream; for example, a PRU is integrated in the respective connection node. A PRU is a programmable function in a device having at least two ports, which function can manipulate received frames or frames to be transmitted before further internal processing or transmission, depending on the program, and can add, change and/or remove contents. The program of the PRU can ensure that all arriving frames that must be transmitted via a tunnel can be recognized as a stream in the superordinate AVB or TSN network. Data frames of an AVB or TSN stream can be recognized, in particular, via the destination address used and/or the VLAN ID and/or VLAN priority.
- At least one stream parameter is preferably provided by the or each connection node in a header of data frames from the field bus which arrive at the field bus port, or a (stream) header having one or more stream parameters is prefixed to the respective data frame.
- The or each connection node practically forms a connector between the (respective) field bus (network) and the AVB or TSN network in which at least one stream has been or is configured, or a network path belonging to the (respective) stream which can also be referred to as a stream network path. The at least one connection node undertakes the function of a proxy, in particular, and/or (respectively) forms an end point of the (respective) stream. The connection node(s) is/are preferably a two-port or multiport device that has at least one port in the field bus and has at least one further port in the direction of the stream network path.
- The use of connection nodes makes it possible to smoothly convert field bus data frames, which may be, for example, in the form of Ethernet (without AVB or TSN expansion) frames or data frames with another coding, into stream-enabled data frames, in particular with a designated stream address and/or a VLAN tag, in particular a VLAN ID and/or a priority, and/or other stream parameters that are generally in a frame header, and vice versa. The respective stream data frame then comprises, in particular, the header and useful data that follow the header and are also referred to as “payload”. The “payload” of the stream data frame then corresponds, in particular, to the field bus data frame. In the opposite direction, at least one stream parameter or a header is removed, in particular.
- It may also be the case that at least one connection node or its function is integrated in a device, for instance a control device, for example in the form of a PLC.
- If a plurality of field buses are connected to an AVB or TSN network in the manner in accordance with the invention, at least one connection node is preferably provided for each field bus, and at least two connection nodes are preferably provided for each field bus.
- If one or more connection nodes are provided, they preferably form nodes at which resources have been and/or are reserved for the at least one stream.
- The connection node(s) and/or possibly existing further nodes are preferably in the form of AVB-enabled or TSN-enabled nodes. They may (each) be, for example, an AVB-enabled or TSN-enabled bridge and/or an AVB-enabled or TSN-enabled switch or other AVB-enabled or TSN-enabled devices. The at least one port of the connection node in the direction of the network is preferably an AVB or TSN port.
- In a further embodiment, one or more devices of the or each field bus have been connected to the field bus port of one connection node and one or more further devices of the or each field bus have been connected to the field bus port of the other connection node. It should be understood that the connection of the respective device to the respective field bus port may be direct or indirect (via one or more further components), for example, via one or more field bus nodes, in particular switches and/or bridges, of the respective field bus.
- It is also an object of the invention to provide a control method for an industrial technical process or a vehicle, in which data are interchanged between at least two devices of an automation system while performing the method in accordance with the invention for communicating data, and the industrial technical process or vehicle is controlled based on the interchanged data.
- It is also an object of the invention to provide an apparatus that is configured to perform the method in accordance with the invention for communicating data or the control method according to the invention, in particular comprising one or more preferably AVB-enabled or TSN-enabled nodes, in particular bridges and/or switches, and at least two devices that are preferably parts of an industrial automation system and at least one of which can be placed on a field bus or is on a field bus.
- It is also an object of the invention to provide a computer program comprising program code means for performing the steps of the method in accordance with the invention for communicating data or the control method in accordance with the invention.
- It is a further object of the invention to provide a computer-readable medium comprising instructions which, when executed on at least one computer, cause the at least one computer to perform the steps of the method in accordance with the invention for communicating data or the control method in accordance with the invention.
- The computer-readable medium may be, for example, a CD-ROM or a DVD or a USB or a flash memory. It should be noted that a computer-readable medium should not be solely understood as meaning a physical medium, but rather such a medium may also be available, for example, in the form of a data stream and/or a signal representing a data stream.
- Other objects and features of the present invention will become apparent from the following detailed description considered in conjunction with the accompanying drawings. It is to be understood, however, that the drawings are designed solely for purposes of illustration and not as a definition of the limits of the invention, for which reference should be made to the appended claims. It should be further understood that the drawings are not necessarily drawn to scale and that, unless otherwise indicated, they are merely intended to conceptually illustrate the structures and procedures described herein.
- Further features and advantages of the present invention become clear based on the following description of embodiments of the method of the present invention with reference to the accompanying drawing, in which:
-
FIG. 1 shows a purely schematic illustration of the logical arrangement of an Ethernet-based PROFINET field bus of an industrial automation system in accordance with the invention; -
FIG. 2 shows a purely schematic illustration of a field bus of an industrial automation system, for which two streams have been configured in a TSN network in accordance with the invention; -
FIG. 3 shows a purely schematic illustration of a connection node in the form of a two-port device, for example, with an integrated PRU in accordance with the invention; -
FIG. 4 shows a purely schematic illustration of a device having an integrated connection node in accordance with the invention; -
FIG. 5 shows a purely schematic illustration of an Ethernet data frame coming/emanating from a field bus, as it arrives at the field bus port of a connection node or is transmitted by the connection node, and a stream data frame, as it arrives at the stream port of a connection node or is transmitted by the connection node in accordance with the invention; -
FIG. 6 shows a purely schematic illustration of the data transmitted in a field bus in accordance with the invention; -
FIG. 7 shows a purely schematic illustration of a TSN network which connects three field buses to one another in accordance with the invention; -
FIG. 8 shows a purely schematic illustration of a TSN network which connects two field bus segments and an individual field device to one another in accordance with the invention; -
FIG. 9 shows a purely schematic illustration of data arriving at the field bus port of a connection node and a stream data frame leaving the connection node in accordance with the invention; -
FIG. 10 shows a purely schematic illustration of four field bus data frames arriving at the field bus port of a connection node and the associated stream data frame in accordance with the invention; -
FIG. 11 shows a purely schematic illustration for forwarding the stream data frames in the TSN network in accordance with the invention; -
FIG. 12 shows a purely schematic illustration for forwarding field bus data frames in a network having a higher bandwidth in predefined time windows in accordance with the invention; and -
FIG. 13 is a flowchart of the method in accordance with the invention. -
FIG. 1 shows a purely schematic illustration of four devices of an industrial automation system for a technical process not illustrated any further in the figures, which devices are connected to one another, for the purpose of interchanging data with one another, via an Ethernet-based field bus 1, specifically a PROFINET field bus. Here, the logical bus based on an Ethernet network not illustrated any further inFIG. 1 is shown. - The four devices are a
programmable logic controller 2, which is referred to as a PLC below, a display apparatus in the form of ascreen 3, an operator panel 4 and an input/output device, that is to say an I/O device 5, which comprises one or more sensors and/or actuators of the automation system that are not illustrated in the figure or is connected to such (a) sensor(s) and/or such (an) actuator(s). It should be emphasized that the onescreen 3, the one operator panel 4 and, in particular, the one I/O device 5 are shown by way of example and many other field devices, in particular I/O devices 5, are or can be connected to the field bus 1. - During operation of the automation system which is not shown any further, data are interchanged in a manner known per se between the
PLC 2 and thefield devices O devices 5 to thePLC 2 and control values for actuators of the automation system, which are determined by the PLC inter alia based on the measured values, are transmitted from thePLC 2 to I/O devices 5. Data are also transmitted from thePLC 2 to thescreen 3 in order to be visualized there for a user, and data which represent user commands, in particular, are transmitted from the operator panel 4 to thePLC 2. -
FIG. 2 shows thePLC 2, thescreen 3, the operator panel 4 and the I/O device 5, where the field bus 1 has been subdivided into twosegments 1 a, 1 b and the twofield bus segments 1 a, 1 b are connected to one another via aTSN network 6. TheTSN network 6 is schematically indicated via a cloud inFIG. 2 , as are the field bus segment networks. - In a step of the exemplary embodiment of the method in accordance with the invention for communicating data, as described here, two
streams TSN network 6 betweendevices devices 4, 5 on the otherfield bus segment 1 b. - Resources have been reserved for each of the two
streams TSN network 6 in the present case. - The two
streams streams - Data frames that come (emanate) from the
PLC 2 and/or data frames that come (emanate) from thescreen 3 are transmitted in the direction of thefield bus segment 1 b via thestream 7, and data frames that come (emanate) from the operator panel 4 and/or data frames that come (emanate) from the I/O device 5 are transmitted in the direction of the field bus segment 1 a via thestream 8. - In order to smoothly convert the field bus data frames, which leave the
respective device connection nodes field bus segments 1 a, 1 b is connected to theTSN network 6 via aconnection node connection node 9 and thesegment 1 b via theconnection node 10. - Both
connection nodes field bus port 11 in the direction of the respectivefield bus segment 1 a, 1 b and astream port 12 in the direction of theTSN network 6. Theports FIG. 3 that shows, by way of example, an enlarged, purely schematic illustration of aconnection node FIG. 2 shows only thefield bus ports 11, but not thestream ports 12 in the direction of theTSN network 6. - As an alternative to the exemplary illustrated embodiment, the function of a
connection node device TSN network 6. This alternative configuration is illustrated in a purely schematic manner inFIG. 4 . Thedevice stream port 12, via which it can be connected to aTSN network 6. This configuration can be used, in particular, in that situation in which twofield bus segments 1 a, 1 b are not connected to one another via a stream, but rather a field bus 1 or afield bus segment 1 a, 1 b, for example, is connected to adevice - In the exemplary described embodiment, a logical configuration is provided in the
connection nodes connection nodes FIG. 5 ). - In this case, the
connection nodes header 14 containing stream parameters, specifically a designatedstream address 15, asource address 16, aVLAN ID 17 and apriority 18, to Ethernet data frames 13 which are transmitted bydevices field bus segment 1 a, 1 b and arrive at thefield bus port 11 of therespective connection node respective stream port 12. TheEthernet frame 13 with the prefixedstream header 14 forms a TSNstream data frame 19, as illustrated in the right-hand half ofFIG. 5 . - In addition to the useful data 20 (also referred to as “payload”), the
Ethernet data frame 13 in turn comprises, in a manner prefixed to said data, a designatedaddress 21, asource address 22, anEthertype 23 and, after theuseful data 20, aCRC 24. - The
connection nodes new CRC 25. Bothconnection nodes devices field bus segment 1 a, 1 b and arrive at the field bus port of therespective connection node - The
connection nodes stream header 14 containing the designatedstream address 15, thesource address 16, theVLAN ID 17 and thepriority 18 from TSN stream data frames 19 that arrive at theirstream port 12 via astream field bus segment 1 a, 1 b via thefield bus port 11. - A
connection node bus data frame 13 and thestream data frame 19 inFIG. 5 , andarrows 26 are used to indicate that the data frames 13, 19 are accordingly manipulated for both communication directions. - It should be noted that resources have been reserved for the two
streams connection nodes - In the exemplary illustrated embodiment, the Stream Reservation Protocol (SRP), which is standardized as IEEE 802.1Qat, was specifically resorted to for the reservation for both directions.
- The data to be transmitted are protected from an excessive effect from other real-time applications and/or other applications in the network by virtue of the reservation. Other applications have only a slight but accurately known effect on the transmission time, in particular. As a result of the resource reservation, real-time data are not lost.
- Within the respective
field bus segment 1 a, 1 b, data are transmitted via Ethernet. In the exemplary illustrated embodiment, data are transmitted specifically from therespective device field bus switch 27 of the respectivefield bus segment 1 a, 1 b and from the respectivefield bus segment 1 a, 1 b to therespective connection node field bus segment 1 a, 1 b. -
FIG. 2 indicates, in a purely schematic manner, the use of the bandwidth for the TSN network, on the one hand, and for the field bus network, on the other hand, via “speech bubbles” adjoining theTSN network 6 and the network of thefield bus segment 1 b. - Specifically, a link bandwidth Blink, a bandwidth B50%, which corresponds to half of the link bandwidth, and an actually used bandwidth By below B50% are depicted for the field bus network (right-hand “speech bubble”). In the present case, a bandwidth of 100 Mbit/s is available and is permanently divided into a half B50% (50 Mbit/s) for real-time data and a further half (generally 50 Mbit/s) for other traffic.
- In the
TSN network 6 in which a higher bandwidth is available, the situation is such that a maximum class bandwidth BKmax is available and there is a stream bandwidth Bstream that is below the class bandwidth. The stream bandwidth may have been taken, in particular, either from the configuration of the field bus 1, in particular the TIA configuration, for example may be 10 Mbit/s, or can be defined as a standard value of 50 Mbit/s by the system definition, in particular in the case of PROFINET. - As an alternative to the exemplary embodiment that is illustrated in
FIG. 2 and has a field bus 1 with twofield bus segments 1 a, 1 b between which data are transmitted via astream TSN network 6 andstreams TSN network 6. - A constellation for more than one field bus 1 is shown by way of example and in a purely schematic manner in
FIG. 6 . Identical components are provided with identical reference numerals therein. It should be noted that thefield bus segments 1 a, 1 b are not illustrated inFIG. 6 , but rather only three pairs ofconnection nodes streams field bus segments 1 a, 1 b connected via the streams. For each individual field bus of the three field buses 1 each with twosegments 1 a, 1 b, it is the case that the arrangement is like that inFIG. 2 . - It is seen that the network path for the horizontally hatched pair of
connection nodes connection nodes streams TSN network 6. Thestreams streams TSN switch 28 which is at the bottom left inFIG. 6 , reservations for fourstreams TSN switch 28 at the bottom right and reservations only for twostreams upper switch 28. - It should be emphasized that this configuration is purely exemplary and the
TSN network 6 may comprise any other desired number ofswitches 28 and the reservations may also be different. - Furthermore, as an alternative to the exemplary above-described embodiments, provision may also be made for more than two
field bus segments 1 a, 1 b to be connected via aTSN network 6 and forstreams - It should be noted that, in the simplest case, a field bus segment may also be formed by an
individual device field bus segments 1 a, 1 b andfurther devices TSN network 6 and forstreams - A constellation in which two
field bus segments 1 a, 1 b and a furtherfield bus device 3 are connected via theTSN network 6 and communicate via theTSN network 6 is illustrated purely by way of example and in a schematic manner inFIGS. 7 and 8 . Identical reference signs have again been used in these figures. - In such a case, three
connection nodes streams TSN network 6. - In this case, analogously to
FIG. 6 ,FIG. 7 shows only theconnection nodes streams field bus segments 1 a, 1 b, 1 c connected via theTSN network 6 and to which threeconnection nodes streams FIG. 2 ,FIG. 8 shows the situation of only one field bus 1 fromFIG. 7 , specifically the field bus 1 with threesegments 1 a, 1 b, 1 c, where the third field bus segment 1 c is formed by an individual device, specifically ascreen 3. - A
stream field bus segment 1 a, 1 b, 1 c and is used to respectively transmit data to the two otherfield bus segments 1 a, 1 b, 1 c (cf. also the arrows inFIG. 7 andFIG. 8 ). This is a multiple listener per talker constellation, and the Stream Reservation Protocol (SRP), which supports this, was resorted to for the resource reservation in the exemplary embodiment illustrated. - For further illustration,
FIG. 9 shows a purely schematic illustration ofdata 31 that are transmitted in the field bus 1, in particular to aconnection node connection node field bus port 11 to the right of thedata 30 and astream data frame 19 with astream header 14 and a useful data region or “payload” 13 and aCRC 25 again to the right of said connection node. The connection of theconnection node TSN network 6 is also schematically indicated inFIG. 6 via a cloud. -
FIGS. 10 and 11 illustrate the frame forwarding in more detail, whereFIG. 10 schematically illustrates four field bus data frames arriving in succession at aconnection node FIG. 10 . The field bus data frames FD0, FD1, FD2, FD3 can arrive with the maximum possible bandwidth. - Illustrated underneath are the corresponding four stream data frames (which are given by the field bus data frames “packed” in a stream-enabled manner) which are denoted SD0, SD1, SD2 and SD3. A preceding stream data frame is indicated to the left of the first stream data frame SD0 using a dashed line. It is seen that the stream data frames SD0, SD1, SD2, SD3 have a shorter extent in the direction of the
time axis 34, which can be attributed to the higher bandwidth in theTSN network 6 in comparison with the field bus network. The stream data frames SD0, SD1, SD2, SD3 can be transmitted with the higher bandwidth. - The top of
FIG. 11 again illustrates the four stream data frames SD0, SD1, SD2, SD3, in which case it is outlined underneath that the forwarding is carried out in such a manner that a break P0, P1, P2, P3 is made after the transmission of each stream data frame SD0, SD1, SD2, SD3, the length of which break depends on the transmitted volume of data, which is indicated in the FIG as the size G0, G1, G2, G3 of the respective stream data frame SD0, SD1, SD2, SD3, and the bandwidth which is reserved for therespective stream stream - This procedure corresponds to the AVB or TSN model with reserved traffic for streams using the CBS (Credit Based Shaper) mechanism (IEEE 802.1Qav). Network resources, inter alia the bandwidth, are reserved for the streams.
- It should be noted that the “credit” is indicated in
FIG. 11 below the respective stream SD0, SD1, SD2, SD3 using the “jagged” line, which credit must “recover” to zero again from the negative range during the break after the transmission of a frame SD0, SD1, SD2, SD3 so that the next frame SD0, SD1, SD2, SD3 can be transmitted. - An alternative for transmitting field bus data frames FD0, FD1, FD2, FD3 in a network with a higher bandwidth, which is known to the applicant and does not provide these advantages, is illustrated (again in a purely schematic manner) in
FIG. 12 . - In this case (analogously to
FIG. 10 ), the top ofFIG. 12 shows four field bus data frames FD0, FD1, FD2, FD3 in a field bus network with a lower bandwidth and underneath in a network with a higher bandwidth. The field bus data frames FD0, FD1, FD2, FD3 are not, as described with reference toFIG. 11 , transmitted via streams with resources secured via reservations, but rather a fixed time window F for transmitting the frames FD0, FD1, FD2, FD3 is provided in eachnetwork cycle 35. If the volume of data in a frame, in particular, is too large to be completely transmitted within the window F, then the transmission must be performed or continued in the next cycle, which is indicated inFIG. 12 by thearrows 36 pointing to the respectively following cycle, and there is a traffic jam of packets. The bandwidth can never be fully used. Another problem of this time-based forwarding is that a different clock rate may arise in the field bus system (application is a time driver) and the higher-bandwidth network (system time in the network). -
FIG. 13 is a flowchart of the method for communicating data in a network. The method comprises transmitting data between a plurality ofdevices step 1310. Here, at least one device of the plurality ofdevices - Next, the data at least is transmitted in sections via either an Audio Video Bridging (AVB) and/or a Time Sensitive Networking (TSN)
network 6 in which at least onestream step 1320. Here, resources have been and/or are reserved for the at least onestream connection node network 6. - Next, data frames 13 that either emanate from at least one device on the field bus and/or are intended for at least one device on the field bus are transmitted via the at least one
stream step 1330. - Next, the or each field bus 1 are connected to either the AVB and/or the
TSN network 6 via the at least oneconnection node step 1340. - In accordance with the method of the invention, the at least one
connection node field bus port 12 in a direction of a respective field bus 1 and a stream port (12) in the direction of either the AVB and/or theTSN network 6 and the at least oneconnection node stream address 15, aVLAN ID 17 and/or apriority 18 to data frames 13 that arrive at thefield bus port 11 and to remove at least one stream parameter comprising either the designatedstream address 15, the VLAN ID and/or thepriority 18 from data frames 19 that arrive at thestream port 12. - Although the invention has been described and illustrated more specifically in detail by the preferred exemplary embodiment, the invention is not restricted by the disclosed examples and other variations can be derived therefrom by a person skilled in the art without departing from the scope of protection of the invention.
- Thus, while there have been shown, described and pointed out fundamental novel features of the invention as applied to a preferred embodiment thereof, it will be understood that various omissions and substitutions and changes in the form and details of the methods described and the devices illustrated, and in their operation, may be made by those skilled in the art without departing from the spirit of the invention. For example, it is expressly intended that all combinations of those elements and/or method steps which perform substantially the same function in substantially the same way to achieve the same results are within the scope of the invention. Moreover, it should be recognized that structures and/or elements and/or method steps shown and/or described in connection with any disclosed form or embodiment of the invention may be incorporated in any other disclosed or described or suggested form or embodiment as a general matter of design choice. It is the intention, therefore, to be limited only as indicated by the scope of the claims appended hereto.
Claims (21)
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP18154319.0 | 2018-01-31 | ||
EP18154319.0A EP3522477B1 (en) | 2018-01-31 | 2018-01-31 | Method for communicating data in an industrial network in particular, device for carrying out the method, computer program and computer-readable medium |
EP18184095.0A EP3522482B1 (en) | 2018-01-31 | 2018-07-18 | Method for communicating data in an industrial network , control method, device, computer program and computer-readable medium |
EP18184095.0 | 2018-07-18 | ||
PCT/EP2019/051506 WO2019149578A1 (en) | 2018-01-31 | 2019-01-22 | Method for data communication in a particularly industrial network, control method, device, computer program and computer-readable medium |
Publications (1)
Publication Number | Publication Date |
---|---|
US20210075838A1 true US20210075838A1 (en) | 2021-03-11 |
Family
ID=61167883
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/965,429 Active 2039-01-30 US11477107B2 (en) | 2018-01-31 | 2019-01-03 | Method for data communication in an industrial network, control method, device, computer program and computer-readable medium |
US16/965,194 Active US11296968B2 (en) | 2018-01-31 | 2019-01-22 | Control method, device, computer program, computer readable medium and method for data communication in an industrial network |
US16/965,970 Pending US20210075838A1 (en) | 2018-01-31 | 2019-01-22 | Control Method, Apparatus, Computer Program, Computer-Readable Medium and Method for Communicating Data in an Industrial Network |
US16/259,026 Pending US20190238441A1 (en) | 2018-01-31 | 2019-01-28 | Method for data communication in a network |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/965,429 Active 2039-01-30 US11477107B2 (en) | 2018-01-31 | 2019-01-03 | Method for data communication in an industrial network, control method, device, computer program and computer-readable medium |
US16/965,194 Active US11296968B2 (en) | 2018-01-31 | 2019-01-22 | Control method, device, computer program, computer readable medium and method for data communication in an industrial network |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/259,026 Pending US20190238441A1 (en) | 2018-01-31 | 2019-01-28 | Method for data communication in a network |
Country Status (4)
Country | Link |
---|---|
US (4) | US11477107B2 (en) |
EP (7) | EP3522477B1 (en) |
CN (4) | CN111670566B (en) |
WO (4) | WO2019149466A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210392084A1 (en) * | 2018-11-13 | 2021-12-16 | Abb Schweiz Ag | Transmission Of Packets Over A TSN Aware Network |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3522477B1 (en) | 2018-01-31 | 2021-08-11 | Siemens Aktiengesellschaft | Method for communicating data in an industrial network in particular, device for carrying out the method, computer program and computer-readable medium |
AT522898A1 (en) * | 2019-08-27 | 2021-03-15 | B & R Ind Automation Gmbh | Transmission of data packets |
EP4017190B1 (en) | 2019-09-18 | 2023-10-25 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Resource configuration method and access network device |
EP4033701A4 (en) * | 2019-09-19 | 2022-11-16 | Vivo Mobile Communication Co., Ltd. | Information transmission method and communication device |
EP3846395A1 (en) * | 2019-12-30 | 2021-07-07 | Siemens Aktiengesellschaft | Method for redundant transmission of data streams in a communication network, network infrastructure device and communication terminal |
CN113543234A (en) * | 2020-04-13 | 2021-10-22 | 中兴通讯股份有限公司 | Port resource reservation method, electronic device and storage medium |
CN111314228B (en) * | 2020-05-11 | 2020-08-11 | 之江实验室 | PLC control system supporting time-sensitive network function |
US11133959B1 (en) * | 2020-06-15 | 2021-09-28 | Moxa Inc. | Apparatuses and methods for routing packets for a time-sensitive networking (TSN) network by virtual local area network (VLAN) tag replacement |
CN116057897A (en) * | 2020-09-07 | 2023-05-02 | 赫思曼自动化控制有限公司 | Method for operating a network |
CN116420347A (en) * | 2020-10-23 | 2023-07-11 | 上海诺基亚贝尔股份有限公司 | Method and apparatus for multicast service support in a time sensitive network |
EP4260535A1 (en) * | 2020-12-10 | 2023-10-18 | Rambus Inc. | Network interface supporting time sensitive networks and macsec protection |
EP4050856A1 (en) | 2021-02-25 | 2022-08-31 | Siemens Aktiengesellschaft | Method for transmitting time-critical data within a communication system and communication device |
CN113259244B (en) * | 2021-05-27 | 2021-10-08 | 中国人民解放军国防科技大学 | Traffic mapping method for time-sensitive network |
CN113949669B (en) * | 2021-10-15 | 2023-12-01 | 湖南八零二三科技有限公司 | Vehicle-mounted network switching device and system capable of automatically configuring and analyzing according to flow |
CN113890790B (en) * | 2021-11-01 | 2023-05-23 | 中国电信股份有限公司 | Method and device for transmitting service data in industrial network, equipment and storage medium |
CN117666493A (en) * | 2023-11-16 | 2024-03-08 | 北京开元泰达净化设备有限公司 | Data interaction method and system applied to industrial Internet of things |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050228509A1 (en) * | 2004-04-07 | 2005-10-13 | Robert James | System, device, and method for adaptively providing a fieldbus link |
US20080232243A1 (en) * | 2007-03-20 | 2008-09-25 | Amit Oren | Method and system for implementing redundancy for streaming data in audio video bridging networks |
US20150363355A1 (en) * | 2014-06-12 | 2015-12-17 | Nxp B.V. | Fine-grained stream-policing mechanism for automotive ethernet switches |
US20160127268A1 (en) * | 2014-11-04 | 2016-05-05 | Siemens Aktiengesellschaft | Network Arrangement and Method Prioritization of Real-Time Telegrams in a Convergent Network |
WO2016202377A1 (en) * | 2015-06-17 | 2016-12-22 | Renesas Electronics Europe Limited | Avb frame forwarding |
EP3013009B1 (en) * | 2014-10-22 | 2017-09-20 | Siemens Aktiengesellschaft | Network assembly and method for detecting a utilisation peak in a convergent network |
US20180338265A1 (en) * | 2017-05-16 | 2018-11-22 | Qualcomm Incorporated | Ethernet over cellular |
Family Cites Families (51)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0676878A1 (en) * | 1994-04-07 | 1995-10-11 | International Business Machines Corporation | Efficient point to point and multi point routing mechanism for programmable packet switching nodes in high speed data transmission networks |
US6246692B1 (en) * | 1998-02-03 | 2001-06-12 | Broadcom Corporation | Packet switching fabric using the segmented ring with resource reservation control |
AU2001240004A1 (en) * | 2000-03-03 | 2001-09-17 | Qualcomm Incorporated | Method and apparatus for participating in group communication services in an existing communication system |
US7058947B1 (en) * | 2000-05-02 | 2006-06-06 | Microsoft Corporation | Resource manager architecture utilizing a policy manager |
US7688764B2 (en) * | 2002-06-20 | 2010-03-30 | Motorola, Inc. | Method and apparatus for speaker arbitration in a multi-participant communication session |
JP2005537764A (en) | 2002-09-03 | 2005-12-08 | トムソン ライセンシング | Mechanism for providing QoS in a network using priority and reserve bandwidth protocols |
ATE385159T1 (en) | 2004-04-27 | 2008-02-15 | Nokia Siemens Networks Gmbh | METHOD FOR ESTABLISHING CONNECTIONS WITH PRE-PAGING WITH OPTIMIZED USE OF RESOURCES |
US7689998B1 (en) * | 2004-07-13 | 2010-03-30 | Microsoft Corporation | Systems and methods that manage processing resources |
WO2006089756A1 (en) | 2005-02-24 | 2006-08-31 | Smsc Europe Gmbh | Distributed network system with hierarchical management of resources |
KR101224594B1 (en) | 2005-04-28 | 2013-01-22 | 삼성전자주식회사 | Guaranteed services method and apparatus in Bridged LAN |
WO2006129819A1 (en) * | 2005-05-31 | 2006-12-07 | Matsushita Electric Industrial Co., Ltd. | Broadcast receiving terminal and program execution method |
EP2122939B1 (en) | 2007-03-21 | 2016-06-01 | Nokia Technologies Oy | Method, apparatus and computer program product for handover failure recovery |
US8345553B2 (en) * | 2007-05-31 | 2013-01-01 | Broadcom Corporation | Apparatus and methods for reduction of transmission delay in a communication network |
CN100571162C (en) * | 2007-07-04 | 2009-12-16 | 华为技术有限公司 | A kind of resource acceptance control method, system and business application system |
CN101355491B (en) | 2007-07-24 | 2012-03-21 | 华为技术有限公司 | Method for transmitting data and network element equipment |
WO2009023838A1 (en) | 2007-08-15 | 2009-02-19 | Cisco Technology, Inc. | Stream reservation protocol for bridged networks |
US8687938B2 (en) * | 2008-03-31 | 2014-04-01 | Panasonic Corporation | Video recording system, video recording apparatus, and video recording method |
EP2227063B1 (en) * | 2009-03-04 | 2012-03-14 | Fujitsu Limited | Improvements to wireless sensor networks |
US20130070788A1 (en) * | 2010-05-25 | 2013-03-21 | Siemens Aktiengesellschaft | Method and Apparatus for Interchanging Data, and Network |
US8908701B2 (en) * | 2011-03-14 | 2014-12-09 | Broadcom Corporation | Stream path selection within convergent networks |
US8705391B2 (en) * | 2011-03-24 | 2014-04-22 | Intel Corporation | Reducing latency of at least one stream that is associated with at least one bandwidth reservation |
US8619803B2 (en) * | 2011-05-05 | 2013-12-31 | Harman International Industries, Incorporated | Sparse mode system |
EP2719126A4 (en) | 2011-06-08 | 2015-02-25 | Samsung Electronics Co Ltd | Enhanced stream reservation protocol for audio video networks |
US8516130B2 (en) * | 2011-06-30 | 2013-08-20 | Harman International Industries, Incorporated | Using non-AVB application layer interface and message to establish a connection over an AVB network |
DE102012207900A1 (en) * | 2012-05-11 | 2013-11-14 | Continental Automotive Gmbh | Method for transmitting data with an Ethernet transport protocol between nodes of a motor vehicle as well as for the implementation of the method set up control device |
DE102012207883A1 (en) * | 2012-05-11 | 2013-11-14 | Continental Automotive Gmbh | A method for transmitting data with an Ethernet AVB transport protocol between nodes of a motor vehicle as well as for the implementation of the method set up control device |
DE102012207929A1 (en) | 2012-05-11 | 2013-11-14 | Continental Automotive Gmbh | A method of transmitting data in a packet-oriented communication network and appropriately configured user equipment on the communication network |
DE102012207952A1 (en) * | 2012-05-11 | 2013-11-14 | Continental Automotive Gmbh | A method of transmitting data in a packet-oriented communication network and appropriately configured user equipment on the communication network |
DE102012216012A1 (en) * | 2012-09-10 | 2014-03-13 | Continental Automotive Gmbh | Data recording device for a vehicle network |
IN2013MU03527A (en) * | 2013-11-08 | 2015-07-31 | Tata Consultancy Services Ltd | |
US20170142226A1 (en) * | 2014-01-31 | 2017-05-18 | Interdigital Patent Holdings, Inc. | Methods, apparatuses and systems directed to enabling network federations through hash-routing and/or summary-routing based peering |
WO2015170144A1 (en) | 2014-05-08 | 2015-11-12 | Nokia Technologies Oy | Techniques allowing activation and deactivation of nodes in a network |
CN103986714B (en) * | 2014-05-16 | 2017-11-21 | 深圳市达图蛙科技开发有限公司 | Bus marco network insertion AVB networks are acted on behalf of into implementation method and device |
CN104243353B (en) | 2014-09-19 | 2018-02-09 | 中国电子科技集团公司第七研究所 | The energy method for obligating and system and network transfer method and system of network transmission |
US9917791B1 (en) * | 2014-09-26 | 2018-03-13 | Netflix, Inc. | Systems and methods for suspended playback |
KR101673304B1 (en) * | 2014-12-10 | 2016-11-07 | 현대자동차주식회사 | Method and apparatus for controlling AVB(Audio/Video Bridging) stream for in-vehicle ethernet |
US20160191597A1 (en) * | 2014-12-26 | 2016-06-30 | Harman International Industries, Incorporated | Avb system diagnostics |
EP3057273B1 (en) * | 2015-02-13 | 2019-03-27 | Mitsubishi Electric R&D Centre Europe B.V. | Method for a traffic shaping in a network |
KR102294634B1 (en) * | 2015-08-12 | 2021-08-26 | 현대자동차주식회사 | Operation method of communication node in network |
CN106921594B (en) | 2015-12-28 | 2019-11-08 | 中国科学院沈阳自动化研究所 | A kind of dynamic network resource reservation QoS assurance towards industrial SDN |
KR102482102B1 (en) | 2016-02-26 | 2022-12-27 | 현대자동차주식회사 | Method for releasing resource reservation in network |
US10555288B2 (en) * | 2016-03-11 | 2020-02-04 | Asustek Computer Inc. | Method and apparatus for assisting data transmission in a wireless communication system |
EP3226484A1 (en) | 2016-03-31 | 2017-10-04 | Siemens Aktiengesellschaft | Method for transmitting data in a communications network of an industrial automation system and communication device |
JP2017204857A (en) * | 2016-05-12 | 2017-11-16 | 現代自動車株式会社Hyundai Motor Company | Method for setting stream communication path in network |
JP6879789B2 (en) * | 2016-05-27 | 2021-06-02 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America | Gateway devices, in-vehicle network systems, transfer methods and programs |
EP3264644A1 (en) * | 2016-07-01 | 2018-01-03 | Nxp B.V. | Multiple source receiver |
WO2018117279A1 (en) * | 2016-12-19 | 2018-06-28 | 엘지전자(주) | Network device and method for selecting transmission of network device |
US11281499B2 (en) * | 2017-02-05 | 2022-03-22 | Intel Corporation | Microservice provision and management |
WO2018166593A1 (en) * | 2017-03-15 | 2018-09-20 | Siemens Aktiengesellschaft | Method for bandwidth reservation and suitable grid element |
US11290923B2 (en) * | 2017-12-30 | 2022-03-29 | Intel Corporation | Handover-related technology, apparatuses, and methods |
EP3522477B1 (en) | 2018-01-31 | 2021-08-11 | Siemens Aktiengesellschaft | Method for communicating data in an industrial network in particular, device for carrying out the method, computer program and computer-readable medium |
-
2018
- 2018-01-31 EP EP18154319.0A patent/EP3522477B1/en active Active
- 2018-07-02 EP EP18181209.0A patent/EP3522480A1/en not_active Withdrawn
- 2018-07-09 EP EP18182351.9A patent/EP3522481A1/en not_active Withdrawn
- 2018-07-18 EP EP18184095.0A patent/EP3522482B1/en active Active
- 2018-07-18 EP EP18184117.2A patent/EP3522483A1/en not_active Withdrawn
-
2019
- 2019-01-03 CN CN201980011043.0A patent/CN111670566B/en active Active
- 2019-01-03 US US16/965,429 patent/US11477107B2/en active Active
- 2019-01-03 EP EP19700553.1A patent/EP3695576B1/en active Active
- 2019-01-03 WO PCT/EP2019/050105 patent/WO2019149466A1/en unknown
- 2019-01-22 WO PCT/EP2019/051504 patent/WO2019149577A1/en unknown
- 2019-01-22 WO PCT/EP2019/051489 patent/WO2019149576A1/en active Application Filing
- 2019-01-22 EP EP19704205.4A patent/EP3695577B1/en active Active
- 2019-01-22 US US16/965,194 patent/US11296968B2/en active Active
- 2019-01-22 CN CN201980011086.9A patent/CN111684776B/en active Active
- 2019-01-22 WO PCT/EP2019/051506 patent/WO2019149578A1/en active Application Filing
- 2019-01-22 US US16/965,970 patent/US20210075838A1/en active Pending
- 2019-01-22 CN CN201980011048.3A patent/CN111670567B/en active Active
- 2019-01-28 US US16/259,026 patent/US20190238441A1/en active Pending
- 2019-01-30 CN CN201910094953.1A patent/CN110099093B/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050228509A1 (en) * | 2004-04-07 | 2005-10-13 | Robert James | System, device, and method for adaptively providing a fieldbus link |
US20080232243A1 (en) * | 2007-03-20 | 2008-09-25 | Amit Oren | Method and system for implementing redundancy for streaming data in audio video bridging networks |
US20150363355A1 (en) * | 2014-06-12 | 2015-12-17 | Nxp B.V. | Fine-grained stream-policing mechanism for automotive ethernet switches |
EP3013009B1 (en) * | 2014-10-22 | 2017-09-20 | Siemens Aktiengesellschaft | Network assembly and method for detecting a utilisation peak in a convergent network |
US20160127268A1 (en) * | 2014-11-04 | 2016-05-05 | Siemens Aktiengesellschaft | Network Arrangement and Method Prioritization of Real-Time Telegrams in a Convergent Network |
WO2016202377A1 (en) * | 2015-06-17 | 2016-12-22 | Renesas Electronics Europe Limited | Avb frame forwarding |
US20180338265A1 (en) * | 2017-05-16 | 2018-11-22 | Qualcomm Incorporated | Ethernet over cellular |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210392084A1 (en) * | 2018-11-13 | 2021-12-16 | Abb Schweiz Ag | Transmission Of Packets Over A TSN Aware Network |
Also Published As
Publication number | Publication date |
---|---|
US20210067571A1 (en) | 2021-03-04 |
US20190238441A1 (en) | 2019-08-01 |
US11477107B2 (en) | 2022-10-18 |
WO2019149577A1 (en) | 2019-08-08 |
EP3695576A1 (en) | 2020-08-19 |
WO2019149578A1 (en) | 2019-08-08 |
EP3522480A1 (en) | 2019-08-07 |
CN110099093B (en) | 2022-07-15 |
EP3522483A1 (en) | 2019-08-07 |
EP3522482B1 (en) | 2020-08-26 |
WO2019149466A1 (en) | 2019-08-08 |
EP3695577A1 (en) | 2020-08-19 |
EP3522477A1 (en) | 2019-08-07 |
EP3522482A1 (en) | 2019-08-07 |
EP3522481A1 (en) | 2019-08-07 |
CN111670567B (en) | 2022-10-04 |
US20210120065A1 (en) | 2021-04-22 |
CN111684776A (en) | 2020-09-18 |
EP3522477B1 (en) | 2021-08-11 |
CN111670566B (en) | 2022-08-30 |
CN111670567A (en) | 2020-09-15 |
CN110099093A (en) | 2019-08-06 |
US11296968B2 (en) | 2022-04-05 |
CN111684776B (en) | 2023-04-04 |
EP3695576B1 (en) | 2021-09-22 |
WO2019149576A1 (en) | 2019-08-08 |
CN111670566A (en) | 2020-09-15 |
EP3695577B1 (en) | 2021-06-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20210075838A1 (en) | Control Method, Apparatus, Computer Program, Computer-Readable Medium and Method for Communicating Data in an Industrial Network | |
JP7312210B2 (en) | GATEWAY DEVICE, VEHICLE NETWORK SYSTEM, TRANSFER METHOD AND PROGRAM | |
US10873536B2 (en) | Distribution node, automation network, and method for transmitting real-time-relevant and non-real-time-relevant data packets | |
US10615997B2 (en) | In-vehicle gateway device | |
US11467566B2 (en) | Communication device, communication terminal, communication device and method for operating a communication system for transmitting time-critical data | |
US11050585B2 (en) | Data transmission method and communications network | |
CN104144094B (en) | Digital bus system slave node and its operating method | |
US11316654B2 (en) | Communication device and method for operating a communication system for transmitting time critical data | |
JP5716133B2 (en) | Industrial controller device capable of low error rate and ultra-high speed serial communication and driving method thereof | |
US8792518B2 (en) | Automation system | |
CN112640386B (en) | Method and simulation system for simulating the handling of reservation requests for multicast data streams in a communication network | |
CA2943875A1 (en) | Method for asynchronous data communication in a real-time capable ethernet data network | |
US20230353422A1 (en) | Network Switch, Communication System and Method for Operating a Communication System for Transmitting Time-Critical Data | |
US11522762B2 (en) | Coordination device and method for providing control applications via a communication network for transmitting time-critical data | |
CN114531943B (en) | Data transmission method and automation communication network | |
EP3879764B1 (en) | Transporting a message from an industrial end device over an ethernet network | |
CN112753206B (en) | Method and communication device for data transmission in industrial communication network | |
An et al. | Analysis of CAN FD to CAN message routing method for CAN FD and CAN gateway | |
US11356358B2 (en) | Network node, computer program, computer-readable medium and method for fail-safe data transmission | |
US20240097981A1 (en) | Method and Control Program for Automated Configuration of a Communication Network Comprising Multiple Virtual Local Area Networks | |
JP2017163437A (en) | Communication apparatus and communication method | |
JP2009118357A (en) | Ethernet switch |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SIEMENS AKTIENGESELLSCHAFT, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KIESSLING, MARCEL;REEL/FRAME:054799/0223 Effective date: 20201026 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: ADVISORY ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: ADVISORY ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |