+ All Categories
Home > Documents > What Channels Should be Considered by the IEEE 802.3ap...

What Channels Should be Considered by the IEEE 802.3ap...

Date post: 13-Mar-2021
Category:
Upload: others
View: 1 times
Download: 0 times
Share this document with a friend
32
What Channels Should be Considered by the IEEE 802.3ap Signaling Ad Hoc? John D’Ambrosia Tyco Electronics November 16, 2004
Transcript
Page 1: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

What Channels Should be Considered by the IEEE 802.3ap Signaling Ad Hoc?

John D’AmbrosiaTyco Electronics

November 16, 2004

Page 2: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

2

SupportersRob Brink Agere Charles Moore AgilentShannon Sawyer AgilentJoe Smetana Alcatel Doug Beumeler ArrayCommMike Shahine CienaJinhua Chen EMC Rich Graham EnterasysArne Alping Ericsson ABIngvar Fröroth Ericsson AB Tad Hofmeister IndependentGlen Koziuk Independent Del Hanson InfineraAnthony Sanders InfineonKevin Bross IntelAniruddha Kundu Intel Michael Altmann Intel Richard Mellitz Intel Brad Booth Intel Schelto Van Doorn Intel Bill Peters Intel

Jack Houde KaparelRobert Jardon Jardon Engineering Mary Mandich Lucent Jeff Sinsky Lucent Hans-Joechin Goetz LucentChuck Byers LucentAndrew Adamiecki LucentBryan Parlor Nortel Bert Simonivich Nortel Graeme Boyd PMC-SierraJohn Doody StratusSteve Mango StratusBob McCormick StratusBill Hoppin SynopsysJohn Stonick SynopsysJimmy Sheffield Tyco Electronics Majid Barazande-Pour VitesseJohn Khoury Vitesse Apoorv Srivastava Vitesse

Page 3: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

3

To DateInformative model (See Slide #13 goergen_03_0904) based on “improved FR-4” and 0.030” stub has been proposed

Looks reasonable in loss dominated channelsChannel data with longer stubs or resonant behavior (nulls, ripple) have been shown to fail proposed informative channel modelDebate over whether channels that have longer stubs and resonant behavior should be considered by Signaling Ad Hoc

Signaling methodology implicationsCost implications – how much counterboring would be required?Extent of Broad Market Potential debate

Debate over amount of frequency content – Nyquist? 3rd

harmonic?

Page 4: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

4

ObservationsActual performance measurements on channels -

Nulls in 6 to 7 GHz regionSimilar loss characteristics to proposed model

Simulations have shown various implementations can solve loss dominated systemsSimulations have shown implementation sensitivity to being able to deal with channels that have nulls in 5 to 7 GHz regionSimulations have shown that channels above the model with ripple can be challenging

Page 5: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

5

16, 17sinsky_01_0904..pdfTesting, no xtalk, hand-built implementation10^-14 BER demonstratedData pattern – PRBS 2^31-1(Analysis with NRZ – see abler_01_0904, lui_01_0904, Analysis with PAM-4 – see lui_01_0904)

DuobinaryTyco Case #2Loss dominated< 6 GHz Ripple at informative model> 6 GHz below informative model

3

25, 26, 27hoppin_01_0304..pdfTesting 5G part overdriven , with xtalk10^-12 BER demonstrated across all channels for multiple configurationsData pattern – PRBS 2^31-1(Analysis with NRZ and duobinary not available)

PAM-4Tyco QuadRoute Backplane (13SI) – SynopsysLine CardsMixture of channels - Loss dominated, stub, ripple effectsAbove and below proposed model depending on configuration

4

12, 15lui_01_0904.pdfSimulation with xtalk10^-15 BER Results for some implementations for bothData pattern - ?(Analysis with duobinary not available)

NRZ / PAM-4Tyco Case #3 – Margin CaseLoss dominated –below proposed informative model

2

12 13, 14abler_01_0904.pdfSimulation with xtalk10^-17 BER Results for some implementationsPackaging had impactsData pattern – random(Analysis with PAM-4, see lui_01_0904, Analysis with duobinary not available)

NRZTyco Case #3 – Margin CaseLoss dominated – below proposed informative channel model

1

Reference Backup

Slide

Reference Presentation

Analysis & Results DescriptionModulationScheme

Channel DescriptionScenario

Loss Dominated Channels

Page 6: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

6

16, 18sinsky_01_0904.pdfTesting, no xtalk, hand built implementation10^-14 BER demonstratedData pattern – PRBS 2^31 -1(Analysis with NRZ and PAM-4 not available)

DuobinaryTyco Case #6 - Modification< 6.5 GHz – above proposed model6.5 GHz – 11 GHz – null dominated, below channel model

1

21 22, 23abler_01_0904.pdfSimulation with xtalk10^-12 OR 10^-17 BER - limited # of implementations could passPackaging had impactsData pattern – random(Analysis with PAM-4, see lui_01_0904, analysis with duobinary not available)

NRZTyco Case #6 –< 6.5 GHz – above proposed model6.5 GHz – 11 GHz – null dominated, below channel model

3

21, 24lui_01_0904.pdfSimulation with xtalk10^-15 BER Results for some implementationsData pattern - ?NRZ - 1 more tap than Scenario #2 loss dominated necessaryPAM-4 – more margin than loss dominated results shown in Scenario #2(Analysis with duobinary not available)

NRZ / PAM-4

Tyco Case #6 < 6.5 GHz – above proposed model6.5 GHz – 11 GHz – null dominated, below channel model

4

25, 26, 27hoppin_01_0304..pdfTesting 5G part overdriven, with xtalk10^-12 BER demonstrated across all channels for multiple configurationsData pattern – PRBS 2^31-1(Analysis with NRZ and duobinary not available)

PAM-4Tyco QuadRoute Backplane (13SI) – SynopsysLine CardsMixture of channels - Loss dominated, stub, ripple effectsAbove and below proposed model depending on configuration

5

19, 20koziuk_01_0904.pdfSimulation, with xtalkOpen Eye, No BER statedData pattern – PRBS 2^31-1(Analysis with NRZ and PAM-4 not available)

DuobinaryTyco XAUI Backplane, 34” channel (4000-2 material)< 5 GHz – similar loss to proposed model> 5 GHZ null dominated, below channel model

2

Reference BackupSlide

Reference Presentation

Analysis & Results DescriptionModulationScheme

Channel DescriptionScenario

Stub Dominated Channels

Page 7: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

7

25, 26, 27hoppin_01_0304..pdfTesting 5G part overdriven, with xtalk10^-12 BER demonstrated across all channels for multiple configurationsData pattern – PRBS 2^31-1(Analysis with NRZ and duobinary not available)

PAM-4Tyco QuadRoute Backplane (13SI) – Synopsys Line CardsMixture of channels - Loss dominated, stub, null efectsAbove and below proposed model depending on configuration

1

28, 29, 30abler_01_0904.pdfSimulation with xtalk10^-12 BER demonstrated for some implementations10^-17 BER demonstrated (packaging had impact) for some implementationsData pattern – Random(Analysis with PAM-4, see lui_01_0904, analysis with duobinary not available)

NRZTyco Case #7 Above proposed model with increased ripple

2

28, 31lui_01_0904.pdfSimulation, with xtalk10^-15 BER demonstrated for some implementations for bothData pattern – ?(Analysis with duobinary not available)

NRZ / PAM-4

Tyco Case #7 Above proposed model with increased ripple

3

Reference Backup

Slide

Reference PresentationAnalysis & Results DescriptionModulationScheme

Channel DescriptionScenario

Ripple Dominated Channels

Page 8: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

8

Channel ChallengesLossDeep Nulls and ripples that go below the loss curveRipple on channels above the loss curve

Premature to use proposed informative channel model as a filter for deciding what test cases should be considered

Page 9: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

9

Aspects of Channel

FNULL

• Informative model loss seems reasonable

• FNull, the frequency of the 1st crossing of the proposed informative channel model caused by one or more nulls, needs to be considered

• Ripple needs to be considered

• Above the model

• Partial channel response below the model

• Current Informative mask set limited

• Subsequent analysis of channel data by Signaling Ad Hoc -

• Determine FNull

• Deterimine ripple characteristics

Page 10: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

10

ConclusionsNeed to consider channel data regardless of whether it meets current proposed informative model

Informative model drove loss, but signaling methodology will impact FNull and Ripple limitsFuture modifications of informative model will be possible based on analytical work on channel dataUse of time domain information for channel model?

To allow a fair trade-off, Signaling Ad Hoc needs to standardize all parameters outside of the consideration of the Channel Ad Hoc, i.e. TP1 to TP5More than channel pass / failure criteria necessary and needs to be evaluated

PowerImplementation issues

Page 11: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

11

BACKUP SLIDES

Page 12: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

12

Case #3

See dambrosia_01_0904.pdf

Page 13: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

13See abler_01_0904.pdf

Page 14: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

14See abler_01_0904.pdf

Page 15: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

15See lui_01_0904.pdf

Page 16: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

16See sinsky_01_0904.pdf

Page 17: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

17See sinsky_01_0904.pdf

Page 18: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

18See sinsky_01_0904.pdf

Page 19: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

19See koziuk_01_0904.pdf

Page 20: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

20See koziuk_01_0904.pdf

Page 21: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

21

Case #6

See dambrosia_01_0904.pdf

Page 22: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

22See abler_01_0904.pdf

Page 23: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

23See abler_01_0904.pdf

Page 24: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

24See lui_01_0904.pdf

Page 25: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

25

10G Payload Measured Feasibility Data

6 backplane configurations4000-6, 4000-13, 4000-13SI, 6000, 6000SI, and ISOLA 6204.75 mil wide traces (4 mil on 4000-6 variants)

3 Lengths8”, 22” and 36” lengths

3 types of HM-Zd signal routing (4 FEXT, 4 NEXT)

QuadRoute Tx to Tx, Rx to RxQuadRoute Tx to Rx, Rx to TxNon QuadRoute

Rx_3Rx_2Rx_1Rx_0Column 6

Tx_3Tx_2Tx_1Tx_0Column 5

Pair G/HPair E/FPair C/DPair A/B

See hoppin_01_0304.pdf

Page 26: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

26

Accelerant Networks / Synopsys Measured 10G Payload Data

1 C2

1 C3

2 C0

2 C1

2 C2

2 C3

1 C0

1 C1

5G PAM4 .13u device running at 10G. Gray Encoding, 0% Overhead

All 8 pairs active on QuadRoute FR4 4000-13SI, full crosstalk conditions (4 FEXT, 4 NEXT)

All devices tested to BER 10^-12 using 2^31 PRBS Pattern over 36 inches

8” and 22” link conditions across all 6 materials passed BER 10^-12 using 2^31 PRBS Pattern

Out of 336 links tested, 34 36” link configurations did not pass and will be the subject of future simulation work on a mutually agreed to channel model with purpose built 10G designs

See hoppin_01_0304.pdf

Page 27: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

27

10Gb/s with PAM-4 to 10^-12 BER with Crosstalk Across These Channels**

** Note – Measurements are channel approximations. Actual line cards had active devices on them. Channel measurements made with passive SMA line cards

Active cards – 3”

Passive line cards – 2”

Page 28: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

28

Case #7

See dambrosia_01_0904.pdf

Page 29: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

29See abler_01_0904.pdf

Page 30: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

30See abler_01_0904.pdf

Page 31: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

31See lui_01_0904.pdf

Page 32: What Channels Should be Considered by the IEEE 802.3ap ...grouper.ieee.org/groups/802/3/ap/public/nov04/dambrosia...Testing 5G part overdriven, with xtalk hoppin_01_0304..pdf 25, 26,

32

Vendor Quote - Nortel“Nortel supports a channel model that addresses legacy backplanes (2.5G/3.125G) with significant via stubs (no back drilling). ATCA full mesh and dual star backplanes should be used as a reference legacy backplane example for the standard.”

Bryan ParlorNortel Networks


Recommended