name: H-SFN
full_form: Hyper System Frame Number
context: When extended DRX (eDRX) is used, the following applies: - For RRC_INACTIVE, eDRX configuration for RAN paging is decided and configured by NG-RAN. In RRC_INACTIVE the UE monitors both RAN and CN paging; - For RRC_IDLE, eDRX for CN paging is configured by upper layers. In RRC_IDLE the UE monitors only CN paging; - Information on whether eDRX for CN paging and RAN paging is allowed on the cell is provided separately in system information; - The maximum value of the eDRX cycle is 10485.76 seconds (2.91 hours) while the minimum value of the eDRX cycle is 2.56 seconds; - The hyper SFN (H-SFN) is broadcast by the cell and increments by one when the SFN wraps around; - Paging Hyperframe (PH) refers to the H-SFN in which the UE starts monitoring paging according to DRX during a Paging Time Window (PTW). The PH and PTW are determined based on a formula (see TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ]  [10]) that is known by the AMF, UE and NG-RAN; - H-SFN, PH and PTW are used if the eDRX cycle is greater than 10.24 seconds; - When the RRC_IDLE eDRX cycle is longer than the system information modification period, the UE verifies that stored system information remains valid before resuming/establishing an RRC connection.
description: The Hyper System Frame Number (H-SFN) is a unique identifier broadcast by cells in a network. It increments by one when the System Frame Number (SFN) wraps around, serving as a reference point for UEs to monitor paging during a Paging Time Window (PTW). The H-SFN plays a crucial role in extended DRX (eDRX) configurations, particularly when the eDRX cycle exceeds 10.24 seconds.
explanation: H-SFN is classified as an Identifier because it serves as a unique reference point for UEs to synchronize their monitoring of paging messages from the network. This identifier is essential in managing extended DRX cycles and ensuring that UEs can efficiently receive paging information, aligning with the specifications outlined in 3GPP TS 38.300.
section_title: 9.2.10 Extended DRX for RRC_IDLE and RRC_INACTIVE
biotag_Context: O,O,B-Procedure,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Network,O,B-Network,O,O,O,O,B-Procedure,O,B-Network,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Network,O,O,O,O,O,B-Procedure,O,B-Network,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,B-Procedure,O,O,O,O,O,B-Parameter,O,O,O,B-Device,O,O,O,O,O,B-Procedure,O,O,B-Parameter,I-Parameter,I-Parameter,O,O,B-Message,O,B-Parameter,O,O,O,O,O,O,O,B-Specification,O,O,B-Device,I-Device,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Message,O,B-Parameter,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Protocol,O
biotag_Description: O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Parameter,I-Parameter,I-Parameter,O,O,B-Parameter,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,B-Procedure,O,O,O,O