3FL00452-S03M01-VDSL2 Advanced

Learning experience powered by
Alcatel-Lucent University
Section 03
VDLS2 advanced
Module 01
VDSL2
3FL00452 Edition 01
@@PRODUCT
@@COURSENAME
@@COURSEPARTNUMBER Edition @@COURSEEDITION
03 · 01 · 1 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

VDSL2 Advanced · 3FL00452 VDSL2
@@PRODUCT · @@COURSENAME
Module objectives
Upon completion of this module, you should be able to:
explain the DSL basics

position VDSL2
list the relevant standards for VDSL2
describe the different band plans and profiles of VDSL2
explain impulse noise and rate adaptation mechanisms
explain the forward error mechanisms used in VDSL2
understand VDSL2 Initialization
understand Spectral Management within VDSL2
describe the use of Upstream and Downstream Power Back Off
list the parameters being measured by DELT
understand VDSL2 bonding
explain the configurable parameters in the XDSL profiles
configure the profiles for VDSL2 ports

VDSL2 spectral management

Power Spectral Density
spectral density:
 PSD = power per unit bandwidth

 Note : usually expressed in (m)Watts (or dBm) per Hertz
 PSD: proportional to power delivered by a signal in a frequency band
 The more power, the higher the crosstalk.

What is crosstalk?
Tx
Near End Crosstalk
Rx Tx
Tx Rx
Rx
Far End Crosstalk
Rx
Crosstalk happens when a receiver listens to the same frequencies where

a nearby transmitter is sending on.
 With the deployment of many different technologies & DSL flavours in the
same cable bundle this has become a complex story.
Signal attenuation by a loop
The transmitted DSL signal is attenuated by the twisted pair:
Twisted pair
Modem:
Transmitter
Signal level
Freq Freq Freq Freq

far-end cross-talk (“FEXT”)
The FEXT noise introduced in a victim modem (at REFV point) is

proportional to “disturber” signal level (at REFA point) .
Binder REFA
Disturber signal 1
Victim signal Modem:
2 Receiver
REFV
Coupling length “lcp” Victim
A received noise needs to be compared with the received signal to

evaluate its impact on the modem performance (“SNR”: Signal-to-Noise
Ratio).

FEXT cross-talk balance: “self” cross-talk
The “FEXT” cross-talk impact strongly depends on the balance between

the victim signal, and the disturber signal.
On the following example the cross-talk is balanced.
Signal
Signal
Freq Binder
1 Freq
CO:
Transmitters CPE 2:
2 Receiver
Signal
Signal
DS Victim
Freqconfiguration is called “self cross-talk”.

 Such cross-talk Freq

FEXT cross-talk unbalance
When the cross-talk is not balanced, some victim receivers will

encounter a very high amount of noise.
This happens when:
 The victim transmitter is not collocated with disturber, but further
 The victim transmitter sends a weaker signal
Signal
?
Binder
1 Freq
Modem:
2 Receiver
Signal
Victim: poor
performance
Freq
Such cross-talk is “abnormal”, and leads to bad performance

Near End Crosstalk (NEXT)
attenuated
US weak signal 998E

cpe
DSLAM
DS strong signal
998ADE
cpe
Strong signal will kill the

weak signal on the other
line
US0 DS1 US1 DS2 US2 DS3 998E
US0 DS1 US1 DS2 US2 DS3 998ADE

VDSL2 PSD masks - ETSI
VDSL2 masks have been created by applying these rules:

 US0: masks similar to ADSL2+ Annex A, Annex B and Annex M
 US1&2: masks similar to ETSI VDSL1 masks P.M1 or P.M2
 DS: envelope of ADSL2+ and VDSL1 Pex.P2.M1 and Pex.P2.M2.
 Except low-frequency edge for B and M masks start at 276kHz, instead of 254kHz of
ADSL2+.
 M1= nominal -60 dBm/Hz above 2.2 MHz (not used much)
 M2= boosted PSD
No difference made in exchange or cabinet deployment
 Cabinet deployment allows use of full ADSL spectrum
 How is crosstalk then avoided? (see later)
Upstream and downstream masks defined in tables
 using breakpoints & interpolation rules

VDSL2 Limit PSD masks – Europe – 997 bandplan

VDSL2 Limit PSD masks – Europe – 998 bandplan
US0 type: A=POTS, B=ISDN, M=extended, N/A=no US0

VDSL2 PSD masks – Europe: example
PSD Limit Mask 998-M2-M (downstream)
DS VDSL2 (derived from ADSL2+ and VDSL1 Pex.P2.M2)

-20
Peak PSD Mask [dBm/Hz]
-30
-40
-50
-60
-70
-80
-90
-100
-110
100 1000 10000
Frequency [kHz]

Upstream PSD masks: plan 998 / 998ADE
P.M1 = solid line

P.M2 = dashed line
Optional upstream band is dotted line

Upstream Power Back-off

Upstream power back-off: why?
strong Rx signal; weak FEXT signal from long loop
FEXT--
FEXT++
weak Rx signal; strong FEXT signal from short loop
Typical example of crosstalk unbalance

 Close-by CPE disturbs signal from far-away CPE
Solution: weaken transmit signal of close-by user by upstream power
back-off (UPBO)
 this will not impact the upstream service too much
UPBO is mostly needed, but there are exceptions:
 UPBO not needed if all loops have an equal length
 or in some cases of FTTB (limited loop lengths)

Reference PSD UPBO method

Equalized FEXT UPBO method

xDSL upstream power backoff (UPBO)
1 CPE
CO
2 CPE
US
 With UPBO
Based on CO-CPE length
1 CPE
CO
2 CPE
US
Power backoff: specify maximum Rx PSD in US

 xTU-C informs xTU-R of max. Rx PSD
 xTU-R will then lower its output power, resulting in lower FEXT
In a DSL network the CPEs are typically NOT collocated.
 As such UPBO is always recommended to be used for VDSL2

Upstream Power Back-off in practice for VDSL
Different Rx PSD masks are pre-defined from which the operator can
choose.
 ETSI-A .. ETSI-F
 In practice VTU-O Rx PSD < Reference PSD Mask (defined in standards)
Operator can define the Rx PSD mask

 Done by defining an “A” & “B” parameter for the upstream bands in which
UPBO is desired.

PSDref   A  B freq. 
 In function of the frequency (in MHz) we have an increasing power backoff

UPBO: ETSI-x masks – max receive PSD
ETSI US PBO reference masks [dBm/Hz]
-80
F
C
-85
-90
D
E
-95 F
AB C
-100 D
E
-105
AB
-110
US1 -A –B√f
-115 US2
-120
-125
0 2 4 6 8 10 12
Frequency [Hz] Frequency (Hz)
x 10
6

UPBO only needed on short lines
PSDref   A  B freq.  
UPBO using ETSI-x or AB-parameters  based on max Rx PSD
For longer lines, the Rx signal is attenuated more
 no UPBO needed from reference (electrical) length onwards
For extremely short lines (e.g. up to 70m 0.4mm)  electrical length is
floored at 1.8 dB
TxPSDus(fx) [dBm/Hz]
max {TxPSDus(fx)}
UPBOPSD(fx) “ref PSD UPBO” “no UPBO”
0 dB eLength [dB]
1.8 dB eLength

UPBO – Equalized FEXT improves bit rate on very short lines

PSDref   A  B freq.  10 * log10 (kL0 _ ref / kL0)
For very short lines, the FEXT decreases more rapidly than the Rx PSD
suggests
 Recommended: use equalized FEXT instead of equal Rx PSD
 Loosen the UPBO constraints for short lines
  up to a certain (electrical) length
TxPSDus(fx) [dBm/Hz]
max {TxPSDus(fx)}
“Equal FEXT”
UPBOPSD(fx)
“ref PSD” “no UPBO”
0 dB kL0_ref eLength kL0 [dB]

1.8 dB = equal FEXT until this
eLength
US performance for different UPBO types
ETSI-D no noise
Sagem Fast3464: US performance ETSI-D
OptAB
30.000
OptAB EqFext
US1 ETSI-D US2 OptAB
6Mbps
25.000 8Mbps
20.000
Bitrate [kbps]
15.000
10.000
5.000
0
0 200 400 600 800 1000 1200 1400 1600
Length [m]
How to optimize the AB-parameters?
AB parameters should be tailored / optimized per operator

 depending on deployment conditions
AB settings might need to be relaxed when starting to roll-out vectoring.

Estimation of electrical length kL0 is key
kL0 is used as estimate for electrical length, to calculate transmit

PSD.
Initial VDSL2 standard (M0) had some flaws:
 Many vendor-specific implementations.
 not reliable for regulation purposes.
 In case of cable issues, as
e.g. bridge tap:
• electrical length not always
estimated accurately
• especially values for
different bands could differ.
(cf. figure)

How to estimate the electrical length kL0?
ISAM can estimate the electrical

length
 can be overwritten by operator for all
bands (not recommended)
Legacy mode = M0
 must be supported by the modems (CO– CPE)
 many different vendor-specific implementations! 
ITU-T defined optional alternative Electrical Length Estimation
methods (supported in ISAM R4.5.01+)
 Three alternative modes are defined:

 M1 = estimation only taking into account the DS estimation (CPE)
 M2 = estimation at CO side per US band
 M3 = estimation taking the minimum of CO and CPE estimation

How to estimate the electrical length kL0?
Electrical length is expressed as attenuation at 1 MHz

 Can be estimated based on downstream or upstream attenuation (at different
frequencies!)
 Values of attenuation can be totally different from kL0 for that band!
expressed as
attenuation
at 1 MHz!
In case of a bridged tap, it’s recommended to use mode 2

 the dip may only affect one of the upstream bands, not all
 mode 2 calculates kL0 based on upstream attenuation per band

How to enable alternate electrical length estimation?
Electrical length estimation mode:

 0= legacy (default)
 1= based on downstream attenuation (CPE)
 2= based on upstream attenuation per band (CO)
 3= min. of CPE and CO estimations for kL0
Electrical length threshold (min): percentile 0 – 15%
 You can only configure the value 10
 Meaning: remove the 10% lowest values
and take the minimum of what remains.
Alternative Electrical Length Estimation Mode (AELE-MODE).

configure>xdsl>spectrum-profile>1>vdsl2> upbo-aele-mode
UPBO Electrical Length Threshold Percentile (UPBOELMT).
configure>xdsl>spectrum-profile>1>vdsl2> upboaele-min-thrs
UPBO modes & policing
What if the CPE doesn’t apply the requested UPBO?

Five modes exist for UPBO:
 no UPBO
 UPBO without policing
 UPBO, passive policing

  notify when CPE doesn’t comply
 UPBO US0 only policing (Recommended)
  deny the use of other US bands - try to initialize with US0 only
 UPBO shutdown
  force the CPE in L3-mode and keep it there (prevent initialization)

Configure how to do UPBO in VDSL2 tab (spectrum profile)
For equalized FEXT: fill in

AB-parameters (by default,
the ones for ETSI-F are
displayed) and reference
electrical length (by default
0.00 = automatic =
determined by DSLAM

Rough values for Equalized FEXT for band plan 998
ALU recommends to use Equalized FEXT

AB parameters can be defined by the regulator or calculated for the
specific cable type.
If not, use the rough values below.
These settings correspond to following UPBO reference length:
 1000m for US1 (0.4mm)
 600m for US2 (0.4mm)
Band A-parameter B-parameter kL0_ref

US0 No UPBO (limited Xtalk on low frequencies)
US1 46.25 29.10 24.7
US2 54.58 16.15 14.9
Electrical length estimation: mode 2 (threshold 10%)

Configure UPBO in CLI
configure xdsl spectrum-profile <INDEX> name <NAME>

 vdsl
 pbo-mode pbo-mode-up (means UPBO is enabled without policing)
 vdsl2
 rx-psd-shape-up equal-fext
 pbo 2 (US band 1; US band 0 corresponds to pbo 1)
 param-a (unit: 0.01) (default values for ETSI-F)
 param-b (unit: 0.01) (default values for ETSI-F)
 equal-fext (unit: 0.1dB; default = 0 = automatic)
 pbo 3
 param-a
 param-b
 equal-fext

Hands-on
Reconfigure your port with UPBO = ETSI-A

 What is the upstream bit rate?
Modify the profile. Configure UPBO = ETSI-F
 Compare the upstream bit rate with the one for UPBO = ETSI-A.
 Launch a short LQD on the line and check if the SNR and the bit loading
graphs show slopes in the upstream bands.
Configure UPBO = Equal FEXT. The default values for A and B
correspond to the ones for ETSI-F. For the reference electrical length,
you don’t have to configure anything (default = automatic).
(Afterwards, you can enter e.g. 15dB)
 Compare the upstream bit rate with the one for UPBO = ETSI-F.
 Launch a short LQD. Is the SNR higher? Is the bit loading higher for US1
and US2? Check Tx PSD graph (only in R8.1+).

Compare US rates for UPBO on loops of different length
Please make sure to remove any Virtual Noise configuration!!
UPBO US bit rate for US bit rate for US bit rate for
loop length=… loop length=… loop length= …
ETSI-A (or ANSI-A)
ETSI-C
ETSI-F (or ANSI-F) Spectrum profile “VDSL2” tab
AB parameters
Equal FEXT – auto
Equal FEXT – 10dB
Equal FEXT – 15dB
Equal FEXT
Band A-parameter B-parameter kL0_ref

US0 No UPBO (limited Xtalk on low frequencies)
US1 46.25 29.10 24.7
03 · 01 · 39
US2 54.58 16.15 14.9
COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.
Hands-on: experiment with different kL0 estimations
Configure your port with Equal FEXT. Apply the spectrum profile with
different kL0 estimation modes. Check the electrical length and the
upstream bit rate.
 if possible on a loop with a bridged tap 
Attainable
Mode US bit rate kL0 – US1 kL0 – US2 kL0 - overall
0 (legacy /
default)
1 - DS - CPE
2 - US – CO
3 - min(CPE,
CO)
Reference spectrum profile for region B
spectrum profile contains advised values per above slides and with
UPBO enabled
configure xdsl spectrum-profile 100 name REF_UPBO version 1 dis-

ansi-t1413 dis-etsi-dts dis-g992-1-a dis-g992-1-b dis-g992-2-a
dis-g992-3-a dis-g992-3-b dis-etsi-ts g993-2-17a rf-band-list
not-used rau-noise-down 80 rau-noise-up 80 rau-time-down 60
rau-time-up 60 rad-noise-down 50 rad-noise-up 50 rad-time-down
5 rad-time-up 5
configure xdsl spectrum-profile 100 vdsl vdsl-band-plan annex-b-
998ade optional-band up adsl-band allow-adsl psd-shape-down
etsi-p-cab-m2 psd-shape-up etsi-p-m2 ghstones-pwr-mode auto
configure xdsl spectrum-profile 100 vdsl2 psd-shape-down
regionbm2-psd-down psd-shape-up regionbm2-psd-up rx-psd-shape-
up equal-fext
configure xdsl spectrum-profile 100 vdsl2
pbo 1 param-a 4000
pbo 2 equal-fext 235 param-a 4625 param-b 2768
pbo 3 equal-fext 105 param-a 5458 param-b 1174
configure xdsl spectrum-profile 100 active

Different UPBO configurations
no UPBO
ETSI-A
 RFI notches higher than ETSI-A!
ETSI-C

ETSI-F
AB-parameters
 AB values for ETSI-F (default)
Equal FEXT – auto

 AB values for ETSI-F
 kL0_ref defined by DSLAM

Equal FEXT – 10dB

Equal FEXT – 15dB

Equal FEXT – recommended

 US1: A = 46.25; B = 29.10
kL0_ref = 24.7
 US2: A = 54.58; B = 16.15
kL0_ref = 14.9

Different UPBO configurations - ANSI
ANSI-A
ANSI-F

Downstream Power Back-off

FEXT unbalance: transmit signal mismatch
The victim transmitter is collocated with disturber transmitter, but the

transmitted signal is different.
Example:
DS
This typically occurs when flavors are mixed: ADSL and VDSL, …

Remote cabinet deployment – DPBO PSD shaping
strong Tx signal; high FEXT signal for long
loop (unbalanced Xtalk)
ADSLx
xDSL downstream spectrum should not be used entirely or adapted

 Do not use ADSL spectrum (up to ... kHz)
 Avoid use of strong Tx signals on frequencies that interfere with nearby long
lines  PSD mask shaping (via breakpoints or calculated via E-side model)
 VDSL2 uses more frequencies than ADSL and could do this without losing too
much bit rate

VDSL2 Downstream PSD shaping (DPBO)
E-side D-side
FEXT++
N xDSL lines from the CO (ADSL > ADSL2+)

area in which PSD shaping is applied
How to get balanced FEXT for
overlapping spectrum?
 Adapt PSD shape of RT as if it was
coming from CO

The “E-SIDE” model
Remote Tx target PSD based on following parameters

 CO-RT attenuation, in four parameters (ElecL, A, B, C)
Attenuation CO  RT ( f )  electricalLength  A  B. f  C. f 
 Assumed CO (exchange) PSD mask “DPBOEPSD”
 Frequency span where PSD back-off is needed “Fmin”, “Fmax”
 Minimum usable signal “MUS”, used to interrupt PSD reduction
The RT target PSD is then derived targeting equal CO/RT signals
PEPSD  DPBOEPSD  Attenuation

(f) (f) CO  RT ( f )
PSD
DPBOEPSD
RT CPE
MUS CO (Ex) ? 2
Line to be protected
Fmin F1 Fmax F 1

DPBO maximum frequency used
DPBO is only needed for frequencies fmin till fmax
 When CO signal becomes unusable (f1) or above fmax, the remote can return
to nominal level
 Frequency where the CO signal becomes unusable is called f1
 @ f1: PSDRT  –80dBm/Hz
Shaped PSD follows CO attenuation up to min (f1, fmax)
 Taking into account PSD floor level for RT system (=-91.5dBm/Hz) and slope
rules
 For a greater CO-RT distance we get a smaller f1
PEPSD
16dB
PEPSD
23dB
Recommended:
MUS = -105 dBm/Hz
MUS
f1 f1 f
DPBO result

Example: CO: ADSL2+, RT: VDSL2 997 B7.1, ESEL 38 dB
Alcatel PSD(ds) Breakpoints Assistant
-35
-40
Original Original RT PSD(ds)
PSDCO
-45PSD
Original RT
MAX. NOM.
OriginalPSD
CO PSD(ds)
RT
-50
CO PSD at RT
-55
orig. RT RT PSD
RT PSDshape
shape
-60
(dBm/Hz)
-65 Breakpoints
-70 MUS
DPBO fMAX
-75 MUF_PSD
-80
MAXNOMPSD
-85
-90 RT PSDsplitFrequency
floor
-95
= -91,5dBm/Hz
MUF
MUSCO -100 bpfmin

-105 bpfmax
-110 PSDCO @ RT
DPBOFMAX
-115
0.0 0.5 1.0 1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5
Cross-section of attenuated PSDCO with

Frequency (MHz)MUS determines the max.
frequency (f1) at which DPBO needs to be applied.
 f1 = DPBO fMAX when the cross-section is bigger than DPBO fMAX
 PSD f1 -80dBm/Hz

Shaped DPBO – Examples for 2km – 4 km distance to CO
PSD mask
-30
-40
-50
PSD [dBm/Hz]
-60
SR @ 2 km (30dB)
SR @ 4 km (60dB)
reference PSD (NRA)
-70
-80
-90
-100
0 64 128 192 256 320 384 448 512
tone number (spacing: 4.3125 kHz)

Sample measurement with DPBO on short VDSL2 line
Sample ADSL2+
signal
attenuated over
800m

DPBO: multiple injection points
Concept = “one RT for multiple injection points in binders”
Electrical length = 23 dB ADSL2+

cluster of
CPEs
VDSL2
Hidden electrical
length = 7 dB
VDSL2 •‘hidden’ ESEL exaggerates PEPSD

•f1 computation is ok
 two electrical lengths needed:
 one for attenuation prediction
ADSL2+  the other for f1 computation
other CPE
cluster

DPBO: multiple injection points
PEPSD PSDRT shape

16dB
PEPSD
23dB
MUS
f123dB f116dB f
The electrical length @ injection point is used to determine f1

The [electrical length @ injection point – hidden electrical length] is
used to determine PSDRT shape
 By the time the RT signal is injected in the same bundle as the CO system it
has experienced an extra attenuation

DPBO profile applied – Transmit PSD (for DS1 band)
f1 f1 f1
ESEL = 23 dB ESEL = 23 dB ESEL = 16 dB
Offset = 0 dB Offset = 7 dB Offset = 0 dB
PEPSD PSDRT shape

16dB
PEPSD
23dB
MUS
03 · 01 · 58
VDSL2 Advanced · 3FL00452 VDSL2 f123dB f116dB
f
DPBO: different CO injections
Electrical length: 25dB
CPE cluster
Case 1
CPE cluster
Case 2
ESEL: 25dB
Which electrical length to choose for DPBO?

CPE cluster
1. Longer ESEL: highest attenuation, lowest MUF
2. Shorter ESEL: lowest attenuation, highest MUF
BEST CHOICE ?
 highest attenuation, highest MUF !

DPBO: different CO injections
MUFCTRL
10dB PSDRT shape
ESEL
25dB
MUS
f125dB f110dB=MUF f
This scenario is also valid for more than two different victims
 Identify weakest (highest ESEL) and strongest (lowest ESEL)
The highest ESEL is used to determine the PSDRT shape
The lowest ESEL is used to determine the MUF (f1)
 In the DPBO configuration: MUFCTRL

DPBO: different CO injections applied (Tx PSD and load)
ESEL = 25 dB ESEL = 25 dB
MUFCTRL = disabled (default: 300) MUFCTRL = 10dB

ADSL2+ loop attenuations

VDSL2 loop attenuations

Example VDSL2 PSD shaping
Parameters Value (Unit) Notes
CO System ADSL2+_mask Technology to deploy from central office
CO TX PSD G992.5 A.1.3 non-overlapped CO PSD table definition
RT System VDSL2_mask Technology to deploy from remote terminal
RT PSD type G993.2-B8.4 - 998-M2x-A RT PSD table definition
Cable model PE050 Cable model for CO-RT connection
CO-RT physical length 2000 m Irrelevant for CAL/ABC line model
Shaped RT transmit PSD and
RT PSD shape
interpolated breakpoints curve
Breakpoints
-40,0
-45,0
-50,0
-55,0
-60,0
-65,0
-70,0
(dBm/Hz)
-75,0
-80,0
-85,0
-90,0
-95,0
-100,0
-105,0
-110,0
-115,0
03 · 01 · 65 0,0 0,5 1,0 1,5 2,0 2,5 3,0 3,5 4,0 4,5 5,0 5,5 6,0 6,5 7,0 7,5 8,0 8,5
VDSL2 Advanced · 3FL00452 VDSL2 Frequency (MHz)
Example: CO=ADSL2+, CO-RT=2km, cable=PE040
VDSL2 PSD type = 998-M1-A
-30,0
-40,0
-50,0
DPBOSHAPEDds (dBm/Hz)
-60,0
-70,0
-80,0
-90,0
-100,0
0 500 1000 1500 2000 2500 3000
frequency (kHz)

Example: CO=ADSL2+, CO-RT=2km, cable=TP100
VDSL2 PSD type = 998-M1-A
-30,0
-40,0
-50,0
-60,0
-70,0
-80,0
-90,0
-100,0
0 500 1000 1500 2000 2500 3000
frequency (kHz)
Example: CO=ADSL2+, CO-RT=2km, cable=TP100
VDSL2 PSD type = 998-M2-B
-30,0
-40,0
-50,0
-60,0
-70,0
-80,0
-90,0
-100,0
0 500 1000 1500 2000 2500 3000
frequency (kHz)

DPBO configuration
DPBO can be configured in two profiles

 spectrum profile
• breakpoints for custom PSD
• do not use ADSL(2+) spectrum (up to a certain frequency)
 DPBO profile
• E-side model  A, B, C, ESEL, MUS, fmin, fmax, offset, MUFCTRL
• breakpoints for custom PSD
• can be configured on VDSL2 port or on entire LT

DPBO profile
Tx PSD for ADSL2+ victim (at CO)
To enter breakpoints in Custom PSD, Electrical length must be 0.

Configure DPBO profile in CLI
configure xdsl dpbo-profile <INDEX> name <NAME>

 micpsd-pt-down custom psd mask (-10 * PSD level)
 epsd-pt-down exchange psd shape (-10 * PSD level)
 [no] es-elect-length : ESEL (unit: 0.1dB) (default = 0)
 [no] es-cable-model-a : parameter a (2^-8 * A) (default = 0)
 [no] es-cable-model-b : parameter b (2^-8 * B) (default = 0)
 [no] es-cable-model-c : parameter c (2^-8 * C) (default = 0)
 [no] min-usable-signal: MUS level (unit: 0.1dB) (default = -1275)
 [no] min-frequency : min frequency in Hz (default = 0)
 [no] max-frequency : max frequency in Hz (default = 30000)
 [no] rs-elect-length : remote side electrical length (default = 0)
 [no] muf-control : maximal usable frequency (0.1dB)(3000)
 [no] offset : offset (0.1dB) (default = 0)

DPBO profile – recommended settings
System from CO that needs to be protected

 Exchange PSD : use ADSL2plus PSD Mask (default)
 Fmin = 138 kHz (for POTS overlay) or 276 (for ISDN overlay)
 Fmax = 2208 kHz
E-side cable model
 Parameters A, B, C for PE cable (e.g. 0.4mm, 0.5mm, 0.6mm, …)
 Reference frequency = 1 MHz
 a=0.1829, b=0.6159, c=0.2012 (CLI : a=47, b=158, c=52)
 Cable model independent for other diameter of same loop type
CO-RT trade-off parameter: MUS = -105.0 dBm/Hz
CO-RT (electrical) distance: ES electrical length: measure with
SELT/DELT or with external test device
 SELT: connect line at CO, open connection at the RT location
 DELT: connect line at CO, connect CPE at RT (just once), measure Hlog @ ref.
freq.

Hands-on
Reconfigure your port. Don’t allow the use of the ADSL spectrum up to
frequency 1500 kHz
 What is the downstream bit rate?
 Launch a short LQD in 5530NA and check the bit loading and SNR.
 Reconfigure the port again and allow the full ADSL spectrum
Configure a DBPO profile on your port for a distance between CO and
RT = 2km and cable type = TP100 (0.5mm).
 Electrical length = 20.5 dB (in CLI  205)
 A=0.36719 (in CLI  94)
 B=0.98438 (in CLI  252)
 C=0.41016 (in CLI  105)
 MUS = -100 dBm/Hz (in CLI  -1000)
 Launch a short LQD. Check bit loading and SNR graph.
Modify your DPBO profile with MUS = -90dBm/Hz. Compare.
Modify your DPBO profile with offset of 10dB (hidden electrical length).
Compare bit loading with previous case.

Hands-on
Configure a DPBO profile with the recommended settings for ABC:

 a=0.1829, b=0.6159, c=0.2012 (CLI : a=47, b=158, c=52)
 MUS = -105 dBm/Hz
Compare the following situations:
 ESEL = 20 dB
 ESEL = 40 dB
 ESEL = 60 dB

Hands-on (continued)
Configure a DPBO profile with MUFCTRL = 10 dB.

 ESEL = 20.5 dB (weakest victim)
 MUFCTRL = 10 dB (strongest victim)
Check the shape of the bit loading and SNR graph in 5530 NA-C
Configure the DPBO profile on the entire LT, not on the port.
Configure breakpoints in the DPBO profile (custom PSD). Make sure you
set the electrical length to 0!
 When ESEL = 0, the other parameters are ignored.
 138 kHz : -60 dBm/Hz (in CLI  600)
 600 kHz : -70 dBm/Hz
 1100 kHz : -80 dBm/Hz
 1500 kHz : -95 dBm/Hz
 1600 kHz : -95 dBm/Hz
 1900 kHz : -60 dBm/Hz

DPBO – Do not use ADSL spectrum
ADSL allowed
Do not use ADSL
Do not use ADSL2+

DPBO – Do not use ADSL spectrum
 Do not use ADSL
 Do not use ADSL2+
 Do not use ADSL spectrum

up to ADSL frequency =
1500 kHz

DPBO – ABC
ABC for TP100

ESEL = 20.5dB
MUS = -105 dBm/Hz
ABC for TP100

ESEL = 20.5dB
MUS = -90 dBm/Hz
ABC for TP100

ESEL = 20.5dB
MUS = -80 dBm/Hz

DPBO – ABC
ABC for TP100

ESEL = 20.5dB
MUS = -90 dBm/Hz
ABC for TP100

ESEL = 20.5dB
offset = 7dB
MUS = -90 dBm/Hz
ABC for TP100

ESEL = 20.5dB
no offset
MUS = -90 dBm/Hz
MUFCTRL = 10dB

DPBO – ABC
recommended ABC (PE)

ESEL = 20.5dB
MUS = -105 dBm/Hz
recommended ABC (PE)

ESEL = 40dB
MUS = -105 dBm/Hz
breakpoints (see lab exercises)

Virtual Noise

Line instability – cause and visible effects
DSL line during prime time (8pm-midnight):
 Service
interruptions: resyncs
Bandwidth (Mbps)
16.00
14.00 noise result in minutes of
12.00
10.00 downtime
 Service degradation:
8.00
6.00
4.00
2.00 lower bandwidth due
0.00
20:00 20:30 21:00 21:30 22:00 22:30 23:00 23:30 0:00
to higher noise
time
1st noise increase 2nd noise
(neighbour increase (strong
modem) radio signal)
Spontaneous DSL line

Excessive transmission errors
resynchronizations
video affected by stable DSL video affected by stable DSL

line resync packet loss
Line instability – field report
Operator line conditions – field data
Operator 1 Instability increases

ILEC. HSI(512k)/ADSL with service level /
bitrate
Operator 2  10-20% for HSI /
ILEC, HSI/ADSL ADSL
 20-35% for IPTV /
Operator 3 ADSL2+
CLEC, HSI/ADSL2 Stable lines Unstable lines
VDSL even more
Operator 4 vulnerable due to
CLEC, IPTV/ADSL2+ higher service level
/ bit rate
Operator 5
ILEC, IPTV/ADSL2+
0% 20% 40% 60% 80% 100%
Unstable lines mean less subscribers, lower ARPU, and higher support cost

Stabilizing an instable line with Virtual Noise
Original situation – high bandwidth but unstable

Bandwidth (Mbps)
 Two service
interruptions
16.00
14.00 noise
 Stable at 9.6Mbps –
12.00
10.00
8.00
6.00 lower service level
4.00
2.00
0.00
20:00 20:30 21:00 21:30 22:00 22:30 23:00 23:30 0:00
Traditional solution: High Noise Margin – stable but reduced bandwidth

16.00
14.00 noise  Increase TNM
12.00
10.00
8.00  Stable at 4.7Mbps
6.00
4.00 - strongly reduced
2.00
0.00
service level
20:00 20:30 21:00 21:30 22:00 22:30 23:00 23:30 0:00
 16.00
14.00
ALU solution: Virtual Noise – stable and high bandwidth
noise
•VN
12.00
10.00
•Normal TNM
8.00
6.00
•Stable at 11.6 Mbps
4.00
2.00
- Increased service
0.00
20:00 20:30 21:00 21:30 22:00 22:30 23:00 23:30 0:00
level
time
Resynchronization due to crosstalk
10 seconds SES
Resynchronization

NM drop due to crosstalk  errors
bit loading
 Major problem =
variation in
stationary noise
 Noise margin drops

below 6dB hence
there is a lot of FEC
& CV
CRC errors  The line is now

intermittent highly
disturbed.
Noise Margin
day1 day2 day3

NM drop due to crosstalk  errors
bit loading
day1 day2 day3
High crosstalk
Low crosstalk

Stationary Noise is varying along time of the day
bit loading
During night
BL Stable
No Errors (CV)
NM high & flat CRC errors
Noise Margin

Problem when non stationary crosstalk occurs …
Central office transmit power –40dBm/Hz
Loop atten.
Loop attenuation
500m
1000m
Signal & noise levels
1500m
2000m
SNR for bit loading
2500m
3km
Noise
Noisemargin
margin
Modem receiver noise floor
DSL carriers index

Loop atten.
Loop attenuation
500m
1000m
1500m
2000m
SNR for bit loading
2500m
3km
Crosstalk Noise margin
DSL carriers index

Loop atten.
Loop attenuation
500m
1000m
1500m
2000m
SNR for bit loading
2500m
High crosstalk
Medium Crosstalk 3km
Crosstalk
DSL carriers index

Strategy 1: protection via large target noise margin …
Loop atten.
Loop attenuation
500m
1000m
1500m
2000m
2500m
High crosstalk
3km
DSL carriers index

Strategy 2: protection via limitation of max bit rate …
Loop atten.
Loop attenuation
500m
1000m
1500m
SNR for bit loading

2000m
Noise margin 2500m

High crosstalk
3km
Medium Crosstalk
Crosstalk
DSL carriers index

Strategy 3: protection via virtual noise with low TNM
Loop atten.
Loop attenuation
500m
1000m
1500m
2000m
SNR for bit loading

2500m
High crosstalk
Artificial Noise
Medium Crosstalk 3km
DSL carriers index

Virtual Noise
Tool to control bit loading and SNR margin calculation

 SNRM_MODE = 1: “normal” mode:
reference noise level = external noise
 SNRM_MODE = 2:
reference noise level = max (external noise, virtual noise)
Virtual Noise ~ “noise-forecast”
 Communicated to modem by management system
 Configured manual by operator, or by “intelligent” management system
 to protect bit loading against future noise increases not present at init time
Goal: assure service stability
 avoid retrains and excessive errored periods
 example applications: triple-play, business services
Optional in VDSL2
 non existing in VDSL1 nor ADSL2

Virtual noise consequences
With virtual noise enabled:

 (assumed) external noise = max (actual external noise, virtual noise)
 So the reported noise margin could be less than the real NM
Reported NM  actual NM
 Reported max. attainable bit rate  actual max. attainable bit rate
Reported SNR = actual SNR

DSL Override (ISAM R3.6+)
used for per-line-management
Possibility to change profile parameters on specific port
General (Service profile related):
 Max bit rate (up and down)
 Minimum INP (up and down)
 Max interleaving delay (up and down)
Spectrum:
 TNM (up and down)
 Max PSD Level (up and down)
Custom PSD  Virtual Noise
Carrier masking

DSL Override configuration
Network
NE
Rack
Subrack
LT
XDSL port
Create
Override XDSL Profile Data

DSL Override configuration
Network
NE
Rack
Subrack
LT
XDSL port

Configure virtual noise in DSL overrule using CLI
configure xdsl overrule-data 1/1/1/1 noise-psd-mode-dn virtual noise-

psd-mode virtual
 noise-psd-pt-down <index> frequency < in Hz> psd <-2*(40+PSD)>
 e.g. noise-psd-pt-down 1 frequency 138 psd 120
 noise level -100 dBm/Hz  + 40 makes -60  *(-2) makes 120
 noise-psd-pt-up
 active

Hands-on
Configure Virtual Noise via DSL overrule on your VDSL2 line:

 Overrule PSD  Virtual noise downstream
 Enter the following breakpoints:
 138 (or 276) kHz  -100 dBm/Hz
 2000 kHz  -70 dBm/Hz
 3750 kHz  -100 dBm/Hz
 Launch a Short Line Quality Diagnosis on your line and check the bit loading
pattern. Do you see a dip in the first downstream band?
Ask your trainer if there’s an existing LQD with a recommendation to
configure VN. Check the shape of the VN graph in the LQD report.
Would you need to configure the VN breakpoints manually via AMS (or
CLI)?

Result
SNR doesn’t take into account the virtual noise.

VDSL2 Bonding

VDSL2 Bonding
VDSL2 Bonding…
2 to 8 DSL copper pairs combined
POTS splitter into a single virtual DSL line
… at board level
Any DSL copper pairs on the same LT
VDSL2 CPE
can be bonded (as opposed to
multi-pair bonding adjacent ports only)
VDSL2 LT
Double the bit rate at the same reach Extend reach, for same bit rate
Bonding offers resiliency. Bonding link can stay up if a link fails.

VDSL2 bonding: PTM bonding – EFM bonding
Offer higher bit rates/longer reach by pair bonding

 According to ITU-T G.998.2 (Ethernet based multi-pair bonding)
 Up to 8 pairs can be bonded (PTM bonding)
Bonded xDSL lines can differ in speed by a factor of up to 4

PTM bonding process at the transmitter
Ethernet frame is segmented in data fragments

 size: min = 64 B  max = 512 Bytes
 Bonding fragments have sequence IDs for later resequencing
Afterwards 64/65B encapsulation on each data fragment

Bonding overhead added to each data fragment
2 Bytes bonding overhead added to each data fragment

 Sequence identifier SID – 14 bits
 Start of packet SOP – 1 bit
 End of packet EOP – 1 bit
Then add EFM overhead; divide in segments of 64B + add 1B

 64/65B encapsulation adds CRC per data fragment

Resequencing
Ethernet frames split into bonding fragments (64 – 512 Bytes)

 sequence IDs for later resequencing at receiving end
Not all fragments arrive in the right order
 a buffer is needed to store fragments for later resequencing
 Buffer size should be at least 65000 bit times per PME
(ITU-T Bonding Standard G998.2 Amd1)
Fast
1
9
8
6
5 buffer
7
4 buffer
3 buffer
2 buffer
Slow
Fragmentation Resequencing

ITU-T G.998.2 Ethernet-based multi-pair bonding
G.998.2 Am. 1
 Differential delay for aggregation of ADSL2plus and VDSL2 links
G.998.2 Am. 2
 New functionality for discovery/aggregation and pair management at the
bonding layer
 Explicit PME-ID
 NW side uses PME-ID of each link to retrieve mgmt data
 Optional 5-bit PME-ID allows parallel initialization of the links (faster)
· If not supported by CPE, the links will be aggregated one-by-one
 BACP (Bonding Aggregation Control Protocol)
 replaces the G.994.1 discovery/aggregation process.
 In ISAM, G.994.1 is used for the discovery and aggregation instead of BACP

Two levels of xDSL bonding
Chipset bonding
 bonding traffic handled by xDSL chipset
 2 adjacent ports on same LT
 primary port must be odd-numbered
Board-level bonding
 bonding traffic handled by interworking function of LT
 non-contiguous ports on same LT can be bonded
 any port can be the primary port
 In ISAM:
 ATM bonding supported for 2 pairs
 PTM bonding supported for up to 8 pairs (depending on xDSL LT type)

Two ways to configure a bonding group
Assign primary link to bonding interface

 bonding group with only this link will be created
 secondary link and bonding group profile will be assigned later
Assign bonding group profile to bonding interface (no links assigned yet)
 bonding group will be created and primary link will automatically be assigned
 secondary link can be assigned afterwards
When the bonding group profile or the primary line is removed, the
bonding group is deleted.

Configure xDSL bonding group profiles
Network
NE
Infrastructure
Transmission
Bonding
Bonding group profile

Configure bonding group
Bonding groups:
Network
 are pre-defined
 select one and assign a bonding group profile
 unlock after the physical links have been added
NE
Rack
Subrack
LT
Bonding
Bonding group
bonding groups

Configure xDSL ports and assign to bonding group
Configure XDSL line profiles on the port

 settings (e.g. bit rates) in service profile may all be 0
 will be overridden by bonding group template
Network  however, if bit rates are 0 in bonding group template, the bit rates in
the XDSL service templates apply
 spectrum profile
NE Assign port to bonding group
 even if you haven’t created a bonding group profile
Rack
Subrack
LT
XDSL port
Create
Bonding link

Unlock bonding group
First create bonding group. Then unlock.

 Bonding group will start to initialize using config parameters of
• the bonding group profile
• the (optional) bonding RTX profile
• the configuration parameters of the individual links
What if a group is unlocked when only one link is assigned?

 For board-level bonding
 If no secondary link is assigned yet, the bonding group will try to initialize with only
the primary link
 For chipset-level bonding
 When no secondary link is assigned yet and the group is unlocked, the secondary link
will automatically be added.
 Bonding group will try to initialize both lines.

G.inp and bonding
Bonding group RTX profile can

be assigned (optional)
 Without bonding group RTX
profile, RTX mode is disabled
 regardless of the individual line
configuration

Bandwidth Split Algorithm – Why?
Bonded lines can have different characteristics

 different attainable bit rate per line
How to divide the aggregate group bit rate among the bonded lines?
Outcome of the algorithm:
 min/plan/max per line
 new delay parameters for the bonding group
2
1 INP 2
1. Loop length difference INP 4
CO
2. INP difference
3. Crosstalk different per
member line

Bonding - Initialization
Bonding bandwidth split

 Dividing the aggregate BW over the lines, taking into account the boundary
conditions
Line characterization Setting new parameters

Register
Probe training LOS Clearing Final training
Phase 1:
probe train: determine capacity Phase 2:
of the group members Assign proportional bit
group assembly timer (GAT): wait rate split – retrain lines
up to GAT for all lines to initialize

Bonding initialization: first training phase (probe training)
Probe training
Each line of the group is trained to determine its max. bit rate
capacity
 Info used to optimize link selection and bit rate split
Bonded lines may differ in speed by a factor of up to 4
 Some poor lines may not be allowed to synchronize
 they will not contribute to the bonding group (until next init)
 Bit rate on good lines may be limited to respect the 4:1 ratio
The option resulting in the best overall bonding bit rate is chosen.

Bandwidth Split - Boundary conditions: ¼ Rule
Bit rate ratio of the fastest line and the slowest line should not drop
below ¼ (IEEE802.3ah)
 in order to reduce delay difference between bonded lines.
When this condition is not fulfilled after first init, either:

 Drop a slow line of the bonding group (impact on both US/DS !)
 Cap the fast lines to a lower bit rate. (only one direction)
rate
60M 50M 60M 40M 40M 40M 60M 50M 60M

10M 10M
Capping Dropping
Bonding initialization: first training phase (ctd)
Check if CPE is bonding capable

 for board level bonding:
 bonding group can initialize when a non-bonding capable CPE is connected, if bit rate
is at least the configured min. bit rate
 for chipset bonding:
 initialization with non-bonding capable CPE is not supported
Check if both lines are connected to the same CPE

 if the ports of a bonding group are connected to different CPEs:
 init failure
 alarm raised

Bonding initialization: first training phase (ctd)
What if one of the links is out of service during training?

 for chipset bonding:
 no initialization
 for board-level bonding:
 bonding group can be brought in service, depending on assembly timer
 timer starts when the first line enters show-time
 timer determines max. additional time to wait for other lines to enter show-time
 lines that are not in show-time when timer expires, are excluded from the group (until next init)
 timer set to “infinite” by default
· i.e. bonding group will not enter show-time as long as one of the links are not in show-time
Probe training phase ends when all lines are in show-time or when
assembly timer expires.

Configure in-service timer / assembly timer
Network
NE
In-service timer (system setting)
Infrastructure
Assembly timer (in bonding group profile)
 by default 0
Transmission • means: bonding link will not come up if only one physical link is up
 in-service timer = 180
Bonding • means: bonding link will come up after 180 seconds if only one
physical link is up
Bonding system • the bonding link will then ignore the second link
parameters • lock/unlock to try again to have both links in the group

Bonding initialization: register clearing phase (PTM)
Register
Clearing
Clear the discovery and aggregation registers in the CPE before starting
the next training phase.
 Only for PTM bonding
Clearing requires G.994.1 handshake phase (no full init)

Bonding initialization: second (final) training phase
Final training
Configured bit rates on the bonding group are split between the links
 proportional to the bit rate capacity of the lines (as measured in probe
phase)
Lines enter show-time
Bonding group is brought into service
 if min group bit rate (or min ETR for the group) can be achieved

Delay equalization – 3 steps approach
1. At first initialization: impose no delay restrictions

40Mbit/s
INP 2 Delay 6
10Mbit/s
INP 2 Delay 8
2. Calculate the optimal shared delay on all lines in US and DS by

predicting the new bit rate after delay forcing
 DS Delay = 6ms = US Delay
3. Use a method to force this calculated delay on all the lines in US and
DS
40Mbit/s
INP 2 Delay 6
9Mbit/s
INP 2 Delay 6
Delay equalization - Calculation: increase/decrease delay
Delay increasing
 Reduces RS overhead (R/N decrease) but asks more memory
 Typical behavior is a strong decrease of NDR because the interleaving memory was
already filled before increasing delay
 Almost linear decrease of bit rate with factor old_delay/new_delay
Delay decreasing
 Increase RS overhead and less memory
 Typical behavior is a small decrease of NDR because of added RSOH

CO and CPE responsibilities - Upstream
Upstream  CO has full bonding control responsibility

 CO has the most information regarding US characteristics
 CO can make correct decision regarding bonding bandwidth split and delay
equalization
CO needs to force the new delay parameter in US.

 no delay constraints at first init
 force maximum delay as actual delay at second init
 This needs to be used with care: if there is no smart delay equalization the US
attainable bit rate can get extremely low due to max_delay=act_delay that is too high
and thus forcing the line into an unnecessary strong interleaving memory limited
situation.

CO and CPE responsibilities - Downstream
Downstream  depends on the CPE capabilities and bonding

implementation.
 Bonding standard does not require the CPE to be able to differentiate between
the two initialization stages
 There is no standardized mechanism to convey the maximum delay difference
between lines for PTM bonding
 If CPE does not care about delay equalization and takes no actions whatsoever
to lower interline delay variation, it should use a larger resequencing buffer to
prevent huge DS traffic loss.
Two options: done by CPE or by CO

Configure xDSL bonding via CLI
configure xdsl-bonding
 group-profile
 configure xdsl-bonding group-profile 2 name default local-profile version 1 active
 Also define here bit rates, interleaving delay & INP values
 group
configure xdsl-bonding group 1/1/6/11 group-profile 2
  configure xdsl-bonding group 1/1/6/11 link 1/1/6/40
  configure xdsl-bonding group 1/1/6/11 up
 group-assembly-time
 = Max waiting period for group to become operational (in seconds)

xDSL line failures
E.g. bonding group is up and one of the links goes down

 Bonding group can remain up if the min. rate for the group can be achieved
 When the other line recovers, it can join the group again.
 If the remaining lines cannot achieve the required min. bit rate for the group,
the group will eventually go down after some persistency period.
 In this case a full re-initialization of the group will be performed.
Lines that were down at the end of the probe phase (assembly timer),
will not be allowed to join the group if they recover.
 until next full re-init (starting with probe training phase)

Hands-on - Bonding
Configure bonding on two physical links on the same LT.

 Ask your trainer which ports (probably port 5 & 6)
 Create a dummy service profile (bit rates = 0)
 Create a spectrum profile
 Configure both physical ports
 Assign the ports to the same bonding group
 Configure the bonding group with a bonding group profile with high maxima
for US and DS
 Unlock the bonding group
 Wait for a few minutes until the modem synchronizes.
 If you use 5530 NA-C, create a bridge port on the bonding group.
 Launch an LSD and a short LQD.

Hands-on - Bonding
When the bonding group is up, unplug one of the pairs (or lock a physical
port)
 Is the bonding group still up?
Plug the cable back in (or unlock the physical port)
 Does the second line join the bonding group again?
Unplug the cable and lock + unlock the bonding group
 Does the bonding group come up?
Keep the cable unplugged. Change setting in bonding group profile (or in
system settings):
assembly timer / in-service timer = 180 s.
Lock & unlock bonding group.
 Does the bonding group come up?
Plug the cable back in.
 Does the second line join the bonding group again?

Hands-on - Bonding
Check if the load is spread evenly over both links

 Configure virtual noise on link 1
 Unlock the bonding group and check the bit rates on each link
 Check noise margins on both links
What happens if you have an operational link (bridge port) and add a
second link?
 Configure both links individually and add a bridge port
 Add these links to the bonding group
 What happens to the first link?
 Do you get an error message when adding a link that already has a bridge port?
(for the first one? for the second link?)

Hands-on - Bonding
Configure a service profile with meaningful bit rates on the physical ports
(e.g. US bit rates: min. 5000 / max. 60000; DS bit rates: min. 10000 /
max. 80000). Configure a bonding group profile with all bit rates equal to
0. Check bit rate of bonding group.
Is it possible to have a bit rate on a participating link that is below the

min. bit rate in the service profile?
Is it possible to have a bit rate on a participating link that is above the

max. bit rate in the service profile? (configure a higher min. bit rate +
configure max. used frequency in spectrum profile or add some virtual
noise)

References
ITU-T G.993.2 Very high speed digital subscriber line transceivers 2

(VDSL2)
ITU-T G.994.1: Handshake procedures for digital subscriber line

transceivers
ITU-T G.997.1: Physical layer management for digital subscriber line

transceivers
ITU-T G.998.4: Improved impulse noise protection for DSL transceivers

End of module
VDSL2 Advanced


3FL00452-S03M01-VDSL2 Advanced

Uploaded by

Copyright:

Available Formats

You might also like

3FL00452-S03M01-VDSL2 Advanced

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3FL00452-S03M01-VDSL2 Advanced

Uploaded by

Copyright:

Available Formats

Learning experience powered by

03 · 01 · 1 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Upon completion of this module, you should be able to:

explain the DSL basics

03 · 01 · 2 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

03 · 01 · 4 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

 PSD = power per unit bandwidth

 PSD: proportional to power delivered by a signal in a frequency band

 The more power, the higher the crosstalk.

03 · 01 · 5 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Crosstalk happens when a receiver listens to the same frequencies where

The transmitted DSL signal is attenuated by the twisted pair:

Freq Freq Freq Freq

03 · 01 · 7 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

The FEXT noise introduced in a victim modem (at REFV point) is

A received noise needs to be compared with the received signal to

03 · 01 · 8 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

The “FEXT” cross-talk impact strongly depends on the balance between

Freqconfiguration is called “self cross-talk”.

03 · 01 · 9 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

When the cross-talk is not balanced, some victim receivers will

03 · 01 · 10 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

US weak signal 998E

Strong signal will kill the

US0 DS1 US1 DS2 US2 DS3 998E

US0 DS1 US1 DS2 US2 DS3 998ADE

03 · 01 · 11 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

VDSL2 masks have been created by applying these rules:

03 · 01 · 14 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

03 · 01 · 15 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

US0 type: A=POTS, B=ISDN, M=extended, N/A=no US0

PSD Limit Mask 998-M2-M (downstream)

DS VDSL2 (derived from ADSL2+ and VDSL1 Pex.P2.M2)

03 · 01 · 17 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

P.M1 = solid line

03 · 01 · 18 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

03 · 01 · 19 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

weak Rx signal; strong FEXT signal from short loop

Typical example of crosstalk unbalance

03 · 01 · 20 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

03 · 01 · 21 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

03 · 01 · 22 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Power backoff: specify maximum Rx PSD in US

03 · 01 · 23 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Operator can define the Rx PSD mask

03 · 01 · 24 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

03 · 01 · 25 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

UPBOPSD(fx) “ref PSD UPBO” “no UPBO”

03 · 01 · 26 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

0 dB kL0_ref eLength kL0 [dB]

AB parameters should be tailored / optimized per operator

AB settings might need to be relaxed when starting to roll-out vectoring.

03 · 01 · 29 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

kL0 is used as estimate for electrical length, to calculate transmit

03 · 01 · 30 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

ISAM can estimate the electrical

 Three alternative modes are defined:

03 · 01 · 31 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.