CS Voice over HSPA WCDMA RAN
Feature Guide
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. I
CS Voice over HSPA Feature Guide
Version Date Author Approved By Remarks
V4.0 2010-06-18 Xu Chunxiao Zhao Dapeng
© 2010 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.
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. II
TABLE OF CONTENTS
1 Functional Attribute ............................................................................................1
2 Overview .............................................................................................................1 2.1 The user plane of CS Voice over HSPA .................................................................2 2.2 Control plane of CS Voice over HSPA ...................................................................3 2.3 Channel change for CS Voice over HSPA ..............................................................3
3 Technology description ......................................................................................3 3.1 The user plane of CS Voice over HSPA .................................................................3 3.1.1 PDCP ..................................................................................................................3 3.1.2 RLC ....................................................................................................................5 3.1.3 Ciphering procedures for CS over HSPA ...............................................................5 3.2 The control plane of CS Voice over HSPA .............................................................6 3.2.1 UE capability........................................................................................................6 3.2.2 The service establishment for CS Voice over HSPA ...............................................6 3.2.3 Bearer strategy of CS Voice over HSPA ................................................................7 3.2.4 The SRB Bearer of CS Voice over HSPA ...............................................................8 3.3 The channel change of CS Voice over HSPA .........................................................8 3.3.1 Channel Reconfiguration Based on Propagation Condition .....................................8 3.3.2 Handover between two cells which support CS Voice over HSPA both ....................9 3.3.3 Handover between cell which support CS Voice over HSPA and the cell which
doesn’t support. .................................................................................................9 3.3.4 The relocation crossing RNC of CS Voice over HSPA.............................................9 3.3.5 The inter-RAT handover for CS Voice over HSPA ................................................10 3.4 Power Control ....................................................................................................10 3.5 Admission Control ..............................................................................................10 3.6 Congestion Control .............................................................................................10 3.7 Overload Control ................................................................................................10
4 Parameters and configurations.........................................................................11 4.1 Parameters list ...................................................................................................11 4.2 Parameters configuration ....................................................................................11 4.2.1 Quality Measurement Switch for VoIP/ CS Voice ..................................................11 4.2.2 Switch of AMR over HSPA ..................................................................................11 4.2.3 Max CS Delay ....................................................................................................11 4.2.4 Delay Time Threshold of D/D->HS/D or HS/E after HS/D or HS/E ->D/D Triggering
by Channel Quality .............................................................................................12 4.2.5 Neighbouring RNC Feather Switch ......................................................................12
5 Counters and Alarm ..........................................................................................13 5.1 Counters list.......................................................................................................13 5.2 Alarm list ...........................................................................................................22
6 Glossary ...........................................................................................................23
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. III
FIGURES
Figure 1 Three sub-flows reassemble ...................................................................................2
Figure 2 PDCP AMR Data PDU format .................................................................................3
Figure 3 UMD RLC format....................................................................................................5
TABLES
Table 1 Compare of three voice solution ..............................................................................2
Table 2 PDCP Type............................................................................................................4
Table 3 The meanings of UMD RLC E bit.............................................................................5
Table 4 The Parameters list of CS Voice over HSPA ..........................................................11
Table 5 The counters of CS Voice over HSPA ....................................................................13
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 1
1 Functional Attribute
System version:[RNC V3.09, Node B V4.09, OMMR V3.09, OMMB V4.09]
Attribute: [Optional]
NEs involved:
UE NodeB RNC MSCS MGW SGSN GGSN HLR
√ - √ - - - - -
Note:
*-: None NE is involved.
*√: An NE is involved.
Dependency: HSDPA, HSUPA
Mutual exclusion: VoIP, R99 AMR Voice, Video Phone
Remarks: CS Voice Service over HSPA supports both of AMR-NB and AMR-WB. AMR
means both of AMR-NB and AMR-WB in this document. If we need to distinguish the AMR-NB and AMR-WB, we will pinpoint them on name.
2 Overview
3GPP set up “CS Voice Service over HSPA” work Item in RAN#37 meeting in Jul. 2007. And this WI was finished in the RAN#39 meeting after six months later.
Simply, CS Voice over HSPA is that the user plane of CS voice bears on HSPA channel (HSDPA/HSUPA), instead of R99 channel. Hence the voice service can interwork with CPC DTX/DRX to improve the cell capacity and increase the battery life. CS Voice over
HSPA will significantly increase the cell capacity by the system simulation.
CS Voice over HSPA will increase the cell capacity up to 100% than traditional R99 voice service depending on CPC DTX/DRX. The battery life during call will be longer up
to 50% than R99 voice service depending on CPC DTX/DRX too. On the other hand, the call duration of CS Voice over HSPA will be double times longer than R99 voice.
Depending on some HSPA+ feature, the call setup delay of CS Voice over HSPA will
reduce up to half than the R99 voice service. These HSPA+ features include Enhanced FACH, Enhanced RACH and SRB over HSPA, and etc.
At present, there are three voice solutions in UMTS network, traditional R99 voice, CS
Voice over HSPA and VoIP over HSPA. Now we compare the sameness and difference of these three voice solutions.
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 2
Table 1 Compare of three voice solution
- R99 voice CS Voice over HSPA VoIP over HSPA
User plane channel DCH HSPA(DPA/UPA) HSPA(DPA/UPA)
Core network CS domain CS domain PS domain
IMS No No Yes
PDCP level No Yes Yes
Sub-flow number 3 or 2 1 1
RLC entities 3 or 2 1 1
We can find the difference of these three voice solutions clearly by the table. The main
difference of VoIP over HSPA is the core network compared to the other two solutions. VoIP over HSPA is carried by PS core network and the other two solutions are carried by CS core network. And VoIP over HSPA bears on HSPA channel in radio side, not
DCH channel compared to R99 voice.
The main difference is the radio channel between CS Voice over HSPA and R99 voice. CS voice over HSPA bears on HSPA channel. And the R99 voice bears on DCH
channel. The core network is same for both of CS voice over HSPA and R99 voice.
The related technology of CS voice over HSPA will be int roduced simply in the following sections. And the detail analysis will be introduced in “technology description” chapter.
2.1 The user plane of CS Voice over HSPA
The main difference is the radio channel between CS Voice over HSPA and R99 voice.
R99 voice bears on DCH in downlink and uplink. And the RLC mode of R99 voice is TM mode. But CS Voice over HSPA bears on HS-DSCH/E-DCH in downlink and uplink.
And the RLC mode is UM mode.
There are three sub-flows in the R99 voice user plane. And every sub-flow bears on individual RLC entity. The user plane of CS Voice over HSPA doesn’t bears on RLC
level directly. The three AMR sub-flows are reassembled and bear on PDCP level firstly. Then it bears on RLC level. Hence the PDCP and RLC were modified for CS Voice over HSPA in the related specifications. It will be introduced detailed in the “technology
description” chapter.
Figure 1 Three sub-flows reassemble
Data
Sub flow A Sub flow B
Sub flow C
Pad
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 3
2.2 Control plane of CS Voice over HSPA
CS Voice over HSPA is related with UE strongly. So RAN needs to know UE capability
about CS voice over HSPA before deciding the channel type. Hence, UE needs to report its capability about CS Voice over HSPA during the call setup duration.
The call setup procedure of CS Voice over HSPA is partly different with R99 voice
because the three AMR sub-flows are reassembled and bear on PDCP level. The specification requires that service establishment and channel reconfiguration use “RADIO BEARER SETUP” RRC message for CS Voice over HSPA. RAN will decide the
channel type, for example, DCH/DCH or HS -DSCH/E-DCH for CS Voice depending on not only the UE capability, but also the UE Propagation Conditions, feature switch, license and etc.
CPC DTX/DRX will not work if some logical channel bears on DCH. So it is very important which channel the SRB bears on.
2.3 Channel change for CS Voice over HSPA
HSUPA’s uplink coverage is worse than DCH, especially for the 2ms TTI. UE activates the CS Voice over HSPA and moves in the cell. Although the cell handover doesn’t
happen, it is possible that the channel is reconfigured from HS-DSCH/E-DCH to DCH/DCH because of the Propagation Conditions.
UE activates the CS Voice over HSPA, and moves from one cell into another cell. The
cell handover will happen. Now, there are two possibilities. One is that the target cell supports CS voice over HSPA, and another is that the target cell doesn ’t support CS Voice over HSPA. The rule of cell handover is different in these two situations.
And CS Voice over HSPA is same to other service. It is possible that CS Voice over HSPA handover between inter-RAT.
3 Technology description
3.1 The user plane of CS Voice over HSPA
3.1.1 PDCP
We have simply introduced the user plane of CS Voice over HSPA in subclause 2.1. The
three or two AMR sub-flows should be reassembled and bear on PDCP level. Then the PDCP PDU bears on RLC level as the RLC SDU. And the transmission mode of RLC level should be UM mode. Hence, a new PDCP packet type is imported in TS25.323. It
is named “PDCP AMR Data PDU”. This PDCP type is only used to encapsulate the user plane of CS Voice over HSPA.
Figure 2 PDCP AMR Data PDU format
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 4
PDU type CS counter
Data
“PDU type” IE includes 3 bits.
Table 2 PDCP Type
Bit PDU Type
000 PDCP Data PDU
001 PDCP SeqNum PDU
010 PDCP AMR Data PDU
011-111 Reserved (PDUs with this encoding are invalid for this version of
the protocol)
“CS counter” IE includes 5 bits. And the value range is from 0 to 31. “CS counter” is used for processing the delay in air interface. The delay maybe comes from HARQ retranslation, transmission level, residual BLER, and etc. RNC and UE control the delay
in air interface depending on “CS counter”. For that, PDCP entity must send both of the SDU and “CS counter” to the upper layers. And the upper layers will process the delay depending on it.
Every PDCP entity is responsible to encode and decode user plane. Then the PDCP PDU bears on RLC level as the RLC SDU. When the PDCP entity at the Receiver receives the PDCP SDU from the upper layers, the PDCP entity shall:
If the length of the PDCP SDU is 0, the PDCP entity discards the PDCP PDU. If the length of the PDCP SDU is of 1 or more bits, the PDCP entity includes the CS counter in the PDCP AMR Data PDU and indicates the PDCP AMR PDU type in the PDU type field
and fills the data field of the PDCP AMR PDU type with the PDCP SDU and adds padding bits.
The value of the CS counter shall be set to the first to fi fth LSBs of the CFN at which the
packet has been received from higher layers.
The PDCP PDU is octet aligned. But the actual PDCP SDU carrying the AMR frame may not be octet aligned. The AMR classes are always encoded in the order of class A, B
and C, where the first bit of data follows immediately after the CS counter field and any padding for octet alignment is inserted at the end of the data field. We choose the 12.2kbps AMR as an example. Every AMR package is of 244 bits after reassembling the
class A and B and C. Now we need to pad 4 bits. The SDU will be of 248 bits, 31bytes. Now it is octet aligned.
For the uplink, when the PDCP entity receives the PDCP PDU from the lower layers,
and the PDCP type is PDCP AMR Data PDU, it shall:
The PDCP entity derives the PDCP SDU from the data field of the PDCP AMR Data PDU. The PDCP entity determines the bit aligned data content and Frame Type from the
PDU Data field length, as possible AMR-NB and AMR-WB payload has a unique size when being octet aligned. Then PDCP entity derives the PDCP SDU and CS counter from the received PDCP header to the upper layer.
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 5
PDCP entity was defined for PS service in earlier. PDCP entity has the head compression function in order to reduce the spending of IP/TCP/UDP/RTP head. But now PDCP can encapsulate CS AMR too, and CS Voice over HSPA has no
IP/TCP/UDP/RTP head. Hence the head compression function is unavailable for CS Voice over HSPA.
3.1.2 RLC
The RLC mode of traditional R99 voice is TM mode. And the RLC mode of CS Voice over HSPA is forced to use UM mode. The data encapsulated structure is as the following illustration:
Figure 3 UMD RLC format
Oct1
E Length Indicator
Data
PAD
Last Octet
E Length Indicator (Optional) (1)
.
.
.
E Sequence Number
(Optional)
(Optional)
The length of Sequence number is of 7 bits. And the value range is from 0 to 127. And the E bit is as following table:
Table 3 The meanings of UMD RLC E bit
Bit Description
0 The next field is a complete SDU, which is not
segmented, concatenated or padded.
1 The next field is Length Indicator and E bit
“SN_Delivery” is a new optional system parameter defined in TS25.322. This parameter is only used for UM mode RLC entity. And if SN_Delivery is configured, the UM mode
RLC entity should deliveries both of the RLC SDU and the Sequence Number to the upper layers. And when SN_Delivery parameter is configured, the transmitting RLC entity does not concatenate nor segment RLC SDUs in downlink. And the transmitting
RLC entity does not concatenate and may segment RLC SDUs in uplink.
3.1.3 Ciphering procedures for CS over HSPA
The RLC mode of CS Voice over HSPA is UM mode. And RLC mode of R99 voice is TM
mode. In order to support the fast ciphering activation, the specifications require that the RB ID must be not same with the current RB ID when cell handovers or channel reconfigures between R99 voice and CS Voice over HSPA.
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 6
If RNC activates the ciphering for user plane, RNC and UE should start the ciphering procedures immediately after the service establishment. And this procedure is excuted by RL mode RLC entity. Both of UE and RNC use the newest “START” for ciphering in
CS Voice over HSPA establishment or channel reconfiguration between DCH and HSPA.
3.2 The control plane of CS Voice over HSPA
3.2.1 UE capability
RAN needs to know whether the UE supports CS Voice over HSPA before RAN decides
the channel type, for example, DCH or HSPA. Hence, UE should report itself capability of CS Voice over HSPA to RAN in RRC connection duration. Off course, the UE capability is not the only one determinant. The CELL capability, the UE Propagation
Conditions and the license status and etc, are the determinants too.
Therefore, a new IE named “Support for CS Voice over HSPA” is adopted into “UE radio access capability “->”PDCP capability” IE as an optional IE in TS25.331. This IE is used
to indicate UE capability of CS Voice over HSPA. If “PDCP capability” IE includes this IE and the value is of “true”, the UE supports CS Voice over HSPA. Otherwise, the UE doesn’t support CS Voice over HSPA.
These following two messages are affected by this IE.
RRC CONNECTION SETUP COMPLETE
UE CAPABILITY INFORMATION
The target RNC needs to know the UE capability to decide the channel type when the UE handovers crossing RNC or handovers into UMTS from other RAT. So the SRNC or the inter-RAT need to report the UE capability to the DRNC. Therefore, “Support for CS
Voice over HSPA” IE is adopted by “UE radio access capability comp 2” IE too. This IE is used to indicate UE’ CS Voice over HSPA capability to the DRNC. These following two RRC messages are affected.
INTER RAT HANDOVER INFO WITH INTER RAT CAPABILITIE
SRNS RELOCATION INFO
3.2.2 The service establishment for CS Voice over HSPA
The specifications don’t restrict the unsymmetrical bearer in downlink and uplink in 3GPP. The unsymmetrical bearer means that the AMR voice bears on DCH in UL and HS-DSCH in DL. But the objective that the specifications set up CS Voice over Work
Item is that the AMR voice can apply the advantage of HSPA (+), for example, CPC DTX/DRX, to improve the cell capacity and save the UE battery. And it depends on that the AMR voice bears on HS-DSCH/E-DCH in both of DL and UL. Hence we believe that
the value of CS Voice over HSPA will be lost for the unsymmetrical bearer. Therefore, ZTE UTRAN will not support the unsymmetrical bearer.
RNC uses “RADIO BEARER SETUP ” RRC message to establish the CS Voice over
HSPA if UE is in idle state or CELL_FACH state and uses “CELL UPDATE CONFIRM” RRC message to establish CS Voice over HSPA if UE is in CELL/URA_PCH state.
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 7
Both of ”RADIO BEARER SETUP” and ”CELL UPDATE CONFIRM ” include ” RAB information for setup” IE. And the specifications extend this IE and add ” CS-HSPA information” IE into it. ” CS-HSPA information” includes two sub-IE, ”UL AMR rate”
and ”Max CS delay”. ”UL AMR rate” IE indicates the UL AMR voice bitrate and ”Max CS delay” is used for de-jitter. Hence RNC adopts a new parameter named ”MaxCSDelay”. This parameter defines the max voice E2E dely.
The AMR UL rate is configured by the Transport Format if the AMR voice bears on DCH channel. But there is no Transport Format concept when the AMR voice bears on HSPA. Hence the specifications extend ”RAB information for setup” and add ”UL AMR rate” IE
into it. The UE’s control plane receives this IE and transfers it to the upper layers. The upper layers control the AMR UL rate by this IE.
”UL AMR rate” IE is an enum type structure and the selectable values are of t0, t1, t2, t3,
t4, t5, t6, t7, t8. These value’s meanings depend on the value of ”NAS Synchronization indicator” parameter. If “NAS Synchronization indicator” is of AMR-NB, the “UL AMR rate” can equals t0, t1, t2, t3, t4, t5, t6, t7 which means 4.75 kbps, 5.15 kbps, 5.9 kbps,
6.7 kbps, 7.4 kbps, 7.95 kbps, 10.2 kbps, 12.2 kbps for AMR-NB. If “NAS Synchronization indicator” is of AMR-WB, the “UL AMR rate” can equals t0, t1, t2, t3, t4, t5, t6, t7, t8 which means 6.60 kbps, 8.85 kbps, 12.65 kbps, 14.25 kbps, 15.85 kbps,
18.25 kbps, 19.85 kbps, 23.05 kbps, 23.85 kbps for AMR-WB.
The default value of ”UL AMR rate” is t7 for AMR-NB and t8 for AMR-WB if it is reserved.
The AMR rate comes from the core network. The core network indicates the AMR rate
by the ”RAB ASSIGNMENT REQUEST” RANAP message. RNC gets the AMR rate and assigns to ”UL AMR rate” IE. The value of ”Max CS delay” is configured by OMC.
3.2.3 Bearer strategy of CS Voice over HSPA
3.2.3.1 The single service establishment of CS Voice over HSPA
It mainly depends on UE capability, license, feature switch, UE Propagation Conditions, and etc, whether the AMR Voice bears on HSPA when the single AMR voice service establishes. We have discussed the UE capability before
CS Voice over HSPA is an optional feature in RNC . RNC adopts a new license for it. And this license is in RNC level. RNC can support CS Voice over HSPA only when the license is on.
A new switch named ”AmrOverHspaSwch” is adopted by RNC. RNC will not support CS Voice over HSPA if ”AmrOverHspaSwch” is off even that the license is on. RNC will support CS Voice over HSPA only when both of ” AmrOverHspaSwch” and license are
on.
We also need to consider the UE Propagation Conditions whether the AMR voice should bears on HSPA even that both of ” AmrOverHspaSwch” and license are on. If the
ppropagation condition is in 1F state, RNC will select the DCH/DCH. And if the propagation condition is in 1E state, RNC will select the HS -DSCH/E-DCH.
3.2.3.2 CS Voice over HSPA interworks with other service
ZTE RAN supports the muti service interworking. And if one of the service bears on HS-DSCH/E-DCH, other service will try to bear on HS-DSCH/E-DCH too. Off course, if the
service can’t bears on HS-DSCH/E-DCH channel, it will bears on DCH/DCH.
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 8
3.2.4 The SRB Bearer of CS Voice over HSPA
The SRB bearer will strongly affect the cell capacity and the call setup efficiency for CS Voice over HSPA. CPC DTX/DRX will not work if the UL SRB is over DCH. Then the
improvement of cell capacity and the saving of battery will lost. If the DL SRB is over DCH, the DL resource of Channelization Code will consume up to 10 times than over F-DPCH. Hence the strategy of SRB bearer is very important for CS Voice over HSPA.
The specifications have confirmed that the UE which support CS Voice over HSPA must support F-DPCH and CPC.
If CS Voice over HSPA is actived and bears on HS-DSCH/E-DCH channel, the SRB will
bears on HS-DSCH/E-DCH channel.
If CS voice over HSPA is interworking with other service and some of the service bears on DCH/DCH channel, the SRB will be over 3.4kbps DCH/DCH channel.
If CS Voice over HSPA is interworking with other service and all of these service are bears on HS-DSCH/E-DCH channel, the SRB will bears on HS-DSCH/ED-CH channel.
3.3 The channel change of CS Voice over HSPA
3.3.1 Channel Reconfiguration Based on Propagation Condition
CS Voice over HSPA is actived and bears on HS-DSCH/E-DCH channel. UE moves in the cell and doesn’t handover to other cell. But it is possible that the propagation condition gets to be worse and UE report the 1F event. If it happens, RNC can
reconfigures the logical channel from HS-DSCH/E-DCH to DCH/DCH. If UE report the 1E event because UE moves, RNC can reconfigures the logical channel to HS -DSCH/E-DCH channel from DCH/DCH too.
It depends on the ” CChQSwch” switch whether RNC reconfigures the logical channel because of the propagation condition. If ”CChQSwch” is off, RNC will not reconfigure it. And if ” CChQSwch” is on, RNC will reconfigure it. ” CChQSwch” is a new parameter
imported into RNC for CS Voice over HSPA.
The Ping-Pang effect maybe happens because of UE moving. The Ping-Pang effect means the fast and Frequent channel reconfiguration because UE alternately reports the
1F and 1E event continually. RNC adopts a new parameter as a timer to control the Ping-Pang effect. Controling the Ping-Pang effect can saves the radio resource and reduces the unnecessary channel reconfiguration. This parameter is ” DtoHsDelayThr”. ”
DtoHsDelayThr” can be set on OMC. ” DtoHsDelayThr” will starts when the logical channel is reconfigured from DCH/DCH to HS -DSCH/E-DCH or from HS-DSCH/E-DCH to DCH/DCH. Before ” DtoHsDelayThr” times out, RNC will not reconfigure the logical
channel even that UE reports the 1E or 1F event again. Off course, if ” DtoHsDelayThr” has timed out, RNC will reconfigures the logical channel.
” DtoHsDelayThr” is available for normal PS service too, for example, Interactive class,
background class and streaming class. The effective rule is same as CS Voice over HSPA.
There are some other switches about propagation conditions, for example,
“IBChQSwch”, “SChQSwch”, and “CChQSwch”. If CS Voice over HSPA is interworking with other PS service and anyone of these switches is on and some service need to be
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 9
reconfigured from HS-DSCH/E-DCH to DCH/DCH because of propagation conditions, all of the interworking service should be reconfigured to DCH/DCH.
3.3.2 Handover between two cells which support CS Voice over HSPA
both
Because the specifications don’t modify the Iur protocol for CS Voice over HSPA, RNC can’t know whether the neighbouring RNC supports the CS Voice over HSPA through
the Iur signaling system. Then RNC adopts a new parameter named ”RncFeatSwitch” This parameter is used to indicate wether the neighbouring RNC support CS Voice over HSPA.
It is fully compliant to the HSDPA/HSUPA mobility procedures. Please refer < ZTE UMTS HSDPA Introduction Feature Guide V3.1.doc> and < ZTE UMTS HSUPA Introduction Feature Guide V3.1.doc>
3.3.3 Handover between cell which support CS Voice over HSPA and the cell which doesn’t support.
We will discuss the handover from the cell which support CS Voice over HSPA to the cell which doesn’t support firstly. TS25.331 requires that RNC should use “RADIO BEARER SETUP” RRC message to handover between the cells in this situation.
“RADIO BEARER SETUP” includes “RAB information for setup”->” “RAB identity” IE. If the value of “RAB identity” is not same with current value saved in UE, UE will deletes the PDCP entity, RLC entities and the Radio Bearer belonging to this RAB. Then UE will
reestablishes these entities and the Radio Bearers in the target cell by the parameters in “RADIO BEARER SETUP” RRC message.
We choose 12.2kbps AMR-NB as a example. If UE moves from the cell which support
CS Voice over HSPA to the cell which doesn’t support, RNC will sends “RADIO BEARER SETUP” message to UE and the value of RAB identity” will be not same with the current value. UE will deletes the Radio Bearer, PDCP entity and RLC entity. Then
UE will reestablish three new RLC entities and three new Radio Bearers to bear the sub-flow A, B and C of the AMR-NB.
Contrarily, UE moves from the cell which doesn’t support CS voice over HSPA to the cell
which support. The procedure is analogical, but contrary. And the logical channels in the target cell are HS-DSCH/E-DCH. The RB ID in target cell should be not same with the ID in the original cell.
3.3.4 The relocation crossing RNC of CS Voice over HSPA
There is no any modification for Iur interface in CS Voice over HSPA standard. So the SRNC can’t know whether the DRNC supports CS Voice over HSPA. Hence RNC
imports a new switch into the “RncFeatSwitch” parameter. This switch indicates whether the DRNC supports CS Voice over HSPA. This switch will not affect the soft or hard handover process in Iur interface. But it will control the relocation procedures.
If CS Voice over HSPA is active in SRNC and the DRNC doesn’t support CS voice over HSPA and there is an Iur connection between these two RNCs, the SRNC won’t active the relocation procedure. The user plane of CS Voice over HSPA will be forwarded to
SRNC through Iur interface.
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 10
If CS Voice over HSPA is active in SRNC and the DRNC doesn’t support CS voice over HSPA and there is no Iur connection between these two RNCs, CS Voice over HSPA will be fall backed to R99 AMR voice and the SRNC will active the relocation procedure.
3.3.5 The inter-RAT handover for CS Voice over HSPA
There are two scenarios in the Inter-RAT handover. One is handover into UMTS from other RAT. And another is handover into other RAT out of UMTS.
The process of handover out of UMTS is same as the R99 AMR’s process. Please refer the original process.
It is possible that the relocation RRC message takes the UE ability of CS Voice over
HSPA to the DRNC in the scenario of handover into UMTS. But the specifications don ’t describe the default configuration for CS Voice over HSPA. It is impossible for RNC to choose the radio parameters in this scenario. Hence the service will be handover into
UMTS as R99 AMR voice firstly. After it successes, RNC will reconfigure it to CS Voice over HSPA.
3.4 Power Control
Please refer <ZTE UMTS Power Control Feature Guide >
3.5 Admission Control
Please refer <ZTE UMTS Admission Control Feature Guide >
CS Voice over HSPA is a type of voice service. So its priority should be higher than Interactive/Background/Streaming. Hence, the admission control will give CS Voice over HSPA more higher priority.
3.6 Congestion Control
Please refer <ZTE UMTS Congestion Cont rol Feature Guide >
The priority of CS Voice over HSPA is higher than other service as described in subclause 3.5. So the congestion control based on service priority will give CS voice
over HSPA higher priority than Interactive/Background/Streaming service. For example, if the cell is congested and needs to drop some UEs, RNC should choose class I/B/S UEs to drop, instead of CS Voice over HSPA UE.
3.7 Overload Control
Please refer < ZTE UMTS Overload Control Feature Guide >
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 11
4 Parameters and configurations
4.1 Parameters list
Table 4 The Parameters list of CS Voice over HSPA
ID Abbreviate Parameter Name
1 CChQSwch Quality Measurement Switch for VoIP/ CS Voice
2 AmrOverHspaSwch Switch of CS voice over HSPA
3 MaxCsDelay Max CS Delay
4 DToHsDelayThr Delay Time Threshold of D/D->HS/D or HS/E after
HS/D or HS/E ->D/D Triggering by Channel Quality
5 RncFeatSwitch Neighbouring RNC Feather Switch
4.2 Parameters configuration
4.2.1 Quality Measurement Switch for VoIP/ CS Voice
OMC path
Path: View->Configuration Management->RNC NE->RNC Radio Resource Management-> Modify Advanced Parameter->Dynamic Radio Bearer Control Information-> Quality Measurement Switch for VoIP/ CS Voice
Parameters configuration
This parameter is the propagation conditions measurement switch for VoIP and CS voice over HSPA. 0 is off and 1 is on. If this switch is on, RNC will start the channel
reconfiguration when UE reports 1E or 1F events. If it is off, RNC will not start the channel reconfiguration.
4.2.2 Switch of CS voice over HSPA
OMC path
Path: View->Configuration Management->RNC NE->RNC Radio Resource
Management->Other parameters-> Switch of CS voice over HSPA
Parameters configuration
This parameter is the switch whether CS Voice can bears on HSPA. 0 is off, 1 is on. The
default value is on.
4.2.3 Max CS Delay
OMC path
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 12
Path: View->Configuration Management->RNC NE->RNC Radio Resource
Management-> Modify Advanced Parameter->Dynamic Radio Bearer Control
Information-> Max CS Delay
Parameters configuration
This parameter is the max delay of the user plane of CS Voice over HSPA. UE ’s NAS
level controls the de-jitter by this parameter. This parameter’s value range is of 20ms to
200ms. And the footstep is of 10ms. Default value is 60ms.
4.2.4 Delay Time Threshold of D/D->HS/D or HS/E after HS/D or HS/E ->D/D
Triggering by Channel Quality
OMC path
Path: View->Configuration Management->RNC NE->RNC Radio Resource
Management-> Modify Advanced Parameter->Dynamic Radio Bearer Control
Information-> Delay Time Threshold of D/D->HS/D or HS/E after HS/D or HS/E ->D/D Triggering
by Channel Quality
Parameters configuration
This parameter is the threshold for controling the Ping-Pang effect of the channel
reconfiguration. This timer will start After channel reconguration because of propagation
conditions. Before it times out, RNC will not excute the channel reconfiguration even that
UE reports 1E or 1F events. The value range of this parameter is of 0 to 65535
seconds. And the default value is of 10s.
4.2.5 Neighbouring RNC Feather Switch
OMC path
Path: View->Configuration Management->RNC NE->RNC Ground Resource
Management->Transmission Configuration->NE Information Configuration->RNC:xx -
>Adjacent RNC Office-> Rnc Config
Parameters configuration
This parameter indicates whether the neighbor RNC supports CS Voice over HSPA.
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 13
5 Counters and Alarm
5.1 Counters list
Table 5 The counters of CS Voice over HSPA
Counter No. Description
C310175759 Number of failed HSDPA RAB assignment setup for CS
domain,Conversational Class
C310175760 Number of failed HSUPA RAB assignment setup for CS domain,Conversational Class
C310175761 Number of failed HSDPA RAB assignment setup in cell for CS domain,Invalid RAB Parameters Value
C310175762 Number of failed HSDPA RAB assignment setup in cell for CS domain,failed in the Radio Interface Procedure
C310175763 Number of failed HSDPA RAB assignment setup in cell for CS domain,UE send rb setup failed
C310175764 Number of failed HSDPA RAB assignment setup in cell for CS domain,Timeout of UU rb setup.
C310175765 Number of failed HSDPA RAB assignment setup in cell for CS domain,TQUEUING Expiry
C310175766 Number of failed HSDPA RAB assignment setup in cell for CS domain,Requested Traffic Class not Available
C310175767 Number of failed HSDPA RAB assignment setup in cell for CS domain,Requested Guaranteed Bit Rate not Available
C310175768 Number of failed HSDPA RAB assignment setup in cell for CS domain,Requested Guaranteed Bit Rate for UL not Available
C310175769 Number of failed HSDPA RAB assignment setup in cell for CS
domain,No Resource Available
C310175770 Number of failed HSDPA RAB assignment setup in cell for CS domain,No Resource Available In SRNC
C310175771 Number of failed HSDPA RAB assignment setup in cell for CS domain,Downlink CE Congestion
C310175772 Number of failed HSDPA RAB assignment setup in cell for CS domain,Downlink CE Congestion
C310175773 Number of failed HSDPA RAB assignment setup in cell for CS domain,Downlink Power Resource Congestion
C310175774 Number of failed HSDPA RAB assignment setup in cell for CS domain,Other Downlink Resource Congestion
C310175775 Number of failed HSDPA RAB assignment setup in cell for CS domain,Uplink CE Congestion
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 14
C310175776 Number of failed HSDPA RAB assignment setup in cell for CS domain,Uplink Power Resource Congestion
C310175777 Number of failed HSDPA RAB assignment setup in cell for CS domain,Other Uplink Resource Congestion
C310175778 Number of failed HSDPA RAB assignment setup in cell for CS domain,HSDPA user number limit
C310175779 Number of failed HSDPA RAB assignment setup in cell for CS domain,HSDPA user number limit
C310175780 Number of failed HSDPA RAB assignment setup in cell for CS domain,No Resource Available In DRNC
C310175781 Number of failed HSDPA RAB assignment setup in cell for CS domain,Access Restricted Due to Shared Networks
C310175782 Number of failed HSDPA RAB assignment setup in cell for CS domain,Non-Standard Cause
C310175783 Number of failed HSDPA RAB assignment setup in cell for CS
domain,Due to NodeB
C310175784 Number of failed HSDPA RAB assignment setup in cell for CS domain,RL Setup or Reconfig Fail
C310175785 Number of failed HSDPA RAB assignment setup in cell for CS domain,RL Setup or Reconfig Timeout
C310175786 Number of failed HSDPA RAB assignment setup in cell for CS
domain,Due to IUB
C310175787 Number of failed HSDPA RAB assignment setup in cell for CS domain,Iub Congestion
C310175788 Number of failed HSDPA RAB assignment setup in cell for CS domain,Iub UL Congestion
C310175789 Number of failed HSDPA RAB assignment setup in cell for CS
domain,Iub DL Congestion
C310175790 Number of failed HSDPA RAB assignment setup in cell for CS domain,Iub TB failed
C310175791 Number of failed HSDPA RAB assignment setup in cell for CS domain,Iub FB Cause
C310175792 Number of failed HSDPA RAB assignment setup in cell for CS
domain,Iur Congestion
C310175793 Number of failed HSDPA RAB assignment setup in cell for CS domain,Iur Congestion
C310175794 Number of failed HSDPA RAB assignment setup in cell for CS domain,Iur TB failed
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 15
C310175795 Number of failed HSDPA RAB assignment setup in cell for CS domain,Iur FB failed
C310175796 Number of failed HSDPA RAB assignment setup in cell for CS
domain,UP CE Limit
C310175797 Number of failed HSDPA RAB assignment setup in cell for CS domain,Due to RNC
C310225798 Number of failed HSDPA RAB assignment setup in cell for CS domain,RB Fail,UP Fail
C310225799 Number of failed HSDPA RAB assignment setup in cell for CS
domain,UCPMC Exception
C310225800 Number of failed HSDPA RAB assignment setup in cell for CS domain,RLMM Exception
C310225801 Number of failed HSDPA RAB assignment setup in cell for CS domain,CRM Exception
C310225802 Number of failed HSDPA RAB assignment setup in cell for CS
domain,SCPM Exception
C310225803 Number of failed HSDPA RAB assignment setup in cell for CS domain,RPM Exception
C310225804 Number of failed HSDPA RAB assignment setup in cell for CS domain,Othere RNC Cause
C310175805 Number of failed HSDPA RAB assignment setup in cell for CS
domain,Unspecified failed
C310175806 Number of failed HSUPA RAB assignment setup in cell for CS domain,Invalid RAB Parameters Value
C310175807 Number of failed HSUPA RAB assignment setup in cell for CS domain,failed in the Radio Interface Procedure
C310175808 Number of failed HSUPA RAB assignment setup in cell for CS
domain,UE send rb setup failed
C310175809 Number of failed HSUPA RAB assignment setup in cell for CS domain,Timeout of UU rb setup.
C310175810 Number of failed HSUPA RAB assignment setup in cell for CS domain,TQUEUING Expiry
C310175811 Number of failed HSUPA RAB assignment setup in cell for CS domain,Requested Traffic Class not Available
C310175812 Number of failed HSUPA RAB assignment setup in cell for CS domain,Requested Guaranteed Bit Rate not Available
C310175813 Number of failed HSUPA RAB assignment setup in cell for CS domain,Requested Guaranteed Bit Rate for DL not Available
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 16
C310175814 Number of failed HSUPA RAB assignment setup in cell for CS domain,No Resource Available
C310175815 Number of failed HSUPA RAB assignment setup in cell for CS domain,No Resource Available In SRNC
C310175816 Number of failed HSUPA RAB assignment setup in cell for CS domain,Downlink CE Congestion
C310175817 Number of failed HSUPA RAB assignment setup in cell for CS domain,Downlink CE Congestion
C310175818 Number of failed HSUPA RAB assignment setup in cell for CS domain,Downlink Power Resource Congestion
C310175819 Number of failed HSUPA RAB assignment setup in cell for CS domain,Other Downlink Resource Congestion
C310175820 Number of failed HSUPA RAB assignment setup in cell for CS domain,Uplink CE Congestion
C310175821 Number of failed HSUPA RAB assignment setup in cell for CS domain,Uplink Power Resource Congestion
C310175822 Number of failed HSUPA RAB assignment setup in cell for CS domain,Other Uplink Resource Congestion
C310175823 Number of failed HSUPA RAB assignment setup in cell for CS domain,HSUPA user number limit
C310175824 Number of failed HSDPA RAB assignment setup in cell for CS
domain,HSDPA user number limit
C310175825 Number of failed HSUPA RAB assignment setup in cell for CS domain,No Resource Available In DRNC
C310175826 Number of failed HSUPA RAB assignment setup in cell for CS domain,Access Restricted Due to Shared Networks
C310175827 Number of failed HSUPA RAB assignment setup in cell for CS
domain,Non-Standard Cause
C310175828 Number of failed HSUPA RAB assignment setup in cell for CS domain,Due to NodeB
C310175829 Number of failed HSUPA RAB assignment setup in cell for CS domain,RL Setup or Reconfig Fail
C310175830 Number of failed HSUPA RAB assignment setup in cell for CS domain,RL Setup or Reconfig Timeout
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 17
C310175831 Number of failed HSUPA RAB assignment setup in cell for CS domain,Due to IUB
C310175832 Number of failed HSUPA RAB assignment setup in cell for CS
domain,Iub Congestion
C310175833 Number of failed HSUPA RAB assignment setup in cell for CS domain,Iub UL Congestion
C310175834 Number of failed HSUPA RAB assignment setup in cell for CS domain,Iub DL Congestion
C310175835 Number of failed HSUPA RAB assignment setup in cell for CS
domain,Iub TB failed
C310175836 Number of failed HSUPA RAB assignment setup in cell for CS domain,Iub FB Cause
C310175837 Number of failed HSUPA RAB assignment setup in cell for CS domain,Iur Congestion
C310175838 Number of failed HSUPA RAB assignment setup in cell for CS
domain,Iur Congestion
C310175839 Number of failed HSUPA RAB assignment setup in cell for CS domain,Iur TB failed
C310175840 Number of failed HSUPA RAB assignment setup in cell for CS domain,Iur FB failed
C310175841 Number of failed HSUPA RAB assignment setup in cell for CS
domain,UP CE Limit
C310175842 Number of failed HSUPA RAB assignment setup in cell for CS domain,Due to RNC
C310225843 Number of failed HSUPA RAB assignment setup in cell for CS domain,RB Fail,UP Fail
C310225844 Number of failed HSUPA RAB assignment setup in cell for CS
domain,UCPMC Exception
C310225845 Number of failed HSUPA RAB assignment setup in cell for CS domain,RLMM Exception
C310225846 Number of failed HSUPA RAB assignment setup in cell for CS domain,CRM Exception
C310225847 Number of failed HSUPA RAB assignment setup in cell for CS
domain,SCPM Exception
C310225848 Number of failed HSUPA RAB assignment setup in cell for CS domain,RPM Exception
C310225849 Number of failed HSUPA RAB assignment setup in cell for CS domain,Othere RNC Cause
C310175850 Number of failed HSUPA RAB assignment setup in cell for CS
domain,Unspecified failed
C310175851 Number of successful HSDPA RAB assignment setup for CS domain,Conversational Class
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 18
C310175852 Number of successful HSUPA RAB assignment setup for CS domain,Conversational Class
C310215853 Total setup time of CS HSDPA RAB connection
C310215854 Total setup time of CS HSUPA RAB connection
C310255855 Number of RAB abnormal release for CS-HSDPA :UE HSDPA categories 1 - 6,conversation
C310255856 Number of RAB abnormal release for CS-HSDPA:UE HSDPA
categories 7 - 8,conversation
C310255857 Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 9 - 10,conversation
C310255858 Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 11 - 12,conversation
C310255859 Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 13 - 14,conversation
C310255860 Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 15 - 16,conversation
C310255861 Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 17 - 18,conversation
C310255862 Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 19 - 20,conversation
C310255863 Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 21 - 22,conversation
C310255864 Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 23 - 24,conversation
C310255865 Number of RAB normal release for CS-HSDPA:UE HSDPA
categories 1 - 6,conversation
C310255866 Number of RAB normal release for CS-HSDPA:UE HSDPA categories 7 - 8,conversation
C310255867 Number of RAB normal release for CS-HSDPA:UE HSDPA categories 9 - 10,conversation
C310255868 Number of RAB normal release for CS-HSDPA:UE HSDPA categories 11 - 12,conversation
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 19
C310255869 Number of RAB normal release for CS-HSDPA:UE HSDPA categories 13 - 14,conversation
C310255870 Number of RAB normal release for CS-HSDPA:UE HSDPA categories 15 - 16,conversation
C310255871 Number of RAB normal release for CS-HSDPA:UE HSDPA categories 17 - 18,conversation
C310255872 Number of RAB normal release for CS-HSDPA:UE HSDPA categories 19 - 20,conversation
C310255873 Number of RAB normal release for CS-HSDPA:UE HSDPA categories 21 - 22,conversation
C310255874 Number of RAB normal release for CS-HSDPA:UE HSDPA categories 23 - 24,conversation
C310255875 Number of RAB abnormal release for CS-HSUPA:UE HSUPA categories 1,conversation
C310255876 Number of RAB abnormal release for CS-HSUPA:UE HSUPA
categories 2,conversation
C310255877 Number of RAB abnormal release for CS-HSUPA:UE HSUPA categories 3,conversation
C310255878 Number of RAB abnormal release for CS-HSUPA:UE HSUPA categories 4,conversation
C310255879 Number of RAB abnormal release for CS-HSUPA:UE HSUPA
categories 5,conversation
C310255880 Number of RAB abnormal release for CS-HSUPA:UE HSUPA categories 6,conversation
C310255881 Number of RAB abnormal release for CS-HSUPA:UE HSUPA categories 7,conversation
C310255882 Number of RAB normal release :UE CS-HSUPA categories
1,conversation
C310255883 Number of RAB normal release :UE CS-HSUPA categories 2,conversation
C310255884 Number of RAB normal release :UE CS-HSUPA categories 3,conversation
C310255885 Number of RAB normal release :UE CS-HSUPA categories
4,conversation
C310255886 Number of RAB normal release :UE CS-HSUPA categories 5,conversation
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 20
C310255887 Number of RAB normal release :UE CS-HSUPA categories 6,conversation
C310255888 Number of RAB normal release :UE CS-HSUPA categories
7,conversation
C310275889 Number of RNC initiate RAB release by release request for CS-HSDPA by uesr inactive
C310275890 Number of RNC initiate RAB release by release request for CS-HSDPA by repeat integrity check
C310275891 Number of RNC initiate RAB release by release request for CS-
HSDPA by UE initiate release
C310275892 Number of RNC initiate RAB release by release request for CS-HSDPA by lost UE connection
C310275893 Number of RNC initiate RAB release by release request for CS-HSDPA by relocation overall timer exceed
C310275894 Number of RNC initiate RAB release by release request for CS-
HSDPA by radio interface fail
C310275902 Number of RNC initiate RAB release by release request for CS-HSDPA by OMC intervention
C310275903 Number of RNC initiate RAB release by release request for CS-HSDPA by overload control
C310275904 Number of RNC initiate RAB release by release request for CS-
HSDPA by RAB pre-empty
C310275905 Number of RNC initiate RAB release by release request for CS-HSDPA by IUUP fail
C310275906 Number of RNC initiate RAB release by release request for CS-HSDPA by UTRAN generating
C310275907 Number of RNC initiate RAB release by release request for CS-
HSDPA by unspecific fail
C310275908 Number of RNC initiate RAB release by release request for CS-HSUPA by uesr inactive
C310275909 Number of RNC initiate RAB release by release request for CS-HSUPA by repeat integrity check
C310275910 Number of RNC initiate RAB release by release request for CS-
HSUPA by UE initiate release
C310275911 Number of RNC initiate RAB release by release request for CS-HSUPA by lost UE connection
C310275912 Number of RNC initiate RAB release by release request for CS-HSUPA by relocation overall timer exceed
C310275913 Number of RNC initiate RAB release by release request for CS-
HSUPA by radio interface fail
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 21
C310275921 Number of RNC initiate RAB release by release request for CS-HSUPA by OMC intervention
C310275922 Number of RNC initiate RAB release by release request for CS-
HSUPA by overload control
C310275923 Number of RNC initiate RAB release by release request for CS-HSUPA by RAB pre-empty
C310275924 Number of RNC initiate RAB release by release request for CS-HSUPA by IUUP fail
C310275925 Number of RNC initiate RAB release by release request for CS-
HSUPA by UTRAN generating
C310275926 Number of RNC initiate RAB release by release request for CS-HSUPA by unspecific fail
C310295927 Number of abnormal release RAB by Uu-fail,UE CS-HSDPA Categories 1 - 6,conversation
C310295928 Number of abnormal release RAB by Uu-fail,UE CS-HSDPA
Categories 7 - 8,conversation
C310295929 Number of abnormal release RAB by Uu-fail,UE CS-HSDPA Categories 9 - 10,conversation
C310295930 Number of abnormal release RAB by Uu-fail,UE CS-HSDPA Categories 11 - 12,conversation
C310295931 Number of abnormal release RAB by Uu-fail,UE CS-HSDPA
Categories 13 - 14,conversation
C310295932 Number of abnormal release RAB by Uu-fail,UE CS-HSDPA categories 15 - 16,conversation
C310295933 Number of abnormal release RAB by Uu-fail,UE CS-HSDPA categories 17 - 18,conversation
C310295934 Number of abnormal release RAB by Uu-fail,UE CS-HSDPA
categories 19 - 20,conversation
C310295935 Number of abnormal release RAB by Uu-fail,UE CS-HSDPA categories 21 - 22,conversation
C310295936 Number of abnormal release RAB by Uu-fail,UE CS-HSDPA categories 23 - 24,conversation
C310295937 Number of abnormal release RAB by Uu-fail,UE CS-HSUPA
categories 1,conversation
C310295938 Number of abnormal release RAB by Uu-fail,UE CS-HSUPA categories 2,conversation
C310295939 Number of abnormal release RAB by Uu-fail,UE CS-HSUPA categories 3,conversation
C310295940 Number of abnormal release RAB by Uu-fail,UE CS-HSUPA
categories 4,conversation
C310295941 Number of abnormal release RAB by Uu-fail,UE CS-HSUPA categories 5,conversation
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 22
C310295942 Number of abnormal release RAB by Uu-fail,UE CS-HSUPA categories 6,conversation
C310295943 Number of abnormal release RAB by Uu-fail,UE CS-HSUPA
categories 7,conversation
C310116464 Number of failed HSDPA RAB assignment setup in cell for CS domain,Due to CN
C310116465 Number of failed HSDPA RAB assignment setup in cell for CS domain,receving Iu release request from CN
C310116466 Number of failed HSDPA RAB assignment setup in cell for CS domain,receving RAB release request from CN
C310116467 Number of failed HSDPA RAB assignment setup in cell for CS domain,receving link release request from CN
C310116468 Number of failed HSUPA RAB assignment setup in cell for CS domain,Due to CN
C310116469 Number of failed HSUPA RAB assignment setup in cell for CS domain,receving Iu release request from CN
C310116470 Number of failed HSUPA RAB assignment setup in cell for CS domain,receving RAB release request from CN
C310116471 Number of failed HSUPA RAB assignment setup in cell for CS domain,receving link release request from CN
C310116472 Number of failed RAB assignment setup in cell for CS domain
SPEECH,Due to CN
C310116473 Number of failed RAB assignment setup in cell for CS domain AMR,Due to CN
C310116474 Number of failed RAB assignment setup in cell for CS domain WB-AMR,Due to CN
C310116475 Number of failed RAB assignment setup in cell for CS domain
64K/64k,Due to CN
5.2 Alarm list
None
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 23
6 Glossary
AMR Adaptive Multi Rate
BE Best Effort
CFN Connection Frame Number (counter)
CPC Continuous Packet Connectivity
CS Circuit Switch
DCH Dedicated CHannel
DRX Discontinuous Reception
DTX Discontinuous Transmission
F-DPCH Fractional Dedicated physical CHannel
GBR Guaranteed Bit Rate
HSPA High Speed Packet Access
HSDPA High Speed Downlink Packet Access
HSUPA High Speed Uplink Packet Access
IP Internet Protocol
MBR Max Bit Rate
PDCP Packet Data Convergence Protocol
PDU Protocol Data Unit
PS Packet Switch
QoS Quality of Service
RAB Radio Access Bearer
RAN Radio Access Network
RB Radio Bearer
RLC Radio Link Control
SDU Service Data Unit
SRB Signal Radio Bearer
UE User Equipment
CS Voice over HSPA Feature Guide
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 24
UL UpLink
UMTS Universal Mobile Telecommunications System
VoIP Voice over IP
Top Related