1 Albert Ferrer-Florit, Steve Parkes Space Technology Centre University of Dundee QoS for SpaceWire networks SpW-RT prototyping.

Slides:



Advertisements
Similar presentations
20.1 Chapter 20 Network Layer: Internet Protocol Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
Advertisements

Why to learn OSI reference Model? The answer is too simple that It tells us that how communication takes place between computers on internet but how??
CCNA – Network Fundamentals
OSI Model OSI MODEL.
1 SpaceWire Router ASIC Steve Parkes, Chris McClements Space Technology Centre, University of Dundee Gerald Kempf, Christian Toegel Austrian Aerospace.
Transmission Control Protocol (TCP) Basics
Chapter 5: TCP/IP and OSI Business Data Communications, 5e.
Transport Layer – TCP (Part1) Dr. Sanjay P. Ahuja, Ph.D. Fidelity National Financial Distinguished Professor of CIS School of Computing, UNF.
CompTIA Network+ Chapter 2
EEC-484/584 Computer Networks Lecture 12 Wenbing Zhao (Part of the slides are based on Drs. Kurose & Ross ’ s slides for their Computer.
EEC-484/584 Computer Networks Lecture 12 Wenbing Zhao (Part of the slides are based on Drs. Kurose & Ross ’ s slides for their Computer.
OSI Model MIS 416 – Module II Spring 2002 Networking and Computer Security.
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 1 v3.0 Module 11 TCP/IP Transport and Application Layers.
Protocols and the TCP/IP Suite
1 6/22/ :39 Chapter 9Fiber Channel1 Rivier College CS575: Advanced LANs Chapter 9: Fibre Channel.
EE 4272Spring, 2003 Protocols & Architecture A Protocol Architecture is the layered structure of hardware & software that supports the exchange of data.
TCP. Learning objectives Reliable Transport in TCP TCP flow and Congestion Control.
ESA UNCLASSIFIED – For Official Use Deterministic Communication with SpaceWire Martin Suess CCSDS Spring Meeting /03/2015.
Internetworking Fundamentals (Lecture #2) Andres Rengifo Copyright 2008.
Error Checking continued. Network Layers in Action Each layer in the OSI Model will add header information that pertains to that specific protocol. On.
Gursharan Singh Tatla Transport Layer 16-May
Chapter 2 Network Models Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
Chapter 6 High-Speed LANs Chapter 6 High-Speed LANs.
Midterm Review - Network Layers. Computer 1Computer 2 2.
Presentation on Osi & TCP/IP MODEL
What is a Protocol A set of definitions and rules defining the method by which data is transferred between two or more entities or systems. The key elements.
FRAME RELAY by Erdem YILMAZ. What is Frame Relay? high-performance WAN protocol operates at the physical and data link layers Originally designed for.
SpaceWire-RT Steve Parkes, Albert Ferrer-Florit
Chapter 7 Low-Level Protocols
1 Chapter 1 OSI Architecture The OSI 7-layer Model OSI – Open Systems Interconnection.
Layer Architecture Layer architecture simplifies the network design. It is easy to debug network applications in a layered architecture network. The network.
TCP : Transmission Control Protocol Computer Network System Sirak Kaewjamnong.
1 The Internet and Networked Multimedia. 2 Layering  Internet protocols are designed to work in layers, with each layer building on the facilities provided.
TELE202 Lecture 5 Packet switching in WAN 1 Lecturer Dr Z. Huang Overview ¥Last Lectures »C programming »Source: ¥This Lecture »Packet switching in Wide.
Data and Computer Communications Circuit Switching and Packet Switching.
SpaceWire Plug-and-Play: A Roadmap Peter Mendham, Albert Ferrer Florit, Steve Parkes Space Technology Centre, University of Dundee 1.
CCNA 1 v3.0 Module 11 TCP/IP Transport and Application Layers.
COP 4930 Computer Network Projects Summer C 2004 Prof. Roy B. Levow Lecture 3.
Chapter 15 – Part 2 Networks The Internal Operating System The Architecture of Computer Hardware and Systems Software: An Information Technology Approach.
Central Engineering / ASG 74 Data Processing Advanced Studies Sev Gunes-Lasnet, Olivier Notebaert 2008, November 5th Prototype implementation of a routing.
Lecture 4 Overview. Ethernet Data Link Layer protocol Ethernet (IEEE 802.3) is widely used Supported by a variety of physical layer implementations Multi-access.
An Introduction to Networking
OSI Reference Model. Open Systems Interconnection (OSI) Model International standard organization (ISO) established a committee in 1977 to develop an.
CHAPTER 4 PROTOCOLS AND THE TCP/IP SUITE Acknowledgement: The Slides Were Provided By Cory Beard, William Stallings For Their Textbook “Wireless Communication.
Department of Electronic Engineering City University of Hong Kong EE3900 Computer Networks Protocols and Architecture Slide 1 Use of Standard Protocols.
OSI Model. Open Systems Interconnection (OSI) is a set of internationally recognized, non proprietary standards for networking and for operating system.
An Introduction to CAN CAN Basics 2 Renesas Interactive
Data Communications and Networks Chapter 6 – IP, UDP and TCP ICT-BVF8.1- Data Communications and Network Trainer: Dr. Abbes Sebihi.
McGraw-Hill©The McGraw-Hill Companies, Inc., 2000 Muhammad Waseem Iqbal Lecture # 20 Data Communication.
OSI Model OSI MODEL. Communication Architecture Strategy for connecting host computers and other communicating equipment. Defines necessary elements for.
OSI Model OSI MODEL.
Application – Transport – Network
What is a Protocol A set of definitions and rules defining the method by which data is transferred between two or more entities or systems. The key elements.
Alessandro Leoni, Felix Siegle September, 2017
Deterministic Communication with SpaceWire
Click to edit Master subtitle style
Process-to-Process Delivery, TCP and UDP protocols
Lecturer, Department of Computer Application
DEPARTMENT OF COMPUTER SCIENCE
Net 431: ADVANCED COMPUTER NETWORKS
Transport Layer Unit 5.
Protocols and the TCP/IP Suite
Chapter 3: Open Systems Interconnection (OSI) Model
Data Communication and Computer Networks
Net 323 D: Networks Protocols
OSI Model OSI MODEL.
Protocols and the TCP/IP Suite
Introduction to Computer Networks
Process-to-Process Delivery: UDP, TCP
Transport Layer 9/22/2019.
Presentation transcript:

1 Albert Ferrer-Florit, Steve Parkes Space Technology Centre University of Dundee QoS for SpaceWire networks SpW-RT prototyping

Protocol design objectives  High performance, high reliability, timely  Simple to implement, simple to understand  Software and Hardware implementations  Support Intelligent and dumb nodes  Compatibility with significant SpW devices.  Flexibility to accommodate multiple user cases under a unique protocol definition. 2

SpW-RT user cases  Asynchronous (usually also reliable) –Dedicated links: Timely –Shared links: Not timely  Scheduled and timely (usually also reliable) –Periodic messages (i.e. status messages) –Sporadic messages (i.e. command & control messages) Multiple user cases can be accommodated within the same SpW network 3

Survey on communication architectures 4  Aeronautics –MIL-STD-1553 –Fibre Channel –SAFEBus  Automotive industry –CAN bus –FlexRay –TTP  Cluster computing –Myrinet  System On Chip –AMBA bus, Core-Connect –Network On Chip

SpW-RT elements: reliability  Cause of packet errors –Link error or faulty router –Network congestion  Retry mechanism –Sliding sending window 5  Redundancy –Recommended network topologies –Redundant paths Message Data ACK Rcv buffer

SpW-RT elements: routing 6  Support Path and logical addressing  Detach routing from device identification 1.Different routes depending on QoS 2.Different routes depending on timeslot Address 120Address 121 port1,port 2Port 2

SpW-RT elements: timeliness  Computation of maximum packet delivery time for a simple case with lineal topology. 7 One packet per source: 5*Transmission time Nodes continuously sending: 9*Transmission time

SpW-RT elements: TDM and sending priority 8 Time-SlotSlot1Slot2... Path120, , 200 Channel1-Command 2-Data 1-Command TDM is very efficient if network traffic is periodic and known Sending priority can be used to avoid wasting resources: payload data traffic is sent when command and control is not required. Node A

RT PDU Other SpW-RT elements 9 Message (SDU) Segmentation limits the maximum packet size SDU segments are encapsulated in RT PDUs SDU segment Flow control assures that 1.SDU segment will be buffered or consumed 2.Low priority messages are completely receive by non parallel processing protocols

SpW-RT elements: Network manager  Device that supervise network status (nodes, links and routers) periodically. –Using best effort service –Using reserved timeslots in scheduled networks  Could be the only device that can write routing tables and open/close RT channels  Could implement PnP and FDIR. 10 Net Manager Router B Node A Router A

SpW-RT: prototyping design space 11 Basic requirements Met Prototyping analysis Prototyping implementation Initial specification Current specification

SpW-RT Prototypes  Two major prototypes have been developed: 1.Complete implementation of the first draft of the SpW-RT To check that the SpW-RT concepts are valid To provide preliminary performance and complexity figures 2.Complete operative RT protocol that evaluate alternative approaches to help on the SpW-RT design trade off. Use of bidirectional channels, piggybacking acknowledgment, data and flow control. Connectionless protocol using control flags to reset sequence numbers. Support for zero configuration channels opening. For synchronous systems, flow control and acknowledgement of multiple channels is provided in the same PDU. 12

SpW-RT prototype scheme 13

SpW-RT application layer 14

Lessons learned  From the prototype work and further theoretical analysis, the trade off results in: –Control PDU format should not be equal for synchronous and scheduled –Bidirectional channels are not very efficient for scheduled systems –Connection oriented protocol offers more robustness –In scheduled networks flow control information should be sent before the sender performs the arbitration and the acknowledgement should be received as soon as possible. –Scheduled systems should send multiple SDU segments per timeslot. Seven segments of 256 bytes is optimum. 15

Conclusions and future work  SpW-RT prototyping efforts have provided an important role in the definition of the SpW-RT protocol. –The specification is a result of a thoroughly analysis of different options, some of them being prototyped.  Future work will focus on: –Prototyping of latest RT specification for EGSE and space qualified components. –Development of network design tools and reference architectures with user cases. 16