Network Requested Session

Description

Network Requested Session (NRS) is a standardized mechanism within 3GPP management frameworks that allows the network to proactively establish a session with a User Equipment (UE) without requiring an initial request from the device itself. This capability is fundamental for operator-initiated tasks, such as Over-The-Air (OTA) device configuration, firmware updates, or diagnostic procedures. The process is governed by the Service-Based Management Architecture (SBMA) principles, where management services can invoke session establishment as defined in specifications like TS 28.404. The network, typically through a Management Function (MF) or an Operations, Administration and Maintenance (OAM) system, identifies a target UE based on criteria like subscription data or network policies. It then triggers the session establishment procedure, which involves core network elements to locate and page the UE if it is in idle mode, ultimately setting up a data session (e.g., a Packet Data Protocol (PDP) context in GPRS or a PDU Session in 5G) dedicated to the management task. This session provides the necessary bearer for transporting management messages, such as those using the Open Mobile Alliance Device Management (OMA DM) protocol or other management protocols, directly to the device. The architecture ensures secure and authorized initiation, often integrating with home subscriber servers and policy control functions to verify permissions. NRS plays a critical role in enabling efficient, large-scale device management, reducing manual intervention, and ensuring devices remain compliant with network policies and software versions, thereby enhancing overall network reliability and service quality.

Purpose & Motivation

The purpose of Network Requested Session (NRS) is to solve the problem of passive device management, where operators previously had to wait for devices to connect or rely on user-initiated actions for maintenance tasks. Historically, managing millions of devices—such as smartphones, IoT sensors, or modems—required inefficient methods like waiting for periodic device check-ins or sending SMS triggers, which were unreliable and slow. NRS was created to give network operators proactive control, enabling them to initiate sessions on-demand for critical operations like security patches, configuration updates, or fault diagnostics. This addresses limitations in scalability and timeliness, particularly as networks evolved to support massive IoT deployments and required more automated operations. By standardizing this capability in 3GPP, starting from Release 7, it provided a unified framework across different access technologies (e.g., GERAN, UTRAN, E-UTRAN, NR), ensuring interoperability and efficient resource use. The motivation stems from the growing need for remote management in complex networks, reducing operational costs, and improving service availability without depending on user behavior.