WO2020125987A1 - Procédé de communication de données, comportant une exigence applicable relative à la fiabilité, appareil de communication, programme informatique et support lisible par ordinateur - Google Patents

Procédé de communication de données, comportant une exigence applicable relative à la fiabilité, appareil de communication, programme informatique et support lisible par ordinateur Download PDF

Info

Publication number
WO2020125987A1
WO2020125987A1 PCT/EP2018/086124 EP2018086124W WO2020125987A1 WO 2020125987 A1 WO2020125987 A1 WO 2020125987A1 EP 2018086124 W EP2018086124 W EP 2018086124W WO 2020125987 A1 WO2020125987 A1 WO 2020125987A1
Authority
WO
WIPO (PCT)
Prior art keywords
redundancy
network
supported
modes
vlan
Prior art date
Application number
PCT/EP2018/086124
Other languages
German (de)
English (en)
Inventor
Feng Chen
Franz-Josef GÖTZ
Marcel Kiessling
An Ninh NGUYEN
Jürgen Schmitt
Original Assignee
Siemens Aktiengesellschaft
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 Aktiengesellschaft filed Critical Siemens Aktiengesellschaft
Priority to PCT/EP2018/086124 priority Critical patent/WO2020125987A1/fr
Publication of WO2020125987A1 publication Critical patent/WO2020125987A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • 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
    • 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]
    • H04L12/4675—Dynamic sharing of VLAN information amongst network nodes
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks

Definitions

  • the invention relates to a method for data communication in a redundantly operable, in particular industrial, network with a plurality of network nodes. Furthermore, the invention relates to a communication device, a computer program and a computer-readable medium.
  • Communication interruptions are a major problem, particularly in industrial networks, which connect a large number of industrial automation devices of an automation system to one another, for example for manufacturing or process automation. Due to messages that are not or not completely transmitted, in particular data frames, a transition of a system into prevent a safe operating state or remain in such a state. In the worst case, there may even be a complete failure of, for example, a production system or an expensive downtime.
  • Real-time communication protocols such as PROFINET, PROFIBUS or Real-Time Ethernet are mainly used for communication in industrial communication networks.
  • a loop-free network topology can be ensured by identifying multiple connections leading to loops and converting a network topology into a tree topology by deactivating selected redundant connections. If a connection or a network node fails, a network reconfiguration can be carried out by determining a new tree topology, taking into account failed connections or components. For this purpose, the network nodes exchange configuration messages with one another with topology information, which is also referred to as Bridge Protocol Data Units (BPDU).
  • BPDU Bridge Protocol Data Units
  • BPDU Bridge Protocol Data Units
  • BPDU Bridge Protocol Data Units
  • RSTP Rapid Spanning Tree Protocol
  • Ethernet is used so each that a real-Z eitübertragung is possible through the different fieldbus systems.
  • redundancy mechanisms such as the High Speed Redundancy Protocol (HRP) for ring redundancy with switchover.
  • HRP High Speed Redundancy Protocol
  • ring topology is often built up in higher-level networks in industry.
  • meshed networks usually only one way is activated, e.g. by RSTP to resolve loops.
  • the data for best effort communication is transferred to every link in the network.
  • IP applications often overlay TCP to compensate for the failure of a single link if packet loss is to be avoided.
  • Ethernet By expanding Ethernet in the AVB Task Group (see in particular IEEE 802.1), it is possible to protect a stream (periodic transmission of data frames) in a network and to guarantee transmission within a certain latency.
  • a reservation protocol for automatic configuration was defined for this.
  • the reservation protocol checks all network resources required for data transmission, for example filter database entries (abbreviated FDB entries), queue memory, link bandwidth, in particular at the send port, and / or other resources at the participating network nodes on the transmission path and, if available, reserved.
  • FDB entries filter database entries
  • Time Sensitive Networking is a series of standards that extends the bridging standard IEEE 802. IQ to include mechanisms for the transmission of real-time-critical data over Ethernet networks.
  • the standards mentioned include, for example, time synchronization (IEEE 802. lAS-Rev), frame preemption (IEEE 802.1Qbu) and reservation (IEEE 802.1Qca, IEEE 802.1Qcc) and other standards.
  • shapers such as the so-called credit-based shapers (abbreviated to CBS, see in particular IEEE 802.1Qav), were introduced. This ensures that there is a certain pause after each data frame when sending stream data. This enables the next network node, for example the next bridge on the transmission path, to ensure that there is no burst of stream data and that the incoming data amount corresponds to the reserved bandwidth.
  • the object of the present invention is to provide a method for data communication in a redundant operable, in particular industrial network, with which a high level of reliability is possible while at the same time particularly efficient use of available resources.
  • the first-mentioned object is achieved by a method for data communication in a redundantly operable, in particular industrial network with a plurality of network nodes, where data is preferably transmitted in the context of and / or for an application between at least two communication partners, in particular in the form of terminal devices where there is a given requirement for the reliability of data transmission and two or more different redundancy modes are to be supported in the network,
  • the redundancy modes supported in the network are each communicated to an associated virtual network in which the respective redundancy mode can be used, in particular to at least one of the at least two communication partners,
  • a suitable redundancy mode is automatically selected in the light of the given requirements for the reliability, and - Preferably data between the at least two communication partners are transmitted via the virtual network belonging to the automatically selected redundancy mode.
  • the basic idea of the present invention is to support a number of different redundancy modes in a particularly industrial network, and to communicate these along with associated virtual networks in which they can be used, preferably at least one of the communication partners involved.
  • Each redundancy mode is preferably assigned at least one, in particular exactly one virtual network, in particular base VLAN or at least one, in particular exactly one base VID.
  • the different virtual networks belonging to the respective redundancy mode are preferably base VLANs (English: Base VLANs), in particular in the sense of IEEE 808.
  • IQ, or the different virtual networks belonging to the respective redundancy mode preferably each represented and / or identifiable and / or defined by a base VLAN (base VLAN) and / or base VID (base VID).
  • a mode which is suitable in the light of the specified requirement of the respective application is selected automatically and the data is expediently transferred between the communication partners involved via the at least one virtual network belonging to the selected mode, in particular a special VLAN or base VID basis.
  • the redundancy modes and associated virtual networks can be communicated, for example, by sending messages with the corresponding content.
  • a mode in which no failure safety is offered represents a redundancy mode in the sense of the present application, in particular a redundancy mode with zero redundancy or a mode that does not offer redundancy.
  • a network that supports, for example, a mode or in which a mode is provided or implemented in which redundancy is guaranteed, and a mode in which no redundancy is guaranteed represents a network in which two redundancy modes are supported or are provided or implemented.
  • the procedure according to the invention makes it possible for an application or, in the event that several applications want to use a network, to communicate each application its request for communication.
  • the existing redundancy capabilities can be described by the network itself. Mapping can then be used to select a redundancy mode that is sufficient for the respective application. As a result, only the mechanism that is really needed by the application can be used. This saves resources in the network. In particular, either the use of a weaker network to meet all requirements is possible, or the use of other applications in the same network, since resources are still available.
  • Another advantage of the invention is that the operation of application (s) and network is decoupled.
  • the network can be upgraded and changed regardless of the application or applications. If the application (s) has changed requirements, they can also be set independently of the network.
  • commissioning in particular when setting up streams for real-time, secure data transmission, the newly introduced description of the network capabilities is then used to map the redundancy mechanisms or modes provided by the network.
  • the data that are to be transmitted between the communication partners involved which are preferably given by terminal devices, are preferably sensor data and / or control values for one or more actuators of one of these that are detected by an automation system.
  • the communication partners can be, for example, one or more in particular programmable logic controllers and / or IO devices or the like.
  • End devices are to be understood in particular in a manner known per se to be devices which represent an initial source and / or a final destination of data, in particular data frames, in a network, which are transmitted or are to be transmitted in the network. They are preferably end stations in the sense of IEEE802.1Q.
  • the procedure according to the invention is particularly advantageous in the event that several applications want or need to use a (physical) network.
  • data are to be transmitted between at least two communication partners belonging to the respective application, wherein there is a predetermined requirement for the reliability of the data transmission for each application, and
  • a redundancy mode is automatically selected from the supported redundancy modes in the light of the requirement for failure safety that belongs to the respective application.
  • the redundancy modes supported in the network, in addition to the associated virtual networks, are preferably communicated to at least one of the communication partners of the respective application.
  • the message is particularly preferably sent to one or the communication partner (talker) representing the transmitter and / or to one or the communication partner representing the transmitter.
  • At least one redundancy mode is preferably assigned a specific redundancy mechanism or a specific redundancy method, or at least one redundancy mode includes one or such.
  • several redundancy modes are each assigned to the redundancy mechanism or redundancy method. Purely by way of example for redundancy mechanisms or redundancy methods, end-to-end, switchover, ie switching, and / or segment protection redundancy mechanisms or methods are mentioned.
  • At least one redundancy mode is not assigned a redundancy mechanism or method, or at least one redundancy mode is not or does not include such, which then in particular represents at least one redundancy mode with zero redundancy or without redundancy.
  • one or more redundancy modes are given or defined by a specific redundancy method or a specific redundancy mechanism or the lack thereof.
  • one or more redundancy modes in addition to a redundancy method or mechanism, such as switchover, end-to-end or segment protection, or the lack of such include additional functions and / or aspects.
  • Examples of additional functions are an auto repair function and / or the need for registration of MAC addresses and / or support for frame replication and elimination by at least some network nodes, in particular in accordance with IEE802.1CB.
  • a first redundancy mode supported in a network can be characterized in that a switchover redundancy method is or can be used in it and an auto-repair function takes effect, in particular in the event of a fault or defect in a network node, and that it is necessary to register MAC addresses.
  • a second redundancy mode can, for example, be characterized in that an end-to-end
  • Redundancy method or mechanism is or can be used, and an auto repair function takes effect, but it is not necessary to register MAC addresses.
  • Further redundancy modes can be distinguished by further combinations of redundancy processes and any additional functions, or also by the fact that they do not include a redundancy method, but other functions.
  • a network in which the method according to the invention is carried out is preferably an Ethernet-based or Ethernet-capable network, preferably in the sense of IEEE802.3.
  • a network is to be understood as a physical network without further designation.
  • One or more virtual networks can be set up in a physical network in a well known manner.
  • VLAN IDs belonging to the respective virtual network
  • VIDs are also referred to as VIDs for short.
  • the virtual networks in which the respective redundancy mode can be used are preferably so-called basic virtual networks or base VLANs or base VIDs, in particular in the sense of IEEE802.1Q, each of which has one or more IDs (see ), in particular VID (s).
  • At least one, preferably exactly one virtual (base) network is administratively available for each supported redundancy mode. If the virtual network belonging to the respective base VLAN is used for data transmission, the forwarding mechanism belonging to the respective basic VLAN automatically takes effect, preferably according to IEEE802.1Q, and the associated redundancy mode or this (if applicable ) associated redundancy mechanism or the redundancy procedure associated with this (if applicable). According to
  • each VID is assigned exactly one base VID, which defines the forwarding mechanism.
  • these are in particular STP, RSTP, MSTP and the forwarding developments Shortest Path Bridging (SPB).
  • SPB Shortest Path Bridging
  • Each virtual network is assigned an associated forwarding mechanism via the associated base VLAN, which serves as the basis for a redundancy mode.
  • the associated redundancy mode is configured in the respective virtual network.
  • the supported redundancy modes and associated virtual networks are transmitted in the form of network availability vectors.
  • the supported redundancy modes and associated virtual networks in the form of network availability vectors are preferably transmitted to at least one of the at least one two communication partners belonging to the respective application.
  • the network availability vectors can also be referred to as network availability vector and abbreviated to NAV.
  • the network availability vectors (NAVs) are preferably bit vectors which are given in a manner known per se by a sequence of bits with assigned meaning.
  • the NAVs for all available redundancy modes are sent in a packet in succession as TLV (Type Length Value).
  • TLV Type Length Value
  • each network availability vector specifies at least one redundancy mechanism or redundancy method or indicates that such is missing , in particular in the form of a bit value representing the mechanism or the method or the lack of such a bit value, and preferably an indication of whether or not an auto repair function is activated in the event of a failure, in particular of a network node, and / or whether a registration of MAC address is necessary or not.
  • a bit sequence that, for example, a bit of a corresponding vector indicates whether or not a registration of a MAC address is necessary, for example two bits following it can represent a total of four different redundancy mechanisms or redundancy methods, and one thereon The following bit indicates whether an auto repair function is activated or deactivated. For example, a 0 bit can indicate that no such function is supported or one is deactivated, and a 1-bit to indicate the existence or being activated of such a function. The same applies to the need to register MAC addresses.
  • At least some of the network nodes support frame replication and elimination, in particular in accordance with IEEE802.1CB.
  • a corresponding notification or notices are preferably sent to at least one of the at least two communication partners of the or each application.
  • the network availability vectors include the information as to whether at least some of the network nodes support frame replication and elimination or not.
  • at least one further bit field can be provided in the vector or vectors, for example in front of the bit field for the need to register MAC addresses.
  • a bit of 0 or 1 can then be used to indicate whether frame replication and elimination (abbreviated FRER for Frame Replication and Elimination for Reliability. See in particular IEEE802.1 CB) is not supported or possible, or is it the case .
  • At least one of the two communication partners of the or each application is informed whether at least one of the at least two communication partners of the or the respective application is performing frame replication and elimination, in particular in accordance with
  • At least one sending communication partner who wants to send data to at least one receiving communication partner is informed whether the at least one receiving communication partner supports frame replication and elimination or not. If frame replication and elimination is supported by the recipient, that is to say the data sink or the destination, this is not necessary by the network nodes via which the frames are forwarded to the recipient. This is particularly due to the fact that the elimination or the filtering out or also the discarding of duplicate frames based on redundancy can then be carried out directly at or by the recipient. If this function is not supported by a receiver, the last network node in front of the receiver, which can also be referred to as a receiving node on the receiving side, has to eliminate replicated or duplicated frames for redundancy reasons in order to avoid problems.
  • transmitters are also referred to as talkers and receivers as listeners.
  • the virtual networks belonging to the supported redundancy modes preferably together with one or more IDs, in particular VIDs, preferably at least one of the at least two communication partners of or depending on the application as type-length values, in particular Configuration type length values are transmitted.
  • the transmission is preferably carried out together with the information about the redundancy mode belonging to the respective virtual network, in particular Base VLAN. It has proven to be particularly advantageous if the associated virtual network, in particular Base VLAN, in which the mode can be used, preferably together with the one or more belonging to the virtual network, if a bit vector with information about an available redundancy mode IDs, in particular VID (s), are transmitted via or in a TLV following the bit vector in particular.
  • a bit vector with the specification of a redundancy mode with a TLV after it with the information about an associated virtual network, in particular Base VLAN along with IDs or IDs belonging to it, can be transmitted, for example, as part of an LLDP message or form one .
  • IDs belonging to the virtual networks are communicated.
  • a virtual network in particular base VLAN or base VLAN, can either include only one ID, in particular VLAN ID or VID, or can also include several IDs, in particular VLAN IDs or VIDs. If several IDs belong to a virtual network, these are expediently all communicated either together with the corresponding redundancy mode and the virtual network, or this information is obtained in another way, for example from a central configurator or the like.
  • each VID is clearly assigned a base VLAN. The configuration of the assignment can follow, for example, the standardized management objects.
  • a number of IDs will be present in particular if, for a redundancy mode, a number of paths, in particular disjoint paths, at least in sections, are preferably used simultaneously for the forwarding of data frames. Then, each path has its own VID, which in particular can be used to control or control forwarding.
  • the redundancy modes supported in the network and in particular the associated virtual networks are communicated by at least one preferably all network node, in particular via a protocol which is suitable for exchanging messages between adjacent network devices.
  • the link layer discovery protocol in particular in accordance with IEEE802.1AB, can be used as a protocol and / or for example Reservation protocol, preferably the Stream Reservation Protocol (SRP), in particular according to IEEE 802.1 Q, and / or MSRP or the like.
  • SRP Stream Reservation Protocol
  • At least one, in particular all network nodes periodically send messages with which at least one, preferably exactly one of the supported redundancy modes is communicated together with the associated virtual network.
  • Corresponding information transfer can in turn take place in the form of network availability vectors, which can be part of messages that are sent in the context of appropriate protocols or also represent own messages.
  • the communication partners receive the information about available redundancy modes and associated virtual networks from a location other than one or more network nodes. This can also come from a central configurator, for example.
  • a further embodiment is characterized in that the redundancy modes supported in the network and in particular the associated virtual networks are particularly preferably communicated directly to at least one of the at least two communication partners of the or the respective application by a preferably central configuration unit.
  • the automatic selection of a suitable redundancy mode for the or each application from the supported redundancy modes includes or is carried out by a mapping, which has proven to be a particularly suitable option.
  • Redundancy in a network means in particular that alternative or additional devices or paths within the network infrastructure are available that can be used in the event of a failure or error or unavailability to continue to ensure data transmission.
  • the fact that a redundancy mode or redundancy method or mechanism is supported means, for example, that in the event of a failure or error or the unavailability of one or more network devices or paths in particular, an automatic change to one or more other devices or Paths done.
  • the various redundancy mechanisms or methods supported in accordance with the invention in a network can in principle be any method known from the prior art.
  • Switchover redundancy mechanisms such as the Rapid Spanning Tree Protocol (RSTP) and / or the Multiple Spanning Tree Protocol (MSTP, see in particular IEEE802.1Q) and / or ring MRP (MRP for media redundancy protocol) are examples in this context stands, see in particular IEC62439) and / or the shortest path.
  • RSTP Rapid Spanning Tree Protocol
  • MSTP Multiple Spanning Tree Protocol
  • MRP ring MRP
  • a bumpless mechanism an end-to-end redundancy mechanism between transmitter and receiver or several end-to-end redundancy mechanisms in the network between network components can be supported.
  • frame replication and elimination redundancy mechanisms may be mentioned, which preferably comprise segment protection.
  • FRER frame replication and elimination for reliability
  • Redundancy modes comprising two or more different redundancy mechanisms are preferably supported or implemented and can be used via the associated virtual network, so that there is a high degree of flexibility.
  • a further advantageous embodiment is accordingly characterized in that a protected connection is set up for the data transmission between the or the respective at least two communication partners of the or each application, for which network resources are preferably reserved at participating network nodes.
  • the data transmission is then preferably carried out via the or the respective protected connection, in particular in the form of a stream and / or using reserved resources.
  • the network or, in particular, at least the network nodes involved are preferably AVB or TSN-capable, in particular support or support the establishment of protected connections reserved network resources at the participating network nodes. This is well known from the prior art.
  • the newly added description of the network redundancy functions is preferably used during the setup of the stream (s) mapping to the mechanisms provided by the network.
  • a corresponding available redundancy mechanism in the form of a redundancy mode - possibly with additional functions - can be selected that fulfills the requirements (possibly as well as possible).
  • the base VLAN to be used and thus the VID or the VIDs to be used result from the selection of the redundancy mode.
  • Another object of the invention is a communication device. This is designed and / or set up to carry out a method accordingly to the preceding description.
  • the device according to the invention is preferably designed and / or set up to support a plurality of network redundancy modes and / or to periodically send out messages with which the supported redundancy modes are each known with an associated virtual network in which the respective redundancy mode can be used can be made or made known.
  • a communication device is preferably a network infrastructure device, for example in the form of a bridge or a switch. It has proven to be particularly expedient if a protocol is supported for the announcement which is suitable for exchanging messages between neighboring network devices, particularly preferably the Link Layer Discovery Protocol, in particular in accordance with IEEE802.1AB.
  • the device according to the invention can be designed and / or set up to receive information about the redundancy modes supported in the network in each case with an associated virtual network, in which the respective redundancy mode can be used, and for at least one application, within the scope of which and / or for the data to be sent and / or received by the device, a predetermined requirement for the reliability to determine the data transmission, and to automatically select a redundancy mode suitable from the redundancy modes in the light of the specified requirements for fail-safety.
  • a communication device is in particular a terminal device, which represents an original source and or a final destination of data.
  • the invention also relates to an industrial network, in particular, which comprises one or more communication devices according to the invention.
  • the invention further relates to a computer program which comprises program code means for carrying out the steps of the method for data communication according to the invention.
  • the subject of the invention is a computer-readable medium which comprises instructions which, when executed on at least one computer, cause the at least one computer to carry out the steps of the method according to the invention for data communication.
  • 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 only be understood as a physical medium, but also, for example, in the form of a data stream and / or a signal which represents a data stream.
  • FIG. 1 is a purely schematic partial representation of an industrial, Ethernet-based network with several network nodes
  • FIG. 2 shows a table with the possible combinations that result from the redundancy mechanisms supported in the network, the CB (FRER) support on the part of the network nodes, the auto repair function and the CB (FRER) support on the part of the end devices;
  • FIG. 3 shows a purely schematic representation of a NAV and a bit for FRER support on the part of the end devices, which together form an Availability Selector (AS);
  • AS Availability Selector
  • FIG. 4 shows a purely schematic representation of a configuration TLV with the base VLANs belonging to the redundancy mechanisms and VIDs belonging to them;
  • FIG. 5 shows the partial representation according to FIG. 1 for the case in which FRER with segment protection is selected as the redundancy mode
  • FIG. 6 shows the partial representation according to FIG. 1 in the event that an end-to-end redundancy mode is selected.
  • FIG. 1 shows a purely schematic partial illustration of an industrial Ethernet-based network with several network nodes 1, which are given in the form of bridges in the exemplary embodiment shown.
  • two communication partners can be recognized in the form of end devices, of which one communication partner 2 would like to send data to another communication partner 3.
  • the communication partner 2 represents a transmitter and is also referred to here as a talker.
  • the communication partner 3 which should be the recipient of the data sent, is referred to below as the listener.
  • the network which is only shown in part, can comprise or comprise a large number of further network nodes 1, and further communication partners can participate or participate in the network.
  • the talker 2 would like to periodically send data frames in real time with guaranteed quality of service, in particular guaranteed maximum latency, to the listener 3 in the context of or for a control application for an industrial process (not shown). Accordingly, a TSN stream should be set up between Talker 2 and Listener 3.
  • a stream announcement with a stream description, in particular a talker advert is sent by the talker 2 in a well-known manner and forwarded via the network node 1 to the listener 3, who can log on to the stream, whereby for the secure transmission supply at the participating network nodes 1 network resources, e.g. bandwidth and / or filter database entries and / or queue memory, if they are available.
  • network resources e.g. bandwidth and / or filter database entries and / or queue memory
  • the application has a predetermined, high requirement for the reliability of the data transmission.
  • the talker 2 and the listener 3 are connected to one another via two coupled ring segments SI and SII and there are at least partially disjoint paths de PI and P2 via which the talker 2 and the listener 3 are connected and communicate with one another can. Since at least two redundant paths are available, reliability / redundancy can be guaranteed.
  • the cloud 4 in FIG. 1 indicates the redundant path domain.
  • the network supports various redundancy modes Ml-Mn (see Figure 3).
  • Each redundancy mode Ml-Mn includes a specific redundancy mechanism / a specific redundancy method and optionally further functions, in this case specifically whether the network node 1 and thus also the edge port at which the listener 3 is present at the next network node 1, frame replication and Elimination support or this function is activated and / or available or not, the need to register the MAC addresses and an auto repair function.
  • the table according to FIG. 2 shows various possible combinations of redundancy mechanisms and the optional additional functions auto repair and FRER support through edge ports.
  • the abbreviation ES stands for end station, that is to say end device (talker 2 and listener 3), the abbreviation EP for edge port, specifically relates to the edge port of the network node 1 at which the talker 2 or listener 3 is located on the transmitter or receiver side gen edge network node 1 is present.
  • N stands for "None", i.e. no redundancy or with a redundancy of "zero”
  • SWO for switch chover i.e. for a switchover redundancy mechanism, as can be provided by RSTP, MSTP or SP
  • E2E for End-2 -End i.e. end-to-end redundancy
  • SP for segment protection i.e. segment protection, especially FRER with segment protection.
  • the table does not take into account whether or not it is necessary to register MAC addresses.
  • the different redundancy modes Ml-Mn with the associated redundancy mechanisms or methods can be used in different basic virtual networks (Base VLANs) that are administratively available in the network. These can simply called Base VLAN1, Base VLAN2, ..., Base VLANn.
  • Base VLANs basic virtual networks
  • An embodiment of the method according to the invention is carried out in order to enable a high level of reliability with optimal use of available resources, in particular also in the case of using the network by several applications.
  • the redundancy modes Ml-Mn supported in the network with the respectively associated virtual network specifically the assigned base VLANs in which the respective redundancy mode Ml-Mn can be used, are the talker 2 communicated.
  • all network nodes 1 periodically send LLDP messages (LLDP stands for the well-known Link Layer Discovery Protocol) with which end devices are informed about the network availability options.
  • LLDP stands for the well-known Link Layer Discovery Protocol
  • the talker 2 receives corresponding messages from the network node 1 which is closest to it and which can also be referred to as a transmitter-side edge node.
  • the network availability options in particular the supported redundancy modes Ml-Mn, are transmitted in the form of network availability vectors NAV, which are given by bit vectors.
  • FIG. 3 shows, purely schematically, an example of a NAV which represents a redundancy mode Ml-Mn.
  • the NAV comprises five consecutive bits 5-9, the first bit 5 indicating whether the network node 1 and thus also the edge port at which the listener 3 is connected to the next network node 1 support frame replication and elimination FRER or this function is activated and / or available or not (in the figure it is indicated with "EP” that the information relates to the "edge port", that is to say edge port), the second bit 6 indicates whether a registration of the MAC addresses is necessary or not, the third and fourth bits 7, 8 an available one
  • the absence of a redundancy mechanism with N or one of the three redundancy mechanisms mentioned, i.e. switchover SWO, end-to-end E2E and segment-protected SP, is indicated in each case by the bit sequence 00 , 01 10 and 11 in that order.
  • network 1 can be communicated or defined via bits 6-9, which is abbreviated to ViN in FIG. 3.
  • redundancy mode Ml-Mn can accordingly be communicated in or with a NAV.
  • NAV redundancy mode
  • several NAVs are sent in succession in one packet as a TLV.
  • TLV time-to-live
  • IEE802.1CB is supported or not. This message is not sent by the network nodes 1 to the end devices, such as the NAVs, but this information is provided locally by the listener 3 or talker 2 and evaluated locally. It also applies here that 0 indicates that this is not supported and 1 that there is support.
  • a NAV together with bit 6 with the information about the terminal-side FRER support is also referred to in the present case as the availability selector or availability selector AS.
  • the Availability Selector AS thus results from the capabilities of the network together with the support of CB / FRER according to IEE802.1CB in the end device, specifically the list ner 3 or talker 2.
  • Each base VLAN in which a certain redundancy mode Ml-Mn can be used, comprises one or more VIDs which are to be used for data transmission, in particular the forwarding of data frames from the talker 2 to the listener 3 . are.
  • the network describes what VIDs belong to which base VLAN.
  • corresponding configuration TLVs TLV stands for Type Length Value in a well-known manner
  • FIG. 4 shows the structure of a configuration TLV in a purely schematic manner, in which a base VLAN (abbreviated in the figure with B VLAN) is contained with the associated VID (s).
  • the TLVs with the base VLANs and associated or associated VIDs are each periodically sent together with the NAVs (see FIG. 4) by the network node 1, that is to say also via the LLDP messages.
  • a NAV is followed by a TLV with the associated Base VLAN and the VDI (s) of the Base VLAN.
  • the NAV therefore precedes the TLV like a header. This is to be understood as playful and therefore not restrictive.
  • a redundancy mode Ml-Mn that is suitable in the light of the requirements for fail-safety specified by the application is automatically selected and data frames are then automatically selected between the two communication partners 2, 3 Redundancy mode Ml-Mn associated virtual network transmitted.
  • the selection is made by mapping the requirement or requirements of the application and the notified network availability, together with the local capabilities of the terminal device 2, 3 itself.
  • a redundancy mode with SP in the present case FRER with segment protection, is selected as the redundancy mechanism for the real-time transmission of the control data.
  • This particularly robust mechanism is chosen because the Talker 2 and Listener 3 are comparatively far from each other, for example at different ends of a larger system.
  • the base VLAN belonging to this mode and communicated to the talker 2 together with the NAV belonging to the mode, or the associated VID or the associated VIDS, are then assigned by the talker 2 when the stream is set up for the real-time transmission of the control data the listener 3 used.
  • the VID which belongs to the automatically selected redundancy mode Ml-Mn, is contained in the Talker Advertise and the Listener Join. If several VIDs are included, i.e. several paths have to be set up, a talker advertise and listener join is carried out for each path and thus each VID, which then contain one of the VIDs.
  • FIGS. 5 and 6 the situation resulting for two different redundancy mechanisms for the constellation according to FIG. 1 - purely by way of example and schematically - is illustrated.
  • FIG. 5 shows the situation for the use of frame replication and elimination for redundancy (FRER) and segment protection, that is to say for the redundancy mode selected by the control application (the situation after the stream setup and activation of the is shown Forwarding).
  • FRER redundancy
  • segment protection that is to say for the redundancy mode selected by the control application (the situation after the stream setup and activation of the is shown Forwarding).
  • the transmitted data frames are transmitted from the talker 2 to the first network node 1 using a first VID0. This is indicated by an arrow with a solid line. It should be noted that in the purely schematic FIG. 5 the data frames are not shown, but only arrows which represent their transmission path.
  • the incoming data frames are duplicated from the network node 1 closest to the talker 2 and the one frame is forwarded in each case via the lower path PI and the second frame in each case via the upper path P2, the VIDs VIDI and VID2 being used.
  • Data transmission using VIDI is indicated by arrows with dash-dotted lines, that of VID2 by arrows with dashed lines.
  • the network node 1 is designed and / or set up to carry out the duplication.
  • a stream merge function with duplicate elimination takes place at the four network nodes 1 which connect the two segments SI and SII to one another and at the network node 1 closest to the listener 3, that is to say the receiver-side edge node 1.
  • the first incoming duplicate is duplicated for each further path and forwarded with the required VID of the respective path on the path or paths, and all further incoming duplicates are discarded.
  • the corresponding places are marked with a circle symbol, which is provided with the reference number 11.
  • a network node 1 fails on path PI or path P2, the other path PI, P2 can be used, where occur nits Z at any Shift.
  • the other path PI, P2 can be used, where occur nits Z at any Shift.
  • a duplicate arrives at the locations provided with the reference number 11, which is treated as the first incoming duplicate and is accordingly itself duplicated again for each further path and provided with the corresponding VID of the path. Since no further duplicates arrive due to the error, they do not have to be discarded.
  • redundancy mode is also automatically selected for this, and data are transmitted using the virtual network associated with the redundancy mode, in particular base VLAN.
  • a mode can be selected which includes end-to-end redundancy E2E.
  • Talker 2 then duplicates each of the data frames to be sent periodically via the stream.
  • One frame is forwarded to path ner 3 via path PI, that is to say in FIG. 6 below, using the VIDI of the base VLAN for end-to-end redundancy E2E.
  • This is indicated in FIG. 6 by dash-dotted arrows pointing from the talker 2 to the listener 3.
  • two frames leave the talker 2 and two frames arrive at the listener 3, which is indicated by the two arrows between the Talker 2 and the first network node 1 and the last network node 1 and the listener is indicated.
  • the respective second data frame is sent periodically to the listener 3 via the path P2, that is to say in FIG. 6 above, using the VID2 of the base VAN for the end-to-end redundancy E2E (indicated by arrows with a broken line).
  • a network node 1 fails on path PI or path P2, the other path PI, P2 can be used in each case. Since the transmission is interrupted in the event of an error due to the failure of network node 1, the duplicated frames in network node 1 are discarded on network node 1 that preceded the path.
  • a video transmission application for which image data are to be transmitted from the talker 2 to the listener 3 may be mentioned as an example of an application in the light of which a switchover redundancy mechanism SWO would be suitable in terms of the reliability. Since a short failure of the video sequence or a jerk can be accepted, a switchover time can be accepted and switchover can be used. Then a virtual network belonging to a mode with switchover redundancy SWO is used. The associated base VLAN and the associated VIDs have been communicated to the talker via the LLDP message with the corresponding NAV and TLV.
  • an application in which data that are sent from the talker 2 to the list ner 3 can subsequently be evaluated completely without a security mechanism against failure, that is to say without a redundancy mechanism.
  • N a virtual network, in particular Base VLAN, is used for the data transmission, which belongs to a mode without a redundancy mechanism.
  • the base VLAN and the associated VID since there are no additional, redundant paths, it is in this one If there is only one VID), the talker has also been informed of an associated LLDP message with NAV and TLV.
  • both the network nodes 1 read and the terminals 2, 3 represent exemplary embodiments of communication devices according to the invention. They are designed and / or set up to carry out the described exemplary embodiment of the method according to the invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)

Abstract

L'invention concerne un procédé de communication de données dans un réseau à fonctionnement redondant qui comporte plusieurs nœuds de réseau (1). Selon le procédé, des données doivent être transmises entre au moins deux partenaires de communication (2, 3), une exigence applicable relative à la fiabilité de la transmission de données existant, et deux ou plusieurs modes de redondance (M1-Mn) étant supportés dans le réseau, * les modes de redondance (N, SWO, E2E, SP) supportés dans le réseau étant communiqués chacun à l'aide d'un réseau virtuel associé (B VLAN), notamment à l'un des au moins deux partenaires de communication (2, 3), le mode de redondance (M1-Mn) pouvant être utilisé dans ledit réseau virtuel associé, * un mode de redondance (M1-Mn) approprié étant choisi automatiquement parmi les modes de redondance (M1-Mn) en tenant compte de l'exigence applicable relative à la fiabilité, et * des données étant transmises de préférence entre les au moins deux partenaires de communication (2, 3) via le réseau virtuel (B VLAN) appartenant au mode de redondance (M1-Mn) choisi automatiquement. La présente invention concerne en outre un appareil de communication, un programme informatique et un support lisible par ordinateur.
PCT/EP2018/086124 2018-12-20 2018-12-20 Procédé de communication de données, comportant une exigence applicable relative à la fiabilité, appareil de communication, programme informatique et support lisible par ordinateur WO2020125987A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2018/086124 WO2020125987A1 (fr) 2018-12-20 2018-12-20 Procédé de communication de données, comportant une exigence applicable relative à la fiabilité, appareil de communication, programme informatique et support lisible par ordinateur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2018/086124 WO2020125987A1 (fr) 2018-12-20 2018-12-20 Procédé de communication de données, comportant une exigence applicable relative à la fiabilité, appareil de communication, programme informatique et support lisible par ordinateur

Publications (1)

Publication Number Publication Date
WO2020125987A1 true WO2020125987A1 (fr) 2020-06-25

Family

ID=65019474

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2018/086124 WO2020125987A1 (fr) 2018-12-20 2018-12-20 Procédé de communication de données, comportant une exigence applicable relative à la fiabilité, appareil de communication, programme informatique et support lisible par ordinateur

Country Status (1)

Country Link
WO (1) WO2020125987A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114143318A (zh) * 2021-12-13 2022-03-04 航天新通科技有限公司 一种网络多径传输调度方法、装置、系统及可读存储介质
CN116260706A (zh) * 2023-01-03 2023-06-13 北京智芯微电子科技有限公司 表配置、帧消除方法、装置、网络设备及存储介质
LU501035B1 (de) * 2021-12-17 2023-06-20 Phoenix Contact Gmbh & Co Verfahren und System zum Absichern des Austausches von Daten in einem Netzwerksystem für industrielle Steuerungen
WO2024066967A1 (fr) * 2022-09-28 2024-04-04 中兴通讯股份有限公司 Procédé et appareil pour réaliser une protection de réseau en anneau ethernet dans un pont virtuel tsn

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008106907A1 (fr) * 2007-03-02 2008-09-12 Siemens Aktiengesellschaft Recherche de port cible dans des réseaux constitués de sous-réseaux reliés
WO2010105828A1 (fr) * 2009-03-18 2010-09-23 Hirschmann Automation And Control Gmbh Exploitation en parallèle de protocoles rstp (rapid spanning tree protocol) et mrp (media redundancy protocol) et segmentation/couplage
US8144629B2 (en) * 2005-07-28 2012-03-27 Verizon Services Corp. Admission control for services

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8144629B2 (en) * 2005-07-28 2012-03-27 Verizon Services Corp. Admission control for services
WO2008106907A1 (fr) * 2007-03-02 2008-09-12 Siemens Aktiengesellschaft Recherche de port cible dans des réseaux constitués de sous-réseaux reliés
WO2010105828A1 (fr) * 2009-03-18 2010-09-23 Hirschmann Automation And Control Gmbh Exploitation en parallèle de protocoles rstp (rapid spanning tree protocol) et mrp (media redundancy protocol) et segmentation/couplage

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114143318A (zh) * 2021-12-13 2022-03-04 航天新通科技有限公司 一种网络多径传输调度方法、装置、系统及可读存储介质
CN114143318B (zh) * 2021-12-13 2024-02-02 航天新通科技有限公司 一种网络多径传输调度方法、装置、系统及可读存储介质
LU501035B1 (de) * 2021-12-17 2023-06-20 Phoenix Contact Gmbh & Co Verfahren und System zum Absichern des Austausches von Daten in einem Netzwerksystem für industrielle Steuerungen
WO2024066967A1 (fr) * 2022-09-28 2024-04-04 中兴通讯股份有限公司 Procédé et appareil pour réaliser une protection de réseau en anneau ethernet dans un pont virtuel tsn
CN116260706A (zh) * 2023-01-03 2023-06-13 北京智芯微电子科技有限公司 表配置、帧消除方法、装置、网络设备及存储介质

Similar Documents

Publication Publication Date Title
WO2020125987A1 (fr) Procédé de communication de données, comportant une exigence applicable relative à la fiabilité, appareil de communication, programme informatique et support lisible par ordinateur
EP2070256B1 (fr) Procédé pour reconfigurer un réseau de communication
EP2343857B1 (fr) Noeud de réseau pour un réseau de communication
DE102007015539A1 (de) Verfahren zum Rekonfigurieren eines Kommunikationsnetzwerks
EP2838220A1 (fr) Procédé de transmission redondante de messages dans un réseau de communication industriel et appareil de communication
EP2688249A1 (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
EP1532771A1 (fr) Methode d'essai de chemins de messages dans des reseaux de communication et element de reseau
EP3017570B1 (fr) Dispositif de controle, noeud de reseau et procede pour l'echange des donnees sur un reseau
EP3577871A1 (fr) Procédé et dispositif permettant l'orientation modulaire d'un flux avb
WO2006077173A1 (fr) Procede pour determiner la direction de transmission de trames ethernet
EP3228036A1 (fr) Procédé et dispositif de commande pour la transmission de données relatives à la sécurité dans un véhicule automobile au moyen d'une norme éthernet
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
WO2008119626A2 (fr) Procédé de reconfiguration d'un réseau de communication
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
WO2020211921A1 (fr) Procédé de transmission de données, nœuds de réseau, réseau, programme informatique et support lisible par ordinateur
EP3142334B1 (fr) Procédé de fonctionnement d'appareils de communication au sein d'un système d'automatisation industriel
WO2021037466A1 (fr) Procédé de transmission de données dans un réseau de communication fonctionnant de manière redondante et couplage de dispositif de communication
EP2750310A1 (fr) Procédé de synchronisation d'horloges locales dans un réseau de communication d'un système d'automatisation industriel et appareil d'infrastructure de réseau
WO2019001828A1 (fr) Procédé de transmission de messages dans un réseau de communication industriel pouvant fonctionner de manière redondante et appareil de communication pour la mise en œuvre dudit procédé
EP4125253A1 (fr) Procédé de transmission de données temporellement critiques, système de communication et appareil de communication couplée
EP3697034A1 (fr) Procédé de transmission des données, appareil, programme informatique et support lisible par ordinateur
EP3629550A1 (fr) Procédé de transmission de données dans un réseau de communication industrielle et dispositif de communication couplée
EP3868083B1 (fr) Procédé de fourniture d'une fonction de relais, en particulier de routage redondante, système, programme informatique et support lisible par ordinateur
WO2018177537A1 (fr) Procédé d'exploitation d'un réseau de communication comportant plusieurs appareils de communication pour un système industriel d'automatisation et unité de commande
EP3694156A1 (fr) Procédé de transmission de données protégé contres les défaillances, noeuds de réseau, 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: 18833645

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: 18833645

Country of ref document: EP

Kind code of ref document: A1