HSPA+ Deployment Guide

Internal

Document Code

Product Name Product Version Document Version

WCDMA Node B&RNC

Intended Audience Prepared by

Internal UMTS Maintenance Development Dept

HSPA+ Deployment Guide
Prepared by Reviewed by Reviewed by Approved by HSPA team, Maintenance Department UMTS Date 2009-07-24

Date Date Date

2009-07-24 2009-07-24 2009-07-24

Huawei Technologies Co., Ltd.
All rights reserved

2010-01-14

HUAWEI Confidential

Page1, Total45

HSPA+ Deployment Guide

Internal

Table of Contents
HSPA+ Deployment Guide .................................................................................................. 1 Chapter 1 Overview ............................................................................................................. 9 1.1 Overview of HSPA+................................................................................................ 9 1.2 Availability............................................................................................................. 11 1.2.1 Involved Network Elements ....................................................................... 11 1.2.2 Version Support ......................................................................................... 12 1.3 Principles .............................................................................................................. 13 1.3.1 HSPA+ Code Allocation Policy .................................................................. 13 1.3.2 Flow Control ............................................................................................... 13 1.3.3 Scheduling.................................................................................................. 14 1.3.4 Power Control on HSPA+ Channels .......................................................... 15 1.3.5 HSPA+ RRM Policy ................................................................................... 15 Chapter 2 Introduction to Basic Principles ........................................................................ 16 2.1 Overview of Basic HSPA+ Principles ................................................................... 16 2.2 Key Technologies of HSPA+ ................................................................................ 16 2.2.1 Adaptive Modulation and Coding ............................................................... 16 2.2.2 HARQ ......................................................................................................... 16 2.2.3 Schedule .................................................................................................... 17 2.2.4 Layer 2 Enhancement ................................................................................ 17 2.2.5 64QAM High-Order Modulation ................................................................. 17 2.2.6 2x2MIMO .................................................................................................... 18 2.3 Structure of HSPA+ Channels.............................................................................. 18 2.3.1 HS-DSCH ................................................................................................... 18 2.3.2 HS-SCCH ................................................................................................... 19 2.3.3 HS-DPCCH ................................................................................................ 19 2.4 Data Transmission on Physical Layer of HSPA+................................................. 20 2.5 MAC-ehs Entity..................................................................................................... 21 2.6 HSPA+ Signaling Plane and User Plane ............................................................. 22 2.6.1 HSPA+ Signaling Plane ............................................................................. 22 2.6.2 Data Transmission on HSPA User Plane .................................................. 23 2.7 Mobility Management ........................................................................................... 24 2.7.1 HSPA+ Intra-Frequency Handover Policy ................................................. 24 2.7.2 HSPA+ Inter-Frequency Handover Policy ................................................. 25 2.7.3 HSPA+ Inter-System Handover Policy ...................................................... 25
2010-01-14 HUAWEI Confidential Page2, Total45

HSPA+ Deployment Guide

Internal

Chapter 3 Upgrade Guide.................................................................................................. 25 3.1 RNC Upgrade ....................................................................................................... 25 3.1.1 Upgrade Requirement ................................................................................ 25 3.2 NodeB Upgrade .................................................................................................... 26 Chapter 4 Data Configuration Policy ................................................................................. 27 4.1 HSPA+ Network Establishment............................................................................ 27 4.1.1 GGSN Configuration (Huawei)................................................................... 27 4.1.2 SGSN Configuration (Huawei) ................................................................... 27 4.1.3 Registration Rate Configuration ................................................................. 27 4.2 Check on Transmission Configuration on Iub or Iu Interface .............................. 28 4.2.1 Check on Transmission Configuration on Iub Interface ............................ 28 4.2.2 Check on Bandwidth of Iu-PS Interface ..................................................... 28 4.2.3 Node B Configuration ................................................................................. 28 4.2.4 RNC Configuration ..................................................................................... 29 4.3 Service and Bearer Configuration ........................................................................ 30 4.3.1 HSPA+ Configuration During Registration................................................. 30 4.3.2 Code Allocation of HSPA+-Enabled Cell ................................................... 30 4.3.3 Power Configuration of HSPA+-Enabled Cell............................................ 31 4.3.4 HSPA+ Scheduling and Flow Control Configuration ................................. 31 4.3.5 HSPA+ Power Control Configuration ......................................................... 31 4.3.6 QoS Guarantee Configuration of HSPA+ .................................................. 31 4.3.7 License Configuration for HSPA+ .............................................................. 32 4.4 Radio Resource Management Configuration ....................................................... 32 4.4.1 HSPA+ Measurement Control Configuration ............................................. 32 4.4.2 HSPA+ Admission Control Configuration .................................................. 32 4.4.3 HSPA+ DRD Configuration ........................................................................ 33 4.4.4 HSPA+ Load Control Configuration ........................................................... 33 4.5 Typical HSPA+ Configuration in Competition Scenarios ..................................... 33 Chapter 5 Networking Policy ............................................................................................. 35 5.1 Overview ............................................................................................................... 35 5.2 HSPA+ 64QAM Dual-Carrier Service Allocation Policy ....................................... 36 5.2.1 HSPA+ 64QAM Networking Mode I ........................................................... 36 5.2.2 HSPA+ 64QAM Networking Mode II .......................................................... 36 5.2.3 Comparison of Two HSPA+ 64QAM Networking Modes .......................... 37 5.3 Introduction to MIMO Networking Policy .............................................................. 38
2010-01-14 HUAWEI Confidential Page3, Total45

HSPA+ Deployment Guide

Internal

5.3.1 MIMO Networking Mode I .......................................................................... 38 5.3.2 MIMO Networking Mode II ......................................................................... 39 5.3.3 MIMO Networking Mode III ........................................................................ 40 Chapter 6 FAQs ................................................................................................................. 41 6.1 Services Failing to Access HSPA Channels ........................................................ 41 6.2 Low Download Rate of HSPA Service ................................................................. 41 6.3 Rate of High-rate HSPA+ Service (21 Mbit/s) Being Low.................................... 41 Chapter 7 Appendix ........................................................................................................... 43 7.1 RNC-Related MML Commands ........................................................................... 43 7.2 Node B-Related MML Commands ....................................................................... 45

2010-01-14

HUAWEI Confidential

Page4, Total45

............. 13 Table 5 Recommended RNC version ........................................ 45 2010-01-14 HUAWEI Confidential Page5........................... 11 Table 3 Categories of HSPA+-enabled UEs (red) ........... 11 Table 4 Version support table ... 37 Table 8 RNC-related MML commands......................... 45 Table 9 Node B-related MML commands ................................................................................................ 26 Table 7 Comparison of two networking modes .................................................................................................................................................................. Total45 ..HSPA+ Deployment Guide Internal List of Tables Table 1 Acronyms and Abbreviations ............................................................................................................................................................... 8 Table 2 Hardware requirement....................................................................... 25 Table 6 Recommended NodeB version .......................

.................................................................... 20 Figure 5 Structure of a MIMO HS-DPCCH frame ........................................................................................................................................................................................................................................... 21 Figure 7 Resource audit procedure .............. 19 Figure 3 Structure of an HS-SCCH frame.............................. 24 Figure 12 Dual-carrier networking I ........... 36 Figure 13 Dual-carrier networking II ......................... 37 Figure 14 MIMO networking mode I ..... 19 Figure 4 Structure of a non-MIMO HS-DPCCH frame ............................. 39 Figure 16 MIMO networking mode III ............ 39 Figure 15 MIMO networking mode II ............... 22 Figure 9 Type 2 HS-DSCH data frame ........................................................... 24 Figure 11 Capacity allocation frame......................................................................... Total45 ................................. 17 Figure 2 Structure of an HS PDSCH frame ................................................................................................................................................................................................. 20 Figure 6 MAC-ehs entity .....................................................HSPA+ Deployment Guide Internal List of Figures Figure 1 Code multiplexing combination .................................... 40 2010-01-14 HUAWEI Confidential Page6......................................................................... 23 Figure 10 Capacity request frame ............................................................................................. 22 Figure 8 Resource status indication ...................................................................................

Total45 . Acronyms and Abbreviations Acronyms and Abbreviations Full Spelling 16QAM 64QAM ACK AG BE CN DCCH DCH DPCH DTCH FP HARQ HSPA HSUPA IR MAC-d MIMO NACK NE PDU QoS RG RLC RLS 2010-01-14 16 Quadrature Amplitude Modulation 64 Quadrature Amplitude Modulation Acknowledgement Absolute Grant Best Effect Core Network Dedicated Control Channel Dedicated Channel Dedicated Physical Channel Dedicated Traffic Channel Frame Protocol Hybrid Automatic Repeat Request High Speed Downlink Packet Access High Speed Uplink Packet Access Increment Redundancy Medium Access Control . MAC-HS scheduling Abstract This document describes the deployment preparation. HARQ. network policies. upgrade precautions. but not as basis of any reply to customers or public.HSPA+ Deployment Guide Internal HSPA+ Deployment Guide Key words HSPA+. basic principles. and FAQs relating to the HSPA+ deployment and works as a guide for field deployment. This document is used for reference only.dedicated Multiple Input Multiple Output Negative Acknowledgement Network Element Protocol Data Unit Quality of Service Relative Grant Radio Link Control Radio Link Set HUAWEI Confidential Page7. data configuration policies.

HSPA+ Deployment Guide Internal RNC RoT RSN RV RTT SF SG SRNC TNL TSN TTI UE UTRAN WCDMA Radio Network Controller Raise of Thermal Retransmission Sequence Number Redundancy Version Round Trip Time Spreading Factor Serving Grant Serving RNC Transport Network Layer Transmission Sequence Number Transmission Time Interval User Equipment UMTS Radio Access Network Wideband Code Division Multiple Access Table 1 Acronyms and Abbreviations 2010-01-14 HUAWEI Confidential Page8. Total45 .

This improvement is especially significant when there are users who transmit data infrequently as VoIP users. This document only involves the 64QAM. This reduction in the transmitted power also helps to increase the uplink capacity by decreasing the total interference. MIMO. and Enhanced Layer 2 (basis of the two important features).or dual-stream transmission according to channel conditions. . The purpose is to increase the peak rates in these states and reduce the signaling transmission delay during service setup or state transition with the result improving the user experience. In a cellular network. The feature prevents the L2 from becoming the bottleneck of higher Uu rate increased by MIMO and 64QAM. . CPC feature consists of DL-DRX. The peak rate at the MAC layer can reach 28 Mbit/s. . It is an enhancement to HSDPA introduced in the WCDMA protocol of R6. Therefore. the downlink transmit power of the BTS 2010-01-14 HUAWEI Confidential Page9. the HSPA+ benefits mobile operators and end users in the following aspects: 64QAM: DL 64QAM allows the use of 64QAM in HSDPA to increase the number of bits per symbol and thus to obtain higher transmission rates. Therefore.. the downlink capability is 2–5 times the uplink capability. 2x2MIMO: MIMO increases transmission rates through space multiplexing and improves channel qualities through space diversity. and URA_PCH state. the HSPA+ further improves the service experience of end users.0. For the downlink coverage. . the uplink traffic and downlink traffic are unbalanced. This feature reduces the transmitted power (and thus increases the UE battery life) because the UE does not have to monitor and transmit overhead channels every TTl. the downlink capability in the WCDMA system is limited. Enhanced CELL_FACH and CPC are not described here. CPC: CPC allows the uplink and downlink transmissions to take place at periodic intervals. CELL_PCH. The 64QAM and MIMO are the most important and commercialized features of the HSPA+ technology.HSPA+ Deployment Guide Internal Chapter 1 Overview 1. Enhanced CELL_FACH: Enhanced CELL_FACH operation allows the use of HSDPA technologies for the UEs in the CELL_FACH. The peak rate at the MAC layer can reach 21 Mbit/s. UL DTX and HS-SCCH Less Operation. DL Enhanced Layer 2: This feature allows Uu L2 to use flexible PDU size on RLC layer and segmentation on MAC layer. Generally.1 Overview of HSPA+ HSPA+ is introduced in the 3GPP Release 7. The network side can dynamically select single. Total45 . As the most important feature of RAN11. The use of the HSPA+ technology helps provide higher data rate on downlink radio links and improve the throughput of a single user and cell capacity.

Mobile operators concern about the expenses for building an HSPA+ network. and the uplink transmit power of the UE is 21–24 dBm. Using the space diversity method. increase average system capability. if the HSPA+ MIMO technology is adopted. the downlink transmit power of the BTS is 43 dBm. The HSPA+ offers a higher data transmission rate. The HSPA+ 64QAM provides a higher data transmission rate than the HSDPA. In the case of high SNR. Typically. Total45 . and reliable service performance for a UE. Therefore. uplink UEs are easy to obtain higher SNR. it improves the service experience of the UE.952 Mbit/s). Therefore. 2x2MIMO. Theoretically.  Upgrade on the existing WCDMA network. excluding the 64QAM and MIMO technologies in R7. the peak rate is 27. the HSPA+ is compatible with the HSPA of earlier versions and R99. From the aspects of mobile operators and terminal users. Theoretically.HSPA+ Deployment Guide Internal is far greater than the uplink transmit power of the UE. the use of the HSPA+ can reduce the unit cost for transmitting every mega bytes of data stream. This helps shorten the network construction period and protect the investments of the operator. the higher-order modulation technology can be used to obtain the higher spectral efficiency. As a high-rate data service enhancement technology in the WCDMA R5. and Enhanced Layer 2 of the R7 HSPA+. if the 64QAM technology is adopted. short service response time. The operator can upgrade NodeBs in the existing WCDMA R99 network to introduce the HSPA+ with little impact on the existing architecture. enhance downlink data service performance of a UE.  Improve service performance of end users.096 Mbit/s). the 64 QAM high-order modulation technology is introduced in R7 (the 16 QAM modulation is applied in R6). HSDPA: The HSDPA involved in this document refers to the R5/R6 HSDPA technology. This depends on the equipment price and the service strategies of a single operator. the HSPA+ has the following advantages:  Expand the downlink capacity of the network and obtain higher spectral efficiency in the case of higher SNR. Constraint: This document describes the 64QAM. Therefore. 2010-01-14 HUAWEI Confidential Page10. For operators. and improves the cell throughput. the MIMO technology adopts the multi-antenna technology on the transmitting side and receiving side to improve the transmission capacity of the radio communication system by several times without increasing transmit power and bandwidth in the high SNR environment (the transmission capacity is in proportion to the number of antennas).952 Mbit/s (Formula: TB_Size/TTI = 27952 / 2ms x 2 (double data stream) = 27. the peak rate is 21.096 Mbit/s (Formula: TB_Size/TTI = 42192 / 2ms = 21. excluding the E_FACH and CPC technologies.

Total45 QPSK.4 0. and CN are involved to implement the HSPA+ feature.2 7.8 1. category 13 and category 14 support only the 64QAM.2 14. The symbol √ indicates the corresponding NE is required. six categories of UEs (Category 13–Category 18) are increased to support the HSPA+.2 10. 16QAM Not applicable (MIMO not supported) Max bit rate(Mbps) Supported modulations without MIMO operation Supported modulations simultaneous with MIMO operation . Table 3 Categories of HSPA+-enabled UEs (red) HS-DSCH category Maximum number of HS-DSCH codes received Minimum inter-TTI interval Maximum number of bits of an HS-DSCH transport block received within an HS-DSCH TTI NOTE 1 Category 1 Category 2 Category 3 Category 4 Category 5 Category 6 Category 7 Category 8 Category 9 Category 10 Category 11 2010-01-14 5 5 5 5 5 5 10 10 15 15 5 3 3 2 2 1 1 1 1 1 1 2 7298 7298 7298 7298 7298 7298 14411 14411 20251 27952 3630 HUAWEI Confidential 1. Table 2 Hardware requirement Requirement of IP Feature Data configuration requirement Hardware requirement 1.2 1. The following table shows the data configuration requirement of these NEs. RNC.8 3.2 1.2. UE UE √ NodeB √ RNC √ HLR Supporting the registration speed of the HSPA+ No special requirement CN Supporting the R7 protocol No special requirement √ √ √ In R7.6 7. category 17 and category 18 support the 64QAM and MIMO.6 3. NodeB. The details are marked in red.HSPA+ Deployment Guide Internal 1. but cannot use the two technologies at the same time.2 Availability 1.1 Involved Network Elements Network elements (NE) such as the UE.9 QPSK Page11. category 15 and category 16 support only the MIMO.

16QAM – QPSK. only the WBBPb or later version baseband board supports the HSPA+. 16QAM QPSK. supports the capabilities of category 18 in this version of the protocol 2. 16QAM.2.8 17. supports the capabilities of category 17 in this version of the protocol For future use. (d) For the BTS3801C/3803C. 64QAM – 15 1 – QPSK. it supports the HSPA+ with EBBM board added. only the FMRc or later versions support this feature. the HBBI+EDLP or EULP+EDLP must be configured to support the 64QAM. (c) For the BTS3812E/AE,BTS3812/3806/3806A. the EBBI must be configured. 64QAM – QPSK. only the enhanced downlink baseband processing board (EBBC) supports the HSPA+.3 21.HSPA+ Deployment Guide HS-DSCH category Maximum number of HS-DSCH codes received Minimum inter-TTI interval Maximum number of bits of an HS-DSCH transport block received within an HS-DSCH TTI NOTE 1 Category 12 Category 13 Category 14 Category 15 Category 16 Category 17 NOTE 2 5 15 15 15 15 1 1 1 1 1 3630 35280 42192 23370 27952 35280 23370 42192 27952 1. there is no limitation. NodeB (a) For the DBS3800. Total45 . 16QAM. (b) For the DBS3900 or BTS3900/3900A. (b) For the V2 (BSC6810) platform.6 23. 64QAM QPSK.9 Max bit rate(Mbps) Internal Supported modulations without MIMO operation Supported modulations simultaneous with MIMO operation QPSK. 16QAM Category 18 NOTE 3 Category 19 Category 20 15 1 For future use. RNC (a) For the V1 (BSC6800) platform. 16QAM. 1. and the EULP+EDLP must be configured to support the MIMO. 3.6 21.2 Version Support Product RNC BSC6800 Version Versions later than BSC6800V100R011C00 2010-01-14 HUAWEI Confidential Page12.9 17.3 27.1 23.1 27. If there is no EBBI.

and ensure that services with higher priorities are transmitted preferentially. CS over HSDPA and flow control policies of the E-FACH are added. HS-PDSCH code allocation information. modulation mode. HS-PDSCH codes can be allocated in following modes:    Static code allocation Dynamic code allocation controlled by the RNC Dynamic code allocation controlled by the Node B An HS-SCCH carries the information about the downlink HS-PDSCH allocated for each UE. However.1 HSPA+ Code Allocation Policy HS-PDSCH: The HSPA throughput of a cell depends on the number of HS-PDSCH codes in the cell. the information carried on each HS-SCCH is intended for one UE. To schedule multiple UEs within 2 ms.3 Principles 1.HSPA+ Deployment Guide Internal DBS3800/BTS3801C/380 3C BTS3812E/AE Nod eB BTS3812/3806/3806A DBS3900/ BTS3900/BTS3900A Versions later than DBS3800V100R011C00 Versions later than BTS3812E-12AC-12AE-BTS3812AV100R011 C00 Versions later than BTS3812-BTS3806-BTS3806A V100R011C00 Versions later than V200R011C00 Table 4 Version support table 1.3. the flow control policies of the HSPA+ differ from those of RAN10. the general goal is to transmit traffic through the MAC-d flow of the Iub interface to make full use the bandwidth of the Iub interface. cooperate with the HSPA+ scheduling to make efficient use of resources of the Iub interface. The information carried in the HS-SCCH includes the information required by the UE to demodulate the HS-PDSCH. 1. and transport block size. the HSPA+ code allocation policy is the same as that of RAN10. This document only involves the 64QAM and 2010-01-14 HUAWEI Confidential Page13. more HS-PDSCH codes must be configured to meet high speed requirements. The maximum number of codes supported by a UE depends on the HSDPA category of the UE. Each HS-SCCH contains 128 spreading factors (SFs).3. Total45 . including UE ID. The HSPA+ introduction requires more code resources. Therefore. CS AMR over HSDPA.2 Flow Control The HSPA+ introduces the Enhanced Layer 2. Within 2ms TTI. E-FACH. IMS. multiple HS-SCCHs are required. Generally. Therefore. VOIP. The main difference is that no flow control policies are adopted for the SRB.

Factors to be considered are as follows:   Consider the fairness. The scheduling algorithm is used to balance the resources and UEs.3.   The flow control requires to consider the following factors:       Transmission capability of the Uu interface Transport bandwidth on the Iub interface Buffer usage of the Node B Amount of data to be transmitted on the RNC Packet loss ratio on the Iub interface Transmission delay on the Iub interface 1. Make sure that every UE has the chance to transmit data. Compared with RAN10. A channel with a high carrier-to-interference rate (C/I) and a great CQI is more likely to be chosen.0. the HSPA+ increases the Layer 2 Enhancement and CS AMR over HSDPA. Consider the priority. Consider the channel conditions. PF: Proportion equity scheduling algorithm. Purposes of flow control are as follows:  Control the transmission of the HSPA data stream of the MAC-d or MAC-c/sh from the RNC on the Iub interface. each UE can be served in a certain period of time. Total45   2010-01-14 .3 Scheduling The object of the scheduling algorithm is all the UEs that need to share the HSPA+ and HSPA channels. and optimizes the QoS guarantee policies of the non-real-time service (background or interactive service) and real-time services such as Streaming. Max C/I: It aims at obtaining the maximum system capacity and highest resource utilization without considering the fairness.HSPA+ Deployment Guide Internal MIMO and ignores new flow control policies. VoIP. Implement the traffic shaping function on the Iub interface. HUAWEI Confidential Page14.  Common scheduling algorithms are as follows:  RR Scheduling: This algorithm schedules all the UEs in turn. The UE with higher priority tends to be chosen. It aims at ensuring fairness. CS AMR carried on the HS-DSCH. affects the scheduling algorithm. Ensure that the queue buffer saves enough data to be transmitted. Regard the RR and Max C/I as special PFs. that is. supports Layer 2 Enhancement and enhancement technology in the physical layer.

the R99 cell enters into the overload congestion state. Dynamic power control is recommended. the HSPA+ admission control includes power admission control on streaming and BE services and admission control of bandwidth of the Iub interface. LDR algorithm: If the usage of cell resources exceeds the basic congestion threshold. HSPA+ channels include UL HS-DPCCH. 1. The DRD function can be triggered by the following factors:  The HSPA service is initiated in cell R99.0. fast OLC actions are required to quickly eliminate the overload congestion of the cell. Power control on HSPA+ channels refers to that on these three types of channels. 1.4 Power Control on HSPA+ Channels Similar to physical channels of RAN10. PF-QoS: General name of algorithms (based on the PF algorithm) aiming at ensuring the quality of services (new algorithm in RAN11.HSPA+ Deployment Guide Internal   EPF: Enhanced proportion equity scheduling algorithm.    Traffic Retry timer Access failure of the HSPA service The load control policy of the HSPA+ is similar to that of the HSDPA. and DL HS-SCCH. the R99 cell enters into the basic congestion state. 2010-01-14 HUAWEI Confidential Page15. In this case. Total45 .5 HSPA+ RRM Policy Similar to the RAN10. To ensure the system stability.3. To support the enhancement function of the inter-frequency networking. If the uplink or downlink power of R99 cell is lower than the uplink or downlink congestion releasing threshold for OLC. DL HS-PDSCH. the cell enters into the basic congestion state. the HSPA supports the DRD function.0. the cell triggers the LDR to relieve the cell resource congestion. OLC algorithm: When the uplink or downlink power in an R99 cell exceeds the uplink or downlink triggering threshold for OLC.3.0).

the HSDPA increases the multi-user scheduling function and rapid retransmission function in the physical layer. Similar to the HSDPA.2. 2010-01-14 HUAWEI Confidential Page16. The 64QAM high-order modulation which is a new function of the HSPA+ is used to improve the downlink peak rate. but the channel utilization is low. and fast scheduling. that is. Adaptive Modulation and Coding (AMC). the Layer 2 Enhancement technology is introduced in R7 to flexibly adapt to changes of the Uu interface. If the SAW HARQ protocol is adopted. The HSPA+ still uses the preceding channels of the HSDPA. In addition. that is. To support the high-speed data transmission capability of the HSPA+.HSPA+ Deployment Guide Internal Chapter 2 Introduction to Basic Principles 2. At Node B. the next data packet is transmitted only when the correct acknowledgement information of the previous data packet is received. However. for each channel. 2. and 64QAM. and HS-DPCCH.1 Overview of Basic HSPA+ Principles In R6. 16QAM. the two technologies can be implemented only when the Layer Enhancement technology is supported. However. The 1/3 Turbo code is the basic code. HS-PDSCH. This is described in following parts. the HSPA+ adopts the SAW HARQ protocol.2 Key Technologies of HSPA+ 2. The HARQ combines the forward error code (FEC) and automatic Repeat Request (ARQ) technologies. Hybrid Automatic Repeat Request (HARQ). R99 and R44 adopt the traditional ARQ method that is implemented on the RLC layer. The protocol is simple.2. the HSDPA increases a transmission channel (HS-DSCH) and three physical channels. The SAW HARQ protocol can solve the problem of low channel utilization. The R7 protocol specifies that a UE cannot adopt both the 64 QAM and the MIMO at the same time. the HSPA cannot support the rapid power control function and there is no combining gain of downlink HSPA channels during soft handover. 2. HS-SCCH.1 Adaptive Modulation and Coding The basic method of implementing the adaptive modulation and coding (AMC) technology is to measure the quality of downlink channels and adjust the coding and modulation solution in an adaptive manner based on the measurement result (expressed by CQI) to select the appropriate modulation and coding rate to maximize the data transmission rate. These technologies aim at improving the downlink user throughput and resource utilization. The modulation modes include QPSK. the channel structure changes. the 64 QAM and MIMO must be based on the Layer Enhancement technology. Total45 .2 HARQ The Hybrid Automatic Repeat Request (HARQ) is an error correction technology.

3 Schedule Similar to the HSDPA. In addition.096 Mbit/s) 2010-01-14 HUAWEI Confidential Page17.096 Mbit/s (Formula: TB_Size/TTI = 42192 / 2ms = 21.HSPA+ Deployment Guide Internal 2. the RLC layer supports up to 1500-byte PDU. According to the protocol. the peak rate is 21.2. By default. to support the Layer 2 Enhancement technology. the HSPA+ provides downlink HS-DSCHs for all the users to transmit data.2. Therefore. MAC-ehs is introduced in the MAC. and the related HS-DSCH FP changes. 2.1Mbps).4 Layer 2 Enhancement Before the Layer 2 Enhancement technology is introduced in the R7 protocol. 2. RLC PDU Size is usually set to 320 bits or 640 bits.5 64QAM High-Order Modulation The 64QAM technology adopts higher order modulation to provide data traffic higher than the HSDPA by quickly adjusting downlink modulation and coding mode in better radio environment. According to the preceding typical configuration.1s = 13. The basic principle of the Layer 2 Enhancement technology is to introduce a variable length PDU in the RLC layer. Total45 . RLC Window Size is set to 2048.2. Theoretically. A codes to w ll hich H SDPAtransm ission is m apped (5 inthis exam ple) Data to UE#1 Data to UE#2 Data to U #3 E Code Tim e Figure 1 Code multiplexing combination Rapidly schedule different UEs to allocate resources to users with high-quality channels to greatly improve system capacity. This cannot meet the high-speed requirement of the HSPA+. RLC PDU Size is set to a fixed value.1Mbps (Formula: 640bits x 2048/0. Due to the great change of the transmission of the Uu interface. the Layer 2 Enhancement technology is introduced. Resources are shared through code multiplexing and time multiplexing. and the supported highest transmission rate is 13. if the 64QAM technology is adopted. the RTT delay between the data sending to the receiving of the acknowledge message is 100 ms.

that is. 2. 2ms. chip rate. the peak rate is 27. M *10 *2 k bits (k=4) S lot #0 S lot#1 1 subfram e: T f = 2 ms Slot #2 2010-01-14 HUAWEI Confidential Page18. such as HS-DSCHs used for carrying downlink user data. The number of configured HS-DSCH codes determines the HSPA capability of the cell. Therefore. a maximum of 15 SFs (equal to 16) are configured for HS-DSCHs. Currently. HS-SCCHs used for carrying downlink control information.1 HS-DSCH As downlink shared channels. dual-fed and dual-receiving mode.HSPA+ Deployment Guide Internal 2. HS-DSCHs are used to carry downlink user data.2. The number of HS-DSCH codes used by the UE depends on the capacity. the spectral efficiency is improved further.952 Mbit/s (Formula: TB_Size/TTI = 27952 / 2ms x 2 (double data stream) = 27. This is described in subsequent parts. if the MIMO technology is adopted. To adapt to high-speed data transmission and rapid response to channel changes. structures of HS-SCCHs and HS-DPCCHs change. HS-DSCHs do not support rapid power control and select the appropriate channel code combination. Theoretically. For the HSPA+.6 2x2MIMO Using the space diversity method. and modulation mode. However.3 Structure of HSPA+ Channels The HSPA+ uses the same channels with the HSDPA. the structure of HS-DSCHs is reserved. the TTI of HS-DSCHs is 3slot. Compared with HSDPA channels. the MIMO technology adopts the multi-antenna technology on the transmitting end and receiving end to improve the transmission capacity of the radio communication system by several times without increasing transmit power and bandwidth in the high SNR environment (the transmission capacity is in proportion to the number of antennas). Data N data 1 bits T slot = 2560 chips. HS-DSCHs support the retransmission gain combing through the HARQ mechanism. The BTS schedules UEs in a TTI of 2ms. that is. the typical scenario is 2x2MIMO. HS-DSCHs of the HSPA+ support 64QAM high-order modulation.3. and HS-DPCCHs used for carrying uplink control information. All UEs share these HS-DSCHs through the time multiplexing and code multiplexing. The spreading factor of each HS-DSCH is fixed to 16. 2.952 Mbit/s) Note that the 64QAM and MIMO cannot be configured in the R7 protocol at the same time. Total45 . In each cell.

3.2 HS-SCCH HS-SCCHs are downlink shared channels. Therefore. The spreading factor is 256. 2010-01-14 HUAWEI Confidential Page19. the UE determines whether the data on HS-DSCHs are sent to the UE and how to receive the data. Each HS-SCCH carries the information required for the UE to demodulate the HS-PDSCH. For non-MIMO users. The BTS determines whether to transmit downlink data through the information. 40 bits Slot #0 Slot#1 1 subframe: Tf = 2 ms S lot #2 Figure 3 Structure of an HS-SCCH frame 2. The uplink HS-DPCCH and other uplink channels of the UE adopt the code multiplexing mode. HS-SCCHs transmit information two slots in advance than the corresponding HS-DSCHs. Data N data 1 bits T slot = 2560 chips. Therefore. In a 2-ms TTI.3 HS-DPCCH HS-DPCCHs are uplink dedicated hannels. modulation mode. Total45 . The spreading factor of each HS-SCCH is 128. the information carried on each HS-SCCH can only be used for one UE.HSPA+ Deployment Guide Internal Figure 2 Structure of an HS PDSCH frame 2. An uplink HS-DPCCH must be established for an HSPA-enabled UE. The information carried by HS-SCCHs is important for the UE to demodulate the HS-DSCHs. Through the information. information carried on HS-DPCCHs includes the ACK/NACK message used for the rapid retransmission in the physical layer and the CQI (channel quality result) measured by the UE.3. including UE ID. multiple HS-SCCHs must be configured if you schedule multiple UEs within 2 ms. the UE decides whether to demodulate HS-DSCHs after demodulating HS-SCCHs. and transport block size. A UE monitors a maximum of four HS-SCCHs at the same time. HS-DSCH code allocation information.

After an HSPA service is established. Total45 . If yes. PCI (only for MIMO users).HSPA+ Deployment Guide Internal T s lo t = 2 5 6 0 c h i p s H A R Q -A C K 2  T s lo t = 5 1 2 0 c h i p s CQI O n e H S -D P C C H s u b fra m e (2 m s ) S u b fra m e # 0 S u b fra m e # i O n e ra d io fra m e T f = 1 0 m s S u b fra m e # 4 Figure 4 Structure of a non-MIMO HS-DPCCH frame For MIMO users. the BTS establishes downlink channels in terms of the number of HS-DSCH codes and the number of HS-SCCH codes. If the setup of an HSPA+-enabled cell is supported. After receiving the CQI. including the data block size. modulation 2010-01-14 HUAWEI Confidential Page20. the BTS transmits the data block information. the PCI information is added in the HS-DPCCH frame. and reports the CQI to the BTS through uplink HS-DPCCHs. Figure 5 shows that the PCI is added behind the CQI. calculates the CQI according to the pilot of the cell and the Measure Power Offset (MPO) configured for the UE by the BTS. and UE capability. Then. T slo t = 2 5 6 0 c h i p s H A R Q -A C K 2  T s l o t = 5 1 2 0 c h ip s C Q I/P C I O n e H S -D P C C H su bfram e (2 m s) S ub fram e # 0 S u b fra m e #i O n e r a d io f r a m e T f = 1 0 m s S u b fra m e # 4 Figure 5 Structure of a MIMO HS-DPCCH frame 2. you can understand the role of each channel during the data transmission. The UE continually monitors the downlink HS-SCCHs to check whether the data is sent to the UE. codes to be used. BTS resource utilization.4 Data Transmission on Physical Layer of HSPA+ This section describes data transmission on the physical layer of the HSPA+. the BTS determines whether to send the data to the UE according to the CQI. the UE continually measures the signal quality in the radio environment.

If the UE finds that the data block information on HS-SCCHs is transmitted to the UE. two MAC-ehs PDUs are transmitted during a TTI). 8 ms. supports multiple prior queues (a maximum of three).5 MAC-ehs Entity Figure 6 MAC-ehs entity After the Layer 2 Enhancement is introduced. the BTS transmits the data blocks of the UE on HS-DSCHs. The RNC determines whether to configure the UE to use MAC-ehs entities according to the capability of the cell and UE. and UE ID through HS-SCCHs. 2. The Layer 2 Enhancement technology is the basis of the 64QAM. Total45 . and Cell FACH. Each cell has only one MAC-ehs entity. MIMO. 4 ms. 2010-01-14 HUAWEI Confidential Page21. MAC-ehs entities are added in the MAC layer of the Node B. reorders and multiplexes SDUs (a maximum of 26) to MAC-ehs PDUs (2x2MIMO. If the UE supports the Layer 2 Enhancement technology during the HSDPA downlink data transmission. the UE demodulates the HS-DSCHs by using the obtained information after two timeslots to obtain the data block information. In step 2. Steps 3–5 are performed every 2 ms. the CQI reporting period is set by the BTS to 2 ms. The great difference between the MAC-ehs and the MAC-hs is that the MAC-hs supports data segmentation and concatenation. After two timeslots. that is. or 16 ms. you can configure MAC-ehs or MAC-hs entities to process data transmitted on HS-DSCHs.HSPA+ Deployment Guide Internal mode.

6 HSPA+ Signaling Plane and User Plane 2.1 HSPA+ Signaling Plane With the introduction of the 64QAM and MIMO. the support capability must be notified to the 64QAM-enabled UEs.. 2010-01-14 HUAWEI Confidential Page22. the RESOURCE STATUS INDICATION from the Node B to the RNC must include the indication that the 64QAM or MIMO is supported. 2. 1.HSPA+ Deployment Guide Internal 2. the AUDIT RESPONSE from the Node B to the RNC must include the indication that the 64QAM or MIMO is supported. Resource audit procedure CRNC AUDIT REQUEST Node B AUDIT RESPONSE Figure 7 Resource audit procedure If a local cell supports the 64QAM or MIMO. If the Node B supports the 64QAM or MIMO.. The following signaling procedures are for reference only.6. Resource status indication CRNC RESOURCE STATUS INDICATION Node B Figure 8 Resource status indication If a local cell supports the 64QAM or MIMO. certain information elements are added and related signaling procedures are affected. Total45 .

HSPA+ Deployment Guide Internal 2. and the frame header indicates the length of different data blocks. The type-2 data frame supports the variable PDU size.6. Therefore. Total45 .2 Data Transmission on HSPA User Plane 1. the type-2 data frame is added as shown in the preceding figure. HS-DSCH data frame Figure 9 Type 2 HS-DSCH data frame The Layer 2 Enhancement technology is introduced in the HSPA+. 2010-01-14 HUAWEI Confidential Page23.

the mobility control is based on changes of the serving cell. Total45 . that is.7. the RNC is required to map the RAB to the HS-DSCHs of the best serving cell. Control frame on user plane N ode B CRNC C A P A C IT Y R E Q U E S T Figure 10 Capacity request frame Capacity allocation: The Node B sends the CAPACITY ALLOCATION message to the RNC to notify the amount of data transmitted by the RNC in a certain period of time. the capacity allocation frames can be classified into type 1 data frames and type 2 data frames.HSPA+ Deployment Guide Internal 2. Add the handover between 64QAM cells and HSDPA/R99 cells or between MIMO cells and HSDPA/R99 cells due to changes of the cell capability. type 2 data frames are adopted. Node B CRNC C A P A C IT Y A L L O C A T IO N Figure 11 Capacity allocation frame After the Layer 2 Enhancement technology is introduced. the HSPA+ is the same as R5 HSDPA. 2010-01-14 HUAWEI Confidential Page24.7 Mobility Management 2. type 1 data frames are adopted. 2. the 1D measurement event (change of the best serving cell) is used to trigger the changes of the HS-DSCH serving cell to.1 HSPA+ Intra-Frequency Handover Policy From the perspective of mobility. and the serving cell changes through the 1x events. For HSDPA users supporting the Layer 2 Enhancement technology. To achieve high-quality data transmission on HS-DSCHs. Otherwise. Generally. The introduction of the HSPA+ brings the following impacts on mobility:   Add intra-frequency handover between 64QAM cells or MIMO cells.

In this procedure. If HS-DSCHs can carry the RAB with requested rate.7.2 HSPA+ Inter-Frequency Handover Policy The inter-frequency handover policies of the HSPA+ are the same as those of the HSDPA. the UE switches to the 2G network. radio links and HS-DSCHs are set up in the new cell. Intra-Node B hard handover adopts the same signaling procedure with the inter-Node B hard handover. The hard handover can be performed when the serving cell is being upgraded.7. MIMO.HSPA+ Deployment Guide Internal UEs in the CELL_DCH state can use technologies such as 64QAM. the RB is set up on HS-DSCHs. 2. If the HSPA+-enabled UE is set to disable the compression mode through the SET CMCF command. The prerequisite is that the corresponding cell implements the HSPA+ feature. 2G->3G handover The 2G-to-3G handover process of the HSPA+ is the same as that of the HSDPA. 2.1 Upgrade Requirement The following table lists the recommended RNC versions for commercial use.1 RNC Upgrade 3. Then. physical channels are reconfigured. and old links are removed.3 HSPA+ Inter-System Handover Policy 3G->2G handover The 3G-to-2G handover process of an HSPA+-enabled UE is the same as that of an HSDPA-enabled UE. Table 5 Recommended RNC version Recommended RNC Version Whether to Support HSPA+ 64QAM&MIMO Yes BSC6800V100R011C00SPC120 or later version BSC6810V200R011C00SPC120 2010-01-14 HUAWEI Confidential Yes Page25. services are carried on DCHs (the compression mode is enabled). Layer 2 Enhancement. Chapter 3 Upgrade Guide 3. The Uu interface and the Iub interface complete the RB reconfiguration and the RL reconfiguration respectively to run the service on DCHs instead of HS-DSCHs. the H2D process is started.1. Total45 . When services of the HSPA+-UE are carried on DCHs.

please confirm the hardware of NodeB support HSPA+ commercialization. the following upgrade steps are applicable to RAN11. the content refers to Chapter 1. Unless otherwise stated.0 V1 and V2. 3.2.1 2. Total45 . Table 6 Recommended NodeB version Type of NodeB Recommended NodeB Version Whether to Support HSPA+ 64QAM&MI MO Yes DBS3800/BTS3801C/3 803C Versions later than DBS3800V100R011C00SPC200 Versions later than BTS3812E-12AC-12AE-BTS3812AV100R011C 00SPC200 Versions later than BTS3812-BTS3806-BTS3806A V100R011C00SPC200 Versions later than V200R011C00SPC200 Yes BTS3812E/AE Yes BTS3812/3806/3806A DBS3900/BTS3900/BT S3900A Yes 2010-01-14 HUAWEI Confidential Page26. The following table lists the recommended NodeB versions for commercial use. For the BSC6800. the RNC hardware configuration does not impose special requirement on the BSC6810. at least the FMRc is configured to support the HSPA+.2 NodeB Upgrade 1.HSPA+ Deployment Guide Internal or later version To support the HSPA+ commercialization. Before upgrading.

Total45 . the rate is expanded to 21 Mbit/s (if the 64QAM is supported) or 28 Mbit/s (if the MIMO is supported). the UMTS supports a higher rate. MBRUPLKEX=250. That is. 4. Run the following command to set the maximum rate to 256000 kbit/s. On the SGSN.3 Registration Rate Configuration According to the rate requirement of the operator. set the downlink data rate. If yes. R7QOS=YES.1.2 SGSN Configuration (Huawei) The method of configuring the SGSN is similar to that configuring the GGSN. If not. SET PROCR: RNCQOSVERSION=R7. (1) On the GGSN. run the LST APNQoS command to check whether the uplink data rate of a certain APN is set. QOSVER=R7Qos. (2) On the GGSN. MOD GGSNCHARACT: IPT=IPV4. In addition. 4.HSPA+ Deployment Guide Internal Chapter 4 Data Configuration Policy 4.1 GGSN Configuration (Huawei) The HSPA+ provides a higher throughput than the HSDPA. SGSNQOSVERSION=R7. run the commands LST QoS and SET QoS to check whether the uplink and downlink data rate reaches the required value. GBRUPLKEX=250. MBRDNLKEX=250. MBRUPLK=254. If not. GBRDNLKEX=250. GGSNQOSVERSION=R7. Note that the following command corresponds to the index of the RNC actually used. capacity-related attributes must be set on the GGSN. check whether the rate reaches the required value. If the HSPA+ feature is supported. Set the Extended MBR to 250 (MBRDNLKEX 250 represents 256 Mbit/s).1 HSPA+ Network Establishment 4. RNCVER=R7. GBRDNLK=256000. modify the uplink and downlink data rate. If not. SET COMPATIBILITY: RABQOS=YES. SET QOS: MBRDNLK=256000. 2010-01-14 HUAWEI Confidential Page27.1. Set the RNC version to R7. run the commands LST COMPATIBILITY and SET COMPATIBILITY to set RABQOS to YES. do not set or ignore the rate. GBRUPLK=254. MOD RNC: IMS=YES. SET 3GSM: PARATYPE=QOS. Set the QoS attribute of a certain GGSN to R7Qos. MBRDNLK=254. GBRDNLK=254.1. set the rate value.

however. On the RNC. For the DBS3900. the size of HSPA+ bandwidth depends on the Receive Cell Rate (RCR).3 Node B Configuration The 64QAM-enabled or MIMO-enabled cell must be set up on the enhanced board. it is recommended to adopt IP networking on the Iub interface. Therefore. (2) Run the LST TRAFFIC command to check the bandwidth corresponding to the traffic index. For the BTS3812E. it supports the HSPA+ with EBBM board added. the number of the slot that controls the downlink resource group is the number of that houses the EBBI. After the cell is set up. the number of the slot that controls the downlink resource group is the number of that houses the EBBC.1 Check on Transmission Configuration on Iub Interface Add the types of paths that transmit the HSPA service on the RNC and NodeB sides. for a single user. run the DSP LOCELLRES command to check whether the downlink resource group established on the enhanced board or not. the HSPA+ feature is not supported.2 Check on Transmission Configuration on Iub or Iu Interface 4. 4.2.2 Check on Bandwidth of Iu-PS Interface (1) Run the LST IPOA command to check the traffic index of the user plane. On the Node B. check whether the downlink resource group is established on the enhanced board. For the BTS3801C/3803C. Total45 . Check the RCR of the AAL2 path. this rate cannot meet the peak value requirement (this cannot meet the peak rate requirement of a single UE). and cell rate (cells/s) corresponding to the traffic index.2. If the HSPA+ is supported. EULP. or EDLP. the number of the slot that controls the downlink resource group is the number of that houses the WBBPb. that is. If the supported rated is too low. For the DBS3800. PCR peak cell rate (cells/s). you must configure the NodeB and the cell must supports the 2010-01-14 HUAWEI Confidential Page28.2. You also can obtain the supported rate. you can modify it manually. However. 4. 1000 bit/s is recommended. Otherwise. It is recommended that the RCR is set to a maximum of 20 Mbit/s to impose strict requirement on the HSPA+ bandwidth. The configuration of a local 64QAM cell is the same as that of an HSDPA-enabled cell. set the bandwidth to the maximum value. refer to the HSPA+ bandwidth configuration of the IP RAN deployment guide. For the bandwidth configuration of the IP RAN. You can check the bandwidth in the ATM network by using the following method: ADD AAL2PATH: AAL2PATHT=HSPA.HSPA+ Deployment Guide Internal 4. For an MIMO-enabled cell. The HSPA+ improves the transmission requirement of the Iub interface. run the DSP AAL2 PATH command to check the available bandwidth of the AAL2 path carrying the HSPA.

Run the following command to add two RRUCHAINs: ADD RRUCHAIN: RCN=0. HPN=1. SET CORRMALGOSWITCH:CfgSwitch= CFG_HSDPA_64QAM_SWITCH-1&CFG_HSDPA_MIMO_SWITCH-1. In addition. The only difference is that only one RRUCHINA is required in serial connection mode.2. STN=0. 4.2. SECT=REMOTE_SECTOR. TP=TRUNK. ADD LOCELL: LOCELL=0. PS=0. Run the following command to add a SEC and select the common mode: ADD SEC: STN=0. (Position 0) ADD RRU: SRN=21. 4. SECN=0. SECT=REMOTE_SECTOR. ANTM=2. ADD LOCELL: LOCELL=0. TT=CHAIN. RCN=1. 4. HPN=0. Total45 . SRN1=20. TTW=TRUE.2. for the BSC6810 platform.3. SRN2=21. TP=TRUNK. there is no hardware limits. SECN=0. RT=MRRU. RCN=0. RCN=0. ANTM=2. 1. TT=CHAIN. 3. and configure two power amplifiers. RCN=0. PS=0. SECT=REMOTE_SECTOR. TP=TRUNK. SECN=0. set the dual-fed capability to True. the RNC requires to use the FMRc board to support the HSPA+ feature. 4. 2. HISPM=FALSE. RT=MRRU. HPN=0. Run the following command to add two RRUs: ADD RRU: SRN=20. set the dual-fed capability to True. PS=1. TT=CHAIN. (Position 1) 3.2 Node B Configuration of MIMO-Enabled Cell in Serial Connection Mode The configuration of the RRU cell in serial connection mode is the same as that in parallel connection mode. TTW=TRUE. SECN=0.HSPA+ Deployment Guide Internal transmit diversity mode. 2. TP=TRUNK. RMTCM=FALSE. 2010-01-14 HUAWEI Confidential Page29. RT=MRRU. Run the following command to add an RRUCHAIN: ADD RRUCHAIN: RCN=0.4 RNC Configuration 1. Run the following command to add a local cell. SECT=REMOTE_SECTOR. HSN=0. DIVM=COMMON_MODE.3. STN=0. ADD SEC: STN=0. ADD RRU: SRN=21.1 Node B Configuration of MIMO-Enabled Cell in Parallel Connection Mode 1. The former is recommended. DIVM=COMMON_MODE. and configure two power amplifiers. Run the following command to enable the HSDPA feature to configure attributes of the 64QAM and the MIMO. Run the following command to add two RRUs on an identical RRUCHAIN: ADD RRU: SRN=20. PS=0. SRN1=20. HISPM=FALSE. ADD RRUCHAIN: RCN=1. RT=MRRU. 4. the local cell can be configured in serial connection mode or parallel connection mode. HSN=0. HSN=0. SRN2=21. 2. RMTCM=FALSE. Run the following command to add a local cell. Run the following command to add a SEC and configure the Tx diversity. Hardware check: For the BSC6800.

3. If the Node B-based dynamic code allocation is closed. and Layer 2 Enhancement in the algorithm. HSPA+-related parameters are described previously and determined by operators according to requirements. CP1SupInd=CP1_not Supported. To enable the Node B-based dynamic code allocation policy. MOD CELLSETUP: CellId=0. 4. 4. you can enable the Node B-based dynamic code allocation when configuring the fixed code allocation on the RNC. HsPdschMaxCodeNum=15. set the maximum number of HS-PDSCH codes to 15. and the number of HS-SCCH codes to 2. the minimum number HS-PDSCH codes to 1. 4. Run the following command to configure RNC-based dynamic code allocation policy. AllocCodeMode=Automatic. or disable the Node B-based dynamic code allocation when configuring the dynamic code allocation on the RNC. ADD CELLHSDPA: AllocCodeMode=Manual. Total45 . 5. configure the static code allocation policy and allocate two HS-SCCH codes. run the ADD QUICKCELLSETUP command to set up a local cell and run the MOD CELLSETUP command to configure the transmit diversity and STTD attributes. Thus RNC using fixed code allocation. Run the following command to turn on the switch of the 64QAM. run the following command to activate the MIMO feature: ACT CELLMIMO. Node B-based dynamic code allocation is configured on the Node B. HsScchCodeNum=2. for example. MOD CELLALGOSWITCH: HspaPlusSwitch=64QAM-1&MIMO-1&L2ENHANCED-1. HsPdschMinCodeNum=1.2 Code Allocation of HSPA+-Enabled Cell The code allocation is based on the cell. For the MIMO-enabled cell. It is recommended to enable the Node B-based dynamic code allocation. Fixed code allocation and RNC-based dynamic code allocation are configured on the RNC.HSPA+ Deployment Guide Internal 3. DpchDivModforMIMO=STTD. ADD CELLHSPA: CellId=1. For the MIMO-enabled cell. HsPdschCodeNum=1.3. The code allocation configured on the RNC and that on the Node B do not affect each. TxDiversityInd=TRUE. run the SET MACHSPARA 2010-01-14 HUAWEI Confidential Page30. That is. HspdschPrioTxDiversityMode=STTD. 7. HsScchCodeNum=2. DpchPrioTxDiversityMode=STTD. MIMO. CodeAdjForHsdpaSwitch=ON.3 Service and Bearer Configuration 4. STTDSupInd=STTD_Supported.1 HSPA+ Configuration During Registration All registration-related information is configured on the HLR. The license supports the enabling of the switch of 21 Mbit/s and 28 Mbit/s (You can run the DSP LICENSE command to check the switch configuration). Run the following command to activate the corresponding HSPA+ cell: ACT CELLHSDPA: CellId=0. Run the ADD CELLHSDPA command to configure code allocation in the RNC. 6.

The dynamic code allocation policy adopted on the Node B is not detected on the LMT of the RNC.3. 2010-01-14 HUAWEI Confidential Page31. It is recommended to adopt baseline parameters. 4. For the flow control policy. ARP6Priority=Silver. The following command set the UE level of each ARP priority. run the following command: SET MACHSPARA: PWRMGN=5. ARP2Priority=Gold. for example. SCCHFER=10. To set the power margin of the cell to 5% of the baseline value. HspaPower=0. DYNCODESW=OPEN. DYNAMIC_BW_SHAPING or NO_BW_SHAPING can be selected automatically through the congestion check mechanism. ARP7Priority=Silver.5 HSPA+ Power Control Configuration The power control of HS-DPCCHs is configured on the RNC by using the SET HSDPCCH command.6 QoS Guarantee Configuration of HSPA+ Run the SET USERPRIORITY command to map the ARP to the SPI.3 Power Configuration of HSPA+-Enabled Cell Run the ADD CELLHSDPA command to configure the power of the HSPA+-enabled cell in the RNC by using. ARP4Priority=Gold. You can also run the following command to configure the flow control policy: SET HSDPAFLOWCTRLPARA: SWITCH=BW_SHAPING_ONOFF_TOGGLE. 4. run the following command: SET MACHSPARA: SCCHPWRCM=CQI. Total45 . for example. to adjust the HS-SCCH the power control based on the CQI. and set the frame error rate to 1%. these codes are allocated to the HSPA. If idle codes (SF=16) are available. you can run the following command to adopt the EPF scheduling algorithm on the Node B: SET MACHSPARA: SM=EPF It is recommended to adopt default settings of flow control parameters. ADD CELLHSDPA: AllocCodeMode=Automatic.3.HSPA+ Deployment Guide Internal command as follows: SET MACHSPARA: LOCELL=1. 4. The configured power is the power offset of the maximum transmit power of the HSPA+-enable cell. set the offset relative to the initial power of the PCPICH to 0dB.4 HSPA+ Scheduling and Flow Control Configuration The scheduling algorithm is configured on the Node B by using the SET MACHSPARA command. ARP3Priority=Gold. ARP5Priority=Gold.3. SET USERPRIORITY: ARP1Priority=Gold.3. The power control of HS-SCCHs is configured on the Node B by using the SET MACHSPARA command. 4.

SilverUlGBR=D64. Run the SET SCHEDULEPRIOMAP command to map the UE service type and class to the SPI.9 HSPA+ Admission Control Configuration During deployment. SET USERGBR: GoldUlGBR=D128.3. ******************************************************************************* Radio Resource Management Configuration 4. the modification is unnecessary. run the following command: SET LDM: ChoiceRprtUnitForDlBasicMeas=TEN_MSEC. Run the SET USERGBR command to configure the GBR for BE services. To set the basic downlink measurement period to 200 ms. CopperUlGBR=D32. Configuration related to HSPA+ measurement includes configuration of the measurement switch and measurement period. run the following command: SET LDM: ChoiceRprtUnitForHSPAPwrMeas=TEN_MSEC. SET SCHEDULEPRIOMAP: TrafficClass=INTERACTIVE. TenMsecForHSPAPwrMeas=100. *******************************************************************************  Note You can query settings of the preceding parameters first. TenMsecForDlBasicMeas=20. SET LDM: ChoiceRprtUnitForHSPARateMeas=TEN_MSEC. To measure the GBP and PBR. GoldDlGBR=D128. In the preceding example. CopperDlGBR=D32.7 License Configuration for HSPA+ Apply for licenses of the RNC to support the traffic of 21 Mbit/s and 28 Mbit/s. Run the MOD CELLALGOSWITCH command to configure the measurement switch. SilverDlGBR=D64. UserPriority=SILVER. NBMCacAlgoSwitch=HSPA_GBP_MEAS-1&HSPA_PBR_MEAS-1. Run the SET LDM command to set the measurement period.3. use the baseline values of the following parameters. To set the HSPA GBP measurement period and HSPA PBR measurement period to 1 second. SPI=5. 2010-01-14 HUAWEI Confidential Page32. you do not need to modify parameter settings. ARP14Priority=Copper. ARP9Priority=Silver. run the following command.8 HSPA+ Measurement Control Configuration Generally. THP=10. ARP11Priority=Copper. The values can be changed according to the operator requirements. ARP13Priority=Copper. You do not need to change the values of these parameters. If these parameters are set to baseline values. TenMsecForHSPAPrvidRateMeas=100. ARP12Priority=Copper. MOD CELLALGOSWITCH: CellId=1. the GBR parameters use the baseline values. the following parameters are set to baseline values. therefore.3. 4. Total45 . ARP10Priority=Silver. 4.HSPA+ Deployment Guide Internal ARP8Priority=Silver.

few actions are related to the HSPA service. and CE resource reshuffling algorithm switch. The following parameters are set when the dual carrier is adopted during the deployment. To turn on the two switches. ADD CELLALGOSWITCH: NBMCacAlgoSwitch=CRD_ADCTRL-1. You do not need to change the values of these parameters. ADD CELLINETSTRATEGY: R99CSSepInd=TRUE. SET CORRMALGOSWITCH: DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-1&DRA_HSUPA_STAT E_TRANS_SWITCH-1. When congestion occurs to a cell. the traffic type of the cell can be determined by traffic distribution. the system can take multiple measures to relieve the congestion of the cell. run the following commands: SET CORRMALGOSWITCH:DrSwitch=DR_RRC_DRD_SWITCH-1. SET CACALGOSWITCH: CacSwitch=NODEB_CREDIT_CAC_SWITCH-1. BlindHOPrio=0. The following commands are related to the HSPA service. ADD CELLALGOSWITCH: CellId=1.4 Typical HSPA+ Configuration in Competition Scenarios If the uplink adopts R99 connections. 4. 4. R99PSSepInd=TRUE. use the baseline values of the following parameters. and inter-frequency D2H algorithm switch. Run the ADD CELLALGOSWITCH command to turn on the load reshuffling algorithm switch. code resource reshuffling algorithm switch.3. turn on the HSPA DRD algorithm switch and the blink handover switch when the inter-frequency concentric neighboring cell is configured.. Run the following commands to turn on the CE resource admission control switch. DrSwitch=DR_RRC_DRD_SWITCH-1. 4.10 HSPA+ DRD Configuration The DRD policy of the HSPA+ is the same as that of the HSDPA. Run the following commands to turn on the Iub bandwidth admission switch. However. In addition.3. Run the ADD CELLLDR command to control load reshuffling algorithm parameters. you can adopt the fixed SIR Target in the case of high BER 2010-01-14 HUAWEI Confidential Page33. To support the DRD of the HSPA+. ADD CELLALGOSWITCH: NBMCacAlgoSwitch=IUBBAND_ADCTRL-1. NBMLdcAlgoSwitch=ULLDR-1&DLLDR-1&CELL_CODE_LDR-1&CELL_C REDIT_LDR-1.11 HSPA+ Load Control Configuration During deployment. run the following command to turn on the admission control switch of the HSPA+: ADD CELLALGOSWITCH: NBMCacAlgoSwitch=HSPA_ADCTRL-1. intra-frequency D2H algorithm switch. SET CACALGOSWITCH: CacSwitch=IUB_CONG_CAC_SWITCH-1. Total45 . ADD INTERFREQNCELL:BlindHoFlag=TRUE.HSPA+ Deployment Guide Internal Similar to that of the HSDPA. Run the SET CORRMALGOSWITCH command to turn on the HSPA state transition switch.

Total45 . SIRSTEPUPONBER=0. APPLIEDDIRECT=APPLIED_ON_BOTH. maximum value. TRCHTYPE=TRCH_DCH. Search exported scripts for the index of the registered traffic corresponding to the uplink 384-kbit/s traffic. SDUERRRATIOUPEXP=3. MAXSIRSTEPDN=500. Copy the preceding command to the blank area of the MML command to run this command. BERTARGET1=0. MAXSIRTARGET=172. CNDOMAINID=PS_DOMAIN. NONDTXBERTARFILTERCOEF=800. TYPICALBERDPCCH=300. If not. TRCHTYPE=TRCH_DCH. MAXSIRTARGET=172. 2010-01-14 HUAWEI Confidential Page34. SIRADJUSTSTEP=4. INITSIRTARGET=152. SIRADJUSTPERIOD=2. SIRSTEPUPONBER=0. SIRADJUSTSTEP=4. MAXSIRSTEPUP=1000. SDUERRRATIOLOWEXP=6. SDUERRRATIOUPEXP=3. 6. for example the traffic class is INTERACTIVE. SDUERRRATIOUPEXP=3. BLERQUALITY=-20. SDUERRRATIOLOWMANTISSA=1. TRAFFICCLASS=INTERACTIVE. SIRSTEPUPONBER=0. 4. and RABINDEX is 48. MOD TYPRABOLPC:RABINDEX=48. BETAC=4. 2. SDUERRRATIOLOWEXP=6. TYPCFGSUPPORT=ON. TYPICALBERDPCCH=300. NONDTXBERTARFILTERCOEF=800. DELAYCLASS=1. SDUERRRATIOUPMANTISSA=9. BERTARGET1=0. BLERQUALITY=-20. SDUERRRATIOLOWMANTISSA=1. s After the demonstration. 3. SUBFLOWINDEX=0. MAXSIRSTEPDN=500. MAXSIRSTEPUP=1000. MAXSIRTARGET=172. BLERTARMAPIND=FALSE. BLERTARMAPIND=FALSE. maximum value. SDUERRRATIOLOWEXP=6. INITSIRTARGET=152. TRCHTYPE=TRCH_DCH. Otherwise. MAXSIRSTEPDN=500. REQ2GCAP=EDGE. MOD TYPRABOLPC:RABINDEX=48. MAXBITRATE=384000. DELAYCLASS=1. Check whether the SIR Target switch for the radio link reconfiguration is enabled. SUBFLOWINDEX=0. SDUERRRATIOLOWMANTISSA=1. ULFPMODE=SILENT. BETAD=15. BLERQUALITY=-20. BLERTARMAPIND=FALSE. 5. BERTARGET2=0. MINSIRTARGET=152. SDUERRRATIOUPMANTISSA=9. SIRSTEPDOWNONBER=0. SDUERRRATIOUPMANTISSA=9. DELAYCLASS=1. SUBFLOWINDEX=0. MAXSIRSTEPUP=1000. DTXBERTARFILTERCOEF=0. BERTARGET2=0. BERTARGET1=0. MINSIRTARGET=172. 7. SSD=UNKNOWN. performance of multiple UEs in the existing network is affected (copy the following command to the blank area of the MML command and run this command). and minimum value (obtained from the output of the preceding command) to 172 (9dB). MINSIRTARGET=152. Run the following command to modify the initial value. and minimum value to 172 (9dB) through the following method: 1. INITSIRTARGET=172. run the following command to change parameters to initial values. SIRADJUSTPERIOD=2. SIRSTEPDOWNONBER=0. enable this parameter to notify modifications of parameter settings to the Node B. ADD TYPRABOLPC:RABINDEX=48. Run the EXP INNERCFGMML command on the LMT to export internal scripts. DTXBERTARFILTERCOEF=0. SIRSTEPDOWNONBER=0. BERTARGET2=0. Search scripts for corresponding outer loop power control parameter OLPC if the RABINDEX is 48. TYPICALBERDPCCH=300. ADD TYPRABBASIC:RABINDEX=48. SIRADJUSTSTEP=4. NONDTXBERTARFILTERCOEF=800.HSPA+ Deployment Guide Internal and set the initial value. SHIND=HO_TO_GSM_SHOULD_NOT_BE_PERFORM. DTXBERTARFILTERCOEF=0. SIRADJUSTPERIOD=2.

HSDPA. and HSPA+ services fully share transmission resources. the research focuses on how to allocate code. and HSPA+ services can share code resources dynamically. HSDPA. The network policies of the 64QAM are the same as those of the HSDPA.1 Overview With the rapid development of the HSPA+. the prerequisite to introduce the HSPA+ is that the existing HSDPA or R99 services are not affected. However. 2010-01-14 HUAWEI Confidential Page35. A 64QAM-enabled cell can share the second carrier with an HSDPA-enabled cell. That is. it is an inevitable trend to introduce the HSPA+ to commercial networks. However. Total45 . compared with the HSDPA and HSPA+ services. The R99. HSDPA. 3. and transmission resources to the HSPA+ and R99 service to achieve the maximum resource usage in addition to the original features of the R99 service. The MIMO requires the STTD to set to ON. However. The networkings of the 64QAM and MIMO are configured separately. To guarantee the smooth operation of the HSPA+ service. 2. The R99. Generally. the R99 service is always preferred. power. the R99 service is always preferred. and HSPA+ services can share power resources dynamically. the R99 service is always preferred. Considering actual operation scenarios and industry policies. code. For the HSPA+-enabled dual-carrier service. Therefore. it is recommended that a MIMO cell shares carriers with an R99 cell instead of an HSDPA cell.HSPA+ Deployment Guide Internal Chapter 5 Networking Policy 5. Configure a GBR for the HSPA+ service to ensure the minimum power. the performance of certain HSDPA terminals of R5 and R6 deteriorates due to the rollback of the receiver type. The R99. and transmission resources obtained by the service. the R99 service 1.

the load balancing of the HSPA service brings fluctuations and the ping-pong effect.2 HSPA+ 64QAM Dual-Carrier Service Allocation Policy 5.2 HSPA+ 64QAM Networking Mode II The first TRX implements continuous coverage and the second TRX covers hot spot areas. 5. In addition.HSPA+ Deployment Guide Internal 5. it is difficult to guarantee smooth operation of the HSDPA and HSPA+ 64QAM services and trigger the load balancing between the two carriers. The second carrier supports the HSDPA service and HSPA+ 64QAM service. F2 R99+H R99+H 1 R99+H 1 R99+H R99+H 2 R99+H R99+H F1 R99+H Hot Spot Figure 12 Dual-carrier networking I Hot Spot The networking advantage is that either the networking policy or the configuration is simple. F2 R99+H R99+H 1 1 R99 R99+H R99+H 2 F1 R99 R99 R99+H Hot Spot 2010-01-14 HUAWEI Confidential Hot Spot Page36. Therefore. One clear disadvantage is that the HSPA fails to achieve load balancing. The following figure shows the networking. The R99 service can preempt either code or power resources of the HSDPA service. Both the two TRXs support the R99 and HSPA+ 64 QAM. Total45 .1 HSPA+ 64QAM Networking Mode I The first carrier supports the R99 and HSPA services (including the HSDPA service and HSPA+64QAM service) and implements continuous coverage.2. and the uniform management is implemented in the network.2.

The advantage of networking mode II is to guarantee smooth operation of the R99 and HSPA+ 64QAM services and ensure load balancing of the HSDPA service. R99 users implement load sharing in hot spot areas. 1. Disadvantage Dual carrier scenario I: Both two carriers provide continuous coverage of the HSPA service. 2010-01-14 HUAWEI Confidential Page37. The disadvantage is that the networking is complex and involves multiple policies and configurations. HSPA users implement load balancing through random camping policies. 2. 5.2. Therefore. The two carriers implement continuous coverage of the HSPA service. 2. Both R99 and HSPA users can make calls in this cell. 4. Table 7 Comparison of two networking modes Scenario Name Advantage 1.3 Comparison of Two HSPA+ 64QAM Networking Modes Table 6 shows advantages and disadvantages of the two networking modes. HSPA resources are configured preferentially for each TRX. The network is expensive to construct. and load control. cells served by the two carriers achieve load balancing. Total45 . Therefore. 3. 3. it is hard to ensure the smooth operation of the HSPA service. and the access delay is low.HSPA+ Deployment Guide Internal Figure 13 Dual-carrier networking II Networking mode II greatly differs from networking mode I in camping policies. HSPA users do not achieve load balancing. mobility management.

The general principle is as follows:   Maximize the MIMO capacity grain and balance powers of the two transmit channels. 1. Currently. Avoid performance loss of R5 HSPA UEs. If the HSPA-enabled UE enters from the area covered by the single TRX to that covered by double TRXs. Networking mode I involves simple policies. most networks adopt dual carrier networking. HSPA-enabled UEs initiate PS calls in the cell covered by frequency 2. the MIMO networking must be separate from the HSDPA networking. the type of the HSDPA receiver rolls back and performance of HSDPA UEs deteriorates. 5. that is. There are three MIMO networking modes. which poses little impact on existing networks. configuration. 5. 2010-01-14 HUAWEI Confidential Page38. 2. another frequency is required. and algorithms and is similar to common dual carrier networking. 1. Therefore. the HSPA-enabled UE is handed over to an inter-frequency cell through the DRD. However. Users can obtain good experience. To guarantee smooth operation of the HSPA service. This can affect the access delay of the UE.3. When initiating a call. commercial networks of Huawei adopt networking mode II. Total45 .HSPA+ Deployment Guide Internal Dual carrier scenario II: HSPA cells are not covered continuously (recommended). at least operators provide three 3G frequencies. Experience of HSPA users is greatly improved because there are fewer R99 users in the cell. The R99 service is covered continuously by a single TRX.3 Introduction to MIMO Networking Policy If a MIMO-enabled cell shares one carrier with a common R5 or R6 cell. Therefore. 2. the HSPA coverage cannot be implemented.1 MIMO Networking Mode I The MIMO technology is deployed on a single frequency. the UE is handed over to the intra-frequency R99 cell and cannot be handed over to the inter-frequency HSPA cell.

HSPA+ Deployment Guide Internal Figure 14 MIMO networking mode I  Advantage The MIMO technology is deployed separately from existing networks. During the early period of the MIMO application. 5. This avoids performance loss of old R5 HSPA UEs. The networking is as follows: Figure 15 MIMO networking mode II  Advantage Separate MIMO carrier from HSPA carriers. the penetration ratio of MIMO-enabled UEs is low. capacity.  Disadvantage The MIMO technology requires to be deployed on an independent frequency and has extra requirements on frequency resources. This imposes minimum impacts on existing networks and does not affect the coverage. In the early application period. The MIMO service and R99 service are bound to an identical carrier to reduce the number of required frequencies. Therefore. or KPIs.3. and network resource usage is not high. high-end users are fewer.2 MIMO Networking Mode II If frequency resources are limited. binding the 2010-01-14 HUAWEI Confidential Page39. Total45 . the MIMO deployment can be bound to the R99 service. This avoids performance loss of original R5 HSPA UEs in the diversity cell.

If the frequency resource usage reaches the maximum value. If the HSPA performance loss is acceptable. and network resource usage is not high. it is recommended to deploy the MIMO on a single TRX. 5. In this case. 2010-01-14 HUAWEI Confidential Page40. the R99 service shares one carrier with the MIMO service. capacity. This imposes little impact on the existing network. In the early period. or KPIs. the penetration ratio of MIMO-enabled UEs is low. the impacts on R5 HSDPA UE is minimized. Total45 .  Disadvantage Binding the MIMO and R99 services to an identical carrier increases the average downlink load of frequency F1 and affects KPIs of the R99 cell because the HSPA service consumes larger downlink power.HSPA+ Deployment Guide Internal MIMO and R99 services to an identical carrier improves user experience and increases network resource usage.3 MIMO Networking Mode III If the operator increases the second TRX to deploy the HSPA+ during the Tx only networking. you can control uplink load to relieve these impacts. networking mode II is recommended. you can enable the LDR switch to increase resource usage.3. The networking is as follows: Figure 16 MIMO networking mode III  Advantage The MIMO technology is deployed separately from existing networks. This imposes minimum impacts on existing networks and does not affect the coverage. that is. For the MIMO.  Disadvantage The MIMO technology requires to be deployed on an independent frequency and has extra requirements on frequency resources.

Factors that affect the single thread service are as follows:  Registered rate  Size of the TCP receiving window on the PC (the size can be modified by using the DRTCP tool)  Rate limit of the server  Packet loss on the TCP layer  Packet delivery in sequence or randomly (It is recommended that packets are delivered in sequence on the uplink)  Rate limit on the Iu interface (check whether the bandwidth of the Iu interface on the user plane is sufficient)  Iub flow control (it is recommended to maintain the flow control)  Bandwidth limit on the Iub interface (Check whether the bandwidth is sufficient) 2010-01-14 HUAWEI Confidential Page41. 3. Check whether the index of the traffic transmitted on paths of the RNC and Node B is correct. 2. If the RCR of the Node B is greater than the transmission bandwidth of the RNC. Check whether transmission bandwidth is limited. For the HSPA+ service. Check whether the path configuration on the RNC is consistent with that on the Node B. it is recommended to adopt IP networking and configure sufficient bandwidth to meet high rate requirement of the HSPA+ service. Check whether the UE supports the service. Check whether the initial rate reaches the rate threshold of HSPA channels. 3. RNC’ s SCR=PCR-1 5. Check whether the UE supports high-rate download. Make clear that the download service is a single thread or multithread service. 4. Check whether the registered rate of the SIM card is correct.HSPA+ Deployment Guide Internal Chapter 6 FAQs 6.3 Rate of High-rate HSPA+ Service (21 Mbit/s) Being Low Tests on a site show that the rate of the high-rate HSPA+ download service (21 Mbit/s) is in low. Total45 . Recommended relation is: Node B’s RCR=RNC’ s SCR. 2.2 Low Download Rate of HSPA Service 1. the transmission rate is lowered due to packet loss. 6. 6.1 Services Failing to Access HSPA Channels 1. Run the DSP CELL command on the RNC to check whether the HSPA service of related cells is available. 4.

Guarantee performance of the portable computers and the FTP server in actual tests. 2010-01-14 HUAWEI Confidential Page42. Therefore. the HSPA+ imposes high requirements on each NE. *******************************************************************************  Rate limit on the Iu interface  Poor-quality radio environment (Observing Ec/N0 on the LMT or by using other tools)  Packet loss on data sources of the CN causing insufficient data sources The most possible cause is that the configuration of the portable computer and the driver of the UE cause low rate in the application layer. The peak rate of the HSPA+ service imposes high requirements on the quality of the Uu interface. The cause may be one of the followings:  Problems occurred on the Iub interface (see the preceding configuration specifications) ******************************************************************************* Note: For the IP networking environment. portable computers.HSPA+ Deployment Guide Internal  BLER of the Uu interface (Check the quality of the tested radio environment. Total45 . performance of the HSPA+ service may be affected. and FTP server. The recommended configuration of portable computers is as follows:       1GB memory high-performance CPU UE E270+ (driver of the latest version) No packet loss in the CN High rate High performance in the application layer on the receiving side In conclusion. Otherwise.)  Great impact imposed by the CQI on the single thread service (check the quality of the tested radio environment) Problems occurred in the multithread service are different from those in the single thread service. check settings of all ports to ensure that the CN and switch work in forcible full duplex mode. the radio environment of the Uu interface must be high-quality.

Set the HSPA algorithm switch. SET CORRMALGOSWITCH Set the connection-oriented algorithm switch. SET SCHEDULEPRIOMAP ADD TYPRABBASIC/ MOD TYPRAB Set mapping information about the scheduling priority. SET FRC Set parameters relating to the RNC-oriented basic channel configuration algorithm (FRC). Set parameters related to the HSPA admission control algorithm. Deactivate the HSPA feature of the cell. Add/Modify basic information about the typical service. Add/modify basic parameters of the radio bearer of the typical service. Total45 Add/Modify radio link control parameters of the radio bearer of a typical service. ADD CELLCAC Set parameters related to the admission control algorithm of the cell. Set scheduling priorities of the HSPA feature. Function Set the protocol version on the Node B side. Set basic channel algorithm parameters of the HSPA feature. DEA CELLHSPA Deactivate the HSPA feature (high-speed downlink packet access) of the cell.1 RNC-Related MML Commands MML Command ADD NODEB ADD CELLHSPA ACT CELLHSPA Description Add a Node B. ADD TYPRABRLC/MOD TYPRABRLC Add/Modify radio link control parameters of the radio bearer of a typical 2010-01-14 HUAWEI Confidential Page43. Activate the HSPA feature of the cell.HSPA+ Deployment Guide Internal Chapter 7 Appendix 7. . Set HSPA parameters of the cell. Activate the HSPA feature (high-speed downlink packet access) of the cell. Configure basic resources of the HSPA feature.

Set/query RNC-oriented HS-SCCH power control algorithm parameters. The RNC changes the HS-DPCCH power offset based on the actual initial SIR target of the UL DPCCH. ADD TYPRABOLPC/MOD TYPRABOLPC Add/modify outer loop power control parameters of the radio bearer of the typical service. SET HSDPCCH ADD CELLHSDPCCH/MOD CELLHSDPCCH Set/modify cell-oriented HS-DPCCH power control algorithm parameters. SET HSSCCH/LST HSSCCH Set/query RNC-oriented HS-SCCH power control algorithm parameters. ADD TYPRABHSPA /MOD TYPRABHSPA Add/modify the HSPA information of the radio bearer of the typical service. Provides the default HS-SCCH offset relative to the PILOT power regardless of spreading factors and the number of radio link sets. This ensures that the power requirement on the HS-DPCCH changes little when 2010-01-14 HUAWEI Confidential Page44. Add/Modify the cell algorithm switch. such as Enhanced L2. A add a set of HS-DPCCH power offset values corresponding to the initial SIR target that is specified based on the UL DPCCH. Add/modify the HSPA information of the radio bearer of the typical service. Set the RNC-oriented HS-DPCCH power offset.HSPA+ Deployment Guide MML Command Description service. Function Internal Add/modify outer loop power control parameters of the radio bearer of the typical service. Total45 . The RNC changes the HS-DPCCH power offset based on the actual initial SIR target of the UL DPCCH. This ensures that the power requirement on the HS-DPCCH changes little when the initial SIR target of the UL DPCCH differs. Query radio bearer parameters of the typical service. 64QAM and MIMO. LST TYPRAB Query radio bearer parameters of the typical service. ADD CELLALGOSWITCH/MOD CELLALGOSWITCH ADD CELLHSSCCH/ MOD CELLHSSCCH Add/Modify the cell-oriented algorithm switch Set/query RNC-oriented HS-SCCH power control algorithm parameters. Set RNC-oriented HS-DPCCH power control algorithm parameters.

Add AAL2 paths to carry channels on the user plane during the ATM transmission. SET HSPATRF Enable or disable the HSPA traffic of the WFMR/WFMRb/WFMRc.2 Node B-Related MML Commands MML Command ADD AAL2PATH Description Add AAL2 paths on the Iub interface. ADD ATMTRF Add ATM traffic records. SET HOCOMM Set common parameters related to the handover on the RNC. For the HSPA feature.HSPA+ Deployment Guide MML Command Description Function Internal the initial SIR target of the UL DPCCH differs. Set IP paths related to the HSPA feature. Table 8 RNC-related MML commands 7. and SAAL link. As common resources. Set IPOA PVC links during IP transport. AAL2 path. Set parameters related to the HSPA handover. Table 9 Node B-related MML commands 2010-01-14 HUAWEI Confidential Page45. ATM traffic record indexes can be used by the IPoA PVC link. Total45 . ADD IPPATH SET MACHSPARA SET HSPAFLOWCTRLPARA Set the flow control switch of the HSPA feature. Set algorithms and functions related to the HSPA feature. Enable or disable the HSPA traffic of the WFMR/WFMRb/WFMRc. ADD IPPATH ADD IPOAPVC Add IP paths. ADD AAL2PATH Add AAL2 paths between the RNC and the neighbor node. Add IP paths on the Iub interface. Add IP paths of the HSPA type. Add an IPoA PVC link between the local IPoA client and the peer IPoA client. set the type of the path to the HSPA. Set parameters related to the Mac-hs. Set the flow control switch of the HSPA feature. Function Set AAL2 paths related to the HSPA feature.