IMS Solution for FMC

2008. 6. 24

youngki.jeon@samsung.com

Contents
FMC (Fixed & Mobile Convergence) & IMS
Service Continuity
IMS QoS
IMS Charging
GRUU (Globally Routable User Agent URIs)
IMS Vision for FMC

2/45

KRnet2008

FMC (Fixed & Mobile Convergence) & IMS

3/45

KRnet2008

Convergence Vision
Convergence : Communication, Broadcasting, Service, Web etc.

Multimedia
Services

Network
Network
Convergence
Convergence
Service
Service
Convergence
Convergence
Seamless services
for the same user
over different access
networks and
different devices

4/45

Unified core
network, multiple
access networks

Device
Device
Convergence
Convergence
Multi-Band/MultiMode/Multi-Media
Device

KRnet2008

Requirements for Convergence

Customer Needs

Network
Requirements

Converged Service
Service Continuity

Service:
- Personalization
- Instant
- Multimedia

Network Capabilities:
- Unified Core Network
- Single sign on/Single Bill
- Secure, QoS
- Service Continuity
- Customer awareness

- One-phone, WiFi, WiMAX/Cellular, UMA

Multimedia Communication
- PTT, Video Conferencing, VoIP/Video
Telephony, SMS/MMS, Sharing (Image, Video)
CONNECTION
Push to Talk (E)
Push to Talk (N)
Push to Video
Push to Play
Push to Locate
Push to E-Mail
Push to IM

Infra:
- Mobile Device
- Always Best Connect
- High speed data

BACK

Access Capabilities:
- High speed mobility
- All-IP
- Broadband
- Always On

OK

Telephony + Broadcasting
-IPTV + Telephony / QPS / Mobile TPS

Broadband (Wireline, Wireless)

- FTTH / WiFi, M-WiMax

5/45

KRnet2008

FMC Network Architecture

Application Server

WiFi
RGW AP

Cable

PS (Policy
Server)
CMTS

Enabler
(PS/IM/DMS)

PTA

TAS

VCC

Other AS

IMS Core

Signaling (SIP)
Signaling
(Diameter)
Signaling
(MEGACO)
Signaling (ISUP)
IP Bearer
TDM Bearer

CG

HSS

WiFi

SCIM

Broadband A-RACF
(xDSL)
xDSL) BRAS
SBC-SP
(IMS-ALG)

WiFi
GGSN/
PDSN/
ACR
WCDMA/CDMA/WiBro
WiBro
WCDMA/CDMA/

IBCF

CSCF

MGCF

AGCF

Other IP Network

WiFi AP
RGW

MRFC

SPDF

Narrowband

POTS
Phone

6/45

AGW

SPDF

PCRF

Resource and Admission Control Subsystem

C-BGF

IMS-AG

MRFP

MGW

I-BGF

PSTN

IP Transport
KRnet2008

Features of IMS (1/2)

Session Control
Perform session registration and session setup through register, reg
event package, invite message
Control Application Server by using ISC interface at S-CSCF

QoS control
Provide QoS along with Services
Network based VoIP
Rich Multimedia Services is provided, based Packet Switch, under the
guarantee of QoS
Real-time and non real-time, communication services
Between peers, or in a client-server configuration

Charging
Provide variable charging mechanism (Online/Offline charging, Flow
Based Charging, etc.)

7/45

KRnet2008

Features of IMS (2/2)

Mobility Management
Support Mobility / Nomadicity
Service mobility independent of User and Terminal Location

Security
Authentication/Authorization for providing services
Protection of unauthorized peer-to-peer traffic or rogue RTP

Inter-working with other networks (Legacy)

Independent Configuration with variable Access Network
CDMA, WCDMA, Wibro, WLAN, etc.
Interworking between same operator network and different operator network for
providing services

8/45

KRnet2008

Standardization
IMS standard has been adopted by mobile communication industry first
Broadband and Cable industries are in the process of adoption
- Wireless communication Standard body : 3GPP, 3GPP2
- Wireline communication Standard body : ETSI / TISPAN / ITU-T
- Cable Standard body : CableLabs

Interoperability between IMS and Non-IMS Network : MSF

- Enlarging Focus Area : FMC, Guaranteed NGN Service & Architecture

3GPP R5
(HSDPA)
IMS basic
architecture

3GPP R7
(HSPA+)
Interworking with
other networks

3GPP R6
(HSPA)
Service
standard

3GPP R8
Fixed-Mobile
Convergence

Adoption of IMS standard

3GPP2

ETSI/TISPAN
CableLabs

3GPP (3rd Generation Partnership Project) ETSI (European Telecommunications Standards Institute) MSF (Multi Service Forum)
TISPAN (Telecoms & Internet converged Services & Protocols for Advanced Networks)
HSDPA (High Speed Downlink Packet Access)

9/45

KRnet2008

Service Continuity

10/45

KRnet2008

Service Continuity Concept

Provides seamless service between Heterogeneous
Networks
Voice Call Continuity
Provides handover between CS domain and IMS domain
Provides Domain Selection for terminating VCC user

Single Radio Voice Call Continuity

Provides handover mechanism from LTE (Long Term Evolution) domain to
3GPP/3GPP2 CS domain using Single Radio

IMS Centralized Service

Provides IMS services to users by utilizing CS bearer independently of
access network

Multimedia Session Continuity

Provides domain transfer/selection of multimedia sessions

11/45

KRnet2008

Voice Call Continuity (1/2)

Provides capabilities to transfer voice calls between the CS do
main and the IMS
Application Servers

VCC AS

IMS Core

Voice, Video
telephony & SMS

Multimedia Service
(VoIP/MMoIP)

IMS to CS Domain Transfer

IMS Domain
WiFi

WCDMA / CDMA
(CS Core)

WiBro

WiFi

CS-Domain
WCDMA/CDMA

Provides VoIP service in

WiFi/WiBro at low price
Increases user convenience by
providing telephony service
continuity beyond IMS
coverage

CS to IMS Domain Transfer

Multi-mode/One Phone/One Number

12/45

KRnet2008

Voice Call Continuity (2/2)

VCC in the Market and SDOs
Needs

Standardization

Need of IMS based WiMax/WiFi service

control
Need of single Number based CS-IMS call
control
Need of voice call origination/termination
control outside of WiMAX/WiFi (IMS) coverage

3GPP VCC Standardization

Stage 1: TR 23.806, TS22.101, TS22.228

Capabilities and Benefits

Provide voice service outbound of
WiMAX/WiFi coverage through mobile
communication system
Seamless voice handover between
WiMAX/WiFi - CS Domains
Reduce CAPEX/OPEX
Support international roaming with mobile
network

13/45

Stage 2: TS23.228, TS23.206

Stage 3: TS24.228, TS24.206
3GPP2 VCC Standardization
X.P0042-001, Voice Call continuity
between IMS and Circuit Switched
Systems Stage 2
X.P0042-003-0_v0.2 SMS Interoperability
Stage-2 3
CableLabs (PacketCable)
PacketCable 2.0 Cellular Integration,
PKT-cellular-D01

KRnet2008

Single Radio VCC

Provides Voice Call Continuity between IMS over PS and CS
when the UE is capable of transmitting/receiving on only one of
those access networks at a given time
Scope
SRVCC from E-UTRAN access to 3GPP2 1xCS access
SRVCC from E-UTRAN access to 3GPP UTRAN/GERAN CS accesses
for voice calls that are anchored in the IMS

Standardization(Rel.8, 2008/04/30)
3GPP System Architecture Evolution Specification - Evolved Packet
System (non RAN aspects)
Single Radio Voice Call Continuity for 3GPP
50%, (2007/01/02 ~ 2008/09/15)

Single Radio Voice Call Continuity for CDMA2000 1X

80%, (2007/06/25 ~ 2008/06/13)

14/45

KRnet2008

Single Radio VCC for 3GPP2 (1/2)

1xCS
SRVCC
UE

A1

1xRTT CS
Access

1xRTT
MSC

IS41 (ISUP)

A1

VCC AS

1xCS IWS
S102

3GPP2
IMS

S11

MME
S1-MME
1xCS
SRVC
C UE

Serving/PDN
GW

E-UTRAN

SGi

S1-U
SIP signalling
Bearer before HO

Tunnelled 1xRTT messages

Bearer after HO

MME/E-UTRAN should support tunneling mechanism for sending CS

signal message to 3GPP2 CS domain
1xCS IWS (Interworking Solution Function) should be added
To be a signaling tunneling end point towards the MME for
receiving/sending encapsulated 3GPP2 1xCS signaling messages
to/from the UE
To emulate a 1xRTT BSS towards the 1xRTT MSC
15/45

KRnet2008

Single Radio VCC for 3GPP2 (2/2)

SRVCC Network Diagram from LTE to 3GPP2 CS

16/45

KRnet2008

Single Radio VCC for 3GPP (1/2)

VCC
AS

MSC server should be enhanced for SRVCC

Interworking LTE signaling message with CS signaling message

MME should support

Performing the PS bearer splitting function by separating the voice PS bearer
from the non-voice PS bearers
Initiating the SRVCC handover procedure for handover of the voice
component to the target cell

HSS should send SRVCC VDN and MSISDN to MME during E-UTRAN
attach procedure
* VDN: VCC Domain Transfer Number

17/45

KRnet2008

Single Radio VCC for 3GPP (2/2)

SRVCC network diagram from LTE to 3GPP CS

18/45

KRnet2008

IMS Centralized Service (1/4)

Provides communication services such that all services, and service
control, are based on IMS mechanisms and enablers. It enables IMS
services when using CS access for the media bearer

Consideration
SCC AS should be added
Interworking and control Service Control Signaling path with CS bearer
signaling
Provide Domain Selection, with ICS UE (when needed)
Support USSD transport

MSC server should support SIP interface with CSCF and control not only
CS-MGW, but also IMS-MGW

* SCC AS: Service Centralization and Continuity Application Server

* USSD: Unstructured Supplementary Service Data

19/45

KRnet2008

IMS Centralized Service (2/4)

Service Control Signaling Path established via IP-CAN
Service Control Signaling Path
CS Bearer Control Signaling Path
Media Bearer Path

te Leg
Remo

SIP AS

Leg
SCC AS
ess
c
c
A

CSCF
MSC Server/MGW

CS Bearer Control Signaling Path established via CS network

SCC AS correlates Service Control Signaling and CS Bearer
Control Signaling and presents session to IMS
Bidirectional Speech Media established via CS and IMS network

20/45

KRnet2008

IMS Centralized Service (3/4)

Service Control Signaling Path established via CS
network
Service Control Signaling Path
CS Bearer Control Signaling Path
Media Bearer Path
SCC AS
Ac
ce
ss

Le
g

ote
em

Leg

SIP AS

MSC Server/HSS

CSCF
MSC Server/MGW

CS Bearer Control Signaling Path established via CS network

SCC AS correlates Service Control Signaling and CS Bearer
Control Signaling and presents session to IMS
Bidirectional Speech Media established via CS and IMS network
21/45

KRnet2008

IMS Centralized Service (4/4)

Service consistency
IMS
Centralized Services

Core
Network

ICS enhanced
CS MSC

Access
Network

IMS
Centralized
Services
Provided to
User

Legacy (or ICS enhanced)

CS MSC

SAE

GSM +
GPRS,
EDGE

GSM +
GPRS,
EDGE

UMTS/
HSPA

WLAN

LTE

Wired
Access

Legacy UE

ICS UE

ICS UE

ICS UE

ICS UE

ICS UE

CS Voice

CS Voice

CS Voice

VoIP

QoS VoIP

QoS VoIP

CS Equiv
MMTEL SS

Partial
MMTEL SS

FULL
MMTEL SS

FULL
MMTEL SS

FULL
MMTEL SS

FULL
MMTEL SS

Data

Hi Speed
Data

Hi Speed
Data

Hi Speed
Data

Hi Speed
Data

Rich IP
Services

Rich IP
Services

Rich IP
Services

Rich IP
Services

IMS Video

IMS Video

IMS Video

IMS Video

Real Time
Services
( Gaming )

Real Time
Services
( Gaming )

IP Services

Common Device Client provides Consistent User View

Service Capabilities Grow with Access Capabilities

22/45

KRnet2008

Multimedia Session Continuity (1/4)

Supports the continuity of multimedia services refers to the capability
of continuing ongoing communication sessions with multiple media
across different access networks or across different UEs
MMSC
UE
V1

MMSC AS

ISC

S-CSCF

MMSC AS
Extend existing functional capabilities from the VCC Application
Anchor all multimedia sessions
Enable network initiated multimedia session transfer by updating and
providing session transfer policies stored in the UE
Provide multimedia session splitting/merging functionalities
23/45

KRnet2008

Multimedia Session Continuity (2/4)

PS PS Session Continuity
UE-1

Non-3GPP
(e.g. WiMAX)

Voice + data
P-CSCF-a1
UE-2

Intermediate
Voice + data
IMS
elements

MGCF
E-UTRAN
P-CSCF-a2
Voice + data

PS-PS session continuity in conjunction with PS-CS continuity

Voice + data

UE -1

WLAN

UTRAN
/
GERAN

P-CSCF-a1

UE-2

Voice

ICS interworking
nodes

P-CSCF-a2

Intermediate
IMS
elements

Voice + data

Data

To support Service Continuity between CS and PS of bidirectional speech media in IMS sessions, ICS AS shall
be used for the CS leg

24/45

KRnet2008

Multimedia Session Continuity (3/4)

Mobility of media components of a session between different
terminals under the control of the same user
Transfer media components to different UEs
Retrieve media components from different UEs
Add new media components to different UEs
Remove media components from different UEs

UE-2

Other media
Voice
IP Network

IP-CAN2
UE-1

IP-CAN1
UE-2

CS Access

UE-1

UE-1

25/45

KRnet2008

Multimedia Session Continuity (4/4)

Mobility of media components of a session between different
terminals under the control of the same user using keep
control mode and release control mode
Transfer media components to different UEs with the selection of
keep control mode
Transfer media components to different UEs with the selection of
release control mode

keep control mode

26/45

release control mode

KRnet2008

IMS QoS

27/45

KRnet2008

IMS based QoS (1/2)

Why IMS based QoS?
Packet network can not guarantee proper Service QoS per each services.
Each service/subscriber has different requirements of bandwidth, delay, etc
Some mechanism are required that identify the QoS requirement of service
and enforce the QoS requirement.

Goal
Support service/service data flow level QoS differentiation
Guarantee a minimum QoS for a session
Prevent network resource from exclusively possessed by few sessions
Increase the resource utilization

Principles
End-to-end Service QoS negotiation
E2E Service QoS requirements are negotiated via SIP/SDP Signaling

Service Based Policy

Policy Server makes a QoS decision based on negotiated service QoS
requirements, operators policy rules and subscription profile
28/45

KRnet2008

IMS based QoS (2/2)

Policy based QoS control
Policy server indicates to the PCEF how to control the IP-CAN bearer

QoS differentiation
Subscriber
Service (e.g. multimedia chatting)
Service data flow (e.g. text chatting window, video or audio of multimedia
chatting)

Guarantee a minimum QoS for a session

Depend on a dynamic policy decision and resource status of IP edge
Policy decision is made based on session description parameters at the
service time

Prevent network resource from exclusively possessed by few sessions

Increase the resource utilization
29/45

KRnet2008

3GPP PCC Architecture (Rel.7)

Policy and Charging Control
Complete harmonization and merger of the policy control and flow based
charging architecture and procedures
Flow Based Charging, including charging control and online credit control
Policy Control (e.g. gating control, QoS control, etc)
PCC (FBC as basis)

Support Subscriber / service / service data flow based QoS and charging
differentiation
Support for end-user subscription differentiation
Support general policy control aspects to the policy/charging control

Main Feature
Policy Control (QoS, Gating)
Charging Control
Event trigger
Subscription profile Repository
30/45

KRnet2008

3GPP PCC Architecture (Rel.7)

AF
Diameter : Rx

Online Charging System (OCS)

CAMEL
SCP

Subscription
Subscription Profile
Profile
Repository
Repository
(SPR)
(SPR)

Service Data Flow

Based
Credit Control

Sp

Policy
Policy and
and
Charging
Charging Rules
Rules
Function
Function
(PCRF)
(PCRF)

Diameter : Gx

PCEF
PCEF
Diameter : Gy

GW
AF
: Application Function (e.g. P-CSCF of IMS)
SPR : Subscriber Profile Repository
PCC : Policy and Charging Control
PCRF : Policy & Charging Rules Function
PCEF : Policy & Charging Enforcement Function
OFCS : Offline Charging System
OCS : Online Charging System

31/45

Diameter : Gz
Offline
Charging
System
(OFCS)

KRnet2008

3GPP EPC QoS Architecture (Rel. 8)

AF

3GPP TS 23.401
- CN Architecture for 3GPP

H-PCRF
Rx+

S9

- Rx+, S9, S7 interface

V-PCRF
3GPP TS 23.402
- CN Architecture for non-3GPP

PCRF

- Rx+, S9, S7, S7a/b/c interface

S7b
S7a

S7

S7c

S-GW

A-GW

ePDG

P-GW
(PCEF)

3GPP TR 29.804 3GPP System Architecture Evolution

Architecture (non-roaming, roaming)
PCC roaming architecture for home-routed traffic
PCC roaming architecture for LBO with AF in the H-PLMN
PCC roaming architecture with AF in the V-PLMN
Definitions of Functional Entities
Diameter Routing Agent : select PCRF
EPC-specific QoS AVPs, etc.
32/45

* EPC: Evolved Packet Core

* LBO : Local Breakout

KRnet2008

WiMAX PCC Architecture (NWG Rel.1.5)

ASN

CSN

ASN1

PCC-R3-P

Anchor SFA/A-PCEF
Accounting Client

ASP

Policy
Gx (Ty)
Distribution
Function

PCRF

Rx(Tx)

Sp
PCC-R3- OFC

AF
(P-CSCF
or non-IMS
application server)

SPR/
AAA

Re-Used
-PCRF, SPR
-Rx, Gx interface

Gz

OFCS

R4
PCC-R3-OC

Charging
Distribution
Function

Gy

New
-PDF
-PCC-R3-P/OC/OFC
interface

OCS/

(PCC-based)
Gy/Gz

ASN2
Serving SFA

(MIP)

Accounting Agent

HA

Accounting
Client

C-PCEF

Home
IP Network

Non-roaming scenario

Phase1 (Feb. 2008) under V&V stage

Architecture (non-roaming, roaming), Definitions of Functional Entities, Stage2
call flows, WiMAX QoS AVPs, etc.

Phase2 (June. 2008) - plan

Bearer binding, Stage3 call flows, offline/online charging details, C-PCEF details,
etc.
* PCC: Policy and Charging Control

33/45

KRnet2008

PacketCable 2.0 QoS Architecture

AF #1

pkt-qos-1

AF
P-CSCF

SOAP

pkt-mm-3
PacketCable
Application
Manager (PAM)

COPS

Signal
translation

CM

Policy
Server

DOCSIS

PDP
pkt-qos-2

pkt-mm-2
COPS

Gm: signal

UE

PacketCable 2.0
Define Architecture and Functional
Entities, etc.

AF #n

CMTS

PEP

PAM
Determine the QoS resources needed
for a session using SDP
Manage the QoS resources allocated
for a session

pkt-qos-1 interface
XML / SOAP

PacketCable 2.0
AF

Rx

PCRF
AM
PS
Pkt-mm-2 (COPS)

UE

CM

DOCSIS IP-CAN

PCE

CMTS

3GPP Harmonization
PCRF
Merging the AM (Application Manager)
and PS (Policy Server)

pkt-qos-1 interface
Rx (Diameter)

3GPP Harmonization
34/45

KRnet2008

IMS Charging

35/45

KRnet2008

IMS Charging
Why IMS based Charging?
User requests guaranteed QoS as enough as he pay.
Operator wants to charge a fee as enough as users usage.
Different services require different charging rules.
User/Operator wants to get one bill for telecommunication service that
includes transport, core and service level fees.

IMS based Charging

IMS supports both online and offline charging.
IMS NEs (e.g. CSCF, MGCF, AS, MRF, IP edge) generate the charging event
information.

CDF (Charging Data Function) and OCS (Online Charging Server) generate
the CDRs (Charging Data Records) for offline and online charging.

CDF/OCS or Billing Domain correlate the CDRs received from multiple IMS
NEs based on icid (IMS Charging ID).
36/45

KRnet2008

IMS Charging Architecture (Offline)

IMS Charging Correlation
Based on unique ICID (IMS Charging Identifier), Charging correlation will
be performed for session, bearer and service/event charging

Billing Domain

Service & Event

Charging

AS
AS

Correlated
CDRs
(Charging Date
Records)

IMS based
Integrated Offline
Charging Server
(CDF/CGF)
Charging
event
Information

MGCF
MGCF

Session Charging

CSCF/BGCF
CSCF/BGCF

Session & Event

Charging

Session Information

PCRF
PCRF
Charging rules (Offline)

MRF
MRF
37/45

IP
IPEdge
Edge

Bearer
Charging
KRnet2008

IMS Charging Architecture (Online)

IMS Charging Correlation
Based on unique ICID (IMS Charging Identifier), Charging correlation will
be performed for session, bearer and service/event charging

Billing Domain
AS
AS

Correlated
CDRs

IMS based
Integrated Online
Charging Server
(OCS)

S-CSCF
S-CSCF
IMS-GWF
IMS-GWF

Charging
event
Information

Service & Event

Charging
Session & Event
Charging

P-CSCF
P-CSCF
Session Information

PCRF
PCRF
Charging rules (Online)

MRF
MRF
38/45

IP
IPEdge
Edge

Bearer
Charging
KRnet2008

Benefits of IMS Based Charging

Benefits of IMS based Charging
IMS charging provides not only session based charging but also event based
and service based charging.

IMS charging provides the unified charging data that associate the Service &
Event, Session and Bearer level charging information

IMS charging provides the easy charging architecture for integrated charging
for multi-session and multi-services.

IMS charging provides the different charging rules per each service on the
basis of policy control architecture with the help of PCRF.

CDR structures will not be changed with introduction of new services.

39/45

KRnet2008

GRUU (Globally Routable User Agent URIs)

40/45

KRnet2008

Globally Routable User Agent URIs

GRUU (Globally Routable User Agent URIs)
Identify a unique combination of Public User Identity and UE instance
Prevent SIP request from forking to another registered UE of the same Public Us
er Identity

Necessity of GRUUs
User can get multiple UEs of the same public User IDs
It is difficult to identify the proper UE among these UEs during Call Transfer, CS
to IMS handover

Two Types of GRUUs

Public GRUUs
pub-gruu="sip:callee@example.com;gr=urn:uuid:f81d4fae-7dec-11d0-a76500a0c91e6bf6"
reveal the Public User Identity of the user and are very long lived

Temporary GRUUs
temp-gruu="sip:tgruu.7hs==jd7vnzga5w7fajsc7-ajd6fabz0f8g5@example.com;gr"
contain a URI that do not reveal the Public User Identity of the user
valid until the contact is explicitly de-registered or the current registration expires
41/45

KRnet2008

IMS Subscription & ID

Public
User Identity
IMS
Subscription

Private
User Identity

Public
User Identity

Public User Identity : Service Profile = 1:1 or N :1

Public
User Identity
Implicitly
Registered ID Set

Private
User Identity

Public
User Identity 1
Public
User Identity 2
Public
User Identity 3

IMS
Subscription

Registered ID Set 1

Service
Profile 2

Implicitly
Registered ID Set 2

Service
Profile 3

Public
User Identity 4
Private
User Identity

Public
User Identity 5
Public
User Identity 6

42/45

Implicitly

Service
Profile 1

Implicitly
Registered ID Set 3

Service
Profile 4
KRnet2008

Relationship of PUIs, GRUUs and UEs

Relationship of PUIs, GRUUs and UEs

Public User
Identity

GRUU Set 1

UE
1

Instance ID1

GRUU Set 2
Public User
Identity
GRUU Set 3

UE
1

Public User
Identity

43/45

Instance ID2

GRUU Set 4

KRnet2008

IMS Vision for FMC

44/45

KRnet2008

IMS Vision for FMC

Anytime, anywhere access
to converged services with anydevice

Converged
Services

Network
Network
Convergence
Convergence
Service
Service
Continuity
Continuity
Seamless services
for the same user
over different access
networks and
different devices

QoS/Charging/Single Sign On

VCC/SRVCC, ICS, MMSC

45/45

Device
Device
Convergence
Convergence

Unified core
network, multiple
access networks

Multi-Band/MultiMode/Multi-Media
Device

Private ID/Public ID, GRUU

KRnet2008