Baseline Proposal EFM_PHY_rev 0.3

Transcription

1 Baseline Proposal EFM_PHY_rev 0.3 Behrooz Rezvani, Ikanos communications, editor 802.3ah Michael Beck, Alcatel, co-author Steven Haas, Infineon, co-author

2 Supporters for Ethernet over VDSL Hugh Barrass, Cisco systems, Chair 802.3ah Copper Sub Task Force Behrooz Rezvani, Ikanos Communications, Editor IEEE 802.3ah Michael Beck, Alcatel Steven Haas, Infineon Craig Easley, Extreme Networks, President EFMA

3 Table of Contents EFM_PHY_r0.3 Arriving to EoVDSL Architectural and protocol requirements Architectural description PHY interfaces PHY rate matching VDSL_PHY specifications Referenced ANSI, ETSI and ITU-T documents OA&M Referenced band plans Simulation and conformance test criteria Summary and conclusion Appendix: additional work to complement VDSL

4 Arriving to EoVDSL Section 1.0

5 Arriving to EoVDSL Goals Specify a PHY which is compliant with IEEE Architecture and which covers all the objectives of the EFM Task Force (Cu track): 10Mbps full duplex on a single 750 meters Spectrally Compatible WW Optional Multi-pair Mode Additionally leverages ITU-T G Reference Layered Protocol Architecture

6 Arriving to EoVDSL Principles When applicable to EFM, take text from existing standards as is. Add specifications for parts that are not standardized elsewhere.

7 Arriving at EoVDSL Standardized VDSL as basis for EFM-Copper PHY This presentation provides the details and open issues: How standards-based VDSL can be used as the basis for 802.3ah PHY Sublayers can be taken, from ANSI/ETSI/ITU standards for VDSL Changes/additions need to be defined by the EFM in order to create a definition that meets public network standards and IEEE PAR objectives VDSL is standardized in: ETSI TS (requirements) and TS (specification) T1E1 s draft trial use standard <LB941-D> ITU s G.993.1

8 Architectural and Protocol Requirements Section 2.0

9 Architectural and Protocol Requirements Overall interfaces MII MDIO/MDC PCS Rate Matching Proposals Loop Aggregation proposal MII to PTM mapping Gamma interface 802.3ah link management functions Rate setting Mode setting EOC (HDLC) Management interface PMA PMD PTM-TC (Packet layer) OC-TPS-TC PMS-TC (Framing, Error correction,interleaving) PMD Media and service splitter definitions Layer control VOC control Link state machine Covered in VDSL standards

10 Architectural and Protocol Requirements IEEE (10/100 Mbps) LLC Logical Link Control MAC Control (Optional) MAC Media Access Control Reconciliation MII PCS PMA PMD MDI voice grade Cu Minimal changes are allowed here if necessary. The approved PAR authorizes the EFM Task Force to specify these layers.

11 Architectural and Protocol Requirements ITU-T G reference model γ-c interface α interface U-C interface Packet Entity Packet Entity PTM-TC PTM-TC PMS-TC PMS-TC PMD PMD voice grade Cu γ-r interface β interface U-R interface The red blocks have been specified for different media/service requirements. The green blocks have been declared out of scope by ITU-T, and can be used for EFM.

12 Architectural and Protocol Requirements Merged Model MAC Control (Optional) MAC Media Access Control Reconciliation MII PCS Ethernet-over-VDSL PTM-TC PMA PMS-TC PMD PMD MDI voice grade Cu From IEEE TO BE DEFINED From existing VDSL standards

13 Architectural and Protocol Requirements PMS-TC/PMD MAC Control (Optional) MAC Media Access Control Reconciliation PCS PMA PMD MII Ethernet-over-xDSL AL PTM-TC PMS-TC PMD MDI voice grade Cu FEC Framing Modulation (VDSL)

14 Architectural and Protocol Requirements PMS-TC/PMD ITU-T G.993 Transceiver Specifications G VDSL VDSL technical foundation Different regional band plans approved by ITU-T. At this time, the Recommendation does not yet specify the modulation method. A pointer to the physical layers of the T1E1.4 Trial Use standard is appropriate. Specifies TPS-TC sublayers

15 Architectural and Protocol Requirements PMS-TC/PMD ITU-T G.99x reference documents G Handshaking Procedures for DSL Transceivers G Overview of DSL Recommendations G Test Procedures for DSL Transceivers G Physical Layer Management for DSL Transceivers

16 Architectural and Protocol Requirements PTM-TC MAC Control (Optional) MAC Media Access Control Reconciliation MII PCS PMA PMD Ethernet-over-xDSL AL PTM-TC PMS-TC PMD MDI voice grade Cu Encapsulation Error Detection Idle Byte Insertion

17 Architectural and Protocol Requirements PTM-TC description Transmit PTM-TC Layer performs HDLC encapsulation Byte stuffing mode 0x7E Bytes are inserted between packets CRC-16 Receive PTM-TC Layer performs decapsulation Every received packet is sent to the Packet Entity, an error signal is provided at the end of the packet (OK/CRC/abort) Interfaces With the physical layer: α/β-interface With the Packet Entity: γ-interface (PTM-TC controls the flow)

18 Architectural and Protocol Requirements PTM-TC References Architecture and γ-interface ITU-T Annex H /G ITU-T Liaison Letter SC-097R2.pdf

19 Architectural and Protocol Requirements Ethernet-over-VDSL Adaptation Layer MAC Control (Optional) MAC Media Access Control Reconciliation PCS PMA PMD MII Ethernet-over-VDSL AL PTM-TC PMS-TC PMD MDI voice grade Cu Flow Control Frame pre-processing Aggregation

20 EoVDSL PHY Rate Matching and loop aggregation Section 3.0

21 EoVDSL PHY Rate Matching References, separate baseline propsoals Flow Control MII: Arthur Marris proposal marris_1_0302 Aggregation fosmark_1_0302.pdf. It will be covered in a separate baseline proposal

22 EoVDSL PHY Rate Matching and loop aggregation Reference Model for Rate Matching and Loop Aggregation MAC Media Access Control MII Reconciliation Rate Matching Loop Aggregation The architecture requirements of this proposal require loop aggregation to be carried out above the γ-interface. Klaus Fosmark s presentation points out how this can be done. PTM-TC PMS-TC PMD MDI voice grade Cu PTM-TC PMS-TC PMD MDI voice grade Cu

23 EoVDSL Specifications Section 4.0

24 EoVDSL Specifications VDSL reference model ª -O Hypothetical application independent interface (HAPI) Æ Hypothetical application independent interface (HAPI) ª -R U 2 -O U 1 - O U 1 -R U 2 -R Application Specific Network Interface LT PTSN or Splitter NID Splitter RT PTSN or Application Specific Customer Interface ISDN PMS-TC & PMD NID- Network Interface Device protection and distribution cable termination ISDN PMS-TC & PMD VTU-O VTU-R The VDSL reference model, chapter 5.1 VDSL-Part 1/T1E1.4 There are 2 types of devices: VTU-O: The master device, located in the switch/line card VTU-R: The slave device, located in customer s premises (such as a NIC or CPE) Service splitter allows the loop to be shared with POTS or BR-ISDN The VTU-R (NT) resembles the VTU-O except: Network timing reference (NTR) is an output Device acts has a slave link state machine and is controlled by the VTU-O

25 EoVDSL Specifications The PMD layer (T1E1.4 VDSL Part 1, section 8) Two line codes are referenced by section 8 of ANSI s part 1: QAM PMD is defined in part 2 of VDSL spec (T1E1.4) DMT PMD is defined in part 3 of VDSL spec (T1E1.4) A T1E1 trial use standard is valid for two years with both line codes supported during this period Power control and line interfacing performed by PMD layer

26 EoVDSL Specifications PMD details Parts 2 & 3 of T1E1.4 Baseline PMD proposal includes: All items covered in parts 2 and 3 of T1E1.4 trial use spec PMD MIB parameters Profiles (as appropriate) Control functions (via Code words, EOC/VOC, link state?) Simplifications where applicable Common elements between line codes will be consolidated States, PSD masks

27 EoVDSL Specifications PMD items defined in VDSL pt 1 (i) Section 5.5 coexistence with POTS & ISDN (also section 12) Do we need ISDN co-existence? Regional Annex (A,B,C)? Sections 5.6, 5.7 remote power and repeater not needed Section 6 transport capacity & performance Payload rates better defined in parts 2 & 3 than part 1 Define profiles / parameters for the MIB? Performance requirements Probability of error 10-7 (with 6dB margin) This is effective BER with RS FEC

28 EoVDSL Specifications PMD items defined in VDSL pt 1 (ii) Section 7 U interface PSD templates/power use as is? Spectral Plan 998, 997, Fx, proprietary? Allow variances (via MIB parameters) or fix? PnP compatibility with multiple spectra? Section Power control (includes UPBO) PBO mask or better technique? Termination impedance, return loss, signal balance All as is Connector definition? Demarcation point for standard

29 EoVDSL Specifications PMA layer (PMS-TC) Header Data PMS-TC sublayer Header Mux MUX Scrambler FEC Interleaver PMS-TC management To PMD management I- interface PMD sublayer To/from PMD PMA mostly common between line codes Scrambler, FEC, Interleaver all common I-interface (to PMD) Only one data stream (Tx + Rx) EOC, VOC defined as part of frame across I-interface Latency Single latency only with programmable delay

30 EoVDSL Specifications Transmission Convergence reference model (VDSL Part 1, section 9) TPS-TC Packets The Packet TPS-TC is specified in ITU- T G (not yet in T1E1) TC Sublayer TPS-TC sublayer PMS-TC sublayer PMD sublayer VTU-R Header Mux Internal interfaces for different application transport protocols NTR (8 khz) VTU-O Header Fast Slow EOC RX TX RX TX RX TX TPS-TC TPS-TC TPS-TC ATM ATM Packets MUX_F.... Fast Scrambler FEC F MUX To/from PMD MUX_S VOC.... Slow Scrambler FEC Interleaver S TPS-TC OC OAMEntitiy γ-interface I- interface Defined in Part 1 TPS-TC management Æ/ interface PMS-TC management To PMD management Only the interleaved (slow) path is supported Defined in Part 2 & 3 Only two TPS-TC functions supported: Packet Transfer Mode as defined in Annex H / G VDSL embedded operations channel (EOC) PCS (TPS-TC) is common for both line codes

31 EoVDSL Specifications The T1E1 VDSL link state machine No (Quiet) Power-off (Service Installation or change) Power-up Request Power Down Power-up Request Power loss Cold-Start (Time out = T1) Yes No Applied if sync loss occured in Idle Steady-State Transmission Warm-Start (Time out = T2) Yes No Yes Sync Recovery Sync. loss Resume-on-Error (Time out = T4) Time out = T5 Loss of Sync. (Loss of Signal) Power loss Idle Request Idle Back-to-Service Request Yes Warm-Resume (Time out = T3) No Sync. loss Power loss Areas for work Simplification, unnecessary states? Warm start, Resume on error, Power down, Loss of sync, Warm resume, Idle Timing & stability, define hysteresis

32 PCS Encapsulation Between MII interface and alpha/beta interface TBD HDLC as defined in annex H / G b/66b Errored frames are handled as defined by ITU OAM Needs liaison with OAM track

33 EoVDSL Operation and Maintenance Section 5.0

34 EoVDSL Operation and Management An operational channel is defined for VDSL (VDSL Part 1/T1E1.4, section ) Internal interfaces for different application transport protocols γ-interface OAMEntitiy TPS-TC Packets TC Sublayer TPS-TC sublayer PMS-TC sublayer PMD sublayer NTR (8 khz) VTU-O VTU-R Header Mux EOC Other TPS-TC RX TX RX TX RX TX Header Fast TPS-TC ATM Slow TPS-TC ATM MUX_F.... Fast Scrambler FEC F MUX..... To/from PMD The operational channel TPS-TC is part of the VDSL standard Management controls the usage of the VDSL operational channel (VOC) messages All VDSL management functions can be controlled with the VOC Contribution simon_1_0302.pdf defines PMD control mechanism MUX_S.... Slow Scrambler FEC Interleaver S VOC TPS-TC OC I- interface Defined in Part 1 TPS-TC management Æ/ interface PMS-TC management To PMD management Defined in Part 2 & 3 Bit level indications

35 Summary Existing VDSL standards provide a definition of lower PHY sublayers Upper sublayers must be added by EFM Simplification improves uniformity, Ethernet compatibility & interoperability EoVDSL will meet the EFM copper objectives: >= 750 meter with >= 10Mbps full-duplex payload bit rate can be met with Plan 998 in US and Japan, Band Plan 997 in Europe Plan 998 is more asymmetric. Plan 997 is more symmetric Compliant with spectral management standard and frequency plans approved by T1.417, ITU-T,NRIC, and ETSI/TM6

36 Appendix A: any new work New PSDs may be needed for private networks. Medium reach may be defined in IEEE objectives HDLC encapsulation may not be optimal for Ethernet frames, but it allows a generic architecture that accommodates any kind of packets.

37 References Steven Haas, NC meeting presentation Miachael Beck, NC presentation Behrooz Rezvani