EP4005163A1 - Transmission de paquets de données - Google Patents

Transmission de paquets de données

Info

Publication number
EP4005163A1
EP4005163A1 EP20764060.8A EP20764060A EP4005163A1 EP 4005163 A1 EP4005163 A1 EP 4005163A1 EP 20764060 A EP20764060 A EP 20764060A EP 4005163 A1 EP4005163 A1 EP 4005163A1
Authority
EP
European Patent Office
Prior art keywords
tsn
network
ethernet
stream
data packet
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
Application number
EP20764060.8A
Other languages
German (de)
English (en)
Inventor
Dietmar Bruckner
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
B&R Industrial Automation GmbH
Original Assignee
B&R Industrial Automation GmbH
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by B&R Industrial Automation GmbH filed Critical B&R Industrial Automation GmbH
Publication of EP4005163A1 publication Critical patent/EP4005163A1/fr
Pending legal-status Critical Current

Links

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/28—Flow control; Congestion control in relation to timing considerations
    • 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
    • H04L12/4625—Single bridge functionality, e.g. connection of two networks over a single bridge
    • 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/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • the present invention relates to a method for transmitting a, preferably cyclical, data packet from an Ethernet component, which is arranged in an Ethernet network within a mixed network, to a TSN component, which is configured in a TSN according to the standards of the IEEE 802.1 TSN Industrial communication network is arranged.
  • a pure Ethernet network which consists exclusively of standard Ethernet components, is not deterministic, which means that no time guarantees can be given for sent / received data packets - even if all existing quality-of-service mechanisms are exhausted.
  • data packets can be transmitted cyclically and with guarantees.
  • industrial communication networks are usually set up using special Industrial Ethernet components, i.e. special Industrial Ethernet software stacks and special Industrial Ethernet hardware.
  • Industrial communication networks are usually characterized by low bit error rates, as well as special frame formats and the sending of cyclical frames that is organized at a precise time.
  • Endpoints and controllers represent components of a network, whereby an endpoint can only receive data packets via one connection and a controller via several connections.
  • a bridge is also called a switch and is used to connect components of a network.
  • An edge bridge is used to connect a network (e.g. an industrial communication network) with a second network (e.g. a standard Ethernet network).
  • Bridges can thus represent pure network infrastructure devices, but they can also be used as endpoints or controllers as bridged endpoints or bridged controllers, which means that they can also be used to connect other components.
  • a mixed network which comprises an industrial communication network and a (standard) Ethernet network.
  • Ethernet components can be connected to the industrial communication network via a gateway.
  • the (standard) Ethernet components do not support any functions necessary for cyclic data traffic for sent / received data packets, for example the issuing of guarantees, in particular time guarantees.
  • Well-known industrial communication networks with special industrial Ethernet hardware include PROFINET IRT, POWERLINK, EtherCAT, SERCOS, etc.
  • Such industrial communication networks each have special mechanisms in order to implement mixed networks. In the context of these mechanisms, however, the introduction of non-real-time traffic is fundamentally restricted in order not to endanger the real-time capability.
  • Ethernet / IP and Profinet / IO represent industrial communication networks that are built up from standard Ethernet components.
  • these industrial communication networks have longer cycle times and are less robust than non-real-time traffic, since real-time traffic and non-real-time traffic cannot be differentiated on the basis of their associated frames and are therefore treated in the same way by the bridges. It is therefore possible that real-time traffic is displaced by non-real-time traffic.
  • part of the real-time traffic can be shifted to a subsequent cycle.
  • the receiver thus receives no data packets at least in one cycle and switches to an error mode and / or extrapolates the previously received data packets.
  • the recipient then receives several data packets. These multiple data packets must in turn be handled specially. If a small proportion of non-real-time traffic is provided, the problem mentioned seldom occurs. Choosing such a long cycle time that the bandwidth required for real-time traffic is relatively small can serve to increase robustness. At best, this measure does not result in any shifting of individual frames into the next cycle.
  • Components must be based to enable cyclic data traffic at all
  • Network Calculus is a common method to use in a non-real-time network
  • Data packets are specified, with which the required bandwidths for a transmission of a data packet are calculated. This information is correspondingly more statistical
  • this object is achieved by a method for transmitting a, preferably cyclic, data packet from an Ethernet component, which is arranged in an Ethernet network within a mixed network, to a TSN component, which is in a TSN according to the standards of the IEEE 802.1 TSN configured industrial communication network is arranged within the mixed network, with at least one guarantee defined in the standards of the IEEE 802.1 TSN working group being granted for the data packet by a frame F1 containing the data packet in the industrial communication network configured according to the standards of the IEEE 802.1 TSN working group identified by a TSN bridge, converted into a TSN stream containing the data packet, and the data packet is transmitted to the TSN component in the TSN stream.
  • the industrial communication network is thus configured according to the standards of the IEEE 802.1 TSN working group, which enables guarantees to be issued, e.g. for cyclic data packets.
  • the industrial communication network which is configured according to the standards of the IEEE 802.1 TSN working group, is referred to as a TSN network for the sake of simplicity.
  • the components in the TSN network are referred to as TSN components.
  • the streams configured in the standards of the IEEE 802.1 TSN working group are referred to as TSN streams.
  • the part of the network outside of the TSN network is commonly referred to as the Ethernet network.
  • Components that are not in the TSN network (or other industrial communication networks) but in the (Ethernet) network are referred to as Ethernet components.
  • Ethernet frames are referred to as frames for the sake of simplicity.
  • TSN streams are used according to the invention, which improves the communication between the TSN components and the Ethernet components.
  • a data packet is sent by a TSN component as a transmitter (talker) via one or more appropriately configured TSN bridges are transmitted to one or more TSN components as receivers (listeners).
  • TSN streams has the advantage that it is easier to estimate the bandwidth required to transmit the data packets in the TSN network, since the bandwidth of unscheduled time windows and / or the free bandwidth of the TSN components is known.
  • the free bandwidth can be planned for further TSN streams by providing further time windows for TSN streams, as described in the TSN configuration options introduced in IEEE 802.1Qcc.
  • the further TSN streams transport further data packets.
  • the entire network could also be built up exclusively from TSN components, which means that there is only one global TSN network.
  • TSN functions of the TSN components are only required for high-performance applications that only include a part of the tasks, only a partial structure using TSN components is advantageous.
  • such a structure as a mixed network is significantly more cost-effective than a pure TSN network.
  • Ethernet components thus serve as feeders to the TSN network.
  • Communication within the Ethernet network (and outside the TSN network) can take place in a known manner by sending frames with data packets.
  • no guarantees, but at best estimates, can be given for the respective data packet.
  • This also applies to frames with data packets that are sent to the TSN network before they arrive in the TSN network and are converted into TSN streams.
  • Isolation generally refers to the use of individual subnetworks through which only part of the data traffic is routed. As a result, the potential interference for real-time traffic due to non-real-time traffic that occurs is lower.
  • isolation generally refers to the use of individual subnetworks through which only part of the data traffic is routed.
  • more network infrastructure ie more bridges and cabling, is required than for an Ethernet network without isolation.
  • using such measures in the Ethernet network (outside the TSN network) is still less costly than operating a pure TSN network.
  • Another advantage of a mixed network is that additional Ethernet components can be connected to the Ethernet network as part of the mixed network without affecting the already existing TSN streams, since the TSN streams are only available in the TSN network as part of the mixed network exist.
  • a mixed network can also be set up in a simple manner, since industrial Ethernet components are often provided with a standard Ethernet connection and the TSN network can easily be expanded to include additional Ethernet components, creating an “Ethernet island” in the TSN Network can be generated.
  • the TSN network is an extension of an Ethernet network and is therefore fully backwards compatible. However, the additional Ethernet components can influence existing "best effort" frames.
  • the frame is preferably identified in accordance with the IEEE 802.1 CB standard.
  • the TSN stream in the TSN network can thus be shaped with the time-aware shaper of the TSN standard IEEE 802.1Qbv. This is particularly advantageous if, for example, a time of reception or a bandwidth is assigned as a guarantee.
  • cyclic process data, audio / video data and other streaming services, configurations, network traces, firmware downloads etc. can be sent as data packets.
  • a stream identification function as defined in the IEEE 802.1CB standard, can be used.
  • Four stream identification functions are defined in the 802.1CB standard, whereby access to the header information from higher protocols (IP, UDP, TCP, OPC UA etc.) is also possible.
  • the credit-based shaper (from IEEE 802.1Q) or the asynchronous traffic shaper from IEEE 802.1Qcr can also be used for guaranteed bandwidth, burst capability and / or latency.
  • These egress features (which “shape” the traffic at the output of a bridge) are very often supported by ingress policing (IEEE 802.1Qci) in order to sort out incorrectly “shaped” or sent TSN frames at the input of a bridge.
  • the frame When it arrives at the industrial communication network configured according to the standards of the IEEE 802.1 TSN working group, the frame is preferably identified by a TSN edge bridge, converted into the TSN stream and transmitted to the TSN component.
  • a TSN edge bridge is a TSN bridge which is also connected to a standard Ethernet component.
  • the frame can also be sent on by a TSN edge bridge as a "best effort" along the communication link to other TSN bridges and only converted into the TSN stream by a subsequent TSN bridge and then forwarded as such.
  • an Ethernet header of the frame is preferably replaced by a TSN header, which is particularly preferably done by means of a retagging function according to the IEEE 802.1Qci standard.
  • the TSN header then comprises a stream address instead of a (unicast) destination MAC address used by Ethernet.
  • the frame containing the data packet can therefore be identified on the one hand based on an Ethernet header and on the other hand the Ethernet header of the original frame can be replaced by a TSN header during the subsequent conversion into the TSN stream.
  • a frequently used function in managed Ethernet networks are virtual LANs (VLANs), where each Ethernet component can become a member of one or more VLANs.
  • the frames sent between Ethernet components of a VLAN are provided with a corresponding tag (tagged frames).
  • the network infrastructure ensures that these frames are not seen by Ethernet components that are members of other VLANs - not even if they are sent as a broadcast.
  • the TSN streams in the TSN network can be seen as an extension of this concept, since subnetworks are encapsulated with VLANs and concrete communication relationships are encapsulated with TSN streams. Therefore, the VLAN field can be used as part of the stream address of TSN streams.
  • a TSN stream prescribes a VLAN tag, which is a fixed part of the stream address.
  • a retagging function as described in the IEEE 802.1Qci standard can be used for this purpose.
  • the identified frame thus receives a new header with stream ID, which means that the data packet is treated as a TSN stream and not as unspecified “best efforf traffic”.
  • the standards of the IEEE 802.1 TSN working group require a VLAN tag and define (as one of the possibilities) DMAC + VLAN tag as the stream address.
  • This stream address comprises a total of 10 bytes and is overwritten during retagging.
  • the other header fields in this case the source MAC address and Ethertype preferably remain unchanged).
  • the Ethernet standard only optionally allows the 4-byte VLAN tag in which VLANs and priorities can be defined. If this VLAN tag was not available, it can be inserted during retagging, whereby the frame is lengthened accordingly.
  • a minimum bandwidth of the TSN stream and / or a maximum latency of the TSN stream and / or a defined burst capability of the TSN stream and / or a defined reception time of the TSN stream is preferably assigned as a guarantee. This is not possible in Industrial Ethernet networks based on standard Ethernet components and is therefore made possible by using a TSN network as an industrial communication network. A burst is the transmission of a large amount of data as quickly as possible. Without the appropriate precautions, however, it is very likely that individual frames of the burst will collide with other traffic in the network. In a TSN network, the IEEE 802.1 TSN Qav standard can be used, which defines the so-called credit-based shaper for a burst.
  • a sender can save credits by "resting” or “not sending”, which he then has to spend when sending TSN frames. This defines the maximum size of a possible burst. If the sender has no more credits, he has to wait after each frame until he has enough credits for the next frame. This will spread its frames fairly evenly over time.
  • the standards of the IEEE 802.1 TSN working group include various traffic shaping mechanisms.
  • the (802.1) Qbv standard can, for example, provide time guarantees.
  • the (802.1) Qav standard can also be used to reserve latencies and bandwidths.
  • the (802.1) Qci standard can in turn be used to restrict bandwidths.
  • all (relevant) other standards contained / referenced in IEEE 802.1 TSN can also be used for the implementation of traffic guarantees (such as Qch, Qcr etc.).
  • the guarantees can be given for data packets sent cyclically, but also for "irregular" (sporadically sent) data packets such as video streams or Internet downloads, etc.
  • the content of the data packet is not relevant for the issuing of guarantees, although the choice of configuration can of course be based on the assumed requirements of the data packets.
  • cyclic process data are sent as data packets, guarantees are preferably given for the time of receipt or for the latency. In the case of audio / video data or configuration data as data packets, guarantees are preferably given for the bandwidth. In the case of traces and / or downloads as data packets, guarantees for burst capability and latency are preferably given.
  • the standards of the IEEE 802.1 TSN working group define, among other things, shaping mechanisms for real-time, bandwidth, burst capability and latency. TSN shaping mechanisms are therefore preferably used to issue guarantees for the TSN stream. This means that any guarantees that are defined in the standards of the IEEE 802.1 TSN working group can be issued. This can be done by performing a shaper configuration in the TSN bridge, which converts to the TSN stream. Furthermore, the shaper configuration is carried out in all other TSN bridges over which the TSN stream is routed. A reception time can be assigned as a guarantee by transmitting the data packet to the TSN component in a TSN stream during a specified time window of a cycle.
  • time windows are configured exclusively for this TSN stream in the TSN network for each TSN bridge over which the TSN stream is routed. If the sender (talker) also guarantees its transmission time for each cycle, the transmission of the TSN stream can be optimized, since the time windows in the TSN network can be very close and without large buffers.
  • a shaping mechanism is used in a TSN network at the same time as “best effort” traffic or several shaping mechanisms, this is generally referred to as “converged”, which results in a so-called “converged network”.
  • converged In a "converged network”, different types of data traffic with different requirements (runtime, bandwidth, burst capability, etc.) are mapped simultaneously on a network infrastructure.
  • TSN streams with lower priority can also be interrupted by TSN streams with higher priority, if this allows the TSN streams with lower priority to meet their guarantees (as described in IEEE 802.1Qbu and IEEE 802.3br).
  • a TSN stream containing the data packet is converted by a TSN bridge into a frame containing the data packet and the data packet is transmitted in the frame to the Ethernet component.
  • the TSN header of the TSN stream can be replaced by an Ethernet header, preferably by a retagging function according to the IEEE 802.1Qci standard.
  • the TSN header of the TSN stream, the VLAN tag can be removed or the TSN header of the TSN stream can be used for the frame.
  • the features of the VLAN tag i.e. the
  • the TSN header is interpreted as a frame header by unconfigured Ethernet components.
  • the multicast bit is set in the TSN header, which means that the frame is sent everywhere in the Ethernet network. The respective recipient must therefore be configured in such a way that it receives the multicast address. Furthermore, the Ethernet network is more heavily loaded with such multicast frames.
  • the multicast destination MAC address used by the TSN stream is interpreted as a broadcast and the bridges of the Ethernet network send the frame to all Ethernet components. However, doing this will flood part of the network with unnecessary data. Therefore it is fundamentally advantageous to convert the TSN stream into a frame.
  • the TSN stream when transmitting a TSN stream from the TSN component located in the industrial communication network to an Ethernet component located in the Ethernet network outside the industrial communication network, the TSN stream can be converted into a frame by a TSN bridge.
  • the TSN stream is preferably converted by a TSN edge bridge into the frame containing the data packet.
  • a TSN bridge located further inside the TSN network can take over the conversion into a frame.
  • the frame is sent on the communication link from the converting TSN bridge to the TSN edge bridge as a "best effort", although it is actually still in the TSN network.
  • the standards of the IEEE 802.1 TSN working group include in particular the IEEE 802.1Q-2018 standard, which describes the TSN functions.
  • the standards of the IEEE 802.1 TSN working group also include the IEEE 802.1CB-2017 standard.
  • IEEE 802.1Qbv-2015, IEEE 802.1Qci-2017, IEEE 802.1Qch-2017, IEEE 802.1Qbu-2016 standards were amendments to the IEEE.802.1Q-2014 standard until 2018 and thus represented independent standards and were incorporated into the IEEE standard 802.1Q-2018 added.
  • IEEE 802.1Qav-2009 was already included in the standard in IEEE.802.1Q-2014.
  • the IEEE 802.1Qcc-2018 standard was only published in 2018 and is therefore an amendment to the IEEE 802.1Q-2018 standard.
  • the IEEE 802.1Qav standard was included in the IEEE 802.1Qav-2009 standard and is now also included in the IEEE 802.1Q-2018 standard.
  • the IEEE 802.1Qcr project has not yet been published as a standard at the time the patent application in question is submitted and has the project number IEEE P802.1Qcr.
  • the IEEE Std. 802.3br-2016 standard is an amendment to the IEEE Std. 802.3-2015 standard and is now included in the IEEE 802.3-2018 standard.
  • FIGS. 1 to 3 show exemplary, schematic and non-limiting advantageous embodiments of the invention. It shows
  • Fig. 1 an Ethernet network and an embedded TSN network
  • 3 shows a time of receipt as a time guarantee.
  • the Ethernet network 3 in turn comprises a number of Ethernet components E1, E2, E3.
  • Ethernet components E1, E2, E3 Network components that are configured in accordance with IEEE 802.1Q (and the other commonly used standards for Ethernet bridges), but not in accordance with the standards of the IEEE 802.1 TSN working group, are referred to as Ethernet components E1, E2, E3.
  • an Ethernet controller is provided in the Ethernet network 3 as the Ethernet component E1, which is connected to an Ethernet field device as the second Ethernet component E2 and to an Ethernet printer as the third Ethernet component E3.
  • the Ethernet controller E1 and the Ethernet field device E2 can process cyclic data traffic, but the Ethernet printer E3 cannot.
  • the applicative function of the Ethernet components E1, E2, E3 is not decisive for the function of the invention.
  • Ethernet controller E1, Ethernet field device E2 and Ethernet printer E3 are therefore generally referred to as Ethernet components E1, E2, E3.
  • the communication connections between the Ethernet components E1, E2, E3 are shown as bars in FIGS. 1 and 2 and connect ports of the respective Ethernet components E1, E2, E3.
  • ok Frames F2, F3 are sent in the Ethernet network 3 between the Ethernet components E1, E2, E3 and each contain data packets D2, D3.
  • the Ethernet component E2 communicates via a connecting communication link with the Ethernet component E1 (and vice versa) via a data packet D2 contained in the frame F2.
  • the Ethernet component E3 communicates via a connecting communication link with the Ethernet component E1 (and vice versa) via a data packet D3 contained in the frame F3.
  • This communication is indicated in FIG. 1 by the arrows along the respective communication connections between the Ethernet components E1, E2, E3.
  • the data packets D2, D3 can only be sent in frames F2, F3 and thus without specifying guarantees.
  • the Ethernet components E1, E2, E3 can be managed (managed) or also unmanaged (not managed). Unmanaged Ethernet components E1, E2, E3 can be connected to the Ethernet network 3 in a simple manner (plug-and-play), but offer no option for configuration or management. An unmanaged Ethernet component E1, E2, E3 learns the target address of a further Ethernet component E1, E2, E3 that can be reached via a port by evaluating the source addresses of frames F2, F3 which are sent by this further Ethernet component E1, E2 , E3 are sent.
  • Managed Ethernet components E1, E2, E3, can be configured, managed and / or monitored, for example, by an external device.
  • an address table can be configured or the Ethernet network 3 can be divided into independent segments by means of VLANs.
  • managed and / or unmanaged Ethernet components E1, E2, E3 and / or VLANs can be used.
  • Ethernet components E1, E2, E3 and TSN components TSN-A, TSN-F, TSN-C described in the illustrated embodiment are able to generate and receive data packets and are also part of the network infrastructure with more than one Port.
  • they are bridged endpoints. Without loss of generality, however, all endpoint-specific statements also apply to endpoints with only one port and all network infrastructure-specific statements also apply to pure network infrastructure devices, i.e. pure bridges.
  • the mixed network 1 includes at least one
  • Industrial communication network preferably with cyclic data traffic, which is configured according to the invention in such a way that functions according to the standards of
  • TSN Network 2 referred to as a “TSN island”, can be surrounded by Ethernet network 3.
  • the TSN network 2 can also adjoin the Ethernet network 3, as is shown in FIGS. 1 and 2.
  • the TSN network 2 comprises the TSN components TSN-A, TSN-F and TSN-C, for example as field devices, the TSN component TSN-F also serving as a TSN edge bridge.
  • the communication links between the TSN components TSN-A, TSN-F, TSN-C are also shown as bars and connect the ports of the respective TSN components TSN-A, TSN-F, TSN-C.
  • One or more further Ethernet networks 3 and / or one or more further industrial networks could of course also be provided in the mixed network 1.
  • These one or more further industrial networks can also be configured according to the standards of the IEEE 802.1 TSN working group and thus represent one or more TSN networks 2.
  • Any industrial networks or TSN networks can adjoin other Ethernet networks 3 and / or TSN networks 2 in the mixed network 1 and / or be surrounded by other Ethernet networks 3 and / or TSN networks 2 as “TSN islands” be.
  • a data packet D2, D3 is sent in a frame F2, F3 from an Ethernet component E1, E2, E3 to a further Ethernet component E1, E2, E3, then said frame F2, F3 can instead of a direct transmission via the directly connecting communication link can also be routed through the TSN network 2.
  • said frame F2, F3 can instead of a direct transmission via the directly connecting communication link can also be routed through the TSN network 2.
  • the transmission of TSN data packets DO, D4 between the respective TSN components TSN-C, TSN-F, TSN-A can be configured with known TSN traffic shaping mechanisms.
  • the TSN component TSN-F can send a TSN stream SO with a data packet DO to the TSN component TSN-C (as indicated in FIG. 2) and vice versa (not shown in FIG. 2).
  • Guarantees can be given for the transmission of the data packet DO, for example a maximum required bandwidth, a maximum latency, a guaranteed transmission time and / or reception time, etc.
  • TSN-C the boundary conditions of the TSN components TSN-C, Subordinate TSN-F, TSN-A, such as network load occurring on the transmitter side, forwarding latencies, available bandwidth or data transmission rate (eg gigabit) etc., in the TSN network 2.
  • TSN-C the boundary conditions of the TSN components
  • Subordinate TSN-F the TSN-F
  • TSN-A such as network load occurring on the transmitter side, forwarding latencies, available bandwidth or data transmission rate (eg gigabit) etc.
  • a further TSN stream S4 with a data packet D4 is sent from the TSN component TSN-A via the TSN component TSN-F to the TSN component TSN-C by way of example.
  • the configuration of the TSN network 2 ensures that the TSN stream S4 and the TSN stream SO can be sent from the TSN component TSN-F to the TSN component TSN-C. In this case, neither the TSN stream S4 interferes with the TSN stream SO, nor vice versa, although the same communication connection is used. This is possible even if the further TSN stream S4 and the TSN stream SO require the same guarantees (time of reception, bandwidth, latency, etc.).
  • a data packet D1 is transmitted from the Ethernet component E1 via the TSN component TSN-F (as a TSN edge bridge) to the TSN component TSN-C. This arrives approximately at the same time as the transmission of the TSN streams SO, S4 at the TSN component TSN-F.
  • S4 from the TSN component TSN-F to the TSN component TSN-C basically no time guarantee can be given for a transmission of a frame F1 itself. Depending on the time of arrival, the frame F1 would be forwarded before the two TSN streams SO, S4 or only afterwards.
  • the frame F1 which contains the data packet D1
  • the TSN network 2 by a TSN bridge, which is done here by the TSN component TSN-F in the form of a TSN edge bridge. From this identification onwards, the necessary transmission properties of the data packet D1 to be transmitted are known, since these are preconfigured.
  • the frame F1 is converted into a TSN stream S1 and processed accordingly in the TSN network 2. This conversion takes place, for example, by replacing the Ethernet header of the frame F1 with a TSN header from the TSN stream S1 in accordance with the configuration.
  • the TSN stream S1 is then sent from the TSN bridge (here TSN component TSN-F) to the addressed TSN component (s) (here TSN component TSN-C) via the intended communication links and according to the Configuration handled.
  • This does not affect the further data traffic (here in the form of the TSN streams SO, S4 with the data packets DO, D4) on the same communication link - im converged network, the guarantees for all TSN streams SO, S1, S4 are met.
  • only one communication connection from the TSN component TSN-F to the TSN component TSN-C serves as a communication connection.
  • the TSN stream S1 could also be routed via further communication links and TSN components.
  • the identification of the frame F1 and the conversion of the frame F1 into a TSN stream S1 can, as described in this exemplary embodiment, immediately upon arrival in the TSN network 2 at a TSN edge bridge (here on the TSN component TSN-F) TSN network 2 take place.
  • frame F1 could also first be forwarded by a TSN edge bridge as a “best effort” and identified by one of the subsequent TSN bridges and converted into a TSN stream S1. This can be particularly advantageous if the configuration capacities of the TSN Edge Bridge are insufficient.
  • all frames originating from the Ethernet network 3 can be converted into TSN streams, provided that there is sufficient bandwidth in the TSN network 2.
  • a frame with a data packet is sent as “best effort” into the TSN network 2, this is done without a guarantee, in particular without a time guarantee, provided that no conversion into a TSN stream takes place in the TSN network 2.
  • the frame in question is then also treated as a frame after it has arrived in the TSN network 2. No guarantees are given because no corresponding mechanisms are configured. This can lead to the data packet arriving with unpredictable delay times.
  • TSN network 2 On the left-hand side, the TSN network 2 is shown, here in the form of the TSN components TSN-A, TSN-C and TSN-F, exemplified as field devices.
  • the Ethernet network 3 is shown on the right-hand side, only the Ethernet component E1 being considered here by way of example.
  • a data packet DO is transmitted as a TSN stream SO from the TSN component TSN-F to the TSN component TSN-C. Furthermore, a data packet D4 is sent as a TSN stream S4 from the TSN component TSN-A via the TSN
  • S1, S4 issued a time guarantee by configuring an exclusive time window t0, t1, t2 for an associated TSN stream SO, S1, S4 for the communication link between the TSN components TSN-F and TSN-C in each cycle z1, z2 .
  • an exclusive time window t0, t1, t2 for an associated TSN stream SO, S1, S4 for the communication link between the TSN components TSN-F and TSN-C in each cycle z1, z2 .
  • the reserved TSN stream SO, S1, S4 is forwarded in the respective time window t0, t1, t2.
  • the reception times for the TSN component TSN-C are guaranteed in the time window tO of the respective cycle z1, z2 if the TSN component TSN-F can comply with the intended transmission times of the TSN stream SO.
  • the TSN component TSN-F sends the TSN stream SO to the TSN component TSN-C at the intended transmission time, the TSN stream SO is sent to the TSN component TSN- in the same time window tO of the current cycle z1, z2. C sent.
  • the corresponding bandwidth is kept free in the TSN network 2 for the TSN stream SO containing the data packet DO on the communication link between the TSN component TSN-F and the TSN component TSN-C. If the transmission time for a TSN stream SO is adhered to with the data packet DO, then this always arrives at the TSN component TSN-C in the same cycle z1, z2.
  • TSN-A, TSN-F, TSN-C Due to an error in one or an incorrect configuration of a TSN component TSN-A, TSN-F, TSN-C, the case may arise that the intended transmission time for the TSN network 2 internal TSN stream SO is not adhered to. This means that no guarantee can be given for reception in the time window t0 of the current cycle z1. However, if at least the maximum size of the data packet DO contained in the TSN stream SO can be maintained, then one cycle can be guaranteed as the maximum latency. The data packet DO is buffered up to the time window tO of the following cycle z2 and then sent in this time window tO. In this case, there is no guarantee for the time window t0 in the current cycle z1. Therefore, however, a Guarantee given for the time window tO in the next cycle z2. The same applies to the TSN stream S4 with the data packet D4.
  • a data packet D1 is now sent from the Ethernet component E1 to the TSN network 2 in a frame F1.
  • the frame F1 is identified by the TSN component TSN F as a TSN (edge) bridge and converted into a TSN stream S1.
  • the data packet D1 is sent to the TSN component TSN-C after the conversion of the frame F1 into the TSN stream S1.
  • a guarantee can also be given for the data packet D1 sent from an Ethernet component E1 to a TSN component TSN-C.
  • a time guarantee can be given by reserving the time window t1 for the TSN stream S1 in each cycle z1, z2.
  • the data packet D1 arrives in the TSN network 2 without delay and the associated frame F1 is converted into a TSN stream S1, this can be transmitted in the same cycle z1, z2 in the time window t1 provided for this purpose.
  • the conversion to a TSN stream S1 and the configuration of an associated time window t1 it is ensured that the data packet D1 as TSN stream S1 always arrives at the TSN component TSN-C in the time window t1 of a cycle z1, z2. This prevents data packet D1 from being discarded due to excessive data traffic (e.g. from other TSN components).
  • the case for a TSN network “internal” TSN stream can occur that a transmission time is not adhered to. However, this case rarely occurs.
  • the data packet D1 does not originate from the TSN network 2, but from the surrounding Ethernet network 3. Therefore (in contrast to the TSN stream SO from the TSN network 2,
  • a jitter is indicated by the later start of the frame F1 on the Ethernet component E1. This means that the frame F1 arrives even later in the following cycle. The jitter is caused by an inaccurate transmission time at the Ethernet component and individual forwarding delays (for example due to other frames) at each bridge along the communication link over which the frame F1 is routed. Analogously to the first cycle z1, no guarantee for the time window t1 is possible in the second cycle z2 either, which is why a guarantee is given for the time window t1 in the following cycle (not shown).
  • the memory can be emptied in the current cycle z1, z2 (or every couple of cycles), for example by transferring all data packets D1 in frames instead of TSN streams with "best effort" to the TSN over a specified period of time.
  • Network 2 or the memory is simply deleted and the old frame is discarded.
  • the time window can be enlarged by the size of a data packet, so that such an error can be corrected per cycle z1, z2.
  • the respective time windows t0, t1, t2 are thus each reserved exclusively for a TSN stream SO, S1, S4, regardless of whether the TSN stream SO, S1, S4 is sent at all. If the time windows t0, t1, t2 are lined up as shown in FIG. 3, the further frame Fy sent by the further Ethernet component Ey must wait until all time windows t0, t1, t2 have expired. However, if there is enough bandwidth on the communication link between the TSN component TSN-F and the TSN component TSN-C for the further frame Fy and no time window t0, t1, t2 is reserved, then the further frame Fy is immediately sent to the TSN -Component TSN-C forwarded.
  • a TSN stream S1 uses virtual Ethernet multicast receiver addresses, which are correctly interpreted in the TSN network 2, and can thus be sent to the respective TSN component TSN-A, TSN-C, TSN-F in the TSN network 2 be sent as a recipient. It is possible to transmit a TSN stream S1 from the TSN network 2 to the Ethernet network 3, the TSN stream S1 being sent to each Ethernet component E1, E2, E3 in the Ethernet network 3 when using a multicast address would. This is usually not desired, since it also requires a high bandwidth. It could also happen that an Ethernet component E1, E2, E3 cannot receive multicast messages correctly at all.
  • TSN stream S1 is therefore advantageously converted into a frame F1 when it leaves the TSN network 2, its TSN header being replaced by an Ethernet header.
  • the VLAN tag can also be deleted if it is not needed for any other purpose.
  • TSN stream S1 for the permanent, cyclical exchange of a data packet D1.
  • TSN network 2 other, non-cyclical, applications of TSN streams, even temporary TSN streams, are fundamentally also possible. For example, in the event of a (larger) print job, a TSN stream with a bandwidth guarantee could be created between a TSN field device and a TSN printer, which is then cleared down again. If several TSN streams are active on a TSN bridge, the TSN network 2 keeps all given guarantees at the same time.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

Le but de la présente invention est de transmettre un paquet de données (D1) d'un composant ethernet (E1, E2, E3), qui se trouve dans un réseau ethernet (3), à un réseau de communication industriel dans un réseau mixte (1). Selon l'invention, un réseau de communication industriel (2) configuré selon les normes du groupe de travail TSN IEEE 802.1 est utilisé, et au moins une garantie définie dans les normes du groupe de travail IEEE 802.1 TSN est attribuée au paquet de données (D1) en ce qu'une trame (F1) qui contient le paquet de données (D1) est identifiée dans le réseau de communication industriel (2) configuré selon les normes du groupe de travail IEEE 802.1 TSN par un pont TSN (TSN-F) et convertie en un flux TSN (S1) qui contient le paquet de données (D1), et le paquet de données (D1) est transmis à un composant TSN (TSN-C) dans le flux TSN (S1).
EP20764060.8A 2019-08-27 2020-08-25 Transmission de paquets de données Pending EP4005163A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
ATA50740/2019A AT522898A1 (de) 2019-08-27 2019-08-27 Übertragung von Datenpaketen
PCT/EP2020/073721 WO2021037837A1 (fr) 2019-08-27 2020-08-25 Transmission de paquets de données

Publications (1)

Publication Number Publication Date
EP4005163A1 true EP4005163A1 (fr) 2022-06-01

Family

ID=72266288

Family Applications (1)

Application Number Title Priority Date Filing Date
EP20764060.8A Pending EP4005163A1 (fr) 2019-08-27 2020-08-25 Transmission de paquets de données

Country Status (5)

Country Link
US (1) US20230031236A1 (fr)
EP (1) EP4005163A1 (fr)
CN (1) CN114631290B (fr)
AT (1) AT522898A1 (fr)
WO (1) WO2021037837A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3866442B1 (fr) * 2020-02-17 2023-06-07 ABB Schweiz AG Appareil d'interface entre des dispositifs tsn et des dispositifs non tsn
US20230283560A1 (en) * 2022-03-01 2023-09-07 Ge Aviation Systems Llc Converged avionics data network
CN115086239B (zh) * 2022-08-23 2022-11-04 中国人民解放军国防科技大学 一种共享式tsn整形调度装置
CN115665273B (zh) * 2022-10-17 2024-03-12 重庆邮电大学 一种autbus与时间敏感网络的协议转换方法

Family Cites Families (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7515616B2 (en) * 2001-11-24 2009-04-07 Lg Electronics Inc. Packet transmission scheduling technique
CN100433702C (zh) * 2003-09-01 2008-11-12 日本电信电话株式会社 分组通信方法
EP1650905A1 (fr) * 2004-10-25 2006-04-26 Siemens Aktiengesellschaft Procédé pour la gestion de profils de bande passante dans un réseau Ethernet de type Metro (MAN)
CN101212424B (zh) * 2006-12-28 2011-03-23 杭州华三通信技术有限公司 融合了电路交换和分组交换的以太网交换方法与设备
WO2012001616A2 (fr) * 2010-06-27 2012-01-05 Valens Semiconductor Ltd. Procédés et systèmes pour réseaux sensibles au temps
CN102572982B (zh) * 2010-12-08 2014-09-17 同济大学 一种用于异构车辆通信网络的多属性切换判决方法
EP3057273B1 (fr) * 2015-02-13 2019-03-27 Mitsubishi Electric R&D Centre Europe B.V. Procédé pour une mise en forme du trafic dans un réseau
US10044524B1 (en) * 2015-09-18 2018-08-07 Aquantia Corp. Ethernet controller with integrated TSN/AVB control point and time slave
EP3166255B1 (fr) * 2015-11-03 2018-09-26 Robert Bosch Gmbh Commutation de trames ordonnancées dans un réseau embarqué ethernet
CN108353314B (zh) * 2015-11-24 2021-11-09 瑞典爱立信有限公司 切换用于通过提供回程和前传两者（xhaul）连接性的传输网络的传输的至少两个类型的数据信号
US10447606B2 (en) * 2017-04-12 2019-10-15 General Electric Company Time-sensitive networking differentiation of traffic based upon content
US10218628B2 (en) * 2017-04-12 2019-02-26 General Electric Company Time sensitive network (TSN) scheduler with verification
US11072356B2 (en) * 2016-06-30 2021-07-27 Transportation Ip Holdings, Llc Vehicle control system
JP6962697B2 (ja) * 2016-05-27 2021-11-05 パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America ネットワークハブ、転送方法及び車載ネットワークシステム
EP3264725B1 (fr) * 2016-07-01 2021-08-25 Harman Becker Automotive Systems GmbH Convertisseur de classe de réservation de flux
US10425321B2 (en) * 2017-04-25 2019-09-24 Keysight Technologies Singapore (Sales) Pte. Ltd. Methods, systems, and computer readable media for testing time sensitive network (TSN) elements
CN108173614B (zh) * 2017-12-08 2019-08-06 同济大学 一种车载以太网的时间同步和调度方法
EP3499805A1 (fr) * 2017-12-13 2019-06-19 Siemens Aktiengesellschaft Procédé de transmission et / ou de réception de paquets de données
EP3503485B1 (fr) * 2017-12-22 2023-01-25 Marelli Europe S.p.A. Procédé de gestion de trafic réseau dans une reseau à base de commutateurs ethernet, véhicule, interface de communication et produit de programme informatique
EP3522477B1 (fr) * 2018-01-31 2021-08-11 Siemens Aktiengesellschaft Procédé de communication de données dans un dispositif de réseau à base d'ethernet, en particulier industriel, destiné à la mise en uvre dudit procédé, programme informatique ainsi que support lisible par ordinateur
WO2020035133A1 (fr) * 2018-08-14 2020-02-20 Nokia Solutions And Networks Oy Adaptation et mise en forme de qualité de service (qos) de projet de partenariat de troisième génération (3gpp)-réseautage sensible au temps (tsn) (3gpp-tsn) mutuelle
CN110943899B (zh) * 2019-12-13 2022-06-03 重庆邮电大学 一种epa工业总线与时间敏感网络适配系统及方法

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"IEEE Standard for Local and metropolitan area networks--Bridges and Bridged Networks--Amendment 29: Cyclic Queuing and Forwarding ; IEEE 802.1Qch-2017 (Amendment to IEEE Std 802.1Q-2014 as amended by IEEE Std 802.1Qca-2015, IEEE Std 802.1Qcd(TM)-2015, IEEE Std 802.1Q-2014/Cor 1-2015, IEEE Std 802.1Q", IEEE STANDARD, IEEE, PISCATAWAY, NJ USA, 28 June 2017 (2017-06-28), pages 1 - 30, XP068114903, ISBN: 978-1-5044-4095-0, [retrieved on 20170628], DOI: 10.1109/IEEESTD.2017.7961303 *
ANONYMOUS: "IEEE 802.1Q - Wikipedia - Version of 2 June 2018", 2 June 2018 (2018-06-02), XP055788170, Retrieved from the Internet <URL:https://en.wikipedia.org/w/index.php?title=IEEE_802.1Q&oldid=844120352> [retrieved on 20210322] *
ANONYMOUS: "OpenFlow Switch Specification Version 1.3.5", INTERNET CITATION, 26 March 2015 (2015-03-26), pages 1 - 177, XP009522926, Retrieved from the Internet <URL:https://www.opennetworking.org/wp-content/uploads/2014/10/openflow-switch-v1.3.5.pdf> [retrieved on 20200915] *
See also references of WO2021037837A1 *

Also Published As

Publication number Publication date
US20230031236A1 (en) 2023-02-02
WO2021037837A1 (fr) 2021-03-04
AT522898A1 (de) 2021-03-15
CN114631290B (zh) 2024-03-22
CN114631290A (zh) 2022-06-14

Similar Documents

Publication Publication Date Title
WO2021037837A1 (fr) Transmission de paquets de données
EP3695577B1 (fr) Procédé de communication de données dans un réseau tsn, procédé de commande et dispositif
DE60118799T2 (de) Netzwerksvorrichtung zum selektiven datenzeitschlitz verwerfen
WO2016026783A1 (fr) Nœud de distribution, réseau d&#39;automatisation et procédé de transmission de paquets de données sensibles au temps réel et non sensibles au temps réel
EP2676409A2 (fr) Boucles de trajets mpls au niveau réacheminement pour réseaux mpls sans connexion
EP1554839A1 (fr) Procedes, unite interface et noeuds pour utiliser en parallele un reseau de communication pour des applications temps reel et des applications non temps reel
EP2324601A1 (fr) Procédé de transmission de paquets de données dans un réseau de communication et dispositif de commutation
WO2019007516A1 (fr) Procédé de transmission performante de données dans un réseau de données, à conditions en partie en temps réel, et dispositif de mise en oeuvre dudit procédé
DE102017125086A1 (de) Datenübertragungsverfahren und Kommunikationsnetzwerk
WO2008125687A1 (fr) Dispositif de commutation de paquets et réseau de communication local comprenant un tel dispositif de commutation de paquets
EP3035606A1 (fr) Procédé de transmission de données dans un réseau de communication comprenant au moins 2 réseaux locaux virtuels et appareil de communication pour un système d&#39;automatisation industriel
DE102012207952A1 (de) Verfahren zur Übertragung von Daten in einem paketorientierten Kommunikationsnetzwerk und entsprechend eingerichtetes Teilnehmergerät an dem Kommunikationsnetzwerk
WO2016110326A1 (fr) Procédé et dispositif de transmission de données dans un réseau de données avec au moins deux modes de transmission avec fragmentation
EP3854035B1 (fr) Procédé de transmission de données et réseau de communication d&#39;automatisation
DE102010000995B3 (de) Erhöhung der Echtzeitfähigkeit von Ethernetnetzwerken
DE102009050767B4 (de) Verfahren und Vorrichtung zur Datenübertragung
DE102017130167A1 (de) Verfahren zur Optimierung der Ausfallerkennung von Redundanz-Protokollen mit Testdatenpaketen
AT517778B1 (de) Verfahren zur Datenkommunikation mit reduziertem Overhead in einem echtzeitfähigen Ethernet-Datennetzwerk
EP1453252B1 (fr) Transmission de données dans un réseau de données commutable
EP3716537A1 (fr) Procédé de communication de données, noeuds réseau, programme informatique et support lisible par ordinateur
DE10160844B4 (de) System zur Übertragung eines Datenstroms über ein Netzwerk an unterschiedliche Netzwerkprotokolle unterstützende Empfänger
WO2020169280A1 (fr) Procédé de transmission de données, appareil, programme d&#39;ordinateur et support lisible par ordinateur
WO2002078252A2 (fr) Circuit electronique et procede pour interface de communication a memoire tampon pseudo-transit
EP3840303A1 (fr) Dispositif de transmission de données, dispositif récepteur de données et procédé d&#39;émission destiné à la transmission des paquets de données à l&#39;aide d&#39;un tunnel

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20220228

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20230328

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED