EPON Powersaving

via Sleep Mode

Jeff Mandin
PMC-Sierra
September 2008

Sept 2008

Target and Scope

Goal is to introduce a flexible powersaving solution for

EPON/10GEPON system for long term use
Proposal for Protocol-Based Power Saving with:
- ONU going to sleep during idle periods (ie. sleep mode)
- Handshake model
Not included in this outline:
- Particulars of handshake protocol (eg. PCS codes, PDUs,
etc.)
- To be addressed later

- Specific components that will be turned off during sleep

- Vendor-specific and out-of-scope

Sept 2008

Conceptual Model

For the purposes of these slides, assume the

following model:
OLT
Power save function

ONU
Power save function

Optics

Sept 2008

Electronics

Control Message Flow

(OLT-initiated and terminated)
ONU

OLT
SLEEP

2. ONU puts itself to sleep

for indicated period
3. Prior to the end of the
sleep period, ONU wakes
itself up
5. ONU sends
SLEEP_REQ to indicate that
it wants to resume sleep

Wakeup Time specified by OLT

GATE

Max Sleep Time

6. OLT instructs ONU to go

back to SLEEP

Wakeup Time specified by OLT

GATE

9. ONU sends SLEEP_REQ

4. After the end of the sleep

period, OLT sends GATE to
the ONU

SLEEP_REQ

SLEEP

7. ONU goes back to sleep

for indicated period

1. OLT instructs ONU to

SLEEP. Stops sending data
to the ONU.

8. After the end of the sleep

period, OLT sends GATE to
the ONU

SLEEP_REQ
Max Sleep Time
DATA

Sept 2008

10. OLT denies sleep

request, sends data

Control Message Flow

(ONU-initiated and terminated)

ONU

OLT
SLEEP_REQ

1. ONU asks to go to sleep

Max Sleep Time

SLEEP

3. ONU puts itself to sleep

for indicated period
4. Prior to the end of the
sleep period, ONU wakes
itself up
6. ONU sends
SLEEP_REQ to indicate that
it wants to continue sleep
8. ONU goes back to sleep
for indicated period

Wakeup Time specified by OLT

GATE

Sept 2008

5. After the end of the sleep

period, OLT sends GATE to
the ONU

SLEEP_REQ
Max Sleep Time
SLEEP

7. OLT instructs ONU to go

back to SLEEP

Wakeup Time specified by OLT

GATE

10. ONU sends REPORT to

indicate that it has data to
send

2. OLT instructs ONU to

SLEEP. Stops sending dat a
to the ONU.

REPORT

9. After to the end of the

sleep period, OLT sends
GATE to the ONU

Assumptions for 10G power estimates

1. Assumptions for Standby power consumption of components:
-

TRx consumes 3.5W while awake, 0W while sleeping

SoC consumes 2W while awake and .4W while sleeping
.15W constant for onhook SLIC
DDR consumes .7 while active, .02 in sleep (self-refresh)
UNI port is assumed to be inactive
With no sleep: PowerConsumed = 3.5+2+.15+.7 = 6.35W
In interval between wakeups: PowerConsumed = 0+.4+.15+.02 =
0.57W

2. Assumptions for Wakeup Time following sleep:

Sept 2008

Conservative assumption: 5ms to power up and synchronize,

.5ms to send data from ONU to OLT

Aggressive assumption: is 2ms to power up and synchronize,

.2ms to send data from ONU to OLT

Effectiveness
10G Sleep mode (Aggressive wakeup
assumptions)

Total power
consumption
Electrical
component
consumption
Transceiver
power
consumption

Power Consumption (W)

7
6.35

6
5
4
3.50

3.02
2.85

2
1

1.82
1.48
1.53

1.41

1.20

0.751.06
0.510.90 0.82
0.38

0
0

10

20

0.99

0.82

0.74
0.25

30

0.73

0.67
0.15

40

50

60

Sleep Time (ms)

7

Sept 2008

0.70

0.63
0.10

70

80

0.62
0.08

90

100

Summary

1. Sleep mode enables a steep dropoff in ONU power

consumption
-

around 25-30 ms seems to be best tradeoff between sleep period

and power savings

Can do early wakeup in case of customer-side offhook event

2. ONU Power consumption will drop off in a similar manner even

under different assumptions about component consumption
3. Next Steps:
-

Sept 2008

Details on maintaining service quality

Working out the handshake protocol