~ Introduction to Interleaving
Traditionally BT adsl <2Mb used what is known as "FAST" method for transmitting
data. DSL actually has two channels for data transmission; FAST and Interleaved.
When DSL data packets are transmitted they contain additional control bits
that enable your modem/router to check and/or correct a certain amount
of erroneous bits. This type of error checking is known as CRC or Cyclic Redundancy Check. It detects any corrupt data packets and if necessary will request the data which can cause symptoms of lag and slow internet browsing.
If during transit more than a certain amount of data
has been lost then the data cannot be correctly
decoded by your router.
Short bursts of noise on the line can cause these data packets
to become corrupt and the modem has to re-request data which in turn
can slow down the overall rate at which data is transmitted and may even cause the loss of sync.
MaxDSL, ADSL2+ and VDSL can make use of a technology called Interleaving
to help maintain tolerance against noise bursts. BT/Openreach tends to reserve the FAST channel for time critical applications such as VoIP and IPTV. Normal internet data for activities like browsing, emaill, file transfers is transmitted over the Interleaved channel. The amount of interleaving depends on your line conditions and is controlled by the DLM.
~ What is Interleaving?
Interleaving is a method of taking data packets, chopping them up into
smaller bits and then rearranging them so that once contiguous data
is now spaced further apart into
a non continuous stream.
DSL modems contain an interleaver which is responsible for interleaving the outgoing data & a de-interleaver which decodes and re-assembles data at the receiving end.
Interleaving is not just used in DSL broadband, many other technologies such as data & disk storage, CD's, satellite & digital communication etc also use interleaving for safe data transmission.
The diagram below is an example of how interleaved DSL traffic is
transmitted compared to a raw data stream:

~ The benefits of Interleaving.
If your line is particularly susceptible to bursts of noise
then interleaving should improve your DSL experience and add another layer of error protection. Error correction is always turned on at the same time as interleaving.
The spreading out of data decreases the likely hood of whole blocks of data being lost. When used in conjunction with error correction, it increases the chance of the modem being able to recover corrupt data without having to re-request information.
We can see in the diagram below what effect bursts of noise can have
on packets that are being transmitted.
Using the more traditional FAST method, the modem would not be able
to interpret the data and the information would have to be re-requested, or even worse, your
connection could drop and lose sync with the exchange.

Using Interleaving, the modem is able to re-assemble the data or if necessary
just re-request the part of the data that it is unable to recover.
By improving the efficiency of the error detection and correction correction
codes, BT state that interleaving has been "shown to significantly
improve error performance and stability of marginal lines".
~ Disadvantages of Interleaving
By now you may be asking if interleaving is so good, then why isn't it used by
default?
The answer to that is that it can also have a downside - chopping
up, rearranging and decoding of the data adds a small amount of additional
time it takes for data transmission. Forward Error Correction will also add to the delay, since the check bytes will take additional transmission time.
BT state that interleaving can increase latency by an additional 20-40ms. Whilst this
will not be noticeable to the vast majority of users, ardent gamers
are the ones most likely to complain about additional latency and therefore
prefer a slower synch speed than higher latency.
It should also be pointed out that whilst BTw state that applying interleaving shouldn't reduce your line speed, it does
reduce the maximum line rate achievable from 8128kbps to 7616kbps due to the additional overhead required for check bytes.
Since this article was first written there have been improvements made in both interleaving algorithms and error protection coding that have less overheads. Typical interleaving delay being 8ms. Compare that the average human reaction time is 250ms.
Note: although BT state 7616 is maximum sync speed
with interleaving, many instances of higher sync speeds have been reported
by users. This is dependent upon your router being able to support S=1/2 mode which effectively combines two RS code words into a larger logical code word of 510 bytes (ANSI T1.413).
~ Interleaving & Error Correction
Interleaving and Error Correction are usually switched on at
the same time and the 7616 profile has a 512kbps error correction overhead
with an increased latency of around 16 ms.
Whilst Interleaving on its own may not reduce your maximum sync speed, Forward Error Correction can and does affect your maximum sync rate.
With ADSL2/ADSL2+/VDSL error correction is more efficient and carries less overheads (see S=1/2 mode above). The resultant effect is that latency can be reduced from 16ms to 8ms.
Interleaving is set to "auto"
by default and interleaving is then controlled by the DLM process, turning it on if needed.
It is possible to arrange to have interleaving set to permanently
"on" or "off" via your ISP. Some ISPs may make a charge
for doing this. It is not possible to request no interleaving for VDSL in the UK.
Note: ADSL2+ and VDSL has the capability of switching on Interleaving and Error Correction as separate parameters. Data by default is usually sent using the interleaved channel with a depth of 1 which is the equivalent of FAST path. Because error correction can be set as a separate parameter it is possible to turn on Error Correction without increasing the depth of interleaving. In this circumstance it is possible that the EU may records FECs without the line seeing any of the usual delay of interleaving and subsequent increase in latency.
---
~ Interleave Depth
- Interleave Depth defines the number of bits (or bytes) in each block
of data, for example my diagram above shoes an example Interleaving depth of 4.
- ADSL supports a various levels of interleaving, the depth of which
can range from 0 (off) and from 1 to 64. VDSL2 profile 17a can support interleaving depths of up to 3072.
- Steps I've seen are 1, 4, 8, 16, 32, 64 for the downstream and 1, 2, 4, 8 for the upstream. VDSL values are higher.
- BTw makes little mention of Interleave Depth, and this would appear to be something that is controlled entirely by the DLM as there certainly are various depths of interleaving applied by the system.
- Some LLU providers have configurable Interleaving Depths and will change your profile upon request.
- Some routers will show you the depth of Interleaving applied to your line
eg: D (interleaver depth) 32 4
- Interleave Depth = 1 means that data is being transmitted over the interleaved path but data packets are not being interleaved. ie the equivalent of Fast Path.
~ Interleave Delay
- Interleave Delay defines the mapping (relative spacing) between
subsequent input bytes at the interleave input and their placement
in the bit stream at the interleave output.
- For example, in my diagram this would be the time between say
2 yellow boxes in the interleaved stream.
- Some routers will show you the interleave delay in ms. Typical values set by BT are 8ms & 16ms.
- The higher the delay, the greater chance of data recovery in the event of noise bursts.
~ Maximum Interleave Delay:
- Configurable attribute on some dslams/routers
as the maximum time for the Interleave Delay. - The higher the
Interleave Delay the greater the Interleaving Depth and more latency.
- The maxDelay parameter is used with the minINP parameter to set a required level of Impulse Noise Protection.
- Some LLU providers (such as Sky) will configure this figure upon request.
~ Impulse Noise Protection (INP)
INP (Impulse Noise Protection) was introduced with ADSL2 and is also in use with ADSL2+ and VDSL. Whilst ADSL1 provided for a Maximum Interleave Delay, previously there was no minimum figure to ensure that permanent protection against noise bursts was applied.
- The INP parameter specifies the minimum protection against noise to be applied at all times.
- INP = 3 means that noise lasting the duration of three DMT symbols can be recovered from regardless of how many errors there are in the symbol.
The total number of bits in a DMT symbol can vary depending upon how many bits are contained in each sub-carrier bin. For example tone 40 may have sufficient SNR to load 14 bits, whilst tone 400 may only contain 5 bits. The number of bits carried in each bin is called a symbol.
- DMT symbols are received in 0.25ms intervals & noise bursts are measured in units of 0.25ms.
Using our above example, for a tone with 14 bits and an INP value of 3, then the system must ensure that sufficient error protection is applied to ensure recovery of 42 bits of contiguous data for that particular tone. For the tone with 5 bits symbol and INP=3, this would need error protection of 15 bits.
Whilst 42 bits may not seem much, remember DMT utilises numerous tones in tandem and some noise bursts can affect more than just one tone.
- Because noise bursts may span more than one frame on noisy lines then higher levels of INP may be applied. Typical values applied by BT's DLM are: 3 (low interleave) and 4 (high interleave).
~ Latency
- It is important to note that Interleave Depth & Interleave
Delay are not necessarily the same thing as the additional amount of
latency you will see when interleaving is switched on.
- Nor is latency affected by connection speed -eg it does not decrease when
you go from 1Mb to 2Mb.
~ Relationship between Interleave Depth & Latency
|
|
64 QAM systems
|
256 QAM
|
conf
|
Interleave Depth |
Latency
|
Burst Protection
|
Latency
|
Burst Protection
|
I/J
|
|
|
|
|
|
|
8 |
0.22 ms |
5.9 ms |
0.15 ms |
4.1 ms |
8/16 |
12 |
0.43 ms |
18 ms |
0.32 ms |
14 ms |
12/17 |
16 |
0.48 ms |
12 ms |
0.33 ms |
8.2 ms |
16/8 |
32 |
0.98 ms |
24 ms |
0.68 ms |
16 ms |
32/4 |
64 |
2 ms |
47 ms |
1.4 ms |
33 ms |
64/2 |
128 |
4 ms |
95 ms |
2.8 ms |
66 ms |
128/1 |
|
©kitz Apr 2006
last update Mar 2015
Minor update 2023
|