UMTS and IPv6

Presentation Outline

Overview of 3GPP
Introduction to 3GPP architecture
Concepts of the UMTS packet domain
IPv6 in UMTS
Summary
Overview of 3GPP
 Overview of 3GPP
(1/2)
3GPP TSG
ORGANIZATION
TSG GERAN
TSG RAN TSG SA
TSG CN GSM EDGE TSG T
Radio Access Services & System
Core Networks Radio Access Terminals
Network Aspects
Network

T WG 1
RAN WG1
CN WG 1 GERAN WG 1 SA WG 1 Mobile Terminal
Radio Layer 1
MC/CC/CS (lu) Radio Aspects Services Conformance
specification
testing

RAN WG2 T WG 2
CN WG 2 GERAN WG 2 Radio Layer 2 SA WG 2 Mobile Terminal
CAMEL Protocol Aspects spec. & Radio Architecture Services &
Layer 3 RR spec. capabilities

RAN WG3 T WG 3
CN WG 3 GERAN WG 3
Interworking with Base Station Testing
lub spec, lur spec SA WG 3 Universal Subscriber
lu sp ec & UTRAN Security Identity Module
External Networks and O & M
O&M requirements (USIM)

CN WG 4 GERAN WG 4 RAN WG4

SA WG 4
Mobile Station Radio performance
MAP/GTP/BCH/SS Codec
Testing & Protocol aspects

CN WG 5 SA WG 5
OSA
Telecom
(Open Service
Management
Architecture)
 Overview of 3GPP
(2/2)
Technical Work Done in WGs
Meetings
As Necessary
Decision through Consensus or Voting
Most of the Work Done in Meetings
Deliverables
Technical Reports/Technical Specifications
Approval by Consensus or Vote
Change Control When Sufficiently Stable
Inter-WG Coordination
In TSGs
Information Exchange through Liaison Statements
Standards
Releases
The UMTS Architecture
R99 UMTS/GPRS Architecture
SMS-GMSC
SMS-IWMSC SM-SC

E C CAMEL GSM-SCF

Gd

MSC/VLR HLR
D Ge
Gs
A Iu Gc
Gr
R Uu Iu Gi
TE MT UTRAN SGSN GGSN PDN TE
Gn
Ga
Gb Ga
TE MT BSS Gp
Gn Billing
R Um CGF System

GGSN
SGSN Gf EIR
Other PLMN
Signalling Interface
Signalling and Data Transfer Interface
 R99 UMTS/GPRS Architecture
A
Node B Packet
BTS BSC RNC
network
PSTN
Iu
Um
MSC
Gb HLR/AuC SMS-GMSC
Iu Gs Gr
Uu Gd
Gr Gd
SGSN Packet
Gs SS7
network
Gn Network EIR
GPRS
INFRASTRUCTURE MAP-F
IP Gc

BG Gn Packet
Gp Gi
GGSN
network
Internet/Intranet
Packet
Packet network
PLMN
Inter-PLMN
network
Backbone
network
Packet
network
PLMN
 Release 4/5 Architecture
Application and Services IM CN Subsystem

AppServ MRF

I-CSCF
S-CSCF
AppServ

SCP
P-CSCF

Gi
HSS

GGSN
GMSC
MSC

MGW MSC
SGSN
Server

Iu CS Iu PS
RAN
CS Domain PS Domain
 Release 4/5 Architecture
Application and Services IM CN Subsystem

AppServ MRF

I-CSCF
AppServ S-CSCF IPv6
SCP
P-CSCF

Gi
HSS

GGSN
GMSC
MSC

MGW MSC
SGSN
Server

Iu CS Iu PS
RAN
CS Domain PS Domain
 Simplified model for IP Multimedia
Blue line
represents IPv6
Red line
represents IPv6,
may need to inter-
work with IPv4 Mc Mm
Black line S-CSCF
represents existing MRF
IP or/& legacy CS
interfaces Cx
Mw
Mm
External IP
HSS Cx networks
and other IMS
Um Gr Gc networks
Gi Mw I-CSCF
UE GERAN Iu-ps
Gn Go
Mw
SGSN GGSN P-CSCF
Um
Gf
UE UTRAN Iu-ps
Gp EIR Gi

GGSN Gi
Other PLMN

Internet/External
 CS Domain: Signaling & User Plane

MSC MSC
Server Serve
Nc r
Iu-
cs
Mc Mc
UTRA PSTN
Iu-
N
cs
Nb

MGW MGW

This bearer independent architecture makes

possible to use IP transport
CS domain protocol stack using
IP transport option

MAP/CAP

TCAP

SCCP BICC N-ISUP

H.248 M3UA Q.2150.3 M3UA

SCTP SCTP SCTP SCTP

IP IP IP IP

LL LL LL LL

MAP/CAP BICC (Nc) N-ISUP

H.248 (Mc)
Simplified PS Domain Architecture
R Uu Iu Gn Gi Packet Data
TE MT UTRAN SGSN GGSN Network
(PDN)
TE
MS

PS Domain User Plane protocol stack

Application

IP
IP IP
v4 or v6
v4 or v6 v4 or v6

Relay Relay

PDCP PDCP GTPU GTPU GTPU GTPU

RLC RLC UDP/IP UDP/IP UDP/IP UDP/IP

v4 or v6 v4 or v6 v4 or v6 v4 or v6
MAC MAC AAL5 AAL5 L2 L2 L2

L1 L1 ATM ATM L1 L1 L1
Uu Iu-PS Gn Gi

MS UTRAN 3GSGSN 3GGGSN

 MT-TE Configuration

IP based services
TE R ref
MT

Application

IP
IP RELAY

L2/PPP L2/PPP Packet Domain

Bearer
L1 L1

Note: MT and TE can be physically separated or physically co-located

 User plane vs transport plane

User IPv6

Application
Terminal GGSN
Server

UTRAN Core Network

Transport IPv6

User and transport planes are completely independent, i.e. the transport
plane can run on a different IP version than the user plane
UTRAN and Core Network transport can also run on different IP
versions
 Transport of user IP packets in UMTS

User IPv6 (PDP type IPv6)

Application
UTRAN SGSN GGSN
Terminal Server

Radio Bearer GTP-U GTP-U

IP packets to/from the terminal are tunneled through the UMTS

network, they are not routed directly at the IP level.
 The PDP Context

Same PDP (IP) address and APN

ISP X
GGSN

PDP Context X 1(APN X, IP address X, QoS 1)

APN X
PDP Context X 2(APN X, IP address X, QoS 2)

SGSN
PDP Context selection ISP Y
Terminal based on TFT (downstream)
GGSN

APN Y
PDP Context Y (APN Y, IP address Y, QoS)

APN Z
PDP Context Z (APN Z, IP address Z, QoS)

ISP Z
 The PDP CONTEXT

When an MS attaches to the Network, the SGSN creates a Mobility

Management context containing information pertaining to e.g.,
mobility and security for the MS.

At PDP Context Activation (PDP - Packet Data Protocol), the SGSN

and GGSN create a PDP context, containing information about the
session (e.g. IP address, QoS, routing information , etc.),

Note: Each Subscriber may activate several PDP Contexts towards the
same or different GGSNs. When activated towards the same GGSN,
they can use the same or different IP addresses.
 The Access Point Name - APN

The APN is a logical name referring to a GGSN. The APN also

identifies an external network.

The syntax of the APN corresponds to a fully qualified name.

At PDP context activation, the SGSN performs a DNS query to find

out the GGSN(s) serving the APN requested by the terminal.

The DNS response contains a list of GGSN addresses from which the
SGSN selects one address in a round-robin fashion (for this APN).
 Traffic Flow Template (TFT)

A TFT is a packet filter allowing the GGSN to classify packets

received from the external network into the proper PDP context.

A TFT consists of a set of packet filters, each containing a

combination of the following attributes:
Source Address and Subnet Mask
Destination Port Range
Source Port Range
IPsec Security Parameter Index (SPI)
Type of Service (TOS) (IPv4) / Traffic Class (IPv6) and Mask
Flow Label (IPv6)
 GPRS Tunneling Protocol

GTP is a simple tunneling protocol based on UDP/IP, used both in

GSM/GPRS and UMTS.

A GTP tunnel is identified at each end by a Tunnel Endpoint Identifier

(TEID)

For every MS, one GTP-C tunnel is established for signalling and a
number of GTP-U tunnels, one per PDP context (i.e. session), are
established for user traffic.
QoS Management Functions in UMTS
P-CSCF
Local Policy Control
SIP proxy Function

UE UTRAN SGSN GGSN External

Network
IP BS IP BS External
Manager Manager Service Control

Adm/Cap. Adm/Cap. Subsc. Adm/Cap.

Transl. Adm/Cap. Transl.
Control Control Control Control
Control

UMTS BS UMTS BS UMTS BS

Manager Manager Manager
RAB
Manager

Radio BS Radio BS Iu BS Iu BS CN BS CN BS
Manager Manager Manager Manager Manager Manager

UTRA UTRA Iu NS Iu NS BB NS BB NS
ph. BS M ph. BS M Manager Manager Manager Manager

Protocol interface Service primitive interface

 IP BS Manager

is used to control the external IP bearer service to provide IP QoS

end-to-end.
communicates with the UMTS BS manager through the translation
function.
uses standard IP mechanisms to manage the IP bearer service.
may exist both in the UE and the Gateway node, and it is possible
that these IP BS Managers communicate directly with each other by
using relevant signalling protocols, e.g., RSVP
is the policy enforcement point for Service-based Local Policy
control
 Policy Control Function (PCF)

is a logical entity that is co-located with the P-CSCF (the interface

between the P-CSCF and PCF is not standardized in Release 5)
is a logical policy decision element which uses standard IP
mechanisms to implement Service-based Local Policy in the bearer
level
enables coordination between events in the SIP session level and
resource management in the bearer level
makes policy decisions based on information obtained from the P-
CSCF
has a protocol interface with GGSN (Go interface) which supports
the transfer of information and policy decisions between the policy
decision point and the IP BS Manager in the GGSN (following
COPS framework)
 IP BS Manager capability
in the UE and GGSN

Table 1: IP BS Manager capability in the UE and GGSN

Capability UE GGSN

DiffServ Edge Function Optional Required

RSVP/Intserv Optional Optional
IP Policy Enforcement Point Optional Required (*)

(*) Although the capability of IP policy enforcement is required within the GGSN, the
control of IP policy through the GGSN is a network operator choice.
IPv6 Details
 IPv6 History in UMTS
IPv6 in the 3GPP standards
User plane: PDP Type IPv6 introduced in GPRS R97

Transport plane: IPv6 is optional

UTRAN: IP transport study is being conducted right now

IMS: The IP Multimedia Core Network Subsystem has

been standardized to be based on the following IPv6
support:
- The architecture shall make optimum use of IPv6.
- The IM CN subsystem shall exclusively support IPv6.
- The UE shall exclusively support IPv6 for the connection to services
provided by the IM CN subsystem.
 IPv6 Address Allocation Methods
Stateless Address Autoconfiguration
Introduced in GPRS R99

Stateful Address Autoconfiguration

DHCPv6 client in the terminal
Requires DHCPv6 relay agent in the GGSN

GPRS-specific Address Configuration

Static Address Configuration
The MS provides its statically configured IPv6 address at PDP context
activation
Dynamic Address Allocation
The IPv6 address is provided by the GGSN at PDP context activation
Dynamic Address Allocation in UMTS/GPRS

MS BSS/UTRAN SGSN GGSN

1. Activate PDP Context Request (PDP type = IPv6, PDP Address = empty, APN, ...)

2. Create PDP Context Request

3. DHCP and/or RADIUS procedures

4. Create PDP Context Response (

PDP address = IPv6 address, ...)

5. Activate PDP Context Accept (PDP Address = IPv6 address, ...)

For example the GGSN may use
RADIUS for user authentication
and IP address allocation, or it may
use RADIUS for authentication and
DHCP for IP address allocation.

Alternatively, the address may be

allocated from a local pool of
addresses in the GGSN.
 Stateless Address Autoconfiguration in
UMTS/GPRS
MS BSS/UTRAN SGSN GGSN

1. Activate PDP Context Request (PDP type = IPv6, PDP Address = empty, APN, ...)

2. Create PDP Context Request

The MS extracts the 3. Create PDP Context Response (

Interface-ID from the PDP address = link-local address, ...)
link-local address
4. Activate PDP Context Accept (PDP Address = link-local address, ...)

5. Router Solicitation The GGSN shall be configured to

The MS constructs
advertise only one network prefix
its full IPv6 address
6. Router Advertisement (M flag = 0, Network prefix, )
Neighbor Solicitation messages
7. Neighbor Solicitation shall be discarded by the
GGSN except if part of
Neighbor Unreachability
7. GGSN-Initiated PDP Context Modification Procedure
Detection

The GGSN updates the SGSN and

MT with the full IPv6 address
 Header Compression
R Uu Iu Gn Gi Packet Data
TE MT UTRAN SGSN GGSN Network
(PDN)
TE
MS

PS Domain User Plane protocol stack

Header Compression: Application

RFC2507 IP
v4 or v6 IP IP
v4 or v6 v4 or v6
RFC
Relay Relay

PDCP PDCP GTPU GTPU GTPU GTPU

RLC RLC UDP/IP UDP/IP UDP/IP UDP/IP

v4 or v6 v4 or v6 v4 or v6 v4 or v6
MAC MAC AAL5 AAL5 L2 L2 L2

L1 L1 ATM ATM L1 L1 L1
Uu Iu-PS Gn Gi

MS UTRAN 3GSGSN 3GGGSN

 IPv4/IPv6 Transition

Text in 23.221 shows examples of transition:

Dual Stack
NAT/PT
Tunneling

These are only examples to show how transition could be done.

They are not mandatory to implement/deploy.

 Contact

Juan-Antonio Ibanez Jonne Soininen

Ericsson Nokia

Juan-Antonio.Ibanez@eed.ericsson jonne.soininen@nokia.com
.se