Cover Image
市場調查報告書

通訊API的全球市場:展望與未來預測 (2016∼2020年)

Telecom API Market Outlook and Forecasts 2016 - 2021

出版商 Mind Commerce 商品編碼 364538
出版日期 內容資訊 英文 167 Pages
商品交期: 最快1-2個工作天內
價格
Back to Top
通訊API的全球市場:展望與未來預測 (2016∼2020年) Telecom API Market Outlook and Forecasts 2016 - 2021
出版日期: 2016年07月26日 內容資訊: 英文 167 Pages
簡介

全球通訊API (Application Programming Interface)的市場規模,推算到2021年將達到1836億美元。但通訊電信業者卻尚不能說是充分活用了市場機會,一般認為反而是OTT供應商持續扮演著推動市場發展的角色。通話區域功能等潛力領域,將是今後主要的開發領域。

本報告提供全球通訊API市場相關之詳細分析,提供您通訊API定義·功能,及經營模式和實際的使用案例·最佳業務實踐,價值鏈結構,通訊業者/API供應商的產業策略,今後的技術開發·利用的應有的樣子,市場規模趨勢預測 (今後5年份),相關技術的概要 (SDN·虛擬化·IoT等),產業相關人員應該取策略等相關之調查與考察。

第1章 簡介

第2章 通訊API概要

  • 網路API (Application Programming Interface)的定義
  • API的活用:對通訊服務供應商 (CSP) 而言的商務推動因素
    • 新收益來源的必要性
    • B2B服務和不對稱的經營模式
  • 通訊網路API的類別
    • Web即時通訊 (WebRTC)
    • SMS和RCS-E
    • 存在感
    • MMS
    • 地理定位
    • 付款
    • 語音/會話
    • 語音控制
    • 多媒體語音控制
    • M2M (機器間通訊)
    • SDM/ID管理
    • 用戶簡介
    • QoS
    • ID/SSO
    • 內容傳送
    • 託管UC (整合通訊)
    • 名錄
    • Number Provisioning
    • USSD
    • 非數位財的收費
    • 廣告
    • 合作
    • IVR (互動語音回覆系統)/語音商店
  • 通訊API的經營模式
    • 3種經營模式
    • 不對稱的經營模式
    • 對API開發商的開放
    • Web混搭
  • 明細
    • 各市場區隔的用戶數
    • 人員管理
  • 市場競爭上的課題
    • 削減總持有成本 (TCO)
    • 開放式API
    • 可配置性 (環境配置的可變更性)
  • 使用API的應用
  • 通訊API的潛在的收益
    • API單體的收益額和,最終產品的收益額
    • 通訊API支援行動VAS (附加價值服務) 應用
    • 通訊電信業者對企業用通訊API的關心
  • 通訊API的使用概況 :各產業
  • 通訊API的價值鏈
  • API交易的費用:各類型
  • API交易的規模

第3章 API聚合

  • API整合業者所扮演的角色
  • API整合業者的整體運用成本
    • 初始設置成本
    • 交易成本
    • 現行設備的整備·支援
    • 中間業者的專門服務
  • 整合業者API的使用概況 :各類別
    • API整合業者:案例研究
    • 聚合:2個大需求交點
    • 其他API類別的案例
    • 新經營模式的轉變

第4章 通訊API的市場

  • DaaS (「作為服務的」資料管理)
    • 電信業者結構化/非結構化資料
    • DaaS的電信業者的資料管理
    • DaaS生態系統的資料聯合
  • API市場製造原
    • mashape
    • Mulesoft
  • 新種類的應用市場
    • 通訊支援應用程式 (CAM) 市場
    • CAM市場機會與課題

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

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

第6章 網路業者方面的通訊API策略

  • 通訊電信業者的市場策略和定位
    • API投資額的一定化
    • 電信業者·API·OTT
    • 用戶資料和API的活用
    • 通訊API的規格
    • 通訊API和企業
  • 全球各國的通訊電信業者的API計劃
    • AT&T Mobility
    • Verizon Wireless
    • Vodafone
    • France Telecom
    • Telefonica
  • 通訊電信業者和內部通訊API的利用
    • 內部利用的案例
    • 內部通訊API的使用案例
  • 通訊電信業者和OTT服務供應商
    • 對OTT供應商的應用管理的許可
    • 活用API的創新技術:電信業者無法單獨配合
  • 通訊電信業者和附加價值服務 (VAS)
    • VAS所扮演的角色和重要性
    • 電信業者通訊支援VAS的案例
    • VAS相關通訊電信業者的課題與機會

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

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

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

  • 價值鏈內部啟用的定位
  • 擺脫Box/Product供應商的策略

第9章 市場分析與預測

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

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

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

第11章 附錄

圖表一覽

目錄

Overview:

Telecom APIs enable a variety of new and unique business models, including carrier branded application stores, web mash-ups, two sided business models, and developer communities. Network operators leverage APIs to derive wholesale transaction revenue as well as communication-enabled application revenue.

Over-the-Top service providers and other third-parties continue to enjoy the most benefits from Telecom APIs. However, enterprise is gaining fast on OTT providers as they begin to understand how to leverage their own communications data for improved products, services, and customer experience.

Telecom APIs continue to present new attractive opportunities for network operators and service bureau providers such as Do Not Call Registry compliance and Unwanted Call blocking services. Certain technology development and adoption trends will continue to drive the long-term future of Telecom APIs including Service Oriented Architecture (SOA), Virtualization, Software Defined Networks (SDN), and the Internet of Things (IoT).

Telecom API Market Outlook and Forecasts 2016 - 2021 provides an in-depth assessment of the global Telco APIs market, including business models, value chain analysis, operator strategies and a quantitative assessment of the industry from 2016 to 2021. All purchases of Mind Commerce reports includes time with an expert analyst who will help you link key findings in the report to the business issues you're addressing. This needs to be used within three months of purchasing the report.

Key Findings:

  • Telecom API revenue is forecast to reach $183.6 billion globally by 2021
  • Carriers continue to miss opportunities for Telecom APIs in Internet of Things
  • Unwanted Call blocking a developing area for carriers to leverage Telecom APIs
  • OTT providers continue to lead the way in terms of wholesale revenue for carriers
  • Enterprise to represent an important customer base as they leverage data their own data

Target Audience:

  • Telecom API providers
  • Application developers
  • Data services companies
  • Mobile network operators
  • Integrated ICT service providers
  • Enterprise companies of all types

Table of Contents

1. Introduction

  • 1.1. Executive Summary
  • 1.2. Topics Covered
  • 1.3. Key Findings
  • 1.4. Target Audience

2. Telecom API Overview

  • 2.1. Defining Network APIs
  • 2.2. Business Drivers for CSPs to Leverage APIs
    • 2.2.1. Need for New Revenue Sources
    • 2.2.2. B2B Services and Asymmetric Business Models
  • 2.3. Telecom API Categories
    • 2.3.1. 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 API Business Models
    • 2.4.1. Three Business Model Types
      • 2.4.1.1. Model One
      • 2.4.1.2. Model Two
      • 2.4.1.3. Model Three
    • 2.4.2. The Asymmetric Business Model
    • 2.4.3. Exposing APIs to Developers
    • 2.4.4. 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. Applications that use APIs
  • 2.8. Telecom API Revenue Potential
    • 2.8.1. Standalone API Revenue vs. API enabled 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 API Usage by Industry Segment
  • 2.10. Telecom 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. API Transaction Cost by Type
  • 2.12. Volume of API Transactions

3. API Aggregation

  • 3.1. Role of API Aggregators
  • 3.2. Total Cost of Operation with API 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. API Aggregator Case Study
    • 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. 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
    • 4.2.1. mashape
    • 4.2.2. Mulesoft
  • 4.3. New Type of Application Marketplace
    • 4.3.1. Communications-enabled App Marketplace
    • 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. Network Operator Telecom API Strategies

  • 6.1. Carrier Market Strategy and Positioning
    • 6.1.1. API Investment Stabilization
    • 6.1.2. Carriers, APIs, and OTT
    • 6.1.3. Leveraging Subscriber Data and APIs
    • 6.1.4. Telecom API Standards
    • 6.1.5. Telecom APIs and Enterprise
  • 6.2. Global Network Operator API Programs
    • 6.2.1. AT&T Mobility
    • 6.2.2. Verizon Wireless
    • 6.2.3. Vodafone
    • 6.2.4. France Telecom
    • 6.2.5. Telefonica
  • 6.3. Carriers and Internal Telecom API Usage
    • 6.3.1. The Case for Internal Usage
    • 6.3.2. Internal Telecom API Use Cases
  • 6.4. Carriers and OTT Service Providers
    • 6.4.1. Allowing OTT Providers to Manage Applications
    • 6.4.2. Carriers Lack the Innovative Skills to Capitalize on APIs Alone
  • 6.5. Carriers and Value-added Services
    • 6.5.1. Role and Importance of VAS
    • 6.5.2. The Case for Carrier Communication-enabled VAS
    • 6.5.3. Challenges and Opportunities for Carriers in VAS

7. API enabled App Developer Strategies

  • 7.1. A Critical Asset to Developers
  • 7.2. Stimulating the Growth of API Releases
  • 7.3. Working alongside Carrier Programs
  • 7.4. Developer Preferences: Google vs Carriers

8. Telecom API Vendor Strategies

  • 8.1. Positioning as Enablers in the Value Chain
  • 8.2. Moving Away from a Box/Product Supplier Strategy

9. Market Analysis and Forecasts

  • 9.1. Telecom API Revenue 2016-2021
  • 9.2. Telecom APIs Revenue by API Category 2016-2021
    • 9.2.1. Messaging API Revenues
    • 9.2.2. LBS API Revenues
    • 9.2.3. SDM API Revenues
    • 9.2.4. Payment API Revenues
    • 9.2.5. IoT API Revenues
    • 9.2.6. Other API Revenues
  • 9.3. Telecom API Revenue by Region 2016-2021
    • 9.3.1. Asia Pacific 1
    • 9.3.2. Eastern Europe
    • 9.3.3. Latin & Central America
    • 9.3.4. Middle East & Africa
    • 9.3.5. North America
    • 9.3.6. Western Europe

10. Technology and Market Drivers for Future API Market Growth

  • 10.1. Service Oriented Architecture
  • 10.2. Software Defined Networks
  • 10.3. Virtualization
    • 10.3.1. Network Function Virtualization
    • 10.3.2. Virtualization beyond Network Functions
  • 10.4. Internet of Things
    • 10.4.1. IoT Definition
    • 10.4.2. IoT Technologies
    • 10.4.3. IoT Applications
    • 10.4.4. IoT Solutions
    • 10.4.5. IoT, DaaS, and APIs

11. Appendix

  • 11.1. Telecom API Definitions
  • 11.2. More on Telecom APIs and DaaS
    • 11.2.1. Tiered Data Focus
    • 11.2.2. Value-based Pricing
    • 11.2.3. Open Development Environment
    • 11.2.4. Specific Strategies
      • 11.2.4.1. Service Ecosystem and Platforms
      • 11.2.4.2. Bringing to Together Multiple Sources for Mash-ups
      • 11.2.4.3. Developing Value-added Services as Proof Points
      • 11.2.4.4. Open Access to all Entities including Competitors
      • 11.2.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
  • 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 API Value Chain
  • Figure 9: API Transaction Value by Type
  • Figure 10: API Transaction Costs (US Cents) 2012-2019
  • Figure 11: Volume of API Transactions for a Tier 1 Carrier (Billions per Month): 2016-2021
  • 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: Telecom API Revenue (USD Billions) 2016-2021
  • Figure 20: Telecom API Revenue (USD Billions) by Category 2016-2021
  • Figure 21: Messaging APIs Revenue (USD Billions) 2016-2021
  • Figure 22: LBS APIs Revenue (USD Billions) 2016-2021
  • Figure 23: SDM APIs Revenue (USD Billions) 2016-2021
  • Figure 24: Payment APIs Revenue (USD Billions) 2016-2021
  • Figure 25: IoT API Revenue (USD Billions) 2016-2021
  • Figure 26: API Revenue for Other Categories (USD Billions) 2016-2021
  • Figure 27: Telecom API Revenue (USD Billions) by Region 2016-2021
  • Figure 28: Telecom API Revenue (USD Billions) Asia Pacific 2016-2021
  • Figure 29: Telecom API Revenue (USD Billions) Eastern Europe 2016-2021
  • Figure 30: Telecom API Revenue (USD Billions) Latin & Central America 2016-2021
  • Figure 31: Telecom API Revenue (USD Billions) Middle East & Africa 2016-2021 108
  • Figure 32: Telecom API Revenue (USD Billions) North America 2016-2021
  • Figure 33: Telecom API Revenue (USD Billions) Western Europe 2016-2021
  • Figure 34: Services Oriented Architecture
  • Figure 35: Growth of Connected Devices
  • Figure 36: IoT and Future Telecom API Topology
  • Figure 37: Different Data Types and Functions in DaaS
  • Figure 38: Ecosystem and Platform Model
  • Figure 39: Telecom API and Internet of Things Mediation
  • Figure 40: DaaS and IoT Mediation
Back to Top