AMR 2G Problem

[d0000h]

Familiar with E*******, not NSN but here it goes. Hopefully you can relate this to NSN and find the problem:

- AMR params on setup different from AMR on call (adaptive) params.
- Params based on BOTH quality and AVAILABLE CAPACITY (on the cell)
- pools of AMR capable vocoders for the BSC. No more vocoders, no more AMR.
- MS must be capable of AMR HR.
- change from FR to HR may only happen when available capacity is below threshold. Otherwise no NEED to change to HR.
- TS consolidation can be enabled. If there are no available FULL TS, then you CANNOT switch from HR to FR.

Q’s:
1) Do you see the codec change requests happening in the logs?
2) Why only 5.9 in FR?
3) What are your settings for FRH1-3 and FRS
4) What are your settings for HRH1-3 and HRS
5) How is it determined if you set up on HR or FR?
(After re-reading your post sound like you most of the issue is only changing codec no changing between HR/FR. So some of the info above maybe not so valid)

[josef]

Familiar with E*******, not NSN but here it goes. Hopefully you can relate this to NSN and find the problem:

- AMR params on setup different from AMR on call (adaptive) params.
- Params based on BOTH quality and AVAILABLE CAPACITY (on the cell)
- pools of AMR capable vocoders for the BSC. No more vocoders, no more AMR.
- MS must be capable of AMR HR.
- change from FR to HR may only happen when available capacity is below threshold. Otherwise no NEED to change to HR.
- TS consolidation can be enabled. If there are no available FULL TS, then you CANNOT switch from HR to FR.

Q’s:
1) Do you see the codec change requests happening in the logs?
2) Why only 5.9 in FR?
3) What are your settings for FRH1-3 and FRS
4) What are your settings for HRH1-3 and HRS
5) How is it determined if you set up on HR or FR?
(After re-reading your post sound like you most of the issue is only changing codec no changing between HR/FR. So some of the info above maybe not so valid)

1) Do you see the codec change requests happening in the logs?
when it is working yes, but otherwise No
2) Why only 5.9 in FR?
we implement 4.75, 5.9; 7.4 and 12.2 in FR but when it is not working, it stay on 5.9 (the initial codec)
3) What are your settings for FRH1-3 and FRS
FRH1: 6 dB
FRH2: 9 dB
FRH3: 13 dB
FRS: 1dB
4) What are your settings for HRH1-3 and HRS
HRH1: 11 dB
HRH2: 14 dB
HRH2: 0 AS WE HAVE ONLY 3 CODECS 4.75, 5.9 and 7.4
HRS: 1dB
5) How is it determined if you set up on HR or FR?
to go to hr or fr is determinated with 2 param
amrSegLoadDepTchRateLower = 40% and
amrSegLoadDepTchRateUpper = 60 %
So, if load is upper than 60% we go to HR and we wait until load will be lower than 40% to go back to FR
For codecs, we start with initial codec 5.9 (with any rate: HR or FR. We are not forcing the rate mode) then MS start to measure C/I and with comparison with FRHx or HRHx we can have upgrades or downgrades.

In our case, with the same radio conditions (even in stationary mode) we have upgrades only in 20% of calls (even less) !!!

Thank you bro

Josef

[josef]

Brothers,

is this problem can be related to MGW???

turning OFF/ON AMR feature is helping on something?

Thank's by advance for your replays

Josef

[d0000h]

3) What are your settings for FRH1-3 and FRS
FRH1: 6 dB
FRH2: 9 dB
FRH3: 13 dB
FRS: 1dB
4) What are your settings for HRH1-3 and HRS
HRH1: 11 dB
HRH2: 14 dB
HRH2: 0 AS WE HAVE ONLY 3 CODECS 4.75, 5.9 and 7.4
HRS: 1dB

Thank you bro, Josef

FRS/HRS are not dB values (just a number 0-3). Is "1" correct for FRS and HRS?

What is FRC and HRC set to and what do you feel your setting means? (it looks like a more complicated parameters). Can you confirm it is set the same setting for ALL of your sites/sectors?

FRT/FRH etc are in units/steps of 0.5dB. Just want to confirm that you are stating the correct dB level and not the parameter settings (i.e FRT1 setting of 12 = 6dB)

-Deuce-

[d0000h]

3) What are your settings for FRH1-3 and FRS
FRH1: 6 dB
FRH2: 9 dB
FRH3: 13 dB
FRS: 1dB
4) What are your settings for HRH1-3 and HRS
HRH1: 11 dB
HRH2: 14 dB
HRH2: 0 AS WE HAVE ONLY 3 CODECS 4.75, 5.9 and 7.4
HRS: 1dB

Thank you bro, Josef

Sorry, I am a bit unsure. The numbers above are Hysteresis (FRH), and the ones below you gave for Thresholds (FRT). They are (virtually) identical in setting, is this correct or are you FRH and FRT mixed up?

* Thresholds for full rate: 6, 9 and 12 dB
* Thresholds for half rate: 11 & 14 dB

-Deuce-

[josef]

Sorry, I am a bit unsure. The numbers above are Hysteresis (FRH), and the ones below you gave for Thresholds (FRT). They are (virtually) identical in setting, is this correct or are you FRH and FRT mixed up?

* Thresholds for full rate: 6, 9 and 12 dB
* Thresholds for half rate: 11 & 14 dB

-Deuce-

amrConfigurationFr: hysteresis1 FRH1 1
amrConfigurationFr: hysteresis2 FRH2 1
amrConfigurationFr: hysteresis3 FRH3 1
amrConfigurationFr: threshold1 FRT1 6
amrConfigurationFr: threshold2 FRT2 9
amrConfigurationFr: threshold3 FRT3 12
amrConfigurationHr: hysteresis1 HRH1 1
amrConfigurationHr: hysteresis2 HRH2 1
amrConfigurationHr: hysteresis3 HRH3 1
amrConfigurationHr: threshold1 HRT1 11
amrConfigurationHr: threshold2 HRT2 14
amrConfigurationHr: threshold3 HRT3 0

I made a mistake on writing this email, that's all

Any solutions brothers ???

[josef]

FRS/HRS are not dB values (just a number 0-3). Is "1" correct for FRS and HRS?

What is FRC and HRC set to and what do you feel your setting means? (it looks like a more complicated parameters). Can you confirm it is set the same setting for ALL of your sites/sectors?

FRT/FRH etc are in units/steps of 0.5dB. Just want to confirm that you are stating the correct dB level and not the parameter settings (i.e FRT1 setting of 12 = 6dB)

-Deuce-

In our network:

FRS = 0 and amrConfFrInitCodecMode = 0 (3GPP algorithm) => start with 5.9
HRS = 1 and amrConfHrInitCodecMode = 1 => start with 5.9

FRC = 149 (4.75, 5.9; 7.4 and 12.2)
HRC = 21 (4.75, 5.9 and 7.4)
RRC & HRC are exactly same for all celles

I know that FRT/FRH etc are in units/steps of 0.5dB. please see image attached
waiting for your answer

Br
Josef

[josef]

The problem was on MGW. One parameter can make your life bad

Time Alignment Disabled ==> Enabled

Thank you brothers

Jo.

[moslyi0891]

The problem was on MGW. One parameter can make your life bad

Time Alignment Disabled ==> Enabled

Thank you brothers

Jo.

oh ..yes ..thanx for sharing it