IMS Solution for FMC 삼성전자전영기수석

Transcription

1 IMS Solution for FMC 삼성전자전영기수석

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

3 3/45 FMC (Fixed & Mobile Convergence) & IMS

4 Convergence Vision 4/45 Convergence : Communication, Broadcasting, Service, Web etc. Multimedia Services Service Convergence Seamless services for the same user over different access networks and different devices Network Convergence Unified core network, multiple access networks Device Convergence Multi-Band/Multi- Mode/Multi-Media Device

5 Requirements for Convergence 5/45 Customer Needs Service: - Personalization -Instant - Multimedia Network Requirements Network Capabilities: - Unified Core Network - Single sign on/single Bill - Secure, QoS - Service Continuity - Customer awareness Converged Service Service Continuity - 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 Push to IM Infra: - Mobile Device - Always Best Connect - High speed data Access Capabilities: - High speed mobility - All-IP - Broadband - Always On Telephony + Broadcasting -IPTV + Telephony / QPS / Mobile TPS 5 Broadband (Wireline, Wireless) - FTTH / WiFi, M-WiMax BACK OK

6 FMC Network Architecture 6/45 WiFi RGW AP Cable CMTS PS (Policy Server) Application Server Enabler (PS/IM/DMS) IMS Core HSS PTA TAS VCC Other AS CG Signaling (SIP) Signaling (Diameter) Signaling (MEGACO) Signaling (ISUP) IP Bearer TDM Bearer WiFi SCIM WiFi AP RGW WiFi Broadband A-RACF (xdsl) BRAS WCDMA/CDMA/WiBro WiBro GGSN/ PDSN/ ACR AGCF SBC-SP (IMS-ALG) CSCF MRFC MGCF IBCF Other IP Network Narrowband AGW SPDF PCRF Resource and Admission Control Subsystem SPDF POTS Phone C-BGF IMS-AG MRFP IP Transport MGW I-BGF PSTN

7 Features of IMS (1/2) 7/45 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.)

8 Features of IMS (2/2) 8/45 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

9 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 R6 (HSPA) Service standard 3GPP R7 (HSPA+) Interworking with other networks 3GPP R8 Fixed-Mobile Convergence Adoption of IMS standard 3GPP2 ETSI/TISPAN CableLabs 9/45 3GPP (3 rd 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)

10 10/45 Service Continuity

11 Service Continuity Concept 11/45 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 Service Continuity Provides domain transfer/selection of multimedia services

12 Voice Call Continuity (1/2) 12/45 Provides capabilities to transfer voice calls between the CS do main and the IMS Application Servers IMS Core VCC AS WCDMA / CDMA (CS Core) Provides VoIP service in WiFi/WiBro at low price Multimedia Service (VoIP/MMoIP) IMS Domain WiFi WiBro WiFi Voice, Video telephony & SMS IMS to CS Domain Transfer CS-Domain WCDMA/CDMA Increases user convenience by providing telephony service continuity beyond IMS coverage CS to IMS Domain Transfer Multi-mode/One Phone/One Number

13 Voice Call Continuity (2/2) 13/45 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 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 3GPP VCC Standardization Stage 1: TR , TS22.101, TS Stage 2: TS23.228, TS Stage 3: TS24.228, TS GPP2 VCC Standardization X.P , Voice Call continuity between IMS and Circuit Switched Systems Stage 2 X.P _v0.2 SMS Interoperability Stage-2 3 CableLabs (PacketCable) PacketCable 2.0 Cellular Integration, PKT-cellular-D01

14 Single Radio VCC 14/45 Provides Voice Call Continuity between IMS over PS and CS when the UE is capable of transmitting/receiving on only one o f 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)

15 Single Radio VCC for 3GPP2 (1/2) 1xCS SRVCC UE 1xRTT CS Access A1 A1 1xRTT MSC IS41 (ISUP) VCC AS 1xCS IWS S102 S11 3GPP2 IMS MME 1xCS SRVC C UE E-UTRAN SIP signalling Bearer before HO Bearer after HO S1-MME S1-U Serving/PDN GW SGi Tunnelled 1xRTT messages MME/E-UTRAN should support tunneling mechanism for sending CS signal message to 3GPP2 CS domain 15/45 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

16 Single Radio VCC for 3GPP2 (2/2) 16/45 SRVCC Network Diagram from LTE to 3GPP2 CS Originating Side Target Side 1xCS SRVCC UE E-UTRAN MME 1xCS IWS 1xRTT MSC EUTRAN/EPS tunnelling S102 tunnelling Registration and Authorization if needed Towards VLR/HLR E CS Call setup procedures Call terminated at VCC AS VCC AS STARTS VCC Domain Transfer PROCEDURES 1xCS signalling messages tunnelled across EUTRAN / EPS 1xCS signalling messages tunnelled inside S102 protocol A1 messages

17 Single Radio VCC for 3GPP (1/2) 17/45 UE Um/Uu Target UTRAN/GERAN Iu-cs/A MSC Server Iu-ps/Gb SGSN S3 S3-cs SGs VCC AS MME S6a HSS 3GPP IMS S1-MME S11 UE LTE-Uu E-UTRAN S1-U Serving/PDN GW SGi 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

18 Single Radio VCC for 3GPP (2/2) 18/45 SRVCC network diagram from LTE to 3GPP2 CS UE E-UTRAN MME MSC Server Target UTRAN/GERAN 3GPP IMS Measurement Reports Handover to UTRAN/GERAN required Initiates SRVCC for voice component Handles PS-PS HO for non-voice if needed CS handover preparation IMS Service Continuity Procedure Handover CMD To eutran Coordinates SRVCC and PS HO response CS HO response to MME Handover execution

19 IMS Centralized Service (1/4) 19/45 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 I1 SCC AS ISC UE Gm CSCF I2 GERAN/UTRAN Access A/Iu MSC Server I3 IMS-MGW 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

20 IMS Centralized Service (2/4) 20/45 Service Control Signaling Path established via IP-CAN SCC AS Remote Leg Access Leg SIP AS 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 IMS Centralized Service (3/4) 21/45 Service Control Signaling Path established via CS network SCC AS MSC Server/HSS Access Leg Remote Leg SIP AS 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

22 IMS Centralized Service (4/4) Service consistency Core Network IMS Centralized Services ICS enhanced CS MSC Legacy (or ICS enhanced) CS MSC SAE Access Network 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 IMS Centralized Services Provided to User CS Equiv MMTEL SS Partial MMTEL SS Data IP Services FULL MMTEL SS Hi Speed Data Rich IP Services FULL MMTEL SS Hi Speed Data Rich IP Services FULL MMTEL SS Hi Speed Data Rich IP Services FULL MMTEL SS Hi Speed Data Rich IP Services IMS Video IMS Video IMS Video IMS Video Real Time Services ( Gaming ) Real Time Services ( Gaming ) 22/45 Common Device Client provides Consistent User View Service Capabilities Grow with Access Capabilities

23 Multimedia Service Continuity (1/4) 23/45 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

24 Multimedia Service Continuity (2/4) PS PS Session Continuity UE-1 Non-3GPP (e.g. WiMAX) Voice + data P-CSCF-a1 UE-2 E-UTRAN MGCF Intermediate IMS elements Voice + data Voice + data P-CSCF-a2 PS-PS session continuity in conjunction with PS-CS continuity UE-1 WLAN Voice + data P-CSCF-a1 UE-2 UTRAN / GERAN ICS interworking nodes P-CSCF-a2 Data Voice Intermediate IMS elements Voice + data 24/45 To support Service Continuity between CS and PS of bidirectional speech media in IMS sessions, ICS AS shall be used for the CS leg

25 Multimedia Service Continuity (3/4) 25/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 UE-2 Other media IP Network Voice UE-1 IP-CAN2 UE-2 IP-CAN1 UE-1 CS Access UE-1

26 Multimedia Service Continuity (4/4) 26/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

27 27/45 IMS QoS

28 IMS based QoS (1/2) 28/45 Why IMS based QoS? Goal 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. 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, operator s policy rules and subscription profile

29 IMS based QoS (2/2) 29/45 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

30 3GPP PCC Architecture (Rel.7) 30/45 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

31 3GPP PCC Architecture (Rel.7) 31/45 AF Diameter : Rx Online Charging System (OCS) CAMEL SCP Service Data Flow Based Credit Control Subscription Profile Repository (SPR) Sp Policy and Charging Rules Function (PCRF) Diameter : Gx Diameter : Gy PCEF 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 Diameter : Gz Offline Charging System (OFCS)

32 3GPP EPC QoS Architecture (Rel. 8) Rx+ AF H-PCRF S9 V-PCRF 3GPP TS CN Architecture for 3GPP - Rx+, S9, S7 interface PCRF 3GPP TS CN Architecture for non-3gpp - Rx+, S9, S7, S7a/b/c interface S7c S7a S7b S7 S-GW A-GW epdg P-GW (PCEF) 32/45 3GPP TR GPP 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

33 WiMAX PCC Architecture (NWG Rel.1.5) ASN CSN ASP ASN1 Anchor SFA/A-PCEF Accounting Client R4 PCC-R3-OC ASN2 Serving SFA Accounting Agent PCC-R3-P Charging Distribution Function (MIP) Policy Distribution Function Gx ( Ty) PCC-R3- OFC Gy (PCC-based) Gy/Gz HA Non-roaming scenario PCRF Sp SPR/ AAA Gz OFCS OCS/ Accounting Client Rx(Tx) PCC-R3-OFC C-PCEF AF (P-CSCF or non-ims application server) Home IP Network Re-Used -PCRF, SPR -Rx, Gx interface New -PDF -PCC-R3-P/OC/OFC interface 33/45 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

34 PacketCable 2.0 QoS Architecture AF P-CSCF UE pkt-qos-1 SOAP Gm: signal CM AF #1 AF #n PacketCable Application Manager (PAM) Signal translation DOCSIS pkt-mm-3 COPS pkt-mm-2 COPS PacketCable 2.0 Policy Server CMTS PDP pkt-qos-2 PEP PacketCable 2.0 Define Architecture and Functional Entities, etc. 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 UE CM AF Rx DOCSIS IP-CAN PCRF AM PS PCE CMTS Pkt-mm-2 (COPS) 3GPP Harmonization PCRF Merging the AM (Application Manager) and PS (Policy Server) pkt-qos-1 interface Rx (Diameter) 34/45 3GPP Harmonization

35 35/45 IMS Charging

36 IMS Charging 36/45 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 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).

37 IMS Charging Architecture (Offline) 37/45 IMS Charging Correlation Based on unique ICID (IMS Charging Identifier), Charging correlation will be performed for session, bearer and service/event charging Correlated CDRs (Charging Date Records) Billing Domain IMS based Integrated Offline Charging Server (CDF/CGF) MRF Charging event Information AS AS MGCF CSCF/BGCF PCRF IP IP Edge Session Information Charging rules (Offline) Service & Event Charging Session Charging Session & Event Charging Bearer Charging

38 IMS Charging Architecture (Online) 38/45 IMS Charging Correlation Based on unique ICID (IMS Charging Identifier), Charging correlation will be performed for session, bearer and service/event charging Correlated CDRs Billing Domain IMS based Integrated Online Charging Server (OCS) MRF IMS-GWF IMS-GWF Charging event Information AS AS S-CSCF P-CSCF P-CSCF Session Information PCRF IP IP Edge Charging rules (Online) Service & Event Charging Session & Event Charging Bearer Charging

39 Benefits of IMS Based Charging 39/45 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.

40 40/45 GRUU (Globally Routable User Agent URIs)

41 Globally Routable User Agent URIs 41/45 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-a765-00a0c91e6bf6" 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

42 IMS Subscription & ID 42/45 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 Implicitly Registered ID Set 1 Service Profile 1 Service Profile 2 IMS Subscription Public User Identity 3 Public User Identity 4 Implicitly Registered ID Set 2 Service Profile 3 Private User Identity Public User Identity 5 Public User Identity 6 Implicitly Registered ID Set 3 Service Profile 4

43 Relationship of PUIs, GRUUs and UEs 43/45 Relationship of PUIs, GRUUs and UEs Public User Identity GRUU Set 1 UE 1 Instance ID1 Public User Identity Public User Identity GRUU Set 2 GRUU Set 3 GRUU Set 4 UE 1 Instance ID2

44 44/45 IMS Vision for FMC

45 IMS Vision for FMC Anytime, anywhere access to converged services with anydevice Converged Services Network Convergence Service Continuity Seamless services for the same user over different access networks and different devices Unified core network, multiple access networks QoS/Charging/Single Sign On Device Convergence Multi-Band/Multi- Mode/Multi-Media Device 45/45 VCC/SRVCC, ICS, MMSC Private ID/Public ID, GRUU

46