Cover Image
市場調查報告書

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

Telecom API Market Outlook and Forecasts 2018 - 2023

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

本報告詳細分析了全球通訊API市場,並調查研究了通訊API的定義及功能,商業模式與實際使用案例、最佳實踐、價值鏈架構、通訊操作商/API供應商的事業戰略、今後技術開發及運用的情況、市場規模動態預測、相關技術概要(SDN、虛擬化、IoT等)與業界人士應採取的策略等等。

第1章 執行摘要

第2章 簡介

第3章 通訊API

  • 通訊API的作用及其重要性
  • 對於可活用API的CSP的商業促進要素
    • 新的收入來源的必要性
    • 需要與社會各界合作發展
    • B2B服務與非對稱商業模式
    • IoT Mediation的新需求
  • 通訊API的分類
    • 訪問管理
    • 廣告、行銷
    • 非數位商品計費
    • 內容傳遞
    • Directory、Registry管理
    • 企業協作
    • IVR/語音解決方案
    • 位置確定
    • M2M與IoT
    • 語音信箱與其他非語音服務
    • 號碼管理
    • 包括買方驗證的付款服務
    • 驗證存在
    • 即時通信與WebRTC
    • 訂戶ID管理
    • 訂戶設定檔管理
    • 服務品質管理
    • 整合通訊 UCaaS
    • 非結構化附加服務
    • 騷擾電話管理、自動語音電話 (robocall)
    • 語音/對話
  • 通訊API的商業模式
  • 類別
  • 競爭問題
  • 使用API的應用程式
  • 通訊API收入潛力
  • 通訊API的價值鏈
  • API資料庫事務成本:依種類區分
  • API資料庫事務量

第4章 通訊API聚合

  • API聚合器的作用
  • API聚合器的總成本
    • 初始設置成本
    • 資料庫事務成本
    • 當前設備的維護和支援
    • 中介商的專業服務
  • 聚合器API的使用狀況:按類別分類
    • 聚合器API案例:LocationSmart
    • 聚合:在2大需求的交匯處
    • 其他API類別的事例
    • 向新的商業模式過渡

第5章 通訊API市場

  • 資料作為服務(DaaS)
    • 電信業者結構化和非結構化資料
    • DaaS中電信業者的資料管理
    • DaaS生態系統的資料聯合
  • API市場參與產業
    • Mashape
    • Salesforce (Mulesoft)
    • TeleStax
  • 通訊API生態系統供應商
  • 通信應用的開發
    • 支援通訊的應用程式(CAM)市場
    • 改善現有應用程式和服務市場

第6章 通訊API應用程式的使用案例

  • 通訊應用程式的收益化
    • API的直接收入
    • 資料收益化
    • 成本控制
    • 提高使用頻率
    • 抑制客戶流失 (解約率)
  • 使用上的挑戰
    • 安全性
    • 互操作性

第7章 通信服務供應商的通訊API戰略

  • 電信運營商市場戰略與定位
    • API投資額穩定化
    • 電信業者、API、OTT
    • 有效使用訂戶資料和API
    • 通訊API的標準
    • 通訊API與企業
  • 主要網路操作員API程式
    • AT&T
    • Verizon Wireless
    • Vodafone
    • France Telecom (Orange)
    • Telefonica
  • 專注於內部通訊API運用的電信業者
    • 內部運用案例
    • 內部通訊API使用案例
  • OTT服務提供者和運營商
    • 賦予OTT提供者應用程式的許可
    • 為了有效活用API而生的創新技術:電信業者無法單獨對應
  • 通訊業者與附加價值服務(VAS)
    • VAS的作用及其重要性
    • 電信業者支援VAS的案例
    • 電信業者在VAS的挑戰與機會

第8章 通訊API應用程式開發者的戰略

  • 將通訊API作為關鍵的開發資產處理
  • API發佈的明智選擇
  • 依照電信業者的計畫推展業務
  • 開發者的喜好:OTT服務提供者或電信業者

第9章 通訊API供應商戰略

  • 總體戰略
  • 具體戰略

第10章 通訊API市場分析與預測

  • 全球通訊API市場
    • 通訊API市場整體
    • 通訊API市場:依類別區分
    • 通訊API市場:依服務型態區分
    • 通訊API市場:依使用者型態區分
    • 通訊API市場:依網路技術區分
    • 通訊API市場:依推展方向區分
    • 通訊API市場:依模組區分
    • 通訊API市場:依利害相關者區分
  • 區域通訊API市場
    • 通訊API市場:依地區區分
    • 北美洲
    • 歐洲
    • 亞洲及太平洋
    • 中東及非洲
    • 拉丁美洲
    • 通訊API市場排名前10

第11章 技術與API市場增長促進因素

  • SOA (面向服務的體系結構)
  • SDN (軟體定義網路)
  • 虛擬化
    • NVF (網路功能虛擬化)
    • 非功能網路虛擬化
  • IoT (物聯網)
    • IoT定義
    • IoT技術
    • IoT應用程式
    • IoT解決方案
    • IoT、DaaS與API
  • IoT WAN與通訊API
    • 蜂巢式IoT WAN
    • 非蜂巢式IoT WAN
    • 蜂巢式 vs. 非蜂巢式IoT WAN通訊API的需求
    • IoT電腦系統結構與面向平台的通訊API

第12章 結論和建議

第13章 附錄

本網頁內容可能與最新版本有所差異。詳細情況請與我們聯繫。

目錄

Overview:

Global Communication Service Providers (CSP) continue to see Telecom APIs as a means of leveraging their network and subscriber assets to generate revenues with high margins. However, the ecosystem remains one in which largely third-parties, such as OTT players, maintain the end-user relationship with app and service clients, while CSPs merely provide essentially data as a service on a B2B basis.

While this model may suffice for CSPs with respect to the consumer segment and SMBs, it is not sustainable for large corporate clients. CSPs are facing increasing pressure to provide a greater variety of high quality enterprise communications and business collaboration solutions. Accordingly, Mind Commerce sees this as an area ripe for leveraging Telecom APIs to offer value-added carrier offerings such as team collaboration, telepresence, and unified communications (UC).

For many larger Telecom API vendors, a substantial proportion of revenue continues to be generated from SIP Trunking in support of their client's VoIP, UC, and other IP-based communications apps and services. However, many smaller players are innovating in areas that have high growth potential such as analytics data, device information, edge computing, and number management for calls, data, and subscribers. The last category in particular is emerging as an important area for unwanted call management solutions including robocall management.

Longer term, Mind Commerce sees CSPs leveraging Telecom APIs and related tools to support a variety of industry requirements in which carriers are amply positioned to leverage their market position. Those opportunities include Internet of Things (IoT) authentication, robotics, Artificial Intelligence (AI) platforms, Mobile Edge Computing (MEC), and support of Blockchain. Three areas that represent great opportunities for carriers to aggressively pursue solution development in the more near-term timeframe are AI, IoT, and Mobile Edge Computing.

Telecom APIs in IoT

IoT represents a huge and largely untapped market for CSPs, which Mind Commerce sees emerging once carriers begin to fully leverage 5G for IoT apps and services. More specifically, we have identified the opportunity for carriers to act as a orchestrator/mediator within the IoT ecosystem. Uniquely positioned as owner of the primary network to be used for IoT, and provider of data services for humans and machines alike, CSPs have the opportunity to provide various critical services such as IoT authentication, authorization, and accounting. This will include use of Telecom API resources to help manage IoT related access control, permissions, and usage tracking.

Telecom APIs in Mobile Edge Computing

Carriers are also well positioned to leverage Telecom API enabled capabilities in support of many edge computing use cases as MEC is rolled-out to optimize LTE, 5G, and IoT. Many MEC use cases will require support from multiple Telecom API categories such as Location, Presence, Subscriber Data, and QoS in support of zone-based enterprise apps, services, and data analytics. This will create both a challenge and opportunity for CSPs, which will need the assistance of systems integrators for implementation and managed infrastructure services providers for ongoing operations.

Telecom APIs in Artificial Intelligence

While many AI capabilities will be embedded within other areas (such as platforms, devices, semiconductors, etc.), AI will also be closely associated with end-users, creating an opportunity for CSPs to provide resource support for many AI enabled use cases. This will include basic support for AI, such as user verification, as well as more advanced functionality, such as identifying resource usage and behaviors among a closed user group like enterprise collaboration teams.

Now in its sixth year of covering the Telecom API market, Mind Commerce is pleased to offer the most comprehensive research covering the ecosystem including players, platforms, tools, solutions, and service offerings. Telecom API Market Outlook and Forecasts 2018 - 2023 provides an in-depth assessment of the global Telecom API market, including business models, value chain analysis, operator strategies and a quantitative assessment of the industry from 2018 to 2023.

This report evaluates the current state of the market and outlook for the future including analysis and forecasts for the Telecom API market segmented many ways including:

  • Globally, Regionally, and Countries
  • Stakeholder Type (Carriers and Vendors)
  • Network Technology (2G, 3G, LTE, and 5G)
  • API Category (Presence, Location, SCM, etc.)
  • App Developer (Carrier, Enterprise, Long Tail, and Partner)
  • Deployment Type (Enterprise Hosted, Private Cloud, and Public Cloud)
  • Implementation (Development and Set-up) and by Ongoing Operations
  • Solution (AI, Analytics, Blockchain, Edge Computing, Robotics, WebRTC, etc.)

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.

Select Report Findings:

  • Total global Telecom API related revenue will reach $319.6B by 2023
  • Telecom API support of IoT remains a high priority cellular operator-only opportunity
  • Edge Computing related Telecom API revenue reaches $395M in North America by 2023
  • Global IoT platform and authentication API revenue reaches $5.3B and $9.2B respectively by 2019
  • Fastest growing global revenue areas will be MEC, blockchain, and robotics at 39%, 34%, and 31% respectively
  • Conversely, the market share for next generation use cases remains low compared to messaging, WebRTC, and others

Report Benefits:

  • Gain a better perspective of the State of the Market for Telecom APIs
  • Identify challenges and opportunities across the entire API ecosystem
  • Understand the role of Telecom APIs within the realm of Programmable Telecom
  • Identify leading companies and solutions for Telecom API enabled apps and services
  • Understand the market dynamics, players, and outlook for communication enabled apps
  • Forecasts for every major Telecom API area including Categories, Solutions, Stakeholder Share, and more
  • Forecasts for Telecom API support of Unwanted Call Management including Do Not Disturb and Call Screening

Target Audience:

  • Telecom API providers
  • ICT Infrastructure providers
  • Data infrastructure and services companies
  • Legacy mobile network operators and OTT service providers
  • Systems integrators for enterprise communications and collaboration solutions
  • Application developers such as unified communications and enterprise collaboration
  • Communications service providers including contact centers, VoIP based carriers, and others

Vendors in Report:

  • Amdocs
  • Apidaze
  • Apifonica
  • Aspect Software
  • Bandwidth
  • BICS
  • CA Technologies
  • Cisco
  • CLX Communications
  • Ericsson
  • Fortumo
  • GENBAND
  • Google
  • hSenid Mobile
  • Huawei
  • Hubtel
  • LocationSmart
  • Mashape
  • MessageBird
  • Mulesoft
  • Nokia Networks
  • Oracle
  • Persistent Systems
  • Syniverse
  • TeleStax
  • Telnyx
  • Twilio
  • Tyntec
  • Vidyo
  • Vonage

Table of Contents

1. Executive Summary

2. Introduction

  • 2.1. About the Report
    • 2.1.1. Topics Covered
    • 2.1.2. Key Findings
    • 2.1.3. Target Audience
  • 2.2. Programmable Telecom
    • 2.2.1. Programmable Telecom Definition
    • 2.2.2. Programmable Telecom Purpose
    • 2.2.3. Telecom Programmability Tools
      • 2.2.3.1. Application Programming Interfaces (API)
      • 2.2.3.2. Cloud Hosted Services
      • 2.2.3.3. Communications Platform as a Service (CPaaS)
      • 2.2.3.4. Graphical User Interfaces (GUI)
      • 2.2.3.5. Open Source Telecom Software
      • 2.2.3.6. Software Development Kits (SDK)
  • 2.3. State of the Industry

3. Telecom API Overview

  • 3.1. Role and Importance of Telecom APIs
  • 3.2. Business Drivers for CSPs to Leverage APIs
    • 3.2.1. Need for New Revenue Sources
    • 3.2.2. Need for Collaboration with Development Community
    • 3.2.3. B2B Services and Asymmetric Business Models
    • 3.2.4. Emerging Need for IoT Mediation
  • 3.3. Telecom API Categories
    • 3.3.1. Access Management
    • 3.3.2. Advertising and Marketing
    • 3.3.3. Billing of Non-Digital Goods
    • 3.3.4. Content Delivery
    • 3.3.5. Directory and Registry Management
    • 3.3.6. Enterprise Collaboration
    • 3.3.7. IVR/Voice Solutions
    • 3.3.8. Location Determination
    • 3.3.9. M2M and Internet of Things
    • 3.3.10. Messaging and other Non-Voice Communications
      • 3.3.10.1. Text Messaging
      • 3.3.10.2. Multimedia Messaging
    • 3.3.11. Number Management
    • 3.3.12. Payments including Purchaser Present Verification
    • 3.3.13. Presence Detection
    • 3.3.14. Real-time Communications and WebRTC
    • 3.3.15. Subscriber Identity Management
    • 3.3.16. Subscriber Profile Management
    • 3.3.17. Quality of Service Management
    • 3.3.18. Unified Communications and UCaaS
    • 3.3.19. Unstructured Supplementary Service Data
    • 3.3.20. Unwanted Call Management and Robo Calls
    • 3.3.21. Voice/Speech
  • 3.4. Telecom API Business Models
    • 3.4.1. Three Business Model Types
      • 3.4.1.1. Model One
      • 3.4.1.2. Model Two
      • 3.4.1.3. Model Three
    • 3.4.2. The Asymmetric Business Model
    • 3.4.3. Exposing APIs to Developers
    • 3.4.4. Web Mash-ups
  • 3.5. Segmentation
    • 3.5.1. Users by Segment
    • 3.5.2. Workforce Management
  • 3.6. Competitive Issues
    • 3.6.1. Reduced Total Cost of Ownership
    • 3.6.2. Open APIs
    • 3.6.3. Configurability and Customization
  • 3.7. Applications that use APIs
  • 3.8. Telecom API Revenue Potential
    • 3.8.1. Standalone API Revenue vs. API enabled Revenue
    • 3.8.2. Telecom API-enabled Mobile VAS Applications
    • 3.8.3. Carrier Focus on Telecom API's for the Enterprise
  • 3.9. Telecom API Usage by Industry Segment
  • 3.10. Telecom API Value Chain
    • 3.10.1. Telecom API Value Chain
    • 3.10.2. How the Value Chain Evolves
    • 3.10.3. API Transaction Value Split among Players
  • 3.11. API Transaction Cost by Type
  • 3.12. Volume of API Transactions

4. API Aggregation

  • 4.1. Role of API Aggregators
  • 4.2. Total Cost of Operation with API Aggregators
    • 4.2.1. Start-up Costs
    • 4.2.2. Transaction Costs
    • 4.2.3. Ongoing Maintenance/Support
    • 4.2.4. Professional Services by Intermediaries
  • 4.3. Aggregator API Usage by Category
    • 4.3.1. API Aggregator Example: LocationSmart
    • 4.3.2. Aggregation: Intersection of Two Big Needs
    • 4.3.3. The Case for Other API Categories
    • 4.3.4. Moving Towards New Business Models

5. Telecom API Marketplace

  • 5.1. Data as a Service (DaaS)
    • 5.1.1. Carrier Structured and Unstructured Data
    • 5.1.2. Carrier Data Management in DaaS
    • 5.1.3. Data Federation in the DaaS Ecosystem
  • 5.2. API Marketplace Companies
    • 5.2.1. Mashape
    • 5.2.2. Salesforce (Mulesoft)
    • 5.2.3. TeleStax
  • 5.3. Telecom API Ecosystem Vendors
    • 5.3.1. APIs part of Infrastructure and Services Portfolio
      • 5.3.1.1. Ericsson
      • 5.3.1.2. Huawei
      • 5.3.1.3. Nokia Networks
      • 5.3.1.1. Ribbon Communications
    • 5.3.2. API Capabilities Acquired via M&A
      • 5.3.2.1. Amdocs
      • 5.3.2.2. Aspect Software
      • 5.3.2.3. BICS
      • 5.3.2.4. CA Technologies
      • 5.3.2.5. Cisco
      • 5.3.2.6. Google
      • 5.3.2.7. Oracle
      • 5.3.2.8. Persistent Systems
      • 5.3.2.9. Vonage
    • 5.3.3. API Capabilities Independently Developed
      • 5.3.3.1. Apidaze
      • 5.3.3.2. Apifonica
      • 5.3.3.3. Bandwidth Inc.
      • 5.3.3.4. CLX Communications
      • 5.3.3.5. Fortumo
      • 5.3.3.6. hSenid Mobile
      • 5.3.3.7. Hubtel
      • 5.3.3.8. MessageBird
      • 5.3.3.9. Syniverse
      • 5.3.3.10. Telnyx
      • 5.3.3.11. Tyntec
      • 5.3.3.12. Twilio
      • 5.3.3.13. Vidyo
  • 5.4. Telecom Application Development
    • 5.4.1. Communications-enabled App Marketplace
      • 5.4.1.1. Market Opportunities and Challenges
      • 5.4.1.2. Marketplace Facilitators
    • 5.4.2. Improving Existing Apps and Services Marketplace

6. Telecom API Enabled App Use Cases

  • 6.1. Monetization of Communications-enabled Apps
    • 6.1.1. Direct API Revenue
    • 6.1.2. Data Monetization
    • 6.1.3. Cost Savings
    • 6.1.4. Higher Usage
    • 6.1.5. Churn Reduction
  • 6.2. Use Case Issues
    • 6.2.1. Security
    • 6.2.2. Data Privacy
    • 6.2.3. Interoperability

7. Communication Service Provider Telecom API Strategies

  • 7.1. Carrier Market Strategy and Positioning
    • 7.1.1. API Investment Stabilization
    • 7.1.2. Carriers, APIs, and OTT
    • 7.1.3. Leveraging Subscriber Data and APIs
    • 7.1.4. Telecom API Standards
    • 7.1.5. Telecom APIs and Enterprise
  • 7.2. Select Network Operator API Programs
    • 7.2.1. AT&T
    • 7.2.2. Verizon Wireless
    • 7.2.3. Vodafone
    • 7.2.4. France Telecom (Orange)
    • 7.2.5. Telefonica
  • 7.3. Carrier Focus on 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
    • 7.5.1. 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 Application Developer Strategies

  • 8.1. Treating Telecom APIs as a Critical Developer Asset
  • 8.2. Judicious Choice of API Releases
  • 8.3. Working alongside Carrier Programs
  • 8.4. Developer Preferences: OTT Service Providers vs Carriers

9. Telecom API Vendor Strategies

  • 9.1. General Strategies
    • 9.1.1. Value Chain Enhancers and Development Facilitators
    • 9.1.2. Moving from Platforms to Cloud-based CPaaS
  • 9.2. Specific Strategies
    • 9.2.1. Reliance upon SIP Trunking
    • 9.2.2. Improving Existing Solutions
    • 9.2.3. Increased Focus on Enterprise Solutions
    • 9.2.4. Embracing Next Generation Use Cases

10. Telecom API Market Analysis and Forecasts

  • 10.1. Global Telecom API Market 2018-2023
    • 10.1.1. Total Telecom API Market
    • 10.1.2. Telecom API Market by Category
    • 10.1.3. Telecom API Market by Service Type
    • 10.1.4. Telecom API Market by User Type
    • 10.1.5. Telecom API Market by Network Technology
    • 10.1.6. Telecom API Market by Deployment
    • 10.1.7. Telecom API Market by Module
    • 10.1.8. Telecom API Market by Stakeholder
  • 10.2. Regional Telecom API Market 2018-2023
    • 10.2.1. Telecom API Market by Region 2018-2023
    • 10.2.2. North America Telecom API Market by API Category and Service Type 2018-2023
    • 10.2.3. Europe Telecom API Market by API Category and Service Type 2018-2023
    • 10.2.4. APAC Telecom API Market by API Category and Service Type 2018-2023
    • 10.2.5. Middle East and Africa Telecom API Market by API Category and Service Type 2018-2023
    • 10.2.6. Latin America Telecom API Market by API Category and Service Type 2018-2023
    • 10.2.7. Top Ten Telecom API Markets 2018-2023

11. Technology and Market Drivers for API Market Growth

  • 11.1. Service Oriented Architecture
  • 11.2. Software Defined Networks
  • 11.3. Virtualization
    • 11.3.1. Network Function Virtualization
    • 11.3.2. Virtualization beyond Network Functions
  • 11.4. Internet of Things
    • 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
  • 11.5. IoT WANs and Telecom APIs
    • 11.5.1. Cellular IoT WAN
    • 11.5.2. Non-Cellular IoT WAN
    • 11.5.1. Cellular vs. Non-Cellular IoT WAN Telecom API Needs
    • 11.5.2. Telecom APIs for IoT Authentication and Platforms

12. Conclusions and Recommendation

  • 12.1. Overall Telecom API Outlook

13. Appendix

  • 13.1. Telecom API Definitions
  • 13.2. More on Telecom APIs and DaaS
    • 13.2.1. Tiered Data Focus
    • 13.2.2. Value-based Pricing
    • 13.2.3. Open Development Environment
    • 13.2.4. Specific Strategies
      • 13.2.4.1. Service Ecosystem and Platforms
      • 13.2.4.2. Bringing to Together Multiple Sources for Mash-ups
      • 13.2.4.3. Developing Value-added Services as Proof Points
      • 13.2.4.4. Open Access to all Entities including Competitors
      • 13.2.4.5. Prepare for Big Opportunities with the Internet of Things (IoT)
  • 13.3. Monetizing IoT APIs
    • 13.3.1. IoT API Business Models
    • 13.3.2. Peer Support of Platforms, Devices, and Gateways
    • 13.3.3. Supporting the API Developer Community
    • 13.3.4. Data and Database Transactions

Figures

  • Figure 1: Communication Service Provider Assets
  • Figure 2: Next Generation CSP Assets driving Telecom API Usage
  • Figure 3: RCS and Telecom API Integration
  • Figure 4: Enterprise Dashboard
  • Figure 5: Enterprise Dashboard App Example
  • Figure 6: Telecom API Value Chain
  • Figure 7: API Transaction Value by Type
  • Figure 8: Volume of API Transactions for a Tier 1 Carrier 2018-2023
  • Figure 9: Cloud Services and APIs
  • Figure 10: Programmable Telecom Vendor Services Comparative Segmentation
  • Figure 11: GSMA OneAPI: Benefits to Stakeholders
  • Figure 12: AT&T Wireless API Catalog
  • Figure 13: Verizon Wireless API Program
  • Figure 14: France Telecom (Orange) API Program
  • Figure 15: Telefonica API Program
  • Figure 16: Carrier Internal Use of Telecom APIs
  • Figure 17: Global Telecom API Market 2018-2023
  • Figure 18: Global Telecom API Market Yearly Growth 2018-2023
  • Figure 19: Top Ten Telecom API Market Share by Country 2018-2023
  • Figure 20: Services Oriented Architecture
  • Figure 21: Global Connected IoT Things and Objects 2018-2023
  • Figure 22: IoT and Future Telecom API Topology
  • Figure 23: 3GPP IoT Proposals for LTE, Narrowband and 5G Network
  • Figure 24: LoRaWAN Network Architecture
  • Figure 25: Cellular vs. Non-Cellular IoT WAN Comparison
  • Figure 26: Different Data Types and Functions in DaaS
  • Figure 27: Ecosystem and Platform Model
  • Figure 28: Telecom API and Internet of Things Mediation
  • Figure 29: DaaS and IoT Mediation

Tables

  • Table 1: Global Telecom API Market by Category 2018-2023
  • Table 2: Global Telecom API Market Share by Category 2018-2023
  • Table 3: Global Telecom API Market by Service Type 2018-2023
  • Table 4: Global Telecom API Market Share by Service Type 2018-2023
  • Table 5: Global Telecom API Market by User Type 2018-2023
  • Table 6: Global Telecom API Market Share by User Type 2018-2023
  • Table 7: Global Telecom API Market by Network Technology 2018-2023
  • Table 8: Global Telecom API Market Share by Network Technology 2018-2023
  • Table 9: Global Telecom API Market by Deployment 2018-2023
  • Table 10: Global Telecom API Market Share by Deployment 2018-2023
  • Table 11: Global Telecom API Market by Module 2018-2023
  • Table 12: Global Telecom API Market Share by Module 2018-2023
  • Table 13: Global Telecom API Market by Stakeholder 2018-2023
  • Table 14: Global Telecom API Market Share by Stakeholder 2018-2023
  • Table 15: Telecom API Market by Region 2018-2023
  • Table 16: Telecom API Market Share by Region 2018-2023
  • Table 17: North America Telecom API Market by Category 2018-2023
  • Table 18: North America Telecom API Market by Service Type 2018-2023
  • Table 19: North America Telecom API Market by User Type 2018-2023
  • Table 20: North America Telecom API Market by Network Technology 2018-2023
  • Table 21: North America Telecom API Market by Deployment 2018-2023
  • Table 22: North America Telecom API Market by Module 2018-2023
  • Table 23: North America Telecom API Market by Stakeholder 2018-2023
  • Table 24: North America Telecom API Market by Country 2018-2023
  • Table 25: North America Telecom API Market Share by Country 2018-2023
  • Table 26: Europe Telecom API Market by Category 2018-2023
  • Table 27: Europe Telecom API Market by Service Type 2018-2023
  • Table 28: Europe Telecom API Market by User Type 2018-2023
  • Table 29: Europe Telecom API Market by Network Technology 2018-2023
  • Table 30: Europe Telecom API Market by Deployment 2018-2023
  • Table 31: Europe Telecom API Market by Module 2018-2023
  • Table 32: Europe Telecom API Market by Stakeholder 2018-2023
  • Table 33: Europe Telecom API Market by Country 2018-2023
  • Table 34: Europe Telecom API Market Share by Country 2018-2023
  • Table 35: APAC Telecom API Market by Category 2018-2023
  • Table 36: APAC Telecom API Market by Service Type 2018-2023
  • Table 37: APAC Telecom API Market by User Type 2018-2023
  • Table 38: APAC Telecom API Market by Network Technology 2018-2023
  • Table 39: APAC Telecom API Market by Deployment 2018-2023
  • Table 40: APAC Telecom API Market by Module 2018-2023
  • Table 41: APAC Telecom API Market by Stakeholder 2018-2023
  • Table 42: APAC Telecom API Market by Country 2018-2023
  • Table 43: APAC Telecom API Market Share by Country 2018-2023
  • Table 44: MEA Telecom API Market by Category 2018-2023
  • Table 45: MEA Telecom API Market by Service Type 2018-2023
  • Table 46: MEA Telecom API Market by User Type 2018-2023
  • Table 47: MEA Telecom API Market by Network Technology 2018-2023
  • Table 48: MEA Telecom API Market by Deployment 2018-2023
  • Table 49: MEA Telecom API Market by Module 2018-2023
  • Table 50: MEA Telecom API Market by Stakeholder 2018-2023
  • Table 51: MEA Telecom API Market by Country 2018-2023
  • Table 52: MEA Telecom API Market Share by Country 2018-2023
  • Table 53: Latin America Telecom API Market by Category 2018-2023
  • Table 54: Latin America Telecom API Market by Service Type 2018-2023
  • Table 55: Latin America Telecom API Market by User Type 2018-2023
  • Table 56: Latin America Telecom API Market by Network Technology 2018-2023
  • Table 57: Latin America Telecom API Market by Deployment 2018-2023
  • Table 58: Latin America Telecom API Market by Module 2018-2023
  • Table 59: Latin America Telecom API Market by Stakeholder 2018-2023
  • Table 60: Latin America Telecom API Market by Country 2018-2023
  • Table 61: Latin America Telecom API Market Share by Country 2018-2023
  • Table 62: Top Ten Telecom API Market by Country 2018-2023
  • Table 63: Global Connected Device by Non-IoT Product 2018-2023
  • Table 64: Global Connected Device by Consumer IoT Product 2018-2023
  • Table 65: Global Connected Device by Enterprise IoT Product 2018-2023
  • Table 66: Global Connected Device by Industrial IoT Product 2018-2023
  • Table 67: Global Connected Device by Government IoT Product 2018-2023
Back to Top