What is Vectoring Technology
What is vectoring technology
Vectoring technology has emerged as a means of delivering high bandwidth over existing copper infrastructure by extracting more value from it, without investing in an extensive fiber roll-out.
Let us take a look at the some basic principles of how the copper infrastructure is organized.
Phone lines that carry VDSL2 signals are part of cables that contain from 10 to a few hundred lines positioned very closely together. This close proximity results in cross-talk (FEXT, undesired effect of a signal transmitted on one circuit to another one) and the higher the number of lines in a bundle, the more cross-talk is generated. Cross-talk is the one of the biggest impediments to deliver good VDSL2 performance. With no interference, every VDSL2 line can operate as if it were the only line in the cable, and, as consequence, deliver higher bit rates. So basically, vectoring is not a method for raising the theoretical maximum speeds, but permits to decrease the gap between the theoretical upper limit of performance and the speeds that can be delivered in variable field conditions.
Opposite to Dynamic Line Management (DLM), for which there is no guarantee that the improved speed once awarded by the DLM process on a specific VDSL2 line will always remain, the vectored lines will keep their new higher rates based on a recurrent process of measurement, processing and correction.
Vectoring technology can be compared to the noise-cancelling technology used in headphones: it works by 'listening' to unwanted noise and producing a sound that is exactly like it but with an inverted phase—this way two sounds can cancel each other out.
Vectoring roll-out in Belgium is part of the worldwide vectoring deployment. Several suppliers are working on development of their own vectoring technologies: such as Alcatel-Lucent for Belgium, Austria and Turkey or Huawei, which is the supplier to Telecom Italia, Eircom, Swisscom and service providers in other countries. For most of them, vectoring will be commercially rolled-out by the following years.
In the Belgacom (now Proximus) network, vectoring technology will be implemented at street cabinet (ROP) level where the cross-talks of the lines of the same bundle can be properly measured and neutralized by generating appropriate anti-phase signals. In order to cancel the cross-talk between all VDSL2 lines in the bundle, there has to be a cross-talk analyzing mechanism to obtain the cross-talk coefficients and to permanently—and in real time—calculate and update the anti-signals across hundreds of VDSL2 lines over the full frequency spectrum occupied by the VDSL2 signals. Correlation of the received error values and generation of anti-signals are performed by DSLAM.
Surely all this calculations needed for vectoring requires enormous computing power. Since the current elements of Belgacom (Proximus) infrastructure do not permit to fulfill requirements mentioned above, there are two main things to be implemented in order to bypass it: use of the new VDSL2 line cards in the ROPs and an upgrade of all installed CPE (Customer Premises Equipment) to vector-friendliness or its replacement by vector-compliant hardware.
All VDSL2 cards will be replaced by Belgacom (Proximus) starting from February 2014, street cabinet per street cabinet. As for second requirement, the efficient estimation of the cross-talk between VDSL2 lines, the additional functionality at the CPE side is defined by the International Telecommunication Union (ITU vectoring standard, G.993.5 (G.vector).
On the hardware level, VDSL2 line can only be vectored if two following requirements are fulfilled: modem installed on it should be vector-compliant and, at the same time, each modem installed on every other line of the same bundle is vector-compliant or at least vector-friendly. Otherwise, a modem, which is not at least vector-friendly, is installed on any other VDSL2 line, will interfere with the calculation of the cross-talk between the lines. Thus, the cross-talk from some line will remain uncancelled, resulting in an unpredictable negative impact on all other lines of the bundle.
In order to prevent it, all modems that are not at least vector-friendly will synchronize on a fallback profile (7000/512 Kb/s) that will not create more cross-talk than the one coming from ADSL2+ lines and will not disturb the continuous cross-talk estimation. On the contrary, a vector-friendly VDSL2 CPE does not disturb any other lines in the cable, but will not allow to benefit from the advantage of vectoring, being a higher speed rates.
Frequently asked questions
- Where does the limitation of VDSL2 CPE use on the VDSL2 network originate from?
- Where does the permission for the alternative operators to use their own VDSL2 CPE originate from?
- Why has nothing changed during those 2 years?
- Why has it been possible to use another VDSL modem on the Belgacom network than the Belgacom-one(s) all those years?
- Why is there all of a sudden a CPE-problem with the introduction of vectoring?
- Why is my VDSL2 CPE not allowed on the Belgacom network while it’s vectoring-friendly or -compliant according to the manufacturer?
- What’s the difference between a vectoring-friendly and a vectoring-compliant VDSL2 CPE?
- Is the FRITZ!Box 7360 vectoring-friendly or vectoring-compliant?
- What about FRITZ!Box 7390 / 7490? They are made by the same manufacturer.
- What about the Sagem / B-Box 2?
- What about the O-Box 3 / B-Box 3?
- Why didn’t edpnet oblige the purchase of the Sagem when ordering a VDSL2 line?
- What to do in case of another VDSL2 CPE?
- Why is this not a breach of contract by edpnet?
- When will vectoring be activated?
- When will vectoring be activated in a specific street?
- Who will be affected by vectoring?
- Why should I have vector-friendly modem if I live more than 400 meters from ROP?
- Where can I check if vectoring will have effect on a specific line?
- What if I have another question?
Where does the limitation of VDSL2 CPE use on the VDSL2 network originate from?
Back in 2009 it was the general opinion of network operators (Belgacom(now Proximus) in Belgium, KPN in the Netherlands …) that, since the VDSL2 technology was not yet mature enough, the chipset of both the modem and the DSLAM should be the same in order to prevent operational problems, performance reductions and line instabilities. Hence the idea of only allowing one VDSL2 CPE on the network. Since interoperability was not guaranteed, an agreement made in the Decision from September 30th 2009 on WBA VDSL2 the Council of the BIPT (Belgium Institute for Posts and Telecommunications) with the limitation to allow only one type of VDSL2 CPE on the Proximus(Belgacom) VDSL network.
What were the consequences of this Decision?
Any alternative operator who wanted to roll out a VDSL2 offer had to use a VDSL2 CPE of a specific type, being the SAGEM F@st 3464 (hereinafter referred to as: Sagem).
Where does the permission for the alternative operators to use their own VDSL2 CPE originate from?
Under influence of the alternative operators, who strongly rejected the idea of being obliged to use the specific VDSL2 CPE that Proximus(Belgacom) told them to use, in the Decision from September 30th 2009 on WBA VDSL2 the Council of the BIPT obliged Proximus(Belgacom) to come up with a proposal that would allow alternative operators to use their own VDSL2 CPE on the Proximus(Belgacom) VDSL2 network. After having gathered some information, in 2011 the BIPT concluded that the VDSL2 CPE restriction was limiting competition in the market and that a review of the CPE-obligation was at order.
- What were the consequences of this twist?
A VDSL2 CPE test plan was to be developed that would primarily aim to protect the Proximus(Belgacom) network and at the same time allow alternative operators to use their VDSL2 CPE in normal competitive conditions. The original plan was written in the context of an alternative operator developing his own VDSL2 CPE. Belgacom would provide the alternative operator with a series of tests that his VDSL2 CPE had to pass successfully. Then the alternative operator would be allowed to connect its own VDSL2 CPE’s to the Proximus(Belgacom) VDSL2 network.
On 20/12/2011 the BIPT approved the test plan, which resulted in 2 types of VDSL2 CPE’s being possible from then onwards: the Proximus(Belgacom) CPE (Sagem) and an OLO CPE.
Why has nothing changed during those 2 years?
Upon approval by the BIPT, edpnet immediately started with the preparations of having its own VDSL2 CPE certified for use on the Proximus(Belgacom) VDSL2 network. It did not take long to find out that both financially and technically the approved certification procedure was nearly impossible to pass. It took edpnet many months and many convincing to get the BIPT and Proximus(Belgacom) to soften the requirements a little.
In August 2012, edpnet was the first alternative operator to officially inform both Proximus(Belgacom) and the BIPT of its intention to have the AVM FRITZ!Box 7360 certified as VDSL2 CPE, the first official step into the certification process. During the months that followed it became quite clear that Proximus(Belgacom) had been allowed to make the requirements way more extensive than the requirements in other countries. It took edpnet almost another year before an agreement could be made with Proximus(Belgacom) and the BIPT on a test plan that was do-able and acceptable for all parties.
In January 2014, edpnet submitted the necessary test samples to Proximus(Belgacom) as a final step in the certification process. But there has been some change though!
In June 2014 the FRITZ!Box 7360 and the newer FRITZ!Box 7490 both got certified!
Why has it been possible to use another VDSL modem on the Belgacom network than the Belgacom-one(s) all those years?
In theory Proximus(Belgacom) was entitled to shut down any VDSL line with a non-Belgacom VDSL CPE attached to it, but as long as the VDSL CPE did not disturb the network / any other lines, they “allowed” it. So basically, Proximus(Belgacom) did what other xDSL network operators in other countries do: they only took action when a CPE was disturbing the network / other lines.
Why is there all of a sudden a CPE-problem with the introduction of vectoring?
There are mainly two reasons for that.
On one hand, it is the result of the vectoring technology itself. Different copper lines are bundled in a cable that arrives in a street cabinet. These lines disturb each other because they create cross-talk, noise, which results in a loss of quality and a loss of performance (read: speed). Vectoring technology eliminates this cross-talk, noise, resulting in better performance (read: speed). All VDSL2 modems connected to the copper lines in the same cable must support ITU G993.5 (a.k.a. G.Vector), otherwise the performance of all modems falls back to "normal" VDSL2. Nobody wants that to happen. Following the above, it’s crucial to prevent one VDSL2 CPE causing problems for 383 others connected to the same cable.
This leads to reason number 2. Each national VDSL network operator has introduced some kind of a whitelist procedure (read: a certification procedure) based on chipset + firmware combinations (CFC). If a specific CFC has been tested and approved for vectoring and interoperability with DSLAM upgrades, it appears on the whitelist. If it is on the whitelist, it will be recognized as such by the DSLAM and will pass the security test. If not, the line at which the non-compliant CPE is attached will automatically be put on a VDSL2 fallback profile (equal to an ADSL2+ type of speed).
Why is my VDSL2 CPE not allowed on the Belgacom network while it’s vectoring-friendly or -compliant according to the manufacturer?
Proximus(Belgacom) was allowed by the BIPT to take it one step further and work with a CPE-model + chipset + firmware combination. The certification / whitelisting procedure from Proximus(Belgacom) (as approved by the BIPT) is far more extensive and strict than what national xDSL network operators in other countries use. In Belgium, only an alternative operator can initiate a certification procedure, while in other countries also CPE vendors can do this. This results in a very short whitelist in Belgium, containing only the Proximus(Belgacom) CPE’s and—since June 2014—the FRITZ!Box 7360 and 7490.
What’s the difference between a vectoring-friendly and a vectoring-compliant VDSL2 CPE?
A vectoring-compliant VDSL2 CPE will allow the VDSL2 end-user to benefit from higher downstream speeds resulting from the application of vectoring.
A vectoring-friendly VDSL2 CPE does not disturb any other lines in the cable, nor the network, but won’t allow to benefit from the advantage of vectoring, being a higher downstream speed.
The third kind, a so-called legacy CPE is a CPE that’s neither vectoring-compliant nor vectoring-friendly and will result in the line being limited to a VDSL2 fallback profile (equal to an ADSL2+ type of speed).
Is the FRITZ!Box 7360 vectoring-friendly or vectoring-compliant?
The FRITZ!Box 7360 and 7490 are vectoring-compliant, provided that the modem is equipped with the appropriate version of the modem firmware (06.06 (v1 and v2)for 7360 and 06.06 for 7490).
What about FRITZ!Box 7390 / 7490? They are made by the same manufacturer.
Unlike FRITZ!Box 7360, most other AVM modems are not vector-friendly or vector-compliant. The reason is simple enough: the restrictions that Proximus(Belgacom) applied to the certification procedure, making it almost impossible to whitelist more non-Belgacom CPE. For every extra CPE + chipset + firmware combination—even if part of them are the same as of FRITZ!Box 7360—the whole certification process has to be passed and price has to be paid, but despite that obstacle edpnet has worked hard and got FRITZ!Box 7490 certified, as well.
What about the Sagem / B-Box 2?
These are not—and will not be—vector-compliant. Nevertheless, they are and will be vector-friendly, provided that they are equipped with the latest vector-friendly version of the modem firmware.
- How to upgrade my Sagem / B-box 2 to vector-friendliness?
There is normally nothing that needs to be done: Proximus(Belgacom) is remotely upgrading all the VDSL2 modems to the appropriate firmware version. Those who do not hear from us are in this situation. Sit back, relax and enjoy the ride. However, if something is wrong—sometimes it happens—and the modem is not upgraded remotely, you will be contacted (or most probably, have already been contacted) by our friendly helpdesk to know what exactly has to be done to get the appropriate firmware version on the modem.
You can also follow this step-by-step guide: How to make my Sagem Vectoring-Friendly
What about the O-Box 3 / B-Box 3?
These are vectoring-compliant and allow to benefit from vectoring technology.
Why didn’t edpnet oblige to the purchase of the Sagem when ordering a VDSL2 line?
That would be / have been a violation of article 44 of the law of April 6 2010, which forbids a company to use default options which the consumer is required to reject in order to avoid any payment for one or more additional products.
What to do in case of another VDSL2 CPE?
In case your CPE is not one of the above, you have two options: you either obtain one of the above mentioned VDSL2 CPE’s or you do not and will be put on the fallback profile as soon as vectoring is being activated on the ROP you are connected to. Note that both FRITZ!Box 7360 and 7490 can be put in bridge mode, which means that you can install the modem between your current CPE and the xDSL network. This way you can keep your current modem configuration / settings, and avoid the risk of automatically being put on the fallback profile once vectoring is being activated. Sagem can be also put in bridge mode, but you should keep in mind that since it is not vector-compliant hardware, it will permit to keep actual VDSL2 profile, but not to obtain any higher speeds.
Why is this not a breach of contract by edpnet?
We understand that this will be a lot of customer’s initial reaction. However, please note that edpnet is still offering internet access via the VDSL2 technology, like it did before. It is the VDSL2 technology itself that has evolved, resulting in the use of certain “outdated” hardware giving a lower VDSL2 speed profile. Vectoring activation is not an opt-in / opt-out thing: edpnet cannot choose to switch it off because it is not being introduced by Belgacom the way edpnet would have liked to see it introduced.
When will vectoring be activated?
Proximus(Belgacom) will gradually activate vectoring on its network, street cabinet per street cabinet. This means that it will take most part of 2014 to fully roll out vectoring in the whole Belgacom network.
When will vectoring be activated in a specific street?
Edpnet does not receive information from Proximus(Belgacom) at this level of detail: we do not know to which specific street cabinet a specific end-user line is attached.
Who will be affected by vectoring?
Basically it will have effect on all VDSL2 lines, no matter the distance from the street cabinet. This means that every VDSL customer needs at least a Belgacom whitelisted vectoring-friendly CPE. When located within 400 meters of the street cabinet, a Belgacom whitelisted vectoring-compliant VDSL2 CPE will allow higher speeds.
Why should I have vector-friendly modem if I live more than 400 meters from ROP?
This is the result of the vectoring technology itself: all VDSL2 lines in the cable need to participate in the cross-talk estimation or—at least—to not disturb it, no matter how far from street cabinet the line is. Unless this requirement is not fulfilled, the line will be put on a VDSL fallback profile.
Where can I check if vectoring will have effect on a specific line?
The edpnet availability tool will allow you to verify the feasibility of the vectoring profile on a specific address after vectoring will be rolled out. You can check whether the line will be eligible for vectoring using the same tool: just enter your address or your fixed telephone number: in case the estimated speed is around 50 Mbps, there should be no obstacle to benefit from vectoring.
What if I have another question?
We will gladly answer any questions you might have, just drop us a line at info[at]edpnet[dot]net