Академический Документы
Профессиональный Документы
Культура Документы
TM51103EN03GLA2
2010 Nokia Siemens Networks
1
Contents
1 UMTS Air interface technology 3
1.1 Duplex methods 4
1.2 UMTS Frequency 7
1.3 Access method 8
2 UMTS Air interface description 11
2.1 Principle 12
2.2 Data processing 13
2.3 Codes 21
2.4 Logical, transport and physical Channels 28
2.5 Air interface protocol stack 35
3 High Speed Downlink Packet Access HSDPA 51
3.1 HSDPA performance 52
3.2 HSDPA implementation : 53
3.3 HSDPA channels : 55
3.4 MAC Layer Split 57
3.5 Adaptive Modulation and Coding (AMC) Scheme : 58
3.6 Error Correction (HARQ) 59
3.7 Fast packet scheduling 61
3.8 Impact on the Iub Interface 63
3.9 Handset Capabilities 64
4 Exercises 65
5 Solution 67
UMTS Air Interface
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
2
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
3
1 UMTS Air interface technology
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
4
1.1 Duplex methods
The duplex define the way how two communicating entities will communicate with
each others.
We define here three ways:
Simplex: This is one way communication method used for broadcasting (TV,
Radio)
Half-duplex: This is a two ways communication method; the two communicating
entities cannot transmit and receive simultaneously.
Full-duplex: This method is the same as half duplex except that the two entities
can communicate simultaneously.
We define two means to achieve full or half duplex method:
FDD: Frequency Division Duplex :
The frequency band is split into two sub-band one for the uplink and the other for the
downlink. Then the receiver and the transmitter use two carriers at the same time.
Advantages: Using this method we can avoid collision between uplink and
downlink.
Drawbacks: Frequency resources are wasted
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
5
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uplink
Uplink
Downlink
Downlink
Fig 1 Frequency division duplex
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
6
TDD: Time Division Duplex :
The two communicating entities use the same frequency band, but it doesnt
communicate simultaneously. It uses two different time period, one period for the
uplink and the other one for the downlink.
Advantages: The frequency resources are not wasted.
Drawbacks: Collision may occur during communication.
TM51103EN03GLA01
1 Nokia Siemens Networks
Time
Frequency
Uplink
Uplink
Downlink
Downlink
Fig 2 Time division duplex
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
7
1.2 UMTS Frequency
The IMT-2000 has allocated the band from 806 MHz - 960 MHz, 1710 MHz - 2025
MHz, 2110 MHz 2200 MHz and finally 2500Mhz 2690 MHz for a worldwide
mobile communication implementation.
The frequency band which is used for UMTS use is summarized in the following
graph:
TM51103EN03GLA01
1 Nokia Siemens Networks
Fig 3 IMT-2000 frequency allocation for different mobile system
1920-1980 and 2110-2170 MHz Frequency Division Duplex (FDD, W-CDMA) Paired
uplink and downlink, channel spacing is 5 MHz. An Operator needs 3 - 4 channels
(2x15 MHz or 2x20 MHz) to be able to build a high-speed, high-capacity network.
1900-1920 and 2010-2025 MHz Time Division Duplex (TDD, TD/CDMA) Unpaired,
channel spacing is 5 MHz. Tx and Rx are not separated in frequency.
1980-2010 and 2170-2200 MHz Satellite uplink and downlink.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
8
1.3 Access method
The goal of a network operator is to achieve a higher capacity with fewer resources.
In order to do this different access methods are used following is defining these
methods:
1.3.1 FDMA: Frequency division multiple access
The used frequency band is divided into different carriers as shown below. The same
number of carrier is used for both uplink and downlink. Each carrier is indexed with
UARFCN (UTRA absolute radio frequency carrier number).
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
UAR
FC
Frequency
Uplink
Downlink
Fig 4 Frequency division multiple access technique
The advantage of this technique is that the bandwidth is used more efficiently. It
means that one operator can reuse its set of frequency according to a certain pattern
called cluster.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
9
1.3.2 TDMA: Time division multiple access
This is a time domain multiplexing technique. The principle is simple one carrier is
divided into different timer period called timeslot.
TM51103EN03GLA01
1 Nokia Siemens Networks
Time
F
R
E
Q
U
E
N
C
Y
Timeslot
Fig 5 TDMA Time division multiple access
In order to increase the capacity of the network the two previously discussed
techniques are used together.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
10
1.3.3 CDMA: Code division multiple access
This is a technique which is using code division in the air interface. Lets assume that
there is a crowd of people speaking together, so if everyone will speak loudly nobody
can listen to his talker. The principle introduced by CDMA is as simple as that: each
one will speak with low level and with his own language so everybody can have a
coherent discussion without disturbing his neighbor. So in CDMA system the
subscribers share the same frequency and the same time but they got different
codes.
Fig 6 CDMA Concept expressed in terms of power, frequency and time
The capacity of the cell is not anymore function of number of timeslots in the air
interface but its expressed in function of power allowed within one cell, or to be more
specific this capacity is expressed with allowed signal to interference ratio within one
cell.
Then when more subscribers acess the cell then they will add more interference level
to the cell till the interference level reach a planed level or threshold.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
11
2 UMTS Air interface description
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
12
2.1 Principle
The air interface is the interface located between the UE and the base station and in
the standard it is referred as Uu interface.
The transmission in the air interface is based on CDMA technology and its called
W-CDMA (Wideband CDMA) because its using 3 times the bandwidth which is used
by the CDMA and then for the WCDMA we allocate 3.84 MHz effective band.
Adding the guard band the total bandwidth will reach 5 MHz.
TM51103EN03GLA01
1 Nokia Siemens Networks
Fig 7 UMTS bandwidth
Different variants bandwidths are specified by the standard 5 MHz, 10 MHz and 20
MHz, the mostly used by operators is 5 Mhz.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
13
2.2 Data processing
Before sending the data over the Uu interface data need to be processed in order to
comply with the air interface requirement in term of bandwidth and QoS. This
processing in the following steps:
Fig 8 Data process
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
14
2.2.1 Channel coding
Channel coding refers to a technique used to protect data against losses in the air
interface. The technique used here is adding redundancy to the signal giving it more
chance to be transmitted correctly over the Uu interface.
For the channel coding in UTRA two options are supported for FDD and three options
are supported for TDD:
Convolutional coding.
Turbo coding.
No coding (only TDD).
Channel coding selection is indicated by higher layers. In order to randomize
transmission errors, bit interleaving is performed further.
2.2.2 Rate Matching
After channel coding data needs to be put into radio frames and sometime the
amount of data is less or exceed the size of these radio frames. So in order make a
correct framing bits are added or by puncturing in a controlled way and this process
is called rate matching. The following graph shows which are allowed data rate to be
matched:
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
15
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TM51103EN03GLA01
Fig 9 UMTS Rate matching
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
16
2.2.3 Radio framing, and Spreading
After rate matching the data from previous block comes with a tight bandwidth and a
higher output power. So in order to reduce the power of the signal we multiply it by a
code, channelization code, so that the signal will be spread all over the total
bandwidth reducing then the power under the noise level.
TM51103EN03GLA01
1 Nokia Siemens Networks
Fig 10 Spreading
By doing that the receiver transmits the signal with a lower level allowing then less
interference in the air interface.
The length of the code that the signal will be multiplied with is expressed as follow:
The chip is the smallest logical unit in a code it means a chip is a bit in the code. The
code frequency is higher than the signal frequency so that we obtain spreading of the
signal over the bandwidth. The chip rate used is 3.84 million chips per second
(Mcps/s) and it is fixed.
The characteristics of the spreading codes will be discussed later.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
17
2.2.4 Modulation
There are several considerations that were taken into account when making the
choice for the overall format for the UMTS WCDMA modulation formats. Some of the
considerations were:
It is necessary to ensure that the data is carried efficiently over the available
spectrum, and therefore maximum use is made of the available spectrum, and
hence the capacity of the system is maximized.
The modulation format should be chosen to avoid the audio interference caused to
many nearby electronics equipment resulting from the pulsed transmission format
used on many 2G systems such as GSM
As the uplink and downlink have different requirements, the exact format for the
modulation format used on either direction is slightly different.
UMTS modulation schemes for both uplink and downlink, although somewhat
different are both based around QPSK formats. This provides many advantages
over other schemes that could be used in terms of spectral efficiency and other
requirements.
Fig 11 UMTS Modulation
The OQPSK is the Offset QPSK the difference with QPSK is that there is no jump
is permitted over the intermediate states.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
18
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
19
2.2.5 Multipath propagation
Due to the environment of serving area the microwave can be reflected by different
obstacles before it reach the BTS or the MS and this is the multipath propagation. So
at the receiver side there will be a combination of different signals. In order to deal
with such a propagation context the RAKE receiver is used.
TM51103EN03GLA01
1 Nokia Siemens Networks
Fig 12 RAKE receiver block diagram
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
20
In a W-CDMA receiver the following steps take place (excluding the error correction
coding):
1. Descrambling: Received signals are multiplied by the scrambling code and
delayed versions of the scrambling code. The delays are determined by a path
searcher prior to descrambling. Each delay corresponds to a separate multipath
that will eventually be combined by the Rake receiver.
2. Despreading: The descrambled data of each path are dispread by simply
multiplying the descrambled data by the spreading code.
3. Integration and dump: The dispread data is then integrated over one symbol
period, giving one complex sample output per quadrature phase-shift keying
(QPSK) symbol. This process is carried out for all the paths that will be combined
by the RAKE receiver.
4. The same symbols obtained via different paths are then combined together using
the corresponding channel information using a combining scheme like maximum
ratio combing (MRC).
5. The combined outputs are then sent to a simple decision device to decide on the
transmitted bits.
6. The objective of the channel estimation block is to estimate the channel phase
and amplitude [denoted in Figure 1 as g(t, i)] for each of the identified paths.
Once this information is known, it can be used for combining each path of the
received signal.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
21
2.3 Codes
Previously we talked about spreading codes, spreading is done using a
channelization codes and scrambling codes:
Fig 13 Spreading using channelization and scrambling codes
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
22
2.3.1 Channelization code
Channelization codes are used
UL: to separate physical data and control data from same terminal
DL: to separate connection to different terminals in a same cell.
For a good separation these code are orthogonal and then we use OVSF codes
(orthogonal variable spreading factor codes) these codes are also called Walsh
codes. It uses a different spreading factor according to bandwidth requirement
increasing then the data rate of the signal.
TM51103EN03GLA01
1 Nokia Siemens Networks
Fig 14 Code tree
One important limitation of OVSF-WCDMA is that the system must maintain the
orthogonality among the assigned codes. The maintenance of the orthogonality
among the assigned OVSF codes causes the code blocking problem due to their tree
structure. When users are using a higher data rate then they will use a shorter code
this will lead to a blocking to the remaining tree branch and then limiting the access to
the other users.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
23
2.3.2 Scrambling codes
Scrambling codes has a different use from the channelization code, they are used to
distinguish in the UL between different users and downlink between different Node B.
One scrambling code then is allocated by cell or by user. The scrambling codes have
a lower orthogonality than the channelization codes.
These codes are organized into 512 code sets. We define then 512 primary
scrambling codes and in a lower hierarchical level we define from 1 to 15 secondary
scrambling codes achieving then a total number of 8096 codes. The scrambling code
is identified by first identifying its code set to significantly reduce the degree of code
uncertainly.
Fig 15 Scrambling codes set
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
24
2.3.3 Code management
Code management is devoted to managing the downlink OVSF (Orthogonal Variable
Spreading Factor) code tree used to allocate physical channel orthogonality among
different users. Clearly, the advantage of the OVSF codes used in the UTRAN
downlink is perfect orthogonality. However, the drawback is the limited number of
available codes. Therefore, it is important to be able to allocate/reallocate the
channelization codes in the downlink with an efficient method, in order to prevent
code blocking. Code blocking indicates the situation where a new call could be
accepted on the basis of interference analysis and also on the basis of the spare
capacity of the code tree but, due to an inefficient code assignment, this spare
capacity is not available for the new call that must, therefore, be blocked. This
situation is depicted in Figure 4.24, where two transmissions with SF 4 and two
transmissions with SF 8 are assumed to have been assigned the corresponding
code sequences Cch,4,2, Cch,4,3, Cch,8,1 and Cch,8,3, respectively, which prevent
the use of the codes marked with a cross in Figure 4.24. It is worth noting that, with
such OVSF code tree occupancy, the arrival of a new call requesting for SF 4
would experience code blocking, since no code at that layer is available. On the
contrary, if the code allocation shown in below figure was used, it would allow the
support of the two SF 4 users, the two SF 8 users and still would provide room
to support a new SF 4 request with code Cch,4,1.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
25
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig 16 Example of code blocking
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
26
Fig 17 :Example of code allocation preventing code blocking
In general terms, a code allocation strategy would aim at minimizing code tree
fragmentation, preserving the maximum number of high rate codes and eliminating
code blocking. Nevertheless, since the purpose of the code allocation/reallocation
strategies is to prevent code blocking, this may require code handover, that is, a call
using a given code is forced to use a different code belonging to the same layer.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
27
2.3.4 Multiuser detection in WCDMA systems
Before sending user data in the air interface it must be multiplied by a scrambling
code C1. While sending over the air interface different signals of different users are
combined. In order to extract the user data from the other signals we must multiply it
by the same code again.
1 1 1 1 0 0 0 0 1 1 1 1 1 1 1 1 User data
1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1
X
Code
0 1 1 0 1 0 0 1 0 1 1 0 0 1 1 0
1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1
Scrambled Signal
Code
X
Fig 18 Scrambling process
The characteristic of this scrambling code is that they are not orthogonal but they
have very good orthogonality propriety and they are pseudo random.
Fig. 1
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
28
2.4 Logical, transport and physical Channels
UTRA FDD radio interface has logical channels, which are mapped to transport
channels, which are again mapped to physical channels. Logical to Transport
channel conversion happens in Medium Access Control (MAC) layer, which is a
lower sub-layer in Data Link Layer (Layer 2).
TM51103EN03GLA01
1 Nokia Siemens Networks
Radio resources control
Radio resources control
Medium Access Control
Medium Access Control
Physical Layer
Physical Layer
Logical channel
Transport channel
Physical channel
Control
and
measur
ement
Fig 19 Protocol stack
Different channels transport channels can be mapped into one physical channel and
different logical channel can be mapped to a transport channel. This channel
organization allows signaling information to be transfer to the concerned and
appropriate protocol level in a network element.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
29
TM51103EN03GLA01
1 Nokia Siemens Networks
Fig 20 Channels
Fig 21 Channels 2
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
30
2.4.1 Physical channels
A physical channel is basically defined by a frequency and a spreading code. The
physical channel uses a cosine or sine waveform as a signal carrier. We can
distinguish between two kinds of physical channels:
o Dedicated physical channel.
o Common physical channel.
A dedicated physical channel is allocated only for one connection but common
channels are used simultaneously or alternatively by different connections.
The physical layers map under control of the MAC the transport channels to the
physical channel according to their physical requirement.
o Dedicates Physical Data Channel DPDCH: Used in uplink direction to
transmit signaling and user data from higher layer.
o Dedicated physical control channel DPCCH: This channel is used to
control the data transmission over the air interface. The information
included in this channel are power control commands, pilot bits
o Dedicated physical channel DPCH: The DPDCH and the DPCCH are
implemented on DPCH.
o Physical Random Access Channel PRACH: This physical channel is
used during the initial access procedure or call setup. The information
contained on this channel is RACH.
o Physical common packet control channel PCPCH: Packet data of the
CPCH is sent via PCPCH through the use of CSMA/CD technique.
o Common Pilot Channel CPICH: CPICH is an important channel used for
cell phase and time reference as well as channel estimation. This channel
will help the UE to identify the primary scrambling code by sending a bit
pattern at a fixed data rate at 30 kb/s and with a known 256 spreading
factor. The same channel code is always used by the CPICH.
o Common control physical channel CCPCH: This is a downlink channel
which is used to carry broadcast information and synchronization to the
mobile station. We have two CCPCH:
P-CCPCH: Primary common control channel which used to broadcast BCH cell
info for different users within a cell serving area.
S-CCPCH: Secondary Common control physical channel which is used to carry
the FACH Forward Access channel and PCH paging channel.
Synchronization channel SCH: Physical channel is used to for cell search and
frame synchronization. We can distinguish two SCH:
Primary SCH: The 10ms radio frames of the SCH are divided into 15 slots, each
of length 2560chips. The Primary SCH consists of a modulated code PSC
(Primary synchronization code) of length 256chips, and is transmitted once every
slot.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
31
TM51103EN03GLA01
1 Nokia Siemens Networks
Fig 22 WCDMA Frame
Secondary SCH: consists of repeatedly transmitting a length 15 sequence of
modulated codes of length 256 chips, the Secondary Synchronization Codes
(SSC), transmitted in parallel with the Primary SCH. The SSC is denoted csi,k ,
where i = 0, 1, , 63 is the number of the scrambling code group, and k = 0, 1, ,
14 is the slot number. Each SSC is chosen from a set of 16 different codes of
length 256. This sequence on the Secondary SCH indicates which of the code
groups the cell's downlink scrambling code belongs to.
o Physical downlink shared channel: This channel is used to carry data
over DSCH and different connections can share this channel. A DPCH is
always allocated to the PDSCH.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
32
2.4.2 Transport channels
The output from, and input to, MAC is in the form of transport channels, which can be
seen as service between MAC and Layer 1 (physical layer). Generally, transport
channels map onto specific physical channels and have specific characteristics in
terms of direction, data rate (including variation) and power control requirements. The
configuration of a transport channel is related dynamically to QoS requirements.
Random Access Channel RACH: This channel is mapped to PRACH and it is
used to send a small amount of data for a connection setup or initial access in
uplink direction. When it use the RACH the mobile send a first preamble and then
wait for an indication from the network that a first preamble was received and then
it send a second preamble.
Broadcast channel BCH: This downlink channel is used to transmit cell specific
information to the mobile. This information is contained on the BCCH which is itself
mapped to BCH.
Forward Access channel FACH: This channel is used to transfer a small amount
of user data or signaling over the air interface and also to grant access to the
mobile during initial access procedure after receiving second preamble of the
RACH.
Dedicated channel DCH: This channel to carry user data traffic different logical
channel can be mapped over this channel (DCCH or DTCH).
Data Shared Channel DSCH: In UMTS, the Downlink Shared Channel (DSCH) is
used to transmit data packets from the Node B to the User Equipment (UE). Each
DSCH is associated with a Dedicated Channel (DCH) which is used for power
control, channel estimation and transmission of associated control information for
the DSCH.
Common pilot channel CPICH: This channel is used in UMTS to enable channel
estimation. The CPICH uses a pre defined bit sequence. It has a fixed rate of
30Kbps with a SF (Spreading Factor) of 256. This allows the UE (User Equipment)
to equalize the channel in order to achieve a phase reference with the SCH
(Synchronization Channel) and also allows estimations in terms of power control.
The same channel code is always employed on the Primary CPICH.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
33
2.4.3 Logical channels
Logical channel are used for different purpose depending on the information carried
within these channels. This information could be paging information or BCCH or other
signaling information.
Broadcast Control Channel BCCH: This logical channel carry specific
information and parameter about the cell.
Paging Control Channel (PCCH): A downlink channel that transfers paging
information.
Dedicated Control Channel (DCCH): A point-to-point bidirectional channel that
transmits dedicated control information between a UE and the RNC. This channel
is established during the RRC connection establishment procedure.
Common Control Channel (CCCH): A bidirectional channel for transmitting
control information between the network and UEs. This logical channel is always
mapped onto RACH/FACH transport channels. A long UTRAN UE identity is
required (U-RNTI, which includes SRNC address), so that the uplink messages
can be routed to the correct serving RNC even if the RNC receiving the message
is not the serving RNC of this UE.
The Traffic Channels are:
Dedicated Traffic Channel (DTCH): A Dedicated Traffic Channel (DTCH) is a
point-to point channel, dedicated to one UE, for the transfer of user information. A
DTCH can exist in both uplink and downlink.
Common Traffic Channel (CTCH): A point-to-multipoint downlink channel for
transfer of dedicated user information for all, or a group of specified, UEs.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
34
TM51103EN03GLA01
1 Nokia Siemens Networks
Fig 23 Channels mapping
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
35
2.5 Air interface protocol stack
The protocol stack in the air interface is 3 level layered as shown below:
TM51103EN03GLA01
1 Nokia Siemens Networks
Signaling
Signaling
RLC
RLC
Logical Channels
Logical Channels
MAC
MAC
Transport Channels
Transport Channels
Physical layer
Physical layer
Control and
measurements
BMC
BMC
PDCP
PDCP
Control plane
User plane Radio Bearer
Control plane Radio Bearer
Physical Channels
Physical Channels
1
2
3
User plane
RRC
RRC
Fig 24 Air interface protocol stack
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
36
The physical layer offers services to the MAC layer via transport channels that were
characterized by how and with what characteristics data is transferred. The MAC
layer, in turn, offers services to the RLC layer by means of logical channels. The
logical channels are characterized by what type of data is transmitted. The RLC layer
offers services to higher layers via service access points (SAPs), which describe how
the RLC layer handles the data packets and if, for example, the automatic repeat
request (ARQ) function is used. On the control plane, the RLC services are used by
the RRC layer for signaling transport. On the user plane, the RLC services are used
either by the service-specific protocol layers PDCP or BMC or by other higher-layer
u-plane functions (e.g. speech codec). The RLC services are called Signaling Radio
Bearers in the control plane and Radio Bearers in the user plane for services not
using the PDCP or BMC protocols. The RLC protocol can operate in three modes
transparent, unacknowledged and acknowledged mode. The Packet Data
Convergence Protocol (PDCP) exists only for the PS domain services. Its main
function is header compression. Services offered by PDCP are called Radio Bearers.
The Broadcast Multicast Control protocol (BMC) is used to convey over the radio
interface messages originating from the Cell Broadcast Centre. In Release 99 of the
3GPP specifications, the only specified broadcasting service is the SMS Cell
Broadcast service, which is derived from GSM. The service offered by BMC protocol
is also called a Radio Bearer.
The RRC layer offers services to higher layers (to the Non-Access Stratum) via
service access points, which are used by the higher layer protocols in the UE side
and by the Iu RANAP protocol in the UTRAN side. All higher layer signaling (mobility
management, session management, and so on) is encapsulated into RRC messages
for transmission over the radio interface.
The control interfaces between the RRC and all the lower layer protocols are used by
the RRC layer to configure characteristics of the lower layer protocol entities,
including parameters for the physical, transport and logical channels. The same
control interfaces are used by the RRC layer, for example to command the lower
layers to perform certain types of measurement and by the lower layers to report
measurement results and errors to the RRC.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
37
2.5.1 Medium Access Control MAC
In the Medium Access Control (MAC) layer the logical channels are mapped to the
transport channels. The MAC layer is also responsible for selecting an appropriate
transport format for each transport channel depending on the instantaneous source
rate of the logical channels. The transport format is selected with respect to the
transport format combination set which is defined by the admission control for each
connection.
The functions of the MAC layer include:
Mapping between logical channels and transport channels.
Selection of appropriate Transport Format (from the Transport Format
Combination Set) for each Transport Channel, depending on the instantaneous
source rate.
Priority handling between data flows of one UE. This is achieved by selecting high
bit rate and low bit rate transport formats for different data flows.
Priority handling between UEs by means of dynamic scheduling. A dynamic
scheduling function may be applied for common and shared downlink transport
channels FACH and DSCH.
Identification of UEs on common transport channels. When a common transport
channel (RACH, FACH or CPCH) carries data from dedicated-type logical
channels
(DCCH, DTCH), the identification of the UE (Cell Radio Network Temporary
Identity
(C-RNTI) or UTRAN Radio Network Temporary Identity (U-RNTI)) is included in
the MAC header.
Multiplexing/demultiplexing of higher layer PDUs into/from transport blocks
delivered to/from the physical layer on common transport channels. MAC handles
service multiplexing for common transport channels (RACH/FACH/CPCH). This is
necessary, since it cannot be done in the physical layer.
Multiplexing/ demultiplexing of higher layer PDUs into/from transport block sets
delivered to/from the physical layer on dedicated transport channels. MAC allows
service multiplexing also for dedicated transport channels. While the physical layer
multiplexing makes it possible to multiplex any type of service, including services
with different quality of service parameters, MAC multiplexing is possible only for
services with the same QoS parameters.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
38
Traffic volume monitoring. MAC receives RLC PDUs together with status
information on the amount of data in the RLC transmission buffer. MAC compares
the amount of data corresponding to a transport channel with the thresholds set by
RRC. If the amount of data is too high or too low, MAC sends a measurement
report on traffic volume status to RRC. The RRC can also request MAC to send
these measurements periodically. The RRC uses these reports for triggering
reconfiguration of Radio Bearers and/or Transport Channels.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
39
2.5.2 The Radio Link Control Protocol
The radio link control protocol provides segmentation and retransmission services for
both user and control data. Each RLC instance is configured by RRC to operate in
one of three modes: transparent mode (Tr), unacknowledged mode (UM) or
acknowledged mode (AM). The service the RLC layer provides in the control plane is
called Signaling Radio Bearer (SRB). In the user plane, the service provided by the
RLC layer is called a Radio Bearer (RB) only if the PDCP and BMC protocols are not
used by that service; otherwise the RB service is provided by the PDCP or BMC.
Each mode provides a different set of services defining the use of that mode by the
higher layers. Transfer of user data is a service which is common to all three modes.
Transparent mode is defined for quick and dirty data transfer across the radio
interface, and is the only one of the three modes which does not involve the addition
of any header information onto the data unit. Erroneous data units are discarded or
marked as erroneous.
Transparent mode is the mode normally used by both the PNFE and BCFE entities
within RRC, for paging/notification and cell broadcast messaging.
In Unacknowledged mode, as in transparent mode, no retransmission protocol is
used, and so data delivery is not guaranteed. Received erroneous data can be either
marked or discarded, depending on configuration.
For both Transparent mode data transfer & unacknowledged mode data transfer,
RLC provides a function for the segmentation of large data units into smaller ones
(and re-assembly at the receive end). The segment lengths are defined when the
channel is established. In unacknowledged mode, segment lengths are given by a
length indicator which is within the header added to the data unit.
Unacknowledged mode additionally provides a service whereby small packet data
units can be concatenated together (again indicated within a header field), a
ciphering service, and a sequence number check which allows the receiver to check
whether or not data has been lost.
The functions of the RLC layer are:
Segmentation and reassembly. This function performs segmentation/reassembly
of variable-length higher layer PDUs into/from smaller RLC Payload Units (PUs).
One RLC PDU carries one PU. The RLC PDU size is set according to the smallest
possible bit rate for the service using the RLC entity. Thus, for variable rate
services, several RLC PDUs need to be transmitted during one transmission time
interval when any bit rate higher than the lowest one is used.
Concatenation. If the contents of an RLC SDU do not fill an integral number of
RLC PUs, the first segment of the next RLC SDU may be put into the RLC PU in
concatenation with the last segment of the previous RLC SDU.
Padding. When concatenation is not applicable and the remaining data to be
transmitted does not fill an entire RLC PDU of given size, the remainder of the
data field is filled with padding bits.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
40
Transfer of user data. RLC supports acknowledged, unacknowledged and
transparent data transfer. Transfer of user data is controlled by QoS setting.
Error correction. This function provides error correction by retransmission in the
acknowledged data transfer mode.
In-sequence delivery of higher layer PDUs. This function preserves the order of
higher layer PDUs that were submitted for transfer by RLC using the
acknowledged data transfer service. If this function is not used, out-of-sequence
delivery is provided.
Duplicate detection. This function detects duplicated received RLC PDUs and
ensures that the resultant higher layer PDU is delivered only once to the upper
layer.
Flow control. This function allows an RLC receiver to control the rate at which the
peer RLC transmitting entity may send information.
Sequence number check (Unacknowledged data transfer mode). This function
guarantees the integrity of reassembled PDUs and provides a means of detecting
corrupted RLC SDUs through checking the sequence number in RLC PDUs when
they are reassembled into an RLC SDU. A corrupted RLC SDU is discarded.
Protocol error detection and recovery. This function detects and recovers from
errors in the operation of the RLC protocol.
Ciphering is performed in the RLC layer for acknowledged and unacknowledged
RLC modes. The same ciphering algorithm is used as for MAC layer ciphering, the
only difference being the time-varying input parameter (COUNT-C) for the
algorithm, which for RLC is incremented together with the RLC PDU numbers. For
retransmission, the same ciphering COUNT-C is used as for the original
transmission (resulting in the same ciphering mask); this would not be so if
ciphering were on the MAC layer. An identical ciphering mask for retransmissions
is essential from Release 5 onwards when the HSDPA feature with physical layer
retransmission combining is used. The ciphering details are described in 3GPP
specification TS 33.102 [4].
Suspend/resume function for data transfer. Suspension is needed during the
security mode control procedure so that the same ciphering keys are always used
by the peer entities. Suspensions and resumptions are local operations
commanded by RRC via the control interface.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
41
2.5.3 The Packet Data Convergence Protocol PDCP
The Packet Data Convergence Protocol (PDCP) [6] exists only in the user plane and
only for services from the PS domain. The PDCP contains compression methods,
which are needed to get better spectral efficiency for services requiring IP packets to
be transmitted over the radio. For 3GPP Release 99 standards, a header
compression method is defined, for which several header compression algorithms
can be used. As an example of why header compression is valuable, the size of the
combined RTP/UDP/IP headers is at least 40 bytes for IPv4 and at least 60 bytes for
IPv6, while the payload, for example for IP voice service, can be about 20 bytes or
less.
The main PDCP functions are:
Compression of redundant protocol control information (e.g. TCP/IP and
TP/UDP/IP headers) at the transmitting entity, and decompression at the receiving
entity. The header compression method is specific to the particular network layer,
transport layer or upper layer protocol combinations, for example TCP/IP and
RTP/UDP/IP. The only compression method that is mentioned in the PDCP
Release 99 specification is RFC2507.
Transfer of user data. This means that the PDCP receives a PDCP SDU from the
non access stratum and forwards it to the appropriate RLC entity and vice versa.
Support for lossless SRNS relocation. In practice this means that those PDCP
entities which are configured to support lossless SRNS relocation have PDU
sequence numbers, which together with unconfirmed PDCP packets are forwarded
to the new SRNC during relocation. Only applicable when PDCP is using
acknowledged mode RLC with in sequence delivery.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
42
2.5.4 The Broadcast /Multicast Control Protocol BMC
The Broadcast/Multicast Control (BMC) protocol exists also only in the user plane.
This protocol is designed to adapt broadcast and multicast services, originating from
the Broadcast domain, on the radio interface. In Release 99 of the standard, the only
service using this protocol is the SMS Cell Broadcast service. This service is directly
taken from GSM. It uses UM RLC using the CTCH logical channel which is mapped
into the FACH transport channel. Each SMS CB message is targeted to a
geographical area, and RNC maps this area into cells.
The main functions of the BMC protocol are:
Storage of Cell Broadcast messages. The BMC in RNC stores the Cell Broadcast
messages received over the CBCRNC interface for scheduled transmission.
Traffic volume monitoring and radio resource request for CBS. On the UTRAN
side, the BMC calculates the required transmission rate for the Cell Broadcast
Service based on the messages received over the CBCRNC interface, and
requests appropriate CTCH/ FACH resources from RRC.
Scheduling of BMC messages. The BMC receives scheduling information together
with each Cell Broadcast message over the CBCRNC interface. Based on this
scheduling information, on the UTRAN side the BMC generates schedule
messages and schedules BMC message sequences accordingly. On the UE side,
the BMC evaluates the schedule messages and indicates scheduling parameters
to RRC, which are used by RRC to configure the lower layers for CBS
discontinuous reception.
Transmission of BMC messages to UE. This function transmits the BMC
messages (Scheduling and Cell Broadcast messages) according to the schedule.
Delivery of Cell Broadcast messages to the upper layer. This UE function delivers
the received non-corrupted Cell Broadcast messages to the upper layer.
When sending SMS CB messages to a cell for the first time, appropriate capacity
has to be allocated in the cell. The CTCH has to be configured and the transport
channel used has to be indicated to all UEs via (RRC) system information
broadcast on the BCH. The capacity allocated for SMS CB is cell-specific and may
vary over time to allow efficient use of the radio resources.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
43
2.5.5 The Radio Resource Control Protocol RRC
The major part of the control signaling between UE and UTRAN is Radio Resource
Control messages. RRC messages carry all parameters required to set up, modify
and release Layer 2 and Layer 1 protocol entities. RRC messages carry in their
payload also all higher layer signaling (MM, CM, SM, etc.). The mobility of user
equipment in the connected mode is controlled by RRC signaling (measurements,
handovers, cell updates, etc.).
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
44
2.5.6 Radio Access Bearer
A bearer is a data stream that spans some part of the system and has a specific
quality of service (QoS). Figure below shows the most important bearers in UMTS.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
45
TM51103EN03GLA01
1 Nokia Siemens Networks
Fig 25 Bearers used in UMTS. (Adapted from 3GPP TS 23.107.)
When the mobile and the network agree to set up a data stream, the system first
implements it using a UMTS bearer. This carries information such as voice or packet
data between the mobile termination and the far end of the core network (MSC,
GMSC or GGSN). If the MT and TE are implemented as two different devices, then
another bearer transports information between them. However, this bearer lies
outside the scope of UMTS, so we will not consider it further. The same applies to the
bearer that lies beyond the far end of the core network.
The UMTS bearer is associated with a number of QoS parameters. These describe
the service that the user expects to receive, using parameters such as the required
data rate, error rate and delay.
The system cannot supply this quality of service right away, because the UMTS
bearer spans different interfaces that use different transport protocols. It therefore
breaks the UMTS bearer down into bearers that have a smaller scope. A CN bearer
handles the path over the core network, while a radio access bearer (RAB) handles
the path between the mobile and its first point of contact there. In turn, the radio
access bearer is broken down into an Iu bearer between the core network and the
SRNC, and a radio bearer between the SRNC and the mobile. Each bearer is then
implemented using the transport protocols that are appropriate for the corresponding
interface, which provide the user with the quality of service expected. On the air
interface, for example, the radio bearer is implemented using the RLC, MAC and
physical layer protocols.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
46
Five special radio bearers carry signaling messages between the mobile and its
serving RNC. They are known as signaling radio bearers (SRBs), and they are:
RB0 for all CCCH messages (RLC unacknowledged mode and RLC transparent
mode)
RB1 for DCCH signaling using RLC unacknowledged mode
RB2 for DCCH signaling using RLC acknowledged mode (except those carrying
NAS signaling)
RB3 for DCCH signaling using RLC unacknowledged mode and carrying NAS
signaling. (Optionally RB4 also)
RB5 RB31 for DCCH signaling using RLC transparent mode.
Each of them is implemented in a particular way that is appropriate for a particular
type of message. RB 0 is used to set up signaling communications between the
mobile and the network; the other signaling radio bearers handle all subsequent
communications.
RBs 1 and 2 carry RRC messages between the mobile and its serving RNC, the
main difference between them being in the configuration of the RLC protocol. RBs 3
and 4 are used to forward non-access stratum messages that begin or end in the
core network. RB 4 is optional, but if it is implemented, then RB 3 is used for high
priority messages, and RB 4 is used for low priority ones.
UMTS Air Interface
TM51103EN03GLA2
2010 Nokia Siemens Networks
47
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TM51103EN03GLA01
1 Nokia Siemens Networks
RRC
RRC
RLC
RLC
MAC
MAC
Physical layer
Physical layer
Control
and
measure
ments
BMC
BMC
PDCP
PDCP
Control plane signaling radio bearer User plane Radio bearer
RB0 RB1 RB2 RB3 RB4 RB5 RB31
1
2
3
Mapped to TRM SAP/UM SAP/AM SAP