Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[kitz]

I seriously doubt they'd reset all lines

1).  There will be millions of lines that are likely to be on the correct profile and stable

Resetting all lines will instantly make one heck of a lot of lines unstable and flapping all over the place.  The ISP's support calls would go through the roof.  Most people dont have a clue about DLM and dont care.  Add in the fact that most FTTC users dont even know their sync speed let alone understand that they are getting additional latency through interleaving.  All they care about is line stability and not dropping in the middle of playing a game or whilst streaming a movie.

ISP's would suddenly be deluged with calls of 'My Internet keeps dropping out', which would also affect call outs for Openreach faults.

Those customers caught between changes and on a higher profile than they should be, will be comparatively few and far between.

2) DLM only calculates the profiles that should be used. It passes this info to the OSS and then its the Element Managers that set any relevant parameters on the DSLAM.   Element Managers are used to monitor and configure DSLAMs/MSANs not just for DLM functions, but also provide status and make general configuration changes to the DSLAM/MSANs.
Those for sure will not be turned off, so any profiles already on the DSLAM will stay. 

[Chrysalis]

yep, thats why I said they will keep as is, it doesnt require any work, plus unstable lines as you say would cause problems.

Newt may as well uncap his line now, as what he doing wont work with the current situation.

[adslmax]

Has anyone try this yet? Switch off modem and switch back on ten times in the space of 30 minutes to see if DLM has kick in?

[kitz]

Has anyone try this yet? Switch off modem and switch back on ten times in the space of 30 minutes to see if DLM has kick in?

I do NOT recommend that anyone tries it.  If you hit the 10 times parameter then that over-rides the normal DLM process and causes the Device Manager to go into over-drive - Monitoring then is no longer performed by the data collectors and the usual algorithms dont apply.   We do not know which part of the system has been switched off. 

[adslmax]

Then the whole of DLM switched off is more confused now.

I reckon BT will start to bring in new DLM v2 in 2015

[kitz]

I reckon BT will start to bring in new DLM v2 in 2015

or it may be simpler to drop back to the previous DLM using just SNR & Interleaving?   Until we know which part of the patent BT have infringed then we cant really speculate too much.

[les-70]

I seriously doubt they'd reset all lines

   If they did I am sure it would be to a safe well interleaved setting. 

[tbailey2]

[Chrysalis]

I find it ironic they claim their technology improves performance when DLM only slows down lines.

[Dray]

It reduces packet loss and retransmits so less bandwidth is wasted resending packets.

[guest]

The ASSIA patents in question aren't (AIUI - and I may well be mistaken) in general to do with the nitty-gritty of DLM, its more to do with the management of those lines and how that is handled.

None of this has any impact whatsoever on on the current Openreach "fibre" services (VDSL2). AIUI this relates to BT Wholesale/Retail ADSL services only.

For those having a pop at ASSIA - they pioneered DSL profiling/management solutions a LONG time before BT came to the party. Been a very very long time since BT pioneered anything & the infringements saved BT multiple millions in customer support so I have more sympathy for ASSIA than BT.

My personal opinion is that BT will come back to the table when they are forced to rollout vectoring - and again this is about how you MANAGE vectoring/profiling/etc, not how you implement it.

Not a great fan of s/w patents but BT are taking the proverbial on this one - and they know it.

Edit - and in a different thread on these boards I go on about how good Sky DLM is, that's not down to Sky having great hardware - its mainly down to g.INP firmware support and the ASSIA management suite.

[kitz]

I'd imagine that might be buried in HERE somewhere:

I think you may be right in that it is 'something' to do with the vdsl system.

For those having a pop at ASSIA

I dont see that anyone has     (so far)

My personal opinion is that BT will come back to the table when they are forced to rollout vectoring - and again this is about how you MANAGE vectoring/profiling/etc, not how you implement it

The system profiles will have to change anyhow to account for vectoring.  Bet BT are busy beavers atm.

[Ixel]

I'd imagine that might be buried in HERE somewhere:

I think you may be right in that it is 'something' to do with the vdsl system.

For those having a pop at ASSIA

I dont see that anyone has     (so far)

My personal opinion is that BT will come back to the table when they are forced to rollout vectoring - and again this is about how you MANAGE vectoring/profiling/etc, not how you implement it

The system profiles will have to change anyhow to account for vectoring.  Bet BT are busy beavers atm.

I wonder if this will motivate them into rolling out things like vectoring, who knows maybe it will help .

[NewtronStar]

I am just glad this Rambo shutdown thread was made or would have missed Kitz's DLM system tutorial very well worded and can undertand most of it 10 out of 10 and thanks 

[kitz]