Description
Radio Network Information Service (RNIS) is a 3GPP-defined service that exposes radio network information to authorized external entities, such as application service providers (ASPs) and edge application platforms. It is part of the Service Capability Exposure Function (SCEF) and Network Exposure Function (NEF) framework, which allows third parties to access network capabilities in a controlled and secure manner. RNIS was introduced in Release 18 as part of the work on edge computing and network exposure, with specifications in 3GPP TS 23.436 (Edge Computing) and TS 23.700 (Study on enhancement of network exposure). The service enables applications to obtain real-time or near-real-time information about the radio access network (RAN), such as cell load, user equipment (UE) location, radio link quality, and available radio resources, which can be used to optimize application behavior and improve user experience.
RNIS operates through a set of APIs defined by 3GPP, typically based on RESTful principles, that allow an application to query or subscribe to radio network information. The service is provided by the network exposure function (NEF) or SCEF, which acts as a gateway between the external application and the 3GPP network. The NEF/SCEF authenticates and authorizes the application, and then retrieves the requested information from the appropriate network functions, such as the Access and Mobility Management Function (AMF), Session Management Function (SMF), or the RAN itself via the Operations, Administration, and Maintenance (OAM) system. The information is then formatted and returned to the application according to the API specification.
Key types of information exposed by RNIS include cell-level load and congestion, radio resource utilization, UE radio link quality (e.g., RSRP, RSRQ, SINR), UE location (cell ID or geographic coordinates), and network slice-related radio information. This data can be used by applications to adapt video streaming bitrates, adjust edge computing offloading decisions, or optimize traffic routing. For example, an edge application hosting a cloud gaming service could use RNIS to detect when a UE is experiencing poor radio conditions and proactively reduce the game's bitrate or switch to a lower-latency server. Similarly, a content delivery network could use RNIS to select the best edge node for a user based on current cell load.
RNIS is designed with privacy and security in mind. Access to radio network information is subject to authorization and policy control, and the granularity of information can be restricted to avoid revealing sensitive user data. The service supports both one-time queries and event-based subscriptions, allowing applications to receive notifications when certain conditions are met (e.g., cell load exceeds a threshold). The 3GPP specifications define the data models, API operations, and security mechanisms for RNIS, ensuring interoperability across vendors and networks.
In the broader 3GPP architecture, RNIS is one of several exposure services, alongside Monitoring Event Exposure, Background Data Transfer, and Network Status Exposure. It plays a crucial role in enabling edge computing and application-aware network optimization, which are key features of 5G and beyond. By providing radio network information to external applications, RNIS helps bridge the gap between the network and the application layer, enabling a more responsive and efficient ecosystem.
Purpose & Motivation
RNIS was created to enable external applications to access radio network information in a standardized and secure way, addressing the need for context-aware optimization in 5G networks. Previously, such information was only available within the network operator's domain, limiting the ability of third-party applications to adapt to changing radio conditions. RNIS solves this by exposing controlled, authorized access to radio network data through standardized APIs, enabling use cases such as edge computing, adaptive streaming, and network-aware application optimization. Its introduction in Release 18 reflects the growing importance of network exposure and edge computing in 5G, and it builds on the existing SCEF/NEF framework to provide a consistent and secure exposure mechanism.
What changed in its specifications
The latest release-to-release comparison of specifications that define RNIS. Each summary describes the whole specification, not only this term.
Rel-19 adds new clauses and APIs for analytics procedures. These cover data storage, edge computing preparation, collision detection, and location-related UE group analytics.
Full comparison in TS 23.436 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference RNIS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.436 vk20 | Application Data Analytics Enablement | Rel-20 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |