COMIT Training Course 1

Oct - 2015

Objectives
At the end of this module, you will be able to
Name the structure of UTRAN specific signalling interfaces

Understand the RAB QoS parameters

UMTS Release 99
In December 1999, the first UMTS Release was frozen. This release is commonly called UMTS Release 99. In the
specification phase, two main objectives had to be met:
New radio interface solution
Core Network (CN) evolution

Mobile communication became a big business case in the 90s with unexpected growth rates.
In some areas, this imposed capacity problems. There were not enough radio resources available to supply the
subscribers in a satisfying way.
The 2nd generation mobile communication systems were still optimised for speech transmission.
Also in the 90s, there was an unprecedented growth in data communications. This was mainly caused by the
introduction of user friendly GUIs, the browsers, to serve in the net, and by the steadily dropping costs for
computer and router.

3G RPLS / AA / 10/2008

UMTS Release 99 (cont.)

Therefore, during the standardisation process, one major focus lay on the radio interface solution.
It had to be more efficient to serve more subscribers in one geographical area, resp. to allow higher data
rates.
On the other hand, more flexibly was required, too, so that all kinds of present and future multimedia
applications could be served.
CDMA was selected as multiple access technology for the radio interface solution. The UMTS radio
interface solution is often called WCDMA, because CDMA is used on 5 MHz.
Two duplex transmission solutions are available with UMTS Release 99, one based on the TDD and one
based on the FDD mode.
The introduction of a new radio interface solution required a new design of the whole radio access network,
which is called UTRAN.

CN evolution
There are more than 500 GSM operators worldwide. So one requirement to UMTS Release 99 was to enable a
smooth evolution from 2G to 3G. Therefore, the UMTS Rel99 CN is an enhanced GSM NSS.

3G RPLS / AA / 10/2008

(Adopted from TR 21.902)

3GPP Release 4

3GPP Release 4 is a further enhancement of 3GPP Release 1999.

3GPP Release 4 contains, but is not limited to
UTRA FDD repeater function
low chip rate TDD option
700 MHz support for GERAN,
e2e transparent packet streaming service
Tandem Free Operation
Transcoder Free Operation
IP transport of CN protocols
bearer independent CS core network
CAMEL enhancements and OSA enhancements.
The 3GPP Release 4 was functionally frozen in March 2001.

3G RPLS / AA / 10/2008

(Adopted from TR 21.902)

3GPP Release 5

3GPP Release 5 is a further enhancement of the previous releases.

3GPP Release 5 contains, but is not limited to,

High Speed Downlink Packet Access (HSDPA)

Initial phase of the IP Multimedia Subsystem (IMS)
Wideband AMR
Location Services enhancements
UMTS in 1800/1900 MHz bands (release independent)
IP transport in the UTRAN
UTRAN sharing in connected mode and security enhancements.

The 3GPP Release 5 was functionally frozen in March 2002 and the remaining part in June 2002.

3G RPLS / AA / 10/2008

(Adopted from TR 21.902)

3GPP Release 6

Release 6 (frozen 09/2005) . contains, but is not limited to

FDD Enhanced Uplink (HSUPA)

FDD Enhanced Uplink - Physical Layer

FDD Enhanced Uplink - Layer 2 and 3 Protocol Aspects

FDD Enhanced Uplink - UTRAN Iub/Iur Protocol Aspects

FDD Enhanced Uplink - RF Radio Transmission/ Reception, System Performance Requirements and
Conformance Testing
Location Services enhancements 2
WLAN-UMTS Interworking Rel-6

Security

WLAN charging

USIM enhancements for WLAN Interworking

IMS Phase 2
Multimedia Messaging (MMS) enhancements
Multimedia Broadcast/Multicast Service (MBMS)
AMR-WB extension for high audio quality
Push Services and Presence
Network Sharing

NOTE: Nokia/NSN RAN releases (RAN1.5, RAN04, RAS05, RAS 06, RU 10..) do not follow strictly the 3GPP
releases

3G RPLS / AA / 10/2008

(Adopted from Work_plan_3gpp_rel7)

3GPP Release 7

Release 7 (closed 10/2007) with HSPA+ features:

Higher order Modulation
64QAM for the DL; 16QAM for the UL
larger Peak Data rates & Capacity

MIMO Antennas: 2x2 MIMO

larger Peak Data rates & Capacity
Network Architecture Improvements:
Improved latency & efficiency; lower OPEX / CAPEX WLAN charging
Direct Tunneling
Continuous Packet Connectivity CPC / VoIP
higher efficiency; more capacity; less UE battery consumption
Enhanced UE Receiver
more capacity; higher UE throughput
Enhanced Cell_FACH
higher throughput in Cell_FACH
L2 / RLC Optimisation
less L2 overhead; higher net throughput

3G RPLS / AA / 10/2008

3GPP Release 8 & 9

Release 8 (closed 12/2008)

Enhancements for HSPA+ evolution

64QAM & 2x2 MIMO simultaneously

Peak Rates up to 42 Mbps

.
Long Term Evolution (LTE) as new radio access system
and 3GPP System Architecture Evolution (SAE) /
Enhanced Packet Core EPC for GERAN, UMTS and non
3GPP access
.

Release 9 (expected to be closed 12/2009)

LTE-Advanced (LTE-A)

3GPP proposal for IMT-Advanced (4G)

Max. Peak Rate (low Mobility) 1 Gbps DL and up to

500 Mbps (UL)

Max. Peak Rate (high Mobility) 100 Mbps UL & DL

Bandwidth of up to 100 Mbps expected

Advanced MIMO-antenna systems expected

3G RPLS / AA / 10/2008

(Adopted from Work_plan_3gpp_rel8)

UMTS Releases
1999

2001

2002

2006

2007
2008
2009/10
3G RPLS / AA / 10/2008

UMTS Release 99

UMTS CN = enhanced GSM NSS

UTRAN & WCDMA

UMTS Release 4

Bearer independent CS domain

Low chip rate TDD mode
UTRA repeater
MMS

UMTS Release 5

High Speed Downlink Packet Access (HSDPA)

Wideband AMR
Initial phase of the IP Multimedia Subsystem
IP transport in the UTRAN
Location Services enhancements

UMTS Release 6

FDD Enhanced Uplink (HSUPA)

IMS Phase 2
Wireless LAN/UMTS Inter-working
Multimedia Broadcast/Multicast Service (MBMS)
Push Services and Presence.

UMTS Release 7

HSPA+ (MIMO & Higher Order Modulation)

Enhanced UE Receiver
Direct Tunneling

UMTS Release 8

HSPA+ Enhancements
LTE + SAE/EPS

UMTS Release 9

LTE-A: IMT-Advanced (4G) proposal

UMTS Network Architecture

The UMTS CN can be organised into two main domains:
CS domain

This domain offers Circuit Switched (CS) bearer services.

The CS domain is nowadays mainly used for real time data services, including speech and fax
transmission.
The network entities MSC, GMSC and VLR can be found here.
PS domain
This domain offers Packet Switched (PS) bearer services.
It is based on the GSM feature GPRS. Originally, this domain was developed for non-real time
packet switched applications, such as file transfer, email, access to the Internet.
It is used today mainly for MMS. But there are tendencies to improve its offered QoS, so that real
time services can be offered, too.
The SGSN and GGSN are located in the packet switched domain. Other specified PS domain
entities are the BGF and the CGF, which are often offered as stand alone devices.

There are also some network elements, which are shared by the packet switched and circuit switched domain. The
common network elements comprise the HLR, AuC and EIR.
A set of network elements were specified for application provisioning, which can be also found in the CN.
Examples are the Camel Service Environment and WAP. Some service solutions affect the access network, too. See
for instance LCS.
3G RPLS / AA / 10/2008

UMTS Core
Network
CN (Core Network)
GERAN

circuit switched (cs) domain

MSC/VLR

GMSC

HLR
EIR
AC

UTRAN

SGSN

common
cs & ps
network
elements

WAP

PDN

IPbackbone

GGSN
corporate
networks

BGF CGF
Packet Switched (PS) domain

3G RPLS / AA / 10/2008

PSTN/
ISDN

Inter-PLMN
Network

Billing
Centre

UMTS Release 4 core network

In the 3GPP R4 Core Network the MSC evolves to the MSC Server and the MGW.
The MSC Server is responsible e.g. for signalling, paging and collecting charging information while
the MGW is doing a switching.
MSC Server contains a communication management functionality and is also responsible for a
mobility management.
The MGW (Multimedia Gateway) main functions are:
To adapt a conventional signalling between the MSC Server or the GCS (Gateway Control Server)
and different network interfaces
To connect a user data from an ATM/IP backbone into the RAN or circuit switched networks
To provide tones and announcements to end users
To do a transcoding and signal processing for a user plane when it's needed

3G RPLS / AA / 10/2008

UMTS Release 4 core network

3G RPLS / AA / 10/2008

UTRAN

The UMTS Terrestrial Radio Access Network (UTRAN) is the access network, which was developed with
UMTS.

The access network is organised in Radio Network Subsystems (RNS).

Each RNS has one radio resource control unit, called Radio Network Controller (RNC).
The tasks of a RNC can be seen on one figure on the following pages.

In each RNS, there is at least one Node B active, which is connected to its Controlling RNC (CRNC)

A Node B is the 3G base station.

One or several cells can be activated with one Node B.
The main features of a Node B can be seen on one figure of the following pages.

UTRAN

With UTRAN, four new interfaces were specified:

Iu
Iu connects UTRAN with the CN.
A distinguishing is drawn between the Iu connection to the PS domain, which is labelled Iu-PS, and to
the CS domain, which is called Iu-CS.
In both cases, ATM is used as transmission network solution.
Please note, that there are differences in the protocol stacks on the Iu-CS and Iu-PS interface.
Iub
This interface is used between the Node B and its controlling RNC.
Iur
This is an inter-RNS interface, connecting two neighbouring RNC.
It is used among others in soft handover situations, where a UEs active cells are under the control of
more than one RNC.
One RNC is responsible for the UE; it is called Serving RNC (SRNC). The remaining RNCs in a
connection are called Drift RNC (DRNC).
Uu
Uu is the acronym for the WCDMA radio interface.
On the interfaces Iu, Iur, and Iub, ATM is used for the transport of user data and higher layer signalling
information.

UTRANUTRAN

CN

UE

Uu

Radio Network Subsystem (RNS)

Iub

RNC

Iu-CS

circuit
MSC/VLR switched
(cs)
domain

Uu
Iur
UE

Iub

RNC

Radio Network Subsystem (RNS)

Iu-PS
SGSN

packet
switched
(ps)
domain

RNC Tasks and Functions

WCDMA radio resource management
Admission Control, Packet Scheduling, Load
Control, Power Control, Handover Control,
Resource Manager.
Telecom functionality
incl. Location & connection management
(Transport Manager), ciphering, Iu and Iub
channel management, ATM switching and
multiplexing
Maintenance
incl. Fault localisation and reconfiguration
Operation
incl. RNC and Node B parameter
modification

Node B Tasks and Functions in Rel

99
O&M Processing.
Interfacing with NMS
and RNC for alarm and
control (Operations
and Maintenance)
functions.

Radio Channel functions.

Transport to physical channel
mappings. Encoding/Decoding
Spreading/Despreading user
traffic and signalling.
Uu Interface
WCDMA

RNC
Iub Interface
ATM
Cellular Transmission management
Managing ATM switching and
multiplexing over the Iub interface.
Control of AAL2/AAL5 connections.
Control of the physical transmission
interfaces E1, PDH, SDH or microwave.

Air Interface management.

Controlling Uplink and
Downlink radio paths on the Uu
Air Interface. Baseband to RF
conversion. Antenna multicoupling.

Key WCDMA Facts

Two radio interface solutions were specified with UMTS Release 99:
FDD mode
(high chip rate) TDD mode
The used carrier frequency band is 5 MHz.
The radio interface is organised in 10 ms frames, which are divided into 15 timeslots.
72*10 ms frames represent one hyperframe, which was introduced for UMTS-GSM Handovers.

The information bearing stream is spread with the so-called spreading code.
The spreading code consists of 3.84 Mcps.
The spreading code is a composition of two codes, Scrambling codes and channelisation codes
Different types of handovers are supported: soft handover (FDD only) , softer handover (FDD only), and hard
handovers.
Hand handovers can be classified into intra-frequency, inter-frequency, and inter-RAT handovers.
The modulation is QPSK in UMTS Release 99.

Key WCDMA Facts

Scrambling Codes
The scrambling codes are derived from the Gold code family.
They represent pseudo noise sequences.
As a consequence, if there is multi-path propagation in the system, the individual multi-paths can be
detected due the scrambling codes.
There are 512 primary scrambling codes defined for the downlink transmission.
Uplink, several million scrambling codes are available.
A scrambling code repeats with every 10 ms frame.
Channelization Codes
The channelization code are used for channel separation within one multi-path.
The channelization codes are orthogonal codes.
They repeat with each information bit, which has to be transmitted. Data rates and channelization codes
are consequently related.
Uplink, user data and control data are code multiplexed on one physical channel.
Downlink, they are time multiplexed.

Key WCDMA Facts in Rel 99

Duplex Transmission Modes:
Frequency Division Duplex (FDD)
Time Division Duplex (TDD)
Multiple Access:
Code Division Multiple Access (CDMA)
Modulation
Quadrature Phase Shift Keying (QPSK)
16-QAM (HSDPA)
Bandwidth
5 MHz

Time Organisation:
10 ms per radio frame
15 time slots per frame
72 radio frames per hyperframe
2560 chips per timeslot

Spreading
Spreading codes =
channelisation codes scrambling codes
Chip rate: 3.84 Mchips
Channelisation codes = orthogonal codes,
length: depends on spreading factor
Scrambling codes = pseudo noise codes
(derived from Gold code family)
length: 38400 chips (10 ms)

Spreading Factors (FDD mode):

UL: 4, 8, 16, 32, 64, 128, 256
DL: 4, 8, 16, 32, 64, 128, 256, 512
The spreading factor can be changed every
TTI (10, 20, 40, or 80 ms).
Handover types: Soft & Softer HO (FDD only),
Hard Handover;

Access Stratum
Strata were introduced to group protocols related to one aspect of service. In this course, especially the Access
Stratum is of importance.
The Access Stratum (AS) comprises infrastructure and protocols between entities of the infrastructure specific
to the applied access technique. In UMTS it offers services related to the data transmission via the radio
interface. It also allows the management of the radio interface on behalf of other parts of the network. Two
access strata are defined in UMTS:
UTRAN MT
The protocols in use between UTRAN and the mobile phone specify in detail radio interface related
information. AS signalling is used to inform the UE about how to use the radio interface in the UL
and DL direction.
UTRAN CN
The CN requests the access network to make transmission resources available. The interaction
between UTRAN and the CN is hereby independent of the interaction between the UTRAN and the
UE. In other words, the UTRAN CN access stratum is independent of the used radio interface
technology.
In this course, we focus our interest mainly on the transmission of signalling information and related parameters
via the radio interface. Consequently, the access stratum between the UE and UTRAN will be discussed in detail.
But also Non Access Stratum (NAS) signalling will be outlined. NAS signalling is exchanged between the UE
and the serving network. In this course material, this signalling is regarded as part of the non-access stratum.

AS and NAS Signalling

CN Iu edge node

UE

NAS signalling and User data

i.e. MM, PMM & CC, SS, SMS, SM

UTRAN
RNC
Access Stratum Signalling
(Uu Stratum)
RRC

Access Stratum Signalling

(Iu Stratum)

RANAP

UMTS QoS Architecture

When a subscriber requests a network service, he expects to get and is willing to pay for a specific end-toend quality of service.
In a peer-to-peer communication, the QoS has to be provided between the two participating terminals. The
QoS of an end-to-end bearer service has to be described. Parameter such as minimum bit rate, guaranteed bit
rate, and end-to-end delay can be used.
An end-to-end bearer service may be made available by several operators. This is the situation displayed in the
figure on the right hand side. The UMTS provider offers the UMTS bearer service, a service established
between the UE and a CN edge node (GMSC, GGSN).
The UMTS bearer service and its QoS depends on the underlying bearer services:
The CN bearer service and the Radio Access Bearer (RAB) Service.
The signalling protocols RANAP between the CN Iu edge node (MSC/VLR, SGSN) and the RNC is used among
others to establish, maintain, modify and release the Iu Bearer Service, which is required to establish the RAB
between the CN Iu edge node and the S-RNC. Between the S-RNC and the UE, the signalling and control
protocol RRC is used to establish Radio Bearer (RB) Services, which is also required to establish a RAB Service.
The RRC is used peer-to-peer between the UE and the S-RNC. There are two intermediate devices, which also
have to be informed about the bearer management: The Node B and during a soft handover the D-RNC.
The management of the Iub resources to offer adequate QoS to higher layer bearer services is done with the
NBAP. This protocol is also used to inform the Node B about the transmission and reception of common and
dedicated information on the radio interface Uu. The RNSAP is used between neighbouring RNCs for features
such as inter-RNC soft handovers and S-RNC relocation.

UMTS QoS Architecture

TE

MT

UTRAN

CN Iu
edge node

CN
Gateway

TE

End-to-End Service
TE/MT Local
Bearer Service

UMTS Bearer Service = UMTS QoS

Radio Access
Bearer Service
Radio
Bearer Service

Iu
Bearer Service

UTRA FDD/TDD
Service

Physical
Bearer Service

CN
Bearer Service

Backbone
Bearer Service

(adopted from TS 23.107)

External
Bearer Service

QoS Management Functions in the

Control Plane
TE

MT

Translation

Adm/
Cap.
Control

UTRAN

Adm/
Cap.
Control

UMTS BS
Manager

CN Iu edge node

CN Gateway

Adm/
Subscr
Cap.
Control
Control

Adm/
TransCap.
lation
Control

UMTS BS
Manager

UMTS BS
Manager

ext. network

RAB
Manager

Local
BS
Manager

Radio
BS
Manager

Radio
BS
Manager

Iu BS
Manager

Iu BS
Manager

CN BS
Manager

CN BS
Manager

UTRA
ph. BS
Manager

UTRA
ph. BS
Manager

Iu NS
Manager

Iu NS
Manager

BB NS
Manager

BB NS
Manager

Ext. BS
Manager

(adopted from
TS 23.107)

UTRAN Specific Signalling and

Control Protocols
RNS
UE

Node B

RNC
3G-MSC/VLR

RRC

3G-SGSN

Iur: RNSAP

RNC

RNS

UMTS QoS Architecture

In UMTS, four QoS classes have been defined:
Conversational class
is the QoS class for delay sensitive real time services such as speech telephony.
Streaming class
is also regarded as real-time QoS class. It is also sensitive to delays; it carries traffic, which looks real time
to a human user. An application for streaming class QoS is audio streaming, where music files are
downloaded to the receiver. There may be an interruption in the transmission, which is not relevant for
the user of the application, as long as there are still enough data left in the buffer of the receiving
equipment for seamless application provision to gap the transmission time break.
Interactive class
is a non-real time QoS class, i.e. it is used for applications with limited delay sensitivity (so-called
interactive applications). But many applications in the internet still have timing constraints, such as http,
ftp, telnet, and smtp. A response to a request is expected within a specific period of time. This is the QoS
offered by the interactive class.
Background class
is a non-real time QoS class for background applications, which are not delay sensitive. Example
applications are email and file downloading.
A set of UMTS bearer attributes have been defined to specify the UMTS service. They are listed on the right
hand side. When a UMTS bearer is established, modified or released, aspects such as the UE capabilities,
subscription profiles and network specific QoS profiles have to be taken under consideration.

UMTS Bearer Attributes

Traffic class

Conversational
class

Streaming
class

Interactive
class

Background
class

Maximum bit rate

Delivery order
Maximum SDU size
SDU format
information
SDU error ratio
Residual bit
error ratio
Delivery of
erroneous SDUs
Transfer delay
Guaranteed bit rate
Traffic handling
priority
Allocation/Retention
priority
(adopted from TS 23.107 chap. 6.4.3.3)

Services and traffic class

(adopted from TS 23.107)

Different services and applications set different requirements for the connection over the radio access
network (RAN), i.e. radio access bearer (RAB)
Minimum bit rate
Delay
Error protection
These different quality requirements can be met by selection of traffic class
Conversational class
The most well known use of this scheme is telephony speech (e.g. GSM). But with Internet and
multimedia a number of new applications will require this scheme, for example voice over IP and video
conferencing tools. Real time conversation is always performed between peers (or groups) of live
(human) end-users. This is the only scheme where the required characteristics are strictly given by
human perception.
Streaming class
When the user is looking at (listening to) real time video (audio) the scheme of real time streams
applies. The real time data flow is always aiming at a live (human) destination. It is a one way transport.
This scheme is one of the newcomers in data communication, raising a number of new requirements in
both telecommunication and data communication systems. It is characterised by that the time relations
(variation) between information entities (i.e. samples, packets) within a flow shall be preserved,
although it does not have any requirements on low transfer delay.
Interactive class
When the end-user, that is either a machine or a human, is on line requesting data from remote
equipment (e.g. a server), this scheme applies. Examples of human interaction with the remote
equipment are: web browsing, data base retrieval, server access. Examples of machines interaction with
remote equipment are: polling for measurement records and automatic data base enquiries (telemachines).
Background class
When the end-user, that typically is a computer, sends and receives data-files in the background, this
scheme applies. Examples are background delivery of E-mails, SMS, download of databases and
reception of measurement records.

Services/apps and traffic class

Traffic class

Conversational
class

Streaming
class

Interactive
class

Background
class

Speech
Video call
Streaming video
Streaming audio
Web browsing
Email
Email (background)
VoIP
Gaming
Presence
Initially 3G networks do not support all traffic classes and services are implemented with
lower quality connections.

General Protocol Model for UTRAN

Interfaces
The general protocol model for UTRAN interfaces can be seen in the figure on the right hand side.
It is organised in horizontal and vertical planes.
There are two main vertical layers:
The control plane is used for signalling and control.
UTRAN specific signalling protocols had been developed, such as the RNSAP. This is one example
of an application protocol, as denoted in the figure.
Each signalling and control protocol requires a signalling bearer.
The signalling bearers in UMTS are based on standard bearer protocols (e.g. ATM).
The user plane describes the user data transport.
The data streams are transmitted via data bearers.
Within the transport network layers, there are vertical transport network user and control planes.
A transport network control plane is responsible for the transport of higher layer data.
The transmission resources for the control plane are made available by operation and maintenance.
The Transmission resources for the user data streams can be made available on demand. On some
interface, ALCAP is used.
It is a transport network control plane specific signalling protocol to establish, maintain, modify, and
release data bearers. It is for instance in use on the Iu-CS interface, but not on the Iu-PS interface. The
signalling bearers for ALCAP are always set up by operations and maintenance.

General Protocol Model for UTRAN

Interfaces

Radio
Network
Layer

Control Plane

User Plane

Application
Protocol

Data
Streams

Transport Transport Network

User Plane
Network
Layer

Transport Network
Control Plane

Transport Network
User Plane

ALCAP

Signalling
Bearer(s)

Signalling
Bearer(s)

Data
Bearer(s)

Physical Layer

(copied from TS 25.401 chap. 11.1.1)

General Protocol Model for UTRAN

Interfaces
The figure on the right hand side shows the Uu access stratum protocols as implemented in the UE.
The UE protocol stack can be divided into a control and a user plane.
The L3 protocol RRC is used to inform the UE about the use of the uplink and downlink radio resources.
The RRC protocols peer entities are the RNC and the Node B.
The receiving entity has to configure the L2 (MAC, PHY, PDCP, and BMC) protocol entities in accordance to the
received commands.
MAC: Medium Access Control
PHY: Physical layer
PDCP: Packet Data Conversion Protocol
BMC: Broadcast/multicast control
The protocol stacks for signalling and user data transfer can be seen with the two figures, which follow the next
one.

Radio Interface Protocol Architecture

(in UE)
Control Plane Signalling

control
control
control

User Plane Signalling

RRC Layer
RBs
control

PDCP

PDCP
PDCP
BMC

control

RLC Layer
RLC

RLC
RLC

RLC
RLC

RLC

RLC

RLC

LogCHs
MAC Layer
TrCHs
PHY Layer
(copied from TS 25.301 chap. 5.1)

PhyCHs

References
For this course module, following 3GPP specifications were used:

TR 21.902, Evolution of 3GPP system

TS 23.002, Network architecture
TS 23.101, General UMTS Architecture
TS 23.107, Quality of Service (QoS) concept and architecture
TS 25.301, Radio interface protocol architecture
TS 25.308, UTRA HSDPA; Overall description; Stage 2
TS 25.401, UTRAN overall description
TR 25.876, MIMO in UTRA
TS 25.308, HSDPA Overall Description
TS 25.309, FDD Enhanced Uplink (HSUPA) Overall Description
TS 36.300, E-UTRA and E-UTRAN Overall Description
TR 36.913, LTE-Advanced

TS Technical Specification
TR Technical Report
Remark:
Most of these Specifications are available in different versions, mainly depending on the 3GPP Release. HSDPA is
only available starting with Release 5; therefore, HSDPA is only contained in Version 5 or later specifications.
Release 99 is referred to as Version 3. Modifications within one release are possible, resulting in running
numbers.
Example: TS 25.401 V3.10.0 gives an overall description of UTRAN based on Release 99. 10.0 refers to 10 (by
3GPP) approved versions with minor corrections.