Escolar Documentos
Profissional Documentos
Cultura Documentos
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.
TA-TC 6270 /Version 01/Chap. 04 Quality
3
1.Quality aspects in UTRAN
Iub
Serving
Iur
IuCS
IuPS
Drift
Power
Base Band
Resources
Processors
Power Power ATM
Hardware
ATM
Code
Processors
TA-TC 6270 /Version 01/Chap. 04 Quality
+
+.2. ATN Neasurements
1 ATM in UTRAN
2 AAL2
3 ATM Measurements
TA-TC 6270 /Version 01/Chap. 04 Quality
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.
TA-TC 6270 /Version 01/Chap. 04 Quality
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
TA-TC 6270 /Version 01/Chap. 04 Quality
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.
TA-TC 6270 /Version 01/Chap. 04 Quality
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
TA-TC 6270 /Version 01/Chap. 04 Quality
9
2.2 AAL2 and CAC
Application Protocol : Bearer Setup Request
ALCAP : Bearer Establishment Request ERQ
ALCAP : Bearer Establishment Confirmed ERC
Application Protocol : Bearer Setup Complete
NBAP, RNSAP, RANAP
Connection
Admission Control
Connection
Admission Control
TA-TC 6270 /Version 01/Chap. 04 Quality
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
......
TA-TC 6270 /Version 01/Chap. 04 Quality
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
TA-TC 6270 /Version 01/Chap. 04 Quality
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
TA-TC 6270 /Version 01/Chap. 04 Quality
13
2.2 AAL2 Virtual Connections
Application Protocol : Bearer Setup Request
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
TA-TC 6270 /Version 01/Chap. 04 Quality
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.
TA-TC 6270 /Version 01/Chap. 04 Quality
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
TA-TC 6270 /Version 01/Chap. 04 Quality
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.
TA-TC 6270 /Version 01/Chap. 04 Quality
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.
TA-TC 6270 /Version 01/Chap. 04 Quality
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.
TA-TC 6270 /Version 01/Chap. 04 Quality
19
3. Throughput Neasurements
1 PS throughput
2 User data throughput
3 Throughput measurements
4 Radio Measurements
5 Codes
TA-TC 6270 /Version 01/Chap. 04 Quality
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
TA-TC 6270 /Version 01/Chap. 04 Quality
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
TA-TC 6270 /Version 01/Chap. 04 Quality
22
3.1 User throughput on IuPS
Iub
Serving
Iur
IuCS
IuPS
Drift
time
Idle and Unassigned Cells
Physical capacity
User data
Signaling information
TA-TC 6270 /Version 01/Chap. 04 Quality
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
TA-TC 6270 /Version 01/Chap. 04 Quality
2+
3.2 User data throughput
ATM Throughput on Iu-CS Interface
The KPI describes the average throughput in uplink in cells per second (cps) and kbits per second (kbps) related
to the Iu-CS interface to MSC.
The KPI describes the average throughput in Downlink in cells per second (cps) and kbits per second
(kbps) related to the Iu-CS interface to MSC.
ATM Throughput on Iur Interface
The KPI describes the average throughput in uplink in cells per second (cps) and kbits per second (kbps) related
to the Iur.
The KPI describes the average throughput in Downlink in cells per second (cps) and kbits per second
(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
TA-TC 6270 /Version 01/Chap. 04 Quality
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
TA-TC 6270 /Version 01/Chap. 04 Quality
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
TA-TC 6270 /Version 01/Chap. 04 Quality
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.
TA-TC 6270 /Version 01/Chap. 04 Quality
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
TA-TC 6270 /Version 01/Chap. 04 Quality
29
Radio Measurements
1 Measurements
2 UL/DL Power
3 Interference
TA-TC 6270 /Version 01/Chap. 04 Quality
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)
TA-TC 6270 /Version 01/Chap. 04 Quality
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)
TA-TC 6270 /Version 01/Chap. 04 Quality
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
.........
TA-TC 6270 /Version 01/Chap. 04 Quality
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