name: ISR
full_form: Idle mode Signaling Reduction
context: Figure J.4-1 shows a downlink data transfer to an idle state UE when ISR is activated. The Serving GW receives downlink data. Because of activated ISR, the Serving GW has control connections with both MME and SGSN and sends therefore downlink data notifications to both nodes. MME and SGSN start their paging procedures, which results in paging of the UE in the registered RA and TA(s) in parallel. In the example illustrated in Figure J.4-1 it is assumed that the UE camps on E-UTRAN. So the UE responds to paging as usual with Service Request. This triggers the MME to setup the user plane connection between eNodeB and Serving GW. The downlink data are transferred to the UE. When the UE camps on UTRAN/GERAN it performs the paging response as specified for these access systems without any required update or other signalling before. The downlink data are then transferred via UTRAN/GERAN to the UE. Figure J.4-1: Downlink data transfer with ISR active
description: Idle mode Signaling Reduction (ISR) is a procedure in mobile networks that aims to reduce signaling overhead when a user equipment (UE) is in idle mode. It allows the Serving Gateway (Serving GW) to maintain control connections with both the Mobility Management Entity (MME) and the Serving GPRS Support Node (SGSN), enabling it to send downlink data notifications to both nodes simultaneously. This procedure streamlines the process of paging the UE, whether it is camping on E-UTRAN, UTRAN, or GERAN, by eliminating the need for additional signaling updates before transferring downlink data.
explanation: ISR is classified as a Procedure because it outlines a specific sequence of operations that network components follow to manage idle mode signaling efficiently. This includes the Serving GW's handling of control connections and downlink data notifications, the MME and SGSN's initiation of paging procedures, and the UE's response to paging across different access systems.
section_title: J.4 Downlink data transfer
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,B-Device,O,B-Procedure,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,B-Procedure,O
biotag_Description: B-Procedure,I-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O