UMTS Training Course Overview

UMTSTrainingCourse UMTS Training Course
Prepared & presented by

G b i l Ab h Gabriel Abraham
11th of February 2004
Gabriel.Abraham.extern@icn.siemens.com
l 4989 2238222 Tel : +49 89 722 38222
AGENDA
Agenda - Day 1
Introduction
UTRAN Protocol Architecture
UTRAN Channel Model
Hierarchical Cell Structure (HCS) Hierarchical Cell Structure (HCS)
UMTS Signalling Model
Call Flow
Z i i t Ch l Zooming in to Channels
Logical Channels Mapped in to Transport Channels
Transport Channels Mapped in to Physical Channels
?
Agenda - Day 2
Physical Channel : Key concept in the UMTS y y p
Radio channel configuration
Cell search, selection and reselection
Hierarchical Cell Structure (HCS) Hierarchical Cell Structure (HCS)
Handover
Power control
R ll ti Resource allocation
Congestion control
Radio bearer control
Restriction control
Agenda - Day 3
Messages Flow Analysis g y
Siemens UMTS System
RNC Model and Capacity
IuB Overbooking IuB Overbooking
Connection Admission Control
AAL2 Ownership-CID Allocation
AAL2 P th S l ti d L d B l i AAL2 Path Selection and Load Balancing
VP Shaping
Circuit Emulation Services
?
PART 1
Introduction
Objective of Course is to enable testers to
Introduction
intelligently use Siemens UMTS UTRAN
and associated simulators and perform L&S p
test cases
The intention is to provide some insight into
the theory of operation, as well as hands on y p ,
experience.
I first present set of concepts to provide
intellectual context before detailed presentation e ec ua co e beo edea edp ese a o
Instructor and Background
Gabriel Abraham
Member of L&S team Member of L&S team.
StoriesandExcuses Stories and Excuses
I am not professional course makers/givers
I squeezed this work in during a very busy time for our
L & S team.
You are the first to get this course.
.So please be kind.and understanding.I am
all that is at the moment
Lif Hi f C ll Life History of a Call
This is a REVIEW.I was told that
different studentshavedifferent different students have different
backgrounds.sorry
Butit is good to think about the various
steps a mobile has to go through before
discussing lower level details. g
Fast Facts Fast Facts
ThemobilesandtheBaseStationtalkviachannels we The mobiles and the Base Station talk via channels .we
will be discussing them at great length, literately.
Thesechannelsarecommon anddedicated---
Each step makes use of the right kind or combination of
channelsfor efficient useof theradioresources
These channels are common and dedicated
channels for efficient use of the radio resources
1 . 1 M o b i l e O r i g i n a t e d V o i c e C a l l
M obi l e B T S M SC R NC
R R C _ C O N N E C T I O N _ R E Q U E ST ( R A C H )
Data transport bearer sync
NB A P_ R A DI O_ L I N K _
SET U P_ R EQU E ST
SET U P_ R ESPONSE
A L C A P Data T ransport B earer
Setup
R R C _ C O N N E C T I O N _ S E T U P ( F A C H )
RRC_ CONNE CT I ON_ SE T U P_
COM PL E T E (DC C H)
M o b il e mo v e s t o
C E L L D C H o r
C E L L F A C H s ta t e
C M SER V I C E REQU E ST (DC CH)
1
RRC_ U E_ C A PA B I L I T Y _ I N FORM A T I ON (DC CH)
5
R R C _ U E _ C A P A B I L IT Y _ I N F O R M A T I O N _ C O N F I R M ( D C C H )
SE T U P (DCC H)
3
CA L L _ PR OC EE DI N G (DCC H)
2
RE C ONFI G PR E PA RE
_ _ Q ( )
CM _ SERV I CE _ A CC E PT (DC CH)
2
B SSM A P_ A SSI GNM E NT _
R E QU E ST
RE C ONFI G R E A DY
A L C A P Data T ransport B earer
Setup
Data transport bearer sync
B SSM A P_ A SSI GNM E NT _
C OM PL E T E
_ _ _
RE C ONFI G C OM M I T
R R C _ R A D I O _ B E A R E R _ S E T U P ( D C C H )
R R C _ R A D I O _ B E A R E R _ SE T U P _ C O M P L E T E ( D C C H )
A L E R T I N G (DCC H)
2,4
2
N otes:
1 T ransferred over RR C as an I N I T I A L DI R E CT T R A NSFE R (E r r o r ! R e f e r e n c e so u r c e n o t f o u n d Secti on 8 1 8) and then over I u
C O N N E C T ( D C C H )
2
C O N N E C T _ A C K N O W L E D G E ( D C C H
3
A ppl y new transport format set Now requi re co-ordinated set
of 3xDC H for A M R and separate DCH (wi th several logi cal
DCC Hs) for R L C.)
M obi le moves to
CE L L DC H state
1 T ransferred over RR C as an I N I T I A L _ DI R E CT _ T R A NSFE R (E r r o r ! R e f e r e n c e so u r c e n o t f o u n d . Secti on 8.1.8) and then over I u
i nterface as a DT A P message. CM servi ce type = M obi le Ori gi nating Call E stabl i shment. E r r o r ! R e f e r e n c e s o u r c e no t f o u n d . Secti on
10.5.3.3.
2 T ransferred over RR C as a DOWN L I N K _ DI R E CT _ T R A NSFE R (E r r o r ! R e f e r e n c e so u r c e n o t f o u n d . Secti on 8.1.9) and then I u i nterface
as a DT A P message.
3 T ransferred over RR C as an U PL I N K _ DI R E CT _ T R A NSFE R (E r r o r ! R e f e r e n c e s o u r c e n o t f o u n d . Secti on 8.1.10) and then I u i nterface as
a DT A P message.
4 A L E RT I N G i s asynchronous and may occur any ti me between C A L L _ PROCE E DI N G and CONNE CT , or potenti ally not at all though that
would be unusual on a voice cal l. RNC should al low for thi s message at any ti me. I t does not need to be state based.
5 R NC h ld ll f hi i I d d b b d T f d RR C
I dU U Pl
UTRAN Protocol Architecture
User
data
User
data
Non Access Stratum
Iu and Uu User Plane
NAS Services
-Transfer of User Data
Radio
Protocol
Radio
Protocol
Iu
Protocol
Iu
Protocol
SAP SAP
Radio
Uu
UTRAN CN UE
Iu
Access Stratum
Iu and Uu Control Plane
CM MM CM MM
NAS Services
CM,MM
GMM,SM
CM,MM
GMM,SM
Non Access Stratum
SAP SAP
- Registration,
- Call Control,
- SMS,
S l t S i
Radio
Protocol
Radio
Protocol
Iu
Protocol
Iu
Protocol
Access Stratum
- Supplementary Services,
- Session Management,
- Logical Link Control
Radio
Uu
UTRAN CN UE
Iu
S
UTRAN Access Model (3G TS 25.301section 5.1)
Non-Access Stratum No ccessS u
GC Nt DC GC Nt DC
Relay
GC Nt DC GC Nt DC
RRC RRC
C/ AC /
bearer
C/ AC /
bearer
Access Stratum
Uu Stratum Iu Stratum
RLC / MAC /PHY RLC / MAC /PHY
UE UTRAN CN
Uu i/f Iu i/f
Protocol stack
RRC
Upper layer
TransmittedbetweenUE andCN
RANAP
SCCP+
RRC
RLC
RRC
RLC
RRC protocol
SCCP+
MTP3b
SSCOP
RLC
MAC
RLC
MAC
SSCOP
AAL5
MAC
AAL2
AAL2
MAC
L1
ATM ATM
L1
ATM
PHY PHY
PHY
UE Node B RNC
UTRAN Channel Model
MM
CC
GMM
SM
MM
CC
GMM
SM
[NAS] Higher Layer
RRC [AS] Higher Layer RRC
MAC
RLC
Transport Channel
Logical Channel
MAC
RLC
PHY Physical Channel PHY
UE
Um i/f
Node B RNC
Iub i/f Iu i/f
CN
WCDMA radio interface protocol
Radio Resource Control(RRC) Network
Layer
L3
Radio Link Control(RLC)
Logical
channel
Data
Link
Layer
Medium Access Control(MAC)
L2
PHY
Transport
channel
Physical
Layer
L1
PHY
Establishment, maintenance and
release of an RRC connection
between the UE and UTRAN,
UMTS - Access Stratum
U Pl E bli h fi i
Gc Nt DC
L3
Control Plane
Signaling
User Plane
Information
Establishment, reconfiguration
and release of Radio Access
Bearers,
Routing of higher layer PDUs,
BCFE
Routing Function Entity (RFE)
PNFE DCFE
RRC PDCP
TR UM
Transfer Mode Entity (TME)
UE measurement reporting and
Outer loop power control,
Initial cell selection and re-
selection in idle mode
AM
RLC
CRLC
Error Control, Segmentation & Re-
assembly, In-sequence delivery of
higher layer PDU, Physical Link
Control, Ciphering.
BMC
Ciphering,
Header
Ciphering,
Error Ctrl
Header
RLC
L2
RLC
Mapping between logical channels
& transport channels, Selection of
appropriate Transport Format for
each Transport Channel depending
oninstantaneoussourcerate
Logical
Channels
CMAC
BCCH
PCCH DCCH CCCH
CTCH DTCH
MAC b MAC d
on instantaneous source rate,
Multiplexing, De-multiplexing
of higher layer PDUs, Dynamic
Transport Channeltype switching.
Transport
Channels
MAC-b
PHY
MACC/sh
MAC-p
BCH PCH CPCH RACH FACH DCH
MAC-d
Error Correction, Measurement
& indication to higher layer,
Multiplexing of transport
channels, De-multiplexing of
codedcompositetransport
AMR
CPHY
Physical Layer
Channel Config
UE Control Cell search, NW sync
Channels
PHY
coded composite transport
channels & mapping of the
channels on physical channels,
Synchronization & Power Ctr
y y
L1 Channel Control
Measurement
PC, DTX, L1 sync
Meas ctr, routing
Radio channel structure
Physical Channel
N d B
T t Ch l
Node B
UE
Transport Channel
Logical Channel
RNC
UMTS Signalling Model (Control Plane)
CC
Layer 3
SM CC SM
MM
Layer 2
RLC
RRC
GMM
RLC
RRC
RANAP RANAP
MM
RANAP
GMM
MAC
Layer 2
RLC
NBAP FP NBAP FP
MAC
RLC RANAP RANAP
M3UA
SCCP
M3UA
SCCP
RANAP
SCCP
Layer 1 AAL5
SAAL
AAL2
PHY AAL5
SAAL
AAL2
PHY
AAL5 AAL5
IP
SCTP MTP
M3UA
AAL5
IP
SCTP
M3UA
AAL5
MTP
e.g. E1,STM
ATM
e.g. E1,STM
ATM
e.g. E1,STM
ATM
e.g. E1,STM
ATM
e.g. E1,STM
ATM
e.g. E1,STM
ATM
UE
Um i/f
Node B RNC PS-CN
Iub i/f Iu i/f
CS-CN
UMTS Signalling Model (ps - User Plane)
A L 3 App.
Layer 2
Layer 3
RLC
PDCP
RLC
PDCP GTP-U
GTP U GTP U GTP U
App.
MAC
Layer 2
RLC
FP
MAC
RLC
FP
UDP/IP
GTP-U
UDP/IP
GTP-U
UDP/IP
GTP-U
UDP/IP
Layer 1
AAL2
PHY PHY
AAL2
AAL5
SAAL
Layer 2
AAL5
SAAL
Layer 2
e.g.
E1, STM
ATM
e.g.
E1, STM
ATM
e.g.
E1, STM
ATM
Layer 1
e.g.
E1, STM
ATM
Layer 1
UE
Um i/f
Node B RNC
Iub i/f Iu i/f
GGSN SGSN
Iu i/f
M bil i P dUP Mobile is Powered UP
Needs to find and lock onto a cell
transmittersynchronize for timing/framing
Needs to download the local system common parameters
which are used to later listen for control/paging/originating
L i U d Location Update
Mobile has to make itself known to
cell/system MSC canthenrespond cell/system. MSC can then respond
properly for incoming callsand could
h di d i have directed paging.
This can be done periodically p y
Has to begin over well known common
h l th t BTSli t t channelthat BTS listens to
M bil S O i i Mobile Starts to Originate
Mobile tells system using common channel that it would
like to make a call. UE to RNC using the Access Stratum.
RNC sets up a dedicated channel between UE and
MSC using the Access Stratum
UE and MSC get connected directly so they can talk to
each other using the Non Access Stratum.
NonAccessStratum Non Access Stratum
Mobile sets up Call with MSC
Si lli d di t d h l Signalling over dedicated channel
Call processing code (NAS) in UE talks
directly with peer in MSC y p
Sends information such as: called party, p y,
type of call desired, etc. over dedicated
channel channel.
MSC does its job
MSC does digit analysis, uses HLR/VLR to screen, etc.
MSC sets up a voice path to destination, including
vocoders as needed, including path out via E1s etc.
MSC then tells Mobile that Call is proceeding but
doesnt cut voice path resources through yet.
If voice path is allocated successfully, MSC tells UE to
alert (ring)
Connection Reached
When all is ready (far end picks up), MSC
sends (again over dedicated channel)
Message to Connect. g
Connect State
In this state a dedicated channel is set up with 4
subchannels for VOICE subchannels, for VOICE
These are DCH1, DCH2, DCH3 and DCH4 , ,
DCH4 carries signalling information g g
Other 3 Carry VOICE (for Data mode only one
Subchannel) Subchannel)
Adaptive Multirate Voice
The 3 voice channels carry compressed voice according to
UMTS standards: AMR
AMR has many different compression rates (numbered 1
to7) to 7)
AMR uses 3 channelsof decreasing importance to voice
understanability Withall 3workingat compressionrate understanability. With all 3 working at compression rate
7, we get excellent voice at effectively 12.2Kbs.
Th 3 h l d d db th TRAU f ti i th The 3 channels are decoded by the TRAU function in the
RNC.
Zooming In: Channels
This set of actions takes place using a variety of tailor
madechannelswhichareadaptedespeciallyfor the made channels which are adapted especially for the
specific use they will be put to.again, to be very efficient
with scarce radio time and channel space. p
UMTS terminology is a bit complex, but makes sense after
youhaveanendtoendfeel (seesomeexamples) you have an end to end feel (see some examples)
Logical Channels; Transport Channels; Physical Channels
These are mapped from top down, and UMTS allows a fair
f fl ibili ill di h i d il amount of flexibilitywe will discuss each case in detail.
Logical Channels/Transport Channels Logical Channels/Transport Channels
i l h l h i db h f f h Logical Channels are characterized by what type of information they
carry--thus a logical differentiation
Transport Channels are characterized by the different ways the Logical
Channels will be transmitted.a physical difference.
Physical Channels are the physical manifestations of the Transport
Channels.
A layered structure is used to conceptualize this.
Logical channels mapped onto transport channels
U/D
Control
Plane
U/D
User
Plane
U
U
NTr=MAC header
Tr=No MAC header
NTr=RLC header
Tr=No RLC header Ack=No RLC header
Uack=RLC header
BCCH CCCH CTCH DCCH
Logical
Channels
DTCH
PCCH
Plane
PCCH
BCCH
DCCH
CCCH
CTCH DTCH
Tr No MAC header
Tr=if no multiplexing
M=NTr if multiplex
Tr=No RLC header Ack=No RLC header
B = Both Ack & Uack
AoU = Ack or Uack
ToN=Tr or NTr
Tr
BCCH CCCH CTCH DCCH
MAC SAPs
DTCH
Tr Tr
PCCH
Tr Uack Tr B B AoU NTr Uack ToN AoU AoU
MAC-c/sh
Add/Read
Deciphering
Channel Switching
Tr NTr Tr NTr NTr NTr NTr NTr Tr
M
Tr
dd/ ead
UE Id
C/T MUX
Scheduling/Priority
MAC-b MAC-p M
MAC-d
UL :TFC Selection
Ciphering
Handling
UL :TF Selection
ASC Selection
TCTF MUX/
Multiplexing
MAC d
Transport
Channels
DCH BCH
PCH
CPCH FACH RACH
RLC Layer Transparent Mode

Radio Interface (Uu)
UE/UTRAN
UTRAN/UE
TM-SAP TM-SAP
Transmitting
TM- RLC
entity
Transmission
buffer
Receiving
TM- RLC
entity
Reassembly
Segmentation
Reception
buffer
CCCH/DCCH/DTCH/SHCCH UE
BCCH/PCCH/DCCH/DTCH UTRAN

CCCH/DCCH/DTCH/SHCCH UTRAN
BCCH/PCCH/DCCH/DTCH UE

RLC Layer Unacknowledged Mode

UM -SAP
UM -SAP
Radi o Interface (Uu)
UE/UTRAN
UTRAN/UE
Transmi tti n
Transmi ssi on
Recei vi ng
Reassembl y
g
UM RL C
enti ty
s ss o
buffer
UM RL C
enti ty
Segmentati on &
Concatenati on
Reassembl y
Remove RL C
header
Recepti on
buffer
Ci pheri ng
Add RL C header
Deci pheri ng
Ci pheri ng
p g
DCCH/DTCH UE
CCCH/SHCCH/DCCH/DTCH/CTCH UTRAN
DCCH/DTCH UTRAN
CCCH/SHCCH/DCCH/DTCH/CTCH UE CCCH/SHCCH/DCCH/DTCH/CTCH UTRAN CCCH/SHCCH/DCCH/DTCH/CTCH UE

U E /U T R A N
RLC Layer Acknowledged Mode
A M - S A P
R L C C ontrol U ni t
A M R L C enti ty
S egmentati on/C oncatenati on
A dd R L C header
P i ggyback ed status
R etransmi ssi on
buf f er &
management
R
e
c
e
i
v
e
a
c
k
n
o
w
R eassembl y
P i ggyback ed status
O pti onal
T ransmi ssi on
M U X
e
d

w
l
e
d
g
e
m
e
n
t
s

A ck nowl edgements
R ecepti on buf f er
R emove R L C header & E x tract
P i ggyback ed i nf ormati on
T ransmi ssi on
buf f er
S et f i el ds i n P D U H eader (e.g. set pol l
bi ts) & pi ggyback ed S T A T U S P D U
A ck nowl edgements
& R etransmi ssi on
management
D eci pheri ng
D emux /R outi ng
R e c e i v i n g s i d e
C i pheri ng (onl y f or A M D P D U )
T r a n s m i t t i n g s i d e
D C C H /
D T C H
*
D C C H /
D T C H
* *
D C C H /
D T C H
* *

D C C H /
D T C H
*
D C C H /
D T C H
* *
D C C H /
D T C H
* *
MAC header structure while logical channels are mapped to transport channels g pp p
BCCH
PCCH
CCCH
Logical
Channels
DCCH DTCH CTCH
No Multiplexing
With Multiplexing
MAC SDU
C/T MAC SDU
MAC SDU MAC SDU MAC SDU TCTF
TCTF MAC SDU
MAC SDU UE-id Type UE-id
C/T UE-id Type UE-id MAC SDU
No Multiplexing
With Multiplexing
MAC SDU TCTF
UE-id Type MAC SDU C/T TCTF UE-id
C/T UE id Type UE id MAC SDU
DCH CPCH BCH
PCH
Transport
Channels
FACH RACH
Start with Transport Channels..UE very aware of these
Broadcast Channel (BCH)--Common channel used to XMIT system
information (downlink from BTS). XMITed all the time. Will contain ( )
many parameters for UE to set into themselves for this cell
Forward Access Channel--(FACH)--common channel used when
UTRAN needs to send signalling to a particular UE, usually in
preparation for setting up a dedicated channel. To carry info to set up
dedicated channel, for example. , p
Paging Channel (PCH)--common channel, similar to FACH, but used
to find/alert a specific UE. downlink
Random Access Channel (RACH)--common channel uplink for UE to
communicate with UTRAN before a dedicated channel is set up. p
Contention based.
Dedicated Channel (DCH)--specific UE to UTRAN communication,
li k dd li k V h df NAS NAS i i uplink and downlink. Very much used for NAS-NAS communication.
Logical
PCCH
BCCH DCCH CCCH DTCH CTCH
MAC header - coding of TCTF field & structure of UE-id, UE id type & C/T
Logical
Channels
TCTF MAC SDU
U-RNTI 32 bits
C-RNTI 16 bits
UE-id Type UE-id C/T C S U
00 U-RNTI
01 C-RNTI
U d ype U d C/
Id of multiple LC instance when
multiple LC are carried on the
same transport channel.
0000 Logical Channel 1 (DCCH)
A flag which provides identification of Logical Channel class on
FACH & RACH
Identifier of UE
Ensure correct
decoding of the
0001 Logical Channel 2 (DTCH)
. ..
1110 Logical Channel 15
g
UE-id field
00 BCCH
01000000 CCCH
10000000 CTCH
11 DCCH or DTCH
00 CCCH
01 DCCH or
DTCH
Transport
Channels
BCH FACH RACH CPCH DCH
PCH
The size of MAC header depends on the type of logical channel, and in some cases none of the parameters in the MAC header are needed.
The MAC SDU depends on the size of the RLC-PDU, which is defined during the setup procedure.
Logical
PCCH
Coding of TCTF field when mapping logical channels on FACH & RACH
Logical
Channels
TCTF MAC SDU
U-RNTI 32 bits
C-RNTI 16 bits
UE-id Type UE-id C/T C S U
00 U-RNTI
01 C-RNTI
U d ype U d C/
Id of multiple LC instance when
multiple LC are carried on the
same transport channel.
A flag which provides identification of Logical Channel class on
FACH & RACH
Identifier of UE
Ensure correct
decoding of the
0001 Logical Channel 2 (DTCH)
. ..
1110 Logical Channel 15
g
UE-id field
00 BCCH
01000000 CCCH
10000000 CTCH
11 DCCH or DTCH
00 CCCH
01 DCCH or
DTCH
Transport
Channels
BCH FACH RACH CPCH DCH
PCH
The size of MAC header depends on the type of logical channel, and in some cases none of the parameters in the MAC header are needed.
The MAC SDU depends on the size of the RLC-PDU, which is defined during the setup procedure.
L i l
Transport channels mapped onto physical channels, seen from the UE side
PCCH
Logical
Channels
MAC-b MAC-p
MAC-c/sh
SAPs
Transport
MAC-d
SAPs
p
Channels
PCH BCH FACH RACH CPCH DCH
SAPs
Physical
Channels
SAPs
P-CCPCH
DPDCH DPCH
SAPs
DPCCH
PRACH PCPCH
1ry CPICH 2ry CPICH
S-CCPCH + PICH
Multiplexed with
DPCCH 1ry CPICH 2ry CPICH
2ry CPICH .
Overview of RRM
Measurement control
Power control Resource
Radio Resource
Management
Power control Resource
allocation
(RRM)
Handover
control
Congestion
control
Radio bearer control
RRM function in UTRAN
R
N
C
Power
control
Handover control Radio Bearer
control
Measurement control
Intrafrequency HO
RRM for SRNC
Interfrequency HO
Intersystem HO
Power
control
Measurement control Congestion
control
RRM for CRNC
Resource allocation
Admission control
Code allocation
RRM for CRNC
SRNC function
RNS
Node
B
CN
RNS
Iu user
data link
B
SRNC
Node
B
Iu signaling link
DRNC function
Iu
interface
Node
B
RNS
SRNC
CN
Node
B
RNS
Iur interface:
User data and
signaling
Node
B
N d DRNC Node
B
DRNC
Radio Bearers
Radio Bearer Control
The Radio Bearer Control function controls the use of resources
of one UE,
If a UE has variable rate services, for example a web browsing
session, then its demand for air capacity changes over time. The
RB Control function tries to optimise the use of radio resources,
by assigning sufficient capacity to the UE when it needs it, and
taking it away when the data rate is low, so that it can be used
f th for other users,
In summary, one can say that the RB Control function adapts the y, y p
bit rate of a UE to the source bit rate and to the current load
conditions in a cell,
This can be done by either changing the bit rate on Dedicated
Transport Channels, or by switching the UE to Common
Channels. While performing bit rate adaptation or Channel p g p
Type Switching, the function must observe the QoS
requirements of the RAB
Overall Algorithm Relations for Radio Bearer Control and Translation
UE is switched to the lowest rate regardless of the current RLC buffer status
SRNC
CRNC
RL
Translates the RAB QoS parameters
into an initial radio configuration
RB
Translation
Admission
Control
Protocol
Functions
RRC Request
RAB Request
RL
Setup/Reconf
Admission
Response
Translation Control Functions
q
Configure
Activate
Congestion
Indication
Radio
Bearer
Congestion
Control
Measurement
Control
Congestion
Indication
Activate
Deactivate
Indication
Control
Control
Traffic Volume
Measurements
- BRA on DTCH
May switch the UE to the PCH states
RLC buffer load UE/RNC> <
- CTS between Common &
Dedicated Channels
- CTS used only for PS
BRAused for both PS and CS simultaneously
May switch the UE to the PCH states
during periods of long inactivity
O&M
upper/lower threshold
- BRA used for both PS and CS simultaneously
because CS Service does not support
common channels
Only applicable if the UE has calls
whose data rate may be changed

Radio Bearer Control Input and Output Model
Radio
UL Traffic Volume
Measurements
DLTrafficVolume
Increase Data Rate
Protocol
Radio
Bearer
Control
DL Traffic Volume
Measurements
IInactivity
Reduce Data Rate
Protocol
Handling
+
API Control

RB
translation
IInactivity
C ti I di ti
CTS Command
Congestion Indication
Summarization of RBC
UE
DCH to
FACH
FACH
to DCH
Channel
Type
Radio
Bearer
Control
Measurement
Control Cell
PCH
URA
PCH
Type
Switching
Traffic Volume
measurement report
High
rate
Bit Rate Adaptation
rate
Low
rate
OM Data base and
parameters
SRNC
rate
Algorithm for transport channel type
switching
Traffic
Upper payload
switching
Traffic
volume
Threshold on
RACH/FACH
UL/DL
Switch to
Switch to
Dedicated
channels
Lower payload
Threshold on DCH
(UL/DL)
Time
Common
channels
Time to trigger
TDCH-FACH
Time to trigger
TFACH-DCH
Cell URA Cell
Cell
Cell change URA
change
Max_C_Crossing
S
t
Cell
PCH
URA
PCH
Cell
FACH
Cell
FACH
Cell
FACH
a
t
e
Timeout TPCH-Idle
Timeout TPCH-Idle
Time to trigger
TFACH-PCH
Data
Data
t
r
a
Cell
FACH
Cell
DCH
Traffic underflow
Cell
FACH
Cell
FACH
a
n
s
i
FACH DCH
FACH FACH
Traffic overflow
i
t
i
o
RRC
setup
RRC
release
RRC
release
Stable
o
n
d
Idle
Mode
Stable
Transient
i
a
g
Idle
r
a
m
Bit Rate Adaptation flow p
DCH
Transition for single PS RAB Transition for PS+CS RAB
DCH HIGH
CS RAB
deleted
DCH HIGH
DCH HIGH
L

a
n
d

L

t
r
a
f
f
i
c

d
e
r
f
l
o
w
r

D
L

f
i
c

l
o
w
i
c

DCH LOW
U
L
D
L
u
n
d
U
L

o
r
t
r
a
f
f
o
v
e
r
f
l
CS RAB
a
n
d

D
L

t
r
a
f
f
u
n
d
e
r
f
l
o
w
a
f
f
i
c

o
v
e
r
w
added
U
L

a
U
L

o
r

D
L

t
r
f
l
o
w
FACH
FACH
Selection of transport format as a function of load. Bit rate allocation in SRNC
based on information from admission control
TF
4
TF max
TF
3
TF
TF
1
TF
2
SRNC: Transport CRNC: Admission
load
4
1. Load Information ()
SRNC: Transport
Channel Type
Switching Control
CRNC: Admission
Control
()
TFi
2. DCH setup request (TFi)
Load
Evaluation
Load
2. DCH setup request (TFi)
Iur
Mapping on Dedicated Channels
All SRBs are mapped onto the same DCH
Signalling
AMR P S CS
RAB
pp
RB 0-3
RB
Logical
Channel
RBs are mapped
onto separate DCH
Channel
DCH
Dedicated
P hyscial
Channel
Upper layer
RAB AMR
L3
Radio protocol configuration with radio bearers
RRC
RB4 RB5
L3
SRB1 SRB2 SRB3 SRB0
PDCP
RB
RLC UM RLC
AM
RLC
AM
RLC
AM
RLC
AM
RLC
TM
L2
RLC
DCCH DCCH DCCH DCCH DTCH DTCH
Logical
channels
MAC
PHY
DCH DCHn
Transport
channels DCHn-1
L1 PHY
(DPCCH, DPDCH)
L1
Mapping for Common Channels
PS
RAB
RB
DCCH
DTCH
CCCH
Logical
Channel
BCCH PCCH
Channel
FACH 2
FACH 1
PCH
Common
Ph i l
S-CCPCH 1
S-CCPCH 2
Physical
Channel
Radio Bearer
UTRAN
UMTS
CN Iu
Node
UMTS
CN
gateway
Radio
bearer
Iu
bearer
Backbone
bearer service
Node gateway
bearer
Radio Access Bearer CN Bearer service
UMTS bearer services
Radio Bearer services in UMR3.0
RAB Traffic Class CS / PS
Max. rate
[kbps]
UL DL UL DL
AMR speech Conversational CS 12.2 12.2
UDI C ti l CS 64 64 UDI Conversational CS 64 64
P k t
Interactive /
PS
64 64
64 128
Packet
Background
PS
64 384
8 8
SignalingRadio Bearer
UL/DL
Maximum
rate(Kbps)
Channel
DL 27.2 DCCH
UL/DL 3.4 DCCH
UL/DL 13 6 DCCH UL/DL 13.6 DCCH
DL 24 PCCH
DL 30.4 CCCH
UL 16.6 CCCH
DL 32.2 BCCH
Multi Call Services
RABs Traffic Class CS / PS
Max. rate [kbps]
1 2
1 2 UL DL UL DL
12.2 12.2 64 64
AMR Packet
Conversational +
I t ti /B k d
CS +PS
12.2 12.2 64 128
12.2 12.2 64 384
Interactive/Background
12.2 12.2 0 0
12.2 12.2 8 8 12.2 12.2 8 8
UDI Packet Conversational CS +PS 64 64 8 8
S i
Packet Packet
Streaming +
Interactive/Background
PS +PS 16 64 8 8
Radio Bearers
RB No. Plane Meaning
SRB0 Control Signalingradio bearer for all messages in RLC-UMmode
SRB1 Control Signalingradio bearer for all messages in RLC-AMmode
SRB2 Control Signaling radio bearer for Direct Transfer message in RLC-AM
mode
SRB3 Control Signaling radio bearer for Direct Transfer message in RLC-AM
mode
RB4~ User Bearer for voice and data services RB4~
RB31
User Bearer for voice and data services
Congestion Control
Node
B
Measurement report
R
N
C
B
A
B
C
D
Traffic control
C
Traffic congestion
DCH <> CCH
Bit rate down
Drop
Function of Congestion Control
CRNC Node B
Admission
Control
Congestion
Control
Common
measurement
initiation request
N
B
A
P
N
B
A
P
RB
Control
Bearer drop
Bit rate adaptation
C
o d
C
p
Switching from
dedicated to common
o
n
g
e
s
t
i
o
n
d
e
c
i
s
i
o
n
C
o
n
g
e
s
t
i
o
n
h
a
n
d
l
i
n
g
Common
measurement report
channel
OM Data base and
parameters
UL: RSSI (dB)
Congestion control
RB reconfiguration
Drop of users
Basic Algorithm of Congestion Control
Congestion
UL: RSSI (dB)
DL: Tx Power (dB)
Congestion
Threshold
UL/DL
Congestion g
Hysteresis
UL/DL
Congestion
l d canceled
Time
Reporting period
Commandformat example:
Example of Congestion Control
Command format example:
cre cell cctl cellid=10 nodebid=0 ul_cngt=10 ul_cngh=4 dl_cngt=19
dl_cngh=1 mmti_rtwbp=600 mmti_tcp=600 k=2 ebd=dis etpchr=ena
-85
-90
T =0 s
k =2
-95
R
S
S
I

[
d
B
]
T =0 s
T =0.6 s
k =3
T =1.2 s
-100
R
S
-105
-110
0 0,2 0,4 0,6 0,8 1
load
CR
N
Measurement Sequence of Congestion Control
CR
N
C
B
NBAP
NBAP
Common Measurement Initiation Request:
Measurement ID, Cell ID, measurement type,
Report characteristic, etc
Common Measurement Initiation Response
Measurement ID, measurement type, measuredvalue
Common Measurement Report ( this case periodic)
Measurement ID, measurement type, measuredvalue
Common Measurement Initiation Failure
Radio Bearer Translation Function
set-up or release RABs or
O&M
Serving UE
p
set up a signalling connection or
increase or decrease the data rate of a PS service
Admission Control
Information:
Maximum allowed rate
SUE
Generate the appropriate
NBAP and RRC protocol
messages and API commands
Radio
Bearer
RRC Connection Setup
RAB Setup
New Configuration and
Admission Request
RAB Release
Traffic Volume
Protocol
Handling
Translation
I d t t
RAB Release
measurement
configuration
AAL2link characteristics
g
+
API Control
Increase data rate
Reduce data rate

Radio Bearer
Control
AAL2 link characteristics
New radio- and
AAL2 configuration
Radio Bearer Mapping Steps
RAB
207
M1
M5
RAB
RB Type RLC/RB Info
RAB
Combination +
UE Capability
Class
UE Supported
Rate
212-
219
208, 210
207,
209
AAL2/5
New MOR
RB Type+Rate
DCH Type
TFS
227,
228 205, 206
M2
DCH
Combination+Rate
220,
221
M3
TFCS
TFCS Type
221
DCH M4
278, 279
Physical Ch Par
220,
221
DCH
Combination+Rate
DPCH Type
202, 203
M4
Physical Channels: A KEY Concept ..
The transport channels are manifested by the proper different physical
channels so that the air characteristics match the needs efficiently.
I l th diff t h i l h l ll WCDMA b t In general the different physical channels are all W-CDMA, but are
separated from each other by 1) frequency band, 2) Channelization
Code, and 3) Scrambling code. In some cases time division is used
too.
Continued...
i h i l h l f h li i d bli A given physical channelfreq., channelization code, scrambling
code, is called a Coded Composite Transport Channel (CCTrCH).
Data is then laid onto this channel in extremely flexible waysunique
to UMTS.
The CCTrCH timing can have different repetition rates (TTIs)10,
20, 40 msec.
In general data is delivered to the MAC layer each TTI, in Transport
Channels. The MAC layer multiplexes these blocks onto the y p
CCTrCH each TTI. For example, you can have DCH1, DCH2, and
DCH3 muxed on every interval. UMTS allows you to change the
layout of theseTransport ChannelseachTTI if youwant, andtheinfo layout of these Transport Channels each TTI if you want, and the info
for demuxing is carried along with the CCTrCH
What happensat CCTrCH? What happens at CCTrCH?
Typical Example yp p
DCH1--39bits DCH1--39bits DCH1--80bits
DCH2--55bits
DCH3--88bits
DCH2--55bits
DCH3--88bits
DCH2--103bits
DCH3--0bits
TTI1
TTI2 TTI3
Note that Transprort Channel Block Size combo
can change every TTI! This is key to UMTS
flexibility!! flexibility!!
ConceptualizationAide Conceptualization Aide
View Transport Block Formats as Structures. Each Structure layout is
a Tranport Format Combination. (TFC) p ( )
Each member of the structure is a Tranport Format (TF)
Struct TFC1 {
TrCH1 39 bits
bi TrCH2 55 bits
TrCH3 88bits
}
Struct TFC2 {
TrCh1 80bits
T Ch2 103bit TrCh2 103bits
TrCh3 0 bits
Every TTI, a different TFC can be sent, with a TFCI
indicator in frame. The defns. Are sent when call is setup
Typical, Classic Use of all this: AMR
During the connected phase of call, the CCTrCh has to carry 4(!)
DCHs. SignallingDCH(for DCCH) and3voicechannelsfor DCH s. Signalling DCH (for DCCH) and 3 voice channels for
Adaptive Multirate Compression.called A, B, C.
Cbit 60
Bbits-103
Cbits-60
DCCH 148bits
Abits-80
DCCH--148 bits
for 12.2 kbps data
NOTE: This example can be applied to AMR speech.
Tab l e 1: Par amet er ex amp l es f o r 12 35 k b p s d at a Tab l e 1: Par amet er ex amp l es f o r 12.35 k b p s d at a
The number of TrChs 3
Transport block size 81, 103, and 60 bits
CRC 12 bits (attached only to TrCh#1)
Coding CC,
coding rate =1/3 for TrCh#1, 2 coding rate 1/3 for TrCh#1, 2
coding rate = 1/2 for TrCh#3
TTI 20 ms

TrCh#1 Transport block
81
TrCh#2
103
TrCh#3
60
CRC attachment
CRC
Tail bit attachment
81
81
Tail
12

103
103
Tail

60
60
Tail
Convolutional
coding R=1/3, 1/2
Rate matching
303
8 93
333
8 103
136
8 60
303+N
RM1

1
st
interleaving
Radio frame
segmentation
303 +N
RM1

333 +N
RM2
136 +N
RM3
136 +N
RM3
333 +N
RM2

segmentation
#1a
NRF1 = (303 +NRM1)/2
N
RF2
= (333+ N
RM2
)/2
N
RF3
= (136+ N
RM3
)/2
#1b #2a #3a #3b #2b
NRF1 NRF1 NRF2 NRF2 NRF3 NRF3
To TrCh Multiplexing
Multiplexing Flow (3G TS 25.212)
TrCH #1 TrCH #n
TrBl Concatenation
CRC Attachment
TrBl Concatenation
CRC Attachment
Channel Coding
1 t I t l i
Radio Frame Equalisation
Channel Coding
1 t I t l i
Radio Frame Equalisation
1st Interleaving
Radio Frame Segmentation
RateMatching
1st Interleaving
Radio Frame Segmentation
RateMatching Rate Matching
TrCh Multiplexing
Rate Matching
Physical Channel Segmentation
2nd Interleaving
Physical Channel Mapping
PhCH #1 PhCH #n
Transport Format (TF) Description on MAC/L1 (3G TS 25.302)
TF
Transport Block Size (MAC PDU) 0 .. 512
dynamic part
Data Rate
Transport Block Set Size (RLC PDU Size)
Transmission Time Interval [TDD] 10, 20, 40, 80 ms
0 .. 4992 bits
Transmission Time Interval
Convolutional,
Turbo, no coding
Channel Coding Type
10, 20, 40, 80 ms
dynamic [TDD]
semi-static part
BER, Delay
Coding Rate [if Convolutional]
Static Rate Matching Parameter 1 .. hiRM
CRC size
Puncturing Limit [FDD-UpLink]
0, 8, 12, 16, 24
Almost There.but have to add
Asmentionedabove theNodeB istransmittinganumber of behind As mentioned above, the NodeB is transmitting a number of behind
the scenes channels that the mobile has to lock onto, and decode to
begin receiving and transmitting. Needs to find Cell Scrambling
C d If hi d d hhh Code. If this doesnt succeeduhhh...
Then the UE has to listen for BCH.
Oncethesetwostepsaredone yougofurther Once these two steps are done, you go further
P.S. RACH Xmission needs a special physical channelit does not
Xmit constantlycontention mode. Lots of other fine points
We are skipping discussion of physical layer.would be good to
know, but lackof timemeansmanyparametershavetobecopied know, but lack of timemeans many parameters have to be copied
or taken on faith.
RecommendedTest Strategy- L1 Recommended Test Strategy - L1
Pre-requisite :
Familiarity with 3GPP 25.211, 25.212, 25.213, 25.214, 25.215, y , , , , ,
25.302, 29.926
1- Learn how to use the test mobile and the UTRAN
Read the user manuals and the product specification
Study the use of different radio and system parameters :
understand why the parameters are set to the value used
understand why different measurement are sent in the order that they
arein are in
understand what is the advantage and disadvantage of those
parameters.
2- Be sure that the Node B under test and the test mobile are
compatible
Is the Node B compliant with the same 3GPP spec version (J une 2000)?
Is the Node B compliant with the same 3GPP Crs after J une 2000 ?
RecommendedTest Strategy- L1 Recommended Test Strategy - L1
3- Test Synchronization
Test mobile need to receive CPICH, PSCH, SSCH from the Node B in
order to synchronize correctly
4- Test BCH transmission
Test mobile needs to receive BCH before it can receive any other channels
because it needs the SFN
5- Test transmission of all other DL transport channels (and p (
implicitly the physical channel which carry them)
DCH, FACH, PCH DCH, FACH, PCH
Check the product spec to make sure the UTRAN & test mobile release
that you are using can cope with the parameter combination you want to
check.
Recommended Test Strategy - L1
6- Test reception of UL transport channels (and implicitly the
physical channel which carries them) p y )
DCH, CPCH
RACH procedure
4- Test transmission of other DL physical channels
PICH AICH
RACH procedure
PICH, AICH
PDSCH, CSICH, CD/CA-ICH, AP-AICH
End of Introduction
Went over Call Flow
Various Transport Channels and their uses
What it takestoset upaUE/NodeB inL1 What it takes to set up a UE/NodeB in L1
mode
Touched L2/L3 Mode
Shouldgivecontext for rest of course Should give context for rest of course.
Measurement Processing Measurement Processing
(RNC - UE Context) (RNC UE Context)
Layer 1 measurement specification
Layer 1
measurement
specification specification
Measurements in the Measurements in the
UE
messages described in
RRC-Protocol
UTRAN
messages described in
NBAP and Frame Protocol
(25.331) (25.433)
Source: 3 GPP 25.215 (Chap. 4)
UE Measurement Abilities (I)
CPICH RSCP
x x x
Common Pilot Channel Received Signal Code Power
The received power on one code measured on the Primary CPICH
PCCPCH RSCP
x x x
x x
Prim. Common Control Phy. Channel Received Signal Code Power
The received power on one code measured on the PCCPCH from a TDD
cell. Measurement on the midamble is assumed.
SIR
Signal to Interference Power:
SIR := (RSCP / ISCP) x (SF / 2)
Measured on DPCCH
x
Measured on DPCCH.
RSCP and ISCP (Interference Signal Code Power) measured on pilot bits.
Source: 3 GPP 25.215 (Chap. 5.1)
Received Signal Code Power (RSCP)
RSCP
P-CPICH
Power of
P-CPICH
Definition Is the receivedpower on one code measuredon P-CPICH
Applicable Idle mode ,connectedmode (intra andinter frequency)
Range Aresolutionof 1dB within the range -115to -25dBm
UE Measurement Abilities (II)
UTRA carrier RSSI
x x x
Received Signal Strength Indicator, the wide-band received power within the
relevant channel bandwidth.
Measurement performed on a UTRAN downlink carrier.
x x x
GSM carrier RSSI
Measurement performed on a GSM BCCH carrier.
CPICH Ec/No
x x
x x x
Received energy per chip divided by the power density in the band.
Ec/No is identical to RSCP/RSSI.
Measurement performed on Primary CPICH.
Transport channel BLER
Estimation of the transport channel Block Error Rate, based on evaluating CRC.
(Con. mode: on any transport ch.; Idle mode: if requested on PCH)
x x x
Ec/No
Ec/No = (RSCP/RSSI)
P-CPICH
Power of
P-CPICH
Definition Is the receivedpower per chip (Ec) dividedby the power Definition Is the received power per chip (Ec) divided by the power
density in the band.
Applicable Idle mode ,connected mode (intra and inter frequency)
Range A resolution of 1dB within the range -24 to 0 dB
UE Measurement Abilities (III)
UE transmitted power
x
Total UE transmitted power on one carrier.
SFN-CFN observed time difference
System Frame Number (DL) - Connection Frame Number (UL) time difference
x x
in chips, measured on P-CCPCH and DPCCH/DPDCH
SFN-SFN observed time
SFN-SFN observed time difference between different cells.
Type 1: measured on P-CCPCH
Type 2: measured on CPICH
UE Rx-Tx time difference
x x
x x x
x
Time difference between the UE uplink DPCCH/DPDCH frame transmission
and the first significant path on the downlink DPCH frame from the measured
radio link. Measured for each cell in the active set.
x
UE Measurement Abilities (IV)
Observed time difference to GSM cell
x x
Time difference between the beginning of a P-CCPCH frame with SFN=0 and
the beginning of a GSM BCCH 51-multiframe.
UE GPS Timing of Cell Frames for LCS
x x
x x
The timing between cell j and GPS Time Of Week.
Summarization
Signal Interference Ratio
Interference Signal Code Power
ReceivedSignal Code Power
ReceivedSignal Strength Indicator
CPICH Ec/No
g
Block Error Rate
Physical Ch. Bit Error Rate
Transport.Ch. Bit Error Rate
UTRAN
Measurement Control message
(measurement ID, object criteria, etc)
Measurement Report message Measurement Report message
(measurement ID, results)
UE
UTRANMeasurementAbilities (I)
RSSI RSSI
Received Signal Strength Indicator, the wide-band received power within the
UTRAN uplink carrier channel bandwidth in an UTRAN access point.
SIR SIR
Signal to Interference Power:
SIR := (RSCP / ISCP) x SF
Measured on DPCCH after RL combination in Node B. easu ed o CC a te co b ato ode
RSCP and ISCP (Interference Signal Code Power) measured on pilot bits.
Transmitted carrier power
Ratio between the total transmitted power and the max. transmission power. p p
In case of Tx diversity the transmitted carrier power for each branch shall be measured.
Transmitted code power
Transmitted power on one channelisation code on one given scrambling code on one p g g
given carrier.
In case of Tx diversity the transmitted carrier power for each branch shall be measured
and summed together
RSSI
Received Signal Strength Indicator (RSSI)
Received
RSSI
Total received
power
Received
signal
strength
power
Definition Is the widebandreceivedpower within the relevant bandwith
Applicable Idle mode, connectedmode (intra and inter frequency)
Range A resolutionof 1dB within the range -94 to -32 dBm
Signal to Interference Ratio (SIR)
SIR = (RSCP/ISCP) x SF
f f
SIR
Received
power
Signal after de-spreading
Interference from
other users, other cells
Frequency
Definition Is the ratio of radio signal power to its interference power in the
channel channel
Range The reporting range for SIR is from -11 to 20 dB, step of 0.5dB.
Ec/No = (RSCP/RSSI)
P-CPICH
Power of
P-CPICH
Definition Is the receivedpower per chip (Ec) dividedby the power Definition Is the received power per chip (Ec) divided by the power
density in the band.
Applicable Idle mode, connected mode (intra and inter frequency)
Range A resolution of 1dB within the range -24 to 0 dB
UTRAN Measurement Abilities (II)
T t h l BER Transport channel BER
Estimation of the average bit error rate (BER) of RL-combined DPDCH data.
Physical channel BER
E ti ti f th bit t (BER) th DPCCH ft RL bi ti i Estimation of the average bit error rate (BER) on the DPCCH after RL combination in
Node B.
Round trip time (RTT = T
RX
- T
TX
)
Diff b t ti f t i i f th b i i f d li k DPCH f t Difference between time of transmission of the beginning of a downlink DPCH frame to
a UE (T
TX
) and the time of reception of the beginning of the corresponding uplink
DPCCH/DPDCH frame from the UE.
UTRAN GPS Ti i f C ll F f LCS UTRAN GPS Timing of Cell Frames for LCS
Timing between cell j and GPS Time Of Week.
Bit Error Rate
Physical / transport channel BER
200
250
100
150
p
o
r
t
e
d

v
a
l
u
e
DPCCH/DPDCH
50
100
R
e
p
0
1 2 5 10 20 50 100
BER [%]
Definition Is the estimated bit error rate on DPCCH (physical BER) and
DPDCH (transport BER) DPDCH (transport BER)
Applicable Connected mode (intra and inter frequency)
Range A resolution 0.008 (log[BER]) within the range 0 to 1
UTRAN Measurement Abilities (III)
PRACH / PCPCH P ti d l PRACH / PCPCH Propagation delay
Defined as one-way propagation delay during either PRACH or PCPCH access.
Acknowledged PRACH preambles
D fi d th t t l b f k l d dPRACH bl f Defined as the total number of acknowledged PRACH preambles per access frame per
PRACH.
Detected PCPCH access preambles
D fi d th t t l b f d t t d bl f th Defined as the total number of detected access preambles per access frame on the
PCPCH belonging to a CPCH set.
Acknowledged PCPCH access preambles
D fi d th t t l b f k l d dPCPCH bl Defined as the total number of acknowledged PCPCH access preambles per access
frame on the PCPCH belonging to a SF. (equivalent to the number of positive
acquisition indicators transmitted for a SF per access frame per AP-AICH)
Measurement Procedure Types (I)
Inter-frequency
Intra-frequency
Inter-frequency
measurements
Inter-system q y
measurements
y
measurements
What should the
Internal
measurements
LCS
measurements
What should the
UE measure ?
Traffic ol me Q alit
easu e e ts easu e e ts
Traffic volume
measurements
Quality
measurements
Cells that the UE is monitoring
Cells, which belong to the:
active set:
User info is sent from all these cells and they are
simultaneously demodulated and coherently combined
FDD th ll i l d i S ft H d FDD: these cells are involved in Soft Handover
TDD: active set always comprises of one cell only (no Soft
HO))
monitored set:
not included in the active set
monitored according to a neighbour list from UTRAN
detected set:
not included in the active set not included in the active set
detected by the UE without receiving a neighbour list from
UTRAN
Intra-freq. meas. of the unlisted set is required only from UEs
in Cell_DCH state
Measurement in the UE
UTRAN UE
MEASUREMENT CONTROL Message
Downlink DCCH using AM RLC
(def in 25 331 Chap 10 2 15) (def. in 25.331, Chap. 10.2.15)
Perform
Measurements
MEASUREMENT REPORT Message
Measurements
Uplink DCCH using AM or UM RLC
(def. in 25.331, Chap. 10.2.17)
Source: 3 GPP 25.331 (Chap. 8.4.1)
MEASUREMENT CONTROL MEASUREMENT CONTROL
Message (I)
Measurement Type
g ( )
yp
One of the 7 types (Intra-freq., Inter-freq. ...)
Measurement Identity Number
Reference number used by UTRAN when modifying or releasing Reference number, used by UTRAN when modifying or releasing
the meas. and by UE in the meas. report
Measurement Command
Setup: setup a new measurement
Modify: modify a previously defined measurement
Release: stop a measurement and clear all info in the UE
Measurement Object
Objects the UE shall measure on and corresponding object information
M t Q tit Measurement Quantity
Quantity the UE shall measure on
MEASUREMENT CONTROL Message (II)
Reporting Quantities
Quantities the UE shall include in addition to the quantities Quantities the UE shall include in addition to the quantities
that are mandatory to report for the specific event
Reporting Criteria
Triggering of the measurement report:
periodical or event triggered
Reporting Mode Reporting Mode
UE shall transmit the meas. Report using acknowledged or
unacknowledged data transfer of RLC
UE performs measurements
In idle mode
UE shall perform meas. according to the MEASUREMENT CONTROL p g
information in System Inf. Block Type 11, transmitted on BCCH
In CELL_FACH, CELL_PCH or URA_PCH state
UE shall performmeas according to the MEASUREMENT CONTROL UE shall perform meas. according to the MEASUREMENT CONTROL
information in System Inf. Block Type 12, transmitted on BCCH.
In CELL_DCH state
UE shall report radio link related meas. to the UTRAN with a
MEASUREMENT REPORT message
Reception of a MEASUREMENT_CONTROL
bytheUE by the UE
Read IE: measurement command
Setup Modify Release
IE: measurement identity number
Terminate the measurement
associated with the IE measurement
identity number.
Retrieve the stored measurement
information.
If any IEs of the control information
Store measurement (IE meas.
identity number) and control
information defined by IEs:
meas. object, meas. quantity,
Clear all stored measurement control
information.
If any IEs of the control information
are present, replace the
corresponding stored information.
meas. object , meas. quantity ,
reporting quantity, meas. reporting
criteria, meas. validity, reporting
mode in Variable:
MEASUREMENT IDENTITY SU _
Beginn measurements Resume measurements Clear stored measurements
Source: 3 GPP 25.331 (Chap. 8.4.1)
MEASUREMENT REPORT Message (I) g ( )
CELL PCH
CELL_FACH CELL_DCH
CELL_PCH
Cell
update
URA_PCH
Reporting criteria are fullfilled ?
Periodical reporting: time elapsed Periodical reporting : time elapsed
event triggered: stored event was triggered
Transmit a
MEASUREMENT_REPORT
Message
for any ongoing
measurement
for ongoing
traffic volume
measurement
Source: 3 GPP 25.331 (Chap. 8.4.2)
MEASUREMENT REPORT Message (II) g ( )
UE transmits MEASUREMENT_REPORT message in
acknowledge (AM) or unacknowledge (UM) mode according to the stored
IE t ti d IE measurement reporting mode
UE sets in MEASUREMENT REPORT message the IEs: _ g
measurement identity number
to the associated meas. identity number
measured results
to include measurements according to the IE reporting quantities
measured results in the IE additional measured results measured results in the IE additional measured results
to include measurements associated with the IE additional measurements
which are stored in the variable MEASUREMENT_IDENTITY.
Source: 3 GPP 25.331 (Chap. 8.4.2)
Resource Allocation Fonction
Resource Allocation Function
R
N
C
Cell 1
NodeB
New radio
bearer
Reject/ accept
request
Cell 1
R
A
Code
allocation
Node
B
N
C
Cell 2
C
D
Traffic quality
B
Admission
Control
SRNC CRNC
Admission Control Algorithm
Resource allocation
Admission
C t l
-RL setup request
-RL addition request
RL reconfigurationprepare
-RL setup response
RL additionresponse
Control
Admission
decision
-RL reconfiguration prepare
-Common Transport Ch. Resource request
-RL addition response
-RL reconfiguration ready
-Common Transport Ch. Resource
response
R
N
S
A
P
R
N
S
A
P
Algorithm
OK
Code
Allocation
/Release
P P
-RL setup failure
-RL addition failure
-RL reconfiguration failure
failure
Admission
decision
Algorithm
NG
-RL deletion request
RL reconfigurationcancel
OM Data base and
parameters
-RL reconfiguration cancel
release
Admission Control Purpose
Maximum
Interference
level
Unstable
I threshold
flexible
range
Maximum
planned
Safe range
noise rise
DI
Transmission load
DL
Itotal
Carrier and Interference for Radio Bearer i
Carrier power of
radio bearer i:
i
C
j
C
Carrier power of
other radio bearers j:
j
j
Thermal noise:
UL
N
Interference coming from other cells:
j
j UL
C f
NodeB
j
Node B
Admission Control: Example for UL
Current load: New service: Current load:
- 4 user: 12.2 kbit/s
- 2 user 384 kbit/s
- scaling factor: 0.5
New service:
- 384 kbit/s
Note:
This example calculation has
been done with arbitrary Eb/No
values. For the exact evaluation
one has to apply equation (7). o e as to app y equat o ( )
cre cell adc cellid=10
wa=0.99 mulfnrb=0.65
mdlfnrb=0.55
mulfshrls=0.8
mdlfshrls=0.8
maxno_bear=100
max_psrate=384
Admission Control
Admission Control Process
HOof bearer i Setupof newbearer i Releaseof
load(n)UL:=load(p)UL+new load UL
load(n)DL:=load(p)DL+new load DL
HO of bearer i Setup of new bearer i Release of
bearer i
load(n+1)UL:=load(p)UL-released load UL
load(n+1)DL:=load(p)DL-released load DL ( ) (p)
load(n)UL <
max. HO
load UL
load(n)UL
<
max. new
( ) (p)
no no
load UL
yes
no no
load(n)DL< load(n)DL
yes
load(n)DL
max. HO
load DL
load(n)DL
<
max. new
load DL
yes
Bearer i admitted Bearer i dropped
OVL
Bearer i denied Bearer i admitted
load(p)UL: load(n)UL load(p)UL: load(n)UL
load(p)=estimated initial load
Max. HO UL/DL and max. new UL/DL is OM parameters
load(p)UL:=load(n)UL
load(p)DL:=load(n)DL
load(p)UL:=load(n)UL
load(p)DL:=load(n)DL
SF1 SF2 SF4 SF8
OVSF code tree
C4,0=
C8,0=
(1,1,1,1,1,1,1,1)
C4,1 assigned
SF1 SF2 SF4 SF8
(1,1,1,1)
C2,0=
(1,1)
C8,1=
(1,1,1,1,-1,-1,-1,-1)
C1 0=
( , )
C4,1=
(1,1,-1,-1)
C8,2 =
(1,1,-1,-1,1,1,-1,-1)
Not available
codes
C1,0=
(1)
C8,3=
(1,1,-1,-1,-1,-1,1,1)
C8,4=
(1 -1 1 -1 1 -1 1 -1)
C2 1=
C4,2=
(1,-1,1,-1)
(1, 1,1, 1,1, 1,1, 1)
C8,5=
(1,-1,1,-1,-1,1,-1,1)
C2,1=
(1,-1)
C4,3=
C8,6=
(1,-1,-1,1,1,-1,-1,1)
CSF,code number
(1,-1,-1,1)
C8,7=
(1,-1,-1,1,-1,1,1,-1)
SF
Channel symbol
t (k )
Channel bit
t (kb )
Maximum user data rate
ith 1/2 t di (kb )
DL Dedicated channel symbol and bit rate
SF
rate (ksps) rate(kbps) with 1/2-rate coding(kbps)
512 7.5 15 1~3
256 15 30 6~12
128 30 60 20~24
64 60 120 45
32 120 240 105 32 120 240 105
16 240 480 215
8 480 960 456
4 960 1920 936
Example of code allocation
4,0
SF=4
8,0 8,1
used code
SF=8
16,0 16,2 16,1 16,3
newcode
SF=16
32,0 32,1 32,2 32,3 32,4 32,5 32,6 32,7
SF=32
64,1 64,0 64,3 64,2 64,5 64,4 64,7 64,6 64,9 64,8 64,13 64,12 64,11 64,10 64,15 64,14
SF=64
unavailable code available code
Power Control
MS1
Power control function
MS1
MS2
MS3
F1
F1
MS1
MS3
MS2
F1
F1
MS3
M
S
M
M
S
M
S
M
S
Power at
N d B
Power at
N d B
1
M
S
2
M
S
3
S
1
S
2
S
3
Node B Node B
Without Power Control With Power Control
Principle of power control
V
Low
V
e
r
y

l
o
w
High
V
e
r
y
h
V
e
r
y
h
ig
h
Example:
Power Control
Fast power control
Example:
- Fast (1500 Hz)
- Closed inner loop
- Adaptionof transmittedpower ensures an (almost) constant level at the receiver Adaption of transmitted power ensures an (almost) constant level at the receiver
- E.g.: UE speed =3 km/h
Types of Power Control
POWER CONTROL
Open Loop Closed Loop Common Open Loop
Power
Control
Closed Loop
Power
Control
Common
Channel Power
Control
Inner Loop Power Control
Outer Loop Power Control
OLPC OLPC
Theouter looppower control adaptstheSIR The outer loop power control adapts the SIR
target value used by the closed loop power
l i h h i control in such a way that a certain
transmission quality in terms of bit and
block error ratio can be maintained
Furthermore, the SIR target is adapted to
the minimum required value in order to
optimise system capacity p y p y
Function Parameter Table name Value Description
Common Channel Power Control
Primary CPICH
transmissionpower
pwr_pcpit cell iub 33
dBm
Total transmittedpower of CPICH
MaximumFACH power mfachp dlcc -3dB First S-CCPCH channel power value
relative to CPICH
PCH power offset po_pch dlcc -3dB Second S-CCPCH channel power value
relative to CPICH
BCH ff t h ll i b 3dB P CCPCH l l ti t CPICH BCH power offset po_pch cell iub -3dB P-CCPCH power value relative to CPICH
PICH power offset po_pich dlcc -6dB PICH power value relative to CPICH
AICH power offset po_aich ulcc -6dB AICH power value relative to CPICH
P-SCH power offset po_psch cell iub -3dB P-SCH power value relative to CPICH
S-SCH power offset po_ssch cell iub -3dB S-SCH power value relative to CPICH
Control Channel Power Data
cre cell iub cellid=10 cellid lcl=0nodebid=0uarfcn=9862 10812 cre cell iub cellid=10 cellid_lcl=0 nodebid=0 uarfcn=9862,10812
max_dltp=43 t_cell=0 sac=0 rac=10 lac=42 nwom=md2 atdt=mnd
tmr_cspu=0 t312=10 n312=1 t313=3 n313=50 n315=1 id_ura=1 tpcu=5
t302=4000 n302=3 t307=30 sc_pcpi=2 pwr_pcpit=33 po_bch=-3.0
po psch= 3 0 po ssch= 3 0 cellbr=nbar cellrop=nrsvcsrqm=ecn0trslct=3 po_psch=-3.0 po_ssch=-3.0 cellbr=nbar cellrop=nrsv csrqm=ecn0 trslct=3
dclc_utran=7 qqualm=-24 poffset=20 pwval_max=7 t316=30 t317=30
ifc_rslct=nalwd t_br=10 qhyst1s=4 qhyst2s=4 maut=24 qrxlevmin=-115 cio=
0.0 t300=3000 n300=2 t309=5 t314=12 t315=180 sac_cbs=0 fach_moclc=5
interrat mind=false iffdd mind=true interrat_mind=false iffdd_mind=true
Downlink Control Channel Power Data
cre dlcc cellid=10 nodebid=0 id_cch=0 ccho_type=2 po_pch=-3 po_pich=-6 mfachp=-3
sccpch_scd=0
Uplink Control Channel Power Data
cre ulcc cellid=10 nodebid=0 id_cch=0 sc_wno=0
avsgn=0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 po_aich=5
Open Loop Power Control Function
BCH information
MS sets the initial transmission power of RACH and p
send preamble signal
Preamble
AICH
Preamble
Preamble
Random access message
(PRACH)
Inner Loop and Outer Loop Power Control Operation
CRC
Received
RNC
Node B
Signal CRC
evaluation
Received
signal
Signal
detector
Inner Loop
Comparing target
SIR (OLPC) with
target SIR (NodeB)
SIR
measurement
g ( )
I L
Outer
Inner Loop
Power
Control
New Target SIR
Transmit power
up/down order
by TPC
Loop
Power
Control
Outer Loop
Inner Loop Power Control
DL DPCH channel with TPC
UL DPCCH channel with TPC
If
SIR > target SIR
If
SIR < target SIR SIR > target SIR,
thenTPC is set down(1dB)
SIR < target SIR,
thenTPC is set up(1dB)
Inner Loop Power Control Operation
0 66666
The SIR is
measured on Pilot
bits
PL TPC PL TPC UL (DPCCH)
0.66666ms
bits
Received SIR
Measurement
Up (TPC=1)
Down(TPC=0)
Received SIR
Measurement
Up (TPC=1)
PL TPC PL TPC (DPCH) DL Data Data
Down(TPC=0)
0.66666ms
Designated transmitter power
Range and Initialization of DPDCH power
P
max
(dB) = min (SIR
target
10log(SF) + Poffset , Max. power value)
P
min
(dB) = max [P
max
(dB) delta , -35dB]
P
DPDCH,init
= median[SIR
target
10log(SF/2) - (Ec/No) + margin, Max_init_power_value, -35 dB]
- SIR
target
: DL SIR target depending on the application
- SF : Spreading factor for the channel
- Poffset : cell iub: poffset
- Max Power value: iub:pwval_max
- Delta : Fixed to 25 dB
Command format example
cre cell iub cellid=10 cellid lcl=0nodebid=0uarfcn=9862 10812 cre cell iub cellid=10 cellid_lcl=0 nodebid=0 uarfcn=9862,10812
t302=4000 n302=3 t307=30 sc_pcpi=2 pwr_pcpit=33 po_bch=-3.0
po psch=3 0po ssch=3 0cellbr=nbar cellrop=nrsvcsrqm=ecn0trslct=3 po_psch=-3.0 po_ssch=-3.0 cellbr=nbar cellrop=nrsv csrqm=ecn0 trslct=3
interrat mind=false iffdd mind=true interrat_mind=false iffdd_mind=true
Outer Loop Power Control Function
F1
R
N
C
Frame reliability
information
P d
Target SIR adjustment
Power up or down
If received SIR>set SIR,
then power down
If BLER increase then
set SIR up, else down
SIR Target value
SIR target value
number
SIR target in
dB
Note
UL SIR Target=000 -8.2 dB
Value range:
-8.2 dB to 17.3 dB
Step of 0.1 dB
p
UL SIR Target=254 17.2 dB
UL SIR Target=255 17.3 dB
Example:
Outer loop power control
Example:
- in the long-term the target frame error rate BLER
target
is reached
- SIR is adapted to changing conditions
Outer loop power control Reduction of update rate
Example: Reduction of update rate
- Node B - SIR
target
is only updated if a certain threshold is reached
- e.g. Update threshold =0.5 dB
Example: Handlingof limited UE dynamic
Outer loop power control- Limited UE power control dynamic
Example: Handling of limited UE dynamic
- Outer loop power control will be deactivated if SIR
error
is exceeded
- important: particularlywhen the UE applies max. Power important: particularly when the UE applies max. Power
- e.g. SIR_error_max =3 dB
Outer Loop Power Control
Outer Loop Power Control Function
error_flag=false
target initial, target CLPC,
SIR SIR
SIR SIR =
DCH setup
target initial, target OLPC,
SIR SIR =
Idle
SIR
error
measurement
report
Uplink Iub/Iur user data
frame of reference bearer
Error flag =false ?
SIR SIR SIR s s
No
RAB assignment
Select new
reference bearer
for at least one radio link
in the active set ?
Yes
No
max error, error min error,
SIR SIR SIR s s
Error_flag=true
Yes
A
A +
ok, not is DCH reference of CRC if
), , min(
max target, target OLPC,
BLER
SIR SIR
Initialise new OLPC:
BLER
target
SIR
OLPC,target
SIR
CLPC,target
Error_flag=false
=
ok. is DCH reference of CRC if
), ,
1
max(
:
min target,
target
target
target OLPC,
target OLPC,
SIR
BLER
BLER
SIR
SIR
? Update_threshold
target CLPC, target OLPC,
> SIR SIR
Yes
No
Send SIR
CLPC,target
via
Iub control frame
target OLPC, target CLPC,
SIR SIR =
Outer Loop Power Control - command format example
cre olpc thr_upd=0 step_size=1 lowthr_sirerr=-3 upthr_sirerr=3
Handover
Example of different handover types
GSM
I t t HO
UMTS macro cell
Intersystem HO
Triggered by limited
coverage of UMTS
3
2
Intersystem HO
Triggered by GSM
Interfrequency HO
UMTS macro cell
1b
UMTS micro cells
Softer HO
S ft HO
1a
Softer HO
(Intrafrequency HO
Intra Node B)
Soft HO
(Intra-frequency HO
Inter Node B)
HO pre-processing: filtering of the measurements
Filtering of the received signal :
n
1 n n M
~
a M a) (1 M + =
a =
(k/2)
strong dependence on k
k received in the IE "Filter coefficient"
k =0 19
n
) (
k =0 .. 19
k =0 no filtering
Th th dfilt fl t ti db h t t f di
Filtering: fading channel
The method filters fluctuations caused by short term fading
Example:
k =6 - k =6
- UE speed =3.6 km/h
Filt i f l t f di
Filtering: fading channel in case of long term fading
Filtering of long term fading
Example:
k =11 - k =11
- UE speed =22 km/h
0
5
10
e
d
measured
filtered
threshold
-10
-5
0
[
d
B
m
]

&

f
i
l
t
e
r
e
-20
-15
r
x

l
e
v
e
l

a
r
b
.

[
-30
-25
0 20 40 60 80 100 120 140 0 20 40 60 80 100 120 140
di stance [m]
Basic Handover Algorithm: Events 1A, 1B, 1C
time to trigger time to trigger time to tri gger
CPICH 1
Measurement
Quantity M
R H / 2
R
1A
H
1A
/ 2
R
1B
+H
1A
/ 2
H
1C
/ 2
CPICH 2
CPICH 3
Cell 1 Connected
Event 1A
Add Cell 2
Event 1C
Replace Cell 1 with Cell 3

Event 1B
Remove Cell 3
Time
Primary CPICH 4 gets better than Primary CPICH 3
Example:
- three cells 1,2 and 3 (P CPICH 1, 2 and 3) are in the active set
cell 4 (CPICH 4) is not (yet) in the active set
Radio link replacement
- cell 4 (CPICH 4) is not (yet) in the active set.
- Primary CPICH gets better than a P CPICH 4 that is in the active set AND
- event 1C has been ordered by UTRAN, then this event shall trigger a report to be sent from the UE
Measurement
quantity
P CPICH 1
P CPICH2 P CPICH 2
P CPICH 3
i
P CPICH 4
Reporting
event 1C
Time
Dependence of the quality of active set on W
W increases the quality of the active set Q
UTRAN
E l
Weighting factor W
Example:
- W =0 Q
UTRAN
determined by the strongest CPICH
- W >0 impact of the rest of the cells increases
Dependence of the quality of active set on the number of cells
For W >0 the Q
UTRAN
depends on the number of cells in the active set
E l
Weighting factor W
Example:
- 1 .. 3 cells in the active set
Hysteresis limits the amount of measurement reports
- limits the amount of event-triggered reports
Hysteresis
- a hysteresis parameter is connected with each reporting event
- value of the hysteresis is given to the UE in the reporting criteria field of the measurement control message
Measurement
quantity
P CCPCH 1
Hysteresis
P CCPCH 2
Reporting
event
Time
Time-to-trigger limits the amount of measurement reports
Measurement
quantity
P CPICH 1
Reporting
range g
P CPICH 2
Time-to-trigger
P CPICH 3
Reporting
event
Time
Execution of HO: e.g. radio link addidion
DR SR DR
N
C
SR
N
C
S
N
B
D
N
B
Decision to setup
newRL
Measurement report for new link
NB
AP
NB
AP
R
NS
AP
1. RL Setup Request
2. RL SetupResponse
2. RL SetupRequest
2. RL Setup Response
R
NS
AP
AL
CA
P
AL
CA
P
3. Establish Request
AL
CA
P
AL
CA
P
3. Establish Request
3. Establish Confirm
RR
C
4. DCCH: Active Set Update Command
3. Establish Confirm
RR
C C
4. DCCH: Active Set Update Complete
C
voice voice
voice voice
voice
R
1A
Handover
R
1A
= R
1A
- R
OFFSET
PCPICH 2 monitored cell
Time
1A 1A
Example: limited coverage triggers time maintained hard HO
RF2: neighbor cell1 RF2: neighbor cell2 RF2: neighbor cell3
RF1: neighbor cell4 RF1: endof coverage RF1: neighbor cell4 RF1: end of coverage
cell5
Example: Coverage triggered inter-frequency HO: event 2D
Cell 4 & 5 connected
CPICH cell 4 & 5 / 5
Q
UTRAN
Cell 5
connected
H
T
2D
H
2D
event 2D
Time
event 1B event 2D
(Q
UTRAN
)
Leaving
triggering
Entering
triggering
(cell 4) (Q
UTRAN
)
triggering
condition
triggering
condition
Inter system HO control: event 2D followed by 2F - no HO
CPICH A
Q
used
T
used2F
+ H
2F
/ 2
T
used2D
H
2D
/ 2
T
used
H
3A
/ 2
cell A connected
event 2D
start inter-system
measurements
time
event 2F
Stop inter-system
measurements measurements measurements
Inter system HO control: event 2D is followed by 3A
HO is triggered
M
otherRAT
Q
used
/ C O
gg
CPICH A
GSM RXLEV
T
otherRAT
+ H
3A
/ 2-CIO
otherRAT
T
used2D
H
2D
/ 2
T
used2F
+ H
2F
/ 2
event 2D
time
T
used
H
3A
/ 2
cell A connected
event 2D
start inter-system
measurements
event 3A
handover
triggered
GSM RXLEV GSM RXLEV
Compressed mode
TG pattern 2
#TGPRC #1 #2 #3 #4 #5
TG pattern 1 TG pattern 1 TG pattern 2 TG pattern 1 TG pattern 2
TG pattern 1 TG pattern 2
Transmission
Transmission gap 2
gap 2 gap 1
Transmission Transmission
gap 1
p p
gap 2
TGSN TGSN
gap 1 gap 1
TGL2 TGL2
TGD TGD
TGL1 TGL1
TGPL1 TGPL2
Hierarchical Cell Structure
Example: macro / micro / pico cells
Macro cell
0
1
Pico cell
1 1
2
2
2
1
2
2
1
Micro cell
Hierarchical cell structure: principle
F1 F1 F1
Layer 1 Cells with
RF1
F2 F2 F2
Layer 2 Cells with
RF2
HCS evolution example
1) F1 in macro cells
Overall capacity
F1 F1
2) F1+F2 in macro cells F1 F1
F1,F2 F1,F2
3) F1+F2 in macro cells and
F1 in selected micro cells
Overall capacity ,Hot spot capacity
F1 F1
F1,F2 F1,F2
F1 F1 F1 F1
Overall capacity ,Hot spot capacity
4) F2 in macro cells and
F2 in selected micro cells
F1 in continuous micro cells
F1 F1 F1 F1 F1 F1
F2 F2
F1 F1 F1 F1 F1 F1 F1 F1 F1 F1
F2 F2 F2 F2
Cell re-selection: HCS measurements of neighbor cells will be
triggered if these HCS-dependent conditions are met. gg p
Measurement of Neighbor Cells: Measurement of Neighbor Cells:
HCS: Neighbor Cell Measurements
Intra-RAT (FDD): Intra RAT (FDD):
all cells if [(Squal <= S
intersearch
) OR (Srxlev <= S
searchHCS
)] else
h i h i if N i T l *) hcs_prio
n
<= hcs_prio
s
if n
CR
> N
CR
in T
CRmax
else *)
hcs_prio
n
> hcs_prio
s
if Squal > S
intrasearch
else
hcs_prio
n
>= hcs_prio
s
Squal <= S
intrasearch
Inter-RAT (GSM):
all cells if [(Squal <= S
searchRAT
) OR (Srxlev <= S
HCS,RAT
)] else
hcs prio
n
<= hcs prio
s
if n
CR
> N
CR
in T
CRmax
else *) hcs_prio
n
< hcs_prio
s
if n
CR
> N
CR
in T
CRmax
else )
no cells if Squal > S
limit,SearchRAT
else
h i h i S l S
*) High mobility state
hcs_prio
n
>= hcs_prio
s
Squal <= S
limit,SearchRAT
HCS: decision criterion H for prioritized ranking
HCS Q lit L l Th h ld HCS Q lit L l Th h ld
HCS: Hierarchical Cell Selection, Criterion H
HCS Quality Level Threshold: HCS Quality Level Threshold:
H
s
= Q
meas,s
- Qhcs
S
H
n
= Q
meas,n
- Qhcs
n
- TEMP_OFFSET
n
* W(PENALTY_TIME
N
T
n
)
if HCS_PRIO
n
<> HCS_PRIO
s
(Trigger: Q
meas,n
> Q
hcsn
)
Quality Measure Q:
Q
meas,n
= CPICH RSCP / RxLev
Q
meas,n
= CPICH Ec/No
HCS: Cell Ranking Criterion R
R ki f ll R ki f ll
HCS: Cell Ranking Criterion R
if HCS_PRIO
n
= HCS_PRIO
s
(Trigger: Q > Q + Qoffset )
Ranking of cells: Ranking of cells:
R
s
= Q
meas,s
+ Qhyst
S
(Trigger: Q
meas,n
> Q
meas,s
+ Qoffset
s,n
)
R
n
= Q
meas,n
Qoffset
s,n
- TEMP_OFFSET
n
* W(PENALTY_TIME
n
T
n
)
Re-selected cell: Suitable (S > 0)
Highest HCS PRIO [if H > 0] *) Highest HCS_PRIO [if H 0] )
Best Ranked (Highest R)
*) in high mobility state neighbor cells with lower priorities are selected
Quality Measure
Q
meas,n
= CPICH RSCP / RxLev Qhyst1s
s,n
& Qoffset1s
s,n
Q
meas,n
= CPICH Ec/No Qhyst2s
s,n
& Qoffset2s
s,n meas,n
y
s,n s,n
Load overflow mechanism
RF2
Cell with Lowload Cell with Low load
Overflow
RF1
Cell with High load
Load balancing mechanism
RF2 RF2 RF2
Cell2 balanced load Cell2 balanced load Cell2 balanced load
RF1 RF1 RF1
Cell1 balanced load Cell1 balanced load Cell1 balanced load
NodeB1 NodeB2 NodeB3
Cell Search
Power on
Overall selection process
PLMN Selection
and Reselection
PLMN
F1
C
PLMN
selected
PLMN
available
F1
Registration
response
Cell selection
and
Reselection
C
N
R
N
C
Reselection
Location registration
Registration
PLMN Selection and reselection
PLMN A PLMN B
MCC= XX , MNC(A)=YY MCC= XX , MNC(B)=ZZ
USIMcard
IMSI=MCC+MNC+MSIN
IMSI format
MCC
3 digits
MNC
2~3 digits
MSIN
(Mobile Subscriber Identity Number)
Maximum 10 digits
RRC idle and connected mode
RRC service state
Idle Mode
Cell selection Camping
F1
Cell selection Camping
on a cell
RRC connection request
R
NN
C
RRC connection set up
Cell
DCH
Cell FACH
Connected
Mode
Cell
PCH
URA
PCH
PCH
PCH
Initial cell selection
Cell 1 Cell 4
System information:
-PLMN identity
-Cell information
-Neighboringcells
Cell 2
Cell 3
Neighboring cells
Candidate List: :
- Cell Information:
Carrier frequency,
Scrambling code,etc
- Neighboring cells:
Cell 1,cell 3,cell 4
Cell 4
New PLMN Selection
No Yes
Idle mode cell selection
and reselection
Initial
Cell Selection
Stored
information
Cell Selection
No suitable cell
found
Stored
information
Camped normally
Suitable cell
found
Suitable cell
found
Cell Reselection
l ti
No suitable cell
found
Connected
mode
Suitable cell
found
trigger
evaluation
Any cell selection
No USIM
No suitable cell
found
Any cell selection
USIM inserted
Acceptable cell
found
Camped on any cell
Suitable cell
found
Connected
mode
Acceptable cell
found
trigger
Cell Reselection
evaluation
No Acceptable cell
found
(EC calls only)
Cell search
Slot Synchronization
(P-SCH)
SCG0
Frame Synchronization
(S-SCH)
SCG0
(8 sc)
Scrambling code
group
SCGi
(8 sc)
512sc
Scrambling Code
Identification
(CPICH)
SCG63
Scrambling code
SCG63
SC
Parameter name parameter Sector / Cell value
1 0 timing offset of the t_cell
Cell synchronization
2 256
3 512
P-SCH power offset po_psch Urban -3dB
cell
P(t)
CPICH
S-SCH power offset po_ssch urban -3dB
SCH1
SCH2 SCH3
Off t ti i 256 Off t ti i 512
t
SCH
1
SCH
2
Offset timing=256 Offset timing=512
SCH
3
2
Sector
3
Sector
2
Sector
1
Cell selection criterion: S
A ll i it bl if it f lfill S
S it bl ll S it bl ll
A cell is suitable if it fulfills S
Suitable cells: Suitable cells:
FDD cells: Srxlev > 0 AND Squal > 0
GSM cells: Srxlev > 0
Squal => CPICH EC/N0
Srxlev => CPICH RSCP
Squal = Q
qualmeas
Qqualmin q Q
qualmeas
Qq
Srxlev = Q
rxlevmeas
- Qrxlevmin Pcompensation *)
*) Pcompensation =max(UE_TXPWR_MAX_RACH - P_MAX, 0)
Non HCS: Neighbour Cell Measurements
M t f i hb ll M t f i hb ll
Non HCS: Neighbour Cell Measurements
Measurement of neighbor cells: Measurement of neighbor cells:
I t F S l < S OR Intra-Frequency: Squal <= S
intrasearch
OR
S
intrasearch
is not sent
Inter-Frequency: Squal <= S
intersearch
OR
S
intersearch
is not sent
Inter-RAT (GSM): Squal <= S
searchRAT
OR
S
searchRAT
is not sent
searchRAT
Non HCS: Cell reselection and ranking criterion: R
R ki f ll R ki f ll Ranking of cells: Ranking of cells:
R
s
= Q
meas,s
+ Qhyst
S
R
n
= Q
meas,n
Qoffset
s,,n
Re-selected cell: Suitable (S Criterion)
Best Rank(Highest R)
Q
meas,s
/ Q
meas,n
= CPICH RSCP / RxLev Qhyst1s
s,n
& Qoffset1s
s,n
Q
meas,s
/ Q
meas,n
= CPICH Ec/No Qhyst2s
s,n
& Qoffset2s
s,n
FDD: Cell iub csrqm = rscp cell iub qhyst1s & cell aci qoffset1
= ecno cell iub qhyst2s & cell aci qoffset2 = ecno cell iub qhyst2s & cell aci qoffset2

Example: Cell Re-selection; Non - HCS case
Radio Channel Configuration
Radio interface channels
Upper Layers
UL DL
RLC
BP CD D
MAC
Logical channel
B
C
C
H
P
C
C
H
C
C
C
H
D
C
C
H
D
T
C
H
C
C
C
H
D
C
C
H
D
T
C
H
MAC
Transport channel
B
C
H
F
A
C
H
P
C
H
R
A
C
D
C
H
D
C
H
PHY
H
C
H
H
P
-
C
C
P
C
H
S
-
C
C
P
C
H
C
P
I
C
H
A
I
C
H
P
I
C
H
S
C
H
D
P
C
H
D
P
C
C
H
P
R
A
C
H
D
P
D
C
H
Air interface
Physical Channel
Transport Channel
Physical channels
UL Physical Channel DL Physical Channel
y
Dedicated
Channel
Common Channel Dedicated
Channel
Common Channel
Dedicated
Physical Data
Channel
(DPDCH)
Physical
Random
Access
Ch l
Dedicated
Physical
Channel
(DPCH)
Common Control
Physical Channel
(CCPCH)
(DPDCH) Channel
(PRACH)
Dedicated
Physical Control
(DPCH)
Synchronization
Channel
(SCH)
Channel
(DPCCH)
(SCH)
Common Pilot
Channel
(CPICH)
Paging Indicator
Channel
(PICH)
Acquisition Indication
Channel
(AICH)
Tslot=2560chips 10x2
k
bits(k=0 7)
Common and dedicated physical channel configuration
Tslot=2560 chips , 10x2
k
bits(k=0~7)
Data1
Ndata1 bits
TPC
NTPC bits
TFCI
NTFCI bits
Data2
Ndata2 bits
Pilot
Npilot bits
DPCH
DL
1 frame 10ms 1 frame 10ms
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
0
14
UL
1 TS, 2560 chips,10 bits
Pilot
Npilot bits
Transmission Power
Control
(TPC) NTPC bits
Feedback
Information
(FBI)NFBI bits
Transmission Format
Combination Indicator(TFCI)
NTFCI bits
UL
DPCCH
User data
Ndata=10x2
k
(k=0~6)
DPDCH
Slot Channel bit rate SF Bits/ Bits/ Ndata Slot Channel bit rate SF Bits/ Bits/ Ndata
UL DPDCH slot format
Slot
format
Channel bit rate
(kbps)
Channel symbol
Rate(ksps)
SF Bits/
Frame
Bits/
Slot
Ndata
0 15 15 256 150 10 10
Slot
format
Channel bit rate
(kbps)
Channel symbol
Rate(ksps)
SF Bits/
Frame
Bits/
Slot
Ndata
0 15 15 256 150 10 10 0 15 15 256 150 10 10
1 30 30 128 300 20 20
0 15 15 256 150 10 10
1 30 30 128 300 20 20
2 60 60 64 600 40 40 2 60 60 64 600 40 40
3 120 120 32 1200 80 80
4 240 240 16 2400 160 160
3 120 120 32 1200 80 80
4 240 240 16 2400 160 160
5 480 480 8 4800 320 320 5 480 480 8 4800 320 320
6 960 960 4 9600 640 640 6 960 960 4 9600 640 640
DPDCH bits/slot
Ch l Bit
Channel
TX slot
DPCCH
bits/slot
DL DPCH slot format
N
data
1
N
data2
0 15 7.5 512 10 0 4
N
TPC
N
TFCI
2 0
Slot format
Channel Bit
Rate (kbps)
Channel
Symbol Rate
(ksps)
SF Bits / Slot
per
radio
frame
N
Pilot
4 15
bits/slot
1 15 7.5 512 10 0 2
2 30 15 256 20 2 14
3 30 15 256 20 2 12
2 2
2 0
2 2
4 15
2 15
2 15
4 30 15 256 20 2 12
5 30 15 256 20 2 10
6 30 15 256 20 2 8
2 0
2 2
2 0
4 15
4 15
8 15
7 30 15 256 20 2 6
8 60 30 128 40 6 28
9 60 30 128 40 6 26
2 2
2 0
2 2
8 15
4 15
4 15 9 60 30 128 40 6 26
10 60 30 128 40 6 24
11 60 30 128 40 6 22
2 2
2 0
2 2
4 15
8 15
8 15
12 120 60 64 80 12 48
13 240 120 32 160 28 112
14 480 240 16 320 56 232
4 8
4 8
8 8
8 15
8 15
16 15
15 960 480 8 640 120 488
16 1920 960 4 1280 248 1000
8 8
8 8
16 15
16 15
DL transmission timing
10ms
#1 #14 #0
CPICH CPICH CPICH
P-SCH
256chip
P-SCH
256chip
P-SCH
256chip p
S-SCH S-SCH
p p
S-SCH
P-CCPCH(BCCH)
Tx off Data
P-CCPCH(BCCH)
Tx off Data
P-CCPCH(BCCH)
Tx off Data
S-CCPCH(FACH,PCH)
Pilot TFCI Data
S-CCPCH(FACH,PCH)
Pilot TFCI Data
S-CCPCH(FACH,PCH)
Pilot TFCI Data
D
A
T
A
P
I
L
O
T
T
F
C
I
DATA
T
P
C
DPCH(DCH)
D
A
T
A
P
I
L
O
T
T
F
C
I
DATA
T
P
C
DPCH(DCH)
dat
a
pil
ot
TF
CI data
TP
C
DPCH(DCH)
T
I
T
I
MAC layer
Transport channel
configuration
UL Channel DL Channel
Dedicated
Channel
Common
Channel
Dedicated
Channel
Common
Channel
Dedicated
Channel
(DCH)
Random
Access
Channel
Dedicated
Channel
(DCH)
Broadcast Channel
(BCH)
Transport Channel
Channel
(RACH)
Forward Access
Channel
(FACH)
Common
Paging Channel
(PCH)
Packet Channel
(CPCH)
Downlink Shared
Channel
(DSCH)
Physical Channel
Logical channel configuration
CONTROL CHANNEL
Common Control Channel (CCCH) Dedicated Control Channel
(DCCH)
TRAFFIC CHANNEL
(DCCH)
M
A
C
R
L
U
L

C
h
a
n
n
e
l
Dedicated Traffic Channel (DTCH)
C
C
CONTROL CHANNEL
Broadcast Control Channel
(BCCH)
Paging Control Channel
(PCCH)
Common Control Channel
(CCCH)
Dedicated Control Channel
(DCCH)
D
L

C
h
a
n
n
TRAFFIC CHANNEL
Dedicated Traffic Channel (DTCH) Common Traffic Channel (CTCH)
n
e
l
Outline for commands for common channels
Physical
channels
Cell channel parameters
P-CPICH P-SCH P-CCPCH S-SCH S-CCPCH PICH PRACH AICH
cell iub dlcc ulcc
FACH
BCH PCH
FACH
FACH RACH
Transport
channels
Definition of UL and DL frequency
cre cell iub cellid=10 cellid_lcl=0 nodebid=0 uarfcn=9862,10812
tmr cspu=0 t312=10 n312=1 t313=3 n313=50 n315=1 id ura=1 tpcu=5 _ p _ p
t302=4000 n302=3 t307=30 sc_pcpi=2 pwr_pcpit=33 po_bch=0.0 po_psch=-
3 po_ssch=-3.0 cellbr=nbar cellrop=nrsv csrqm=ecn0 trslct=3 dclc_utran=7
qqualm=-24 poffset=20 pwval_max=7 t316=30 t317=30 ifc_rslct=nalwd
t br=10 qhyst1s=4 qhyst2s=4 maut=24 qrxlevmin=-115 cio=0.0 t300=3000 _ q y q y q
n300=2 t309=5 t314=12 t315=180 sac_cbs=0 fach_moclc=5
interrat_mind=false iffdd_mind=true
... ...
200 kHz
F
centre
= UARFCN * 200 kHz
>UARFCN 5 * F / MH -> UARFCN = 5 * F
centre
/ MHz
DL physical channel data: command format example
cre cell iub cellid=10 cellid_lcl=0 nodebid=0 uarcfn=9862,10812
t302=4000 n302=3 t307=30 sc_pcpi=2 pwr_pcpit=33 po_bch=0.0
po_psch=-3 po_ssch=-3.0 cellbr=nbar cellrop=nrsv csrqm=ecn0 trslct=3
interrat_mind=false iffdd_mind=true
Transport channel multiplexing
Carrying PCH/FACH
multiplexing(Type2)
Carrying FACH multiplexing
(Type1)
Carrying PCH
(Type0)
S-CCPCH PICH S-CCPCH S-CCPCH PICH
PCH
FACH
FACH
FACH FACH PCH
cre dlcc cellid=10nodebid=0id cch=0 ccho type=2 po pch=3po pich=6mfachp=3 cre dlcc cellid=10 nodebid=0 id_cch=0 ccho_type=2 po_pch=-3 po_pich=-6 mfachp=-3
sccpch_scd=0
cre dlcc cellid=10 nodebid=0 id_cch=0 ccho_type=0 po_pch=-3 po_pich=-6 sccpch_scd=0
cre dlcc cellid=10 nodebid=0 id_cch=1 ccho_type=1 mfachp=0 sccpch_scd=0
cre ulcc cellid=10 nodebid=0 id_cch=0 sc_wno=0
avsgn=0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 po_aich=5
DCH UL Scrambling code
Bit 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
UL Scrambl i ng Code
SC RNC S-RNTI
Command format example: UL scrambling code per RNC
cre rnc rncid=14 mcc=454 mnc=03 a2ea_idi=85263349005
a2ea_dsp=0000000000000000000000 opc=11171 udpp_rnc=2152
udpp sgsn=2152 nwind ps=2 dpc ps=11140 drxclc ps=7 udpp_sgs 5 d_ps dpc_ps 0d c c_ps
nwind_cs=2 dpc_cs=11122 drxclc_cs=7 sc_rnc=1 cnodei=false
type_ldc=none opue_ibase=000000000 opue_iofs=0 ho_psrrh=hotr
tmr_iubhc=60 ipadr_cbc=000.000.000.000 _ p _
Restriction control
Restriction Control
Restriction control is a feature that will enhance network
resiliencetohighload andallowfor better testing resilience to high load, and allow for better testing,
maintenance and resource management.
There are two types of restriction control, automatic and
manual manual.
Automatic restriction control is applied by the RNC, by

refusing new requests for servicing when its CPUs are
overloaded overloaded.
Manual restriction is applied by the OMC/LMT by

changing the office data or issuing a command to the RNC
Measurement of CPU load
For the duration of its uptime, the RNC shall monitor the load of its
CPU(s)
The load is measured as a percentage of the maximum possible load (=
100%)
It is assumed that the basic period is 10 seconds. NumPeriods for
automatic restriction control has to be set to 1 (because any delay in
applying restriction may have hazardous effects on the RNC)
The RNC will perform the actions only for the CPUs that are
l d d d f h h l f h overloaded and not for the whole of the RNC
If a CPU that has an RNC-wide role (like the RMP processor) is
overloaded, then restriction shall be applied to all CPUs of the RNC
LSM
A
GTPM
From/To
CN/RNC
156 M
CLKD TINF
HUBIU TINF
TINF
G
M
U
X
C
1
H
W
Y
Restriction
l
A
T
M
S
W
D-CMPM
PRM
From/To
Node-B
From/To
156 M
TINF
TINF
CMP DTI
PRLC
C
M
U
X
E C
M
E1
HUBIU
C
1
H
W
Y
C
1
R
N
control
C-CMPM
DHTM
Node-B
TINF
TINF
CMP
CMP DTI
DHT
DHT
C
M
CMP DTI
C
M
U
X
E
M
U
X
E
E1
C
1
H
W
Y
H
W
Y
C
1
N
C
MHM
SIGM
TINF
TINF
CMP
HUBIU
MHC
HUBIU
M
U
X
C
C
M
U
X
ANC/
MFG
C
1
H
W
Y
1
H
W
Y
C
1
m
o
d
M2CM
TINF
MHC
HUBIU
M2C
M2C
C
M
U
X
C
M
U
X
E
1
H
W
Y
u
l
e
HUB
CP00 CLK
M2C E
CP02 CP01
D CCPM
s
CP00
SVC COC SCC
MIF
CLK CP02 CP01
D-CCPM
E-CCPM
IMAT
DK
DAT
Automatic Restriction Control Command Format
E l Example:
- Command format:
cre rsta thr1=80 thr_rs1=75 thr2=92 thr_rs2=89 rr2=90 rr1=50
cgc=01 peri=6
- Two severities: (1 & 2) are applied:
Basic period =10 s Supervision period =multiple of 10 s
Automatic Restriction due to processor overload
E l Example:
- Command format:
cre rsta thr1=80 thr_rs1=75 thr2=92 thr_rs2=89 rr1=50 rr2=90
cgc=01 peri=6
Restricted:
- incoming RRC connection requests
- incoming URA updates g
- incoming Cell updates
- CTS (FACH to DCH)
- Radio Link setup
- RL addition
- RL ReconfigurationPrepare RL Reconfiguration Prepare
- Paging requests from the SRNC
Restricted Restricted:
- incoming RRC connection requests
- incoming URA updates
- incoming Cell updates
- CTS (FACH to DCH)
Restriction control Restriction level =2 (20%)
E l Example:
- restriction control with pre-defined patterns
cre rstm kind=perset peri=6
cre rstm kind=acccls accrstl=2 cellid=10
- Command format example:
- e.g. 20 % restriction
AC 1 2 3 4 5 6 7 8 9 10 1 2 3 . . .
15 . . .
14 . . .
13
pstn
13 . . .
12 . . .
11 . . .
10 . . .
99 . . .
8 . . .
7 . . .
6 . . .
5 . . .
4 . . .
3 . . .
2 . . .
1 . . .
0 . . .
0 60 120 180 240 300 360 420 480 540 600 660 720 . . .
time [s]
Manual Restriction with self defined Patterns
cre rstm kind=accptn acccrstl=3
Example:
Command format
cre rstm kind accptn acccrstl 3
ptn1=1111111111000100
ptn2=1111111111000100
:
ptn10=0111111111000000
restriction control with self-
defined patterns
ptn10 0111111111000000
cre rstm kind=perset peri=6
cre rstm kind=acccls accrstl=3 cellid=11
Cell related Procedures
Audit, Cell Setup, Audit, Cell Setup,
System Information Modification
Cell Setup Request
Cell Setup (3G TS 25.433)
Cell Setup Response
Secondary CCPCH (FACH PCH PICH)
Common Transport Channel Setup Request
Initialisation of
P-SCH, S-SCH
P-CPICH, S-CPICH
P-CCPCH (BCH)
Secondary CCPCH (FACH, PCH, PICH)
Common Transport Channel Setup Response
Initialisation of
S-CCPCH
ALCAP Data Transport Bearer Setup
PRACH, AICH
PCPCH (CPCH AP AICH CD/CA ICH )
Initialisation of PRACH
PCPCH (CPCH, AP-AICH, CD/CA-ICH )
Initialisation of PCPCH
using Common Transport
Channel IDat ALCAP
System Information Update Request
System Information Update Response
Transmitting of System
Information on BCCH
Channel ID at ALCAP
(same VPI-VCI is used)
RNC Node B Iub Uu UE
Audit (3G TS 25.433)
Aft N d B t
Audit Required
After Node B reset or
to indicate possible misalignment of
State or Configuration Parameter.
In response to Audit Required or
Audit Request
to re-sync the Status of logical resources
and Configuration Parameter.
Node B information
Cell Information
Common Channel Information
Communication Control Port Information
Local Cell Information
Audit Response
Local Cell Information
RNC Node B Iub
Modification of System Information (3G TS 25.331)
S t I f ti U d t R t
Update of System
Information
Transmitting of new System
Information on BCH:BCCH
and FACH:BCCH
CCCH:PCH
Indication towards UE in Idle
Mode, CELL_PCH, URA_PCH
Paging Type 1
MIB Value Tag
Time Critical Modification of System Information (3G TS 25.331)
SystemInformation Update Request
Update of System
Information
BCCH Modification Time
Transmitting of new System
Information on BCH:BCCH and
FACH:BCCH at specified time
S t I f ti Ch I di ti
FACH:BCCH
Indication towards UE in
CELL_FACH state
CCCH:PCH
Indication towards UE in Idle
Mode, CELL_PCH, URA_PCH
System Information Change Indication
MIB Value Tag
Paging Type 1
MIB Value Tag
3G UMTS 3G-UMTS
Call related Procedures
UE CapabilityInformation, UE Capability Information,
RRC and NBAP Dedicated
M C l Measurement Control
Measurement Control
RRC, NBAP RRC, NBAP
RRC Measurement Control (3G TS 25.331)
RRC Measurement Control
RRC Measurement Report
Comnand: start
Reference, Type, Quantity
Report: Mode = periodical
Criteria = amount or interval
T interval
T interval
C d dif
T interval
Command: modify
Reference, Type, Quantity
Report: Mode = event
Criteria=Time to trigger
T t i
Event =true
T trigger
Command: release
NBAP Measurement Reporting(3G TS 25.331)
Measurement Initiation Request
Node B Communication Contect ID
Dedicated Common
Measurement Procedures
Measurement Initiation Response
Dedicated Measurement Object Type ID [RL, RLS, DPCH]
Report Characteristics [On-Demand, Periodic Event x]
additional Parameter [Thrshold, Hysteresis, Requested Time]
Filter Coefficient
Measurement Initiation Response
M t R ti Measurement Reporting
Measurement Reporting
Measurement Termination Request
Measurement Termination Response
RNC Node B Iub
UE Capability
UE Capability Update after RRC Connection Establishment (3G TS 25.331)
UE Capability Update Requirement =true
System Information 13
UE Capability Information
T 304
V304
RRC Connection Establishment
UE Capability Information Confirm
Radio Access Capability:
ICS Version, PDCP, RLC, TrCH,
RF, PhCh, RAT, security, LCS and
Measurement
UE System Specific Capability:
Inter-System Classmark
CN RNC Node B Iu Iub Uu UE
UE Capability Update during Handover towards GSM (3G TS 25.331, 25.413)
UE Capability Update Requirement =true
RRC Connection
Establishment
Confirm
T 304
V304
Establishment
RF, PhCh, RAT, security, LCS,
Measurement
Inter-System Classmark
NAS Connection Establishment
Relocation Required
Classmark 2
H d R t
Classmark 3
Handover Request
Classmark 2
Classmark 3
CN RNC Node B Iu Iub Uu UE BSS A
UE Capability Enquiry (3G TS 25.331)
RRC and/or NAS Connection Connection Establishment
UE Capability Enquiry
T 304
V304
UE Capability Information Confirm
RF, PhCh, RAT, security, LCS and
Measurement
Inter SystemClassmark Inter-System Classmark
3G UMTS
circuit switched
L ti U d t P d Location Update Procedures
FlowCharts Flow Charts
Timer
PM Counter
Normal Location Update (3G TS 25.931)
CR: Initial UE Message ((Loc Update Req) Initial Direct Transfer (Loc Update Req)
Cause: normal Location update
CC
MM Procedures (Authentication, Identification, Ciphering)
DT1: Direct Transfer ((Loc Update Accept) DL Direct Transfer ((Loc Update Acc)
Release initiated by the Network
Periodic Location Update (3G TS 24.008, 25.331, 25.931)
S t I f ti 1
UE Switch on
T3212
CC
DT1: Direct Transfer ((Loc Update Accept) DL Direct Transfer ((Loc Update Acc)
Release initiated by the Network
T3212
Expiry
T3212
Cause: periodic Location update
CC
3GUMTS 3G UMTS
circuit switched
Call Handling Procedures
MessageSequenceCharts Message Sequence Charts
Timer, PM Counter
Mobile Terminated Call (3GPP TS 25.931)
Paging for UE in Idle or Connected Mode
CR: Initial UE Message (Paging Response) Initial Direct Transfer (Paging Response)
Paging Cause
CC
DT1: Direct Transfer (Setup) UL Direct Transfer (Setup)
RN, RAB Establishment
DT1 : Direct Transfer (Call Confirmed) DL Direct Transfer (Call Confirmed)
DT1 : Direct Transfer (Alerting) DL Direct Transfer (Alerting)
DT1 : Direct Transfer (Connect) DL Direct Transfer (Connect)
DT1 : Direct Transfer (Connect Ack) UL Direct Transfer (Connect Ack)
Call Release initiated by the Network or Mobile
Ongoing Network - Mobile Call carry dedicated resources (e.g. AMR)
CN RNC Node B UE Iu Iub Uu
RRC C ti E t bli h t
Mobile Originated Call (3GPP TS 25.931)
CR: Initial UE Message (CM Service Req) Initial Direct Transfer (CM Service Req)
MO Cause
CC: DT1: Direct Transfer (Service Accept) DL Direct Transfer (Service Accept)
DT1 : Direct Transfer (Call Proceeding) DL Direct Transfer (Call Proceeding)
UL Direct Transfer (Setup) DT1 : Direct Transfer (Setup)
RB, RAB Establishment
DT1 : Direct Transfer (Connect) DL Direct Transfer (Connect)
UL Direct Transfer (Connect Ack)
Ongoing Mobile - Network Call carry dedicated resources (e.g. AMR)
DT1 : Direct Transfer (Connect Ack)
Call Release initiated by the Network or Mobile
Network Initiated Call Release (3G TS 25.931)
RRC RANAP
NAS NAS
SCCP
DT1 : Direct Transfer (Release) DL Direct Transfer (Release)
DT1 : Direct Transfer (Release Complete) UL Direct Transfer (Release Complete)
Connection Release of Dedicated Channel
Mobile Initiated Call Release (3G TS 25.931)
RRC RANAP
NAS NAS
SCCP
DT1 : Direct Transfer (Release Complete) DL Direct Transfer (Release Complete)
DT1 : Direct Transfer (Release) UL Direct Transfer (Release)
3G-UMTS
packet switched
C ll H dli P d Call Handling Procedures
MessageSequenceCharts Message Sequence Charts
Timer, PM Counter
NetworkInitiatedDataTransfer Network Initiated Data Transfer
Mobile Initiated Data Transfer
Paging for UE in Idle or Connected Mode
Network initiated Data Transfer (3GPP TS 23.060)
g g
CR: Initial UE Message (Paging Response) Initial Direct Transfer (Paging Response)
GMM Procedures (Authentication, Identification, Ciphering)
DT1 : Direct Transfer DL Direct Transfer
CC
UL Direct Transfer
(Activate PDP Context Request)
DT1 : Direct Transfer
(Request PDP Context Activation)
DL Direct Transfer
(Request PDP Context Activation)
(Activate PDP Context Accept)
DL Direct Transfer
UE or Network initiated PDP Context Deactivation
Ongoing Network - Mobile Data Transfer
RB, RAB Release
CN RNC Node B UE
Mobile initiated Data Transfer (3GPP TS 23.060)
GMM Procedures (Authentication, Identification, Ciphering)
CR: Initial UE Message (Service Request) Initial Direct Transfer (Service Request)
( p g)
CC: DT1: Direct Transfer (Service Accept) DL Direct Transfer (Service Accept)
UL Direct Transfer
Ongoing Mobile - Network Data Transfer
DL Direct Transfer
UE or Network initiated PDP Context Deactivation
RB RAB Release RB, RAB Release
CN RNC Node B UE
NetworkinitiatedRelease Network initiated Release
Mobile initiated Release
Network initiated Data Transfer Release (3G TS 25.931)
RRC RANAP
NAS NAS
SCCP
(Deactivate PDP Context Request)
DL Direct Transfer
(D ti t PDP C t t A t)
UL Direct Transfer
(D ti t PDP C t t A t) (Deactivate PDP Context Accept) (Deactivate PDP Context Accept)
CN RNC Node B UE
Mobile initiated Data Transfer Release (3G TS 25.931)
RRC RANAP
NAS NAS
SCCP
DL Direct Transfer
UL Direct Transfer
(Deactivate PDP Context Accept) (Deactivate PDP Context Accept)
CN RNC Node B UE
Service Request Procedures
Service Request initiated by MS Procedure not having active PDP Context
(UE requested PDP Context Activation Procedure)
PMM-Idle
SM-Inactive
signalling
Service Request
S it F ti
PMM-Connected
SM-Inactive
Security Functions
PMM-Connected
SM-Active
PDP Context Activation
RNC Node B UE SGSN HLR
Service Request initiated by MS Procedure having already active PDP Context
(UE requested Re-establishment of RAB's)
PMM-Idle
SM-Active
PMM-Connected
data
Service Request
S it F ti
PMM-Connected
SM-Active
Security Functions
SGSN initiated PDP Context Modification
Up-Link PDU
RNC Node B UE SGSN HLR
Service Request initiated by Network Procedure not having active PDP Context
(Network requested PDP Context Activation Procedure)
Send Routing Info
for GPRS Response
Send Routing Info
for GPRS Request
Down-Link PDU
PMM-Idle
SM-Inactive
Paging
PDU Notification Response
PDU Notification Request
p
PMM-Connected
SM Inactive
Service Request
SM-Inactive
Security Functions
Request PDP Context Activation
T3385
PMM-Connected
SM-Active
RNC Node B UE SGSN HLR GGSN PDN
unsuccessful Network requested PDP Context Activation Procedure
cause =MS GPRS Detached
Send Routing Info
for GPRS Response
Down-Link PDU
Send Routing Info
for GPRS Request
p
Failure Report
Response
Failure Report
Request
cause =IMSI Not Known
Send Routing Info
for GPRS Response
Down-Link PDU
Send Routing Info
for GPRS Request
cause =IMSI not known
p
Send Routing Info
for GPRS Response
Send Routing Info
for GPRS Request
newSGSN address
Failure Report
Request
new SGSN address
If same SGSN address
Failure Report
Response
cause =no Paging Response
Send Routing Info
for GPRS Response
Send Routing Info
for GPRS Request
Down-Link PDU
PMM-Idle
SM-Inactive
Paging
p
PDU Notification Reject Request
PDU Notification Reject Response
set MNRG
cause =UE refuse
Send Routing Info
for GPRS Response
Send Routing Info
for GPRS Request
Down-Link PDU
PMM-Idle
SM-Inactive
Paging
p
PMM-Connected
SM Inactive
Service Request
SM-Inactive
Security Functions
Request PDP Context Activation
T3385
Request PDP Context Activation Reject
PDU Notification Reject Request
cause =MS refuse
causes:
#26: insufficient resources
#31: activation rejected (unspecified)
#40: feature not supported
#95-111: protocol errors
Service Request initiated by Network Procedure having already active PDP Context
(Network requested Re-establishment of RAB's)
SM-Active
PMM-Connected
Down-Link PDU
Paging
Service Request
Security Functions
PMM-Connected
SM-Active
Down-Link PDU
PDP Context Activation PDP Context Activation
Procedures
PDP Context Activation Procedure (3G TS 23.060)
SM-Inactive
Activate PDP Context Request Activate PDP Context Request
CAMEL_GPRS_PDP_Context_Establishment
Invoke Trace
Create PDP Context Request
T3380
Activate PDP Context Accept
Create PDP Context Response
CAMEL_GPRS_PDP_Context_Establishment_Acknowledgement
SM-Active
RNC UE SGSN GGSN PDN
IPv6 Stateless Address Auto configuration Procedure (3G TS 23.060)
Router Solicitation
Router Advertisment
GGSN Initiated PDP Context Modification
Secondary PDP Context Activation Procedure (3G TS 23.060)
SM-Active
Activate Secondary PDP Context Request Activate Secondary PDP Context Request
Invoke Trace
T3380
PDP Context Activation for Non-transparent Access (3G TS 23.060, 29.061)
AT-Commands
PPP-LCP Negotiation
Activate PDP Context Request
PPP LCP Negotiation
CHAP / PAP Authentication
Configuration Request
Invoke Trace
T3380
PPP-IPCP
Access Request
Access Accept
RADIUS
Discover
Offer
Request
Ack
DHCP
Ack
Configuration Ack
ISP
Itranet
UE MT TE SGSN GGSN PDN RNC
PDP Context Activation with Mobile IP Registration (3G TS 23.060, 29.061)
AT-Commands
PPP-LCP Negotiation
Activate PDP Context Request
PPP LCP Negotiation
CHAP / PAP Authentication
Configuration Request
PPP-IPCP
Invoke Trace
T3380
CAMEL GPRS PDP Context Establishment Acknowledgement
Configuration Ack
Agent Advertisement
ICMP
Registration Request
Registration Request
Registration Replay
Registration Replay
MIP
ISP
Itranet
SGSN initiated PDP Context Modification Procedure
UE MT TE SGSN GGSN PDN RNC
PDP Context Modification PDP Context Modification
Procedures
UE initiated PDP Context Modification Procedure (3G TS 23.060)
Modify PDP Context Request
Update PDP Context Request
Update PDP Context Response
T3381
Invoke Trace
Modify PDP Context Accept
CAMEL_GPRS_Change_Of_QoS
SGSN initiated PDP Context Modification Procedure (3G TS 23.060)
T3386
Invoke Trace
GGSN initiated PDP Context Modification Procedure (3G TS 23.060)
RB RAB E t bli h t
T3386
Invoke Trace
PDP Context Deactivation PDP Context Deactivation
Procedures
UE initiated PDP Context Deactivation Procedure (3G TS 23.060)
Deactivate PDP Context Request
CAMEL_GPRS_PDP_Context_Disconnection
Delete PDP Context Request
Delete PDP Context Response
T3390
RB, RAB Release
Deactivate PDP Context Accept
RAB Release-Initiated Local PDP Context Modification Procedure (3G TS 23.060)
RB, RAB Release
SGSN initiated PDP Context Deactivation Procedure (3G TS 23.060)
T3395
RB, RAB Release
T3395
GGSN initiated PDP Context DeactivationProcedure (3G TS 23.060)
RB RAB R l
T3395
RB, RAB Release
Preservation Procedures
RAB Release Procedure triggered by UTRAN (3G TS 23.060)
RAB Release Request
RAB Assignment Request
RB Release
RAB Assignment Response
data
RAB Assignment Response
Iu Release Procedure triggered by UTRAN (3G TS 23.060)
Iu Release Request
Iu Release Command
RB Release
Iu Release Complete
signalling + data
Iu Release Complete
Attach Procedures
Attach Procedure (3G TS 23.060, 24.008)
GPRS attach
GPRS attach while IMSI attached
Combined GPRS/IMSI attach
Attach Request
KSI, Attach Type
Follow on proceed
Follow on Request pending
No follow on Request pending
Attach Accept
Combined GPRS attach or GPRS only
T3310
T3350
Network Operation Mode
Attach Complete
If TMSI and/or P-TMSI allocated
#2 =IMSI unknown in HLR
#16 =MSC temporarily not reachable
#17 =Network failure
#22 =congestion
normal
GPRS
attach
I II III MS
A
B
C
combined
GPRS
attach
Attach Request
T3310
Attach Accept
#3 or 6 =illegal MS or ME
#7 =GPRS service not allowed
#8 =GPRS and non-GPRS service not allowed
#11 =PLMN not allowed
#12 =Location Area not allowed
#13 =Roaming not allowed at this Location Area
RNS UE CN
GPRS Attach at same RAI/LAI using known P-TMSI (3G TS 23.060)
Attach Request
Authentication
T3310
IMEI Check
Update Location
clear MNRG
Ready For SM Gr
Gr p
Note MS
GPRS Present
clear MNRG
SMS Alert Procedure
clear MNRG
Location Update Request
Gs
Location Update Accept Gs
Attach Accept
Attach Complete
TMSI Reallocation Complete
CAMEL_GPRS_ATTACHED
T3350
Gs
RNS sameSGSN UE GGSN HLR sameVLR EIR
Iu Uu
SMSC
Gc
GPRS Attach at new RAI/LAI using known P-TMSI (3G TS 23.060)
Attach Request
Identification
Request
SEC.AttIdentityReqFromPsgsn
Identification
Response
Authentication
SEC.SuccIdentityReqFromPsgsn
T3310
IMEI Check
Update Location
Cancel Location
Cancel Location Acknowledge
Update Location Acknowledge
Insert Subscriber Data Acknowledge
Insert Subscriber Data
LocationUpdateRequest Gs Location Update Request
Cancel Location
Update Location
Gs
Location Update Accept
Update Location
Gs
Attach Accept
Attach Complete
CAMEL_GPRS_ATTACHED
T3350
Gs
RNS newSGSN UE GGSN HLR oldSGSN newVLR oldVLR EIR
Iu Uu Gc
GPRS Attach at new RAI/LAI using unknown P-TMSI (3G TS 23.060)
Attach Request
Identification
Request
SEC.AttIdentityReqFromPsgsn
Identification
Response
Identity Request
Identity Response
Authentication
SEC.SuccIdentityReqFromPsgsn
T3310
IMEI Check
Update Location
Cancel Location
Update Location Acknowledge
LocationUpdateRequest Gs Location Update Request
Cancel Location
Update Location
Gs
Location Update Accept
Update Location
Gs
Attach Accept
Attach Complete
CAMEL_GPRS_ATTACHED
T3350
Gs
RNS new SGSN UE GGSN HLR old SGSN new VLR old VLR EIR
Iu Uu Gc
Detach Procedures
UE initiated (explicit) Detach Procedure (3G TS 23.060, 24.008)
Detach Type
GPRS detach only
IMSI detached only
Combined GPRS/IMSI detach
Switch off
Detach Request
T3321
Delete PDP
Contect Request
Delete PDP
Contect Response
IMSI Detach
GPRS Detach
_ _ _ _
CAMEL_GPRS_Detach
set MNRG set MNRG set MNRG
Gs
Detach Accept
If Not Detach Type=switch off
RB, Iu Release
Purge Procedure Purge Procedure
RNS UE HLR VLR SGSN GGSN
SGSN initiated (explicit) Detach Procedure (3G TS 23.060, 24.008)
Detach Request
T3322
Delete PDP
Contect Request
Delete PDP
Contect Response
GPRS Detach
CAMEL_GPRS_Detach
Gs
Detach Accept
RB, Iu Release
SGSN initiated (implicit) Detach Procedure (3G TS 23.060, 24.008)
ThenetworkdetachestheMS without notifyingtheMS The network detaches the MS, without notifying the MS,
a configuration-dependent time after the mobile reachable timer expired,
or after an irrecoverable radio error causes disconnection of the logical link.
Delete PDP
Contect Request
Delete PDP
Contect Response
GPRS Detach
CAMEL_GPRS_Detach
Gs
HLR initiated (explicit) Detach Procedure (3G TS 23.060, 24.008)
Detach Request
T3322
Cancel Location
Delete PDP
Contect Request
Delete PDP
Contect Response
GPRS Detach
CAMEL_GPRS_Detach
Gs
Detach Accept
RB, Iu Release
Purge Procedure
Purge Procedure (3G TS 23.060, 24.008)
ThePurgefunctionallowsanSGSNtoinformtheHLR that it hasdeleted The Purge function allows an SGSN to inform the HLR that it has deleted
the MM and PDP contexts of a detached MS.
The SGSN may, as an implementation option, delete the MM and PDP contexts
of an MS immediately after the implicit or explicit detach of the MS.
Alternatively, the SGSN may keep for some time the MM and PDP contexts and
P MS
the authentication triplets of the detached MS, so that the contexts can be reused at a
later GPRS attach without accessing the HLR.
Purge MS
Purge MS Acknowledge
set MS_Purged_for_GPRS
Security Procedures
P-TMSI Reallocation (3G TS 23.060, 33.102)
P-TMSI Reallocation Command
T3350
P-TMSI Reallocation Complete
T3350
RNS UE EIR SGSN
Authentication Procedure
Authentication Data Request
Authentication Data Request
Authentication Data Response
Authentication Data Response
Authentication Request
SEC.AttAuthProcsSgsnUsim
q
Authentication Response
SEC.SuccAuthProcsSgsnUsim
T3360
RNS SGSN UE HLR AuC
H
Ciphering Procedure (3G TS 23.060, 33.102)
Security Mode Command
Security Mode Command
SEC.AttCiphering
T3360
Security Mode Complete
Security Mode Complete
SEC.SuccCiphering
T3360
Node B UE RNC SGSN
IMEI Identification (3G TS 23.060, 33.102)
Identity Request
SEC.AttIdentityReqImsi
T3370
Identity Response
Check IMEI Request
IMEI or IMEISV
SEC.SuccIdentityRequest
Check IMEI Response
RNS UE EIR SGSN
Gf
3GUMTS 3G UMTS
Handover Procedures
Handover Types Handover Types
Flow Charts, Timer, PM Counter
Soft Handover
B hAdditi Branch Addition
Branch Deletion
Branch Addition & Deletion simultaneously
Soft Handover: Radio Link Addition (3G TS 25.331, 25.433)
Radio Link Addition Request
Radio Link Setup Request
RNSAP
NBAP
SHOAttRLAddUTRANSide
Radio Link Addition Response
Radio Link Setup Response
ALCAP Data Transport Bearer
Setup
SHO.AttRLAddUTRANSide
SHO.SuccRLAddUTRANSide
SHO.FailRLAddUTRANSide
Setup
Active Set Update: Link Addition
DCCH
RRC
Active Set Update: Link Addition
Active Set Update Complete
SHO.AttRLAddUESide
SHO.SuccRLAddUESide
serving drift drift
SHO.FailRLAddUESide.Cause
sRNC dRNC dNodeB Iur Iub Uu UE
Soft Handover: Radio Link Deletion (3G TS 25.331, 25.433)
Active Set Update: Link Deletion
DCCH
RRC
RNSAP
SHO.AttRLDelUESide
SHO.SuccRLDelUESide
Radio Link Deletion Request
RNSAP
NBAP
SHO.AttRLDelUTRANSide
Radio Link Deletion Response
Release
Release
SHO.SuccRLDelUTRANSide
serving drift drift
sRNC dRNC dNodeB Iur Iub Uu UE
Radio Link Addition Request
Soft Handover: Radio Link Addition and Deletion simultaneously (3G TS 25.331, 25.433)
Setup
Setup
p
Start RX
A ti S t U d t Li k D l ti / Additi
DCCH
Downlink Synchronization
Uplink Synchronization
Start TX
Active Set Update: Link Deletion/ Addition
Deactivate old DL branch
Activate new DL branch
p
Release
serving drift drift serving
sRNC dRNC dNodeB Uu sNodeB UE
Backward Hard Handover
RNC t ll d RNC controlled
CN controlled
Hard Handover via Iur-i/f (3GTS 25.331)
Setup
Physical Channel Reconfiguration
DCCH
Setup
Physical Channel Reconfiguration Complete
y g p
Release
Release
serving target target source source
sRNC RNC Node B RNC Node B UE
Hard Handover via Iur-i/f, unsuccessful case (3G TS 25.331)
Setup
DCCH
Setup
Physical Channel Reconfiguration Failure
Radio Link Failure Indication
y g
Release
Release
serving target target source source
sRNC RNC Node B RNC Node B UE
i t t
Hard Handover cases (3G TS 25.331)
serving source target
Soft HO
Hard HO
source target
Hard HO
traget source
Soft HO
Hard HO
RNC RNC RNC
Relocation Required Trelocprep
Hard Handover with switching in the CN: UE connected to two CN nodes (3G TS 25.331)
Relocation Request
Treloccalloc Treloccalloc
Relocation Request Acknowledge
Setup
DCCH
Relocation Command
Relocation Detect
Treloccompl Treloccompl
Trelocoverall
Relocation Complete
IU Release Command
Release Complete
ALCAP Data Transport
Radio Link Deletion
target source target source
Bearer Release
Release
CN RNC RNC CN Node B Node B UE
CPHY RL Setup R
Hard Handover with switching in the CN: UE connected to one CN nodes (3G TS 25.331)
CPHY-RL-Setup-R
CPHY-TrCH-Setup-R
CPHY-RL-Setup-CNF
DCCH
CPHY-TrCH-Setup-CNF
Start TX/RX
Relocation Command
CPHY-RL-Release-REQ
CPHY RL S t REQ
Stop old TX/RX
CPHY-RL-Setup-REQ
CPHY-Sync-IND
Start new TX/RX
CPHY-Sync-IND
Relocation Complete
Relocation Detect
Data Frame Synchronization
Relocation Complete
CN
RRC L1 RRC L1 RLC RRC
Forward Hard Handover
C ll U d t URA U d t Cell Update, URA Update
CCCH
Cell Update via Iur without SRNS Relocation (3G TS 25.331)
Uplink Signaling Transfer Indication
Cell Update
C-RNTI
UL message
Common Transport Channel
Resource Request
Cell Update Confirm
DCCH
Resource Response
Setup
p
RNTI Relocation Complete
R R l Resource Release
C-RNTI
serving target source
sRNC dRNC dRNC Iur Iub Uu UE
CCCH
Cell Update via Iur without SRNS Relocation with C-RNTI Relocation (3G TS 25.331)
Cell Update
new C-RNTI
UL message
Resource Request
Cell Update Confirm
DCCH
Resource Response
Setup
p
R R l Resource Release
old C-RNTI
serving target source
sRNC dRNC dRNC Iur Iub Uu UE
CCCH
Cell Update with SRNS Relocation (3G TS 25.331)
new C-RNTI
UL message
Relocation Required
Cell Update
CCCH
Relocation Request
CCCH
Relocation Command
Relocation Comit
Cell Update Confirm
RNTI R l ti C l t
DCCH
S-RNTI and new S-RNTI
SRNC-ID and new SRNS-ID
new C-RNTI
Relocation Complete
IU Release Command
Release
serving target
IU Release Complete
Release
CN sRNC RNC Iu Iur Uu UE
CCCH
Inter-RNS URA Update via Iur with SRNS Relocation (3G TS 25.331)
C-RNTI
UL message
Relocation Required
URA Update
CCCH
UL message
Relocation Request
URA Update Confirm
CCCH
Relocation Command
Relocation Comit
p
DCCH
S-RNTI and new S-RNTI
SRNC-ID and new SRNS-ID
Relocation Complete
IU Release Command
Release
serving target
IU Release Complete
CCCH
Inter-RNS URA Update via Iur without SRNS Relocation (3G TS 25.331)
C-RNTI
URA Update
CCCH
C-RNTI
UL message
URA Update Confirm
CCCH
Downlink Signaling Transfer Request
C-RNTI
UL message
p
DCCH
serving target
Inter-System Handover
F dt GSM From and to GSM
RRC BSSMAP RANAP
Handover from UTRAN to GSM (3G TS 25.331)
Prepare HO
Relocation Required
Prepare HO Response
HO Request Acknowledge
HO Request
Relocation Command
HO Command
DCCH
RRC
RR
HO Complete
HO Complete
HO Detect
Send End Signal Request Send End Signal Request
IU Release Command
Bearer Release
Send End Signal Response
IU Release Complete
MSC BSS RNC CN UE
RRC BSSMAP RANAP
Handover from GSM to UTRAN (3G TS 25.331)
Prepare HO
HO Required
Relocation Request
Relocation Request Ack
Bearer Setup
Prepare HO Response
Relocation Request Ack
HO Command
DCCH
RR
HO Command
HO Complete
Relocation Complete
Relocation Detect
RRC
Relocation Complete
Send End Signal Request
Clear Command
Send End Signal Response
Clear Complete
MSC BSS RNC CN UE
P k t S it h d Packet Switched
Handover Procedures Handover Procedures
SRNS Relocation with Iur-Interface (3GTS 23.060, 25.413, 29.060)
Relocation Request
Relocation Required
Forward
Relocation Request
old SGSN address C-plane (old SGSN-UE)
old SGSN GTP-TEID
Target ID of RNC, Transparent Container
MM and PDP Context
(GGSN address U-Plane,
NSAPI QoS, UL-TEID C-/U-plane etc.)
IP for U-plane
GTP-TEID for C-plane
Transparent Container
RAB ID =NSAPIv
Forward
Relocation Response
Relocation Command
Data
Forwarding
IP for U-plane
GTP-TEI D for C-plane
old SGSN address C-plane (new SGSN-UE)
new SGSN GTP-TEID
Target ID of RNC
RAB ID = NSAPI (GTP TEID IP)
Data forwarding timer
SRNS Context
Relocation Commit
Relocation Detect
Update PDP Context
Request
RNTI Reallocation
Forward DL Data
RAB ID = NSAPI (GTP-TEID, IP)
Copy of DL Data send
through (GTP) Iu to target RNC
GTP-U / PDCP PDU sequence #
Relocation Complete
Update PDP Context
Response
RNTI Reallocation Complete
Forward Relocation Forward Relocation
Complete
Forward Relocation
Complete Acknowledge
Iu Release Command
Iu Release Complete
serving target source old new
Bearer Release
GGSN RNC RNC UE SGSN SGSN
Access Stratum - Air Interface
G Nt DC G Nt DC
Control Plane
Signaling
User Plane
Information
Gc Nt DC
L3
Gc Nt DC
BCFE PNFE DCFE
TR Ack Unack
PDCP
RRC
Transfer Mode Entity (TME)
CRLC
BMC
TR Ack Unack
L2
CMAC
RLC
RLC
BCCH
PCCH DCCH CCCH
CTCH DTCH
MAC-b
CMAC
MAC-d C/sh MAC
MAC-p
BCH DCH
Ph i l L
CPHY
PHY
BCH
PCH CPCH RACH FACH
DCH
Physical Layer
L1
Annex: Use of Standards Docs
To follow high level call flows..use 24.008 (Core Network
protocols), and 25.331(RRC Protocol). Standards have
every contingency. In these standards, Messages and
information elements are given in different sections.
D fi iti f i di id l IE i th ti Definitions of individual IEs are in other section.
The mobile is in an idles state (locked on and BCH all
decodedandimplemented decoded and implemented.
24.008 5.2==>Mobile NAS requests CM Service Request
toRRC whichcausesRRC todoaseriesof actionstoget to RRC which causes RRC to do a series of actions to get
to a DC connect state.
25.331 8.1.3.2==>UE issues RRC Connection Request, q ,
with data cause, init. UE ident., init. UE capability Data
Layout 25.331 10. (RACH from UE to BTS/RNC)
Utran issues RRC Connection Setup 25.331 8.1.3.3 on p
FACH. Information sent to UE in 25.331 10.2.42. Values
needed to setup direct connection
UE changes to dedicated channel per 25.331 8.1.3.4
according to RB (radio bearer mapping info from previous)
UE d RRC CONNECTION SETUPCOMPLETE UE sends RRC CONNECTION SETUP COMPLETE
message over DCCH. (also 8.1.3.4)
ki i bilit i f t d db t .skippingsome capability info traded between
RRC/RRC
ActionbacktoCM IssuesCM ServiceRequest Backto Action back to CM. Issues CM Service Request. Back to
24.008
Useful URL and FTP Sites Useful URL and FTP Sites
https://mcscn.siemens.at/umts/
https://ims.icn.siemens.de/
3GUMTS FDD 3G UMTS - FDD
Handover Procedures
Specifications
3GPP TS 10.89/50.089 GSM to other Systems Handover and Cell Selection/Reselection
3GPP TS 03.09/23.09 Handover procedures
3GPP TS 22.129 Handover requirements between UTRAN and GERAN or other radio systems
3GPP TS 25.841 DSCH power control improvement in soft handover
3GPP TS 25.832 Manifestations of Handover and SRNS relocation
3GPP TS 25.936 Handover for real-time services from PS-domain
3GPP TS 25.922 Radio Resource Management Strategies
3GPP TS 25.936 Handover for realtime services from PS-domain
3GPP TS 25.849 DSCH power control improvement in soft handover
3GPP TS 33.108 3G security: Handover interface for Lawful Interception (LI)
Intra-Frequency Handover
Active Set (AS)
The UE is communication via Radio Links (RL) towards the UTRAN.
A Radio Link describes all necessary parameter (PhCH, TrCH, LoCH) to make that communication working.
The UE may have multiple RL at the same time. In UL, the RLs will have the same parameters (like SC, CC),
where in DL different parameters are applied. The DL-RL may come from the same sector, cell, Node B, RNC
or from different one in any combination.
The Active Set contains this RLs which are currently in use.
One new RL is established between UE-UTRAN and therefore inserted to the active set.
Link Addition
One RL is released between UE-UTRAN and therefore removed from the the active set.
Link Deletion
One RL out of the active set is deleted and a new RL is added at the same time.
Link Replacement
Active Set Size (ASS)
TheASSmaychangeablecell or RNC wide The ASS may changeable cell or RNC wide.
Question: what happens in case on cell has ASS =2 and the other ASS =3? How to select? The highest?
The same applies for O&M parameter restricting HO execution, like ISHO allowed in one cell, but in another not.
How to decide? If it is allowed in at least one cell than its allowed?
Field trials showed that increasing ASS will not improve quality significantly.
This is also different for cs- and ps-Services.
Capacity planning has to proper calculate the needed channel element resources any additional link in AS
during soft handover.
maxASS for CS-Service =3
maxASS for CS-Service =2
Proposal
Intra-Frequency Handover Algorithm (3G TS 25.922, Siemens)
Q
meas
CPICH 1
TTT
1A
TTT
1C
TTT
1B
R
1A
-H
1A
H
1C
R
1B
+H
1B
R
1B
time
CPICH 2
CPICH 3
1B
time
Report 1A Report 1C Start 1A,1B,1C
AddCell 2 AddCell 3
Report 1B
RemoveCell 3 Add Cell 2 Add Cell 3
Remove Cell 1
Remove Cell 3
ActiveSet Cell 1 Cell 1 2 Cell 2 3 Cell 2 Active Set Cell 1 Cell 1, 2 Cell 2, 3 Cell 2
R : Replacement threshold
H : Hysteresis
TTT : TimetoTrigger TTT : Time to Trigger
(condition has to be fulfilled for that time before event will be reported)
Inter FrequencyHandover Inter-Frequency Handover
(IFHO) ( )
Inter-Frequency Handover (IFHO) (Siemens)
Blind handover Intra RNC - Intra Node B Intra Antenna
Without neighbour cell measurements the RNC may decide to send the UE to a new cell one the other frequency
based on the adjacent cells configured by O&M.
Applicable when target cell is within the Node B of the source cell (and same antenna configuration is used).
The internal information of frame offsets between cells is used to calculate the necessary information
to provide frame and chip offset for the new radio links.
Timing maintained handover Intra RNC - Inter Node B, Intra RNC - Intra Node B
TheRNC must chose a new value for DOFF, calculate frame and chip offset andestablishanewRL
Timing re-initialised handover Inter RNC
The RNC must chose a new value for DOFF, calculate frame and chip offset and establish a new RL
with NBAP or if necessary with RNSAP.
The received neighbouring cell info, either in the RL Setup Response or internally, is stored.
The RNC provides the DOFF value to the UE and sets the IE Timing Indication to initialise to force the UE
tocalculateanewCFN after readingthenewSFN. to calculate a new CFN after reading the new SFN.
The number of radio links established on the new frequency layer depend on the latest measurement, q y y p ,
in case the measurement provides information to hand over into a new active set, this information can be used
to setup or add more than one radio link. If this information is not available only one radio link is established.
After establishing the common intra-frequency RRM more links would be added, using the common procedures.
Control of Compressed Frame Mode for Inter-Frequency Measurements (Siemens)
Inter-Frequency Measurements are activated using the RRC Measurement Control procedure.
After the start of the compressed mode operation, the UE will attempts to find and synchronise
to the IS-FDD cells given in the neighbour cell list, and will provide the required measurements reports.
The reporting can be event triggered or periodic using: Events 2D, which triggers activation of compressed
frame mode and start of 2A, 2B, 2A and Event 2F, which triggers deactivation of compressed frame mode.
While the UE is in compressed mode, the RNC shall update the list of IF-FDD neighbour cells stored
in the UE and the requested measurements stored in the UE every time the active set is updated,
by sending subsequent measurement control messages.
FDDf
Q
meas
Inter-Frequency Handover (ISHO)
(Blind, timing maintained /
re-initialised)
FDD f
1
FDD f
2
FDD f
3
R 2D R 2F
time
Compressed Frame Mode
S 2D 2A 2B 2A Report 2D Report 2F
FDD <threshold FDD >threshold
Start 2D 2A, 2B, 2A
better frequency
current < threshold
other > threshold other > threshold
Inter SystemHandover Inter-System Handover
(ISHO) ( )
Inter-System Handover (ISHO) to UTRAN (Siemens)
UE Initiated Inter-System Cell Re-Selection PS forward
Will result in a RRC Connection establishment with a establishment cause Inter System cell re-selection,
which indicates that the former RAT was different to the current.
The relevant parameters for Inter-System cell reselection are given via GSM radio access network.
The Inter-System cell reselection is used for PS services only and is signalled by a RRC Connection Establishment
andfollowingNASsignalling
Network Initiated Inter-System Cell Change
and following NAS signalling.
PS backward
Will result in a RRC Connection establishment with a establishment cause Inter System Cell Change,
hi hi di t th t th f RAT diff t t th t which indicates that the former RAT was different to the current.
The relevant parameters for Inter-System cell reselection are given via GSM radio access network.
The Inter-System cell reselection is used for PS services only and is signalled by a RRC Connection Establishment
and following NAS signalling.
If a backward inter system HO is triggered by a RANAP procedure towards the target RNC,
the UE is configured with the RRC message HO To UTRAN. This RRC message is assembled in the target RNC
andsent viasignallingonRANAP(RRC information, target RNC tosourcesystem) totheoriginatingRAT
Inter-System Handover CS backward
and sent via signalling on RANAP (RRC information, target RNC to source system) to the originating RAT
and forwarded to the UE.
If the UTRAN receives a Handover To UTRAN Complete on a SRB in AM mode the inter system procedure
indicates the success to the originating entity.
The other RAT must request necessary UE capabilities from the UE before starting the HO To UTRAN
procedureinorder toprovidethenecessaryinformationtoset upciphering procedure in order to provide the necessary information to set up ciphering.
After establishing optional AS security, the RNC shall immediately invoke a UTRAN Mobility Information
procedure, in order to provide a complete S-RNTI to the UE and the UE timer and constants..
If the RNC receives an indication from the originating RAT that the HO failed, all radio resources shall be released.
Control of Compressed Frame Mode for Inter-System Measurements
used for Inter-System Handover (ISHO) (Siemens)
Inter-System (GSM) Measurements are activated using the RRC Measurement Control procedure.
to the GSM cells given in the neighbour cell list, and will provide the required measurements reports.
frame mode and start of 3A and Event 2F, which triggers deactivation of compressed frame mode.
While the UE is in compressed mode, the RNC shall update the list of GSM neighbour cells stored
Q
meas
Inter-System Handover (ISHO)
FDD
GSM A
GSM B GS
time
R 2D R 2F R 3A S 2D
GSM B >
GSM A
Report 2D Report 2F Report 3A Start 2D
Inter-System Cell Change (ISCC) (Siemens)
The purpose of the inter-RAT cell change order procedure is to transfer, under the control of the UTRAN,
a connection between the UE and UTRAN to a GSM/GPRS cell.
This procedure is applicable, when the established RABs are only from PS domain and
no signalling connection to the CS domain exists and Cell Change Order is allowed (O&M).
The service class may be used to differentiate the handling of different RABs.
(Best Effort will trigger Cell Change but Streaming no as GPRS doesnt support this service yet.)
The UE has to do the mapping between the PS RABs and the SAPI in GSM/GPRS and therefore to
re-establish the PDP contexts.
The cell order is purely coverage triggered, that means it has not been possible to keep the call in UMTS
but RNC has no knowledge of the capabilities of the target 2G system.
The UE can reject a cell change order with cause value "Unsupported Configuration",
if the UE believes that a service cannot be supported in GPRS.
The UTRAN related customer benefit is the reduction of connection interruption time due to inter-RAT
cell change If not applied thedatatransmissionsuffersonbadradioconditionsinUMTScoverageborder
Benefit
cell change. If not applied, the data transmission suffers on bad radio conditions in UMTS coverage border
cells until UTRAN and/or UE detects radio link failure condition. Afterwards UE requires additional time
to perform cell selection to a supplying GSM/GPRS cell. If the inter-RAT cell change order procedure is applied,
a RNC controlled cell change can be performed which minimises the interruption time.
ServicebasedHandover Service based Handover
(SBHO) ( )
Overview
The intention is to perform an Inter-System Handover to the GSM system based on actual used Service, p f y y ,
which is offered at GSM with the same quality as at UMTS (e.g. Speech) or for Services which are not yet
supported at UMTS (e.g. CS Data Services).
The UTRAN is aided in its decision to perform Service Based Handover by the Service Handover parameter p y p
received from the Core Node, indicating whether from the Core Nodes point of view,
the RAB in question should be transferred to GSM or not.
Di t d R t f UMTS t GSM CS
Whereby the RAB Assignment is rejected, using the cause value Directed Retry and
subsequently a Relocation Required message is sent also including the cause value Directed Retry
torequest anIntersystemHandover toGSM .
Directed Retry from UMTS to GSM CS
to request an Intersystem Handover to GSM .
Subsequent Inter-System Handover
The RAB may be accepted in the RNC and a subsequent Intersystem Handover is triggered,
f ll i f h UE
CS
following measurement reports from the UE.
Subsequent Inter-System Cell Change
TheRAB maybeacceptedintheRNC andasubsequent IntersystemHandover istriggered
PS
The RAB may be accepted in the RNC and a subsequent Intersystem Handover is triggered,
following measurement reports from the UE.
IE Service Handover
TheRNC will savethevalueof theServiceHandover parameter if received The RNC will save the value of the Service Handover parameter, if received,
with the RAB context for the duration of the RAB.
The actions of the RNC after receipt of a RANAP RAB Assignment Request will depend on:
- presence/valueof thereceivedIE presence/value of the received IE
- the RAB parameters
- current RNC load situation
- whether the UE already has an active RAB.
IE ServiceHandover
RAB Assignment Request
IE Service Handover
Handover to GSM should be performed
RAB should be handed over to GSM as soon as possible although the final
decision whether to perform a handover to GSM is still made in UTRAN
RAB shouldremaininUMTSaslongaspossiblealthoughthefinal decision
Handover to GSM shall not be performed
Handover to GSM should not be performed
RAB should remain in UMTS as long as possible although the final decision
whether to perform a handover to GSM is still made in UTRAN
RAB shall never be handed over to GSM.
This means that UTRANshall not initiate handover to GSM for the UE
unlesstheRABswiththisindicationhavefirst beenreleased unless the RABs with this indication have first been released
with the normal release procedures.
SBHO execution matrix (Siemens)
The table shows the actions of the RNC when a RAB Assignment request is received, with a particular Service Handover
parameter value(horizontal plane) against thecurrent RAB situationfor therelevant UE (vertical plane)
IE Service Handover
Handover to GSM
parameter value (horizontal plane) against the current RAB situation for the relevant UE (vertical plane).
shall not
be performed
should be performed
should not
be performed
Not present
Current RAB Situation
shall not
be performed
resource allocation
failure
RAB not
t d
SBHO triggered SBHO triggered RAB assignment RAB assignment No existing RAB
SBHO triggered SBHO triggered RAB assignment RAB assignment Existing PS RAB (IE Service HO not present)
RAB assignment
RAB assignment
supported
SBHOtriggered SBHOtriggered RAB assignment RAB assignment ExistingPSRAB ( shouldbeperformed) RAB assignment SBHO triggered SBHO triggered RAB assignment RAB assignment Existing PS RAB (.. should be performed) RAB assignment
SBHO triggered SBHO triggered RAB assignment RAB assignment Existing PS RAB (.. should not be performed) RAB assignment
RAB assignment RAB assignment RAB assignment RAB assignment Existing PS RAB (.. shall not be performed) RAB assignment
RAB assignment RAB assignment RAB assignment RAB assignment Existing CS RAB ( - any case - ) RAB assignment
Additional Trigger Condition:
Ser iceBasedHando er isallo edinat least onecell inthec rrentActi eSet or theSer ingCell (O&M data) Service Based Handover is allowed in at least one cell in the current Active Set or the Serving Cell (O&M data)
AND
At least one of the current Active Set has GSM neighbour(s) (in Cell_DCH state) or
the Serving Cell has GSM neighbour(s) (in Cell_FACH state)
SBHO special cases (Siemens)
It h ldb t fi bl h th SBHO b t i d h PS B t Eff t RAB It should be operator configurable whether SBHO can be triggered when a PS Best Effort RAB
is assigned to the UE. The resultant intersystem change will generally result in suspension of the
PS service in GPRS, unless the UE is also a Class A GPRS equipment.
It should be operator configurable whether SBHO can be triggered when a PS Streaming RAB
isassignedtotheUE ass chaRAB canc rrentl not bes pportedinGPRS is assigned to the UE as such a RAB can currently not be supported in GPRS.
In the case that there are multiple RABs, and one of those is a CS RAB not marked
Handover to GSM shall not be performed should the other RAB be released and Intersystem Handover
betriggeredwhilesendingaRAB ReleaseRequest messagetotheMSC withcausevalue be triggered while sending a RAB Release Request message to the MSC with cause value
Release due to UTRAN Generated Reason.
Service Based Handover may be triggered by load/service considerations when the Service Handover
parameter isset to Shouldnot behandedover toGSM parameter is set to Should not be handed over to GSM .
If the admission control function in the UMTS System rejects a RAB Assignment Request,
whose Service Handover parameter value is Should not be handed over to GSM,
or the requested RAB is not supported in the RNC, then Service Based Handover can still be triggered
inorder toavoidrejectingtheRAB in order to avoid rejecting the RAB.
It should be noted that this option is to be taken after all attempts to set up the RAB in the UTRAN have failed,
as the intention of the Service Handover parameter value Should not be handed over to GSM is that the RAB
should, where possible, remain in the UMTS world.
Thisoptionshouldbeoperator configurable This option should be operator configurable.
SBHO control by O&M (Siemens)
S it h th h l SBHOf ti lit ff ( ll b i )
Service Based Handover
Speech Service Based Handover
Directed Retry
Yes
N Di dR
RAB Request =Speech
will trigger Directed Retry +SBHO or
will leadtoRAB assignment beforeSBHO
Switches the whole SBHO functionality on or off (cell basis)
Service Based Handover Type
Blind
C dM d
SBHO will be based on Blind Handover or
on Inter-System Measurements
(applicable for Directed Retry and RAB assignment following SBHO)
No Directed Retry
will lead to RAB assignment before SBHO
Compressed Mode
( pp y g g )
Load Service Based Handover Yes / No
RAB Request not supported or rejected will trigger or will not trigger SBHO
Exception: Not possible if Compressed Mode is needed. (load reduction)
Existing Best Effort PS RAB Yes / No
Existing Streaming PS RAB Yes / No
will trigger or will not trigger SBHO if there is already a Best Effort PS RAB present
will trigger or will not trigger SBHO if there is already a Streaming PS RAB present
Timing Control of Inter-Frequency Measurements (Siemens)
Select first IS-Target Cell
Trigger ISHO
Event 3C with suitable cell
Trigger ISHO
Directed
Retry
Activate IF- Measurements
Start T
i
Expiry of T
InterMeasDirRetry
Trigger ISHO
RAB
Request
Trigger ISHO
time
Retry Start T
InterMeasDirRetry
Proceed Call
Request
Event 3C with suitable cell
Trigger ISHO
Activate IF- Measurements
Start T
InterMeas
Expiry of T
InterMeas
Deactivate IF- Measurements
RAB
Assignment
RAB
Request
time
T
InterMeasDirRetry
Start: After initiating Intersystem Measurements.
Stop: Reception of Measurement Report Event 3C indicating a suitable GSM Cell.
E i N it bl GSM ll h b f d ithth i i i dQ lit l l f il d i
T
InterMeas
Expiry: No suitable GSM cell has been found with the minimum required Quality level or on failure during
Compressed Mode activation. Select first target cell from the Adjacent GSM Cell list and trigger ISHO.
Start: After initiating Intersystem Measurements.
Stop: Reception of Measurement Report Event 3C indicating a suitable GSM Cell.
E pir St t ti d dth ll Expiry: Stop measurement reporting and proceed the call.
If the activation of Compressed mode fails the procedure ends.
ISHO Failure: If an attempted ISHO fails then the RNC will report this to the CN with the RANAP message
RelocationCancel stopanymeasurement reportingthat maybeactiveand will await further actionfromtheCN Relocation Cancel, stop any measurement reporting that may be active and will await further action from the CN.
SBHO and RRC states (3G TS 25.331, Siemens)
SBHO b t i di C ll FACH C ll DCH t t SBHO may be triggered in Cell_FACH or Cell_DCH state,
but the Uu message Handover from UTRAN Command can only be sent in Cell_DCH state.
[The procedure is initiated when UTRAN orders a UE in CELL_DCH state, to make a handover to a
radio access technology other than UTRAN, e.g. GSM. 3G TS 25.331v3.7.0]
Thus a state transition to Cell_DCH will be necessary.
This is applies regardless of whether Intersystem Measurements are required or using Blind HO.
TheCTSCCH to DCH sho ldbedoneeither beforetheinitiationof CompressedModeor The CTS CCH-to-DCH should be done either before the initiation of Compressed Mode or
before initiating Blind HO,
thus before the RANAP message Relocation Required is sent to the MSC.
Control of Compressed Frame Mode for Inter-System Measurements
used for Service Based Handover (SBHO) (Siemens)
Inter-System (GSM) Measurements are activated using the RRC Measurement Control procedure.
to the GSM cells given in the neighbour cell list, and will provide the required measurements reports.
frame mode and start of 3A and Event 2F, which triggers deactivation of compressed frame mode.
While the UE is in compressed mode, the RNC shall update the list of GSM neighbour cells stored
Q
meas
Service Based Handover (SBHO)
FDD
GSM A
GSM B GS
time
R 2D R 2F R 3C S 2D
GSM >
threshold
Report 2D Report 2F Report 3C Start 2D
IMSI basedHandover IMSI based Handover
(IBHO) ( )
UMTS Network Sharing
Operator A Operator B
HLR
PSTN PDN
HLR
PSTN PDN
HLR
GMSC GGSN
HLR
GMSC GGSN
MSC SGSN MSC SGSN MSC SGSN
BSC BSC RNC
BTS
GSM
BTS
GSM
Node B
UMTS
Network sharing based on Subscriber level, where there exists only subscriptions within existing GSM networks.
The UMTS network always handles subscribers as roaming subscribers (GSM-to-UMTS cell selection/handover).
In case of UMTS-to-GSM Handover the network shall tread the roaming subscriber in a ways that it would
find back to the originating network where it was coming from (national, international roaming). g g g ( , g)
Example of Heterogeneous PLMN environment at Country Borders
PLMN zE PLMN yC
PLMN D
II II
I I
PLMN yD
PLMN zF
II I PLMN xA PLMN xB
RAT =GSM
There are three countries indicated by MCC =x, y, z.
RAT =UMTS
y y
There are two operators having one mobile networks (RAT=GSM) in each country indicated by PLMN =
MCC +MNC where the MNC may different in each country: PLMN xA, xB; PLMN yC, yD; PLMN zE, zF.
There are roaming contracts between one operators out of each country or one operator is owning one networks
within each country (which is the same for the time being): Operator I (x) - Operator I (y) -Operator I (z) and
Operator II (x) - Operator II (y) -Operator II (z).
Goal: Optimal planning to allow international roaming between networks of Operator I and II respectively also
in case there is a subscriber which comes from a different country.
Goal: In-cooperate a new mobile network (RAT=UMTS) into one country, which can be used by subscribers
of both operators in that country and take care about the existing roaming relationships.
Example of Subscriber Movement through heterogeneous PLMN environment
Operator I (x) Operator II (x) Operator II (y) Operator I (y) Operator III (x)
RAT: GSM
PLMN xA
RAT:GSM
PLMN xB
RAT: UMTS
PLMN xZ
RAT:GSM
PLMN yD
RAT:GSM
PLMN yC
roaming
agreement
roaming
agreement
HPLMN xA HPLMN xB HPLMN yC
HPLMN yD
PLMN zF PLMN zE
The UMTS network in country x with PLMN xZ has neighbour cell relations towards cells from PLMN xA and xB
belonging to Operator I(x) and II(x).
Subscriber with HPLMN xA or xB enters the PLMN xZ (national roaming) which should be handed back
(if applicable) towardsPLMN xA or xB respectively (if applicable) towards PLMN xA or xB respectively.
Subscriber with HPLMN yC or yD (international roaming) may also enter the PLMN xZ and
should be handed back (if applicable) towards PLMN xA,yC,zE or xB,yD,zF respectively.
InthisexampleroamingagreementsexistsbetweenxA yC zE andxB yDzF respectively In this example roaming agreements exists between xA,yC,zE and xB,yD,zF respectively.
Subscriber Management in Idle Mode or Connected Mode (Cell_FACH)
TheCell Re-SelectionprocedureisusedduringIdleModeandConnectedMode(Cell FACH) The Cell ReSelection procedure is used during Idle Mode and Connected Mode (Cell_FACH).
The UMTS network is broadcasting Inter-System Neighbour Cells of all surrounding cells.
As the network doesnt has information about particular subscriber it cant differentiate which neighbour cell
would be an appropriated one in terms of roaming agreements.
GSM 4 GSM 6 GSM-4
PLMN yD
GSM-3
PLMN yC
GSM-5
PLMN zE
GSM-6
PLMN zF
UMTS
PLMN xZ
GSM-2
PLMN xB
GSM-1
PLMN xA
Subscriber Management in Connected Mode (Siemens)
The UMTS network is broadcasting only a sub-set of surrounding Inter-System Neighbour Cells. g y g y g
If the subscriber identity (IMSI sent with Common ID) is known than a filtering of allowed neighbour cells
can be applied. The handover trigger and execution is done as any Inter-System Handover (ISHO).
Inter-System
Complete
List Filter applicable
Subscriber IMSI
Filtered
List Inter System
y
Adjacent Cells
Configured by O&M
List Filter applicable
Adjacent Cells
List Inter-System
Measurement Control
PLMN IMSI
Mapping Table (MT)
White List
Black List
White List:
Subscriber found in one MT will get Neighbour Cell List belonging to the PLMNs in that MT.
Subscriber foundinbothMT will get Neighbour Cell List belongingtothePLMNsinbothMTsor randomisedfromonlyoneMT. Subscriber found in both MT will get Neighbour Cell List belonging to the PLMN s in both MT s or randomised from only one MT.
Subscriber not found in both MT will get Neighbour Cell List which is empty.
Black List:
Subscriber found in one MT will not get Neighbour Cells belonging to the PLMNs in that MT.
Subscriber found in both MT will not get Neighbour Cells belonging to the PLMNs in both MTs.
Subscriber not foundinbothMT will get acompleteNeighbour Cell List Subscriber not found in both MT will get a complete Neighbour Cell List.
Example on Mapping of PLMN and IMSI (Siemens)
Mapping Table for Operator I (MT I)
Identity Name
Reference Adjacent Cells (1..3)
PLMN xA
PLMN C
Reference Subscriber PLMN (1..256)
PLMN xA
PLMN C
t
o
r
m
e
O&M Adjacent Cell List
PLMN xA
PLMN yC
PLMN zE
GSM-1
GSM-3
GSM-5
O
p
e
r
a
t
o
r

I
PLMN yC
PLMN zE
PLMN yC
PLMN zE
v
i
s
i
t
h
o
m
PLMN HH
PLMN xB
PLMN yD
PLMNzF
N
GSM-2
GSM-4
GSM 6
GS 5
O
p
e
r
a
t
o
r

I
I
Mapping Table for Operator II (MT II)
PLMN zF GSM-6
O
Reference Adjacent Cells (1..3) Reference Subscriber PLMN (1..256)
PLMN xB
PLMN yD
o
a
m
i
n
g
h
o
m
e
PLMN xB
PLMN yD
PLMN ST GSM-7
PLMN TS GSM-8
PLMN zF
r
o
PLMN zF
E l
PLMN HH
Example:
Subscriber PLMN xA, which is found in MT I will get Neighbour Cell List belonging to PLMN xA,yC,zE. (white list filtering)
Subscriber PLMN HH, which is found in both MTs will Neighbour Cell List belonging to MT I =xA,yC,zE or MT II =xB,yD,zF
(which may randomised) or both [O&M option] in case of white list filtering. And cells belonging to PLMN ST,TS in case of
black list filtering. g
Subscriber PLMN OO, which is not found in both MTs, will get no Neighbour Cells (white list filtering) or all (black list filtering).
Hierarchical Cell Structure Hierarchical Cell Structure
(HCS) ( )
Macro-Macro : same coverage (Siemens)
Two cell layers on different frequencies have the same coverage.
Frequency 2
Cell 1 Cell 2
Cell 3 Cell 4
NodeB
Frequency 1
UE
Node B
The inter-frequency handovers are restricted to handovers from one frequency to a cell
of the other frequency where the path-loss relations and timing relations are known. q y p g
This is achieved by performing handover to a cell that lies on the same antenna as a cell of the active set (solid)
or failing that, a cell on the same Node B as the active cell (dashed).
Since handover is performed to a cell on the same antenna, the UE stays on the same Node B.
This means IFHO over Iur will not occur.
The target cell for this kind of inter-frequency handover is determined by using the antenna data in
O&M for each cell. This means the handover occurs blindly, i.e. without measurement information.
For this reason, inter-frequency measurements and compressed mode are not required.
Macro-Macro : same coverage (Siemens)
Two cell layers on different frequencies have the same coverage.
Frequency 3 Frequency 2
Cell 1 Cell 2
Cell 3 Cell 4
Cell 1 Cell 2
Cell 3 Cell 4
Frequency 1
UE
Node B Node B
Handover to another cell of a different frequency residing on a different antenna, where the path-loss and
timing relations are not known. This kind of handover is possible with the introduction of inter-frequency
measurements. The target cell may connect to the same Node B (Inter RNC - Inter Node B - Intra Antenna)
using blind handover, the same RNC (Intra RNC - Inter Node B) using time maintained handover or
to a different RNC (Inter RNC - Inter Node B) using timing re-initialised handover.
There could also be more than 2 different frequencies.
HCS Scenarios (Siemens)
Macro-Macro (different coverage): Two cell layers on different frequencies which have different coverage, where the cell size is equal.
Frequency 2
F 1 Frequency 1
Macro-Micro: Twocell layersondifferent frequencieswhichhavedifferent coverage wherealsothecell sizeisdifferent Macro-Micro: Two cell layers on different frequencies which have different coverage, where also the cell size is different.
Frequency 2
Frequency 1
Mixed: Multiple cell layers on different frequencies which have different coverage, where also the cell size is different. ed: u pece yeso d ee eque c esw c ved ee cove ge, w ee so ece s e sd ee .
Frequency 3
Frequency 1
Frequency 2
Handover Triggers for HCS
The reasons for performing inter-frequency handover in a HCS environment are:
- lack of coverage
- adjacent cell interference
- Cell capacity: Load Overflow, Load Balancing, Service Segregation
UE iti / d - UE position/speed
Lack of Coverage (Siemens)
IFHOi HCS i t h th UE t f it t f IFHO in a HCS environment can occur when the UE moves out of coverage on its current frequency.
This can happen if it is in a coverage gap or has reached the boundary of current frequency coverage.
Frequency 3
F 2
Frequency 1
Frequency 2
Adjacent Cell Interference (ACI) (Siemens)
In a HCS scenario it may occur that a UE connected to a cell of one frequency layer experiences increasing y q y y p g
interference by a cell of a different frequency layer it is closely passing.
Performing a handover to a different frequency can reduce this interference.
Micro Cell
Frequency 2
M C ll Macro Cell
Frequency 1
Load Overflow Mechanism (Siemens)
Traffic overflow from frequency 1 to frequency 2 occurs when a cell in frequency layer 1 is completely filled.
Overflow mechanism determines only the sequence of the resource allocation requests within the corresponding cells.
This scheme is mandatory for the micro/macro scenario, because it provides the maximum system utilisation
(lowest blocking probability) if an overflow from the micro to the macro cell layer is performed.
This is due to the fact that the macro cell is only loaded in those areas where the micro cell layer has
not enough capacity to cope with the traffic demand.
Frequency 2
Frequency 1
heavy loaded cell
This scheme might be also useful macro/macro scenarios with identical coverage:
- To improve coverage in the lightly loaded cell due to a lower interference level in that cell.
Therefore thehighlyloadedcell servesthoseUEswhichareclosetotheantennawhereasthecell withthe Therefore, the highly loaded cell serves those UEs which are close to the antenna whereas the cell with the
lower load is reserved for users at the border of the coverage area.
- The overflow principle provides a better pooling of resources and reduces the blocking probability for
high bit rate bearers, because the spare capacity in the overflow layer is maximised.
Load Balancing Mechanism (Siemens)
The load of the cells in different frequency layers will be balanced.
This scheme is only applied in the macro/macro scenario.
It has the advantage, that both frequency layers have identical coverage and no coverage triggered handover occurs
(if load is defined by the interference and power level within the system).
Frequency 2
medium loaded cell
Frequency 1
The load will be evaluated by the admission control function depending on the interference and power levels within
the system (soft capacity). The load balancing procedure tries to balance the uplink and downlink loads of
all frequencies to achieve a similar coverage for all frequencies and all link directions (uplink and downlink). g
Hence, for the case of two different frequencies, the following selection mechanism can be defined:
LOAD
*
= | o Determine DL and UL Load for Frequency Layer 1 and 2
) LOAD , LOAD max( ) LOAD , LOAD max(
) LOAD , LOAD max( ) LOAD , LOAD max(
frequency2 DL, frequency2 UL, frequency1 DL, frequency1 UL,
frequency2 DL, frequency2 UL, frequency1 DL, frequency1 UL,
>
<
Select frequency 2
Select frequency 1
Measurements for Handover
Measurements for Handover
Event Triggered Measurement Reports
The Measurement Algorithm is employed in the mobile.
As long as the Measurement parameters (for HO) are transmitted correctly from UTRAN to the mobile
it is absolutely up to the mobile what (measurement accuracy) and when (precise trigger moment) to trigger the HO.
The Measurement Algorithm is employed in the mobile.
AslongastheMeas rement parameters(for HO) aretransmittedcorrectl fromUTRAN tothemobile
Periodical Reported Measurement Reports
As long as the Measurement parameters (for HO) are transmitted correctly from UTRAN to the mobile
it is absolutely up to the mobile what (measurement accuracy) to report to UTRAN.
The UTRAN gets the measurements in a regularly interval and will have to make HO trigger decision by its own,
but is impacting when (precise trigger moment) to trigger the HO.
Measurement Calculation
Measurement Report 1A
( ) ) ( log 1 log 10 log 10
1a best
N
i
i new
H R M W M W M
A
+ +
|
|
.
|
\
|
>

+for Pathloss
- for all other Q-meas
R : Reporting Range
H
1a
: virtual offset/hysteresis
W : weighting of best/all Cells
M
best
: best Cell within Active Set
ll ( ) C ll i hi A i S
Measurement Report 1B
M
i
: all (N
A
) Cells within Active Set
M
new
: new Cell not within Active Set
R : Reporting Range
H
1b
W : weighting of best/all Cells
M
best
: best Cell within Active Set
M
i
: all (N
A
) Cells within Active Set
M : Cell leavingtheActiveSet
( ) ) ( log 1 log 10 log 10
1b best
N
i
i old
H R M W M W M
A
+ +
|
|
.
|
\
|
s

+for Pathloss
Measurement Report 1C
M
old
: Cell leaving the Active Set
R: ActiveSet Threshold
) log 10 log 10
repl new old
H M M s
R : Active Set Threshold
H
repl
M
old
: Cell leaving the Active Set
M
new
: Cell entering the Active Set
Impact of Measurement Parameter (Example Event 1A, 1B)
N
|
|
|
+for Pathloss
) ( log 1 log 10 log 10 H R
best
M W
A
N
i
i
M W
new
M + +
> |
.
|
\
|
|
|
|
|
|
.
|
\
|
Weighting (W)
W >0
W =0 The observed Cell is evaluated against the best Cell only
The observed Cell is evaluated against all Cells in the Active Set. W >0
ReportingRange(R)
Hysteresis (H)
Reporting Range (R)
The reporting range is defined relative to the best Cell or/and all Cells in the active Set.
The Hysteresis is defined as additional offset parameter,
where an event is not reported until the difference is equal to the hysteresis value.
Time-to-Trigger (TTT)
The trigger has to enter the reporting range but has to stay there for a certain time:
Time-to-Trigger or the Time it needs that the conditions of the hysteresis is fulfilled.
TTT and H are different mechanism with the same purpose: to avoide successive trigger of the same event
The trigger has to be fulfilled for a certain time to become valid.
TTT and H are different mechanism with the same purpose: to avoide successive trigger of the same event.
Simultaneous Measurement Control (Siemens)
At RRC connection establishment on DCH, RRC connection re-establishment, CTS CCH-to-DCH,
H dH d dS f H d i b i d i l l Hard Handover and Soft Handover it may be required to simultaneously start measurement events:
2D for IFHO and 2D for ISHO.
The order in which they are started can be obtained using the parameter threshold used frequency:
IF
"Threshold used frequency" for event 2D (IFHO) >="Threshold used frequency" for event 2D (ISHO)
THEN
St t t t 2D(IFHO) fi t th t t t t 2D(ISHO) Start measurement event 2D (IFHO) first, then start measurement event 2D (ISHO)
ELSE
Start measurement event 2D (ISHO) first, then start measurement event 2D (IFHO)
If th UE t t t "M lti l 2DS t" i FALSE th th b h k till li b t l If the UE context parameter "Multiple 2D Support" is FALSE then the above check still applies but only
the first measurement is started, e.g. if it is determined that 2D (IFHO) is to be started first followed
by 2D (ISHO) then only 2D (IFHO) will be started in this case, and visa versa.
Measurements for HO (Siemens)
Event 1A,1B,1C started when adjacent Intra-Frequency Cells exists and HO is allowed.
1A
1B
1C
Trigger for RL addition
Trigger for RL removal
Trigger for RL replacement
cell > threshold
cell < threshold
cell x+1 better cell x
H
O
1C Trigger for RL replacement cell x+1 better cell x
Measurements for ISHO, SBHO and IFHO (Siemens)
Event IS-2D started when adjacent IS-Cell exists and HO is allowed. UE Capability
2D
2F
3A
Trigger for activation of Compressed Frame Mode and 3A or 3C
Trigger for deactivation of Compressed Frame Mode and 3A or 3C
Trigger for ISHO
UTRAN < threshold
UTRAN > threshold
GSMbetter cell
I
S
H
O
Multiple 2D support
3A Trigger for ISHO GSM better cell
3C Trigger for SBHO GSM > threshold
Event Event 2D started when adjacent IF-Cell exists and handover is allowed.
2D
Blind Handover when adjacent IF-Cell on same antenna. One re-try.
Trigger for activation of Compressed Frame Mode FDD Measurement Report UTRAN < threshold
Multiple 2D support
2F
I
F
H
O
and 2A, 2B, 2A,2F
Trigger for deactivation of Compressed Frame Mode
Deactivation 2A, 2A, 2B,2F
Multiple 2A support
2A
If reportedfrequencydiffersfromthecurrent one.
UTRAN > threshold
better frequency
2B
2A
2A
Determine target IF-Cell. Trigger IFHO.
One re-try for second best IF-Cell.
If reported frequency differs from the current one.
Determine target IF-Cell. Execute IFHO. No re-try. On IFHO-Failure
and 2A if target IF-Cell was next to current, call release.
better frequency
better frequency
current < threshold
other > threshold
Handling of compressed mode for inter-system measurements and for inter-frequency measurements at same time,
would require handling of simultaneous IS and IF compressed mode patterns. woud equ e a d go s uta eous Sa d co p essed odepatte s.
CPCHprinciple CPCH principle
AP-AICH CD-ICH
DPCCH (DL)
T
a
APs
CD
Power Control, Pilot and CPCH
control commands
t
p-a1
t
a1-cdp
t
cdp-a2
[Example shown is for Tcpch =0]
P0
P1 P1
PCPCH (UL)
0 or 8 slots
Power Control
Preamble
Information
and
t
p-p
t
p-cdp
t
cdp-pcp
and
Control Data
What is RACH
Transport Channel Physical Channel
Transport-to-Physical Channel Mapping
DCH
p y
DPDCH
DPCCH
RACH
CPCH
PRACH
PCPCH
CPICH CPICH
P-CCPCH
S-CCPCH
BCH
FACH
SCH
PDSCH
PCH
DSCH
AICH
PICH
Non Access Stratum(NAS)
Consist of the following Sub-Layers:
Mobility Management (MM Layer) :
Consist of MM & GMM
Call Management (CM Layer) :
Consist of CC & SM Consist of CC & SM
Mobile Network (MN Layer)
A ti t f ll t l ibl f i iti ti Active part of call control, responsible for initiating
CM layer functionality as a result of local events
suchasuser initiatingacall. such as user initiating a call.
RACH procedure
Case of RACH Access failures (MAC level)
No positive ACK received:
All Power Ramping ended by an undetected preamble
All Power Ramping ended by the reception of a NACK
Mix of both reasons
Positive ACK received but:
Corrupted message (bad CRC)
Collisions (2 messages sent with the same signature exactly at the
sametime) same time)
RACH procedure
Access procedure at MAC level and PHY
level
1 RACH access at MAC level =
up to M_max successive Power Ramping cycles
+ 1 RACH message (if one preamble has finally been acknowledged)
1 Power Ramping Cycle at PHY level
= up to Preamble Retrans Max preambles
retransmissions
Power offset
preamble
.
.
Control part (DPCCH)
Data part (DPDCH)
Preamble Init power is
fixed by Open Loop
Power Control at each
new Ramping cycle
Total power
of the RACH
Message
message
Preamble Power
Ramping step
At least
3 or 4 access slots
Persistency delay
3 or 4 access slots Backoff Timer
+ Persistency delay
A Positive Acquisition Indicator is sent by
the BTS when a preamble has been detected
and hardware resources are available to
demodulate the RACH message
A
C
K
N
A
C
Case where no preamble has
been detected by the BTS
K
A Negative Acquisition Indicator is sent by
the BTS when a preamble has been detected
but no hardware resources are available to
Mobility Management (MM)
Consist of the following CS functions :
IMSI attach/detach procedure,
HandlenetworkinitiatedTMSI reallocation, Handle network initiated TMSI reallocation,
authentication and identification procedures,
Locationupdatingprocedures Location updating procedures,
MM Connection management procedures.
GPRSMobilityManagement GPRS Mobility Management
(GMM) (GMM)
Consist of the following PS functions :
Handle network initiated P-TMSI re-
allocation, GPRS authentication and ciphering, , p g,
GPRS identification,
GPRSattach/detachprocedures, GPRS attach/detach procedures,
Routing area updating.
C ll Call Management
Support the CC (Call Control) & SM
(SessionManagement) Their functionis: (Session Management). Their function is :
Establish, maintain and terminate CS
ti i CC f GPRS i connection ie. CC for non-GPRS services,
SMS for non-GPRS and GPRS services,
GSMS Support (GSMS)
SM for Packet Switchedcalls, SM for Packet Switched calls,
Supplementary Services Support (SS) for non-
GPRSservices GPRS services.
Mobile Network (MN)
Its function is :
Active part of call control, responsible for
initiating CM layer functionality as a result of g y y
local events such as user initiating a call.
Adaptation Layer (ADP)
Provide the following services :
Mapping of MM/GMM (GSM) primitives and
their parameters to RRC primitives and vice- p p
versa,
Simulate/terminatenon-mappedprimitives. Simulate/terminate non mapped primitives.
MTE Protocol Layers & Interfaces ooco yes& e ces
Mobile Network (MN)
SNSM
SMREG MNSMS MNCC MNSS
N
o
n
GMMSM MMSS
GMMREG
Connection Management
GMMAA GMMSMS MMSMS MMCC
n
-
A
c
c
e
s
s

S
t
r
a
t
u
m
L
a
y
e
r

3
Mobility Management Sublayer
LLGMM GMMRR RR
LLSMS
Radio Resource Control (RRC)
GC NT DC
p y ( )
User Plane
Services
L
a
y
e
r

2Radio Link Control (RLC)
TR UM AM
BCCH PCCH DCCH CCCH DTCH
A
c
c
e
s
s

S
t
r
a
t
u C
o
n
t
r
o
l
TR / UM / AM
a
y
e
r

1
Medium Access Control (MAC)
BCH PCH RACH FACH DCH
u
m
L
a
Physical (PHY)
RACH procedure
Case of RACH Access failures (MAC level)
No positive ACK received:
All Power Ramping ended by an undetected preamble
All Power Ramping ended by the reception of a NACK
Mix of both reasons
Positive ACK received but:
Corrupted message (bad CRC)
Collisions (2 messages sent with the same signature exactly at the
sametime) same time)
Mobile Network (MN)
SNSM
SMREG MNSMS MNCC MNSS
N
o
n
GMMSM MMSS
GMMREG
Connection Management
GMMAA GMMSMS MMSMS MMCC
n
-
A
c
c
e
s
s

S
t
r
a
t
u
m
L
a
y
e
r

3
Mobility Management Sublayer
LLGMM GMMRR RR
LLSMS
Radio Resource Control (RRC)
GC NT DC
p y ( )
User Plane
Services
L
a
y
e
r

2Radio Link Control (RLC)
TR UM AM
BCCH PCCH DCCH CCCH DTCH
A
c
c
e
s
s

S
t
r
a
t
u C
o
n
t
r
o
l
TR / UM / AM
a
y
e
r

1
Medium Access Control (MAC)
BCH PCH RACH FACH DCH
u
m
L
a
Physical (PHY)
PART 3
SAP linkage example: CCCH (UE context)
CCCH Frames to/from the BSC RRC
RRC
RLC Connections
RLC
RLC
MAC
Logical Channels
CCCH
MAC
PHY-u
FP
RELAY
MAC
CCCH
Transport Channels
FACH (DL) / RACH(UL)
FP
ATM
FP
PHY
ATM
PHY
SCCPCH(DL) / PRACH (UL)
Physical Channels
Radio Resource Control (RRC) - Attributes ( )
BSC entity
RAB RAB management
RR Management
Connection mobility
Call AdmissionControl Call Admission Control
Handover
P i d tifi ti Paging and notification
Closed loop power control
Ciphering control
Measurement control Measurement control
RadioLinkControl (RLC) Attributes Radio Link Control (RLC) - Attributes
TPU entity TPU entity
Transparent data transfer service with SAR
Unacknowledged data transfer service with SAR
and concatenation
Acknowledged data transfer service with SAR,
concatenation, error correction, PDU sequencing,
duplicate detection and flow control
di i k l ( ) d l Radio Link Control (RLC) - Model
UM/AM SAP Tr SAP
Transparent
SAR SAR and concatenation
Add/Remove RLC header
Unacknowledged Acknowledged
MUX
Transmission buffer Transmission buffer Retransmission buffer
Transmission buffer
BCCH,PCCH,
CCCH DTCH
DCCH,DTCH DCCH,DTCH
CCCH,DTCH
Medium Access Control (MAC) - Attributes
TPU entity
Mapslogical channelstotransport channels Maps logical channels to transport channels
Selects transport format for transport channels
Schedules PDUs
Mux/Demux of higher layer PDUs
Traffic volume monitoring
Dynamictransport channel typeswitching Dynamic transport channel type switching
MAC-c handles common logical channel (CCCH) and
t t h l (RACHFACH) common transport channels (RACH,FACH)
MAC-d handles dedicated logical channels (DCCH,DTCH)
and dedicated transport channel (DCH)
Medium Access Control (MAC) - Model
DCCH CCCH DTCH DTCH
MAC Control
DL:TF
Selection
DL:TFC Selection
MAC
MAC d
DCH FACH RACH DCH DCH
MAC-c
MAC-d
PHY upper PHY-upper
Frameselection/distribution Frame selection/distribution
Frame synchronisation
Open-loop power control (lower level)
Outer-loop power control BER/SER estimate Target Eb/I0
Frame selection & distribution Frame quality Best frame
Frame synchronization Early/late arrival Timing command

UMTS Training Course Overview

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

UMTS Training Course Overview

Uploaded by

Copyright:

Available Formats

UMTSTrainingCourse UMTS Training Course

Prepared & presented by

Replace Cell 1 with Cell 3

Automatic restriction control is applied by the RNC, by

Manual restriction is applied by the OMC/LMT by

You might also like