Professional Documents
Culture Documents
Table of Contents
Chapter 1 HSDPA.......................................................................................................................... 4 1.1 Introduction....................................................................................................................... 4 1.2 Definitions, Acronyms and Abbreviations..........................................................................4 1.2.1 Definitions............................................................................................................... 4 1.2.2 Acronyms and Abbreviations..................................................................................5 1.3 Availability......................................................................................................................... 7 1.3.1 License................................................................................................................... 7 1.3.2 Versions.................................................................................................................. 7 1.3.3 NEs......................................................................................................................... 8 1.4 Principles........................................................................................................................... 8 1.4.1 Overview................................................................................................................. 8 1.4.2 Realization of the HSDPA.......................................................................................8 1.4.3 HSDPA Physical Channel.....................................................................................10 1.4.4 HSDPA Channel Mapping.....................................................................................10 1.4.5 HSDPA Key Technologies.....................................................................................13 1.4.6 HSDPA Power Allocation......................................................................................19 1.4.7 HSDPA Codes Allocation......................................................................................21 1.5 Other Features of HSDPA...............................................................................................25 1.5.1 Overview............................................................................................................... 25 1.5.2 HSDPA Cell Admission Control.............................................................................25 1.5.3 HSDPA Power Control.......................................................................................... 27 1.5.4 HSDPA Channel Switch........................................................................................ 28 1.5.5 HSDPA Mobility Management...............................................................................30 1.6 Implementation................................................................................................................ 39 1.6.1 Engineering Guidelines......................................................................................... 39 1.6.2 Summary of HSDPA Data Configuration Commands...........................................40 1.6.3 Description of HSDPA Parameters on RNC Side..................................................43
1.6.4 Description of HSDPA Parameters on NodeB Side..............................................54 1.6.5 Example of Data Configuration.............................................................................55 1.7 Maintenance ................................................................................................................... 56 1.7.1 Related Alarms..................................................................................................... 56 1.7.2 Related Performance Items .................................................................................56
Chapter 1 HSDPA
1.1 Introduction
High Speed Downlink Packet Access (HSDPA) is an important feature of the 3GPP R5. As a downlink high-speed data transmission solution, its theoretical maximum rate at the air interface is 14.4 Mbit/s. The main features of the HSDPA are as follows:
The frames transmitted over the air interface are 2 ms. The physical layer adopts the HARQ and AMC adaptive rate technologies. A high order modulation is used to improve spectrum usage. Both code division and time division are used to schedule UEs.
Higher downlink peak transmission rate: up to 14.4 Mbit/s Shorter service delay: providing a faster service experience to the subscribers More efficient downlink codes and power utilization: for macro cell coverage, the capacity is 50% higher; for micro cell coverage, the capacity is 200% 300% or higher
Definition A cell that can provide HSDPA connection and HSDPA service to the UEs. A UE can have at most one servicing HSDPA cell at one time.
MAC-hs
On the NodeB side and the UE side. Includes four entities: HARQ, scheduling/priority handing, TFRC selection and flow control.
scheduling/priority
Resources scheduling between data flow and HARQ. Deciding whether to send or resend according to feedbacks of the channel and ACK/NACK. Setting Priority, queue and data block number.
TFRC selection
The entity selects a transmission mode according to the current channel and resources.
HSDPA cell
Refers to the cell with the HSDPA channel and provides HSDPA service to the UEs.
R99 cell
Refers to the cell without the HSDPA channel and cannot provide HSDPA service to UEs.
HSDPA channel
The physical channels of the HSDPA, including HS-SCCH, HS-PDSCH,, and HS-DPCCH.
All channels other than the HSDPA channel. A connection between a cell and a UE when the service the UE applies to is carried on HS-DSCH. A connection between a cell and a UE when the service the UE applies to is totally carried on HS-DSCH.
HS-DSCH channel
Abbreviation ACK AMC BE CAC CmCH-PI CQI CRNC DCH DPCH EDGE FACH FRC FP GPRS GSM HARQ HSDPA HS-DPCCH
Full name Acknowledgement Adaptive Modulation and Coding Best Effort Call Admission Control Common Transport Channel Priority Indicator Channel Quality Indicator Controlling Radio Network Controller Dedicated Channel Dedicated Physical Channel Enhanced Data rates for Global Evolution Forward Access Channel Fundamental Resource Configuration Frame Protocol General Packet Radio Service Global System for Mobile Communications Hybrid Automatic Repeat Request High Speed Downlink Packet Access Dedicated Physical Control Channel (uplink) for HSDSCH
High Speed Downlink Shared Channel High Speed Physical Downlink Shared Channel Shared Control Physical Channel for HS-DSCH Increment Redundancy Medium Access Control for HSDPA Negative Acknowledgement
Full name Protocol Data Unit Quality of Service Quaternary Phase Shift Keying Radio Link Control Radio Network Controller Round Trip Time Spreading Factor User Equipment UMTS Radio Access Network Wideband Code Division Multiple Access
1.3 Availability
1.3.1 License
This feature is an optional feature of HUAWEI UMTS RAN. It can be used only after the relative license is purchased.
1.3.2 Versions
Table 1.1 lists the Huawei RAN products that support HSDPA. Table 1.1 Huawei RAN products that support HSDPA Product RNC NodeB BSC6800 DBS3000 BTS3812A BTS3812E V100R005 V100R006 V100R006 V100R006 Version
1.3.3 NEs
HSDPA needs joint support of NodeB, RNC, and CN, as shown in Table 1.1. Table 1.1 Support of NodeB, RNC, and CN HSDPA request NodeB RNC MS Server Additional hardware Data configuration MGW SGSN GGSN HLR
1.4 Principles
1.4.1 Overview
This section introduces the following information of HSDPA:
Realization of the HSDPA HSDPA Physical Channel HSDPA Channel Mapping HSDPA Key Technologies HSDPA Power Allocation HSDPA Codes Allocation
Adding MAC-hs and HSDPA physical layer processing at both the UE and NodeB sides Transmitting the user plane data flow through the HS-DSCH FP between the SRNC, CRNC, and NodeB
Trough Iub when the SRNC and the CRNC are the same
See the following for details. 1) HSDPA protocol stack model when the SRNC and the CRNC are the same
Figure 1.1 shows the model when the SRNC and CRNC are the same.
DTCH DCCH DTCH DCCH
MAC-d
MAC-d
MAC-hs
MAC-hs
HS-DSCH FP
HS-DSCH FP
PHY
PHY
TNL
TNL
Uu
NodeB
Iub
CRNC/SRNC
Figure 1.1 HS-DSCH protocol stack model (the SRNC and CRNC are the same) See the following description about the figure above:
The MAC-d of the SRNC sends the MAC-d PDUs through FP to the MAC-hs of the NodeB. The MAC-hs of the NodeB completes scheduling of the HS-DSCH. The MAC-hs of the NodeB sends the MAC-hs PDU through Uu interface to the equivalent MAC-hs of the UE.
I. HS-SCCH
The HS-SCCH carries downlink control information. It is used to notify the UE of the information about the HS-PDSCH, including modulation mode, size of a transmission block, version redundant information, UE ID and HS-PDSCH channel code. HS-SCCH is aligned with the PCCPCH in timing and keeps fixed time offset with the HS-PDSCH. Its spreading factor is fixed as 128 and QPSK is the only modulation mode. The number of HS-SCCHs (128 at most) and the channel codes in the cell are decided by RNC, which notifies NodeB through the NBAP signaling message. The UE can detect one to four HS-SCCHs specified by the NodeB at one time.
II. HS-PDSCH
The HS-PDSCH is used to carry downlink service data. The spreading factor of the HS-PDSCH can be 16 only. Each cell can provide at most 15 HS-PDSCHs whose codes must be continuous. When a cell provides 15 HSPDSCHs, the maximum rate reaches 14.4 Mbit/s. The HS-PDSCH adopts the QPSK or 16QAM modulation mode.
III. HS-DPCCH
The HS-DPCCH is used to carry the uplink feedback information related to the downlink HS-PDSCH, including ACK/NACK and CQI. The spreading factor of the HSDPCCH is fixed as 256.
Streaming
When the switch is on, the streaming service is mapped When the switch is off, the streaming service is mapped
to the HS-DSCH.
to the DPCH. Interactive Background The generic term for these two services is BE service. The BE services are mapped to the HS-DSCH whenever possible.
Traffic classes
Indicates whether the HS-DSCH supports this service or not, as listed in I. 1Table 1.1.
Service rate
The HS-DSCH can carry a service only when its service rate is higher than the rate threshold. The service rate thresholds are: [HS-DSCH streaming service threshold] [HS-DSCH BE service threshold]
Indicates whether the cell provides the HS-DSCH Indicates whether the UE supports the HSDPA
Note:
The combination of the two HSDPA services can be carried by the same HSDSCH. The UE needs admission of the HS-DSCH to access the network after the mapping. For the process of the admission decision, see 1.5.2"HSDPA Cell Admission Control ".
DTCH
DCCH
MAC - D
MAC - D
DCH
HS-DSCH FP
DCH
DCH FP
DCH FP
Iub
HS-DSCH
HS-SCCH
HS-PDSCH
DPCH
DPCH
Cell 2
Figure 1.1 HS-PDSCH mapping When a downlink RAB is mapped to the HS-DSCH, two DCHs will be set up regardless of the existence of uplink data. One DCH transmits the uplink and
downlink signaling, and the other transmits uplink RLC acknowledge message or possible uplink service data. These two DCHs are called associated DCH in the text below, and the corresponding DPCHs are called associated DPCH.
Note: When the UE is in soft handover, its HSDPA data can be carried by one HS-DSCH cell at most while the none-HSDPA data can be carried by DPCHs of many cells.
2 ms TTI Link adaptation through HARQ and AMR in the physical layer Flexible scheduling by code division and time division
I. 2 ms TTI
By using 2 ms TTI at the air interface, the HSDPA acquires the following advantages:
II. HARQ
1) HARQ technology
The HARQ reserves the decoding error information to combine it with the retransmitted data. In this way, the HARQ can be called a new technology and a combination of the Forward Error Correction (FEC) and ARQ. (18.5.5) The HARQ supports two coding combination modes as listed in Table 1.1. Table 1.1 Coding combination modes the HARQ supports
Coding combination Description Comparison
Chase Combing
The second mode is better in that the combination of the retransmitted bit set and the former bit set raises the redundant data and the possibility of recovery from errors at the air
Increment Redundancy
Coding combination
Description
Comparison
interface.
2)
Every HSDPA user has an HARQ entity on both the UE and NodeB sides, each having up to eight HARQ processes. Several HARQ processes used together can fully utilize the transmission capability of the air interface, as shown in Figure 2.1.
HS-SC HS-PDS
HS-SC HS-PDS
HARQ process 1
HARQ process 2
12ms or more
Figure 2.1 Data transmission of the HARQ processes It takes around 12 ms for an HARQ from sending the HS-SCCH PDU to receiving the ACK/NACK (RTT). In an HARQ process, it takes only 2 ms to send data within an RTT. While by using several HARQ processes, RTT can be fully used to send more data, as shown in Figure 2.1:
In this case, the first process sends data in the first 2 ms, and then starts to wait. In the second 2 ms, the second process sends data, and then starts to wait. With such multi-process, each 2 ms can be used to send data to the UE.
III. AMC
The UE reports the CQI to the NodeB through the HS-DPCCH and the NodeB selects coding rate and modulation mode according to the radio environment indicated by the CQI, as listed in Table 1.1.
Table 1.1 Coding rate and modulation mode based on the CQI
The condition of the Modulation and rate Result
radio environment
Good ( The UE is near the NodeB) Poor(The UE is at the boarder of the cell or there is a sever attenuation)
High order modulation (for High coding rate Low order modulation (for Low coding rate
example, 16QAM)
example, QPSK)
In HSDPA scheduling, the codes and timeslots of the cell are shared by and allocated to the users on different HSDPA channels. Figure 1.1 gives an example.
All channelization codes available for HSDPA Channelization code Time UE1 data UE2 data
UE3 data
Figure 1.1 HSDPA sharing mechanism Suppose there are three HSDPA users in the cell and five channelization codes that can be used by HSDPA channels in Figure 1.1. Table 1.1 describes of resources allocation for six frames in the above example. Table 1.1 HSDPA scheduling sample
Subframe Codes allocation
First
The five codes are allocated to UE1 that has fine transmission
Subframe
Codes allocation
conditions. Second UE2 is allocated with two codes and UE3 is allocated with three codes. Third UE2 is allocated with two codes and UE3 is allocated with three codes. Fourth The five codes are allocated to UE1 that has fine transmission conditions. By analogy
2)
Fast scheduling
The HSDPA uses the following methods to adapt to the fast change of channels:
Shorten the transmission time interval (TTI) to 2 ms. Locate the scheduling function unit in the NodeB. HSDPA scheduling strategy
3)
In a short term, the strategy is based on channel condition. That is, the system sends data to the UE with the best channel condition. In a long term, the strategy gives attention to both priority and equity.
Channel quality indicating value Queue priority Buffer size Waiting time Others, including UE capacity, number of ACK/NACK retransmissions, data retransmission, and compression mode HSDPA basic scheduling algorithms
4)
Table 1.1 lists three HSDPA basic scheduling algorithms. Table 1.1 HSDPA basic scheduling algorithms
Algorithm Description
Max C/I
Allocates resources to the UE with the best channel conditions at TTIs, maximizing the cell handling capacity
Algorithm
Description
Round Robin
Gives attention to both allocation equity and efficiency By using this algorithm, the carrier can decide the weights (queue priority, CQI, waiting time, and queue length) in resources allocation according to the cell types (PICRO, MICRO, or MACRO).
A flow control entity is added at the lub interface after introducing the HSDPA. Flow control is adopted in the HSDPA user plane. The system controls separately every prior queue of MAC-d. The purpose of flow control is to reduce data delay and avoid discarding data due to congestion. In addition, it is to transmit the data buffered by the RNC to the NodeB within its buffering capacity. Flow control is implemented through the capacity request and allocation processes at the lub interface. 2) Capacity request at the Iub interface
The RNC sends a CAPACITY REQUEST control frame to the NodeB at the Iub, as shown in Figure 2.1.
NodeB SRNC
CAPACITY REQUEST
Figure 2.1 Capacity request at the Iub interface The structure of capacity request frame is shown in Figure 2.2. The frame includes the queue priority and the data buffer size in the RNC RLC layer.
bit0 Cm CH-PI
Payload
Figure 2.2 Structure of capacity request frame 3) Capacity allocation at the Iub interface
After receiving the capacity request from the RNC, the NodeB decides the queue capacity according to the following factors:
The transmit rate of the requesting queue at the Uu interface The data buffer size of the requesting queue on the NodeB The bandwidth for transmitting HSDPA data at the Iub interface
Then, the NodeB sends a CAPACITY ALLOCATION message to the RNC, shown in Figure 3.1.
NodeB SRNC
CAPACITY ALLOCATION
Note: The NodeB can also initiate capacity allocation to the RNC according to the buffer size of the queue and the bandwidth available at the Iub interface.
bit0 Cm CH-PI
Number of Octets 1
Maximum MAC-d PDU Length Maximum MAC-d PDU Length(cont) HS-DSCH Credits Payload
Figure 3.2 Structure of the capacity allocation frame CmCH-PI: the queue with priority HS-DSCH Interval: length of the cycle HS-DSCH Credits: the number of data frames Maximum MAC-d PDU Length: the greatest PDU size HS-DSCH Repetition Period: how many times at most the HS-DSCH Interval can repeat
The actual power of DPCH is adjusted through the inner and outer loop power control algorithm. The actual power of HSDPA channel is allocated dynamically among users through the NodeB scheduling algorithm.
Power of the HSDPA downlink physical channel (HS-SCCH and HS-PDSCH) Common channel power DPCH power
Among the three parts, the second is reserved and the first is allocated by the NodeB.
The two kinds of allocation are mutually exclusive. Configure either one in [HS-SCCH Power Set Flag] on the OMC of the NodeB. The following describes the two kinds of allocation.
The DPCH has the priority to use the rest power resources for its real time services and inner loop power control. The rest power resources of the cell are allocated for the HSDPA downlink physical channels.
This section describes the allocation of cell downlink codes. The codes described in this section are the available channel codes. For example, the HSDPA codes are the maximum channel codes the HS-PDSCH can use. HSDPA enables the HSDPA UE to share the channel codes dynamically scheduled by the NodeB.
The codes are reserved for the common channels and the HS-SCCH.
SF=16
Figure 1.1 Static codes allocation Configure the parameters of the codes reserved for the HSDPA by the RNC in [Code Number for HS-PDSCH] and [Code Number for HS-SCCH] on the OMC.
Note: In practical use, determine the codes to be reserved for the HS-PDSCH and HSSCCH by the performance measurement data (the long-term average cell handling capacity).
In the RNC-controlled dynamic allocation, the RNC adjusts the reserved HS-PDSCH codes according to the real-time usage status of the codes. Configure the maximum and minimum numbers of codes available for HS-PDSCH on the RNC OMC.The codes between the two parameters are called shared codes. See Figure 1.1.
Code reserved for common channel SF=16 Max number of codes Codes available for DPCH Min number of codes Codes reserved for HS- PDSCH
Shared codes
Figure 1.1 Shared codes The RNC monitors how the codes are allocated in real time and extends or reduces the codes reserved for the HS-PDSCH. 2) Extending the codes reserved for the HS-PDSCH
The RNC adds a code to the codes reserved for the HS-PDSCH in the following case:
There are idle codes in the DPCH. Among the idle codes, the shared code whose SF is 16 is neighboring to the reserved codes for the HS-PDSCH.
Shared codes
Note: In Figure 2.1, the solid dots represent the occupied codes and the circles represent the idle codes.
3)
The RNC releases the minimum shared codes reserved for the HS-PDSCH to the DPCH when the codes of the DPCH are not enough. See Figure 3.1.
Code reserved for common channel +HS-SCCH SF=16 Shared codes
Note: In Figure 3.1 the solid dots represent the occupied codes and the circles represent the idle codes.
4)
In fully dynamic allocation, the RNC does not reserve codes for HS-PDSCH. Instead, the NodeB allocates codes for the HS-PDSCH according to the usage status of cell
codes. The NodeB manages the virtual codes whose SF is 16 and marks each code with a status: occupied, idle, and temporarily occupied. See Table 1.1. Table 1.1 Meaning of the virtual code status
Status Meaning
Occupied
If a code or one of its sub-codes is allocated to the DPCH, this code is called occupied.
If a code of its sub-codes is not used, this code is idle. In each MAC-hs scheduling period, the NodeB searches for the maximum idle code that will be allocated to the HS-PDSCH in the next period. This code is marked temporarily occupied. If this code is released, it will be re-marked idle.
SF=16
Used code
Idle code
Temporarily code
Figure 4.2 Marks of the virtual codes status This mode might cause code conflict. When the RNC allocates a code for the DPCH through NBAP at the Iub interface, this code might be in temporarily occupied state. In this case, the NodeB will release this code in the next scheduling period.
The RNC allocates codes in ascending order for the DPCH. The NodeB allocates codes in descending order for the HS-PDSCH. When a code allocated to the DPCH with a smaller number is released, the RNC will adjust the code tree and use it to replace the code of a bigger number. This helps to avoid code idle state.
HSDPA Cell HSDPA Power Control HSDPA Channel Switch HSDPA Mobility Management Error: Reference source not found
I. HSDPA UE
When the UE initiates an access request, the RNC maps the service to a certain type of transmission channel based on some rules. Then, the RNC determines whether to grant the access. For relevant information of channel mapping, see "1.4.4HSDPA Channel Mapping. Table 1.1 lists two types of UEs depending on whether the HS-DSCH carries any service.
Table 1.1 Admission control for the HSDPA UE and R99 UE If The is The HS-DSCH carries some services HSDPA UE As shown in II. 1Table 1.1, it consists of three procedures. The UE access will succeed only if it passes all the procedures. Otherwise, the system attempts to let the UE access over the DPCH. The HS-DSCH carries no service R99 UE It is the same as the process of R99 cell access. UE called Admission control process
I. Overview
There are three types of channels in HSDPA:
The HSDPA power control is about the power control on these three channels.
the highest priority as shown in 4Table 1.1. Then the scheduling algorithm distributes power for the HS-PDSCH based on the data flow of the queue. 4) If there is any power left, the scheduling algorithm repeats step 2) for the queue with the second highest priority, until the total power of the DL HSDPA is used up. There are two exclusive ways to distribute the power to the HS-SCCH, as shown in Table 1.1. Select one way in [HS-SCCH Power control parameter] on the OMC. Table 1.1 Two ways of power control of the DL HS-SCCH Description The total transmission power of the HSSCCH is fixed. Evaluation Easy to implement More consumed power Parameters [HS-SCCH Power is control parameter] is used to set the
-
Configuration
Suitable in the early transmission phase of HSDPA power of the HSapplication to 2 There is an offset between the HSSCCH and the associated DPCH. The offset values are different for the handover area and the non-handover area. More complex Higher power utility [HS-SCCH Power offset for SFi] and [HS-SCCH Power offset for SFi multiRLS] i = 4, 8, 16, 32, 64, 128, 256 Reserve some power Set bigger offset power for the soft handover area. when HS- SCCH. SCCH code number is 1
CELL_DCH
CELL_PCH
CELL_FACH
CELL_DCH
(with HS-DSCH)
Figure 1.1 Different status of the RRC of the UE See Table 1.1 for the influences of HSDPA handover has on the types of the channel. Table 1.1 Channel type transition after introducing the HSDPA UE state transition CELL_DCH (with HS-DSCH) CELL_DCH Channel switching HS-DSCH DCHin handover stage CELL_DCH (with HS-DSCH) CELL_FACH HS-DSCH FACH
The HS-DSCH carries the BE service for the UE. There is no data flow of any of the services for a certain length of time.
Note: Set the length of time during which there is no data flow in [DCH to FACH transition timer] on the OMC.
On the other hand, when the data flow gets more active, for example, when the RNC receives a 4a event measuring report, the UE is switched from the FACH to the HSDSCH.
UE moves from a R99 cell to an HSDPA cell. UE moves from the HSDPA cell to a R99 cell.
When a HSDPA UE moves from a R99 cell to a HSDPA cell, if it is suitable to bear the service on the HS-DSCH, the RNC will add the HSDPA cell into the active set and then trigger the channel switching to assign the service to the HS-DSCH.
The similarity of the HSDPA handover and DPCH handover lies in that they are based on the measurement report of the UE and controlled by the network. If the UE has both the HSDPA and the DPCH connections, the measurement and the handover decision are made separately. The following text describes the HSDPA handover, including:
HSDPA cellR99 cell HSDPA cell HSDPA cell HSDPA cellGSM/GPRS cell
1)
Scenarios
Table 1.1 lists the four scenarios of handover between the HSDPA cell and R99 cell. Table 1.1 Scenarios of handover between the HSDPA cell and R99 cell No. 1 The The UE 1b Scenario moves from an or 1c event is Description The RNC sets the HSDPA connection to the DPCH of the R99 cell.
HSDPA cell to a R99 cell. triggered. The HSDPA cell is deleted from the active set. 2 The UE moves from an
The RNC sets the UE on the DPCH of the R99 cell through hard handover. If the HS-PDSCH is suitable to carry the service of the UE, the RNC switches the service to the HS-PDSCH of the HSDPA cell.
HSDPA cell to a R99 cell. The 2x event is triggered. 3 The UE moves from a R99 cell to an HSDPA cell. The 1x event is triggered. The HSDPA cell is added to the active set. 4 The UE moves from a R99 cell to an HSDPA cell. The 2x event is triggered.
The RNC sets the UE to the HSDPA cell through hard handover. If the HS-PDSCH is suitable to carry the service of the UE, the RNC switches the service to the HS-PDSCH of the HSDPA cell.
(HSDPA) to cell 2 (R99). Cell 1 is the only HSDPA cell in the active set and cell 2 and cell 1 are intra-frequency neighboring cells.
Cell 1(HSDPA) Cell 2(R99) Cell 2(R99)
Cell 1(HSDPA)
after handover
Figure 2.1 Soft handover between the HSDPA and R99 cell (HSDPA R99) When the UE moves, the 1b event is triggered if the signal quality of cell 1 is poor enough to be deleted and then the 2A event is triggered. To ensure the continuity of the service, the HSDPA connection between the UE and cell1 is switched to the DPCH of cell 2. 3) Scenario 2
Figure 3.1 is an example of scenario 2. Suppose the UE is moving from cell 1 (HSDPA) to cell 2 (R99) that is the inter-frequency neighboring cell of cell 1.
Cell 1(HSDPA) Cell 2(R99) Cell 1(HSDPA) Cell 2(R99)
after handover
Figure 3.1 Hard handover between the HSDPA and R99 cells (HSDPA R99)
When the UE moves, if the UE switches from cell 1 to cell 2 through hard handover, the services carried by the HSDPA in cell 1will be switched to the DPCH of cell 2.
Note: The HSDPA handover decision is based on the measurement report of the pilot channels of neighboring cells.
4)
Scenario 3
Figure 4.1 is an example of scenario 3. Suppose the UE is moving from cell 2 (R99) to cell 1 (HSDPA) that is the intra-frequency neighboring cell of cell 1. The DPCH of cell 2 carries the BE service of the UE.
Cell 1(HSDPA) Cell 2(R99) Cell 1(HSDPA) Cell 2(R99)
after handover
Figure 4.1 Soft handover between the HSDPA and R99 cells (R99 HSDPA) When the UE moves, if the quality of the signals in cell 1 is good, the 1a event will be triggered. The UE adds cell 1 to the active set and sets up a DPCH connection to cell 1. If it is suitable for the HS-PDSCH to carry the BE service, the service will be switched from the DPCH to the HS-PDSCH after handover. 5) Scenario 4
Figure 5.1 is an example of scenario 4, which supposes that UE is moving from cell 2 (R99) to cell 1 (HSDPA). Cell 1 is the inter-frequency neighboring cell of cell 2. The DCH of cell 2 carries the BE service of the UE.
Cell 1(HSDPA)
Cell 2(R99)
Cell 1(HSDPA)
Cell 2(R99)
after handover
Figure 5.1 Hard handover between the HSDPA and R99 cells (R99 HSDPA) When the UE moves, if the quality of the signals of cell 1 is good, inter-frequency handover will be triggered and the UE switches from cell 2 to cell 1. For better quality, the BE will be switched from the DPCH to the HS-PDSCH.
Note: When the UE moves from a R99 cell to an HSDPA cell, the BSC6800 hands over the UE in the following sequence:
Inter-cell handover (intra-frequency soft handover, hard handover or interfrequency hard handover) for the DPCH UE. The RNC sets the data service on the HS-PDSCH if suitable.
An HSDPA to HSDPA handover may occur only when there are at least two HSDPA cells in the active set. Table 1.1 lists the common scenarios.
Table 1.1 Scenarios of handover between two HSDPA cells No. 1 Scenario When the UE moves and another cell becomes the cell of the best signal quality, 1d event is triggered. 2 When the UE moves, inter-frequency handover is triggered and the target cell is the HSDPA cell. 3 When the UE moves, when the cell that provides the HSDPA service for the UE is deleted, 1b event is triggered. Hard handover the UE to the target HSDPA cell. Set the HSDPA connection in the HS-PDSCH of the target cell. Update the HSDPA cell. Set the HSDPA connection in the HSPDSCH of the target cell. The RNC will Update the HSDPA connection of the UE to the target HSDPA cell.
Figure 2.1 is an example of scenario 1. Suppose the UE is moving from cell 1 (HSDPA) to cell 2 (HSDPA) that is the intra-frequency neighboring cell of cell 1.
Cell 1(HSDPA) Cell 2(HSDPA) Cell 1(HSDPA) Cell 2(HSDPA)
after handover
Figure 2.1 Soft handover between two HSDPA cells (the best cell changes)
When the UE moves and another cell becomes the cell of the best signal quality, 1d event is triggered. The RNC will switch the HSDPA connection from cell 1 to cell 2.
Note: To avoid the ping-pong update at the boundary of the two HSDPA cells, set the [HSDPA hysteresis timer length] on the OMC. The UE can update the HSDPA serving cell again only after the time expires.
3)
Scenario 2
Figure 3.1 is an example of scenario 2. Suppose the UE is moving from cell 1 (HSDPA) to cell 2 (HSDPA) that is the inter-frequency neighboring cell of cell 1.
Cell 1(HSDPA) Cell 2(HSDPA) Cell 1(HSDPA) Cell 2(HSDPA)
after handover
Figure 3.1 Hard handover between HSDPA cells When the UE moves, inter-frequency is triggered if the quality of cell 2 is good enough. While the UE is moving, if the signals are good in cell 2, the handover event is triggered. The UE is handed over from cell 1 to cell 2. Meanwhile, the HSDPA connection of the UE is set up on the HS-PDSCH.
Note: The triggers and conditions of hard handover of the HSDPA cell are the same as those of the R99 cell.
4)
Scenario 3
Figure 4.1 is an example of scenario 3. Suppose the UE is moving from cell 1 (HSDPA) to cell 2 (HSDPA) that is the intra-frequency neighboring cell of cell 1.
Cell 1(HSDPA) Cell 2(HSDPA) Cell 1(HSDPA) Cell 2(HSDPA)
after handover
Figure 4.1 Soft handover between HSDPA cells (HSDPA service cell is deleted from active set) While the UE is moving, the HSDPA cell (cell 1) may be deleted from the active set due to the poor quality of signals. This triggers the 1b event. The HSDPA connection is set on the HS-PDSCH of the best HSDPA cell (cell 2) in the active set.
Coverage
The initial UMTS network cannot continuously cover the area. The UE is handed over to the GSM/GPRS when it is at the boundary of the network or the quality of the signal is poor.
Services
Fully utilize the network and expand the system capacity by handing over the services (for example, voice) to the GSM/GPRS network. 2) Handover procedures
Real-time services: handover procedure from the UMTS to the GSM/GPRS of the CS services (The PS services interrupt after handover.) Non-real-time services: handover procedure from the UMTS to the GSM/GPRS
Huawei Technologies Proprietary 37
of the PS services 3) Handover procedure from the UMTS to the GSM/GRPS of the CS services The handover procedure from the UMTS to the GSM/GPRS of the CS services is as shown in Figure 3.1.
UE NodeB SRNC CN MSC BSC
1. Relocation Required
RANAP RANAP
MAP/E
2. Prepare Handover
MAP/E
3. Handover Request
BSSMAP BSSMAP
6. Relocation Command
RANAP RANAP
9. Handover Complete
BSSMAP BSSMAP
Figure 3.1 Handover procedure from the UMTS to GSM/GPRS of the CS services 4) Handover procedure from the UMTS to the GSM/GRPS of PS services
The handover procedure from the UMTS to the GSM/GPRS of the PS services is as shown in Figure 4.1.
UE SRNC CN
1. Cell Change Order from UTRAN RRC RRC 2. Iu Release Command RANAP 3. Iu Release Complete RANAP RANAP RANAP
Figure 4.1 Handover procedure from the UMTS to the GSM/GPRS of the PS services
1.6 Implementation
1.6.1 Engineering Guidelines
I. Hardware Installation
The HSDPA algorithm module is integrated in RNC and NodeB. It does not need extra hardware support.
2) 3) 4) 5)
Check the existence of the data of the cell through LST CELL. Add HSDPA parameters to the cell through ADD CELLHSDPA. Activate the HSDPA service through ACT CELLHSDPA. (Optional) Change the HSDPA data by commands listed in 1.6.2 I. 1Table 1.218 upon practical requirements of network planning or optimization.
Note: For all of the parameters, there are default value which be verified and optimized in field test, and can be used in commercial network, in the special scene some parameters based on the cell shall be optimized further.
Data configuration commands for RNC-oriented HSDPA, as listed in Table 1.117 Data configuration commands for cell-oriented HSDPA, as listed in Table 1.218
Table 1.1 Configuration commands for RNC-oriented HSDPA (on RNC side)
Function Command
SET HSSCCH
Function
Command
List RNC-oriented HSSCCH power control algorithm parameters. Configure RNC-oriented HS-DPCCH power control algorithm parameters. Set RNC-oriented HSDPCCH power control algorithm parameters. List RNC-oriented HSDPCCH power control algorithm parameters. Configure algorithm switches related to HSDPA: [HSDPA_DRD_SWITCH] [HSDPA_STATE_TRANS_SWITCH] Set the connectionoriented algorithm switches. List the connectionoriented algorithm switches. Configure the FRC parameters of HSDPA: [DLSTRTHSONHSDPA] [DLBETRAFFTHSONHSDPA] Set the RNC-oriented FRC algorithm parameters. List the RNC-oriented FRC algorithm parameters. Configure [HSDPATIMERLEN] Set RNC-oriented handover algorithm common parameters. List RNC-oriented handover algorithm common parameters.
LST HSSCCH
SET HSDPCCH
LST HSDPCCH
LST FRC
SET HOCOMM
LST HOCOMM
Table 1.2 Configuration commands for cell-oriented HSDPA (on RNC side)
Function Command
Function
Command
Remove cell HSDPA parameters. Activate cell HSDPA parameters. Deactivate cell HSDPA parameters. List cell HSDPA parameters. Configure cell-oriented HS-SCCH power control algorithm parameters. Add cell-oriented HS-SCCH power control algorithm parameters. Modify cell-oriented HS-SCCH power control algorithm parameters. Remove cell-oriented HSSCCH power control algorithm parameters. List cell-oriented HS-SCCH power control algorithm parameters. Configure cell-oriented HSDPCCH power control algorithm parameters. Add cell-oriented HS-DPCCH power control algorithm parameters. Modify cell-oriented HSDPCCH power control algorithm parameters. Remove cell-oriented HSDPCCH power control algorithm parameters. List cell-oriented HS-DPCCH power control algorithm parameters.
RMV CELLHSDPA
ACT CELLHSDPA
DEA CELLHSDPA
MOD CELLHSSCCH
RMV CELLHSSCCH
LST CELLHSSCCH
ADD CELLHSDPCCH
MOD CELLHSDPCCH
RMV CELLHSDPCCH
LST CELLHSDPCCH
Function
Command
Add cell-oriented CAC algorithm parameters. Modify cell-oriented CAC algorithm parameters. Remove cell-oriented CAC algorithm parameters. List cell-oriented CAC algorithm parameters.
ADD CELLCAC
MOD CELLCAC
RMV CELLCAC
LST CELLCAC
Key parameters of initial configuration Channel class parameters CAC parameters Power control parameters Handover parameters
CELLID
Cell ID
HSPDSCHCODENU M
HSSCCHCODENUM
HSDPAPOWER
Value range: 0500. Physical value range: 050: Step: 0.1 dB. Content: Max sum of HS_PDSCH power and HS_SCCH power. Physical unit: dBm. Default value: 430. Recommended value:430outdoor 380indoor
HSPDSCHMPOCON STENUM
Value range: -0.5dB, 0.5dB, 1.5 dB, 2.5dB, 3.5dB, 4.5dB, 5.5dB Content: Measure Power Offset Constant is used to compute Measure Power Offset. Measure Power Offset = Min (13,CellMaxPower - PcpichPower - Measure Power Offset Constant) Physical unit: dB. Default value: 2.5.
SET CORRMALGOSWITCH, see its parameters in Table 1.121. SET FRC, see its parameters in Table 1.222.
Value range:ENUMERATED (DISABLE~0, ENABLE~1) Content:When it is checked,UEs RRC state can be transferred from HSDPA state to CELL_FACH state Recommended: DISABLE
HSDPA_DRD_SWITC H
Value range: DISABLE0, ENABLE1 Content: When it is checked and DRD_SWITCH is checked, DRD will be applied for high speed traffic when current cell are not support HSDPA. Recommended: DISABLE
PS_STREAMING_ON _HSDPA_SWITCH
Value range: DISABLE0, ENABLE1 Content: When it is checked, PS streaming traffic can be mapped to HS-DSCH when the downlink max bit rate is more than or equal to the streaming on HSDPA threshold. Recommended: DISABLE
DLSTRTHSONHSDP A
Value range: D8, D16, D32, D64, D128, D144, D256. Physical value range: 8, 16, 32, 64, 128, 144, 256. Physical unit: kbit/s. Content: The rate decision threshold of DL PS domain streaming service to be carried on HS-DSCH. When the maximum DL service rate is greater than or equal to this threshold, the service will be carried on HSDSCH; otherwise, on DCH. Default value: D64. Recommended value:D256.
DLBETRAFFTHSON HSDPA
Value range: D8, D16, D32, D64, D128, D144, D256, D384, D768, D1024, D1536, D2048. Physical value range: 8, 16, 32, 64, 128, 144, 256, 384, 768, 1024, 1536, 2048. Physical unit: kbit/s. Content: The rate decision threshold of DL PS domain background/interactive service to be carried on HSDSCH. When the maximum DL service rate is greater than or equal to this threshold, the service will be carried on HS-DSCH; otherwise, on DCH. Default value: D8. Recommended value:D768.
ULHSDPCCHRSVDF ACTOR
Value range: 0100. Physical unit: 01; step: 0.01. Content: If the HS-DPCCH is to carry ACK/NACK, the system will not perform CAC. If the HS-DPCCH is to carry CQI, the system will perform CAC. The corresponding threshold of this parameter equals the product of UL limit capacity and this parameter value. Default value: 0.
HSDSCHGBRTHD
Value range: 0100. Physical unit: 01; step: 0.01. Content: On the HS-DSCH, the access of guaranteed service is based on power forecast. This parameter defines the ratio of admission threshold of guaranteed service to total power of HS-DSCH. Default value: 60.
HSDSCHBETHD
Value range: 01000. Physical unit: 01; step: 0.001. Content: On the HS-DSCH, the access of BE service is based on serving probability. If the probability of an admitted user being served is lower than this threshold, this user will not be set up on the HSDSCH. Default value: 50.
MAXHSDSCHUSERN UM
Value range: 0100. Content: Max number of users supported by HSDPA channel. Default value: 70. Recommended value:16.
SET HSSCCH, see its parameters in Table 1.124. ADD CELLHSSCCH, see its parameters in Table 1.124. SET HSDPCCH, see its parameters in Table 1.225. ADD CELLHSDPCCH, see its parameters in Table 1.2.
Table 1.1 HSDPA power control parameters of SET HSSCCH and ADD CELLHSSCCH commands.
ID Name Description
HSSCCHPOFO RSF4
Value range: 128 to 127. Physical value range: 32 to 31.75. Physical unit: dB. Content: HSSCCH power offset from DL DPCCH PILOT bits when the spreading factor (SF) of DL DPCH is 4. Default value: -43.
HSSCCHPOFO RSF4SHO
Value range: 128 to 127. Physical value range: 32 to 31.75. Physical unit: dB. Content: HSSCCH power offset from DL DPCCH PILOT bits when the SF of DL DPCH is 4 with multi RLS. Default value: -27.
ID
Name
Description
HSSCCHPOFO RSF8
Value range: 128 to 127. Physical value range: 32 to 31.75. Physical unit: dB Content: HSSCCH power offset from DL DPCCH PILOT bits when the SF of DL DPCH is 8. Default value: -31.
HSSCCHPOFO RSF8SHO
Value range: 128 to 127. Physical value range: 32 to 31.75. Physical unit: dB. Content: HSSCCH power offset from DL DPCCH PILOT bits when the SF of DL DPCH is 8 with multi RLS. Default value: -15.
Omit parameters:
[HSSCCHPOFORSF16], [HSSCCHPOFORSF16SHO] [HSSCCHPOFORSF32], [HSSCCHPOFORSF32SHO] [HSSCCHPOFORSF64], [HSSCCHPOFORSF64SHO] [HSSCCHPOFORSF128], [HSSCCHPOFORSF128SHO] [HSSCCHPOFORSF256], [HSSCCHPOFORSF256SHO]
These parameters also belong to SET HSSCCH and ADD CELLHSSCCH commands. The descriptions of these parameters are similar to those listed above.
Table 1.2 HSDPA power control parameters of SET HSDPCCH/ADD CELLHSDPCCH command
ID Name Description
SIRTARGET
Value range: 0255. Physical value range: -8.2 to 17.3; step: 0.1. Physical unit: dB. Content: Initial value of DPCCH SIR. It is used as the reference value for configuring the parameters of HSDPCCH power control algorithm. Default value: 112.
ID
Name
Description
ACKPO1
ACK poweroffset1
Value range: PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15, PO_15/15, PO_19/15, PO_24/15, PO_30/15. Physical value range: 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15, 30/15. Content: ACK power offset from UL DPCCH when the Minimum inter-TTI interval in UE capability information is 1. Default value: PO_19/15.
ACKPO1FORS HO
Value range: PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15, PO_15/15, PO_19/15, PO_24/15, PO_30/15. Physical value range: 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15, 30/15. Content: ACK power offset from UL DPCCH when the Minimum inter-TTI interval in UE capability information is 1 and the UE is with multi RLS. Default value: PO_24/15.
ACKPO2
ACK poweroffset2
Value range: PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15, PO_15/15, PO_19/15, PO_24/15, PO_30/15. Physical value range: 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15, 30/15. Content: ACK power offset from UL DPCCH when the Minimum inter-TTI interval in UE capability information is 2. Default value: PO_12/15.
ACKPO2FORS HO
Value range: PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15, PO_15/15, PO_19/15, PO_24/15, PO_30/15. Physical value range: 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15, 30/15. Content: ACK power offset from UL DPCCH when the Minimum inter-TTI interval in UE capability information is 2 and the UE is with multi RLS. Default value: PO_24/15.
ID
Name
Description
ACKPO3
ACK poweroffset3
Value range: PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15, PO_15/15, PO_19/15, PO_24/15, PO_30/15. Physical value range: 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15, 30/15. Content: ACK power offset from UL DPCCH when the Minimum inter-TTI interval in UE capability information is 3. Default value: PO_9/15.
ACKPO3FORS HO
Value range: PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15, PO_15/15, PO_19/15, PO_24/15, PO_30/15. Physical value range: 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15, 30/15. Content: ACK power offset from UL DPCCH when the Minimum inter-TTI interval in UE capability information is 3 and the UE is with multi RLS. Default value: PO_24/15.
NACKPO1
NACK poweroffset1
Value range: PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15, PO_15/15, PO_19/15, PO_24/15, PO_30/15. Physical value range: 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15, 30/15. Content: NACK power offset from UL DPCCH when the Minimum inter-TTI interval in UE capability information is 1. Default value: PO_19/15.
NACKPO1FOR SHO
Value range: PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15, PO_15/15, PO_19/15, PO_24/15, PO_30/15. Physical value range: 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15, 30/15. Content: NACK power offset from UL DPCCH when the Minimum inter-TTI interval in UE capability information is 1 and the UE is with multi RLS. Default value: PO_24/15.
ID
Name
Description
NACKPO2
NACK poweroffset2
Value range: PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15, PO_15/15, PO_19/15, PO_24/15, PO_30/15. Physical value range: 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15, 30/15. Content: NACK power offset from UL DPCCH when the Minimum inter-TTI interval in UE capability information is 2. Default value: PO_12/15.
NACKPO2FOR SHO
Value range: PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15, PO_15/15, PO_19/15, PO_24/15, PO_30/15. Physical value range: 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15, 30/15. Content: NACK power offset from UL DPCCH when the Minimum inter-TTI interval in UE capability information is 2 and the UE is with multi RLS. Default value: PO_24/15.
NACKPO3
NACK poweroffset3
Value range: PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15, PO_15/15, PO_19/15, PO_24/15, PO_30/15. Physical value range: 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15, 30/15. Content: NACK power offset from UL DPCCH when the Minimum inter-TTI interval in UE capability information is 3. Default value: PO_9/15.
NACKPO3FOR SHO
Value range: PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15, PO_15/15, PO_19/15, PO_24/15, PO_30/15. Physical value range: 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15, 30/15. Content: NACK power offset from UL DPCCH when the Minimum inter-TTI interval in UE capability information is 3 and the UE is with multi RLS. Default value: PO_24/15.
ID
Name
Description
ACKNACKREF 1
Value range: 14. Content: Number of ACK/NACK retransmissions when the Minimum inter-TTI interval in UE capability information is 1. Default value: 1.
ACKNACKREF 2
Value range: 14. Content: Number of ACK/NACK retransmissions when the Minimum inter-TTI interval in UE capability information is 2. Default value: 2.
ACKNACKREF 3
Value range: 14. Content: Number of ACK/NACK retransmissions when the Minimum inter-TTI interval in UE capability information is 3. Default value: 3.
ACKNACKREF FORSHO
Value range: 14. Content: Number of ACK/NACK retransmissions with multi RLS. Default value: 3.
CQIPO
Value range: PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15, PO_15/15, PO_19/15, PO_24/15, PO_30/15. Physical value range: 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15, 30/15. Content: CQI power offset from UL DPCCH. Default value: PO_12/15.
CQIPOFORSH O
Value range: PO_5/15, PO_6/15, PO_8/15, PO_9/15, PO_12/15, PO_15/15, PO_19/15, PO_24/15, PO_30/15. Physical value range: 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15, 30/15. Content: CQI power offset from UL DPCCH with multi RLS. Default value: PO_12/15.
CQIREF
ID
Name
Description
CQIREFFORSH O
Value range: 14. Content: Number of CQI retransmissions with multi RLS. Default value: 3.
CQIFBCK
Value range: D0, D2, D4, D8, D10, D20, D40, D80, D160. Physical value range: 0, 2, 4, 8, 10, 20, 40, 80, 160. Physical unit: ms. Content: CQI feedback cycle. Default value: D2.
CQIFBCKFORS HO
Value range: D0, D2, D4, D8, D10, D20, D40, D80, D160. Physical value range: 0, 2, 4, 8, 10, 20, 40, 80, 160. Physical unit: ms. Content: CQI feedback cycle with multi RLS. Default value: D8.
Note:
When configuring HS-SCCH power control parameters, if the power of HS-SCCH is adjusted dynamically, set the offset of HS-SCCH power from DPCH power. For handover and nonhandover areas, set different power offsets for HS-SCCH.
During a soft handover, different links are combined, for example, the maximum PILOT rate of the DL DPDCH is combined with that of DL DPCCH. Increase the power offset of HS-SCCH in this case, especially when the HS-SCCH is carried by links of big path loss. That is, set [HSSCCHPOFORSF i] smaller than [HSSCCHPOFORSF4SHO] (i = 4, 8, 16, 64, 128, 256).
HSDPATIMERLEN
Value range: 01024. Physical unit: s. Content: HSDPA handover is triggered by event 1D. To avoid frequency handover from affecting the system performance, a protection timer TimerHSDPA is needed. After event 1D triggers HSDPA handover, this timer is started. Then, event 1D will not trigger HSDPA handover any more before expiry of this timer. The value 0 means this timer is not started; that is, HSDPA handover is trigger immediately. The value 1024 means HSDPA handover will not be triggered before the cell bearing the HSDPA service is removed. Default value: 0. Recommended value:30.
LOCELL
Local Cell ID
It refers to Local Cell ID. Value range: 0~268435455 Default value: None
SM
Scheduling Method
Scheduling Method Value range: PF (PF), RR (Round Robin), MAXCI (Max C/I) Default value: PF
MXRETRAN
ID
Name
Description
PWRMGN
Power Margin(%)
PWRFLG
It refers to the HS-SCCH power is fixed or dynamic. Value range: FIXED (Fixed), DYNAMIC (Dynamic) Default value: FIXED
PWR
This parameter is valid when the HS-SCCH power uses the fixed value, indicating the percentage of HS-SCCH fixed power to total cell transmit power. Value range: 0~20 Default value: 5
IBLER
Initial BLER(%)
4)
1.7 Maintenance
1.7.1 Related Alarms
Table 1.128 lists alarms related to the HSDPA. Table 1.1 Alarms related to HSDPA
AlarmID AlarmName
Cell HSDPA Setup Failed Cell HSDPA Reconfiguration Failed Cell HSDPA Delete Failed Cell HSDPA Unavailable
VS.HSDPA.MACDSuccStpPerCell
VS.HSDPA.MACDSuccDelPerCell VS.HSDPA.MACDFailStpPerCell
VS.HSDPA.MACDFailDelPerCell
VS.HSDPA.ChR.DCHtoHSDSCH
Number of Successful Handovers from DCH to HSDSCH Number of Successful Handovers from FACH
VS.HSDPA.ChR.FACHtoHSDSCH
to HSDSCH
Item
Description
VS.HSDPA.ChR.HSDSCHtoDCH
Number of Successful Handovers from HSDSCH to DCH Number of Successful Handovers from