TM Forum Technical Report
CSP Use Cases Utilizing
Blockchain
TR279
Team Approved Date: 08/Aug/2019
Release Status: Production Approval Status: TM Forum Approved
Version: 3.1.1 IPR Mode: RAND
TM Forum 2019. All Rights Reserved.
CSP Use Cases Utilizing Blockchain
Notice
Copyright © TM Forum 2019. All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative
works that comment on or otherwise explain it or assist in its implementation may be
prepared, copied, published, and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this section are included on all such copies
and derivative works. However, this document itself may not be modified in any way, including
by removing the copyright notice or references to TM FORUM, except as needed for the
purpose of developing any document or deliverable produced by a TM FORUM Collaboration
Project Team (in which case the rules applicable to copyrights, as set forth in the TM FORUM
IPR Policy, must be followed) or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by TM FORUM or
its successors or assigns.
This document and the information contained herein is provided on an “AS IS” basis and TM
FORUM DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY
OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
TM FORUM invites any TM FORUM Member or any other party that believes it has patent
claims that would necessarily be infringed by implementations of this TM Forum Standards
Final Deliverable, to notify the TM FORUM Team Administrator and provide an indication of its
willingness to grant patent licenses to such patent claims in a manner consistent with the IPR
Mode of the TM FORUM Collaboration Project Team that produced this deliverable.
The TM FORUM invites any party to contact the TM FORUM Team Administrator if it is aware
of a claim of ownership of any patent claims that would necessarily be infringed by
implementations of this TM FORUM Standards Final Deliverable by a patent holder that is not
willing to provide a license to such patent claims in a manner consistent with the IPR Mode of
the TM FORUM Collaboration Project Team that produced this TM FORUM Standards Final
Deliverable. TM FORUM may include such claims on its website but disclaims any obligation to
do so.
TM FORUM takes no position regarding the validity or scope of any intellectual property or
other rights that might be claimed to pertain to the implementation or use of the technology
described in this TM FORUM Standards Final Deliverable or the extent to which any license
under such rights might or might not be available; neither does it represent that it has made
any effort to identify any such rights. Information on TM FORUM's procedures with respect to
rights in any document or deliverable produced by a TM FORUM Collaboration Project Team
can be found on the TM FORUM website. Copies of claims of rights made available for
publication and any assurances of licenses to be made available, or the result of an attempt
© TM Forum 2019. All Rights Reserved. Page 2 of 54
CSP Use Cases Utilizing Blockchain
made to obtain a general license or permission for the use of such proprietary rights by
implementers or users of this TM FORUM Standards Final Deliverable, can be obtained from
the TM FORUM Team Administrator. TM FORUM makes no representation that any
information or list of intellectual property rights will at any time be complete, or that any
claims in such list are, in fact, Essential Claims.
Direct inquiries to the TM Forum office:
4 Century Drive, Suite 100
Parsippany, NJ 07054 USA
Tel No. +1 973 944 5100
Fax No. +1 973 998 7916
TM Forum Web Page: [Link] [Link]
© TM Forum 2019. All Rights Reserved. Page 3 of 54
CSP Use Cases Utilizing Blockchain
Table of Contents
Notice 2
Table of Contents 4
List of Figures 7
Executive Summary 9
1. Introduction 10
1.1. Blockchain Basics 10
1.2. Smart Contracts11
1.3. Key Blockchain Characteristics 11
1.4. Use case categories of interest to service providers 12
1.5. The role of blockchain in service providers' digital transformation 13
2. Virtual Identity Supporting Mobility across Platform-based Ecosystems 14
3. Mobile Money Cross-Operator Transfer 17
4. Identity as a Service 19
5. Roaming with Local Breakout Mode 21
6. Data Access Authorization 23
7. SLA Management 25
8. Use Cases from the Blockchain Unleashed Catalyst 28
8.1. Elimination of Call Detail Records (CDRs) for Billing, Settlement, and Fraud
Detection 28
8.1.1. Current process.......................................................................................29
8.1.2. Challenges related to the current process...............................................29
8.1.3. Solution architecture...............................................................................30
8.1.4. New process based on the solution architecture.....................................30
8.1.5. Benefits of the new process.....................................................................31
8.2. Identity Management 31
8.2.1. Current process.......................................................................................31
8.2.2. Challenges related to the current process...............................................32
8.2.3. Solution architecture...............................................................................32
8.2.4. New process based on the solution architecture.....................................33
8.2.5. Benefits of the new process.....................................................................33
© TM Forum 2019. All Rights Reserved. Page 4 of 54
CSP Use Cases Utilizing Blockchain
8.3. Service-Level Agreement (SLA) Monitoring 34
8.3.1. Current process.......................................................................................34
8.3.2. Challenges related to the current process...............................................34
8.3.3. Solution architecture...............................................................................34
8.3.4. New process based on the solution architecture.....................................35
8.3.5. Benefits of the new process.....................................................................35
8.4. Reducing Mobile Phone Thefts 36
8.4.1. Current process.......................................................................................36
8.4.2. Challenges related to the current process...............................................36
8.4.3. Solution architecture...............................................................................37
8.4.4. New process based on the solution architecture.....................................37
8.4.5. Benefits of the new process.....................................................................37
8.5. Mobile Number Portability (MNP) 38
8.5.1. Current process.......................................................................................38
8.5.2. Challenges related to the current process...............................................38
8.5.3. Solution architecture...............................................................................39
8.5.4. New process based on the solution architecture.....................................39
8.5.5. Benefits of the new process.....................................................................39
8.6. Key Learnings 40
8.6.1. Due to limitations with blockchain’s processing capabilities, we have to
be careful when determining what processes and data should be placed in the
blockchain.............................................................................................................40
8.6.2. Due to technology limitations today, there’s no efficient way to create
digital rules and logic from legal documents which can be incorporated into the
blockchain.............................................................................................................40
8.6.3. Lack of standards in implementing blockchain leads to inconsistencies in
development and implementation........................................................................40
9. Use Cases from the Blockchain based Telecom Infrastructure Marketplace Catalyst 42
9.1. Business Scenarios 42
9.2. Asset Marketplace 42
9.2.1. Current Assets Marketplace process.......................................................42
9.2.2. Challenges of existing Asset Marketplaces..............................................43
9.2.3. Assets Marketplace: Blockchain Solution................................................43
© TM Forum 2019. All Rights Reserved. Page 5 of 54
CSP Use Cases Utilizing Blockchain
9.2.4. Generic Blockchain-based Marketplace: proposed 5G deployment
Scenarios...............................................................................................................44
9.3. Energy Marketplace Use Case 44
9.4. 5G Cell Re-enforcement /Densification through Telecom Infrastructure
Marketplace 45
9.4.1. Macro design...........................................................................................45
9.4.2. Actors and roles involved in this scenario................................................46
9.4.3. Smart Contract Inventory........................................................................47
9.4.4. Details workflows....................................................................................48
9.5. 5G Cell Re-enforcement / Densification through Telecom Infrastructure
Marketplace (extended to Energy as asset) 48
9.6. 5G Cell Re-enforcement / Densification through Telecom Infrastructure
Marketplace and Energy Marketplace 49
9.7. Initial 5G Country / City / White Zone / Stadium Cell deployment and Re-
enforcement / Densification through Telecom Infrastructure Marketplace and
Energy Marketplace 50
10. Appendix A: Terms & Abbreviations Used within this Document 52
10.1. Administrative Appendix 52
10.2. Document History 52
10.2.1. Version History.......................................................................................52
10.2.2. Release History.......................................................................................53
10.3. Company Contact Details 53
10.4. Acknowledgments 53
© TM Forum 2019. All Rights Reserved. Page 6 of 54
CSP Use Cases Utilizing Blockchain
List of Figures
Figure 1: Use Case Categories of Interest..................................................................................11
Figure 2: The Role of Blockchain in Service Providers’ Digital Transformation..........................12
Figure 3: Virtual Identity Supporting Mobility Across Platform-Based Ecosystems...................13
Figure 4: An Approach to Virtual Identity..................................................................................14
Figure 5: Basic Form of MNO Facilitated Transfer (Peer-to-Peer).............................................16
Figure 6: Typical Form of MNO (Hub or Middleman)................................................................17
Figure 7: Innovative Solution provided by MNOs......................................................................17
Figure 8: Identity as a Service (IDaaS).......................................................................................18
Figure 9: IDaaS Based on Blockchain.........................................................................................19
Figure 10: Blockchain Based Solution – Roaming with local Breakout Mode............................20
Figure 11: Blockchain to Support Trust in Charging Plan...........................................................20
Figure 12: Current approach to data access authorization........................................................22
Figure 13: A blockchain based solution to Data Access Authorization......................................23
Figure 14: Service Level Agreement (SLA) Management...........................................................25
Figure 15: Visiting Public Mobile Network (VPMN)....................................................................28
Figure 16: Elimination of CDRs: Blockchain solution architecture.............................................29
Figure 17: Overview of Blockchain Network for Eliminating CDRs............................................30
Figure 18: Current Identity Management Process.....................................................................31
Figure 19: Identity Management - Blockchain Solution Architecture.......................................32
Figure 20: SLA Monitoring: Blockchain Solution........................................................................34
Figure 21: Reducing Mobile Phone Threats...............................................................................35
Figure 22: Reducing Mobile Phone Threats: Blockchain Solution Architecture.........................36
Figure 23: Mobile Number Portability (MNP)............................................................................37
Figure 24: Mobile Number Portability: Blockchain Solution......................................................38
Figure 25: 5G Cell Re-enforcement /Densification through Telecom Infrastructure Marketplace
...................................................................................................................................................44
Figure 26: Actors and Roles involved in Blockchain based Telecom Infrastructure Marketplace
...................................................................................................................................................46
Figure 27: Workflows of Blockchain based Telecom Infrastructure Marketplace......................47
© TM Forum 2019. All Rights Reserved. Page 7 of 54
CSP Use Cases Utilizing Blockchain
Figure 28: 5G Cell Re-enforcement / Densification through Telecom Infrastructure Marketplace
(extended to Energy as asset)....................................................................................................48
Figure 29: 5G Cell Re-enforcement / Densification through Telecom Infrastructure Marketplace
and Energy Marketplace............................................................................................................49
Figure 30: Initial 5G Country / City / White Zone / Stadium Cell deployment and Re-
enforcement / Densification through Telecom Infrastructure Marketplace and Energy
Marketplace...............................................................................................................................50
© TM Forum 2019. All Rights Reserved. Page 8 of 54
CSP Use Cases Utilizing Blockchain
Executive Summary
This report introduces blockchain technology in the context of use cases of interest to service
providers. We first review the key characteristics that differentiate blockchain from other
technologies, then propose categories of use cases based on those characteristics. Next, we
examine specific use cases in detail. This version incorporates the latest set of blockchain
scenarios as explored by TM Forum catalysts.
© TM Forum 2019. All Rights Reserved. Page 9 of 54
CSP Use Cases Utilizing Blockchain
1. Introduction
Within the Internet of Everything (IoE) and Digital Ecosystem program, the TM Forum has
initiated an exploration of blockchain technology including development of a blockchain
“sandbox" and member contributions of proposed use cases.
In this context, the aim of this document is to describe the use cases developed to date, along
with the background information necessary to evaluate them.
This version incorporates the most recent work done by catalysts in exploring use cases
important to CSPs and can be found in Section 9.
This report is related to other documents or technical reports already published by TM Forum
including:
Monetizing Internet of Everything (TR271) which (to be filled in during review)
The Partnership Revenue Models (TR217) introduces a high level classification of all kinds
of business partnership and concentrates on the revenue models used in partnerships i.e.
focusing on the charging, billing and payment models between business partners. See:
[Link]
The Business scenario template (TMF424) provides a consistent structure and content to
describe a business problem and the way to solve it. For more information, see
[Link]
template-r16-5-1/
1.1. Blockchain Basics
This section provides a quick overview of blockchain technology. It can be skipped over by
readers already familiar with the subject.
As is customary, we can begin with highlights from the Wikipedia definition of blockchain:
A continuously growing list of records, called blocks, which are linked and secured using
cryptography.
Each block contains typically a hash pointer as a link to a previous block, a time stamp and
transaction data.
By design, blockchains are inherently resistant to modification of the data.
Functionally, a blockchain can serve as “an open, distributed ledger that can record
transactions between two parties efficiently and in a verifiable and permanent way. “
For use as a distributed ledger a blockchain is typically managed by a peer-to-peer network
collectively adhering to a protocol for validating new blocks.
Once recorded, the data in any given block cannot be altered retroactively without the
alteration of all subsequent blocks and a collusion of the network majority.
© TM Forum 2019. All Rights Reserved. Page 10 of 54
CSP Use Cases Utilizing Blockchain
Bitcoin is built on the first widely known implementation of a blockchain and is the first
successful digital currency. Digital currencies (and digital assets in general) require a solution to
the “double-spend problem” – the ability to spend a digital token twice. Before Bitcoin, this
required a single trusted third party, which is a single point of failure from both technical and
trust viewpoints.1 Bitcoin solves the problem with a distributed “chain” of “blocks” that
contain verified, time stamped financial transactions. Bitcoin blocks are hard to create, easy to
verify, and globally visible – eliminating the need for a centralized authority. Bitcoin’s
blockchain is a public distributed ledger running on many nodes communicating over a peer-
to-peer network protocol.
The second major blockchain implementation, Ethereum, solves the double-spend problem in
a way similar to Bitcoin, but more favorable to decentralized distribution of security. Ethereum
blocks contain accounts rather than transactions – its blockchain tracks “the transfer of value
and information between accounts”2 rather than focusing only on financial transactions.
Ethereum is programmable – cryptocurrency is just one example of a use case. Each Ethereum
node runs a virtual machine that can execute code – every Ethereum node can execute the
same instructions. Ethereum is for “applications that automate direct interaction between
peers or facilitate coordinated group action” 2.
Ethereum blockchains can be public, semi-private, or private.
¹ [Link]
² [Link]
1.2. Smart Contracts
A smart contract stores and executes technical aspects of a business contract as software. It is
typically implemented on a blockchain that supports code execution using a specialized smart
contract language, and often refers to, but is not (yet), in itself a legal contract. Smart contracts
are typically driven by external events but can call other smart contracts. They are applicable
to many use cases that involve state changes over time with associated value. A smart contract
executes as coded, not necessarily as expected (e.g. successful theft of funds last year from
DAO / Ethereum by people exploiting code defects).
1.3. Key Blockchain
Characteristics
Several characteristics of blockchain technology work to differentiate blockchain from other
technologies that could support similar use cases:
Blockchain works in a “trustless" environment: The distributed ledger performs the
accounting and audit functions neutrally and reliably.
A distributed ledger requires no intermediaries: Transactions can be conducted without
the need for third parties like clearinghouses.
Blockchain implements decentralized consensus which ensures integrity: The negotiation
protocol ensures that all participants see and approve a common view.
Immutability prevents tampering: It is unfeasible for a bad actor to change the distributed
record in all locations.
© TM Forum 2019. All Rights Reserved. Page 11 of 54
CSP Use Cases Utilizing Blockchain
Near-real-time updates maintain consistency: Although transaction times vary, consistency
across all copies of the ledger is quickly achieved.
Verifiability supports auditing: Any participant can go back to any transaction at any time
and prove its integrity.
Timestamps & sequencing support chronology: The distributed ledger establishes the
timing of transactions as well as their content.
Scripted transactions support smart contracts: Blockchain enables the execution of coded
“contracts" which are themselves part of the irrevocable record.
Fractional currency for micro-transactions: The cryptocurrencies supported by blockchain
allow extremely small financial transactions that re impractical or impossible with
traditional settlement systems.
1.4. Use case categories
of interest to service
providers
The Figure 1 below maps proposed use case categories to the key characteristics identified
above.
Figure 1: Use Case Categories of Interest
Based on this mapping, the initial experiment in the blockchain sandbox was conducted in SLA
management, as described in a later chapter of this report.
© TM Forum 2019. All Rights Reserved. Page 12 of 54
CSP Use Cases Utilizing Blockchain
1.5. The role of
blockchain in service
providers' digital
transformation
As depicted in Figure 2 below, blockchain can play an important role in the efforts of service
providers to transform their operations and business models.
Figure 2: The Role of Blockchain in Service Providers’ Digital Transformation
An Infrastructure Provider provides reliable network infrastructure with low latency for
blockchain businesses and may also be building Blockchain as a Service using that
infrastructure.
During Self Business Transformation, a service provider optimizes its traditional businesses
while improving efficiency, security, auditability and transparency. Additional areas of focus
may include Billing, Roaming Settlement, and Anti-Fraud. BT, Sprint and Softbank are examples
of service providers that have undergone this transformation.
As an Innovative Service Provider/Partner, a service provider may supply innovative services in
different verticals in association with partners, leveraging blockchain to build open,
transparent, reliable business ecosystems. Additional areas of focus may include Identity as a
Service, Data Product Trading, and Drone as a Service. China Mobile, BT, and Vodafone are
examples of service providers in this category.
© TM Forum 2019. All Rights Reserved. Page 13 of 54
CSP Use Cases Utilizing Blockchain
2. Virtual Identity Supporting Mobility across
Platform-based Ecosystems
Service providers and other large enterprises are building ecosystems based on platforms. A
key factor in the use of such ecosystems by consumers, especially in the context of multiple
ecosystems, is trust (the subject of another technical report referenced in the Introduction). A
fundamental aspect of trust is the focus on several types of identity:
Customer Identity (organization, person)
o Contract – legal identity
o Access Control – order and change management
o Authentication – interaction
Consumer Identity (person)
o Authentication – interaction
o Access Control – permission-based access to services
Platform Identity
Partner Identity
The importance and interrelationship of these identities is illustrated in Figure 3 below.
Figure 3: Virtual Identity Supporting Mobility Across Platform-Based Ecosystems
The ecosystems shown above share several key objectives:
Frictionless transactions
Fast Onboarding
© TM Forum 2019. All Rights Reserved. Page 14 of 54
CSP Use Cases Utilizing Blockchain
Improved customer’s interaction experience – throughout customer journeys (a single
person may have multiple personas with different service partners)
Sharing of customer identity across partners
Ability to hop or roam across ecosystems
Security and trust of identity
A common Identity for the customer across organizations requires or at least implies a single
personal identity (which could be national or even international). Ideally the customer would
manage their own identity as a “Self-Sovereign". But identity management requires external
verification/authorization. The need to be secured is an important aspect of Trust.
Figure 4 below illustrates an approach to virtual identity that may meet some of the above
requirements.
Figure 4: An Approach to Virtual Identity
The two-phase approach above uses a series of operations to create and utilize a virtual
identity:
A blockchain is used as a store of identity transactions.
A CSP provides Identity as a service to its partners.
A CSP creates a digital identity for each subscriber.
The private key for a subscriber's identity is stored on an eSIM.
The CSP creates a virtual identity using the public key from the subscriber's digital identity,
then adds a digital signature using its own private key.
© TM Forum 2019. All Rights Reserved. Page 15 of 54
CSP Use Cases Utilizing Blockchain
A pointer to virtual identity is added to the blockchain.
A copy of the distributed ledger entry is sent to partnering merchants.
An e-commerce site can then take the public key from the virtual identity, encrypt a
challenge and send it to the subscriber's app which decrypts it and responds.
The e-commerce site can then generate an e-commerce virtual identity which is stored in
the distributed ledger.
The next time the subscriber visits the same e-commerce site, they can be authenticated in
the same way.
The distributed ledger also holds the subscriber's history and preferences.
An e-commerce site can use related insights if given permission.
A subscriber can use the same virtual identity to login to a different e-commerce site in the
same way.
The CSP-provided virtual identity can be used to help create other virtual identities, e.g. a
travel virtual identity.
© TM Forum 2019. All Rights Reserved. Page 16 of 54
CSP Use Cases Utilizing Blockchain
3. Mobile Money Cross-Operator Transfer
Money transfer or remittance is one of the largest individual uses of money in the world
economy. It is responsible for a significant portion of the financial economy in many countries.
As such, it offers an opportunity for mobile network operators who can facilitate transfers by
individuals using mobile devices in a way that disrupts existing methods.
Figure 5 below shows the most basic form of MNO-facilitated transfer, which is peer-to-peer.
The aspect of trust is lacking in this method, which simply runs a periodic settlement of
accounts. In the case of disputes or fraud, the offended party may not have any legal recourse
to recover their funds, because no entity is playing the role of arbiter.
Figure 5: Basic Form of MNO Facilitated Transfer (Peer-to-Peer)
Figure 6 shows a more typical form of MNO-facilitated transfer, which uses a hub or
“middleman", typically some type of financial broker or clearinghouse.
The aspect of trust is improved in this method because the hub fills the role of an objective
arbiter who can settle disputes. However, there are also significant disadvantages introduced
by the inclusion of the hub. Perhaps the most important is that the hub itself incurs transaction
costs that must be paid by the participants, forming in effect a tax on their exchange.
Additionally, although the hub can arbitrate in case of disputes or fraud, the participants have
no further recourse. Finally, the participants are vulnerable to the manipulation of data by
employees of the hub, which is the only source of record for all transactions.
© TM Forum 2019. All Rights Reserved. Page 17 of 54
CSP Use Cases Utilizing Blockchain
Figure 6: Typical Form of MNO (Hub or Middleman)
Figure 7 shows an innovative solution provided by MNOs which disintermediates the hub and
improves several aspects of participants' experience.
In this solution, the role of the hub is played by a distributed ledger in a blockchain. Because it
is widely distributed and immutable, a different and more comprehensive kind of trust is
provided. The new solution uses a smart contact to automatically settle transactions, so that
once confirmed, they become effective immediately. The new solution uses the blockchain's
consensus algorithm to ensure data consistency and enhance trust. Finally, because no trusted
third party is required, the overall cost is reduced compared to the hub solution.
Figure 7: Innovative Solution provided by MNOs
© TM Forum 2019. All Rights Reserved. Page 18 of 54
CSP Use Cases Utilizing Blockchain
4. Identity as a Service
Another area of opportunity for service providers is the Identity as a Service (IDaaS) space. The
opportunity is visualized in Figure 8 below, starting from the current level 0 of simple
authentication, through level 1 of providing verified information, through the level 2 of fully
understanding the customer from objective data.
Figure 8: Identity as a Service (IDaaS)
Currently at level 0, social media apps compete with single-sign-on providers for the
authentication market. Similarly, because information is distributed across multiple systems of
record, it is difficult to provide a unified service at levels 1 and 2.
This situation creates an opportunity for service providers to work together with other public
organizations involved in trust, to provide IDaaS based on blockchain, as shown in the Figure 9
below. Such a service could uniquely leverage the assets of service providers in several ways:
1. Subscribers' existing mobile numbers can be used as the link between digital information
and real-world information.
2. Subscribers already trust service providers with registration that includes their real name
rather than a pseudonym.
3. Service providers are generally more trusted by their subscribers compared to other
potential providers of IDaaS.
© TM Forum 2019. All Rights Reserved. Page 19 of 54
CSP Use Cases Utilizing Blockchain
Figure 9: IDaaS Based on Blockchain
In the blockchain based IDaaS, a user first requests an institution to endorse and register their
information on the chat, with their privacy fully protected by the blockchain's unique feature
set. Third-party apps with appropriate permissions can authenticate and retrieve user
information using smart contracts, which will leave traceable records on the blockchain for
audit purposes. In this scheme each user controls their own data. The system also ensures
transparency by using a blockchain that is distributed across a consortium, not under the
control of a single organization.
© TM Forum 2019. All Rights Reserved. Page 20 of 54
CSP Use Cases Utilizing Blockchain
5. Roaming with Local Breakout Mode
Global roaming brings another blockchain related opportunity for service providers. Currently
most use a third-party service to change SIM information and register to the local network. A
blockchain based solution might allow roaming with local breakout mode to get all the
advantages of the current solution without its drawbacks.
Figure 10: Blockchain Based Solution – Roaming with local Breakout Mode
The Figure 10 above shows the typical current situation. There is no need to change the SIM,
and the subscriber can use local resources to achieve better QoS and less latency. However,
there is a trust problem in charging because it is performed by the local carrier (VPLMB) but
the home carrier needs a reliable means of validation (for example, service level statistics such
as IMS, Blackberry).
Figure 11: Blockchain to Support Trust in Charging Plan
© TM Forum 2019. All Rights Reserved. Page 21 of 54
CSP Use Cases Utilizing Blockchain
Figure 11 above shows one possible way that a service provider could use blockchain to create
a solution that supports trust in the charging plan. In the proposed solution, the visited carrier
saves real time charging data in a distributed ledger. Then consensus can be achieved between
the service provider, device, home carrier, etc. This solution also has the advantage that
permissioned blockchain ensures that sensitive data is only accessible by authorized
participants.
© TM Forum 2019. All Rights Reserved. Page 22 of 54
CSP Use Cases Utilizing Blockchain
6. Data Access Authorization
Service providers can also find opportunity in the field of data access authorization, in which
service providers frequently need to share data with consumers, often through an
intermediate agency. Figure 12 below summarizes the current approach to data access
authorization and contrasts it with a proposed approach based on blockchain.
The current process carries significant legal risk: it is difficult to clarify the various parties'
responsibilities in sensitive data transfer because the scope of authority is not clear for a given
piece of data. In multi-party cooperation, the service provider finds it difficult to maintain a
reliable data transfer record, and there is a high cost in verifying the demand from a data
consumer. Furthermore, once the data has been transferred, it is impossible for the sender to
ensure the data is used without abusing the scope of authority. For example, the receiving
company or its staff may engage in illegal activity, or the data could be leaked or hacked.
Figure 12: Current approach to data access authorization
In contrast, a blockchain based solution could remediate the above problems while providing
additional advantages (see Figure 13). In the solution detailed below, authorization is endorsed
by all participants. The service provider can validate the demand from the data consumer
easily with full non-repudiation. The service provider can also track and oversee the data
transfer flow between participants. This solution allows data transfer with high efficiency, but
with a lower cost of providing trust. Because of the distributed ledger, no single participant can
control the process, while the transfer process / history / log cannot be forged, denied nor
modified. The solution provides a trustworthy source of information for audit both internally
and externally. Lastly, the proposed solution achieves piece wise authorization for each
element of data that is transferred between participants. The authorization can cover content,
scope of authority / usage, duration of authority usage, responsibility of each participants, etc.
- providing much finer-grained control.
© TM Forum 2019. All Rights Reserved. Page 23 of 54
CSP Use Cases Utilizing Blockchain
Figure 13: A blockchain based solution to Data Access Authorization
© TM Forum 2019. All Rights Reserved. Page 24 of 54
CSP Use Cases Utilizing Blockchain
7. SLA Management
Service level agreements (SLAs) and related business processes have been exhaustively defined
by the TM Forum and other organizations, but still incur risk of litigation over significant sums.
Sources of risk include
Legal agreements that are discovered to be inconsistent, incomplete and/or incorrect
Processes that do not reflect legal agreements
Disagreements over the application of service level criteria and/or measurements
Long intervals between settlements leading to “bill shock”.
Given these longstanding issues with SLA management, and the high degree to which SLA
management use cases utilize blockchain features, as described in the Introduction, SLA
management was the first area of investigation for the blockchain sandbox. The demo
described here attempted to demonstrate the technical possibility of addressing the above
sources of risk with the following techniques:
Use computational law tools to ensure the validity of the legal contract and its mapping to
the smart contract
Use a blockchain to provide a shared, immutable record of criteria, measurements and
events as well as a platform for smart contracts
Use smart contracts running on a blockchain to automate the detection, assessment,
documentation, and settlement of SLA violations
Use token currency supported by a blockchain to make frequent, small settlements using
token micropayments
© TM Forum 2019. All Rights Reserved. Page 25 of 54
CSP Use Cases Utilizing Blockchain
Figure 14: Service Level Agreement (SLA) Management
The numbered call outs in Figure 14 above correspond to the steps of the demo:
1. Legal staff use a template to create a contract representing a service level agreement
(SLA), validate the contract using a computational law tool, and distribute it for electronic
signature.
2. Technical staff use the validated electronic contract and a smart contract template to
create a smart contract that will manage the execution of the previously defined SLA.
3. The SLA covers the availability of a Website as reported by a smart oracle. Pingdom, a
widely trusted company for this purpose, monitors the Website. The smart oracle uses the
Pingdom API as a trusted source of data.
4. The two parties to the SLA each place in escrow an amount of ether sufficient for worst-
case fulfillment of their contractual obligation. They then initiate the smart oracle and
smart contract.
5. The smart oracle reports the smart contract initiation to the SLA management system
using the TM Forum SLA Management API.
© TM Forum 2019. All Rights Reserved. Page 26 of 54
CSP Use Cases Utilizing Blockchain
6. The smart oracle sends the smart contract a message at previously agreed intervals. The
message contains the current up/down state of the Website.
7. The smart contract makes incremental micropayments from the escrow to one of the
parties at each predefined interval, based on the reported state of the Website.
8. The smart oracle reports violations to the SLA management system using the TM Forum
SLA Management API.
© TM Forum 2019. All Rights Reserved. Page 27 of 54
CSP Use Cases Utilizing Blockchain
8. Use Cases from the Blockchain Unleashed
Catalyst
The Blockchain Unleashed catalyst project explored five use cases of general interest to service
providers. This chapter of TR279 summarizes the findings of the catalyst for each use case,
followed by overall lessons learned. The use cases included:
1. Elimination of Call Detail Records (CDRs) for Billing, Settlement, and Fraud Detection
o CDR transaction details and roaming transaction details (TAP/NRTDE) are stored in
the blockchain in order to give complete transparency to internal applications. As a
result, settlement times are drastically reduced in case of roaming scenarios, in
addition to improving fraud detection.
2. Identity Management
o A blockchain solution is used to manage customer identities. A single customer ID
is digitalized and used to holistically identify and authenticate customers and
services/digital apps they are using, while having full control of their identity.
3. Service-Level Agreement (SLA) Monitoring
o With smart contracts used in a blockchain, automation and streamlining of
incident ticket SLA operations on blockchain are achieved.
4. Reducing Mobile Phone Thefts
o Service providers store the unique device or SIM data on the blockchain along with
the corresponding customer profile. With blockchain transparency, operators in
other countries are able to detect and track a stolen device by referring to the
blockchain record.
5. Mobile Number Portability
o A blockchain can be used to deliver transparency and immutable data from a
single source of truth, resulting in streamlining of the Mobile Number Portability
process across operators.
8.1. Elimination of Call Detail
Records (CDRs) for Billing,
Settlement, and Fraud Detection
CDRs are the foundation of processes that are essential to service providers' success: billing
customers for services provided, settling with other operators for services exchanged, and
protecting revenue by identifying fraudulent activity. Yet current CDR processes present
multiple challenges.
© TM Forum 2019. All Rights Reserved. Page 28 of 54
CSP Use Cases Utilizing Blockchain
8.1.1. Current process
When a call is placed, the Visiting Public Mobile Network (VPMN) queries Home Location
Register (HLR) of Home Public Mobile Network (HPMN) to find about users subscribed
services. Per availability or schedule, say multiple time a day or week (as per bilateral
agreement), VPMN sends a TAP file (with the CDR) to HPMN via Data Clearing House which is
responsible for transmission and conversion of TAP file. HPMN must settle accounts per costs
incurred with the VPMN in accordance with the roaming agreement tariffs (account settlement
between Roaming partner based as inter operator tariff (IOT).
Figure 15: Visiting Public Mobile Network (VPMN)
8.1.2. Challenges related to the current process
Current processes that use CDRs suffer from several issues:
Longer processing time due to time required for exchange of data between networks.
No real time visibility into the data.
Possibility of roaming fraud resulting in additional costs for roaming services.
Multiple disputes due to data mismatch.
Third party settlements are required.
These issues generate multiple challenges:
Costs incurred of fraudulent subscribers, resulting in inaccurate billing
When a fraudulent subscriber uses home network resources via the partner network, but
the home network can’t charge the subscriber. The home network still has to pay the
partner network for roaming services.
Time required to detect fraud results in longer settlement
Fraud occurs when the subscriber is not within the home network. The time required to
detect fraud is extended due to delays in the exchange of data between the home network
and partner network.
Since the fraud occurs outside of the home network, it takes a longer time to respond to it.
© TM Forum 2019. All Rights Reserved. Page 29 of 54
CSP Use Cases Utilizing Blockchain
8.1.3. Solution architecture
The catalyst solution uses a blockchain platform to provide a single source of truth in near real
time for all participating mobile networks, as shown in the Figure 16 below.
Figure 16: Elimination of CDRs: Blockchain solution architecture
8.1.4. New process based on the solution architecture
The solution uses smart contracts to allow the VPMN operator to generate charges, and to
calculate charges for the HPMN operator and forward to billing.
© TM Forum 2019. All Rights Reserved. Page 30 of 54
CSP Use Cases Utilizing Blockchain
Figure 17: Overview of Blockchain Network for Eliminating CDRs
8.1.5. Benefits of the new process
The new process provides near real time data availability to all participants in the network
resulting in:
Fast action on roaming data provided.
Automatic triggering of roaming contract enables near-real-time charging which reduces
roaming fraud.
Faster dispute resolutions through clear transaction history between operators.
Single source of truth is maintained to reduce multiple conversations between parties,
hence reducing disputes.
Cost savings from removing the data clearing house.
8.2. Identity
Management
The management of customers' identities and related data has been approached in multiple
ways, but issues with current methods remain.
8.2.1. Current process
A simple example of an identity management process is shown in Figure 18 below. For every
service a subscriber wants to use, it is required to register and create an ID with each vendor.
This requires each vendor to validate and store the subscriber ID, resulting in different
© TM Forum 2019. All Rights Reserved. Page 31 of 54
CSP Use Cases Utilizing Blockchain
customer PII and (personally identifiable information) customer usernames/passwords across
vendors.
Figure 18: Current Identity Management Process
8.2.2. Challenges related to the current process
Current identity management processes introduce several types of challenges:
Data security
o Personal Identity Information (PII) is stored across different websites/applications
or different subsidiaries. This can result in:
o Potential data hacks.
o Exploitation of PII by third-party entities.
o Multiple login usernames and passwords which are difficult to maintain and easily
forgotten by users.
o Passwords and PINs are increasing becoming an unsafe mechanism for
authentication.
o Printed PII is easily lost and difficult to replace, for example, ID and debit/credit
cards.
Verification processes
o Manual verification of PII is time consuming.
o Integrity of shared information to website/application can be questionable.
Customer experience
o Lack of convenience due to multiple usernames and passwords.
o Customers hesitant to use third party Single Sign On (SSO) for accessing new
vendors.
8.2.3. Solution architecture
The catalyst solution introduces a blockchain, implemented at a national level, containing
personal ID and related information. The blockchain is accessible to individuals to create and
maintain their information, and for authorized entities to access information for validation,
control, and processing purposes.
© TM Forum 2019. All Rights Reserved. Page 32 of 54
CSP Use Cases Utilizing Blockchain
Figure 19: Identity Management - Blockchain Solution Architecture
8.2.4. New process based on the solution architecture
Only one digital ID is maintained on the blockchain giving a single source of truth for all
participating companies.
8.2.5. Benefits of the new process
The new process provides several benefits in comparison with existing processes:
Know Your Customer (KYC) data including address proof, ID proof, photo and other
information can be mapped with the blockchain ID.
Ease of business and improved overall customer experience.
Cost savings from using a blockchain solution compared to a traditional Identity
management solution.
New revenue stream by offering Identity Management as a service (IDaaS) solution to
partners and consumers.
© TM Forum 2019. All Rights Reserved. Page 33 of 54
CSP Use Cases Utilizing Blockchain
8.3. Service-Level
Agreement (SLA)
Monitoring
The catalyst team found ample opportunities for improvement in the manner in which SLAs
are monitored and how related tasks and processes are managed.
8.3.1. Current process
The implementation of SLA monitoring processes in many service providers is labor-intensive
and error-prone:
Customer reports an incident to an operator.
Operator creates an incident ticket and assigns it to an internal investigation group.
Investigation group upon investigation responds that external vendor support is needed.
Operator creates a vendor task and sends it to vendor via email.
Vendor accepts and allocates the task.
Vendor troubleshoots and updates the task.
Vendor closes the ticket and notifies the operator via email.
Operator updates the ticket and confirms its resolution with the customer.
Customer will verify closure.
8.3.2. Challenges related to the current process
Processes like the above example give rise to a number of challenges of several categories:
Manual processes resulting in errors and delays in processing SLAs
o SLAs need to be manually reviewed and corrected.
o Delays in processing response from vendors due to manual processes requiring
email and phone not automated.
Disputes between vendors resulting in delays in payments
o SLAs from contracts need to be manually interpreted, potentially resulting in
different interpretations by vendors and service providers, causing disputes.
SLA ticketing system relies on manual ticket creation
o Emails to create/update tickets may not be reliable, can cause duplicate tickets
created.
o Full API ticket integration between service provider and vendor can be costly.
8.3.3. Solution architecture
The catalyst team implemented a solution based on a blockchain that supports smart contracts
and accessible only to the service provider(s) and vendors involved in SLAs.
© TM Forum 2019. All Rights Reserved. Page 34 of 54
CSP Use Cases Utilizing Blockchain
Figure 20: SLA Monitoring: Blockchain Solution
8.3.4. New process based on the solution architecture
The solution enabled a new process quite different from the typical current process:
1. A blockchain enables a smart contract or series of smart contracts that cater to the rules
put forward between the service provider and one of the service vendors.
2. SLA data and KPI rules are then managed by smart contracts on the blockchain.
3. When an incident ticket is raised, a smart contract triggers the SLA initiation in the system.
4. Smart contracts can further send real time notification to the involved parties.
5. Once remediation is completed, another trigger updates the status on the blockchain, and
a smart contract decides the SLA status as “good” or “bad”.
6. Based on the SLA status, the contract calculates charges or incentives and a payment is
issued accordingly.
8.3.5. Benefits of the new process
Real time transparency of data on the network, in addition to the SLA being monitored and
executed on the blockchain as one source of truth resulting in significant benefits:
Real time settlement and visibility.
o Vendor and Service provider see same SLAs.
o Reduced number of disputes between Vendors and Service Providers as both have
full visibility of SLAs.
Reduced settlement times due to:
© TM Forum 2019. All Rights Reserved. Page 35 of 54
CSP Use Cases Utilizing Blockchain
o Vendor engaged faster through blockchain.
o Updated SLA on closure is instantaneous.
o SLAs automatically calculated.
Significant reduction in the cost of SLA monitoring due to reduced time to implement and
manage SLAs.
8.4. Reducing Mobile
Phone Thefts
Theft of mobile devices continues to be a serious problem worldwide, partly because current
processes are inadequate in response and prevention, motivating the catalyst team to propose
a new solution and process.
8.4.1. Current process
The current process, illustrated in Figure 21 below, introduces significant delays at every step:
Figure 21: Reducing Mobile Phone Threats
8.4.2. Challenges related to the current process
The current manual process carries with it a number of challenges:
Manual process steps result in errors and delays
o The blocking of a device is not instantaneous and can only be performed by the
owner´s operator.
o Update of the global database is based on files sent periodically (daily) by the
owner´s operator to a global database, for example, GSMA.
The process is reliant on consistent operator global database across operators
© TM Forum 2019. All Rights Reserved. Page 36 of 54
CSP Use Cases Utilizing Blockchain
o Blocking in a given country is guaranteed only if the operator has downloaded the
latest updated global database, for example, from GSMA.
8.4.3. Solution architecture
The catalyst solution is based on a global blockchain accessible to participating service
providers, as illustrated in Figure 22 below.
Figure 22: Reducing Mobile Phone Threats: Blockchain Solution Architecture
8.4.4. New process based on the solution architecture
The new process uses the solution to enable a much greater degree of automation and
coordination:
1. Subscriber data along with the device information is put on the blockchain by all operators
in a country.
2. The device unique ID, IMEI, is mapped to a user and a hash of this data is uploaded to the
blockchain.
3. If the device is stolen, the subscriber or operator uploads the First Investigation Report
(FIR) on the blockchain.
4. When a call is made from this device in other country, the local operator picks up the
unique ID of the device and checks the details on the blockchain.
5. If a matching FIR is found, the local operator blocks the device and updates its location on
the blockchain
6. An alert is sent to the original operator via the blockchain.
8.4.5. Benefits of the new process
The new process provides significant benefits in contrast to the old manual process:
Immediate blocking of a reported stolen device within the blockchain is now possible.
Multiple agents connected to the blockchain are able to report stolen devices for blocking.
Agents different than owner's operator (provided authorization to update the chain) can
block a device.
Smart contracts allow third parties to be instantaneously informed of any change of status
of a device.
© TM Forum 2019. All Rights Reserved. Page 37 of 54
CSP Use Cases Utilizing Blockchain
8.5. Mobile Number
Portability (MNP)
Although the concept of mobile number portability has been implemented since 1999, MNP
processes are ripe for improvement, and the catalyst team devised a blockchain-based
solution that addressed current challenges.
8.5.1. Current process
A typical MNP process is illustrated in Figure 23 below. Customers request ports via their
destination provider, which must communicate with the home provider, update its local copy
of the MNP database, and provide updates to the central database. Those communications
involve multiple interactions with serious timing implications. At the same time, each
provider's local database must be synchronized daily the master database.
Figure 23: Mobile Number Portability (MNP)
8.5.2. Challenges related to the current process
The current process suffers from problems related to its semi-manual implementation and its
reliance on database consistency:
Manual process steps result in errors and delays.
o Requests are rejected due to data mismatch between operators.
o High processing time are incurred in some countries.
The current process is reliant on consistent operator Global Database across operators.
o A central database of portable numbers is a single point of failure.
o Delays in processing occur due to periodic updates required of the local database
from the central database.
© TM Forum 2019. All Rights Reserved. Page 38 of 54
CSP Use Cases Utilizing Blockchain
8.5.3. Solution architecture
The catalyst solution, illustrated below in Figure 24, is based on a blockchain that is accessible
through an application layer to members of a national consortium of service providers.
Figure 24: Mobile Number Portability: Blockchain Solution
8.5.4. New process based on the solution architecture
The catalyst solution supports a new process that is more streamlined and less error-prone
than the current process:
1. A subscriber sends a request to the move operator to his/her Home Service Provider for
number portability.
2. The Home Service Provider in return provides Porting Authorization Code (PAC) or Unique
Porting Code (UPC) to subscriber.
3. The subscriber uses this code and submits request to the Destination Service Provider (the
recipient telecom provider).
4. The Destination Service Provider sends a request to the Home Service Provider for
clearance.
5. The Home Service Provider “accepts” or “rejects” request.
6. Once clearance is done, the Destination Service Provider submits request for routing
update.
8.5.5. Benefits of the new process
The new process confers several significant benefits:
© TM Forum 2019. All Rights Reserved. Page 39 of 54
CSP Use Cases Utilizing Blockchain
The distributed ledger eliminates the possibility of a single point of failure, as all service
providers have access to the same data.
Delays in the process are eliminated as a real time view is provided by the blockchain.
Frequent updates of the local database from the central database are no longer required
All participants in the blockchain have access to the latest records.
Portability records are maintained with hassle-free operations.
8.6. Key Learnings
The catalyst team published several lessons learned, which are reproduced below.
8.6.1. Due to limitations with blockchain’s processing capabilities, we have to be careful
when determining what processes and data should be placed in the blockchain.
Challenges:
Not all business rules/logic could be placed in the chaincode. Some of the business
rules/logic had to be taken off chain and built on the application layer with heavy
consideration
Larger block sizes can hold more data in the blockchain; however, it’ll take longer time to
process each block.
Calls to action:
Accelerate further research should be done to unearth blockchain capabilities and use
cases which support real world workloads.
Implementation teams should further assess when to have the logic or data on or off the
blockchain.
8.6.2. Due to technology limitations today, there’s no efficient way to create digital rules
and logic from legal documents which can be incorporated into the blockchain.
Challenges:
There is no automated way to convert existing business logic or legal contracts into
blockchain readable snippets of code (a.k.a. smart contracts/chain code)
Although these smart contracts may be created manually, no automated way to calibrate
or configure them exist.
Calls to action:
Research should be continued together with research firms to accelerate the study and
PoC to be able to adopt blockchain as an avenue for mechanization (e.g. Stanford
University’s research on blockchains adoption for computational law).
8.6.3. Lack of standards in implementing blockchain leads to inconsistencies in
development and implementation.
Challenges:
Implementing blockchain became a reactive, trial and error approach where the nodes,
chaincode, business logic, and data storage vary even in similar use cases.
© TM Forum 2019. All Rights Reserved. Page 40 of 54
CSP Use Cases Utilizing Blockchain
Different companies may come up with standards of their own which may lead to
blackboxing blockchain solutions.
Calls to action:
Accelerate further research within and across blockchain alliances to unearth the full
potential of blockchain.
Create industry-wide standards in blockchain capabilities, business logic implementation,
smart contract mapping, data storage, and all other future capabilities.
© TM Forum 2019. All Rights Reserved. Page 41 of 54
CSP Use Cases Utilizing Blockchain
9. Use Cases from the Blockchain based Telecom
Infrastructure Marketplace Catalyst
9.1. Business Scenarios
CSPs know they will face a huge CAPEX issue in the coming years (CAPEX will increase 60%
[2020-2023] according to McKinsey & Company, White paper 2018).
Therefore, reducing dramatically deployment cost (Zero-Capex model) as well as Energy
consumption (expected to be 3 times for 5G) becomes key objective. Besides, mobile traffic
growth is continuous. In this regard, CSPs shall bring 5G Mobile Access Networks closer to
Users (Country, City, White Zone, Stadium, Factory 4.0, Enterprise) to meet requested 5G
eMBB, uRLLC, and mMTC services.
CSPs seek new Telecom Infrastructure and Energy Sourcing, Deployment and Investment
models to overcome this Challenge.
Global small cell 5G network market valued USD 381 million in 2018; USD 3,495 million by
2025; CAGR of 37.2% between 2019 and 2025 (Source Zion Market Research)
CSPs would like to order 5G passive infrastructures made available by some actors to allow
sourcing On Demand-basis (e.g. under Auction-based model) rather than under traditional
costly renting model to perform some Network Mobile Network deployment scenarios
Potential real use cases
The flexible passive infrastructure may be ordered for reinforcing existing
infrastructure during a temporary event at a crowded location: to ensure connectivity
of a stadium, coverage of a white area, or a country for a given period (e.g. 5G, RAN
Sharing)
More precisely, CSP would like to automatically Discover, Query & Find in a “Passive
infrastructure” Marketplace the frequency, the cell (e.g. high altitude platforms, WiFi
Access Point), the passive infrastructure (e.g. Tower co), the backhaul (flexible satellite
connection) for such dedicated purpose and need
To move away from traditional costly Make / Buy / Rent models of Mobile Network
Resources to an Auction-based model that is more efficient and transparent and most
appropriate for such use cases
The Catalyst is exploring Blockchain-based Telecom Infrastructure & Energy Marketplace as a
potential promising solution
9.2. Asset Marketplace
9.2.1. Current Assets Marketplace process
Asset Providers need to describe their assets using some well-known format
Asset Providers need to advertise their asset on a proprietary platform (marketplace)
© TM Forum 2019. All Rights Reserved. Page 42 of 54
CSP Use Cases Utilizing Blockchain
Asset Providers need to approach possible Service Providers and drive their attention to
their platforms (marketplace)
Service Providers need to visit different proprietary platforms (marketplaces) to identify
required assets
Service Providers need to identify most suitable assets and prepare one or multiple offers,
according to the rules of the given selected platform (marketplace)
Asset Providers need to manually review offers and select best ones
Service Providers need to perform payments for different assets using the different
systems present on each considered platforms (marketplace)
Asset Providers need to manually clear orders with auditors
9.2.2. Challenges of existing Asset Marketplaces
Asset offers are posted on different platforms (marketplaces)
Service Providers need to post requests on different platforms
Complexity of asset discovery increases, and the best assets might be missed
Selection of asset requests is done manually
Delay and complexity of selection reduce asset providers’ ROI
Asset payments are done using different systems
Service Providers need to set up and manage different accounts with increased
overhead and costs
Clearing of usage agreements is done manually
Usage agreement clearing is delayed for regulated assets
Auditing integration of APIs for different marketplaces and platforms is costly and
complex
9.2.3. Assets Marketplace: Blockchain Solution
● A transparent open marketplace for posting of asset offers, requests, automated
matching and payments settlement with a tamper-proof audit trails resulting in:
● Real-time asset offers and requests discovery, and optimal asset matching
● The maximization of ROI for Asset Providers and best asset selection for Service
Providers
● A unique payment system to speed up asset access
● An easy-to-review audit trail and fast usage agreement clearing for auditors
● Reduced settlement times due:
● Asset and Service Providers engage through a trusted block chain-based infrastructure
● Payment performed using interoperable cryptocurrency
© TM Forum 2019. All Rights Reserved. Page 43 of 54
CSP Use Cases Utilizing Blockchain
● Immutable and trusted audit trails accessible in real-time
● Significant reduction in the cost of advertising and searching for required assets due
to the reduced time to integrate with a unique marketplace
9.2.4. Generic Blockchain-based Marketplace: proposed 5G deployment Scenarios
Scenario 1: Energy Marketplace
Scenario 2: 5G Cell Re-enforcement /Densification through Telecom Infrastructure
Marketplace
Scenario 3: 5G Cell Re-enforcement / Densification through Telecom Infrastructure
Marketplace (extended to Energy as asset)
Scenario 4a: 5G Cell Re-enforcement / Densification through Telecom Infrastructure
Marketplace and Energy Marketplace - cooperation between two Marketplaces (Terms
and conditions / Smart Contract between the two Marketplaces to be defined
Scenario 4b: Initial 5G Country / City / White Zone / Stadium Cell deployment and Re-
enforcement / Densification through Telecom Infrastructure Marketplace and Energy
Marketplace - cooperation between two Marketplaces (Terms and conditions / Smart
Contract between the two Marketplaces to be defined
9.3. Energy Marketplace Use Case
In this marketplace, we have four types of actors:
- Energy providers
- Energy consumers
- Energy consumers and producers
- Service providers whose equipment requires energy.
The actors that act as energy providers can declare assets in the marketplace, and also offers
based on these assets (the attributes of an asset being a quantity, a price, a location, a start
date and a finish for its availability).
The actors that act as energy consumers can post requests for energy.
Then the marketplace proposes matches between offers and requests according to the
following process:
Step1: find all offers satisfying the following requirements
Offered unitary price <= Requested unitary price
Offered begin Timeslot <= Requested beginTimeSlot
Offered endTimeSlot >= Requested endTimeSlot
Offered location = Requested location
Step2: Select offers according to a defined policy
Criterion 1: Price Finding the offer with the lowest price
© TM Forum 2019. All Rights Reserved. Page 44 of 54
CSP Use Cases Utilizing Blockchain
Criterion 2: Quantity Satisfying quantity (i.e., Qoffer(s) >=Qrequest)
Criterion 3: Publication date Buying the older offer(s)
The Policy is: Buying from one/many producers (the older offers with the lowest prices that
their Qoffer sum satisfies Qrequest).
Once matching proposals have been done, consumers have to accept one, and once this has
been done, the corresponding transaction is recorded in the marketplace Blockchain.
9.4. 5G Cell Re-enforcement /Densification
through Telecom Infrastructure Marketplace
This scenario addresses the following top 6 requirements:
1. Continuous Coverage Improvement
2. Spectrum Efficiency
3. Continuous Capacity Enhancement
4. Energy Efficiency
5. Lowering Backhaul cost
6. Delivery of 3 network Slices (eMBB, uRLLC, mMTC)
9.4.1. Macro design
The figure below depicts this scenario. This scenario is a Blockchain-based Telecom
Infrastructure Marketplace only, the Energy is not considered as an asset in this Marketplace.
The left-hand side corresponds to the Blockchain-based Telecom Infrastructure Marketplace
with its actors and their interactions (transactions).
Figure 25: 5G Cell Re-enforcement /Densification through Telecom Infrastructure Marketplace
© TM Forum 2019. All Rights Reserved. Page 45 of 54
CSP Use Cases Utilizing Blockchain
9.4.2. Actors and roles involved in this scenario
The table below lists the Actors and associated roles involved in this scenario. It
describes the roles of each actor.
Actors Roles example
Service Provider Provide a telco service (and declared as a telco e.g. Telco
service provider to a regulation authority)) operators such as
Orange,
- order a flexible infrastructure (the whole
Vodafone, …
infrastructure or only some component)
- Exchange token for the infrastructure, thanks to
its services revenues, to the different owners of
the infrastructure.
- May be sponsors for the infrastructure (provide
data analytics of UE connectivity with the 3 rd
party)
Infrastructure Own a physical infrastructure residential
Provider customer
Offer a physical infrastructure for a location to
(femto), airport
deploy a type of antenna within a type of
infrastructure (aerial (balloon, drone) terrestrial
(tower, building, home, billboard) for an area, a
location, a type of coverage (indoor, outdoor), for
a characteristics of an antenna (length, width,
height, weight) and for a date with different
options
- electricity
- guard service
- level 1-2 management (basic management:
on/off, cell replacement)
The location offer must be authorized by the
regulatory authority if it is required (outdoor
coverage).
Cell service - install a cell within an infrastructure Telco vendors
provider (such as Nokia),
- manage a programmable cell
Vertical
Offer the management of a cell for a type of
frequency, a power, a tilt, within an area and a
location, for a date.
The offer must be authorized by the regulatory
authority if it is required (outdoor coverage).
Note A cell provider may also offer the
infrastructure.
Regulator/Audito Provide the authorization to operate an Telco Regulator
r infrastructure, a cell or a frequency for a type of
service (e.g. mobile service, fixed service) if
required.
© TM Forum 2019. All Rights Reserved. Page 46 of 54
CSP Use Cases Utilizing Blockchain
Actors Roles example
Verify the installation of the Telecom
infrastructure by auditing the transactions stored
in ledgers (power, location, tilt, service, …)
Frequency Owner of a spectrum band (PMR, Satellite television
provider provider, Fixed Wireless Access) which could be spectrum,
proposed for (mobile or fixed providers) services
new auction
providers with regulatory authorization, if any.
spectrum (e.g.,
Or it could be used to share the management of microwave
an unlicensed spectrum to avoid interference such frequencies),
as WiFi Access point in a mall. satellite
operators
Offer a spectrum band (e.g. Wi-Fi canal number)
within an area, a location, a date, the power
associated and the type of frequency (e.g.
unlicensed, licensed).
Wholesale Connect the cell to the service provider Satellite
Connectivity infrastructure. providers,
provider Orange/Vodafone
Offer the connectivity of a cell within a location,
an area, a date, a type of connectivity (XDSL,
fibber (WDM PON), Satellite) the SLA should
provide some KPI (e.g. up/down throughput,
packet loss rate, data volume up/down)
3rd party The third party sponsor the infrastructure for an Fund Provider
area which it could monetized (e.g. a mall, airport)
with advertisement)
On demand Manage the Auction-based model transaction DLT
infrastructure
Marketplace /
Broker
Figure 26: Actors and Roles involved in Blockchain based Telecom Infrastructure Marketplace
9.4.3. Smart Contract Inventory
Different smart contracts may be used to manage the different transactions of a Telco
Infrastructure marketplace. Smart contracts should be used i) to automate and secure
transaction and ii) to provide traceability of the overall Telco infrastructures between those
different partners since each transaction is stored in an architecture based on Distributed
Leger Technology. Finally, the transactions are stored in a secured distributed ledger. The
lifetime of a smart contract is thus saved. A smart contract execution is composed of 3
successive tasks:
1) Execution environment verification: the smart contract verifies the validity of the identity of
the different actors for a given transaction. It verifies also the solvency of each financial
account of the partners for a financial transaction, by reading previous financial transactions.
© TM Forum 2019. All Rights Reserved. Page 47 of 54
CSP Use Cases Utilizing Blockchain
It may stop the execution of the contract in case the environment is no longer trusted, or
conditions are not met.
2) Terms and Process execution as described in the smart-contract (e.g.
creation/offer/request/order). The smart-contract may request or deliver services through API
of a BSS service portal of a partner which executes the process.
3) Transaction generation with the key performance indicators (KPIs) of the good execution of
a process. In case of financial transitions, the smart contract will also exchange financial token
associated to the transaction if the KPIs related to the contract are respected.
9.4.4. Details workflows
The figure below depicts the workflows between actors of the Blockchain-based
Telecom Infrastructure Marketplace.
Passive
Frequency Cell Connectivity Regulator Service 3rd party
Infrastructure Auditor
Marketplace
provider Provider provider Provider Provider sponsor
Offer Spectrum (frequency band, location, date, LAC, cellID…)
Offer infrastructure ( location, date, indoor/outdoor type:aerial/building)
Offer Cell (type(outdoor/indoor antenna); frequency(wifi, 3G,4G,…);location, date)
Offer Connectivity (access type, quality, bandwidth, location, date)
Offer sponsor (location, date, $)
Search infrastructure(location, date, spectrum, )
infrastructure matches([Link] $; [Link] $; [Link] $; [Link] $, [Link] $)
infrastructure selected (); sponsor selected()
Configure selected infrastructure (management cell ID lists location)
Configure selected Cell(frequency ():service porvider id (APN); SON services)
Onboard sponsor (location, date, $)
Selected frequency (channel bandwdth reserved)
Validation and acceptance
infrastructure available
Activate sponsoring process
SLA assurance (KPI; $, availability period)
SLA monitor
Figure 27: Workflows of Blockchain based Telecom Infrastructure Marketplace
9.5. 5G Cell Re-enforcement / Densification through Telecom
Infrastructure Marketplace (extended to Energy as asset)
This scenario addresses the following top 6 requirements:
1. Continuous Coverage Improvement
2. Spectrum Efficiency
3. Continuous Capacity Enhancement
4. Energy Efficiency
5. Lowering Backhaul cost
6. Delivery of 3 network Slices (eMBB, uRLLC, mMTC)
The figure below depicts this scenario. This scenario implies the only a Blockchain-based
Telecom Infrastructure Marketplace. The Energy is considered as an asset in this Marketplace.
© TM Forum 2019. All Rights Reserved. Page 48 of 54
CSP Use Cases Utilizing Blockchain
Figure 28: 5G Cell Re-enforcement / Densification through Telecom Infrastructure Marketplace
(extended to Energy as asset)
9.6. 5G Cell Re-enforcement / Densification through Telecom
Infrastructure Marketplace and Energy Marketplace
Cooperation between two Marketplaces (Terms and conditions / Smart Contract between the
two Marketplaces to be defined)
This scenario addresses the following top 6 requirements:
1. Continuous Coverage Improvement
2. Spectrum Efficiency
3. Continuous Capacity Enhancement
4. Energy Efficiency
5. Lowering Backhaul cost
6. Delivery of 3 network Slices (eMBB, uRLLC, mMTC)
The figure below depicts this scenario. This scenario implies a cooperation between two
Marketplaces (Terms and conditions Smart Contract) Blockchain-based Telecom Infrastructure
Marketplaces and Blockchain-based Energy Marketplaces
© TM Forum 2019. All Rights Reserved. Page 49 of 54
CSP Use Cases Utilizing Blockchain
Figure 29: 5G Cell Re-enforcement / Densification through Telecom Infrastructure Marketplace and
Energy Marketplace
9.7. Initial 5G Country / City / White Zone / Stadium Cell
deployment and Re-enforcement / Densification through
Telecom Infrastructure Marketplace and Energy Marketplace
Cooperation between two Marketplaces (Terms and conditions / Smart Contract between the
two Marketplaces to be defined)
This scenario addresses the following top 6 requirements:
1. Continuous Coverage Improvement
2. Spectrum Efficiency
3. Continuous Capacity Enhancement
4. Energy Efficiency
5. Lowering Backhaul cost
6. Delivery of 3 network Slices (eMBB, uRLLC, mMTC)
The figure below depicts this scenario. This scenario implies a cooperation between two
Marketplaces (Terms and conditions Smart Contract) Blockchain-based Telecom Infrastructure
Marketplaces and Blockchain-based Energy Marketplaces.
© TM Forum 2019. All Rights Reserved. Page 50 of 54
CSP Use Cases Utilizing Blockchain
Figure 30: Initial 5G Country / City / White Zone / Stadium Cell deployment and Re-enforcement /
Densification through Telecom Infrastructure Marketplace and Energy Marketplace
© TM Forum 2019. All Rights Reserved. Page 51 of 54
CSP Use Cases Utilizing Blockchain
10. Appendix A: Terms & Abbreviations Used within
this Document
10.1. Administrative
Appendix
This Appendix provides additional background material about the TM Forum and this
document. In general, sections may be included or omitted as desired; however, a Document
History must always be included.
10.2. Document History
10.2.1. Version History
Version Date Modified Modified by: Description of changes
Number
1.0.0 December John Wilmes Initial Release of this document
2017
1.0.1 December Adrienne Walcott Formatting/style edits prior to publishing
2017
2.0.0 June 2018 John Wilmes Added Billing to Use Case Categories in
section 1.4
Added section 8 containing findings from
Blockchain Unleashed catalyst
2.0.1 20-Jun-2018 Adrienne Walcott Formatting/style edits prior to publishing
2.0.2 21-Aug-2018 Adrienne Walcott Updated to reflect TM Forum Approved
status
3.0 02-Jun-2019 Gnanapriya Added Section 9, to cover new set of use
Chidambaranathan cases and findings from ‘Blockchain based
Telecom Infrastructure Marketplace’ catalyst
3.1 19-Jun 2019 Tayeb Ben Meriem, Update Section 9 and Catalyst team
approval;
3.1 08 Aug 2019 Nancy Lyness Collaboration Team Approved
3.1.1 29 Nov 2019 Adrienne Walcott Updated to reflect TM Forum Approved
Status
© TM Forum 2019. All Rights Reserved. Page 52 of 54
CSP Use Cases Utilizing Blockchain
10.2.2. Release History
Release Date Modified by: Description of changes
Number Modified
R17.5 December Initial Release of this document
2017
R18.0.0 June 2018 Added Billing to Use Case Categories in
section 1.4Added chapter 8 containing
findings from Blockchain Unleashed catalyst
R18.0.1 21-Aug-2018 Adrienne Walcott Updated to reflect TM Forum Approved
status
Pre-Production 08 Aug 2019 Nancy Lyness V 3.1 Collaboration Team Approved
Production 29 Nov 2019 Adrienne Walcott Updated to reflect TM Forum Approved
Status
10.3. Company Contact
Details
Company Team Member Title Email
10.4. Acknowledgments
The 3.0 version of this document was prepared by Gnanapriya Chidambaranathan utilizing the
contribution from the Blockchain based Telecom Infrastructure Marketplace Catalyst which
exhibited at DTW Nice 2019. The Marketplace blockchain use cases are described in Section 9.
Catalyst champions and participants contributing to the use cases include:
Tayeb Ben Meriem, Orange Shanthi R, Infosys
Benoit Radier, Orange Mark Nixon, IOTA
Philippe Genestier, Orange Michele Nati, IOTA
Atul Purohit, Vodafone Anand Adhiappan, Nokia
Gnanapriya Chidambaranathan, Infosys Umut Karabudak, Nokia
Luxman Seshadri, Infosys Thomas Spencer, R3
© TM Forum 2019. All Rights Reserved. Page 53 of 54
CSP Use Cases Utilizing Blockchain
The 2.0 version of this document was prepared by John Wilmes utilizing the contribution from
the Blockchain Unleashed Catalyst which exhibited at DTW Nice 2018. The five blockchain use
cases are described in Section 8. Catalyst champions and participants contributing to the use
cases include:
Adam De Linde, Orange Gnanapriya Chidambaranathan, Pavan Toor, Deloitte
Infosys
Alan McNamee, Opennet Jerome Pons, Orange Piyush Sarwal, IBM
Alexander Roca, Globe Julius Aribon, Globe Pete van Velden, Ultrafast
Amandeep Singh, IBM Karthikeyan Shanmugam, Infosys Prasad DLN, Infosys
Andrea Cerritelli, Fastweb Kevin John Lee, Globe Russell Sassoon, Deloitte
Andreas Manolis, BT Luis Velarde, Telefonica Sean McMenamy, Opennet
Anthony Symons, Optus Luxman Seshadri, Infosys Takuya Kato, KDDI Research
Atul Purohit, Vodafone Mark Collins, Openet Tayeb Meriem, Orange
Declan Buckley, Opennet Mark Wall, IBM Vincent Seet, Globe
Felisa Xu Cheng, Vodafone Michael Recabar, Globe Vishwas Chine, Infosys
Frederic Desnoes, Orange Ng Soo Kee, Singtel YuYa Minami, KDDI Research
Gerry Donohoe, Openet
This original version of this document was prepared by John Wilmes utilizing input and
discussion from 2017 TAW Vancouver meeting participants at the Blockchain Working Session.
Meeting Attendees included:
Baljit Sarpal, Sarpal Emmanuel A. Frank Grasic, Huawei
Consulting Otchere,Huawei
Hugo Vaughan, Crowdframe Ruinan Sun, Huawei Qiuling Pan, Huawei
Mathieu Paris - Arseneault, Qiuling Pan, Huawei Rajshree Char, Ericsson
Videotran
Ke Zhang, China Telecom Amira Obradovic, Telus Luis Bras, Wedo
Norihiro Fukumoto, KDDI [Link]@mycom- Rajesh Karunamurthy, Telus
[Link], Mycom OSI
Tomohiro Otani, KDDI JUNKO IWASAKI, NEC John Wilmes, TM Forum
Abinash Vishwakarma, Guillermo Martínez, nsuri@[Link]
Netcracker Telefonica
Gene Glaudell, Gn0man Mark Geere, Huawei Thandi Demanet, TM Forum
© TM Forum 2019. All Rights Reserved. Page 54 of 54