+ All Categories
Home > Documents > A protocol for Mixed-Criticality management in Switched ...robdavis/wmc/p3.pdf · A protocol for...

A protocol for Mixed-Criticality management in Switched ...robdavis/wmc/p3.pdf · A protocol for...

Date post: 28-May-2020
Category:
Upload: others
View: 4 times
Download: 0 times
Share this document with a friend
27
A protocol for Mixed-Criticality management in Switched Ethernet networks O.Cros, X.Li, L.George December 1, 2015
Transcript

A protocol for Mixed-Criticality management in

Switched Ethernet networks

O.Cros, X.Li, L.George

December 1, 2015

What’s the matter ?

Mixed-Criticality (MC) in network context

A protocol to manage MC

Delay computation

Simulation results

Plan and objectives

MC in network context

A protocol to manage MC

Delay computation

Simulation results

Context

Domains

Public transport (CAN) (Volvo, Renault, ...)Avionics (AFDX) (Airbus)Home automationDefense

Context

Domains

Public transport (CAN) (Volvo, Renault, ...)Avionics (AFDX) (Airbus)Home automationDefense

Principles

Message routing and schedulingClassifying messages by importance

Context

Domains

Public transport (CAN) (Volvo, Renault, ...)Avionics (AFDX) (Airbus)Home automationDefense

Principles

Message routing and schedulingClassifying messages by importance

MC

Privileging messages in critical situation

Critical for the vehicle, for the mission, for the users

Overload context

Assuring critical messages transmission

Why Mixed-Criticality ?

Today

1 network per group of functions (mechanical, comfort, gpstracking, ...)Increasing of financial costs, weight, fuel and energy consumptionExample : 3/4 different antennas per public bus

Mixed-criticality

Mixing all the functions in the same networkEach function associated to a criticality levelMC management protocol to guarantee critical messagestransmission

Mixed-Criticality

Related work

Mono/Multicore context2-levels of criticalityQoS

Synchronization protocol

Ethernet IEEE-1588PTPv2

Mixed-criticality

Problems

How to manage messages scheduling inside a embedded network ?How to assure critical messages transmission ?

Mixed-criticality

Problems

How to manage messages scheduling inside a embedded network ?How to assure critical messages transmission ?

Solution

Providing MC management in embedded networksPeriod-oriented or WCTT-orientedStatic-defined path

Example

Flow T LOi (µs) THI

i (µs) Ci (µs) uLOi uHIi

v1 500 250 100 0.2 0.4v2 500 250 100 0.2 0.4v3 300 - 100 0.33 -

Topology

Centralized topology

Automotive Ethernet, AFDX targetsOne central node to store criticality information

Example

Plan and objectives

MC in network context

A protocol to manage MC

Delay computation

Simulation results

A two-phase protocol

First phase

Switch-criticality callTransmitting switch order to a central nodeCentralized topology

Second phase

Multicast the switch criticality order (reliable multicast)Sending new criticality info to all nodesReliable (deterministic) multicast

A two-phase protocol : The call phase

Principle

Triggering a criticality switch when :Longer period detected Or shorter inter-arrival time detectedFixed WCTT Cc (static known size)Ethernet protocol

Transmission

Dedicated VLAN, highest priorityPTP messages : clock accuracy (PTP-ETE)

MC management protocol

A two-phase protocol : the multicast phase

Multicast

Each node can get the switch criticality order at a different instantClock precision and clock synchronization (PTP - IEEE1588)Total order : coherency in the networkAt each instant, all nodes have the same criticality information(precision ǫ)

Reliability

Each single physical link is boundedClock accuracy ǫ

Worst-case delay computation

Switch-criticality order

All nodes switch at the same timeLast reception instant : maxn∈N (dn ∗ (Cc + sl) + ǫn)

Plan and objectives

MC in network context

A protocol to manage MC

Delay computation

Simulation results

The trajectory approach

Flows

Representing the network as a set of flowsEach flow vi emits messagesvi = {Pi ,Ci , ~Ti}

Criticality management

One period per criticality level~Ti = {T LO

i ,THIi }

Call phase delay

Principle

Sending criticality switch call to central nodeEmitting a call when a message exceeds its period or LO-WCTTHighest priority VLAN

Delay

Indelay = FPTP ∗

j∈hpc

Pc∩Pj 6=∅

(

Sfirstc,jmaxc −M

firstc,jc + Ac,j

)

+∑

h∈Pc

δhc + (|Pn| − 1) ∗ (sl + 2 ∗ Cc)

Multicast phase delay

Principle

Sending the criticality level information to all nodesDepending on the size of the network

Delay

Mndelay = dn ∗ (Cc + sl) + ǫn

Total delay

Phases delay

Sdelay = maxn∈N

(I ndelay +Mndelay )

Final expression

Sdelay = FPTP ∗∑

j∈hpc

Pc∩Pj 6=∅

(

Sfirstc,jmaxc −M

firstc,jc + Ac,j

)

+∑

h∈Pc

δhc

+ (2 ∗ maxn∈N

(dn)− 1) ∗ (Cc + sl) + Cc(maxn∈N

(dn)− 1) + ǫ

Plan and objectives

MC in network context

A protocol to manage MC

Delay computation

Simulation results

Criticality switch delay

0.3 0.4 0.5 0.6 0.7 0.8 0.9

load

120

130

140

150

160

de

lay (

µs)

WCTT_MAX: 20 µs

WCTT_MAX: 30 µs

WCTT_MAX: 40 µs

WCTT_MAX: 115,8 µs

Criticality switch delay

Highest priority (except PTP)

Non-preemptive effect

Switch criticality delay stays constant

Criticality messages transmission is guaranteed in a boundedtime

Conclusion

MC management protocol

Reliable multicast

Independent from the load

Perspectives

Delay computation on switch-criticality delayDelay computation to return to low-criticality modeUncentralized MC management

Conclusion

Thanks

Thanks to all the authors of this presentation and publicationThanks to our respective labsThank you for your attention !

?

Questions ? Feel free to ask !


Recommended