IMS Solution for FMC - KRnet LTE signaling message with CS signaling message MME should support...

IMS Solution for FMC

2008. 6. 24

삼성전자 전영기수석

[email protected]

KRnet20082/45

Contents

▣ FMC (Fixed & Mobile Convergence) & IMS

▣ Service Continuity

▣ IMS QoS

▣ IMS Charging

▣ GRUU (Globally Routable User Agent URIs)

▣ IMS Vision for FMC

KRnet20083/45

FMC (Fixed & Mobile Convergence) & IMS

KRnet20084/45

Convergence VisionConvergence Vision

NetworkConvergence

NetworkNetworkConvergenceConvergence

Unified core network, multiple access networks


Device Convergence

Device Device ConvergenceConvergence

Multi-Band/Multi-Mode/Multi-Media

Device


Device

Service Convergence

Service Service ConvergenceConvergenceSeamless services for the same user

over different access networks and

different devices

Seamless services for the same user


different devices

Multimedia Services

Multimedia Services

Convergence : Communication, Broadcasting, Service, Web etc.

KRnet20085/45

Broadband (Wireline, Wireless)- FTTH / WiFi, M-WiMax

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

Multimedia Communication- PTT, Video Conferencing, VoIP/Video Telephony, SMS/MMS, Sharing (Image, Video)

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

5

CONNECTION

BACK OK

Push to Talk (E)

Push to Talk (N)Push to VideoPush to PlayPush to LocatePush to E-MailPush to IM

Converged ServiceCustomer Needs

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

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

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

NetworkRequirements

Service:- Personalization- Instant- Multimedia

Requirements for Convergence

KRnet20086/45

FMC Network Architecture

PSTN

NarrowbandNarrowband

Application Server

Enabler(PS/IM/DMS) PTA

AGW

TAS

Resource and Admission Control Subsystem

IP Transport

MGW I-BGFMRFP

IMS Core

CSCF

HSS

MGCF

MRFC

SBC-SP(IMS-ALG)

AGCF

Other IP

Netw

ork

SCIM

IBCF

SPDF

VCC

CG

POTSPhone

Broadband Broadband ((xDSLxDSL))

WiFiWiFi

RGWWiFi AP

BRASA-RACF

SPDF PCRF

C-BGF IMS-AG

Cable

WiFiWiFi

RGWWiFiAP CMTS

PS (Policy Server)

Other AS

WCDMA/CDMA/WCDMA/CDMA/WiBroWiBro

GGSN/PDSN/ACR

Signaling (SIP)

IP Bearer

Signaling (Diameter)Signaling (MEGACO)Signaling (ISUP)

TDM Bearer

KRnet20087/45

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 QoSReal-time and non real-time, communication servicesBetween peers, or in a client-server configuration

▣Charging◈ Provide variable charging mechanism (Online/Offline charging, Flow

Based Charging, etc.)

KRnet20088/45

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

KRnet20089/45

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

3GPP R5(HSDPA)IMS basic

architecture

3GPP R6(HSPA)Service

standard

3GPP R8

Fixed-Mobile Convergence

3GPP R7(HSPA+)

Interworking withother networks

Adoption of IMS standard

※ 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)

3GPP23GPP2 ETSI/TISPANCableLabs

ETSI/TISPANCableLabs

Interoperability between IMS and Non-IMS Network : MSF- Enlarging Focus Area : FMC, Guaranteed NGN Service & Architecture

Standardization

KRnet200810/45

Service Continuity

KRnet200811/45

Service Continuity Concept

▣Provides seamless service between Heterogeneous Networks◈ Voice Call Continuity

Provides handover between CS domain and IMS domainProvides Domain Selection for terminating VCC user

◈ Single Radio Voice Call ContinuityProvides handover mechanism from LTE (Long Term Evolution) domain to 3GPP/3GPP2 CS domain using Single Radio

◈ IMS Centralized ServiceProvides IMS services to users by utilizing CS bearer independently of access network

◈ Multimedia Service ContinuityProvides domain transfer/selection of multimedia services

KRnet200812/45

Voice Call Continuity (1/2)

▣ Provides capabilities to transfer voice calls between the CS domain and the IMS

Provides VoIP service inWiFi/WiBro at low price

Increases user convenience by providing telephony service continuity beyond IMS coverageWiFiWiFi

CS-DomainWCDMA/CDMA

IMS Core

Application Servers

WCDMA / CDMA (CS Core)

VCC ASVCC AS

Multi-mode/One Phone/One Number

Multimedia Service

(VoIP/MMoIP)

Voice, Video telephony & SMS

IMS to CS Domain Transfer

CS to IMS Domain Transfer

WiBroIMS Domain

KRnet200813/45

Voice Call Continuity (2/2)

▣ VCC in the Market and SDOs

▣Provide voice service outbound ofWiMAX/WiFi coverage through mobile communication system▣Seamless voice handover between

WiMAX/WiFi - CS Domains▣Reduce CAPEX/OPEX▣Support international roaming with mobile

network

Capabilities and Benefits

▣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

Needs

▣3GPP VCC Standardization◈Stage 1: TR 23.806, TS22.101, TS22.228 ◈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

Standardization

KRnet200814/45

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/06/25 ~ 2007/06/25)

Voice Call Continuity for CDMA2000 1X 80%, (2007/06/25 ~ 2007/06/13)

SAE impacts on IMS (e.g. Local Break Out aspects) 40%, (2007/01/02 ~ 2008/09/15)

KRnet200815/45

Single Radio VCC for 3GPP2 (1/2)

E-UTRAN

MME

Serving/PDN GW

SGi

1xRTT CS Access

1xRTTMSC

1xCS IWS

S102 S11

S1-MME

S1-U

A1

1xCS SRVCC UE

Bearer before HO

Bearer after HO

SIP signalling

IS41 (ISUP)

A1 VCC AS

3GPP2IMS

Tunnelled 1xRTT messages

1xCS SRVCC

UE

▣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

KRnet200816/45

Single Radio VCC for 3GPP2 (2/2)

▣ SRVCC Network Diagram from LTE to 3GPP2 CS

E

E-UTRAN MME1xCSIWS

1xRTT MSC

Originating Side Target Side

1xCS signalling messages tunnelled inside S102 protocol

Registration and Authorization if needed

CS Call setup procedures

Towards VLR/HLR

Call terminated at VCC AS

VCC AS STARTS VCC Domain Transfer

PROCEDURES

EUTRAN/EPS tunnelling

1xCS signalling messages tunnelledacross EUTRAN / EPS

A1 messages

S102 tunnelling

1xCSSRVCC

UE

KRnet200817/45

Single Radio VCC for 3GPP (1/2)

▣ 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

UE E-UTRAN

MME

MSC ServerTarget UTRAN/GERAN

Serving/PDNGW

3GPPIMS

UEUm/Uu Iu-cs/A

S3

S3-cs

S11S1-MME

S1-ULTE-Uu SGi

SGs

HSSS6a

SGSN

Iu-ps/GbVCC AS

KRnet200818/45

Single Radio VCC for 3GPP (2/2)

▣ SRVCC network diagram from LTE to 3GPP2 CS

UE E-UTRAN MME MSC Server Target UTRAN/GERAN

MeasurementReports

Handover to UTRAN/GERAN required

3GPP IMS

Initiates SRVCC for voice component

CS handover preparation IMS Service Continuity Procedure

Handles PS-PS HO for non-voice if needed

CS HO response to MMETo eUTRAN

Coordinates SRVCC and PS HO response Handover CMD

Handoverexecution

KRnet200819/45

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

UE

I1

ISC

I2

I3MSC Server IMS-MGW

SCC AS

CSCFGm

A/IuGERAN/UTRANAccess

▣ Consideration◈ SCC AS should be added

Interworking and control Service Control Signaling path with CS bearer signalingProvide 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

KRnet200820/45


▣Service Control Signaling Path established via IP-CAN

CSCF

SCC AS

SIP AS

Access Leg

Remote Leg

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

KRnet200821/45


▣Service Control Signaling Path established via CS network

CSCF

SCC AS

SIP AS

Access Leg Remote Leg

MSC Server/HSS

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

KRnet200822/45


▣Service consistency

CS Voice

CS Equiv MMTEL SS

ICS enhanced CS MSC

Legacy UE ICS UE ICS UEICS UE

Legacy (or ICS enhanced) CS MSC

ICS UE

IMS Centralized Services

IMS Centralized

Services Provided to

User

Access Network

Core Network

Common Device Client provides Consistent User ViewService Capabilities Grow with Access Capabilities

SAE

ICS UE

WLAN LTE WiredAccess

UMTS/HSPA

GSM +GPRS, EDGE

GSM +GPRS, EDGE

CS Voice

Partial MMTEL SS

Data

IP Services

CS Voice

FULL MMTEL SS

Hi Speed Data

Rich IP Services

IMS Video

QoS VoIP

FULL MMTEL SS

Hi Speed Data

Rich IP Services

IMS Video

Real Time Services

( Gaming )

QoS VoIP

FULL MMTEL SS

Hi Speed Data

Rich IP Services

IMS Video

Real Time Services

( Gaming )

VoIP

FULL MMTEL SS

Hi Speed Data

Rich IP Services

IMS Video

KRnet200823/45

Multimedia Service Continuity (1/4)

▣ Supports the continuity of multimedia services refers to the capability of continuing ongoing communication sessions with multiple mediaacross different access networks or across different UEs

MMSC

UE

MMSC AS

S-CSCF

V1

ISC

◈ MMSC ASExtend existing functional capabilities from the VCC ApplicationAnchor all multimedia sessionsEnable network initiated multimedia session transfer by updating and providing session transfer policies stored in the UEProvide multimedia session splitting/merging functionalities

KRnet200824/45


▣ PS – PS Session Continuity

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

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

Non-3GPP(e.g. WiMAX)

E-UTRAN

IntermediateIMS

elementsMGCF

P-CSCF-a1

Voice + data

Voice + data

P-CSCF-a2

UE-1

UE-2

Voice + data

WLAN

UTRAN/

GERAN

IntermediateIMS

elements

P-CSCF-a1

Voice + data

Voice + data

DataP-CSCF-a2

Voice

UE-1

UE-2

ICS interworking nodes

KRnet200825/45


▣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

IP Network

Other media

Voice

UE-2

UE-1

UE-2IP-CAN1

IP-CAN2

CS Access

UE-1

UE-1

KRnet200826/45


▣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 “release control” mode

KRnet200827/45

IMS QoS

KRnet200828/45

IMS based QoS (1/2)

▣ Why IMS based QoS?◈ Pakcet 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 QoSrequirements, operator’s policy rules and subscription profile

KRnet200829/45

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

KRnet200830/45

3GPP PCC Architecture (Rel.7)

▣ Policy and Charging Control◈ Complete harmonization and merger of the policy control and flow based

charging architecture and proceduresFlow Based Charging, including charging control and online credit controlPolicy 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

KRnet200831/45

3GPP PCC Architecture (Rel.7)

GWDiameter : Gy

Diameter : Rx

AF

Diameter : Gz

Diameter : Gx

Subscription ProfileRepository

(SPR)

Subscription ProfileRepository

(SPR)

Sp

Offline Charging System (OFCS)

PCEFPCEF

AF : Application Function (e.g. P-CSCF of IMS)SPR : Subscriber Profile Repository PCC : Policy and Charging ControlPCRF : Policy & Charging Rules FunctionPCEF : Policy & Charging Enforcement FunctionOFCS : Offline Charging SystemOCS : Online Charging System

Online Charging System (OCS)

Service Data Flow Based

Credit Control

CAMELSCP

Policy and Charging Rules

Function(PCRF)

Policy and Charging Rules

Function(PCRF)

KRnet200832/45

3GPP EPC QoS Architecture (Rel. 8)

▣ 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. * EPC: Evolved Packet Core* LBO : Local Breakout

PCRF

Rx+

AF

S7a

A-GW ePDGS-GW

S7c

S7bS7

P-GW (PCEF)

▣3GPP TS 23.401- CN Architecture for 3GPP- Rx+, S9, S7 interface

▣3GPP TS 23.402- CN Architecture for non-3GPP- Rx+, S9, S7, S7a/b/c interface

H-PCRF

V-PCRF

S9

KRnet200833/45

WiMAX PCC Architecture (NWG Rel.1.5)

▣ 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.

HomeIP Network

Anchor SFA/A-PCEF

Accounting Client

ASN1

Serving SFA

Accounting Agent

ASN2

R4

PCRF

SPR/AAA

OCS/

OFCS

C-PCEFHA

PolicyDistribution

Function

PCC-R3-P AF(P-CSCF

or non-IMSapplication server)

ASN CSN ASP

(MIP)

Gx (Ty)

(PCC-based)

Rx(Tx)

ChargingDistribution

Function

Gy

Gy/Gz

Sp

PCC-R3-

AccountingClient

PCC-R3-OC

Gz

OFC

PC

C-R

3-OFC

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

• New-PDF-PCC-R3-P/OC/OFCinterface

* PCC: Policy and Charging Control

Non-roaming scenario

KRnet200834/45

PacketCable 2.0 QoS Architecture

▣ PacketCable 2.0◈ Define Architecture and Functional

Entities, etc.◈ PAM

Determine the QoS resources needed for a session using SDPManage the QoS resources allocated for a session

◈ pkt-qos-1 interfaceXML / SOAP

PacketCableApplication

Manager (PAM)

Policy Policy ServerServer

COPS

Signal translation

PEP

P-CSCF

CMCM DOCSISUE

AF

PDPSOAP

CMTSCMTS

Gm: signal

COPS

AF #1 AF #n

pkt-qos-1 pkt-mm-3

pkt-mm-2 pkt-qos-2

DOCSIS IP-CAN CMTS

PCE

PS

Pkt-mm-2 (COPS)

CM UE

AMPCRF

AF Rx

PacketCable 2.0

3GPP Harmonization

▣ 3GPP Harmonization◈ PCRF

Merging the AM (Application Manager) and PS (Policy Server)

◈ pkt-qos-1 interfaceRx (Diameter)

KRnet200835/45

IMS Charging

KRnet200836/45

IMS ChargingIMS Charging

▣Why IMS based Charging?◈User requests guaranteed QoS as enough as he pay.

◈Operator wants to charge a fee as enough as user’s 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 eventinformation.

◈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 IMSNEs based on icid (IMS Charging ID).

KRnet200837/45

IMS Charging Architecture (Offline)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

IP EdgeIP Edge

CSCF/BGCFCSCF/BGCFIMS based

Integrated OfflineCharging Server

(CDF/CGF)

MGCFMGCF

ASAS

MRFMRF

PCRFPCRF

Charging rules (Offline)

Session Information

Service & EventCharging

Session Charging

Bearer Charging

Session & EventCharging

Charging event

Information

CorrelatedCDRs

(Charging Date Records)

KRnet200838/45

IMS Charging Architecture (Online)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

IP EdgeIP Edge

S-CSCFS-CSCFIMS based

Integrated OnlineCharging Server

(OCS)

ASAS

MRFMRF

PCRFPCRF

Charging rules (Online)

Session Information

Service & EventCharging

Bearer Charging

Session & EventCharging

Charging event

Information

P-CSCFP-CSCFIMS-GWFIMS-GWF

CorrelatedCDRs

KRnet200839/45

Benefits of IMS Based ChargingBenefits 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.

KRnet200840/45

GRUU (Globally Routable User Agent URIs)

KRnet200841/45

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:[email protected];gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6"reveal the Public User Identity of the user and are very long lived

◈ Temporary GRUUstemp-gruu="sip:[email protected];gr"contain a URI that do not reveal the Public User Identity of the uservalid until the contact is explicitly de-registered or the current registration expires

KRnet200842/45

IMS Subscription & ID

IMSSubscription

PublicUser Identity 1


PrivateUser Identity




ServiceProfile 1

ServiceProfile 2

ServiceProfile 4

Implicitly

Registered ID Set 1

IMSSubscription

PublicUser Identity

PublicUser Identity

PublicUser Identity


ImplicitlyRegistered ID Set

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

PublicUser Identity 5 Implicitly

Registered ID Set 3

PublicUser Identity 3 Implicitly

Registered ID Set 2

ServiceProfile 3

KRnet200843/45

Relationship of PUIs, GRUUs and UEs

GRUU Set 1

UE 1

Public User Identity

Instance ID1

GRUU Set 2



GRUU Set 3

GRUU Set 4

1 Instance ID2

UE

▣ Relationship of PUIs, GRUUs and UEs

KRnet200844/45

IMS Vision for FMC

KRnet200845/45

IMS Vision for FMCIMS Vision for FMCAnytime, anywhere access Anytime, anywhere access

to converged services withto converged services with anydeviceanydevice

NetworkConvergence

NetworkNetworkConvergenceConvergence



Device Convergence

Device Device ConvergenceConvergence


Device


Device

Service Continuity

Service Service ContinuityContinuity



different devices



different devices

ConvergedServices

ConvergedServices

VCC/SRVCC, ICS, MMSC

QoS/Charging/Single Sign On

Private ID/Public ID, GRUU

IMS Solution for FMC - KRnet LTE signaling message with CS signaling message MME should support...

Documents

Transcript of IMS Solution for FMC - KRnet LTE signaling message with CS signaling message MME should support...