Sie sind auf Seite 1von 98

The Physical layer Rel.

99

Course Content
Warming Up
The Physical Layer Rel. 99
The Physical Layer HSDPA, HSUPA & HSPA+
RRC Modes, System Information, Paging & Update Procedures
Cell Selection & Reselection
RRC Connection Establishment
WCDMA Measurements in the UE
Mobility Management & Connection Management
UTRAN Control Protocol Overview (without RRC)

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

The Physical layer Rel. 99

Module Objectives

At the end of the module you will be able to:


Describe the WCDMA channel structure
Explain transport channel format
List different code types
Name the main differences in UL and DL data transmission organisation
Describe the UE cell synchronisation
Outline the paging organisation and its impact on the UE
Characterise the random access, its power control and code planning
Describe the DPCHs, their power control, time organisation, and L1
synchronisation

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

The Physical layer Rel. 99

The Physical Layer Rel. 99


Channel Mapping
Transport Channel Formats
Cell Synchronisation
Common Control Physical Channels
Physical Random Access
Dedicated Physical Channel Downlink
Dedicated Physical Channel Uplink

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

The Physical layer Rel. 99

Radio Interface Channel Organisation


In UMTS there are three different types of channels:
Logical Channels
Logical Channels transmit specific contents.
There are e.g. logical channel to transmit the cell system information, paging information, or user data.
Logical channels are offered as data transfer service by the Medium Access Control (MAC) layer to the next
higher layer.
Consequently, logical channels are in use between the mobile phone and the RNC.

Transport Channels (TrCH)


The MAC layer is using the transport service of the lower lower, the Physical layer.
The MAC layer is responsible to organise the logical channel data on transport channels. This process is called
mapping.
In this context, the MAC layer is also responsible to determine the used transport format.
The transport of logical channel data takes place between the UE and the RNC.

Physical Channels (PhyCH)

The physical layer offers the transport of data to the higher layer.
The characteristics of the physical transport have to be described.
When we transmit information between the RNC and the UE, the physical medium is changing.
Between the RNC and the Node B, where we talk about the interface Iub, the transport of information is
physically organised in so-called Frames.
Between the Node B and the UE, where we find the WCDMA radio interface Uu, the physical transmission is
described by physical channels.
A physical channel is defined by the UARFCN and the a spreading code in the FDD mode.

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

The Physical layer Rel. 99

Radio Interface Channel Organisation

Logical Channels
content is organised in separate channels, e.g.
System information, paging, user data, link management

Transport Channels
logical channel information is organised on transport channel
resources before being physically transmitted

Physical Channels
(UARFCN, spreading code)

Nokia Siemens Networks

Frames
Iub interface

RN31552EN20GLA0

RN31552EN20GLA0

The Physical layer Rel. 99

Logical Channels
There are two types of logical channels (FDD mode):
1) Control Channels (CCH):
Broadcast Control Channel (BCCH)
System information is made available on this channel.
The system information informs the UE about the serving PLMN, the serving cell, neighbourhood lists,
measurement parameters, etc.
This information permanently broadcasted in the DL.
Paging Control Channel (PCCH)
Given the BCCH information the UE can determine, at what times it may be paged.
Paging is required, when the RNC has no dedicated connection to the UE.
PCCH is a DL channel.
Common Control Channel (CCCH)
for UL & DL Control information
in use, when no RRC connection exists between the UE and the network
Dedicated Control Channel (DCCH)
UL & DL: Layer 3 Signalling dedicated to a specific radio link.

2) Traffic Channels (TCH):


Dedicated Traffic Channel (DTCH)
UL & DL: dedicated resources for User data transmission between the UE and the network
Common Traffic Channel (CTCH)
DL only: User data to be transmitted point-to-multipoint to a group of UEs.

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

The Physical layer Rel. 99

Transport Channels (TrCH)


Logical Channels are mapped onto Transport Channels. There are two types of Transport Channels (FDD mode):

a) Common Transport Channels:


Broadcast Channel (BCH)
It carries the BCCH information.
Paging Channel (PCH)
It is in use to page a UE in the cell, thus it carries the PCCH information. It is also used to notify UEs about cell
system information changes.

Forward Access Channel (FACH)


The FACH is a DL channel. Control information, but also small amounts of user data can be transmitted on this
channel.

Random Access Channel (RACH)


This UL channel is used by the UE, when small amounts of data have to be transmitted; the UE requires no
Dedicated resources. It is often used to allocated dedicated signalling resources to the UE to establish a connection
or to perform higher layer signalling. It is a contention based channel, i.e. several UE may attempt to access UTRAN
simultaneously.

b) Dedicated Transport Channels:


Dedicated Channel (DCH)
Dedicated resources can be allocated both UL & DL to a UE. Dedicated resources are exclusively in use for the
subscriber.

HS-Downlink Shared Channel (HS-DSCH) & E-DCH


Transport Channels for DL HSDPA respectively UL HSUPA data transfer
Note: DSCH (FDD), CPCH removed from R5 specification, 25.301 v5.6.0
7

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

The Physical layer Rel. 99

Physical Channels (PhyCH)


Physical Channels are characterised by
UARFCN,
Scrambling Code,
Channelisation Code (optional),
start and stop time, and
relative phase (in the UL only, with relative phase being 0 or /2)
Transport channels can be mapped to physical channels.
But there exist physical channels, which are generated at the Node B only, as can be seen on the next
figures.
The details of the physical channels is described in detail within this module (see following pages).

Note: PDSCH & PCPCH have been removed from R5 specification, 25.301 v5.6.0

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

The Physical layer Rel. 99

Channel Mapping DL (Network Point of View)


Logical
Channels

Transport
Channels

Physical
Channels
P-SCH
S-SCH

BCCH

BCH

PCCH

PCH

CCCH

FACH

CTCH

CPICH
P-CCPCH
S-CCPCH
PICH
AICH

DCCH

HSDSCH

F-DPCH
HS-PDSCH
HS-SCCH

DTCH

DCH

DPDCH
DPCCH
E-AGCH
E-RGCH
E-HICH

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

The Physical layer Rel. 99

Channel Mapping UL (Network Point of View)


Logical
Channels

Transport
Channels

Physical
Channels

RACH
PRACH

CCCH

DCCH

DPDCH
DCH
DTCH
E-DCH

10

Nokia Siemens Networks

DPCCH
HS-DPCCH
E-DPDCH
E-DPCCH

RN31552EN20GLA0

RN31552EN20GLA0

10

The Physical layer Rel. 99

Channel configuration examples


AMR call
The data transferred during AMR call consists of
Speech data
L3 signalling
L1 signalling

User data is transferred on DTCH logical channel


RT connection uses always DCH transport channel
DCH transport channel is mapped on DPCH (DPDCH + DPCCH)
AMR + PS call (Multi-RAB)
Additional stream of user data
NRT data

Also configurations with HS-DSCH possible


NRT PS call
Different configurations utilising DCH, FACH/RACH, HS-DSCH or HS-DSCH/E-DCH
possible

11

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

11

The Physical layer Rel. 99

Example Channel configuration during call


Data

RRC
signalling

Logical
Channels

DCCH0-4

Transport
Channels

Physical
Channels

DCH1
DPDCH

Speech
data

DTCH1

DCH2-4

NRT
data

DTCH2

DCH5

DPCCH

AMR speech
+
NRT data

AMR speech connection utilises multiple transport channels


RRC connection utilises multiple logical channels
DPCCH for L1 control data
12

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

12

The Physical layer Rel. 99

The Physical Layer Rel. 99


Part I: Channel Mapping
Part II: Transport Channel Formats
Part III: Cell Synchronisation
Part IV: Common Control Physical Channels
Part V: Physical Random Access
Part VI: Dedicated Physical Channel Downlink
Part VII: Dedicated Physical Channel Uplink

13

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

13

The Physical layer Rel. 99

Transport Channel Formats


Transport Channels are used to exchange data between the MAC-layers in the UE and the RNC.
The data is hereby organised in Transport Blocks (TB). A Transport Block is the basic data unit.
The MAC layer entities use the services offered to them by the Physical layer to exchange Transport
Blocks.
One Transport Block can be transmitted only over one Transport Channel. Several Transport Blocks
can be simultaneously transmitted via a Transport Channel in one transport data unit to increase the
transport efficiency.
The set of all Transport Blocks, transmitted at the same time on the same transport channel (between
the MAC layer and the physical layer) is referred to as Transport Format Set (TFS).
Transport Blocks and Transport Block Sets are characterised by a set of attributes:
Transport Block Size
The transport block size specifies the numbers of bits of one Transport Block.
If several Transport Blocks are transmitted within one TBS, then all TBs have the same size.
Please note, that the transport block size among different TBSs which are transmitted at different times on one transport
channel - can vary.

Transport Block Set Size


This attribute identifies the numbers of bits in one TBS.
It must be always a multiple of the transport block size, because all TBs transmitted in one TBS have the same size.

(continued on the next text slide)

14

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

14

The Physical layer Rel. 99

The Transfer of Transport Blocks


Node B
RNC

UE

MAC Layer

MAC Layer
Transport Channel
TBS

TBS

TFI

TFI

FP/AAL2
PHY Layer

FP/AAL2

PHY Layer
L1

L1

TTI radio
frames in use
15

Nokia Siemens Networks

RN31552EN20GLA0

TBS: Transport Block Set


TFI: Transport Format Indicator

RN31552EN20GLA0

15

The Physical layer Rel. 99

Transport Channel Formats


Transport Blocks and Transport Block Sets are characterised by a set of attributes (continued):
Transmission Time Interval (TTI)
The TTI specifies the transmission time distance between two subsequent TBSs, transferred
between the MAC and the PHY layer.
In the PHY layer, the TTI also identifies the interleaving period. Following TTI periods are
currently specified:
- 2 ms (HS-DSCH), 10 ms, 20 ms, 40 ms, and 80 ms
Error Protection Scheme
When data is transmitted via a wireless link, it faces a lot of distortion and can thus easily
corrupted.
Redundancy is added to the user data to reduce the amount of losses on air.
In UMTS, three error protection schemes are currently specified:
convolutionary coding with two rates: 1/2 and 1/3,
turbo coding (rate 1/3), and
no channel coding (this coding type is scheduled for removal from the UMTS
specifications).
Size of CRC
CRC stands for cyclic redundancy check. Each TBS gets an CRC.
The grade of reliability depends on the CRC size, which can be 0, 8, 12, 16, and 24 bits.

16

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

16

The Physical layer Rel. 99

Transport Formats
TFCS
TB
TB

TB

DCH 2

TB

TTI

TTI

TTI

TB
TB
TB

TB

TB

TB

TB

TBS

DCH 1

TFS
TTI

TTI

TTI

TFC

TB
TBS

17

Nokia Siemens Networks

TF
Transport Block
Transport Block Set

TF
TFS
TFC
TFCS

Transport Format
Transport Format Set
Transport Format Combination
Transport Format Combination Set

RN31552EN20GLA0

RN31552EN20GLA0

17

The Physical layer Rel. 99

Transport Channel Formats


The above description refers to a situation, where the MAC-layer hands the TBS to the PHY layer.
This happens in the UE. But TBSs are normally exchanged between the UE and the RNC. As a
consequence, the TBS must be transmitted over an AAL2 virtual channel between the RNC and the
Node B. The TBS is packet into a frame protocol defined for the traffic channel.
Different TBSs can be transmitted in one Transport Channel.
How do MAC and PHY layer know, what kind of TBS they exchanged?

18

When a transport channel is setup or modified the allowed Transport Block Sets are specified.
Each allowed TBS gets a unique Transport Format Indicator (TFI).
All TFIs of a Transport Channel are summarised in the Transport Format Set (TFS).
The TF consists of two parts (FDD mode):
Semi-static part
The attributes belonging to the semi-static part are set by the RRC-layer.
They are valid for all TBSs in the Transport Channel.
Semi-static attributes are the Transmission Time Interval (TTI), the error correction
scheme, the CRC size, and the static rate matching parameter (used by the PHY layer for
dynamic puncturing if the TBS is too long for the radio frame).
Dynamic part
The dynamic part comprises attributes, which can be changed by the MAC layer
dynamically.
The affected attributes are the Transport Block Size & Transport Block Set Size.
Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

18

The Physical layer Rel. 99

Transport Formats
RRC Layer

Transport Format
Semi-Static Part
TTI
Channel Coding
CRC size
Rate matching
Dynamic Part
Transport Block Size
Transport Block Set Size

configuration

MAC Layer

TrCHs

PHY Layer
Example: semi-static part dynamic part:
- TTI = 10 ms
- turbo coding
- transport block size:
64
- CRC size = 0
- transport block set size: 1
- ...

19

Nokia Siemens Networks

RN31552EN20GLA0

TrCH: Transport Channel


TBS: Transport Block Set
TFI: Transport Format Indicator

TFI1

RN31552EN20GLA0

64
2

64
4

128
2

TFI2

TFI3

TFI4

19

The Physical layer Rel. 99

Transport Channel Formats


The PHY layer can multiplex several Transport Channels in one internal Transport Channel, called
Coded Composite Transport Channel (CCTrCH).
This CCTrCH can be transmitted on one or several physical channels. Consequently, the TCSs of
different Transport Channels can be found in one radio frame.
The Transport Format Combination Set (TFCS) lists all allowed Transport Format Combinations
(TFC).
A Transport Format Combination Indicator (TFCI) is then used to indicate, what kind of Transport
Format Combination is found on the radio frame. You can find TFCI-fields for instance in the SCCPCH. The TFCS is set by the RRC protocol.
The table on the following slide lists the allowed Transport Formats for the individual Transport
Channels (FDD mode only).

20

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

20

The Physical layer Rel. 99

Transport Format Ranges

Dynamic Part

Semi-static Part

Transport
Block Size

Transport
Block Set Size

TTI

coding types
and rates

CRC
size

BCH

246 bits

246 bits

20 ms

convolutional 1/2

16

PCH

1...5000 bits
granularity: 1 bit

1...200000 bits
granularity: 1 bit

10 ms

convolutional 1/2

0, 8, 12,
16 & 24

FACH

0...5000 bits
granularity: 1 bit

0...200000 bits
granularity: 1 bit

10, 20, 40
& 80 ms

convolutional 1/2
& 1/3; turbo 1/3

0, 8, 12,
16 & 24

RACH

0...5000 bits
granularity: 1 bit

0...200000 bits
granularity: 1 bit

10 & 20
ms

convolutional 1/2

0, 8, 12,
16 & 24

DCH

0...5000 bits
granularity: 1 bit

0...200000 bits
granularity: 1 bit

10, 20, 40
& 80 ms

convolutional 1/2
& 1/3; turbo 1/3

0, 8, 12,
16 & 24

3GPP TS 25.302 V5.9.0


21

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

21

The Physical layer Rel. 99

Example: Transport Formats in AMR call


The AMR codec was originally developed and standardized by the European
Telecommunications Standards Institute (ETSI) for GSM cellular systems. It has been
chosen by the Third Generation Partnership Project (3GPP) as the mandatory codec for
third generation (3G) cellular systems. It supports 8 encoding modes with bit rates
between 4.75 and 12.2 kbps.
Feature of the AMR codec is Unequal Bit-error Detection and Protection (UED, UEP).
The UEP/UED mechanisms allow more speech over a lossy network by sorting the bits
into perceptually more and less sensitive classes (A, B, C).
A frame is only declared damaged and not delivered if there are bit errors found in the most
sensitive bits (Class A).
Acceptable speech quality results if the speech frame is delivered with bit errors in the less
sensitive bits (Class B, C). Decoder uses error concealment algorithm to hide the errors.

On the radio interface, one Transport Channel is established per class of bits i.e. DCH A
for class A, DCH B for class B and DCH C for class C. Each DCH has a different transport
format combination set which corresponds to the necessary protection for the
corresponding class of bits as well as the size of these class of bits for the various AMR
codec modes.

22

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

22

The Physical layer Rel. 99

Example: Transport Formats in AMR call


DCH 1: AMR class A
bits

DCH 2: AMR class B


bits

DCH 3: AMR class C


bits

le
mp
a
Ex
DCH 24: RRC
Connection
TTI = 40 ms

TTI = 20 ms

TTI = 20 ms

Coding type: convolutional

Convolutional coding

Coding rate: 1/3

Coding rate: 1/3

Coding rate: 1/2

Coding rate: 1/3

CRC size: 12 bits

CRC size: 0 bits

CRC size: 0 bits

CRC size: 16 bits

TTI = 20 ms
Convolutional coding

Coding type: convolutional

TBS size:1
TB size: 81 bits

TBS size: 1
TB size: 39 bits
(SID)

TBS size = 0
(DTX)

TBS size: 1
TB size: 103 bits

TBS size = 0
(DTX)

TBS size: 1
TB size: 60 bits

TBS size = 0
(DTX)

12.2 kbit/s
23

Nokia Siemens Networks

TBS size = 1
TB size: 148 bits

TBS size = 0
(DTX)

3.7 kbit/s

RN31552EN20GLA0

RN31552EN20GLA0

23

The Physical layer Rel. 99

The Physical Layer Rel. 99


Part I: Channel Mapping
Part II: Transport Channel Formats
Part III: Cell Synchronisation
Part IV: Common Control Physical Channels
Part V: Physical Random Access
Part VI: Dedicated Physical Channel Downlink
Part VII: Dedicated Physical Channel Uplink

24

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

24

The Physical layer Rel. 99

Cell Synchronisation
When a UE is switched on, it starts to monitor the radio interface to find a suitable cell to camp on but
it has to determine, whether there is a WCDMA cell nearby.
If a WCDMA cell is available, the UE has to be synchronised to the DL transmission of the system
information transmitted on the physical channel P-CCPCH before it can make a decision, in how
far the available cell is suitable to camp on.
Initial cell selection is not the only reason, why a UE wants to perform cell synchronisation. This
process is also required for cell re-selection and the handover procedure.
Cell synchronisation is achieved in 3 steps*:
Step 1: Slot synchronisation
During the first step of the cell search procedure the UE uses the SCHs primary synchronisation code to acquire slot
synchronisation to a cell. This is typically done with a single matched filter (or any similar device) matched to the primary
synchronisation code which is common to all cells. The slot timing of the cell can be obtained by detecting peaks in the
matched filter output.

Step 2: Frame synchronisation and code-group identification


During the second step of the cell search procedure, the UE uses the SCHs secondary synchronisation code to find
frame synchronisation and identify the code group of the cell found in the first step. This is done by correlating the
received signal with all possible secondary synchronisation code sequences, and identifying the maximum correlation
value. Since the cyclic shifts of the sequences are unique the code group as well as the frame synchronisation is
determined.

Step 3: Scrambling-code identification


During the third and last step of the cell search procedure, the UE determines the exact primary scrambling code used by
the found cell. The primary scrambling code is typically identified through symbol-by-symbol correlation over the CPICH
with all codes within the code group identified in the second step. After the primary scrambling code has been identified,
the Primary CCPCH can be detected. And the system- and cell specific BCH information can be read.

If the UE has received information about which scrambling codes to search for, steps 2 and 3 above
can be simplified.
25

Nokia Siemens Networks

RN31552EN20GLA0

* further Information about Primary- & Secondary Synchronisation


Channels and Code Groups can be found on the following pages

RN31552EN20GLA0

25

The Physical layer Rel. 99

Cell Synchronisation

Detect cells

Phase 1 P-SCH

Acquire slot
synchronisation
Acquire frame synchronisation

Phase 2 S-SCH

Identify the code group of the


cell found in the first step

Determine the exact primary


scrambling code used by the
found cell

Phase 3 P-CPICH
PriScrCode
WCEL; 0..511; 1; no default
(Range; Step; Default)
26

Nokia Siemens Networks

Measure level & quality of the


found cell

RN31552EN20GLA0

RN31552EN20GLA0

26

The Physical layer Rel. 99

Cell Synchronisation
Cell synchronisation is achieved with the Synchronisation Channel (SCH). This channel divides up into
2 sub-channels:

Primary Synchronisation Channel (P-SCH)


A time slot lasts 2560 chips.
The P-SCH only uses the first 10% of a time slot.
A Primary Synchronisation Code (PSC) is transmitted the first 256 chips of a time slot. This is the case
in every UMTS cell.
If the UE detects the PSC, it has performed TS and chip synchronisation.

Secondary Synchronisation Channel (S-SCH)


The S-SCH also uses only the first 10% of a timeslot
Secondary Synchronisation Codes (SSC) are transmitted.
There are 16 different SSCs, which are organised in a 10 ms frame (15 timeslots) in such a way, that
the beginning of a 10 ms frame can be determined, and 64 different SSC combinations within a 10 ms
frame are identified.
There is a total of 512 primary scrambling codes, which are grouped in 64 scrambling code families,
each family holding 8 scrambling code members.
The 15 SSCs in one 10 ms frame identify the scrambling code family of the cells DL scrambling code.

27

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

27

The Physical layer Rel. 99

Synchronisation Channel (SCH)


2560 Chips

256 Chips

Primary Synchronisation Channel (P-SCH)

CP

CP

CP

CP

Cs15

Cs1

Secondary Synchronisation Channel (S-SCH)


Cs1

Cs2

Slot 0

Slot 1

Slot 14

Slot 0

10 ms Frame
Cp = Primary Synchronisation Code
Cs = Secondary Synchronisation Code
28

Nokia Siemens Networks

PtxPrimarySCH

PtxSecSCH

-35..15; 0.1; -3 dB

-35..15; 0.1; -3 dB

(Range; Step; Default)

(Range; Step; Default)

RN31552EN20GLA0

RN31552EN20GLA0

28

The Physical layer Rel. 99

SSC Allocation for S-SCH


scrambling
code group

slot number
0

10

11

12

13

14

group 00

10

15

10

16

15

16

group 01

16

14

16

10

12

14

12

10

group 02

15

12

16

11

16

11

15

12

group 03

group 04

16

11

15

12

15

12

16

11

group 05

group 62

11

12

15

12

13

13

11

14

10

16

15

14

16

group 63

12

10

15

13

14

14

15

11

11

13

12

16

10

11

29

Nokia Siemens Networks

15

I monitor the
S-SCH

RN31552EN20GLA0

RN31552EN20GLA0

29

The Physical layer Rel. 99

Common Pilot Channel (CPICH)


With the help of the SCH, the UE was capable to perform chip, TS, and frame synchronisation.
Even the cells scrambling code group is known to the UE.
But in the initial cell selection process, it does not yet know the cells primary scrambling code.
There is one primary scrambling code in use over the entire cell, and in neighbouring cells, different
scrambling codes are in use.
There exists a total of 512 primary scrambling codes.
The CPICH is used to transmit in every TS a pre-defined bit sequence with a spreading factor 256.
The CPICH divides up into a mandatory Primary Common Pilot Channel (P-CPICH) and optional
Secondary CPICHs (S-CPICH).
The P-CPICH is in use over the entire cell and it is the first physical channel, where a spreading code
is in use.
A spreading code is the product of the cells scrambling code and the channelisation code.
The channelisation code is fixed: Cch,256,0. i.e., the UE knows the P-CPICHs channelisation code,
and it uses the P-CPICH to determine the cells primary scrambling code by trial and error.
The P-CPICH is not only used to determine the primary scrambling code. It also acts as:phase reference for most of the physical channels,
measurement reference in the FDD mode (and partially in the TDD mode).
There may be zero or several S-CPICHs. Either the cells primary scrambling code or its secondary
scrambling codes can be used. In contrast to the P-CPICH, it can be broadcasted just over a part of
the cell.

30

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

30

The Physical layer Rel. 99

Primary Common Pilot Channel (P-CPICH)


10 ms Frame
2560 Chips

256 Chips

Synchronisation Channel (SCH)

CP
P-CPICH

Cell scrambling
code? I get it with
trial & error!

P-CPICH

applied speading code =


cells primary scrambling code C ch,256,0

Phase reference
Measurement reference

PtxPrimaryCPICH
-10..50; 0.1; 33 dBm
(Range; Step; Default)

(20 W sector)
31

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

31

The Physical layer Rel. 99

CPICH as Measurement Reference


The UE has to perform a set of L1 measurements, some of them refer to the CPICH channel:
CPICH RSCP
RSCP stands for Received Signal Code Power.
The UE measures the RSCP on the Primary-CPICH.
The reference point for the measurement is the antenna connector of the UE.
The CPICH RSCP is a power measurement of the CPICH.
The received code power may be high, but it does not yet indicate the quality of the received
signal, which depends on the overall noise level.
UTRA carrier RSSI.
RSSI stands for Received Signal Strength Indicator.
The UE measures the received wide band power, which includes thermal noise and receiver
generated noise.
The reference point for the measurements is the antenna connector of the UE.
CPICH Ec/No
The CPICH Ec/No is used to determine the quality of the received signal.
It gives the received energy per received chip divided by the bands power density.
The quality is the primary CPICHs signal strength in relation to the cell noise.
(Please note, that transport channel quality is determined by BLER, BER, etc. )
If the UE supports GSM, then it must be capable to make measurements in the GSM bands, too. The
measurements are based on the GSM carrier RSSI
The wideband measurements are conducted on GSM BCCH carriers.
32

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

32

The Physical layer Rel. 99

P-CPICH as Measurement Reference


CPICH RSCP

Received Signal Code Power (in dBm)

CPICH Ec/No

received energy per chip divided by the power density in the band (in dB)

UTRA carrier
RSSI

received wide band power, including thermal noise and noise generated in the
receiver

CPICH Ec/No =
CPICH Ec/No
0: < -24
1: -23.5
2: -23
3: -22.5
...
47: -0.5
48: 0
49: >0
Ec/No values in dB
33

Nokia Siemens Networks

CPICH RSCP
UTRA carrier RSSI

CPICH RSCP
-5: < -120
-4: -119
:
0: -115
1: -114
:
89: -26
90: -25
91: -25
RSCP values in dBm

GSM carrier RSSI


0: -110
1: -109
2: -108
:
71: -39
72: -38
73: -37
RSSI values in dBm

RN31552EN20GLA0

RN31552EN20GLA0

33

The Physical layer Rel. 99

Primary Common Control Physical Channel (P-CCPCH)


The UE knows the cells primary scrambling code.
It now wants to gain the cell system information, which is transmitted on the physical channel PCCPCH.
The channelisation code of the P-CCPCH is also known to the UE, because it must be Cch,256,1 in
every cell for every operator.
By reading the cell system information on the P-CCPCH, the UE learns everything about the
configuration of the remaining common physical channels in the cell, such as the physical channels for
paging and random access.
As can be seen from the P-CCPCHs channelisation code, the data rate for cell system information is
fixed.
The SCH is transmitted on the first 256 chips of a timeslot, thus creating here a peak load.
The cell system information is transmitted in the timeslot except for the first 256 chips. By doing so, a
high interference and load at the beginning of the timeslot is avoided.
This leads to a net data rate of 27 kbps for the cell system information.
Channel estimation is done with the CPICH, so that no pilot sequence is required in the P-CCPCH.
(The use of the pilot sequence is explained in the context of the DPDCH later on in this
document.)
There are also no power control (TPC) bits transmitted to the UEs.

34

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

34

The Physical layer Rel. 99

Primary Common Control Physical Channel (P-CCPCH)


10 ms Frame
2560 Chips

256 Chips

Synchronisation Channel (SCH)

CP
P-CCPCH

PtxPrimaryCCPCH

Finally, I get the


cell system
information

-35..15; 0.1; -5 dB
(Range; Step; Default)

P-CCPCH

channelisation code: Cch,256,1


no TPC, no pilot sequence
27 kbps (due to off period)
organised in MIBs and SIBs

35

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

35

The Physical layer Rel. 99

Synchronisation Issues and Node Synchronisation


Synchronisation Issues in UMTS. 5 different UTRAN synchronisation issues were identified:
1.

Network synchronisation stands for the very accurate reference frequency, which must be
distributed to the individual UTRAN network elements.

2.

Node synchronisation takes place between the Node B and the RNC.

Node Synchronisation is used to determine the run-time difference between UTRAN nodes,
which must be estimated and then compensated.

In the FDD mode, only RNC-Node B Node Synchronisation is in use.

3.

While radio interface synchronisation is required between the UE and the Node B.

4.

Transport channel synchronisation is a L2 synchronisation (for the MAC layer).

It is therefore done between the UE and the RNC.

Please note in this context, that a UE may be in a soft handover state, i.e. the UE may be
connected to several cells simultaneously.

Transport channel synchronisation is required to guarantee, that the transport of user data
via several channels is coordinated in such a way, that the transmitted data from several
cells arrives within the UEs receive window.

5.

Time alignment handling takes place between UTRAN and the CN for adequate timing of data
transfer.

36

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

36

The Physical layer Rel. 99

Node Synchronisation
RFN:
RNC Frame
Number counter
0..4095 frames

Node B
SRNC
BFN

BFN:
Node B Frame
Number counter
0..4095 frames

128

T1

129

T2

ation
roniz
ynch
S
e
d
o
DL N
( T1 )

130

3114

UL
Nod
( T1 e Sync
hro
,T2,
niza
T3 )
tion

132

3116
UL offset

133

3117

134

Nokia Siemens Networks

(T4 T1) (T3 T2)


= Round Trip Delay
(RTD) determination
for DCH services

3115

T3

37

DL offset

3113

131

user plane defined on


DCH, FACH & DSCH

time

3118
time

135

RFN

3112

(T4)
T1, T2, T3
range: 0 .. 40959.875 ms
resolution: 0.125 ms

RN31552EN20GLA0

RN31552EN20GLA0

37

The Physical layer Rel. 99

Cell Synchronisation and Sectorised Cells


A timing reference is required by the Node Synchronisation:
Node B Frame Number (BFN)
The BFN is a counter at the Node B, based on the 10 ms framing structure of WCDMA.
RNC Frame Number (RFN)
The RFN is a counter at the RNC, based on the 10 ms framing structure of WCDMA.
Cell System Frame Number (SFN)
This is a counter for each cell, and is broadcasted on the P-CCPCH.
With one Node B, several (sector) cells can be deployed. These cells overlap.
If the SCH is transmitted at the same tame in all the sector cells of the Node B, and when a UE is in
the overlapping coverage area of two of these cells, it will have difficulties to synchronise to one cell.
As a consequence, an offset can be used for neighbouring cells of one Node B: T_cell.
T_cell is a timing delay for the starting time of the physical channels SCH, CPICH, BCCH relative
to the Node Bs timer BFN.
The timing delay is a multiple (0..9) of 256 chips due to of the length of a SCH burst.
The cells timing is identified with the counter SFN = BFN + T_cell.
(Please note, that this description only applied for the FDD mode!)

38

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

38

The Physical layer Rel. 99

Cell Synchronization and Sectorised Cells


T_cell1

1 TS
S
C
H

cell1

S
C
H

S
C
H

T_cell2

Tcell
WCELL; 0..2304 chip;
256 chip; no default

S
C
H

cell2

S
C
H

S
C
H

S
C
H

cell3
T_cell3

SFN =
BFN + T_cell3

S
C
H

SFN = BFN + T_cell1

cell1

BFN
SFN = BFN + T_cell2

Node B with three


sectorised cells

cell3

BFN: Node B Frame Number


RFN: RNC Frame Number
SFN: Cell Frame Number
39

Nokia Siemens Networks

SFN: Cell System Frame Number


range: 0..4095 frames
T_cell: n 256 chips, n = 0..9

cell2

Tcell: Timing delay used for defining the start of SCH, PCPICH, P-CCPCH in a cell relative to BFN
RN31552EN20GLA0

RN31552EN20GLA0

39

The Physical layer Rel. 99

The Physical Layer Rel. 99


Part I: Channel Mapping
Part II: Transport Channel Formats
Part III: Cell Synchronisation
Part IV: Common Control Physical Channels
Part V: Physical Random Access
Part VI: Dedicated Physical Channel Downlink
Part VII: Dedicated Physical Channel Uplink

40

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

40

The Physical layer Rel. 99

Secondary Common Control Physical Channel


(S-CCPCH)
The S-CCPCH can be used to transmit the transport channels
Forward Access Channel (FACH) and
Paging Channel (PCH).
More than one S-CCPCH can be deployed.
FACH & PCH information can multiplexed on one S-CCPCH (even on the same 10 ms frame), or they
can be carried on different S-CCPCH.
The first S-CCPCH must have a spreading factor of 256, while the SF of the remaining S-CCPCHs
can range between 256 and 4.
UTRAN determines, whether a S-CCPCH has the TFCI (Transport Format Combination Indicator)
included.
Please note, that the UE must support both S-CCPCHs with and without TFCI.

41

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

41

The Physical layer Rel. 99

Secondary Common Control Physical Channel (S-CCPCH) (1/7)


10 ms Frame
Slot 0

Slot 1

TFCI
(optional)

Slot 2

Data

carries PCH and FACH


Multiplexing of PCH and FACH on one
S-CCPCH, even one frame possible
with and without TFCI (UTRAN set)
SF = 4..256
(18 different slot formats
no inner loop power control

42

Nokia Siemens Networks

Slot 14

Pilot bits

S-CCPCH

RN31552EN20GLA0

RN31552EN20GLA0

42

The Physical layer Rel. 99

S-CCPCH (2/7): Number of S-CCPCHs


The S-CCPCH (Secondary Common Control Physical Channel) carries FACH & PCH
transport channels
Parameter WCEL: NbrOfSCCPCHs (Number of SCCPCHs) tells how many SCCPCHs
will be configured for the cell. (1, 2 or 3)
If only 1 SCCPCH is used in a cell, it will carry FACH-c (containing DCCH/CCCH /BCCH),
FACH-u (containing DTCH) and PCH. FACH and PCH multiplexed onto the same SCCPCH.
If 2 SCCPCHs are used in a cell, the first SCCPCH will carry FACH-u & FACH-c and the second
SCCPCH will always carry PCH only.
If 3 SCCPCHs are used in a cell, the third SCCPCH will carry FACH-s (containing CTCH) &
FACH-c idle (containing CCCH & BCCH). The third SCCPCH is only needed when Service Area
Broadcast (SAB) is active in a cell.
NbrOfSCCPCHs
WCEL; 1..3; 1; 1
(Range; Step; Default)

43

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

43

The Physical layer Rel. 99

S-CCPCH (3/7): Configuration 1

If only 1 SCCPCH is used in a cell, it will carry FACH-c (containing DCCH/CCCH /BCCH), FACH-u
(containing DTCH) and PCH. FACH and PCH multiplexed onto the same SCCPCH.

the PCH bit rate is limited to 8 kbps

the PCH always has priority

the SF for SCCPCH, which is carrying FACH (with or without PCH), is 64 (60ksps)

Logical channel

Transport channel

DTCH

FACH-u

DCCH

CCCH

FACH-c

SCCPCH 1

Physical channel

SF 64

44

Nokia Siemens Networks

BCCH

PCCH

PCH

PtxSCCPCH1
Transmission Power of SCCPCH1

WCEL; -35..15; 0.1; 0 dB


(Range; Step; Default)

RN31552EN20GLA0

RN31552EN20GLA0

44

The Physical layer Rel. 99

S-CCPCH (4/7): Configuration 2 a & b

If 2 SCCPCHs are used in a cell, the first SCCPCH will carry FACH-u & FACH-c and the second
SCCPCH will always carry PCH only.

PCH bit rate limited to 8 kbps (RU10 & earlier) or can be extended
to 24 kbps (RU20 feature RAN 1202: 24 kbps Paging Channel)

if PCH24kbps enabled, NbrOfSCCPCHs must be set to 2 or 3

Logical
channel

DTCH

DCCH

CCCH

BCCH

PCH24kbpsEnabled
WCEL; 0 (Disabled), 1 (Enabled);
default: 0 (Disabled)

PCCH
PtxSCCPCH2
used for 8 kbps paging

Transport
channel

FACH-u

FACH-c

PCH

WCEL; -35..15; 0.1; -5 dB

PtxSCCPCH2SF128
used for 24 kbps paging

WCEL; -35..15; 0.1; -2 dB

Physical
channel

SCCPCH 1

SCCPCH 2

SF 64
or
45

Nokia Siemens Networks

SF 256
SF 128

RN31552EN20GLA0

RN31552EN20GLA0

45

The Physical layer Rel. 99

S-CCPCH (5/7): Configuration 3a & b


if 3 SCCPCHs are used in a cell, the third SCCPCH will carry FACH-s (containing CTCH) & FACH-c
idle (containing CCCH & BCCH). The third SCCPCH is only needed when Service Area Broadcast
(SAB) is active in a cell.
For
For SAB
SAB

Logical channel

Transport
channel

Physical
channel

DTCH

DCCH

FACH-u

FACH-c

BCCH

CTCH

PCCH

FACH-c

FACH-s

PCH

CCCH

SCCPCH
connected

SCCPCH
idle

SCCPCH
page

SF 64

SF 128

SF 256
or

PtxSCCPCH3

SF 128

WCEL; -35..15; 0.1; -2 dB


46

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

46

The Physical layer Rel. 99

S-CCPCH (6/7): Summary Power Setting


The power of SCCPCHs are set relative to CPICH transmission power, but it is based on the bitrate.
The SF for SCCPCH, which is carrying FACH (with or without PCH), is 64 (60ksps)
The SF for SCCPCH, which is carrying PCH only is 256 (15ksps) or 128 (30ksps)
The SF for SCCPCH, which is carrying FACH-s/FACH-c idle for SAB, is 128 (30ksps)
Recommended value of the SCCPCH Tx power is depended on the number of SCCPCHs:
WCEL: PtxSCCPCH1 (SF=64)

for PCH/FACH or standalone FACH

WCEL: PtxSCCPCH2 (SF=256)

for Standalone PCH (8 kbps paging)

WCEL: PtxSCCPCH2SF128 (SF=128)

for Standalone PCH (24 kbps paging)

WCEL: PtxSCCPCH3 (SF=128)

for SAB

PtxSCCPCH1

PtxSCCPCH2

PtxSCCPCH3

WCEL; -35..15; 0.1; 0 dB

used for 8 kbps paging

WCEL; -35..15; 0.1; -2 dB

(Range; Step; Default)

WCEL; -35..15; 0.1; -5 dB

PtxSCCPCH2SF128
used for 24 kbps paging

WCEL; -35..15; 0.1; -2 dB


47

Nokia Siemens Networks

RN31552EN20GLA0

SF: Spreading Factor

RN31552EN20GLA0

47

The Physical layer Rel. 99

S-CCPCH (7/7) in NSN RAN

48

FACH-u

FACH-c
(connected)

FACH-c
(idle)

FACH-s

PCH

TFS

0: 0x360 bits
(0 kbit/s)
1: 1x360 bits
(36 kbit/s)

0: 0x168 bits
(0 kbit/s)
1: 1x168 bits
(16.8 kbit/s)
2: 2x168 bits
(33.6 kbit/s)

0: 0x168 bits
(0 kbit/s)
1: 1x168 bits
(16.8 kbit/s)

0: 0x168 bits
(0 kbit/s)
1: 1x168 bits
(16.8 kbit/s)

0: 0x80 bits
(0 kbit/s)
1: 1x80 bits
(8 kbit/s)
2: 1x240 bits
(24 kbps)

TTI

10 ms

10 ms

10 ms

10 ms

10 ms

Channel
coding

TC 1/3

CC 1/2

CC 1/3

CC 1/3

CC 1/2

CRC

16 bit

16 bit

16 bit

16 bit

16 bit

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

48

The Physical layer Rel. 99

The Paging Process


Paging Indicator Channel (PICH)
UMTS provides the terminals with an efficient sleep mode operation. The UEs do not have to read and
process the content, transmitted during their paging occasion on their S-CCPCH.
Each S-CCPCH, which is used for paging, has an associated Paging Indicator Channel (PICH).
A PICH is a physical channel, which carries paging indicators.
A set of (paging indicator) bits within the PICH indicate to a UE, whether there is a paging occasion for
it. Only then, the UE listens to the S-CCPCH frame, which is transmitted 7680 chips after the PICH
frame in order to see, whether there is indeed a paging message for it.
The PICH is used with spreading factor 256.
300 bits are transmitted in a 10 ms frame, and 288 of them are used for paging indication.
The UE was informed by the BCCH, how many paging indicators exist on a 10 ms frame.
The number of paging indicator Np can be 18, 36, 72, and 144, and is set by the operator as part of the network
planning process.
The higher Np, the more paging indicators exist, the more paging groups exist, among which UEs can be
distributed on.
Consequently, the lower the probability, that a UE reacts on a paging indicator, while there is no paging message
in the associated S-CCPCH frame.
But a high number of paging indicators results in a comparatively high output power for the PICH, because less
bits exists within a paging indicator to indicate the paging event.
The operator then also has to consider, if he has to increase the number of paging attempts.

How does the UE and UTRAN determine the paging indicator (PI) and the Paging Occasion?
This is shown in one of the next slides.

49

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

49

The Physical layer Rel. 99

S-CCPCH & associated PICH


S-CCPCH frame,
associated with PICH frame

S-CCPCH
PICH
PICH frame

= 7680
chips

for paging indication


b0

b1

b286 b287 b288

# of paging
indicators per frame
(Np)
18
36
72
144
50

Nokia Siemens Networks

no transmission

Np
Repetition of PICH bits

18, 36, 72 144

b299

PtxPICH
-10..5; 1; -8 dB
(Range; Step; Default)

RN31552EN20GLA0

RN31552EN20GLA0

50

The Physical layer Rel. 99

S-CCPCH and the Paging Process


The network has detected, that there is data to be transmitted to the UE.
Both in the RRC idle mode and in the RRC connected mode (e.g. in the sub-state CELL_PCH) a UE
may get paged. But how does the mobile know, when it was paged?

And in order to save battery power, we dont want the UE to listen permanently to paging
channel instead, we want to have discontinuous reception (DRX) of paging messages.

But when and where does the UE listen to the paging messages?
Cell system information is broadcasted via the P-CCPCH.
The cell system information is organised in System Information Blocks (SIB).

SIB5 informs the mobile phones about the common channel configuration, including a list of
S-CCPCH descriptions.

The first 1 to K entries transmit the (transport channel) PCH, while the remaining S-CCPCH
in the list hold no paging information.
The UE determines the S-CCPCH, where it is paged, by its IMSI and the number of PCH/S-CCPCHs
carrying S-CCPCHs K.
When paging the UE, the RNC knows the UEs IMSI, too, so that it can put the paging message on
the correct PCH transport channel.
Discontinuous Reception (DRX) of paging messages is supported.

51

A DRX cycle length k has to be set in the network planning process for the cs domain, ps domain, and
UTRAN.
k ranges between 3 and 9. If for instance k=6, then the UE is paged every 2k = 640 ms.
If the UE is in the idle mode, it takes the smaller k-value of either the cs- or ps-domain.
If the UE is in the connected mode, it has to select the smallest k-value of UTRAN and the CN, it is not
connected to.

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

51

The Physical layer Rel. 99

S-CCPCH & Paging Process


UTRAN

P-CCPCH/BCCH (SIB 5)
common
channel
definition,
including
a lists of

UE

Node B

RNC

Index of S-CCPCHs

S-CCPCH carrying 1 PCH

S-CCPCH carrying 1 PCH

K-1

S-CCPCH carrying 1 PCH


S-CCPCH without PCH

UEs paging channel:


Index = IMSI mod K
e.g. if IMSI mod K = 1
52

Nokia Siemens Networks

my paging
channel

S-CCPCH without PCH

RN31552EN20GLA0

RN31552EN20GLA0

52

The Physical layer Rel. 99

Paging & Discontinuous Reception (FDD mode)


Duration: 2k frames
k = 3..9

Example with
two CN domains

CN domain specific
DRX cycle lengths
(option)

stores

UE

RRC connected
mode

UTRAN_DRX_length
80; 160; 320; 640; 1280;
2560; 5120 ms

CS Domain

PS Domain

UTRAN

k1

k2

k3

Update:
a) derived by NAS
negotiation
b) otherwise:
system info

Update:
a) derived by NAS
negotiation
b) otherwise:
system info

Update:
locally with
system info

if RRC idle:
UE DRX cycle length is
min (k1, k2)
CNDRXLength

if RRC connected:
UE DRX cycle length is
min (k3, kdomain with no Iu-signalling connection)

640; 1280; 2560; 5120 ms


53

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

53

The Physical layer Rel. 99

Paging Indicator & Paging Occasion (FDD mode)


my paging
indicator (PI)

number of paging indicators


18, 36, 72, 144

PI = ( IMSI div 8192) mod Np

UE

DRX index
When will
I get paged?

Paging Occasion

number of S-CCPCH with PCH

= (IMSI div K) mod (DRX cycle length)


+ n * DRX cycle length

FDD
mode

UE

54

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

54

The Physical layer Rel. 99

Example Paging instant and group calculation


UE calculates paging instant based on following information as presented before
IMSI
Number of S-CCPCH (K)
DRX cycle length (k)
Np

User are distributed to different paging groups based on their IMSI. Paging group
size can be calculated based on
Number of S-CCPCH (K)
DRX cycle length (k)
Np

Paging group size affects on how often UE has to decode paging message from
S-CCPCH Power consumption
55

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

55

The Physical layer Rel. 99

Example Paging instant & group calculation


K (Number of S-CCPCH with PCH)
k (DRX length)
DRX cycle length
IMSI
Which S-CCPCH #?
IMSI div K
When (Paging occation, SFN)?
Np
DRX Index
My PI?

72 PIs/frame
43762994
26

Number of subsc. In LA/RA


Number of subsc. Per S-CCPCH
Number of subsc. Paging occation (PICH
frame)
Number of subsc. Per PI

56

Nokia Siemens Networks

1
6
64 frames
358506452377
0
358506452377
25 + n*DRX cycle length

100000
100000
1562.5
21.7

RN31552EN20GLA0

RN31552EN20GLA0

56

The Physical layer Rel. 99

The Physical Layer Rel. 99


Part I: Channel Mapping
Part II: Transport Channel Formats
Part III: Cell Synchronisation
Part IV: Common Control Physical Channels
Part V: Physical Random Access
Part VI: Dedicated Physical Channel Downlink
Part VII: Dedicated Physical Channel Uplink

57

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

57

The Physical layer Rel. 99

Random Access
In the random access, initiated by the UE, two physical channels are involved:
Physical Random Access Channel (PRACH)
The physical random access is decomposed into the transmission of preambles in the UL.
Each preamble is transmitted with a higher output power as the preceding one.
After the transmission of a preamble, the UE waits for a response by the Node B.
This response is sent with the physical channel Acquisition Indication Channel (AICH), telling
the UE, that the Node B as acquired the preamble transmission of the random access.
Thereafter, the UE sends the message itself, which is the RACH/CCCH of the higher layers.
The preambles are used to allow the UE to start the access with a very low output power.
If it had started with a too high transmission output power, it would have caused interference
to the ongoing transmissions in the serving and neighbouring cells.
Please note, that the PRACH is not only used to establish a signalling connection to UTRAN, it
can be also used to transmit very small amounts of user data.
Acquisition Indication Channel (AICH)
This physical channel indicates to the UE, that it has received the PRACH preamble and is now
waiting for the PRACH message part.

58

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

58

The Physical layer Rel. 99

Random Access the Working Principle


Node B
UE
No response
by the
Node B

No response
by the
Node B

PRAC H (pream ble)

PRAC H (pream ble)

I just detected
a PRACH preamble

PRAC H (pream ble)

OLA!

AICH
PRAC H (messa ge part)

59

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

59

The Physical layer Rel. 99

Random Access Timing


The properties of the PRACH are broadcasted (SIB5, SIB6).
The candidate PRACH is randomly selected (if there are several PRACH advertised in the cell) as well
as the access slots within the PRACH.
15 access slots are given in a PRACH, each access slot lasting two timeslots or 5120 chips.

In other words, the access slots stretch over two 10 ms frames.


A PRACH preamble, which is transmitted in an access slot, has a length of 4096 chips.
Also the AICH is organised in (AICH) access slots, which stretch over two timeslots.

AICH access slots are time aligned with the P-CCPCH.

60

The UE sends one preamble in UL access slot n.


It expects to receive a response from the Node B in the DL (AICH) access slot n, p-a chips later on.
If there is no response, the UE sends the next preamble p-p chips after the first one.
The maximum numbers of preambles in one preamble access attempt can be set between 1 and 64.
The number of PRACH preamble cycles can be set between 1 and 32.
If the AICH_Transmission_Timing parameter in the SIB is set to BCCH SIB5 & SIB6 to

0 = then, the minimum preamble-to-preamble distance is 6 access slots, the minimum


preamble-to-message distance is 6 access slots, and the preamble-to-acquisition indication
is 3 timeslots.

1 = then, the minimum preamble-to-preamble distance is 8 access slots, the minimum


preamble-to-message distance is 8 access slots, and the preamble-to-acquisition indication
is 4 timeslots.

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

60

The Physical layer Rel. 99

Random Access Timing


SFN mod 2 = 0

SFN mod 2 = 1

SFN mod 2 = 0

P-CCPCH
AICH access
slots

5120
chips

10 11 12

13 14

preamble-to-AI
distance p-a

4096 chips

Broadcasted by P-CCPCH;
NSN (WCEL):

AICHTraTime = 0, 1; 0

AS # i

Message
part

Preamble

Preamble
5120 chips

AS # i

preamble-to-preamble
distance p-p
Nokia Siemens Networks

Acquisition
Indication

AICH
access slots

61

TS 25.211:
Preamble-to-Preamble distance p-p p-p,min = 6 / 8 Slots
Preamble-to-AI distance p-a = 3 / 4 Slots
Preamble-to-Message distance p-m = 6 / 8 Slots

UE point of view

PRACH
access slots

preamble-to-message
distance p-m

RN31552EN20GLA0

RN31552EN20GLA0

61

The Physical layer Rel. 99

RACH Sub-channels and Access Service Classes


RACH Sub-channels

RACH sub-channels were introduced to define a sub-set of UL access slots.


A total number of 12 RACH sub-channels exist, numbered from 0 to 11.
The PRACH access slots are numbered relative to the AICH assess slot.

The offset is given by p-a (see preceding slides).

The AICH is transmitted synchronised to the P-CCPCH.

An access slot of sub-channel #i is using access slot #i, when SFN mod 8 = 0 or 1. It is then using every
12 th access slot following access slot #i.

You can see in the figure on the right hand side all existing sub-channels and the timeslots, they are
using.

Access Classes (AS) and Access Service Classes (ASC)

Access Service Classes were introduced to allow priority access to the PRACH resources, by
associating ASCs to specific access slot spaces (RACH sub-channels) and signatures.
8 ASC can be specified by the operator; The UE determines the ASC and its associated resources from
SIB5 & SIB7.
The mapping of the subscribers access classes (1..15) is part of the SIB5.

RACH Access Slot Sets

62

Two access slot set were specified:


Access slot set 1 holds PRACH access slots 1 to 7, i.e. the PRACH access slots, whose corresponding
AICH access slots begin in a P-CCPCH with a SFN modulo 2 = 0.
Access slot set 2 holds PRACH access slots 8 to 15, i.e. the PRACH access slots, whose
corresponding AICH access slots begin in a P-CCPCH with a SFN modulo 2 = 1.

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

62

The Physical layer Rel. 99

PRACH Sub-channels and Access Service Classes (ASC)


SFN mod 8 of the
corresponding
P-CCPCH frame

12

13

14

Sub-channel number

2
3

10

5
6

11

12

13

14

10

11

10

11

10

11

7
8

12

13

14

10

11

12

13

14

(cited from TS 25.214 V5.11.0, chap. 6.1.1)


BCCH (SIB 5, SIB 7)

UE
63

ASCs & their PRACH access resources + signatures,


AC mapping into ASCs

Nokia Siemens Networks

Node B

RN31552EN20GLA0

RN31552EN20GLA0

63

The Physical layer Rel. 99

PRACH Preamble
In the PRACH preamble, a random preamble code is used.
This code is composed from a

Preamble Scrambling Code and a

Preamble Signature
There is a total of 16 preamble signatures of 16 bit length, which is repeated 256 times within one
preamble.
When monitoring the cell system information, the UE gets the information, which of the signatures are
available for use in the cell. (see IE PRACH info)
There are 8192 preamble scrambling codes, which are constructed from the long scrambling code
sequences.
The PRACH preamble scrambling codes are organised in 512 groups, with each group holding 16
members.
There are also 512 primary scrambling codes available in UMTS, and one of them is in use in the cell.
If the primary scrambling code s is in use in the cell, then only the PRACH preamble scrambling codes
belonging to PRACH preamble scrambling code group s can be used for random access.
Consequently, 16 PRACH preamble scrambling codes are left, and the BCCH is used to inform the
UE, which PRACH preamble scrambling codes can be used. (see IE PRACH info)

64

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

64

The Physical layer Rel. 99

PRACH Preamble
UTRAN

BCCH

UE

available signatures for


random access
available preamble
scrambling codes
available spreading
factor
available sub-channels
etc.

Node B

RNC

Pi Pi

Pi Pi

PRACH Preamble Scrambling Code

16 chip
256 repetitions

Preamble Signature
(16 different versions)
65

Nokia Siemens Networks

AllowedPreamble
Signatures
WCEL; 16-bit field;
0.01111; max. 4
signatures allowed

512 groups, each with 16


preamble scrambling codes
Cells primary scrambling codes
associated with preamble
scrambling code group

RN31552EN20GLA0

RN31552EN20GLA0

65

The Physical layer Rel. 99

PRACH Message Part

The length of the PRACH message part can be 10 ms or 20 ms.


Its length is set as Transmission Time Interval (TTI) value by the higher layers.
UL, we apply code multiplexing.
L1 Control data are transmitted with SF 256, while message data can be transmitted with SF 256,
128, 64 or 32.
The message data contains the information, given by the RACH.
The control data contains 8 known pilot bits / slot. 15 different pilot bit sequences exist they are
associated with the slot, where the transmission takes place within the 10 ms message frame. 2 bits in
the control data carry TFCI bits / slot.
Which spreading code is allocated to the message part?
The message parts channelisation code is determined from the signature, which was used by the UE
in the preamble.
16 different signatures exist, and each can be correlated to a channelisation code in the
channelisation code tree with spreading factor 16.
The channelisation codes are calculated like this:

Each signature has a number k, with 0 k 15.

For the control data, the channelisation code CCH,256,n is used, with n = 16*k + 15.

For the message data, the channelisation code CCH,SF,m is used, with m = SF*k/16.

The scrambling code is the same, which was used for the PRACH preamble.

66

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

66

The Physical layer Rel. 99

PRACH Message Part


10 ms Frame
Slot 1

Slot 0

Slot 2

8 Pilot bits (sequence depends on slot number)

L1 control data

2 TFCI bits

data

RACH data

SF = 256
channelisation code:
C CH,256,16*k+15, with
k = signature number
67

Slot 14

Nokia Siemens Networks

SF = 256, 128, 64, or 32


channelisation code:
C CH,SF,SF*k/16, with
k = signature number
Scrambling code =
PRACH preamble scrambling code

RN31552EN20GLA0

RN31552EN20GLA0

67

The Physical layer Rel. 99

PRACH Power Setting


When it comes to the random access, two questions have to be asked:
What kind of output power does the UE select for the first preamble?
And how does the output power change with the subsequent preambles and the message part?
Open Loop Power Control
The output power for the first PRACH preamble is based in parts on broadcasted parameters (SIB6, if
missing, from SIB5; and SIB7).
The UE acquires the Node Bs Primary CPICH TX Power, a Constant Value, and the UL
Interference level.
The UE also determines the received CPICH RSCP (variable CPICH_RSCP).
Then, it calculates the power for the first preamble:

Preamble_Initial_Power = Primary CPICH TX power CPICH_RSCP + UL interference


+ Required received C/I

The Required received C/I is an UTRAN parameter (NSN: PRACHRequiredReceivedCI;


range: -35 ... -10 dB, step 1 dB default: -25dB).

The UL Interference is measured by the Node B and broadcasted via SIB 7 on P-CCPCH
to the UEs.
The power ramp steps from one preamble to the next can be set between 1 and 8 dB (step size 1dB).
The power offset between the last PRACH and the PRACH control message can be set between 5
and 10 dB (step size 1dB).
The gain factor c is used for the PRACH control part.

68

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

68

The Physical layer Rel. 99

PRACH Power Setting

Preamble_Initial_Power =
Primary CPICH TX power
CPICH_RSCP
+ UL interference
+ Required received C/I

PRACHRequiredReceivedCI
WCEL: -35..-10; 1; -25 dB

PowerOffset
LastPreamble
PRACHmessage
WCEL:
-5..10; 1; 2 dB

Downlink / BS
UEtxPowerMaxPRACH
WCEL: -50..33; 1; 21 dBm

Uplink / UE
Preamble 1

PowerRampStep
PRACHpreamble
WCEL: 1..8; 1; 2 dB

.
Preamble n

PRACH_preamble_retrans:
The maximum number of preambles
allowed in 1 preamble ramping cycle

Message part
PRACH_preamble_retrans
WCEL: 1..64; 1; 8

RACH_tx_Max: # of preamble power


ramping cycles that can be done
before RACH transmission failure is
reported,
69

Nokia Siemens Networks

RACH_tx_Max
WCEL: 1..32; 1; 8
(Range, Steps; Default)

RN31552EN20GLA0

RN31552EN20GLA0

69

The Physical layer Rel. 99

Acquisition Indication Channel (AICH)


The AICH is used to indicate to UEs, that their PRACH preamble was received, and that the Node B is
expecting to receive the PRACH message part next.
The AICH returns an indicator of signature s, which was used in the PRACH preamble.
Spreading factor is fixed to 256 for the AICH.
The AICH is transmitted via 15 access slots, each lasting 5120 chips.
Consequently, the AICH access slots are distributed over two consecutive 10 ms frames.
Similar to the PRACH preamble, only 4096 chips are used to transmit the Acquisition Indicator part.
32 real value symbols are transmitted.
Each real value is calculated by a sum of AI s b s,j.
AI is an acquisition indicator for signature s.
If signature s is positively confirmed, Ai s is set to +1; a negative confirmation results in 1; if
signature s is not part of the active signature set, then Ai s is set to 0. b s,j stands for signature
pattern j, with j = 0..31.
If more than one PRACH preamble signatures within one PRACH access slot is detected
correctly, the Node B sends the AIs of all the detected signatures simultaneously in the 1 st or 2 nd
AICH access slot after the PRACH access slot.
If the number of correctly detected signatures is higher than the Node B's capability to
simultaneously decode the PRACH message parts, a negative AI s is used for generating the AIs
for those PRACH messages, which can not be decoded within the default message part
transmission timing.
A negative AI indicates to the MS that it shall exit the random access procedure.
The Node B 's capability to decode the PRACH message parts is determined in the RNC and
transmitted to the Node B.
70

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

70

The Physical layer Rel. 99

Acquisition Indication Channel (AICH)


20 ms Frame
Access Slot 0

Access Slot 1

Access Slot 2

a0 a1 a2

Access Slot 14

a29 a30 a31

AICH signature pattern (fixed)


15

a j = AI s b s, j
s =0

PtxAICH
-22..5; 1; -8 dB
(Range; Step; Default)

71

Nokia Siemens Networks

Acquisition Indicator
+1 if signature s is positively confirmed
-1 if signature s is negatively confirmed
0 if signature s is not included in the
set of available signatures

RN31552EN20GLA0

RN31552EN20GLA0

71

The Physical layer Rel. 99

Summary of RACH procedure

(Adopted from TS 25.214)

1- Decode from BCCH

Available RACH spreading factors


RACH scrambling code number
UE Access Service Class (ASC) info
Signatures and sub-channels for each ASC
Power step, RACH C/I requirement = Constant, BS interference level

2 Calculate initial preamble power


3 Calculate available access slots in the next full access slot set and select randomly one of those
4 Select randomly one of the available signatures
5 Transmit preamble in the selected access slot with selected signature
6 Monitor AICH
IF no AICH
Increase the preamble power
Select next available access slot & Go to 3

IF negative AICH or max. number of preambles exceeded


Exit RACH procedure

IF positive AICH
Transmit RACH message with same scrambling code and channelisation code related to signature

72

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

72

The Physical layer Rel. 99

The Physical Layer Rel. 99


Part I: Channel Mapping
Part II: Transport Channel Formats
Part III: Cell Synchronisation
Part IV: Common Control Physical Channels
Part V: Physical Random Access
Part VI: Dedicated Physical Channel - Downlink
Part VII: Dedicated Physical Channel - Uplink

73

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

73

The Physical layer Rel. 99

Downlink Dedicated Physical Channel (DPCH)


The DL DPCH is used to transmit the DCH data.
Control information and user data are time multiplexed.
The control data is associated with the Dedicated Physical Control Channel (DPCCH), while the user
data is associated with the Dedicated Physical Data Channel (DPDCH).
The transmission is organised in 10 ms radio frames, which are divided into 15 timeslots.
The timeslot length is 2560 chips. Within each timeslot, following fields can be found:

Data field 1 and data field 2, which carry DPDCH information

Transmission Power Control (TPC) bit field

Transport Format Combination Indicator (TFCI) field, which is optional

Pilot bits
The exact length of the fields depends on the slot format, which is determined by higher layers.
The TFCI is optional, because it is not required for services with fixed data rates.
Slot format are also defined for the compressed mode; hereby different slot formats are in used, when
compression is achieved by a changed spreading factor or a changed puncturing scheme.
The pilot sequence is used for channel estimation as well as for the SIR ratio determination within the
inner loop power control.

The number of the pilot bits can be 2, 4, 8 and 16 it is adjusted with the spreading factor.

A similar adjustment is done for the TPC value; its bit numbers range between 2, 4 and 8.
The spreading factor for a DPCH can range between 4 and 512. The spreading factor can be changed
every TTI period.
Superframes last 720 ms and were introduced for GSM-UMTS handover support.
74

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

74

The Physical layer Rel. 99

Downlink Dedicated Physical Channel (DPCH)


Superframe = 720 ms
Radio Frame
0

Radio Frame
1

Radio Frame
2

Radio Frame
71

10 ms Frame
Slot 0

Slot 1

Data 1 bits

DPDCH

Slot 2

TPC
bits

Slot 14

TFCI
bits

Data 2 bits

Pilot bits

DPDCH

DPCCH

(optional)

DPCCH

17 different slot formats


Compressed mode slot
format for changed SF &
changed puncturing
75

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

75

The Physical layer Rel. 99

Power Offsets for the DPCH


Power offsets for the optional TFCI, TPC and pilot bits have to be specified during the radio link setup.
This is done with the NBAP message RADIO LINK SETUP REQUEST message, where following
parameters are set:

76

PO1: defines the power offset for the TFCI bits; it ranges between 0 and 6 dB with a 0.25
step size.
PO2: defines the power offset for the TPC bits; it ranges between 0 and 6 dB with a 0.25
step size.
PO3: defines the power offset for the pilot bits; it ranges between 0 and 6 dB with a 0.25
step size.
In the same message, the TFCS, DL DPCH slot format, multiplexing position, FDD TPC DL
step size increase, etc. are defined.

The FDD TPC DL step size is used for the DL inner loop power control.

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

76

The Physical layer Rel. 99

Power Offsets for the DPCH

Power offsets
TFCS
DL DPCH slot format
FDD DL TPC step
size
...

NBAP: RADIO LINK SETUP REQUEST

DCH Data Frame

Node B

Iub

Uu

RNC

P0x: 0..6 dB
step size: 0.25 dB

PO2
Data 1 bits
77

Nokia Siemens Networks

UE

TPC
bits

TFCI
bits
(optional)

PO3

PO1

Pilot bits

Data 2 bits

RN31552EN20GLA0

RN31552EN20GLA0

77

The Physical layer Rel. 99

DL Inner Loop Power Control


Inner loop power control is also often called (fast) closed loop power control.
It takes place between the UE and the Node B.
We talk about UL inner loop power control, when the Node B returns immediately after the reception
of a UEs signal a power control command to the UE. By doing so, the UEs SIR ratio is kept at a
certain level (the details will be discussed later on in the course).
DL inner loop power control control is more complex. When the UE receives the transmission of the
Node B, the UE returns immediately a transmission power control command to the Node B, telling the
Node B either to increase or decrease its output power for the UEs DPCH.
The Node Bs transmission power can be changed by 0.5, 1, 1.5 or 2 dB. 1 dB must be supported by
the equipment. If other step sizes are supported or selected, depends on manufacturer or operator.
The transmission output power for a DPCH has to be balanced for the PICH, which adds to the power
step size.
There are 2 DL inner loop power control modes:

DPC_MODE = 0: Each timeslot, a unique TPC command is send UL.

DPC_MODE = 1: 3 consecutive timeslots, the same TPC command is transmitted.


One reason for the UE to request higher output power is the case that the QoS target is not met.

It requests the Node B to transmit with a higher output power, hoping to increase the quality
of the connection due to an increased SIR at the UEs receiver.

But this also increases the interference level for other phones in the cell and neighbouring
cells.
The operator can decide, whether to set the parameter Limited Power Increase Used.

If used, the operator can limit the output power raise within a time period.
78

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

78

The Physical layer Rel. 99

DL Inner Loop Power Control

TPC

two modes

cell

DPC_MODE = 0

DPC_MODE = 1

unique TPC command


per TS

same TPC over 3 TS,


then new command

TPCest per
1 TS / 3 TS

79

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

79

The Physical layer Rel. 99

DL Inner Loop PC: UTRAN behaviour


UE

WCDMA BTS
DL DPCCH + DPDCHs

Receiving the TPC commands BS adjusts the DL


DPCCH/DPDCH power
UTRAN shall estimate the transmitted TPC command
TPCest to be 0 or 1; it shall update the power every slot.

Measure received SIR on DL DPCCH

Compare measured SIR with SIR target


value received from DL outer loop PC

After estimating the k:th TPC command, UTRAN


shall adjust the current DL power P(k-1) [dB] to a
new power P(k) [dB]:

P(k) = P(k - 1) + PTPC(k)


Measured SIR < SIR target --> TPC command is "1"
Measured SIR => SIR target --> TPC command is "0"

where PTPC(k) is the k:th power adjustment due to


the inner loop power control

Send TPC command on UL DPCCH

BS sets the power on DL DPCCH and


DL DPDCH following way:
TPC command = "1" --> increase power by 1 dB
TPC command = "0" --> decrease power by 1 dB

Changed power on DL DPCCH + DPDCHs

DownlinkInnerLoop
PCStepSize
RNC: 0.5..2; 0.5; 1 dB
(Range, Steps; Default)

DownlinkInnerLoopPCStepSize
80

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

80

The Physical layer Rel. 99

Timing Relationship between Physical Channels


The P-CCPCH is the timing reference for all physical channels.
As can be seen in the figure on the right hand side, following timing relationships exist:

The SCH, CPICH, P-CCPCH and DSCH have an identical timing.

S-CCPCHs can be transmitted with a timing offset S-CCPCH,n. (n stands for the nth SCCPCH.)

The timing offset may be different for each S-CCPCH, but it is always a multiple of 256 chips,
i.e. S-CCPCH,n = Tn * 256 chips, with Tn {0,..,149}.

We have already seen, that some S-CCPCHs transmit paging information.

The associated PICH frame ends PICH = 7680 chips before the associated S-CCPCH frame.
DPCHs are also transmitted with a timing offset, which may be different for different DPCHs.

The timing offset DPCH,k is similar to the S-CCPCH a multiple of 256, i.e.
DPCH,k = Tk * 256 chips, with Tk {0,..,149}.

The timing of a DSCH, which is allociated with a DPCH, is explained later on in the course
documentation.
AICH access slots for the RACH and CPCH also require a time organisation.

As we have seen e.g. with the RACH, an access slot combines two timeslots.

How can the timing to the P-CCPCH be identified?

The P-CCPCH transmits the cell system frame number (SFN), which increases by one with
each radio frame.

The AICH access slot number 0 starts simultaneously with the P-CCPCH frame, whose SFN
modulo 2 is zero.
81

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

81

The Physical layer Rel. 99

Timing Relationship between Physical Channels


SFN mod 2 = 0

SFN mod 2 = 1

P-CCPCH

SCH
AICH access
slots

10

11

12

13

14

0..38144
(step size 256)
nth S-CCPCH

kth S-DPCH

S-CCPCH,n

DPCH,k

0..38144
(step size 256)
82

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

82

The Physical layer Rel. 99

Radio Interface Synchronisation


A major problem arises, when the UE is connected to several cells simultaneously.
The active set cells must transmit the DL DPCH in a way that their arrival time is within a receive
window at the UE.
DLnom is the nominal receive time of a radio frame with a specific CFN at the UE.
T0 = 4 TS later, the UE starts to transmit the a radio frame with the same CFN.
T0 is always calculated relative to the UE transmission start point.

Of course, due to multipath propagation and handover situations, the reception of the
beginning of a DL radio frame is often not exactly at To times before the UE starts to send.
When the UE is in a soft handover, and moving from one cell to another, the radio frames arriving
from one cell may arrive later and later, while the radio frames of another cell arrive earlier. I.e., the
reception from the two neighbouring cells drifts apart.
The picture on the right hand side is only valid, if the UE is in the macro-diversity state. In this case,
the parameter Tm is the time difference between the nominal DL received signal DLnom and the
appearance of the first P-CCPCH of the neighbouring cell.
The serving RNC determines the required offset between P-CCPCH of the neighbouring cell and the
DL DPCH.

This information is sent as Frame Offset and Chip Offset to the target Node B.

The target Node B can change the transmission of the DL DPCH only with a step size of 256
chips, in order to be synchronised to the SCH and P-CCPCH structure.

The S-RNC informs also the UE about the Frame Offset.

83

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

83

The Physical layer Rel. 99

Radio Interface Synchronisation


Tm =
timing difference
range: 0..38399
Res.: 1 chip

(e.g DLn
. C om
FN
=

Relative timing
between DL DPCH
and P-CCPCH
range: 0..38144
res.: 256 chips

H2
C P C 2555)
P-C
=
N 2 ipath
. SF
lt
(e.g iest mu
ear l

Offset
between DL DPCH
and P-CCPCH
range: 0..38399
res.: 1 chip

1 2)

T0 =
1024
chips
C H 2)
DP
1
UL FN =
C
.
(e . g

cell1

(Frame Offset, Chip Offset)

UE

cell2
= target
cell for HO

(Frame Offset)
84

Nokia Siemens Networks

SRNC

RN31552EN20GLA0

RN31552EN20GLA0

(TM)

84

The Physical layer Rel. 99

The Physical Layer Rel. 99


Part I: Channel Mapping
Part II: Transport Channel Formats
Part III: Cell Synchronisation
Part IV: Common Control Physical Channels
Part V: Physical Random Access
Part VI: Dedicated Physical Channel - Downlink
Part VII: Dedicated Physical Channel - Uplink

85

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

85

The Physical layer Rel. 99

Uplink Dedicated Physical Channels


The UL dedicated physical channel transmission, we identify two types of physical channels:
Dedicated Physical Control Channel (DPCCH),

Which is always transmitted with SF 256.

Following fields are defined on the DPCCH:

pilot bits for channel estimation. Their number can be 3, 4, 5, 6, 7 or 8.

Transmitter Power Control (TPC), with either one or two bits

Transport Format Combination Indicator (TFCI), which is optional, and a

Feedback Indicator (FBI). Bits can be set for the closed loop mode transmit diversity
and site selection diversity transmission (SSDT)

6 different slot formats were specified for the DPCCH. Variations exist for the compressed
mode.
Dedicated Physical Data Channel (DPDCH),

Which is used for user data transfer.

Its SF ranges between 4 and 256.

7 different slot formats are defined, which are set by the higher layers.
The DPCCH and DPDCH are combined by I/Q code multiplexing with each multiframe.
Multicode usage is possible. If applied, additional DPDCH are added to the UL transmission, but no
additional DPCCHs! The maximum number of DPDCH is 6.
The transmission itself is organised in 10 ms radio frames, which are divided into 15 timeslots. The
timeslot length is 2560 chips.

86

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

86

The Physical layer Rel. 99

Uplink Dedicated Physical Channels


Superframe = 720 ms
Radio Frame
0

Radio Frame
1

Radio Frame
2

Radio Frame
71

10 ms Frame
Slot 0

Slot 1

Slot 2

DPDCH

Data 1 bits

SF = 256 - 4

DPCCH

Pilot bits

SF 256
6 different slot formats
Compressed mode slot
format for changed SF &
changed puncturing
7 different
slot formats
87

Nokia Siemens Networks

Slot 14

TFCI bits

FBI bits

(optional)

(optional)

TPC
bits

Feedback Indicator for


Closed loop mode transmit diversity, &
Site selection diversity transmission (SSDT)

RN31552EN20GLA0

RN31552EN20GLA0

87

The Physical layer Rel. 99

Discontinuous Transmission and Power Offsets


Discontinuous transmission (DTX) is supported for the DCH both UL and DL.
If DTX is applied in the DL as it is done with speech then 3000 bursts are generated in one
second. (1500 times the pilot sequence, 1500 times the TPC bits)
This causes two problems:
Inter-frequency interference, caused by the burst generation.
At the Node B, the problem can be overcome with exquisite filter equipment. This filter
equipment is expensive and heavy. Therefore it cannot be applied in the UE.
The UEs solution is I/Q code multiplexing, with a continuous transmission for the DPCCH.
DPDCH changes can still occur, but they are limited to the TTI period. The minimum TTI
period is 10 ms. The same effects can be observed, then the DPDCH data rate and with it its
output power is changing.
3000 bursts causes audible interference with other equipment just see for example GSM.
By reducing the changes to the TTI period, the audible interference is reduced, too.
Determination of the power difference between the DPCCH and DPDCH
I/Q code multiplexing is done in the UL, i.e. the DPCCH and DPDCH are transmitted with different
codes (and possible with different spreading factors). Gain factors are specified: c is the gain
factor for the DPCCH, while d is the gain factor for the DPDCH. The gain factors may vary for
each TFC. There are two ways, how the UE may learn about the gain factors:
The gain factors are signalled for each TFC. If so, the nominal power relation Aj between
the DPDCH and DPCCH is d/c.
The gain factor is calculated based on reference TFCs. (The details for gain factor calculation
based on reference TFCs are not discussed in this course.)
88

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

88

The Physical layer Rel. 99

Discontinuous Transmission and Power Offsets

DPDCH
DPDCH

DPDCH

DPCCH

DPCCH

TTI

DPCCH

TTI

TTI

UL DPDCH/DPCH Power Difference:


two methods to determine the gain factors:
signalled for each TFCs
calculation based on reference TFCs
DPDCH
Nominal Power Relation

89

Nokia Siemens Networks

Aj =

d
c

DPCCH

RN31552EN20GLA0

RN31552EN20GLA0

89

The Physical layer Rel. 99

UL Inner Loop Power Control


The subscriber is mobile. The distance of the UE from a Node B is changing over time.
With growing distance and a fixed output power at the UE, the received signals at the Node B
become weaker.
UE output power adjustment is required.
But the UEs received signal strength can change fast Rayleigh fading in one phenomena,
which causes this event.
As a consequence, a fast UL power control is required.
This power control is called UL inner loop power control, though many experts also call it (fast)
closed loop power control.
At each active set cell, a target SIR (SIRtarget) is set for each UE. The active set cells estimate SIRest
on the UEs receiving UL DPCH. Each active set cell determines the TPC value. If the estimated SIR
is larger than the UEs target SIR, then the determined TPC value is 0. Otherwise it is 1. These
values are determined on timeslot basis and returned on timeslot basis.
The UE has to determine the power control command (TPC_cmd). The higher layer control
protocol RRC is used to inform the UE, which power control algorithm to apply. This informs the UE
also how to generate a power control command from the incoming TPC-values.
There are power control algorithm 1 (PCA1) and 2 (PCA2), which are described in the figure
following the next one. Given the power control algorithm and the TPC-values, the UE determines,
how to modify the transmit power for the DPCCH: DPCCH = TPC TPC_cmd. TPC stands for the
transmission power step size.

(continued on the next text slide)


90

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

90

The Physical layer Rel. 99

UL Inner Loop Power Control


SIRest

SIRtarget

time
T TCP
TC TCP CP = = 0
P= =1 0
1

TPC
TPC_cmd

in FDD mode:
1500 times per second

91

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

91

The Physical layer Rel. 99

UL Inner Loop Power Control


Power Control Algorithm 1

is applied in medium speed environments.

Here, the UE is commanded to modify its transmit power every timeslot.

If the received TPC value is 1, the UE increases the transmission output at the DPCCH by
DPCCH, otherwise it decreases it by DPCCH.

The DPCCH is either 1 or 2 dB, as set by the higher layer protocols.

TPC values from the same radio link set represent one TLC_cmd.

TPC_cmds from different radio link sets have to be weighted, if there is no reliable
interpretation.
Power Control Algorithm 2

was specified to allow smaller step sizes in the power control in comparison to PCA1.

This is necessary in very low and high speed environments.

In these environments, PCA1 may result in oscillating around the target SIR.

PCA2 changes only with every 5th timeslot, i.e. the TPC_cmd is set to 0 the first 4 timeslots.
In timeslot 5, the TPC_cmd is 1, 0, or 1.

For each radio set, the TPC_cmd is temporarily determined. This can be seen in the next
figure.

The temporary transmission power commands (TPC_temp) are combined as can be seen in
the figure after the next one. Here you can see, how the final TPC_cmd is determined.
NSN supports only PCA 1.
92

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

92

The Physical layer Rel. 99

UL Inner Loop Power Control


algorithms for processing power
control commands TPC_cmd

NSN supports only


PCA 1 with step size 1 dB

PCA1

PCA2

TPC_cmd for each TS


TPC_cmd values: +1, -1
step size TPC: 1dB or 2dB

TPC_cmd for 5th TS


TPC_cmd values: +1, 0, -1
step size TPC: 1dB

UL DPCCH power adjustment: DPCCH = TPC TPC_cmd


PCA2
0

93

Nokia Siemens Networks

PCA1
Rayleigh fading can be compensated

PCA2
80

km/h

RN31552EN20GLA0

RN31552EN20GLA0

93

The Physical layer Rel. 99

Power Control Algorithm 1


Example: reliable transmission
Cell 3
TPC3 = 1

TPC1 = 1

Cell 1

TPC_cmd = -1 (Down)

TPC3 = 0

Cell 2

NSN: only PCA 1 is supported.


94

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

94

The Physical layer Rel. 99

Power Control Algorithm 2


TPC_temp

TPC = 1
TPC = 1
TPC = 1
TPC = 1
TPC = 1

0
0
0
0
1

TPC = 1
TPC = 0
TPC = 1
TPC = 0
TPC = 1
TPC = 0

0
0
0
0
0
0

TPC = 0
TPC = 0
TPC = 0
TPC = 0

0
0
0
-1

NSN: PCA 2 is not supported.


95

Nokia Siemens Networks

if all TPC-values = 1
TPC_temp = +1
if all TPC-values = 0
TPC_temp = -1
otherwise
TPC_temp = 0

RN31552EN20GLA0

RN31552EN20GLA0

95

The Physical layer Rel. 99

Initial UL DCH Transmission


UTRAN shall start the transmission of the DL DPCCH and may start the transmission of DPDCH if any
data is to be transmitted.
The UE UL DPCCH transmission shall start

When higher layers consider the DL physical channel established, if no activation time for UL
DPCCH has been signalled to UE

If an activation time has been given, UL DPCCH transmission shall not start before the DL
physical channel has been established and the activation time has been reached.
When we look to the PRACH, we can see, that preambles were used to avoid UEs to access UTRAN
with a too high initial transmission power.
The same principle is applied for the DPCH.
The UE transmits between 0 to 7 radio frames only the DPCCH UL, before the DPDCH is code
multiplexed.
The number of radio frames is set by the higher layers (RRC resp. the operator).
Also for this period of time, only DPCCH can be found in the DL.
The UE can be also informed about a delay regarding RRC signalling this is called SRB delay,
which can also last 0 to 7 radio frames. The SRB delay follows after the DPCCH preamble.
How to set the transmission power of the first UL DPCCH preamble?

Its power level is

96

DPCCH_Initial_power = CPICH_RSCP + DPCCH_Power_offset

The DPCCH Power Offset is retrieved from RRC messages. Its value ranges between 164
and 6 dB (step size 2 dB). CPICH_RSCP is the received signal code power on the PCPICH, measured by the UE.

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

96

The Physical layer Rel. 99

Initial UL DCH Transmission


DPCCH only

DPCCH & DPDCH

reception
at UE

transmission
at UE

PCPreamble

0 to 7 frames for
power control preamble

RNC: 0..7; 1; 0

DL Synch &
Activation time

0 to 7 frames of
SRB delay

DPCCH only

SRBDelay
RNC: 0..7; 1; 7

DPCCH & DPDCH

DPCCH_Initial_power = CPICH_RSCP + DPCCH_Power_offset


97

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

97

The Physical layer Rel. 99

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

TS
TS
TS
TS
TS
TS
TS
TS
TS
TS
TS
TS

25.211
25.212
25.213
25.214
25.215
25.301
25.302
25.306
25.321
25.331
25.402
25.433

V6, Physical channels & mapping of transport channels onto physical channels
V6, Multiplexing and channel coding (FDD)
V6, Spreading and modulation (FDD)
V6, Physical layer procedures (FDD)
V6, Physical layer; Measurements (FDD)
V6, Radio interface protocol architecture
V6, Services provided by the physical layer
V5 V8: UE Radio Access capabilities
V6, Medium Access Control (MAC) protocol specification
V6, Radio Resource Control (RRC) protocol specification
V6, Synchronization in UTRAN Stage 2
V6, UTRAN Iub interface Node B Application Part (NBAP) signalling

NSN WCDMA Product documentation

98

Nokia Siemens Networks

RN31552EN20GLA0

RN31552EN20GLA0

98

Das könnte Ihnen auch gefallen