ZTE UMTS (U9.3) CS Voice Over HSPA Feature Guide - V4.0

CS Voice over HSPA
WCDMA RAN
Feature Guide
CS Voice over HSPA Feature Guide

Version V4.0 Date 2010-06-18 Author Xu Chunxiao Approved By Zhao Dapeng Remarks
2010 ZTE Corporation. All rights reserved. ZTE CONFIDENTIAL: This document contains propriet ary 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
2010 ZTE Corporation. All rights reserved.
TABLE OF CONTENTS
1 2 2.1 2.2 2.3 3 3.1 3.1.1 3.1.2 3.1.3 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.4 3.5 3.6 3.7 4 4.1 4.2 4.2.1 4.2.2 4.2.3 4.2.4 4.2.5 5 5.1 5.2 6 Functional Attribute ............................................................................................1 Overview .............................................................................................................1 The user plane of CS Voice over HSPA .................................................................2 Cont rol plane of CS Voice over HSPA ...................................................................3 Channel change for CS Voice over HSPA ..............................................................3 Technology de scription ......................................................................................3 The user plane of CS Voice over HSPA .................................................................3 PDCP ..................................................................................................................3 RLC ....................................................................................................................5 Ciphering procedures for CS over HSPA ...............................................................5 The control plane of CS Voice over HSPA .............................................................6 UE capability........................................................................................................6 The service establishment for CS Voice over HSPA ...............................................6 Bearer strategy of CS Voice over HSPA ................................................................7 The SRB Bearer of CS Voice over HSPA ...............................................................8 The channel change of CS Voice over HSPA .........................................................8 Channel Rec onfiguration Based on Propagation Condition .....................................8 Handover bet ween two cells which support CS Voice over HSPA bot h ....................9 Handover bet ween cell whic h support CS Voice over HSPA and the cell which doesnt support. .................................................................................................9 The relocation crossing RNC of CS Voice over HSPA.............................................9 The inter-RA T handover for CS Voice over HSPA ................................................10 Power Control ....................................................................................................10 Admission Control ..............................................................................................10 Congestion Control .............................................................................................10 Overload Control ................................................................................................10 Parameters and configurations.........................................................................11 Parameters list ...................................................................................................11 Parameters configuration ....................................................................................11 Quality Measurement Switch for VoIP/ CS Voice ..................................................11 Switch of AMR over HSPA ..................................................................................11 Max CS Delay ....................................................................................................11 Delay Time Threshold of D/D-> HS/D or HS/E after HS/D or HS/E ->D/ D Triggering by Channel Quality .............................................................................................12 Neighbouring RNC Feather Switch ......................................................................12 Counters and Alarm ..........................................................................................13 Counters list.......................................................................................................13 Alarm list ...........................................................................................................22 Glossary ...........................................................................................................23
II
FIGURES
Figure 1 Figure 2 Figure 3 Three sub-flows reassemble ...................................................................................2 PDCP AMR Data P DU format .................................................................................3 UMD RLC format....................................................................................................5
TABLES
Table 1 Table 2 Table 3 Table 4 Table 5 Compare of three voice solution ..............................................................................2 PDCP Type............................................................................................................4 The meanings of UMD RLC E bit.............................................................................5 The Paramet ers list of CS Voice over HSPA ..........................................................11 The counters of CS Voice over HSPA ....................................................................13
III
Functional Attribute
System version:[RNC V 3.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.
Overview
3GPP set up CS V oice Service over HSPA work Item in RA N#37 meeting in Jul. 2007. And this WI was finished in the RA N#39 meeting after six months later. Simply, CS Voice over HSPA is that the user plane of CS voice bears on HSPA channel (HS DPA/HSUPA ), instead of R99 channel. Hence the voice s ervice 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 CP C 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 RA CH and S RB over HSPA, and etc. At present, there are three voice solutions in UMTS net work, traditional R99 voice, CS Voice over HSPA and VoIP over HSPA. Now we compare the sameness and difference of these three voice solutions.
Table 1
Compare of three voice solution
User plane channel Core network IMS PDCP level Sub-flow number RLC entitie s
R99 voice DCH CS domain No No 3 or 2 3 or 2
CS Voice over HSPA HSPA(DPA/ UPA) CS domain No Yes 1 1
VoIP over HSPA HSPA(DPA/ UPA) PS domain Yes Yes 1 1
We can find the difference of these three voice solutions clearly by the table. The main differenc e 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 net work 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-DS CH/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 does nt bears on RLC level directly. The three AMR sub-flows are reassembled and bear on P DCP level firstly. Then it bears on RLC level. Hence the P DCP 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
Sub flow A
Sub flow B
Sub flow C
Data
Pad
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 RA DIO BEARE R SETUP RRC message for CS Voice over HSPA. RAN will decide the channel type, for example, DCH/DCH or HS -DS CH/E-DCH for CS V oice 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

HSUPAs uplink coverage is worse than DCH, especially for the 2ms TTI. UE activates the CS V oice over HSPA and moves in the cell. Although the c ell handover doesnt 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 does nt 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 bet ween inter-RA T.
3
3.1
3.1.1
Technology description
The user plane of CS Voice over HSPA
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 P DU bears on RLC level as the RLC SDU. And t he 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 Dat a PDU. This PDCP type is only used to encaps ulate the user plane of CS Voice over HSPA.
Figure 2
PDCP AMR Data PDU format
PDU type Data
CS counter
PDU type IE includes 3 bits.
Table 2
PDCP Type
Bit 000 001 010 011-111
PDU Type PDCP Data PDU PDCP SeqNum P DU PDCP AMR Data PDU Reserved (P DUs wit h this encoding are invalid for this version of the protocol)
CS count er 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 count er to the upper layers. And the upper layers will process the delay depending on it. E very 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 P DU 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 fifth LSBs of the CFN at which the packet has been rec eived from higher layers. The PDCP PDU is octet aligned. But the actual P DCP 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. E very 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 Dat a PDU, it shall: The PDCP entity derives the PDCP SDU from the dat a 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 rec eived PDCP header to the upper layer.
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 P DCP 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
Sequence Number Length Indicator

. . .
E E
Oct1 (Optional) (1)
Length Indicator Data
(Optional)
PAD
(Optional) Last Octet
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 0 1
Description The next field is a complete S DU, which is not segment ed, concatenated or padded. The next field is Length Indicator and E bit
SN_Delivery is a new optional system parameter defined in TS 25.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 lay ers. And when SN_Delivery parameter is configured, the transmitting RLC entity does not conc atenat e nor segment RLC S DUs in downlink. And the transmitting RLC entity does not concat enat e 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.
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 STA RT for ciphering in CS Voice over HSPA establishment or channel reconfiguration between DCH and HSPA.
3.2
3.2.1
The control plane of CS Voice over HSPA

UE capability
RAN needs to know whether the UE supports CS Voice over HSPA before RA N 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 CE LL 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 doesnt support CS Voice over HSPA. These following two messages are affected by this IE. RRC CONNECTION SE TUP COMP LE TE UE CAPABILITY INFORMA TION The target RNC needs to know the UE capability to decide the channel type when the UE handovers crossing RNC or han dovers into UMTS from other RA T. S o the SRNC or the inter-RA T need to report the UE capability to the DRNC. Therefore, Support for CS Voice over HSPA IE is adopt ed 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. INTE R RA T HANDOVE R INFO WITH INTE R RA T CAPABILITIE SRNS RE LOCA TION INFO
3.2.2
The service establishment for CS Voice over HSPA

The specifications dont 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 voic e bears on HS-DSCH/E-DCH in both of DL and UL. Henc e we believe that the value of CS Voice over HSPA will be lost for the unsymmetrical bearer. Therefore, ZTE UTRA N will not support the unsymmetric al bearer. RNC uses RA DIO BEARE R SE TUP RRC message to establish the CS Voice over HSPA if UE is in idle state or CELL_FA CH state and uses CELL UPDA TE CONFIRM RRC message to establish CS Voice over HSPA if UE is in CELL/URA_P CH state.
Both of RA DIO BEARER SETUP and CELL UP DA TE CONFIRM include RAB information for setup IE. And the specifications extend this IE and add CS-HSPA information IE int o 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 MaxCS Delay. 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. Henc e the specifications extend RAB information for setup and add UL AMR rate IE into it. The UEs 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. Thes e values meanings depend on the value of NAS Synchronization indicator parameter. If NAS Sync hronization indicat or 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 net work indicates the AMR rate by the RAB ASSIGNMENT REQUES T RA NAP 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
3.2.3.1
Bearer strategy of CS Voice over HSPA

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 s witch named AmrOverHspaS wch is adopted by RNC. RNC will not support CS Voice over HSPA if AmrOverHspaS wc h is off even that the license is on. RNC will support CS Voice over HSPA only when bot h of AmrOverHs paS wc h 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 AmrOverHspaS wc h 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 -DS CH/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 HSDSCH/E-DCH, other service will try to bear on HS-DSCH/E-DCH too. Off course, if the service cant bears on HS-DS CH/E-DCH channel, it will bears on DCH/DCH.
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-DP CH. 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-DP CH and CPC. If CS V oice over HSPA is actived and bears on HS-DSCH/E-DCH channel, the S RB will bears on HS -DS CH/E-DCH channel. If CS voice over HSPA is interworking wit h 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 -DS CH/E-DCH channel, the SRB will bears on HS-DS CH/ED-CH channel.
3.3
3.3.1
The channel change of CS Voice over HSPA

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 doesnt handover to other cell. But it is possible that the propagation condition gets to be wors e and UE report the 1F event. If it happens, RNC can reconfigures the logical channel from HS-DS CH/E-DCH to DCH/DCH. If UE report the 1E event because UE moves, RNC can rec onfigures the logical channel to HS -DS CH/EDCH channel from DCH/ DCH too. It depends on the CChQS wch switch whether RNC reconfigures the logical channel because of the propagation condition. If CChQS wch is off, RNC will not reconfigure it. And if CChQS wc h is on, RNC will reconfigure it. CChQS wch is a new parameter imported into RNC for CS Voice over HSPA. The Ping-P ang effect maybe happens because of UE moving. The Ping-P ang 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-P ang effect can saves the radio resource and reduces the unnecessary channel reconfiguration. This parameter is Dt oHsDelayThr. DtoHs DelayThr can be set on OMC. DtoHsDelayThr will starts when the logical channel is reconfigured from DCH/DCH to HS -DS CH/E-DCH or from HS -DS CH/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 DtoHs DelayThr 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 ot her switches about propagation conditions, for example, IBChQS wch, SChQS wc h, and CChQS wc h. If CS Voice over HSPA is interworking with other PS servic e and any one of these switches is on and some service need to be
reconfigured from HS-DS CH/E-DCH to DCH/DCH becaus e of propagation conditions, all of the int erworking service should be reconfigured to DCH/DCH.
3.3.2
Handover between two cells which support CS Voice over HSPA both
Because the specifications dont modify the Iur protocol for CS Voice over HSPA, RNC cant know whether the neighbouring RNC supports the CS Voice over HSPA through the Iur signaling system. Then RNC adopts a new parameter named RncFeatS witch 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 HS DPA Introduction Feature Guide V3.1.doc> and < ZTE UMTS HS UPA Introduction Feat ure Guide V3.1.doc>
3.3.3
Handover between cell which support CS Voice over HSPA and the cell which doesnt support.
We will discuss the handover from the cell which support CS Voice over HSPA to the cell which doesnt support firstly. TS25.331 requires that RNC should use RADIO BEARER SE TUP RRC message t o handover bet ween the cells in this situation. RA DIO BEARE R 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 B earer belonging to this RAB. Then UE will reestablis hes these entities and the Radio B earers in the target cell by the parameters in RA DIO BEARER SE TUP 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 doesnt 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 B earer, PDCP entity and RLC entity. Then UE will reestablish three new RLC entities and three new Radio B earers to bear the subflow A, B and C of the AMR-NB. Cont rarily, UE moves from the cell which doesnt 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 -DS CH/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 cant know whether the DRNC supports CS V oice over HSPA. Hence RNC imports a new switch into the RncFeatS witch parameter. This switch indicates whet her the DRNC supports CS Voice over HSPA. This switch will not affect the soft or hard handover process in Iur int erface. But it will control the relocation procedures. If CS V oice over HSPA is active in SRNC and the DRNC doesnt support CS voice over HSPA and there is an Iur connection between these two RNCs, the SRNC wont active the relocation procedure. The user plane of CS Voice over HSPA will be forwarded to SRNC through Iur interface.
If CS V oice over HSPA is active in SRNC and the DRNC doesnt support CS voice over HSPA and there is no Iur connection between t hese t wo RNCs, CS V oice over HSPA will be fall backed to R99 AMR voice and the SRNC will active the reloc ation procedure.
3.3.5
The inter-RAT handover for CS Voice over HSPA

There are two scenarios in the Inter-RA T handover. One is handover into UMTS from other RA T. And another is handover into other RA T out of UMTS. The proc ess of handover out of UMTS is same as the R99 AMRs 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 dont describe the default configuration for CS Voice over HSPA. It is impossible for RNC to choose the radio parameters in this scenario. Hence the servic e 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 cont rol 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 bas ed 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 >
10
4
4.1
Parameters and configurations

Parameters list
Table 4 The Parameters list of CS Voice over HSPA
ID 1 2 3 4 5
Abbreviate CChQS wch AmrOverHspaS wch MaxCsDelay DToHs Delay Thr RncFeatSwitch
Parameter Name Quality Measurement Switch for VoIP/ CS Voice Switch of CS voice over HSPA Max CS Delay Delay Time Threshold of D/D-> HS/D or HS/E after HS/D or HS/E ->D/D Triggering by Channel Quality Neighbouring RNC Feather Switch
4.2
4.2.1
Parameters configuration
Quality Measurement Switch for VoIP/ CS Voice
OMC path Path: View->Configuration Management-> RNC NE-> RNC Radio Res ource Management-> Modify Advanced Parameter->Dynamic Radio B earer Control Information-> Quality Measurement Switch for VoIP/ CS Voice Parameters configuration This parameter is the propagation conditions meas urement 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 Management->Ot her paramet ers-> 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. Radio Resource
4.2.3
Max CS Delay
OMC path
11
Path: View->Configuration Management->RNC NE ->RNC Radio Resource Management-> Modify Advanced Parameter->Dy namic Radio Bearer Control Information-> Ma x CS Delay Parameters configuration This paramet er is the max delay of t he us er plane of CS V oice over HSPA. UE s NAS level controls the de-jitter by this parameter. This parameters 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->Dy namic 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-P ang 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 supp orts CS Voice over HSPA.
12
5
5.1
Counters and Alarm

Counters list
Table 5 The counters of CS Voice over HSPA
Counter No. C310175759 C310175760 C310175761 C310175762 C310175763 C310175764 C310175765 C310175766 C310175767
Description Number of failed HSDPA RAB assignment setup for CS domain,Conversational Class Number of failed HSUPA RAB assignment setup for CS domain,Conversational Class Number of failed HSDPA RAB assignment setup in cell for CS domain,Invalid RAB Parameters Value Number of failed HSDPA RAB assignment setup in cell for CS domain,failed in the Radio Interface Procedure Number of failed HSDPA RAB assignment setup in cell for CS domain,UE send rb setup failed Number of failed HSDPA RAB assignment setup in cell for CS domain,Timeout of UU rb setup. Number of failed HSDPA RAB assignment setup in cell for CS domain,TQUEUING Expiry Number of failed HSDPA RAB assignment setup in cell for CS domain,Requested Traffic Class not Available Number of failed HSDPA RAB assignment setup in cell for CS domain,Requested Guaranteed Bit Rate not Available Number of failed HSDPA RAB assignment setup in cell for CS domain,Requested Guaranteed Bit Rate for UL not Available Number of failed HSDPA RAB assignment setup in cell for CS domain,No Resource Available Number of failed HSDPA RAB assignment setup in cell for CS domain,No Resource Available In SRNC Number of failed HSDPA RAB assignment setup in cell for CS domain,Downlink CE Congestion Number of failed HSDPA RAB assignment setup in cell for CS domain,Downlink CE Congestion Number of failed HSDPA RAB assignment setup in cell for CS domain,Downlink Power Resource Congestion Number of failed HSDPA RAB assignment setup in cell for CS domain,Other Downlink Resource Congestion Number of failed HSDPA RAB assignment setup in cell for CS domain,Uplink CE Congestion
C310175768
C310175769 C310175770 C310175771 C310175772 C310175773 C310175774 C310175775
13
C310175776
Number of failed HSDPA RAB assignment setup in cell for CS domain,Uplink Power Resource Congestion Number of failed HSDPA RAB assignment setup in cell for CS domain,Other Uplink Resource Congestion Number of failed HSDPA RAB assignment setup in cell for CS domain,HSDPA user number limit Number of failed HSDPA RAB assignment setup in cell for CS domain,HSDPA user number limit Number of failed HSDPA RAB assignment setup in cell for CS domain,No Resource Available In DRNC Number of failed HSDPA RAB assignment setup in cell for CS domain,Access Restricted Due to Shared Networks Number of failed HSDPA RAB assignment setup in cell for CS domain,Non-Standard Cause Number of failed HSDPA RAB assignment setup in cell for CS domain,Due to NodeB Number of failed HSDPA RAB assignment setup in cell for CS domain,RL Setup or Reconfig Fail Number of failed HSDPA RAB assignment setup in cell for CS domain,RL Setup or Reconfig Timeout Number of failed HSDPA RAB assignment setup in cell for CS domain,Due to IUB Number of failed HSDPA RAB assignment setup in cell for CS domain,Iub Congestion Number of failed HSDPA RAB assignment setup in cell for CS domain,Iub UL Congestion Number of failed HSDPA RAB assignment setup in cell for CS domain,Iub DL Congestion Number of failed HSDPA RAB assignment setup in cell for CS domain,Iub TB failed Number of failed HSDPA RAB assignment setup in cell for CS domain,Iub FB Cause Number of failed HSDPA RAB assignment setup in cell for CS domain,Iur Congestion Number of failed HSDPA RAB assignment setup in cell for CS domain,Iur Congestion Number of failed HSDPA RAB assignment setup in cell for CS domain,Iur TB failed
C310175777
C310175778 C310175779
C310175780
C310175781
C310175782 C310175783 C310175784
C310175785
C310175786 C310175787 C310175788 C310175789 C310175790 C310175791 C310175792 C310175793 C310175794
14
C310175795 C310175796 C310175797 C310225798 C310225799 C310225800 C310225801 C310225802 C310225803 C310225804 C310175805
Number of failed HSDPA RAB assignment setup in cell for CS domain,Iur FB failed Number of failed HSDPA RAB assignment setup in cell for CS domain,UP CE Limit Number of failed HSDPA RAB assignment setup in cell for CS domain,Due to RNC Number of failed HSDPA RAB assignment setup in cell for CS domain,RB Fail,UP Fail Number of failed HSDPA RAB assignment setup in cell for CS domain,UCPMC Exception Number of failed HSDPA RAB assignment setup in cell for CS domain,RLMM Exception Number of failed HSDPA RAB assignment setup in cell for CS domain,CRM Exception Number of failed HSDPA RAB assignment setup in cell for CS domain,SCPM Exception Number of failed HSDPA RAB assignment setup in cell for CS domain,RPM Exception Number of failed HSDPA RAB assignment setup in cell for CS domain,Othere RNC Cause Number of failed HSDPA RAB assignment setup in cell for CS domain,Unspecified failed Number of failed HSUPA RAB assignment setup in cell for CS domain,Invalid RAB Parameters Value Number of failed HSUPA RAB assignment setup in cell for CS domain,failed in the Radio Interface Procedure Number of failed HSUPA RAB assignment setup in cell for CS domain,UE send rb setup failed Number of failed HSUPA RAB assignment setup in cell for CS domain,Timeout of UU rb setup. Number of failed HSUPA RAB assignment setup in cell for CS domain,TQUEUING Expiry Number of failed HSUPA RAB assignment setup in cell for CS domain,Requested Traffic Class not Available Number of failed HSUPA RAB assignment setup in cell for CS domain,Requested Guaranteed Bit Rate not Available Number of failed HSUPA RAB assignment setup in cell for CS domain,Requested Guaranteed Bit Rate for DL not Available
C310175806
C310175807
C310175808 C310175809 C310175810
C310175811
C310175812
C310175813
15
C310175814
Number of failed HSUPA RAB assignment setup in cell for CS domain,No Resource Available Number of failed HSUPA RAB assignment setup in cell for CS domain,No Resource Available In SRNC Number of failed HSUPA RAB assignment setup in cell for CS domain,Downlink CE Congestion Number of failed HSUPA RAB assignment setup in cell for CS domain,Downlink CE Congestion Number of failed HSUPA RAB assignment setup in cell for CS domain,Downlink Power Resource Congestion Number of failed HSUPA RAB assignment setup in cell for CS domain,Other Downlink Resource Congestion Number of failed HSUPA RAB assignment setup in cell for CS domain,Uplink CE Congestion Number of failed HSUPA RAB assignment setup in cell for CS domain,Uplink Power Resource Congestion Number of failed HSUPA RAB assignment setup in cell for CS domain,Other Uplink Resource Congestion Number of failed HSUPA RAB assignment setup in cell for CS domain,HSUPA user number limit Number of failed HSDPA RAB assignment setup in cell for CS domain,HSDPA user number limit Number of failed HSUPA RAB assignment setup in cell for CS domain,No Resource Available In DRNC Number of failed HSUPA RAB assignment setup in cell for CS domain,Access Restricted Due to Shared Networks Number of failed HSUPA RAB assignment setup in cell for CS domain,Non-Standard Cause Number of failed HSUPA RAB assignment setup in cell for CS domain,Due to NodeB Number of failed HSUPA RAB assignment setup in cell for CS domain,RL Setup or Reconfig Fail Number of failed HSUPA RAB assignment setup in cell for CS domain,RL Setup or Reconfig Timeout
C310175815
C310175816 C310175817
C310175818
C310175819
C310175820
C310175821
C310175822
C310175823 C310175824
C310175825
C310175826
C310175827 C310175828 C310175829
C310175830
16
C310175831 C310175832 C310175833 C310175834 C310175835 C310175836 C310175837 C310175838 C310175839 C310175840 C310175841 C310175842 C310225843 C310225844 C310225845 C310225846 C310225847 C310225848 C310225849 C310175850 C310175851
Number of failed HSUPA RAB assignment setup in cell for CS domain,Due to IUB Number of failed HSUPA RAB assignment setup in cell for CS domain,Iub Congestion Number of failed HSUPA RAB assignment setup in cell for CS domain,Iub UL Congestion Number of failed HSUPA RAB assignment setup in cell for CS domain,Iub DL Congestion Number of failed HSUPA RAB assignment setup in cell for CS domain,Iub TB failed Number of failed HSUPA RAB assignment setup in cell for CS domain,Iub FB Cause Number of failed HSUPA RAB assignment setup in cell for CS domain,Iur Congestion Number of failed HSUPA RAB assignment setup in cell for CS domain,Iur Congestion Number of failed HSUPA RAB assignment setup in cell for CS domain,Iur TB failed Number of failed HSUPA RAB assignment setup in cell for CS domain,Iur FB failed Number of failed HSUPA RAB assignment setup in cell for CS domain,UP CE Limit Number of failed HSUPA RAB assignment setup in cell for CS domain,Due to RNC Number of failed HSUPA RAB assignment setup in cell for CS domain,RB Fail,UP Fail Number of failed HSUPA RAB assignment setup in cell for CS domain,UCPMC Exception Number of failed HSUPA RAB assignment setup in cell for CS domain,RLMM Exception Number of failed HSUPA RAB assignment setup in cell for CS domain,CRM Exception Number of failed HSUPA RAB assignment setup in cell for CS domain,SCPM Exception Number of failed HSUPA RAB assignment setup in cell for CS domain,RPM Exception Number of failed HSUPA RAB assignment setup in cell for CS domain,Othere RNC Cause Number of failed HSUPA RAB assignment setup in cell for CS domain,Unspecified failed Number of successful HSDPA RAB assignment setup for CS domain,Conversational Class
17
C310175852 C310215853 C310215854 C310255855 C310255856
Number of successful HSUPA RAB assignment setup for CS domain,Conversational Class Total setup time of CS HSDPA RAB connection Total setup time of CS HSUPA RAB connection Number of RAB abnormal release for CS-HSDPA :UE HSDPA categories 1 - 6,conversation Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 7 - 8,conversation Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 9 - 10,conversation Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 11 - 12,conversation Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 13 - 14,conversation Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 15 - 16,conversation Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 17 - 18,conversation Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 19 - 20,conversation Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 21 - 22,conversation Number of RAB abnormal release for CS-HSDPA:UE HSDPA categories 23 - 24,conversation Number of RAB normal release for CS-HSDPA:UE HSDPA categories 1 - 6,conversation Number of RAB normal release for CS-HSDPA:UE HSDPA categories 7 - 8,conversation Number of RAB normal release for CS-HSDPA:UE HSDPA categories 9 - 10,conversation Number of RAB normal release for CS-HSDPA:UE HSDPA categories 11 - 12,conversation
C310255857
C310255858
C310255859
C310255860
C310255861
C310255862
C310255863
C310255864
C310255865 C310255866
C310255867
C310255868
18
C310255869
Number of RAB normal release for CS-HSDPA:UE HSDPA categories 13 - 14,conversation Number of RAB normal release for CS-HSDPA:UE HSDPA categories 15 - 16,conversation Number of RAB normal release for CS-HSDPA:UE HSDPA categories 17 - 18,conversation Number of RAB normal release for CS-HSDPA:UE HSDPA categories 19 - 20,conversation Number of RAB normal release for CS-HSDPA:UE HSDPA categories 21 - 22,conversation Number of RAB normal release for CS-HSDPA:UE HSDPA categories 23 - 24,conversation Number of RAB abnormal release for CS-HSUPA:UE HSUPA categories 1,conversation Number of RAB abnormal release for CS-HSUPA:UE HSUPA categories 2,conversation Number of RAB abnormal release for CS-HSUPA:UE HSUPA categories 3,conversation Number of RAB abnormal release for CS-HSUPA:UE HSUPA categories 4,conversation Number of RAB abnormal release for CS-HSUPA:UE HSUPA categories 5,conversation Number of RAB abnormal release for CS-HSUPA:UE HSUPA categories 6,conversation Number of RAB abnormal release for CS-HSUPA:UE HSUPA categories 7,conversation Number of RAB normal release :UE CS-HSUPA categories 1,conversation Number of RAB normal release :UE CS-HSUPA categories 2,conversation Number of RAB normal release :UE CS-HSUPA categories 3,conversation Number of RAB normal release :UE CS-HSUPA categories 4,conversation Number of RAB normal release :UE CS-HSUPA categories 5,conversation
C310255870
C310255871
C310255872
C310255873
C310255874
C310255875 C310255876 C310255877 C310255878 C310255879 C310255880 C310255881 C310255882 C310255883 C310255884 C310255885 C310255886
19
C310255887 C310255888 C310275889 C310275890 C310275891 C310275892
Number of RAB normal release :UE CS-HSUPA categories 6,conversation Number of RAB normal release :UE CS-HSUPA categories 7,conversation Number of RNC initiate RAB release by release request for CSHSDPA by uesr inactive Number of RNC initiate RAB release by release request for CSHSDPA by repeat integrity check Number of RNC initiate RAB release by release request for CSHSDPA by UE initiate release Number of RNC initiate RAB release by release request for CSHSDPA by lost UE connection Number of RNC initiate RAB release by release request for CSHSDPA by relocation overall timer exceed Number of RNC initiate RAB release by release request for CSHSDPA by radio interface fail Number of RNC initiate RAB release by release request for CSHSDPA by OMC intervention Number of RNC initiate RAB release by release request for CSHSDPA by overload control Number of RNC initiate RAB release by release request for CSHSDPA by RAB pre-empty Number of RNC initiate RAB release by release request for CSHSDPA by IUUP fail Number of RNC initiate RAB release by release request for CSHSDPA by UTRAN generating Number of RNC initiate RAB release by release request for CSHSDPA by unspecific fail Number of RNC initiate RAB release by release request for CSHSUPA by uesr inactive Number of RNC initiate RAB release by release request for CSHSUPA by repeat integrity check Number of RNC initiate RAB release by release request for CSHSUPA by UE initiate release Number of RNC initiate RAB release by release request for CSHSUPA by lost UE connection Number of RNC initiate RAB release by release request for CSHSUPA by relocation overall timer exceed Number of RNC initiate RAB release by release request for CSHSUPA by radio interface fail
C310275893
C310275894 C310275902 C310275903 C310275904 C310275905 C310275906 C310275907 C310275908 C310275909 C310275910 C310275911
C310275912
C310275913
20
C310275921 C310275922 C310275923 C310275924 C310275925 C310275926 C310295927 C310295928 C310295929 C310295930 C310295931 C310295932 C310295933 C310295934 C310295935 C310295936 C310295937 C310295938 C310295939 C310295940 C310295941
Number of RNC initiate RAB release by release request for CSHSUPA by OMC intervention Number of RNC initiate RAB release by release request for CSHSUPA by overload control Number of RNC initiate RAB release by release request for CSHSUPA by RAB pre-empty Number of RNC initiate RAB release by release request for CSHSUPA by IUUP fail Number of RNC initiate RAB release by release request for CSHSUPA by UTRAN generating Number of RNC initiate RAB release by release request for CSHSUPA by unspecific fail Number of abnormal release RAB by Uu-fail,UE CS-HSDPA Categories 1 - 6,conversation Number of abnormal release RAB by Uu-fail,UE CS-HSDPA Categories 7 - 8,conversation Number of abnormal release RAB by Uu-fail,UE CS-HSDPA Categories 9 - 10,conversation Number of abnormal release RAB by Uu-fail,UE CS-HSDPA Categories 11 - 12,conversation Number of abnormal release RAB by Uu-fail,UE CS-HSDPA Categories 13 - 14,conversation Number of abnormal release RAB by Uu-fail,UE CS-HSDPA categories 15 - 16,conversation Number of abnormal release RAB by Uu-fail,UE CS-HSDPA categories 17 - 18,conversation Number of abnormal release RAB by Uu-fail,UE CS-HSDPA categories 19 - 20,conversation Number of abnormal release RAB by Uu-fail,UE CS-HSDPA categories 21 - 22,conversation Number of abnormal release RAB by Uu-fail,UE CS-HSDPA categories 23 - 24,conversation Number of abnormal release RAB by Uu-fail,UE CS-HSUPA categories 1,conversation Number of abnormal release RAB by Uu-fail,UE CS-HSUPA categories 2,conversation Number of abnormal release RAB by Uu-fail,UE CS-HSUPA categories 3,conversation Number of abnormal release RAB by Uu-fail,UE CS-HSUPA categories 4,conversation Number of abnormal release RAB by Uu-fail,UE CS-HSUPA categories 5,conversation
21
C310295942 C310295943 C310116464
Number of abnormal release RAB by Uu-fail,UE CS-HSUPA categories 6,conversation Number of abnormal release RAB by Uu-fail,UE CS-HSUPA categories 7,conversation Number of failed HSDPA RAB assignment setup in cell for CS domain,Due to CN Number of failed HSDPA RAB assignment setup in cell for CS domain,receving Iu release request from CN Number of failed HSDPA RAB assignment setup in cell for CS domain,receving RAB release request from CN Number of failed HSDPA RAB assignment setup in cell for CS domain,receving link release request from CN Number of failed HSUPA RAB assignment setup in cell for CS domain,Due to CN Number of failed HSUPA RAB assignment setup in cell for CS domain,receving Iu release request from CN Number of failed HSUPA RAB assignment setup in cell for CS domain,receving RAB release request from CN Number of failed HSUPA RAB assignment setup in cell for CS domain,receving link release request from CN Number of failed RAB assignment setup in cell for CS domain SPEECH,Due to CN Number of failed RAB assignment setup in cell for CS domain AMR,Due to CN Number of failed RAB assignment setup in cell for CS domain WB-AMR,Due to CN Number of failed RAB assignment setup in cell for CS domain 64K/64k,Due to CN
C310116465
C310116466
C310116467
C310116468
C310116469
C310116470
C310116471
C310116472 C310116473 C310116474 C310116475
5.2
Alarm list
None
22
Glossary
AMR BE CFN CPC CS DCH DRX DTX F-DP CH GBR HSPA HSDPA HSUPA IP MBR PDCP PDU PS QoS RAB RAN RB RLC SDU SRB UE Adaptive Multi Rate Best Effort Connection Frame Number (counter) Continuous Packet Connectivity Circuit Switch Dedic ated CHannel Discontinuous Reception Discontinuous Transmission Fractional Dedicated physical CHannel Guarant eed Bit Rat e High Speed Packet Access High Speed Downlink Packet Access High Speed Uplink Packet Access Internet Protocol Max Bit Rate Packet Data Convergence Protocol Protocol Data Unit Packet Switch Quality of Servic e Radio Access Bearer Radio Access Network Radio Bearer Radio Link Control Service Data Unit Signal Radio Bearer User Equipment
23
UL UMTS VoIP
UpLink Universal Mobile Telecommunications System Voice over IP
24

ZTE UMTS (U9.3) CS Voice Over HSPA Feature Guide - V4.0

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZTE UMTS (U9.3) CS Voice Over HSPA Feature Guide - V4.0

Uploaded by

Copyright:

Available Formats

CS Voice over HSPA

CS Voice over HSPA Feature Guide

CS Voice over HSPA Feature Guide

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

CS Voice over HSPA Feature Guide

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

CS Voice over HSPA Feature Guide

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

CS Voice over HSPA Feature Guide

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

CS Voice over HSPA Feature Guide

Compare of three voice solution

R99 voice DCH CS domain No No 3 or 2 3 or 2

CS Voice over HSPA HSPA(DPA/ UPA) CS domain No Yes 1 1

VoIP over HSPA HSPA(DPA/ UPA) PS domain Yes Yes 1 1

The user plane of CS Voice over HSPA

Three sub-flows reassemble

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

CS Voice over HSPA Feature Guide

Control plane of CS Voice over HSPA

Channel change for CS Voice over HSPA

PDCP AMR Data PDU format

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

CS Voice over HSPA Feature Guide

PDU type Data

PDU type IE includes 3 bits.

Bit 000 001 010 011-111

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

CS Voice over HSPA Feature Guide

UMD RLC format

Sequence Number Length Indicator

Oct1 (Optional) (1)

Length Indicator Data

(Optional) Last Octet

The meanings of UMD RLC E bit

Ciphering procedures for CS over HSPA

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

CS Voice over HSPA Feature Guide

The control plane of CS Voice over HSPA

The service establishment for CS Voice over HSPA

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

CS Voice over HSPA Feature Guide

Bearer strategy of CS Voice over HSPA

CS Voice over HSPA interworks with other service

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

CS Voice over HSPA Feature Guide

The SRB Bearer of CS Voice over HSPA

The channel change of CS Voice over HSPA

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

CS Voice over HSPA Feature Guide

The relocation crossing RNC of CS Voice over HSPA