QoS-aware Mobility Management for Convergence

QoSQoS--aware Mobility aware Mobility yyManagement for Convergence Management for Convergence

2009. 6. 25.

Nam-Seok Ko([email protected])

FMC Technology Research Team

Network Research Division

([email protected])

Electronics and Telecommunications Research Institute

KRNET 2009KRNET 2009

ContentsContents

IntroductionIP MobilityIP Mobility

NGN, 3GPP LTE/SAE, WiMAX

Dynamic Policy and QoS ControlNGN, 3GPP LTE/SAE, WiMAX

QoS-aware MobilityNGN, 3GPP LTE/SAE, WiMAX

SummaryDiscussionDiscussion

2 KRNET 2009KRNET 2009

Convergence in Network PerspectiveConvergence in Network PerspectiveNGN (ITU-T/TISPAN)

Packet-based (IP-based) Network

ITU-T’s definition of NGN : A packet-based network able to provide services including Telecommunication Services and able to make use of multiple broadband, QoS-enabled transport technologies and in which service related functions are independent from underlying transport

IMS-based Service Control

Dynamic Policy-based Service Control (RACF, RACS)

IP-based Mobility (Host-based and Network-based Mobility Architectures)

service-related functions are independent from underlying transport related technologies.

IP based Mobility (Host based and Network based Mobility Architectures)MMCF (Mobility Management and Control Function)

3GPP LTE/SAEAll IP NetworkAll IP Network

Application-based (including IMS-based) Service Control

Dynamic Policy-based Service Control (PCC) – Merging Policy and Charging into a F iFunction

IP-based Mobility (PMIP, DSMIPv6, MIPv4 FA Mode)

WiMAXAll IP Network

Application-based (including IMS-based) Service Control (Rel 1.5)

Dynamic Policy-based Service Control (PCC) – 3GPP R7 compliant

3

Dynamic Policy-based Service Control (PCC) 3GPP R7 compliant

IP-based Mobility (CMIPv4, PMIPv4, CMIPv6, PMIPv6)KRNET 2009KRNET 2009

Convergence in ITUConvergence in ITU--T NGNT NGN

Service Stratum

Applications

Application FunctionsApplication Support Functions and Service Support Functions

ServiceControl

A dOther NGN Service

ComponentsS. UserProfile

Oth

Oth

And Delivery Functions

Components

IP Multimedia Component

FunctionsIPTV

Service ComponentPSTN / ISDN Emulation

Service Component

IP Multimedia

LegacyTerminals

her Netw

orksher N

etworks

Network Attachment Control Functions

Resource and AdmissionControl FunctionsUserT. UserGWGW

&PSTN/ISDN Simulation

GWGW

IP MultimediaService Component

Mobility ManagementControl Functions

LegacyTerminals

Core transport

CustomerNetworks Core Transport

Control Functions(NACF)

Access Network

Control Functions (RACF)ProfileProfile

Function

GWGW Control Functions (MMCF)

Transport StratumEnd-UserFunctions

Core transport Functions

NGNTerminals

pFunctions

EdgeFunctions

Access Transport Functions

Access NetworkFunctions

4

Functions


Source : ITU-T NGN FRA R2 Revision Draft

Convergence in TISPAN NGNConvergence in TISPAN NGN

Applications

Other SubsystemComponents

DataBase

…

PSTN / ISDN Emulation

Other N

etw

IP Multimedia Component (Core IMS)

ICF

RACSNASS

LegacyTerminals

works

PSTN / ISDGW

LegacyTerminals

Core transport Network

Access Transport IP

CustomerNetworks

DN

I-BGF

T-MGFGW

NGN Terminals

LegacyTerminals

3GPP IP-CAN

a poNetwork

3GPP Terminals

NGN Terminals

5

Source : EU workshop on NGN, 2005


Convergence Big PictureConvergence Big Picture

Application(SIP AS,OSA SCS

IM SSF

ASHSS

‘IMS Data’OSA AS,

CAMEL SE)

IM SSFSIP AS

IMS Data

HLR/AuC (‘CS/PS’)

SLF

BGCFSignalling

User Plane Data

MGCF

I-CSCFS-CSCF

CSCF

P-CSCF

PCRF

CS NetworksSGW

MGCF

SPDF/ A-RACF(PD-FE)

RACS (RACF)

NASS (NACF)

MRF IMS GWMMCF

NGN

UE DSLAM

IPv4 PDN

CS Networks(PSTN, CS PLMN)

IMS-MGWBS

MRFC

MRFP

ALG

TrGW

BRAS RCEF(PE-FE)

PDF

IP mobility based on MMCF

MMCF

WiMAX

UE

UE

IPv6 PDN(IPv6 Network)

N(IPv4 Network)

SFM

ASN-GW(FA, MAG)

BBERF

HA C-PCEFSFA/

A-PCEF

P-GWS-GW

CMIP4/6, PMIP4/6 BG

BB(IPv4/IPv6)

6

3GPP

UE


BBERF PCEFP GW

(HA/LMA)S GW(MAG)

PMIP, DSMIPv6, MIPv4eNB

MobilityMobilityMobilityMobility


IETF IETF -- Proxy Mobile IPv6 (Proxy Mobile IPv6 (PMIPv6, RFC 5213PMIPv6, RFC 5213))

Key FeaturesIP address does not change across access CN

networks as long as the user stay within a “PMIP domain”

Mobility signalling is handled by network agents (MAGs) instead of MNs

Internet

agents (MAGs) instead of MNs

Related IDs in NETLMM WGIPv4 Support for Proxy Mobile IPv6

GRE K O ti f P M bil IP 6

LMA

Network-based Tunnel(IP-in-IP, GRE, etc.)

LMA

GRE Key Option for Proxy Mobile IPv6

Heartbeat Mechanism for Proxy Mobile IPv6

Interactions between PMIPv6 and MIPv6: scenarios and related issues

Local Network(a PMIP domain)

MAG1

Proxy mobility signalling instead of MN

MAG2Advertise the same prefix for the MN so that MN may scenarios and related issuesnot realize that it has moved in layer 3 perspective.

moveMN


IETF IETF -- Dual Stack Mobile IPv6 (Dual Stack Mobile IPv6 (DSMIPv6, RFC 5555DSMIPv6, RFC 5555))

Maintaining binding cache for both IPv4 and IPv6 HoAs

Key FeaturesExtend Mobile IPv6 to support IPv4 instead of

i i i l f IP 4 & IP 6

HANAT

Dual Stack HA

maintaining separate protocols for IPv4 & IPv6Mobile IPv6 BU message (IPv4 Home Address option, IPv4 Care-of Address option)

Mobile IPv6 BU message (IPv4 Address

Host-based Tunnel

IPv4IPv4

IPv6Private IPv4

Mobile IPv6 BU message (IPv4 Address Acknowledgement option, NAT Detection option)

Mobility support independent of IP version of underlying access network

Support NAT TraversalUDP header is added when a NAT is detected

Route optimization is not supported in a visited network that supports IPv4 onlyMN

w/ IPv4 HoA and IPv6 HoA

Running IPv4 and/or IPv6 applications independent of IP version of the underlying access network

network that supports IPv4 only

Related IDs in MEXT WGBinding Revocation for IPv6 Mobility

Mobility Support in IPv6 (RFC 3775bis)access network Mobility Support in IPv6 (RFC 3775bis)

Home Agent Reliability Protocol

Flow Bindings

Multiple CoA

9

Multiple CoA

Prefix Delegation


ITUITU--T Mobility T Mobility –– MMCF (MMCF (Mobility Management and Control FunctionMobility Management and Control Function))MMCF

NACFM9MLM-FE

Mobility location management (e.g. MIP binding and PMIP proxy binding)

Handover decision and control f ti b i t ti ith

HGWC-FE

M1

M8

M9

M10

MLM FE

TLM-FE TUP-FE

RACF

HDC FE PD FE

function by interacting with RACF

M2

M12

M11

AM FE

NAC-FE TAA-FE

M13NID-FE

HDC-FE

TRC--FE

PD-FE

Control plane

NIR-FE

M3M4

M5M7

AM-FE

UE

Network information distribution function (which can be mapped to a part of MIH)Network information

repository function

Control planeForwarding plane

M5

M6

AR-FEAR-FE

L2 TransportFunctions

AN-FE Packet TransportFunctions

L2HE-FE

L3HEF

EN-FE

L3HEF

ABG-FE

L3HEF

IBG-FE


Access Transport Core TransportSource : Y.2018 (Formerly Y.MMCF)

3GPP SAE 3GPP SAE –– IP MobilityIP MobilityInterface Protocols Spec

S5/S8 (GTP) GTP/UDP/IP 29.274S5/S8 (PMIP) CP: PMIP/IP, UP: GRE/IP 29.275S2a PMIP/IP or MIPv4/UDP/IP 29 275

2G/3GSGSN HSS

S3

UTRAN

GERAN

S2a PMIP/IP, or MIPv4/UDP/IP 29.275S2b PMIP/IP 29.275S2c DSMIPv6, IKEv2 24.303SWn PMIP 29.275SWu IKEv2, MOBIKE 24.302

MME

S3

S1-MME

S6a

S4Gx

RxGxc

Gxb

PCRF

PDNGateway(LMA/HA)

Operators’s IP Services (e.g. IMS, PSS, …)

S10

S1-U

S11SGi

SWxeNBUELTE-Uu S5/

S8

ServingGateway(MAG)

3GPP AAAServer

S2cS2a

S2bS6b

SWmS2c

S2cX2Gxa

ePDG(MAG)

Untrusted non-3GPP Network

SWaSWn

Trusted non-3GPP Network

AGW(MAG or FA)

e.g. ASN-GW, HSGW SWu

11

STa


UE

3GPP SAE 3GPP SAE –– IP MobilityIP MobilitySAE supports both host-based and network-based mobility management solutions

Dual-Stack MIPv6 (host-based)

Proxy MIPv6 and MIPv4 in Foreign Agent mode (network-based)

PDN GW works as MIP/PMIP Home Agent/LMAPDN GW works as MIP/PMIP Home Agent/LMAWhen connected to a 3GPP access the UE can be assumed to be at home in MIP sense

M bilit ithi 3GPP (E UTRAN UTRAN d GERAN) i d i Mobility within 3GPP accesses (E-UTRAN, UTRAN and GERAN) is managed in a network-based fashion using 3GPP-specific protocols

Service continuity is guaranteed in case the UE moves from a 3GPP access to a 3GPP ( i )non-3GPP access (or vice versa)

UE communicates using the same IP address independently of the access network it is attached to

Serving GW and ePDG work as PMIP MAGTrusted AGW (such as HSGW) works as PMIP MAG or MIPv4 FA


Mobile Mobile WiMAXWiMAX –– IP MobilityIP Mobility• Session mobility management• Foreign agent (FA), PMIP Client• Connectivity to selected CSN• ASN Radio Resource Management • Location Management & Paging• Mobility Management

ASN

CSN

• Mobility Management• Network Entry (AAA proxy & temporary DB mgmt)• AAA client• ASN admission control• Data Path Function (DPF)• DHCP Proxy/Relay

• Manage 802.16 Air Interface• Handle Backhaul interface

toward ASN GW• Handover control (i.e. decision

point of handover in controlled HO d )

R3BS

R8

R6

R6

ASN GW

MIPHA AAA

HLRHSS DHCP

PolicyServer

CSN

ASN-anchoredMobility

HO mode)

R4R5 (Roaming)

BSR6 HA AAA HSS

CSN-anchoredMobility(IETF based Mobility Protocols)

MS

R4

Another Operator’s CSNASN

(IETF-based Mobility Protocols)

MIPHA AAA

HLRHSS DHCP

PolicyServer

NAP (Network Access Provider) NSP (Network Service Provider)

13

NAP (Network Access Provider) NSP (Network Service Provider)


Mobile Mobile WiMAXWiMAX –– IP MobilityIP MobilityASN Anchored Mobility Management

R6 Mobility (BS and ASN-GW), R8 Mobility (inter-BS handover)

Related FunctionsHandover Function

Mobile-initiated, network-initiated, and fast handover such as FBSS and MDHO

Data Path Functionanchor, serving, target, and relay DP function

Context Function

Data Integrity mechanismsBuffering and Bi/multicasting

Completely transparent to the core network (CSN)

CSN Anchored Mobility ManagementR3 Mobility (ASN-GW and HA), R4 Mobility (between ASN-GWs)

IP mobility yCMIPv4, PMIPv4, CMIPv6 (NWG Rel 1.0)

PMIPv6, Simple IPv4, Simple IPv6 (NWG Rel 1.5)

FA and PMIP Client resides in ASN-GW with Authenticator and establishes MIP

14

signaling between FA and HA


Mobility Mobility –– Summary Summary IETF-based Mobility in IP-based NetworksTwo main protocols in each of host-based and network-based pmobility architecture

Proxy Mobile IPv6

Dual stack Mobile IPv6Dual-stack Mobile IPv6

ITU-T 3GPP/SAE TISPAN WiMAX Cable

Layer 2

MMCF-Host-based

MMEServing GW

* GTP tunneling

N/A ASN-Anchored Mobility N/A

PDN-GWprotocols-Network-based protocolsLayer 3

PDN GWServing GW

* Protocols- DSMIPv6- PMIPv6

N/ACSN-Anchored Mobility- CMIP (CCoA, FA-CoA)- PMIP

N/A

PMIPv6- CMIP

Remarks Framework level design

Non-3GPP access networks (WiMAX, WiFi, HRPD) are also considered

N/AInterworking with non-WiMAX networks is considered

N/A


< Comparison of Mobility Functions in Major SDOs and Fora >

Dynamic Policy (Dynamic Policy (QoSQoS) Control) ControlDynamic Policy (Dynamic Policy (QoSQoS) Control) Control


ITUITU--T NGN T NGN –– QoSQoS ArchitectureArchitecture

Service Control Functions

RACFNACF Oth

Service StratumTransport Stratum

PD‐FE

Rs

RiRdRu

er NGNs

Rn Rc Rw

RtRp

RhMMCF

TRC‐FE

CGPE-FECPN

PE-FE

Transport Functions

TRE-FE

PD-FE is for transport independent aspect TRC-FE is for transport dependent aspect. Session based and aggregated level (VLAN Port etc ) resource control isSession-based and aggregated level (VLAN, Port, etc.) resource control is performed in PD-FE

Push and Pull modeI t f b t MMCF d PD FE ill b d fi d f Q S bilit

17

Interface between MMCF and PD-FE will be defined for QoS-aware mobility


ITUITU--T NGN T NGN –– QoS Architecture (Cont’d)QoS Architecture (Cont’d)

Service Control FunctionsService Control Functions

RACF

(1) Service Request(2) Authorization

Request

RACF

(1) Service Request(2) Admission and

Resource Request (3) Authorization

Response

Transport FunctionsCPE

(5) Policy Decision Request

(6) Policy Decision Response

Transport FunctionsCPE

(3) Policy Enforcement Request

(4) QoS Request

< Push Mode > < Pull Mode >


3GPP SAE 3GPP SAE –– PCC ArchitecturePCC ArchitectureInterface Protocols Spec

Gx Diameter/SCTP/IP 29.212Gxa Diameter/SCTP/IP 29.212Gxb Diameter/SCTP/IP 29.212Gxc Diameter/SCTP/IP 29.212Rx Diameter/SCTP/IP 29.2142G/3G

SGSN HSS

S3

UTRAN

GERAN

MME

S3

S1-MME

S6a

S4Gx

RxGxc

Gxb

PCRF

PDNGateway(PCEF)

Operators’s IP Services (e.g. IMS, PSS, …)

S10

S1-U

S11SGi

SWxeNBUELTE-Uu S5/

S8

ServingGateway(BBERF)

3GPP AAAServer

S2cS2a

S2bS6b

SWm

SWn

S2c

S2cX2Gxa

ePDG(BBERF)

Untrusted non-3GPP Network

SWa

SWn

Trusted non-3GPP Network

AGW(BBERF)

e.g. ASN-GW, HSGW SWu

19

STaUE


3GPP SAE 3GPP SAE –– PCC Architecture (Cont’d)PCC Architecture (Cont’d)Combines the Flow Based Charging and Service Based Local Policy to form the Policy Control and Charging (PCC) architecture

PCRF (Policy and Charging Rule Function) and PCEF (Policy and Charging Enforcement Function)

Both push and pull mode operations are supportedAF is no longer limited to IMS specific elementsPCRF is split into home domain and visited domain functionsInteraction between the PCRF and the transport layer has been extended

PCRF interacts and enforces PCC rules across a greater number of access technologies and QoS g g Qmodels

PCEF is separated into the Serving Gateway, the Packet Data Network (PDN) Gateway, and the evolved Packet Data Gateway (ePDG)

QoS Class Identifier (QCI)– Control bearer level packet forwarding treatment (e.g. scheduling weights, admission thresholds, queue management thresholds, link

layer protocol configuration, etc.)Allocation and Retention Priority (ARP)

Service level QoS parameters

Allocation and Retention Priority (ARP)– Decide whether a bearer establishment/modification request can be accepted or notGuaranteed Bit Rate (GBR)

– Bit rate that can be expected to be provided by a GBR bearerMaximum Bit Rate (MBR)

– Limits the bit rate that can be expected to be provided by a GBR bearer

20

p p yper APN Aggregate Maximum Bit Rate (APN-AMBR).per UE Aggregate Maximum Bit Rate (UE-AMBR)


3GPP SAE 3GPP SAE –– PCC Architecture (Cont’d)PCC Architecture (Cont’d)

UEAF session signalling,

AFMaps the application specific

Application

AF session signalling, possibly with SDI

i

SDI Mapping function

Maps the application specific information into the appropriate AVPs

GW

PCEF/BBERF PCRF

IP BS Manager

Serviceinformation

Rx

IP BS ManagerTranslation /

Mapping function

Gx/Gxx Policy EngineAuthz IP QoS

parameters

Authorizes the IP flows described within service information by mapping from service information to authorized IP QoSTranslation /

Mapping function

Access-Access-

authorized IP QoSparameters (e.g. QCI, GBR, MBR, ARP, …) for transfer to the PCEF/BBERF via the Gx/Gxx interface

Specific BS Manager

Specific BS Manager Access-specific

QoS parameters

Map from the authorized IP QoS parameters

21

Map from the authorized IP QoS parameters to the access specific QoS parameters


Source : 3GPP TS 29.213

3GPP SAE 3GPP SAE –– QoSQoS Mapping in BearerMapping in BearerTwo levels of QoS control

Service data flows

High

Service data flow templates (downlink parts), applied in order of precedence.

aHigh

Service data flow templates (uplink parts), associated with the IP-CAN bearer, applied in order of precedence a

IP packet of service data flow “a”a

ec

da

b

cIP-CAN bearers

Uplink IP packets

IP-CANbearersa

fb

d

e

bearers

d

bearers

discardIP packet of service data flow “d”

d

Precedence Precedence

Lowf

discard

Low

Service Data Flow (SDF) is characterized by the IP 5-tuple (source IP address, destination IP address, source port number, destination port number, protocol ID of the protocol above IP)SDF flows transported by the EPS bearer will be applied to the same packet scheduling algorithm, using the same priority, the same E-UTRAN RLC configuration, etc.

22

g



3GPP SAE 3GPP SAE –– PCC Logical ArchitecturePCC Logical Architecture

O li Ch i S t (OCS)Subscription ProfileRepository

(SPR)

Rx

AFSp Online Charging System (OCS)

Service Data FlowBased

Credit Control

In roaming case, PCRF is divided into two H-PCRF and V-PCRF. S9 reference point is defined for that

Policy and Charging Rules Function(PCRF)

that.

Gateway control session through which requests and receives

Gy

GxGxx

which requests and receives Gateway Control and QoS Rules.IP header information (Framed-IP-Address AVP or Framed-IP-Prefix AVP) is delivered to PCRF

CoA-Information AVP is delivered from PCEF to PCRF

Gy

GzOffline

ChargingSystem

IP-CAN session- Bearer binding

l k b b d

(Serving GW, ePDG, or HSGW)

BBERF PCEF

System(OFCS)

< Non-roaming Case >

- Uplink bearer binding verification

- Event reporting to the PCRF- Sending or receiving IP-CAN-specific parameters, to or from the PCRF

Gateway

23

< Non-roaming Case >



3GPP SAE 3GPP SAE –– Dynamic PCC FlowDynamic PCC Flow

BBERFMME PCEF V-PCRF H-PCRFeNBUE

IP-CAN specific resource request/release initiated by UE

Access Dependent Policy Enforcement

Gateway Control QoS Policy Rules Provision - begin

p y(Dedicated bearer creation, etc.)

Gateway Control QoS Policy Rules Provision - end

PCC Rules Provision Procedure

24



3GPP SAE 3GPP SAE –– Gateway Control SessionGateway Control SessionGateway Control (GC) Session

An association between a BBERF and a PCRF, used for transferring access specific parameters, BBERF events and QoS rules between PCRF and BBERF

When a Trusted or Untrusted Non-3GPP IP Access to 3GPP Access handover occurs and a PMIP-based S5/S8 Interface is used, the Serving GW sends a Gateway Control Session Establishment (IP CAN Type, MN NAI, APN, RAT Type) message to the PCRF.

Two kinds of GC sessionA GC session that serves a single IP-CAN session (e g S-GW/BBERF connecting to A GC session that serves a single IP CAN session (e.g. S GW/BBERF connecting to PDN-GW using S5/S8 PMIP).

A GC session that serves all the IP-CAN sessions from the same UE (e.g. a GW/BBERF connecting to PDN-GW using S2c)GW/BBERF connecting to PDN GW using S2c).


3GPP SAE 3GPP SAE –– Gateway Control Session (Cont’d) Gateway Control Session (Cont’d)

Establish Gateway Control Session Request

BBERF PCEFV-PCRF H-PCRF

O i l PCRF d i

Gateway Control Session Establishment

PCRF initiated IP-CAN Session Modification Procedure

Optional, PCRF may need to waits until it gets informed about the establishment of the corresponding IP-CAN session

Session Modification Procedure

Acknowledge Gateway Control Establishment

Deploy QoS Rules and Event Triggersand Event Triggers

Establish Gateway Control Session Reply



3GPP SAE 3GPP SAE –– IPIP--CAN SessionCAN SessionCase 1 – No Gateway Control Session is required

No Gateway Control Establishment occurs at all (e.g. 3GPP Access where GTP-based S5/S8 are employed.)

Case 2 – A Gateway Control Session is required

Case 2a) - All IP-CAN sessions using a CoA are handled by the same Gateway Control SessionCase 2a) - All IP-CAN sessions using a CoA are handled by the same Gateway Control Session.

The BBERF assigns a Care of Address (CoA) to the UE and establishes a Gateway Control Session prior to any IP-CAN session establishment.

Case 2b) - Each IP-CAN session is handled in a separate Gateway Control Session.Case 2b) Each IP CAN session is handled in a separate Gateway Control Session.

At IP-CAN session establishment A Gateway Control Session is required before the PCEF announces the IP-CAN Session to the PCRF.

At BBERF change and pre-registration The Gateway Control Session shall match an IP-CAN session that the PCEF has already announced.


3GPP SAE 3GPP SAE –– IPIP--CAN Session (Cont’d)CAN Session (Cont’d)

G t C t l S i E t bli h t ( 2 d 2b)

BBERF H-PCRFPCEF V-PCRF SPR OCS

Gateway Control Session Establishment (case 2a and 2b)

Establish IP-CAN Bearer Request

Indication of IP CAN Session Establishment

Profile Request

Profile Response

Policy Decision

Acknowledge IP CAN Session Establishment

Credit Request

Credit Response

Establish IP-CAN Bearer ResponseEstablish IP CAN Bearer Response

IP CAN Bearer SignalingIP CAN Session Establishment Acknowledge

Install PCC Rules. Policy enforcement



Mobile Mobile WiMAXWiMAX –– PCC ArchitecturePCC Architecture

ASN CSN ASP

ASN 1

Translate the policy and charging rules from PCRF/PDF to the WiMAX specific QoS and charging attributes 3GPP Rel 7 compliant PCC frameworkASN 1

Policy Distribution

Function

PCC-R3-P Gx Rx

S

AF(P-CSCF or

non-IMS application )

ASN-GW

R6

BS

A-PCEF

Accounting

SFA

g g 3GPP Rel. 7 compliant PCC framework

Local RscInfo

LPF

Local Policy DB

SFM

PCRF

SPR/ AAA

PCC-R3-OFC

Sp server)

Gz

Accounting Client

Responsible for the creation, admission, activation, modification and deletion of

Interworking function between WiMAX ASN d

Data Path Func

Data Path Func

OFCS

OCSPCC-R3-OCR4

PC

C-R

3-OFC

802.16 service flows WiMAX ASN and 3GPP core network

C-PCEF

HA

GyASN 2

R6A PCEF

SFALocal RscInfo

Local Policy DB

ASN-GWBS

R3-MIP

Home IP Network

C-PCEF

Accounting Client

A-PCEF

Accounting Client

LPFSFM

Data Path FuncData Path Func


Mobile Mobile WiMAXWiMAX –– Dynamic Flow CreationDynamic Flow CreationA service flow is mapped to :

A unique Service Flow ID (SFID) and connection ID (CID)Each CID is characterized by a Mobile Subscriber Station (MSS) ID, link direction and QoS service class

A hS i A hS iAnchorSFA

ServingSFASFMMS

RR-Request

DP-Reg-Request

AnchorSFA

ServingSFASFMMS

Apply Admission

DSA-Request

Apply Admission Control

DSA-Request

pp yControl

RR-RequestDP-Reg-Request

Perform Policy D i i

DSA-Response

DP-Reg-ResponseDP-Reg-Response

RR-ResponseDecision

Assign ResourceRR-ResponseDSA-Ack

DSA-Response

DSA-Ack

Assign Resource


< SF Creation by ASN > < SF Creation by MS >Source : WiMAX NWG Rel. 1.2

Dynamic Policy (Dynamic Policy (QoSQoS) Control ) Control –– SummarySummaryDynamic Policy-based Resource and QoS Control per Service

Push and Pull mode

Both of session level and aggregate-level QoS in transport level are assumed

ITU-T 3GPP/SAE TISPAN WiMAX Cable

Policy Decision PD-FE PCRF SPDF, A-RACF (partial) PCRF, PDF PAM, PS

Transport Resource Control TRC-FE N/A A-RACF (partial) N/A N/A

Policy Enforcement PE-FE PCEF RCEF, BGF PCEF CMTS

Remarks N/A N/A N/A 3GPP R7 compliant N/A

< Comparison of QoS and Resource Control Functions in Major SDOs and Fora >


QoSQoS aware Mobilityaware MobilityQoSQoS--aware Mobilityaware Mobility


Why QoSWhy QoS--aware in IP aware in IP Mobility?Mobility?QoS-awareness is described in dynamic policy control point of view in this presentation Need to re-enforce policies to new network nodes through which traffic from a moved UE is passing

Initial Policy Enforcement Points

CN

Need to re-enforce policies- IP session information change- Network resource changeg

UE

UE


Why QoSWhy QoS--aware in IP aware in IP Mobility? (Cont’d)Mobility? (Cont’d)

Application Function is not aware of UE’s movement, so it will enforce QoS based on the UE’s HoAenforce QoS based on the UE s HoA

The policy/QoS enforcement points may be the ones at the UE’s original location if there is no prior information about UE’s movement

How could RACF/PCRF know the proper QoS provisioning points?How could RACF/PCRF know the proper QoS provisioning points?Mobility related functions should notify UE’s movement as soon as they detect UE’s movement

RACF Mobility

RACF/PCRF will enforce policy and QoS to the policy enforcement points (PE-

CN

RACF orPCRF

Mobility Related

Functions

to the policy enforcement points (PEFE/PCEF) at UE’s original location if they do not receive any information about MN’s movement

proper QoS provisioning points

MN

34

MNMN


Consideration in Dynamic Policy Control in Consideration in Dynamic Policy Control in MobilityMobility

Original IP header information is lost when a mobile UE movesData traffic may be tunneled

MobilityMobility

Data traffic may be tunneled

RACF/PCRF could provision resource based on the new IP header information

CN

Tunnel

Original IP header cannot be not expected in network nodes because of tunneling

MNMN

MN


ITUITU--T NGN QoST NGN QoS--aware Mobilityaware Mobility

SCFMMCF

3HDC-FE

MLM-FE

2 4’5’

PD-FE

TRC-FE

1

66

PD-FE7NACF 5

8PD-FE

5NACF

6

7

8

4

TRC-FE66

88

8 8

TRC-FE

88

PE-FE PE-FEMNCUE

targetaccess access

corePE-FE PE-FE PE-FE PE-FE

[1] Binding Update Req[2] Handover Request[3] Resource Re-provisioning

Request (w/ IP address m ppin inf m ti n)

[4] Policy Check[4’] Handover Response[5] Resource Request[5’] Binding Update

Response

[6] Resource Check[7] Subscription Check[8] Commit Resource

Mobility control messageResource control message

36

mapping information) Response


3GPP SAE 3GPP SAE QoSQoS--aware Mobilityaware Mobility(PMIP(PMIP--based Initial Attachment)based Initial Attachment)(PMIP(PMIP--based Initial Attachment)based Initial Attachment)

Non-3GPP GW3GPP access

Attach procedure – authentication, location update, L3 attach trigger, etc.

S-GW(BBERF)MME P-GW

(PCEF) V-PCRF H-PCRFeNBUE HSS

..L3 Attach Trigger

.Create Default Bearer Request (3GPP) or non-3GPP specific L3 Attach Trigger


Proxy Binding UpdateIP address is allocated during the process using DHCPv4, etc.

IP-CAN Session Establishment

Proxy Binding Ack

PMIP Tunnel

Gateway Control and QoS Rules Provision

Attach procedure –create default bearer response L3 attach complete etc

...L3 Attach Complete Create Default Bearer Complete(3GPP) or non-3GPP specific L3 Attach Complete

y

37

Attach procedure create default bearer response, L3 attach complete, etc.


Source : 3GPP TS 23.401/23.402

3GPP SAE 3GPP SAE QoSQoS--aware Mobility aware Mobility (DSMIPv6(DSMIPv6--based Initial Attachment)based Initial Attachment)(DSMIPv6(DSMIPv6--based Initial Attachment)based Initial Attachment)

P-GW(PCEF) V-PCRF H-PCRFUE HSSNon-3GPP

GW ( )

Access Authentication

L3 Attach and Local IP

Authentication and Authorization

Address Allocation


IPSec Tunnel

For an untrusted non-3GPP access network, IPSec tunnel is created between UE and ePDG

Binding Update

Authentication and AuthorizationDSMIPv6 Security Association Setup

Binding AcknowledgementIP-CAN Session Establishment

DSMIPv6 TunnelIPSec Tunnel

The information of mobility protocol tunnelling encapsulation header is delivered to the non 3GPP access Gateway

Gateway Control and QoS Rules Provision

38

y


Source : 3GPP TS 23.401/23.402

3GPP SAE 3GPP SAE QoSQoS--aware Mobility aware Mobility (PMIP(PMIP--based Handover based Handover w/ w/ SS--GW Relocation)GW Relocation)(PMIP(PMIP--based Handover based Handover w/ w/ SS--GW Relocation)GW Relocation)

Downlink and uplink data

SourceeNB

SourceS-GW

TargetS-GWMME P-GW V-PCRF H-PCRFTarget

eNBUE

PMIP Tunnel

Handover execution

Downlink and uplink data

Handover preparation

Forwarding of data

X2-based handover(Intra-LTE and Inter-eNodeB handover with Serving GW relocation)

Downlink dataUplink data

Path Switch RequestCreate Bearer Request

Handover completion

Layer 2 handover is done first

Handover event initiates gateway control session

CoA info is delivered through this control session

Create Bearer Response

(A)

Proxy Binding Update

Proxy Binding Ack

QoS rules are re-provisioned to target network


IP-CAN Session EstablishmentCreate Bearer Response

Path Switch Request Ack

Downlink data

Uplink data

If not S-GW relocation, Gateway Control and QoS Rules Request Procedure will be processed instead

PMIP Tunnel

Release Resource Delete Bearer Request

Delete Bearer Response

Gateway Control Session Termination

39

Tracking Area Update procedure

KRNET 2009KRNET 2009Source : 3GPP TS 23.401/23.402

Mobile Mobile WiMAXWiMAX QoSQoS--aware Mobilityaware Mobility

HA(C-PCEF)

ASN-GW(A-PCEF/SFA) PDF V-PCRF H-PCRFBS

(SFM)UE AAA/SPR( )(C-PCEF)( )(A-PCEF/SFA)( )(SFM)

802.16e Link Setup

Authentication and Authorization

AAA-server-provided pre-provisioned QoS

Bearer Establishment

IP Address Allocation

IP-CAN Session EstablishmentRequest

Subscriber Info.

Binding Update

Authentication and AuthorizationMIP Security Association Setup

Binding AcknowledgementIP-CAN Session Establishment


SummarySummaryIETF-based mobility protocols have become a commodity in IP-based Networks (NGN, 3GPP SAE, WiMAX, etc.)

Proxy Mobile IPv6, Dual-stack Mobile IPv6, etc.

Dynamic policy-based resource and QoS control per service flowPush and Pull modePush and Pull mode

Both of session level and aggregate-level QoS in transport level are assumed

Mobility control procedure should be closely related to dynamic policy and QoS control procedure

Since IETF-based mobility protocols are based on the tunneling mechanism when a mobile UE moves changed IP address information mechanism, when a mobile UE moves, changed IP address information should be notified to policy and QoS control function

Most of network architectures are considering this while especially 3GPP R l 8 i d ibi h d i d ilRel. 8 is describing the procedures in more detail

Further studies in WiMAX and NGN architecture seem to be required for a little bit more detailed procedures


DiscussionDiscussion

As the use of bandwidth in mobile broadband networks is increasing, the network nodes that can process sessions at wire-g, pspeed while guaranteeing QoS per session will also become necessary

Fl b d t l tf i f tl t h d t th i tFlow-based router platform is perfectly matched to the requirementETRI has developed flow-based router series (refer to backup slides)We are trying to integrate mobility solutions with flow-based router platform

ETRI also developed some mobility solutionsAs an example, xGMIP is introduced in backup slides


Q & AQ


ReferencesReferences[ 1] 3GPP TS 23.228, “IP Multimedia System (IMS).”[ 2] 3GPP TS 23.203, “Policy and Charging Control Architecture.”[ 3] 3GPP TS 23.207, “End-to-end Quality of Service (QoS) concept and architecture.”[ 4] 3GPP TS 29.212, “Policy and Charging Control over Gx reference point.”[ 5] 3GPP TS 29.213, “Policy and Charging Control signalling flows and QoS parameter mapping.”[ 6] 3GPP TS 29 214 “P li d Ch i C t l R f i t ”[ 6] 3GPP TS 29.214, “Policy and Charging Control over Rx reference point.”[ 7] ETSI TISPAN ES 282 003 V2.0.0, “Resource and Admission Control Sub-system (RACS):

Functional Architecture,” May 2008.[ 8] ITU-T Recommendation Y 2111 “Resource and admission control functions in next generation[ 8] ITU-T Recommendation Y.2111, Resource and admission control functions in next generation

networks,” Sept. 2006.[ 9] Richard Good and Neco Ventura, “Linking session based services and transport layer

resources in the IP multimedia subsystem,” [10] J. Song, et. al., “Overview of ITU-T NGN QoS Control,” IEEE Communication Magazine, pp.

116-123, Sept. 2007[11] G. Camarillo, et. al., “Towards an Innovation Orientated IP Multimedia Subsystem”, IEEE

C i ti M i 130 135 M h 2007Communications Magazine, pp. 130-135, March 2007[12] L. Skorin Kapov, et. al., “Application-Level QoS Negotiation and Signaling for Advanced

Services in the IMS”, IEEE Communications Magazine, pp. 108-116, March 2007


References (Cont’d)References (Cont’d)[13] Cathal McDaid, “Overview and Comparison of QoS Control in Next Generation Networks,”

http://www.palowireless.com/3g/qos.asp[14] Hannes Ekström “QoS Control in the 3GPP Evolved Packet System” IEEE Communications[14] Hannes Ekström, “QoS Control in the 3GPP Evolved Packet System”, IEEE Communications

Journal – Feb 2009.[15] José-Javier Pastor Balbás and Stefan Rommer and John Stenfelt, “Policy and Charging

Control in the Evolved Packet System”, IEEE communication Journal – Feb 2009.y ,[16] Irfan Ali, et. al., “Network-Based Mobility Management in the Evolved 3GPP Core Network

“ IEEE Communication Journal - Feb 2009.[17] Martin Niekus, “ETSI TISPAN NGN status: Potential policy and regulatory issues,” EU

workshop on NGN, 22 June 2005[18] LTE: Towards Mobile Broadband, http://www.atis.org/LTE/, Jan. 26-27, 2009[19] http://www.wimax.com/commentary/spotlight/evolution-of-qos-and-charging-framework-in-

wimaxwimax


AcronymsAcronymsA-RACF : Access Resource Admission Control FunctionBGF : Border Gateway Function

li f i l iCGPE-FE : CPN Gateway Policy Enforcement Functional EntityCMIP : Client Mobile IPCMTS : Cable Modem Termination SystemCPN C t P i N t kCPN : Customer Premises NetworkDP : Data PathDSA : Dynamic Service AdditionDSMIPv6 : Dual Stack Mobile IPv6DSMIPv6 : Dual Stack Mobile IPv6MMCF : Mobility Management and Control FunctionMME : Mobility Management EntityNACF : Network Attahcment FunctionNACF : Network Attahcment FunctionPAM : PacketCable Application ManagerPCEF : Policy and Charging Enforcement FunctionPCRF : Policy and Charging Rules FunctionPCRF : Policy and Charging Rules FunctionPDF : Policy Distribution FunctionPD-FE : Policy Decision Functional EntityPE-FE : Policy Enforcement Functional Entity

46

PE FE : Policy Enforcement Functional EntityPMIPv6 : Proxy Mobile IPv6


Acronyms (Cont’d)Acronyms (Cont’d)PS : Policy ServerRACF : Resource and Admission Control Function

d d i i l bRACS : Resource and Admission Control SubsystemRR : Resource ReservationSFA : Service Flow AgentSFM S i Fl MSFM : Service Flow ManagerSPDF : Service Policy Decision FunctionTRC-FE : Transport Resource Control Functional EntityTRE FE : Transport Resource Enforcement Functional EntityTRE-FE : Transport Resource Enforcement Functional Entity


Backup Slides Backup Slides ––ppRelated Projects in ETRIRelated Projects in ETRI


ETRI’s FlowETRI’s Flow--based Routerbased Router3 Modular Platforms

Scale from 20Gbps-720Gbps

Common Processor Modules and SW

Carrier-grade, Highly-Availability

Flow-aware Service Control S80

S20

Flow-aware Service ControlASIC(NP)-driven, Line-rate Services for Millions of Sessions

Subscriber Management with Hierarchical QoS S240

S80

Premium IPTV, Video, VOIP Service Management

Line-rate Deep Packet Inspection, Dynamic Flow Identification

Seamless Network FitStandard OSS, Policy and Application Server interfaces

Range of interfaces: GigE, 10 GigE / OC-12 to OC-192

Optional Carrier grade Routing including V6 Multicast MPLSOptional Carrier-grade Routing including V6, Multicast, MPLS


Dynamic Policy Control on FlowDynamic Policy Control on Flow--based Routerbased RouterExplicit control of flows

Signalling based explicit flow control by interfacing with SIP, IPTV Middleware, Security, etc.

Simple XML interface

Implicit control of flowsp c t co t o o o sLocal policies are pre-provisioned

Flows are dynamically identified through DFI (Dynamic Flow Identification) and DPI (Deep Packet Inspection) which makes the mechanism be called implicit control(Deep Packet Inspection), which makes the mechanism be called implicit control

OperationsCreate or block flows

Set QoS parameters for flow including MR (Maximum Rate), AR (Available Rate), GR (Guaranteed Rate), CR (Composite Rate)

Precise control of shaping, burst tolerance and policing for any flow


Dynamic Policy Control Deployment ScenarioDynamic Policy Control Deployment ScenarioExternal Interface to Session Server and Policy InfrastructureExplicit control of individual multimedia or premium business sessionsScales to millions of sessions per card!

SessionServer

dProvision Session :Bandwidth, QoS andInline Services

Session SetupSession Setup

Access Core Video

Flow-based Router

Network NetworkVideoStore


ETRI’s HostETRI’s Host--based Mobility Solution based Mobility Solution –– xGMIPxGMIP

Reliable, Managed Tunnel- Tunnel Management : MCP (Mobility Control Platform)u e a age e C ( o y Co o a o )

7. Secured Peer-to-Peer Data Communication

6.1 Learning Peer’s Location Information6 2 Create Peer to Peer Direct Tunnel

5. Secured Key Exchange

6.2 Create Peer-to-Peer Direct Tunnel

1. Subscription

IPv4 Network

4. Location Registration

xGMIP Client xGMIP Client

IPv6 over IPv4

IPv6 over IPv4 Tunnel

IPSec Control Tunnel

Subscriber DB

xGMIP Portal Security Manager

IPv6 over IPv4 Tunnel Manager3. Tunnel Creation

2. Secured Key Exchange

52

IPSec Data TunnelMCP


ETRI’s HostETRI’s Host--based Mobility Solution based Mobility Solution –– xGMIPxGMIP(Cont’d)(Cont’d)(Cont d)(Cont d)

Seamless Host-based IP MobilityL3 MBB (Make-before-Break) based on multiple interfaces

MCP CN

Terminal-Initiated handover

CellularWiFi WiMAX

ActiveActivestandby (Make)standby (Make) Active

standby (Make)

CellularWiFi

53

MOVE


Documents

QoS-aware Mobility Management for Convergence