Simone Mangiante | University of Genova (original) (raw)

Papers by Simone Mangiante

IEEE ACM Transactions on Networking, Dec 31, 2022

IEEE Conference Proceedings, 2016

IEEE Access, 2022

It is widely expected that future networks of 6G and beyond will substantially improve on 5G. Tec... more It is widely expected that future networks of 6G and beyond will substantially improve on 5G. Technologies such as Internet of Skills and Industry 4.0 will become stable and viable, as a direct consequence of networks that offer sustained and reliable mobile performance levels. The primary challenges for future technologies are not just low-latency and high-bandwidth. The more critical problem Mobile Service Providers (MSPs) will face will be in balancing the inflated demands of network connections and customers' trust in the network service. That is, being able to interconnect billions of unique devices while adhering to the agreed terms of Service Level Agreements (SLAs). To meet these targets, it is self-evident that MSPs cannot operate in a solitary environment. They must enable cooperation among themselves in a manner that ensures trust, both between themselves as well as with customers. In this study, we present the BEAT (Blockchain-Enabled Accountable and Transparent) Infrastructure Sharing architecture. BEAT exploits the inherent properties of permissioned type of distributed ledger technology (i.e., permissioned distributed ledgers) to deliver on accountability and transparency metrics whenever infrastructure needs to be shared between providers. We also propose a lightweight method that enables device-level accountability. BEAT has been designed to be deployable directly as only minor software upgrades to network devices such as routers. Our simulations on a resource-limited device show that BEAT adds only a few seconds of overhead processing time-with the latest state-of-the-art network devices, we can reasonably anticipate much lower overheads. INDEX TERMS Infrastructure sharing, smart contracts, permissioned distributed ledgers.

IEEE Communications Surveys and Tutorials, 2017

arXiv (Cornell University), Mar 19, 2018

The automotive and telco industries have taken an investment bet on the connected car market, pus... more The automotive and telco industries have taken an investment bet on the connected car market, pushing for the digital transformation of the sector by exploiting recent Information and Communication Technology (ICT) progress. As ICT developments continue, it is expected that the technology advancements will be able to fulfill the sophisticated requirements for vehicular use cases, such as low latency and reliable communications for safety, high computing power to process large amount of sensed data, and increased bandwidth for on-board infotainment. The aforementioned requirements have received significant focus during the ongoing definition of the 3GPP 5G mobile standards, where there has been a drive to facilitate vertical industries such as automotive, in addition to providing the core aspects of the communication infrastructure. Of the technology enablers for 5G, Multi-access Edge Computing (MEC) can be considered essential. That is, a cloud environment located at the edge of the network, in proximity of the end-users and coupled with the service provider's network infrastructure. Even before 5G is rolled out, current mobile networks can already target support for these challenging use cases using MEC technology. This is because MEC is able to fulfill low latency and high bandwidth requirements, and, in addition, it lends itself to be deployed at the vertical industrial sector premises such as road infrastructure, air/sea ports, smart factories, etc., thus, bringing computing power where it is needed most. This work showcases the automotive use cases that are relevant for MEC, providing insights into the technologies specified and investigated by the ETSI MEC Industry Specification Group (ISG), who were the pioneer in creating a standardized computing platform for advanced mobile networks with regards to network edge related use cases.

ArXiv, 2021

It is widely expected that future networks of 6G and beyond will deliver on the unachieved goals ... more It is widely expected that future networks of 6G and beyond will deliver on the unachieved goals set by 5G. Technologies such as Internet of Skills and Industry 4.0 will become stable and viable, as a direct consequence of networks that offer sustained and reliable mobile performance levels. The primary challenges for future technologies are not just low-latency and high-bandwidth. The more critical problem Mobile Service Providers (MSPs) will face will be in balancing the inflated demands of network connections and customers’ trust in the network service, that is, being able to interconnect billions of unique devices while adhering to the agreed terms of Service Level Agreements (SLAs). To meet these targets, it is self-evident that MSPs cannot operate in a solitary environment. They must enable cooperation among themselves in a manner that ensures trust, both between themselves as well as with customers. In this study, we present the BEAT (Blockchain-Enabled Accountable and Transp...

IEEE Transactions on Network and Service Management, 2022

Ossification of the Internet transport-layer architecture is a significant barrier to innovation ... more Ossification of the Internet transport-layer architecture is a significant barrier to innovation of the Internet. Such innovation is desirable for many reasons. Current applications often need to implement their own mechanisms to receive the transport service they need, but many do not have the breadth of adapting to all possible network characteristics. An updated transport architecture can do much to make the Internet more flexible and extensible. New ground-breaking services often require different or updated transport protocols, could benefit from better signalling between application and network, or desire a more flexible choice of which network path is used for which traffic. This document therefore proposes a new transport architecture. Such architecture lowers the barrier to service innovation by proposing a "transport system", the NEAT System, that can leverage the rich set of available transport protocols. It paves the way for an architectural change of the Inter...

IEEE Communications Magazine, 2017

NEAT has identified application requirements and associated NEAT service components from use case... more NEAT has identified application requirements and associated NEAT service components from use cases in Task 1.1. To fulfill these requirements, the NEAT System must provide certain services, and the NEAT API must contain a set of primitives and events that allow applications to use these services. Because NEAT makes use of the functionality of transport protocols without statically binding them to applications, the NEAT API must also provide (generic) access to the features of the transport protocols that NEAT uses. This document presents generic API primitives and events that map to features of TCP and SCTP, as well as primitives, events and services that relate to NEAT's use cases.

This document presents the core transport system in NEAT, as used for development of the referenc... more This document presents the core transport system in NEAT, as used for development of the reference implementation of the NEAT System. The document describes the components necessary to realise the basic Transport Services provided by the NEAT User API, with the description of a set of NEAT building blocks and their related design choices. The design of this core transport system takes into consideration the Transport Services and the API (defined in Task 1.3) and in close coordination with the overall architecture (Task 1.2). To realise the Transport Services provided by the API, a set of transport functionalities has to be provided by the NEAT Core Transport System. These functionalities take the form of several building blocks, or NEAT Components, each representing an associated implementation activity. Some of the components are needed to ensure the basic operation of the NEAT System—e.g., a NEAT Flow Endpoint, a callback-based NEAT API Framework, theNEAT Logic and the functional...

This document presents the first version of the low-level Core Transport System in NEAT, to be us... more This document presents the first version of the low-level Core Transport System in NEAT, to be used for development of a reference implementation of the NEAT System. The design of this core transport system takes into consideration the Transport Services and the API defined in Task 1.3 and in close coordination with the overall architecture (Task 1.2). To realise the basic Transport Services provided by the API, a set of low-level transport functionalities has to be provided by the NEAT core transport system. These functionalities take the form of several building blocks, or NEAT Components, each representing an associated implementation activity. Some of the components are needed to ensure the basic opera- tion of the NEAT System—e.g., a NEAT Flow Endpoint, a callback-based NEAT API Framework, the NEAT Logic and the functionality to Connect to a name. Some other components are needed to ensure connectivity using Middlebox Traversal techniques (e.g., TURN), discovery of path support...

This document presents the core transport system in NEAT, as used for development of thereference... more This document presents the core transport system in NEAT, as used for development of thereference implementation of the NEAT System. The document describes the componentsnecessary to realise the ba ...

This document presents the core transport system in NEAT, as used for development of the referenc... more This document presents the core transport system in NEAT, as used for development of the reference implementation of the NEAT System. The document describes the components necessary to realise the basic Transport Services provided by the NEAT User API, with the description of a set of NEAT building blocks and their related design choices. The design of this core transport system, which is the final product of Work Package 2, is driven by the Transport Services and API design from Task 1.4, and in close coordination with the overall NEAT architecture defined in Task 1.2. To realise the Transport Services provided by the API, a set of transport functions has to be provided by the NEAT Core Transport System. These functions take the form of several building blocks, or NEAT Components, each representing an associated implementation activity. Some components are needed to ensure the basic operation of the NEAT System— e.g., a NEAT Flow Endpoint, a callback-based NEAT API Framework, the N...

ArXiv, 2011

A huge amount of data is everyday managed in large organizations in many critical business sector... more A huge amount of data is everyday managed in large organizations in many critical business sectors with the support of spreadsheet applications. The process of elaborating spreadsheet data is often performed in a distributed, collaborative way, where many actors enter data belonging to their local business domain to contribute to a global business view. The manual fusion of such data may lead to errors in copy-paste operations, loss of alignment and coherency due to multiple spreadsheet copies in circulation, as well as loss of data due to broken cross-spreadsheet links. In this paper we describe a methodology, based on a Spreadsheet Composition Platform, which greatly reduces these risks. The proposed platform seamlessly integrates the distributed spreadsheet elaboration, supports the commonly known spreadsheet tools for data processing and helps organizations to adopt a more controlled and secure environment for data fusion.

The NEAT System offers an enhanced API for applications that disentangles them from the actual tr... more The NEAT System offers an enhanced API for applications that disentangles them from the actual transport protocol being used. The system also enables applications to communicate their service requi ...

Ossification of the Internet transport-layer architecture is a significant barrier to innovation ... more Ossification of the Internet transport-layer architecture is a significant barrier to innovation of the Internet. Such innovation is desirable for many reasons. Current applications often need to implement their own mechanisms to receive the transport service they need, but many do not have the breadth of adapting to all possible network characteristics. An updated transport architecture can do much to make the Internet more flexible and extensible. New ground-breaking services often require different or updated transport protocols, could benefit from better signalling between application and network, or desire a more flexible choice of which network path is used for which traffic. This document therefore proposes a new transport architecture. Such architecture lowers the barrier to service innovation by proposing a “transport system”, the NEAT System, that can leverage the rich set of available transport protocols. It paves the way for an architectural change of the Internet where ...

Infrastructure sharing is a widely discussed and implemented approach and is successfully adopted... more Infrastructure sharing is a widely discussed and implemented approach and is successfully adopted in telecommunications networks today. In practice, it is implemented through prior negotiated Service Level Agreements (SLAs) between the parties involved. However, it is recognised that these agreements are difficult to negotiate, monitor and enforce. For future 6G networks, resource and infrastructure sharing is expected to play an even greater role. It will be a crucial technique for reducing overall infrastructure costs and increasing operational efficiencies for operators. More efficient SLA mechanisms are thus crucial to the success of future networks. In this work, we present "BEAT", an automated, transparent and accountable end-to-end architecture for network sharing based on blockchain and smart contracts. This work focuses on a particular type of blockchain, Permissioned Distributed Ledger (PDL), due to its permissioned nature allowing for industry-compliant SLAs wit...

IEEE ACM Transactions on Networking, Dec 31, 2022

IEEE Conference Proceedings, 2016

IEEE Access, 2022

IEEE Communications Surveys and Tutorials, 2017

arXiv (Cornell University), Mar 19, 2018

ArXiv, 2021

IEEE Transactions on Network and Service Management, 2022

IEEE Communications Magazine, 2017

This document presents the core transport system in NEAT, as used for development of the referenc... more This document presents the core transport system in NEAT, as used for development of the reference implementation of the NEAT System. The document describes the components necessary to realise the basic Transport Services provided by the NEAT User API, with the description of a set of NEAT building blocks and their related design choices. The design of this core transport system, which is the final product of Work Package 2, is driven by the Transport Services and API design from Task 1.4, and in close coordination with the overall NEAT architecture defined in Task 1.2. To realise the Transport Services provided by the API, a set of transport functions has to be provided by the NEAT Core Transport System. These functions take the form of several building blocks, or NEAT Components, each representing an associated implementation activity. Some components are needed to ensure the basic operation of the NEAT System— e.g., a NEAT Flow Endpoint, a callback-based NEAT API Framework, the N...

ArXiv, 2011

Ossification of the Internet transport-layer architecture is a significant barrier to innovation ... more Ossification of the Internet transport-layer architecture is a significant barrier to innovation of the Internet. Such innovation is desirable for many reasons. Current applications often need to implement their own mechanisms to receive the transport service they need, but many do not have the breadth of adapting to all possible network characteristics. An updated transport architecture can do much to make the Internet more flexible and extensible. New ground-breaking services often require different or updated transport protocols, could benefit from better signalling between application and network, or desire a more flexible choice of which network path is used for which traffic. This document therefore proposes a new transport architecture. Such architecture lowers the barrier to service innovation by proposing a “transport system”, the NEAT System, that can leverage the rich set of available transport protocols. It paves the way for an architectural change of the Internet where ...