Section: 5.3.16 Extended DRX cycle for UEs in 5GMM-IDLE and 5GMM-CONNECTED mode with RRC inactive indication
Content: Extended DRX (eDRX) cycle is supported for a UE in N1 mode. When eDRX is requested by the UE and accepted by the network: - if the UE is not in NB-N1 mode, eDRX is used when the UE is in 5GMM-IDLE mode or in 5GMM-CONNECTED mode with RRC inactive indication; or - if the UE is in NB-N1 mode, eDRX is used when the UE is in 5GMM-IDLE mode. The UE may request the use of eDRX cycle during a registration procedure by including the Requested extended DRX parameters IE (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ]  [8] and 3GPP TS 23.502[ Procedures for the 5G System (5GS) ]  [9]). The UE shall not request the use of eDRX during a registration procedure for emergency services. The UE may use the extended idle mode DRX cycle length stored in the USIM (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ]  [22]) when requesting the use of eDRX. The UE and the network may negotiate eDRX parameters during a registration procedure when the UE has an emergency PDU session. The network accepts the request to use the eDRX by providing the Negotiated extended DRX parameters IE when accepting the registration procedure. The UE shall use eDRX only if it received the Negotiated extended DRX parameters IE during the last registration procedure and the UE does not have an emergency PDU session. NOTE 1: If the UE wants to keep using eDRX, the UE includes the Extended DRX parameters IE in each registration procedure. If the UE received the Negotiated extended DRX parameters IE during the last registration procedure, upon successful completion of the PDU session release procedure of the emergency PDU session, the UE shall resume eDRX. If the network has provided the Negotiated extended DRX parameters IE during the last registration procedure, upon successful completion of the PDU session release procedure of the emergency PDU session, the network shall resume eDRX. If the UE or the network locally releases an emergency PDU session, the UE or the network shall not use eDRX until the UE receives eDRX parameters during a registration procedure with PDU session context synchronization or upon successful completion of a service request procedure with PDU session context synchronization. If the UE did not receive the Negotiated extended DRX parameters IE, or if the UE has an emergency PDU session, the UE shall use the stored UE specific DRX parameter, if available. If the network did not accept the request to use eDRX, or if the UE has an emergency PDU session, the network shall use the stored UE specific DRX parameter, if available. If the network provided the Negotiated extended DRX parameters IE and also assigned a new 5G-GUTI for the UE as described in subclause 5.5.1.3.4 during the last registration procedure, the network shall use the stored UE specific DRX parameter, if available, with the old 5G-GUTI and use the eDRX provided by the network with the new 5G-GUTI until the old 5G-GUTI can be considered as invalid by the network (see subclauses 5.4.4.4 and 5.5.1.3.4). NOTE 2: If the UE using eDRX has joined one or more multicast MBS sessions or wants to receive the traffic of broadcast MBS sessions, the upper layers of the UE provide the lower layers with the MBS start time and the scheduled activation times of the respective MBS session if any of those times are obtained via the service announcement as specified in 3GPP TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ]  [53]. This interaction between the upper layers and the lower layers is out of scope of the present document.