An efficient and scalable monitoring system is a critical component for any network to monitor and validate the functioning of the running services and the underlying infrastructure. This is more valid in 5G, as it relies on the network slicing concept, which adds many challenges to the monitoring system. Besides data isolation and multi-tenancy support, network slices require monitoring different types of resources, like RAN, computing, memory, network data rate, which belong to different technological domains, managed by different entities. Moreover, the monitoring system needs to be scalable, as in 5G a high-number of running network slices is envisioned. In this paper, we devise a novel monitoring framework for network slicing ready mobile networks, which features: 1) scalable monitoring system that supports a high number of running network slices in parallel; 2) technological domain agnostic thanks to a novel data collection (or monitoring) communication protocol; 3) support of multi-tenancy in a cloudnative environment. The framework has been implemented in a 5G facility, and its performance has been extensively evaluated.

The Radio Network Information Service (RNIS) is one of the key services provided by a Multi-access Edge Computing Platform (MEP), as specified in the relevant ETSI MEC standards. It is responsible for interacting with the Radio Access Network (RAN), collecting RAN-level information about User Equipment (UE) and exposing it to mobile edge applications, which can in turn utilize it to dynamically adjust their behavior to optimally match the RAN conditions. Putting the provision of RNIS in the context of the emerging MEC-in-NFV environment, where the components and services of the MEC architecture, including the MEP itself, are integrated in an NFV environment and are delivered on top of a virtualized infrastructure, we present our standards-compliant RNIS implementation based on OpenAirInterface and study critical performance aspects for its provision as a virtual function. Since the RNIS design and operation follows the publish-subscribe model, we provide alternative implementations using different message brokering technologies (RabbitMQ and Apache Kafka), and compare their use and performance in an effort to evaluate their suitability for providing RNIS in an as-a-service manner.

No abstract

No abstract

No abstract