TSN Support for Quality of Service in Space ERTS Conference - Jan. - - PowerPoint PPT Presentation

TSN Support for Quality of Service in Space

ERTS Conference - Jan. 2020

Presenter: Pierre-Julien CHAINE, PhD Student Supervisor from ONERA: Marc BOYER Supervisor from ONERA: Claire PAGETTI Supervisor from AIRBUS: Franck WARTEL

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Introduction

Introduction

➥ Internal project E4S - Ethernet for Space - from Airbus Defence and Space, ➥ A PhD program was started in Nov. 2018 within E4S project, ➥ PhD is hosted at ONERA, directed by Claire PAGETTI and Marc BOYER, ➥ PhD is supervised on technical aspects by Franck WARTEL , ➥ Goal: Find and assess potential new technologies based on Ethernet suited for space applications.

2/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Outline

1

Satellite Architecture Overview Introduction Current Satellite Network

2

Satellite Network Foreseen Evolution Opportunity for an unified network Overview of TSN Which protocols for an On-Board Unified TSN Network?

3

Satisfying FDIR requirements with 802.1CB-FRER

4

Conclusion

3/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Outline

1

Satellite Architecture Overview Introduction Current Satellite Network

2

Satellite Network Foreseen Evolution Opportunity for an unified network Overview of TSN Which protocols for an On-Board Unified TSN Network?

3

Satisfying FDIR requirements with 802.1CB-FRER

4

Conclusion

4/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satellite Architecture

Payload - High Performance Domain It is the purpose of the satellite, what the clients pays for.

Spot 5 Payload Platform Service module Propulsion module HRG HRS Case Vegetation

https://earth.esa.int/web/eoportal/satellite-missions/s/spot-5

5/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satellite Architecture

Payload - High Performance Domain It is the purpose of the satellite, what the clients pays for. Platform - Time Critical Domain It is what allows the payload to achieve its mission:

Spot 5 Payload Platform Service module Propulsion module HRG HRS Case Vegetation

https://earth.esa.int/web/eoportal/satellite-missions/s/spot-5

5/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Scope of the presentation

Scope

The following presentation will only focus on the network part of the satellite architecture and especially the network safety properties e.g. FDIR properties for the spacecraft industry (Fault Detection, Isolation and Recovery).

6/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Current Satellite Architecture Introduction

Platform Payload

7/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Current Satellite Architecture Introduction

Platform: Performances: Low latency, low jitter, guarantee of arrival Technologies: 1553, CAN, SpaceWire

Platform Payload

Sensors (N) Actuators RIU IMU Star Tracker SW + MM A (N) OBC N Instrument B Instrument A Instrument C Instrument B

Payload: Performances: High average throughput Technologies: SpaceWire, SpaceFibre, SerDes

7/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Current Satellite Architecture Introduction

Platform: Performances: Low latency, low jitter, guarantee of arrival Safety: Link and device cold redundancy Technologies: 1553, CAN, SpaceWire

Platform Payload

Sensors (N) Actuators RIU IMU Star Tracker Sensors (N) Actuators RIU IMU Star Tracker SW + MM A (N) SW + MM B (N) OBC R OBC N Instrument B Instrument A Instrument C

Payload: Performances: High average throughput Safety: Link and device cold redundancy Technologies: SpaceWire, SpaceFibre, SerDes

7/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Current Satellite Architecture Introduction

Platform: Performances: Low latency, low jitter, guarantee of arrival Safety: Link and device cold redundancy Technologies: 1553, CAN, SpaceWire

Platform Payload

Sensors (N) Actuators RIU IMU Star Tracker Sensors (N) Actuators RIU IMU Star Tracker SW + MM A (N) SW + MM B (N) OBC R OBC N Instrument B Instrument A Instrument C

Payload: Performances: High average throughput Safety: Link and device cold redundancy Technologies: SpaceWire, SpaceFibre, SerDes

7/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Current Satellite Architecture Introduction

Platform: Performances: Low latency, low jitter, guarantee of arrival Safety: Link and device cold redundancy Technologies: 1553, CAN, SpaceWire

Platform Payload

Sensors (N) Actuators RIU IMU Star Tracker Sensors (N) Actuators RIU IMU Star Tracker SW + MM A (N) SW + MM B (N) OBC R OBC N Instrument B Instrument A Instrument C

Payload: Performances: High average throughput Safety: Link and device cold redundancy Technologies: SpaceWire, SpaceFibre, SerDes

7/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Outline

1

Satellite Architecture Overview Introduction Current Satellite Network

2

Satellite Network Foreseen Evolution Opportunity for an unified network Overview of TSN Which protocols for an On-Board Unified TSN Network?

3

Satisfying FDIR requirements with 802.1CB-FRER

4

Conclusion

8/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Actual Network Pros & Cons

Spacewire + 1 553

Well suited for space environment Very reliable, simple behavior, easy to analyse Mature for space applications Synchronous protocols developed

• ver 1553 are perfect for AOCS

control loops Evolution opportunities and performances limited Few users of these technologies Few manufacturers Expensive Two very different technologies

9/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Where to go ?

Problem Statement

Is it possible to find a unique technology, that: ➥ is able to fulfil both platform and payload needs, ➥ has better performances, ➥ is easy to analyse/configure, ➥ eases development and integration, ➥ is cheaper

10/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Unified Ethernet network Pros & Cons

Unified network using Ethernet/ TSN

Very large ecosystem Very mature in industrial applications Lot of manufacturers, COTS available Lower costs (TBC) Complex behavior, non deterministic in general Not qualified for space environment yet Risk of re-designing « legacy » devices Easier integration High data rate (>1Gbit/s) Only one technology

11/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

TSN ?

Challenge

Is TSN a superset of 1553 + SpaceWire i.e. is it possible to satisfy both platform and payload requirements using the same technology in a Unified Ethernet/TSN Network ?

Organization

In order to answer that question, two aspects have to be analysed:

12/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

TSN ?

Challenge

Is TSN a superset of 1553 + SpaceWire i.e. is it possible to satisfy both platform and payload requirements using the same technology in a Unified Ethernet/TSN Network ?

Organization

In order to answer that question, two aspects have to be analysed:

1

Which protocols/features should be used ? Which protocols should be avoided ?

12/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

TSN ?

Challenge

Is TSN a superset of 1553 + SpaceWire i.e. is it possible to satisfy both platform and payload requirements using the same technology in a Unified Ethernet/TSN Network ?

Organization

In order to answer that question, two aspects have to be analysed:

1

Which protocols/features should be used ? Which protocols should be avoided ?

1

What are the protocols offered by TSN ? 12/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

TSN ?

Challenge

Is TSN a superset of 1553 + SpaceWire i.e. is it possible to satisfy both platform and payload requirements using the same technology in a Unified Ethernet/TSN Network ?

Organization

In order to answer that question, two aspects have to be analysed:

1

Which protocols/features should be used ? Which protocols should be avoided ?

1

What are the protocols offered by TSN ?

2

What are the requirements of the satellite network ? 12/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

TSN ?

Challenge

Is TSN a superset of 1553 + SpaceWire i.e. is it possible to satisfy both platform and payload requirements using the same technology in a Unified Ethernet/TSN Network ?

Organization

In order to answer that question, two aspects have to be analysed:

1

Which protocols/features should be used ? Which protocols should be avoided ?

1

What are the protocols offered by TSN ?

2

What are the requirements of the satellite network ?

3

What is the minimum subset of TSN protocols allowing to satisfy these requirements ? 12/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

TSN ?

Challenge

Is TSN a superset of 1553 + SpaceWire i.e. is it possible to satisfy both platform and payload requirements using the same technology in a Unified Ethernet/TSN Network ?

Organization

In order to answer that question, two aspects have to be analysed:

1

Which protocols/features should be used ? Which protocols should be avoided ?

1

What are the protocols offered by TSN ?

2

What are the requirements of the satellite network ?

3

What is the minimum subset of TSN protocols allowing to satisfy these requirements ?

2

What is a good and valid topology ?

12/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

TSN ?

Challenge

Is TSN a superset of 1553 + SpaceWire i.e. is it possible to satisfy both platform and payload requirements using the same technology in a Unified Ethernet/TSN Network ?

Organization

In order to answer that question, two aspects have to be analysed:

1

Which protocols/features should be used ? Which protocols should be avoided ?

1

What are the protocols offered by TSN ?

2

What are the requirements of the satellite network ?

3

What is the minimum subset of TSN protocols allowing to satisfy these requirements ?

2

What is a good and valid topology ?

12/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Which protocols for an On-Board Unified TSN Network ?

Organization

1

What are the protocols offered by TSN ?

2

What are the requirements of the satellite network ?

3

What is the minimum subset of TSN protocols allowing to satisfy these requirements ?

13/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Overview

(Farkas, 2018)

14/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Which protocols for an On-Board Unified TSN Network ?

Organization

1

What are the protocols offered by TSN ?

2

What are the requirements of the satellite network ?

3

What is the minimum subset of TSN protocols allowing to satisfy these requirements ?

15/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Outline

1

Satellite Architecture Overview Introduction Current Satellite Network

2

Satellite Network Foreseen Evolution Opportunity for an unified network Overview of TSN Which protocols for an On-Board Unified TSN Network?

3

Satisfying FDIR requirements with 802.1CB-FRER

4

Conclusion

16/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfy FDIR requirements with 802.1CB

FDIR ?

FDIR - Fault Detection Isolation and Recovery is the satellite function in charge of monitoring the satellite system by identifying when a fault has occurred, isolating it to prevent its propagation and repairing the fault or recovering from it.

Fault Fault Detection Fault Isolation Fault Recovery

FDIR

Problem statement

Is TSN protocol 802.1CB-Frame Replication and Elimination for Reliability able to satisfy the network FDIR requirements ?

17/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Requirement 1: No Single Point of Failure

• Req. 1: No Single Point of Failure

A Single of Point of Failure (SPOF) is a part of the system that, if it fails, will stop the entire system from working.

SPOFs are forbidden !

➥ At network level: even if a link or device fails, the communication shall still occur.

18/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfying Req. 1 with TSN feature 802.1CB-FRER

Fault Fault Detection Fault Isolation Fault Recovery

FDIR

Switch

Software Stack (OBC N) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES

Software Stack (OBC R) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES Switch

Goal : ensure that this message arrives even in case of a single link or device failure

19/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfying Req. 1 with TSN feature 802.1CB-FRER

Fault Fault Detection Fault Isolation Fault Recovery

FDIR

Switch

Software Stack (OBC N) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES

Software Stack (OBC R) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES Switch

19/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfying Req. 1 with TSN feature 802.1CB-FRER

Fault Fault Detection Fault Isolation Fault Recovery

FDIR

Switch

Software Stack (OBC N) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES

Software Stack (OBC R) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES Switch

Use of Individual Recovery Function to detect ES failures and isolate them

19/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfying Req. 1 with TSN feature 802.1CB-FRER

Fault Fault Detection Fault Isolation Fault Recovery

FDIR

Switch

Software Stack (OBC N) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES

Software Stack (OBC R) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES Switch

Use of Individual Recovery Function to detect Switch failures and isolate them

19/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfying Req. 1 with TSN feature 802.1CB-FRER

Fault Fault Detection Fault Isolation Fault Recovery

FDIR

Switch

Software Stack (OBC N) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES

Software Stack (OBC R) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES Switch

Recovery from a faulty message using the Sequencing Function (possibly due to a link default or failure.

19/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfying Req. 1 with TSN feature 802.1CB-FRER

Fault Fault Detection Fault Isolation Fault Recovery

FDIR

Switch

Software Stack (OBC N) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES

Software Stack (OBC R) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES Switch

Message is received and passed to the application

19/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfying Req. 1 with TSN feature 802.1CB-FRER

Fault Fault Detection Fault Isolation Fault Recovery

FDIR

Switch

Software Stack (OBC N) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES

Software Stack (OBC R) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES Switch

Loss of upper (nominal) switch

19/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfying Req. 1 with TSN feature 802.1CB-FRER

Fault Fault Detection Fault Isolation Fault Recovery

FDIR

Switch

Software Stack (OBC N) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES

Software Stack (OBC R) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES Switch

Message still arrives to its destination (back-up path)

19/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Requirement 2: Network Monitoring

• Req. 2: Network Monitoring

"Network Monitoring (NM) is the on-board function in charge of collecting indicators on the good or bad health of the satellite system."

NM is mandatory !

At network level: observations to diagnose communication links and devices health status.

20/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfying Req. 2 with TSN feature 802.1CB-FRER

Switch

Software Stack (OBC N) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES

Software Stack (OBC R) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES Switch 802.1CB - MIB TX/RX Counter

21/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfying Req. 2 with TSN feature 802.1CB-FRER

Switch

Software Stack (OBC N) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES

Software Stack (OBC R) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES Switch 1

21/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfying Req. 2 with TSN feature 802.1CB-FRER

Switch

Software Stack (OBC N) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES

Software Stack (OBC R) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES Switch 1 1 1 1 1

21/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfying Req. 2 with TSN feature 802.1CB-FRER

Switch

Software Stack (OBC N) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES

Software Stack (OBC R) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES Switch 1 1 1 1 1 1 1 1 1

21/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfying Req. 2 with TSN feature 802.1CB-FRER

Switch

Software Stack (OBC N) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES

Software Stack (OBC R) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES Switch 1 1 1 1 1 1 1 1 1 1

21/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfying Req. 2 with TSN feature 802.1CB-FRER

Switch

Software Stack (OBC N) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES

Software Stack (OBC R) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES Switch 1 1 1 1 1

21/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfying Req. 2 with TSN feature 802.1CB-FRER

Switch

Software Stack (OBC N) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES

Software Stack (OBC R) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES Switch 1 1 1 1 1 1 1 1 1

21/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Satisfying Req. 2 with TSN feature 802.1CB-FRER

Switch

Software Stack (OBC N) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES

Software Stack (OBC R) TSN Harware Stack

ES

Software Stack (RIU) TSN Harware Stack

ES Switch 1 1 1 1 1 1 1 1 1

21/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Other requirements

Other requirements

There are other safety requirements such as: Seamless redundancy at application level Network protection against babbling idiot end-stations etc. ⇒ They will be addressed in future works.

22/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Outline

1

Satellite Architecture Overview Introduction Current Satellite Network

2

Satellite Network Foreseen Evolution Opportunity for an unified network Overview of TSN Which protocols for an On-Board Unified TSN Network?

3

Satisfying FDIR requirements with 802.1CB-FRER

4

Conclusion

23/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Satellite Architecture Overview Satellite Network Foreseen Evolution Satisfying FDIR requirements with 802.1CB-FRER Conclusion

Conclusion

Summary

➥ Existing satellite network technologies used in space are specific and have limited performances and high cost, ➥ Change opportunity: using an Unified Ethernet TSN Network, shared with other industries such as aeronautic, automotive, industrial automation, . . . ➥ TSN is interesting but wide and its complexity can increase quickly, ➥ Challenge:Which configuration for TSN protocol 802.1CB-FRER? ➥ Challenge: What is the minimum subset of TSN to satisfy the network requirements and the FDIR requirements while minimizing complexity, having a minor impact on legacy equipments at lower cost possible ?

24/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Annexes References

Pro for TSN: Babbling Idiot Example

Expected ACK More traffic than expected Switch to alternate bus and shut-down transceiver Drop the frames (Policing + Individual recovery) Reboot transceiver Reboot transceiver

• n MIB

analysis Babbling idiot transceiver More traffic than expected Individual recovery + Policing + Monitoring Fault Fault

Detection

Fault Isolation Fault Recovery

FDIR

In 1553 In TSN 25/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Annexes References

TSN Profile for Aerospace

Not requested:

• IEEE 802.1Qat
• IEEE 802.1Qcc (dynamic)
• IEEE 802.1Qca

Optional

• IEEE 802.1Qbu & 802.3br
• IEEE 802.1Qch

Mandatory:

• IEEE 802.1AS & 802.1AS-rev
• IEEE 802.1Qci
• IEEE 802.1CB
• IEEE 802.1Qbv
• IEEE 802.1Qav
• IEEE 802.1 Qcc (static configuration)

26/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference

Annexes References

Réferences I

Farkas, J. (2018). Introduction to time sensitive networking. IEEE Communications Standards Magazine. Notebaert, O., Lachaize, J., Clavier, R., Fueser, A., Herpel, H., Montano, G., & Planche, L. (November 2014). Spacewire 2: Needs and evaluation metrics. 6th SpaceWire Conference. Notebaert, O., Montano, G., Planche, T., Pruvost, C., Wartel, F., Schüttauf, A., . . . Jameux,

• D. (October 2016). Towards spacewire-2: Space robotics needs. 6th SpaceWire

Conference. Osra communication network specification (Tech. Rep.). (2017). European Space Agency. Pruvost, C., Planche, T., Notebaert, O., Rossignol, A., Herpel, H., & Schüttauf, A. (May 2016). Ethernet for space: an enabler for next generation avionics. Data Systems in Aerospace (DASIA). Savoir functional reference architecture (Tech. Rep.). (2016). European Space Agency.

27/24

Pierre-Julien CHAINE - January 30, 2020 - ERTS Conference