Review of the Next Generation Service Platforms event brings together 3 events: Telecom APIs, Web Real-Time Communications & Legacy Networks Evolution.
Weblog http://alanquayle.com/2014/07/ngsp-review-art-possible-mantra-self-defeat/
2024: Domino Containers - The Next Step. News from the Domino Container commu...
Next Generation Service Platforms Review 2014
1. A Few Highlights from the Next Generation
Service Platforms Event
http://serviceplatformsevents.com
June 10th and 11th 2014
Here are few highlights from the Next Generate Service Platform Event which took
place in Berlin, 10-11th June 2014. Just after TADHack, www.tadhack.com.
4. Dominique highlights in important aspect of WebRTC to Telecoms. Because its in the browser
its easier for developers to become aware of it than Telecom APIs which have very slowly (and in
some cases negatively) entered general developer awareness. But as I saw in TADHack, once a
developer sees what is possible in adding communications into their apps, services and business
processes with WebRTC; they then appreciate the ubiquitous access made possible of Telecom
APIs to any mobile device. What this means is WebRTC must be part of Telcos’ service
innovation platform and plans.
5. WebRTC Working Group Participants
Alcatel-Lucent Apple AT&T Avaya Baidu
Bistri Cable Labs China Unicom Chinese Acad.
Of Sciences
Cisco
ETRI Ericsson Genesys Google Hookflash
Huawei Microsoft Mirae Web Mitsubishi Mozilla
MStar NICTA Nokia Nuance Opera
Orange Qihoo 360 Plantronics Qihoo 360 Samsung
Telecom Italia Temasys Tencent Unify Verisign
Voxeo
Telcos are getting involved in WebRTC, but it needs to be the innovators, not the tired
old telco standards people. Looks at IMS, OneAPI, RCS, etc. The telco standards
route has failed the industry – their approach has not adapted to the IT-centric world.
6. WebRTC Status
• Protocol: stable core, lots of optimizations still in flux
• Codecs: audio done, video tabled for now
• Camera access: mostly stable
• P2P Audio / Video: stabilizing
• P2P Data: stabilizing
• Identity management: stabilizing
• Upcoming: screen sharing, 3D camera, push
WebRTC is not baked, and remains quite complex for many developers. This technology is a
long run disruptor, but telcos need to understand WebRTC within their own organization and
not rely on their suppliers. As an example of vendor mis-information, several operators think
they need IMS BEFORE they can use WebRTC. This is incorrect, and demonstrates why
operators can not rely on their IMS vendors for impartial strategic advice / guidance.
7. WebRTC Implementations
isWebRTCReadyYet.com
Even when all the boxes are green interoperability will remain an issue. In creating a HTML5
website you have to test in many browsers to ensure it works. The is going to be true for WebRTC
functionality as well, the web site that uses WebRTC in the browser will need to manage this.
8. Adapting To Change
Accelerating the pace and
overcoming the cost barrier.
Mark Windle, Head of Marketing
OpenCloud have maintained the same message for over a decade – telcos
need a communications focused service innovation layer to manage the
complex mess across legacy and multiple IMS platforms.
13. The Future of Voice Services
Beyond the Phone Call
Dean Bubley, Disruptive Analysis
IIR NextGen Service Platforms & WebRTC
Munich, June 2014
dean.bubley@disruptive-analysis.com @disruptivedean
Dean has a good review of this event here: http://
disruptivewireless.blogspot.com/2014/06/the-old-world-telco-
mindset-lives-on.html
14. The big problem for the mobile industry…
Copyright Disruptive Analysis Ltd 2014June 2014
0
200
400
600
800
1000
1200
1400
2012 2013 2014 2015 2016 2017 2018 2019
Voice telephony
VAS / digital
Internet/data access
SMS/MMS
$bn – Global Mobile
Operator Revenue
?
New/partner services?
Voice/video-based?
Verticals?
Source: Disruptive Analysis
We all know this problem, yet I continue to see a lack of time and cash being sensibly invested in
addressing this problem. Spend money on the innovators – spend your time on TADHack and
TADSummit which is focused on building the ecosystem. Pouring millions into strategic
consultants and NEP innovation projects is simply pissing money and time away.
15. RCS/joyn isn’t going to rescue messaging either
Copyright Disruptive Analysis Ltd 2014June 2014
Attribution (Creative Commons): https://www.flickr.com/photos/dhollister/2596483147I had to include this slide J RCS is now an interop spec between telcos, rather than a
real service. GSMA has failed on so many service initiatives I remain shocked action
has not been taken by the telcos that bank-roll it.
16. Net/Not neutrality won’t stop data flattening too
Copyright Disruptive Analysis Ltd 2014June 2014
Data connectivity will soon saturate in developed markets
Source: Disruptive Analysis Non-Neutral MBB Report
Dean’s analysis on non-neutral models for mobile broadband show that it’s a small
revenue opportunity – and its not in sponsored data or taxing the OTTs – its in
enterprise services (i.e. businesses running their business on mobile networks).
17. 2 problems: competition & substitution
Copyright Disruptive Analysis Ltd 2014June 2014
Price, functionality,
integration, coolness etc –
but still a voice app
More effective ways to
perform tasks than a phone
call or voice interaction
Voice will not disappear, but there are more effective ways than voice to achieve what
we want, hence why voice minutes are in decline in some developed markets.
18. The vision: voice & video comms everywhere
Copyright Disruptive Analysis Ltd 2014June 2014
The challenge is remaining relevant in this transition to communications being a part of many
applications, services and business processes. We have to act together as an ecosystem to make
this happen, and the GSMA is NOT the right route. They lack the freedom to act commercially
and the leadership team does not understand the emerging market: no WebRTC position, OneAPI
mess, RCS mess, weak 2020 vision, same tired old roaming model on voice and data, etc..
19. DISCOVER, DISRUPT, DELIVER
Telco API ARCHITECTS
ANONYMOUS
Dr. Andreas Boose
CSD Architecture
Telefónica Germany
Andreas gave a great presentation on the Telco AAA club ;)
20. DISCOVER, DISRUPT, DELIVER
9
LEARN & SHARE
This is critical, and through all the telecom events and organizations its simply not being done
adequately. Some Telcos think IMS is required before they can use WebRTC. Some Telcos are
grossly misinformed on OneAPI. Many Telcos remain focused on spending vast sums on
technology platforms without focused on the people, process and business. Build it and they will
come does not work – especially if you’re using OneAPI. And OneAPI for use internally is
inadequate as well – see Telefonica, Portugal Telecom and Telecom Italia for proof.
21. DISCOVER, DISRUPT, DELIVER
Some examples:
14
Help Each Other LEARN
SHARE
This is a key slide – we have to work together – in an open way that brings the all
components of the ecosystem together. And thanks for recognizing TADS J
22. DISCOVER, DISRUPT, DELIVER
16
Take Home CHANGE
critical situation
requires behavioural change
ADMIT – LEARN – SHARE –
HELP – ENCOURAGE – CHANGE
applying these consequently
gradual change may
pass a threshold to success
EXPOSE best features: Network,
Bundling, Billing, Identity
ENCOURAGE Tech Knowhow
JOIN FORCES where possible
situation
principles
hypothesis
what
I
share
This is a great summary. We have to change people and processes, not just
technology. Open, honest and ecosystem-wide (not just a few desk-jockeys and their
favorite vendors). The focus must be on the business – the technology is the easy bit.
24. Pay per Use
~100 Enterprises
~17 Web Services
~5M transaction/month
Revenue Sharing
~ 200 Partners
~150 Web Services
~30M transaction/month
Developer
Community
individual developers
& start-ups
API Management System
TELCO CAPABILITIES
Nice quantification on where they are, its early days, but they have engaged partners
AND enterprises which will be an important source of revenue growth.
25. Deployment of VoLTE on an IMS platform
Next Generation Service Platforms 2014
Legacy networks evolution
Antonio.Cuevas@telefonica.com
10-11 June 2014, Munich, Germany
Good review of the challenges the network folks face, and why it makes adding service
innovation to their plate a stretch too far.
26. As a consequence, many operators had to build several
IMS/IP networks…
Silos are back!
6
Silos never really left, but its true we have many more these days, see the earlier
OpenCloud presentation.
27. VoLTE, with SR-VCC and assuring universal consistent
service in CS and IP
Affects ALL the network nodes of an operator. The MOST complicated NT
project ever at Telefónica Germany!
8
VoLTE is NOT easy, but to deliver the SAME voice experience as 2G, there really isn’t
any choice. Unless we accept the voice experience can be in some scenarios inferior.
28. Yes…but
e.g. IMS core was there (o2 DSL voice), no new deployment for mVoLTE
But, e.g. we had to add functionalities like IMS – AKA to support the more
secure authentication mechanisms required by wireless VoLTE.
e.g. 2:
Interconnection IMS – CS was in place, re-use. BUT: now more scenarios
and they need to be supported in one single IMS:
Breakout to CS for voice
•To o2 mobile network
•To the rest of CS networks
IMS to IMS interconnection
•But not for all the services! Just for RCSe
10
Its not easy with all the silos – it requires much effort.
29. And how to re-use telephony services?…
Existing telephony services (DSL) can be re-
used for VoLTE… but in VoLTE context they
need to co-exist with CS world
Call Waiting: UE or Network Service?
CDIV “not logged in”: offer it? In GSMA IR92
not clear if it is part of the service set or not
How many services are provisioned to the
user: how can UE interrogate this via Ut?
No clear guidance in GSMA. We had even to
push for standardization
11
And even on the really basic stuff there are gaps.
30. 15
We invest a lot to support
this:
And we still invest a lot to keep
this:
And we achieved exceptional networks
and communications possibilities
But, then, what
happens with this?
Telefónica’s
convergent IMS still
has to evolve but it is
in the right track!The core guys have enough on their plate, service innovation has to be a separate
group within a telco with a different group of suppliers. Else the business will always
be compromised by the legacy business trying to maintain its revenues.
32. This document is confidential and owned by Portugal Telecom. Unauthorized use or disclosure of the included information is strictly prohibited.
Service-Orientation Is Not Optional
Knowledge of the source code for each resource is
necessary
Forcing usage of specific programming languages
Consumer applications are coupled with underlying
technology
Knowledge of underlying resources technology is not
necessary
Developers code in their most proficient language against
standardized interfaces
Most common infrastructure aspects are abstracted and
standardized
Going from multiple point-to-point connections …to API management & mediation
Similar
apps…
…requiring
multiple
connections
to each
resource
Similar app
interfaces
will be
developed
in specific
languages…
…but
standard
resource
interfaces are
already
available
IT
Resources ContentNetwork
Resources
Enterprise Catalog of APIs
Service Delivery Broker
IT
Resources ContentNetwork
Resources
Domain APIs
SOA patterns drastically reduced multi-platform apps development effort and complexity
PT have delivered a common services infrastructure across all networks and end-
points. And its mostly self-built using off the shelf IT software, including open source
projects. Just like most web companies like Amazon and Google.
33. This document is confidential and owned by Portugal Telecom. Unauthorized use or disclosure of the included information is strictly prohibited.
• SDB Backoffice
– > 700 services, > 4000 operations, > 7000 strategies
– Average 23% increase YoY (over last 3 years)
– > 350 active users
• SDB Runtime
– > 40 million service requests per day
– ~20 ms latency
– ~13 TB XML/JSON data traffic per month
The Numbers (May 2014)
700 Services! With 23% growth YoY! Great example of the importance of taking
control of your destiny.
34. This document is confidential and owned by Portugal Telecom. Unauthorized use or disclosure of the included information is strictly prohibited.
One Protocol, Multiple IdP Options
They use OAuth but allow multiple identity options – as its about meeting the
customers’ needs not the telcos – that’s why telco ID management solutions can only
every be a compliment to existing solutions.
35. This document is confidential and owned by Portugal Telecom. Unauthorized use or disclosure of the included information is strictly prohibited.
• Collaborative API management, based on RBAC
• Gamification: service badges, level points, people’s reputation
• Standard service certification processes would benefit everyone
IT Service Management for APIs
Service
Operator
Service
Transition
Manager
Change
Manager
Service
Designer
Service
Developer
Project
Manager
Concept Design Develop Deploy Operate Retire
Partnerships
Manager
Security
Manager
Quality
Manager
Enterprise
Architect
Product
Manager
For internal service creation they have built a solid process – again following IT best
practices.
36. This document is confidential and owned by Portugal Telecom. Unauthorized use or disclosure of the included information is strictly prohibited.
• Jeff Bezos Mandate: check!
• APIs are needed for provisioning, but also for on-boarding, offers
configuration, selling, payments and revenue sharing.
• Most effort must be done through self-service portals and apps.
• Critical to sustain investment in innovation.
IT Processes Automation
PT remains for me one of the leading examples of a telco NOT wasting time and
money on “smoke and mirrors” SDP projects, instead focusing on using off the shelf
technology and processes to deliver a cost effective platform under their control that
delivers business results and keeps PT in control of its destiny.
37. This document is confidential and owned by Portugal Telecom. Unauthorized use or disclosure of the included information is strictly prohibited.
Service Management Interface
Application
Users
Monitoring and
Reporting
Content
Service
(e.g. News)
Network
Service
(e.g. Location)
Resource
(e.g. Database)
Application or API
Management
Interface (SMI)
Functional
Interface
e.g. GetManagementReporte.g. GetNews or
GetLocationByIPAddress
API Management is important but there are many solutions, including open source
options, the investment needs to be in the services not the management.
38. This document is confidential and owned by Portugal Telecom. Unauthorized use or disclosure of the included information is strictly prohibited.
• Cloud Services have great business potential for Telcos
– Can you forget about delivering Telco APIs for a minute?
– Can you forget about IaaS for a minute?
– Besides the network, what are your distinctive advantages?
– What about offering IT Service Management, Billing, Payments, IAM, API
Management, Marketplaces, etc. all of those “As A Service”?
– You may offer customer facing services, but APIs are (still) required
• Service-Orientation design principles helps business agility
• Multi-tenancy is required to sustain operational scalability
• Identity provider abstraction for competitive white-labeled offers
• Enabling clear integration “recipes” and easy-to-follow processes
for on-boarding partners and driving apps development
efficiently reduces integration cost and maintenance effort
Beyond “Telco APIs”: Cloud Services
PT are now focused on a range of bundled cloud services, this is worth watching as many telcos
have struggled to be successful is simply offering a me-too storage offer. PT is focused on a range
of local bundled cloud services – it will be interesting to see what market share they win. Initial
performance of those offers appears quite positive.
41. GRUPPO TELECOM ITALIA
Telecom Italia’s Update on
NetAPI Exposure
Next Generation Service Platforms, 10th June 2014
Mario Bonnet, Telecom Italia
Service Delivery Platform & Net API division - Head
Telecom Italia have a dedicated division to its APIs, headed by Mario.
42. Work in progress
NetAPI
Different protocols
From days to weeks
Market/segment specific
Ad hoc, traditional process
Provisioning
Today
Offering
NetAPI
Homogeneous, Web Oriented
More API available
Tomorrow
Provisioning
Offering
Unified publishing & browsing
catalog
Multi-tenancy
Marketplace oriented
«Self Service», «plug and play»
where applicable
«Easy» API
Third Party Internal
Network & IT Enablers
NetAPI interface
The focus of TI’s NetAPI development is very similar to what Portugal Telecom has achieved.
43. Bridge over troubled water
19Telecom Italia, T.TL.NMD.SD
NetAPI Creation
Network Abstraction
Service Orchestration
Service Execution
BSS & OSS Integration
NetAPI Exposure
Fully fledged SDP
- Network Platform will be natively more API-oriented
- Need of industry specific service bundles, bundling Telco NetApi with
enterprise/industry APIs (e.g. M2M, M-payment)
- Capex and Opex pressures: reduce TCO & complexity, explore
alternatives to traditional license based delivery models
Easy API Exposure
Thiner layer
Focus on NetAPI lifecycle
management
Native support of multi-tenant
environment
Collaborative and easy NetAPI
usage (self service model)
Though subtle the key messages are: its not an SDP, open source and revenue share
are going to play a greater role, enterprise (see Turkcell slides) will play a greater role.