Ttethernet Dataflow Concept

Ttethernet Dataflow Concept

Presented at the 8th IEEE International Symposium on Network Computing and Applications, Cambridge, MA, July 2009. TTEthernet Dataflow Concept Wilfried Steiner Gunther¨ Bauer Brendan Hall Michael Paulitsch Srivatsan Varadarajan Chip IP Design Advanced Technology, Aerospace TTTech Computertechnik AG Honeywell [email protected] [email protected] Abstract—TTEthernet is a novel communication infrastruc- are, for example, industrial control, automotive, or avionics. tures that allows using a single physical communication in- Coming from the avionics area, TTEthernet was also designed frastructure for distributed applications with mixed-criticality to be compliant to the Avionics Full-Duplex Switched Ethernet requirements, e.g. the command and control systems and au- dio/video systems. This is achieved via a fault-tolerant self- (AFDX) [1] standard. AFDX itself is a successful attempt stabilizing synchronization strategy, which establishes temporal to increase the temporal quality and reliability of standard partitioning and, hence, ensures isolation of the critical dataflows Ethernet. With TTEthernet, this technology is improved to be from the non-critical dataflows. even usable for tight control loops. The focus in this paper is on the dataflow in TTEthernet. TTEthernet provides three traffic classes: time-triggered For this we take the synchronization as a given and discuss from a TTEthernet user perspective which communication options Traffic (TT), rate-constrained (RC) Traffic, and best-effort TTEthernet provides and how they are aligned and realized. Traffic (BE). Rate-constrained (RC) Traffic is commonly While this paper uses TTEthernet as reference communication known as the traffic provided by AFDX. infrastructure, the methods and strategies presented are valid This paper is structured as follows: in the next section for any message-based network. we revise general dataflow characteristics and TTEthernet Keywords: mixed-criticality systems, cross-industry appli- concepts. In Section III we elaborate qualitatively, how the cation, Ethernet, Avionics Full-Duplex Switched Ethernet TTEthernet traffic classes meet the general characteristics of (AFDX), Time-Triggered Protocol (TTP), TTEthernet dataflow. Section IV discusses the possible integration options, pros and cons, and the particular integration strategy chosen I. INTRODUCTION for TTEthernet. This paper concludes in Section V. Our modern life relies on the proper function of electronic devices that provide convenience and safety. To further ad- II. DATAFLOW CHARACTERISTICS vance our life’s quality, technology fosters the interaction of The network discussed below is based on a switched electronic devices and, hence, the communication infrastruc- Ethernet model. Hence, the network topology comprises a ture becomes ever more important and has to fulfill demanding star structure consisting of end systems that are connected requirements. via a single centralized switch device or several devices that The difficulty of the interconnection is a result of re- are directly connected (i.e. multi-hop communication). The quirements that not only grow with respect to the available channels can be implemented redundantly with respect to bandwidth, but, even more complex, that are driven by real- the degree of fault tolerance that has to be provided. The time communication performance and fault tolerance. This communication channel is assumed to be full-duplex, meaning mix of manifold requirements demands a new integrative that an end system is able to transmit and receive concurrently. communication infrastructure to keep the number of physical To maintain compatibility with existing standards, the mes- networks reasonable and bandwidth efficiency sustainable. In sage format utilized for TTEthernet is made compliant with this paper we propose TTEthernet as such an integrative com- the legacy network standard e.g. ARINC664. This standard munication infrastructure that supports communication among uses Ethernet multicast MAC destination addresses as unique applications with different real-time and safety requirements identifiers for all messages within an application dataflow, and over a single physical network. TTEthernet is an industrial this same message identifier is used in TTEthernet to identify development which builds on the fundamental academic TT- a message’s traffic type. In this document we use the terms Ethernet technology [2]. message and frame interchangeably. TTEthernet only uses standard Ethernet compliant frames As depicted in Figure 1, the time-triggered services (TT and, hence, remains fully backward compatible to the Ethernet Services) can be viewed in parallel to the common OSI layers: standard. While, in principle, any message-based communica- a communication controller that implements the TT Services tion protocol would be suited for an integrated communication is able to synchronize its local clock with the local clocks of infrastructure, Ethernet has significant benefits: Ethernet is other communication controllers and switches in the system. the dominating standard in office communication, and, fur- The communication controller can then send messages at off- thermore, we observe a market trend to apply Ethernet for line planned points in this synchronized global time. These distributed control systems. New application areas of Ethernet messages are said to be time-triggered and it is the task of 1 the off-line planning tool to guarantee that the time-triggered 1) Temporal Quality: The pre-planned message exchange message schedule is free of conflict. By conflict-free we mean is one of the most important benefits of time-triggered com- that it will never be the case that two time-triggered messages munication: timeliness is guaranteed and latency as well as compete for transmission and, hence, no dynamic arbitration jitter can be kept small as contentions for the shared medium actions for the communication medium (for time-triggered are avoided. messages) are required. 2) Protocol Overhead: Time-triggered communication re- lies on the implementation of synchronization services. Such Rate-Constrained Best-Effort Time-Triggered Traffic (RC) Traffic (BE) Traffic (TT) services include a method to establish an initial agreement on Application the values of the local clocks of the components in the system (i.e. a startup algorithm [6]) and a clock synchronization service [3] that maintains the synchronization of the local UDP, TCP, ... UDP, TCP, ... clocks during normal operation mode. In addition, a time- RC Services IP IP TT Services triggered communication protocol supports services for restart Ethernet 802.3 in case the synchronization is lost. Synchronization services are distributed algorithms that involve the cooperation of a set of end systems and switch(es) in the network. These services Fig. 1. Interaction of standards need to be fault-tolerant. The TTEthernet synchronization services are defined in [5]. As depicted in Figure 1, messages from higher layer pro- 3) Composability/Scalability: A time-triggered communi- tocols, like IP or UDP, can easily be “made” time-triggered cation paradigm requires locally stored schedule tables. If new without modifications of the messages’ contents itself. This messages have to be scheduled, e.g. when adding a new end is because the TTEthernet protocol overhead is transmitted in system, these schedule tables have to be modified. To reduce dedicated messages, called Protocol Control Frames, which the impact of such changes the tables are organized to support are used to establish system-wide synchronization upon those an “incremental scheduling philosophy”, which is a method components that need to be synchronized. In short, TTEthernet that allows building a new schedule from an existing one is only concerned with “when” a data message is sent, rather without changing the required latency constraints. than with specific contents within a data message. A dataflow defines a, possibly infinite, sequence of mes- B. Rate-Constrained Communication sages between end systems. Each dataflow has exactly one RC denotes the traffic that is transmitted according to a source, which we call the sender and may have an arbitrary rate-constrained communication paradigm. Unlike TT, RC number of end systems that consume the respective messages; traffic does not rely on Protocol Control Frames. RC is we call these end systems the receivers. the communication paradigm realized by ARINC 664 part A traffic class is the sum of all dataflows that adhere to 7 (Avionics Full-Duplex Switched Ethernet). Each sender either one communication paradigm: TT, RC, or BE. realizes a traffic shaping function for each RC dataflow. This traffic shaping function ensures that there will be a minimum III. DISCUSSION OF TTEthernet TRAFFIC CLASSES inter-frame gap between any two following messages of a dataflow. Each switch in the network realizes a traffic checking A. Time-Triggered Communication function that checks whether, indeed, the end systems produce TT denotes the traffic that is transmitted according to a a well-shaped sequence of messages. A switch drops messages time-triggered communication paradigm. Typically, TT com- that are sent too early, hence, violating the minimal inter-frame munication requires synchrony between the time-triggered gap. senders. In order to establish and maintain synchrony Protocol 1) Temporal Quality: The rate of message transmission of Control Frames are exchanged between the end systems. RC traffic is bounded. As the end systems are not synchro-

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    4 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us