Vous êtes sur la page 1sur 6

CHEN Gang

Oman NIS
2014-08-28

Author
Department
Update Time
Approver

Case Title

Work ID
Product Line
Product version

00190103
WCDMA RNP&RNO
V900R015ENGC00SPC560

UL CE Utilization Issue after SRB over HSUPA

Phenomenon
Description:

1. After the SRB over HSUPA feature deployment, the Uplink CE congestion
happened on RNC side and the Service CSSR is impacted.

2. After the feature deployment the RNC and NodeB CE utilization changed , but
with the different trend. The RNC side CE used increase obvious while the NodeB
side decreased slightly.

2007-05-24

1 , 6

The customer asks about the reason.


NONE

Alarm
Information

Cause
Analysis

1. After the Dynamic CE enabled, the CE utilization mechanism is different between


RNC and NodeB. NodeB will recycle the CE dynamically while the admission CE
number will never change even NodeB recycle the CE. So there is no relationship
(the same trend) between the RNC counter VS.LC.ULCreditUsed.Mean and the
NodeB counter VS.LC.ULMean.LicenseGroup.Shared.
2. The RNC side VS.LC.ULCreditUsed.Mean increase and the reason is there is
mechanism difference for SRB over DCH and SRB over HSUPA. From the feature
document, additional one CE is consumed for SRB over DCH compared with SRB
over HSUPA.

2007-05-24

2 , 6

Detailed description as following,


1. The signaling part and the user part will used (share) the same EDCH for SRB
over HSUPA user: If there exist SRB in the TTI, TBS+SRB is used together to
count the CE consumption; if no SRB exist, only the TBS is used.
2. The Signaling part will consume one separate CE without considering SRB for
SRB over DCH user. The actual CE utilization number is CE used for TBS plus 1.
Most of the time we will use TBS to count the CE utilization number directly due to
the low TTI ratio for SRB over HSUPA containing SRB data.
The current configuration as following
function
status
HSUPA 2MS
OFF
Dynamic CE
ON
Uplink L2 enhancement
OFF
From the feature document description,

RNC do the user admission for CE resource according to the following criterion:
one RLC PDU bit rate of 10ms TTI = (336-16)*100=32kbps
(HSUPA RLC PDU size=336)
the CE utilization for service with different bit rate as following :

2007-05-24

3 , 6

Some key points need be mentioned for this table,


1. The first column is used for bit rate admission while the second is for MBR
admission.
2. This table is just for user plan CE utilization. No additional CE will be
consumed if SRB over HSUPA while 1 additional CE will be consumed for
SRB over DCH.
3. If there is no matching for service admission bit rate in this table, the CE
utilization number is got by the up matching rules.
The following GBR configuration for the RNC04

2007-05-24

4 , 6

According to the above rules,


1. when 64kbps GBR is configured, MAX(one RLC PDU bit rate, GBR)=
MAX32kbps,64kbps=64kbps
Then the CE consumption number is:
For SRB over DCH user, 10MS HSUPA admission CE number is 2+1=3
For SRB over HSUPA user 10MS HSUPA admission CE number is
4(128kbps by the up matching rules)
2. when <=32kbps GBR is configured, MAX(one RLC PDU bit rate, GBR)=
MAX32kbps,GBR=32kbps
Then the CE consumption number is:
For SRB over DCH user, 10MS HSUPA admission CE number is 1+1=3
For SRB over HSUPA user10MS HSUPA admission CE number is 2
We can see that (VS.LC.ULCreditUsed.Mean is used to monitor)
1. If GBR 64kbps configured and SRB over HSUPA is configured, the CE
admission number for RNC will increase.
2. If GBR configured not more than 32kbps, the CE admission number for RNC
keeps the same.

Handling

Change the GBR from 64kbps to 32kbps for uplink

Process

2007-05-24

5 , 6

After that the Congestion desappeared and the Service CSSR fallack to normal level

Suggestions
and

The engineer should be familiar with the feature document and when the problem happens,
the right feature can be found to solve the issue.

summary
Attachments

Related
document
link

2007-05-24

6 , 6