# 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
### RNIS as a Service Architecture  
In this context, our proposed RNIS as a service enhancement is designed to manage information traffic for various applications, boosting delivery and enabling optimization and performance for its agricultural clients. RNIS brings several advantages that have already been highlighted for 4G networks. However, for 5G networks, an improved RNIS for communicating and capturing information will be necessary. The technical document provides information on uptake but needs to be detailed to include 5G networks. One of the key questions identified by ETSI 031 [23] (a document describing the main areas of study in MEC and 5G integration) is whether RNIS itself requires enhancement to expose more radio network information expressly for the 5G RAN, such as lower layers and coordinated beam management information.  
Figure 3 shows the general architecture of the RNIS as a service proposal, where RNIS is deployed in the MEC Platform, consuming information via Mp2 in the RNIS direction to RAN information providers and providing information in the MEP direction to MEC apps. In this proposal, the RNIS comprises the Broker RabbitMQ, which proved very efficient in the tests carried out by [PERSON] et al. [18]. The Broker can classify and organize messages by  
various criteria, as specified in ETSI document 012 [15]. In addition to the Broker, RNIS has incorporated a Receiver responsible for analyzing and organizing messages from gNodeB, managing them, and adapting them to a specific format, such as JSON. The messages are then forwarded to the Broker.  
RNIS enables efficient and practical access to information about UE in the radio network via applications at the network's edge, either for internal MEC Platform services or interested MEC applications. Upon implementing this functionality, the service receives information from the RAN and reviews and adapts it appropriately to allocate it through the implemented receiver. After this process, the service forwards the information to predefined topics of interest, hosted in a Broker, where it is exposed to RNIS's functionalities and forwarded to interested clients, such as MEC apps.  
To properly deliver information to consumers, it must have a clear destination route. To enable this delivery, consumers must register with RNIS, providing their pre-registered identifier, the type of notification they are interested in, and the callback URL from which they wish to receive the information. Initially, RNSI also offered the option of delivery via socket; however, in our proposal, we opted to process the information exclusively via callback. This approach provides greater flexibility and control in the management of notifications.  
RNIS plays an important role in a number of agricultural applications. Among them, it is possible to improve overall efficiency and reduce logistical costs, minimize carbon emissions and improve logistical optimization during crop transport by using MEC for local data processing and RNIS to ensure efficient communication between UE and edge infrastructure. Improving operating costs and enhancing the safety of operations is possible through the automation of agricultural machinery with MEC and RNIS. This results in improved safety and increased operational efficiency [20; 36].  
In short, the service acts as an effective bridge between the RAN and applications at the network's edge, ensuring the efficient flow of information, proper validation, and accurate delivery to consumers registered with RNIS. The proposal aims to implement the RNIS as a service and serve agricultural applications, seeking appropriate times for such applications. In this way, efforts are focused on the ability to receive information (requests from the RAN) and process it, preparing it for interested consumers.