# A Novel Radio Network Information Service (RNIS) to MEC Framework in B5G Networks
## 3 Our Proposed RNIS as a Service to MEC Framework in B5G Networks  
Multi-Access Edge Computing (MEC), introduced by ETSI, is a technology that extends intelligence to the network's edge, offering excellent processing and storage capacity [33]. It is considered one of the leading emerging technologies for 5G and 6G networks, providing an environment for IT services and computing resources at the edge of the mobile network [34; 35]. MEC enables interaction with the RAN through a critical component of MEC--the RNIS--which provides information to support various applications. By using real-time and contextual information from the RAN, MEC enables improvements in the performance of existing applications and the development of new and innovative ones. Figure 2 illustrates the MEC reference architecture, in which we can see some of the essential components for the proposal.  
Figure 2: MEC reference architecture [14].  
The MEC architecture consists of components such as MEC host, MEC Platform (MEP), MEC applications (MEC apps), and Multi-Access Edge Orchestrator (MEO), managing MEC apps and acting as an intermediary between the MEC host and the Operations/Business Support System (OSS/BSS) of the operator [14]. The MEP, in turn, can interact with the MEC apps via the Mp1 reference point, which enables service discovery, application registration, and communication. Through this interface, the MEC apps can consume the services the MEP provides. The Mp2 reference point bridges the MEP and the data plane, enabling the MEP to obtain RAN-level information about the UE. In this way, MEC is characterized by its proximity to mobile users, low latency, location recognition, and real-time network context information [9].  
MEC brings with it several advantages and benefits for mobile edge applications. RNIS stands out from MEC as one of the primary MEP services, offering and collecting information about radio network conditions. The actual use of RNIS for emerging applications in the B5G context requires improvements to the service so that it can adapt to network conditions and provide accurate information to interested MEC apps. Some of this information needs to be addressed in the current specifications, such as methods for collecting and exposing information regarding the RRC, centralized coordinated beam management, and lower-layer information.  
Emerging applications are increasingly demanding, requiring growing requirements and generating intense network traffic. This fact already highlights the need for RNIS to advance with its demands. In different works, RNIS is used as a basis for analysis and dynamic adjustments to the behavior of various applications, both in emerging 5G scenarios and in 4G itself. In this way, RNIS must be prepared to support such demands, consuming and exposing information quickly, effectively, and fairly.  
The existing technical documents are based on the MEC reference architecture, exploring its functionalities at the network's edge and highlighting the operation of RNIS and its relationship with interested applications (MEC apps). In the ETSI GS MEC 012 [15] document, RNIS is described as a mobile edge service provided by MEP that communicates via two APIs, each of which has its function, namely to collect, obtain, and expose information.  
The Mp1 API is the communication interface between RNIS and the MEC apps, enabling service registration, service discovery, communication support for services, and other functionalities. This interface includes application availability, support procedures for session state relocation, traffic rules, DNS rule activation, storage access, and information such as time of day. In addition, the Mp1 reference point can also be used to consume services and provide functionalities specific to a service. The Mp2 API, on the other hand, is described as the communication interface between the RNIS and the radio network information provider.