Ericsson 3G Chapter 5 (Service Integrity) - WCDMA RAN Opt

WCDMA RAN P6 Optimization
Chapter 5: Service Integrity

Chapter 5 Objectives
After this module, the participants will be able to:
1. Explain why inner, outer, and open loop power control are needed
2. Explain the operation of inner loop power control and the impact of the
network
3. Explain the operation of outer loop power control and the impact of the
network
4. Control the channel switching by means of parameter settings
5. Explain which counters and formulas to use in order to retrieve the
worst cells
6. Explain how to optimize HSPA network
7. Explain techniques for troubleshooting Integrity KPIs, clustering and
drill through statistics analyze.
8. Analyze data from real networks and propose changes in order to
improve the networks integrity
© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

. A Figure2 5 - Service Integrity
Service Integrity Workflow
Recommendation
Performance Performance Verification of
&
Measurements Analysis changes
Implementation
BLER counters BLER, power, Test the settings Check statistics

and Down SIR parameters If not OK, roll back
Switching
counters Throughput
pmFaultyTransportBlocksBcUl
pmTransportBlocksBcUl
pmNoOfSwDownNgCong
PmNoOfSwDownNgAdm
PmDl Traffic volume counters

Worst Cells
Observability of Service Integrity is very limited.
Only UL BLER per RAB on RNC level can be monitored
The system is designed to fight against BLER deviations from
the set BLER targets
There are two counters on cell level before combining :
 pmFaultyTransportBlocksBcUl These counters

does also contain
 pmTransportBlocksBcUl BLER information
for all RAB’s
pmFaultyBlocksBcUL
100 
pmTranspor tBlocksBcUl

Worst Cells

Worst Cells – after combining
Formula Below shows Block Error rate after uplink combining at
RNC level. That means in RNC blocks coming from different legs
in SHO are compared:
pmFaultyTr ansportBlocksAcUl[UeRc]
100 
pmTranspor tBlocksAcUl[UeRc]
UeRc stands for different RAB’s

UeRc=2, Speech
UeRc=3, Video Call
UeRc=4, Packet Common Channel
UeRc=5, PS 64/64
UeRc=6, PS64/128
UeRc=7, PS 64/384
UeRc=10 multirab Speech+PS 0 or PS 64/64).

WCMA Power Control
Soft/Softer Handover benefits
The UE and the WCDMA RAN must achieve a connection

that has a sufficient Signal-to-Interference Ratio (SIR), even
when the UE is at the cell border.
The UE requires enough power to achieve sufficient downlink

SIR .
Using Soft or Softer Handover,

UE takes advantage of having
several simultaneous radio links
DL RBS's output power can be

lowered, reducing interference
and increasing capacity.
WCMA Power Control
The Outer Loop Power Control algorithm is used to maintain

the required Block Error Rate (BLER) for a service by
modifying the SIR target of Inner Loop Power Control.
Workflow
 Through performance statistics data (RNC counters) identify

RAB’s that are not performing in line with targets
(blerQualityTargetUl). That means - uplink BLER derived from
counters is higher than UL BLER Target value set by
parameter.
 Review radio parameter settings and verify settings against Ericsson
default/recommended values.
– Check RAB parameters on the RNC level (blerQualityTargetUl
and blerQualityTargetDl)
– Check the values of the RAB Power Mapping parameters,
– Check UL Outer Power loop parameters (SIRMax, ul SIR Step)
 Check if different blerQualityTarget settings should be investigated
(for example, what is happening changing target from 1 to 2% for
voice)

Cyclic Redundancy Check (CRC)
The Error detection and error protection of the data channels
are performed using Cyclic Redundancy Check (CRC)
coding, Forward Error Correction (FEC) and interleaving, all
after error correction
Transmitter
Original Data CRC Original Data Checksum 12 bits
244 bits Generator 1001011010.. 110010110011
RF
Transmission Path
Receiver
Received Data Received Checksum If Checksums do not match,
1001010010.. 110010110011
there is an error
CRC Re-Generated Checksum

Generator 110010110001

. A Figure105 - Service Integrity
WCMA UL Inner Loop Power Control
The RBS maintains the QoS by sending Transmit Power Control (TPC)
commands in every slot (i.e., 1500 times per second in a 15 slots per 10 ms
format) requesting a power adjustment.
If estimated SIR >= target SIR, the RBS sends a down command.
If estimated SIR < target SIR, the RBS sends an up command
WCMA Outer Loop Power Control
There are two alternative

algorithms for uplink
Outer Loop Power
Control implemented :
 Constant Step
Regulator
 Jump Regulator
The parameter setting

the type of regulator is
ulOuterLoopRegulator

(cont)
The start point of SIR
target regulation is
determined by the Initial
Uplink SIR Target
(ulInitSirTargetLow or
ulInitSirTargetHigh)
depending on the
Spreading Factor of
DPDCH
The two configurable

parameters sirMax and
sirMin set the limits of the
uplink SIR target,
expressed in dB

SIR Target Behavior According to the
Constant Step Regulator algorithm
Constant Step Regulator algorithm When the
NBR_OF_CRC_OK of
concecutive transport
blocks is fulfilled SIR is
decreased by ulSirStep
Whenever the Cyclic

Redundancy Check
(CRC) indicates that the
reception of a transport
block is erroneous, the
uplink SIR target is
increased by configurable
increment ulSirStep,
expressed in dB

(cont)
Jump Regulator algorithm
 -X Y
SIRtarget_new  SIRtarget  ulSirStep  
 (Z * UP_DOWN_STEP_RATIO) Z 
Where:
ulSirStep is the configurable parameter that defines the size of SIR target
increment.
Z is the total number of received transport blocks.
X is the number of transport blocks that have a CRC=OK.
Y is the number of transport blocks that have a CRC=NG.

SIR Target Behavior According to
the Jump Regulator algorithm
Jump Regulator algorithm Whenever the CRC
indicates that the
reception of a transport
block is erroneous, the
uplink SIR target is
increased by ulSirStep.
Whenever a transport
block is correct, the UL
SIR target is decreased
by a fraction of ulSirStep.
This fraction,
UP_DOWN_STEP_RATI
O, depends on the BLER
target.
blerQualityTargetDl/ Ul  10 log10  BLER quality target 
(cont) Default values for parameters blerQualityTarget UL/DL set on TrCH
RAB Type TrCH Default Value

BLER Targets SRB SRB -20 ( 1% BLER)
Speech 12.2 Speech -20 (1% BLER)

The purpose of configurable SRB -20 (1% BLER)
BLER targets is to enable the Conversational CS data 64 CS64

SRB
-25 (0.3% BLER)
-20 (1% BLER)
operator to trade quality of CS Streaming 57.6 CS57.6 -20 (1% BLER)

the connections versus SRB -20 (1% BLER)
resource usage. PS Interactive 64/64 PS64

SRB
-20 (1% BLER)
-20 (1% BLER)
PS Interactive 64/128 PS128 -20 (1% BLER)
 blerQualityTargetDl SRB -20 (1% BLER)
PS Interactive 64/384 PS384 -20 (1% BLER)

SRB -20 (1% BLER)
 blerQualityTargetUl Speech+ PS Interactive 64/64 Speech -20 (1% BLER)

PS64 -20 (1% BLER)
SRB -20 (1% BLER)
PS Streaming 16/64 PS Streaming -13 (5% BLER)

PS8/8 -13 (5% BLER)
SRB -20 (1% BLER)

Throughput - Session throughput
and THold
Throughput = the perceived user data rate from the
application layer.
Throughput will never reach the peak rate, since the TCP and
IP overhead, and retransmissions, have to be taken into
account.
The throughput can be expressed per session, per bearer or

per cell.

Throughput - Session throughput
and THold

Worst Cells - Average Throughput
Observability of throughput measurements on cell level are
split into RB specific measures (HSDPA/EUL/R99).
Average Throughput : DCH/FACH Average Throughput kbit/s

P int DCH _ I _ TF ( RncFunctio n) 
 pmSentPacketData2( RncFunction)  
8  1000   
 pmSentPacketData3( RncFunction )  pmSentPacketData 4( RncFunction ) 
 pmTotalPac ketDuration 2( RncFunction)  
 
 pmTotalPac ketDuration3( RncFunction)  pmTotalPac ketDuration 4( RncFunction 
Average Throughput : HS Average Throughput kbit/s

P int HS _ I _ TP ( RncFunctio n) 
8  1000  ( pmSentPacketDataHs3( RncFunction)  pmSentPacketDataHs 4( RncFunction))

( pmTotalPac ketDurationHs3( RncFunction)  pmTotalPac ketDurationHs 4( RncFunction))
Worst Cells – Average User
Throughput DCH/FACH
DCH/FACH User Throughput, Downlink (kbit/s )
pmSumDchDlRlcUserPacketThp (UtranCell )
P int DCH _ I _ D(Tp _ User (UtranCell ) 
pmSamplesDchDlRlcUserPacketThp (UtranCell )
DCH/FACH User Throughput, Uplink (kbit/s )
pmSumDchUlRlcUserPacketThp (UtranCell )
P int DCH _ I _ UlTp _ User (UtranCell ) 
pmSamplesDchUlRlcUserPacketThp (UtranCell )

Worst Cells – Average User
Throughput HS/EUL
HS User Throughput, Downlink (kbit/s )
pmSumHsDlRlcUserPacketThp (UtranCell )
P int HS _ I _ DlTp _ User (UtranCell ) 
pmSamplesHsDlRlcUserPacketThp (UtranCell )
EUL User Throughput, Uplink (kbit/s )
pmSumEulRlcUserPacketThp (UtranCell )
P int EUL _ I _ UITp _ User (UtranCell ) 
pmSamplesEulRlcUserP acketThp (UtranCell )

Channel Switching I
The idea:
Congestion control is used to resolve overload in both the

uplink and the downlink.
It uses Power and RSSI (Received Signal Strength

Indicator) measurements.
In case of overload, congestion control
1. reduces bit rates of delay tolerant (non-guaranteed)

existing connections down to common channels
2. as a second option, removes existing connections.

Channel Switching II
The idea:
3. When the Cell load rises (due to the increased power

requirement - the UE that is moving away from the RBS)
and this load reaches a defined limit, the RBS must
reduce it by switching non-guaranteed users to lower
rate common channels.

Channel Switching III
The idea:
Channel Switching applies only to packet traffic on the

interactive and Background QoS classes RABs, which
has little or no quality of service attributes that apply.
When sufficient resources available, the interactive RAB

receives high bit rates but when the system is heavily
loaded and not many resources are available, the bit
rates offered may be low.
In a heavily loaded situation, it may not be given any

bandwidth at all, since there are no guarantees on
resource allocation for the RAB.
Throughput - Channel Switching I
The idea:
Channel Switching Algorithms use
• buffer load,
• throughput,
• transmitted code power
as input to the algorithms.

Throughput - Channel Switching II
The idea:
Buffer load: The buffer load is defined as the minimum of

the Radio Link Control (RLC) transmission window
Throughput: UL throughput is defined as the number of bits

received to the RLC layer from the MAC layer. DL
throughput is defined as the number of bits transmitted
from the RLC layer to the MAC layer.
Transmitted Code Power: Transmitted code power is

defined as the DL power of the pilot bits of the DPCCH
field.

Channel Switching
Coverage, bad
quality or RAB
not supported
by EUL can
Cell_DCH EUL/HS trigger
Upswitch downswitch to
HS, DCH or
based on Cell_DCH 384/HS FACH
throughput
Downswitch
Cell_DCH 64/HS based on
throughput or
Coverage inactivity
triggered downswitch Cell_DCH 64/384
DL
Cell_DCH 64/128 SHO can
initiate a
Soft switch if it
Cell_DCH 64/64 fails to add a
Congestion
RL
Common Dedicated
to Cell_FACH
to common
Dedicated based on
No
based on Activit UL/DL user
URA_PCH activity
buffer size y inactivity or
or activity No cong.
activity
Channel Switching
The idea:
The channel downswitch success rate per UtranCell in a

measurement period of 15 minutes is given by:
pmDownSwitchSuccess
ChDSw _ S 
pmDownSwitchAttempt
Channel Switching can be divided into Channel Type

Switching and Channel Rate Switching.

Channel Type Switching I
Channel Type Switching handles the switching of UEs
between common channels, i.e. FACH or URA (UTRAN
Registration Area), and dedicated channels, i.e.
DCH/DCH, DCH/HSDPA or EUL/HSDPA.
On the common channels the UE will consume less power

and radio resources than when on the dedicated
channel.
Switching between channel types is triggered at threshold

values in the data buffers (upswitch) or on data
throughput (downswitch).

Channel type switching II
Prio 1 Prio 2 Prio 3
384 / HS
EUL / HSDPA DCH / HSDPA DCH/ DCH

EUL / HS DCH / DCH
64 / HS
Down
FACH Throughput
Up Inactivity
Buffersize Coverage
Activity URA Mobility
Idle

Channel Type Switching III
The Algorithm:
When the throughput on both the uplink and downlink is below

the threshold value (downswitchThreshold), the timer
downswitchTimer starts (when on DCH/DCH) or the timer
hsdschInactivityTimer starts (when on DCH/HS or EUL/HS).
If the throughput increases above a second threshold

(downswitchTimerThreshold) before the timer expires, the
timer is stopped and no switch is issued.

Channel Type Switching IV
Optimization of the
downswitch from DCH to
common channels is a
trade-off between resource
utilization and user
throughput.
The downswitchThreshold parameter determine how the radio access

network should behave in the end of a TCP transmission.

Channel Type Switching V
The URA_PCH state is not an idle state.
By introducing this state the RRC request in the system will

decrease so in order to check the accessability rate for PS data
this formula can be used:
pmChSwitchSuccessUraFach
100 
pmChSwitchAttemptUraFach

Channel Type Switching VI
The buffer load is defined as the minimum of the Radio Link Control (RLC)
transmission window and the sum of bytes in the SDU buffers and
retransmission buffers of some of the RLC instances.
UL RLC buffer load > ulRlcBufUpswitch, a measurement report is sent

from the UE.
DL RLC buffer load (in the RNC) > dlRlcBufUpswitch.
The success rate for

upswitch the HSDPA
pmDlUpswitchSuccess  Rate  The success rate for

100  upswitching from one DCH
pmDlUpswitchAttempt  Rate  channel to another

P6 Channel Rate Up Switching
P5 PS DCH Rates 0..0 8..8 16..16 32..32 64..64
128..128 144..144 256..256
64/384 128/384 384/384 384..384 768..768 2048..2048
rateSelectionPsInteractive.dlPrefRate
64/128 128/128 384/128
rateSelectionPsInteractive.ulPrefRate
0..0 8..8 16..16 32..32 64..64

16/64 64/64
128/128 128/64 384/64
128..128 144..144 384..384
DCH/HS E-UL/HS
16/16 64/16
PS DCH Rates 3rd Choice 2nd Choice 1st Choice

added in P6
rateSelectionPsInteractive.channelType = DCH
4th
FACH Choice SRB Idle
or
rateSelectionPsInteractive.channelType = FACH
Channel rate Down switching I
The channel switching 384 / HS
feature use the total EUL / HSDPA DCH / HSDPA
throughput, i.e. throughput EUL / HS
64 / HS
including the
retransmissions, when
determine if a rate switching
should occur.
64/384 128/384 384/384

pmDownSwitchSuccess
100 
pmDownSwitchAttempt
64/128 128/128 384/128
64/64 128/64 384/64

Throughput - Channel Switching VII
The algorithm applies both for Single RAB and for Multi RAB. The
algorithm monitors the UL and the DL throughput separately
DL throughput >bandwidthMargin or
UL throughput > bandwidthMarginUl.
DL throughput < dlThroughputAllowUpswitchThreshold or

UL throughput < ulThroughputAllowUpswitchThreshold
DL transmitted code power < upswitchPwrMargin for all legs in

the active set.
The maximum bitrate capability for QoS profiling < maximum

bitrate for the user.

Throughput based downswitch
Throughput based down switch optimize the usage of the RAN resources for the packet
interactive RABs. The RAN system will monitor the throughput and if the user/application
reduces the data rate, a down switch to radio bearer with a lower rate will occur if the lower rate
is sufficient to satisfy the needs of the user
Downswitch due to:

64/384 128/384 384/384
Coverage
Capacity
Inactivity 64/128 128/128 384/128
And in P5:
Throughput
64/64 128/64 384/64
Benefit:
Optimise resource to the momentary needs
More efficient use of network capacity
Throughput based Downswitch
DL
throughput
Next lower rate
dlDownswitchBandwidth
Margin e.g. 80%
dlThroughputDownswit
chTimer
Downswith
request executed

Coverage Based Down Switch
Transmitted Code Power:

Transmitted code power is defined as the downlink power of
the pilot bits of the DPCCH field.
The Coverage Triggered Downswitch Evaluation algorithm

monitors the code power utilization on the downlink
DL transmitted code power > downswitchPwrMargin the

downswitch will take place.
The average amount of transmitted code power is not only

dependent on the used transmission rate and attenuation to
the UE, but also on the blerQualityTarget parameters

TEMS Investigation and Statistics
To compare the measured throughput (by TEMS Investigation) to the average

throughput at the cell and at the RNC level could be done by looking at the traffic
counters in at RBS and RNC level.
DCH 64/384
DCH 64/128
RAB state
DCH 64/64
FACH
Packet RAB
establishment actual throughput
pmXTrafficVolume<RAB>
Where X = Ul or Dl
pmSum<RAB>RabEstablish
pmSamples<RAB>RabEstablish * ROP
sec

HSDPA
 Shared channel transmission (dynamically in time and code)
 Higher order modulation (QSPK and 16QAM).
 Short transmission time interval (TTI = 2ms)
 Fast Link adaption (adjusting to multi path fading, path loss).
 Fast scheduling
 Fast hybrid automatic-repeat-request (ARQ)

(retransmissions in the RBS)

Optimizing HSDPA
 SW and HW preparations such as new sites, new
carriers, new transmissions solutions and new SW
versions in all NE.
 Review radio parameter settings. There will be a major

impact on the power parameter settings
 System Interference
 Handover performance, the network must have well

confined HO areas.
 System Load - The DL Load is here measured as the

percentage of used DL Power compared to the
available one. pmTransmittedCarrierPower
Optimizing HSDPA – Power
performance
HSDPA will take whatever power that is left in RBS after
common channels and dedicated channels has taken their
part. The average power utilization in the network will increase
with HSDPA.
Power
Max cell power Power of the Common Channels, e.g.
CPICH and SCH should be increased and
HSDPA power verified. This because with 100% cell load
Admission control threshold the common channels should remain their
quality.
DCH power Max power of the DCH (other RABs)

should be increased and verified. The
DCH channel should remain their quality in
CCH power the cell border, where they are using their
max power.
time

Optimizing Power performance - Hints
In areas with poor coverage it is possible to increase the
success of the random access procedure by maximizing the
number of transmitted preambles.
Set parameter powerOffsetP0 to 1 dB,

preambleRetransMax to 32, and maxPreambleCycle to 32.
They ensure that the UE transmits the maximum number of

preambles before aborting the attempt, thus ensuring
maximum detection probability in the RBS.
Tests have shown that the coverage improvement with this

setting is in the order of 1 - 3 dB.

HSDPA Throughput Concepts
The throughput for HSDPA can be divided in different categories:
Application throughput is defined as TCP/IP to end-to-end throughput. It is

the net payload throughput and is considered to be error free. It is
measured every second.
Physical Served Throughput is defined as the Layer 1 throughput that

includes all received transport blocks, including error blocks.
MAC-HS Throughput is defined as the Layer 2 throughput that includes all

received acknowledge transport blocks, excluding error blocks. It is
measured every 200 millisecond.
Radio Link Control (RLC) Throughput is defined as the Layer 2

throughput that includes all PDU and SDU. It is measured every 3rd
second.

HSDPA Throughput Concepts

HSDPA Throughput Counters
pmSumAckedBitsSpi00 : To observe the total amount of acknowledged data

sent on MAC-hs level per scheduling priority class 00.
pmSumTransmittedBitsSpi00 : Measurement to observe the total amount of

data sent on MAC-hs level per scheduling priority class 00.
pmNoActiveSubFramesSpi00 : Measurement to observe the sum of active 2

ms subframes for scheduling priority class 00.
pmNoInactiveRequiredSubFramesSpi00 : Measurement to observe the sum

of not used 2 ms subframes for scheduling priority class 00 during a ROP
when there was data in the buffers.
pmSumNonEmptyUserBuffersSpi00 : Measurement to observe the number of

user buffers for scheduling priority class 00 with data in the buffer for each
2 ms subframes.

HSDPA Throughput
The throughput for HSDPA is calculated differently from the other RAB due
to the MAC-ehs.
Average HS cell throughput can be obtained on DSCH level per SPI:

pmSumAckedBitsSpiXX
ROP Period
The Average Scheduled HS throughput on MAC-ehs level:
pmSumAckedBitsSpiXX
TTI pmNoActiveSubFramesSpiXX

HSDPA Throughput
The throughput for HSDPA is calculated differently from the other RAB due
to the MAC-ehs.
Average user throughput with no retransmissions can be obtained on DSCH

level:
pmSumAckedBitsSpiXX
TTI  pmNoInactiveRequiredSubFramesSpiXX
The HARQ retransmission rate:
pmEulHarqT ransmTti10Failure
pmEulHarqT ransmTti10PsInteractive

HSDPA Throughput considerations
The scheduled throughput. This is mainly related to coverage and available
power for HSDPA.
The percentage of TTIs that the channel is available but there is data in the
buffer. This could be problems with decoding CQI or ACK or that the A-DCH
is not synchronized.
The percentage of TTIs that the UE has something n the buffer. This is
mainly due to TCP effects.

HSDPA Throughput efficiency
considerations

The scheduling ratio

% of time the HS-DSCH is in use:
TTI x pmSumAckedBits
100 x
ROPperiod
The transmission ratio

% of time there is something to transmit:
TTI x pmNoActiveSubFrame  pmNoInavtive RequiredSubFrame

100 x
ROPperiod

The MAC transmission efficiency - HS-DSCH is in use
pmNoActiveSubFrame
100 x
pmNoActiveSubFrame  pmNoInavtive RequiredSubFrame
Average number of UE in the queue when HS is transmitting
pmSumNonEmptyUserBuffers
100 x
pmNoActiveSubFrame  pmNoInavtive RequiredSubFrame

Enhanced Uplink
The uplink transport channel E-DCH allows for

improved uplink performance compared to the DCH in
terms of the following:
 Reduced delays
 Increased data rates
 Increased capacity
EUL is a natural complement to the High-Speed
Downlink Packet Access for high-performance packet
data applications.

Enhanced Uplink Bit Rate
The maximum achievable bit rate on the E-DCH depends on the

following factors:
 Available power
 Radio conditions (radio channel type, interference, UE speed, and
so on)
 Number of E-DCH codes
 TTI length (2 ms or 10 ms)
 Choice of transport format table
WCDMA RAN provides an EUL solution with 2 ms TTI and 10 ms TTI

and a peak rate of 1.376 Mbps for 10 ms TTI and 5.44 Mbps for 2 ms
TTI at the RLC level.
The GRAKE receiver can be used with the EUL. A GRAKE receiver
suppresses self-interference and increases the probability of getting
high bit rates in time dispersive channels.

Enhanced Up Link Parameters
Some parameters for EUL Configuration and Optimization
eulNonServHwRate maxNumEulUsers
eulMaxShoRate eulNoERgchGroups
eulSchedulingWeight eulMaxShoRate
eulTargetRate eulNonServHwRate
eulNoReschUsers eulLowRate
eulMaxNoSchEdch eulMaxAllowedSchRate
eulServingCellUsersAdm

Enhanced Up Link Counters
Some counters useful for EUL Optimization
pmEulHarqTransmTti2Failure pmSumAckedBitsCellEulTti10
pmEulHarqTransmTti2PsRabs pmSumAckedBitsCellEulTti2
pmEulMacesPduTti2DelivPsRabs pmNoUlUuLoadLimitEul
pmEulMacesPduTti2UndelivPsRabs pmNoSchEdchEul
pmNoActive2msFramesEul pmNoAllowedEul
pmNoActive2msIntervalsEul pmCommonChPowerEul
pmNoActive2msIntervalsEulTti2 pmCapacityServEDchUsers

HSDPA Throughput increase
By changing the TCP
window settings in the
laptop the scheduled
throughput is almost the
same as the cell
throughput
By changing the UTRAN

parameters such as
pwrAdm the application
throughput has increased


Ericsson 3G Chapter 5 (Service Integrity) - WCDMA RAN Opt

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Ericsson 3G Chapter 5 (Service Integrity) - WCDMA RAN Opt

Загружено:

Авторское право:

Доступные форматы

WCDMA RAN P6 Optimization

Chapter 5: Service Integrity

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

BLER counters BLER, power, Test the settings Check statistics

PmDl Traffic volume counters

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

 pmFaultyTransportBlocksBcUl These counters

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

UeRc stands for different RAB’s

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

The UE and the WCDMA RAN must achieve a connection

The UE requires enough power to achieve sufficient downlink

Using Soft or Softer Handover,

DL RBS's output power can be

The Outer Loop Power Control algorithm is used to maintain

 Through performance statistics data (RNC counters) identify

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

CRC Re-Generated Checksum

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

There are two alternative

The parameter setting

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

The two configurable

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

Whenever the Cyclic

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

(cont) Default values for parameters blerQualityTarget UL/DL set on TrCH

RAB Type TrCH Default Value

Speech 12.2 Speech -20 (1% BLER)

BLER targets is to enable the Conversational CS data 64 CS64

operator to trade quality of CS Streaming 57.6 CS57.6 -20 (1% BLER)

resource usage. PS Interactive 64/64 PS64

PS Interactive 64/128 PS128 -20 (1% BLER)

 blerQualityTargetDl SRB -20 (1% BLER)

PS Interactive 64/384 PS384 -20 (1% BLER)

 blerQualityTargetUl Speech+ PS Interactive 64/64 Speech -20 (1% BLER)

PS Streaming 16/64 PS Streaming -13 (5% BLER)

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

The throughput can be expressed per session, per bearer or

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

Average Throughput : DCH/FACH Average Throughput kbit/s

Average Throughput : HS Average Throughput kbit/s

8  1000  ( pmSentPacketDataHs3( RncFunction)  pmSentPacketDataHs 4( RncFunction))

DCH/FACH User Throughput, Uplink (kbit/s )

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

HS User Throughput, Downlink (kbit/s )

EUL User Throughput, Uplink (kbit/s )

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

Congestion control is used to resolve overload in both the

It uses Power and RSSI (Received Signal Strength

In case of overload, congestion control

1. reduces bit rates of delay tolerant (non-guaranteed)

2. as a second option, removes existing connections.

3. When the Cell load rises (due to the increased power

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

Channel Switching applies only to packet traffic on the

When sufficient resources available, the interactive RAB

In a heavily loaded situation, it may not be given any

Channel Switching Algorithms use

• transmitted code power