Академический Документы
Профессиональный Документы
Культура Документы
Notice
The purchased products, services and features are stipulated by the commercial contract made between Huawei and the customer. All or partial products, services and features described in this document may not be within the purchased scope or the usage scope. Unless otherwise agreed by the contract, all statements, information, and recommendations in this document are provided AS IS without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1 1.2 Intended Audience ........................................................................................................................ 1-1 1.3 Change History.............................................................................................................................. 1-1
Issue 01 (2010-03-30)
iii
1 Introduction
1 Introduction
1.1 Scope
This document describes the development of voice bearer technologies and the bearer schemes of voice over HSPA. It provides an overview of the key technologies used for HSPA to carry CS/PS voice.
Document Issues
The document issues are as follows: 01 (2010-03-30) Draft (2009-12-05)
01 (2010-03-30)
This is the document for the first commercial release of RAN12.0. Compared with issue Draft (2009-12-05) of RAN12.0, this issue optimizes the description.
Draft (2009-12-05)
This is the draft of the document for RAN12.0. This is a new document.
Issue 01 (2010-03-30)
1-1
Table 2-2 compares different voice bearer technologies. Table 2-2 Comparison between voice bearer technologies Item Radio bearer RNC rate control RLC CN Terminal AMR over DCH R99 DCH AMRC TM CS Ordinary terminal AMR over HSPA/HSPA+ HSPA/HSPA+ AMRC UM CS Supports HSPA/HSPA+. Supports AMR over HSPA/HSPA+. VoIP over HSPA/HSPA+ HSPA/HSPA+ None UM PS+IMS Supports HSPA/HSPA+. Supports the VoIP client. VoIP over DCH DCH None UM PS+IMS Supports the VoIP client.
Issue 01 (2010-03-30)
2-1
capacity and reduce UE battery consumption. Thus, the HSPA/HSPA+ technology is being increasingly used for transmitting voice services. The voice over HSPA/HSPA+ schemes consist of VoIP over HSPA/HSPA+ (WRFD-010617 VoIP over HSPA/HSPA+) and AMR over HSPA/HSPA+ (WRFD-010619 CS voice over HSPA/HSPA+). Figure 2-1 shows the data flow of VoIP over HSPA/HSPA+ and AMR over HSPA/HSPA+. Figure 2-1 Data flow of VoIP over HSPA/HSPA+ and AMR over HSPA/HSPA+
The two voice bearer schemes are described as follows: VoIP over HSPA/HSPA+ In the RAN, the VoIP service is carried on the HSPA/HSPA+ channel. In the CN, the VoIP service is carried on the PS domain and requires the support of the IMS. The IMS controls calls and connections by using the SIP protocol. Compared with voice data, TCP/IP headers are very large, which greatly reduces the transmission efficiency of the air interface. Therefore, the VoIP service requires the support of Robust Header Compression (RoHC) to reduce the overhead of TCP/IP headers. AMR over HSPA/HSPA+ In the RAN, AMR over HSPA/HSPA+ enables the CS voice to be carried on the HSPA/HSPA+ channel instead of the DCH. In the CN, the AMR service is carried only on the CS domain. Thus, operators need not deploy the IMS for the VoIP service. Only RNCs need to update the related mapping to support AMR over HSPA/HSPA+. MSCs and NodeBs are not affected. The call process of AMR over HSPA/HSPA+ is the same as that of AMR over DCH. The PDCP capability and signaling are extended to same extent. Voice services have a small traffic volume. When services with a small volume are carried on the HSPA/HSPA+ channel, the power and codes of downlink HS-SCCHs and the power of uplink DPCCHs account for a large proportion of the total resources. CPC (DTX, DRX, and HS-SCCH Less Operation) can greatly reduce the resource consumption of these channels and significantly increase the capacity of a single cell. Therefore, the scheme of voice over HSPA/HSPA+ becomes more logical after CPC is introduced.
2-2
Issue 01 (2010-03-30)
3 Technical Description
3 Technical Description
This provides an overview of the key functions related to voice over HSPA/HSPA+ so that you can have a general understanding of these functions.
3.1 Bearer
This section involves the feature "WRFD-01061701 RAB Mapping. For AMR over DCH, the CN transmits three sub-flows to the RNC, and then the RNC sets up three RBs by using TM RLC to carry the three sub-flows. For VoIP/AMR over HSPA/HSPA+, the CN transmits only 3 flows to the RNC, and then the RNC merges them into one flow and sets up one RB by using UM RLC to carry the flow. The difference between AMR over HSPA/HSPA+ and VoIP over HSPA/HSPA+ is that PDCP contains RTP/UDP for VoIP not for AMR. Figure 3-1 shows the difference between these voice bearer schemes. Figure 3-1 Difference between voice bearer schemes
CS and PS voice can be carried on the DCH, HS-DSCH, or E-DCH, depending on bearer policies and switching parameters. For details, see the Radio Bearers Feature Parameter Description. The outer loop power control (OLPC) target of voice over HSUPA is RBLER. HSUPA OLPC adjusts the SIR target of DPCCH pilot based on the comparison between the RBLER target and the measured RBLER. For details, see the Power Control Feature Parameter Description.
Issue 01 (2010-03-30)
3-1
3 Technical Description
Voice services have a small traffic volume, and they have a little impact on the Iub interface and require that the delay be as short as possible. Therefore, flow control is not required for voice services. For details, see the Transmission Resource Management Feature Parameter Description. If there is no flow control, admission control is required to ensure that sufficient resources are available for voice services to guarantee the QoS. The GBR admission control is used for the VoIP service, and the MBR admission control is used for the AMR service. For details, see the Call Admission Control Feature Parameter Description. HSUPA scheduling and flow control Voice services have a high requirement for delay, and therefore flow control and scheduling are not performed so that voice data can be transmitted quickly. For details, see the HSUPA Feature Parameter Description and Transmission Resource Management Feature Parameter Description. If there is no flow control or scheduling, the QoS is guaranteed through admission control. Admission control ensures that sufficient resources are available for voice services. For details, see the Load Control Feature Parameter Description.
3.3 Mobility
Mobility of VoIP over HSPA/HSPA+
For the handover of VoIP over HSPA/HSPA+, whether the target cell supports VoIP over HSPA/HSPA+ needs to be considered. The possible scenarios of handover are as follows: Handover between the cells that support VoIP over HSPA/HSPA+ (intra- or inter-frequency handover): follows the normal handover procedure. Handover between the cells that support VoIP over HSPA/HSPA+ and the cells that do not support VoIP over HSPA/HSPA+ (intra- or inter-frequency handover): VoIP over HSPA/HSPA+ needs to roll back to VoIP over DCH or AMR over DCH. Handover between the cells that support VoIP over HSPA/HSPA+ and the GSM cells: VoIP over HSPA/HSPA+ needs to roll back to AMR over DCH before handover.
3-2
Issue 01 (2010-03-30)
3 Technical Description
For hard handover, if the target cell supports HSPA/HSPA+, the normal handover procedure is performed. If the target cell does not support HSUPA or HSDPA, AMR over HSPA/HSPA+ needs to roll back to AMR over DCH, along with a hard handover. When a UE moves from the GSM cell to a 3G cell, the inter-RAT incoming handover procedure may be triggered. For voice over HSPA/HSPA+, associated parameters need to be configured. For voice over DCH, the normal handover procedure is performed. When a UE moves from the 3G cell to a GSM cell, the inter-RAT outgoing handover procedure may be triggered. It is a normal handover procedure.
F-DPCH
Before the Fractional DPCH (F-DPCH) is introduced, each HSDPA user requires an associated DPCCH, which consumes the downlink power and codes. The F-DPCH is introduced in 3GPP Release 6. The F-DPCH is a simplified DPCCH and has only a TPC field. One F-DPCH can be shared by up to 10 UEs. Therefore, F-DPCHs reduce the consumption of associated DPCCHs and save the codes and power of the cell.
DTX/DRX
For services such as VoIP and web browsing, UEs need to maintain uninterrupted connection and transmit data intermittently. When the number of UEs of this type increases, uplink DPCCHs greatly increase the uplink load of the cell. In the downlink, UEs need to listen to HS-SCCHs without interruption, thus wasting battery power. DTX/DRX is introduced in 3GPP Release 7. Uplink DTX allows UEs to disable the uplink DPCCH transmission periodically to reduce interference caused by the uplink DPCCH and increase uplink capacity. Downlink DRX allows UEs to receive data on the HS-SCCH at the specified time periodically, thus reducing the power consumption of UEs. For details on DTX/DRX, see the HSPA+ Feature Parameter Description.
Issue 01 (2010-03-30)
3-3
3 Technical Description
Therefore, before transmission on the air interface, the IP header needs to be compressed. RoHC is introduced in the 3GPP PDCP. It is used to compress IP headers. After RoHC is performed, the redundant headers are reduced from 4060 bytes to 35 bytes. For details on RoHC, see the PDCP Header Compression Feature Parameter Description.
3-4
Issue 01 (2010-03-30)
4 HGlossaryH
4 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
Issue 01 (2010-03-30)
4-1
5 Reference Documents
5 Reference Documents
[1] HSDPA Feature Parameter Description [2] HSUPA Feature Parameter Description [3] Transmission Resource Management Feature Parameter Description [4] Handover Feature Parameter Description [5] Power Control Feature Parameter Description [6] Load Control Feature Parameter Description
Issue 01 (2010-03-30)
5-1