Escolar Documentos
Profissional Documentos
Cultura Documentos
Feature Guide
Date
Author
Approved By
Remarks
V4.0
2010-6-13
Wang Yue
Peng Bei, Hu Ye
th
TABLE OF CONTENTS
1
2
2.1
2.1.1
2.1.2
Overview .............................................................................................................1
Function Introduction ............................................................................................1
HSUPA Fast Scheduling .......................................................................................2
HSUPA Flow Control ............................................................................................6
3
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.2
3.2.1
3.2.2
4
4.1
4.2
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.2.6
4.2.7
4.2.8
4.2.9
5
5.1
5.2
Glossary ...........................................................................................................26
II
FIGURES
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
Figure 10
TABLES
Table 1
III
Functional Attribute
System version: [RNC V3.09, Node B V4.09, OMMR V3.09, OMMB V4. 09]
Attribute: [Optional]
Involved NEs:
MS
Node B
RNC
MSC
MGW
SGSN
GGSN
HLR
Note:
*-: Not involved.
*: Involved.
Dependency: [None]
Mutual exclusion: [None]
Remarks: [None]]
Overview
2.1
Function Introduction
The High Speed Uplink Packet Access (HSUPA) is a technology used in WCDMA to
enhance uplink transmission capability.
HSUPA technology features shorter Transmission Time Interval (TTI), Node B-based
scheduler and Hybrid Automatic Retransmission Request (HA RQ), and new transport
channel-Enhanced Dedicat e Channel (E-DCH).
The adoption of the HSUPA technology brings the following advantages to the WCDMA
system:
The WCDMA system adopting the HSUPA technology consists of the Radio Network
Cont roller (RNC), Node B and Us er Equipment (UE). Node B contains several cells
which are a type of public radio resource serving UEs in the same area. The uplink load
of system can be measured through cells in HSUPA. The UE scheduling by Node B is
cell-based. The HSUPA technology leaves service control and scheduling functions to
Node B. Node B sends different grants to UE based on service scheduling information,
buffer occupancy status, service priority, UE Uplink Power Headroom (UP H), cell uplink
interference and load, and Node B processing capacity. UE sends data in response to
the grants from Node B.
The HSUPA packet scheduler contains two parts: HS UPA fast scheduling and flow
control, which are respectively detailed as follows:
2.1.1
Figure 1
DTCH DCCH
DTCH DCCH
MAC-d
MAC-d
MAC-es
MAC-es/MAC-e
MAC-e
EDCH
FP
Uu
EDCH FP
Iub
PHY
PHY
UE
NODEB
TNL
Iur
TNL
TNL
DRNC
TNL
SRNC
Compared with R99, the functional changes of all protocol entities in HSUPA are as
follows:
UE: New MAC entity (MAC-es/MAC-e) is added under MAC-d. MAC- es/MAC-e
implements such functions as HA RQ, scheduling, MAC-e multiplexing and E-DCH
TFC selection.
Figure 2 shows the protocol block diagram of MA C-e (Node B side) where the HS UPA
scheduler is located.
Figure 2
MAC-e functions
MAC-d Flows
MAC-e
MAC Control
E-DCH
Scheduling (FFS)
E-DCH
Control (FFS)
De-multiplexing
HARQ
Associated
Uplink
Signalling
Associated
Downlink
Signalling
E-DCH
The functions of various modules of MAC-e (Node B side) are described as follows:
E-DCH scheduling: Manage E-DCH among UEs. Determine and transmit grants
based on scheduling request.
HARQ: One HA RQ entity supports several Stop -and-Wait (SAW) HARQ process
instances. Each HARQ proc ess generates ACKs or NACKs to indicate the transmit
status of E-DCH. The HARQ used in HS UPA is a multi-channel SAW concurrent
retransmission mechanism. The HA RQ supports several HARQ processes, each of
which transmits data packets in sequence. For one UE, there is only one HA RQ
process transmitting data at one moment. If Node B receives a data packet from
one HA RQ process and the Cyclic Redundancy Check (CRC) is passed, Node B
will return a correct decoding indication (ACK); otherwise, it will return a block error
indication (NACK). If UE rec eives a NACK message, the related HA RQ process
needs to retransmit the data packet at physical layer; if UE receives an ACK
message, the related HARQ process can transmit a new data packet. At the same
time, other HA RQ proc esses can each transmit different data packets, irrespective
of whether the HARQ process receives ACK/NACK message. The adoption of
multi-channel HARQ lowers waiting time of SAW protocol and enhanc es
transmission rate. 3GPP defines 8 and 4 HARQ processes respectively for UE with
2ms and 10ms Transmission Time Intervals (TTIs) in HSUPA.
Figure 3
DRNC
MAC-d
FP
MAC-es
Iur/Iub FP
NodeBs
Iur/Iub FP
NodeBd
MAC-e
FP
MAC-e
Scheduler
MRC
MRC
E-HICH (ACK/NACKs)
E-RGCH (relative grants)
(ChCode, signature -> UE)
serving cell
E-AGCH
(Absolute Grants,
"E-RNTI" -> UE)
E-DPDCH
E-DPCCH
UE
MAC-e/
MAC-es
MAC-d
DTCHs
The above figure shows the connection relation bet ween UTRA N and UE that uses EDCH and stays in soft handover state, as well as HSUPA -related protocol entities on UE
and network sides. The basic concept and operating principle of HSUPA are described
as follows:
E-DCH active set: The set of cells which carry the E-DCH for one UE. .It can be a
subset of DCH active set.
Serving E -DCH cell: Refers to the cell from which the UE receives the absolute
grants. UE only has one E-DCH serving cell. The serving cell change is triggered
when UE reports event 1D triggered by downlink pilot channel quality.
Serving E -DCH RLS or Serving RLS: Set of Cells which contains at least the
Serving E-DCH cell and from which the UE can receive and combine one Relative
Grant. The UE has only one Serving E-DCH RLS.
Non-serving E-DCH RL or Non-Serving RL: Cell which belongs to the E -DCH active
set but does not belong to the Serving E-DCH RLS and from which the UE can
receive one Relative Grant. The Ue can have zero, one or several Non-serving EDCH RL(s).
UE has one Serving E-DCH cell. The Node B where the Serving E-DCH cell is
located implements E-DCH scheduling. The Serving E -DCH cell sends scheduling
instruction, that is, absolute grant, to UE over downlink E-AGCH. The absolute grant
stipulates the absolute value of the maximum available resources for UE.
The Serving E -DCH cell and non-serving E-DCH cell sends relative grant to UE
over downlink E-RGCH. As a fine tuning of the absolut e grant, the r elative grant can
take one of the three values: UP, DOWN and HOLD, instructing the UE to inc reas e,
decrease or not change the power limitation. Only the Serving E -DCH RLS can
send UP message and Non-Serving E-DCH RLS can only send HOLD or DOWN
message. Generally Non-Serving E -DCH RLS sends a DOWN message as a res ult
of uplink overload.
RNC may configure a percentage thres hold (non -serving RL E-DCH received
power/total E -DCH received power) for Node B over physical shared channel
reconfiguration. Node B stores this threshold and uses it to control E-DCH
scheduling to ensure the power proportion of non-serving RL E-DCHs to all E-DCH
received in the cell does not exceed this threshold. Node B decreases the power of
non-serving RL UE by sending a DOWN message to UE.
UE performs E-TFC selection based on the grant information received, sends data
(including retransmitted data) on E-DP DCH and sends E-TFC information, HA RQ
RV information (RSN) and one Happy Bit on E-DPCCH. The Happy bit is used to
notify Node B whether UE is satisfied with currently assigned res ourc es (grant), that
is, whether UE needs higher grants.
The E-DCH collects E-DCH data received by different cells under the same Node B
for MRC combination and sends it to Mac -e. Each UE has one MAC-e in every
Node B. MAC-e demultiplexes MAC-e PDUs into MAC-es PDUs before sending
them to RNC. Mac-e also sends E-DCH scheduling messages as well as HA RQ
ACK/NACK.
Each UE has one Mac-es entity in SRNC. Mac-es performs macro diversity
combination of MAC-es PDUs from different Node Bs and re-sequences and
disassembles them into Mac-d PDUs before sending them to Mac-d.
Handling of different grants by UE: UE may receive the AGs and RGs from the
serving cell as well as RG DOWN from non-serving cell at the same time. According
to 3GPP TS 25.321, when a UE receives grants from both serving and non-serving
E-DCH RLSs simultaneously, the Scheduling Grant (SG) of UE is set to the smaller
one of SGs calculated from non-serving and serving E-DCH RLS.
The HS UPA fast scheduling control function makes quick response to service
requirements of all UEs in a c ell, cell uplink interference and Node B processing load;
assigns SGs for all UEs; notifies UEs of available SGs by sending AGs or RGs to UEs.
UEs transmit data using the dat a rate and power allowed by SGs.
2.1.2
Technical Description
3.1
3.1.1
3.1.2
Figure 4
lub
De-mux
RNC
HARQ
E-DCH
UE
Associated
Uplink Schedule
Information
Uplink Processing
ACK/
NACK
AG
HSUPA
Scheduler
Uu
RG
Uu
E-HICH
Uu
E-AGCH
Uu
E-RGCH
Downlink
NodeB
UE is sent to Node B over UU interface. Upon det ecting the signal, Node B
performs transport layer processing including descrambling and despreading. The
E-DCH data packets and uplink-relat ed Scheduling Information (SI) are obtained
after transport layer processing. E-DCH data packets are sent to HARQ at MAC -e
layer for combining int o MAC-e PDUs. At the same time, HARQ generates ACK or
NACK indication based on combining results and sends it to UE on downlink EHICH. MAC-e PDUs are sent to demultiplexing entity for demultiplexing into MA Ces PDUs, and then sent to MAC-es layer of RNC over lub interface for further
processing.
HSUP A packet scheduling: The HS UPA packet scheduler offers a function that
meets uplink service requirements of all UEs in Node B by utilizing such information
as uplink load, UE service requirements and Node B processing capacity in
WCDMA system. The scheduler describes and classifies uplink service
requirements of UEs based on their urgency and priority. Then it allocates different
resources for UEs by means of fast control and scheduling to meet varied uplink
service requirements of UEs while ensuring effective utilization of uplink radio
resources.
The functions of all above modules are implemented in EBBUB/BBUB. Each UE has
one MAC-e entity in Node B. Each local cell group is configured with an HS UPA
scheduler. The HSUPA scheduling is cell-based.
3.1.3
Uplink Reference Rec eived Tot al Wide Band Power (RefRTWP) configured by RNC
through NBAP. (refer to ZTE UMTS Admission Control Feat ure Guide).
Target Non-serving E-DCH to Total E-DCH Power Ratio (NS ervToTotalP wr) (refer
to ZTE UTMS Overload Control Feature Guide).
Figure 5
HSUPA
NodeB->:RTWPcurrent,
CE resource
PS Scheduler
UE:AG, RG,
RNC->:
MaxRTWP, RefRTWP
NServToTotalPwr
RNC->: UE QoS parameters
SPIGBR
Non-scheduled BitRate
Figure 6
The key algorithm of the scheduler implements scheduling in the following steps:
1
Collect and update UE status, cell radio resource and Node B processing
information.
Collected information includes:
The SI reported by UE (including SI and happy bit, used to obtain buffer area
size and UP H of UE).
Current DPCCH and E-DCH signal quality of UE (SIR and Eb/No, reported by
the Baseband Processing Unit and used to calculate UE-contributed load. The
SIR Filter Period (40ms) is an internal parameter that cannot be configured.
For details, refer to ZTE UMTS Node B Interface Parameter Description).
CE resource indication.
Referenc e Received Total Wide Band Power ( Ref RTWP), Maximum Target
Received Total Wideband Power (MaxRTWP), Target Non-serving E-DCH to
Total E-DCH Power Ratio (NS ervToTotalP wr) configured by RNC through
NBAP.
Determine UE, air interface and Node B resource utilization and load:
The measurement unit of Node B meas ures air interface interference, and
sends the measurement result RTWP current to the scheduler. The scheduler
calculates current cell load Cell _Load_current and maximum target load Cell_Load_max
(unit: %) through the following equations:
RoT = Itotal/Pn
(1)
Cell_Load_current = 11/RoT
(2)
(3)
10
Where,
Itotal refers to the total rec eive bandwidth power inclusive of background noise power
(unit: mW) and takes the value of RTWP current . The RTWP Filter Period (40 ms) is an
internal parameter and cannot be configured. For det ails, see Node B Int erface
Parameter Description.
Pn refers to background noise and takes the value of RefRTWP (Reference
Received Total Wide Band Power). The original unit of P n is dBm and translated
into mW in the above equation. RNC notifies of Node B of Pn through NBAP after
internal measurement.
MaxRTWP refers to the Maximum Target Received Total Wideband Power. The
original unit of MaxRTWP is dBm and translated into mW in the above equation.
MaxRTWP is configured at combining and sent to Node B by RNC through NBAP.
RoT refers to Rise over Thermal. The original unit of RoT is dB, and converted into
dimensionless ratio during calculation.
The Uplink Process Unit of Node B demodulates E-DP DCH in each TTI to obtain
MAC-e PDU, SI and Eb/No, and sends MAC-e PDU multiplexing information to the
scheduler which calculates UE-contributed load in the following equation:
UEload = 1/(1+(W/((Eb/No)R)))
(4)
Where,
Itotal refers to the total rec eive bandwidth power inclusive of background noise power
(unit: mW) and takes the value of RTWP current.
W refers to WCDMA chip rate and equals to 3.84M chips/s.
Eb/No refers to per bit signal energy divided by noise power spectral density, and
reflects service signal quality. It is dimensionless
R refers to the bit rate of UE (unit: bits/s).
3
11
UEs with higher scheduling priorities will take precedence over UEs with lower ones
in preempting more resources, resulting in rate decrease for the latter. But UEs
originally with lower scheduling priorities are given higher scheduling priorities
because of their low transmission throughput, and thus they will be scheduled
preferentially to ensure fairness among all UEs.
The specific calculation procedure of scheduling priority is as follows:
th
The uplink throughput offered for UEs in past TTIs can be updated for all UEs in
each TTI by using the recursive expression:
Rn = (1-a)Rn-1 + aDn
(5)
Other cases:
Rn = (1-a)Rn-1
(6)
Where,
Rn-1 refers to the value of Rn in last TTI (Unit: bits/s).
R0 refers to the uplink rat e of UE at initial moment (Unit: bits/s).
Dn refers to available uplink transmission rate of UE (Unit: bits/s), and takes the
smallest one of the following values: Data size in UE buffer area, size of data that
can be transmitted in relation to the rest power of UE, and maximum rate limit of UE.
th
12
(8)
GBRweight = 0,
(9)
GBRweight = MaxGBRWeightValue,
(10)
When Streaming services are carried on E-DCH, RNC informs Node B of the
QoS parameter MA C-es Guaranteed Bit Rate (GBR) through NBAP.
Calculat e available cell load based on the cell and UE load obtained in steps 1
and 2 as well as Node B processing capacity.
Reserve load for R99 RT, R99 NRT, SRB and HS UPA non-scheduled
transmission services from the available cell load. (The scheduler thinks the
load cont ribut ed by these services is constant before or after scheduling).
13
If current available system load and CE resources are larger than the
summation of load contributed by all UE requested transmission rates, the
scheduler allocat es grants in relation to requested rates for all UEs.
If current available system load or CE resources are less than the summation
of load contributed by all UE requested transmission rates, the scheduler first
calculates the load and CE res ourc es contributed by the rate requested by the
UE with highest priority.
The scheduler releases grants of UEs with low priorities one by one in
ascending sequence of scheduling priorities. Then it calculates the load
contribut ed after releasing grants until the load and CE resources released
from UEs with low priorities meet the requirements of the UE with highest
priority. If the load released from UEs with low priorities still fails to meet all
requirements of the UE with highest priority, the UE with highest priority will
have to use the load and CE resources released from those with low priorities.
The scheduler allocates CE resources and load to the rest UEs with high
priorities in the queue by following the above rule until all system resources are
used up (all UEs with low priorities have their resources released).
Map load contribut ed by UEs into grants of UEs (the relation bet ween UE contribut ed load and grant is as follows):
UE Serving Grants refers to the ratio of available E-DCH t ransmit power to DP CCH
transmit power:
SG = P E-DCH,TX / PDPCCH,TX
(11)
Where,
PE-DCH,TX refers to E-DCH transmit power.
PDPCCH,TX refers to DPCCH transmit power.
DPCCH and E-DCH undergo the same fading process, and therefore, the relation
between receive powers of Node B DPCCH and E-DCH is given by the following
equation:
PE-DCH,RX / PDPCCH,RX = P E-DCH,TX / PDPCCH,TX
(12)
And,
PDPCCH,RX(1 + SG)= P DPCCH,RX + P E-DCH,RX
(13)
Where,
PE-DCH,RX refers to the receive power of E-DCH in Node B.
PDPCCH,RX refers to the receive power of DPCCH in Node B.
14
(14)
(15)
(16)
In the above equation, 256 refers to the processing gain of DP CCH. Substitute (16)
into (15):
((Eb/ No)R)/W = SIR(1 + SG)/256
(17)
(18)
3.1.4
For a UE with highest scheduling priority, the scheduler needs to send AG for
scheduling to facilitate the UE to quickly obtain required grant. The AG cannot
be used for the rest UEs aft er it is engaged because AGCH is shared am ong
all UEs. The RGCH, however, is dedicated control channel allocat ed for each
UE. Therefore, for the rest UEs, they can either get more resources or release
their resources by RG commands. The scheduler sends RG= UP to UEs
allocated with more resources, RG=DOWN to UEs with resources released
and RG=HOLD to UEs with grants retained during scheduling.
When the ratio of the receive power of non -serving E-DCH RLS to the total
receive power of E-DCH is larger than NservToTotalP wr, Node B sends
RG=DOWN to non-serving RL UE.
The AGCH and RGCH may transmit data to UE in each TTI based on
scheduling requirements.
The Schedule Period is related to TTI and not adjustable (the schedule period
is 40ms). For details, see Node B Interface Parameter Description.
15
DCH TT, the cycle duration will c hange t o UE_DTX_cycle_2 subframes, and subframe
number to be transmitted in every cycle duration is controlled by UE_DP CCH_burst_2.
Relat ed parameters can be referenced from ZTE UMTS HSPA Evolution Feat ure Guide.
When CP C is activated in UE, Node B HSUPA packet scheduling algorithm needs to
know UE in cycle1 or cycle2 status, and proc ess this UE scheduling according to the
status.
After activation of CP C in UEs, RNC will stagger individual UEs burst instance through
parameter UE DTX DRX Offset to decrease UL interferenc e as much as possible. So in
order to save UE t ransmission power, UE needs to complete HP( HA RQ Process)with
the burst time instance.
HSUPA packet scheduling algorithm will average the historical load of each UE in the
recent RTT, A fter introducing CP C, sometimes UE maybe transmit UL DPCCH only and
no E-DCH, accurate SIR and the power offset bet ween UL DP CCH and other uplink
physical channels must be included in UL decoding report message as same as CPC
non-activation.
When HS UPA packet scheduling algorithm try to forecast UE UL load, the estimated
SIR is the historic al average value in recent RTT. After introducing CP C, DTX maybe
happen with DP CCH transmission. In order to estimate the S IR in the future, its
suggested to consider the influence of the DP CCH DTX.
3.2
E-DCH uplink congestion control is detected by RNC and implemented by Node B, and
Back-pressure flow control is implemented in Node B. The back-pressure function
exercises control over the uplink service rate of E-DCH UEs based on lub bandwidth
utilization status.
3.2.1
3.2.1.1
16
E-DCH congestion detection and indication proc edure on RNC side is described as
follows:
3.2.1.2
Upon receiving E -DCH FP, the RNC rec ords such information as data frame
receiving time, FSN, CFN, sub-frame No. as well as TTI.
If it is the first dat a frame received on uplink, RNC only records such information as
frame receiving time, FS N, CFN, and sub-frame No. and the processing ends. If
RNC does not receive any uplink data for a long time, it will proc ess subsequently
received data frames in the same way as the first data frame.
Frame loss judgment: RNC compares the FS N of one frame wit h that of its previous
frame. If the FS Ns of them are not consecutive, RNC will set out-of-sequence
tolerance period (out-of-s equence tolerance period =20ms+ TimeDelayJitter *2;
TimeDelayJitter can be configured in OMM). The out-of-sequence tolerance period
is introduced to reduc e frame out-of-sequenc e caused by transmission jitter and
avoid false or excessive report of transmission congestion exec ution frames of
Frame loss type. The out-of-sequence tolerance period is related to office direction
transmission jitter.
Frame delay judgment: By comparing the CFNs and sub-frame Nos. of two E-DCH
FP frames with consecutive FSNs, RNC obtains Uu interface time differenc e of
these two frames; by comparing the receiving time of two consecutive E -DCH FP
frames, RNC obtains the receiving time difference of them. If the receivi ng time
differenc e is x ms (x = TTI + TimeDelayJitter *2; TimeDelayJitter can be configured
in OMM) larger t han t he Uu interface time difference, RNC c onsiders it as Frame
delay.
Upon detecting E-DCH congestion (for example, after frame delay and loss), RNC
sends a TNL Congestion Indication message t o Node B. To prevent Node B from
failing to respond to the TNL Congestion Indication message due to transmission
delay or other causes, RNC sets a protection timer (timer duration = 100ms +
TimeDelay; TimeDelay can be configured in OMM) after sending the TNL
Congestion Indication message to avoid repeated transmission of TNL Congestion
Indication wit h identical congestion status.
17
Figure 7
Start
Receive TNL
congestion
Indication of UEi
no
yes
Timer is up
Indicate Congestion
yes
yes
no
The upper limit
of SG is smaller
than 37
yes
Upgrade the upper
limit of SG;restart
the timer
no
end
3.2.2
Figure 8
18
Uu
Uplink Processing
RNC
lub
UE
TNS
Measure
report
AG
HSUPA
Scheduler
RG
Uu
E-AGCH
Uu
E-RGCH
Downlink
NodeB
3.2.2.1
Figure 9
Reserved Bandwidth
Total Bandwidth
Assignable Bandwidth
Used Bandwidth
The meanings of bandwidths shown in the above figure are described as follows:
Reserved Bandwidth has two roles: (1) Reserve certain bandwidt h margin for buffer
protection so as to avoid congestion on lub interfac e; (2) Reserved for R99 and
HSUPA non-scheduled services. Reserved Bandwidth is an internal variable of the
HSUPA scheduler and the value is not adjustable.
19
Used Bandwidth: Refers to the bandwidth measured through TNS, including uplink
traffic of all services.
3.2.2.2
The TNS realtime obtains the number of bytes transmitted on the network interface
at a specific time interval, and converts it into current rate (unit: bps).
The TNS reports current rat e to the UPA scheduler at a cert ain time interval.
In IPoverE1 mode:
The TNS realtime obtains the number of bytes transmitted through PPP/MLPPP at
a specific time interval, and converts it into current rat e (unit: bps).
The TNS reports current rat e to the UPA scheduler at a cert ain time interval.
In A TM mode:
1
The TNS realtime obtains the number of bytes transmitted through AAL2 PVC at a
specific time interval, and converts it into current rate (unit: bps).
The TNS reports current rate to the UPA scheduler at a certain time interval.
20
Start
Rbw >
R_BW_LMT_UP
YES
Suppress
SGlmtIub
processing
NO
Rbw <
R_BW_LMT_DOWN
YES
Resume
SGlmtIub
processing
NO
end
Assign current grant as the back-pressure grant threshold SGlmtIub of all UEs on the
channel.
Set SGlmtIub of the two UEs with lowest scheduling priority among all UEs on the
channel to: current SGlmtIub DownStep (DownStep is an internal parameter of the
scheduler and is not adjustable).
Set SGlmtIub of the UE wit h highest scheduling priority among all UEs on the channel
to: current SGlmtIub + UpStep (UpStep is an internal parameter of the scheduler and
is not adjustable).
Assign current grant as the back-pressure grant threshold SGlmtIub of the rest UEs
on the channel.
The back-pressure grant thres hold SGlmtIub is an internal variable of the HS UPA
scheduler, and one of upper grant thresholds including congestion and maximum bit rate
of UE. These thresholds are set to perform more effective scheduling and appropriate
grant allocation. When scheduling grants are allocat ed for UEs, not e that these
thresholds cannot be exceeded so as to s eparate control procedure from scheduling
procedure and realize smooth grant allocation.
Parameters related to congestion control are described as follows:
21
4.1
Parameter List
Abbreviated name
Parameter name
EdchNormBitRate
MaxRTWP(dB)
NServToTotalP wr
MaxRetransEdch
TimeDelay
TimeDelayJitter
R_IPPARABandwidth
Bandwidth
SPI_WEIGHT
4.2
Parameter Configuration
4.2.1
OMM Path
View -> Configuration Resource Tree > OMM -> UTRA N Subnet work XXX -> RNC
Managed Element XXX -> RNC Config Set XXX (Choose the us ed config set) -> QoS
ConfigurationXXX -> Priority and Rate Segment of QoS Advanced Parameter
Parameter Configuration
Relat ed description
22
This parameter is configured for Nominal Bit Rate (NB R) of I-/B-class services on EDCH, related to basic priority level. UEs with high priority have high NBRs.
EdchNormBitRate is used as the minimum guaranteed rat e in NodeB HSUPA packet
scheduling.
Parameter description:
This parameter is used to configure the uplink NBR of interactive/background-class
services with basic priority.
Note: This parameter is only valid for the uplink rate of I-/B-class services.
Recommendation: Set an appropriate value for this parameter bas ed on actual
conditions.
4.2.2
OMM Path
View-> Configuration Management ->RNC NE-> RNC Radio Resource Management>Utran Cell-> Utran Cell XXX->Modify Advanced Parameter->Hspa Configuration
information In A Cell
Parameter Configuration
This paramet er indicates the maximum target UL interference allowed by a cell, which is
an offset relative to the UL interferenc e when there is zero load in the cell. This
parameter can also be deemed as the maximum RTWP used for Node B scheduling.
The RTWP increases by increasing the configuration of this parameter and decreases
by decreasing the configuration of this parameter.
4.2.3
OMM Path
View-> Configuration Management->RNC NE-> RNC Radio Resource Management>Utran Cell-> Utran Cell XXX->Modify Advanced Parameter->Hspa Configuration
information In A Cell
Parameter Configuration
23
4.2.4
OMM Path
View-> Configuration Management -> RNC NE-> Rnc Radio Resource Management>Modify Advanced Parameter ->Servic e Basic Configuration Information
Parameter Configuration
None.
4.2.5
OMM Path
View-> Configuration Management ->RNC NE-> Rnc Radio Res ource Management->
Node B Configuration Information-> Node B Configuration Information xx-> Modify
Advanced Parameter
View-> Configuration Management ->OMM->UTRA N SubNetwork->RNC Managed
Element-> Rnc Radio Resource Management->External UTRA N Cell ->External UTRAN
Cell xx-> Modify Advanced Parameter
Parameter Configuration
Configure this parameter based on Node B office direction; for c ell not controlled by
current RNC, configure this parameter based on cell settings.
4.2.6
OMM Path
View-> Configuration Management -> RNC NE-> Rnc Radio Resource Management>Node B Configuration Information-> Node B Configuration Information xx-> Modify
Advanced Parameter
Parameter configuration
None.
4.2.7
OMM Path
View-> Configuration Management -> RNC NE-> Rnc Radio Resource Management>Node B Configuration Information-> Node B Configuration Information xx-> Modify
Advanced Parameter
Parameter configuration
24
None.
4.2.8
R_IPPARA Bandwidth
OMM Path
Parameter Configuration.
None.
4.2.9
SPI_WEIGHT ( 0~15)
OMMB Path
radio
Parameter Configuration
Table 1
SPI
SPI_WEIGHT
=SPI+1
SPI_WEIGHT
=EXP((SPI+1)/2)
SPI_WEIGHT
=SPI^3
27
64
12
125
20
216
33
343
55
512
90
729
10
148
1000
10
11
245
1331
11
12
403
1728
12
13
665
2197
13
14
1097
2744
14
15
1808
3375
25
15
16
2981
5.1
Counter List
4096
5.2
Alarm List
There is no alarm in this feature.
Glossary
A
ACK
Acknowledgement
AG
Absolute Grant
C
CFN
D
DPCCH
E
E-AGCH
E-DCH
E-DP CCH
E-DP DCH
E-HICH
E-RGCH
E-TFCI
F
FSN
26
FP
Frame Protocol
G
GBR
H
HARQ
HSUPA
I
IR
Incremental Redundancy
L
LUP R
M
MAC-es/e E-DCH MA C
MAC-d
MAC
MLPPP
Multi-Label PPP
N
Node B
Base Station
NACK
Negative Acknowledgement
NRT
O
OMM
OMMB
OMM in Node B
OMMR
OMM in RNC
P
PF
Proportional Fair
PPP
Q
QoS
Quality of Servic e
27
R
RNC
RG
Relative Grant
RTWP
RL
Radio Link
RLS
RSN
RNC
RoT
Rise of Thermal
S
SF
Spreading Factor
SI
Scheduling Information
SIR
SPI
SRNC
Serving RNC
SRB
T
TTI
TNL
TNS
U
UE
User Equipment
UPH
UMTS
28