Method and apparatus for paging in mobile wireless communication system

The terminal device's adaptive paging mechanism optimizes energy consumption by switching between energy-efficient and legacy modes, addressing inefficiencies in wireless communication systems.

KR103039748B1Active Publication Date: 2026-10-30주식회사 세틀랩
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
KR1020260051756
Authority / Receiving Office
KR · KR
Patent Type
Patents
Current Assignee / Owner
Priority Date
2025-04-07
Filing Date
2026-03-23
Publication Date
2026-10-30
Estimated Expiration
2046-03-23

AI Technical Summary

Technical Problem

Existing wireless communication systems face inefficiencies in energy consumption due to unnecessary paging opportunities, particularly in low-load cell scenarios, leading to unnecessary energy waste and suboptimal network performance.

Method used

A terminal device with adaptive paging capability that supports both baseline and enhanced paging opportunity determination methods, allowing it to switch between energy-efficient operation and seamless interoperability with legacy and enhanced networks based on network conditions.

Benefits of technology

The solution optimizes energy consumption while maintaining network efficiency by adapting paging strategies, reducing energy waste in low-load scenarios and preserving congestion mitigation in high-load scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 112026034926477-PAT00006_ABST
    Figure 112026034926477-PAT00006_ABST
Patent Text Reader

Abstract

Zone's New Radio (NR) systems utilize a paging transmission method that distributes paging opportunities (PO) in the time domain to alleviate random access congestion; however, this consumes significant energy because base station transmitters must remain continuously active. While this distributed approach is reasonable in high-load scenarios where random access congestion may occur, it is inefficient in various network configurations, including low-load cells with a low probability of congestion, and results in wasted network energy without providing substantial benefits from distributed PO allocation. The present invention introduces an enhanced paging method that condenses paging opportunities in the time domain, enabling base stations to achieve significant energy savings by deactivating transmitters between condensed PO intervals. Efficient procedures, signaling mechanisms, terminal device implementations, and network implementations are provided to enable seamless coexistence and optimal energy management based on network load conditions, allowing legacy terminals that support only the basic PO determination method and new terminals that support both the basic and enhanced methods to coexist within the same network.
Need to check novelty before this filing date? Find Prior Art

Description

Technology Field

[0001] The present disclosure relates to a method and apparatus for performing paging in a wireless mobile communication system. Background Technology

[0002] Fifth-generation (5G) systems are being developed to meet the demand for increasing wireless data traffic following the commercialization of fourth-generation (4G) communication systems. 5G systems have introduced millimeter-wave (mmW) frequency bands (e.g., the 60 GHz band). Various technologies such as beamforming, MIMO (massive multiple-input multiple output), FD-MIMO (full dimensional MIMO), array antennas, analog beamforming, and large-scale antennas are being introduced to mitigate propagation loss and extend propagation range in 5G communication systems. Additionally, base stations have been divided into a central section and multiple distribution sections to enhance scalability. The problem to be solved

[0003] The present disclosure provides a method and apparatus for performing paging in a wireless mobile communication system. means of solving the problem

[0004] The present invention provides a terminal device for receiving adaptive paging in a wireless communication system. The terminal device enables energy-efficient operation by supporting both a baseline paging opportunity determination method and an enhanced paging opportunity determination method.

[0005] According to one embodiment of the present invention, the terminal device includes a transceiver configured to transmit and receive wireless signals, and a controller operably coupled to the transceiver to manage paging monitoring operations.

[0006] The controller is configured to receive system information from a base station, and the system information includes at least a first parameter indicating the number of paging opportunities and a first parameter specifying a paging frame offset. Based on the received system information and applicable conditions, the controller determines a starting monitoring opportunity number for a specific set of consecutive monitoring opportunities and monitors at least one monitoring opportunity within the set.

[0007] As a key feature of the present invention, the terminal implements a condition-based paging opportunity determination logic. Specifically, when a first specific condition is satisfied, the start monitoring opportunity number is determined based on a second parameter associated with the first monitoring opportunity. The first specific condition refers to a case where the system information includes the second parameter associated with the first monitoring opportunity and paging adaptation is applied by the network.

[0008] Meanwhile, if a second specific condition is satisfied, the start monitoring opportunity number is determined based on a first parameter associated with the first monitoring opportunity. The second specific condition means that at least the system information includes the first parameter associated with the first monitoring opportunity.

[0009] Through this dual-mode operation, the terminal can support both the legacy distributed paging opportunity allocation method and the enhanced condensed paging opportunity method within the same network. When the network applies paging adaptation and provides a second parameter, the terminal operates in an energy-efficient enhanced mode with condensed paging opportunities. Conversely, when paging adaptation is not applied or only the first parameter is provided, the terminal reverts to the default paging opportunity determination method to ensure backward compatibility with legacy network configurations.

[0010] By implementing the adaptive paging monitoring mechanism of the present invention, the terminal achieves optimal energy consumption while maintaining seamless interoperability with both legacy and enhanced network deployments. Accordingly, the present invention provides a flexible and efficient solution for various network deployment conditions by solving the technical problem of unnecessary energy waste in low-load cell scenarios while preserving the congestion mitigation benefits of distributed paging in high-load scenarios. Effects of the invention

[0011] The present disclosure provides a method and apparatus for performing paging with enhanced network energy efficiency in a wireless mobile communication system. Brief explanation of the drawing

[0012] Figure 1 is a diagram showing the structure of a 5G system and NG-RAN. Figure 2 is a diagram showing the wireless protocol structure in a 5G system. Figure 3 illustrates the overall operation of the UE and the network. Figure 4 illustrates an SS / PBCH block. Figure 5 illustrates an improved paging method. Figure 6 illustrates the operation of a terminal and a network. Figure 7 illustrates the operation of a terminal and a network. Figure 8 is a diagram showing the operation of a terminal. FIG. 9 is a block diagram showing the internal structure of the UE according to the initiation. FIG. 10 is a block diagram showing the internal structure of a base station according to the initiation. Specific details for implementing the invention

[0013] A feasible solution to promote energy conservation on the network side is to provide the opportunity to turn off downlink transmission at base stations. One example of downlink transmission to be turned off is system information. System information is transmitted periodically to provide the information necessary for access to the cell by an unspecified number of terminals.

[0014] In certain situations, if access to a cell may be delayed, the transmission of such system information may not be necessary. For example, if the geographical coverage of a cell is covered by another cell, the terminal may first camp on to the other cell (e.g., an anchor cell) and then access the cell (non-anchor cell) from the other cell, possibly based on support information obtained from the other cell.

[0015] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Furthermore, in the description of the present disclosure, if it is determined that a detailed description of related known functions or configurations may unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure and may vary depending on the intent or convention of the user and operator. Therefore, they must be defined based on the entire content of this specification.

[0016] In the following description, the terms used to denote access nodes, network entities, messages, interfaces between network entities, and various identity information are provided for the convenience of explanation. Therefore, the terms used in the following description are not limited to specific meanings and may be replaced with other terms corresponding to their technical meanings.

[0017] In the following description, terms and definitions set forth in 3GPP standards are used for convenience of explanation. However, the present disclosure is not limited by the use of such terms and definitions, and any other terms and definitions may be used instead.

[0018] In the present disclosure, "trigger" or "triggered" and "initiate" or "initiated" may be used interchangeably.

[0019] In the present disclosure, the UE, terminal, and wireless device may be used interchangeably. In the present disclosure, the NG-RAN node, base station, and GNB may be used interchangeably.

[0020] The 5G system consists of NG-RAN 1A01 and 5GC 1A02. The NG-RAN node is one of the following.

[0021] >1: gNB providing NR user plane and control plane protocol termination for the UE; or

[0022] >1: ng-eNB providing E-UTRA user plane and control plane protocol termination toward the UE.

[0023] The gNBs (1A05 or 1A06) and ng-eNBs 1A03 or 1A04 are interconnected via the Xn interface. The gNBs and ng-eNBs are connected to the 5GC, more specifically the Access and Mobility Management Function (AMF) and User Plane Function (UPF), via the NG interface. The AMF 1A07 and UPF 1A08 can be implemented as physical nodes or as separate physical nodes.

[0024] gNB 1A05 or 1A06 or ng-eNB 1A03 or 1A04 hosts the various functions listed below.

[0025] >1: Functions for radio resource management such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, and dynamic allocation (scheduling) of resources for UEs in uplink, downlink, and sidelink; and

[0026] >1: IP and Ethernet header compression, uplink data decompression and user data stream encryption; and

[0027] >1: A step of selecting an AMF from the UE attachment when routing to the MME cannot be determined from the information provided by the UE; and

[0028] >1: User plane data routing with UPF; and

[0029] >1: Scheduling and transmission of paging messages and

[0030] >1: Scheduling and transmission of broadcast information (initiated by AMF or O&M) and

[0031] >1: Configuration of measurement and measurement reporting for mobility and scheduling; and

[0032] >1: Session management; and

[0033] >1: QoS flow management and mapping for data wireless bearers; and

[0034] >1: Support for UEs in RRC_INACTIVE state; and

[0035] AMF 1A07 hosts functions such as NAS signaling, NAS signaling security, AS security control, SMF selection, authentication, mobility management, and positioning management.

[0036] UPF 1A08 hosts functions such as packet routing and forwarding, transport-level packet presentation for uplink, QoS handling and downlink, and mobility anchoring for mobility.

[0037] The user plane protocol stack consists of SDAP 1B01 or 1B02, PDCP 1B03 or 1B04, RLC 1B05 or 1B06, MAC 1B07 or 1B08, and PHY 1B09 or 1B10. The control plane protocol stack consists of NAS 1B11 or 1B12, RRC 1B13 or 1B14, PDCP, RLC, MAC, and PHY.

[0038] Each protocol sublayer performs functions related to the tasks listed below.

[0039] NAS: Authentication, mobility management, security monitoring, etc.

[0040] RRC: System information, paging, establishment, maintenance, and release of RRC connections, security functions, establishment, configuration, maintenance, and release of Signaling Radio Bearer (SRB) and Data Radio Bearer (DRB), mobility, QoS management, wireless link failure detection and recovery, NAS message transmission, etc.

[0041] SDAP: Mapping between QoS flows and data wireless bearers, and displays the QoS flow ID (QFI) in both DL and UL packets.

[0042] PDCP: Data transmission, header compression and decompression, encryption and decryption, integrity protection and integrity verification, replication, reordering and sequential delivery, non-sequential delivery, etc.

[0043] RLC: Transmission of upper-layer PDUs, error correction via ARQ, segmentation and resegmentation of RLC SDUs, SDU reassembly, RLC reconstruction, etc.

[0044] MAC: Mapping between logical channels and transmission channels, multiplexing / demultiplexing MAC SDUs belonging to one or another logical channel to the physical layer of the transmission channel or to transmission blocks (TBs) delivered from the transmission channel, reporting scheduling information, handling priorities between UEs, handling priorities between logical channels of a single UE, etc.

[0045] PHY: Channel coding, physical layer hybrid-ARQ processing, rate matching, scrambling, modulation, layer mapping, downlink control information, uplink control information, etc.

[0046] When switching on the wireless device (e.g., UE) 2A11, the UE performs PLMN select 2A21 to select a carrier provided by a PLMN that the UE can register.

[0047] Then, the UE performs cell selection 2A31 to camp into the appropriate cell.

[0048] When camping in a suitable cell, the UE performs RRC_IDLE mode operations 2A41, such as paging channel monitoring, cell reselection, and obtaining system information.

[0049] The UE performs the RRC connection setup procedure 2A51 to perform NAS procedures, such as initial registration for a selected PLMN, for example.

[0050] After successfully establishing an RRC connection, the UE performs NAS procedure 2A61 by transmitting the corresponding NAS message through the established RRC connection (e.g., SRB1).

[0051] The base station may trigger UE capability reporting procedure 2A71 before configuring the data bearer and various MAC functions.

[0052] The base station and the UE perform the RRC connection reconfiguration procedure 2A81. Through this procedure, the data radio bearer, logical channel, various MAC functions (e.g., DRX, BSR, PHR, and beam failure reporting, etc.), and various RRC functions (e.g., RRM, RLM, measurement, etc.) are configured.

[0053] The base station and the UE perform data transmission 2A91 through an established radio bearer and based on the configured MAC function and configured RRC function.

[0054] If the UE's geographical location changes, for example, when the current serving cell no longer provides suitable radio conditions, the base station and the UE perform cell-level mobility such as handover, conditional reconfiguration, or lower-layer triggered mobility.

[0055] For example, if an RRC connection to a UE is no longer needed because there is no longer any traffic available for the UE, the base station and the UE perform the RRC disconnection procedure 2A101. The base station may transmit the UE status as RRC_IDLE (when low data activity of the UE is expected) or RRC_INACTIVE (when high data activity of the UE is expected).

[0056] The UE performs the RRC_IDLE action or RRC_INACTIVE mode action 2A111 until the next event for RRC connection establishment / resumption occurs.

[0057] The synchronization signal and PBCH block (SSB) (2E10) consists of a primary synchronization signal (PSS) (2E20) and a secondary synchronization signal (SSS) (2E30). The PSS and SSS occupy one symbol and 127 subcarriers. The PBCH (2E40) spans three OFDM symbols and 240 subcarriers, the possible time positions of the SSB within the half-frame are determined by the subcarrier spacing, and the periodicity of the half-frame in which the SSB is transmitted is configured by the network. During the half-frame, different SSBs can be transmitted in different spatial directions (i.e., using different beams, across the cell's coverage area).

[0058] Short-period paging transmission consumes significant base station energy. NR systems use a paging transmission method that keeps base station transmitters awake by distributing paging opportunities across the time domain. This is a reasonable approach, as otherwise random access congestion could occur.

[0059] Because various types of networks / cells have been deployed (and are scheduled to be deployed), random access congestion may not be an issue in some cases (e.g., low-load cells where random access congestion may not occur), and "distributed paging opportunities" may only consume network energy without providing any substantial benefit.

[0060] By compressing paging opportunities in the time domain, the base station can turn off the receiver until the next paging opportunity arises, leading to network energy savings.

[0061] The UE can only support baseline PO decision schemes (distributed multiple PO groups) or enhanced PO decision schemes (condensed multi-PO group or single PO group).

[0062] In the case of RAN paging, based on UE capability and base station capability, the base station sends paging messages to the UE according to the basic scheme or the enhanced scheme.

[0063] In the case of CN paging, based on UE capability, base station capability, and CN capability, the base station sends paging messages to the UE according to the basic scheme or enhanced scheme.

[0064] Paging schemes and PO decision schemes are used interchangeably.

[0065] Enhanced paging scheme and NES paging scheme are used interchangeably.

[0066] Enhanced paging (transmission / scheme / reception) and NES paging (transmission / scheme / reception) are used interchangeably.

[0067] PTW is the CN configuration PTW unless otherwise specified.

[0068] Paging is a paging message, paging transmission, paging reception, or paging scheme.

[0069] DRX cycle, DRX value, and T are used with the same meaning.

[0070] CN Paging RAN Paging >: Initiated by CN / AMF >: Paging messages include 5G-S-TMSI >: Monitored and received by both RRC_IDLE UEs and RRC_INACTIVE UEs >: Started by GNB >: Paging messages include fullI-RNTI >: Monitored and received by UE in RRC_INACTIVE

[0071] Basic paging NES Paging This is paging applied when specific instructions regarding NES paging are not included in specific system information. It is paging applied to UEs that do not support NES paging (UEs not configured with NES paging). Paging opportunities for DRX cycles are distributed across DRX cycles. Paging applied to UE: >: If specific instructions regarding NES paging are included in specific system information; >: If the UE supports NES paging (UE with NES paging configured). Paging opportunities for the DRX cycle are compressed into a specific part of the DRX cycle.

[0072] NsExt and pagingAdaptation-NS are used interchangeably. Enhanced paging scheme and paging-adaptation are used interchangeably. If the operation associated with T is for CN-initial paging, T and T_cn are used interchangeably. If the operation associated with T is for RAN-initial paging, T and T_ran are used interchangeably. N is the number of PFs per T. From the UE perspective, there is only one PF per T. From the NW perspective, there may be one or more PFs per T. Multiple PFs per T are advantageous in terms of load balancing. Multiple PFs per T are disadvantageous in terms of NW power savings. N is controlled by nAndPagingFrameOffset and pagingAdaptationNAndPagingFrameOffset. nAndPagingFrameOffset indicates one of [oneT, halfT, quarterT, oneEighthT, oneSixteenthT]. pagingAdaptationNAndPagingFrameOffset specifies one of [oneT, halfT, quarterT, oneEighthT, oneSixteenthT, oneThirtySecondT]. As the parameter names imply, oneT means that N is equal to T (in terms of radio frames), oneEighthT means that N is equal to T / 8 (e.g., if T is 256 radio frames, N is 32), oneThirtySecondT means that N is equal to T / 32 (e.g., if T is 256 radio frames, N is 8), and so on. The smaller N is, the better the NW power efficiency. The larger N is, the better the load balancing. For UEs that do not support paging adaptation, N is controlled by nAndPagingFrameOffset.For UEs that support paging adaptation, NW controls N via pagingAdaptationNAndPagingFrameOffset.PTW:.

[0073] >: When the UE is running on an extended DRX, the time period during which paging is transmitted

[0074] Configuration parameters for PTW are configured via NAS messages.

[0075] Paging opportunities for UEs during the DRX cycle consist of one or more PMOs or POs.

[0076] PMO:

[0077] >: PDCCH monitoring opportunity for paging;

[0078] A PMO consists of one or more consecutive symbols (indicated as monitoringSymbolsWithinSlot in IE, corresponding to the SearchSpace in pagingSearchSpace).

[0079] The PMO is located in the slot.

[0080] PMOs that do not overlap with UL symbols (determined by tdd-UL-DL-ConfigurationCommon) are numbered sequentially starting from 0, beginning with the first PMO of the PF.

[0081] PO / PMOG:

[0082] >: Paging Event / PMO Group

[0083] A series of consecutive PMOs;

[0084] A PO consists of one or more time slots (a PO may span two or more slots).

[0085] PO consists of a series of S*X PMOs.

[0086] >>: S is the number of actual transmitted SSBs determined by SIB1's ssb-PositionsInBurst.

[0087] >>: X is nrofPDCCH-MonitoringOccasionPerSSB-InPO if configured, and equal to 1 otherwise.

[0088] In the PO, the [x*S+K]th PMO corresponds to the Kth transmitted SSB.

[0089] POG:

[0090] >: Paging Event Group;

[0091] POG consists of Ns / NsExt continuous PO.

[0092] The POG is connected to a reference point (e.g., the first symbol of a paging frame).

[0093] Each PO in the POG is indexed sequentially from 0 to Ns - 1.

[0094] DRX 1 POG per cycle.

[0095] PF (or Reference Point):

[0096] >: Paging Frame;

[0097] PF provides a reference point for determining the starting point of one or more POs (one or more POs belonging to the same POG).

[0098] The reference point for determining the starting point is the first PMO of a specific wireless frame (e.g., PF).

[0099] T_CN: UE-specific DRX value set by the upper layer (consisting of Registration Accept messages).

[0100] T_RAN: UE-specific DRX value set by RRC (included in RRCRelease).

[0101] T_E_CN: TeDRX_CN (composed of Registration Accept message), DRX value / cycle extension for CN paging, T_eDRX_CN. Consists of extended DRX parameters.

[0102] T_E_RAN: TeDRX_RAN (configured by RRCRelease), DRX value / cycle extension for RAN paging, configured by T_eDRX_RAN.ExtendedPagingCycle-r17

[0103] T_D: Broadcast the default DRX value per cell from System Information (SIB1).

[0104] N: Total number of paging frames of T (or number of RPs of T)

[0105] PF_offset: Offset used for PF measurement

[0106] Ns: Number of paginations for PF (Number of POs for RP, Number of POs for POG)

[0107] UE_ID: 10 LSB of the UE's 5G-S-TMSI (if the UE is not operating in eDRX) or 12 LSB (if the UE is operating in eDRX). Used to determine PF(RP) and PO index (PMOG index).

[0108] first_T, first_N: Parameters / inputs used to determine a specific frame (PF) containing the reference point (reference PMO, first PMO).

[0109] Second_T, second_N: These are parameters / inputs used to determine the PO index.

[0110] For a UE of RRC_IDLE: first_T and second_T are equal or identical. first_N and second_N are equal or identical.

[0111] For UEs of RRC_INACTIVE: first_T and second_T differ in certain cases. First_N and second_N differ in certain cases. first_T and second_T are the same in other cases. First_N and second_N are the same in other cases.

[0112] Generally, PMO / PO / PF is determined as follows.

[0113] The UE's DRX cycle consists of one or more RPs (NRP).

[0114] RP is connected to POG (one or more consecutive POs).

[0115] POG consists of one or more consecutive POs (Ns / NsExt PO).

[0116] A PO consists of one or more consecutive PMOs (S*X PMOs).

[0117] The DRX cycle consists of (N * Ns * S * X) PMOs.

[0118] >>: N instances of consecutive (Ns / NsExt * S * X) PMOs;

[0119] >>: N instances of consecutive Ns / NsExt POs;

[0120] UE determines RP among N RPs.

[0121] >>: UE determines PF.

[0122] >>: UE determines RP based on the determined PF;

[0123] The UE determines a PO from one of the more POs of the POG associated with the RP;

[0124] The UE determines the index (i_s) of the PO to be monitored.

[0125] The UE determines the time domain location of the PMOs of the POs being monitored.

[0126] >>: If firstPDCCH-MonitoringOccasionOfPO is configured:

[0127] >>>: The number of the starting PDCCH PMO (Monitoring Occasion) of the (i_s + 1)th PO is the (i_s + 1)th value of the first PDCCH-MonitoringOccasionOfPO parameter.

[0128] >>: If firstPDCCH-MonitoringOccasionOfPO is not configured:

[0129] >>>: The starting PMO number is equal to i_s * S*X.

[0130] >>: Determines the PMO number and the time domain start point of the corresponding PMO based on pagingSearchSpace's SearchSpace IE and tdd-UL-DL-ConfigurationCommon.

[0131] The UE monitors one or more PMOs of the PO determined based on the RSRP of the downlink path loss reference (e.g., SSB).

[0132] The value contained in firstPDCCH-MonitoringOccasionOfPO or firstPDCCH-MonitoringOccasionOfPOext indicates which symbol is the first symbol of the first PMO of the corresponding PO.

[0133] For all paging schemes, T is determined as follows.

[0134] T is the DRX cycle / value of the UE used to determine the RP and PO indices.

[0135] T_E_CN and T_eDRX_CN are used with the same meaning.

[0136] T_E_RAN and T_eDRX_RAN are used with the same meaning.

[0137] The UE-specific DRX value set by RRC is T_RAN.

[0138] The UE-specific DRX value set by the upper layer is T_CN.

[0139] If the UE does not work with eDRX:

[0140] T is determined by the shortest value among the UE-specific DRX value set by RRC (if any), the UE-specific DRX value set by the upper layer (if any), and the default DRX value broadcast from system information.

[0141] In the RRC_IDLE state, if the UE operates on eDRX and the eDRX is configured by a higher layer, namely T_eDRX_CN, it is as follows.

[0142] If T_eDRX_CN is 1024 radio frames or less:

[0143] >> : T = T_eDRX_CN;

[0144] Besides:

[0145] >>: During CN configured PTW, T is determined by the shortest value among UE-specific DRX values ​​when configured by the upper layer, and by the default DRX value broadcast from system information.

[0146] In the RRC_INACTIVE state, if the UE operates on an eDRX and the eDRX is configured by the RRC, i.e., T_eDRX_RAN (if present) and the upper layer, i.e., T_eDRX_CN:

[0147] If both T_eDRX_CN and the used T_eDRX_RAN are 1024 radio frames or less, then T = min{T_eDRX_RAN, T_eDRX_CN}.

[0148] If T_eDRX_CN does not exceed 1024 radio frames and T_eDRX_RAN is set or not used, T is determined by the shortest value among the UE-specific DRX values ​​set by RRC and T_eDRX_CN.

[0149] If T_eDRX_CN is longer than 1024 radio frames:

[0150] >>: If T_eDRX_RAN is configured or not in use:

[0151] >>>: During the CN configuration PTW, T is determined by the shortest value among the UE-specific DRX value set by RRC, the UE-specific DRX value set by the upper layer (if any), and the default DRX value broadcast from system information. Outside of the PTW set by CN, T is determined by the UE-specific DRX value set by RRC;

[0152] Otherwise, if using T_eDRX_RAN, it is not longer than 1024 radio frames.

[0153] >>>: During the CN configured PTW, T is determined by the shortest of the UE-specific DRX values ​​if set by the upper layer and T_eDRX_RAN, and by the default DRX value broadcast from system information. Outside the CN configured PTW, T is determined by T_eDRX_RAN.

[0154] Otherwise, if using T_eDRX_RAN, it is longer than 1024 radio frames.

[0155] >>>: During the overlap of the CN setting PTW and the RAN setting PTW, T is determined by the shortest value among the UE-specific DRX value set by the RRC, the UE-specific DRX value set by the upper layer (if any), and the default DRX value broadcast from the system information.

[0156] >>>: During CN configuration PTW and external RAN configuration PTW, T is determined by the shortest of the UE-specific DRX values ​​configured by the upper layer (if any) and the default DRX value broadcast from system information.

[0157] >>>: During the PTW outside of the CN-set PTW and the RAN-set PTW, T is determined by the UE-specific DRX value set by the RRC.

[0158] E100 is an exemplary example of the S-POG method when 4 POs are configured per POG.

[0159] FIGS. 6 and FIGS. 7 illustrate operations for paging transmission and paging reception.

[0160] In 610, when power is turned on, the UE performs PLMN selection and cell selection.

[0161] In 620, the UE receives MIB and SIB1 from the selected cell. The UE determines whether the cell is barred. If the cell is not barred, the UE proceeds with the RRC connection establishment procedure. If the cell is barred, the UE selects another cell.

[0162] In 630, the UE and GNB perform the RRC connection establishment procedure. The UE sends an RRCSetupRequest, receives an RRCSetup, and sends an RRCSetupComplete. The UE and GNB establish SRB1.

[0163] In 640, the UE sends ULInformationTransfer containing a REGISTRATION REQUEST message to the GNB. The UE includes an IE in the message indicating support for a paging-adaptation scheme for the NES. The GNB forwards the REGISTRATION REQUEST message to the AMF.

[0164] At 650, the AMF sends REGISTRATION ACCEPT to the GNB. The GNB sends DLInformationTransfer containing REGISTRATION ACCEPT to the UE.

[0165] REGISTRATION ACCEPT includes the following:

[0166] 5G-GUTI including 5G-S-TMSI

[0167] >: Information on whether paging adaptation for NES is allowed in the tracking area. If allowed, the UE applies paging adaptation in the cell if the cell supports / allows paging adaptation for NES.

[0168] In 660, the UE and GNB perform an RRC disconnection to transition to the state of RRC_IDLE. After the NAS registration process is complete, the GNB can disconnect the RRC connection by sending RRCRelease.

[0169] In 670, the UE performs cell selection to find a suitable cell to camp on.

[0170] In 680, the UE receives MIB and SIB1 from the selected cell. The UE determines that the cell is suitable. The UE determines whether the paging adaptation scheme for NES is applied in the cell. If SIB1 contains pagingAdaptationNAndPagingFrameOffset and pagingAdaptation-NS, the UE considers that the paging adaptation scheme for CN-initial paging is supported / allowed in the cell.

[0171] In 690, the UE determines the PO determination method for CN-start paging.

[0172] The UE decides to use the baseline paging scheme in the following cases:

[0173] >: If the UE has not reported / instructed the AMF via REGISTRATION REQUEST that it supports paging adaptation, or if the UE has not received instruction from the AMF via REGISTRATION ACCEPT that paging adaptation is accepted / supported; or

[0174] >: If the UE reports / instructs the AMF that it supports paging adaptation, and the UE receives an instruction from the AMF that paging adaptation is allowed / supported, but SIB1 does not include pagingAdaptationNAndPagingFrameOffset and pagingAdaptation-NS.

[0175] The UE decides to use an adaptive paging method in the following cases:

[0176] >: When the UE reports / instructs the AMF that it supports paging adaptation, and the UE receives an instruction from the AMF that paging adaptation is allowed / supported, and SIB1 includes pagingAdaptationNAndPagingFrameOffset and pagingAdaptation-NS.

[0177] In 700, the UE performs paging monitoring for CN-initial paging based on the determined paging scheme.

[0178] If paging adaptation is not applied in the cell (or if the UE decides to use the default paging method), the UE performs <paging monitoring behavior in RRC_IDLE when paging adaptation is not applied>.

[0179] If paging adaptation is applied in the cell (or if the UE decides to use the paging adaptation method), the UE performs <paging monitoring action in RRC_IDLE when paging adaptation is applied>.

[0180] At 710, the GNB receives a paging message for the UE from the AMF. The GNB decides to use paging adaptation in the following cases:

[0181] >: If the paging message includes a parameter indicating that the UE supports paging adaptation; and

[0182] >: If the cell supports paging adaptation.

[0183] The GNB sends a paging message to the UE. The GNB sends the Paging-DCI to all PMOs of the corresponding PO. The GNB sends a PDSCH containing the paging message according to the scheduling information of the Paging-DCI. The paging message includes the UE's 5G-S-TMSI.

[0184] At 720, the UE performs the procedure to establish an RRC connection with the GNB in ​​response to the paging message containing the UE's 5G-S-TMSI. The UE proceeds to 730. If the paging message does not contain the UE's 5G-S-TMSI, the UE continues the paging monitoring operation for CN-initiated paging.

[0185] In 730, the UE receives UECapabilityEnquiry and transmits UECapabilityInformation. UECapabilityInformation may include the pagingAdaptationSupportInactive field. This field indicates that the UE supports paging adaptation schemes for both CN-initiated paging and RAN-initiated paging.

[0186] In 740, the UE and GNB perform RRC_CONNECTED operations.

[0187] The GNB determines configurations for the UE based on reported capabilities and cell status. The GNB sends RRCReconfiguration to the UE to convey the determined configurations. The UE and GNB perform RRC_CONNECTED operations, such as data transfer and mobility.

[0188] At 750, at some point, the GNB decides to release the RRC connection and transition the UE to the RRC_INACTIVE state. The UE receives RRCRelease from the GNB. RRCRelease includes a suspendConfig field containing various IEs related to RAN-initial paging.

[0189] In 760, the UE performs cell selection and transitions to the state RRC_INACTIVE.

[0190] In 770, the UE receives the MIB and SIB1 from the selected cell. The UE determines that the cell is suitable. The UE determines whether the paging adaptation scheme for NES is applied in the cell. If SIB1 contains pagingAdaptation-NS and pagingAdaptationNAndPagingFrameOffset, the UE considers that the paging adaptation scheme is supported / allowed in the cell for UEs in RRC_INACTIVE.

[0191] In 780, the UE determines the PO determination scheme for RAN-initial paging and CN-initial paging. The UE uses the same paging scheme for RAN-initial paging and CN-initial paging.

[0192] If paging adaptation is not applied in the cell (or if the UE decides to use a paging adaptation scheme), the UE uses the default paging scheme for both RAN-initial paging and CN-initial paging.

[0193] When paging adaptation is applied in a cell (or when the UE decides to use a paging adaptation method), the UE uses a paging adaptation method for both RAN-initial paging and CN-initial paging.

[0194] In 790, if paging adaptation is not applied in the cell, the UE performs the <paging monitoring action in RRC_INACTIVE when paging adaptation is not applied>. If paging adaptation is applied in the cell (or if the UE decides to use paging adaptation in the cell), the UE performs the <paging monitoring action in RRC_INACTIVE when paging adaptation is applied>.

[0195] The UE can perform the following.

[0196] UE determines T_cn, N_cn and i_s_cn;

[0197] The UE determines T_ran, N_ran, and i_s_ran, and

[0198] If the extended DRX value used configured by the upper layer (e.g., T_E_CN) is 1024 radio frames or less,

[0199] >>: The UE uses the same i_s as for the RRC_IDLE state (e.g., the UE uses i_s_cn for both CN-initial paging and RAN-initial paging)

[0200] If the extended DRX value used configured by the upper layer (e.g., T_E_CN) is longer than 1024 radio frames,

[0201] >>: The UE uses the same i_s as for the RRC_IDLE state during CN PTW, i.e.:

[0202] >>>: UE uses T_ran to determine T;

[0203] >>>: The UE uses i_s_cn for both CN-initial paging and RAN-initial paging during CN PTW;

[0204] >>: The UE uses i_s_ran for RAN-initiated paging outside of the CN PTW, i.e.:

[0205] >>>: UE uses T_ran to determine T;

[0206] >>>: UE uses i_s_ran;

[0207] At 793, the GNB decides to page the UE.

[0208] The GNB sends a paging message to the UE. The GNB sends the Paging-DCI to all PMOs of the corresponding PO. Based on the scheduling information of the Paging-DCI, the GNB sends a PDSCH containing the paging message. The paging message includes the UE's I-RNTI.

[0209] In 795, the UE performs a procedure to resume the RRC connection with the GNB in ​​response to the paging message containing the UE's I-RNTI. The UE initiates a procedure to resume the RRC connection. If the paging message does not contain the UE's 5G-S-TMSI, the UE continues the paging monitoring operation for CN-initiated paging and RAN-initiated paging.

[0210] If the paging message contains the UE's 5G-S-TMSI, the UE performs cell selection, <paging monitoring action in RRC_IDLE when paging adaptation is not applied> or <paging monitoring action in RRC_IDLE when paging adaptation is applied>, system information acquisition, and RRC connection establishment procedures.

[0211] To perform paging monitoring, the UE and the network use the same T. There are many factors / parameters that influence T, and the UE and the network select T appropriately based on the given configuration.

[0212] To facilitate discussion, the following cases are defined.

[0213] CASE1: UE is operating on eDRX for CN paging.

[0214] CASE2: UE does not operate on eDRX for CN paging.

[0215] CASE3: UE operates in eDRX with T_RAN_E(>1024) for RAN paging.

[0216] CASE4: UE operates on eDRX with T_RAN_E (=< 1024) for RAN paging.

[0217] CASE5: UE does not operate on eDRX for RAN paging.

[0218] For the RRC_IDLE UE, CASE 1 and CASE 2 are valid. The UE determines the CASE as shown in the table below.

[0219] The UE is configured for eDRX by the upper layer eDRX-AllowedIdle is signaled on SIB1. case Index yes yes CASE1 1 yes no CASE2 2 no yes CASE2 3 no no CASE2 4

[0220] The RRC_INACTIVE UE determines the CASE as shown in the table below.

[0221] The UE is configured for eDRX by ran-ExtendedPagingCycle-r18 eDRX-AllowedInactive-r18 is included in SIB1 The UE is configured for eDRX by ran-ExtendedPagingCycle-r17 eDRX-AllowedInactive-r17 is included in SIB1 CASE Index Y Y Y Y Not applicable 1 Y Y Y N Not applicable 2 Y Y N Y CASE3 3 Y Y N N CASE3 4 Y N Y Y Not applicable 5 Y N Y N Not applicable 6 Y N N Y CASE5 7 Y N N N CASE5 8 N Y Y Y CASE4 9 N Y Y N CASE5 10 N Y N Y CASE5 11 N Y N N CASE5 12 N N Y Y CASE4 13 N N Y N CASE5 14 N N N Y CASE5 15 N N N N CASE5 16

[0222] The UE of RRC_INACTIVE can be a combination of several cases as shown in the table below.

[0223] Operates on eDRX for CN paging Operates on eDRX for RAN paging explanation yes yes CASE1 + CASE 3 / 4 yes no CASE1 + CASE5 no yes impossibility no no CASE2 + CASE5

[0224] T is determined as shown in the table below.

[0225] T Index If the UE does not work in eDRX CASE2 or CASE2 + CASE5 Min [T_RAN,T_CN, T_D] 1 When the UE with RRC_IDLE is operating in eDRX. CASE1 T_ E_CN =<1024 [T_ E_CN] 2 CASE1 T_E_CN > 1024;CN_PTW 중 Among the CN configuration PTW Min [T_CN, T_D]CN configuration PTW outside, UE does not monitor paging and T is not used. 3 When the RRC_INACTIVE UE is operating in eDRX. CASE1 + CASE3 T_E_CN =<1024;T_E_RAN =<1024 Min [T_E_RAN, T_E_CN] 4 CASE1 + CASE3 T_E_CN > 1024;T_E_RAN =<1024 Min [T_CN, T_E_RAN, T_D] among CN configuration PTW. Outside CN configuration PTW, [T_E_RAN] 5 CASE1 + CASE5 T_E_CN =<1024; Does not work on eDRX for RAN paging Min [T_RAN, T_E_CN] 6 CASE1 + CASE5 T_E_CN >1024; Does not work on eDRX for RAN paging Min [T_RAN, T_CN, T_D] among CN configuration PTW. Outside CN configuration PTW, [T_RAN]. 7 CASE1 + CASE4 T_E_CN > 1024;T_E_RAN >1024 During the overlapping portion of the CN configuration PTW and RAN configuration PTW, Min [T_RAN, T_CN, T_D].CN configuration PTW and the outer RAN configuration PTW, Min [T_CN, T_D].CN configuration PTW outer and RAN configuration PTW outer [T_RAN]CN configuration PTW outer and RAN configuration PTW outer UE does not monitor paging and T is not used. 8

[0226] first_T, first_N: Parameters / inputs used to determine a specific frame containing the reference point (reference PMO, first PMO).

[0227] Second_T, second_N: These are parameters / inputs used to determine the PO index.

[0228] For a UE of RRC_IDLE: first_T and second_T are the same. first_N and second_N are the same or identical.

[0229] For UEs of RRC_INACTIVE: first_T and second_T differ in certain cases. First_N and second_N differ in certain cases. first_T and second_T are the same in other cases. First_N and second_N are the same in other cases.

[0230] NsExt and pagingAdaptation-NS are used interchangeably.

[0231] Enhanced paging scheme and paging adaptation are used interchangeably.

[0232] If the operation associated with T is for CN-start paging, T and T_cn are used interchangeably.

[0233] If the operation associated with T is for RAN-initial paging, T and T_ran are used interchangeably.

[0234] N is the number of PFs per T. From the UE perspective, there is only one PF per T. From the NW perspective, there may be one or more PFs per T. Multiple PFs per T are advantageous in terms of load distribution. Multiple PFs per T are disadvantageous in terms of NW power savings.

[0235] N is controlled by nAndPagingFrameOffset and pagingAdaptationNAndPagingFrameOffset.

[0236] nAndPagingFrameOffset indicates one of [oneT, halfT, quarterT, oneEighthT, oneSixteenthT].

[0237] pagingAdaptationNAndPagingFrameOffset indicates one of [oneT, halfT, quarterT, oneEighthT, oneSixteenthT, oneThirtySecondT].

[0238] As the names of the parameters imply, oneT means that N is equal to T (in terms of the number of radio frames), oneEighthT means that N is equal to T / 8 (e.g., if T is 256 radio frames, N is 32), oneThirtySecondT means that N is equal to T / 32 (e.g., if T is 256 radio frames, N is 8), and so on.

[0239] The smaller N is, the better the NW power efficiency. The larger N is, the better the load distribution.

[0240] For UEs that do not support a paging-adaptation scheme, NW controls N by nAndPagingFrameOffset.

[0241] For UEs that support paging adaptation, NW controls N by pagingAdaptationNAndPagingFrameOffset.

[0242] <Paging monitoring behavior in RRC_IDLE when paging adaptation is not applied>

[0243] The UE monitors the corresponding PO for every T_cn.

[0244] The UE monitors the corresponding PO for CN-initial paging.

[0245] T_cn and i_s are determined according to rows 1 through 3 of Table 9.

[0246] The corresponding PF is determined based on T_cn and PF_offset.

[0247] PF_offset is determined based on nAndPagingFrameOffset.

[0248] The starting PMO number of the corresponding PO is determined based on i_s and firstPDCCH-MonitoringOccasionOfPO or firstPDCCH-MonitoringOccasionOfPO-v1710.

[0249] >>: If the cell provides firstPDCCH-MonitoringOccasionOfPO and the cell is one of case1 ~ case8;

[0250] >>>: The UE determines that the starting PDCCH monitoring opportunity number of the (i_s + 1)th PO is the (i_s + 1)th value of firstPDCCH-MonitoringOccasionOfPO;

[0251] >>: If cell provides firstPDCCH-MonitoringOccasionOfPO-v1710 and cell is case9 or case10;

[0252] >>>: The UE determines that the starting PDCCH monitoring opportunity number of the (i_s + 1)th PO is the (i_s + 1)th value of firstPDCCH-MonitoringOccasionOfPO-v1710;

[0253] >>: If the cell does not provide firstPDCCH-MonitoringOccasionOfPO and the cell is one of case1 ~ case8; or

[0254] >>: If the cell does not provide firstPDCCH-MonitoringOccasionOfPO-v1710 and the cell is either case9 or case10,

[0255] >>>: The UE determines that the starting PDCCH monitoring opportunity number of the (i_s + 1)th PO is i_s * S * X;

[0256] The PO consists of S * X PMOs (a starting PMO and (S * X - 1) consecutive PMOs).

[0257] The UE monitors one or more PMOs of the corresponding PO.

[0258] <Paging monitoring behavior in RRC_IDLE when paging adaptation is applied>

[0259] The UE monitors one or more PMOs of the corresponding PO for each T_cn.

[0260] The UE monitors one or more PMOs for CN-initial paging.

[0261] T_cn and i_s are determined according to rows 1 through 3 of Table 10.

[0262] The corresponding PF is determined based on T_cn and PF_offset.

[0263] PF_offset is determined based on pagingAdaptationNAndPagingFrameOffset.

[0264] The starting PMO number of the corresponding PO is determined based on i_s and firstPDCCH-MonitoringOccasionOfPO-v1900.

[0265] >>: If the cell provides firstPDCCH-MonitoringOccasionOfPO-v1900;

[0266] >>>: The UE determines that the starting PDCCH monitoring opportunity number of the (i_s + 1)th PO is the (i_s + 1)th value of firstPDCCH-MonitoringOccasionOfPO-v1900;

[0267] >>: If the cell does not provide firstPDCCH-MonitoringOccasionOfPO-v1900,

[0268] >>>: The UE determines that the starting PDCCH monitoring opportunity number of the (i_s + 1)th PO is i_s * S * X;

[0269] The PO consists of S * X PMOs (a starting PMO and (S * X - 1) consecutive PMOs).

[0270] The UE monitors one or more PMOs of the corresponding PO.

[0272] <Paging monitoring behavior in RRC_INACTIVE when paging adaptation is not applied>

[0273] The UE monitors the corresponding PO for each T_ran.

[0274] The UE monitors the corresponding PO for CN-initial paging and RAN-initial paging.

[0275] T_ran and i_s are determined according to rows 1, 4 through 8 of Table 9.

[0276] >>: i_s is i_s_cn or i_s_ran as shown in Table 9.

[0277] The corresponding PF is determined based on T_ran and PF_offset.

[0278] PF_offset is determined based on nAndPagingFrameOffset.

[0279] The starting PMO number of the corresponding PO is determined based on i_s and firstPDCCH-MonitoringOccasionOfPO or firstPDCCH-MonitoringOccasionOfPO-v1710.

[0280] >>: If the cell provides firstPDCCH-MonitoringOccasionOfPO and the cell is one of case1 ~ case8;

[0281] >>>: The UE determines that the starting PDCCH monitoring opportunity number of the (i_s + 1)th PO is the (i_s + 1)th value of firstPDCCH-MonitoringOccasionOfPO;

[0282] >>: If cell provides firstPDCCH-MonitoringOccasionOfPO-v1710 and cell is case9 or case10;

[0283] >>>: The UE determines that the starting PDCCH monitoring opportunity number of the (i_s + 1)th PO is the (i_s + 1)th value of firstPDCCH-MonitoringOccasionOfPO-v1710;

[0284] >>: If the cell does not provide firstPDCCH-MonitoringOccasionOfPO and the cell is one of case1 ~ case8; or

[0285] >>: If the cell does not provide firstPDCCH-MonitoringOccasionOfPO-v1710 and the cell is either case9 or case10,

[0286] >>>: The UE determines that the starting PDCCH monitoring opportunity number of the (i_s + 1)th PO is i_s * S * X;

[0287] The PO consists of S * X PMOs (a starting PMO and (S * X - 1) consecutive PMOs).

[0288] The UE monitors one or more PMOs of the corresponding PO.

[0290] <Paging monitoring behavior in RRC_INACTIVE when paging adaptation is applied>

[0291] The UE monitors the corresponding PO for each T_ran.

[0292] The UE monitors the corresponding PO for CN-initial paging and RAN-initial paging.

[0293] T_ran and i_s are determined according to rows 1, 4 through 8 of Table 10.

[0294] >>: i_s is i_s_cn or i_s_ran as shown in Table 10.

[0295] The corresponding PF is determined based on T_ran and PF_offset.

[0296] PF_offset is determined based on nAndPagingFrameOffset.

[0297] The starting PMO number of the corresponding PO is determined based on i_s and firstPDCCH-MonitoringOccasionOfPO-v1900.

[0298] >>: If the cell provides firstPDCCH-MonitoringOccasionOfPO-v1900;

[0299] >>>: The UE determines that the starting PDCCH monitoring opportunity number of the (i_s + 1)th PO is the (i_s + 1)th value of firstPDCCH-MonitoringOccasionOfPO-v1900;

[0300] >>: If the cell does not provide firstPDCCH-MonitoringOccasionOfPO-v1900,

[0301] >>>: The UE determines that the starting PDCCH monitoring opportunity number of the (i_s + 1)th PO is i_s * S * X;

[0302] The PO consists of S * X PMOs (a starting PMO and (S * X - 1) consecutive PMOs).

[0303] The UE monitors one or more PMOs of the corresponding PO.

[0304] The PO to be monitored by the UE is denoted as the corresponding PO. The PF associated with the corresponding PO is denoted as the corresponding PF. The corresponding PO and the (i_s)th PO are used interchangeably.

[0305] <T and i_s when paging adaptation is not applied>

[0306] T & i_s Raw UE does not work on eDRX CASE2 or CASE2 + CASE5 T= T_cn = Shortest of [T_RAN, T_CN, T_D];i_s = i_s_cn = f (T_cn, Ns) 1 UEs with RRC_IDLE operate on eDRX CASE1 T_ E_CN =<1024 T = T_cn = [T_E_CN];i_s = i_s_cn = f (T_cn, Ns) 2 CASE1 T_E_CN > 1024;During CN_PTW During CN configured PTWT = T_cn = Shortest of [T_CN, T_D];i_s = i_s_cn = f (T_cn, Ns)Outside the CN configured PTW,UE does not monitor paging and T is not used 3 UEs with RRC_INACTIVE operate on eDRX; UEs use T_ran to determine PF for both RAN-initiated paging and CN-initiated paging. CASE1 + CASE3 T_E_CN =<1024;T_E_RAN =<1024 T = T_ran = Shortest of [T_E_RAN, T_E_CN];i_s = i_s_cn = f (T_cn, Ns) 4 CASE1 + CASE3 T_E_CN > 1024;T_E_RAN =<1024 During CN configured PTW, T = T_ran = Shortest of [T_CN, T_E_RAN, T_D]; i_s = i_s_cn = f (T_cn, Ns)Outside the CN configured PTW, T = T_ran = [T_E_RAN];i_s = i_s_ran = f (T_ran, Ns) 5 CASE1 + CASE5 T_E_CN =<1024;Not operating in eDRX for RAN paging T = T_ran = Shortest of [T_RAN, T_E_CN];i_s = i_s_cn = f (T_cn, Ns) 6 CASE1 + CASE5 T_E_CN >1024;Not operating in eDRX for RAN paging During CN configured PTW, T = T_ran = Shortest of [T_RAN, T_CN, T_D];i_s = i_s_cn = f (T_cn, Ns) Outside the CN configured PTW, T = T_ran = [T_RAN].i_s = i_s_ran = f (T_ran, Ns) 7 CASE1 + CASE4 T_E_CN > 1024;T_E_RAN >1024 During the overlapped part of CN configured PTW and RAN configured PTW, T = T_ran = Shortest of [T_RAN, T_CN, T_D];i_s = i_s_cn = f (T_cn, Ns) During CN configured PTW and outside RAN configured PTW, T = T_ran = Shortest of [T_CN, T_D];i_s = i_s_cn = f (T_cn, Ns) Outside CN configured PTW and during RAN configured PTWT = T_ran = [T_RAN];i_s = i_s_ran = f (T_ran, Ns)Outside CN configured PTW and outside RAN configured PTWUE does not monitor paging and T is not used 8

[0307] <T and i_s when paging adaptation is applied>

[0308] T & i_s Raw UE does not work on eDRX CASE2 or CASE2 + CASE5 T_cn = Shortest of [T_RAN, T_CN, T_D];i_s = i_s_cn = f (T_cn, NsExt) 1 UEs with RRC_IDLE operate on eDRX CASE1 T_ E_CN =<1024 T_cn = [T_ E_CN];i_s = i_s_cn = f (T_cn, NsExt) 2 CASE1 T_E_CN > 1024;During CN_PTW During CN configured PTWT_cn = Shortest of [T_CN, T_D];i_s = i_s_cn = f (T_cn, NsExt)Outside the CN configured PTW,UE does not monitor paging and T is not used 3 UEs with RRC_INACTIVE operate on eDRX; UEs use T_ran to determine PF for both RAN-initiated paging and CN-initiated paging. CASE1 + CASE3 T_E_CN =<1024;T_E_RAN =<1024 T_ran = Shortest of [T_E_RAN, T_E_CN];i_s = i_s_cn = f (T_cn, NsExt) 4 CASE1 + CASE3 T_E_CN > 1024;T_E_RAN =<1024 During CN configured PTW, T_ran = Shortest of [T_CN, T_E_RAN, T_D]; i_s = i_s_cn = f (T_cn, NsExt)Outside the CN configured PTW, T_ran = [T_E_RAN];i_s = i_s_ran = f (T_ran, NsExt) 5 CASE1 + CASE5 T_E_CN =<1024;Not operating in eDRX for RAN paging T_ran = Shortest of [T_RAN, T_E_CN];i_s = i_s_cn = f (T_cn, NsExt) 6 CASE1 + CASE5 T_E_CN >1024;Not operating in eDRX for RAN paging During CN configured PTW, T_ran = Shortest of [T_RAN, T_CN, T_D];i_s = i_s_cn = f (T_cn, NsExt) Outside the CN configured PTW, T_ran = [T_RAN].i_s = i_s_ran = f (T_ran, NsExt) 7 CASE1 + CASE4 T_E_CN > 1024;T_E_RAN >1024 During the overlapped part of CN configured PTW and RAN configured PTW, T_ran = Shortest of [T_RAN, T_CN, T_D];i_s = i_s_cn = f (T_cn, NsExt) During CN configured PTW and outside RAN configured PTW, T_ran = Shortest of [T_CN, T_D];i_s = i_s_cn = f (T_cn, NsExt) Outside CN configured PTW and during RAN configured PTWT_ran = [T_RAN];i_s = i_s_ran = f (T_ran, NsExt)Outside CN configured PTW and outside RAN configured PTWUE does not monitor paging and T is not used 8

[0309] <Determining whether paging adaptation is applied in a cell> Paging adaptation is not applied in a cell in the following cases:

[0310] >: If the UE does not support paging adaptation; or

[0311] If the UE supports paging adaptation but the cell's SIB1 does not include pagingAdaptationNAndPagingFrameOffset and pagingAdaptation-NS.

[0312] Paging adaptation is applied to cells in the following cases:

[0313] >: UE supports paging adaptation; and

[0314] If SIB1 includes pagingAdaptationNAndPagingFrameOffset and pagingAdaptation-NS.

[0315] The UE supports paging adaptation in the following cases:

[0316] >: For CN-start paging,

[0317] >>: If the UE has reported / instructed the AMF to support paging adaptation.

[0318] >: For RAN-initial paging,

[0319] >>: UE reported / instructed AMF to support paging adaptation; and

[0320] >>: When the UE reports / instructs the GNB to support paging adaptation.

[0321] firstPDCCH-MonitoringOccasionOfPO

[0322] The firstPDCCH-MonitoringOccasionOfPO, firstPDCCH-MonitoringOccasionOfPO-v1700, and firstPDCCH-MonitoringOccasionOfPO-v1900 fields indicate the first PDCCH monitoring opportunity for paging to each PO of the PF. The firstPDCCH-MonitoringOccasionOfPO, firstPDCCH-MonitoringOccasionOfPO-v1700, and firstPDCCH-MonitoringOccasionOfPO-v1900 fields are collectively denoted as firstPDCCH-MonitoringOccasionOfPO-xx in this disclosure.

[0323] PDCCH monitoring opportunities for paging are configured by pagingSearchSpace. PDCCH monitoring opportunities for paging can be configured in any symbol, and the granularity of firstPDCCH-MonitoringOccasionOfPO-xx is a PDCCH monitoring opportunity (equivalent to a symbol).

[0324] Depending on the value signaled in nAndPagingFrameOffset / pagingAdaptationNAndPagingFrameOffset and the SCS of the corresponding downlink BWP (in the case of a UE of RRC_IDLE, the initial DL BWP), the number of possible symbols between two adjacent PFs varies.

[0325] for example:

[0326] If:

[0327] >>: nAndPagingFrameOffset indicates oneT (e.g., all radio frames are PF); and

[0328] When SCS is 15KHz,

[0329] The maximum number of PMOs between two adjacent PFs is 140 (14 symbols per time slot and 10 time slots per radio frame; a maximum of one PMO per symbol).

[0330] If:

[0331] >>: pagingAdaptationNAndPagingFrameOffset indicates oneThirtySecondT (e.g., PF occurs every 32 radio frames); and

[0332] When SCS is 480KHz,

[0333] The maximum number of PMOs between two adjacent PFs is 143,360 (14 symbols per time slot, 320 time slots per radio frame, and 2 radio frames between adjacent PFs).

[0334] Considering all possible cases, the table below lists the maximum number of PMOs possible up to the next PF in relation to pagingAdaptationNAndPagingFrameOffset.

[0335] SCS pagingAdaptationNAndPagingFrameOffset oneT halfT quarterT oneEighthT oneSixteenthT oneThirtySecondT 15 140 280 560 1120 2240 4480 30 280 560 1120 2240 4480 8960 60 560 1120 2240 4480 8960 17920 120 1120 2240 4480 8960 17920 35840 240 2240 4480 8960 17920 35840 71680 480 4480 8960 17920 35840 71680 143360

[0336] The table below lists the maximum possible PMOs in relation to nAndPagingFrameOffset.

[0337] SCS nAndPagingFrameOffset oneT halfT quarterT one Eighth oneSixteenthT 15 140 280 560 1120 2240 30 280 560 1120 2240 4480 60 560 1120 2240 4480 8960 120 1120 2240 4480 8960 17920 240 2240 4480 8960 17920 35840 480 4480 8960 17920 35840 71680

[0338] Each cell in Tables 9 and 10 represents the maximum possible number of PMOs in a specific case. For example, the gray cell represents the maximum possible number of PMOs when SCS is 60 KHz and pagingAdaptationNAndPagingFrameOffset is quarterT.

[0339] For simplicity, each case is numbered as follows.

[0340] SCS pagingAdaptationNAndPagingFrameOffset oneT halfT quarterT one Eighth oneSixteenthT oneThirtySecondT 15 case1 case2 case3 case4 case5 case6-1 30 case2 case3 case4 case5 case6 case7-1 60 case3 case4 case5 case6 case7 case8-1 120 case4 case5 case6 case7 case8 case9-1 240 case5 case6 case7 case8 case9 case10-1 480 case6 case7 case8 case9 case10 case11-1

[0341] Max. value Description case1 140 SCS15KHZoneT case2 280 SCS15KHZhalfT or SCS15KHZhalfT case3 560 SCS60KHZoneT, SCS30KHZhalfT orSCS15KHZquarterT case4 1120 SCS120KHZoneT, SCS60KHZhalfT, SCS30KHZquarterT or SCS15KHZoneEighthT case5 2240 SCS240KHZoneT, SCS120KHZhalfT, SCS60KHZquarterT, SCS30KHZoneEighthT orSCS15KHZoneSixteenthT case6-1 4480 SCS15KHZoneThirtySecondT case6 4480 SCS480KHZoneT, SCS240KHZhalfT, SCS120KHZquarterT, SCS60KHZoneEighthT or SCS30KHZoneSixteenthT case7-1 8960 SCS30KHZoneThirtySecondT case7 8960 SCS480HZhalfT, SCS240KHZquarterT, SCS120KHZoneEighthT or SCS60KHZoneSixteenthT case8-1 17920 SCS60KHZoneThirtySecondT case8 17920 SCS480HZquarterT, SCS240KHZoneEighthT or SCS120KHZoneSixteenthT case9-1 35840 SCS120KHZoneThirtySecondT case9 35840 SCS480HzoneEighthT or SCS240KHZoneSixteenthT case10-1 71680 SCS240KHZoneThirtySecondT case10 71680 SCS480HzoneSixteenthT case11-1 143360 SCS480HzoneThirtySecondT

[0342] SCSxxYYY indicates the case where the SCS of DL BWP is xx KHz and nAndPagingFrameOffset / pagingAdaptationNAndPagingFrameOffset indicates YYY.

[0343] firstPDCCH-MonitoringOccasionOfPO-xx is specified as a CHOICE type, which defines a union of multiple alternatives, and only one alternative can be selected and encoded in a given instance. Each alternative is identified by a name (e.g., case7) and associated with a specific data type (e.g., multiple INTEGERs with a maximum value of 8959). These alternatives are mutually exclusive and are guaranteed to be active only once at any given time.

[0344] Depending on the given case, firstPDCCH-MonitoringOccasionOfPO-xx contains alternatives corresponding to the given case. A specific alternative contains one or more INTEGERs, where the maximum value of the INTEGER is equal to the maximum possible PMO (symbol) between adjacent PFs in the given case minus 1. The number of INTEGERs is equal to the value indicated by the ns field or the pagingAdaptation-NS-r19 field. For example, if the cell is one of case 3 (e.g., SCS60KHZoneT, SCS30KHZhalfT, or SCS15KHZquarterT) and the pagingAdaptation-NS-r19 field indicates 8, firstPDCCH-MonitoringOccasionOfPO-v1900 contains the case 3 alternative, the case 3 alternative contains 8 INTEGERs, and the maximum value of the 8 INTEGERs is 559. The bit width of the 8 INTEGERS is 10 bits (i.e., the smallest bit width covering 559).

[0345] firstPDCCH-MonitoringOccasionOfPO CHOICE {

[0346] case1 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..139),

[0347] case2 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..279),

[0348] case3 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..559),

[0349] case4 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..1119),

[0350] case5 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..2239),

[0351] case6 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..4479),

[0352] case7 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..8959),

[0353] case8 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..17919)

[0354] } OPTIONAL, -- Need R

[0356] firstPDCCH-MonitoringOccasionOfPO-v1710 CHOICE {

[0357] case9 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..35839),

[0358] case10 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..71679)

[0359] } OPTIONAL -- Need R

[0361] firstPDCCH-MonitoringOccasionOfPO-v1900 CHOICE {

[0362] case1 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..139),

[0363] case2 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..279),

[0364] case3 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..559),

[0365] case4 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..1119),

[0366] case5 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..2239),

[0367] case6or6-1 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..4479),

[0368] case7or7-1 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..8959),

[0369] case8or8-1 SEQUENCE (SIZE (1..maxPO-perPFext) OF INTEGER (0..17919)

[0370] case9or9-1 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..35839),

[0371] case10or10-1 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..71679),

[0372] case11-1 SEQUENCE (SIZE (1..maxPO-perPFext) OF INTEGER (0..143359)

[0373] } OPTIONAL, -- Need R

[0374] / / / maxPO-perPF = maximum value that can be indicated by ns = 4 / / /

[0375] / / / maxPO-perPFext = maximum value that can be indicated by pagingAdaptation-NS = 8 / / /

[0376] }

[0378] UE uses firstPDCCH-MonitoringOccasionOfPO in the following cases:

[0379] >: If paging adaptation is not applied to the UE in the cell, and the cell is one of case1~case8; and

[0380] When firstPDCCH-MonitoringOccasionOfPO is broadcast from the cell's SIB1.

[0381] UE uses firstPDCCH-MonitoringOccasionOfPO-v1710 in the following cases:

[0382] >: If paging adaptation is not applied to the UE in the cell, and the cell is case9 or case10; and

[0383] When firstPDCCH-MonitoringOccasionOfPO-v1710 is broadcast from this cell's SIB1.

[0384] UE uses firstPDCCH-MonitoringOccasionOfPO-v1900 in the following cases:

[0385] >: When paging adaptation is applied to the UE in the cell; and

[0386] When firstPDCCH-MonitoringOccasionOfPO-v1900 is broadcast from the cell's SIB1.

[0387] The number of INTEGERs (entries) in firstPDCCH-MonitoringOccasionOfPO and firstPDCCH-MonitoringOccasionOfPO-v1710 is equal to the value specified in the ns field. For example, if the ns field specifies 4, 4 INTEGERs are included in firstPDCCH-MonitoringOccasionOfPO. The first INTEGER represents the starting PMO for PO-index 0 (i_s = 0), the second INTEGER represents the starting PMO for PO-index 1 (i_s = 1), and so on.

[0388] The number of INTEGERs (entries) in firstPDCCH-MonitoringOccasionOfPO-v1900 is equal to the value specified in the pagingAdaptation-NS-r19 field. For example, if the pagingAdaptation-NS-r19 field specifies 8, 8 INTEGERs are included in firstPDCCH-MonitoringOccasionOfPO-v1900. The first INTEGER represents the starting PMO for PO-index 0 (i_s = 0), the second INTEGER represents the starting PMO for PO-index 1 (i_s = 1), and so on.

[0389] The paging scheme is determined by the NES paging indication of NAS messages and the NES paging indication of system information.

[0390] The terminal performs the following.

[0391] >: Step in which the terminal transmits a message of the first protocol layer [NAS] to the AMF

[0392] >>: The message consists of an IE indicating that the terminal supports NES paging (enhanced paging, enhanced paging scheme, etc.).

[0393] Step in which the terminal receives a message of the first protocol layer from the AMF

[0394] >>: The message includes an IE indicating that NES paging for the terminal is allowed in one or more TAs (indicated by the TAI list in the message).

[0395] System information received by terminal from base station

[0396] One or more PMOs determined by the terminal

[0397] >: Perform PDCCH monitoring for paging in one or more PMOs

[0398] Here:

[0399] One or more PMOs are determined based on the first method in the following cases.

[0400] >>: NES paging is allowed by the upper layer (e.g., a NAS message containing the first NES paging information is received).

[0401] >>: NES paging is enabled by the base station within the cell (e.g., system information including second NES paging information has been received);

[0402] One or more PMOs are determined based on the second method in the following cases.

[0403] >>: NES paging is not allowed at the upper layer (e.g., NAS message containing the first NES paging indication is not received). Or

[0404] NES paging is allowed at the upper layer, but not at the base station (or NES paging is not allowed at the cell).

[0405] > : In the first method :

[0406] The specific frame is determined according to the first equation.

[0407] >>>: Right side of the first equation:

[0408] >>>>: Consists of 'DRX cycle' and 'an integer derived from UE ID [UE_ID]' and 'an integer derived from DRX cycle (indicating the number of RPs during the DRX cycle)' or 'the same integer for the first specific group of UE IDs [UE_ID mod N]'

[0409] >>>>: Does not include the coefficient of variance.

[0410] The PMO group [PO; PMOG] is determined based on the index of the PMO group and the first PMO in a specific frame.

[0411] The index of the PMO group is determined based on the second equation.

[0412] >>>: Right side of the second equation:

[0413] >>>>: Includes 'the same integer for the second specific group of the UE ID [UE_ID div N]' and 'an integer representing the number of PMO groups associated with the RP';

[0414] One or more PMOs are selected from a group of PMOs based on the SSB's RSRP, and

[0415] > : In the second method :

[0416] The specific frame is determined according to the third equation.

[0417] >>>: Right-hand side of the third equation:

[0418] >>>>: Consists of 'DRX cycle' and 'an integer derived from UE ID [UE_ID]' and 'an integer derived from DRX cycle (indicating the number of RPs during the DRX cycle)' or 'an integer identical to the first specific group of UE IDs [UE_ID mod N]'.

[0419] >>: The integer is the remainder of UE_ID divided by N.

[0420] >>>>: Includes the variance coefficient [T div N].

[0421] The variance coefficient is the quotient of T divided by N.

[0422] The PMO group [PO; PMOG] is determined based on the index of the PMO group and the first PMO in a specific frame.

[0423] The index of the PMO group is determined based on the second equation.

[0424] >>>: Right side of the second equation:

[0425] >>: For the second specific group of UE ID [UE_ID div N], including the same integer and an integer representing the number of PMO groups associated with the RP,

[0426] One or more PMOs are selected from the PMO group based on the SSB's RSRP.

[0427] The terminal performs the following.

[0428] The terminal transmits the first message of the first protocol layer (NAS) to the AMF.

[0429] >>: The message consists of IE / parameters, which indicate that the terminal supports NES paging (enhanced paging, enhanced paging scheme, etc.) for CN paging (or RRC_IDLE state).

[0430] The terminal receives the second message of the first protocol layer from the AMF.

[0431] >>: The message consists of an IE / parameter indicating that NES paging is allowed in RRC_IDLE (or CN paging).

[0432] A step of transmitting a third message [UECapabilityInformation] of the second protocol layer to the base station by the terminal.

[0433] >>: The third message consists of fields / parameters indicating that the terminal supports NES paging for RAN paging (or RRC_INACTIVE state).

[0434] The terminal receives the fourth message (RRCRelease) of the second protocol layer from the base station.

[0435] >>: The fourth message is composed as follows.

[0436] >>>: Field / parameter indicating that NES paging is allowed in RRC_INACTIVE (or for RAN paging) in RNA;

[0437] >>>: Set of parameters associated with the RRC_INACTIVE state (e.g., SuspendConfig).

[0438] Step of receiving system information through a terminal.

[0439] >>: System information is configured as follows.

[0440] >>>: Indicates that NES paging is allowed in cells for UEs in the RRC_INACTIVE state.

[0441] >>>: This is a set of parameters related to NES paging.

[0442] >: A step of determining one or more PMOs by a terminal; and

[0443] Step: Performing PDCCH monitoring for paging in one or more PMOs.

[0444] To check one or more PMOs, perform the following.

[0445] The specific frame is determined according to the first equation.

[0446] >>>: The right-hand side of the first equation includes the following,

[0447] >>>>: This is the first integer derived from UE_ID and N.

[0448] >>: The first integer [UE_ID mod N] that is the same / common to the first set of UE IDs

[0449] >>: The PMO group is determined based on the following criteria.

[0450] >>>: PMO group index; and

[0451] >>>: The first PMO of a specific frame

[0452] The index of the PMO group is determined based on the second equation.

[0453] >>>: The right-hand side of the second mathematical expression includes the following,

[0454] >>>>: This is the second integer derived from UE_ID and N.

[0455] >>: The second integer is the same / common for the second UE ID set [UE_ID div N].

[0456] One or more PMOs are selected from the PMO group based on the SSB's RSRP.

[0457] A specific frame is determined based on an integer associated with the first set of UE_IDs, and the index of the PO is determined based on an integer associated with the second set of UE_IDs.

[0459] The terminal performs the following.

[0460] The terminal transmits the first message of the first protocol layer (NAS) to the AMF.

[0461] >>: The message consists of IE / parameters, which indicate that the terminal supports NES paging (enhanced paging, enhanced paging scheme, etc.) for CN paging (or RRC_IDLE state).

[0462] The terminal receives the second message of the first protocol layer from the AMF.

[0463] >>: The message is composed as follows.

[0464] >>>: IE / parameter indicating that NES paging is allowed in RRC_IDLE (or CN paging)

[0465] >>>: This is a parameter for T_CN.

[0466] >>>: This is a parameter for T_E_CN.

[0467] Step of receiving system information through a terminal.

[0468] >>: System information is configured as follows.

[0469] >>>: Indicates that NES paging is allowed in cells for UEs in RRC_IDLE state for CN paging.

[0470] >>>: This is a set of parameters related to NES paging.

[0471] >: A step of determining one or more PMOs by a terminal; and

[0472] Step: Performing PDCCH monitoring for paging in one or more PMOs.

[0473] To check one or more PMOs, perform the following.

[0474] The specific frame is determined according to the first equation.

[0475] >>>: The right-hand side of the first equation includes the following,

[0476] >>>>: Same integer [UE_ID mod N] for the first set of UE IDs

[0477] >>>: The left side of the first equation includes the following,

[0478] >>>>: If T_E_CN is 1024 radio frames or less, T_E_CN

[0479] >>>>: If T_E_CN is greater than 1024 radio frames, the shortest frame between T_CN and T_D

[0480] >>: The PMO group is determined based on the following criteria.

[0481] >>>: PMO group index; and

[0482] >>>: The first PMO of a specific frame

[0483] The index of the PMO group is determined based on the second equation.

[0484] >>>: The right-hand side of the second mathematical expression includes the following,

[0485] >>>>: Integer derived from UE_ID and N

[0486] >>>>: The integer is the same for the second set of UE IDs.

[0487] One or more PMOs are selected from the PMO group based on the SSB's RSRP.

[0489] The terminal performs the following.

[0490] In 4A10, the terminal transmits the first message of the first protocol layer (NAS) to the AMF.

[0491] >>: The above message consists of IE / parameters, which indicates that the terminal supports paging coordination for CN paging (or RRC_IDLE state).

[0492] In 4A20, the terminal receives a second message of the first protocol layer from the AMF.

[0493] >>: The message is composed as follows.

[0494] >>>: IE / parameter indicating that paging adjustment is allowed in RRC_IDLE (or CN paging)

[0495] >>>: This is a parameter for T_CN.

[0496] >>>: This is the parameter set for T_E_CN.

[0497] In 4A30, the terminal transmits the third message [UECapabilityInformation] of the second protocol layer to the base station.

[0498] >>: The third message consists of a field / parameter indicating that the terminal supports paging coordination for RAN paging (or RRC_INACTIVE state).

[0499] In 4A40, the terminal receives the fourth message (RRCRelease) of the second protocol layer from the base station.

[0500] >>: The fourth message is composed as follows.

[0501] >>>: A field / parameter indicating that paging reorganization is allowed in RRC_INACTIVE (or RAN paging).

[0502] >>>: This is a parameter for T_RAN.

[0503] >>>: Parameter set for T_E_RAN

[0504] >: Set of parameters associated with the RRC_INACTIVE status

[0505] In 4A50, the terminal receives system information.

[0506] >>: System information is configured as follows.

[0507] >>>: Indicates that paging adjustment is allowed in the cell for a UE in the RRC_IDLE state (for CN paging).

[0508] >>>: Indicates that paging reorganization is allowed in cells of UEs with RRC_INACTIVE (both CN paging and RAN paging)

[0509] >>>: This is a set of parameters related to paging coordination.

[0510] In 4A60, the terminal determines one or more PMOs;

[0511] In 4A70, the terminal performs PDCCH monitoring for paging in one or more PMOs.

[0512] To check one or more PMOs, perform the following.

[0513] The specific frame is determined according to the first equation.

[0514] >>>: The right-hand side of the first equation includes the following,

[0515] >>>>: first_N and UE_ID

[0516] >>>: The left side of the first equation includes the following,

[0517] >>>>: first_T and PF_offset

[0518] >>: The PMO group is determined based on the following criteria.

[0519] >>>: PMO group index; and

[0520] >>>: The first PMO of a specific frame

[0521] The index of the PMO group is determined based on the second equation.

[0522] >>>: The right-hand side of the second mathematical expression includes the following,

[0523] >>>>: And second_N

[0524] One or more PMOs are selected from the PMO group based on the SSB's RSRP.

[0525] first_T and first_N are the same as second_T and second_N if ranPagingInIdlePO is not configured as SIB1.

[0526] When ranPagingInIdlePO is configured as SIB1, both T_E_CN and T_E_RAN are smaller than 1024 radio frames, and the terminal is operating in eDRX:

[0527] >>: first_T is the shortest among [T_E_RAN, T_E_CN]. And

[0528] >>: second_T is T_E_CN.

[0529] If ranPagingInIdlePO is configured as SIB1, T_E_CN is greater than 1024 radio frames and T_E_RAN is less than 1024 radio frames, and the terminal is operating in eDRX:

[0530] >>: first_T is the shortest among [T_CN, T_E_RAN, T_D] in the CN configuration PTW, and T_E_RAN is outside the CN configuration PTW. And

[0531] >>: second_T is the shortest among [T_CN, T_D] in the CN configuration PTW and is T_E_RAN outside the CN configuration PTW.

[0532] DownlinkConfigCommonSIB ::= SEQUENCE {

[0533] bcch-Config BCCH-Config,

[0534] pcch-Config PCCH-Config,

[0535] }

[0537] BCCH-Config ::= SEQUENCE {

[0538] modificationPeriodCoeff ENUMERATED {n2, n4, n8, n16},

[0539] ...

[0540] }

[0543] PCCH-Config ::= SEQUENCE {

[0544] defaultPagingCycle PagingCycle,

[0545] nAndPagingFrameOffset CHOICE {

[0546] oneT NULL,

[0547] halfT INTEGER (0..1),

[0548] quarterT INTEGER (0..3),

[0549] oneEighthT INTEGER (0..7),

[0550] oneSixteenthT INTEGER (0..15)

[0551] },

[0552] ns ENUMERATED {four, two, one},

[0553] firstPDCCH-MonitoringOccasionOfPO CHOICE {

[0554] case1 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..139),

[0555] case2 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..279),

[0556] case3 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..559),

[0557] case4 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..1119),

[0558] case5 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..2239),

[0559] case6 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..4479),

[0560] case7 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..8959),

[0561] case8 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..17919)

[0562] } OPTIONAL, -- Need R

[0563] nrofPDCCH-MonitoringOccasionPerSSB-InPO-r16 INTEGER (2..4)

[0564] ranPagingInIdlePO-r17 ENUMERATED {true}

[0565] firstPDCCH-MonitoringOccasionOfPO-v1710 CHOICE {

[0566] case9 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..35839),

[0567] case10 SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..71679)

[0568] }

[0569] pagingAdaptation-NS-r19 ENUMERATED {eight,four, two, one}

[0570] pagingAdaptationNAndPagingFrameOffset CHOICE {

[0571] oneT NULL,

[0572] halfT INTEGER (0..1),

[0573] quarterT INTEGER (0..3),

[0574] oneEighthT INTEGER (0..7),

[0575] oneSixteenthT INTEGER (0..15),

[0576] oneThirtySecondT INTEGER (0..31)

[0577] }

[0579] ]]

[0580] firstPDCCH-MonitoringOccasionOfPO-v1900 CHOICE {

[0581] case1 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..139),

[0582] case2 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..279),

[0583] case3 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..559),

[0584] case4 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..1119),

[0585] case5 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..2239),

[0586] case6or6-1 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..4479),

[0587] case7or7-1 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..8959),

[0588] case8or8-1 SEQUENCE (SIZE (1..maxPO-perPFext) OF INTEGER (0..17919)

[0589] case9or9-1 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..35839),

[0590] case10or10-1 SEQUENCE (SIZE (1..maxPO-perPFext)) OF INTEGER (0..71679),

[0591] case11 SEQUENCE (SIZE (1..maxPO-perPFext) OF INTEGER (0..143359)

[0592] } OPTIONAL, -- Need R

[0593] / / / maxPO-perPF = maximum value that can be indicated by ns = 4 / / /

[0594] / / / maxPO-perPFext = maximum value that can be indicated by pagingAdaptation-NS = 8 / / /

[0595] }

[0596] bcch-Config: Modification cycle related configuration.

[0597] pcch-Config: Paging configuration.

[0598] modificationPeriodCoeff: Actual modification period, expressed in the number of wireless frames m = modificationPeriodCoeff * defaultPagingCycle. n2 corresponds to the value 2, n4 corresponds to the value 4, etc.

[0599] defaultPagingCycle: The default paging cycle used to derive 'T'. Values ​​such as rf32 correspond to 32 radio frames, rf64 correspond to 64 radio frames, etc.

[0600] firstPDCCH-MonitoringOccasionOfPO: Indicates the first PDCCH monitoring opportunity for paging for each PO of the PF.

[0601] pagingAdaptation-NS: Number of paging opportunities per paging frame for paging adaptation.

[0602] pagingAdaptationNAndPagingFrameOffset: Used to derive the total number of paging frames in T and the paging frame offset (corresponding to the parameter PF_offset). The value of oneSixteenthT corresponds to T / 16, the value of oneEighthT corresponds to T / 8, etc.

[0603] nAndPagingFrameOffset: Used to derive the total number of paging frames in T (corresponding to parameter N) and the paging frame offset (corresponding to parameter PF_offset). The value of oneSixteenthT corresponds to T / 16, the value of oneEighthT corresponds to T / 8, and so on.

[0604] nrofPDCCH-MonitoringOccasionPerSSB-InPO: Number of PDCCH monitoring opportunities corresponding to SSBs within paging opportunities.

[0605] ns: Number of paging opportunities per paging frame.

[0606] ranPagingInIdlePO: Indicates that the network supports RAN paging in the PO corresponding to i_s determined by the UE in the RRC_IDLE state.

[0607] The REGISTRATION REQUEST message is sent to the AMF by the UE. The message is composed as follows.

[0608] >: Requested DRX parameters including 5GS DRX parameters

[0609] The requested extended DRX parameter contains the extended DRX parameter.

[0610] >: NES paging support. If this IE is included, the UE supports an enhanced scheme for paging (e.g., NES paging).

[0611] The REGISTRATION ACCEPT message is sent to the UE by the AMF. The message is composed as follows.

[0612] >: Negotiated DRX parameters including 5GS DRX parameters;

[0613] >: Includes negotiated extended DRX parameters extended DRX parameters;

[0614] >: Allow NES paging. If included, the UE assumes that an enhanced scheme for paging (e.g., NES paging) is used in cells that support the enhanced scheme.

[0615] 5GS DRX Parameters IE

[0616] The 5GS DRX parameter information element indicates that the UE wants to use DRX and that the network wants to specify the DRX cycle value to be used in paging. IE consists of the DRX value field. This field represents the DRX cycle parameter 'T'. This value is denoted as T_CN.

[0618] Extended DRX Parameters IE

[0619] The Extended DRX Parameter Information element indicates that the UE intends to use eDRX, and the network specifies the Paging Time Window length value and the Extended DRX Cycle value to be used for eDRX. The eDRX Value field specifies T_E_CN. The Paging Time Window field represents PTW.

[0621] When using Extended DRX (eDRX), the following applies.

[0622] In the case of RRC_INACTIVE, the eDRX configuration for RAN paging is determined and configured by NG-RAN. In RRC_INACTIVE, the UE monitors both RAN and CN paging.

[0623] In the case of RRC_IDLE, the eDRX for CN paging is configured as an upper layer. In RRC_IDLE, the UE monitors only CN paging.

[0624] Information on whether eDRX for CN paging and RAN paging is allowed in the cell is provided separately in the system information.

[0625] The maximum value of the eDRX period is 10485.76 seconds (2.91 hours) and the minimum value of the eDRX period is 2.56 seconds.

[0626] Hyper SFN (H-SFN) is broadcast by the cell and increases by 1 when the SFN is wrapped.

[0627] PH (Paging Hyperframe) refers to the H-SFN at which the terminal begins monitoring paging according to the DRX during the PTW (Paging Time Window). PH and PTW are determined based on formulas known to the AMF, UE, and NG-RAN (see TS 38.304

[10] );

[0628] When the eDRX cycle is greater than 10.24 seconds, H-SFN, PH, and PTW are used.

[0629] If the RRC_IDLE eDRX cycle is longer than the system information modification cycle, the UE checks whether the stored system information remains valid before resuming / establishing the RRC connection.

[0631] If the UE does not work with eDRX:

[0632] T is determined by the shortest value among the UE-specific DRX value set by RRC (if present), the UE-specific DRX value set by the upper layer (if present), and the default DRX value broadcast from system information. For L2 U2N Relay UEs, T for L2 U2N Remote UEs is determined by the shortest value among the UE-specific DRX value provided by PC5-RRC signaling and the default DRX value broadcast from system information.

[0633] In the RRC_IDLE state, if the UE operates on an eDRX and the eDRX is configured by a higher layer, i.e., T_eDRX_CN, then according to Section 7.4, it is as follows.

[0634] If T_eDRX_CN is 1024 radio frames or less:

[0635] >>: T = T_eDRX_CN;

[0636] Besides:

[0637] >>: During CN configuration PTW, if T is set by the upper layer, it is determined by the shortest value among UE-specific DRX values ​​and by the default DRX value broadcast from system information.

[0638] In the RRC_INACTIVE state, if the UE operates on an eDRX and the eDRX is configured by the RRC, i.e., T_eDRX_RAN (if present) and the upper layer, i.e., T_eDRX_CN:

[0639] If both T_eDRX_CN and the used T_eDRX_RAN are not longer than 1024 radio frames, then T = min{T_eDRX_RAN, T_eDRX_CN}.

[0640] If T_eDRX_CN does not exceed 1024 radio frames and T_eDRX_RAN is not set or used, T is determined by the shortest value among the UE-specific DRX values ​​set by RRC and T_eDRX_CN.

[0641] If T_eDRX_CN is longer than 1024 radio frames:

[0642] >>: If T_eDRX_RAN is configured or not in use:

[0643] >>>: During the CN setup PTW, T is determined by the shortest value among the UE-specific DRX value set by the RRC, the UE-specific DRX value set by the upper layer (if any), and the default DRX value broadcast from the system information. Outside of the CN setup PTW, T is determined by the UE-specific DRX value set by the RRC;

[0644] Otherwise, if using T_eDRX_RAN, it is not longer than 1024 radio frames.

[0645] >>>: During the CN configured PTW, T is determined by the shortest of the UE-specific DRX values ​​if set by the upper layer and T_eDRX_RAN, and is broadcast as the default DRX value in the system information. Outside of the CN configured PTW, T is determined by T_eDRX_RAN.

[0646] Otherwise, if T_eDRX_RAN is used, it is longer than 1024 radio frames.

[0647] >>>: During the overlap between the CN-configured PTW and the RAN-configured PTW, T is determined by the shortest value among the UE-specific DRX value set by RRC, the UE-specific DRX value set by the upper layer (if any), and the default DRX value broadcast from system information.

[0648] >>>: During CN configured PTW and outside RAN configured PTW, T is determined by the shortest of the UE-specific DRX values ​​configured by the upper layer (if any) and the default DRX value broadcast from system information.

[0649] >>>: During the PTW outside of the CN-set PTW and the RAN-set PTW, T is determined by the UE-specific DRX value set by the RRC.

[0650] N: Total number of paging frames of T

[0651] Ns: Number of paging operations for PF

[0652] PF_offset: Offset used for PF measurement

[0653] UE_ID:

[0654] When the UE operates on eDRX:

[0655] 5G-S-TMSI mod 4096

[0656] different:

[0657] >: 5G-S-TMSI mod 1024

[0658] The UE may be configured by an upper layer and / or RRC having an eDRX (extended DRX) cycle T_eDRX_CN and / or T_eDRX_RAN.

[0659] In the case of CN paging, if the UE is configured for eDRX by the upper layer and eDRX-AllowedIdle is signaled in SIB1, the UE operates in eDRX in the RRC_IDLE or RRC_INACTIVE state; otherwise, the UE does not operate in eDRX.

[0660] In the case of RAN paging, UEs in the RRC_INACTIVE state are as follows.

[0661] If the UE is configured for eDRX by ran-ExtendedPagingCycle-r18 and eDRX-AllowedInactive-r18 is signaled on SIB1:

[0662] The eDRX cycle configured by extendedPagingCycle-r18 operates in eDRX using T_eDRX_RAN.

[0663] Otherwise, if the UE is configured for eDRX by ran-ExtendedPagingCycle-r17 and eDRX-AllowedInactive-r17 is signaled on SIB1:

[0664] It operates in eDRX using the eDRX cycle T_eDRX_RAN configured with ran-ExtendedPagingCycle-r17.

[0665] else:

[0666] >: Does not work in eDRX.

[0667] If the UE operates in eDRX with an eDRX cycle not exceeding 1024 radio frames, it monitors POs as defined in 7.1 when the eDRX cycle is configured. Otherwise, the UE operating in eDRX monitors POs as defined in 7.1 during the periodic paging time window (PTW) configured for the UE. The PTW depends on the UE and is determined by the Paging Hyperframe (PH), the start position (PTW_start), and the end position (PTW_end) within the PH. The PH, PTW_start, and PTW_end are provided by the following formulas.

[0668] PH for CN is H-SFN satisfying the following equation.

[0669] H-SFN mod T_eDRX_CN= (UE_ID_H mod T_eDRX_CN), where

[0670] >: T_eDRX_CN: UE-specific eDRX cycles of hyperframes configured by the upper layer (T_eDRX_CN = 2, ..., 1024 hyperframes).

[0671] The PH of RAN is an H-SFN satisfying the following equation.

[0672] H-SFN mod TeDRX_RAN= (UE_ID_H mod TeDRX_RAN), where

[0673] >: TeDRX_RAN: UE-specific eDRX cycles of hyperframes configured by RRC (T eDRX_RAN = 2, ..., 1024 hyperframes).

[0674] For CN configuration PTW:

[0675] PTW_start is part of the PTW and represents the first radio frame of the PH for the CN having an SFN that satisfies the following equation.

[0676] SFN = 128 * i_eDRX_CN, where

[0677] >: i_eDRX_ CN = floor(UE_ID_H / T_eDRX_CN) mod 8

[0678] PTW_end is the last radio frame of the PTW and has an SFN that satisfies the following equation.

[0679] SFN = (PTW_start + L*100 - 1) mod 1024, where

[0680] >: L = PTW (Paging Time Window) length (seconds) configured by the upper layer

[0681] For RAN configuration PTW:

[0682] PTW_start is part of the PTW and represents the first radio frame of the PH for the RAN having an SFN that satisfies the following equation.

[0683] SFN = 128 * ieDRX_CN, where

[0684] > : ieDRX_CN = floor (UE_ID_H / TeDRX_CN) mod 8

[0685] PTW_end is the last radio frame of the PTW and has an SFN that satisfies the following equation.

[0686] SFN = (PTW_start + L*100 - 1) mod 1024, where

[0687] >: L = PTW (Paging Time Window) length (seconds) configured by RRC

[0688] UE_ID_H is defined as follows.

[0689] UE_ID_H: The 13 most significant bits of the hashed ID.

[0690] The hashed ID is defined as follows.

[0691] Hashed_ID is the Frame Check Sequence (FCS) for bits b31, b30..., b0 of 5G-S-TMSI.

[0692] As defined in 5G-S-TMSI = TS 23.003

[23] <b47, b46, ..., b0> .

[0693] The 32-bit FCS is the complement of the sum (mod 2) of Y1 and Y2, where Y1 and Y2 are defined in TS 38.304.

[0694] For a UE that supports paging adaptation, when pagingAdaptation-NS and pagingAdaptationNAndPagingFrameOffset are signaled in system information, the UE derives the values ​​of N and PF_offset from the pagingAdaptationNAndPagingFrameOffset parameter and monitors only the PO(s) derived from these paging parameters.

[0695] For a UE that supports paging adaptation, when pagingAdaptation-NS and pagingAdaptationNAndPagingFrameOffset are signaled in system information, the UE determines i_s from pagingAdaptation-NS and the N parameter. The UE determines POs based on i_s and firstPDCCH-MonitoringOccasionOfPO. The UE monitors the determined PO(s).

[0696] If the UE does not have 5G-S-TMSI, for example, if the UE is not yet registered with the network, the UE must use UE_ID = 0 as the default identifier in the above PF and i_s formulas.

[0697] 5G-S-TMSI is a 48-bit bit string. In the formula above, 5G-S-TMSI should be interpreted as a binary number where the leftmost bit represents the most significant bit. This is signaled in the REGISTRATION ACCEPT message.

[0698] In the RRC_INACTIVE state, if the UE supports inactiveStatePO-Determination and the network broadcasts ranPagingInIdlePO with the value "true", the UE must use the same i_s as for the RRC_IDLE state. Otherwise, the UE determines i_s based on the above parameters and formula.

[0699] In the RRC_INACTIVE state, if the eDRX value used configured by the upper layer is 1024 radio frames or less, the UE must use the same i_s as for the RRC_IDLE state for CN paging and RAN-initiated paging.

[0700] In the RRC_INACTIVE state, if the eDRX value used configured by the upper layer is longer than 1024 radio frames, during CN PTW, the UE must use the same i_s as for the RRC_IDLE state for CN paging and RAN-initial paging. Outside of CN PTW, the UE must use the i_s for the RRC_INACTIVE state for CN paging and RAN-initial paging.

[0701] FIG. 9 is a block diagram showing the internal structure of a terminal to which the disclosed material is applied.

[0702] Referring to the configuration diagram, the terminal includes a controller (5A01), a storage unit (5A02), a transmission and reception unit (5A03), a main processor (5A04), and an input / output unit (5A05).

[0703] The control unit (5A01) controls the overall operation of the terminal in terms of mobile communication. For example, the control unit (5A01) receives / transmits signals through the transceiver (5A03). Additionally, the control unit (5A01) writes and reads data to and from the storage unit (5A02). To this end, the control unit (5A01) includes at least one processor. For example, the control unit (5A01) may include a Communication Processor (CP) that performs control for communication and an Application Processor (AP) that controls upper layers, such as an application program. The controller controls the storage unit and the transceiver so that the UE operations exemplified in this disclosure are performed.

[0704] The storage unit (5A02) stores data for the operation of the terminal, such as basic programs, application programs, and configuration information. The storage unit (5A02) provides the stored data upon the request of the control unit (5A01).

[0705] The transceiver (5A03) is composed of an RF processor, a baseband processor, and a plurality of antennas. The RF processor performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. Specifically, the RF processor converts a baseband signal provided by an up-baseband processor into an RF band signal, transmits the same signal through an antenna, and converts an RF band signal received through a down-antenna into a baseband signal. The RF processing unit may include a transmit filter, a receive filter, an amplifier, a mi10r, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. The RF processor can perform MIMO and can receive multiple layers when performing MIMO operations. The baseband processor performs a conversion function between a baseband signal and a bit string according to the physical layer specifications of the system. For example, during data transmission, the baseband processor encodes and modulates the transmitted bit string to generate complex symbols. In addition, during data reception, the baseband processor demodulates and decodes the baseband signal provided by the RF processor to restore the received bit string.

[0706] The main processor (5A04) controls overall operations other than mobile operations. The main processor (5A04) processes user input received from the I / O unit (5A05), stores data in the storage unit (5A02), controls the controller (5A01) for necessary mobile communication operations, and transmits user data to the I / O unit (5A05).

[0707] The I / O unit (5A05) is composed of equipment that inputs user data and outputs user data such as a microphone and screen. The I / O unit (5A05) performs the input and output of user data according to the commands of the main processor.

[0708] FIG. 10 is a block diagram showing the configuration of a base station according to the present disclosure.

[0709] As can be seen in the diagram, the base station includes a controller (5B01), a storage unit (5B02), a transceiver (5B03), and a backhaul interface device (5B04).

[0710] The controller (5B01) controls the overall operation of the main base station. For example, the controller (5B01) receives / transmits signals through the transceiver (5B03) or the backhaul interface (5B04). Additionally, the controller (5B01) writes and reads data to and from the storage unit (5B02). To this end, the controller (5B01) may include at least one processor. The controller controls the receiver, the storage device, and the backhaul interface to enable the base station operation exemplified in the present disclosure to be performed.

[0711] The storage unit (5B02) stores data for the operation of the main base station, such as basic programs, application programs, and configuration information. In particular, the storage unit (5B02) can store information regarding bearers assigned to connected UEs, measurement results reported by connected UEs, etc. Additionally, the storage unit (5B02) can store information that serves as a criterion for determining whether to provide multiple connections to the terminal or to discontinue multiple connections. Furthermore, the storage unit (5B02) provides the stored data upon the request of the control unit (5B01).

[0712] The transceiver (5B03) is composed of an RF processor, a baseband processor, and a plurality of antennas. The RF processor performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. Specifically, the RF processor converts a baseband signal provided by an up-baseband processor into an RF band signal, transmits the same signal through an antenna, and converts a received RF band signal through a down-antenna into a baseband signal. The RF processor may include a transmit filter, a receive filter, an amplifier, a mi10r, an oscillator, a DAC, an ADC, etc. The RF processor may perform downlink MIMO operations by transmitting at least one layer. The baseband processor performs a conversion function between a baseband signal and a bit string according to the physical layer specifications of the first wireless access technology. For example, during data transmission, the baseband processor encodes and modulates the transmitted bit string to generate complex symbols. Additionally, during data reception, the baseband processor demodulates and decodes the baseband signal provided by the RF processor to restore the received bit string.

[0713] The backhaul interface unit (5B04) provides an interface for communicating with other nodes within the network. The backhaul interface unit (5B04) converts a bit sequence transmitted from a base station to another node, for example, another base station or core network, into a physical signal, and converts a physical signal received from another node into a bit string.

[0714] The following are the abbreviations used in the present invention.

[0715] 5GC 5G Core Network RACH Random Access Channel

[0716] ACK Acknowledgment RAN Radio Access Network

[0717] AM Acknowledged Mode RAR Random Access Response

[0718] AMF Access and Mobility Management Function

[0719] RA-RNTI Random Access RNTI

[0720] ARQ Automatic Repeat Request RAT Radio Access Technology

[0721] AS Access Stratum RB Radio Bearer

[0722] ASN.1 Abstract Syntax Notation One RLC Radio Link Control

[0723] BSR Buffer Status Report RNA RAN-based Notification Area

[0724] BWP Bandwidth Part RNAU RAN-based Notification Area Update

[0725] CA Carrier Aggregation RNTI Radio Network Temporary Identifier

[0726] CAG Closed Access Group RRC Radio Resource Control

[0727] CG Cell Group RRM Radio Resource Management

[0728] C-RNTI Cell RNTI RSRP Reference Signal Received Power

[0729] CSI Channel State Information RSRQ Reference Signal Received Quality

[0730] DCI Downlink Control Information RSSI Received Signal Strength Indicator

[0731] DRB (user) Data Radio Bearer SCell Secondary Cell

[0732] DTX Discontinuous Reception SCS Subcarrier Spacing

[0733] HARQ Hybrid Automatic Repeat Request

[0734] SDAP Service Data Adaptation Protocol

[0735] IE Information element SDU Service Data Unit

[0736] LCG Logical Channel Group SFN System Frame Number

[0737] MAC Medium Access Control S-GW Serving Gateway

[0738] MIB Master Information Block SI System Information

[0739] NAS Non-Access Stratum SIB System Information Block

[0740] NG-RAN NG Radio Access Network SpCell Special Cell

[0741] NR NR Radio Access SRB Signalling Radio Bearer

[0742] PBR Prioritised Bit Rate SRS Sounding Reference Signal

[0743] PCell Primary Cell SS Search Space

[0744] PCI Physical Cell Identifier SSB SS / PBCH block

[0745] PDCCH Physical Downlink Control Channel

[0746] SSS Secondary Synchronisation Signal

[0747] PDCP Packet Data Convergence Protocol SUL Supplementary Uplink

[0748] PDSCH Physical Downlink Shared Channel

[0749] TM Transparent Mode

[0750] PDU Protocol Data Unit UCI Uplink Control Information

[0751] PHR Power Headroom Report UE User Equipment

[0752] PLMN Public Land Mobile Network UM Unacknowledged Mode

[0753] PRACH Physical Random Access Channel

[0754] CRP Cell Reselection Priority

[0755] PRB Physical Resource Block PSS Primary Synchronisation Signal

[0756] PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel

Claims

Claim 1 A terminal in a wireless communication system comprising: a transceiver configured to transmit and receive signals; and a controller configured to control the transceiver; wherein the controller receives system information from a base station, the system information comprising at least a first parameter for the number of paging opportunities and a first parameter for a paging frame offset; and is configured to monitor at least one monitoring opportunity of a set of specific continuous monitoring opportunities, wherein if first specific conditions are satisfied, the starting monitoring opportunity number of the set of specific continuous monitoring opportunities is determined based on a second parameter associated with the first monitoring opportunity, and if second specific conditions are satisfied, the starting monitoring opportunity number of the set of specific continuous monitoring opportunities is determined based on a first parameter associated with the first monitoring opportunity, the first specific conditions comprising: the system information comprising a second parameter associated with the first monitoring opportunity; and paging adaptation being applied, and the second specific conditions comprising at least the system information comprising a first parameter associated with the first monitoring opportunity. Claim 2 A terminal according to claim 1, wherein the second specific conditions further comprise that paging adaptation is not applied. Claim 3 A terminal according to claim 1, wherein the first specific conditions are satisfied and the system information further comprises a second parameter for the number of paging opportunities and a second parameter for a paging frame offset, wherein the paging frame is determined based on the second parameter for the paging frame offset and the index of the paging opportunity is determined based on the second parameter for the number of paging opportunities. Claim 4 A terminal according to claim 3, wherein the second specific conditions are satisfied and the system information does not include a second parameter for the number of paging opportunities and a second parameter for the paging frame offset, the paging frame is determined based on the first parameter for the paging frame offset, and the index of the paging opportunity is determined based on the first parameter for the number of paging opportunities.

Citation Information

Patent Citations

  • Method, device and system for configuring and determining paging opportunities

    KR1020210095698A

  • Method and Apparatus for terminal to paging in mobile wireless communication system

    KR1020230169060A