RCS APIs and WebRTC for B2C communications
•
0 likes•815 views
The document discusses the rise of texting as a preferred communication method, especially among young people. It proposes using Rich Communication Services (RCS) APIs to enable innovative text-based business-to-consumer (B2C) applications and services. WebRTC could also bridge traditional phone networks with web-based applications and allow telcos to expose voice services via APIs. Sample use cases described include customer relationship management, public services, commerce applications, and enabling "new voice" capabilities. The document argues RCS and WebRTC APIs could help telcos engage in the growing texting economy and develop new communication services.
Recommended
Recommended
More Related Content
Similar to RCS APIs and WebRTC for B2C communications
Similar to RCS APIs and WebRTC for B2C communications (20)
More from Alan Quayle
More from Alan Quayle (20)
Recently uploaded
Recently uploaded (20)
RCS APIs and WebRTC for B2C communications
- 3. Texting is king • Young people likes texting, they text as fast as they can talk • Texting is asynchronous, voice pre‐empts multitasking • Searchable, sharable, helps personal management and network interaction • People is starting to consider intrusive a call when texting could do (especially youngsters) • With data plans texting is cheaper than voice in many markets • “New voice”/Hypervoice will fix some issues, but still not there
- 5. Where does B2C fit? • Voice and SMS still the workhorses for mass market B2C • Smartphone apps? For a small (growing) fraction of customers – Each step leaks customers away: own a compatible handset ‐> know about the app ‐> find it ‐> download it ‐> use it ‐> remember it next time – For the enterprise: custom solutions, expensive to develop, must be maintained, no in‐house expertise – For the customer: for each app must learn different user experience, possibilities, UI flows, options, capabilities • Web? – ok for desktop, ready for mobile? • Texting would be ideal with mass market reach
- 6. Texting and B2C • Build on current SMS and voice cases – alternative or enhancement or replacement • Richer content than SMS • File transfer to send or receive additional contextual info • Location, Voice notes, … • Business models understood, ecosystem is there
- 7. Market perception? • Enterprises feeling like they are losing the train, can’t benefit from the texting wave • Coca‐Cola marketing VP: two years in a row in MWC Seminar • Companies starting to integrate white‐brand messaging – Mass market reach problem, but better than nothing • Texting now identified with no revenue person to person • That’s not the whole picture. Texting for B2C/A2P/P2A business opportunity is huge (Am I preaching to the choir here?)
- 10. What is missing? • Open enablers to innovation engine – Previous examples still relying on 1‐1 engagements. • Messaging platform with mass market reach • APIs as tools so tinkerers can tinker • No comms expertise required Source: KPCB Internet Trends (http://www.kpcb.com/internet‐trends)
- 11. Can telcos help? • Already part of the existing B2C ecosystem • Already taken care of the technical details and complexity • Already assuring global interconnection and global reach • Texting for B2C in Telco‐land would be ideal
- 12. Enter RCS APIs
- 13. What is RCS anyway? • Rich Communications bring simplicity to real‐time chat, video share and file share on your mobile phone • No passwords, no registering, no new address book – it just works • For every end use case: same user experience, no change or download
- 14. Features
- 21. Key takeaways • Texting becoming preferred communication experience • Rich messaging increases the potential for B2C interaction • Services as contacts in the phonebook are the “new apps”: no install, no need to learn new thing, same UX for thousands of cases • B2C intensive companies (banks, utilities, governments) and B2C tech providers interested in exploring new channels to reach their users • Telco part of existing ecosystems, regulated, trusted by many players • Telco REST APIs are a real platform to for B2C/A2P/P2A communications
- 22. Give it a try !!! • Portal http://tadhackrcs.solaiemes.com/ • Tutorial http://youtu.be/Kw‐y7WKmBrE • Echo service example: https://github.com/solaiemes/tadhack
- 23. Geek time !!!
- 25. WebRTC? • HTML development marries communications • “Love conquers all” version: no network expertise required • Reality: don’t forge comms basics – Signalling, addressing, connectivity, … • Rich ecosystem helping there
- 26. Did I hear “between browsers”? • Not only that … but Web‐based telco end‐points • WebRTC as a bridge between Web and POTS • Implement “new voice” use cases with WebRTC‐ based APIs – accessible to traditional POTS and WebRTC endpoints • WebRTC access to POTS and “new voice”
- 28. • Best communication ubiquity will be a Web based ubiquity • But Telco‐WebRTC is not only about making telco comms ubiquitous • Use WebRTC APIs to create new services and find value added spaces • Leverage your existing services with no changes
- 29. Some examples • Home Office customized communication • Customer care use cases • Interconnecting social identities with telco identities • Enable concepts as “callable” while keeping private the phone number (e.164) • Creating “non physical second lines”, no wire, no SIM • And put to work external talent with SDK for developers
- 30. WebRTC‐Telco Gateway internetinternet WebRTC TELCO Gateway WebRTC TELCO Gateway WebRTC signalling & media Voice Core OR Voice Core OR IMSIMS SoftSwitchSoftSwitch SBCSBC UNI IMS Core or SoftSwitches supporting SIP access DO NOT need any modification POTS or enterprise Telco signalling & Media
- 31. Make developers life easy • No changes to their existing voice infrastructure • SDK • Our experience: Telco services exposed in hours. • New services deployed in days: – prepaid call‐me – casual access – interworking with OTTs, etc
- 34. Geek time !!!