[go: up one dir, main page]

WO2020211921A1 - Procédé de transmission de données, nœuds de réseau, réseau, programme informatique et support lisible par ordinateur - Google Patents

Procédé de transmission de données, nœuds de réseau, réseau, programme informatique et support lisible par ordinateur Download PDF

Info

Publication number
WO2020211921A1
WO2020211921A1 PCT/EP2019/059669 EP2019059669W WO2020211921A1 WO 2020211921 A1 WO2020211921 A1 WO 2020211921A1 EP 2019059669 W EP2019059669 W EP 2019059669W WO 2020211921 A1 WO2020211921 A1 WO 2020211921A1
Authority
WO
WIPO (PCT)
Prior art keywords
ports
network
port
network node
fan
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.)
Ceased
Application number
PCT/EP2019/059669
Other languages
German (de)
English (en)
Inventor
Feng Chen
Franz-Josef GÖTZ
Marcel Kiessling
An Ninh NGUYEN
Jürgen Schmitt
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.)
Siemens AG
Siemens Corp
Original Assignee
Siemens AG
Siemens Corp
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 Siemens AG, Siemens Corp filed Critical Siemens AG
Priority to PCT/EP2019/059669 priority Critical patent/WO2020211921A1/fr
Publication of WO2020211921A1 publication Critical patent/WO2020211921A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • 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/40—Bus networks
    • H04L12/4013—Management of data rate on the bus
    • H04L12/40136—Nodes adapting their rate to the physical link properties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H04L41/122—Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
    • 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/0876—Network utilisation, e.g. volume of load or congestion level
    • H04L43/0882—Utilisation of link capacity
    • 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/72—Admission control; Resource allocation using reservation actions during connection setup
    • H04L47/724—Admission control; Resource allocation using reservation actions during connection setup at intermediate nodes, e.g. resource reservation protocol [RSVP]
    • 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
    • H04L2012/4026—Bus for use in automation systems
    • 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/83—Admission control; Resource allocation based on usage prediction

Definitions

  • the invention relates to a method for data transmission in a particularly industrial network with several network nodes, in which protected connections are to be set up for a secured data transmission, with a particular maximum latency being calculated for ports of network nodes, and a fan in the calculation of the latency -In- number of ports is included.
  • the invention relates to a network node, a network, a computer program and a computer-readable medium.
  • the expansions of the TSN Time-Sensitive Networking, successor group of the AVB (Audio / Video Bridging Taskgroup) working group mean that periodic or cyclical transmissions, so-called streams, are particularly protected in the network by a secure, deterministic
  • Various hardware extensions were defined to enable a defined forwarding behavior for the selected protected connections, streams.
  • the stream reservation protocol (SRP, see IEEE 802.1 Q-2018) was introduced to set up protected connections, so that the mechanisms do not have to be set up manually and end devices can log on to a network.
  • An automatic configuration of SRP can guarantee a secure transmission within a certain maximum latency for streams with a successful reservation.
  • TSN includes a multitude of standards.
  • R an example in this context, in addition to reservation (IEEE 802.1 Q-2018, IEEE 802.1 Qcc), is time synchronization (IEEE 802.1 AS-REV) and frame preemption (IEEE 802.1 Q-2018).
  • a sender is also referred to as a talker and a receiver as a listener.
  • the amount of data with the same priority plays a role, as this can potentially delay the transmission.
  • the times until a stream transmission can be started can be accelerated by the preemption mechanism, the pausing of a data transmission with a lower priority and later continuation.
  • all incoming data packets / frames with the same priority from all other ports must be taken into account, since no further differentiation takes place within the class.
  • the stream message describes the amount of data for each stream with reference to a class. In this way, the amount of data currently used in the stream can be determined with a successful registration.
  • a maximum amount of data must be defined for each class. With AVB, for example, this can be 75% (standard value) of the available bandwidth.
  • streams can then be reserved up to the maximum bandwidth.
  • the parameter "msrpMaxFanlnPorts" was defined. By configuring a value smaller than the actually possible total number of receiving ports (n-1 for n ports), the maximum local latency can be reduced because the Number of ports from "msrpMaxFanlnPorts" is considered for the maximum latency.
  • This object is achieved in a method of the type mentioned in that one or more logical topologies for protected connections are set up in the network, and for at least one port of at least one network node it is determined how many of the other ports of the at least one network node are According to the established logical topology or topologies, data of one or more protected connections that are to be forwarded via the at least one port under consideration can be included, and the number of further ports thus determined as the number of fan-in ports in the calculation of the particular maximum latency for the at least one considered port is included.
  • the present invention is based on the knowledge that the logical topology used plays a role in the forwarding of data of protected connections, in particular stream data.
  • Several different logical topologies are possible, especially in networks with several applications. Only those for connecting one Logical topology required ports of a bridge are used and the stream announcement (also referred to as a stream description and given for example by a talker advertise) is only forwarded via these ports.
  • the basic idea of the present invention consists in taking into account or using the logical topologies set up in a network for an adaptation of the worst-case consideration.
  • the worst-case analysis is carried out with a correspondingly adapted, lower number of ports (worst-case number of receive ports).
  • the logical topologies are in a network e.g. by configuring a VLAN ID for each group (for example, one field bus segment with actuators and sensors and the associated, in particular, virtual control) using management or by configuring it through MVRP in the network, before the individual reservations of streams are made.
  • fan-in ports Only those of the other ports are preferred as fan-in ports and are included in the number of fan-in ports, which belong to at least one logical topology to which the respective port under consideration also belongs.
  • a maximum latency is calculated for the at least one considered port.
  • An accumulated latency in particular a maximum accumulated latency, can also be calculated.
  • the ports used in the logical network topologies and the ports to which end devices that communicate via the logical network topologies are connected are taken into account as possible fan-in ports.
  • An individual determination of the latency is carried out for each port of a device, in that each port is considered as a send port.
  • Network ports that are not used in the logical topologies of the (in each case considered) send port are, however, not considered / taken into account. In other words, in contrast to the state of the art, these ports are not included in the number of fan-in ports.
  • the fan-in port number determined according to the invention taking into account the logical topology (s) for at least one transmission port of stream data is then alternatively to a fan-in port number of n-1 (for network nodes with n ports) or alternatively to one Although it is reduced compared to n-1, it is used for the latency calculation in each case for an entire network node (for example in accordance with the “fanln limit”) specified number of fan-in ports.
  • ports that can be sent via the data of protected connections are considered individually and an associated number of fan-in ports is determined individually for them, taking into account the set up logical topology (s), there are also asymmetrical fan-in constellations -Port number possible, which is particularly advantageous in the industrial environment, where there is often a data exchange in a star-shaped constellation namely between a central control (or several provided at a central point, especially virtual controls) and several fieldbus segments is required.
  • more fan-in ports can be used for one or more considered (sending) ports of a network node according to the established logical topology (s) (for example, several virtual networks for the several fieldbus segments with associated control) belong to one or more other considered (send) ports, to which, for example, only one fan-in port belongs.
  • s logical topology
  • each port of a network node can in principle be both a send and receive port (and fan-in port) or can serve both as a send and receive port.
  • the maximum latency is to be determined for a port if data is to be forwarded / sent via this port, i.e. for a port if this has the role of a send or output port for the data transmission under consideration. If you consider a port as a send port, all other ports of the (respective) node - with regard to these ports as send ports - are possible receiving ports, via which data could in principle arrive that are to be forwarded via the port under consideration (send port).
  • a port is (in each case) considered which represents a transmission port for data from one or more protected connections.
  • the further ports in relation to the (each) considered send port are then (each) possible receive ports.
  • the transmit port or ports under consideration which each belong to one or more logical topologies or are located in one or more logical topologies, the number of receive ports that belong to the same logical topology (s) is determined. lie therein), i.e. also to the logical topology or topologies of the send port.
  • cal / virtual topologies which are particularly suitable for Stream reservation are set up in the network, the number of input / receiving ports, which can represent an additional latency for the forwarding device, can be limited or reduced compared to the prior art.
  • the delay in the local network node / the local bridge is adapted to the logical / virtual topology, which results in a lower forwarding time.
  • the shorter forwarding time means that fewer internal resources have to be reserved for a reservation (queue resources). This allows more protected connections, especially streams, to be reserved.
  • network node such as Bridges larger networks may be used or the application cycles may be reduced (increasing the quality of control) by a lower latency.
  • At least one protected connection can be set up which uses the port or ports as send ports, and data can be transmitted via this.
  • a network node can also be integrated into a device, for example a terminal.
  • a latency calculation can also be carried out in the manner according to the invention for one or more transmission ports of network nodes integrated in devices, for example terminals, taking into account one or more logical topologies set up in the network.
  • end devices with integrated network nodes are often given by simple field devices that include at least one sensor and / or at least one actuator or with at least one sensor and / or at least one Actuator connected or connectable, and preferably have an integrated switch.
  • An example of a protected connection is a stream as defined by the Audio / Video Bridging (AVB) Task Group and in particular by the Time-Sensitive Networking (TSN) Task Group in the international IEEE 802.1 standard.
  • a protected connection resources are or are appropriately reserved at the network nodes involved in a manner previously known from the prior art.
  • a protected connection is characterized in particular by a unique identifier assigned to this, in particular a stream identifier, preferably in the form of a stream ID.
  • an adapted number of fan-in ports is determined for several ports, preferably several network nodes, taking into account the logical topology or topologies set up in the network and used for the latency calculation for each of the several ports.
  • a further embodiment is characterized in that, for several ports, several network nodes are determined at how many of the further ports of the respective network node, based on the established logical topology or topologies, data from one or more protected connections via the respective port under consideration are to be forwarded, and the number of further ports determined in this way is included as the number of fan-in ports in the calculation of the maximum latency for each of the several ports considered.
  • each port which, according to the logical topology (s), represents or can represent a send port for data ge protected connections and preferably belongs to a network node with more than two ports.
  • it is therefore determined for each port that represents a send port for data from one or more protected connections according to the set up logical topology or topologies, at how many of the respective wide ren ports of the respective network node due to the established logical topology or topologies data of one or more protected connections that are to be forwarded via the respective port under consideration, and the number of further ports determined in this way as fan-in port number in the Calculation of the maximum latency for each of these ports is included.
  • the required latency information is then available for all transmission ports of data of protected connections, in particular stream data, belonging to the or at least one of the logical topologies set up.
  • each transmission port of each network node it is determined to how many of the further ports of the respective network node according to the established logical topology or topologies data of one or more protected connections that are to be forwarded via the respective port under consideration , and the number of additional ports determined in this way is included as the number of fan-in ports in the calculation of the maximum latency for each of these ports. It should be noted that this can be dispensed with for network nodes that only have two ports. Accordingly, this determination can be made for all network nodes with more than two ports.
  • the respective logical topology or the respective logical topology comprises in an advantageous embodiment a virtual network and / or a stream class or is given by a virtual network and / or a stream class.
  • the respective logical topology or the respective logical topology preferably comprises the entire or only a partial area of the physical network.
  • the or each of the virtual networks (VLANs) then expediently has a VLAN ID or the virtual network or networks are (each) configured by a VLAN ID.
  • Each virtual network usually has an active topology ("Active Topology" - according to IEEE 802.1 Q).
  • the logical topology to be considered is then in particular still restricted by the SRP domain (according to IEEE 802.1 Q).
  • For each stream class is the area in the network in which these is defined by SRP in the form of the SRP domain (see in particular the "SRPdomainBoundaryPort” value in the IEEE 802. IQ standard - Chapter 35 Stream Reservation Protocol (SRP)) and only includes connections between devices that support the respective stream class.
  • SRP Stream Reservation Protocol
  • the or in the case of several of the respective logical topology is also preferably one which is set up for a stream reservation in the network.
  • the respective logical topology can furthermore preferably belong to a coherent group of neighboring terminals and network nodes.
  • At least one logical topology can also be given by a virtual network configured for a group of terminals and network nodes, preferably with an associated VLAN ID. If a plurality of logical topologies are set up in the network, these can each be given by a virtual network configured for a group of terminals and, in particular, network nodes connecting them, preferably with an associated VLAN ID. Then at least one terminal and / or at least one network node can be part of at least two different groups. In other words, there can be overlaps, one or more terminals and / or one or more network nodes can be a member or part of more than one logical topolo
  • gie / associated group or belong to more than one logical topology / associated group.
  • the respective group or groups comprises a fieldbus segment with actuators and / or sensors and at least one associated, in particular virtual, controller.
  • the sensors and actuators must continue to be supplied with data, particularly when the controls (e.g. PLC) of fieldbus systems are virtualized.
  • the controls e.g. PLC
  • PLC controls
  • a logical topology belongs in particular, or a logical topology is defined by the corresponding group of terminals and network nodes.
  • a virtual network and / or a stream class can be set up for each fieldbus segment with control, which or which forms one of the several logical topologies in the network.
  • the procedure according to the invention has proven particularly advantageous for such a constellation.
  • At the transmission ports in particular of network nodes that are between the central industrial PC with the virtualized controls and the respective associated sensors and / or actuators, at least one direction, in particular in the direction of the sensors and / or actuators, can be based on the logical Topologies significantly lower number of ports can be determined.
  • a further advantageous embodiment ensures that data of protected connections to be forwarded via the respective send port of a respective network node cannot arrive at the respective network node via a number of receiving ports that exceeds the number of fan-in ports.
  • Monitoring or checking can be introduced to maintain the maximum number of ports.
  • a stream description can be distributed in the network to set up protected connections. Then every network node that receives a stream description via one of its ports (receiving port) and forwards it via another of its ports (sending port) can check whether the one ne port (receiving port) has already been taken into account for forwarding via the other port (sending port). In the event that one port (receiving port) has not yet been taken into account and the maximum number of ports has already been reached, it is preferred to provide the stream description with an error code.
  • the stream description is passed on (e.g. Talker Adver- tise, see IEEE 802.1) in the network, a check can also be made at each port (potential send port) to determine whether the associated receive port has already been taken into account for the forwarding at this port. If this is not the case and the maximum number of ports has already been reached, the stream description is provided with an error code (Talker Failed) and logins to the stream via this port are excluded. As soon as a reservation of a
  • the process corresponds to the checking of the available bandwidth defined in SRP when the stream description is passed on.
  • a check is made as to whether a registration to the stream would be possible with the current reserved bandwidth. If another stream is registered, this also changes and the check must also be repeated for all streams without a reservation. If the bandwidth for streams is no longer sufficient, the stream description (Talker Advertise) is marked with a Provide an error code (Talker Failed) and prevent the reservation for this stream in the further network via this port and the end devices are informed that the affected streams cannot be made available. Analogous to this, an intelligent "fan-in" check of the receiving ports can be implemented.
  • Another object of the invention is a network node which forms and / or is set up to carry out the method according to the invention.
  • the network node according to the invention can be, for example, a bridge or a switch.
  • the network node according to the invention expediently has at least two ports.
  • the network node according to the invention is furthermore preferably designed and / or set up to calculate a maximum latency, in particular, a number of fan-in ports being included in the calculation of the latency, and to determine how for at least one of its ports many of its other ports, based on one or more logical topologies for protected connections that are set up in a network in which the network node participates, can receive data from one or more protected connections that are to be forwarded via the at least one considered port, and to include the number of further ports determined in this way as the number of fan-in ports in the calculation of the maximum latency for the at least one considered port.
  • the invention also relates to a network, in particular for an automation system and / or manufacturing system, with one or more network nodes according to the invention.
  • the network includes, in particular, at least one, preferably several, controllers and associated field devices.
  • the network is expediently Ethernet-capable; it is in particular an Ethernet-based network.
  • the network or, in particular, at least the network nodes involved are preferably AVB- or TSN-capable, supports or support the device in particular protected connections with reserved network resources at the participating network nodes.
  • AVB and TSN are sufficiently known from the prior art.
  • a reservation protocol for example SRP and / or MSRP, in particular in accordance with IEEE 802.1 Q, is preferably used to set up or establish protected connections, in particular streams.
  • the network node or nodes according to the invention are preferably designed and / or set up accordingly.
  • the present invention also relates to a computer program which comprises program code means for performing the steps of the method according to the invention.
  • the subject matter of the invention is a computer-readable medium which comprises instructions which, when they are executed on at least one computer, cause the at least one computer to carry out the steps of the method according to the invention.
  • the computer-readable medium can be, for example, a CD-ROM or DVD or a USB or flash memory. It should be noted that a computer-readable medium should not be understood exclusively as a physical medium, but rather such a medium can also be present, for example, in the form of a data stream and / or a signal that represents a data stream.
  • FIG. 1 shows a purely schematic representation of an industrial network in which several logical topologies are set up
  • FIG. 2 shows several network nodes of an industrial network in a purely schematic representation
  • FIG. 3 shows the industrial network from FIG. 1, the associated number of fan-in ports being indicated on some transmission ports of some logical topologies;
  • FIG. 4 shows a purely schematic representation of a further industrial network.
  • FIG. 1 shows an industrial, Ethernet-based network with several network nodes B1-B9 in a purely schematic representation.
  • the network nodes B1-B10 support TSN standards, in particular the reservation of network resources for real-time data transmission with guaranteed latency, so that at least the segment of the network spanned by them is TSN-capable.
  • the network nodes B2-B10 are provided by bridges that form a redundant backbone network (segment) with or in a ring topology. Further networks or network segments (or sub-networks) 1, 2, 3 that do not support a TSN are connected to network node B2.
  • the network node Bl is a provided or implemented on the industrial PC 4 vir- Current switch (vSwitch).
  • the further network nodes B2-B10 are separate, physical bridges B2-B10 from the industrial PC 4.
  • programmable logic controllers 6 which are also separate from the industrial PC 4 and located elsewhere in the network, as well as a large number of distributed field devices with an integrated switch 7 or distributed field devices without an integrated switch 8, each comprising a sensor and / or actuator or being connected to such.
  • the controllers 5, 6 and the field devices 7, 8 represent end devices (in some cases end devices 7 with an integrated network node).
  • the actuators must cyclically receive control values in a manner known per se from one of the controllers 5, 6 in order to act accordingly on a technical process not shown in any further detail in the figures.
  • the technical process can be monitored in a well-known manner by means of the sensors. Specifically, these record measured values, which are also to be transmitted cyclically to an associated controller 5, 6.
  • the control values and the measured values are transmitted as user data content of data packets and the transmission must take place in real time.
  • protected connections in this case TSN streams in the sense of IEEE 802.1, are to be set up in the network. This includes the publication of stream announcements or stream descriptions, in particular in the form of talker advertisements, and the reservation of resources at the network nodes involved, specifically both on bridges B1-B9 and integrated switches of the field devices 7.
  • Each respective logical topology 9-13 is provided by a virtual network (VLAN), each with the associated VLAN ID and / or a stream class.
  • VLAN virtual network
  • Each logical topology 9-13 belongs to a coherent group of neighboring terminals 5-8 and network nodes, which in turn includes both the separate bridges B1-B9 and integrated switches. Specifically, each of the logical topologies 9-13 is given by a virtual network (VLAN) configured for a group G1-G5 of terminals 5-8 and network nodes B1-B10 with the associated VLAN ID.
  • VLAN virtual network
  • the group members belonging to the respective logical topology 9-13 are framed by a border line.
  • a solid line is used for the logical topology 9, a dash-dotted line for the logical topology 10, a double-dotted line for the logical topology 11, a dashed line for the logical topology 12 and a dotted line for the logical topology 13.
  • the groups G1-G5 and the associated logical topologies 9-13 are as follows in the exemplary embodiment described here.
  • the group G2 and logical topology 10 also include the vSPS 5 on the right in FIG. 1 on the industrial PC 4, the nodes B1-B7 and the three field devices 7, 8 arranged in a line topology at the bottom left in FIG the first field device 7 of the line is connected to the node B4.
  • the group G3 and logical topology 11 include the vSPS 5 on the left in FIG. 1 on the industrial PC 4, the nodes B1-B7 and the six field devices arranged in a ring topology 8, one of which is connected to node B5 and one of which is connected to node B6.
  • the group G4 and logical topology 12 include the lower controller 6 in FIG. 1, which is connected to the node B8 and the nodes B8-B10 and the five field devices 7, 8, which are connected to the nodes B8, B9 and B10, partly indirectly are connected via further field devices 7.
  • a terminal, specifically the lower physical control 6 in FIG. 1, and several of the bridges B1-B10 are each part of more than one group G1-G5, that is, each belong to more than one logical topology 9-13.
  • Each of the groups G1-G5 comprises a field bus segment with actuators and / or sensors and at least one controller 5, 6.
  • the logical topology 9 is used so that the physical control 6 can communicate with the higher-level virtualized control 5 belonging to group Gl on the industrial PC 4.
  • the logical topology 10 is used so that the three field devices 7, 8 can communicate with group G2 with the associated virtualized controller 5.
  • the logical topology 11 is used to enable the six field devices 7 of group G3 to communicate with the associated virtualized controller 5 on the industrial PC 4.
  • the logical topology 12 is used to ensure that the field devices 7, 8 of the group G4 can communicate with the associated local, physical controller 6 and the logical topology 13 that the three field devices 7, 8 of the group G5 with the associated local len, physical controller 6 can communicate.
  • Group G4 there is a local control with fieldbus communication and, in addition, communication between the local control 6 and the higher-level virtualized control 5 of group Gl.
  • Group G5 means that there is only purely local real-time communication in the associated virtual network (VLAN).
  • the volume of data with the same priority plays a role, as this can potentially delay the transmission.
  • all incoming data packets / frames with the same priority from all other ports P1-P5 must be taken into account, since there is no further differentiation within the class.
  • the stream message describes the amount of data for each stream with reference to a class. In this way, the amount of data currently used in the stream can be determined with a successful registration.
  • a maximum amount of data must be defined for each class. With AVB, for example, this can be 75% (standard value) of the available bandwidth.
  • streams can then be reserved up to the maximum bandwidth.
  • a frame / data packet from each receiving port and the maximum delay until the stream data begins to be sent are taken into account for the latency calculation.
  • the assumed number of fan-in receiving ports corresponds to the number of all ports of the node with the exception of the sending port (total number of ports of the node minus one or for a node with n ports n-1).
  • this creates a very large number of frames that (can) arrive at the same time for the worst-case scenario and therefore a high maximum latency.
  • the nodes B2 to B8 each have 8 ports. It should be noted that only some of the ports P1-P5 are shown in the figures and, for the sake of clarity, not all ports P1-P5 of all network nodes B1-B10 are provided with reference symbols in FIG.
  • the parameter "msrpMaxFanlnPorts" was defined. By configuring a value smaller than the actually possible total number of receiving ports (n-1 for n ports), the maximum local latency can be reduced because the Number of ports from "msrpMaxFanlnPorts" is considered for the maximum latency.
  • the logical topology used plays a role in forwarding data from protected connections, in particular stream data.
  • several different logical topologies 9- 13 possible as shown schematically in FIG. Only the ports of a bridge B2-B7 required to connect a logical topology 9-13 are used and the stream announcement (also referred to as a stream description and given, for example, by a talker advert) is only forwarded via these ports. If there is only one group, possible interference for a stream can only come from other streams in the same group.
  • the interference can come from all groups G1-G5 that use the transmission port (considered in each case). If these do not overlap, there is no influence.
  • FIG. 2 shows a further, purely exemplary industrial network. Only a few network nodes in the form of bridges B1-B7 are shown, but participating terminals are not shown again. In the example according to FIG. 2, three logical topologies 14, 15, 16 are set up in the network. Since these do not overlap in the scenario shown in FIG. 2, there is no mutual influence.
  • the nodes B1, B2 and B5 are again shown separately, with the number of ports P1-P4 used in the respective logical / virtual topology 14-16 being specified in addition to the nodes B1, B2, B5.
  • the invention therefore provides that for at least one port P1-P5 at least one network node B1-B10 is determined at how many of the further ports P1-P5 of the at least one network node B1-B10 according to the established logical topologies 9-16 data of one or more protected connections that are to be forwarded via the at least one considered port P1-P5, and the thus determined number of further ports P1-P5 as fan-in port number in the calculation of the in particular, maximum latency for the at least one considered port P1-P5 is included.
  • each port P1-P5 which, in accordance with the established logical topologies 9-16, represents a send port for data from one or more protected connections (and which in particular to a network node B2-B10 with more than two ports P1- P5 belongs) determines how many of the respective further ports P1-P5 of the respective network node B2-B10 according to the established logical topologies 9-16 data of one or more protected connections that are to be forwarded via the respective port PI PS can be received , and the number of further ports P1-P5 determined in this way flows into the calculation of the maximum latency for each of these ports as the number of fan-in ports.
  • FIG. 3 again shows the network according to FIG. 1, the resulting number of fan-in ports reduced in the manner according to the invention, at least for some ports P1-P5 of some network nodes B2-B10, for example, each directly next to ports P1-P5 is registered.
  • the procedure according to the invention has proven to be particularly advantageous when data exchange in a star-shaped constellation, for example between a central controller or several, in particular virtual controllers, provided at a central location and several fieldbus segments is required.
  • a star-shaped constellation for example between a central controller or several, in particular virtual controllers, provided at a central location and several fieldbus segments is required.
  • Such a constellation is shown purely schematically and by way of example in FIG.
  • an industrial PC 4 on which a total of four virtualized memory-programmable controllers 5 (vSPS) are provided or implemented, and which - as in FIGS. 1 and 3 - has an internal switch B1, via a separate bridge B2 a total of four field bus segments 17-20 is connected.
  • the bridge B2 is to be understood here as an example.
  • Each field bus segment 17-20 can comprise several field devices and further nodes, as shown in FIG.
  • the associated logical topologies 21-24 are here simply indicated by arrows with solid, dashed, dash-dotted or dotted lines.
  • fan-in ports in this case P2, P3, P4 and P5
  • many fan-in ports can belong to one or more fan-in ports (in this case P2, P3, P4 and P5), for example PI of node B2, according to the established logical topologies 21-24 several other considered (send) ports, for example P2, P3, P4 or P5, significantly fewer, in the present case only one, namely PI.
  • Such an “asymmetrical” number of fan-in ports is determined according to the invention and taken into account. The number of fan-in ports determined according to the invention is also entered in FIG. 4 next to the (transmission) port P1-P5.
  • rule / virtual topologies 9-16, 21-24 which are set up in particular for stream reservation in the network, the number of input / receiving ports, which can represent additional latency for forwarding, ge compared to the prior art can be significantly limited or . be reduced.
  • the delay in the local network node / the local bridge B2-B10 is passed on to the logi
  • At least one protected connection can be set up that uses the port (s) P1-P5 as send port, and data can be transmitted via this port in real time .
  • Monitoring or checking can be carried out to maintain the maximum number of ports. In particular, it can be ensured that data of protected connections to be forwarded via the respective send port P1-P5 of a respective network node B1-B10 cannot arrive at the respective network node B1-B10 via a number of reception ports PI PS that corresponds to the number of fan-in ports exceeds.
  • Every network node B1-B10 that receives a stream description via a port (receiving port) P1-P5 and forwards it via another port (sending port) P1-P5 can check whether the one port (receiving port) P1-P5 is suitable for forwarding via which has already been taken into account at the port (send port) P1-P5.
  • the stream description is preferably provided with an error code. As soon as a reservation of a
  • the process corresponds to the checking of the available bandwidth defined in SRP during the transfer the stream description.
  • a check is made as to whether a registration to the stream would be possible with the current reserved bandwidth. If another stream is registered, this also changes and the check must also be repeated for all streams without a reservation. If the bandwidth for streams is no longer sufficient, the stream description (Talker Advertise) is provided with an error code (Talker Failed) and the reservation for this stream in the further network via this port is prevented. Analogous to this, an intelligent "fan-in" check of the receiving ports can be implemented.
  • bridges B2-B7 from FIGS. 1 and 3 and nodes B1-B7 from FIG. 2 are all exemplary embodiments of network nodes according to the invention which are designed and / or set up to carry out the described exemplary embodiment of the method according to the invention.
  • FIGS. 1 to 3 are also exemplary embodiments of networks according to the invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé de transmission de données dans un réseau comprenant plusieurs nœuds de réseau (B1-B10), dans lequel des liaisons sécurisées doivent être établies pour une transmission sécurisée des données avec un temps de latence garanti, un temps de latence étant calculé pour les ports (P1-P5) des nœuds de réseau (B1-B10), un nombre de ports fan-in étant intégré dans le calcul du temps de latence, et des topologies (9-16, 21-24) logiques étant établies dans le réseau pour les liaisons sécurisées. Pour au moins un port (P1-P5) d'au moins un nœud de réseau (B1-B10), il est déterminé, selon les topologies (9-16, 21-24) établies, le nombre de ports (P1-P5) supplémentaires dans lesquels peuvent entrer les données d'une ou de plusieurs liaisons sécurisées, qui doivent être transmises au moyen du ou des ports (P1-P5) considérés. Le nombre de ports (P1-P5) supplémentaires ainsi établi est ensuite intégré en tant que nombre de ports fan-in dans le calcul du temps de latence maximal pour le ou les ports (P1-P5) considérés. L'invention concerne également un nœud de réseau (B2-B10), un réseau, un programme informatique et un support lisible par ordinateur.
PCT/EP2019/059669 2019-04-15 2019-04-15 Procédé de transmission de données, nœuds de réseau, réseau, programme informatique et support lisible par ordinateur Ceased WO2020211921A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2019/059669 WO2020211921A1 (fr) 2019-04-15 2019-04-15 Procédé de transmission de données, nœuds de réseau, réseau, programme informatique et support lisible par ordinateur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2019/059669 WO2020211921A1 (fr) 2019-04-15 2019-04-15 Procédé de transmission de données, nœuds de réseau, réseau, programme informatique et support lisible par ordinateur

Publications (1)

Publication Number Publication Date
WO2020211921A1 true WO2020211921A1 (fr) 2020-10-22

Family

ID=66334406

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2019/059669 Ceased WO2020211921A1 (fr) 2019-04-15 2019-04-15 Procédé de transmission de données, nœuds de réseau, réseau, programme informatique et support lisible par ordinateur

Country Status (1)

Country Link
WO (1) WO2020211921A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220191147A1 (en) * 2019-03-25 2022-06-16 Siemens Aktiengesellschaft Computer Program and Method for Data Communication
DE102022106058A1 (de) 2022-03-16 2023-09-21 WAGO Verwaltungsgesellschaft mit beschränkter Haftung Bestimmung einer reaktionszeit eines eingangs oder eines ausgangs eines eingabe-/ausgabe-moduls

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120314597A1 (en) * 2011-06-08 2012-12-13 Harkirat Singh Enhanced stream reservation protocol for audio video networks

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120314597A1 (en) * 2011-06-08 2012-12-13 Harkirat Singh Enhanced stream reservation protocol for audio video networks

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LEVI PEARSON: "AVnu Alliance(TM) Best Practices Stream Reservation Protocol Revision 1.0 2014 November 3", 3 November 2014 (2014-11-03), XP055597877, Retrieved from the Internet <URL:https://avnu.org/wp-content/uploads/2014/05/AVnu_Stream-Reservation-Protocol-v1.pdf> [retrieved on 20190619] *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220191147A1 (en) * 2019-03-25 2022-06-16 Siemens Aktiengesellschaft Computer Program and Method for Data Communication
US12047299B2 (en) * 2019-03-25 2024-07-23 Siemens Aktiengesellschaft Computer program and method for data communication
DE102022106058A1 (de) 2022-03-16 2023-09-21 WAGO Verwaltungsgesellschaft mit beschränkter Haftung Bestimmung einer reaktionszeit eines eingangs oder eines ausgangs eines eingabe-/ausgabe-moduls

Similar Documents

Publication Publication Date Title
EP3522482B1 (fr) Procédé de communication de données dans un réseau industriel, procédé de commande, dispositif, programme informatique et support lisible par ordinateur
EP3577871B1 (fr) Procédé et dispositif permettant l&#39;orientation modulaire d&#39;un flux avb
EP2413538B1 (fr) Prévention de boucles de transmission dans un réseau en anneau redondant
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
WO2020211921A1 (fr) Procédé de transmission de données, nœuds de réseau, réseau, programme informatique et support lisible par ordinateur
EP2704370B1 (fr) Procédé de transmission de nouvelles dans un réseau de communication industriel pouvant fonctionner de manière redondante et appareil de communication pour un réseau de communication industriel pouvant fonctionner de manière redondante
EP3874333B1 (fr) Procédé de transfert de données à sécurité intégrée, noeud de réseau, programme informatique et support lisible par ordinateur
EP4125253B1 (fr) Procédé de transmission de données temporellement critiques, système de communication et appareil de communication couplée
EP3629550A1 (fr) Procédé de transmission de données dans un réseau de communication industrielle et dispositif de communication couplée
EP3654594A1 (fr) Procédé de transmission de données, appareil de communication, programme informatique et support lisible par ordinateur
EP3522461A1 (fr) Procédé de transfert de données dans un réseau basé sur ethernet pourvu de n uds de communication et n uds de communication
EP4211872A1 (fr) Procédé pour faire fonctionner un réseau
EP3598719A1 (fr) Procédé de communication de données, en particulier dans un réseau industriel, procédé de commande, dispositif, programme informatique et support lisible par ordinateur
EP2159959B1 (fr) Procédé de détermination d&#39;une topologie, composants de réseau et unité centrale
WO2020164810A1 (fr) Procédé de transmission de données, appareil, programme d&#39;ordinateur et support lisible par ordinateur
EP3672163A1 (fr) Procédé de communication de données, appareil de communication, programme informatique et support lisible par ordinateur
EP3906642A1 (fr) Procédé de communication de données et programme informatique
EP3716550A1 (fr) Procédé de communication de données dans un réseau industriel, commande, réseau, programme informatique et support lisible par ordinateur
EP3518480A1 (fr) Procédé de communication de données dans un dispositif de réseau à base d&#39;ethernet, en particulier industriel, destiné à la mise en uvre dudit procédé ainsi que programme informatique et support lisible par ordinateur
EP3422641A1 (fr) Procédé de transmission de nouvelles dans un réseau de communication industriel à fonctionnement redondant et appareil destiné à son exécution
EP4135290A1 (fr) Procédé de transmission des données pour le diagnostic de réseau entre les sous-réseaux connectés indirectement et appareil de communication de couplage
EP3975488A1 (fr) Procédé et appareil de communication destinés à la transmission de données temporellement critiques
EP2515492A1 (fr) Procédé de communication dans un réseau d&#39;automatisation
EP3846395A1 (fr) Procédé de transmission redondante des flux de données dans un réseau de communication, appareil d&#39;infrastructure de réseau et terminal de communication
EP3644555A1 (fr) Procédé de communication de données, en particulier dans un réseau industriel, procédé de commande, dispositif, programme informatique et support lisible par ordinateur

Legal Events

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

Ref document number: 19720461

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19720461

Country of ref document: EP

Kind code of ref document: A1