Overview:
This report evaluates WebRTC technology, evolving ecosystems, solutions, and applications. It also addresses the role of value chain partners, WebRTC APIs, enterprise applications, telecom operators, and other CSPs within the evolving ecosystem.
This report also assesses WebRTC features/functionality, use cases, and adoption expectations for enterprises and consumers. The report covers the WebRTC solution landscape with vendor analysis focused on business models for each company/solution.
Forecasting provides revenue by categories including solution, service (Implementation, Integration, Consulting, and Maintenance), industry verticals, deployment models, and application. In addition, the report contains forecasts for WebRTC devices and users globally and regionally from 2023 to 2028.
Select Report Findings:
- WebRTC will be the RTC platform of choice with the introduction of 5G and the expansion of OTT offerings
- Cloud-based Communications, Applications, Content, and Commerce (CACC) will benefit greatly from WebRTC
- WebRTC is a key component of an overall CACC strategy for CSPs as they seek to retain customers and grow revenues
- CSPs are stumbling with the implementation of RCS, making WebRTC deployment critical as well as partnering with various third parties
- While WebRTC is table-stakes for CSPs, they also have revenue potential from back-end integration with their most important customers: enterprise
- Telecom APIs are a key component to overall WebRTC success for the entire value chain as well as leveraging telecom data in a cloud-based DaaS business model
- WebRTC supported services will usher into the ICT ecosystem a next-generation services ecosystem of communications, applications, content, and commerce
Web Real-time Communications (WebRTC) provides a framework, protocols, and API that facilitates real-time interactive voice, video, and data via a Web browser. The requirement is only a WebRTC-enabled browser (HTML5).
Because WebRTC requires no plug-ins and works natively, it can be implemented and operated very easily on PCs, laptops, TVs, tablets, smartphones, and wearable devices. The business drivers for WebRTC are many and varied as there are benefits for all industry constituents including:
- End-users: New User Experience, Service Creation/Service Mash-up
- Developers: Ease developer burden with a single platform.
- Communication Service Providers: Expansion of market/customers
WebRTC is being applied to all modern and native browsers for virtually all major platforms to support sharing of voice, video, and generic data between peers, allowing developers to create compelling video-and-voice communication solutions. There are numerous use cases of WebRTC, the technology behind certain industry-leading communications and collaboration solutions including Discord, Facebook Messenger, and Google Meet/Hangout.
Use cases range from advanced video calling apps (such as Skype, Duo, and WhatsApp) and screen sharing to the more basic web apps that can use your microphone or camera. Major drivers for the vendor, service provider, and developer adoption are ease of implementation, compatibility with browsers and OS, and free open-source with no need for third-party applications.
Companies in Report:
- AT&T
- Avaya
- CafeX
- Cisco Systems
- Dialogic
- Ericsson
- Google
- Huawei Technologies
- IBM Corporation
- Mitel Networks
|
- Nokia
- Oracle
- Plivo
- QUOBIS
- Ribbon Communications
- Sonus (Ribbon Communications)
- Temasys
- TokBox Telefonica
- Twilio
|
Table of Contents
1.0. Executive Summary
2.0. WebRTC Technology and Market Overview
- 2.1. Understanding WebRTC
- 2.1.1. WebRTC Features
- 2.1.2. WebRTC Advantages
- 2.1.3. Peer to Peer vs. Browser to Browser Communication
- 2.1.4. Click-to-Call
- 2.2. Evolution of WebRTC
- 2.3. WebRTC Solution Market
- 2.4. WebRTC Market Factors
- 2.4.1. Growth Drivers
- 2.4.2. Market Limitations
- 2.4.3. Market Opportunities
- 2.5. WebRTC Ecosystem / Value Chain
- 2.5.1. Vendors
- 2.5.2. Products
- 2.5.3. Solutions and Services
- 2.5.4. Applications
- 2.5.5. Delivery Platforms
- 2.5.6. End Users
3.0. WebRTC Taxonomy
- 3.1. WebRTC Technology
- 3.1.1. Native Apps vs. WebRTC
- 3.1.2. HTML5
- 3.1.3. WebRTC and Expansion of Media/Data usage via LTE
- 3.1.4. LTE, RCS, and WebRTC
- 3.1.5. Carrier WiFi and WebRTC
- 3.1.6. Cloud Communication and WebRTC
- 3.1.7. Open Source API and WebRTC
- 3.2. WebRTC Architecture
- 3.3. WebRTC Functionality
- 3.3.1. Voice Calling
- 3.3.2. Real Time Messaging
- 3.4. WebRTC Enterprise Application
- 3.4.1. Customer Facing Enterprise
- 3.4.2. In-House Licenses Development
- 3.4.3. Application and Security
- 3.5. WebRTC API
- 3.5.1. Session Description Protocol
- 3.5.2. Open Real-time Communications API
- 3.5.3. WebRTC Security
- 3.5.4. Chrome
- 3.5.5. Firefox
- 3.5.6. Media Stream (getUserData)
- 3.5.7. Hookflash
- 3.5.8. MediaStream API
- 3.5.9. RTCDataChannel API
- 3.6. Cloud RTC Platform
4.0. WebRTC Application Cases
- 4.1. Stages of Creation of WebRTC Application
- 4.1.1. Getting Started
- 4.1.2. Creating Video Audio Calling
- 4.1.3. Using Text
- 4.1.4. File Sharing
- 4.2. WebRTC Applications
- 4.2.1. Use of WebRTC in E-learning
- 4.2.2. WebRTC in Corporate Meetings
- 4.2.3. WebRTC and HTML5 Developments
- 4.2.3.1. Web Applications
- 4.2.3.2. Off-line Applications
- 4.2.4. WebRTC for the Mobile Applications
- 4.3. WebRTC Use Cases
- 4.3.1. Customer Care
- 4.3.2. Premium Customer Services
- 4.3.3. Customer Willingness to Pay for such Premium Services
- 4.4. Economics of WebRTC
5.0. WebRTC Vendor Landscape
- 5.1. Overall Competitive Landscape
- 5.1.1. Platform Vendors
- 5.1.2. Voice Solution Vendors
- 5.1.3. Video Solution Vendors
- 5.1.4. Conference Solution Providers
- 5.1.5. Telecom WebRTC Carrier
- 5.1.6. On-Premise Vendors
- 5.1.7. OTT Communication Providers
- 5.1.8. Bulk SMS Vendors
- 5.1.9. Learning and Development Vendors
- 5.2. Nokia
- 5.2.1. Overview
- 5.2.2. Analysis
- 5.3. AT&T
- 5.3.1. Overview
- 5.3.2. Analysis
- 5.4. Avaya
- 5.4.1. Overview
- 5.4.2. Analysis
- 5.5. CafeX
- 5.5.1. Overview
- 5.5.2. Analysis
- 5.6. Cisco Systems
- 5.6.1. Overview
- 5.6.2. Analysis
- 5.7. Dialogic
- 5.7.1. Overview
- 5.7.2. SWOT Analysis
- 5.8. Ericsson
- 5.8.1. Overview
- 5.8.2. Analysis
- 5.9. Ribbon Communications
- 5.9.1. Overview
- 5.9.2. Analysis
- 5.10. Google
- 5.10.1. Overview
- 5.10.2. Analysis
- 5.11. Huawei Technologies
- 5.11.1. Overview
- 5.11.2. Analysis
- 5.12. IBM Corporation
- 5.12.1. Overview
- 5.12.2. SWOT Analysis
- 5.13. Mitel Networks
- 5.13.1. Overview
- 5.13.2. Analysis
- 5.14. Oracle
- 5.14.1. Overview
- 5.14.2. Analysis
- 5.15. Plivo
- 5.15.1. Overview
- 5.15.2. Analysis
- 5.16. QUOBIS
- 5.16.1. Overview
- 5.16.2. SWOT Analysis
- 5.17. Sonus (Ribbon Communications)
- 5.17.1. Overview
- 5.17.2. Analysis
- 5.18. Temasys
- 5.18.1. Overview
- 5.18.2. Analysis
- 5.19. TokBox Telefonica
- 5.19.1. Overview
- 5.19.2. Analysis
- 5.20. Twilio
- 5.20.1. Overview
- 5.20.2. Analysis
6.0. Future of WebRTC
- 6.1. Beyond Voice/Video and Browsers
- 6.2. Hybrid P2P and Server-based CDN
- 6.3. Emerging WebRTC Issues and Opportunities
- 6.4. WebRTC Implementation Status
- 6.5. WebRTC Applications in Machine Learning and 5G
- 6.6. WebRTC vs. RCS
7.0. WEBRTC Market Analysis and Forecasts 2021 to 2028
- 7.1. Global WEBRTC Markets 2023-2028
- 7.2. Web Real-time Communications Components 2023-2028
- 7.3. Web Real-time Communications Software Applications 2023-2028
- 7.4. Web Real-time Communications Software Enterprise Applications 2023-2028
- 7.5. Web Real-time Communications Software IoT Applications 2023-2028
- 7.5.1. Web Real-time Communications Software Smart Home Applications 2023-2028
- 7.5.2. Web Real-time Communications Software Smart Healthcare Applications 2023-2028
- 7.5.3. Web Real-time Communications Software Smart Industry Applications 2023-2028
- 7.6. Web Real-time Communication Software for Social Media Applications 2023-2028
- 7.7. Web Real-time Communication Software Deployment 2023-2028
- 7.8. Web Real-time Communication Software by Devices 2023-2028
- 7.9. Web Real-time Communication Software by Services 2023-2028
- 7.9.1. Web Real-time Communication Software by Professional Services 2023-2028
- 7.9.2. Web Real-time Communication Software by Managed Services 2023-2028
- 7.10. Web Real-time Communication Software by Industry 2023-2028
- 7.11. Web Real-time Communication Software by Region 2023-2028
8.0. Summary and Recommendations
- 8.1. Communication Service Providers
- 8.2. Social Media Companies
- 8.3. Content Providers
- 8.4. Application Developers
- 8.5. Commerce Providers
- 8.6. Infrastructure Providers
- 8.7. Device Manufacturers
9.0. Appendix
- 9.1. Telecom Application Programming Interfaces
- 9.1.1. Role and Importance of Telecom APIs
- 9.1.2. Business Drivers for CSPs to Leverage APIs
- 9.1.2.1. Need for New Revenue Sources
- 9.1.2.2. Need for Collaboration with Development Community
- 9.1.2.3. B2B Services and Asymmetric Business Models
- 9.1.2.4. Emerging Need for IoT Mediation
- 9.1.3. Telecom API Categories
- 9.1.3.1. Access Management
- 9.1.3.2. Advertising and Marketing
- 9.1.3.3. Billing of Non-Digital Goods
- 9.1.3.4. Content Delivery
- 9.1.3.5. Directory and Registry Management
- 9.1.3.6. Enterprise Collaboration
- 9.1.3.7. IVR/Voice Solutions
- 9.1.3.8. Location Determination
- 9.1.3.9. M2M and Internet of Things
- 9.1.3.10. Messaging and other Non-Voice Communications
- 9.1.3.10.1. Text Messaging
- 9.1.3.10.2. Multimedia Messaging
- 9.1.3.11. Number Management
- 9.1.3.12. Payments including Purchaser Present Verification
- 9.1.3.13. Presence Detection
- 9.1.3.14. Real-time Communications and WebRTC
- 9.1.3.15. Subscriber Identity Management
- 9.1.3.16. Subscriber Profile Management
- 9.1.3.17. Quality of Service Management
- 9.1.3.18. Unified Communications and UCaaS
- 9.1.3.19. Unstructured Supplementary Service Data
- 9.1.3.20. Unwanted Call Management and Robo Calls
- 9.1.3.21. Voice/Speech
- 9.1.4. Telecom API Business Models
- 9.1.4.1. Three Business Model Types
- 9.1.4.1.1. Model One
- 9.1.4.1.2. Model Two
- 9.1.4.1.3. Model Three
- 9.1.4.2. The Asymmetric Business Model
- 9.1.4.3. Exposing APIs to Developers
- 9.1.4.4. Web Mash-ups
- 9.1.5. Segmentation
- 9.1.5.1. Users by Segment
- 9.1.5.2. Workforce Management
- 9.1.6. Competitive Issues
- 9.1.6.1. Reduced Total Cost of Ownership
- 9.1.6.2. Open APIs
- 9.1.6.3. Configurability and Customization
- 9.1.7. Applications that use APIs
- 9.1.8. Telecom API Revenue Potential
- 9.1.8.1. Standalone API Revenue vs. API enabled Revenue
- 9.1.8.2. Telecom API-enabled Mobile VAS Applications
- 9.1.8.3. Carrier Focus on Telecom API's for the Enterprise
- 9.1.9. Telecom API Usage by Industry Segment
- 9.1.10. Telecom API Value Chain
- 9.1.10.1. Telecom API Value Chain
- 9.1.10.2. How the Value Chain Evolves
- 9.1.10.3. API Transaction Value Split among Players
- 9.1.11. API Transaction Cost by Type
- 9.1.12. Volume of API Transactions