Multi Carrier - Problems [Archive]

jan74

2011-07-29, 05:24 PM

Hi,

I've just deployed 3rd carrier on NSN Network. Strategy is

f1 - voice + R99
f2 - hsdpa + hsupa
f3 - hsdpa (cell barred).

After deployment, if UE starts HSDPA Session, it goes to f2. When session closed, never return back to f1.

on F1 : RAB Active Release PS SNRC is increased.

on F2: Inter Frequency Handover Drop NRT increased.

Any idea or suggestion?

This is similar to what we are doing although we do not have F3 yet. I assume you are not using F3 yet either? Here, all users idle on F1. We use Directed RRC for HSDPA to send the HS user to F2 upon RRC Connection Request. Are you using this feature? If so, you need to make sure that you have UE Layering feature enabled. They go hand in hand and if you dont enable the Layering feature, it can go pear-shaped..... Maybe you know all this but your email doesn't give all the details.

UE layering will bring any users who get stuck on F1 in FACH, up to F2. Have you got HS Capability Based HO enabled also on F1? That will bring any other HS Capable devices up from DCH on F1 to HS on F2. Unfortunately, these features are not very effective and you need to enable all three really to make sure your HS traffic goes to F2. Even then you will have anomalies.

Have you checked the counters for these features? Also, what about the counters M1022C3 up to M1022C82? These will give you a breakdown of what is being requested and where and what they are actually getting. You could also consider changing your SintersearchConn parameter on F2 to allow UEs to stay for longer on F2.

What are the PS RAB Act releases for on F1? Are they "Radio" or is there another cause given? Have you seen an increase in PS R99 attempts on F1? If so, maybe the percentage of failures has risen but the actual number of attempts may have dropped as they move to F2?

Also, the IFHO NRT Fails on F2 are worrying. You mention F3 as being "Barred". Are UE's attempting handovers to F3 and failing? Have you also got the above features enabled on F2? If so, they could be attempting to handover to F3 and failing as it is barred.

You mentioned that the UEs "never go back to F1". Is that by design? Have you fixed the HOPI parameters to allow them idle on F2 after call completion? How then are you getting your CS back to F1?

There is a lot to consider. Send on more details of the issues if you need more info.....