healey_02_1108

Embed Size (px)

Citation preview

  • 8/8/2019 healey_02_1108

    1/13

    Observations regarding Energy

    Efficient 1000BASE-KX

    Adam Healey

    LSI Corporation

    IEEE P802.3az Task Force Meeting

    Dallas, TX

    November 2008

  • 8/8/2019 healey_02_1108

    2/13

    2Healey 11/5/2008 IEEE P802.3az Task Force

    1000BASE-KX layer model

    PMA

    PMD

    AUTO-NEGOTIATION

    PCS

    PMA Service Interface

    PMD Service Interface

    MDI

    GMII

    TRANSMIT

    RECEIVE

    SYNCHRONIZATION

    RECEIVETRANSMIT

    Technology-dependent interface

    tx_bit rx_bit

    rx_code-grouptx_code-group

    signal_detect

    link_status

    CLAUSE 36

    CLAUSE 70

    CLAUSE 73

  • 8/8/2019 healey_02_1108

    3/13

    3Healey 11/5/2008 IEEE P802.3az Task Force

    Scope of changes for 1000BASE-KX EEE

    PMA

    PMD

    AUTO-NEGOTIATION

    PCS

    PMA Service Interface

    PMD Service Interface

    MDI

    GMII

    TRANSMIT

    RECEIVE

    SYNCHRONIZATION

    RECEIVETRANSMIT

    Technology-dependent interface

    tx_bit rx_bit

    rx_code-grouptx_code-group

    signal_detect

    link_status

    Low-power idle

    encoding and decoding

    Auto-Negotiation extensions

    Support for quiet-refreshcycles

  • 8/8/2019 healey_02_1108

    4/13

    4Healey 11/5/2008 IEEE P802.3az Task Force

    Summary of issues with Draft 1.0

    PCS encoding and decoding of low-power idle is not completelydefined in Clause 36

    Clause 70 state diagrams incorporate a mixture of PCS and PMDfunctions violating the layering model

    Clause 70 state diagrams define variables and timers that have no

    obvious use

    Clause 70 transmit disable and signal detect requirements are notadequate to ensure reliable transitions to quiet or wake

  • 8/8/2019 healey_02_1108

    5/13

    5Healey 11/5/2008 IEEE P802.3az Task Force

    TX_ACTIVE

    tx_lpi_mode

  • 8/8/2019 healey_02_1108

    6/136Healey 11/5/2008 IEEE P802.3az Task Force

    RX_ACTIVE

    rx_lpi_mode

  • 8/8/2019 healey_02_1108

    7/137Healey 11/5/2008 IEEE P802.3az Task Force

    So, what do we do?

    Define only PMD specific functions in Clause 70

    Transmitter de-activation and re-activation behavior

    Transmitter quiet-refresh cycle timing

    Signal detect assertion and de-assertion behavior

    Rigorously define the low-power idle encoding and decoding processin Clause 36

    Also, may want to take measures to prevent sync_status cycling betweenOK and FAIL during quiet-refresh cycles

    May want to include a watchdog timer to distinguish between quiet-refreshcycles and loss of link

    Define new service interface primitives to support any required inter-sublayer communication

  • 8/8/2019 healey_02_1108

    8/138Healey 11/5/2008 IEEE P802.3az Task Force

    Timing diagram: Sleep to wake

    /I/ or /D/ /LI/

    Ts

    < Tq

    Tw

    Ttd

    Tsd

    Tta

    Ttc

    Tsa

    Tcr

    Tws

    /I/ /I/ or /D/

    Legend

    Ts Sleep time Tsd Receiver signal_detect de-assertion time

    Tq Quiet time Tsa Receiver signal_detect assertion time

    Tw Wake time Tra Receiver activation time

    Ttd Transmitter de-activation time Tcr Receiver timing acquisition time

    Tta Transmitter activation time Tws Receiver PCS synchronization time

    Tra

  • 8/8/2019 healey_02_1108

    9/139Healey 11/5/2008 IEEE P802.3az Task Force

    Framework review

    Assume that transmit and receive functions are deactivated during thequiet periods to conserve energy

    With the exception of the signal detect function

    The transmit functions will take some time to achieve normal operationfollowing activation

    Let Tta be the time it takes for the transmitter to deliver a signal capable of

    triggering the receivers signal detect functionLet Ttc be the time it take the transmitter to achieve compliant operation

    If, during the quiet period, the signal detect function is triggered, then

    receiver functions are reactivatedLet Tsa be the signal detection assertion time. assuming the transmitter isdelivering a suitable signal

    Let Tra + Tcrbe the time it takes the receiver to return to normal operationand recover timing from the incoming signal, assuming the transmitter is

    delivering a compliant signal

  • 8/8/2019 healey_02_1108

    10/13

    10Healey 11/5/2008 IEEE P802.3az Task Force

    Criteria for reliable transition to quiet

    The transmitter differential output voltage required to de-assert signaldetect (Vtq) must be defined

    This voltage should be greater than the peak noise voltage expected at thereceiver

    This voltage is the lower bound of the signal detect de-assertion threshold,Vsd

    The reference time for the measurement of transitions from sleep to quiet isthe point where the peak differential output voltage crosses Vtq

    Similarly, the measurement of transitions from quiet to refresh or wake is thepoint where the where the peak differential output voltage crosses Vtw

  • 8/8/2019 healey_02_1108

    11/13

    11Healey 11/5/2008 IEEE P802.3az Task Force

    Criteria for reliable wake

    Wake time cannot be guaranteed because essential parameters Ttaand Ttc are not constrained

    Transmitter differential output voltage required to trigger signal detect

    (Vtw), at the output of a worst-case channel, must be definedThis voltage must be delivered no later than Tta following activation of the

    transmitter

    The voltage at the output of the channel is established as the signal detect

    assertion threshold, Vtw It must also be larger than the peak noise voltage expected at the receiver

    It is likely that Tsa, Tra, Tcr, and Tws may not be measured individually,

    but values should be established for the purpose of budgeting

    maxmaxmaxmaxmaxmax),max( wscrtcrasataw TTTTTTT ++++

  • 8/8/2019 healey_02_1108

    12/13

    12Healey 11/5/2008 IEEE P802.3az Task Force

    Recommendations

    Use the proposed framework as the basis for updates to Clause 36and Clause 70

    Similar issues exit with 10GBASE-KX4 and 10GBASE-KR

    Review Clauses 48, 49, 71, and 72 in light of these observations

  • 8/8/2019 healey_02_1108

    13/13

    Questions?