Marcus Evans Signaling Evolution Forum

Transcript

1. Interconnecting the IMS Architecture With Other Protocols Sebastian Schumann Slovak Telekom, a.s. – Core and Control Department 30. January 2012. Berlin, Germany
2. Topic §  Interconnecting the IMS architecture with other protocols §  Providing IMS signaling, applications for mobile and broadband IP customers §  Centralized routing in an IMS architecture §  Expanding future services related to IMS network internationally Textbox Headline §  Slovak Telekom communications platform at a glance §  IMS deployment – experiences and next steps §  All-IP opportunities §  Challenges and chances for converged operators Agenda
3. Slovakia Czech Bulgaria Serbia Bosnia - Herzegovina
4. Slovak Telekom, a.s. §  Slovak Telekom Group is the telecommunication market leader in Slovakia §  T-Com, T-Mobile (merger in 2010), Zoznam, Posam §  We provide fixed network services, mobile communications, Internet access + content, data services, CPE, ICT services (data center + cloud), radio and TV broadcasting as well as commercial call center services §  The major shareholder is Deutsche Telekom AG, one of the largest telecommunications operators worldwide §  Successful deployments in SEE as well as in DT group §  One of the biggest national-wide deployment of NGN technology in Europe in 2004, whole city migrated to all-IP NGN in 2007 §  Fixed network IMS migration started in 2011 (class 5 replacement) §  Leader in IPTV (since 2006) and providing also hybrid sat TV (since 2009) §  Extensive FTTx deployments (350.000 households) §  First Flash-OFDM deployment for mobile data in 2005
5. Communication platform at a glance Access §  Fixed broadband access available §  A-DSL up to 12 Mbit/s §  FTTX up to 80 Mbit/s §  2G/3G access, EDGE/UMTS/HSPA mobile broadband access §  Up to 42 Mbit/s §  F-OFDM technology §  Up to 5 Mbit/s à  IP connectivity on fixed/mobile is available à  However, no “extended usage” of IP connectivity for communications yet
6. Communication platform at a glance Core §  Fixed platform in transition towards IP for a long time §  Migration from TDM to softswitch based NGN to IMS in the last years §  2 NGN platforms §  1 IMS platform §  Fully software based telephony since 2006 §  Residential VoIP “Smart” §  Business VoIP “Virtual Voice Net” (Hosted PBX) §  Successful IP based communications connectivity for businesses §  Business trunk §  IP hubbing for VoIP interconnection à  SIP main control protocol for voice call control à  SS#7 still used for PSTN connection and connection to nat. + int. providers
7. Communication platform at a glance Core ctd. §  Mobile platform still “two-fold” §  “Legacy communications” with circuit switched network elements + protocols §  Fast packet-switched broadband access §  IP is used mainly in the core network, not to connect customers or other networks §  IP (ATM) to connect new RNC §  SIGTRAN (SS#7 over IP) between MSC, MSC – MGW, MSC – STP/HLR §  Since 2009 swap from monolithic to layered architecture §  IP based voice SGW using SS#7 ISUP for connection to fixed network as well as national and international operators Direct integration of mobile platform is a big challenge for now. IP based communications services cannot be easily provided.
8. What to do next? §  Slovak Telekom, a.s. started migrating the fixed network to IMS in 2011 §  Migration to IMS in SEE mainly by fixed operators so far §  T-Com Hungary, Croatia, Macedonia, Montenegro, Slovakia §  After merger in 2011, common activities (fixed + mobile) started §  After migration, next steps on the IMS are being evaluated Textbox Headline Applications? What to do next? What to do NOW? Services? Monetization? Integration? Interconnection? Aggregation? (How) Can the IMS help? Mobility?
9. IMS integration §  Many operator’s IMS platforms have been built for PSTN replacement §  RCS/RCS-e mostly deployed discussed “non-telephony” related application on the IMS §  … and yet there is no killer app §  Business telephony was there before §  PSTN emulation is nothing new for the customer §  Phonebook deployments are not yet fully integrated How can we leverage the existence of the IMS with regard to new services?
10. Fixed post-migration service scenarios §  Integration of voice with existing IP based television §  Call with the set-top-box? §  TV set supporting communications! à  Use all services and devices in your domain for an overall service experience
11. IPTV phonebook TV from http://images.campingworld.com/is/image/cwi/40000/42360n.jpg ABC DEF GHI JKL MNO PQR STU UVW XYZ 1 2 3 4 5 6 7 8 9 Address Book Contacts Too many matches! Sajban Schumann Tabor
12. Tomorrow’s Screen TV from http://images.campingworld.com/is/image/cwi/40000/42360n.jpg Calling Sebastian…
13. Fixed post-migration service scenarios §  Integration of voice with existing IP based television §  Call with the set-top-box? §  TV set supporting communications! à  Use all services and devices in your domain for an overall service experience §  Blended services §  Communications as enabler (multi-media, presence, messaging) §  Integration with own services, web integration §  Capable of being integrated with external apps (APIs) §  New business/tariff models §  Ad supported calling (TV set has enough screen estate) No “killer apps” or “desperate innovation”. Integration of own systems and “owned” screens improves products and perception.
14. Mobile network integration §  IMS as common control platform would reduce OPEX as well §  Not trivial, not fast! §  Some investments necessary on mobile side (upgrades) à  Converged operator’s benefits have to be leveraged sooner §  Common user identity between fixed and mobile §  Common services §  Integrate identity management for further federation before §  Subscribers become users, strong OSS/BSS support required §  Identity management to be able to map users §  User mappings can be re-used (e.g. mobile applications, IPTV) à  Provide integrated fixed/mobile services even before convergent network
15. Identity Management Customer 1 Customer 2 Service 1 Service 2 Service 3 Service 4 Customer Service Service 5 PAYS
16. Identity Management ctd. Customer 1 User 1 Customer 2 User 2 Service 1 Service 2 Service 3 Service 4 Customer Service User Service 5 PAYS USES ≠ User-centric Model Potential relation
17. Common service platform §  Service Delivery Framework spanning fixed and mobile call control §  Vendor independent application logic §  New efforts usable within new and legacy networks §  Existing services can be easily extended with IMS access §  Software component that hosts applications and provides access independent adaption layer §  INAP, CAP for legacy support integrated §  SIP for IMS support §  Support for legacy protocols still important §  Migration towards IMS just started §  Legacy technologies still in use for the mid-term future
18. Aggregation §  Centralized routing in the IMS §  MSC upgradable to support SIP and be connected to the IMS (internally) §  HSS front-end extension to serve as HLR à  Single user base manageable §  From using IMS call control logic to IMS centralized services §  End device connectivity for voice can remain CS for now §  Omit early problems of interim solutions towards VoLTE §  No investment necessary §  Re-think strategy in the long run Concentrate on data for LTE coverage for now. Re-think voice strategy with low new investment, while benefiting from convergence.
19. Interconnections with other operators §  Interconnection still heavily based on legacy signaling §  National interconnect only SS#7 (fixed and mobile) §  International interconnect mainly SS#7 §  Some VoIP interconnect via H.323 and SIP §  Phase-out of PSTN and introduction of IP based interconnection brings benefits §  More flexible codecs (e.g. HD Voice) §  More secure than SS#7 (follows high demand of secure voice interconnection) §  SIP becomes de-facto standard for signaling §  Regulation might be a problem (VoIP interconnect differs from traditional PSTN)
20. Slovak Telekom interconnections (fixed perspective) PSTN NGN MOBILE National FIX network providers National MOBILE providers International providers GTW (Signalling & Media) GTW (Signalling & Media) MSC Server Transit Exchange GTW (Signalling & Media) IP HUB SS7 SS7 SS7 SIP/H.323 SS7 SS7 VoIP interconnect SS7
21. Challenges in the fixed market §  No “smart terminals” in the fixed environment yet, still phones §  Sometimes not even IP-terminals (HAG, A-GW) §  Smart phone/tablet is the smart mobile terminal that is represented by the PC at home §  Many parts of the architecture have been “just mapped” from PSTN to IMS §  Households with two lines (private, business) are still two subscribers §  Phone number still main identifier, no aliases considered §  IMS routing is based on phone numbers as well §  Interconnect still via PSTN §  Partially wrong communication with the customer §  Customer still has the choice for technology (analog, ISDN, IP-based) §  Wrong understanding: IP-based à Telephony via the Internet à Why not use Skype? http://www.flickr.com/photos/cgc/5259321/
22. Challenges in the mobile market §  “Visible innovation” happened only on the end devices, mobile network features not so much §  Tablet market (Wi-Fi only devices) and unmanaged access not considered enough §  Own OTT apps might be required to reach customers on those devices §  SIM/MSISDN is the holy grail in customer identification, nothing works without it §  Decrease in voice and SMS revenue §  It is neither decrease in voice minutes nor decrease in sent messages §  Operators do not know how to keep customers, be attractive to them §  RCS might keep customers in their domain, but does not solve revenue problem §  Long term strategy and new business models needed
23. Chances for converged operators §  Development on IMS integrated service layer is future proof §  Legacy integration can be achieved by direct integration or through IMS §  Northbound integration should not be an option, but a must! §  … and should be done with Web 2.0 technologies/protocols §  Integration on back-end (e.g. with IPTV, IMS services) is cheap and helps transition of the customer feeling of “Telco as single home communications provider” §  Not only keep QoS on IP (“assure it’s not worse”) but increase QoE (“make it better”) §  High-definition will become standard also in communications (voice, video)
24. Chances for converged operators ctd. §  Residential services can be enhanced with intelligent network features now §  MMS share, backend Web 2.0 integration (share on Twitter, post to Facebook) without applications to integrate feature phones/less powerful smartphones §  Tariffs must support this §  Start considering “smart end-points” (PCs, tablets, “non-phones”) as part of communication endpoints we have to serve and integrate §  Operators have to open up their architecture – the future is not a walled garden! §  Users needs a reason to use their applications – they have to be attractive and federate with the web! … or it will be accessed directly §  The Web 2.0 is user centric and open to be extended with 3rd party applications – the Telco 2.0 should follow this approach
25. Summary §  Operators do not yet fully utilize all of their estate §  Fixed/mobile integration for residential/business allows new products §  IPTV integration can be done today, no need to wait §  Integration is not always a matter of common core or protocols §  Simple backend systems can help §  Many service platforms can be re-used §  Development should happen for the future (with legacy support) and NOT to keep legacy logic and integrate it somehow with future systems §  Motivation to rather act now than wait for the perfect standard §  Utilize existing infrastructure §  Integrate on the back-end §  Integration is important (internally as well as opening for external access)
26. Thank you. Sebastian Schumann Senior Designer Core and Control Slovak Telekom, a.s. Sebastian.Schumann@telekom.sk +421 903 419 345