Cover Image
市場調查報告書

通訊API與通訊支援應用程式:技術,市場展望,未來預測 (2016∼2020年)

Telecom APIs and Communication Enabled Apps: Technology, Market Outlook, and Forecasts 2016 - 2020

出版商 Mind Commerce 商品編碼 355495
出版日期 內容資訊 英文 295 Pages
商品交期: 最快1-2個工作天內
價格
Back to Top
通訊API與通訊支援應用程式:技術,市場展望,未來預測 (2016∼2020年) Telecom APIs and Communication Enabled Apps: Technology, Market Outlook, and Forecasts 2016 - 2020
出版日期: 2016年03月30日 內容資訊: 英文 295 Pages
簡介

通訊網路API是一面活用現有的網路基礎設施/平台,一面向通訊服務供應商 (CSP) 提供基於DaaS (「作為服務的」資料) B2B服務。舉個例子便是WebRTC,將語音·影片通訊透過Web瀏覽器,即時提供互相傳輸用的組成架構和通訊協定,API。而該服務僅需要支援WebRTC的瀏覽器 (HTML5) 。WebRTC和通訊API,對通訊電信業者和OTT應用程式來說,將成為可大大強化綜合型服務體驗的工具。

本報告提供全球通訊網路API (Application Programming Interface) 市場相關之詳細分析,提供您通訊網路API定義和功能,經營模式和實際的使用案例·最佳業務實踐,價值鏈結構,通訊業者/API供應商的產業策略,今後的技術開發·活用相關願景,市場規模趨勢預測 (今後5年份),相關技術的概要 (WebRTC等),產業相關人員應該扮演的角色等相關調查與考察。

第1章 簡介

第2章 通訊網路API概要

  • 網路API定義
  • 為何通訊電信業者,要引進通訊網路API
    • 新收益來源的需求
    • B2B服務不對稱性的經營模式
  • 通訊網路API的類別
    • Web即時通訊 (WebRTC)
    • SMS和RCS-E
    • 存在感
    • MMS
    • 地理定位
    • 付款
    • 語音/會話
    • 語音控制
    • 多媒體語音控制
    • M2M (機器間通訊)
    • SDM/ID管理
    • 用戶簡介
    • QoS
    • ID/SSO
    • 內容傳送
    • 託管UC (整合通訊)
    • 名錄
    • Number Provisioning
    • USSD
    • 對非數位財寶的收費
    • 廣告
    • 合作
    • IVR (互動語音回覆系統)/語音商店
  • 通訊網路API的經營模式
    • 二面型的經營模式
    • 對API的開發企業的明確指示
    • Web混搭
  • 明細
    • 各市場區隔的用戶數
    • 人員管理
  • 競爭上的課題
    • 削減總持有成本 (TCO)
    • 開放式API
    • 可配置性 (環境配置的可變性)
  • 使用API的應用比率
  • 通訊API的潛在收益額
    • API單體的收益額和最終產品的收益額
    • 電信業者方面對企業用通訊API的興趣
  • 通訊網路API的利用頻率:各產業
  • 通訊網路API的價值鏈
    • 通訊API的價值鏈
    • 價值鏈的發展的辦法
    • API交易收益:企業間的明細
  • 各API交易的費用
  • API交易的數量

第3章 API的聚合

  • API聚合所扮演的角色
  • 附聚合API的整體利用成本
    • 初始設置成本
    • 交易成本
    • 運作中的維修/支援
    • 透過仲介業者的專業服務
  • 聚合的API使用概況 :各類別
    • LBS的使用案例:LOC-AID
    • 聚合:2種大需求交點
    • 除了API以外類別的案例
    • 新經營模式的轉變

第4章 企業用·通訊API市場

  • DaaS (「作為服務的」資料)
    • 電信業者結構化/非結構化資料
    • DaaS的電信業者的資料管理
    • DaaS生態系統的資料聯合
  • 左右API市場的存在
    • mashape
    • Mulesoft
  • 新品種應用市場的必要性:CAM
    • 通訊支援應用程式市場 (CAM)
    • CAM市場機會與課題

第5章 通訊API支援應用程式的使用案例

  • 通訊支援應用程式的活用
    • 來自API的直接收益
    • 資料的收益化
    • 成本控制
    • 擴大利用頻率
    • 降低客戶流失 (解約率)
  • 使用上的課題
    • 安全
    • 互通性

第6章 非通訊網路API及混搭

  • 非通訊網路API
    • Twitter
    • Netflix API
    • Google Maps
    • Facebook
    • YouTube
    • Flickr
    • eBay
    • Last.fm
    • Amazon Web Services
    • Bing Maps
    • Yahoo Web Search API
    • Shopping.com
    • Salesforce.com
  • 混搭
    • BBC News on Mobile 81
    • GenSMS emailSMS
    • Foursquare
    • Amazon SNS and Nexmo
    • Triage.me
    • MappyHealth 8
    • Lunchflock
    • Mobile Time Tracking
    • Fitsquare
    • GeoSMS
    • FONFinder
    • Pound Docs
    • 140Call
    • Salesforce SMS

第7章 通訊電信業者方面的策略

  • 通訊電信業者的市場策略和定位
    • API投資的增額
    • SDM的崛起
    • 通訊API的標準化
    • 電信業者方面對API通訊的態度:美國·亞太地區·西歐
  • 全球各國的通訊電信業者的API計劃
    • AT&T Mobility
    • Verizon Wireless
    • Vodafone
    • France Telecom
    • Telefonica
  • 通訊電信業者和內部通訊API的利用
    • 內部利用的案例
    • 內部通訊API的使用案例
  • 通訊電信業者和OTT服務提供商
    • OTT供應商的應用管理許可
    • 活用API所需的創新技術,電信業者未能獨自支援
  • 通訊電信業者和附加價值服務 (VAS)
    • VAS所扮演的角色和重要性
    • 電信業者通訊支援VAS的案例
    • VAS相關通訊電信業者的課題與機會

第8章 API支援應用程式開發企業的策略

  • 對開發企業 (開發人員) 來說重要的資產
  • 促進API推出數量的增加
  • 沿著電信業者方面的計劃之業務發展
  • 開發企業方面的偏好:是Google,還是通訊電信業者

第9章 通訊API供應商的策略

  • 價值鏈內地的啟用定位
  • 擺脫Box/產品供應商的策略
  • 通訊API企業與解決方案
    • Alcatel Lucent
    • UnboundID
    • Twilio
    • LOC-AID
    • Placecast
    • Samsung
    • AT&T Mobility
    • Apigee
    • 2600 Hz
    • Callfire
    • Plivo
    • Tropo (現在Cisco)
    • Urban Airship
    • Voxeo (現在Aspect Software)
    • TeleStax
    • Intel
    • 其他公司的差異化

第10章 市場分析與預測

  • 通訊網路API的收益額 (今後5年份)
  • 通訊網路API的收益額:API的各類別 (今後5年份)
    • 通訊API的收益額
    • 定位服務 (LBS) API的收益額
    • 用戶資料管理 (SDM) API的收益額
    • 付款API的收益額
    • IoT API的收益額
    • 其他API的收益額
  • 通訊網路API的收益額:各地區 (今後5年份)
    • 亞太地區
    • 東歐
    • 中南美
    • 中東·非洲
    • 北美
    • 西歐

第11章 關係到API市場今後的成長,技術·市場推動因素

  • SOA (服務導向架構)
  • SDN (軟體定義網路)
  • 虛擬化
    • NVF (網路功能虛擬化)
    • 網路功能以外的虛擬化
  • IoT (物聯網)
    • IoT定義
    • IoT技術
    • IoT應用
    • IoT解決方案
    • IoT和DaaS和API (通訊企業·企業)

第12章 專家的見解:TeleStax

第13章 專家的見解:Twilio

第14章 專家的見解:Point.io

第15章 專家的見解:Nexmo

第16章 附錄

圖表一覽

目錄

Telecom Network APIs capitalize on existing network infrastructure and platforms to facilitate many new business opportunities for global Communication Service Providers (CSP) to offer Business-to-Business (B2B) services in a Data as a Service (DaaS) basis. One leading beneficiary is WebRTC, which provides a framework, protocols, and API that facilitates real-time interactive voice, video and data in via a Web browser. The requirement is only a WebRTC-enabled browser (HTML5). Web Real-time Communications (WebRTC) is one tool in the toolkit along with Telecom APIs and integration with carrier and OTT apps for a greatly enhanced and blended service experience.

Telecom APIs and Communication Enabled Apps: Technology, Market Outlook, and Forecasts 2016 - 2020 provides an in-depth assessment of the global Telecom Network API market, including business models, business case, best practices, value chain analysis, operator and vendor strategies, vision for the future of telecom data, and a quantitative assessment of the industry from 2016 to 2020. This research also evaluates WebRTC technology, evolving ecosystem, 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.

The report also assesses WebRTC features/functionality, use cases, and adoption expectations for enterprise and consumers. The report covers the WebRTC solution landscape with vendor analysis focused on business models for each company/solution. The report also forecasts global and regional WebRTC market size. 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 in globally and regionally from 2016 to 2020.

Target Audience:

  • API Aggregators
  • Investment Firms
  • Application Developers
  • Mobile Device Vendors
  • Mobile Network Carriers
  • Service Bureau Companies
  • Wireless Infrastructure Vendors
  • Telecom Managed Service Providers
  • Major enterprise and businesses of all types

Table of Contents

1 Introduction

  • 1.1 Executive Summary
  • 1.2 Topics Covered
  • 1.3 Key Findings
  • 1.4 Target Audience
  • 1.5 Companies Mentioned

2 Telecom Network API Overview

  • 2.1 Defining Network APIs
  • 2.2 Why Carriers are Adopting Telecom Network APIs
    • 2.2.1 Need for New Revenue Sources
    • 2.2.2 B2B Services and Asymmetric Business Models
  • 2.3 Telecom Network API Categories
    • 2.3.1 Web Real-time Communications (WebRTC)
    • 2.3.2 SMS and RCS-E
    • 2.3.3 Presence
    • 2.3.4 MMS
    • 2.3.5 Location
    • 2.3.6 Payments
    • 2.3.7 Voice/Speech
    • 2.3.8 Voice Control
    • 2.3.9 Multimedia Voice Control
    • 2.3.10 M2M
    • 2.3.11 SDM/Identity Management
    • 2.3.12 Subscriber Profile
    • 2.3.13 QoS
    • 2.3.14 ID/SSO
    • 2.3.15 Content Delivery
    • 2.3.16 Hosted UC
    • 2.3.17 Directory
    • 2.3.18 Number Provisioning
    • 2.3.19 USSD
    • 2.3.20 Billing of Non-Digital Goods
    • 2.3.21 Advertising
    • 2.3.22 Collaboration
    • 2.3.23 IVR/Voice Store
  • 2.4 Telecom Network API Business Models
    • 2.4.1 Two-Sided Business Model
    • 2.4.2 Exposing APIs to Developers
    • 2.4.3 Web Mash-ups
  • 2.5 Segmentation
    • 2.5.1 Users by Segment
    • 2.5.2 Workforce Management
  • 2.6 Competitive Issues
    • 2.6.1 Reduced TCO
    • 2.6.2 Open APIs
    • 2.6.3 Configurability
  • 2.7 Percentage of Applications that use APIs
  • 2.8 Telecom API Revenue Potential
    • 2.8.1 Standalone API Revenue vs. Finished Goods Revenue
    • 2.8.2 Telecom API-enabled Mobile VAS Applications
    • 2.8.3 Carrier Focus on Telecom API's for the Enterprise
  • 2.9 Telecom Network API Usage by Industry Segment
  • 2.10 Telecom Network API Value Chain
    • 2.10.1 Telecom API Value Chain
    • 2.10.2 How the Value Chain Evolve
    • 2.10.3 API Transaction Value Split among Players
  • 2.11 Cost for Different API Transactions
  • 2.12 Volume of API Transactions

3 API Aggregation

  • 3.1 The Role of API Aggregators
  • 3.2 Total Cost Usage for APIs with Aggregators
    • 3.2.1 Start-up Costs
    • 3.2.2 Transaction Costs
    • 3.2.3 Ongoing Maintenance/Support
    • 3.2.4 Professional Services by Intermediaries
  • 3.3 Aggregator API Usage by Category
    • 3.3.1 An LBS Case Study: LOC-AID
    • 3.3.2 Aggregation: Intersection of Two Big Needs
    • 3.3.3 The Case for Other API Categories
    • 3.3.4 Moving Towards New Business Models

4 Enterprise and Telecom API Marketplace

  • 4.1 Data as a Service (DaaS)
    • 4.1.1 Carrier Structured and Unstructured Data
    • 4.1.2 Carrier Data Management in DaaS
    • 4.1.3 Data Federation in the DaaS Ecosystem
  • 4.2 API Market Makers 6
    • 4.2.1 mashape
    • 4.2.2 Mulesoft
  • 4.3 Need for a New Type of Application Marketplace: CAM
    • 4.3.1 Communications-enabled App Marketplace (CAM)
    • 4.3.2 CAM Market Opportunities and Challenges

5 Telecom API Enabled App Use Cases

  • 5.1 Monetization of Communications-enabled Apps
    • 5.1.1 Direct API Revenue
    • 5.1.2 Data Monetization
    • 5.1.3 Cost Savings
    • 5.1.4 Higher Usage
    • 5.1.5 Churn Reduction
  • 5.2 Use Case Issues
    • 5.2.1 Security
    • 5.2.2 Interoperability

6 Non-Telecom Network APIs and Mash-ups

  • 6.1 Non-Telecom Network APIs
    • 6.1.1 Twitter
    • 6.1.2 Netflix API
    • 6.1.3 Google Maps
    • 6.1.4 Facebook
    • 6.1.5 YouTube
    • 6.1.6 Flickr
    • 6.1.7 eBay
    • 6.1.8 Last.fm
    • 6.1.9 Amazon Web Services
    • 6.1.10 Bing Maps
    • 6.1.11 Yahoo Web Search API
    • 6.1.12 Shopping.com
    • 6.1.13 Salesforce.com
  • 6.2 Mash-ups
    • 6.2.1 BBC News on Mobile 81
    • 6.2.2 GenSMS emailSMS
    • 6.2.3 Foursquare
    • 6.2.4 Amazon SNS and Nexmo
    • 6.2.5 Triage.me
    • 6.2.6 MappyHealth 8
    • 6.2.7 Lunchflock
    • 6.2.8 Mobile Time Tracking
    • 6.2.9 Fitsquare
    • 6.2.10 GeoSMS
    • 6.2.11 FONFinder
    • 6.2.12 Pound Docs
    • 6.2.13 140Call
    • 6.2.14 Salesforce SMS

7 Carrier Strategies

  • 7.1 Carrier Market Strategy and Positioning
    • 7.1.1 Increasing API Investments
    • 7.1.2 The Rise of SDM
    • 7.1.3 Telecom API Standardization
    • 7.1.4 Carrier Attitudes towards APIs: U.S vs. Asia Pacific and Western Europe
  • 7.2 Carrier API Programs Worldwide
    • 7.2.1 AT&T Mobility
    • 7.2.2 Verizon Wireless
    • 7.2.3 Vodafone
    • 7.2.4 France Telecom
    • 7.2.5 Telefonica
  • 7.3 Carriers and Internal Telecom API Usage
    • 7.3.1 The Case for Internal Usage
    • 7.3.2 Internal Telecom API Use Cases
  • 7.4 Carriers and OTT Service Providers
    • 7.4.1 Allowing OTT Providers to Manage Applications
    • 7.4.2 Carriers Lack the Innovative Skills to Capitalize on APIs Alone
  • 7.5 Carriers and Value-added Services (VAS)
    • 7.5.1 The Role and Importance of VAS
    • 7.5.2 The Case for Carrier Communication-enabled VAS
    • 7.5.3 Challenges and Opportunities for Carriers in VAS

8 API enabled App Developer Strategies

  • 8.1 A Critical Asset to Developers
  • 8.2 Stimulating the Growth of API Releases
  • 8.3 Working alongside Carrier Programs
  • 8.4 Developer Preferences: Google vs Carriers

9 Telecom API Vendor Strategies

  • 9.1 Positioning as Enablers in the Value Chain
  • 9.2 Moving Away from a Box/Product Supplier Strategy
  • 9.3 Telecom API Companies and Solutions
    • 9.3.1 Alcatel Lucent
    • 9.3.2 UnboundID
    • 9.3.3 Twilio
    • 9.3.4 LOC-AID
    • 9.3.5 Placecast
    • 9.3.6 Samsung
    • 9.3.7 AT&T Mobility
    • 9.3.8 Apigee
    • 9.3.9 2600 Hz
    • 9.3.10 Callfire
    • 9.3.11 Plivo
    • 9.3.12 Tropo (now Cisco)
    • 9.3.13 Urban Airship
    • 9.3.14 Voxeo (now Aspect Software)
    • 9.3.15 TeleStax
    • 9.3.16 Intel
    • 9.3.17 Competitive Differentiation

10 Market Analysis and Forecasts 127

  • 10.1 Telecom Network API Revenue 2016 - 2020
  • 10.2 Telecom Network APIs Revenue by API Category 2016 - 2020
    • 10.2.1 Messaging API Revenues
    • 10.2.2 LBS API Revenues
    • 10.2.3 SDM API Revenues
    • 10.2.4 Payment API Revenues
    • 10.2.5 Internet of Things (IoT) API Revenues
    • 10.2.6 Other API Revenues
  • 10.3 Telecom API Revenue by Region 2016 - 2020
    • 10.3.1 Asia Pacific
    • 10.3.2 Eastern Europe
    • 10.3.3 Latin & Central America
    • 10.3.4 Middle East & Africa
    • 10.3.5 North America
    • 10.3.6 Western Europe

11 Technology and Market Drivers for Future API Market Growth

  • 11.1 Service Oriented Architecture (SOA)
  • 11.2 Software Defined Networks (SDN)
  • 11.3 Virtualization
    • 11.3.1 Network Function Virtualization (NFV)
    • 11.3.2 Virtualization beyond Network Functions
  • 11.4 The Internet of Things (IoT)
    • 11.4.1 IoT Definition
    • 11.4.2 IoT Technologies
    • 11.4.3 IoT Applications
    • 11.4.4 IoT Solutions
    • 11.4.5 IoT, DaaS, and APIs (Telecom and Enterprise)

12 Expert Opinion: TeleStax

13 Expert Opinion: Twilio

14 Expert Opinion: Point.io

15 Expert Opinion: Nexmo

16 Appendix

  • 16.1 Research Methodology
  • 16.2 Telecom API Definitions
  • 16.3 More on Telecom APIs and DaaS
    • 16.3.1 Tiered Data Focus
    • 16.3.2 Value-based Pricing
    • 16.3.3 Open Development Environment 2
    • 16.3.4 Specific Strategies
      • 16.3.4.1 Service Ecosystem and Platforms
      • 16.3.4.2 Bringing to Together Multiple Sources for Mash-ups
      • 16.3.4.3 Developing Value-added Services (VAS) as Proof Points
      • 16.3.4.4 Open Access to all Entities including Competitors
      • 16.3.4.5 Prepare for Big Opportunities with the Internet of Things (IoT)

Figures

  • Figure 1: Wireless Carrier Assets
  • Figure 2: Telecom API: Standalone vs. Finished Services
  • Figure 3: RCS and Telecom API Integration 36
  • Figure 4: RCS Revenue Forecast
  • Figure 5: Business vs. Consumer Telecom API Focus
  • Figure 6: Enterprise Dashboard
  • Figure 7: Enterprise Dashboard App Example
  • Figure 8: Telecom Network API Value Chain
  • Figure 9: Value Split among Aggregators, Carriers and Enterprise for API Transactions: 2012 - 2019
  • Figure 10: API Transaction Costs 2012 - 2019
  • Figure 11: Volume of API Transactions for a Tier 1 Carrier 2016 - 2020
  • Figure 12: Cloud Services and APIs
  • Figure 13: GSMA OneAPI: Benefits to Stakeholders
  • Figure 14: AT&T Wireless API Catalog
  • Figure 15: Verizon Wireless API Program
  • Figure 16: France Telecom (Orange) APIs
  • Figure 17: Telefonica APIs
  • Figure 18: Carrier Internal Use of Telecom APIs
  • Figure 19: UnboundID's Portfolio of Services
  • Figure 20: Twilio's Portfolio of Services
  • Figure 21: LOC-AID Exchange Server Architecture
  • Figure 22: Placecast's ShopAlerts Solution
  • Figure 23: Apigee Portfolio of Services
  • Figure 24: Telecom API Revenue 2016 - 2020
  • Figure 25: Telecom API Revenue by API Category 2016 - 2020
  • Figure 26: Messaging APIs Revenue 2016 - 2020
  • Figure 27: LBS APIs Revenue 2016 - 2020
  • Figure 28: SDM APIs Revenue 2016 - 2020
  • Figure 29: Payment APIs Revenue 2016 - 2020
  • Figure 30: IoT API Revenue 2016 - 2020
  • Figure 31: APIs Revenue for Other Categories 2016 - 2020
  • Figure 32: Telecom API Revenue by Region 2016 - 2020
  • Figure 33: Telecom API Revenue Asia Pacific 2016 - 2020
  • Figure 34: Telecom API Revenue Eastern Europe 2016 - 2020
  • Figure 35: Telecom API Revenue Latin & Central America 2016 - 2020
  • Figure 36: Telecom API Revenue Middle East & Africa 2016 - 2020
  • Figure 37: Telecom API Revenue North America 2016 - 2020
  • Figure 38: Telecom API Revenue (USD Billions) Western Europe 2016 - 2020
  • Figure 39: Services Oriented Architecture
  • Figure 40: Growth of Connected Devices
  • Figure 41: IoT and Telecom API Topology
  • Figure 42: Telestax App Store Funnel
  • Figure 43: On-Premise vs. Twilio
  • Figure 44: Point.io and API Ecosystem
  • Figure 45: Different Data Types and Functions in DaaS
  • Figure 46: Ecosystem and Platform Model
  • Figure 47: Telecom API and Internet of Things Mediation
  • Figure 48: DaaS and IoT Mediation for Smartgrid
Back to Top