Log In Sign Up

DICE: Dynamic Interconnections for the Cellular Ecosystem

To enable roaming of users, the cellular ecosystem integrates many entities and procedures, including specific infrastructure to connect Mobile Network Operators (MNOs), business partnerships or the use of third-party Data Clearing Houses (DCHs) for billing. Many of these rely on specifications rooted in dated and arcane practices, involving long waiting periods for financial clearing, complex billing models, and disparate mechanisms for dealing with inter-MNO disputes. In this paper, we propose a novel solution, DICE (Dynamic Interconnections for the Cellular Ecosystem), aimed at facilitating dynamic collaboration between MNOs, and sustain fluid interconnection models between the end-users and MNOs. DICE uses distributed ledger technology (DLT) to enable MNOs to interact directly, and offer customizable services to their users through the use of crypto-currencies. We leverage real-world data from a major operational MNO in Europe to support our claims, and to extract the requirements for the DICE system. We introduce the DICE protocol, and discuss real-world implementation considerations.


page 1

page 2

page 3

page 4


Blockchain-Enabled NextGen Service Architecture for Mobile Internet Offload

The amalgamation of different generations of mobile cellular networks ar...

The Untold Secrets of Operational Wi-Fi Calling Services: Vulnerabilities, Attacks, and Countermeasures

Since 2016, all of four major U.S. operators have rolled out nationwide ...

Community-Based Service Ecosystem Evolution Analysis

The prosperity of services and the frequent interaction between services...

LightAutoML: AutoML Solution for a Large Financial Services Ecosystem

We present an AutoML system called LightAutoML developed for a large Eur...

Knowledge-driven Data Ecosystems Towards Data Transparency

A Data Ecosystem offers a keystone-player or alliance-driven infrastruct...

DICE: Automatic Emulation of DMA Input Channels for Dynamic Firmware Analysis

Microcontroller-based embedded devices are at the core of Internet-of-Th...

1. Introduction

Roaming is one of the fundamental features of cellular networks. It enables clients of one MNO to use the network of another MNO when traveling outside their provider’s area of coverage. To support roaming, partnering MNOs must have a commercial agreement in place, and a technical solution for exchanging signaling and voice/data traffic. Despite the fast evolution of cellular technology over the past decades, this logic has remained largely unchanged. Even more, the associated platforms and systems are opaque, and little innovation has gone into this area. The advance of the inter-provider charging system is especially challenging, as it requires standardization, and subsequent joint evolution and deployment in the networks involved. This is inefficient, as the current inter-provider charging system for roaming services imposes penalties in terms of performance, operational costs and business revenues (15).

In this paper, we propose DICE (Dynamic Interconnections for the Cellular Ecosystem), a novel framework for dynamically establishing roaming agreements between MNOs, and enabling almost real-time financial clearing for roaming services through secure and private transfer of crypto-currencies. Most MNOs today choose to outsource to a DCH for end-to-end roaming operations management, including data collection, clearing and cash settlement, although it is possible to do this on a peer-to-peer basis. Even with DCH, the charging settlement between MNOs remains a slow and tedious procedure (i.e., monthly or yearly for roaming partners with little traffic) and disputes are largely handled case-by-case. Based on real-world data from an MNO in Europe, this is a significant challenge for operators, which are grappling to remain relevant in an otherwise fast evolving landscape (Shaun Kennedy, ). When analyzing the business interactions, MNOs have reported major revenue leakage, mainly because of incomplete customer records, accumulated roaming records, debt write-off and fraud. This issue is imperative, as support for “things” roaming internationally (e.g., connected cars, logistics and wearables) is critical for IoT verticals. Taking advantage of international mobile roaming, IoT platforms can offer more stable connectivity/coverage services to IoT verticals. In this context, there is a stringent need for MNOs to develop sustainable strategies for next-generation interconnections to remain relevant.

The purpose of DICE is to allow MNOs to exchange value easily, without the need of a third party to act as a trusted intermediary, to verify the interaction between the roaming partners. With DICE, MNOs can avoid the need for using a DCHs and instead leverage the potential of Distributed Ledger Technology (DLT) and tokens to retrieve revenue from their roaming partners.

The current business logic around MNO interworking for roaming has further implications in the communication performance. The intrinsic lack of trust between the Home Mobile Network Operator (HMNO) and the Visited Mobile Network Operator (VMNO), and the unwillingness of the former to expose to a foreign operator charging information for their users makes home-routed roaming (HR) roaming the default roaming configuration. Recent measurement studies confirmed that majority of MNOs deploys HR (Mandalari et al., 2018). With HR, the roaming traffic is routed through the home country, regardless the roaming user’s actual geo-location. This allows MNOs to control the charging function of their outbound roaming users, but is also translates into a non-negligible delay penalty and potential performance impairment, as previously uncovered via measurements in the wild (Mandalari et al., 2018). With existing regulation meant to tackle silent roamers and boost roaming revenues (e.g., Roam like at Home in Europe (3)), users also expect high quality, always-on services in a visited network; if these expectations are not met the risk of churn increases. Facilitating local breakout (LBO) roaming and simplifying the inter-MNO charging settlement would respond to this innovation need. However, all these require MNOs to trust their roaming partners to correctly charge roamers, without leaving the doubt that fraud (e.g., tampering with roaming records) might occur. The shift in the business logic that DICE brings through the use of crypto-currencies deliver this, and thus promotes the local breakout roaming configuration. We focus our design on data communications and LTE technology111For voice traffic, there is the need for a permanent identifier which depends on the HMNO, so incoming calls will always be routed through the HMNO. We are not changing this logic, instead we focus on data communications (and outgoing calls) that only require the roamer to have an attachment point to the visited network.

With DICE, we make a two-fold contribution to disrupt the cellular ecosystem: (i) we enable MNOs to have a direct dynamic cooperation in a private and secure setup, establish roaming relationships, and perform data and financial clearing in almost real time, and (ii) we enable the end-user to have control over her mobile connection and connect to a network in a visited country as a native user, receiving optimal service performance. The DLT solution lowers uncertainty about the identity of the different entities involved in the roaming transaction (i.e, the roaming user, the home network and the visited network offering roaming services to the roaming user), and allows the exchange of value without trust between the entities. The purpose of DICE is to allow MNOs to engage in a roaming partnership and to exchange value easily, without the need of a third party to act as a trusted intermediary with the role to verify the interaction between the roaming partners. The notion of uncertainty we consider integrates three main components: identity of partner entities, visibility of transactions between any entities, and recourse in case something goes wrong. No individual organization in the group can be trusted with maintaining this archive of records, because falsified or deleted information would significantly benefit that party while damaging the others. Nonetheless, it is vital that all agree on the archive’s contents, in order to prevent charging disputes.

2. Background and Related Work

2.1. Roaming Background

To support roaming, the two partners must have a functioning technical solution and a commercial agreement in place (i.e., valid interworking). Once interworking is established, the Home Subscriber Servers (HSS) of the roaming partners communicate among them when a roaming customer (Alice) of an HMNO tries to authenticate to the VMNO.

When Alice is outside her provider’s area of coverage, she tries to connect to a local MNO according to a list of preferred MNOs per geographical area provided by HMNO. Assuming VMNO is selected, roamer Alice follows the specified procedure. First, it contacts the HSS of VMNO with their international mobile subscriber identity number (IMSI). The HSS recognizes that Alice’s IMSI does not belong to VMNO, but rather to HMNO and checks for a roaming agreement. If the agreement is in place, the HSS contacts its counterpart in HMNO, otherwise it refuses the access. This procedure leverages an international signaling infrastructure that is usually provided by a third party.

Once authentication is completed there are three possible configurations for data transfer. The one that is currently deployed is HR (5; 8). Other two configurations that are not actually popular are local breakout (LBO) (5; 8) and IPX hub breakout (IHBO) (13). For the former, the visited network assigned the IP address of the roaming user; for the latter, the IP Packet Exchange (IPX) provides Alice’s IP address.

With the most popular configuration (i.e., HR), HMNO logs Alice’s activity at its Packet Data Network Gateway (PGW) while VMNO does the same at its Serving Gateway (SGW). Both MNOs generate Transferred Account Procedure (TAP) files containing Alice’s activity for charging, which are collected by the DCH. The DCH validates and verifies the TAP files and in case of disagreement between information from MNOs, they trigger a dispute. The DCH automatically handles disputes for minor differences, but in most cases disputes are handled case-by-case. The charging settlement procedure is not real time but rather happens yearly, monthly, or when the bill exceeds a certain threshold.

2.2. Related Work

Although prior work extensively investigated business aspects of the wired internet (Lutu et al., 2012), the interconection of networks (Fanou et al., 2016) and its evolution in time (Dhamdhere and Dovrolis, 2008), the interactions between mobile networks and the global Internet remain largely unexplored. Some prior work has underlined structural characteristics of MNOs, internal organization (Vallina-Rodriguez et al., 2015) and their impact around the world (Rula et al., 2017). However, we have little visibility on the mobile networks’ interconnection dynamics and associated business relationships in the context of international roaming. This is an important gap to fill, especially since we know that the manner in which mobile networks interconnect can have important side-effects on the experience of the end-user (Mandalari et al., 2018; Shaun Kennedy, ). In particular, an important effect comes from the relationships between mobile connectivity providers and content providers (Michelinakis et al., 2018). The idea of leveraging distributed ledgers for increasing the dynamics of business agreements in the wired internet (i.e., at Internet Exchange Points) has recently been presented as part of the Dynam-IX framework (Marcos et al., 2018). Similarly, DICE allows for roaming agreement updates in a dynamic manner. Additionally, DICE enables LBO roaming and allows MNOs to avoid tedious procedures for data and financial clearing implemented in the current ecosystem through the creation of a roaming crypto-currency. Furthermore, the use of DLT enables DICE to eliminate the need for roaming fraud detection, as roaming records become immutable once committed. Similar benefits of DLT have also been exploited in charging schemes for third-party infrastructure usage in the cellular edge (Li et al., 2019). Though used in a different application than the one we present in this paper, this validates the feasibility of DLT-enabled solutions to work in a production environment and tackle hard problems such as interaction in the cellular ecosystem without trust.

3. DICE Toy Example

In this section, we provide an overview of how DICE innovates the data and financial settlement procedures, and removes the performance issues for using HR roaming.

3.1. DICE Design Considerations

DICE aims to facilitate dynamic collaboration between MNOs by: (i) eliminating the need for an intermediary, such as a DCH for clearing and settlement services and (ii) supporting the implementation of LBO roaming by enabling the roaming user to attach to a visited network as a native user.

To achieve these goals DICE must ensure the following:

Near real time billing: DICE should enable MNOs to bill a user and settle the roaming charges among them in almost real time. This would guarantee the user is able to consume the traffic she is allowed, avoiding incomplete and accumulated roaming records.

Automated dispute resolution: DICE should avoid the generation of disputes among MNOs, and automatically solve any billing issue arising.

Trust: DICE should provide mechanisms to build trust among MNOs to guarantee optimal performance for the customer (e.g., enable LBO roaming).

Confidentiality: DICE must guarantee that any information considered private by the MNOs (e.g., billing information across roaming partners, or personal customer information) does not leak to unauthorized parties.

DICE builds on DLT, also known as blockchain, to enable MNOs to interact directly and offer custom services to their users (e.g., through the use of crypto-currencies). MNOs in the DICE consortium are free to engage in dynamic and versatile business relationships, without the need of third-party facilitators. The components of the DICE framework include: i) a protocol to automate the interaction of mobile operators (also with their subscribers); ii) a template to specify contracts easily and the legal framework to handle them; iii) a blockchain solution to store every transaction between the involved entities and enable the exchange of value. This enables MNOs to interact directly without trust, benefit from the immutability of roaming records in the blockchain and ensure an optimal experience to end-users.

We provide next a toy example to demonstrate how Alice can use the DICE solution to roam internationally, and how DICE mechanisms provides near real time billing and avoid disputes across MNOs. We then discuss how to leverage existing DLT to implement such mechanisms and guarantee trust and confidentiality in Sec. 5.

Figure 1. A user roaming across MNOs with DICE.

3.2. DICE Mechanism

Figure 1 shows the different steps involved in the DICE protocol and how Alice can use it to obtain service locally in the Visited Country. The protocol is the core component of DICE and we define it to resemble the current interaction between roaming partners and roaming users.

We assume a number of MNOs agree to form the DICE consortium. Every MNO establishes roaming interworking and agreements with some of the other MNOs in the consortium (Step 0 in Figure 1). Each of the MNOs in the consortium owns DICE crypto-currency (unique for each MNO) that they can assign to their customers for roaming services.

When purchasing connectivity from the HMNO (as part of the initial service contract), Alice has the option to opt-in for the DICE schema and use the tokens from the HMNO to buy service when roaming internationally. Alice’s decision to use DICE generates an initial assignment from the HMNO to Alice’s e-wallet of X DICE token that Alice can spend while roaming (Step 1 in Figure 1). This will be a transaction appended to the DICE ledger, which hereinafter remains immutable and tamper-free.

When traveling to a visited country, Alice attempts to obtain connectivity service from a local MNO that has a previous roaming agreement with her HMNO. Through the use of a smart contract that executes on the DICE blockchain the following two conditions are verified: (i) Alice verifies whether the selected VMNO accepts the HMNO DICE tokens (Step 2 in Figure 1); (ii) the VMNO authenticates Alice as a valid user of the HMNO by verifying that her e-wallet contains DICE tokens from the HMNO and by checking the on-chain associated transaction to the initial assignment from the HMNO. If these conditions are met, Alice signs a service contract with the VMNO and requests a new profile to remotely provision her Subscriber Identity Module (SIM) card (Step 3 in Figure 1). We argue that the iSIM technology (integrated SIM) enables a key feature of the DICE solution: roaming like at the destination configuration to resemble the LBO roaming. Remote SIM provisioning allows Alice to remotely change the SIM profile on a deployed SIM without physically changing the SIM itself (Step 4 in Fig. 1).

Once the new SIM profile is configured, Alice opens a uni-directional roaming payment channel towards the VMNO (Step 5 in Figure 1). In order to ensure that Alice pays her bill for the roaming service, tokens have to be locked up as security in a smart contract for the lifetime of the payment channel (Step 6 in Figure 1). Payment channels allow for practically unlimited transfers between the two participants, as long as the net sum of their transfers does not exceed the deposited tokens. These transfers can be performed instantaneously and without any involvement of the actual DICE blockchain itself, except for an initial one-time on-chain creation and an eventual closing of the channel. Alice uses the payment channel to issue micro-payments to the VMNO periodically for the service the latter offers (Step 7 in Figure 1). The MVNO associates a time-out counter after each last micro-payment issued by Alice in order to make sure that the payment channel closes when it has been inactive for a given amount of time (e.g., 24 hours). The channel can also be closed from Alice when she configures another SIM profile of an MVNO or the one of its HMNO. Once the payment channel is closed and the on-chain transaction completes (Step 8 in Figure 1), the VMNO receives the DICE tokens from Alice (Step 9 in Figure 1). In the same time, the HMNO re-provisiones the Alice’s SIM with the initial profile (Step 10 in Figure 1). Finally, the VMNO can proceed to exchange the tokens it has received from Alice for money from the HMNO (Step 11 in Figure 1).

The DICE protocol provides near real time billing as the tokens are locked as Alice (the roamer) starts consuming data, and transferred as the channel is closed. It also guarantees that there will not be dispute or monetary losses, as Alice can use the service only in exchange of tokens transferred to the visited network. We note that the procedures associated with the DICE protocol are automated and do not require any human intervention, besides the initial opt-in for the DICE schema and agreement stipulation across MNOs.

4. System Requirements

In this section, we quantify the roaming interactions of an operational MNO in Europe to derive requirements for the DICE system for deployment (Sec. 5). As DICE is based on DLT, its feasibility to support the magnitude of the cellular ecosystem is related to the number of transactions per seconds the system can sustain. This amount is dominated by the attach and token transfer operations between roamers and VMNOs (i.e., steps 2 to 8 of Figure 1). These account for three transactions to the DICE blockchain, one for the initial smart contract execution (step 2-3), one for opening the payment channel (step 5) and one for closing it (step 8).

4.1. MNO dataset

We quantify the system requirements by focusing on the inbound roamers population dynamics of the European MNNO. We analyze the population of the MNO over four weeks, from April 4th to April 30th 2019 (consistent with a billing cycle). To preserve confidentiality, we present results normalized, anonymized or as order of magnitude. As this is a medium-large size MNO (i.e., 30 millions customers), we further approximate the overall DICE system requirements to cater to as much as 800 MNOs worldwide (6).

(a) Data traffic per day for inbound roamers.
(b) Distribution of Fraction of Inbound Roamers per Home Country.
(c) Distribution of Inbound Roamers traffic per Home MNO.
Figure 2. Analysis for inbound roaming smartphones for an operational MNO in Europe.

Although the dataset includes smartphones, feature phones, and IoT devices, we use a commercial database provided by GSMA to separate for our analysis the smartphones that people use as their primary devices. This latter population subgroup integrates users with different roaming status, including MNO’s native users (active both in the home country and abroad as outbound roamers) or foreign users that belong to other MNOs (national or international), but who use the radio network of the MNO under analysis (i.e., inbound roamers). We separate and analyze the inbound roamers in the MNO’s network (checking the radio network logs), the outbound roamers (checking the core network logs) and the native users of the MNO in the home country. Further we use eXtended Detail Records to provide aggregate service usage for data communications.

4.2. Analysis

Number of roamers. We first note that the inbound roamers are the third largest group in the MNO population (17%), after native users (50%) and users operating with a SIM card from an MVNO enabled by the incumbent MNO (33%). This population integrates all device types, including IoT devices and smartphones. Using the information from the MNO dataset, we are able to separate for further analysis only the smartphones (e.g., by verifying if the GSMA database associated an operating system to the devices such as iOS, Android, Windowsphone, Blackberry). The total population of inbound roaming smartphones per day accounts for 2.5% of the total number of devices connected to the MNO’s radio network on average across the one month period. This percentage represents hundreds of thousands devices that need to be sustained by DICE for a given visited MNO. In the rest of this section, we focus on this subgroup of devices to understand how many transactions they would generate.

Number of transactions for newly connected and leaving roamers (step 2-8). The number of newly connected inbound roaming smartphones (i.e., who start a new roaming session with the visited MNO during the period of analysis) per day fluctuates with between 10% and 30% of the average daily number of inbound roamers connected to the MNO during April 2019. Further, the number of leaving inbound roamers (i.e., who finalize their roaming session with the visited MNO during the period of analysis) similarly fluctuates between 10% and 30% of the average number of inbound roamers. We also measured that, in median, the number of days an inbound roamer is active in the visited MNO is approximately 2.5 days. These results highlight that tens of thousand of roamers per day that would generate a transaction to execute the initial smart-contract, one to connect to and one to leave a visited network for a given MNO. Assuming 800 MNOs, this results in few millions operations per day; even assuming these transactions are concentrated in few hours, there would be few thousands operations per second on the blockchain that can be sustained by existing technologies (cf. Sec.  5).

Number of transactions for data usages. We show in Figure 2 the distributions of amount of traffic transferred per day (in Bytes) by the inbound roamers. We find that more than 50% of all inbound roamers are silent roamers, that do not generate data communications. We note that the median amount of traffic per day transferred by a non-silent inbound roamer is approximately 1MB (”IN-ROAMING smart” curve in Figure 1(a)). This translates into an average sum of traffic transferred by one inbound roamer of approximately 2.5MB during a roaming visit. This is 10 times smaller the the median amount of traffic transfered by a native user of the MNO (”NATIVE smart” curve in Figure 1(a)). We compare the amount of traffic aggregated for inbound roamers from countries in the EU (”EU in-roamers” curve in Figure 1(a)) against countries from outside the EU (”non-EU in-roamers” curve in Figure 1(a)) and find that there is slight increase in the traffic for the EU inbound roamers. Overall, we observe around 10 TB of data generated by roamers. Assuming 100KB as billing granularity as in today’s roaming configuration, there would be hundreds of millions transactions per day for a given visited MNO. With 800 MNOs, this results in few billions operations per day: this high number of transactions justifies the design choice of performing them off-chain so that they do not constitute a bottleneck (cf. Sec. 5).

Number of partner MNOs and countries. Over the entire month of April, we find that the MNO provided service to more than 18 million unique inbound roamers, associated to approximately 400 MNOs mapping to 188 home countries overall. We show in Figure 1(b) the distribution of inbound roamers per home country for the top 10 countries as percentages of the total inbound roamers observed over the one-month period. The top home countries include Poland, Germany, Spain, Italy and Ireland and account for about 60% of inbound roamers. Although this proves increased mobility within the EU (intuitive as a consequence of ”Roam like at Home” EU Regulation (3)), we also observe a large number from non-EU states, such as US or India. We then report in Figure 1(c) the distribution of inbound roamers traffic per home MNO for the top 10 MNOs. We again observe a long tail distribution with the top 10 MNOs accounting for about 50% of traffic. These results highlight that few MNOs from few countries will cover the majority of tokens to be exchanged; however, transactions with the long tail of MNOs are required to exchange the remaining tokens. These metrics do not constitute a bottleneck as token exchanges happen on a long timescale (e.g., weeks or months), but they are relevant to take into account in DICE deployment consideration.

5. DICE Implementation

In this section, we discuss the practical implementation of DICE. We examine the deployment requirements that ensure a smooth transition from the current ecosystem to one where DICE is a valid solution. Then, we extend the mechanism we presented in Sec. 3.2 on several practical aspects for the DICE implementation, feasibility, and charging principles.

5.1. Deployment Considerations

DICE Backwards Compatibility with HR Roaming. The protocol in Figure 3.2 includes the use of remote SIM provisioning through iSIM to enable LBO roaming. Though this is the desirable configuration of the DICE protocol, we also ensure compatibility with the current HR roaming status. In this latter case, we would skip Step 3 in the DICE protocol diagram in Figure 1, and simply rely on the existing roaming configuration implemented by the HMNO. Assuming HR roaming, the HMNO is still the entity that controls the roamer’s exit point to the Internet and there is no need for a legal contract with the VMNO in the visited country. Thus, the ledger accounts in near-real time the activity of the roamer in the VMNO by translating the received service (i.e., transferred traffic) into DICE tokens the roamers pays to the VMNO. This process is compatible with the logic of steps 4-8 in Figure 1.

Blockchain Solution Feasibility. We propose the implementation of a consortium blockchain, which has many of the same advantages of a private blockchain, but operates under the leadership of a group (instead of a single entity). As opposed to the public blockchain model, which allows any person with an internet connection to participate in the verification of transactions process, a few selected nodes are predetermined. A consortium blockchain solution allows the creation of crypto-currencies with meaning only within the private group (different from public crypto-currencies such as Bitcoin). It also keeps the control of the blockchain among its members and avoids external entities to influence or attack the system. Also, consortium blockchains allow for competing business entities to interact on the same blockchain (Guo and Liang, 2016) (see privacy and confidentiality considerations).

Given the requirements in terms of the number of blockchain transactions per second (TPS) we approximated in Section 4, we propose building DICE with Hyperledger Fabric (Androulaki et al., 2018) – a permissioned blockchain – as the distributed tamper-proof ledger. Hyperledger can accommodate 20,000TPS, while other blockchains such as Ethereum can accommodate only 10-25 TPS or Ripple 1,500 TPS. This is enough to process the number of funding transactions required for the creation of the channels for the visiting nodes.

Besides dimensional requirements, Hyperledger is also a suitable technology for the following reasons: i) it offers a modular framework that allows for assets to be transferred between blockchain participants (in our case, DICE tokens that account for mobile connectivity service); ii) it allows the members of the permissioned network to define the asset type, its value and the consensus protocol; iii) Hyperledger provides membership identity service that manages participants’ identities and authenticates them; iv) the ledger consists of a database storing the current state of the network and a log of transactions for tracking each asset’s provenience.

Payment channels with off-chain transactions. We propose to use unidirectional payment channels that allow the transfer of coins from the roamer to the VMNO, based on the traffic exchanged by the visiting node. In particular, we propose a granularity of 100KB, meaning that the roaming user will transfer coins for every 100KB of traffic transferred through the VMNO. This is the typical billing granularity currently used for roaming. To enable scalability of this charging model while meeting our requirements, DICE relies on payment channels based simple on hashed time-locks contracts that enable off-chain transactions between the roaming user and the VMNO (16). It follows that each visiting node will require the creation of one on-chain funding transaction for creating the channel and all the transactions paying for the traffic exchanged will happen off-line.

Roaming Privacy and Confidentiality. The usage of a distributed ledger implies that every party involved in the network would have access to all transactions, even the ones where they were not involved in the transactions themselves. This brings a challenge for telco businesses that are competing in the same space and do not want to reveal company secrets to their competitors. This also impacts privacy of end users that could be tracked across MNOs. Hyperledger Fabric solves the former problem by offering private channels, which are restricted messaging paths that offer privacy for specific subsets. In this case, all data is invisible to members not granted specific access. To further obfuscate the number of customers an MNO has active in DICE and preserve user privacy, we envision that the HMNO can assign to the roamer multiple identities (or e-wallets), to which the latter attaches different amounts of DICE tokens.

5.2. DICE Charging Principles

In the last step of the protocol depicted in Fig. 1, the VMNO triggers the financial clearing procedure by exchanging the DICE tokens from its inbound roamers with the corresponding HMNOs. To avoid potential speculations on exchanging these token to money, we implement in DICE a prior check for the provenience of the tokens being exchanged. Specifically, for an HMNO to accept the tokens from a partner VMNO, the latter must prove that it received the tokens from a customer of the HMNO in exchange for its service. In other words, the HMNO will convert to fiat money the DICE coins that went from it own customers to the VMNO.

This final financial settlement step also implies the use of a specific billing model, one that the roaming partners likely agree upon in the Roaming Agreement they sign (Step 0 in Figure 1). This can accommodate different charging models. In the past decades the wholesale roaming charge models for data usage have remained in the retail-like charge models, which are applied to each visitor who roamed in the VMNO (per session per IMSI). With increasing roaming data usage there is the trend to use a simplified IOT (Inter Operator Tariff) model such as the “Fixed” or “Per-Unit” charge model which is applied to the total volume of data usage with or without a post-discount adjustment. We argue that DICE offers maximum flexibility of implementing dynamics charging models at different granularity levels.

6. Discussion and Future Work

In DLT we may be witnessing a potential explosion of creative potential that catalyzes exceptional levels of innovation. The technology has the capacity to deliver a new kind of trust to a wide range of services, including the largely opaque cellular roaming ecosystem. We argue that DICE will enable a much-needed communication loop between the mobile connectivity provider and the subscribers, allowing the latter to gain control over their connectivity and request certain levels of service. Also, MNOs can form alliances to share their infrastructure and jointly fulfill the requirements of subscribers. The DICE open and competitive framework provides the foundations for growth, innovation and affordable access for the end users.

In continuing the work we outlined in this paper, we aim for a proof-of-concept implementation of DICE. In this framework, we then plan to explore multiple open questions related to the performance of the DICE solution, privacy of the end-user and security of the system. We envision that we can extend DICE to integrate different other functionality, such as real-time fraud detection and anomaly detection.


  • [1] E. Androulaki, A. Barger, V. Bortnikov, C. Cachin, K. Christidis, A. De Caro, D. Enyeart, C. Ferris, G. Laventman, Y. Manevich, S. Muralidharan, C. Murthy, B. Nguyen, M. Sethi, G. Singh, K. Smith, A. Sorniotti, C. Stathakopoulou, M. Vukolić, S. W. Cocco, and J. Yellick (2018) Hyperledger fabric: a distributed operating system for permissioned blockchains. In Proceedings of the Thirteenth EuroSys Conference, EuroSys ’18, New York, NY, USA, pp. 30:1–30:15. External Links: ISBN 978-1-4503-5584-1, Link, Document Cited by: §5.1.
  • [2] A. Dhamdhere and C. Dovrolis (2008) Ten years in the evolution of the internet ecosystem. In Proceedings of the 8th ACM SIGCOMM conference on Internet measurement, pp. 183–196. Cited by: §2.2.
  • [3] European Commission: New Rules on Roaming Charges and Open Internet. Note:[Online; accessed 06-March-2018] Cited by: §1, §4.2.
  • [4] R. Fanou, G. Tyson, P. Francois, and A. Sathiaseelan (2016) Pushing the frontier: exploring the african web ecosystem. In Proceedings of the 25th International Conference on World Wide Web, pp. 435–445. Cited by: §2.2.
  • [5] GSM Association: LTE and EPC Roaming Guidelines. Note:[Online; accessed 06-March-2018] Cited by: §2.1.
  • [6] GSMA Operator Full Members. Note:[Online; accessed 27-06-2019] Cited by: §4.1.
  • [7] Y. Guo and C. Liang (2016) Blockchain application and outlook in the banking industry. Financial Innovation 2 (1), pp. 24. Cited by: §5.1.
  • [8] Huawei: LTE International Roaming Whitepaper. Note:[Online; accessed 06-March-2018] Cited by: §2.1.
  • [9] Y. Li, K. Kim, C. Vlachou, and J. Xie (2019) Bridging the data charging gap in the cellular edge. In Proceedings of the ACM Special Interest Group on Data Communication, SIGCOMM ’19, New York, NY, USA, pp. 15–28. External Links: ISBN 9781450359566, Link, Document Cited by: §2.2.
  • [10] A. Lutu, M. Bagnulo, and R. Stanojevic (2012) An economic side-effect for prefix deaggregation. In 2012 Proceedings IEEE INFOCOM Workshops, pp. 190–195. Cited by: §2.2.
  • [11] A. M. Mandalari, A. Lutu, A. Custura, Ali, Ö. Alay, M. Bagnulo, V. Bajpai, A. Brunstrom, J. Ott, M. Mellia, and G. Fairhurst (2018) Experience: implications of roaming in europe. In Proc. of MobiCom, Cited by: §1, §2.2.
  • [12] P. Marcos, M. Chiesa, L. Müller, P. Kathiravelu, C. Dietzel, M. Canini, and M. Barcellos (2018) Dynam-ix: a dynamic interconnection exchange. In Proceedings of the 14th International Conference on emerging Networking EXperiments and Technologies, pp. 228–240. Cited by: §2.2.
  • [13] Method and System For Hub Breakout Roaming. Note:[Online; accessed 06-March-2018] Cited by: §2.1.
  • [14] F. Michelinakis, H. Doroud, A. Razaghpanah, A. Lutu, N. Vallina-Rodriguez, P. Gill, and J. Widmer (2018) The Cloud that Runs the Mobile Internet: A Measurement Study of Mobile Cloud Services. In Proc. IEEE INFOCOM, Cited by: §2.2.
  • [15] Next-generation Interconnection and Roaming Analysis for Mobile Services. Note:[Online; accessed 28-June-2019] Cited by: §1.
  • [16] Raiden Network. Note:[Online; accessed 28-June-2019] Cited by: §5.1.
  • [17] J. P. Rula, F. E. Bustamante, and M. Steiner (2017) Cell spotting: studying the role of cellular networks in the internet. In Proceedings of the 2017 Internet Measurement Conference, pp. 191–204. Cited by: §2.2.
  • [18] Shaun Kennedy Private Communication about Roaming Ecosystem. Cited by: §1, §2.2.
  • [19] N. Vallina-Rodriguez, S. Sundaresan, C. Kreibich, N. Weaver, and V. Paxson (2015) Beyond the radio: illuminating the higher layers of mobile networks. In Proceedings of the 13th Annual International Conference on Mobile Systems, Applications, and Services, pp. 375–387. Cited by: §2.2.