4xdolw/ $VSHFWV

TA-TC 6270 /Version 01/Chap.
04 Quality
1
+. Quality Aspects
4.1 Resources in UTRAN
4.2 ATM measurements
4.3 Throughput measurements
4.4 Radio Measurements
4.5 Codes
4.6 Quality/load related KPI
TA-TC 6270 /Version 01/Chap. 04 Quality
2
4.1.Resources in UTRAN
This chapter is about the bottlenecks within UTRAN, What are the resources In UTRAN?
Mainly it deals with ATM, Power and Code resources. Other resources like Hardware, processors,
Base Band capacity per Node B shall be mentioned. Here each vendor should provide the required
tools to supervice and to adjust the resources.
3
1.Quality aspects in UTRAN
Iub
Serving
Iur
IuCS
IuPS
Drift
Power
Base Band
Resources
Processors
Power Power ATM
Hardware
ATM
Code
Processors
+
+.2. ATN Neasurements
1 ATM in UTRAN
2 AAL2
3 ATM Measurements
S
2.1 ATM in UTRAN
One ATM cell may carry:
- User data (on Iub, Iur, IuCS handled with higher priority)
- Signaling information
- O&M information
- Idle and Unassigned Cells
The different cell types are related to certain VPI / VCI and PTI (Payload Type Identifier) values. The
information of the higher layers must be adapted to the format of the information field used by ATM.
This adaptation is done by the so called AAL (ATM Adaptation Layer).
2 service types are in use in UTRAN: AAL2 and AAL5.
-User data is carried by AAL2 on Iub, Iur, IuCS and AAL5 for IuPS
-Signaling (NBAP, RANAP, RNSAP) is carried on top of AAL 5 on all the interfaces.
A service category constant bit rate (CBR) is used for AAL2 user plane traffic and all signalling
traffic. A service category unspecified bit rate (UBR) is used for IP over ATM connections for O&M
and Iu-PS (and Broadcast, if supported).
To get an idea of the distribution, the user throughput is especially for IuPS relevant. For all other
interfaces, there are other methods to monitor the availability of resources. ATM overhead is typically
included, because it is almost impossible to filter all kind of,overhead and the ATM header for
example is unavoidable. On ATM level the customers viewpoint, the Application throughput can not
be monitored.
6
2.1 ATM in UTRAN
Iub
Serving
Iur
IuCS
IuPS
Drift
5 Byte ATM
Header
Header Error Check OK?
Eg. IuCS
time
48 bytes 48 bytes 48 bytes 48 bytes 48 bytes
48 bytes 48 bytes 48 bytes 48 bytes 48 bytes
48 bytes payload
7
2.2 AAL 2 connections
The use of the ALCAP is dependent on the type of bearer to be used. The signaling bearers are
usually pre-configured. This means there is no dynamical set up and release for signaling bearers.
Data bearers (AAL2 virtual circuits) have to be set up and released with ALCAP, when they are
not preconfigured (as it is the case for IuPS). AAL2 signalling is used to reserve AAL2 data
channels inside permanent ATM virtual channel connections (VCC).
-The set up or release of a bearer is always controlled by an application protocol. But to avoid
the restriction to a single transport system, the application protocols shall not be specific to a
certain transport solution. Therefore the application protocol can control the bearer via abstract
parameters (QoS parameters) only. This principle is the same as for BICC (Bearer Independent
Call Control). To trigger the set up of a bearer first the application protocol starts a procedure to
the destination node. In UTRAN the RNC is controlling the ATM resources.
- After the application protocol triggered the procedure, the ALCAP, that is specific to the bearer to
be set up, performs all necessary procedures to configure the bearer.
-When the application part receives the notification of a successful bearer set up, the application
protocol procedure can be finished, and the application can be informed to start the data stream
transmission.
-ALCAP procedures in UTRAN are initiated by the RNC.
The unsuccessful case of the ALCAP procedure is RELEASE CONFIRM message received by the
RNC, indicating an failure cause.
8
2.2 AAL2 in UTRAN
Iub
Serving
Iur
IuCS
IuPS
Drift
Application Protocol : Bearer Setup Request
ALCAP : Bearer Establishment Request ERQ
ALCAP : Bearer Establishment Confirmed ERC
Application Protocol : Bearer Setup Complete
NBAP, RNSAP, RANAP
9
2.2 AAL2 and CAC
ALCAP : Bearer Establishment Request ERQ
ALCAP : Bearer Establishment Confirmed ERC
Application Protocol : Bearer Setup Complete
NBAP, RNSAP, RANAP
Connection
Admission Control
Connection
Admission Control
10
2.2 AAL 2 establishments
ALCAP establishment failure rate
ALCP establishment failure rate per Iu
ALCP establishment failure rate per Node B
Number failed ALCAP establishments is compared to the number of ALCAP establishment attempts for each Node B
This KPI describes the ALCAP establishment failure rate, where the number of failed ALCAP establishments is compared
to the number of ALCAP establishment attempts. The ALCAP ESTABLISHMENT REQUEST message is sent toward the
destination node. For the Iur interface the ALCAP ESTABLISHMENT REQUEST message will be received by the SRNC
from an adjacent RNC.
The ALCAP measurements are related to Transport Network
Layer (TNL) and indicate if the ESTABLISHMENT REQUEST
message sent from the RNC to the destination node has been
rejected by the individual failure reason RELEASE CONFIRM
message or no response has been received (No Reply) from
the destination node. The failure causes are defined according
to ITU-T.
Some Failure causes
Failure cause
Number failed ALCAP establishments is compared to the number of ALCAP establishment attempts for each MSC
C-plane - No circuit/channel available
C-plane - Network out of order
C-plane - Temporary failure
C-plane - Switching equipment congestion
C-plane - Requested circuit/channel not available
C-plane - Resource unavailable, unspecified
C-plane - AAL parameters cannot be supported
C-plane - Invalid message, unspecified
......
11
2.2 ALCAP or AAL 2
connections
Following procedures on Iub/Iur may require ALCAP (AAL2 establishment, release)
radio link setup
radio link addition
radio link reconfiguration
radio link release
soft/softer handover
transport channel type switching
Following procedures on IuCS may require ALCAP
RAB assignment
Iu Release
RAB Release
12
2.2 ALCAP or AAL 2
connections
On all interfaces where AAL2 is in use, (in UTRAN on all interfaces except IuPS) user data is transferred in ATM
Virtual Channels/ Virtual Circuits) in AAL 2 minipackets also called Common Part Sublayer (CPS). Each
connection needs so a locally (on that interface) temporary unique Identity for the minipackets, The so called CID
(Channel IDentifier or Call IDentity or (mini) Cell IDentifier).
There are 248 CID values available, this limits the number of ongoing connections. That is the reason why the
IuCS has to be mapped to many VCCs (Virtual Channel Connections) or why the IuB may have to be splitted
between several VCCs.
Especially on the Iub there Common Channels consume permanently CIDs (in most implementations 4, one for
the Paging, one for the FACH-Control, one for FACH user data and one for the RACH.
Each active UE on Cell_DCH RRC substate will require 1 for the SRB plus additionally one for each active RB on
each IuB where the UE has active Radio Links.
Active CID values
Max/Average number of used CID values
13
2.2 AAL2 Virtual Connections
NBAP, RNSAP, RANAP
CID
8 bits
LI
6 bits
UUI
5 bits
HEC
5 bits
CPS-INFO
1 to 45 / 64 octets
AAL2 Packet Header (CPS-PH)
3 Bytes
AAL2 (mini) Packet
4 to 48 Bytes
CPS Packet Payload(CPS-PP)
The CID field being 8 bits gives a maximum of 256 different CID
8 CID are reserved (from CID 0 to CID 7), so that there are 248 possible AAL2 connections
on the Iub per VCC.
Service Number of CID
CCCH per carrier on IuB 4
DCCH (SRB), per connection 1
DCH (AMR, UDI, PS), per connection 1
Multi RAB connection, per RAB 1
HSDPA user (SRB+A-DCH+HSDPA traffic) 3
1+
2.2 AAL 2 Bandwidth
Physical capacity
Each AAL2 connection takes virtual capacity
That means if the transport resources are not available, used the service (RRC connection, RAB, ..) will
be rejected by the RNC!!!. In the case of overbooking of the IuB/IuR cells may be discarded (AAL2 cells
may be buffered for 10 ms)
In one AAL2 user plane VCC there could be up to 248 AAL2 channels (out of the total 256 CIDs, the
CID range from 0 to 7 is reserved for layer management). As long as there is sufficient bandwidth
available and less than 248 channels are occupied within one Node B (one voice call will take 2 CIDs,
one for the SRB and one for the voce), one VCC will be sufficient. Another VCC is needed if either the
bandwidth or the number of channels per VCC is too small.
Constant bit rate (CBR) is used for connections that continuously require a constant bit rate. The bit
rate is further determined by the peak cell rate. There is a defined QoS guarantee for constant bit rate
services if the peak cell rate is not exceeded. Constant bit rate supports real time applications with
strong requirements regarding cell transfer delay and cell delay variation.
1S
2.2 AAL 2 Bandwidth
AAL 2 bandwidth
Built up bandwidth per individual Node B (STM1 and E1).
This measurement provides the average and maximum for build-up bandwidth per Node B (physical interface):
AAL2 UL/DL
AAL5 UL/DL
Maximum
Average
Mimimum
16
2.2 Service specific bitrates
Service (TTI) FP bit rate
AMR 12.2 16 400
CS 64 (20 ms) 66 100
PS AM 4 (20 ms) 69 500
PS AM 128 (20 ms) 136 700
PS AM 384 (10 ms) 408 000
bps +RLC PDUs / 10 ms FP rate FP + RLC overhead
64000 67200 2 76300 1.19
128000 134400 4 145100 1.13
256000 268800 8 282700 1.10
512000 537600 16 557900 1.09
1024000 1075200 32 1108300 1.08
Estimations of HSDPA FP rates
Estimations of Bitrates of the Frame
Protocols for different services.
As the HSDPA air interface data rates may
be changed with 2 ms period, and FP
overheads are changing roughly between
3 to 19 % as well, its recommended to use
10 % overhead over the payload rates to
include the RLC and FP overheads in
order to estimate the required capacity.
17
2.3 ATM measurements
ATM is providing in most implementations the transport network on terrestrial interfaces within
UTRAN. ATM (Asynchronous Transfer Mode) uses cells of 53 bytes (fixed) length, 5 the ATM
header and the remaining 48 bytes are used for the payload. ATM realizes the Bandwidth on
Demand (BoD) concept, If there is no data, the cells will be idle, empty.
KPIs in order to monitor the transport network:
-Usage ratio (Mean and Maximum per physical interface (STM-1, E1, T1, J1)
-Absolute throughput per Interface (Iub, Iur, IuCS, IuPS)
-Number of Cells discarded due to Header error Check
In some cases if there is a lot of traffic the network elements will discard cells, because there is
no capacity left. (for AAL2 cells after 10 msec if there is no capacity left)
-Cells discarded due to no resources
These KPI verify the availability of the transmission resources and are required to be monitored
in order to detect quality problems of the transmission resources and for the dimensioning
process.
It should be mentioned, that all these measurements should be done independant of the
direction for all interfaces.
18
2.3 ATM Capacity/Quality
ATM measurements
Absolute throughput
Number of Cells discarded due to Header error Check
Usage ratio
per PCM
per
Interface
per STM-1
Per
direction
Maximum
Average
The KPI describes the throughput in
uplink/downlink in cells per second (cps) and
kbits per second (kbps) related to the
interface.
This indicator provides the mean, max or min ratio between received cells related to maximum number of received
cells at physical line. Number of not idle cells in relation to all cells sent during a certain timeintervall (the physical
channel capacity).
Maximum
Average
Can only be seen in the networkelemets, all cells which can not be placed onto a physical interface will
be discarded after a certain period.
Number of Cells discarded due to no resources
Mimimum
Mimimum
This indicator provides the number of discarded ATM cells due to HEC violations at the physical line.
19
3. Throughput Neasurements
1 PS throughput
2 User data throughput
3 Throughput measurements
4 Radio Measurements
5 Codes
20
3.1 PS throughput
f Transport Channel Throughput on Iub/Uu includes:
IP packets
Retransmitted (segments of) IP packets
Padding
RLC/MAC header
RLC Status PDUs (RLC signalling)
f User Perceived Throughput:
IP packets without retransmissions
TCP retransmissions
RLC retransmisions
Application
Server
21
3.1 PS throughput
f If measured throughput is sufficient or not cannot be evaluated without a
reference value.
f Reference value = max. possible bit rates, also known as RAB-Type and RB-
Type
PDP Context: UL/DL 64/384 kbps negotiated
RAB-Type: UL/DL
64/384 kbps assigned RB-Type 1: UL/DL
64/64 kbps assigned
RB-Type 2: UL/DL
32/32 kbps assigned
RB-Type 3: UL/DL
64/128 kbps assigned
Dynamic radio bearer
reconfigurations on Iub/Uu
controlled by RNC
t
1
t
2
22
3.1 User throughput on IuPS
Iub
Serving
Iur
IuCS
IuPS
Drift
time
Idle and Unassigned Cells
Physical capacity
User data
Signaling information
23
3.1 PS User data throughput
ATM Throughput on Iu-PS Interface
Downlink
Uplink
kbps
ATM cells
The KPI describes the average throughput in uplink in cells per second (cps) and kbits per second (kbps) related
to the Iu-PS interface to SGSN (Iu-PS).
The KPI describes the average throughput in Downlink in cells per second (cps) and kbits per second
(kbps) related to the Iu-PS interface to SGSN (Iu-PS).
KPI is related to measurements taken on ATM level and comprises both protocol overhead and additional
signaling VC traffic contained in the relevant VPs on Iu-PS interface to SGSN.
Maximum
Average
kbps
ATM cells
Maximum
Average
2+
3.2 User data throughput
ATM Throughput on Iu-CS Interface
to the Iu-CS interface to MSC.
(kbps) related to the Iu-CS interface to MSC.
ATM Throughput on Iur Interface
to the Iur.
(kbps) related to the Iur.
Downlink
kbps
ATM cells
Maximum
Average
Uplink
kbps
ATM cells
Maximum
Average
Uplink
kbps
ATM cells
Maximum
Average
Downlink
kbps
ATM cells
Maximum
Average
2S
3.2 IuB user-throughput
Iub
Serving
Iur
IuCS
IuPS
Drift
User data
Idle and Unassigned Cells
Physical capacity
User data
Signaling information
O&M information
PS data
CS data
26
3.2 IuB user-throughput
Iub
Serving
Iur
Drift
Physical
capacity
JT1, T1 1,544 1,536 3622
E1, ATM 2,048 1,920 4528
nxJT1, nxT1 nx1,544 nx1,487274 nx3592
n x E1 IMA, ATM nx2,048 nx1,904070 nx4490
STM1, ATM 155,52 149,76 353207
Iub interface
type
Nominal bit
rate (Mbps)
Transfer Bit
Rate (Mbps)
Cell rate
(Cps)
CPS Cells Per Second
27
3.2 Iub User Throughput
User throughput on Iub
PS Traffic
PS Traffic HSDPA
CS traffic
DL
UL
Maximum
Average
The KPI describes the max/mean/min PS
user data throughput on DCH in
uplink/downlink in kbits per second (kbps) on
Iub. Per Node B.
Maximum
Average
Mimimum
Mimimum
This indicator is an estimation of the max/mean/min CS user
data throughput in kbit per second per Node B on the Iub
interface in the uplink/downlink direction.
The KPI describes the max/mean/min HSDPA
throughput in uplink/downlink in kbits per
second (kbps) on Iub. Per Node B and per
user.
Maximum
Average
Mimimum
PS Traffic FACH
PS Traffic on DCH
Maximum
Average
Mimimum
The KPI describes the max/mean/min FACH
throughput in uplink/downlink in kbits per
second (kbps) on Iub. Per Node B and per
user.
PCH load Maximum
Average
Mimimum
This measurement is calculated by the ratio out of the
number of sent messages on the PCH to the maximum
capacity of the PCH.
28
3.2 PS throughput
f KPIs that do not help to optimize the network by their own:
Number of PS Data SDUs (= IP packets) on IuPS *
Data volume of PS services on IuPS *
f Why they do not help to optimize the network?
Number of PS Data SDUs (= IP packets) is not an equivalent of traffic, because IP
packets have variable size (576 up to 65,535 bytes)
Data volume cannot be compared to available or required bandwidth
f What network operators need:
* Often found in NEM KPIs defintions as stand-alone KPIs, because e.g. RNC is not able to
measure the throughput (too complicated algorithms, too many system resources required)
# of PS Data SDUs x Length of SDUs (bit)
Time (s)
=
User Perceived (IP)
Throughput
29
Radio Measurements
1 Measurements
2 UL/DL Power
3 Interference
30
4.1 Measurements
The measurement of total received
wide band power per cell is initiated
by CRNC after the common transport
channels of the cell have been set
up.
With Common Measurement
Initiation message a measurement ID
is assigned that is related to the
parameter to be measured as well as
to the cell ID (c-ID). In report
characteristics section the time
interval of measurement is defined.
After first timeout of the
measurement period timer the first
Common Measurement Report with
appropriate measurement ID is sent
by the cell containing the current
RTWP (Received Total Wideband
Power) value measured. Common
Measurement Report and hence
measurement procedure in cell will
be reported periodically as specified
during initialisation.
millisecond (1... 6000 ms; step 10 ms)
Report Periodicity Value
minute (1... 60 min; step 1 min)
Common Measurement Type
Received Total Wideband Power (RTWP)
Transmitted Carrier Power
Acknowledged PRACH Preambles [FDD only]
Acknowledged PCPCH Access Preambles [FDD only]
Detected PCPCH Access Preambles [FDD only]
UTRAN GPS Timing of Cell Frames for UE Positioning,
SFN-SFN Observed Time Difference
Common Measurement Object Type
cell
RACH
CPCH (normally not implemented)
31
4.1 Measurements
Measurements on dedicated resources
(radio links) have their own NBAP
signalling procedures. For start of radio link
measurements the NBAP procedure
DEDICATED MEASUREMENT
INITIATION is used. The associated
initiating message specifies the
measurement itself, as well as reporting
characteristics.
Dedicated measurements are done either
on a single radio link RL or a radio link
set RLS. A single radio link is a pair of
uplink spreading code and downlink
spreading code (spreading code =
scrambling x channelization code). If a UE
has several radio links (multi-code usage)
with the same cell several radio links can
be bundled to a radio link set. The whole
radio link set requires only one DPCCH
downlink. A dedicated measurement
always is associated with a Dedicated
Measurement Object which is either a
radio link or a radio link set.
Dedicated Measurement Object Type
radio link (RL)
radio link set (RLS)
Dedicated Measurement Type
Signal Interference Ratio (SIR)
Signal Interference Ratio Error (SIR Error) [FDD only]
Transmitted Code Power
Received Signal Code Power (RSCP)
[3.84/1.28 Mcps TDD only]
Rx Timing Deviation [3.84 Mcps TDD only]
Round Trip Time (RTT) [FDD only]
millisecond (1... 6000 ms; step 10 ms)
Report Periodicity Value
minute (1... 60 min; step 1 min)
32
4.1Radio Measurements in
messages
New
Node B
Drift
Serving
NBAP: Common Measurement Report
received-total-wide-band-power (RTWP)
transmitted-carrier-power (TCP)
received-total-non EDCH wide-band-power
transmitted-non HSDPA carrier-power
acknowledged-PRACH-preambles (only FDD)
acknowledged-PCPCH-access-preambles (only FDD)
NBAP: Common Measurement Report
Time interval of
measurement is defined during
system start-up by CRNC
SIR
SIR-error (only FDD)
transmitted-code-power
round-trip-time (only FDD)
Time interval of
measurement is defined during
DCH setup initiating message
of the RADIO LINK SETUP
Procedure by CRNC
NBAP: Dedicated Measurement Report
NBAP: Dedicated Measurement Report
NBAP:Dedicated Measurement Initiation
NBAP: RADIO LINK SETUP
.........
33
4.2 Uplink Measurements
f Reporting ranges for RTWP: -112 -50 dBm
f The measurement period should in the range of100 ms
-50.0 dBm RTWP RTWP_LEV_621
-111.9 dBm RTWP < -111.8 dBm RTWP_LEV_002

-112.0 dBm RTWP < -111.9 dBm RTWP_LEV_001
RTWP < -112.0 dBm RTWP_LEV_000
Measured value Reported value
The counter values are given in standardized RSSI values (0-621). This means that the values
must be converted to dBm values (-112.1 - -50.0) before the KPI can be calculated. It is
possible that the counter in the formula is not updated during the measurement period,
meaning that the denominator counter is not updated. These samples should be filtered out.
When using the formula, linear scale has to be used with calculations. This means that the
dBm values in the counters must be converted to Watts and, after the calculation is done, the
result must be converted back to dBms.
Value mapping according 3GPP TS 25.133
The value in dBm can be derived by:
[-112.0+ (RTWP_LEV)/10] dBm
This KPI may be used to identify sites which are experiencing:
-high uplink traffic load,
-high background interference,
-high uplink intercell interference
-HW problems or wrong configuration (eg with Tower Mounted Amplifier)
3+
4.2 Transmitted Carrier Power
f
Reported value Measured quantity value Unit
UTRAN_TX_POWER _000 Transmitted carrier power = 0 %
UTRAN_TX_POWER _001 0 < Transmitted carrier power 1 %
UTRAN_TX_POWER _003 2 < Transmitted carrierpower 3 %

unit: %
measurement interval: 100 ms
range/step: 0%...100 % / 1 %
calculation: Transmitted Carrier Power = current DL Tx Pwr / max DL Tx Pwr
coded as: INTEGER(0..100)
Ratio between current transmission power on a downlink carrier and maximum
configured transmission power on that carrier.
3S
4.2 Power/Cell Load
Cell load
Uplink load
Downlink
This indicator provides the mean, max or min value of the measured transmitted carrier power of all codes not
used for HS-PDSCH or HS-SCCH in Watt or dBm. It is extracted from the NBAP common measurement report at
regular intervals. The cell DL power gives an indication about cell load. Then usually this is set as percent of the
maximum power.
The measured value indicates always a range with a step size of 0.1dBm.
Maximum
Minimum
Average
This indicator provides the mean, max or min value of the measured Received carrier power in Watt or dBm. It is
extracted from the NBAP common measurement report at regular intervals.
The cell UL power gives an indication about cell load. Then usually this is set as percent in relation of UL noise.
The measured value indicates always a range with a step size of 0.1dBm. If e.g. the measured value is 110 the
formula results is (-112 +110 * 0.1) = -92dBm (from -92.1 .. -92.0dBm).
UL noise indicates thermal noise. The value is in the range of = -105dBm. Uplink cell load is just a rough
indication because the background noise is not known.
= --------------------------------------------------------------------- 100%
Maximum
Minimum
Average
Uplink Cell Load
Noise
Received Total Wideband Power
36
4.2 Transmitted Code Power
Reported value Measured quantity value Unit
UTRAN_CODE_POWER _010 -10.0 Transmitted code power < -9.5 dBm

UTRAN_CODE_POWER _120 45.0 Transmitted code power < 45.5 dBm
unit: dBm
measurement interval: 100 ms
range/step: -10 dBm ... 46 dBm / 0.5 dBm
coded as: INTEGER(0..127); values 0..9 and 123..127 not used [NBAP]
Downlink transmission power of a single scrambling / channelization code pair,
measured as transmission power of the associated DPCH pilot bit power.
37
For dedicated physical channels the Node B can report the used transmission power on the relevant
downlink DPCH. This measurement is provided by the so called Transmitted Code Power (UTRAN CODE
POWER). It can be used by the RNC to trigger UE measurements on inter-frequency or inter-RAT neighbor
cells.
The measurement is done on the downlink DPCH pilot bits. During setup of a radio link or radio link set, the
RNC indicates three power offsets PO1, PO2 and PO3 to the Node B. The parameters can be found in the
initiating message of the RADIO LINK SETUP procedure. Of interest here is the value PO3, it indicates
the power difference of data part (coded DCH bits) relative to the power of the DPCH pilot bit field. PO3 can
be set in a range between 0 dB and 6 dB in 0.25 dB steps. The transmitted code power is the power of the
pilot bits. Using the power offset it is possible to determine the power of each of the various bit fields in a
DPCH slot.
The Node B reports the transmitted code power as part of the dedicated measurement report procedure. It
can be found as information element Transmitted Code Power Value inside Dedicated Measurement
Value. Two procedures provide this parameter:
Dedicated Measurement Initiation (successful outcome message),
Dedicated Measurement Report (initiating message).
If a UE uses several channelization codes in parallel (multi-code usage) and thus has not a single radio link,
but a radio link set, then the transmitted code power can be measured only for the whole radio link set. This
is because DPCH pilot bits exist only for the very first channelization code, but not for second or third, etc.
38
Iub
C-RNC Node B
UE
Data 1 Data 2
T
P
C
TFCI
Pilot
Bits
Slot #0 Slot #1 Slot #14
DPCH
PO2
PO1
PO3
PO1 : Power offset data-TFCI
PO2 : Power offset data-TPC
PO3 : Power offset data-pilot
Power Offset [NBAP]:
range: 0 dB ... 6 dB
step: 0.25 dB
coding : INTEGER(0..24)
(PowerOffset in dB x 4)
Transmitted Code Power
39
4.2 Transmitted/Received Code
Power
Power per user
Uplink
Downlink per radio link/radio link set
The current transmit carrier power and received total wide band power value is extracted from the
NBAP dedicated measurement reports at regular intervals. Alternatively the common
measurement report may be used as an estimate:the total transmit power divided by the number
of active radio links. Unit : percent.
Maximum
Minimum
Average
The common measuremnt may be used to give an estimate, the Total Received Power divided by
the number of active Radio Links in that cell.
Maximum
Minimum
Average
+0
4.3 UL Interference
Measurement Reports
Troubleshooting and
optimization strategies:
find external interferers,
setup more cells
Users expression:
poor QoS
RRC Blocking Rates
RAB Setup Failures
Call Drop Rates
-95 dBm
+1
4.3 Downlink Interference
Measurements
Cell
RRC establishment request messages
The Chip Energy over Noise (Ec/No) is for a power level independent quality criterion of received
signals. The EcNo is not really a UE measurement, rather it is a calculated value. It is defined as ratio
between received signal code power RSCP and UTRA carrier strength (UTRA carrier RSSI).
A UE reports the EcNo of CPICH (CPICH Ec/No) of serving and neighbor cells. Obviously this is done via
RRC protocol. Two information elements contain Ec/No measurement results: Measured Results on
RACH and Cell Measured Results. Measured Results on RACH contains measurements done by UE
in idle mode or CELL_FACH state. These measurements are used by the RNC for open loop power
control on FACH. The following messages may contain ECNO values:
RRC CONNECTION REQUEST (for idle UE),
INITIAL DIRECT TRANSFER and UPLINK DIRECT TRANSFER (for CELL_FACH mode only),
CELL UPDATE and URA UPDATE (conditional, depends on measurement configuration in
SIB11/SIB12),
MEASUREMENT REPORT (CELL_FACH mode only).
+2
4.3 Downlink Measurements
The information element Cell Measured Results occurs in the MEASUREMENT REPORT
message only. The reporting scenarios for Ec/No are also applicable for RSCP and Pathloss
reporting Chip Energy over Noise (Ec/No Ec/Io)*
unit: dB
range/step: -24 dBm ... 0 dBm / 0.5 dBm
calculation: CPICH Ec/No = CPICH Ec/No / UTRA carrier RSSI
coded as: INTEGER (0..49) [RRC]
Received energy per single bit divided by power density on the radio band. Calculated as RSCP /
UTRA carrier RSSI. Only reported for donwlink measurements by UE (RRC).
Reported Value Range Unit
CPICH_Ec/No_00 CPICH EcIo < - 24.0 dB
CPICH_Ec/No_01 - 24.0 CPICH EcIo < - 23.5 dB
... ... ...
CPICH_Ec/No_47 - 1.0 RSCP < - 0.5 dB
CPICH_Ec/No_48 - 0.5 RSCP < 0 dB
CPICH_Ec/No_49 0 RSCP dB
* Ec/No and Ec/Io are now considered as equivalent terms. In CDMA theory No covers all wideband
power including wanted and unwanted signals, whereas Io means only interfering signals. Under normal load the
difference between Io and No is neglectable.
+3
Cell A
Cell C
4.3 Cell Overlapped Matrix
fCell Overlapped Matrix can be generated by collecting Iub RRC measurement
reports messages using a protocol analyzer; the Iub interface is a privileged
monitoring point where radio interface measurements are constantly flowing from
the handsets (RRC measurement reports).
Cell b
Cell E
RRC measurement reports
++
+.S. Codes in UNTS
1 Code resources
2 DL Channelization Codes
3 UL Scrambling codes
4 Codes for HSDPA
+S
5.1 Code resources
In WCDMA, all data that is transmitted over the Uu interface is spread withe the help of a
spreading code. Spreading means that each original bit of data, or symbol as it is called, is
modulated into a number of chips, thus increasing the bandwidth of the signal. The spreading
factor indicates the number of chips used to represent one symbol. The length of the spreading
code (channelisation code) is exactly one symbol long in chip units. For example, if the
spreading factor is 128, then each symbol is coded into 128 chips, which is the length of the
code. Orthogonal variable spreading factor (OVSF) spreading codes are used to differentiate
the connections in downlink and the dedicated physical data channel (DPDCH) and dedicated
physical control channel (DPCCH) in uplink.
Scrambling means that a scrambling code is applied to the spread signal. Scrambling and
channelisation codes are used as indicated in the table below.
Users within one cell Data and control
channels from the same
phone
Channelization codes
User separation User separation Scrambling codes
Downlink Uplink Code type
+6
5.1 Code utilization
Downlink
Uplink
DL SC 1
DL SC 2
UL SC 1 UL SC 2
CC 1
CC 2....
CC 1 control
CC 2 user data
CC 1 control
CC 2 user data
+7
5.1 Code utilization
A total of 2
18
-1 = 262,143 scrambling codes, numbered 0.262,142 can be
generated. However not all the scrambling codes are used. The scrambling codes
are divided into 512 sets each of a primary scrambling code and 15 secondary
scrambling codes. Under each Scrambling Code one Channelization Code Tree is
available.
Hence, according to the above, scrambling codes k = 0, 1, ., 8191 are used.
Each of these codes are associated with a left alternative scrambling code and a
right alternative scrambling code, that may be used for compressed frames.
Set 3:
1 Primary SC
Secondary SC 1
Secondary SC 2
.
Secondary SC 15
Set 2:
1 Primary SC
Secondary SC 1
Secondary SC 2
.
Secondary SC 15
Set 1:
1 Primary SC
Secondary SC 1
Secondary SC 2
.
Secondary SC 15
Set 511:
1 Primary SC
Secondary SC 1
Secondary SC 2
.
Secondary SC 15
Set 0:
1 Primary SC
Secondary SC 1
Secondary SC 2
.
Secondary SC 15
Set 510:
1 Primary SC
Secondary SC 1
Secondary SC 2
.
Secondary SC 15
TS 25.213: Spreading and modulation (FDD)

+8
5.1 DL Code utilization
DL SC
There are three kinds of scrambling codes: primary, secondary
and alternative, as defined in 3GPP TS 25.213. Downlink primary
scrambling codes are used for cell separation. One primary
scrambling code is allocated for each cell. Secondary scrambling
codes are usually not used. Alternative scrambling codes can be
used in compressed mode.
CC 1
CC 2....
Downlink spreading codes separate connections within one cell. Because of the
orthogonality of the downlink spreading codes, connections using the same
scrambling code (that is, in one and the same cell) do not ideally cause any
interference to each other. In practice, however, because of multipath
propagation some of the orthogonality is lost when the signals travel over the Uu
interface. In order to maintain orthogonality, the codes have to be managed with
the help of a code tree. The rules for managing codes with the code tree are
simple: codes are orthogonal if they are not descended from an already used
code. With the help of the code tree, the codes are kept orthogonal to each other
in different code allocation and release situations. If a code Cm(n) is in use, all
codes that are below it in the same branch are unavailable as well as all codes
above it in the same branch to the root. The spreading codes for the primary
common pilot channel (P-CPICH) and the primary common control physical
channel (P-CCPCH) are fixed; FACH, PCH and SCH permanently allocated to a
code during system start.
+9
5.2 DL Channelization Codes
SF = 128
SF = 64
SF = 32
SF = 8
SF = 16
SF = 4
SF = 2
SF = 1
Codes for CPICH and P-CCPCH are fixed, for other codes
Options are available, FACH and PCH for example can be
multiplexed on one SF 64 code,
SF = 256
CPICH
P-CCPCH
FACH
PICH
AICH
PCH
Only
SF 4-
256 in
use for
UMTS
In DL
S0
5.2 Code usage
Code usage rate
Codes per SF
The indicated code usage rate per cell applies only for DL. This indicator can be given as mean,
minimum and maximum value. The formula above divided by "512" applies to the implementation
that one code tree is used. If two (secondary) code trees are used the denominator has to be
"1024".
Maximum
Minimum
Average
Code requests
Number of attempted code requests per spreading factor
Number of successfull code requests per spreading factor
RRC: RRC CONNECTION REQUEST message was received and a channelization code allocation
was attempted/successfull.
RANAP: RAB ASSIGNMENT REQUEST message was received and a channelization code
allocation was attempted/successfull.
QAAL2(Iu): ESTABLISH RESPONSE message was received and a channelization code allocation
RRC: MEASUREMENT REPORT message was received and a channelization code allocation
S1
5.3 Uplink Scrambling codes
Uplink scrambling codes separate different UEs in the same cell. Thus, uplink scrambling
codes are UE-specific and allocated when the connection is established. There are two
different kinds of codes available, long and short scrambling codes, but only the long ones
are used. A UE can use the same code for the duration that it is connected to a 3G network.
Even if the UE moves across the border between two neighbouring RNCs, the code stays
the same. The codes are indexed from 0 to 224(16,777,216). A centralised procedure in the
RNC allocates the codes. Different RNCs allocate their own codes and it is possible to have
the same codes in different RNCs. In the worst case, this causes some interference in the
RNC border area if two similarly coded connections are received in the same cell. This can
be avoided by defining different ranges of uplink scrambling codes for neighbouring RNCs.
Centralised management of uplink scrambling codes in the 3G network is not needed, but
the range for each RNC should be correctly defined by the operator.
There is so no KPI needed
Uplink
UL SC 1 UL SC 2
CC 1 control
CC 2 user data
CC 1 control
CC 2 user data
S2
+.6. Qualityfload related KP!
1 Admission Control
2 User data throughput
3 Throughput measurements
4 Radio Measurements
5 Codes
S3
6.1 Quality settings
RAB Assignment
request
(1) RAB attributes:
SDU ER
Traffic class
Max bit rate
AC & PS:
(2) RB attributes
Target BLER
Target EbNo
Initial SIR
TrCh parameters
PDCP & physical channel parameters
(3) Power increase estimation
(4) Admission decision:
RAB denied or
RAB admitted
LC
(5) Load change report
Where:
SDU ER= system data unit error rate
RAB=radio access bearer
RB=radio bearer
TrCh= traffic channel
PDCP=packet data convergence protocol
RB set-up
S+
6.1 Admission Control
Admission Control
Number of rejections per cause
Condition for this measurement is the rejection of a radio bearer establishment request due to the
causes listed below. This shall apply whenever admission control is called, be it for a RAB
assignment request from the CN, Branch addition procedure, Hard handover procedure, RRC
connection re-establishment, CTS, BRA, or relocation request. As consequence the
establishment request for the new radio bearer will be rejected.
Causes:
Cell restriction.
Maximum uplink load failure
Maximum downlink load failure
Code allocation failure
Congestion Control
Other causes
This measurement provides the number of times admission control rejects the
RAB establishment request per cell. For each rejection cause a separate
subcounter is defined.
new calls within own RNC
incoming Inter-RNC calls
SS
6.2 Services per cell
This measurement provides the mean number of bearer services per cell related. For PS
Interactive/Background services the bearer service may be referred to as RRC state CELL_FACH or
CELL_PCH or the HS-DSCH bearer is applicable.
-When a bearer service is set up, which means the RANAP: RAB ASSIGNMENT RESPONSE
message was sent toward CN. Update of the counter shall be related to the assigned bearer service,
not to the required service.
When a bearer service was released triggered by the RANAP: RAB ASSIGNMENT REQUEST
messages indicating RABs to be released was received from CN or when RANAP: RAB RELEASE
REQUEST message was sent toward CN. Remark, that all cells of the active link set have to be
considered. The same applies if the RAB is released per RANAP: IU RELEASE
COMMAND/REQUEST message.
In case of Branch addition the bearer service shall be considered within the added cell.
In case of successful hard handover the corresponding counter shall be decremented within the
originating cell(s) and incremented within the target cell(s).
In case of channel type switching an existing bearer type is decremented and the counter
corresponding to the new bearer type is incremented.
In case of Bit Rate Adaptations.
S6
6.2 Services per cell/Iub
Bearer Service Per cell
CS traffic
DL Cell load
UL Cell load
Maximum
Average
Mimimum
PS traffic
Maximum
Average
Mimimum
Unit: erlang
Bearer Service Per Iub
CS traffic
DL Node B load
UL Node B load
Maximum
Average
Mimimum
PS traffic
Maximum
Average
Mimimum
Unit: erlang
To measure per Node
B means that all softer
handover are
eliminated.
Bearer Service allocation successes per cell
Per bearer
S7
6.2 Services per cell
SRB 3.4/3.4
SRB 13.6/13.6
PS interactive/background in CELL_FACH state
PS interactive/background in CELL_PCH state
CS AMR speech 12.2
CS conversational UDI 64/64
CS conversational UDI 32/32
CS conversational UDI 28.8/28.8
PS conversational 8/8
PS conversational 16/16
CS streaming 57.6/57.6
PS streaming 16/64
PS streaming 8/16
PS streaming 8/32
PS streaming 16/128
PS streaming 32/256
PS interactive/background 64/384
PSinteractive/background 64/128
PS interactive/background 64/0 + HS-DSCH
PS interactive/background 384/0 + HS-DSCH
...................to be continued
S8
MAC-d
6.3 RLC Retransmission Rate for
PS Calls
RLC measurement can be used to measure only those connection types, which use the
acknowledged mode. Those connection types are listed below:
- signalling radio bearer of all call types
- PS non-real time (background, interactive) user data connections, including HSDPA
- PS real-time (streaming) user data connections with long SDU transfer delay requirement in the
subscriber's QoS profile.
RLC
buffer
RNC
PDCP
buffer
IuPS
RLC PDU
RLC PDU
IP packets
IP packets
RLC SDU
RLC SDU
RRC
RRC
Header (de)compression
S9
6.3 RLC observations
RLC observations
DL RLC PDU discards
DL PDCP and RLC buffers
RLC RETRANSMISSION DISTRIBUTION
Buffer occupancy for New RLC and allready transmitted RLCs
Number of RLC PDUs transmitted once, twice, ...
Number of RLC PDUs discarded in DL
UL/DL RLC net throughput
DL RLC PDU transmission quality
DL RLC SDU transfer delay
Transfer delay is the time difference between when the SDU is received from the upper layer (RRC
or PDCP) and when the last PDU containing data from that SDU is acknowledged by the UE as
successfully transferred or if it is deleted, because there is no ack.
The average downlink net PDU throughput of RLC AM connections. Does not include retransmissions.
The ratio between unsuccessfully transmitted RLC AM DL PDUs and all transmitted RLC AM DL
PDUs (including retransmissions).
60
6.3 Tr. Channel vs. User
Perceived Throughput
f Downlink Transport Channel Throughput and DL User
Perceived Throughput of problem zone
Bit rate on the transport channel is sufficient, but bit rate of IP
packets is low. Assumption: too many RLC retransmissions.
61
6.4 BLER Measurements
The RNC's internal constant values define the allowed non-real time dedicated channel bit rates. The
transmission time interval (TTI) of the each allowed dedicated channel bit rate is also an RNC internal
constant value. This means that the operator cannot configure the allowed bit rates and the
corresponding transmission time intervals.
The uplink and downlink transport format sets and transport format combination sets produced by the
UE-specific packet scheduler are delivered to the MAC layer of the RNC, the MAC layer of the UE
and the BTS. MAC selects the appropriate transport format combination (TFC) to be used in L2 PDU
transportation.
62
6.4 BLER Measurements
CLOSED LOOP PC
TBL Rx
fals CRC
BLER
est
_
_
#
#
=
Node B measurements:
IE reporting
interval
Node B measurements are sent to the RNC
periodically
Short reporting period assure good accuracy of
radio resource management algorithms but big
signalling overhead
The measurements can be averaged over the
special measurement window
63
6.4 BLER values
The uplink transport channel block error rate BLER is not a specified measurement value. It is the serving
RNC that measures it, so that there is no external reporting of it.
The serving RNC receives the transport blocks of a single transport channel from uplink transmission of a
UE. In soft handover scenarios the serving RNC receives the same transport block from several cells, from
each soft handover radio link one block with the same data will come. The serving RNC (or already a drift
RNC) performs now so called combining. This means whenever the considered transport block is from one
radio link available without CRC error, it is taken. The transport block data from the other radio links is
discarded.
Of course it can happen that a transport block is received via all radio links with CRC error. In this case a
block error is detected. The serving RNC counts for each transport channel of a UE the total number of
received transport blocks (the same transport block from different radio links is counted once) and the
number of detected block errors (CRC error). The ratio between the two is the transport channel block
error rate (TrCH BLER).
The serving RNC uses the TrCH BLER for radio management (handover decisions, measurement control
trigger) and for outer loop power control (see later).
Obviously it is the serving RNC that measures the TrCH BLER for uplink TrCH and uses it, thus there is no
external reporting defined for uplink TrCH BLER values. So it is up to the serving RNC vendor or external
performance monitoring tools to report UL TrCH BLER measurements. No specification is available.
6+
6.4 UL TrCH BLER
Uplink Transport Channel Block Error Rate
Ratio between received transport blocks of an UL TrCH with CRC error and the total
number of received transport blocks of an UL TrCH. Measured by RNC.
S-RNC
Node B
UE
Node B
Node B
TB #1 CRC
TB #2 CRC
TB #K CRC
. . .
TB #1 CRC
TB #2 CRC
TB #K CRC
. . .
TB #1 CRC
TB #2 CRC
TB #K CRC
. . .
TB #1 CRC
TB #2 CRC
TB #K CRC
. . .
CRC CRC error
CRC
correct TB
TrCH BlER
=
No. CRC Error
Total No. CRC
6S
6.4 BLER
Block Error Rate
Non Real Time Radio Bearer UL BLER [%]
Real Time Radio Bearer UL BLER [%]
AMR RB UL BLER [%]
Buffer occupancy for New RLC and allready transmitted RLCs
Number of RLC PDUs discarded in DL
The measured Block Error Rate for AMR Radio Bearers in Uplink. This KPI is based on
Radio Connection Performance Measurement
=> All active set sizes allowed. If one cell is problematic, and further information is needed
from that cell, then it is possible to set active set size to
This KPI measures only A DCH (for example AMR 12.2 has 3 coordinated DCHs: A, B,
and C).

4xdolw/ $VSHFWV

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

4xdolw/ $VSHFWV

Diunggah oleh

Hak Cipta:

Format Tersedia

TA-TC 6270 /Version 01/Chap.

-111.9 dBm RTWP < -111.8 dBm RTWP_LEV_002

TS 25.213: Spreading and modulation (FDD)

Anda mungkin juga menyukai