Page tree
Skip to end of metadata
Go to start of metadata
TitleIoT and DLT in a telecom multi carriers architecture






GSMA during 2019 is planning to investigate the characteristics and behavior of DLT for IoT applications that utilize mobile connectivity. The idea is to gain a better understanding of the benefits of using DLT and how some of the challenges of IoT, where there are a lot of stakeholders involved, can be bridged. GSMA is also looking at the interoperability with other DLT technologies. One example could be in relation to device identity, or validation of the installed firmware/software. In general, we are not looking to store actual data produced by the devices, due to privacy and data protection laws (i.e. GDPR).


By 2020, there will be over 24 billion connected devices, which are equipped with sensing and actuating capabilities. Obviously, considering billions of people, trillions of IoT devices, and innumerable data resources,

The Internet of Things aims at connecting every entity ranging from

  • individuals (human beings),
  • collectives (homes, organizations, companies, etc.)
  • to things such as objects from physical and cyber worlds

The 3 major characteristics of IoT are mobility, scalability, interoperability that play at three different levels/layers: identity, connectivity and application.

Blockchain and trusted identities enable the true potential of IoT

Current needs:

  • Trusted IoT identities: enabling connection or communication among entities
  • Scalable connectivity
  • Interoperability of apps

The solutions:

  • Cryptographically secured identity
  • Autonomous provisioning
  • Decentralization

Existing identity management systems on the Internet cannot be directly transplanted to IoT environments due to native IoT characteristics and needs such as scalability, trustless, interoperability, mobility, security and privacy

Even though many promising solutions (i.e., blockchain-based identity management and socialized IoT paradigm) are proposed, other critical supporting components of building effective IdMS for IoT remain challenges such as access controls, privacy, trust and performance.

Task 1: 1º PoC

Using Indy to building up an IdM system taking into account the needs of an IoT architecture (mobility, scalability and interoperability) and challenges (access control, privacy, trust and performance).

a - proving basic feasibility and viability

b – proving feasibility with a real system and providing viability

Task 2:

Identify the metrics to measure the performance & scalability of a decentralized IdM for IoT

Task 3: 2º PoC

a - proving scalability to bi- parties (2 carriers) and a large amount of data

c- proving privacy and confidentiality in bi- parties (2 carriers) environment

d- exploring integration with different types of data & contract types

Additional Information

Learning Objectives

  • Participating and contributing to an open-source project
  • Collaborating with other developers over common open-source communication and collaboration tools. / calls / chat / mailing list
  • Understanding IoT applications and architecture
  • Applying self-sovereign Identity concepts to IoT
  • Governance and economics of a cross-carrier IoT network blockchain-based
  • Smart contracts
  • Scalability and performance IoT metrics  

Expected Outcome

  • Developing a PoC of two carriers through Indy
  • Contribute to the Performance and Scalability GIS adding IoT metrics

Relation to Hyperledger 

  • Hyperledger Indy, Telcom GIS 

Education Level

Master’s or Phd


The project mainly focuses on Hyperledger Indy. The project will also showcase how Hyperledger projects can be utilized to enable an important Telecom use case.

  • Familiarity with Blockchain (Hyperledger) and the concept of Self Sovereign
  • Familiarity with IoT applications and networks
  • Experience with Node.js, AngularJS
  • Knowledge of programming/scripting language such as Python.
  • Be a proactive and self-learner, comfortable with dynamic/asynchronous e-mails and exchange of ideas

Future plans

Task 3: 3º PoC

  • a - proving scalability to multiple parties (carriers) and a large amount of data
  • b- proving the feasibility and commercial viability of multiple parties (carriers) platform

Preferred Hours and Length of Internship

Full-time (20 hours a week for 12 weeks during the summer)

Mentor(s) Names and Contact Info

Laura Spinaci;