Utran Protocols

UMTS T
Terrestrial
t i l Radio
R di Access
A
Network (UTRAN)
• UMTS Terrestrial Radio Access (UTRA)

• UTRAN Architecture
A hit t and
d Protocols
P t l
• UTRAN Procedures (see separate presentation)
Important References
Books:
• Kaaranen, Ahtiainen, Laitinen, Naghian, Niemi: UMTS Networks –
Architecture, Mobility and Services. 2nd edition, Wiley, 2005
• Holma, Toskala: WCDMA for UMTS. 4th edition, Wiley, 2007
• Walke,
Walke Althoff,
Althoff Seidenberg: UMTS – Ein Kurs.
Kurs 2.
2 Auflage,
Auflage J.
J Schlembach
Fachverlag, 2002
• T. Benkner, C. Stepping: UMTS – Universal Mobile Telecommunications
System. J. Schelmbach Fachverlag, 2002.
Central 3GPP Documents on UTRAN:

• 25.401: UTRAN overview
• 25.301: Radio link protocols (UTRA)
• 25.931: UTRAN procedures
UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 2

UTRAN Architecture
• Components and Interfaces

• Macro Diversity
• UTRAN Functions
• Protocol Architecture
• RRC connection and signaling connection
• Access Stratum and Non Access Stratum

UTRAN Components and Interfaces
Core Network
Iu Iu
RNS RNS
UTRAN
Iur
RNC RNC
Iub Iub Iub Iub
Node B Node B Node B Node B
A Radio Network Subsystem (RNS) consists of a RNC, one or more Node B‘s and
optionally
ti ll one SAS (standalone
( t d l A-GPS
A GPS serving
i mobile
bil llocation
ti center)
t )
Source: 3GPP 25.401

Macro Diversity:
Serving
Se g and
a d Driftt RNS
S Source: 3GPP 25.401
C o r e N e tw o r k
Iu
D r if t R N S ( D R N S ) S e r v in g R N S ( S R N S )
Iu r
C e l ls
UE
Each RNS is responsible for the resources of its set of cells

For each connection between User Equipment (UE) and the UTRAN
UTRAN, one RNS is the
Serving RNS (SRNS)
Drift RNSs (DRNS) support the Serving RNS by providing radio resources
Macro-diversity and handover is supported by Node B and RNC

Serving, Drift and Controlling RNC
Core Network
Iu Iu
RNS RNS
UTRAN
Iur
DRNC
RNC RNCSRNC
Ib
Iub Iub Iub Iub
Soft handover:
Softer handover: radio frame selection (layer 1)
UE
maximum ratio combining in SRNC (and DRNC)
in Node B
Roles of RNSs/RNCs Source: 3GPP 21.905
Serving
S i RNS (SRNS)
• A role an RNS can take with respect to a specific connection between a UE and
UTRAN
• There
Th is
i one Serving
S i RNS for f each h UE that
th t hhas a connection
ti tot UTRAN
• The Serving RNS is in charge of the RRC connection between a UE and the
UTRAN
• The
Th Serving
S i RNS terminates
t i t ththe IIu for
f thithis UE
Drift RNS (DRNS)
• A role an RNS can take with respect
p to a specific
p connection between a UE and
UTRAN
• An RNS that supports the Serving RNS with radio resources when the
connection between the UTRAN and the UE need to use cell(s) controlled by this
RNS
Controlling RNC (CRNC)
• A role an RNC can take with respect to a specific set of UTRAN access points (an
UTRAN access point is specific to a cell)
• Exactly one Controlling RNC serves an UTRAN access point (i.e. each cell)
• Thee Controlling
Co t o g RNC C has
as tthe
eooverall
e a cocontrol
t o of
o the
t e logical
og ca resources
esou ces o
of its
ts U
UTRAN
access points

Distribution of Functions between
RNCs
Radio resource management:
• CRNC owns the radio resources of a cell
• SRNC handles the connection (RRC/RANAP) to one UE, and may
borrow radio resources of a certain cell from the CRNC
• SRNC performs dynamical control of power for dedicated channels
channels,
within limits admitted by CRNC
Inner loop power control for some radio links of the UE connection may be
done by the Node B
Inner loop control is controlled by an outer loop, for which the SRNC has
overall responsibility
• SRNC handles scheduling of data for dedicated channels
• CRNC handles scheduling of data for common channels (no macro
diversity on DL common channels)
Source: 3GPP 25.401, Ch 6.3

Serving, Drift and Controlling RNC
Core Network
Iu Iu
RNS RNS
UTRAN
Iur
DRNC
RNC RNCSRNC
SRNC
Ib
Iub Iub Iub Iub
common/ shared dedicated channel in

channel
macro-diversity mode
UE 2 UE 1

Serving and Controlling RNC
Example: DCH (UL&DL macro diversity)
Combining/
DTCH DCCH splitting of DCCH DTCH
phy. channels
MAC-d MAC-d
PHY-upper PHY PHY

DchFP DchFP DchFP DchFP
AAL2 AAL2 AAL2 AAL2

PHY PHY
ATM ATM ATM ATM
UE Uu NodeB Iub CRNC Iur SRNC
cells served cells served cells served

by the same by the same by different
node B CRNC RNCs
(optional)
Combining/splitting is supported for DCH only
(no layer 2 processing in Node B and DRNC)
Source: 3GPP 25.401, sc 11.2.4 (see also 25.301, sc 5.6.1)
Serving and Controlling RNC
Example: FACH (DL, no macro diversity)
DTCH DCCH DCCH DTCH
CCCH CCCH
MAC-d
MAC-d
MAC-c/sh MAC-c/sh
FachFP FachFP
FachFP FachFP
AAL2 AAL2 AAL2 AAL2

PHY PHY
ATM ATM ATM ATM
Physical channel is terminated within node B (no support for combining/splitting)

Common MAC (MAC-c/sh) terminates in the CRNC
Dedicated MAC ((MAC-d)) terminates in the SRNC
Source: 3GPP 25.401, sc 11.2.3 (see also 25.301, sc 5.6.2)

Example: BCH
RRC
RRC
RRC
RLC RLC
MAC MAC
PHY PHY
UE NodeB CRNC
RRC terminates in
• CRNC: provides broadcast information distributed by node B
• Node B: handles periodic repetition of broadcast information
Splitting of RRC eliminates repetition of broadcast data on Iub interface
Source: 3GPP 25.301, sc 5.6.7

UTRAN Architecture: Functional Split
Control plane CRNC/DRNC SRNC
Mobile Core
Control Network
Cell Control
P i
Paging
Node-B
Broadcast
Com./ Shared
Channel
Processing
Dedicated
Channel
Processing
Bearer plane

UTRAN Protocol Architecture: Summary
Core Network
paging (idle) Iu paging (connected) Iu

Iub Iur
Node-B CRNC RANAP SABP SRNC RANAP Iu-PS Iu-CS
DRNC FP FP
BM-IWF paging
R (connected
(connected, R
N N N PCCH) N
B B S S
RRC-b RRC-c/sh RRC-d
A A A A
P P P P
BMC PDCP
RLC-b RLC-c/sh RLC-d

LOGICAL
CHANNELS BCCH PCCH CCCH CTCH DCCH DTCH
BCCH Iur Iur
CCH CCH MAC-d
FP FP
MAC-b MAC-c/sh
TRANSPORT
CHANNELS BCH PCH RACH DCH
Iub Iub FACH
CCH CCH DSCH
FP FP CPCH
optional
Softer Handover Iub/Iur Iub/Iur Soft Handover Iub/Iur Iub/Iur Soft Handover
Splitting / DCH DCH Splitting / DCH DCH Splitting /
Combining FP FP Combining FP FP Combining
PHY User plane Control plane

UTRAN Architecture Principles –
User Plane
radio access bearer SAPs (user plane)
Non-Access Stratum
Radio Radio Iu Iu
proto- proto- proto proto
cols cols cols cols
((1)) (1) (2) (2)
Access Stratum
UE UTRAN CN
Radio Iu
(Uu) Non-Access Stratum:
• Protocols between UE and CN that are not
terminated in the UTRAN
Access Stratum:
• Provides
d UE-CN transport service to NAS services
Source: 3GPP 25.401 • AS protocols are closely linked to radio technology
UTRAN Architecture Principles –
Control Plane
signaling connection
CM,MM,GMM,SM (3) Non-Access Stratum CM,MM,GMM,SM (3)
Radio Radio Iu Iu
proto- proto- proto proto
cols cols cols cols
((1)) (1) (2) (2)
Access Stratum
UE UTRAN CN
Radio Iu
(Uu)
NAS control p
plane functions:
CM: Connection Management
MM: Mobility Management
GMM GPRS MM
GMM:
Source: 3GPP 25.401 SM: Session Management
UTRAN Functions (1)
- Transfer of User Data
- Functions related to overall system access control
- Admission Control
- Congestion Control
- System information broadcasting
- Radio channel ciphering and deciphering
- Integrity protection
- Functions related to mobilityy
- Handover
- SRNS Relocation
- Paging support
- Positioning
- Synchronisation
Source: 3GPP 25.401, Ch 7.1

UTRAN Functions (2)
- F
Functions
ti related
l t d tto radio
di resource managementt and
d control
t l
- Radio resource configuration and operation
- Radio environment survey
- Combining/splitting control
- Connection set-up and release
- Allocation and deallocation of radio bearers
- Radio protocols function
- RF power control
- Radio channel coding g and decoding
g
- Channel coding control
- Initial (random) access detection and handling
- CN distribution function for Non Access Stratum messages
- Functions related to broadcast and multicast services (broadcast/multicast
interworking function BM-IWF)
- Broadcast/Multicast Information Distribution
- Broadcast/Multicast Flow Control
- Cell-based Services (CBS) Status Reporting
- Tracing
- Volume reporting
Functions located inside/outside AS
Source: 3GPP 23
23.110
110
LOCATION\ FUNCTION Outside the Access Stratum Inside the Access Stratum
C ll sett up/release
Call / l yes no
(Connection) Bearer Set-Up Release CN bearer [tbd] Radio Access Bearer [tbd]
Supplementary Services yes no
Location management yes (IWF/CN related) yes (Radio related)
Attach/ Detach yes FFS, Contr expected
Resource Management yes (for NAS resource) yes (for AS resource incl. radio)
Handover yes*
yes yes
Macrodiversity [ffs] yes* yes
Encryption yes yes**
Authentication yyes no
compression (non source dependent) yes yes
source dependent coding yes no
radio channel coding (could be many) no yes (could be many)
UE location identification may be supported yes

Charging yes no
NOTE *:: Optionally execution
execution. In some CNs
CNs, it may not be present but not full service will be supported (e
(e.g.
g limited to
RLL type of service).
NOTE **: Contributions expected to clarify the role between encryption and subscriber data.

Wrap-up:
Why is UTRAN so complicated?
Some answers:
• Limitation of radio resources and last-mile transport resources
• Tight
g handover
a do requirements
qu esp.
p for
o voice
o
– Need for proactive handover initiation requires interaction between
radio layers
• CDMA macro-diversity mode

g RLC/MAC
– Single / entityy required
q for synchronous
y deliveryy of radio
frames over all SHO legs
– Splitting/combining of radio frames (multicast)
• Designed for maximum functionality and flexibility

p
– Overdimensioned from the viewpoint of a single
g application
pp

Modes and states (PS mode)
UE SGSN GGSN
SM: PDP context (active, inactive)
HLR
PMM state (detached, idle, connected)
RNC
Signaling connection
RRC connection
UE mode

Radio Link, RRC Connection,
Signaling Connection
Core Network
Iu Iu
RNS RNS signaling connection

UTRAN
Iur
RNC SRNCRNC
Ib
Iub Iub Iub Iub
RRC connection
ti -> connected
t d mode
d
radio link
UE
RRC connections and signaling connections are logical links

Radio Link, RRC Connection,
Core Network
Iu Iu
RNS RNS signaling connection

UTRAN
Iur
DRNC
RNC SRNCRNC
Ib
Iub Iub Iub Iub
RRC connection radio link

UE

RRC Connection and Signaling Connection
UE SRNC MSC/VLR
or SGSN
Higher layer Higher layer
control control
RANA RANA
RRC RRC P
P
Signaling Radio Bearer Iu Signaling Bearer
RRC Connection RANAP Connection
Radio Access Bearer

RRC Connection
Connected mode
Enter URA
Cell connected state
Connected
URA
Enter
E t cell
ll Connected
connected state
RRC
connection
ti RRC UTRAN Registration
connection
establishment
release Area (URA):
• area covered by a
number of cells
• URA is only internally
Idle mode known in the UTRAN
• RRC state machine exists as two peer entities, one in the MS and one in
UTRAN (SRNC)
• Apart from transient situations and error cases the two peer entities are
synchronized
• No signaling connection exist (idle state)
– UE has no relation to UTRAN, only to CN
– no data transfer
– paging identification by IMSI, TMSI, P-TMSI
• Signaling connection exist (connected state)

UE p
position can be known on different levels:
- URA level (UTRAN registration area): URA is a specified set of cells,

which can be identified on the BCCH.
- Cell level: Different channel types can be used for data transfer:
- Common transport channels (RACH(RACH, FACH,
FACH DSCH,
DSCH USCH)
- Dedicated transport channels (DCH)
Source: 3GPP 25.301, ch 6.2

Important Vocabulary Source: 3GPP 21.905
RRC connection
• point-to-point bi-directional connection between RRC peer entities on the UE and
the UTRAN sides
• UE has either zero or one RRC connection
Signaling connection
• an acknowledged-mode
k l d d d link
li k between
b t the
th UE andd the
th CN tot ttransfer
f hihigher
h llayer
information between the entities in the non-access stratum (via RRC and RANAP)
Radio link
• a logical association between a single UE and a single UTRAN access point (cell)
• its physical realization comprises one or more radio bearer transmissions
R di bearer
Radio b (
(compare signaling
i li radio
di bearer)
b )
• service provided by the RLC layer for transfer of user data between UE and SRNC
Radio interface
• interface between UE and a UTRAN access point
• radio interface encompasses all the functionality required to maintain the
i t f
interface

Access Stratum Services
Non-Access Stratum (NAS)
GC Nt DC GC Nt DC
Access Stratum (AS)
end AS entity end AS entity
Relay/RNC functions
GC Nt DC Nt DC GC Nt DC
GC Nt DC GC
Uu
RRC Stratum RRC Iu
(UuS) Stratum
L2/L1 L2/L1
UE UTRAN Core Network

Radio
(Uu) Iu
Services of Access Stratum:
• General Control (GC) – idle mode
• Notification (Nt) – idle mode
• Dedicated Control (DC) – connected mode
Source: 3GPP 25.301
• User data
d transfer
f ((RAB)) – connected
d mode
d
(see also 3GPP 23.110) Note: NAS signaling services are provided by RANAP
Services provided at AS SAPs –
GC and
a d Ntt (UE
(U in idle
d e mode)
ode)
General Control SAPs (GC) – information broadcast service
– Enable CN to provide information and to give commands that do not

relate to specific users or specific sessions (group calls, conference)
– Typically one GC SAP per AN/CN connection point (Iu)

– Typically one GC SAP in MS
Notification SAPs (Nt) – paging and notification broadcast services
– SAPs are used to broadcast data to identified users

– Typical
yp use is for initiating
g paging
p g g in the AN
– Typically one Nt SAP per AN/CN connection point (Iu)

– Typically one Nt SAP (a Paging SAP) in MS
Source: 3GPP 23.110, ch. 6; see also 25.301, ch 5.4

Services provided at AS SAPs – DC (conn. mode)
Dedicated Control SAPs (DC) – connection establishment/release and
message transfer
• SAPs are used to establish and release connections with specific UEs,
and to transfer information on these connections
• Several types of connections are identified, point connections (single
user) and group connections
• SAPs
SAP are ididentified
tifi d by
b a SAPI att th
the AS boundary
b d
• SAPI is valid for the lifetime of a connection
• SAPI is used as a unambiguous connection identifier of the associated
SAP
• Typically a great number of DC SAPs per AN/CN connection point

• Typically a single DC SAP in MS
Source: 3GPP 23.110

Radio Interface Protocols
UMTS Terrestrial Radio Access (UTRA)
• Air interface protocol architecture
• Layer 1, 2 and 3 protocols
• Mapping between logical, transport and

physical channels

Radio Protocols – Overview
GMM / GMM /
SM / SMS SM / SMS
Control plane Relay

Layer 3
RRC RRC RANAP RANAP
– IP,
IP PPP (user plane)
RLC RLC SCCP SCCP
– RRC (control plane)
MAC MAC Signalling
Bearer
Signalling
Bearer Layer 2
L1 L1
AAL5 AAL5
– PDCP (user plane)
Uu
ATM
Iu-Ps
ATM
– BMC (user plane)
A MS
Application
li i RNS 3G SGSN – RLC
E.g., IP, – MAC E.g., IP,
PPP PPP
Layer 1
User plane
Relay Relay – PHY
PDCP PDCP GTP-U GTP-U GTP-U GTP-U
RLC RLC UDP/IP UDP/IP UDP/IP UDP/IP

MAC MAC AAL5 AAL5 L2 L2
L1 L1 ATM ATM L1See

S 3GPP 25.301
25 301 and
d
L1
Uu Iu-PS UMTS Networks
Gn book, ch. 9 Gi
MS UTRAN 3G-SGSN 3G-GGSN
Radio Protocols in Context
Radio Protocols (UTRA)
DTCH DCCH DCCH DTCH
MAC-d Radio Network Layer (RNL) MAC-d
PHY-upper
PHY upper PHY PHY
DchFP DchFP DchFP DchFP
AAL2 AAL2 AAL2 AAL2

PHY PHY
ATM ATM ATM ATM
Transport Network Layer (TNL)
Example: DCH (user plane)

UTRAN Protocol Reference Model
Radio Protocols (UTRA)

• Protocols constituting the radio interface
Radio Network Layer (RNL)

• UTRAN-specific protocols to control the management and use of radio
access bearers across the UTRAN interfaces (Iu, Iub, Iur)
• User plane: frame protocols (FP), e.g. DchFP
• Control plane: application part (AP) protocols, e.g. RANAP, NBAP, RNSAP
Transport Network Layer (TNL)

• Set of general transport protocols allowing non
non-adjacent
adjacent network nodes
to communicate
• ATM transport or IP transport (Release 4 and beyond)

Radio Protocol Architecture
C-plane signalling U-plane information Radio Access Bearers
GC Nt DC AS control plane SAPs
RRC control L3
Radio
ontrol
ontrol
ontrol
ontrol
Bearers
co
co
co
co
PDCP
PDCP L2/PDCP
BMC
L2/BMC
RLC RLC L2/RLC

RLC RLC
RLC RLC
RLC RLC
Logical
Channels
MAC L2/MAC
Transport
Channels
Source: 3GPP 25.301 PHY L1
GC Nt DC Radio Access Bearers
AS control plane SAPs
Physical Layer – Services Duplication avoidance
Physical layer offers information transferGCservices (transport channels) to

Nt DC
UuS boundary
MAC and higher layers C-plane signalling U-plane information
Physical layer transport services define

RRC L3
–how and
control
–with what characteristics data are transferred over the radio interface
control Radio
control
control
control
Bearers
Transport channels do not define what PDCP

PDCP
L2/PDCP
i transported
is t t d (which
( hi h is
i defined
d fi d by
b
logical channels)
BMC
L2/BMC
Example: DCH offers the same type of

service for control and user traffic RLC RLC
RLC
RLC L2/RLC
RLC RLC
RLC RLC
Logical
Channel
MAC L2/MAC
Transport
Channels
PHY L1
Physical Layer – Channel Types Duplication avoidance
• common transport channels (there is a need for inband

GC Nt DC
UuS boundary
identification of the UEs when particular UEs areU-plane
C-plane signalling addressed)
information
• dedicated transport channels (the UEs are identified by the physical

channel, i.e. code and frequency RRC
for FDD (code, time slot and frequency for TDD)
L3
)
control
control Radio
control
control
control
Bearers
PDCP
PDCP L2/PDCP
BMC
L2/BMC
RLC RLC L2/RLC

RLC RLC
RLC RLC
RLC RLC
Logical
Channel
MAC L2/MAC
Transport
Channels
PHY L1
Physical Layer – Common Transport
Channels
C a e s ((1))
Random Access Channel (RACH)
• Contention
C t ti b based
d uplink
li k channel
h l used
d for
f transmission
t i i off relatively
l ti l
small amounts of data, e.g. for initial access or non-real-time
dedicated control or traffic data
Forward Access Channel (FACH)
• Common downlink channel for relatively small amount of data
• no closed-loop
l dl power control
t l
Downlink Shared Channel (DSCH) – TDD only
• Downlink channel shared by several UEs carrying dedicated control or
traffic data
Uplink Shared Channel (USCH) – TDD only
• Uplink channel shared by several UEs carrying dedicated control or
traffic data

Physical Layer – Common Transport
Channels
C a e s ((2))
Broadcast Channel (BCH)

• Downlink channel used for broadcast of system information into an
entire cell
Paging Channel (PCH)
• A downlink channel used for broadcast of control information into an
entire cell allowing efficient UE sleep mode procedures
• Currently identified information types are paging and notification
• Another use could be UTRAN notification of change of BCCH
information
High-Speed Downlink Shared Channel (HS-DSCH) – Rel. 5

• High-speed downlink channel shared by several UEs

Physical Layer – Dedicated Transport
Channels
C a e s & Transport
a spo t Formats
o ats
Dedicated Channel (DCH)
Channel dedicated to one UE used in uplink or downlink
Enhanced Dedicated Channel (E-DCH)

• Channel
Ch l dedicated
d di d to one UE used
d in
i uplink
li k only.
l
• Subject to Node-B controlled scheduling and HARQ
Transport Formats and Transport Format Sets

• A Transport Format or a Transport Format Set is associated with each
transport channel
• A Transport
T t Format
F t defines
d fi the
th format
f t offered
ff d b by L1 tto MAC
(encodings, interleaving, bit rate and mapping onto physical channels)
• A Transport Format Set is a set of Transport Formats
• Example: a variable rate DCH has a Transport Format Set (one Transport
Format for each rate), whereas a fixed rate DCH has a single Transport
Format
See 3GPP 25.302,
25 302 ch.
ch 7 and Walke,
Walke ch 5.10,
5 10 for details on Transport Formats and Transport Format Sets

Physical Layer Processing
Data Transport
Data Data Transport
Block Set Transportt
T
Data Data Data Block Set
Block
DCH DCH DCH
Note: Functional blocks
which implement
concatenation, segmentation, CRC attachment CRC attachment CRC attachment
interleaving, discontinuous
transmission (DTX) and Channel Coding Channel Coding Channel Coding
macrodiversity
di i b i /
distirbution/combining
bi i have
h Rate Matching Rate Matching Rate Matching
been suppressed.
Transport Channel Multiplexing
Note: Physical Channel Coded Composite Transport Channel (CCTrCH)

Mapping is used to implement
multicoding (more than one
DPCH) This
DPCH). Thi will
ill usually
ll Physical Channel Mapping
only be used for high data
rates
DPCH
C DPCH
C
See 3GPP 25.302 for details

Physical Channels
DCH Dedicated Physical Data Channel (DPDCH)

Dedicated Physical Control Channel (DPCCH)
RACH Physical Random Access Channel (PRACH)
Common Pilot Channel (CPICH)

BCH Primary Common Control Physical Channel (P-CCPCH)
FACH Secondary Common Control Physical Channel (S-CCPCH)
PCH
Synchronisation Channel (SCH)
Acquisition Indication Channel (AICH)
Page Indication Channel (PICH)
Channels as of R.99/see 3GPP 25.211 for details

Physical Layer – Functions
• Macrodiversity distribution/combining and soft handover execution
• Error detection on transport
p channels and indication to higher
g layers
y ((CRC))
• FEC encoding/decoding and interleaving/deinterleaving of transport channels
• Multiplexing of transport channels and demultiplexing of coded composite
transport channels
• Rate matching (fit bits into physical channel)
• Mapping of coded composite transport channel on multiple physical channels
• P
Power weighting
i hti and d combining
bi i off physical
h i l channels
h l
• Modulation and spreading/demodulation and despreading of physical channels
• Frequency
q y and time (chip,
( p, bit,, slot,, frame)) synchronisation
y
• Measurements and indication to higher layers (e.g. frame error rate, signal-to-
interference ratio, interference power, transmit power, etc.)
• Closed-loop
Closed loop power control
• RF processing
• Support of timing advance on uplink channels (TDD only)
• S
Support off Uplink
li k Synchronisation
S h i i (TDD ( only)
l )

Medium Access Control (MAC) – Services Duplication avoidance
Data transfer (logical channels SAPs) GC Nt DC

UuS boundary
– Unacknowledged transferC-plane of MAC SDUs between
signalling peer MAC entities
U-plane information
– No
N data
d t segmentation
t ti (performed
( f d by
b higher
hi h layers)l ) on R.99
R 99
Reallocation of radio resources RRC and MAC parameters
control L3
– Execution of radio resource reallocation and change of MAC Radio

control
control
control
control
parameters by request of RRC, i.e. change of transport formatBearers
(combination) sets, change of transport channel PDCP
PDCP type L2/PDCP
– Autonomously
A t l resource allocation
ll ti in
i TDD mode d
BMC
L2/BMC
Reporting of measurements
– Local measurements such as
traffic volume and quality RLC
RLC
RLC
RLC L2/RLC
indication (reported toRLC

RRC)
RLC
RLC
RLC
Logical
Channel
MAC L2/MAC
Transport
Channels
PHY L1
MAC – Logical Channels
Logical channels define what information is transported

(transport channels (PHY SAP) define how data are transported)
• Control Channels (transfer of control plane information)

– Broadcast Control Channel (BCCH) – DL
– Paging Control Channel (PCCH) – DL
– Common Control Channel (CCCH) – DL/UL
– Dedicated Control Channel (DCCH) – DL/UL
– Shared Channel Control Channel (SHCCH) – DL/UL (TDD)
• Traffic Channels (transfer of user plane information)

– Dedicated Traffic Channel (DTCH) – DL/UL
– Common Traffic Channel (CTCH) – DL/UL

MAC – Functions (1)
• Mapping between logical channels and transport channels
• Selection of appropriate Transport Format for each Transport Channel
depending on instantaneous source rate
• Priority handling (multiplexing) between data flows of one UE (MAC-d)
• Priority handling (scheduling) between different UEs (MAC-c/sh)
• Identification of UEs on common transport channels
Example: DTCH/DCCH mapped on DSCH (TDD only)
DTCH DCCH DCCH
CC DTCH
C
MAC-d
MAC-d
MAC d
MAC-c/sh MAC-c/sh
DschFP DschFP
DschFP DschFP
AAL2 AAL2 AAL2 AAL2

PHY PHY
ATM ATM ATM ATM

MAC – Functions (2)
• M
Multiplexing/demultiplexing
lti l i /d lti l i off upper layer
l PDUs
PDU on common transport
t t
channels
• Multiplexing/demultiplexing of upper layer PDUs on dedicated transport
channels
• Traffic volume measurement
• Transport channel type switching (controlled by RRC)
• Ciphering for transparent RLC mode
Example: DTCH/DCCH mapped on DSCH (TDD only)
DTCH DCCH DCCH
CC DTCH
C
MAC-d
MAC-d
MAC d
MAC-c/sh MAC-c/sh
DschFP DschFP
DschFP DschFP
AAL2 AAL2 AAL2 AAL2

PHY PHY
ATM ATM ATM ATM

Distribution of MAC Functions (DSCH –TDD only)
SRNC 1 SRNC 2
RLC1 RLC2
UE1 UE2
MAC-d1 MAC MAC-d2
SRNCs
Iur or local
RLC
Common MAC (MAC-c/sh)
Controlling RNC MAC-c/sh
MAC c/sh • multiplexing between
multiple UEs sharing the
RACH/ DSCH DSCH
Node B FACH
Dedicated MAC (MAC-d)
(MAC d)
Uu
UE
• multiplexing of logical
Signalling Data for g UE
channels of a single
for UE 1&2 UE 1&2
(Case B, TDD only)
Source: 3GPP 25.301, sc 5.6.5
Logical/ Transport/ Physical Channels Mapping
(excerpt, FDD)
Logical Channels Transport Channels Physical Channels
P-SCH
Control Ch Common Ch (no FPC)
S-SCH
Traffic Ch Common Ch (FPC) Fixed Channels
Dedicated Ch (FPC) P-CPICH Info Channels
Assoc Channels
S CPICH
S-CPICH
BCCH BCH P-CCPCH
PCCH PCH PICH
CCCH FACH S-CCPCH
CTCH RACH PRACH
DCCH AICH
DTCH DCH DPDCH
DPCH
C
DPCCH
Key: Uplink
Downlink
Bidirectional
Data Transfer
Association

Logical/Transport Channels Mapping
UE side (all possibilities)
BCCH- PCCH- DCCH- CCCH- SHCCH- CTCH- DTCH-

SAP SAP SAP SAP SAP SAP SAP
(TDD only) Logical
Channels
(MAC SAPs)
Transport
BCH PCH RACH FACH USCH DSCH DCH Channels
(TDD only) (TDD only)

Logical/Transport Channels Mapping
UTRAN side (all possibilities)
BCCH- PCCH- DCCH- CCCH- SHCCH- CTCH- DTCH-

SAP SAP SAP SAP SAP SAP SAP
(TDD only) Logical
Channels
(MAC SAPs)
Transport
BCH PCH RACH FACH USCH DSCH DCH Channels
(TDD only) (TDD only)

GC Nt DC
Radio Link Control (RLC) Duplication avoidance
• Transparent
T anspa ent data transfer
t ansfe (TM) GC Nt DC
• Unacknowledged data transfer (UM) UuS boundary

U-plane information
• Acknowledged data transfer (AM)
C-plane signalling
RRC control L3
control Radio
control
control
control
Bearers
PDCP
PDCP L2/PDCP
BMC
L2/BMC
RLC RLC L2/RLC

RLC RLC
RLC RLC
RLC RLC
Logical
Channel
MAC L2/MAC
Transport
Channels
PHY L1
RLC – Services (1)
Transparentt data
T d t transfer
t f (TM)
• Transmission of upper layer PDUs without adding any protocol information (no
RLC header)
• Possibly
P ibl iincluding
l di segmentation/reassembly
t ti / bl functionality
f ti lit
Unacknowledged data transfer (UM)
• Transmission of upper layer PDUs without guaranteeing delivery to the peer
entity
– Error detection: The RLC sublayer shall deliver only those SDUs to the
g upper
receiving pp layer
y that are free of transmission errors byy using g the
sequence-number check function
– Immediate delivery: The receiving RLC sublayer entity shall deliver a SDU
to the upper layer receiving entity as soon as it arrives at the receiver
Acknowledged data transfer (AM)
• Transmission of upper layer PDUs and guaranteed delivery to the peer entity
• Notification of RLC user at transmitting side in case RLC is unable to deliver the
data correctly
• in-sequence and out-of-sequence delivery
• error-free delivery (by means of retransmission)
• duplication detection
RLC – Services (2)
Maintenance of QoS as defined by upper layers
• retransmission protocol shall be configurable by layer 3 to provide
different levels of QoS
Notification of unrecoverable errors
• RLC notifies the upper layer of errors that cannot be resolved by RLC
itself by normal exception handling procedures
There is a single RLC connection per Radio Bearer

RLC – Functions
• Transfer of user data (AM, UM, TM)
• Segmentation and reassembly (RLC PDU size adapted to transport
format) C
Convertt variable-size
i bl i hi higher
h
• Concatenation layer PDUs into fixed-size
• Padding RLC PDUs (TBs)
• Sequence number check (UM mode) Convert radio link
• Duplicate RLC PDUs detection errors into packet
• In sequence delivery of upper layer PDUs
In-sequence l
loss and
dddelay
l
• Error correction (selective-repeat ARQ)
• Flow control between RLC peers Avoid Tx and Rx
• SDU discard buffer overflows or
• Protocol error detection and recovery protocol stalling
• E h
Exchange off status information
i f i between
b peer RLC entities
ii
• Ciphering (non-transparent mode)
• Suspend/resume and stop/continue of data transfer
• Re-establishment of AM/UM RLC entity
Logical/Transport Channels Mapping Details
UTRAN side
D D U/D U/D D U/D
Broadcast Paging Dedicated Common Control User Common Dedicated
Control Control Control Control Traffic Traffic Logical
Plane Plane
Channel Channel Channel Channel Channel Channel Channels
(BCCH) (PCCH) (DCCH) (CCCH) (CTCH) (DTCH)
BCCH- PCCH- DCCH- CCCH- CTCH- DTCH- SAP

SAP SAP SAP SAP SAP
MAC SAPs
Tr
UM
UM
UM
UM Tr
UM AM
AM UM
Tr Tr AM
AM UM
AM Tr
UM
AM
RLC Modes
Tr Transparent
UM Unacknowledged
AM Acknowledged
Tr
Broadcast Paging Random Forward Transport

Dedicated
Channel D Channel D Access Access Channels
Channel
U D
(BCH) (PCH) Channel Channel (DCH) U/D
(RACH) (FACH)
U Uplink
D Downlink To / From Physical Channels
U/D Uplink / Downlink
Control Plane Relationships
Call signalling: RLC Entities / Channels / Signaling Radio Bearers (SRB) Relationships
SRB1 SRB2 SRB3/4
RLC UM RLC Entity RLC Entity AM RLC Entity AM RLC Entity
Logical
DCCH DCCH DCCH DCCH
Channels
MAC
DCH DCH
LAYER 1 CCTrCH CCTrCH
DPDCH DPDCH
Abbr. Mode RLC Entities Notes:

Tr Transparent mode 2 (one Tx and one Rx) This is for a single user and only shows
UM Unacknowleged Mode 2 (one Tx and one Rx) the control plane. SRB0 is not shown as
AM Acknowleged Mode 1 (bi-directional for ARQ) this is for the CCCH - i.e. not used for a
dedicated call, only for establishment.

Circuit Switched Voice Call Relations
Call signalling: RLC Entities / Channels / Radio Bearers (RB) DL UL
AMR VOICE CODEC

AMR VOICE CODEC
Relationships
Class B (103bits)
Class B (103bits)
Class C (60bits)
Class C (60bits)
Class A (81bits)
Class A (81bits)
Control Plane
SRB1 SRB2 SRB3/4
RB
RB
RB
RB
RB
RB
ne
User Plan
RLC
C
Tr
RLC
RLC
RLC
RLC
RLC
RLC
UM RLC Entity RLC Entity AM RLC Entity AM RLC Entity
DCCH DCCH DCCH DCCH DTCH DTCH
MAC
DCH DCH
DCH DCH
LAYER 1
CCTrCH CCTrCH
Physical
DPDCH DPDCH
Channels
Abbr. Mode RLC Entities Notes:
Tr
Tr. Transparent mode 2 (one tx.
tx And one rx.)
rx ) This is for a single user
user. SRB0 is not shown as this
UM Unacknowleged Mode 2 (one tx. And one rx.) is for the CCCH - i.e. not used for a dedicated call,
AM Acknowleged Mode 1 (bi-directional for ARQ) only for establishment.

Mapping of Layers to Network Elements
Logical Channels Transport Channels
Control Ch Common Ch (no fast power control)
Traffic Ch Common Ch (fast power control)
Dedicated Ch (fast power control)
CCCH DCCH, DTCH

etc.
etc.
etc.
RLC, e
RLC, e
RLC, e
AC-d
MAC-c/sh
h
MA
MAC-d
MAC
FACH
RACH
DSCH
USCH
USCH
FACH
RACH
DSCH
DCH
PCH
DCH
PHY-upper
PHY
Iub Iur
Node B Controlling RNC Serving RNC

Data Flows through Layer 2:
Transparent RLC (TM) and
Transparent MAC
Higher
Hi h
Higher Layer PDU
Layer
reassembly
y
RLC SDU
L2 RLC
(transparent)
RLC PDU … RLC PDU segmentation
L2 MAC
(transparent)
MAC SDU
… MAC SDU
Transport block (MAC PDU)

… Transport block (MAC PDU)
L1
CRC … CRC
Examples: BCCH
BCCH-BCH,
BCH PCCH
PCCH-PCH,
PCH DTCH
DTCH-DCH
DCH

Transparent RLC (TM) and
Non-transparent MAC
Higher
Higher Layer PDU
Layer
RLC SDU
reassembly
L2 RLC
(transparent)
RLC PDU … RLC PDU segmentation
L2 MAC
…
(non-transparent) MAC MAC SDU MAC MAC SDU
header header

L1
CRC
… CRC
Examples: DTCH(multiple)
DTCH(multiple)-DCH,
DCH CCCH
CCCH-FACH/RACH,
FACH/RACH BCCH-FACH
BCCH FACH

Non transparent RLC (UM or AM) and
Non-transparent
Transparent MAC
Higher Layer Higher Layer PDU Higher Layer PDU
reassembly
RLC SDU RLC SDU
L2 RLC
Segmentation &
Concatenation
RLC RLC
L2 MAC MAC SDU MAC SDU

(transparent)
Transport block (MAC PDU) Transport block (MAC PDU)
L1 CRC CRC
Examples: DTCH
DTCH-DCH
DCH, DCCH-DCH
DCCH DCH

Non transparent RLC (UM or AM) and
Non-transparent
Non-transparent MAC
Higher Layer Higher Layer PDU Higher Layer PDU
RLC SDU RLC SDU reassembly
L2 RLC
(non-transparent)
… Segmentation &
concatenation
RLC
header … RLC
header
…
MAC MAC SDU MAC MAC SDU
L2 MAC header header
(non-transparent)
L1
CRC
… CRC
Examples:
p CCCH-FACH/RACH,
/ , DCCH-FACH/RACH,
/ , DCCH-DSCH,, DTCH-
FACH/RACH, DTCH-DSCH, DTCH-DCH, DCCH-DCH, CTCH-FACH
Packet Data Convergence Protocol (PDCP) Duplication avoidance
Service: PDCP SDU delivery GCNt DC

PDCP is defined for PS domain only!
UuS boundary
C-plane signalling U-plane information
RRC control L3
control Radio
control
control
control
Bearers
PDCP
PDCP L2/PDCP
BMC
L2/BMC
RLC RLC L2/RLC

RLC RLC
RLC RLC
RLC RLC
Logical
Channel
MAC L2/MAC
Transport
Channels
PHY L1
PDCP – Functions
Header compression and decompression

• Header compression and decompression of IP data streams (e.g.
TCP/IP and RTP/UDP/IP headers)
Header compression method is specific to the upper layer protocol
combinations, e.g. TCP/IP or RTP/UDP/IP (RFC 2507 & RFC 3095)
Transfer of user data

• PDCP receives PDCP SDU from the NAS and forwards it to the RLC layer
and vice versa
Support for lossless SRNS relocation

• Maintenance of PDCP sequence numbers for radio bearers that are
configured to support lossless SRNS relocation

PDCP Details
Radio Bearers
PDCP-SDU
PDCP-SAPs ...
C SAP
C-SAP
PDCP PDCP PDCP PDCP-
entity entity SDU entity sublayer
numbering
HC Protocol HC Protocol HC Protocol HC Protocol HC Protocol

Type1 Type2 Type1 Type2 Type1
RLC-SDU
...
UM-SAP AM-SAP TM-SAP RLC
HC: Header Compression SDU numbering to support lossless SRNC relocation

GC Nt DC
Broadcast/Multicast Control (BMC) Duplication avoidance
Service: GC Nt DC
UuS boundary
• broadcast/multicast transmission service in the user
C-plane signalling plane
U-plane information
for common user data in unacknowledged mode

RRC control L3
Radio
control
control
control
control
Bearers
PDCP
PDCP L2/PDCP
BMC
L2/BMC
Functions:
• Storage of Cell Broadcast Messages RLC RLC L2/RLC
RLC
• Traffic volume monitoring RLCand RLC
radio RLC
RLC
RLC
resource request for CBS

Logical
• Scheduling of BMC messages Channel
• Transmission of BMC messages to UE MAC L2/MAC
• Delivery
D li off Cell
C ll Broadcast
B d t messages to t Transport
Channels
upper layer (NAS) in the UE PHY L1
GC Nt DC
Radio Resource Control (RRC) Duplication avoidance
GC Nt DC
UuS boundary
C-plane signalling U-plane information
RRC control L3
control Radio
control
control
control
Bearers
PDCP
PDCP L2/PDCP
BMC
L2/BMC
RLC RLC L2/RLC

RLC RLC
RLC RLC
RLC RLC
S
Services
i P
Provided
id d to U
Upper L
Layers Logical
Channel
General Control (GC) – information broadcast service
MAC L2/MAC
Notification (Nt) – paging and notification broadcast services Transport
Channels
Dedicated Control (DC) – connection management PHY and message transfer L1
RRC – Interaction with Lower Layers
Measurement Report
RRC RRC
Radio Resource
Assignment
Control
[Code, Frequency,
Control
TS, TF Set, Mapping,
etc.]
RLC RLC
RLC retransmission
Measurrements
Measureements
control
ntrol
ol
Contro
Con
MAC MAC
Measurements
Meeasurements
Control
Control
C
M
L1 L1
UTRAN UE

RRC – Functions
RRC handles the control plane signaling of layer 3 between the UEs and UTRAN:
- Broadcast of information provided by the non-access stratum (Core Network)
- Broadcast of information related to the access stratum
- Establishment,
E bli h re-establishment,
bli h maintenance
i andd release
l off RRC
connections
- Establishment, reconfiguration and release of Radio Bearers
- Assignment,
Assignment reconfiguration and release of radio resources for the RRC
connection
- RRC connection mobility functions
g g/
- Paging/notification
- Routing of higher layer PDUs
- Control of requested QoS
- UE measurement reporting and control of the reporting
- Outer loop power control
- Control of ciphering
- Slow DCA (TDD)
- Arbitration of radio resources on uplink DCH
- Initial cell selection and re-selection in idle mode
- Integrity protection (message authentication for sensitive data)
- Control
C t l off Cell
C ll Broadcast
B d t Service
S i (CBS)
- Timing advance control (TDD)
RRC State Machine
Connected mode
Enter URA
E
Connected
URA
Enter cell Connected
connected state
RRC
connection RRC
establishment connection
release
Idle mode
• RRC state machine exists as two peer entities (MS and UTRAN)
• The two peer entities are synchronized (apart from transient situations
and error cases)
UTRAN Registration Area (URA)
• URA is known to the
UTRAN only RA URA RA URA RA URA
• URA is established in URA URA URA URA URA URA
RRC connected mode URA URA
URA URA URA URA
LA
RA URA RA URA RA URA URA
URA
URA is independent of URA URA URA URA URA URA
URA
RNC area URA URA
URA URA URA URA URA URA
URA may cover
URA
•part of an RNC area
•parts of several RNC RA URA RA URA URA RA URA
areas URA
URAs may overlap URA
URA
URA

RRC State Machine
RRC Idle mode:
– no connection established between the MS and UTRAN
– no signalling between UTRAN and the MS except for system
information sent from UTRAN on a broadcast channel to the MS
– MS can only receive paging messages with a CN identity on the PCH
– no information of the MS is
Connected mode
stored in UTRAN
Enter URA
Connected
URA
connected state
RRC
connection RRC
ti
release
Idle mode

Connected mode
RRC State Machine Enter URA
Cell connected
t d state
t t
Connected
URA
connected state
RRC
connection RRC
release
RRC Connected mode: Idle mode
– two main states

• C
Cellll Connected:
C t d MS position
iti is
i known
k att the
th cellll level;
l l RRC connection
ti
mobility is handled by handover and cell update procedures
• URA Connected: MS position is known at the URA level; URA updating
procedures provide the mobility functionality; no dedicated radio resources
are used in the state.
– there is one RNC that is acting as serving RNC, and an RRC connection
is established between the MS and this SRNC
An UE has either zero or one RRC connection
RRC State Machine: Details of
connected
co ected mode
ode
UTRA RRC Connected Mode URA_PCH or CELL_PCH
URA_PCH CELL_PCH
UTRA:
Inter-RAT state GSM:
Handover GSM
Handover Connected
Neither DCCH norMode
are DTCH
out of in
service service out of in
available in these states

service service
GPRS
Packet
Transfer
CELL_DCH CELL_FACH Mode
out of in CELL_FACH state
service service Cell reselection Release RR Establish RR
DCCHInitiation
Release of
and, of
if configured,
Connection Connection
Release RRC Establish RRC Release RRC Establish RRC DTCHtemporary

temporary
are available in this
block flow
block flow
C
Connection
ti Connection C
Connection
ti C
Connection
ti
state
GPRS Packet Idle Mode
Camping on a UTRAN cell CELL DCH state

CELL_DCH
Camping on a GSM / GPRS cell
Idle Mode DCCH and DTCH are available

in this state

UMTS RRC State Optimization (PS mode)
Goal: Minimization of Radio Resource
Consumption during Idle Times
idle
Tradeoff for idle periods
• retaining in state (continuous state cost) and
T3
• move to cheaper state (one time transition cost)
URA_PCH Limited resources

• radio resources (transmit power)
• channelization codes
T2 • processing cost (signaling)
• power consumption
cell_PCH • transport
t t resources (I
(Iu, IIub,
b …))
Find optimal timeout settings depending on

T1 • traffic model (distribution of idle times)
• cost per state
cell_DCH • cost per transition
• user mobility
• …

UMTS RRC State Optimization
es
Timeout Value
sum
state
t t costt
transition cost
on of T
Optimizatio

Radio Interface – Control Plane Summary
UE SRNC MSC/VLR
or SGSN
Higher layer Higher layer
control control
RANA RANA
RRC RRC P
P
AS Signaling Radio Bearer 2 Iu Signaling Bearer
Radio Access Bearer

NAS Signaling Radio Bearer
(GC, Nt, DC)

Radio Interface – Control Plane (AS and NAS)
Signaling messages transported over the radio interface (RLC/MAC/PHY) are

– RRC generated signaling messages and
– NAS messages generated in the higher layers (GC, Nt, DC SAPs)
UE SRNC MSC/VLR
or SGSN
RANA RANA
RRC RRC P
P
Radio Access Bearer

NAS Signaling Radio Bearer
(GC, Nt, DC)

Radio Interface – Control Plane Details
On establishment of the signaling connection between the peer RRC entities three or
four signaling radio bearers may be set up
– Two signaling radio bearers for transport of RRC generated signaling messages
• transferring messages through an RLC UM entity and
• transferring messages through an RLC AM entity
– One signaling radio bearer for transferring NAS messages set to "high priority" by
th hi
the higher
h layers
l (RLC AM)
– Optional signaling radio bearer for transferring NAS messages set to "low priority"
by the higher layers (RLC AM)
Subsequent to the establishment of the
UE SRNC MSC/VLR
signaling connection zero to several signaling
or SGSN
radio bearers may be set up for transferring
RRC RANA RANA
signaling messages using transparent
RRC RRC P
mode RLCP (RLC TM entity)
Radio Access Bearer

Bea e
NAS Signaling Radio Bearer Signaling Connection (GC, Nt, DC)

Utran Protocols

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Utran Protocols

Enviado por

Direitos autorais:

Formatos disponíveis

UMTS T

• UMTS Terrestrial Radio Access (UTRA)

Central 3GPP Documents on UTRAN:

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 2

• Components and Interfaces

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 3

Iub Iub Iub Iub

Node B Node B Node B Node B

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 4

Each RNS is responsible for the resources of its set of cells

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 5

Node B Node B Node B Node B

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 7

Source: 3GPP 25.401, Ch 6.3

Node B Node B Node B Node B

common/ shared dedicated channel in

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 9

PHY-upper PHY PHY

AAL2 AAL2 AAL2 AAL2

ATM ATM ATM ATM

UE Uu NodeB Iub CRNC Iur SRNC

cells served cells served cells served

AAL2 AAL2 AAL2 AAL2

ATM ATM ATM ATM

UE Uu NodeB Iub CRNC Iur SRNC

Physical channel is terminated within node B (no support for combining/splitting)

Source: 3GPP 25.401, sc 11.2.3 (see also 25.301, sc 5.6.2)

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 12

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 13

paging (idle) Iu paging (connected) Iu

RLC-b RLC-c/sh RLC-d

PHY User plane Control plane

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 14

CM,MM,GMM,SM (3) Non-Access Stratum CM,MM,GMM,SM (3)

Source: 3GPP 25.401, Ch 7.1

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 17

UE location identification may be supported yes

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 19

• Limitation of radio resources and last-mile transport resources

• CDMA macro-diversity mode

• Designed for maximum functionality and flexibility

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 20

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 21

RNS RNS signaling connection

Node B Node B Node B Node B

RRC connections and signaling connections are logical links

RNS RNS signaling connection

Node B Node B Node B Node B

RRC connection radio link

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 23

Signaling Radio Bearer Iu Signaling Bearer

RRC Connection RANAP Connection

Radio Access Bearer

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 24

• Signaling connection exist (connected state)

- URA level (UTRAN registration area): URA is a specified set of cells,

Source: 3GPP 25.301, ch 6.2

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 26

UMTS Networks Andreas Mitschele-Thiel, Jens Mueckenheim Nov. 2009 27

Non-Access Stratum (NAS)

Access Stratum (AS)

end AS entity end AS entity

UE UTRAN Core Network