Beruflich Dokumente
Kultur Dokumente
CS over HSPA
Feature ID: ZWF26-02-005
Version: V3.11.10
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2012 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
IMS No No 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.
1-1
Key Techniques
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 doesnt 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.
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.
1-2
Hardware Requirement
NE Requirement
RNC None
NodeB None
Software Requirement
2-1
GGSN NO
HLR NO
Topology
Topology is shown in Figure 2-1.
2-2
MSC/MGW - ZTE
N/A
HLR - ZTE
UE1 subscribes conversational 12.2kbps/12.2kbps.
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.rAB_Parameters.trafficClass = RANAP_TrafficClass_conversati
onal
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.rAB_Parameters.maxBitrate.elem[0] =12200
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.rAB_Parameters.guaranteedBitRate.elem[0] = 4750
RNC
Parameters setting in the RNC.
- Switch of CS voice over HSPA: Open
3-1
Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > Logical RNC Associated With PLMN Configuration
Information > DRBC Controlling Configuration Parameter > Switch of CS voice over
HSPA
- HSPA Support Method:Support HSUPA,HSDPA and DCH
Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > UTRAN Cell xxx > Cell Ability and
Reselection > HSPA Support Method
Node B
N/A
3-2
4-1
4-2
5-1
5-2
5-3
5-4
5-5
5-6
5-7
5-8
5-9
5-10
5-11