PDA

View Full Version : NSN DSR feature (detected set reporting)



oswe
2014-03-13, 01:29 AM
guys working with NSN, do you have a clue why even after disabling (parameter to 0) this feature, we still have values in M1028 group of DSR counters ???
thanks

amadeo
2014-03-14, 11:52 PM
Hi Oswe,
Disabling report is not from parameter. You should do it by deactivating the feature using report management or using mml command.

Disabling thru parameter is disabling feature to use DSR data for ADJD.

cheers,

amadeo

oswe
2014-03-15, 12:07 AM
thanks man, we discovered that (unfortunately) by performing a small test...
thanks for your reply!
cheers.

eritelecom
2014-09-11, 06:02 PM
Hi optimizers,


We activated DSR feature (param = 1=> UE reports detected cells but RNC doesn't upgrade ADJS), however KPIs are degraded (specially CDR) !!
anyone can see the relation ? after disabling the feature all KPIs are come back to stbale status.
we are using RU40 (NSN)

Regards
Eritelecom

rumy
2014-09-12, 10:59 PM
DSR feature allows you to have HOs even with the no-neighbour cells (detected set) so you won't see any change in the ADJSs (unless I don't know the latests feature from RU40 onwards - like ANR in LTE). We are using this feature and it helps us in DCR and in optimizing the neighbour plan on the NW.

plumber
2014-10-07, 12:10 AM
You need to set "Detected Set Reporting Based SHO=DSR based SHO is enabled" in FMCS and additionally activate appropriate feature on RNC.
The new ADJS are added to ADJD table not ADJS.
However, according my experience this feature slightly deteriorates KPIs.
It is better to switch the feature on, set "Detected Set Reporting Based SHO=DSR is not allowed" and just utilize data in ADJD table: missing ADJS ngbrs can be added using NetAct Optimizer.