32 0 2MB
Voice service Optimization for Multi-RAB Feature Guide
Voice Service Optimization for Multi-RAB
Voice Service Optimization for Multi-RAB Version
Date
Author
Notes
Reviewer
Compared with UR13: 1.
The modification introduced by the PS
service can be falled back to PS0/0 when the UE is in the CELL-DCH state: 1) Modify csPsSceDchRate in the document to "the DCH rate of PS reconfigured to DCH/DCH used for CS+PS scene" or the two parameters of ULogicalRnc.csPsSceUlDchRate and ULogicalRnc.csPsSceDlDchRate for the uplink and downlink respectively; 2) Modify the DRBC minimum rate in "3.1.1.1 Channel Allocation Policy for the PS Service in CS+PS Multi-RAB when a UE is in CELL_DCH Status" to "the DCH rate of PS reconfigured to V1.0
2015/8/18
Zhang
Ke Yazhu, Wu
DCH/DCH used for CS+PS scene".
Haiyan
He
3) Delete method 1 in "3.1.1.2 Channel Allocation Policy for the PS Service in CS+PS Multi-RAB when a UE is in CELL_FACH Status", i.e. it is only controlled by FchPchUeCsPsSwch in this state. 4) Introduce the uplink DCH Rate of PS service reconfigured to HS-DSCH/DCH,used for CS+PS scene (csPsSceHSDUlDchR) to "3.4 The Strategy of Prohibiting PS Service to be carried on HS-DSCH/E-DCH for Concurrent CS+PS". 2. Supplement “ZWF21-05-029 Voice Service Optimization for PCH/FACH State” and related parameters. 3. Supplement
ZTE Confidential Proprietary
the modification
1
Voice Service Optimization for Multi-RAB
Version
Date
Author
Notes
Reviewer
introduced by the state transition due to reduced traffic volume triggered by event 4B/4B0 of either direction to “Channel Transition Policy for the PS Service Based on the Traffic Volume in CS+PS Multi-RAB” 4. When 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} is supplemented to "3.1.2.1 Channel Transition of HS/E or HS/D->D/D Based on the Traffic Volume". 5. In "3.1.1.3 The Determination Strategy of the Signaling Rate for CS+PS Multi-RAB when a UE is in Common Status", when UCelInfoFDD.cellSigMaxBR takes the value of "6.8 kbps", the SRB uses 3.4kbps. 6. Add "4.1.7 The Controlling Handling Strategy for the PS Service Rate Upgrading for Concurrent CS+PS with the PS Service on Low Rate DCH" and the related parameters. 7. Modify the condition of”3.1.6
Handling
Policy for CS+PS Concurrent Services in Poor Coverage Areas” as if RSCP or Ec/N0 satisfies the condition of poor coverage then it is in the poor coverage area. 9. Modify the GUI name of UExtCelInfoFDD.csPsRateCtrlSwi, ULogicalRnc.csPsLowRateThresh in chapter. Only the English version needs to be modified. 10. Modify the content of 2.1 Feature Introduction-> 2.1.1 ZWF21-05-026 Service Optimization for Multi-RAB to the same as that in the market function
ZTE Confidential Proprietary
2
Voice Service Optimization for Multi-RAB
Version
Date
Author
Notes
Reviewer
description. 11. updated section 6.2~6.4 12. Modify the start time of timer in “3.1.2.1 Channel Transition of HS/E or HS/D->D/D Based on the Traffic Volume” as the time when the CS+PS concurrent services occurs immediately. 13. Add “The Test Data”
V1.10
2015/11/25
V1.20
2016/3/25
Zhang Haiyan
Modified parameter MO info
Zhang
Modify based on field test result
Haiyan
Add C310417161
© 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
3
Voice Service Optimization for Multi-RAB
TABLE OF CONTENTS 1
Feature Attribute ............................................................................................... 8
2 2.1 2.1.1 2.1.2 2.2 2.2.1 2.2.2 2.3
Overview ............................................................................................................ 8 Feature Introduction ............................................................................................. 8 ZWF21-05-026 Service Optimization for Multi-RAB ............................................. 8 ZWF21-05-029 Voice Service Optimization for Common State .......................... 10 License Control .................................................................................................. 11 ZWF21-05-026 Service Optimization for Multi-RAB ........................................... 11 ZWF21-05-029 Voice Service Optimization for Common State .......................... 11 Correlation with Other Features ......................................................................... 11
3 3.1 3.1.1 3.1.2
Technical Description ..................................................................................... 12 ZWF21-05-026 Voice Service Optimization for Multi-RAB.................................. 12 Channel Allocation Policy for the PS Service in CS+PS Multi-RAB .................... 12 Channel Transition Policy for the PS Service Based on the Traffic Volume in CS+PS Multi-RAB .............................................................................................. 17 Controlling Policy for the RB Reconfiguration Method ........................................ 21 Traffic Measurement .......................................................................................... 22 Adding the Controlling Switch of Transiting PS to 0/0 kbps for Concurrent Services ............................................................................................................. 22 Handling Policy for CS+PS Concurrent Services in Poor Coverage Areas ......... 23 The Strategy of Prohibiting PS Service to be Carried on HS-DSCH/E-DCH for Concurrent CS+PS ............................................................................................ 26 The Controlling Handling Strategy for the PS Service Rate Upgrading for Concurrent CS+PS with the PS Service on Low Rate DCH ............................... 28 ZWF21-05-029 Voice Service Optimization for Common State .......................... 29 Handling of Accompanying CS Domain Service for the UE in PCH State .......... 30 Handling of Accompanying CS Domain Service for the UE in CELL_FACH State 30
3.1.3 3.1.4 3.1.5 3.1.6 3.1.7 3.1.8 3.2 3.2.1 3.2.2
4 4.1 4.1.1 4.1.2 4.1.3 4.1.4
Parameters....................................................................................................... 31 ZWF21-05-026 Service Optimization for Multi-RAB ........................................... 31 The Parameter Related to the Channel Allocation Strategy for the PS Service in CS+PS Multi-RAB .............................................................................................. 31 The Parameter Related to the Channel Transition Strategy for the PS Service Based on the Traffic Volume in CS+PS Multi-RAB ............................................. 34 The Parameter Related to the Controlling Strategy for the RB Reconfiguration Method ............................................................................................................... 37 Add Controlling Switch of Transition PS to 0/0kbps for Concurrent service ........ 38
ZTE Confidential Proprietary
4
Voice Service Optimization for Multi-RAB
4.1.5 4.1.6
4.2
The Handling Strategy for CS+PS Concurrent Services in the Poor Coverage .. 40 The Strategy of Prohibiting PS Service to be carried on HS-DSCH/E-DCH for Concurrent CS+PS ............................................................................................ 42 The Handling Strategy for the PS Service Rate Upgrading for Concurrent CS+PS with the PS Service on Low Rate DCH .................................................. 43 ZWF21-05-029 Voice Service Optimization for Common State .......................... 45
5 5.1 5.2
Related Counters and Alarms ........................................................................ 47 Related Counters ............................................................................................... 47 Related Alarms .................................................................................................. 47
6 6.1 6.1.1 6.1.2 6.2 6.2.1 6.2.2 6.3 6.4 6.5 6.5.1 6.5.2 6.6 6.6.1 6.6.2
Engineering Guide .......................................................................................... 48 Application Scenario .......................................................................................... 48 ZWF21-05-026 Service Optimization for Multi-RAB ........................................... 48 ZWF21-05-029 Voice Service Optimization for Common State .......................... 50 Feature Activation Procedure ............................................................................. 50 ZWF21-05-026 Service Optimization for Multi-RAB ........................................... 50 ZWF21-05-029 Voice Service Optimization for Common State .......................... 65 Feature Validation Procedure............................................................................. 67 Feature Deactivation Procedure......................................................................... 67 Impact on the Network ....................................................................................... 68 ZWF21-05-026 Service Optimization for Multi-RAB ........................................... 68 ZWF21-05-029 Voice Service Optimization for Common State .......................... 69 The Test Data .................................................................................................... 70 Test Result......................................................................................................... 70 Commercial Conclusion ..................................................................................... 74
7
Abbreviation .................................................................................................... 74
8
Reference Document....................................................................................... 75
4.1.7
ZTE Confidential Proprietary
5
Voice Service Optimization for Multi-RAB
FIGURES Figure 6-1 Parameters configuration interface 1 ................................................................51 Figure 6-2
Parameters configuration interface 2 ...............................................................51
Figure 6-3 Parameters configuration interface 3 ................................................................52 Figure 6-4 Parameters configuration interface 4 ................................................................52 Figure 6-5 Parameters configuration interface 5 ................................................................53 Figure 6-6 Parameters configuration interface 6 ................................................................53 Figure 6-7 Parameters configuration interface 7 ................................................................54 Figure 6-8 Parameters configuration interface 8 ................................................................55 Figure 6-9 Parameters configuration interface 9 ................................................................56 Figure 6-10 Parameters configuration interface 10 ............................................................57 Figure 6-11 Parameters configuration interface 11 ............................................................57 Figure 6-12 Parameters configuration interface 12 ............................................................58 Figure 6-13 Parameters configuration interface 13 ............................................................59 Figure 6-14 Parameters configuration interface 14 ............................................................60 Figure 6-15 Parameters configuration interface 15 ............................................................60 Figure 6-16 Parameters configuration interface 16 ............................................................61 Figure 6-17 Parameters configuration interface 17 ............................................................62 Figure 6-18 Parameters configuration interface 18 ............................................................63 Figure 6-19 Parameters configuration interface 19 ............................................................64 Figure 6-20 Parameters configuration interface 20 ............................................................65 Figure 6-21 Parameters configuration interface 21 ............................................................66 Figure 6-22 Parameters configuration interface 22 ............................................................66
TABLES Table 2-1 License Control List ...........................................................................................11
ZTE Confidential Proprietary
6
Voice Service Optimization for Multi-RAB
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) ...................................................................................31 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) ......................................34 Table 4-3 Parameters List (The Parameter Related to the Controlling Strategy for the RB Reconfiguration Method) ......................................................................................................37 Table 4-4 Parameters List (Add Controlling Switch of Transition PS to 0/0kbps for Concurrent service) ..............................................................................................................38 Table 4-5 Parameters List (The Handling Strategy for CS+PS Concurrent Services in the Poor Coverage) ....................................................................................................................40 Table 4-6 Parameters List (The Strategy of Prohibiting PS Service to be carried on HS-DSCH/E-DCH for Concurrent CS+PS) ...........................................................................42 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).................................................43 Table 4-8
Parameters List (Voice Service Optimization for Common State) .................45
Table 5-1 Counter List .......................................................................................................47
ZTE Confidential Proprietary
7
Voice Service Optimization for Multi-RAB
1
Feature Attribute RNC version: [ZXWR RNC V3.14.10.14/ZXUR 9000 V4.14.10.14] Node B version: [ZXSDRV4.14.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
ZTE Confidential Proprietary
8
Voice Service Optimization for Multi-RAB
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
ZTE Confidential Proprietary
9
Voice Service Optimization for Multi-RAB
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 (refer to “3.2 ZWF21-05-029 Voice Service Optimization for Common State”).
ZTE Confidential Proprietary
10
Voice Service Optimization for Multi-RAB
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 turned on.
Table 2-1
License Control List
Feature ID
Feature Name
Voice ZWF21-05-026
service
Optimization
for
Multi-RAB
2.2.2
License
Configured
Control Item
NE
Unit
Voice service Optimization
RNC
RNC
for Multi-RAB
ZWF21-05-029 Voice Service Optimization for Common State This feature is controlled by license, which should be granted by OMCR before it is turned on.
Table 2-2
License Control List
Feature ID
Feature Name
Voice ZWF21-05-029
Service
Optimization Common State
2.3
for
License
Configured
Control Item
NE
Unit
Voice Service Optimization for Common
CELL
CELL
State
Correlation with Other Features 1.
Required Features None
ZTE Confidential Proprietary
11
Voice Service Optimization for Multi-RAB
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
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.
ZTE Confidential Proprietary
12
Voice Service Optimization for Multi-RAB
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 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. 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:
ZTE Confidential Proprietary
13
Voice Service Optimization for Multi-RAB
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. 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 DCH_Rate. 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 DCH_Rate, the PS service is reconfigured to the DCH channel with DCH_Rate. If the switch ULogicalRnc.csPlu sPsR5UeSwch is set to “Off”, the fallback of the PS service rate is not needed. For the DCH_Rate refer to ‘1. For UEs of R6 or later’. 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.dchUeCsPsSwch takes 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.
ZTE Confidential Proprietary
14
Voice Service Optimization for Multi-RAB
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.
ZTE Confidential Proprietary
15
Voice Service Optimization for Multi-RAB
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.
ZTE Confidential Proprietary
16
Voice Service Optimization for Multi-RAB
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.
ZTE Confidential Proprietary
17
Voice Service Optimization for Multi-RAB
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}.
ZTE Confidential Proprietary
18
Voice Service Optimization for Multi-RAB
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 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. 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. 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.
ZTE Confidential Proprietary
19
Voice Service Optimization for Multi-RAB
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 service is being established, 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.
ZTE Confidential Proprietary
20
Voice Service Optimization for Multi-RAB
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.
ZTE Confidential Proprietary
21
Voice Service Optimization for Multi-RAB
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.
ZTE Confidential Proprietary
22
Voice Service Optimization for Multi-RAB
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.
ZTE Confidential Proprietary
23
Voice Service Optimization for Multi-RAB
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.
ZTE Confidential Proprietary
24
Voice Service Optimization for Multi-RAB
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 removed, and the current DRBC operations according to the policy based on the 4A event for CS+PS concurrent services can be executed for the PS service.
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.
ZTE Confidential Proprietary
25
Voice Service Optimization for Multi-RAB
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 having
HSDPA capability: 1.
The strategy of the concurrent services establishment for the UE having HSDPA capability 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”.
ZTE Confidential Proprietary
26
Voice Service Optimization for Multi-RAB
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. The GBR for the streaming service is the GBR in the RAB assignment; the GBR for the Interactive and background service is 0 kbp.; The MaxBR is the maximum bit rate handled by the RNC. 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. 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.
ZTE Confidential Proprietary
27
Voice Service Optimization for Multi-RAB
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 and ULogicalRnc.csPlusPsHSEProhSwch is “Off”, 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:
ZTE Confidential Proprietary
28
Voice Service Optimization for Multi-RAB
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.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.
ZTE Confidential Proprietary
29
Voice Service Optimization for Multi-RAB
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”;
ZTE Confidential Proprietary
30
Voice Service Optimization for Multi-RAB
ii.
The
RNC
receives
the
paging
message
with
the
cause
as
terminatingConversationalCall. 2.
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.
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 Name
GUI Name
Parameter Description
Value Range
Unit
Default mende Value
d Value
ZTE Confidential Proprietary
31
Voice Service Optimization for Multi-RAB
Recom Parameter Name
GUI Name
Parameter Description
Value Range
Unit
Default mende Value
d Value
This parameter is used to control PS service channel allocation for concurrent CS+PS
for UE in
CELL_DCH sState. If the parameter is on, for CS Switch of PS service first and then PS
ULogicalRn c.dchUeCsP sSwch
service
service triggered scenario,
Channel
allocate DCH/DCH for the
Allocation for PS service; For PS service 0: Off Concurrent
first and then CS service
1: On
N/A
0: Off
1: On
N/A
0: Off
0: Off
N/A
0: Off
1: On
CS+PS for UE triggered scene, and if PS in CELL_DCH is on HS, perform the HS State
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
Switch of Whether to transfer from ULogicalRn c.csPlusPsR 5UeSwch
HS-DSCH to DCH for R5 UE's "PS Setup before CS" Concurrent Service
whether to transfer from HSDSCH to DCH for R5 UE's "PS Setup before CS" when dchUeCsPsSwch is on.
0:off
For the PS setup before CS scene, if both of
1:on
CsPlusPsR5UeSwch and dchUeCsPsSwch are on, PS will downgrade from HSDSCH to DCH, otherwise not.
Switch of the This parameter indicates 0: Off
ULogicalRn PS Service
the switch of the PS
c.fchPchUe Channel
service channel allocation 1: On
CsPsSwch allocation,Use when a UE in
ZTE Confidential Proprietary
32
Voice Service Optimization for Multi-RAB
Recom Parameter Name
GUI Name
Parameter Description
Value Range
Unit
Default mende Value
d Value
d for UE in the CELL_FACH/CELL_PCH/ CELL_FACH/ URA_PCH state initiates PCH State
the CS service. If this
Triggering CS parameter is set to "1: On", Call
when a UE in CELL_FACH/CELL_PCH/ URA_PCH state initiates the CS service, the PS service is reconfigured to the DCH, and the uplink and downlink rate are determined separately by csPsSceULDchRate and csPsSceDLDchRate. parameter
when
the
UE
indicates is
in
the
CELL_FACH or CELL_PCH
URncInfo.hi
state, if it initiates or receives
ghSignalSw ch
This
N/A
a CS call, whether the SRB
High Speed
on DCH can use the high
Signalling
speed signaling before the CS 0:
Switch
RB setup is completed.
0: Off
1: On
Off; 1: On 0: 27.2 kbps 1: 13.6
UCelInfoFD D.cellSigMa xBR
Maximum Bit Rate allowed for Signalling in Cell
kbps This parameter indicates
2: 6.8
the maximum signaling bit kbps rate allowed in a cell.
3: 3.4
0: N/A
27.2 kbps
1: 13.6 kbps
kbps 4:CELL_ FACH Forced
ZTE Confidential Proprietary
33
Voice Service Optimization for Multi-RAB
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 Parameter Name
GUI Name
Parameter Description
Value
Unit
Range
Default mende Value
d Value
Switch for Whether the PS DRBC
This parameter indicates
URncInfo.ps based on
whether PS DRBC based
DrbcProhSw Traffic
on traffic volume is
ch
Volume is
forbidden for the CS+PS
0: Off 1: On
N/A
0: Off
0: Off
90
90
10
10
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
mer
Volume is
1..65535 s
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 URncFuncti on.dToHsDe layThr
HS-DSCH/E-DCH or
Threshold of HS-DSCH/DCH to D/D->HS/D or DCH/DCH. After the timer (0..65535 HS/E after
expires, switching from
HS/D or HS/E DCH/DCH to ->D/D
)s, step
s
1s
HS-DSCH/E-DCH or HS-DSCH/DCH is allowed. This parameter indicates the timer duration.
ZTE Confidential Proprietary
34
Voice Service Optimization for Multi-RAB
Recom Parameter Name
GUI Name
Parameter Description
Value Range
Unit
Default mende Value
d Value
This parameter indicates Switch of HS-DSCH/EULogicalRn c.csPsSceH sToDSwch
DCH or HS-DSCH/DC H to DCH/DCH,Us ed for CS+PS Scene
the switch of switching an HS-DSCH/E-DCH or HS-DSCH/DCH to a DCH/DCH, used for the CS+PS scenario. For the CS+PS scenario, if this
0: Off 1: On
N/A
0: Off
1: On
parameter is set to "1: On", when there is no data, the PS service is switched from the HS to the DCH.
The Uplink DCH Rate of PS Reconfigured to ULogicalRn DCH/DCH,Us c.csPsSceUl ed for CS+PS DchRate
This parameter indicates
(0, 8, 16,
the uplink rate after the PS 32, 64, service is reallocated to the 128, 144, kbps DCH, used for CS+PS
256, 384)
scenario.
kbps
16
16
8
8
Scene The downlink DCH Rate of PS Reconfigured to
ULogicalRn DCH/DCH,Us c.csPsSceDl ed for CS+PS DchRate
This parameter indicates
(0, 8, 16,
the downlink rate after the 32, 64, PS service is reallocated to 128, 144, kbps the DCH, used for CS+PS 256, 384) scenario.
kbps
Scene This parameter indicates whether to disallow the Switch of
DCH/DCH to be switched
ULogicalRn D/D->HS/D or to the HS-DSCH/E-DCH or c.dToHsDel HS/E after aySwch
HS-DSCH/DCH after traffic
HS/D or HS/E triggers switching from the ->D/D
0: Off 1: On
N/A
0: Off
1: On
HS-DSCH/E-DCH or HS-DSCH/DCH to the DCH/DCH. If this
ZTE Confidential Proprietary
35
Voice Service Optimization for Multi-RAB
Recom Parameter Name
GUI Name
Parameter Description
Value Range
Unit
Default mende Value
d Value
parameter is set to "1: On", 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 Counter ULogicalRn Threshold for c.hsToDE4B HS-DSCH to 0timeThr
DCH,Used for CS+PS Scene
This parameter indicates the maximum number of times (a 4B0 threshold) that the HS-DSCH/E-DCH or HS-DSCH/DCH can be
1..255
N/A
2
2
NA
1: True 1: True
switched to the DCH/DCH, used for the CS+PS scenario. This parameter indicates whether the state transition to CELL_FACH/CELL_PCH/
Whether the URA_PCH/IDLE and the State
state transition from
Transition
HS-DSCH/E-DCH or
Due to
HS-DSCH/DCH to DL
Reduced
DCH/UL DCH in a PS + CS 0: False
Traffic Volume simultaneous service due 1: True is Triggered
to the reduced traffic
by Event 4B
volume can be triggered by
of Either
event 4B/4B0 of either
Direction
direction. If it is set to "0: False", the mentioned state transitions can only be triggered by the event 4B/4B0 from the
ZTE Confidential Proprietary
36
Voice Service Optimization for Multi-RAB
Recom Parameter Name
GUI Name
Parameter Description
Value Range
Unit
Default mende Value
d Value
user plane in the downlink when all conditions such as traffic volume in downlink and uplink are met. If it is set to "1: True", the mentioned state transitions can be triggered by the event 4B/4B0 of either direction when all conditions such as traffic volume in downlink and uplink are met.
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 Parameter Name
GUI Name
Parameter Description
Value Range
Unit
Default mende Value
d Value
This parameter is used to control online-already Online-alread service reconfiguration 0: RB y Service method for UE of R6 and Setup ULogicalR Reconfigurati after R6 when multi-RAB. Method nc.r6MulR on Method for For the scene that it needs 1: RB N/A abRcfgMet UE of Release to reconfigure the already Reconfig h 6 and after online service at the same uration Release 6 time during the setup of Method When new service, if the Multi-RAB
0: RB
0: RB
Setup Setup Method Method
parameter is set to "0" , it means it takes RB Setup
ZTE Confidential Proprietary
37
Voice Service Optimization for Multi-RAB
Recom Parameter Name
GUI Name
Parameter Description
Value Range
Unit
Default mende Value
d Value
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 Parameter Name
GUI Name
Parameter Description
Value Range
Unit
Default mende Value
d Value
This parameter indicates Switch of whether the PS traffic rate ULogicalR Transition to can be degraded to 0/0 0: Off nc.noData 0/0kbps When kbps if there is no PS 1: On Ps00Swch PS Service traffic. If this switch is Has No Data enabled, and the uplink
N/A
0: Off
0: Off
and downlink traffic of a
ZTE Confidential Proprietary
38
Voice Service Optimization for Multi-RAB
Recom Parameter Name
GUI Name
Parameter Description
Value Range
Unit
Default mende Value
d Value
PS I/B service is 0 in case of concurrent CS and PS services or concurrent PS services, the PS traffic rate is decreased to 0/0 kbps. 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. This parameter indicates the event 4B counter threshold for CELL_DCH Event 4B Counter UDrbc.dTo PchThd
Threshold for CELL_DCH to PCH Shared by Uplink and Downlink
to PCH shared by uplink and downlink. For the UE in CELL_DCH state, if the measured RLC buffer payload of the uplink and
1..65535 N/A
3
3
1:
0:Not
downlink is zero, and the triggering times of the event 4B reaches this threshold, UE will be transferred from CELL_DCH to PCH. 0:Not Support This parameter indicates
PS(0
UIurLink.rn Whether
the adjacent RNC feature kbps /0
cFeatSwitc Support PS
switch,0 means not
hBIT18
kbps)
(0kbps/0kbps) support PS(0 kbps /0 kbps) 1:Support and 1 means support.
PS(0
Support Support N/A
PS(0
PS(0
kbps /0 kbps /0 kbps)
kbps)
kbps /0 kbps)
ZTE Confidential Proprietary
39
Voice Service Optimization for Multi-RAB
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 Parameter Name
GUI Name
Parameter Description
Value Range
Unit
Default mende Value
d Value
Switch for Whether ULogicalR nc.csPsBa dCovSwch
Forcing the PS Service to 0/0Kbps When UE is in Bad Coverage Area for CS+PS Scene
This parameter indicates whether the PS traffic rate is forcibly decreased to 0/0 kbps and kept unchanged in case of concurrent CS and PS services if the
0: Off 1: On
N/A
0: Off
1: On
dB
-14
-14
corresponding UE is located in a weak coverage area. This parameter indicates the P-CPICH Ec/No 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
Bad Coverage UCelInfoF DD.csPsba dCovEcN0
P-CPICH Ec/No Threshold Used for CS+PS Scene
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
(-24..0)d B, step 0.5dB
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
ZTE Confidential Proprietary
40
Voice Service Optimization for Multi-RAB
Recom Parameter Name
GUI Name
Parameter Description
Value Range
Unit
Default mende Value
d Value
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 coverage conditions are 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. This parameter indicates 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 Bad Coverage UCelInfoF DD.csPsba dCovRscp
P-CPICH RSCP Threshold Used for CS+PS Scene
PS services. The system determines that a UE is in a weak coverage area if
(-120..-25
the best cell's P-CPICH
)dBm,
dBm
-95Bm -95Bm
RSCP reported by the UE step is smaller than or equal to 1dBm this threshold and the best cell's P-CPICH Ec/No reported by the UE is smaller than or equal to csPsbadCovEcN. If a PS service is initiated after a CS service is already
ZTE Confidential Proprietary
41
Voice Service Optimization for Multi-RAB
Recom Parameter Name
GUI Name
Parameter Description
Value Range
Unit
Default mende Value
d Value
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 coverage conditions are 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.
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 Parameter Name
GUI Name
Parameter Description
Value Range
Unit
Default mende Value
d Value
Switch of
This parameter indicates
ULogicalRn Prohibiting PS whether the c.csPlusPsH Service Carried HS-DSCH/E-DCH is SEProhSwc on h
ZTE Confidential Proprietary
0: Off 1: On
N/A
0: Off
1: On
prohibited for the PS in a PS +
HS-DSCH/E-D CS simultaneous service. If it
42
Voice Service Optimization for Multi-RAB
Recom Parameter Name
GUI Name
Parameter Description
Value
Unit
Range
Default mende Value
d Value
CH for
is set On, a UE supporting
Concurrent
HS/E is prohibited to use
CS+PS
HS-DSCH/E-DCH for the PS setup or reconfiguration in a PS + CS simultaneous service.
The Uplink DCH Rate of PS Reconfigured to ULogicalRn HS-DSCH/DC c.csPsSceH H,Used for
This parameter indicates
(0, 8, 16,
the uplink DCH Rate of PS 32,
64,
service reconfigured to
128, 144, kbps
HS-DSCH/DCH,used for
256, 384)
CS+PS scene.
kbps
16
8
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 Parameter Name
GUI Name
Parameter Description
Value Range
Unit
Default mende 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
FDD.csPsR Upgrading ateCtrlSwi
the
of DCH based on the traffic PS measurment 4A event in
0: Off
N/A
1: On
0: Off
1: On
Service, Used case of concurrent CS and for
CS+PS PS services with the PS on
Scene
DCH/DCH low rate.
ULogicalRn The Low Rate This parameter is the low (0, 8, 16, c.csPsLowR Threshold
ZTE Confidential Proprietary
of rate threshold of the PS 32,
64,
kbps
0kbps 8kbps
43
Voice Service Optimization for Multi-RAB
Recom Parameter Name
GUI Name
Parameter Description
Value
Unit
Range
Default mende Value
d Value
ateThresh
the
PS service, used for CS+PS 128, 144,
Service, Used scene. When the CS+PS 256, 384) for
CS+PS and the PS service is on kbps
Scene
DCH/DCH, if the UL/DL DCH rate of the PS service is not larger than this threshold,
the
PS
is
regarded as low rate. This parameter indicates 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, Traffic Volume volume UDchEvUeT rv.rptThresC sPs
Threshold Event for
becomes
larger 6K,
4K, 8K,
of than the threshold of event 12K, 16K,
4A/4B 4A, a report of 4A event 24K, 32K, DCH will be triggered; and if the 48K
[2k, 64] [2k,
8]
Bytes
Bytes
volume measurement on 512,
[2k,
[2k,
DCH used for the CS+PS 1024, 2K, Bytes
256]
256]
scene and the PS service 3K,
4K,
Bytes
Bytes
is in low rate. If the traffic 6K,
8K,
(CS+PS
traffic
volume
Scene)
smaller than the threshold 128K,
,
Bytes
becomes 64K, 96K,
of event 4B, a report of 4B 192K, event will be triggered.
256K,
MAX_UE_TRV_MEAS_EV 384K, ENT
is
number volume
the of
maximum 512K, UE
traffic 768K)
measurement Bytes
event, which equals to 2.
Traffic Volume UDchEvUp Trv.rptThre sCsPs
Threshold Event for (CS+PS Scene)
of
4A/4B DCH
This parameter indicates (8,
16,
the reporting threshold of 32,
64,
event 4A and 4B for traffic 128, 256,
volume
becomes
larger 12K, 16K,
than the threshold of event 24K, 32K,
ZTE Confidential Proprietary
44
Voice Service Optimization for Multi-RAB
Recom Parameter Name
GUI Name
Parameter Description
Value
Unit
Range
Default mende Value
d Value
4A, a report of 4A event 48K
,
will be triggered; and if the 64K, 96K, traffic
volume
becomes 128K,
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
number volume
the of
maximum 768K) UE
traffic Bytes
measurement
event, which equals to 2.
4.2
ZWF21-05-029
Voice Service Optimization for
Common State Table 4-8
Parameters List (Voice Service Optimization for Common State) Recom
Parameter Name
GUI Name
Parameter Description
Value Range
Unit
Default mende Value
d Value
This parameter indicates whether Fast Return to UExtCelInf Cell-DCH
for
oFDD.fRD CS MO Initial chMOIniDT Direct Swch
Transfer Switch
UE
with
PS
connection in CELL-FACH status will be transferred to CELL-DCH status as soon 0:Off as possible when RNC 1:On
N/A
0:Off
1:On
receiving INITIAL DIRECT TRANSFER message of CS MO from UE. If the switch is turned on, RNC
ZTE Confidential Proprietary
transfers
UE
to
45
Voice Service Optimization for Multi-RAB
Recom Parameter Name
GUI Name
Parameter Description
Value Range
Unit
Default mende Value
d Value
CELL-DCH status. If the switch is turned off, RNC doesn't transfer UE to CELL-DCH status. This parameter indicates whether
UE
with
PS
connection in CELL-FACH status will be transferred to Fast Return to UExtCelInf Cell-DCH
for
oFDD.fRD CS MT Initial chMTIniDT Direct Swch
Transfer Switch
CELL-DCH status as soon as possible when RNC receiving INITIAL DIRECT 0:Off TRANSFER message of 1:On
N/A
0:Off
1:On
CS MT 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. This parameter indicates whether UE move to DCH state as soon as possible when UE received paging message UUtranCell FDD.fastR Fast
cause
that
was
paging
terminating
Return Conversational Call for UE
0:Off 1:On
eturnDchS Dch Switch
in common state.
wch
If the switch is opened,
NA
0:Off 1:On
RNC move the UE to DCH state as soon as possible. If the switch is closed, RNC
process
with
old
strategy.
ZTE Confidential Proprietary
46
Voice Service Optimization for Multi-RAB
5
Related Counters and Alarms
5.1
Related Counters Table 5-1
Counter List Counter ID
C310414096 C310414097 C310414104 C310414105
Number of intra frequency Transport Channel Changing attempt, HS-DSCH to DCH Number of intra frequency Transport Channel Changing attempt, DCH to HS-DSCH Number of intra frequency Transport Channel Changing attempt, E-DCH to DCH Number of intra frequency Transport Channel Changing attempt, DCH to E-DCH
300249
Ratio of
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)
C310417161
5.2
Name
CS Call Drop
Number of attempted change from CELL_FACH to CELL_DCH, cause by receiving Paging message
Related Alarms None
ZTE Confidential Proprietary
47
Voice Service Optimization for Multi-RAB
6
Engineering Guide
6.1
Application Scenario
6.1.1
ZWF21-05-026 Service Optimization for Multi-RAB 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,
ZTE Confidential Proprietary
48
Voice Service Optimization for Multi-RAB
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
ZTE Confidential Proprietary
49
Voice Service Optimization for Multi-RAB
6.1.2
ZWF21-05-029 Voice Service Optimization for Common State 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.
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
ZWF21-05-026 Service Optimization for Multi-RAB
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
ZTE Confidential Proprietary
50
Voice Service Optimization for Multi-RAB
Figure 6-1
Figure 6-2
ZTE Confidential Proprietary
Parameters configuration interface 1
Parameters configuration interface 2
51
Voice Service Optimization for Multi-RAB
Figure 6-3
Parameters configuration interface 3
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 “High Speed Signalling Switch for the UE from Common State to CELL_DCH state Triggered by CS call” as shown in Figure 6-4
Figure 6-4
Parameters configuration interface 4
In the configuration resource tree window, open the [Modify Area->Managed 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
ZTE Confidential Proprietary
52
Voice Service Optimization for Multi-RAB
Figure 6-5
6.2.1.2
Parameters configuration interface 5
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.
Figure 6-6
ZTE Confidential Proprietary
Parameters configuration interface 6
53
Voice Service Optimization for Multi-RAB
In the configuration resource tree window, open the [Modify Area->Managed Element-> 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
Figure 6-7
Parameters configuration interface 7
In the configuration resource tree window, open the [Modify Area->Managed Element-> 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
ZTE Confidential Proprietary
54
Voice Service Optimization for Multi-RAB
Figure 6-8
Parameters configuration interface 8
In the configuration resource tree window, open the [Modify Area->Managed Element-> UMTS Logical Function Configuration->Global Information Configuration->Dynamic Radio Bearer Control Information profile->Dynamic Radio Bearer Control Information] interface and set the parameter “Whether the State Transition Due to Reduced Traffic Volume is Triggered by Event 4B of Either Direction” as shown in Figure 6-9
ZTE Confidential Proprietary
55
Voice Service Optimization for Multi-RAB
Figure 6-9
6.2.1.3
Parameters configuration interface 9
RB Reconfiguration controlling strategy In the configuration resource tree window, open the [Modify Area->Managed Element-> 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
ZTE Confidential Proprietary
56
Voice Service Optimization for Multi-RAB
Figure 6-10
6.2.1.4
Parameters configuration interface 10
Add Controlling Switch of Transition PS to 0/0kbps for Concurrent service In the configuration resource tree window, open the [Modify Area->Managed Element-> 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
Figure 6-11
Parameters configuration interface 11
In the configuration resource tree window, open the [Modify Area->Managed Element-> UMTS Logical Function Configuration->Global Information Configuration->Dynamic
ZTE Confidential Proprietary
57
Voice Service Optimization for Multi-RAB
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-12
Figure 6-12
Parameters configuration interface 12
In the configuration resource tree window, open the [Modify Area->Managed Element-> UMTS Logical Function Configuration->Link Configuration->Iur Link] interface and set the parameter “Whether Support PS(0Kbps/0Kbps)”, as shown in Figure 6-13
ZTE Confidential Proprietary
58
Voice Service Optimization for Multi-RAB
Figure 6-13
6.2.1.5
Parameters configuration interface 13
The Handling Strategy for CS+PS Concurrent Services in the Poor Coverage 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 for Whether Forcing the PS Service to 0/0Kbps When UE is in Bad Coverage Area for CS+PS Scene”, as shown in below
ZTE Confidential Proprietary
59
Voice Service Optimization for Multi-RAB
Figure 6-14
Parameters configuration interface 14
In the configuration resource tree window, open the [Modify Area->Managed Element-> 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-15
Figure 6-15
ZTE Confidential Proprietary
Parameters configuration interface 15
60
Voice Service Optimization for Multi-RAB
6.2.1.6
The Strategy of Prohibiting PS Service to be carried on HS-DSCH/E-DCH for Concurrent CS+PS 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 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-16
Figure 6-16
6.2.1.7
Parameters configuration interface 16
The Handling Strategy for the PS Service Rate Upgrading for Concurrent CS+PS with the PS Service on Low Rate DCH In the configuration resource tree window, open the [Modify Area->Managed Element-> 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-17
ZTE Confidential Proprietary
61
Voice Service Optimization for Multi-RAB
Figure 6-17
Parameters configuration interface 17
In the configuration resource tree window, open the [Modify Area->Managed Element-> 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-18
ZTE Confidential Proprietary
62
Voice Service Optimization for Multi-RAB
Figure 6-18
Parameters configuration interface 18
In the configuration resource tree window, open the [Modify Area->Managed Element-> UMTS
Logical
Function
Configuration->Traffic
Configuration->
Volume
Service
Measurement
Configuration->
Profile->UE
Traffic
Measurement 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
ZTE Confidential Proprietary
63
Voice Service Optimization for Multi-RAB
Figure 6-19
Parameters configuration interface 19
In the configuration resource tree window, open the [Modify Area->Managed Element-> UMTS
Logical
Function
Configuration->Traffic
Configuration->
Volume
Service
Measurement
Configuration->
Profile->UP
Traffic
Measurement 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-20
ZTE Confidential Proprietary
64
Voice Service Optimization for Multi-RAB
Figure 6-20
6.2.2
Parameters configuration interface 20
ZWF21-05-029 Voice Service Optimization for Common State In the configuration resource tree window, open the [Modify Area->Managed Element-> 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 below Figure 6-21
ZTE Confidential Proprietary
65
Voice Service Optimization for Multi-RAB
Figure 6-21
Parameters configuration interface 21
In the configuration resource tree window, open the [Modify Area->Managed Element-> UMTS Logical Function Configuration-> UTRAN Cell] interface and set the parameter “Fast Return Dch Switch” as shown in below Figure 6-22
Figure 6-22
ZTE Confidential Proprietary
Parameters configuration interface 22
66
Voice Service Optimization for Multi-RAB
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.
Steps
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.
3.
Release the CS service, and keep downloading.
4.
Release the PS service.
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 Name ULogicalRnc. dchUeCsPsSwch UUtranCellFDD.fastRetu rnDchSwch
ZTE Confidential Proprietary
GUI Name
Default Value
Deactivation Value
Switch of PS service Channel Allocation for
0:Off
0:Off
0: Off
0: Off
Concurrent CS+PS Fast Return Dch Switch
67
Voice Service Optimization for Multi-RAB
6.5
Impact on the Network
6.5.1
ZWF21-05-026 Service Optimization for Multi-RAB 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. 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/0kbps when it has no value, more resources can be saved for other services, and the service access success rate is improved. 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 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
ZTE Confidential Proprietary
68
Voice Service Optimization for Multi-RAB
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. 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. 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. 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, 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.
6.5.2
ZWF21-05-029 Voice Service Optimization for Common State 1.
Impact on the performance of the devices None
2.
Impact on the network KPIs Advantages of this feature: 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
ZTE Confidential Proprietary
69
Voice Service Optimization for Multi-RAB
establishing the CS service, so as to decrease the time of the call process and increase the success rate, to improve the user experience. Disadvantages of 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.
ZTE Confidential Proprietary
70
Voice Service Optimization for Multi-RAB
The ratio of successful RRC connection establishment is basically stable.
The ratio of successful CS RAB establishment increased a bit.
ZTE Confidential Proprietary
71
Voice Service Optimization for Multi-RAB
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.
ZTE Confidential Proprietary
72
Voice Service Optimization for Multi-RAB
The average TCP utilization ratio decreased a bit.
The average non-HSDPA TCP decreased.
ZTE Confidential Proprietary
73
Voice Service Optimization for Multi-RAB
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
ZTE Confidential Proprietary
74
Voice Service Optimization for Multi-RAB
UMTS
8
Universal Mobile Telecommunication System
Reference Document [1]ZXWR RNC (V3.14.10.14) Radio Network Controller Radio Parameter Reference [2]ZXWR RNC (V3.14.10.14) Radio Network Controller Performance Counter Reference [3]ZXUR 9000 UMTS (V4.14.10.14) Radio Network Controller Radio Parameter Reference [4]ZXUR 9000 UMTS (V4.14.10.14) 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 Confidential Proprietary
75