ZTE UMTS UR15 Voice Service Optimization For Multi-RAB Feature Guide - V1.1

Voice service Optimization
for Multi-RAB
Feature Guide
Voice Service Optimization for Multi-RAB

Version Date Author Reviewer Notes
Compared with UR14:

1. Add “3.1.9 In CS+PS Concurrent
Services Scene, the Optimization for
increasing the Call Connection Rate of the
Cai Yaofang, CS Service” and add the corresponding
V1.0 2016/05/16 Zhanghaiyan
Deng Shiwu parameter in chapter 4.
2. Supplement “Multi-RAB RB Release
Procedure” and related sections.
3. Updated Chapter 6.2, 6.3 and 6.4 by
adding screen shots.
Add "In CS+PS Concurrent Services

V1.1 2016/09/27 Zhanghaiyan Ke Yazhu Scene, the Optimization for Releasing CS
Service" and the related parameter.
© 2016 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used
without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to
change without notice.
ZTE Confidential Proprietary 1

TABLE OF CONTENTS
1 Feature Attribute ............................................................................................... 7
2 Overview ............................................................................................................ 7
2.1 Feature Introduction ............................................................................................. 7
2.1.1 ZWF21-05-026 Service Optimization for Multi-RAB ............................................. 7
2.1.2 ZWF21-05-029 Voice Service Optimization for Common State ............................ 9
2.1.3 Multi-RAB Release............................................................................................. 10
2.2 License Control .................................................................................................. 10
2.2.1 ZWF21-05-026 Service Optimization for Multi-RAB ........................................... 10
2.2.2 ZWF21-05-029 Voice Service Optimization for Common State .......................... 11
2.2.3 Multi-RAB RB Release Procedure ..................................................................... 11
2.3 Correlation with Other Features ......................................................................... 11
2.3.3 Multi-RAB Release............................................................................................. 12
3 Technical Description ..................................................................................... 12

3.1 ZWF21-05-026 Voice Service Optimization for Multi-RAB.................................. 12
3.1.1 Channel Allocation Policy for the PS Service in CS+PS Multi-RAB .................... 13
3.1.2 Channel Transition Policy for the PS Service Based on the Traffic Volume in
CS+PS Multi-RAB .............................................................................................. 17
3.1.3 Controlling Policy for the RB Reconfiguration Method ........................................ 21
3.1.4 Traffic Measurement .......................................................................................... 22
3.1.5 Adding the Controlling Switch of Transiting PS to 0/0 kbps for Concurrent
Services ............................................................................................................. 22
3.1.6 Handling Policy for CS+PS Concurrent Services in Poor Coverage Areas ......... 23
3.1.7 The Strategy of Prohibiting PS Service to be Carried on HS-DSCH/E-DCH for
Concurrent CS+PS ............................................................................................ 26
3.1.8 The Controlling Handling Strategy for the PS Service Rate Upgrading for
Concurrent CS+PS with the PS Service on Low Rate DCH ............................... 28
3.1.9 In CS+PS Concurrent Services Scene, the Optimization for increasing the Call
Connection Rate of the CS Service .................................................................... 29
3.2 ZWF21-05-029 Voice Service Optimization for Common State .......................... 30
3.2.1 Handling of Accompanying CS Domain Service for the UE in PCH State .......... 30
3.2.2 Handling of Accompanying CS Domain Service for the UE in CELL_FACH State
31
3.3 Multi-RAB Release............................................................................................. 32

3.3.2 In CS+PS Concurrent Services Scene, the Optimization for Releasing CS

Service ............................................................................................................... 33
4 Parameters....................................................................................................... 33
4.1 ZWF21-05-026 Service Optimization for Multi-RAB ........................................... 33
4.1.1 The Parameter Related to the Channel Allocation Strategy for the PS Service in
CS+PS Multi-RAB .............................................................................................. 33
4.1.2 The Parameter Related to the Channel Transition Strategy for the PS Service
Based on the Traffic Volume in CS+PS Multi-RAB ............................................. 36
4.1.3 The Parameter Related to the Controlling Strategy for the RB Reconfiguration
Method ............................................................................................................... 38
4.1.4 Add Controlling Switch of Transition PS to 0/0kbps for Concurrent service ........ 40
4.1.5 The Handling Strategy for CS+PS Concurrent Services in the Poor Coverage .. 41
4.1.6 The Strategy of Prohibiting PS Service to be carried on HS-DSCH/E-DCH for
Concurrent CS+PS ............................................................................................ 44
4.1.7 The Handling Strategy for the PS Service Rate Upgrading for Concurrent
CS+PS with the PS Service on Low Rate DCH .................................................. 45
4.1.8 In CS+PS Concurrent Services Scene, the Optimization for increasing the Call
Connection Rate of the CS Service .................................................................... 47
4.2 ZWF21-05-029 Voice Service Optimization for Common State .......................... 47
4.3 Multi-RAB Release............................................................................................. 49
5 Related Counters and Alarms ........................................................................ 50

5.1 Related Counters ............................................................................................... 50
5.2 Related Alarms .................................................................................................. 50
6 Engineering Guide .......................................................................................... 51

6.1 Application Scenario .......................................................................................... 51
6.2 Feature Activation Procedure ............................................................................. 53
6.3 Feature Validation Procedure............................................................................. 70
6.4 Feature Deactivation Procedure......................................................................... 71
6.5 Impact on the Network ....................................................................................... 71
6.6 The Test Data .................................................................................................... 74

6.6.1 Test Result......................................................................................................... 74

6.6.2 Commercial Conclusion ..................................................................................... 78
7 Abbreviation .................................................................................................... 79
8 Reference Document....................................................................................... 79

FIGURES
Figure 6-1 Parameters configuration interface 1 ................................................................54

Figure 6-10 Parameters configuration interface 10 ............................................................59
TABLES

Table 2-1 License Control List ...........................................................................................10

Table 2-2 License Control List ...........................................................................................11
Table 4-1 Parameters List (The Parameter Related to the Channel Allocation Strategy for
the PS Service in CS+PS Multi-RAB) ...................................................................................33
Table 4-2 Parameters List (The Parameter Related to the Channel Transition Strategy for
the PS Service Based on the Traffic Volume in CS+PS Multi-RAB) ......................................36
Table 4-3 Parameters List (The Parameter Related to the Controlling Strategy for the RB
Reconfiguration Method) ......................................................................................................38
Table 4-4 Parameters List (Add Controlling Switch of Transition PS to 0/0kbps for
Concurrent service) ..............................................................................................................40
Table 4-5 Parameters List (The Handling Strategy for CS+PS Concurrent Services in the
Poor Coverage) ....................................................................................................................41
Table 4-6 Parameters List (The Strategy of Prohibiting PS Service to be carried on
HS-DSCH/E-DCH for Concurrent CS+PS) ...........................................................................44
Table 4-7 Parameters List (The Handling Strategy for the PS Service Rate Upgrading for
Concurrent CS+PS with the PS Service on Low Rate DCH).................................................45
Table 4-8 Parameters List (In CS+PS Concurrent Services Scene, the Optimization for
increasing the Call Connection Rate of the CS Service) .......................................................47
Table 4-9 Parameters List (Voice Service Optimization for Common State) .................47
Table 4-10 Parameters List (Multi-RAB RB Release Procedure) ...............................49
Table 5-1 Counter List .......................................................................................................50

1 Feature Attribute
RNC version: [ZXWR RNC V3.15.10.20/ZXUR 9000 V4.15.10.20]
Node B version: [ZXSDRV4.15.10]
Attribute: [Optional]
Involved NEs:
NE Name Related or Not Special Requirement
UE √ -
Node B - -
RNC √ -
iTC - -
MSC - -
MGW - -
SGSN - -
GGSN - -
HLR - -
 “√”: involved
 “-”: not involved
2 Overview
2.1 Feature Introduction
2.1.1 ZWF21-05-026 Service Optimization for Multi-RAB
This feature can decrease the interference to voice service caused by high bit-rate PS
service in Multi-RAB, and then reduce the voice quality degradation and improve service
experience.
As the popularize application of smart phone and PS service, during the voice service,
the PS services are often initiated in the background by application of smart phone (for

example, Keep-Alive message transmission), or during PS service, the voice service,

especially as incoming call, may also be initiated. In general, the duration of voice service
is shorter than which of PS, and users are more sensitive to voice service quality than PS,
then in the multi-RAB scenario above, the voice service quality should be guaranteed
and voice call drop should be avoided to the greatest extent possible. To achieve this
goal, the PS service can establish in DCH channel in case of PS service is added to a
voice service; If a voice service is added to PS service, the PS service can reconfigure to
DCH channel, where the DCH rate can be configured which can be set to the minimum
value 0 (refer to section “Channel Allocation Policy for the PS Service in CS+PS
Multi-RAB”). In addition, during voice service, the PS service should not be reconfigure to
HSPA due to traffic volume to reduce call drop caused by HSDPA serving cell change,
and decrease the interference to voice service caused by high speed PS service carried
in HSPA. If some CS voice services last for a long time, to avoid the PS service
QoE(Quality of Experience) degradation within whole CS+PS duration, ZTE RAN
provides the configurable timer. This timer is triggered when CS voice + PS happens,
only if the timer is expired, the DRBC operations for those concurrent PS services of this
user, such as rate adjustment or channel switching, are allowed, else these operations
are forbidden before the timer expiration (refer to “Policy of Limiting the DRBC Function
of the PS Service During the CS Service Retention”).
These policies above are mainly aimed to improve the CS voice service experience, on
the other hand, to improve requirement of PS service for Multi-RAB, another policy can
be applied(it is under the control of network via a different switch for above described
policies). When PS services are established on HS-DSCH/E-DCH or HS-DSCH/DCH,
even if CS voice service is ongoing or newly setup, the channel switch based on traffic
volume measurement for PS service is supported. According to different traffic volume
measurement events, PS services can be moved downward to DCH/DCH from
HS-DSCH / E-DCH or HS-DSCH /DCH and vice versa. "Channel Transition of HS/E or
HS/D->D/D Based on the Traffic Volume" and "Channel Transition of
DCH/DCH->HS-DSCH/E-DCH (HS-DSCH/DCH) Based on the Traffic Volume"
Besides, the following processing is brought in to handle the multi-RAB performance

degradation in poor coverage:
When a I/B PS service is added to a ongoing voice service, or a voice service is added to
ongoing I/B PS service(s), if the user is in poor coverage area, then the I/B service is

established (for newly setup service) or switched (for ongoing PS service) to DCH
0kbps/0kbps. In addition, if the UE is always in poor coverage within multi-RAB duration,
the PS services are forbidden to increase bitrate, and therefore, it can be decreased for
the performance degradation of voice service in multi RAB in poor radio environment.
Refer to section “Handling Policy for CS+PS Concurrent Services in Poor Coverage
Areas”.
And the following improvement is introduced: if the PS service of multi-RAB is carried on

DCH, and its bitrate is below a pre-configured low bitrate threshold, then the channel
switch( to HS-DSCH/E-DCH or HS-DSCH/DCH) or increasing bitrate can be
implemented according to the 4A event based on the specified traffic volume
measurement. Refer to section “The Controlling Handling Strategy for the PS Service
Rate Upgrading for Concurrent CS+PS with the PS Service on Low Rate DCH”.
In order to increase the call connection rate of the CS service, the admission strategy for
the CS+PS Concurrent Services is optimized: in the scenes of incoming relocation, hard
handover, call reestablishment and the user being transited from the common state to
the CELL_DCH state because of the CS call for the concurrent services, if the PS service
with non-0/0kbps rate is denied, it is accessed with the configuration of CS+PS
0/0kbps,which gurrantees that the PS service can not be refused, so as to avoid that the
CS service cannot be admitted because the PS service is denied,so that the call
connection rate of the CS service is increased. Refer to section” In CS+PS Concurrent
Services Scene, the Optimization for increasing the Call Connection Rate of the CS
Service”.
2.1.2 ZWF21-05-029 Voice Service Optimization for Common State
This function is designed for the UE in the CELL_PCH/URA_PCH and CELL_FACH

state having received the CS domain call. The RNC identifies it in advance, and starts
the operation of transitioning the UE from CELL_PCH/URA_PCH/CELL_FACH state to
CELL_DCH state as early as possible, and establishes the CELL_DCH channel to
execute the process of establishing the CS service, so as to decrease the time of the call
process and increase the success rate, to improve the user experience.

2.1.3 Multi-RAB Release
In the RAB release procedure for CS+PS multi-RAB services, after RNC send Radio
Bearer Release message to UE, if it does not receive the Radio Bearer Release
Complete message in control plane from UE when waiting timer is expired, but the user
plane in RNC confirms that UE has received the Radio Bearer Release message by RLC
ACK, then RNC can do the subsequent processing as it has received the Radio Bearer
Release Complete message from UE, therefore the success rate of RAB Release
operation can be increased, and the call drop rate can be decreased.
Furthermore, for CS+PS multi-RAB services, after the CS service is released, and there
is another CS service, it will be in the CS+PS scene very probably. Because the CS call
success rate is not higher thant that in the single CS service scene, the user experience
of the CS service may be influenced. In order to increase the CS call success rate, when
the CS service is released in the CS+PS service, if the 4B or 4B0 event has been
reported for the PS, the PS service is released at the same time.
2.2 License Control
This feature is controlled by license, which should be granted by OMCR before it is

turned on.
Table 2-1 License Control List
License Configured
Feature ID Feature Name Unit
Control Item NE
Voice service Voice service

ZWF21-05-026 Optimization for Optimization RNC RNC
Multi-RAB for Multi-RAB

This feature is controlled by license, which should be granted by OMCR before it is

turned on.
Table 2-2 License Control List
License Configured
Feature ID Feature Name Unit
Control Item NE
Voice Service
Voice Service
Optimization
ZWF21-05-029 Optimization for CELL CELL
for Common
Common State
State
2.2.3 Multi-RAB RB Release Procedure
This feature is not controlled by license.
2.3 Correlation with Other Features
1. Required Features
None
2. Mutually Exclusive Features
None
3. Affected Features
ZWF21-04-004 Dynamic Radio Bearer Control
ZWF23-04-004 Dynamic Channel Type Transfer for HSDPA Service
ZWF25-04-005 Dynamic Channel Type Transfer for HSUPA Service

None
None
ZWF21-04-004 Dynamic Radio Bearer Control
2.3.3 Multi-RAB Release
None
None
None
3 Technical Description
3.1 ZWF21-05-026 Voice Service Optimization for

Multi-RAB
To improve the experience of CS services accompanied with PS services, the RNC limits
the upper threshold of the PS service rate and reduces the adjustment of the PS service
rate to decrease the impact on the voice service caused by high bit-rate PS services in

Multi-RAB, thereby ensuring the voice service quality, and improving the voice service
experience.
The optimization for multi-RAB includes the following two functions:
 The channel allocation policy for the PS service in CS+PS multi-RAB
 The channel transition policy for the PS service based on the traffic volume in
CS+PS multi-RAB
3.1.1 Channel Allocation Policy for the PS Service in CS+PS Multi-RAB
The CS+PS scenarios include two cases:
 A UE is in CELL_DCH status before the CS+PS services are established.
 A UE is in common status before the CS+PS services are established.
The channel allocation policies for the PS service may differ when a UE is in a different
status.
3.1.1.1 Channel Allocation Policy for the PS Service in CS+PS Multi-RAB When a
UE is in CELL_DCH Status
This function is controlled by the parameter ULogicalRnc.dchUeCsPsSwch. Supposing

the PS service is established and then the CS service needs to be established on the
DCH channel, for UEs of R5 or earlier: there may be call drop when the PS service is
fallen back, so a switch is added to control that.
1. For UEs of R6 or later:
When the switch ULogicalRnc.dchUeCsPsSwch is set to “On”:
Supposing the CS service is established on the DCH channel and then the PS service
needs to be established, the PS service is established on the DCH/DCH with the rate
with the value of DCH_Rate.

Supposing the PS service is established and then the CS service needs to be

established on the DCH channel, if the PS service is not on the DCH/DCH and not use
DCH_Rate, then the PS service is switched to the DCH/DCH channel with DCH_Rate.
Where, the determination method of uplink and downlink DCH_Rate is as follows:
The uplink and downlink DCH rate can be controlled separately by

ULogicalRnc.csPsSceUlDchRate and ULogicalRnc.csPsSceDlDchRate, which is noted
as “the DCH rate of PS reconfigured to DCH/DCH used for CS+PS scene”, which
attends the determination of DCH rate, and the formula is as follows:
DCH_Rate=min( max(min(“the DCH rate of PS reconfigured to DCH/DCH used for

CS+PS scene”, “the limited DCH rate threshold of PS used for CS+PS scene”),
GBR), MaxBR，”limited rate of DCH”)
Where, for streaming class service, the GBR is the RAB assignment GBR; for I/B
class service, GBR is 0; MaxBR is the maximum rate after being handled by RNC.
The above “the limited DCH rate threshold of PS used for CS+PS scene” is
configured for uplink and downlink separately;”limited rate of DCH” is the maximum
uplink and downlink DCH rate of the cell. The detailed content of these rates refer to
ZTE UMTS Dynamic Radio Bearer Control Feature Guide.
2. For UEs of R5 or earlier:
When the switch ULogicalRnc.dchUeCsPsSwch is set to “On”:
Supposing the CS service is established on the DCH channel and then the PS service
needs to be established, the PS service is established on the DCH/DCH with “the DCH
rate of PS reconfigured to DCH/DCH used for CS+PS scene”.
Supposing the PS service is established and then the CS service needs to be

established on the DCH channel, ULogicalRnc.csPlusPsR5UeSwch should also be
judged: If the switch ULogicalRnc.csPlusPsR5UeSwch is set to “On” and the PS service
is not on the DCH/DCH channel with “the DCH rate of PS reconfigured to DCH/DCH
used for CS+PS scene”, the PS service is reconfigured to the DCH channel with “the
DCH rate of PS reconfigured to DCH/DCH used for CS+PS scene”. If the switch
ULogicalRnc.csPlusPsR5UeSwch is set to “Off”, the fallback of the PS service rate is not
needed.

Note: If the CS and PS services in CS+PS multi-RAB are established according to the
channel allocation policy described above, for how to set the subsequent policies for rate
increase on DCH/DCH->DCH/DCH based on traffic volume and how to determine the
target rate, please refer to the ZTE UMTS Dynamic Radio Bearer Control Feature Guide.
Here is an optimization for original strategy for switch

ULogicalRnc.dchUeCsPsSwchtakes the value as “1:On”. If the switch is in “off”, the
strategy remains the same as the original one, i.e. to allocate HS-DSCH/EDCH or
HS-DSCH/DCH or DCH/DCH for the PS service according to the UE‟s capability.
3.1.1.2 Channel Allocation Policy for the PS Service in CS+PS Multi-RAB When a
UE is in Common Status
For a UE in CELL_FACH status or CELL_PCH/URA_PCH status, if there is CS service

coming, the ZTE RNC introduces the channel allocation policy for the PS service in this
scenario to increase the CS service success rate, which is described as the follows:
This function is controlled by the switch ULogicalRnc.fchPchUeCsPsSwch.
If ULogicalRnc.fchPchUeCsPsSwch is set to “On”, when the UE in the CELL_FACH or

CELL_PCH/URA_PCH state initiates CS service and the CS service is to be established
on the DCH/DCH, the PS service is forced to be established on the DCH/DCH.
The uplink and downlink rate (DCH_Rate) are determined as follows:
The uplink and downlink DCH rate are controlled by ULogicalRnc.csPsSceUlDchRate

and ULogicalRnc.csPsSceDlDchRate@ separately, which are noted as “the DCH rate of
PS reconfigured to DCH/DCH used for CS+PS scene”, which joins into the determination
of the DCH rate and the formula is as follows:
DCH_Rate=min(max(min(“the DCH rate of PS reconfigured to DCH/DCH used for

CS+PS scene”, “The rate limitation for CS+PS”), GBR), MaxBR, “DCH rate limitation”)
Notes:
The GBR for the streaming service is the GBR in the RAB assignment; the GBR for the
interactive and background service is 0 kbps.

The MaxBR is the maximum bit rate handled by the RNC, and the above rate limitations
for CS+PS are configured for uplink and downlink separately. For detailed information,
refer to the ZTE UMTS Dynamic Radio Bearer Control Feature Guide.
The DCH rate limitation is the downlink and uplink maximum DCH rate allowed by the
cell. For detailed information, refer to 3.1.2.3 DCH Initial Access Rate for PS Service in
the ZTE UMTS Dynamic Radio Bearer Control Feature Guide.
3.1.1.3 The Determination Strategy of the Signaling Rate for CS+PS Multi-RAB
When a UE is in Common Status
For a UE in CELL_FACH status or CELL_PCH/URA_PCH status, if there comes the CS

service and the CS service will be carried on the DCH, and the PS service will be
switched to the DCH, the SRB usually uses the rate of 3.4Kbps, but in order to decrease
the establishment delay of the CS call and to increase the success rate, the high speed
signaling can be used before the CS RB is setup and when the high speed signaling is
determined to be used, the PS rate is modified to 0/0Kbps.
This function is controlled by the high speed signaling switch

URncInfo.highSignalSwch@,
The determination principle of the SRB rate is as follows:
When all the following conditions are satisfied, the SRB rate is obtained from
UCelInfoFDD.cellSigMaxBR otherwise it is 3.4Kbps:
1. The controlling switch ULogicalRnc.fchPchUeCsPsSwch takes the value of “1: On”.
2. The high speed signaling switch URncInfo.highSignalSwch@ takes the value of “1:
On”.
3. The UE in the CELL_FACH state or CELL_PCH/URA_PCH state initiate CS service

and the CS service will be carried on the DCH, and the PS service will be switched
to DCH.
4. If the poor coverage function is on, the UE is not in poor coverage area, for the
details please refer to "3.1.1 RRC Access Strategy in a Poor Coverage Area" in ZTE
UMTS Adaptive Radio Bearer Feature Guide.

Note: If the SRB rate is obtained from UCelInfoFDD.cellSigMaxBR and the value of the
UCelInfoFDD.cellSigMaxBR is “4:CELL_FACH Forced” or “6.8 Kbps” ( When signaling
and service coexist, it is limited that the 6.8k signaling can only be used when the service
is on HS), the SRB is forced to use the rate of 3.4Kbps.
The determination of PS rate:
If the final SRB rate is higher than 3.4Kbps, the PS uplink and downlink is modified to
0/0Kbps.
If the SRB rate is 3.4Kbps, the PS uplink and downlink rat is the same as the DCH_Rate
in "3.1.2.1 Channel Transition of HS/E or HS/D->D/D Based on the Traffic Volume".
The DRBC strategy before the CS RAB is established:
Because the configuration of the PS service during the establishment of the CS RAB will
influence the connection success rate, when the UE in the CELL_FACH state or
CELL_PCH/URA_PCH state initiate the CS service, once the signaling and the PS
service are established on the DCH, the internal timer (which is set fixedly as 5s) is
started, the DRBC is forbidden before the timer expires.
3.1.2 Channel Transition Policy for the PS Service Based on the Traffic
Volume in CS+PS Multi-RAB
To improve the CS service experience, the PS service is switched from HS-DSCH to

DCH if it has no data. It helps avoid unnecessary procedures of HS-DSCH serving cell
change to improve the CS service quality.
To avoid ping-pong transition between DCH/DCH and HS-DSCH/E-DCH

(HS-DSCH/DCH), which may influence the CS service quality, the limitation of switching
from DCH to HS-DSCH is added.
If the CS+PS services for a UE exist simultaneously, the following function is introduced
to ensure that the CS service quality is not affected by too many reconfigurations caused
by the rate increase and decrease of the PS service:
If the PS service exists after the CS service persists for a period of time, the PS service is
not allowed to implement the DRBC function.

This function affects the following three DRBC transition processes:

 The channel transition of HS/E or HS/D->D/D based on the traffic volume
 The channel transition of DCH/DCH->HS-DSCH/E-DCH(HS-DSCH/DCH) based on

the traffic volume
 The policy of forbidding the PS service from performing the DRBC functions when
the CS service exists.
3.1.2.1 Channel Transition of HS/E or HS/D->D/D Based on the Traffic Volume
This function is controlled by the switch ULogicalRnc.csPsSceHsToDSwch.
If the PS service is established on the HS-DSCH/E-DCH or HS-DSCH/DCH and the

switch ULogicalRnc.csPsSceHsToDSwch is set to “On”, the transition from
CELL_DCH(DL HS-DSCH/UL E-DCH) or CELL_DCH(DL HS-DSCH/UL DCH) to
CELL_DCH(DL DCH/UL DCH) will be triggered when the following conditions are
satisfied:
 There exists concurrent CS service, which is established on the DCH;
URncInfo.psDrbcProhSwch is set to “Off”, or URncInfo.psDrbcProhSwch is set to

“On” and the timer (Timer_limitDRBC) expires. Timer_limitDRBC defines the
effective time length for forbidding the DRBC function of the PS service based on
the traffic volume in the CS+PS scenario. The timer is started at the time when the
CS+PS concurrent services occurs immediately, and is obtained from
URncInfo.psDrbcProhTimer.
 The traffic volume measurement reports of 4B0 events on uplink and downlink are
received for ULogicalRnc.hsToDE4B0timeThr times continuously, and the downlink
channel transition is triggered. (Note: If this condition is not satisfied but the
corresponding 4A event, 4B event, or other event is received, the corresponding
counter must be cleared).
In this case, the fallback rate (DCH_Rate) when the UE is switched from
HS-DSCH/E-DCH or HS-DSCH/DCH to DCH/DCH is determined as follows:

The uplink and downlink DCH rate are controlled by ULogicalRnc.csPsSceUlDchRate

and ULogicalRnc.csPsSceDlDchRate@ separately, which are noted as “the DCH rate of
PS reconfigured to DCH/DCH used for CS+PS scene”, which joins into the determination
of the DCH rate and the formula is as follows:
DCH_Rate=min(max(min(“the DCH rate of PS reconfigured to DCH/DCH used for

CS+PS scene”, “The rate limitation for CS+PS”), GBR), MaxBR, “DCH rate limitation”)
Furthermore, if the UE is transited from DL HS-DSCH/UL DCH to UL DCH/DL DCH, the

UL DCH rate =min {DCH_Rate, the rate of UL DCH before transitioning}.
Notes:
Interactive and background service is 0 kbps;
The MaxBR is the maximum bit rate handled by the RNC, and the above rate limitation
for CS+PS are configured for uplink and downlink separately. For detailed information,
refer to the ZTE UMTS Dynamic Radio Bearer Control Feature Guide.
Note:
For traffic volume measurement of HS-DSCH, refer to Traffic Volume Measurement in

the ZTE UMTS HSDPA Introduction Feature Guide. For the interactive/background
service, the parameters related to traffic volume measurement are obtained from the MO
UDedIBHsdschEvUpTrv. For the streaming service, the parameters related to traffic
volume measurement are obtained from the MO UDedSHsdschEvUpTrv.
For detailed information about the E-DCH channel traffic measurement, refer to Traffic
Volume Measurement in this document.

3.1.2.2 Channel Transition of DCH/DCH->HS-DSCH/E-DCH (HS-DSCH/DCH) Based

on the Traffic Volume
After a UE is switched from HS-DSCH/E-DCH or HS-DSCH/DCH to DCH/DCH (It can be

triggered by traffic volume or other conditions), the DRBC operations of switching to the
HS or rate adjustment on the DCH based on traffic volume measurement, are allowed.
To avoid ping-pong transition between DCH/DCH and HS-DSCH/E-DCH

(HS-DSCH/DCH), which may influence the CS service quality, limitations to switching
from DCH to HS-DSCH are added.
This function is controlled by the switch ULogicalRnc.dToHsDelaySwch.
If the switch is set to “On”, after the PS service is switched from HS-DSCH/E-DCH or
HS-DSCH/DCH to DCH/DCH, the timer Timer_LimitHS is started. The length of this timer
is controlled by URncFunction.dToHsDelayThr.
Before the timer Timer_LimitHS expires, switching from DCH/DCH to HS-DSCH/E-DCH

(HS-DSCH/DCH) based on traffic volume is forbidden.
After the timer Timer_LimitHS expires, switching from DCH/DCH to HS-DSCH/E-DCH

(HS-DSCH/DCH) based on traffic volume is allowed.
Note:
For detailed information about the channel transition policy from DCH/DCH to
HS-DSCH/E-DCH (HS-DSCH/DCH) based on traffic volume and information about traffic
volume measurement, refer to the ZTE UMTS HSDPA Introduction Feature Guide, ZTE
UMTS HSUPA Introduction Feature Guide, and ZTE UMTS Dynamic Radio Bearer
Control Feature Guide.
3.1.2.3 Policy of Limiting the DRBC Function of the PS Service During the CS
Service Retention
If the CS+PS services for a UE exist simultaneously, the following function is introduced
to ensure that the CS service quality is not affected by too many reconfigurations caused
by rate increase and decrease of the PS service:

If the PS service exists after the CS service persists for a period of, the PS service is not
allowed to implement the DRBC function.
This function is controlled by the switch URncInfo.psDrbcProhSwch.
If URncInfo.psDrbcProhSwch is set to”On”, that is, the PS DRBC function is forbidden

within a certain period of time, then:
When the CS+PS concurrent services happen, the timer Timer_limitDRBC is started.
Before the timer expires, if the PS service exists, the DRBC operations for the PS service
are not allowed, including rate increase, rate decrease, and channel transition.
After the timer Timer_limitDRBC expires, the DRBC operations for the PS service are
allowed.
Timer_limitDRBC defines the effective time length for forbidding the DRBC function of
the PS service based on traffic volume in the CS+PS scenario. It is obtained from
URncInfo.psDrbcProhTimer.
3.1.3 Controlling Policy for the RB Reconfiguration Method
The UEs of the R6 version and later versions have the capability of simultaneously
setting up a new service and reconfiguring the online service through the radio bearer
setup message. Considering the compatibility with other UEs, the ZTE RNC uses the
controlling function for parallel processing of new service establishment and online
service reconfiguration for UEs of the R6 version and later versions.
This function is controlled by the switch ULogicalRnc.r6MulRabRcfgMeth.
When the following conditions are satisfied, the RNC uses one message to set up a new
service and reconfigure the online service for a UE:
 The switch ULogicalRnc.r6MulRabRcfgMeth is set to “0: RB Setup Method”.
 The UE version is R6 or a later version.
 The UE needs to reconfigure the online service at the same time when it sets up a
new service due to various causes.

If the switch ULogicalRnc.r6MulRabRcfgMeth is set to “1: RB Reconfiguration Method”,

and if the RB of the online service of the UE must be reconfigured due to various causes
when a new service is established, the online service is reconfigured to the target
channel and rate, following which the new service is established.
The UEs of versions earlier than R6 do not have the capability of simultaneously setting
up a new service and reconfiguring the online service through the radio bearer setup
message. Therefore, they are not controlled by the switch
ULogicalRnc.r6MulRabRcfgMeth, the online service is reconfigured to the target channel
and rate, and then, the new service is established.
3.1.4 Traffic Measurement
The traffic measurement on the E-DCH measures the uplink E-DCH throughput in the FP
layer. It is executed by the user plane.
For the service on the E-DCH, the data volume is accumulated within the average time,
then, the time window is slid 20 ms, the data volume is accumulated again within the
average time.
When the CS+PS multi-RAB occurs, the measurement of the user plane throughput for
switching from E-DCH to DCH reuses the measurement of the E-DCH channel transition
for a single service, and the related traffic measurement parameters are obtained from
the MO UDedEdchEvUpTrv. For detailed information, refer to the ZTE UMTS HSUPA
Introduction Feature Guide.
3.1.5 Adding the Controlling Switch of Transiting PS to 0/0 kbps for

Concurrent Services
The switch ULogicalRnc.noDataPs00Swch is used to control whether the PS service

needs to be transited to 0/0 kpbs when it has no data. The policy after the switch
ULogicalRnc.noDataPs00Swch is added is described as follows:
When the 4B0 event triggers CELL_DCH(DL DCH/ UL DCH ) -> URA_PCH/CELL_PCH
(for the triggering condition, refer to the ZTE UMTS Dynamic Radio Bearer Control
Feature Guide), if there exist concurrent services, all services must satisfy the condition
of transiting to URA_PCH/CELL_PCH.

If CS+PS concurrent services exist or multi-PS services exist, among which there is a PS
I/B class service with no traffic on uplink and downlink, the channel transiting policy is as
follows:
When the RNC continuously receives the 4B0 event from the user plane and the UE for
UDrbc.dToPchThd times, the RNC executes the following operations:
 If there is no DRNC link, if ULogicalRnc.noDataPs00Swch is set to “On”, and the PS

service rate is decreased to 0kbps/0kbps; otherwise, the PS service rate is
decreased to the DRBC minimum rate.
 If there is a DRNC link, if ULogicalRnc.noDataPs00Swch is set to “On”, the final

policies need considers with UIurLink.rncFeatSwitchBIT18 also. If
UIurLink.rncFeatSwitchBIT18 is set to “0:Not Support PS(0 kbps /0 kbps)”, the PS
service rate is decreased to the DRBC minimum rate. If
UIurLink.rncFeatSwitchBIT18 is set to “1:Support PS(0 kbps /0 kbps)”, the PS
service rate is decreased to 0kbps/0kbps.If ULogicalRnc.noDataPs00Swch is set to
“Off”, the PS service rate is decreased to the DRBC minimum rate.
For the definition of the DRBC minimum rate, refer to the ZTE UMTS Dynamic Radio
Bearer Control Feature Guide.
3.1.6 Handling Policy for CS+PS Concurrent Services in Poor Coverage

Areas
When the CS service or the I/B class PS service is initiated, for the case of CS+PS
concurrent services in bad coverage areas, the I/B class service rate is decreased to 0/0
kbps (when there exists PS services already) or the rate of the newly established I/B
class PS service is set to 0/0 kbps.
During the process of CS+I/B class PS services, if the UE is in a bad coverage area, the
PS service rate is not allowed to be increased.
No matter whether the UE is initiating a call or is during the call process, if the UE is not
in a bad coverage area, the channel allocation policy is the same as the current policy for
concurrent services.

If the UE is not in a bad coverage area when the CS service is initiated, but later during
the call process, the UE is in a bad coverage area, to avoid increase in the dropped-call
rate, the I/B class PS service will not be triggered to transit to 0/0 kbps.
Note: The function is suitable for I/B class service, for the Streaming class service, the
policy is the same as the current policy.
The global switch ULogicalRnc.csPsBadCovSwch is used to control whether the I/B

class PS service rate should be forcibly decreased to 0/0 kbps and forbid increasing rate
when the concurrent CS+PS services in a bad coverage area.
Whether a area is a bad coverage area depends on the CPICH channel quality. Two
thresholds (UCelInfoFDD.csPsbadCovEcN0 and UCelInfoFDD.csPsbadCovRscp) are
used separately for P-CPICH Ec/N0 and P-CPICH RSCP. During a call process, the
measurement for bad coverage judgment comes from the intra-frequency measurement
report, and only the best cell is referred to.
3.1.6.1 Channel Allocation Policy for the PS Service When the UE is in a Poor
Coverage Area for the CS+I/B Class PS Concurrent Services
Note: The following policy is applicable to the cases of new establishment, incoming
relocation, hard handover, and call re-establishment.
1. If the CS service is established on the DCH, and then the accompanying I/B class
PS service is established:
 If ULogicalRnc.csPsBadCovSwch is set to “On” and the UE is in a bad coverage

area, the PS service is established on the DCH and the rate is 0/0 Kbps.
 Otherwise, the policy is the same as the current policy.
2. If the I/B class PS service is established, and then the accompanying CS service is
established on the DCH:
 If ULogicalRnc.csPsBadCovSwch is set to “On” and the UE is in a bad coverage

area, the PS service is transited to the DCH and the rate is 0/0 Kbps.
 Otherwise, the policy is the same as the current strategy.

The following describes the principle for determining whether the UE is in a bad coverage
area during the service establishment process:
If the P-CPICH Ec/N0 of the best cell reported by UE is smaller than or equal to
UCelInfoFDD.csPsbadCovEcN0 or the P-CPICH RSCP of the best cell reported by UE is
smaller than or equal to UCelInfoFDD.csPsbadCovRscp, the UE is defined in a bad
coverage area; otherwise, the UE is not in a bad coverage area.
3.1.6.2 DRBC Policy for CS+PS When the UE is in a Poor Coverage Area for the
CS+I/B Class PS Concurrent Services
The following three cases are referred to:
 For CS+ PS concurrent services, if the UE enters a bad coverage area from a
non-bad coverage area, the rate increasing is not allowed.
 For CS+ PS concurrent services, if the UE enters a non-bad coverage area from a
bad coverage area, the limitation of rate increasing is released
 For CS+ PS concurrent services, if the CS call is released, the limitation of rate
increasing is released.
Note: If a UE enters a bad coverage area from the non-bad coverage area, the PS
service will not be decreased to PS0/0 kbps.
The following describes the principle for determining whether the UE is in a bad coverage
area during the call process:
Compare the reported measurement values of P-CPICH Ec/N0 and P-CPICH RSCP of
the best cell with the thresholds UCelInfoFDD.csPsbadCovEcN0 and
UCelInfoFDD.csPsbadCovRscp. If P-CPICH Ec/N0 ≤ UCelInfoFDD.csPsbadCovEcN0 or
P-CPICH RSCP ≤ UCelInfoFDD.csPsbadCovRscp, the UE is in a bad coverage area;
otherwise, the UE is a non-bad coverage area. If the measurement value cannot be
obtained, the UE is regarded as being in a non-bad coverage area.
Note: The threshold for the CPICH is obtained from the best cell of the active set
maintained by the S side, and the measurement value is obtained from the cell with the

latest best quality reported by the UE. The same principle is used for both the Iub
interface and Iur interface.
3.1.7 The Strategy of Prohibiting PS Service to be Carried on

HS-DSCH/E-DCH for Concurrent CS+PS
Because the combination of the CS service being carried on DCH/DCH and the PS
service being carried on HS/E increases the call drop rate of the CS service, the strategy
of prohibiting the PS service using HS/E in concurrent CS+PS scenario is introduced.
This function is controlled by the switch of prohibiting PS service carried on

HS-DSCH/E-DCH for concurrent CS+PS services
(ULogicalRnc.csPlusPsHSEProhSwch).
If ULogicalRnc.csPlusPsHSEProhSwch takes the value of “1: On” and the UE supports

HSDPA:
1. The strategy of the concurrent services establishment for the UE supporting HSDPA
is as follow:
(1) For the service setup for the concurrent CS+PS of the UE in the CELL_DCH
state:
1) If the CS service has been setup first and then comes the PS service, it
is limited that the PS service cannot use DL HS-DSCH/UL E-DCH.
2) If the PS service is setup and then comes CS service and the PS

service is already on HS-DSCH/E-DCH, the PS service should fall back
to HS-DSCH / DCH or DCH/DCH.
(2) For the service setup for the concurrent CS+PS of the UE in the
CELL_FACH state:
If the UE is in the CELL_FACH state or PCH state and there comes the CS
service, the PS service cannot use HS/E.
The determination method of the rate for the PS service when it is carried on the DCH
channel:
When the PS service is carried on DCH/DCH according to the determination result of the
above strategy of limiting the use of HS/E, the DCH rate value keeps in accordance with

that of the PS service when it is established on DL DCH/UL DCH in CS+PS Multi-RAB.

For details, please refer to “3.1.1.1 Channel Allocation Policy for the PS Service in
CS+PS Multi-RAB when a UE is in CELL_DCH Status”.
When the PS service is carried on HS-DSCH/DCH according to the determination result

of the above strategy of limiting the use of HS/E, the uplink DCH takes value of
min( max(min(csPsSceHSDUlDchR, "The rate limitation for CS+PS"),GBR), MaxBR,
"DCH rate limitation").
Where:
CsPsSceHSDUlDchR is the rate used for the uplink DCH in the channel combination of
HS-DSCH/DCH, which is obtained from ULogicalRnc.csPsSceHSDUlDchR;
The rate limitation for CS+PS is configured for uplink and downlink separately. For
detailed information, refer to the ZTE UMTS Dynamic Radio Bearer Control Feature
Guide.
Interactive and background service is 0 kbp.;
The MaxBR is the maximum bit rate handled by the RNC.
2. The DRBC strategy after the CS+PS have been setup in CELL_DCH state:
The PS service of the concurrent CS+PS is not allowed to be transited to HS/E. And the
triggering strategy is the same as the previous strategy which can be referred to in “3.1.2
Channel Transition Policy for the PS Service Based on the Traffic Volume in CS+PS
Multi-RAB”.
Note:

1. For the UE which supports HSDPA, if ULogicalRnc.csPlusPsHSEProhSwch and

ULogicalRnc.dchUeCsPsSwch are turned on at the same time, these two strategies
take effect at the same time. And the available channel is the intersection of these
two strategies.
2. The above strategy only for the setup and DRBC scenes for the concurrent services,
other scenes are not considered, and the scene of CS over HSPA is not considered
either.
3.1.8 The Controlling Handling Strategy for the PS Service Rate Upgrading
for Concurrent CS+PS with the PS Service on Low Rate DCH
The introduction of this sub function is for satisfying the following requirement: to
differentiate the data volume of the PS service for the scene of the concurrent CS+PS
with the PS Service on DCH/DCH. For the small data volume requirement, limiting the
upgrading of the PS rate can avoid the influence to the CS service; for the large data
volume requirement, the UE can be transited to the HS-DSCH/E-DCH or HS-DSCH/DCH,
or upgraded on DCH/DCH, which can guarantee the PS service experience when the
user is also using teleconference ect.
This function is controlled by the switch UExtCelInfoFDD.csPsRateCtrlSwi.
The detailed strategy is as follows:
When the function switch UExtCelInfoFDD.CsPsRateCtrlSwi of the best cell is „On‟, and
for the concurrent CS+PS, and the PS service is on the low rate DCH/DCH, the setting of
the traffic volume measurement are sent to the UE and the user plane respectively for
the uplink and downlink. After receives the 4A event, the RNC makes the following
judgment orderly:
 If the conditions of “Switching from the DL DCH/UL DCH to the DL HS-DSCH/UL
E-DCH triggered by traffic” in the section of “CELL_DCH (DL HS-DSCH/UL E-DCH)
<-> CELL_DCH (DL DCH/UL DCH)” in ZTE UMTS HSUPA Introduction Feature
Guide are satisfied, the PS service is transited to HS-DSCH/E-DCH. If the
conditions of “Switching from DCH to HS-DSCH triggered by traffic volume” in the
section of “CELL_DCH (DL HS-DSCH) <-> DL DCH” in ZTE UMTS HSDPA
Introduction Feature Guide are satisfied, the PS service is transited to HS-DSCH/
DCH.
 If the conditions of “Rate increase triggered by downlink traffic” in the section of “DL

DCH -> DL DCH (Rate Increase)” and “Rate increase triggered by uplink traffic” in
the section of “UL DCH -> UL DCH (Rate Increase)” in ZTE UMTS Dynamic Radio
Bearer Control Feature Guide are satisfied at the same time, the PS service is rate
upgraded on DCH/ DCH.
Where:
The judgment condition of the low rate of the PS service for for the concurrent CS+PS is
as follows: The uplink and downlink DCH rate of the PS service are both not larger than
the threshold ULogicalRnc.csPsLowRateThresh.
The uplink and downlink measurement threshold use the newly added 4A/4B low rate
threshold of the PS service used for CS+PS scene UDchEvUeTrv.rptThresCsPs and
UDchEvUpTrv.rptThresCsPs.
Note:
 For the scene of CS+PS and the PS is on DCH/DCH 0/0Kbps, the rate upgrading
caused by 4B event will not be handled, but it will be counted.
 When the CS is released, the measurement should be modified to that of the single
PS service.
 After the UL/DL DCH rate being upgraded, the uplink and downlink rate should be
compared to the threshold ULogicalRnc.csPsLowRateThresh, if it is larger than the
rate threshold, the measurement should be modified to use the 4A/4B event
threshold of the single PS service. For the measurement for the single PS DRBC,
please refer to ZTE UMTS Dynamic Radio Bearer Control Feature Guide.
3.1.9 In CS+PS Concurrent Services Scene, the Optimization for

increasing the Call Connection Rate of the CS Service
For the CS+PS concurrent services, current admission strategy is that once one service
is denied, all services are refused. In order to increase the call connection rate of the CS
service, the admission strategy for the CS+PS Concurrent Services is optimized: in the
scenes of incoming relocation, hard handover, call reestablishment, if the PS service with
non-0/0kbps rate is denied, it is accessed with the configuration of CS+PS 0/0kbps,which
gurrantees that the PS service can not be refused, so as to avoid that the CS service

cannot be admitted because the PS service is denied,so that the call connection rate of
the CS service is increased.
The RNC level switch URncFunction.ps00AcCsPlusPsSwch controls this strategy, only

when the switch takes the value as “On”,can this strategy been executed. The details are
as follows:
1. For the scenes of incoming relocation, hard handover and call reestablishment
After the PS service is refused during the normal admission attempt (which means until
the attempt of the DRBC minimum rate the PS service is still denied. For the DRBC
minimum rate please refer to ZTE UMTS Dynamic Radio Bearer Control Feature Guide),
the PS service is decreased to PS(0/0kbps), and it needs no admission judgment (which
means needs no comparison with the admission threshold), and is admitted by default.
The normal admission process is executed for the CS service, if the CS service is denied,
only the CS service is executed the congestion handling.
Note: during the establishment of the CS service, if the PS service is already the
PS(0/0kbps), the channel of the PS service remains unchanged.

Common State
This function is designed for the UE in the CELL_PCH/URA_PCH and CELL_FACH

state having received the CS domain call, the RNC identifies it in advance, and starts the
operation of transitioning the UE from CELL_PCH/URA_PCH/CELL_FACH state to
CELL_DCH state as early as possible, and establishes the CELL_DCH channel to
execute the process of establishing the CS service, so as to decrease the time of the call
process and increase the success rate, to improve the user experience.
3.2.1 Handling of Accompanying CS Domain Service for the UE in PCH

State
When the UE is in the CELL_PCH/URA_PCH state, if the following conditions are

satisfied, the RNC will identify in advance that the service to be assigned is a CS service,

and will transition the UE to the CELL_DCH state in advance. For channel allocation
strategy of the PS service, please refer to “Channel Allocation Policy for the PS Service
in CS+PS Multi-RAB when a UE is in Common Status”:
1. If Establishment Cause IE in Cell Update message is

eRRC_EstablishmentCause_originatingConversationalCall, or
eRRC_EstablishmentCause_terminatingConversationalCall, or
eRRC_EstablishmentCause_emergencyCall;
2. Or the Cell Update message does not carry Establishment Cause IE and the Cell
update cause IE has the value of “paging response” and this paging is from CS
domain.
3.2.2 Handling of Accompanying CS Domain Service for the UE in

CELL_FACH State
When the UE is in the CELL_FACH state, and there exists the PS domain connection,
when the RNC identifies it is a CS service from the paging message or the initial direct
transfer message, it will transition the UE to the CELL_DCH state as soon as possible, so
as to establish the CELL_DCH state channel for the successive CS service establishing
process.
1. The strategy of the RNC identifying the CS service by the paging message and
transitioning it to the CELL_DCH state is as follows:
If the following conditions are satisfied, the RNC transitions the UE from the
CELL_FACH state to the CELL_DCH state after it sends the paging type 2
message to the UE:
i. UUtranCellFDD.fastReturnDchSwch takes the value as “On”;
ii. The RNC receives the paging message with the cause as
terminatingConversationalCall.
1. The strategy of the RNC identifying the CS service by the direct transfer message
and transitioning it to the CELL_DCH state is as follows:

If the following conditions are satisfied, the RNC transitions the UE from the
CELL_FACH state to the CELL_DCH state after it receives the direct transfer
message:
i. If the UE is the original side of the CS service, and the Fast Return to
Cell-DCH for CS MO Initial Direct Transfer Switch
UExtCelInfoFDD.fRDchMOIniDTSwch takes the value of “On”.
ii. UE is the terminating side of the CS service, and the Fast Return to Cell-DCH
for CS MT Initial Direct Transfer Switch UExtCelInfoFDD.fRDchMTIniDTSwch
takes the value of “On”.
iii. The initial direct transfer message received by the RNC indicates it is from the
CS domain.
3.3 Multi-RAB Release
For the Radio Bearer Release procedure of CS+PS concurrent services, when the timer
waiting for Radio Bearer Release Complete message expires, if the user plane confirms
that the UE has received the Radio Bearer Release message, the Radio Bearer Release
procedure is considered a success, and the RNC can proceed with the subsequent
processes. The call drops due to Radio Bearer Release Complete message timeout can
be avoided.
When URncInfo.rbRelByRlcAckSw is “1: On”, and the timer (initiated when the RNC
sends a Radio Bearer Release message to the UE) expires before the RNC receives a
Radio Bearer Release Complete message,
 If the user plane confirms that the UE has received the Radio Bearer Release
message by RLC ACK, the Radio Bearer Release procedure is considered a
success even if the control plane does not receive the Radio Bearer Release
Complete message.
 If the user plane does not confirm that the UE has received the Radio Bearer
Release message, then the procedure is considered a timeout.

3.3.2 In CS+PS Concurrent Services Scene, the Optimization for Releasing

CS Service
For CS+PS multi-RAB services, in current strategy, if the CS service is released, the PS
service can only be released after the 4B0 event of the required times are reached. So if
there comes another CS service, it will be in the CS+PS scene very probably. Because
the CS call success rate is not higher thant that in the single CS service scene, the user
experience of the CS service may be influenced. In order to increase the CS call success
rate, the CS+PS concurrent servies is optimised as the follows:
The bit1 of URncFunction.gresPara59is used as the controlling switch. When the CS

service is released in the CS+PS service, if the 4B or 4B0 event has been reported for
the PS, the PS service is released at the same time.
4 Parameters
4.1 ZWF21-05-026 Service Optimization for Multi-RAB
4.1.1 The Parameter Related to the Channel Allocation Strategy for the PS
Service in CS+PS Multi-RAB
Table 4-1 Parameters List (The Parameter Related to the Channel Allocation Strategy
for the PS Service in CS+PS Multi-RAB)
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
Switch of PS This parameter is used to
service control PS service channel
Channel allocation for concurrent
ULogicalRn
Allocation for CS+PS for UE in 0: Off
c.dchUeCsP N/A 0: Off 1: On
Concurrent CELL_DCH sState. If the 1: On
sSwch
CS+PS for UE parameter is on, for CS
in CELL_DCH service first and then PS
State service triggered scenario,

Recom
Name Range Value d
Value
allocate DCH/DCH for the
PS service; For PS service
first and then CS service
triggered scene, and if PS
is on HS, perform the HS
to DCH reconfiguration.
Otherwise,
HS-DSCH/EDCH,
HS-DSCH/DCH or
DCH/DCH for PS service
is allocated in accordance
with UE capability.
This parameter indicates
whether to transfer from
Switch of
HSDSCH to DCH for R5
Whether to
UE's "PS Setup before
transfer from
CS" when
HS-DSCH to
ULogicalRn dchUeCsPsSwch is on. 0:off
DCH for R5
c.csPlusPsR For the PS setup before N/A 0: Off 0: Off
UE's "PS
5UeSwch CS scene, if both of 1:on
Setup before
CsPlusPsR5UeSwch and
CS"
dchUeCsPsSwch are on,
Concurrent
PS will downgrade from
Service
HSDSCH to DCH,
otherwise not.

the switch of the PS
Switch of the
service channel allocation
PS Service
when a UE in
Channel
CELL_FACH/CELL_PCH/
allocation,Use
URA_PCH state initiates 0: Off
d for UE in the N/A 0: Off 1: On
the CS service. If this 1: On
CELL_FACH/
parameter is set to "1: On",
PCH State
when a UE in
Triggering CS
ULogicalRn CELL_FACH/CELL_PCH/
Call
c.fchPchUe URA_PCH state initiates
CsPsSwch the CS service, the PS

Recom
Name Range Value d
Value
service is reconfigured to
the DCH, and the uplink
and downlink rate are
determined separately by
csPsSceULDchRate and
csPsSceDLDchRate.
when the UE is in the
CELL_FACH or CELL_PCH
URncInfo.hi
state, if it initiates or receives
ghSignalSw N/A 0: Off 1: On
a CS call, whether the SRB
ch
High Speed on DCH can use the high
Signalling speed signaling before the CS 0: Off;
Switch RB setup is completed. 1: On
0: 27.2
kbps
1: 13.6
kbps
Maximum Bit
UCelInfoFD This parameter indicates 2: 6.8 0:
Rate allowed 1: 13.6
D.cellSigMa the maximum signaling bit kbps N/A 27.2
for Signalling kbps
xBR rate allowed in a cell. 3: 3.4 kbps
in Cell
kbps
4:CELL_
FACH
Forced

4.1.2 The Parameter Related to the Channel Transition Strategy for the PS
Service Based on the Traffic Volume in CS+PS Multi-RAB
Table 4-2 Parameters List (The Parameter Related to the Channel Transition Strategy
for the PS Service Based on the Traffic Volume in CS+PS Multi-RAB)
Recom
Name Range Value d
Value
Switch for
Whether the
PS DRBC This parameter indicates
URncInfo.ps based on whether PS DRBC based
0: Off
DrbcProhSw Traffic on traffic volume is N/A 0: Off 0: Off
1: On
ch Volume is forbidden for the CS+PS
Prohibited for scenario.
CS+PS
Scene
Valid Time
Threshold for
PS DRBC This parameter indicates
URncInfo.ps based on the valid time in which PS
DrbcProhTi Traffic DRBC based on traffic 1..65535 s 90 90
mer Volume is volume is forbidden for the
Prohibited for CS+PS scenario.
CS+PS
Scene
A timer is started after the

channel quality or traffic
triggers switching from
Delay Time HS-DSCH/E-DCH or
Threshold of HS-DSCH/DCH to
URncFuncti
D/D->HS/D or DCH/DCH. After the timer (0..65535
on.dToHsDe s 10 10
HS/E after expires, switching from )s, step
layThr
HS/D or HS/E DCH/DCH to 1s
->D/D HS-DSCH/E-DCH or
HS-DSCH/DCH is allowed.
the timer duration.

Recom
Name Range Value d
Value

the switch of switching an
Switch of
HS-DSCH/E-DCH or
HS-DSCH/E-
HS-DSCH/DCH to a
DCH or
ULogicalRn DCH/DCH, used for the
HS-DSCH/DC 0: Off
c.csPsSceH CS+PS scenario. For the N/A 0: Off 1: On
H to 1: On
sToDSwch CS+PS scenario, if this
DCH/DCH,Us
ed for CS+PS
when there is no data, the
Scene
PS service is switched
from the HS to the DCH.
The Uplink
DCH Rate of
This parameter indicates (0, 8, 16,
PS
the uplink rate after the PS 32, 64,
Reconfigured
service is reallocated to the 128, 144, kbps
to
DCH, used for CS+PS 256, 384)
ULogicalRn DCH/DCH,Us
scenario. kbps
c.csPsSceUl ed for CS+PS 16 16
DchRate Scene
The downlink
DCH Rate of
PS
the downlink rate after the 32, 64,
Reconfigured
PS service is reallocated to 128, 144, kbps
to
the DCH, used for CS+PS 256, 384)
ULogicalRn DCH/DCH,Us
scenario. kbps
c.csPsSceDl ed for CS+PS 8 8
DchRate Scene

whether to disallow the
Switch of DCH/DCH to be switched
ULogicalRn D/D->HS/D or to the HS-DSCH/E-DCH or
0: Off
c.dToHsDel HS/E after HS-DSCH/DCH after traffic N/A 0: Off 1: On
1: On
aySwch HS/D or HS/E triggers switching from the
->D/D HS-DSCH/E-DCH or
HS-DSCH/DCH to the
DCH/DCH. If this

Recom
Name Range Value d
Value
after traffic triggers
switching from the
HS-DSCH/E-DCH or
HS-DSCH/DCH to the
DCH/DCH, only when the
dToHsDelayThr timer
expires, the DCH/DCH can
be switched to the
HS-DSCH/E-DCH or
HS-DSCH/DCH.

Event 4B0
the maximum number of
Counter
times (a 4B0 threshold)
ULogicalRn Threshold for
that the HS-DSCH/E-DCH
c.hsToDE4B HS-DSCH to 1..255 N/A 2 2
or HS-DSCH/DCH can be
0timeThr DCH,Used for
switched to the DCH/DCH,
CS+PS
used for the CS+PS
Scene
scenario.
4.1.3 The Parameter Related to the Controlling Strategy for the RB

Reconfiguration Method
Table 4-3 Parameters List (The Parameter Related to the Controlling Strategy for the
RB Reconfiguration Method)
Recom
Name Range Value d
Value
ULogicalR This parameter is used to 0: RB

0: RB 0: RB
nc.r6MulR Online-alread control online-already Setup
N/A Setup Setup
abRcfgMet y Service service reconfiguration Method
Method Method
h Reconfigurati method for UE of R6 and 1: RB

Recom
Name Range Value d
Value
on Method for after R6 when multi-RAB. Reconfig
UE of Release For the scene that it needs uration
6 and after to reconfigure the already Method
Release 6 online service at the same
When time during the setup of
Multi-RAB new service, if the
parameter is set to "0" , it
means it takes RB Setup
method, and then both the
online-already service
reconfiguration and new
service built by the RADIO
BEARER SETUP
message in one step. If the
parameter is set to "1", it
means it takes RB
reconfiguration method, it
first performs the
online-already service
reconfiguration by RADIO
BEARER
RECONFIGURATION
message, and then
performs new service built
by the RADIO BEARER
SETUP message.

4.1.4 Add Controlling Switch of Transition PS to 0/0kbps for Concurrent

service
Table 4-4 Parameters List (Add Controlling Switch of Transition PS to 0/0kbps for
Concurrent service)
Recom
Name Range Value d
Value

whether the PS traffic rate
can be degraded to 0/0
kbps if there is no PS
traffic. If this switch is
enabled, and the uplink
and downlink traffic of a
PS I/B service is 0 in case
Switch of
of concurrent CS and PS
ULogicalR Transition to
services or concurrent PS 0: Off
nc.noData 0/0kbps When N/A 0: Off 0: Off
services, the PS traffic rate 1: On
Ps00Swch PS Service
is decreased to 0/0 kbps.
Has No Data
Otherwise, the PS traffic
rate is decreased to the
DRBC minimum rate. If a
link exists at the DRNC
side, the PS traffic rate can
be decreased to 0/0 kbps
only when the DRNC also
supports PS 0/0.

the event 4B counter
Event 4B threshold for CELL_DCH
Counter to PCH shared by uplink
Threshold for and downlink. For the UE
UDrbc.dTo
CELL_DCH to in CELL_DCH state, if the 1..65535 N/A 3 3
PchThd
PCH Shared measured RLC buffer
by Uplink and payload of the uplink and
Downlink downlink is zero, and the
triggering times of the
event 4B reaches this

Recom
Name Range Value d
Value
threshold, UE will be
transferred from
CELL_DCH to PCH.
0:Not
Support
This parameter indicates PS(0 1: 0:Not
UIurLink.rn Whether the adjacent RNC feature kbps /0 Support Support
cFeatSwitc Support PS switch,0 means not kbps) N/A PS(0 PS(0
hBIT18 (0kbps/0kbps) support PS(0 kbps /0 kbps) 1:Support kbps /0 kbps /0
and 1 means support. PS(0 kbps) kbps)
kbps /0
kbps)
4.1.5 The Handling Strategy for CS+PS Concurrent Services in the Poor
Coverage
Table 4-5 Parameters List (The Handling Strategy for CS+PS Concurrent Services in
the Poor Coverage)
Recom
Name Range Value d
Value

Switch for
whether the PS traffic rate
Whether
is forcibly decreased to 0/0
Forcing the
ULogicalR kbps and kept unchanged
PS Service to 0: Off
nc.csPsBa in case of concurrent CS N/A 0: Off 1: On
0/0Kbps 1: On
dCovSwch and PS services if the
When UE is in
corresponding UE is
Bad Coverage
located in a weak
Area for
coverage area.
CS+PS Scene
UCelInfoF Bad Coverage This parameter indicates

dB -14 -14
DD.csPsba P-CPICH the P-CPICH Ec/No (-24..0)d

Recom
Name Range Value d
Value
dCovEcN0 Ec/No threshold that is used to B, step
Threshold determine whether a UE is 0.5dB
Used for in a weak coverage area in
CS+PS Scene case of concurrent CS and
PS services. The system
determines that a UE is in
a weak coverage area if
the best cell's P-CPICH
Ec/No reported by the UE
is smaller than or equal to
this threshold and the best
cell's P-CPICH RSCP
reported by the UE is
smaller than or equal to
csPsBadCovRscp. If a PS
service is initiated after a
CS service is already
established and carried on
a DCH, and the weak
coverage conditions are
met, the PS service is
established on the DCH
0/0 kbps. If a CS service is
initiated and needs to be
carried on a DCH after a
PS service is already
established, and the weak
met, the existing PS
service is forcibly
transferred to the DCH 0/0
kbps. In case of concurrent
CS and PS services,
increasing the PS traffic
rate is not allowed if the
UE is in a weak coverage
area.

Recom
Name Range Value d
Value

the P-CPICH RSCP
threshold that is used to
determine whether a UE is
in a weak coverage area in
case of concurrent CS and
PS services. The system
determines that a UE is in
a weak coverage area if
the best cell's P-CPICH
RSCP reported by the UE
is smaller than or equal to
this threshold and the best
cell's P-CPICH Ec/No
reported by the UE is
smaller than or equal to
Bad Coverage
csPsbadCovEcN. If a PS
P-CPICH
UCelInfoF service is initiated after a (-120..-25
RSCP
DD.csPsba CS service is already )dBm, dBm -95Bm -95Bm
Threshold
dCovRscp established and carried on step
Used for
a DCH, and the weak 1dBm
CS+PS Scene
met, the PS service is
established on the DCH
0/0 kbps. If a CS service is
initiated and needs to be
carried on a DCH after a
PS service is already
established, and the weak
met, the existing PS
service is forcibly
transferred to the DCH 0/0
kbps. In case of concurrent
CS and PS services,
increasing the PS traffic
rate is not allowed if the

Recom
Name Range Value d
Value
UE is in a weak coverage
area.
4.1.6 The Strategy of Prohibiting PS Service to be carried on

HS-DSCH/E-DCH for Concurrent CS+PS
Table 4-6 Parameters List (The Strategy of Prohibiting PS Service to be carried on

HS-DSCH/E-DCH for Concurrent CS+PS)
Recom
Name Range Value d
Value
whether the
Switch of
HS-DSCH/E-DCH is
Prohibiting PS
prohibited for the PS in a PS +
Service Carried
CS simultaneous service. If it
on 0: Off
is set On, a UE supporting N/A 0: Off 1: On
HS-DSCH/E-D 1: On
HS/E is prohibited to use
CH for
ULogicalRn HS-DSCH/E-DCH for the PS
Concurrent
c.csPlusPsH setup or reconfiguration in a
CS+PS
SEProhSwc PS + CS simultaneous
h service.
The Uplink
DCH Rate of
PS
the uplink DCH Rate of PS 32, 64,
Reconfigured
service reconfigured to 128, 144, kbps 16 8
to
HS-DSCH/DCH,used for 256, 384)
ULogicalRn HS-DSCH/DC
CS+PS scene. kbps
c.csPsSceH H,Used for
SDUlDchR CS+PS Scene

4.1.7 The Handling Strategy for the PS Service Rate Upgrading for
Concurrent CS+PS with the PS Service on Low Rate DCH
Table 4-7 Parameters List (The Handling Strategy for the PS Service Rate Upgrading
for Concurrent CS+PS with the PS Service on Low Rate DCH)
Recom
Name Range Value d
Value
The This parameter is used to
Controlling control whether the PS
Switch of the service can be transited to
UExtCelInfo Rate HS or rate upgraded on
0: Off
FDD.csPsR Upgrading of DCH based on the traffic N/A 0: Off 1: On
1: On
ateCtrlSwi the PS measurment 4A event in
Service, Used case of concurrent CS and
for CS+PS PS services with the PS on
Scene DCH/DCH low rate.
This parameter is the low
rate threshold of the PS
The Low Rate service, used for CS+PS
(0, 8, 16,
Threshold of scene. When the CS+PS
ULogicalRn 32, 64,
the PS and the PS service is on
c.csPsLowR 128, 144, kbps 0kbps 8kbps
Service, Used DCH/DCH, if the UL/DL
ateThresh 256, 384)
for CS+PS DCH rate of the PS service
kbps
Scene is not larger than this
threshold, the PS is
regarded as low rate.
This parameter indicates (8, 16,
the reporting threshold of 32, 64,
event 4A and 4B for traffic 128, 256,
Traffic Volume volume measurement on 512,
Threshold of DCH used for the CS+PS 1024, 2K,
UDchEvUeT
Event 4A/4B scene and the PS service 3K, 4K, [2k, 64] [2k, 8]
rv.rptThresC Bytes
for DCH is in low rate. If the traffic 6K, 8K, Bytes Bytes
sPs
(CS+PS volume becomes larger 12K, 16K,
Scene) than the threshold of event 24K, 32K,
4A, a report of 4A event 48K ,
will be triggered; and if the 64K, 96K,
traffic volume becomes 128K,

Recom
Name Range Value d
Value
smaller than the threshold 192K,
of event 4B, a report of 4B 256K,
event will be triggered. 384K,
MAX_UE_TRV_MEAS_EV 512K,
ENT is the maximum 768K)
number of UE traffic Bytes
volume measurement
event, which equals to 2.
the reporting threshold of (8, 16,
event 4A and 4B for traffic 32, 64,
volume measurement on 128, 256,
DCH used for the CS+PS 512,
scene and the PS service 1024, 2K,
is in low rate. If the traffic 3K, 4K,
Traffic Volume volume becomes larger 6K, 8K,
Threshold of than the threshold of event 12K, 16K,
UDchEvUp [2k, [2k,
Event 4A/4B 4A, a report of 4A event 24K, 32K,
Trv.rptThre Bytes 256] 256]
for DCH will be triggered; and if the 48K ,
sCsPs Bytes Bytes
(CS+PS traffic volume becomes 64K, 96K,
Scene) smaller than the threshold 128K,
of event 4B, a report of 4B 192K,
event will be triggered. 256K,
MAX_UE_TRV_MEAS_EV 384K,
ENT is the maximum 512K,
number of UE traffic 768K)
volume measurement Bytes
event, which equals to 2.

4.1.8 In CS+PS Concurrent Services Scene, the Optimization for

increasing the Call Connection Rate of the CS Service
Table 4-8 Parameters List (In CS+PS Concurrent Services Scene, the
Optimization for increasing the Call Connection Rate of the CS Service)
Recom
Paramete Value Default mende
r Name Range Value d
Value
The Switch This parameter is a switch that
of Allowing determines whether to access
PS Service PS service with 0/0kbps
Access with without admission judgement
0/0kbps for concurrent CS+PS.If the
0: Off
without switch is set to "On", it is N/A 0: Off 1: On
1: On
Admission necessary to take 0/0kbps for
URncFun Judgement PS service admission;If the
ction.ps0 for switch is set to "Off", normal
0AcCsPlu Concurrent admission for PS service is
sPsSwch CS+PS taken as before.

Common State
Table 4-9 Parameters List (Voice Service Optimization for Common State)
Recom
Name Range Value d
Value
Fast Return to
whether UE with PS
UExtCelInf Cell-DCH for
connection in CELL-FACH 0:Off
oFDD.fRD CS MO Initial
status will be transferred to 1:On N/A 0:Off 1:On
chMOIniDT Direct
CELL-DCH status as soon
Swch Transfer
as possible when RNC
Switch
receiving INITIAL DIRECT

Recom
Name Range Value d
Value
TRANSFER message of
CS MO from UE.
If the switch is turned on,
RNC transfers UE to
CELL-DCH status.
If the switch is turned off,
RNC doesn't transfer UE
to CELL-DCH status.
whether UE with PS
connection in CELL-FACH
status will be transferred to
CELL-DCH status as soon
Fast Return to
as possible when RNC
UExtCelInf Cell-DCH for
receiving INITIAL DIRECT 0:Off
oFDD.fRD CS MT Initial
TRANSFER message of 1:On N/A 0:Off 1:On
chMTIniDT Direct
CS MT from UE.
Swch Transfer
If the switch is turned on,
Switch
RNC transfers UE to
CELL-DCH status.
If the switch is turned off,
RNC doesn't transfer UE
to CELL-DCH status.
whether UE move to DCH
state as soon as possible
when UE received paging
message that paging
UUtranCell cause was terminating
0:Off
FDD.fastR Fast Return Conversational Call for UE
1:On NA 0:Off 1:On
eturnDchS Dch Switch in common state.
wch If the switch is opened,
RNC move the UE to DCH
state as soon as possible.
If the switch is closed,
RNC process with old
strategy.

4.3 Multi-RAB Release
Table 4-10 Parameters List (Multi-RAB RB Release Procedure)
Recom
Name Range Value d
Value
Switch of
Judging This parameter indicates
URncInfo.r Successful whether judging successful
0: Off
bRelByRlc RB Release RB Release by RLC ACK N/A 0: Off 1: On
1: On
AckSw by RLC ACK of downlink "Radio Bearer
of Downlink Release" message or not.
Message

the switch of releasing the
PS service when the CS
service is released for the
concurrent CS and PS
service.
If this switch is on for the
URncFunct Global service, when the RNC
0: Off
ion.gresPa Reserved releases the CS service if N/A 0: Off 1: On
1: On
ra59 Parameter 56 4B or 4B0 for the PS
service has been received,
the PS service is released.
If this switch is off, for the
service, when the RNC
releases the CS service
the PS service is not
released.

5 Related Counters and Alarms
5.1 Related Counters
Table 5-1 Counter List
Counter ID Name
Number of intra frequency Transport Channel Changing
C310414096
attempt, HS-DSCH to DCH
C310414097
attempt, DCH to HS-DSCH
C310414104
attempt, E-DCH to DCH
C310414105
attempt, DCH to E-DCH
300249 Ratio of CS Call Drop
300571 Traffic of HSDPA
300142 Call Setup Success rate(CS Video telephone)
300143 Call Setup Success rate(CS SPEECH)
300144 Call Setup Success rate(CS AMR)
300145 Call Setup Success rate(CS WBAMR)
Number of inter frequency Transport Channel successful
C310416913
Changing attempt, DCH to PCH
5.2 Related Alarms
None

6 Engineering Guide
6.1 Application Scenario
This feature supports the channel allocation policy for PS services in CS+PS multi-RAB
scenarios and the channel transition policy for PS services based on the traffic volume in
CS+PS multi-RAB scenarios.
The channel allocation policy for the PS service in CS+PS multi-RAB is that when the
CS+PS multi-RAB occurs, the PS service is established on the DCH/DCH and uses a
lower rate to improve the CS service experience.
The channel transition policy for the PS service based on traffic volume in CS+PS
multi-RAB reduces the risk of call drop due to frequent reconfigurations by decreasing
the transition between DCH and HS-DSCH. The PS service is switched from HS-DSCH
to DCH if it has no data. It helps avoid the risk of call drop due to the HS-SDCH serving
cell changes.
Both the two policies sacrifice the throughput of the PS service although the CS service
experience is improved.
When CS+PS concurrent services or multi-PS concurrent services are ongoing, the
switch is used to control whether the PS service is transited to 0/0 kpbs when it has no
data. When the switch is set to “On”, it is allowed to be transited to 0/0 kbps when it has
no value, the PS service experience gets worse, but more resources can be saved for
other services, and the service access success rate is improved. If the switch is set to
“Off”, the PS service can only be transited to the DRBC minimum rate when it has no
data; the PS service experience is good, but more resources are consumed, and the
service access rate is affected.
If the DRBC function for CS+PS services is enabled when the UE is in a bad coverage
area for the CS+I/B class PS concurrent services, the PS service is transited to 0/0
kbps and the rate increase is limited, the PS service experience gets worse. However,

the CS service experience is guaranteed with priority, and more resources are saved for
other services, thus the access rate is improved. If the switch is set to “Off”, for CS+PS
concurrent services, when the UE is in a bad coverage area, the PS service may have
some rate, the PS service experience is good, but more resources are consumed, thus
both the service access rate and the CS service experience are influenced.
The strategy of prohibiting PS service to be carried on HS-DSCH/E-DCH for concurrent

CS+PS can limit the usage of HS/E+CS, which helps to decrease the call drop rate of CS
service caused by the usage of E-DCH. And the DCH rate for CS+PS multi-RAB when
the UE is in CELL_FACH status is no longer the DRBC minimum rate, which can improve
the user rate experience of the service carried on the DCH in CS+PS multi-RAB.
The purpose for introducing the strategy of controlling handling strategy for the PS
service rate upgrading for concurrent CS+PS with the PS service on low rate DCH is to
satisfy the requirement to differentiate the data volume of the PS service when the PS is
on DCH/DCH for the concurrent CS+PS. For the small data volume requirement of the
PS service, limit the rate upgrading, so as to avoid the influence to the CS voice; but for
the large data volume requirement, the PS service can be transited normally to HS/E or
HS/D or rate upgraded on D/D, so that the PS service user experience will not be
influenced in the scene such as accompanying the tele-conference.
In practical applications, to improve the CS service experience, or the operators must

solve problems related to CS service quality, including increasing the call setup success
rate and decreasing the dropped-call rate, or there are complain from the customer. In
such cases, it is suggested to enable the following policies:
 channel allocation policy for the PS service in CS+PS multi-RAB
 channel transition policy for the PS service based on traffic volume in CS+PS
multi-RAB
 controlling switch of transiting the PS service to 0/0 kbps for concurrent services
 DRBC function for CS+PS services when the UE is in a bad coverage area.
 The strategy of prohibiting PS service to be carried on HS-DSCH/E-DCH for

concurrent CS+PS

This function is for the UE in the CELL_PCH/URA_PCH and CELL_FACH state having
received the CS domain call, the RNC identifies it in advance, and starts the operation of
transitioning the UE from CELL_PCH/URA_PCH/CELL_FACH state to CELL_DCH
state as early as possible, and establishes the CELL_DCH channel to execute the
process of establishing the CS service, so as to decrease the time of the call process and
increase the success rate, to improve the user experience.
In bad coverage area, during the process of RB release, RNC may not receive the
response from the UE which causes call drop. At this time, the RB release
accomplishment is judged by the ACK of the user plane to that the UE has received the
RB release message, so as to reduce the call drop caused by the timeout of the air
interface message, so that the service call drop rate of multi-RAB can be improved.
6.2 Feature Activation Procedure
This procedure describes how to locate the parameters related to this feature in the GUI.
The parameter values on the screenshots in the procedure are for reference only. Refer
to Chapter 4 for the recommended values of the related parameters.
6.2.1.1 PS channel Allocation for CS+PS scene
In the configuration resource tree window, open the [Modify Area->Managed

Element->UMTS Logical Function Configuration->PLMN Relating Configuration->Logic
RNC Configuration] interface and set the parameter “Switch of PS service Channel
Allocation for Concurrent CS+PS”, “Switch of Whether to transfer from HS-DSCH to DCH
for R5 UE's "PS Setup before CS" Concurrent Service”, “Switch of the PS Service
Channel allocation, Used for UE in the CELL_FACH/PCH State Triggering CS Call”, as
shown in below.

Figure 6-1 Parameters configuration interface 1


Element->UMTS Logical Function Configuration->Extended Info of RNC] interface and
set the parameter “High Speed Signalling Switch for the UE from Common State to
CELL_DCH state Triggered by CS call” as shown in Figure 6-4

Element->UMTS Logical Function Configuration->UTRAN Cell->Extended Info of
UTRAN Cell] interface and set the parameter “Maximum Bit Rate allowed for Signalling in
Cell” as shown in Figure 6-5

6.2.1.2 PS channel transition based on Traffic Volume for CS+PS Scene
In the configuration resource tree window, open the [Modify Area->Managed Element->
UMTS Logical Function Configuration->Extended Info of RNC] interface and set the
parameter “Switch for Whether the PS DRBC based on Traffic Volume is Prohibited for
CS+PS Scene”, “Valid Time Threshold for PS DRBC based on Traffic Volume is
Prohibited for CS+PS Scene”, as shown in Figure 6-6.

UMTS Logical Function Configuration] interface and set the parameter “Delay Time
Threshold of D/D->HS/D or HS/E after HS/D or HS/E ->D/D” as shown in Figure 6-7
UMTS Logical Function Configuration->Logic RNC Configuration] interface and set the
parameter “Switch of HS-DSCH/E-DCH or HS-DSCH/DCH to DCH/DCH,Used for
CS+PS Scene”, “The Uplink DCH Rate of PS Reconfigured to DCH/DCH,Used for
CS+PS Scene”, “The downlink DCH Rate of PS Reconfigured to DCH/DCH,Used for
CS+PS Scene”,”Switch of D/D->HS/D or HS/E after HS/D or HS/E ->D/D”, “Event 4B0
Counter Threshold for HS-DSCH to DCH,Used for CS+PS Scene” as shown in Figure
6-8

6.2.1.3 RB Reconfiguration controlling strategy
UMTS Logical Function Configuration] interface and set the parameter “Online-already
Service Reconfiguration Method for UE of Release 6 and after Release 6 When
Multi-RAB”, as shown in below.

6.2.1.4 Add Controlling Switch of Transition PS to 0/0kbps for Concurrent service
UMTS Logical Function Configuration] interface and set the parameter “Switch of
Transition to 0/0kbps When PS Service Has No Data”, as shown in below.
UMTS Logical Function Configuration->Global Information Configuration->Dynamic

Radio Bearer Control Information profile->Dynamic Radio Bearer Control Information]

interface and set the parameter “Event 4B Counter Threshold for CELL_DCH to PCH
Shared by Uplink and Downlink”, as shown in Figure 6-11.
UMTS Logical Function Configuration->Link Configuration->Iur Link] interface and set
the parameter “Whether Support PS(0Kbps/0Kbps)”, as shown in Figure 6-12.

6.2.1.5 The Handling Strategy for CS+PS Concurrent Services in the Poor
Coverage
UMTS Logical Function Configuration-> PLMN Relating Configuration Logic RNC
Configuration] interface and set the parameter “Switch for Whether Forcing the PS
Service to 0/0Kbps When UE is in Bad Coverage Area for CS+PS Scene”, as shown in
below.

UMTS Logical Function Configuration-> UTRAN Cell-> Extended Info of UTRAN cell]
interface and set the parameter “Bad Coverage P-CPICH Ec/No Threshold Used for
CS+PS Scene(dB)” and “Bad Coverage P-CPICH RSCP Threshold Used for CS+PS
Scene(dBm)” , as shown in Figure 6-14.

6.2.1.6 The Strategy of Prohibiting PS Service to be carried on HS-DSCH/E-DCH

for Concurrent CS+PS
UMTS Logical Function Configuration-> PLMN Relating Configuration -> Logic RNC
Configuration] interface and set the parameter “Switch of Prohibiting PS Service Carried
on HS-DSCH/E-DCH for Concurrent CS+PS” and “The Uplink DCH Rate of PS
Reconfigured to HS-DSCH/DCH,Used for CS+PS Scene(kbps)” as shown in Figure
6-15.
6.2.1.7 The Handling Strategy for the PS Service Rate Upgrading for Concurrent
CS+PS with the PS Service on Low Rate DCH
UMTS Logical Function Configuration-> UTRAN Cell -> Extended Information 2 of
UTRAN Cell] interface and set the parameter “The Controlling Switch of the Rate
Upgrading of the PS Service, Used for CS+PS Scene” as shown in below Figure 6-16.

UMTS Logical Function Configuration-> PLMN Relating Configuraton->Logic RNC
Configuration] interface and set the parameter “The Low Rate Threshold of the PS
Service, Used for CS+PS Scene” as shown in below Figure 6-17.

UMTS Logical Function Configuration-> Service Configuration-> Measurement
Configuration->Traffic Volume Measurement Profile->UE Traffic Volume Event
Measurement Configuration for DCH] interface and set the parameter “Traffic Volume
Threshold of Event 4A/4B for DCH (CS+PS Scene)(bytes)” as shown in below Figure
6-18.

UMTS Logical Function Configuration-> Service Configuration-> Measurement
Configuration->Traffic Volume Measurement Profile->UP Traffic Volume Event
Measurement Configuration for DCH] interface and set the parameter “Traffic Volume
Threshold of Event 4A/4B for DCH (CS+PS Scene)(bytes)” as shown in below Figure
6-19.

6.2.1.8 The Optimization for Increasing the Call Connection in CS+PS Concurrent
Service
UMTS Logical Function Configuration] interface and set the parameter “The Switch of
Allowing PS Service Access with 0/0kbps without Admission Judgment for Concurrent
CS+PS” as shown in Figure 6-20.

UMTS Logical Function Configuration-> UTRAN Cell -> Extended Information 2 of
UTRAN Cell] interface and set the parameter “Fast Return to Cell-DCH for CS MO Initial
Direct Transfer Switch” and “Fast Return to Cell-DCH for CS MT Initial Direct Transfer
Switch” as shown in Figure 6-21.

UMTS Logical Function Configuration-> UTRAN Cell] interface and set the parameter
“Fast Return Dch Switch” as shown in Figure 6-22

UMTS Logical Function Configuration-> Extended Info of RNC] interface and set the
parameter “Switch of Judging Successful RB Release by RLC ACK of Downlink
Message”, as shown in Figure 6-23.
6.3 Feature Validation Procedure

Test Item Service Optimization for Multi-RAB
 The WCDMA system is ready.

 Cell1 supports HSUPA, HSDPA and DCH.
Prerequisit  UE1 and UE2 camp on cell1 in Idle mode.
e  The voice service optimization for multi-RAB is enabled.
 UE1 supports HSPA and subscribes to interactive or background
services, MBR = UL5bps/DL8Mbps.
1. UE1 activates a PS service in cell1 and starts FTP downloading.

2. UE2 makes an AMR 12.2k voice call to UE1 in Cell1.
Steps
3. Release the CS service, and keep downloading.
4. Release the PS service.

Test Item Service Optimization for Multi-RAB
1. In step 1, the PS service is established on HSPA successfully and

the throughput of FTP downloading is steady.
2. In step 2, the PS service falls back to DCH/DCH to the minimum bit
Expected rate of DRBC. UE1 does not exceed the threshold and does not
Result change to HSPA.
3. In step 3, UE will be changed to HSPA due to traffic.
4. The voice call is established successfully and the voice quality is
good. There is no obvious delay.
6.4 Feature Deactivation Procedure

Managed Object.Logic Default Value Deactivation
GUI Name
Name Value
Switch of PS service
ULogicalRnc.
Channel Allocation for 0:Off 0:Off
dchUeCsPsSwch
Concurrent CS+PS
UUtranCellFDD.fastRetu
Fast Return Dch Switch 0: Off 0: Off
rnDchSwch
6.5 Impact on the Network
1. Impact on the performance of the devices
None
2. Impact on the network KPIs
Advantages of this feature:
The channel allocation policy for the PS service in CS+PS multi-RAB is that when the
CS+PS multi-RAB occurs, the PS service is established on the DCH/DCH and uses a

lower rate to improve the CS service experience; in other words, to increase the success
rate of CS service establishment and decrease the dropped-call rate of CS services.
The channel transition policy for the PS service based on traffic volume in CS+PS
multi-RAB reduces the risk of call drop due to frequent reconfigurations by decreasing
the transition between DCH and HS-DSCH. The PS service is switched from HS-DSCH
to DCH if it has no data. It helps avoid the risk of call drop due to the HS-SDCH serving
cell changes, in other words, it helps reduce the dropped-call rate of CS services.
data. When the switch is set to “On”, it is allowed to be transited to 0/0kbps when it has
no value, more resources can be saved for other services, and the service access
success rate is improved.
area for the CS+I/B class PS concurrent services, the PS service is transited to 0/0 kbps
and the rate increase is limited, the CS service experience is guaranteed with priority,
and more resources are saved for other services, thus the access rate is improved.
The strategy of prohibiting PS service to be carried on HS-DSCH/E-DCH for concurrent

CS+PS can limit the usage of HS/E+CS, which helps to decrease the call drop rate of CS
service caused by the usage of E-DCH. And the DCH rate for CS+PS multi-RAB when
the UE is in CELL_FACH status is no longer the DRBC minimum rate, which can improve
the user rate experience of the service carried on the DCH in CS+PS multi-RAB.
Disadvantages of this feature:
The two policies both sacrifice the throughput of the PS service (namely, the PS service
experience) to improve the CS service experience.
data. If the switch is set to “On”, the PS service is allowed to be transited to 0/0 kbps
when it has no data, and the PS service experience is worsened.

area for the CS+I/B class PS concurrent services, the PS service is transited to 0/0
kbps and the rate increase is limited, and the PS service experience gets worse.
If the function of prohibiting PS service to be carried on HS-DSCH/E-DCH for concurrent

CS+PS is turned on, because the E-DCH cannot be used for the CS+ PS concurrent
services, the user experience of the PS service for the concurrent CS+PS in CELL_DCH
state will be worsen.
None
This function is designed for the UE in the CELL_PCH/URA_PCH and

CELL_FACH state having received the CS domain call, the RNC identifies it in
advance, and starts the operation of transitioning the UE from
CELL_PCH/URA_PCH/CELL_FACH state to CELL_DCH state as early as
possible, and establishes the CELL_DCH channel to execute the process of
establishing the CS service, so as to decrease the time of the call process and
increase the success rate, to improve the user experience.
None
None

For the users in bad coverage area, the service call drop rate of multi-RAB can be
improved obviously after introducing this feature.
None
6.6 The Test Data
ZTE has the following detailed conclusions on the commercial network that enables the
voice service optimization for multi-RAB feature. Because different operators have
different strategies, the following network KPI figures are only for reference:
6.6.1 Test Result
Verify the rate adjustment according to traffic volume of the multi-RAB in an RNC under
certain operator. After modifying corresponding parameters, the CS call drop rate
decreased obviously which is calculated from the original data of OMMR, the number of
HSPA serving cell changing released by the RNC for the circuit domain, the number of
RAB establishment, RAB release and call reestablishment all decreased, the number of
dynamic channel control released by the RNC for the circuit domain increased, but in
general, the call drop number decreased.

The ratio of successful RRC connection establishment is basically stable.

The ratio of successful CS RAB establishment increased a bit.
The ratio of successful PS RAB establishment is basically normal.

The average RTWP decreased a bit, which is related to the decrease of the traffic
volume.
The average TCP utilization ratio decreased a bit.

The average non-HSDPA TCP decreased.
6.6.2 Commercial Conclusion
From the verify result of the field, after this feature is turned on, the CS call drop rate
decreased obviously, and other KPIs had no obvious deterioration, so it is suggested to
be turned on.

7 Abbreviation
Abbreviation Full Name
CS Circuit Switched
DCH Dedicated Channel
DRBC Dynamic Radio Bearer Control
E-DCH Enhanced Dedicated Transport Channel
FACH Forward Access Channel
HSDPA High Speed Downlink Packet Access
HS-DSCH High Speed Downlink Shared Channel
HSPA High Speed Packet Access
PCH Paging Channel
PS Packet Switched
RAN Radio Access Network
UE User Equipment
UMTS Universal Mobile Telecommunication System
8 Reference Document
[1]ZXWR RNC (V3.15.10.20) Radio Network Controller Radio Parameter Reference
[2]ZXWR RNC (V3.15.10.20) Radio Network Controller Performance Counter Reference
[3]ZXUR 9000 UMTS (V4.15.10.20) Radio Network Controller Radio Parameter

Reference
[4]ZXUR 9000 UMTS (V4.15.10.20) Radio Network Controller Performance Counter

Reference
[5]ZTE UMTS Dynamic Radio Bearer Control Feature Guide
[6]ZTE UMTS HSDPA Introduction Feature Guide
[7]ZTE UMTS HSUPA Introduction Feature Guide

ZTE UMTS UR15 Voice Service Optimization For Multi-RAB Feature Guide - V1.1

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ZTE UMTS UR15 Voice Service Optimization For Multi-RAB Feature Guide - V1.1

Hochgeladen von

Copyright:

Verfügbare Formate

Voice service Optimization

Voice Service Optimization for Multi-RAB

Compared with UR14:

Add "In CS+PS Concurrent Services

© 2016 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary 1

3 Technical Description ..................................................................................... 12

ZTE Confidential Proprietary 2

3.3.2 In CS+PS Concurrent Services Scene, the Optimization for Releasing CS

5 Related Counters and Alarms ........................................................................ 50

6 Engineering Guide .......................................................................................... 51

ZTE Confidential Proprietary 3

6.6.1 Test Result......................................................................................................... 74

ZTE Confidential Proprietary 4

Figure 6-1 Parameters configuration interface 1 ................................................................54

ZTE Confidential Proprietary 5

Table 2-1 License Control List ...........................................................................................10

ZTE Confidential Proprietary 6

Node B version: [ZXSDRV4.15.10]

2.1 Feature Introduction

2.1.1 ZWF21-05-026 Service Optimization for Multi-RAB

ZTE Confidential Proprietary 7

example, Keep-Alive message transmission), or during PS service, the voice service,

Besides, the following processing is brought in to handle the multi-RAB performance

ZTE Confidential Proprietary 8

And the following improvement is introduced: if the PS service of multi-RAB is carried on

2.1.2 ZWF21-05-029 Voice Service Optimization for Common State

This function is designed for the UE in the CELL_PCH/URA_PCH and CELL_FACH

ZTE Confidential Proprietary 9

2.1.3 Multi-RAB Release

2.2 License Control

2.2.1 ZWF21-05-026 Service Optimization for Multi-RAB

This feature is controlled by license, which should be granted by OMCR before it is

Table 2-1 License Control List

Voice service Voice service

ZTE Confidential Proprietary 10

2.2.2 ZWF21-05-029 Voice Service Optimization for Common State

This feature is controlled by license, which should be granted by OMCR before it is

Table 2-2 License Control List

2.2.3 Multi-RAB RB Release Procedure

This feature is not controlled by license.

2.3 Correlation with Other Features

2.3.1 ZWF21-05-026 Service Optimization for Multi-RAB

2. Mutually Exclusive Features

ZWF21-04-004 Dynamic Radio Bearer Control

ZWF23-04-004 Dynamic Channel Type Transfer for HSDPA Service

ZWF25-04-005 Dynamic Channel Type Transfer for HSUPA Service

ZTE Confidential Proprietary 11

2.3.2 ZWF21-05-029 Voice Service Optimization for Common State

2. Mutually Exclusive Features

ZWF21-04-004 Dynamic Radio Bearer Control

2.3.3 Multi-RAB Release

2. Mutually Exclusive Features

3.1 ZWF21-05-026 Voice Service Optimization for

ZTE Confidential Proprietary 12

The optimization for multi-RAB includes the following two functions:

 The channel allocation policy for the PS service in CS+PS multi-RAB

3.1.1 Channel Allocation Policy for the PS Service in CS+PS Multi-RAB

The CS+PS scenarios include two cases:

 A UE is in CELL_DCH status before the CS+PS services are established.

 A UE is in common status before the CS+PS services are established.

This function is controlled by the parameter ULogicalRnc.dchUeCsPsSwch. Supposing

1. For UEs of R6 or later: