Slides presenting the approach "WebRTC for Telcos" by Solaiemes. How our WebRTC-Telco GW and its SDK enable telcos to use the potential of WebRTC to innovate in the future communications space.
2. The
Goal
q Helping telcos to add value to their current
services.
q Making fix & mobile voice available using a
web-browser ubiquitously
q Engage the customers & reduced the churn
3. What
is
WebRTC
WebRTC (Web Real-Time Communication) is an
API definition being drafted by the World Wide
Web Consortium (W3C) to enable browser-tobrowser applications for voice calling, video
chat, and P2P file sharing without plugins.
4. Only
browser
to
browser?
NO!
It could be implemented a WebRTC – Telco
Gateway to as a bridge between Web and fix/
mobile operator networks allowing service
providers to extend their communication services
to the Internet. It means creating web-based
telco end-points.
5. WebRTC-‐Telco
Gateway
architecture
internet
WebRTC
signalling
&
media
WebRTC
TELCO
Gateway
IMS
OR
SBC
Voice Core
Telco
signalling
&
Media
telco
So?Switch
IMS Core or SoftSwitches supporting SIP
access DO NOT need any modification
UNI
6. Feasible
as
Cloud
based
architecture
The WebRTC-Telco GW
can be deployed
outside the telco
premise, in a public or
private cloud as the
access to the network
core is UNI based
7. The
plaHorm.
WebRTC-‐Telco
GW
q
Hardware. Intel based server architecture running Linux (Dell, HP, IBM), no special
HW needed, also deployable in public clouds as AWS and virtualized environment
for cloud computing as Cisco UCS.
q
Scalable to the number of concurrent calls and users online needed .
q
A single platform could serve different cores, multi-tenancy available.
q
A single platform could serve different UX for different customers profiles.
q
It could be combined with RCS Thin Client Server to provide an all-in-one Unified
Communications experience: voice, video and enriched messaging.
q
Supporting current WebRTC capable Web-Browsers: Google Chrome & Mozilla
Firefox for Windows, Mac & Linux and Chrome for Android.
8. Features
q
Via WebRTC instanced e-164 identity based phone
q
Outgoing voice-calls / Incoming voice-calls
q
UI/UX modules
ü
Dialer
ü
NAB (network address book) . Possible easy integration with 3rd party NAB.
ü
Call History (starting time, call duration, missed/answered/rejected icons)
q
UI/UX customizable with customer logo and colors. Also possible full re-design
q
UI/UX could include RCS capabilities when combined with RCS Thin Client Server Product
q
RCS Videoshare and IP Videocall capable
q
For the of RCS services with separated voice & RCS cores, dual register capable.
q
Login with credentials not exposing real IMS/Softswitch credentias). Security.
q
HTTPS available for signalling.
q
Plug&Play on top of SIP Servers, SoftSwitch with SIP access, IMS. Proven in 3 telcos from 3 countries. Also could
be integrated with legacy PSTN.
9. SDK
and
embeddable
modules
q The javascropt SDK allows to use Voice/Videocapabilities in your
website freely.
q Embeddable modules make even easier to add WebRTC to third
party websites or applications. Just embedding the pre-designed
modules with CSS3 configuration to adapt to whatever UX preexisting style. Modules include now:
•
Simple dialer
•
NAB
•
Call register
•
…more coming soon…
10. WebPhone.
IniMal
User
Inteface.
Videodemo: https://www.youtube.com/watch?v=q0vClE774aE
UI/UX as it is web
based could be fully
redesigned easily
11. RCS
Full
(messaging,
voice,
video)
Web
Client
Videodemo: https://www.youtube.com/watch?v=V-DvXcngHnk
Combined with RCS Thin
Client Server product it is
possible to build a RCS
web client with all the
features, voice+RCS
UI/UX as it is web
based could be fully
redesigned easily
12. RCS
vs
WebRTC
WebRTC is not a rival service of RCS nor
telco communications, instead it is a great
tool for telcos to extend their end-point
portfolio, and leverage a more ubiquitous
reach of their enablers.
13. WebRTC-‐Telco
GW
internal
architecture
The platform includes the
web-server to serve the
“WebPhone” but it could
be served from other
server as in the case of
future WebRTC cases
using the SDK.
17. Telco
services
deployed
in
days
Javascript SDK as
tool to create
easily telco
services as:
•
•
•
prepaid call-me
services.
creating casual
access to telco
comms
interworking with
OTTs, etc
18. SDK
use
cases:
WebRTC
Service
Market
Portal to buy
prepaid VAS using
WebRTC as callme services hiding
your real number,
international calls
or authorizing SN
friends to call you
without knowing
your number.
19. The
business?
A market of WebRTC services based on
telco capabilities, causal services to
engage the users and extending the
reach of telco driven comms.
Self-service web based market of
premium services based on WebRTC.
Innovation connecting telco and nontelco identities.