OPEN Alliance TC10 Sleep and Wakeup - Vector Informatik · PUBLIC 3 TC-10 Timeline for 1000BASE-T1 in OPEN Alliance Draft 1 Draft 2 Concepts Q1 2019 Q2 2019 Q3 2019 Q2 2018 Interoperability

PUBLIC

Dr. Philip Axer

Günter Sporer

OPEN Alliance TC10 Sleep and WakeupThe Way from 100BASE-T1 to 1000BASE-T1 Capable PHYs

April 2019

PUBLIC 1

Agenda• Introduction

• Landscape of energy saving mechanisms

• Use-Cases + Sleep Flow

• AUTOSAR Integration

• Proposed schemes for 1000BASE-T1

• Conclusion

PUBLIC 2

TC-10 Timeline

PUBLIC 3

TC-10 Timeline for 1000BASE-T1 in OPEN Alliance

Draft 1 Draft 2

Concepts

Q1 2019 Q2 2019 Q3 2019Q2 2018

Interoperability Test Spec

Conformance Test Spec

PUBLIC 4

Wakeup & Sleep

Landscape

PUBLIC 5

Energy Efficient Ethernet (EEE) - IEEE802.3az

• Intended use-case:

− Reduce PHY current consumption while link is active but not utilized

− Asymetric loading (e.g. camera use-case)

• How it works:

− Link in low-power sleep mode when no frames are transmitted

− Link is quiet during this time

− Periodic refresh to keep PHYs in sync

• Prone to re-training due to failed fast recovery

• Not suiteable for garage or parking use-cases (deep sleep)

QUIETAC

TIV

E

SLE

EP

RE

FR

ES

H

QUIET RE

FR

ES

H

QUIET

WA

KE

AC

TIV

E

PUBLIC 6

Power over Dataline - PoDL

• Power sourcing equipment (PSE) puts power on

the data lines

• Powered Device (PD) draws current

• Sleep mode supported

− PSE provides 3.3 V < 1mA as standby supply

• Entering / exiting lower power modes over optional serial interface (SCCP)

− SCCP only available when power-off or when in sleep mode

• Sleep mode strongly linked to power delivery

[1] http://www.ieee802.org/802_tutorials/2015-11/PoDL_tutorial_1115.pdf

[1]

PUBLIC 7

TC-10 Wakeup / Sleep

• Intended to replace the legacy, dedicated wakeup line (wire) in the wiring harness

• Based on three fundamental primitives

− Wakeup of passive link segment

− Wakeup-forwarding over an active link (broadcast wakeup)

− Handshaking Sleep of an active link segment

• Fast wakeup of individual links and a global topology

− Less than 2 ms for a passive link wakeup

− Less than 104 ms for a 7-hop wakeup

• Wakeup / sleep commands as part of PHY

− Significantly less latency compared to Layer 2 mechanism

− Forwarding a wakeup does not need an active link

− No µC interaction required for processing and forwarding

PUBLIC 8

Sleep/Wake-up Service Primitives

• Ingoing primitives have to be triggered by

user

− Sleep.request, Wakeup.request,

SleepAbort.Request

• Outgoing primitives have to be consumed

by user

− Sleep.Indication, Wakeup.Indication,

SleepFail.Indication

• No register map defined at this time

• Vendor specific extensions exist

• Similar or identical interface for Gigabit

PUBLIC 9

Example Use-Case

PUBLIC 10

Example Topology

PHY

uC

PHY

uC uC

PHY

…

PHY

uC

Switch SwitchuCuC

PHYPHYPHYPHYPHY PHY

PUBLIC 11

Sleep Over Active Link

Use-case: Switch wants to power-off cameras

Switch SwitchuCuC

PHYPHYPHYPHYPHYPHY

PHY

uC

PHY

uC uC

PHY

…

PHY

uC

LPS

LPS

SleepReq

uest(LPS)

PUBLIC 12

Sleep Over Active Link

Use-case: Switch wants to power-off cameras

Switch SwitchuCuC

PHYPHYPHYPHYPHYPHY

uC uC uC

PHY

…

PHY

uC

PHY PHY

PUBLIC 13

Wakeup Over Passive Link

Use-case: Switch wakes cameras up

Switch SwitchuCuC

PHYPHYPHYPHYPHYPHY

uC

PHY

uC

PHY

uC

PHY

…

PHY

uC

W

U

P

W

U

P

Wa

ke

up

Re

qu

estP

atte

rn

(WU

P)

PUBLIC 14

Wakeup Over Passive Link

Use-case: Switch wakes cameras up

Switch SwitchuCuC

PHYPHYPHYPHYPHYPHY

uC

PHY

uC

PHY

uC

PHY

…

PHY

uC

PUBLIC 15

Wakeup Forwarding Over Active and Passive Link

(WUP and WUR)Use-case: Wakeup event at gear selector wakes entire system

Switch Switch

uCuC

PHYPHYPHYPHYPHYPHY

uC

PHY

uC

PHY

uC

PHY

…

PHY

uC

Subsystem in Sleep

Wa

ke

up

Re

qu

estW

U

R

PUBLIC 16

Wakeup Forwarding Over Active and Passive Link

(WUP and WUR)Use-case: Wakeup event at gear selector wakes entire system

Switch Switch

uCuC

PHYPHYPHYPHYPHYPHY

uC

PHY

uC

PHY

uC

PHY

…

PHY

uC

Subsystem in Sleep

Wa

ke

up

Re

qu

estW

U

R

W

U

P

WUP

W

U

P

PUBLIC 17

Wakeup Forwarding Over Active and Passive Link

(WUP and WUR)Use-case: Wakeup event at gear selector wakes entire system

Switch Switch

uCuC

PHYPHYPHYPHYPHYPHY

uC

PHY

uC

PHY

uC

PHY

…

PHY

uC

PUBLIC 18

Sleep Handshake (100BASE-T1)

Normal

(Link Training)

Sleep

REQ

Normal

(Link Training)

Sleep

SilentSilent

Sleep.indication

Wakeup.request

Sleep_RequestLPS

Normal NormalLoc_sleep_req

Sleep_ACK

LPS Sleep.indication

WUP

Time window

to abort

sleep

Sleep

Requestor

Sleep

Responder

PUBLIC 19

AUTOSAR Integration

PUBLIC 20

AUTOSAR Network Management – Partial Networking

• In AUTOSAR, the Network Management (NM) is responsible for making decisions of powering communication HW on and off

• Network elements are managed based on partial networks, not as individual items

• Partial networking → only a subset of the elements in a network (nodes and links) need to be active at the same time

− CAN: Only a subset of nodes on a bus active

− Ethernet: Only a subset of endpoints, bridges and links active

SWT SWT

PN1, PN2EP

EP

EP

EP

PN2 PN1

PUBLIC 21

AUTOSAR Network Management Today

• Wake-up: Performed via global wake-up line. No Ethernet involvement

• Sleep: Decided according to User Datagram Protocol (UDP) based protocol

• Currently only the sleep procedure

is involving Ethernet

• Concept for Wakeup over Dataline

(WoDL) based on TC-10 is under

standardization in AUTOSAR

PUBLIC 22

Requirements for

1000BASE-T1

PUBLIC 23

Requirements for 1000BASE-T1 Wakeup and Sleep

• Target is to reuse non-functional requirements as available from 100BASE-T1

defintion.

• 29 baseline requiremnts

− Wakeup indication over dedicated pin and MDIO

− Wakeup forwarding configurable on a per-port basis

− System timing

▪ Wakup over passive link < 2 ms

▪ Wakeup over aktive link < 1 ms

▪ Forward over passive device (e.g. bridge) < 15 ms

▪ Forward over active device (e.g. bridge) < 2 ms

PUBLIC 24

What needs to be done

1000BASE-T1

PUBLIC 25

Open Tasks to Extend 802.3bp

Mapping the wakeup pattern (WUP) to a 802.3bp code pattern

An obvious candidate is the link training patternFirst proposals

available

Mapping Wakeup request (WUR) and LPS (TC-10 Low-power sleep) to PCS

An obvious candate is the OAM channel

First proposal

available

Fine-tune the TC-10 handshake statemachine to 802.3bp specificsFirst proposal

available

Extend 802.3bp PHY Control statemachine to transmit wakeup pattern (WUP)First proposal

available

PUBLIC 26

Conclusion

• TC-10 Wakeup and Sleep mechanism orthogonal to

− Energy Efficient Ethernet - EEE

− Power over Dataline – PoDL

• Wakeup and sleep 1000BASE-T1 will share the concept with 100BASE-T1

− Wakeup over passive link

− Wakeup request / forward over active link

− Sleep Handshake

• Next steps:

− Map the coding primitives / commands for WUP, WUR, LPS

− Finish the PHY control statemachines

• TC-10 concept is picked up – AUTOSAR

PUBLIC 27

OPEN ALLIANCE TC-10 (ISO21111) Development kit

ADTJA1101-RMII

(TJA1101 Daughter Card)

S32K148EVBQ176

(S32K Eval board)

SJA1105SMBEVM

GW Prototyping Platform

(incl. TJA1102/S)

PUBLIC 28

THANK YOU

Questions?

PUBLIC 29

BACKUP

PUBLIC 30

OAM Introduction

• Operations, Administration, and Maintenance (OAM)

− In-band layer-1 communication between PHYs (not propagated to MAC and above)

− Intended for link monitoring, health status (SQI)

− OAM optional (mandatory if EEE is implemented)

− Part of the PCS (Clause 97.3.8)

• OAM Message

− Message Number + Message

− Mechanism to acknoweldge the reception of the last message

• Jump onto OAM to transmit TC-10 codes (much like EEE’s LPI)

PUBLIC 31

OAM Frame

• Fields available for TC-10 use: • OAM Message Number: “user-defined and its definition is outside the scope of this standard.”

• OAM Message Data: „The 8-octet message data is user-defined and its definition is outside the scope of this standard.”

• Reserved bits Symbol 0

Custo

mer

defin

ed

Std defined

NXP and the NXP logo are trademarks of NXP B.V. All other product or service names are the property of their respective owners. © 2016 NXP B.V.