Service Environment migration to IMS

Matjaž Beričič MSc. CTO, Mobitel

3GPP release 8 IMS implementation, deployment and testing Sophia Antipolis 24th of November 2010 Agenda

 Introduction to Mobitel

 Mobitel Service delivery environment based on (NG)IN

 Mobitel multimedia intelligent network evolution

 A view to 3GPP Release 8

 Conclusions, Questions & Answers

2 Mobitel, Slovenia – relevant country data

Area: 20,273 km2 Population: 2,008,516 (30.6.2006) GDP per capita: 17.331 EUR (2009) Independence - 25 June 1991 Member of EU - 1 May 2004 Currency: Euro - 1 January 2007 Mobile operators: Mobitel, Simobil, Tušmobil, T2 Mobile penetration: 103% Broadband Internet access: 56% of households (2009) Plasic (credit&debit) cards: 1,9 per inhabitant POS terminals: 32.000 POS: 7.500

3 3 Relevant data on Mobitel d.d.

 “Incumbent” MNO with 56% market share (1.171.802 users, 835.523 post-paid).

 Part of Telekom Slovenija Group (7 countries, 4 MNOs, 3 ISPs, 2 POPs).

 Market leader in value added services (IN, messaging, portal, payment, mTV, mAdvert,3pSE)

 Typical technological trends: NW modernization MSS (Rel4) done, HSPA+ under broad deployment, MBB FUP, SIP FMC services, SOA

4 Mobitel Service environment – (ng)IN domain of SDP

 Prepaid

 Virtual Private Network – business FMC

 Call completion

 Single Personal Number – GSM/GSM, GSM/SIP

 Mobile Call Center – advanced call distribution, premium numbers

 EMCY location

 BAOFD, Incoming Call Screening

 RBT

 In-house development; Group sinergies

5 IMS deployment environment and drivers

 Fixed networks trends and evolution  TDM  VOIP, VOIP internet (OTT), FMS, IPTV, FBB, FTTH slowdown  (over)regulation  Mobile networks trends and evolution  NW modernization, MBB HSPA+, FUP, Convergence of all technologies and signalling systems via ‘all-IP’  new terminal eq.players – Smart phones, appstores, Slowdown of ‘GSMA domain services development’, e.g. RCS versus Social Networks (i.e. Communication versus Advertising industry)  (over)regulation  LTE, LTE-A  Digital dividend to overcome Digital divide?  IMS should support network evolution, convergence and new services  But what happened with a promising role of IMS?

6 6 IMS role in new communications world

Source: Ericsson 7 7 Hype Cycle for CSP Infrastructure, 2010 – IMS, RCS

8 Key Next-Gen SDP Capabilities Function Description – “The Menu”

9 Genesis of IMS standards

10 IMS - multimedia intelligent network evolution

 “If IMS will only promise new multimedia services but not support also migration/evolution of some existing advanced and costly services&platforms, it will fail or will be significantly delayed.” – M.B. in 2004 after Push2Talk IMS trial

 Mobitel path to IMS:

 Pre-standard SIP solutions

 Video gateways, GSM/SIP SPN (m:stik)

 IMS trial in 2007-2008

 Infrastructure (standards compliance), NNI, Presence, SDK, terminals

 FMC, CS IMS anchoring…

 Almost in parallel: ngIN evolution

 Why not combine IN and IMS?  IMS Centralized Services

 Paradox after all these years: IMS, designed for PS would serve CS 11 IMS development at Mobitel

 SIP domain

 IMS puzzle is coming up in pieces, e.g. SBC, PCRF (FUP), MGCF, IM-MGW

 First SIP services in Convergent domain

 Clients

 NG-IN evolution  IM-SCF IMS Centralized Services

 RBT service is migrated to IMS MMRB solution, we gain:

 Unique service for CS and PS users

 Video ring back content

 Environment for mobile advertising based services

 MKC is migrated to MultimediaMobileCallCenter:

 Premium Rate Number on mobile and SIP soft-clients

 Flexible enviorment, administration and control via WEB

 IMS AS: simply better to be integrated into Web environment, mainly important for 3rd party Service Exposure

 But: IMS readiness to cover all IN services?? (IFC capabilities the same as SSF, triggering flexibility ...). Waiting for “full” ICS…

 SSF, MGCF, CSCF, IM-SSF, IM-SCF, SCP

 Vendors, please put all these close together as possible  12 IMS development at Mobitel Presence Presence Enabled GMPC Network Agent Applications

SIP MLP SIP XCAP

Sh PGM  Presence and Group Management HSS Web user Zx Aggregation DNS interface Presence XDM DNS ENUM G&DM Proxy  OMA Enabler (as Location) to be open for SLF Zx

plenty of services, not just SN based, like RCS HTTP XCAP SIP XCAP Presence Web client XCAP client  Clients OMA compliance User Agent

 SOA in business support and SDP domain

 IMS development beyond NG-IN evolution

 RCS: IM-Messaging, PresenceGM, VShare...

 Mobile advertising

 Business Communication Suite

 Development of own services

• SDP evolution

• 3party Service exposure in web domain

 Any access:

• VCC

• MMTEL, LTE/SAE ...

 Qplay enrichment, IPTV, DLNA

13 Interworking and integration issues: MMRB example

 If MGCF on MSCS doesn`t support multiple SIP dialog, then it cannot be used

 SIP-ISUP Interworking problems between MSS and IMS

 189 + 183 (CPG alerting indication): A subscriber is not able to turn load speaker on while playing MMRB - with some phones --- OPT BACKW --- A : ...... 1 = in-band information or an appropriate pattern is now available B : ...... 0. = no indication C : .....0.. = no additional information will be sent D : ....0... = no indication E-H : 0000.... = reserved for national use PARAMETER : 2Eh LEN : 1 --- ACC DELIV --- A : ...... 0 = set-up message generated H-B : 0000000. = Spare bits PARAMETER : 39h LEN : 2 --- PARAM COMP --- PARAMETER : 2Eh = Access delivery information --- INST INDI --- A : ...... 0 = transit interpretation B : ...... 0. = do not release call C : .....0.. = do not send notification D : ....0... = do not discard message E : ...0.... = do not discard parameter (pass on) GF : .10..... = discard parameter EXT INDI : 1...... = last octet PARAMETER : 00h

 Subscriber absent: MGCF converted ISUP ACM cause 20 (Sub.absent) into 180 ringing - ringback tone played for detached B number.

 CallForwarding : redirection reason was not mapped into SIP history info.

 Optional Backward Call Indicator: sometimes ACM with OPTbackw information was received and in this case MMRB was not played.

14 Importance of 3GPP Rel-8 IMS items 1 (Completed in end 2008)

 Common IMS - IMPORTANT Incorporation of TISPAN, 3GPP2 and PacketCable specifications into 3GPP, aligning the different flavours of IMS into one common IMS. This is done in a number of areas, such as Security, Multimedia Telephony services and Presence. Examples of detailed features, not indicated elsewhere, are Access awareness and Notification of IP-CAN type change .

 MMTel service and supplementary services, evolution Based on TISPAN R2 and 3GPP2 requirements. Supplementary services such as Communication Waiting, Communication Completion on Busy Subscriber, and Advice of Charge. Also general MMTel supplementary services generated charging output AVPs.

 IMS Centralized Service Control – VERY IMPORTANT Full service control by the IMS domain also at mobile CS access. Deployed before 2012?

 IMS Service Continuity Transfer of sessions between accesses, including handover of voice sessions between broadband and mobile CS access. Implies replacement and enhancement of Rel-7 Voice Call Continuity. Single radio VCC (handover 3G PS to 2G CS) is standardized, facilitating single radio solutions over cellular access. These standards are further evolved in 3GPP Rel-9 onwards.

 Inter-IMS Network to Network interface Protocol interconnection to support the delivery of IMS services between two separate IMS networks with the focus on a basic call. Reference point Ici for support of IMS procedures on the control plane, and Izi for exchange of media streams. Specified in 3GPP TS 29.165.

15 Importance of 3GPP Rel-8 IMS items 2

 ISC/iFC enhancements - IMPORTANT Items such as Increased flexibility, Fault handling, Request URI handling at additional AS invocations, and Additional information sent at 3rd party registration.

 CAT(Customized alerting tone) -  An alerting tone that is customized by the called subscriber. It may e.g. be a piece of recorded music, greeting words , voice, advertisement or video.

 Local Breakout for IMS System enhancements for the use of IMS services in local breakout at within one operator’s network or roaming to a visited network. More detailed definitions of how to discover and connect IMS (P-CSCF).

 IMS Restoration Procedures A set of standardized procedures for automatic restoration after loss or corruption of S-CSCF data. The objective is to improve the quality of service to end-users. Specified in 3GPP TS 23.380.

 IMS based Mobile TV IMS application level initiated and controlled 3GPP Rel-6 PSS (packet switched streaming) and MBMS (multimedia broadcast multicast services). IMS application server access to mobile network multimedia services.

 Advice of charge support Transport of Advice of Charge (AoC) tariff information on applicable charging interfaces, evaluation of tariff information (Online Charging System), as well as the advice to the subscriber.

16 Importance of 3GPP Rel-8 IMS items 3

 Formalising multiple authentication methods - IMPORTANT Formal inclusion of the pre-IMS AKA authentication methods used by ETSI TISPAN, Packet Cable, and 3GPP2. Those include the methods Digest authenticaion, GPRS-IMS Bundled authentication(former "Early IMS security"), and NASS-IMS bundled authentication. In addition ’Authentication co-existence’, including the possibility to have multiple authentication methods in the same system and for the same user.

 Corporate Network access support Enhancements to IMS covering corporate network access. Support for both subscription based (UNI type) and peering based (NNI type) corporate access to IMS. Introduction of Wildcarded Public User Identities and handling of trusted identities for subscription based access.

 Cable Network regulatory requirements support IMS interworking aspects driven by the regulatory requirements of cable networks. Includes Local number portability and Equal Access.

 Multimedia interworking between IMS and CS networks -  Standardisation of the Video service interworking. MGCF and SGW to deliver control plane aspects, and MGW to deliver the user plane aspects.

 Service-level interworking for Messaging services - IMPORTANT Interworking function between Instant Message and the Short Message to enable the communication between SM User Equipment and Instant Message User Equipment.

17 Conclusions

 Current networks evolution and a changing role of IMS

 Supporting network/SDP evolution and convergence

 Supporting new services deployment

 Mobitel on the way with ngIN to IMS (multimedia IN) migration

 Still plenty of MSS – IMS interworking issues

 Still plenty of problems when mapping IN triggering flexibility to IMS

 Importance of IMS standardization in 3GPP

 Rel8 Common IMS for both fixed and mobile domains

 ICS to support ngIN evolution (glad to see our vision in it )

 The three elements of the story: network evolution, convergence and new services

 ICS gives IMS important push

 But: RCS potential drifts to OTTs.

 Could originaly GSM based terminal equipment players wake up on time?

18 ?

matjaz. [email protected] phone: +386 31 740 660