UMTS Networks: Leo Petrak, Dr. Christian Hoene Und Prof. Georg Carle

Lehrstuhl fr Rechnernetze und Internet
Wilhelm-Schickard-Institut fr Informatik Universitt Tbingen
UMTS Networks
Leo Petrak, Dr. Christian Hoene und Prof. Georg Carle
Course Overview

Motivation Standardization issues UMTS architecture basics UMTS radio link

Physical layer Signaling
UE, UTRAN, PS Domain, CS Domain Basic functionalities:

Accessing the network Transferring data Detaching from the network Information storage

Mobility QoS Security
IMS Charging UMTS Evolution: from R99 to Rel7 Beyond UMTS
UMTS Networks and Internet Telephony Sommersemester 2006
Mobility
Mobility consequences Mobility in IP networks Mobility in UMTS
cf. TS 23.060 "General Packet Radio Service (GPRS)"
Mobility consequences I
In any network (IP, UMTS, GSM,...), mobility of the terminal requires extra functionality
terminal location needs to be registered
Detect new location (who?) Make new location known to both terminal and network
when moving from one cell to a neighboring cell, a handover needs to be performed
detect necessity detect new access point (may be equivalent to detecting new location) transfer user context?
incl. authentication and authorization credentials, QoS information
remove /loose connectivity on old path establish connectivity on new path

update routing establish QoS
paging support
Mobility consequences II
Seamless handover (= user doesn't notice) as desired in UMTS needs even more functionality
fast and without loss of data "make before break" is desireable
establish connectivity along new path before handover takes place
Mobility
Mobility in IP networks
IP originally was designed without mobility in mind

IP address codes both location and terminal identity
Handover entails change of IP address
to the network, the terminal is different "before" and "after" handover this makes session handover difficult
IETF HIP WG tackles this problem

In IPv4, mobility was added on later In IPv6, mobility was integrated from the start
IP was extended to also support mobile terminals

Mobile IP (MIP) Hierarchical Mobile IP (HMIP) Fast Handoffs for Mobile IP (FMIP)
Mobility in IP networks II Mobile IPv4 (MIP)

terminal listens to "advertisment messages" from "Foreign Agent" in visited network a mobile terminal is assigned a local "Care-of-Address" (CoA) Mobile terminal registers Care-of-Address with Home Agent in home network
Home Agent tunnels all packets arriving in home domain for mobile terminal to Care-of-Address to avoid triangular routing, Home Agent may instruct sender of packets to directly send to the Care-of-Address
location privacy problem
Mobile
Mobile terminal uses home address as source address

for location privacy may always send via Home Agent
Registration with Home Agent expires after negotiated life-time

prevent "stale state" due to aborting mobile terminals
Mobile Terminal signaling traffic data traffic
Visited network FA
Correspndent Node
HA Home network
HA Home Agent FA Foreign Agent

8
Mobility in IP networks III
Mobile IPv4 (MIP)cont'

Handover entails
acquiring new Care-of-Address from new Foreign Agent communicating new Care-of-Address to Home Agent packets destined to mobile terminal during handover are lost
No built-in seamless QoS support
Mobile IPv6 works slightly differently Seamless mobility support in IP networks is true to the "bazaar approach"
most ingredients are being developed flexible specifications how will they cooperate? no fixed architecture
what nodes are Foreign Agents? What nodes provide context transfer? What nodes take care of QoS?
Mobility
10
Mobility in UMTS

Reminder: Mobility Management States Mobility in PMM-Idle Mode Mobility in PMM-Connected Mode
Location Mgmt controlled by UE Handover controlled by RNC
Handover SRNC relocation Paging
11
Reminder: Mobility Management States

In PMM Detached state, UE location is unknown In PMM Connected state, UE informs SRNC and SGSN about location with cell or URA granularity. The Serving RNC controls handover. SGSN knows Serving RNC
UE can be paged
In PMM Idle state, UE location known at SGSN with Routing Area granularity.UE keeps network informed.
UE can be paged
PS Signalling Connection: RRC and RANAP Connection established for control signaling
PMM DETACHED
ch
De tac h
GP
PMM DETACHED Detach, GPRS Attach Reject, RA Update Reject Detach, GPRS Attach Reject, RA Update Reject
GP
De ta
RS At
RS
At
GP R
RS
PS Signalling Connection Release PMM-IDLE PS Signalling Connection Establish PMMCONNECTED
GP
UE Mobility Management States
h ta c
PS Signalling Connection Release
h ta c
PMM-IDLE PS Signalling Connection Establish
PMMCONNECTED Serving RNC relocation
SGSN Mobility Management States
12
Mobility in PMM-Idle Mode I

UE must perform location update with SGSN: in regular intervals to prevent time-out
when timed out, UE is moved to PMM-detached
guards against "lost UEs"
when
Routing Area changes
UE detects Routing Area change by listening to RAI broadcast UE sends a Routing Area Update Request to SGSN with GMM protocol
Implies generic SGSN addressing because SGSN may change
RNC SGSN GGSN before handover after handover user context RNC RNC SGSN RNC
13
Mobile Terminal
Mobility in PMM-Idle Mode II

if
Routing Area change entails an SGSN change, new SGSN obtains user context from old SGSN
identify old SGSN from old RAI SRNC is changed such that new SRNC is connected to SGSN
User context is transferred between SGSNs, such as IMSI, temporary keys, Charging Information
RNC SGSN GGSN before handover after handover user context RNC RNC SGSN RNC
Mobile Terminal
14
Mobility in PMM-Connected Mode
Location control by UE
UE tracks cells / URAs and updates them with SRNC UE tracks Routing Area and updates them with SGSN
when SGSN changes, same steps as in PMM-Idle mode, plus
PDP context information is transferred between SGSNs PDP context is torn down on old path and set up on new path
updating in regular intervals or upon cell / URA /Routing Area change
Handover controlled by SRNC

Soft handover Softer handover Hard handover
15
Inter SGSN Routeing Area Update Procedure I

MS new SRNS old SRNS new 3G-SGSN old 3G-SGSN GGSN new MSC/VLR HLR old MSC/VLR
1. Routeing Area Update Request 2a. SRNS Context Request 2a. SRNS Context Response
2. SGSN Context Request
3. SGSN Context Response 4. Security Functions 5. SGSN Context Ack C1 6. SRNS Data Forward Command 7. Forward Packets 8. Forward Packets 9. Update PDP Context Request 9. Update PDP Context Response 10. Update Location 11a. Iu Release Command 11a. Iu Release Complete 11. Cancel Location Ack 12. Insert Subscriber Data UMTS Networks and Internet Telephony Sommersemester 2006 11. Cancel Location
Fig 36 of 23.060
16
Soft and Softer Handover I
Because of Macrodiversity, radio signal picked up by multiple antennas can be combined

support of up to 6 simultaneous radio links
SRNC decides on adding / removing connections based on signal-tonoise ratio reported by UE
Core Network Iu DRNC Cells UE Iur SRNC
17
Soft and Softer Handover II
Softer Handover, when all cells involved in handover are controlled by same Node B otherwise Soft Handover Soft(er) Handover allows seamless handover
18
Hard Handover
Hard Handover: Macrodiversity cannot be used

GSM, Mobile IP communication is interrupted for several microseconds (GSM) or more (Mobile IP?)
In UMTS, Hard Handover must be used, when

handover between RNCs without Iur interface FDD / TDD handover
19
SRNC relocation
Because of Soft Handover, the SRNC can in principle be maintained for the duration of the connection Sometimes it is desireable to change the SRNC in order to optimize routing (Old) SRNC instructs a DRNC to become (new) SRNC
may entail change of SGSN
Algorithm for triggering (old) SRNC to perform relocation not specified in standard SRNC relocation timing independent of (soft) handover timing
SRNC SGSN RNC GGSN RNC before relocation after relocation SGSN DRNC
Mobile Terminal Iur
20
Paging
For a mobile-terminated session, the UE is paged, i.e. searched

when in PMM-idle mode UE is searched in the Routing Area when in PMM-connected mode, paging request is directly sent to UE using existing signaling conection by paging, the UE is requested to set up an additonal PDP context for the incoming session
21
Sequence Chart Paging
MS
RNS
MSC/VLR
3G-SGSN 1. PDP PDU or Downlink signalling 2. Paging 3. Paging Type1 4. Service Request 4. Service Request
Fig 58 of 23.060
UMTS Networks and Internet Telephony Sommersemester 2006 22
Summary
Mobility of the terminal requires extra functionality

terminal location needs to be tracked when moving from one cell to a neighboring cell, a handover needs to be performed seamless handover implies fast handover without packet loss paging support
The IETF is in the process of specifying support for seamless IP mobility

not specified how different ingredients will collaborate
UMTS offers seamless mobility

in PMM-idle mode, Routing Area is tracked in PMM-connected mode, cell or URA is tracked Macrodiversity allows Soft Handover
23
Course Overview

Motivation Standardization issues UMTS architecture basics UMTS radio link

Physical layer Signaling
UE, UTRAN, PS Domain, CS Domain Basic functionalities:

Accessing the network Transferring data Detaching from the network Information storage

Mobility QoS Security
IMS Charging UMTS Evolution: from R99 to Rel7 Beyond UMTS
24
QoS
What is QoS? Role of QoS in UMTS IP QoS technology QoS in the UMTS Core Network QoS in Real-life UMTS Networks
cf.
TS 23.107 Quality of Service (QoS) concept and architecture TS 23.207 End-to-end Quality of Service (QoS) concept and architecture
25
What is QoS?
normal Internet offers best effort service

For traditional Internet applications (email, http) this is ok
Some applications
Telephony Video conferencing Video streaming Online gaming
need better service, for example

Dedicated bandwidth Maximum delay requirement
this is called Quality of Service (QoS) Providing QoS requires extra effort in IP networks
for free in circuit-switched networks
26
QoS
What is QoS? Role of QoS in UMTS IP QoS technology QoS in the UMTS Core Network QoS in Real-life UMTS Networks
cf.
TS 23.107 Quality of Service (QoS) concept and architecture TS 23.207 End-to-end Quality of Service (QoS) concept and architecture
27
Role of QoS in UMTS I
UMTS shall deliver multimedia services via the PS-domain

video conferencing, voice "rich voice" web browsing ... bandwidth delay delay variance (jitter) ...
Each service has different requirements regarding

Typically, real-time services have stringent requirements, non-realtime services have lax requirements In other words, each service requires different Quality of Service (QoS)
28
Role of QoS in UMTS II
On radio interface, adequate QoS can be guaranteed by assigning common or shared channels In parts of UTRAN and in PS domain use IP protocol IP networks originally were not designed to deliver QoS
all packets are treated equal no resources are reserved for particular applications / users => can deliver satisfactory real-time services only in low-load conditions => IP QoS technology needs to be applied to guarantee QoS in UMTS
29
QoS
What is QoS? Role of QoS in UMTS IP QoS technology

QoS Signaling Resource Provisioning Admission Control
QoS in the UMTS Core Network QoS in Real-life UMTS Networks
30
IP QoS technology How to?
In order to support QoS, the following is needed:

QoS requirements of a session must be made known to all network elements delivering QoS, end-to-end: Protocol for QoS Signaling QoS must be realized. e.g. by reserving resources in all network elements: Resource Provisioning Technique Both standardized by IETF QoS needs to be managed and controlled e.g. admission control
Framework for UMTS QoS specified by 3GPP
31
IP QoS technology Resource Provisioning I
Overprovisioning
Provide sufficient resources to handle any traffic Can be combined with admission control at the ingress Probabilistic QoS guarantee No signaling needed (except may be to ingress routers for admission control)
DiffServ RFC 2475 "An Architecture for Differentiated Service"

prioritization of particular flows via Code Points (DSCP) in IP header
e.g. real-time packets are always handled first
should be used together with admission control unless packet paths are known, results in probabilistic QoS guarantees resource requirements should be signaled to nodes performing admission control (ingress routers)
32
IP QoS technology QoS Signaling protocols

1.
Today, no generally accepted solution exists: RSVP and its extensions RFC 2205 "Resource ReSerVation Protocol (RSVP)"
only QoS signaling protocol supported to any extent in commercial routers powerful all-purpose QoS signaling protocol
for IntServ, extension for MPLS for Admission Control

2.
travels hop-by-hop on transport layer interpreted by each router on the data-path
Signaling of DiffServ packet priority with DSCPs in IP Header
33
Admission Control
Edge router Interior router Domain
Bandwidth Broker

Overprovisioning and DiffServ can provide more reliable QoS when combined with Admission Control at the ingress router Ingress router only admits new session when sufficient resources available How does the ingress router determine sufficient resources are available?
1. 2. 3. Determine based on local knowledge (Personally, I have sufficient resources) this doesnt imply further down the path resources are available Needs full view of the domain how does it obtain this? Consults bandwidth broker who has full view
34
QoS
What is QoS? Role of QoS in UMTS IP QoS technology QoS in UMTS Networks QoS in Real-life UMTS Networks
35
QoS in UMTS
Detailed Requirements on QoS

QoS Classes, Parameters, Values
End-to-End QoS scenarios

Signaling and resource provisioning
QoS management functions defined for UMTS
36
Detailed QoS requirements: QoS Classes, Parameters, Values I

UMTS QoS is offered by the UMTS Bearer Service 4 QoS classes are defined:
conversational class (e.g. voice, video conferencing) streaming class (e.g. video streaming) interactive class (e.g. Web browsing, gaming) background class (e.g. Background email download) Guaranteed / max. Bit rate max packet size transfer delay traffic handling priority
These classes are characterized by e.g.:

37
Detailed QoS requirements: QoS Classes, Parameters, Values II

SDU - Service Data Unit (packet) BER - Bit Error Rate
Value ranges for UMTS Bearer Service Attributes from 23.107

Traffic class Maximum bitrate (kbps) Delivery order Maximum SDU size (octets) SDU format information Delivery of erroneous SDUs Residual BER SDU error ratio Transfer delay (ms) Guaranteed bit rate (kbps) Traffic handling priority Allocation/Retention priority Conversational class < 2 048 (1) (2) Yes/No <=1 500 or 1 502 (4) (5) Yes/No/- (6) 5*10 , 10 , 5*10 , -3 -4 -6 10 , 10 , 10 -2 -3 -3 -4 10 , 7*10 , 10 , 10 , -5 10 100 maximum value < 2 048 (1) (2)
-2 -2 -3
Streaming class < 2 048 (1) (2) Yes/No <=1 500 or 1 502 (4) (5) Yes/No/- (6) 5*10 , 10 , 5*10 , -3 -4 -5 -6 10 , 10 , 10 , 10 -1 -2 -3 -3 10 , 10 , 7*10 , 10 , -4 -5 10 , 10 250 maximum value < 2 048 (1) (2)
-2 -2 -3
Interactive class < 2 048 - overhead (2) (3) Yes/No <=1 500 or 1 502 (4)
Background class < 2 048 - overhead (2) (3) Yes/No <=1 500 or 1 502 (4)
Yes/No/- (6) 4*10 , 10 , 6*10 (7) 10 , 10 , 10

-3 -4 -6 -3 -5 -8
Yes/No/- (6) 4*10 , 10 , 6*10 (7) 10 , 10 , 10

-3 -4 -6 -3 -5 -8
1,2,3 (8)
1,2,3 (8)
1,2,3 (8) 1,2,3 (8)
1,2,3 (8)
38
End-to-End QoS Scenarios I: Basics
End-to-End QoS needs QoS signaling:

all network elements need be informed about the QoS that is to be provided QoS signaling e.g. via
RSVP DSCPs (DiffServ Code Points; limited information) PDP context
End-to-End QoS needs QoS provisioning via e.g.

Overprovisioning DiffServ
Signaling and provisioning mechanisms dont need be the same in all network segments
interworking possible
39
End-to-End QoS Scenarios II: Basics
40
End-to-End QoS Scenarios III: Basics
5 end-to-end QoS signaling scenarios are described in Release 5

all scenarios with PDP context / DiffServ interworking 2 scenarios with additional RSVP signaling App. layer signaling via SIP
this is a UMTS specific SIP dialect with additional functionality compared to IETF SIP
Inter-PLMN QoS Agreements (GRX)

Only between PLMNs
Not much in standard about QoS provisioning (because no interworking necessary)
41
End-to-End QoS Scenarios IV: Signaling Scenario 1

The UE controls the QoS mechanisms from the UE. QoS in UMTS controlled by PDP context. QoS in backbone network controlled QoS on remote access by DS. DS marking performed by link controlled by DS. GGSN.
Application Layer (eg. SIP/SDP)
DS PDP Flow
UplinkDat
The UE may control the QoS mechanisms from received information.
QoS in UMTS controlled by PDP context selected by TFT.
QoS in backbone network controlled QoS on remote access by DS. DS marking performed by link controlled by DS or other means. RUE, or remarking by RAP.
Application Layer (eg. SIP/SDP)
DS PDP Flow
Downlink Dat
UE UE
IP Network beyond PS Domain GGS Remot GGSN Remote AP Access Point
Remot Remote Host Host
42
End-to-End QoS Scenarios V: Signaling Scenario 1
UE signals QoS via the PDP context GGSN translates between PDP context and DiffServ
downlink data may however be re-classified because PDP context overrides external DiffServ marking
IP network beyond PS domain is DiffServ enabled
43
End-to-End QoS Scenarios VI: Sign. Scenario 3

The UE controls the QoS mechanisms from the UE. QoS in UMTS controlled by PDP context. UE DS marking and RSVP signalling carried transparently. QoS in backbone network controlled QoS on remote access by DS. DS marking performed by link controlled by UE, or by GGSN based on PDP either DS or RSVP. context signalling. RSVP signalling carried transparently.
Application Layer (eg. SIP/SDP) RSVP Signalling DS
Uplink Data
PDP Flow
The UE may control the QoS mechanisms from received information.
QoS in UMTS controlled by QoS in backbone network controlled QoS on remote access PDP context selected by by DS. DS marking performed by link controlled by TFT. RUE (or remarking by RAP). either DS or RSVP. Remote DS marking/GGSN RSVP signalling carried remarking and RSVP transparently. signalling carried transparently. Application Layer (eg. SIP/SDP) RSVP Signalling DS
Downlink Data
PDP Flow
UE
The UE performs DS edge functions and RSVP
GGSN
Remote AP
Remote Host
44
End-to-End QoS Scenarios VII: Signaling Scenario 3
Compared to previous Scenario,

UE additionally issues RSVP signaling used in remote access network will it be accepted there?
45
End-to-End QoS Scenarios VIII - GRX
PLMNs can be interconnected by administered IP backbone

Enabling secure IP-based packet routing between networks GPRS Roaming Network or GRX network
can be operated by separate entity
Guidelines issued by GSM Association (GSMA)

Facilitates roaming and inter-PLMN sessions Realized by off-line agreeing on Service Level Agreements (SLAs)
Between pairs of PLMNs, or between PLMN and GRX operator
SLA defines PLMN-to-PLMN service specification, including QoS

This QoS must be supported throughout entire GRX network
46
QoS management functions for PS Domain
The above scenarios are realised by QoS management functions, many of them known from the IP world QoS mgmt functions for user plane include
making user traffic adhere to the traffic profile agreed upon managing the network resources such that QoS agreed upon is delivered
QoS mgmt functions for the control plane include

limiting incoming traffic so QoS agreed upon can be delivered policy enforcement / authorization
47
QoS management functions for PS Domain - user plane I

TE MT RAN CN EDGE Gateway Ext. Netw.
Class if. Cond. Cond. Mapper Resource Manager Mapper Resource Manager Resource Manager
Class if. Cond.
Mapper Resource Manager
Local BS
Resource Manager
Resource Manager
External BS
RAN
phys. BS
RAN Access network service

direction
BB network service
data flow with indication of
Class.
- Classifier
Cond. - Conditioner Gateway - usually GGSN

UMTS Networks and Internet Telephony Sommersemester 2006 48
QoS management functions for PS Domain - user plane II
User plane QoS management functions are similar to those known from IP (e.g. DiffServ) A user-plane packet originating from the UE,
is classfied as belonging to one of the PDP contexts open for this UE is conditionalized, i.e. if need be dropped, demoted or delayed
in UE
according to the service described in PDP context
is scheduled, queued etc in the resource manager this last step is repeated (at least once) in each network segment in each network segment a new mapping (DSCP marking, MPLS labeling) might be necessary
user-plane packets entering the PS domain at the GGSN experience the same classification/conditioning etc.
49
QoS management functions for PS Domain - control plane I
TE
Transl. Local Service Control
MT
Adm./Cap. Control
RAN
Adm./Cap. Control
CN EDGE
Adm./Cap. Control Subscr. Control
Gateway
Adm./Cap. Control Transl.
Ext. Netw.
Ext. Service Control
UMTS BS Manager
RAB Manager
UMTS BS Manager
UMTS BS Manager
Local BS Manager
Radio BS Manager
Radio BS Manager
RA BS Manager
RA BS Manager
CN BS Manager BB NS Manager
CN BS Manager BB NS Manager
Ext. BS Manager
RAN ph. BS M protocol interface
RAN ph. BS M
RA NS Manager
RA NS Manager
service primitive interface
Adm./Cap. Control - Admission/Capability Ctrl. Transl. - Translation Subscr. Control - Subscription Control IP BS Mgr - IP Bearer Service Manager
50
QoS management functions for PS Domain - control plane II
Some control-plane QoS management functions are similar to those necessary in IP networks:
Admission and capability control subscription control
The Translation Function translates between IP-specific and UMTSspecific QoS attributes
e.g. between RSVP QoS description and PDP context QoS attributes necessary because app. in UE provides IP specific info, but UE needs to signal PDP context
51
Overview QoS in UMTS
What is QoS? Architecture UMTS Network QoS technology QoS in the UMTS (Core) Network QoS in Real-life UMTS Networks
52
What is necessary beyond the standard presented so far? I
Not everything is standardized by 3GPP.

Only standardize what is necessary for interworking In order to allow differentiation between equipment providers and operators Because time did not permit
may be done in later Releases
Because IP does not provide a solution yet
issues left open by the standard must be solved by equipment providers and operators
53
What is necessary beyond the standard presented so far? II
Equipment providers deduce UMTS product specification from

3GPP Standard own work on open issues
Factors influencing product specification

who are the customers?
incumbent or greenfield? (incumbent operator already owns network)
incumbents likely to be more conservative already own equipment that needs to be integrated
what kind of networks do they operate?
continuous product evolution important

as opposed to completely new design for each release
too expensive for all parties involved
54
Open issues
Some open issues:

QoS provisioning technique Network resource management End-to-end QoS signaling
55
End-to-end QoS signaling
Inter-operator signaling without GRX

E.g. between operators that do not often exchange traffic, or across Internet Was investigated in TR 23.802 Architectural Enhancements for end-toend Quality of Service
Now abandoned
What assumptions to make on QoS Mgmt in non-UMTS network?

Bandwidth Broker? On-path?
What signaling protocol to use?

On-path? Off-path? All-in-one?
56
Summary

In order for UMTS to deliver multimedia services via the PS domain, QoS, particulary IP QoS, needs to be supported 4 QoS classes are offered by the UMTS Bearer Service
conversational, streaming, interactive, background
QoS support includes

QoS signaling
RSVP, DSCPs, SIP, (nsis), PDP context 5 scenarios for end-to-end QoS signaling are described by 3GPP
however they are not guaranteed to work
SLAs across the GRX
resource provisioning technique

overprovisioning, DiffServ, IntServ, MPLS not prescribed by 3GPP
QoS management and control

3GPP specifies
user plane: classification, conditioning, scheduling, queuing control plane: admission control, subscription control, translation
3GPP does not specify

resource management
57

UMTS Networks: Leo Petrak, Dr. Christian Hoene Und Prof. Georg Carle

Uploaded by

Document Information

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 Networks: Leo Petrak, Dr. Christian Hoene Und Prof. Georg Carle

Uploaded by

Copyright:

Available Formats

Lehrstuhl fr Rechnernetze und Internet

Wilhelm-Schickard-Institut fr Informatik Universitt Tbingen

Leo Petrak, Dr. Christian Hoene und Prof. Georg Carle

Motivation Standardization issues UMTS architecture basics UMTS radio link

UE, UTRAN, PS Domain, CS Domain Basic functionalities:

Mobility QoS Security

IMS Charging UMTS Evolution: from R99 to Rel7 Beyond UMTS

UMTS Networks and Internet Telephony Sommersemester 2006

Mobility consequences Mobility in IP networks Mobility in UMTS

cf. TS 23.060 "General Packet Radio Service (GPRS)"

UMTS Networks and Internet Telephony Sommersemester 2006

remove /loose connectivity on old path establish connectivity on new path

UMTS Networks and Internet Telephony Sommersemester 2006

UMTS Networks and Internet Telephony Sommersemester 2006

Mobility consequences Mobility in IP networks Mobility in UMTS

cf. TS 23.060 "General Packet Radio Service (GPRS)"

UMTS Networks and Internet Telephony Sommersemester 2006

IP originally was designed without mobility in mind

IETF HIP WG tackles this problem

IP was extended to also support mobile terminals

UMTS Networks and Internet Telephony Sommersemester 2006

Mobility in IP networks II Mobile IPv4 (MIP)

Mobile terminal uses home address as source address

Registration with Home Agent expires after negotiated life-time

Mobile Terminal signaling traffic data traffic

HA Home Agent FA Foreign Agent

UMTS Networks and Internet Telephony Sommersemester 2006

Mobility in IP networks III

Mobile IPv4 (MIP)cont'

No built-in seamless QoS support

UMTS Networks and Internet Telephony Sommersemester 2006

Mobility consequences Mobility in IP networks Mobility in UMTS

cf. TS 23.060 "General Packet Radio Service (GPRS)"

UMTS Networks and Internet Telephony Sommersemester 2006

Handover SRNC relocation Paging

UMTS Networks and Internet Telephony Sommersemester 2006

Reminder: Mobility Management States

PS Signalling Connection Release PMM-IDLE PS Signalling Connection Establish PMMCONNECTED

UE Mobility Management States

UMTS Networks and Internet Telephony Sommersemester 2006

PS Signalling Connection Release

PMM-IDLE PS Signalling Connection Establish

PMMCONNECTED Serving RNC relocation

SGSN Mobility Management States

Mobility in PMM-Idle Mode I

Routing Area changes

UMTS Networks and Internet Telephony Sommersemester 2006

Mobility in PMM-Idle Mode II

UMTS Networks and Internet Telephony Sommersemester 2006

Mobility in PMM-Connected Mode

updating in regular intervals or upon cell / URA /Routing Area change

Handover controlled by SRNC

UMTS Networks and Internet Telephony Sommersemester 2006

Inter SGSN Routeing Area Update Procedure I

2. SGSN Context Request

Soft and Softer Handover I

Because of Macrodiversity, radio signal picked up by multiple antennas can be combined

SRNC decides on adding / removing connections based on signal-tonoise ratio reported by UE

Core Network Iu DRNC Cells UE Iur SRNC

UMTS Networks and Internet Telephony Sommersemester 2006

Soft and Softer Handover II

UMTS Networks and Internet Telephony Sommersemester 2006

Hard Handover: Macrodiversity cannot be used

Yes/No/- (6) 410 , 10 , 610 (7) 10 , 10 , 10

Yes/No/- (6) 410 , 10 , 610 (7) 10 , 10 , 10