Method and apparatus for transmitting and receiving wireless signals in a wireless communication system

Abstract

Disclosed are a method for a terminal to monitor a signal in a wireless communication system according to various embodiments and an apparatus therefor. Disclosed are a method and an apparatus, the method including receiving, from a base station, configuration information for a connected mode discontinuous reception (C-DRX), detecting first downlink control information (DCI) including wake-up indication information, and determining whether to monitor, based on a result of the detection of the first DCI, second DCI related to a cell discontinuous transmission (DTX) or a cell DRX in an inactive time interval configured by the configuration information.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically, to methods and apparatus for transmitting and receiving wireless signals. Background Technology

[0002] Wireless communication systems are widely deployed to provide various communication services, such as voice and data. Typically, a wireless communication system is a multiple access system that can support communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of multiple access systems include Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA).

[0003] With an increasing number of communication devices requiring larger communication services, and given current trends, the next-generation fifth-generation (5G) system is needed to provide enhanced wireless broadband communication compared to traditional LTE systems. In the next-generation 5G system, communication scenarios include enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC).

[0004] In this paper, eMBB is a next-generation mobile communication scenario characterized by high spectral efficiency, high user experience data rate, and high peak data rate; URLLC is a next-generation mobile communication scenario characterized by ultra-high reliability, ultra-low latency, and ultra-high availability (e.g., vehicle-to-everything (V2X), emergency services, and remote control); and mMTC is a next-generation mobile communication scenario characterized by low cost, low energy, short packet size, and massive connectivity (e.g., Internet of Things (IoT)). Summary of the Invention

[0005] Technical issues

[0006] The purpose of this disclosure is to provide methods and apparatus for transmitting and receiving signals more accurately and efficiently.

[0007] Those skilled in the art will understand that the objectives that can be achieved by various embodiments of this disclosure are not limited to those specifically described above, and that the above and other objectives that can be achieved by various embodiments of this disclosure will become clearer from the following detailed description.

[0008] Technical solution

[0009] According to one aspect, a method for receiving signals by a user equipment (UE) may include the following steps: receiving configuration information for connected mode discontinuous reception (C-DRX) from a base station (BS); detecting first downlink control information (DCI) including wake-up indication information; and determining, based on the result of detecting the first DCI, whether to monitor a second DCI related to cell DRX or cell discontinuous transmission (DTX) during an inactive period configured by the configuration information.

[0010] Alternatively, based on the default operation of performing a wake-up operation due to the failure to detect the first DCI, monitoring of the second DCI can be performed during inactive periods.

[0011] Alternatively, based on the default operation of performing sleep since the first DCI is not detected, monitoring of the second DCI may not be performed during inactive periods.

[0012] Alternatively, based on the detection of a first DCI including wake-up indication information with bit values ​​associated with wake-up, monitoring of a second DCI can be performed during inactive periods.

[0013] Alternatively, based on the detection of a first DCI including wake-up indication information with sleep-related bit values, monitoring of the second DCI may not be performed during inactive periods.

[0014] Alternatively, monitoring of the second DCI can be performed only during the duration of sleep initiation indicated by the first DCI.

[0015] Alternatively, the wake-up indication information may include a first bit value or a second bit value, the first bit value indicating the start of the drx-onDurationTimer for the next DRX cycle, and the second bit value indicating that the drx-onDurationTimer for the next DRX cycle has not been started.

[0016] Alternatively, the second DCI format may also include a CHO trigger bit indicating whether a conditional switch (CHO) is triggered.

[0017] Alternatively, the first DCI can be DCI format 2_6, and the second DCI can be DCI format 2_9.

[0018] According to another aspect, a computer-readable recording medium may be provided for recording a program for performing the above-described method for receiving signals.

[0019] According to another aspect, a UE for performing the above-described method for receiving signals can be provided.

[0020] According to another aspect, a processing apparatus for controlling a UE that performs the above-described method for receiving signals can be provided.

[0021] According to another aspect, a method for a BS to send a signal may include the following steps: sending configuration information for connected mode discontinuous reception (C-DRX) to a UE; and determining whether to send a second DCI related to cell DRX or cell DTX during an inactive period configured for the UE by the configuration information based on whether a first DCI including wake-up indication information is sent.

[0022] Beneficial effects

[0023] According to embodiments of this disclosure, signals can be transmitted or received more accurately and more efficiently in a wireless communication system.

[0024] Alternatively, the power consumption of the network and / or user equipment (UE) can be controlled more efficiently in a wireless communication system.

[0025] The effects to be achieved by the implementation method are not limited to those specifically described above, and those skilled in the art to which the implementation method pertains will gain a clearer understanding of other effects not mentioned herein based on the following detailed description. Attached Figure Description

[0026] The accompanying drawings, which are included to provide a further understanding of this disclosure and are incorporated into and constitute a part of this application, illustrate embodiments of this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0027] Figure 1 This is a diagram illustrating the physical channels used in a 3GPP NR system and the typical signal transmission methods using them.

[0028] Figure 2 The structure of an NR radio frame to which this disclosure applies is illustrated.

[0029] Figure 3 The time slot structure of the NR frame to which this disclosure applies is illustrated.

[0030] Figure 4 This is a diagram illustrating an exemplary mapping of the physical channel in a time slot to which the implementation method is applicable.

[0031] Figure 5 and Figure 6 This is a diagram used to illustrate Discontinuous Receive (DRX) operation in idle mode.

[0032] Figures 7 to 9 This is a diagram used to illustrate DRX operation in Radio Resource Control (RRC) connection mode.

[0033] Figure 10This is a diagram used to illustrate the method of monitoring DCI format 2_6.

[0034] Figure 11 This is a diagram illustrating a method for monitoring a second DCI by a user equipment (UE).

[0035] Figure 12 This diagram illustrates a method for a base station (BS) to send a second DCI to a UE.

[0036] Figures 13 to 16 The communication system 1 and wireless device to which this disclosure applies are illustrated. Detailed Implementation

[0037] The embodiments disclosed herein are applicable to various radio access technologies such as Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA). CDMA can be implemented as radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as radio technologies such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rate GSM Evolution (EDGE). OFDMA can be implemented as radio technologies such as IEEE 802.11 (Wireless Fidelity (Wi-Fi)), IEEE 802.16 (Global Microwave Access Interoperability (WiMAX)), IEEE 802.20, and Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of Evolved UMTS using E-UTRA (E-UMTS), and LTE-Advanced (A) is an evolution of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolution of 3GPP LTE / LTE-A.

[0038] As more and more communication devices require greater communication capacity, there is a need for enhanced mobile broadband communications compared to traditional radio access technologies (RATs). Furthermore, the ability to provide various services anytime, anywhere by connecting multiple devices and objects is another important consideration for next-generation communications. Communication system designs considering reliability and latency-sensitive services / UEs are also being discussed. Therefore, the introduction of new radio access technologies that consider enhanced mobile broadband (eMBB), massive MTC, and ultra-reliable low-latency communication (URLLC) is being discussed. In this disclosure, for simplicity, this technology will be referred to as NR (New Radio or New RAT).

[0039] The term "base station" as used in this document can be replaced with terms such as fixed station, node B, gNode B (gNB), access point (AP), cell, or transmit and receive point (TRP). "Relay" can be replaced with terms such as relay node (RN), relay station, etc. Additionally, the term "terminal" can be replaced with terms such as user equipment (UE), mobile station (MS), mobile subscriber station (MSS), subscriber station (SS), etc.

[0040] For the sake of brevity, the description focuses on 3GPP NR, but the technical concepts disclosed herein are not limited thereto.

[0041] Details regarding the background, terminology, abbreviations, etc., used herein can be found in documents previously published. For example, this disclosure may be supported by the following documents: - 38.211: Physical Channels and Modulation - 38.212: Multiplexing and Channel Coding - 38.213: Physical layer procedures for control - 38.214: Physical layer procedures for data - 38.215: Physical Layer Measurement - 38.300: General Description of NR and NG-RAN - 38.304: User Equipment (UE) Procedures in Idle Mode and RRC Inactive State - 38.321: Media Access Control (MAC) Protocol Specification - 38.331: Radio Resource Control (RRC) Protocol Specification - 37.213: Introduces channel access procedures for unlicensed spectrum for NR-based access. - 36.355: LTE positioning protocol - 37.355: LTE positioning protocol

[0042] Terms and acronyms

[0043] - 5GC: 5G Core Network

[0044] - 5GS: 5G system

[0045] - NES: Network Energy Saving

[0046] - ES: Energy Saving

[0047] - SSB: Synchronization Signal / PBCH Block

[0048] - FR: Frequency range

[0049] - CC: Component Carrier

[0050] - NCGI: NR Cell Global Identifier

[0051] - SI: System Information

[0052] - PCell: Main Cell

[0053] - SCell: Secondary Cell

[0054] - PDCCH: Physical Downlink Control Channel

[0055] - PDSCH: Physical Downlink Shared Channel

[0056] - PUSCH: Physical Uplink Shared Channel

[0057] - CSI: Channel State Information

[0058] - RRM: Radio Resource Management

[0059] - SCS: Subcarrier Spacing

[0060] - RLM: Radio Link Monitoring

[0061] - DCI: Downlink Control Information

[0062] - CAP: Channel Access Procedure

[0063] - Ucell: License-free cell

[0064] - TBS: Transport Block Size

[0065] - TDRA: Time Domain Resource Allocation

[0066] - SLIV: Start and Length Indicator Value (SLIV is a field that indicates the start symbol index and the number of symbols in the slot for the PDSCH and / or PUSCH, and SLIV is carried on the PDCCH that schedules the corresponding PDSCH and / or PUSCH).

[0067] - BWP: Bandwidth component (A BWP can consist of consecutive resource blocks (RBs) in the frequency domain, which can correspond to a set of parameters (e.g., subcarrier spacing, cyclic prefix (CP) length, slot / mini-slot duration, etc.). Additionally, multiple BWPs can be configured on a single carrier (the number of BWPs per carrier can be finite), but the number of active BWPs per carrier can be limited (e.g., one).

[0068] - CORESET: Control Resource Set (CORESET refers to the time-frequency resource area that can transmit PDCCH, and the number of CORESETs per BWP can be limited.)

[0069] - REG: Resource Element Group

[0070] - SFI: Slot Format Indicator (SFI is an indicator that indicates the DL / UL direction at the symbol level in a specific time slot, and SFI is transmitted via the group common PDCCH.)

[0071] - COT: Channel Occupancy Time

[0072] - SPS: Semi-persistent scheduling

[0073] - QCL: Quasi-colocation (The QCL relationship between two reference signals can represent that QCL parameters such as Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx parameter obtained from one reference signal can be applied to another reference signal (or the antenna port of that RS). In NR systems, four QCL types are defined as follows: "Type A": {Doppler shift, Doppler spread, average delay, delay spread}, "Type B": {Doppler shift, Doppler spread}, "Type C": {Doppler shift, average delay}, "Type D": {spatial Rx parameter}. For any DL RS antenna port, the first DL RS can be set to reference QCL type X (X=A, B, C, or D), and the second DL RS can be set to reference QCL type Y (Y=A, B, C, or D, but X≠Y).)

[0074] - TCI: Transmission Configuration Indicator (A TCI state contains the QCL relationship between one or more DL RSs, such as the DM-RS port of PDSCH, the DM-RS port of PDCCH, or the CSI-RS port of CSI-RS resources. For the "Transmission Configuration Indicator" field in the DCI of the scheduling PDSCH, the TCI state index corresponding to each code point including this field is activated via MAC CE, and the TCI state setting for each TCI state index is set via RRC signaling. In the Rel-16 NR system, the corresponding TCI state is set between DL RSs, but future versions may allow setting between DL RSs and UL RSs or between UL RSs. Examples of UL RSs are SRS, PUSCH DM-RS, PUCCH DM-RS, etc.)

[0075] - SRI: SRS Resource Indicator (Indicates one of the SRS resource index values ​​set in the "SRS Resource Indicator" field of the DCI for scheduling PUSCH. When transmitting PUSCH, the terminal may use the same spatial domain transmission filter used for transmitting and receiving reference signals associated with the corresponding SRS resource. In this case, the reference RS is set by RRC signaling via the SpatialRelationInfo parameter for each SRS resource, and SS / PBCH blocks, CSI-RS, or SRS can be set as the reference RS.)

[0076] - TRP: Transmitting and Receiving Point

[0077] In wireless communication systems, terminals receive information from base stations via the downlink (DL) and transmit information to base stations via the uplink (UL). The information transmitted and received by base stations and terminals includes data and various control information, and various physical channels exist depending on the type / purpose of the information they transmit and receive.

[0078] Figure 1 This is a diagram illustrating the physical channels used in a 3GPP NR system and the typical signal transmission methods using them.

[0079] Upon power-on or when the UE initially enters a cell, the UE performs an initial cell search involving synchronization with the BS in step S101. For the initial cell search, the UE receives a Synchronization Signal Block (SSB). The SSB includes a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). The UE synchronizes with the BS and obtains information such as the cell identifier (ID) based on the PSS / SSS. The UE can then receive broadcast information from the cell on the PBCH. Furthermore, the UE can check the downlink channel state by receiving a Downlink Reference Signal (DL RS) during the initial cell search.

[0080] After the initial cell search, in step S102, the UE can obtain more specific system information by receiving the Physical Downlink Control Channel (PDCCH) and receiving the Physical Downlink Shared Channel (PDSCH) based on the information in the PDCCH.

[0081] Subsequently, to establish a connection with the eNB, the UE can perform a random access procedure with the eNB (S103 to S106). During the random access procedure, the UE can transmit a preamble on the Physical Random Access Channel (PRACH) (S103) and receive the PDCCH and the Random Access Response (RAR) for the preamble on the PDSCH associated with the PDCCH (S104). The UE can transmit the Physical Uplink Shared Channel (PUSCH) using the scheduling information in the RAR (S105) and perform a contention resolution procedure including receiving the PDCCH signal and the corresponding PDSCH signal (S106).

[0082] Following the above process, during general UL / DL signal transmission, the UE can receive PDCCH and / or PDSCH from the BS (S107) and send PUSCH and / or Physical Uplink Control Channel (PUCCH) to the BS (S108). The control information sent by the UE to the BS is typically called Uplink Control Information (UCI). UCI includes Hybrid Automatic Repeat and Request Acknowledgment / Negative Acknowledgment (HARQ-ACK / NACK), Scheduling Request (SR), Channel Quality Indicator (CQI), Precoding Matrix Index (PMI), Rank Indicator (RI), etc. UCI is usually sent periodically on the PUCCH. However, if control information and service data should be sent simultaneously, they can be sent on the PUSCH. Additionally, UCI can be sent aperiodically on the PUSCH when a request / command is received from the network.

[0083] Figure 2 The structure of an NR radio frame to which this disclosure applies is illustrated. (Refer to...) Figure 2 Radio frames can be used for UL and DL transmissions in NR. A radio frame is 10 ms long and can be defined by two 5 ms half-frames. HF can include five 1 ms subframes. Subframes can be divided into one or more time slots, and the number of time slots in SF can be determined based on the subcarrier spacing (SCS). Depending on the cyclic prefix (CP), each time slot can include 12 or 14 OFDM (A) symbols.

[0084] Table 1 shows how the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary with SCS when using normal CP.

[0085] [Table 1] N slot symb Number of symbols in a time slot Nframe,u slot Number of time slots in a frame N subframe,u slot Number of time slots in a subframe Table 2 below lists the number of symbols per slot, the number of slots per frame, and the number of slots per subframe under the SCS in the ECP case.

[0086] [Table 2]

[0087] The frame structure is just an example, and the number of subframes, time slots, and symbols in a frame can vary.

[0088] In NR systems, different OFDM(A) parameter sets (e.g., SCS, CP length, etc.) can be configured for multiple cells aggregated for a single UE. Therefore, the (absolute) duration of time resources (e.g., SF, time slots, or TTI) comprising the same number of symbols can differ between aggregated cells (for ease of description, such time resources are often referred to as time units (TUs)).

[0089] Figure 3 The slot structure of the NR frame to which this disclosure applies is illustrated. (Refer to...) Figure 3 A time slot comprises multiple symbols in the time domain. For example, a time slot may include 14 symbols in a normal CP and 12 symbols in an extended CP. Alternatively, a time slot may include 7 symbols in a normal CP and 6 symbols in an extended CP. A carrier may include multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple consecutive subcarriers (e.g., 12 subcarriers) in the frequency domain. A bandwidth portion (BWP) may be defined as multiple consecutive (P) RBs in the frequency domain, and a BWP may correspond to a set of parameters (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication can take place in an active BWP. In the resource grid, each element may be called a resource element (RE) and may be mapped to a complex symbol.

[0090] Figure 4This is a diagram illustrating an exemplary mapping of physical channels in a time slot to which the implementation method applies. A time slot may include all DL control channels, DL or UL data, and UL control channels. For example, the first N symbols of a time slot may be used to transmit DL control channels (hereinafter referred to as the DL control area), and the last M symbols of the time slot may be used to transmit UL control channels (hereinafter referred to as the UL control area). Each of N and M is an integer equal to or greater than 0. The resource area between the DL control area and the UL control area (hereinafter referred to as the data area) may be used to transmit DL data or UL data. There may be time gaps between the control area and the data area for DL-to-UL or UL-to-DL handover. PDCCH can be transmitted in the DL control area, and PDSCH can be transmitted in the DL data area. Some symbols at the DL-to-UL handover time in a time slot may be used as time gaps.

[0091] The PDCCH transmits the DCI. For example, the PDCCH (i.e., the DCI) may carry information about the transmission format and resource allocation of the DL-SCH, resource allocation information for the Uplink Shared Channel (UL-SCH), paging information for the PCH, system information for the DL-SCH, resource allocation information for higher-layer control messages (e.g., RARs transmitted on the PDCCH), transmission power control commands, information about enabling / releasing configured schedules, etc. The DCI includes Cyclic Redundancy Check (CRC). The CRC is masked using various identifiers (IDs) (e.g., Radio Network Temporary Identifiers (RNTIs)) depending on the owner or purpose of the PDCCH. For example, if the PDCCH is used for a specific UE, the CRC is masked using the UE ID (e.g., Cell-RNTI (C-RNTI)). If the PDCCH is used for paging messages, the CRC is masked using the Paging-RNTI (P-RNTI). If the PDCCH is used for system information (e.g., System Information Block (SIB)), the CRC is masked by the System Information RNTI (SI-RNTI). When the PDCCH is used for RAR, the CRC is masked by the Random Access-RNTI (RA-RNTI).

[0092] To receive PDCCH, a terminal can monitor (e.g., blindly decode) the PDCCH candidate set in a CORESET. A PDCCH candidate represents a CCE monitored by the terminal for PDCCH reception / detection. PDCCH monitoring can be performed on one or more CORESETs on the active DL BWP of each active cell where PDCCH monitoring is enabled. The PDCCH candidate set monitored by the terminal is defined as a PDCCH search space (SS) set. The SS set can be a common search space (CSS) set or a UE-specific search space (USS) set.

[0093] Table 3 shows the characteristics of each SS.

[0094] [Table 3]

[0095] SS sets can be established via system information (e.g., MIB) or terminal-specific upper-layer (e.g., RRC) signaling. Each DL BWP in the serving cell can establish no more than S (e.g., 10) SS sets. For example, the following parameters / information can be provided for each SS set. Each SS set is associated with one CORESET, and each CORESET configuration can be associated with one or more SS sets.

[0096] - searchSpaceId: Represents the ID of the SS set.

[0097] - controlResourceSetId: Indicates the CORESET associated with the SS set.

[0098] - monitoringSlotPeriodicityAndOffset: Indicates the PDCCH monitoring period interval (in time slots) and the PDCCH monitoring interval offset (in time slots).

[0099] - monitoringSymbolsWithinSlot: Indicates the first OFDMA symbol used for PDCCH monitoring within a slot where PDCCH monitoring is enabled. It is indicated via a bitmap, where each bit corresponds to each OFDMA symbol within the slot. The MSB of the bitmap corresponds to the first OFDMA symbol in the slot. The OFDMA symbol corresponding to a bit with a value of 1 corresponds to the first symbol in the CORESET of the slot.

[0100] - nrofCandidates: Indicates the number of PDCCH candidates per AL = {1, 2, 4, 8, 16} (e.g., one of the values ​​0, 1, 2, 3, 4, 5, 6, 8).

[0101] - searchSpaceType: Indicates whether the SS type is CSS or USS.

[0102] - DCI format: Indicates the DCI format of the PDCCH candidate.

[0103] Based on the CORESET / SS set settings, the terminal can monitor PDCCH candidates in one or more SS sets within a time slot. The timing (e.g., time / frequency resources) used to monitor PDCCH candidates is defined as a PDCCH (monitoring) opportunity. One or more PDCCH (monitoring) opportunities can be configured within a time slot.

[0104] [Table 4]

[0105] 1) PUCCH format 0 (PF0)

[0106] - Supported UCI payload size: up to K bits (e.g., K=2)

[0107] - The number of OFDM symbols that make up a single PUCCH: 1 to X symbols (e.g., X=2)

[0108] - Transmission structure: Consists only of UCI signals, without DM-RS, and the UCI state is transmitted by selecting and transmitting one of multiple sequences.

[0109] 2) PUCCH Format 1 (PF1)

[0110] - Supported UCI payload size: up to K bits (e.g., K=2)

[0111] - Number of OFDM symbols that make up a single PUCCH: Y to Z symbols (e.g., Y=4, Z=14)

[0112] - Transmission structure: UCI and DM-RS are composed of different OFDM symbols in TDM form, where UCI multiplies certain sequences with modulation (e.g., QPSK) symbols. Cyclic shift (CS) / orthogonal overlay code (OCC) is applied to both UCI and DM-RS to support CDM (following PUCCH format 1) between multiple PUCCH resources (within the same RB).

[0113] 3) PUCCH Format 2 (PF2)

[0114] - Supported UCI payload size: more than K bits (e.g., K=2)

[0115] - The number of OFDM symbols that make up a single PUCCH: 1 to X symbols (e.g., X=2)

[0116] - Transmission structure: DMRS and UCI are configured / mapped in FDM form within the same symbol and transmitted by applying an IFFT without DFT to only the encoded UCI bits.

[0117] 4) PUCCH Format 3 (PF3)

[0118] - Supported UCI payload size: more than K bits (e.g., K=2)

[0119] - Number of OFDM symbols that make up a single PUCCH: Y to Z symbols (e.g., Y=4, Z=14)

[0120] - Transmission Structure: DMRS and UCI are configured / mapped to different symbols in TDM form and transmitted by applying a DFT to the enhanced UCI bits. Multiplexing is supported for multiple terminals by applying the OCC in the DFT preamble to the UCI and applying the CS (or IFDM mapping) to the DMRS.

[0121] 5) PUCCH Format 4 (PF4)

[0122] - Supported UCI payload size: more than K bits (e.g., K=2)

[0123] - Number of OFDM symbols that make up a single PUCCH: Y to Z symbols (e.g., Y=4, Z=14)

[0124] - Transmission structure: DMRS and UCI are configured / mapped to different symbols in TDM format and transmitted between terminals without multiplexing by applying DFT to the encoded UCI bits.

[0125] DRX (Discontinuous Receiver) Operation

[0126] The UE uses Discontinuous Reception (DRX) in the RRC_IDLE and RRC_INACTIVE states to reduce power consumption. When DRX is configured, the UE performs DRX operations according to the DRX configuration information.

[0127] When the UE operates based on DRX, the UE repeatedly turns on / off to receive data. For example, when DRX is configured, the UE only attempts to receive / detect PDCCH (e.g., PDCCH monitoring) during a predetermined time interval (e.g., on), and does not attempt to receive PDCCH during the remaining time period (e.g., off / sleep).

[0128] The period during which the UE should attempt to receive the PDCCH is called the on-duration, and this on-duration is defined once per DRX cycle. The UE can receive DRX configuration information from the gNB via RRC signaling, and the reception of the (long) DRX command MAC CE is considered as DRX operation.

[0129] DRX configuration information can be included in MAC-CellGroupConfig. MAC-CellGroupConfig is used to configure MAC parameters for cell groups, including DRX.

[0130] DRX (Discontinuous Receive) refers to an operating mode that enables the UE (User Equipment) to reduce battery consumption by discontinuously receiving / monitoring the downlink channel. In other words, a UE configured with DRX can reduce power consumption by discontinuously receiving DL signals. DRX operation is performed in a DRX cycle that is periodically repeated for an indicated on-duration period. The DRX cycle includes an on-duration period and a sleep-duration period (or an opportunity for DRX). The on-duration period indicates the time interval during which the UE monitors the PDCCH in order to receive the PDCCH. DRX can be performed in the RRC (Radio Resource Control)_IDLE state (or mode), RRC_INACTIVE state (or mode), or RRC_CONNECTED state (or mode). In the RRC_IDLE and RRC_INACTIVE states, DRX is used for discontinuous reception of paging signals.

[0131] - RRC_Idle state: The state in which no radio connection (RRC connection) has been established between the base station and the UE.

[0132] - RRC inactive state: A radio connection (RRC connection) has been established between the base station and the UE, but the radio connection is deactivated.

[0133] - RRC_Connected status: The status of a radio connection (RRC connection) established between the base station and the UE.

[0134] DRX is basically divided into Idle Mode DRX, Connected DRX (C-DRX), and Extended DRX. DRX used in the RRC idle state is called Idle Mode DRX, and DRX used in the RRC connected state is called Connected Mode DRX (C-DRX).

[0135] eDRX (Extended / Enhanced DRX) is a mechanism that extends the loop of Idle Mode DRX and C-DRX. In Idle Mode DRX, whether eDRX is allowed can be configured based on system information (e.g., SIB1).

[0136] SIB1 can include the eDRX enable parameter. The eDRX enable parameter is a parameter that indicates whether idle mode extended DRX is allowed.

[0137] (1) Idle mode DRX

[0138] In idle mode, the UE can use DRX to reduce power consumption. A paging opportunity (PO) can be a time interval (e.g., a time slot or subframe) during which a Physical Downlink Control Channel (PDCCH) based on a Paging-Radio Network Temporary Identifier (P-RNTI) can be transmitted. The P-RNTI-based PDCCH can address / schedule paging messages. For P-RNTI-based PDCCH transmissions, the PO can indicate the first subframe used for PDCCH repetition.

[0139] A paging frame (PF) is a radio frame that may include one or more paging opportunities. When DRX is used, the UE can be configured to monitor only one PO per DRX cycle. The PF, PO, and / or PNB can be determined based on DRX parameters provided via network signaling (e.g., system information).

[0140] In the following text, “PDCCH” may refer to MPDCCH, NPDCCH, and / or normal PDCCH. In the following text, “UE” may refer to MTC UE, BL (Bandwidth Reduction Low Complexity) / CE (Coverage Enhancement) UE, NB-IoT UE, RedCap UE, normal UE, and / or IAB-MT (Mobile Terminal).

[0141] Figure 5 This is a flowchart illustrating an example of a method for performing an idle mode DRX operation.

[0142] The UE receives idle mode DRX configuration information from the base station via higher-layer signaling (e.g., system information) (S110).

[0143] Furthermore, the UE determines the PF (paging frame) and PO (paging opportunity) for monitoring the physical downlink control channel (e.g., PDCCH) during the paging DRX cycle based on the idle mode DRX configuration information (S120). In this case, the DRX cycle includes an on duration and a sleep duration (or an opportunity for DRX).

[0144] In addition, the UE monitors the PDCCH (S130) within the determined PO of the PF. For each paging DRX cycle, the UE monitors only one time interval (PO). For example, the time interval can be a time slot or a subframe.

[0145] Additionally, if the UE receives a PDCCH scrambled by P-RNTI (more precisely, the CRC of the PDCCH) during the on-time duration (i.e., if paging is detected), the UE can switch to connected mode and send or receive data with the base station.

[0146] Figure 6 This is a diagram illustrating an example of DRX operation in idle mode.

[0147] Reference Figure 6 If there is service (data) directed to a UE in the RRC_Idle state (hereinafter referred to as "idle state"), then a paging will be performed on the corresponding UE.

[0148] Therefore, the UE wakes up and monitors the PDCCH in each (paging) DRX cycle.

[0149] If paging is present, the UE switches to connected state and receives data. Otherwise, the UE can re-enter sleep mode.

[0150] (2) Connectivity Mode DRX (C-DRX)

[0151] C-DRX is a DRX used in RRC connection mode. C-DRX DRX cycles can be configured with short DRX cycles and / or long DRX cycles. Short DRX cycles are optional.

[0152] If C-DRX is configured, the UE performs PDCCH monitoring during the on-duration period. If a PDCCH is successfully detected during PDCCH monitoring, the UE operates (or runs) an inactivity timer and remains awake. Conversely, if a PDCCH is not successfully detected during PDCCH monitoring, the UE enters a sleep state after the on-duration period ends.

[0153] If C-DRX is configured, PDCCH reception timing can be configured discontinuously based on the C-DRX configuration (e.g., time slots with a PDCCH search space / candidate). Conversely, if C-DRX is not configured, PDCCH reception timing can be configured continuously based on the PDCCH search space configuration (e.g., time slots with a PDCCH search space / candidate). Furthermore, PDCCH monitoring can be restricted to time intervals configured as measurement gaps, regardless of the C-DRX configuration.

[0154] Figure 7 This is a flowchart illustrating an example of a method for performing a C-DRX operation.

[0155] The UE receives RRC signaling (e.g., MAC-MainConfig IE) from the base station, which includes DRX configuration information (S310). The DRX configuration information may include the following information.

[0156] - on-duration: The duration for which the UE waits to receive the PDCCH after waking up. If the UE successfully decodes the PDCCH, the UE remains awake and starts the drx-inactivity timer; - onDurationTimer: The duration at which the DRX cycle begins. For example, the duration can refer to the time interval to be continuously monitored at the beginning of the DRX cycle, which can be expressed in milliseconds (ms).

[0157] - drx-InactivityTimer: PDCCH indicates the duration following the PDCCH timing of a new UL or DL ​​transmission for a MAC entity. For example, the duration can be a time interval in milliseconds after the UE decodes a PDCCH that includes scheduling information. In other words, the duration refers to the time the UE waits for another PDCCH to be successfully decoded after decoding the first one. If no other PDCCH is detected within the corresponding duration, the UE transitions to sleep mode.

[0158] Apart from the PDCCH used for retransmission, the UE restarts the drx-inactivity timer only after successfully decoding the PDCCH used for the initial transmission.

[0159] - drx-RetransmissionTimer: For DL, the maximum duration before a DL retransmission is received; for UL, the maximum duration before a permission to retransmit for UL is received. For example, for UL, drx-RetransmissionTimer indicates the number of time slots in the bandwidth portion (BWP) of the transport block (TB) to be retransmitted. For DL, drx-RetransmissionTimer indicates the number of time slots in the BWP of the TB to be retransmitted.

[0160] - longDRX-Cycle: Enables the duration of the event.

[0161] - drxStartOffset: The subframe number at which the DRX loop begins.

[0162] - drxShortCycleTimer: The UE should follow the duration of the short DRX cycle; - shortDRX-Cycle: The number of times the DRX loop operates up to the number of drxShortCycleTimers when Drx-InactivityTimer terminates. - drx-SlotOffset: The delay before drx-onDurationTimer starts. For example, the delay can be expressed in milliseconds (ms), and more specifically, in multiples of 1 / 32 ms.

[0163] - Activity time: The total duration for which the UE monitors the PDCCH, which may include (a) the "on-duration" of the DRX cycle, (b) the time during which the UE performs continuous reception while the drx-inactivity timer has not expired, and (c) the time during which the UE performs continuous reception while waiting for a retransmission opportunity.

[0164] Specifically, when DRX cyclic is configured, the active time of the serving cell in a DRX group includes the following items.

[0165] - (a) drx-onDurationTimer configured for the DRX group or (b) drx-InactivityTimer is running; or

[0166] - (c) Running drx-RetransmissionTimerDL or drx-RetransmissionTimerUL on any serving cell in the DRX group; or

[0167] - (d) Ra-ContentionResolutionTimer or msgB-ResponseWindow is running; or

[0168] - (e) The scheduling request was sent on the PUCCH and is pending; or

[0169] - (f) After successfully receiving a random access response for a contention-based random access preamble that was not selected by the MAC entity, a PDCCH indicating a new transmission addressing to the MAC entity has not yet been received.

[0170] In addition, if DRX “on” is configured via DRX command of MAC CE (command element) (S320), the UE monitors PDCCH during the on duration of the DRX cycle based on the DRX configuration (S330).

[0171] Figure 8 This is a diagram illustrating an example of C-DRX operation.

[0172] Reference Figure 8 When the UE receives scheduling information (e.g., DL assignment or UL permission) in the RRC_Connected state (hereinafter referred to as the connected state), the UE runs the DRX inactivity timer and the RRC inactivity timer.

[0173] DRX mode begins after the DRX inactivity timer expires. The UE wakes up during the DRX cycle and monitors the PDCCH for a predetermined time (duration timer).

[0174] In this scenario, if short DRX is configured, when the UE initiates DRX mode, it first starts with a short DRX cycle and then transitions to a long DRX cycle after the short DRX cycle terminates. The long DRX cycle is a multiple of the short DRX cycle. During the short DRX cycle, the UE wakes up more frequently. After the RRC inactivity timer expires, the UE transitions to an idle state and performs idle mode DRX operations.

[0175] Figure 9 An example of a DRX cycle is provided. To conserve UE power, C-DRX operation has been introduced. If the UE does not receive a PDCCH within the on-duration defined for each DRX cycle, the UE enters sleep mode until the next DRX cycle and does not perform any transmit / receive operations.

[0176] On the other hand, when the UE receives the PDCCH during the on-duration period, the active time can continue (or be extended) based on the operation of the inactivity timer, retransmission timer, etc. If the UE does not receive additional data during the active time, the UE can operate in sleep mode until the next DRX operation.

[0177] In NR, a Wake-up Signal (WUS) has been introduced to provide additional power-saving gains beyond existing C-DRX operations. The WUS can be used to notify the UE whether PDCCH monitoring needs to be performed on-duration in each DRX cycle (or multiple DRX cycles). If the UE does not detect the WUS at the specified or indicated WUS timing, the UE can remain in sleep mode for one or more DRX cycles associated with the corresponding WUS without performing PDCCH monitoring.

[0178] (3) WUS (DCI format 2_6)

[0179] Figure 10 This is a diagram illustrating a method for monitoring DCI format 2_6.

[0180] According to the power-saving technology of the Rel-16 NR system, when performing DRX operation, the UE can be notified via DCI format 2_6 whether the UE needs to be woken up for each DRX cycle.

[0181] Reference Figure 10 For DCI format 2_6, the timing of PDCCH monitoring can be determined by the ps offset indicated by the network and the time interval reported by the UE. In this case, the time interval reported by the UE can be interpreted as the preparation period required for operation after the UE is woken up.

[0182] Reference Figure 10The base station (BS) can provide the UE with a search space (SS) set configuration capable of monitoring DCI format 2_6. Based on the corresponding SS set configuration, DCI format 2_6 can be monitored in consecutive time slots, as long as the duration falls within the monitoring period interval.

[0183] In the DRX configuration, the monitoring window used to monitor DCI format 2_6 can be determined by the start time of the DRX cycle (e.g., the time when the on-duration timer starts) and the ps offset configured by the BS. Additionally, PDCCH monitoring may not be required during the time intervals reported by the UE. Therefore, the timing of the SS set monitoring that the UE actually performs can be determined as the first complete duration within the monitoring window (i.e., Figure 10 (Actual monitoring timing).

[0184] If the UE detects DCI format 2_6 in the monitoring window based on the ps offset configuration, the BS can notify the UE whether to wake up in the next DRX cycle.

[0185] NES (Network Energy Saving)

[0186] Energy efficiency in network energy saving (BS) is considered important in wireless communication systems, including those in 3GPP, as it can help build environmentally friendly networks and reduce the operating expenses (OPEX) of communication service providers by reducing carbon emissions. Specifically, due to the need for high transmission rates with the introduction of 5G communications, BS should be equipped with more antennas and provide services in a wider bandwidth and frequency band. Therefore, recent studies have shown that the energy cost of BS has reached 20% of total OPEX. Due to the increased interest in BS energy efficiency, research on network energy saving (NES) is being discussed in 3GPP NR Release 18. Because of this increased interest in BS energy efficiency, a new research project entitled "Research on Network Energy Saving" has been approved for predetermined scenarios (e.g., 3GPP NR Release 18).

[0187] Specifically, the following enhancement technologies are considered in this project to improve energy efficiency from the perspective of BS transmission and reception.

[0188] - Methods for more finely adjusting transmission and / or reception in one or more NES technologies in the time, frequency, spatial, and power domains, and methods for achieving more efficient operation through potential UE assistance / feedback and potential UE assistance information.

[0189] The following describes in detail a method for monitoring the PDCCH during periods outside of active time (e.g., inactive time) when Connected Mode Discontinuous Reception (C-DRX) is configured for the UE.

[0190] PDCCH monitoring outside of UE C-DRX activity time

[0191] When a UE initially connects to a BS and enters connected mode (or RRC_CONNECTED state), it should continuously perform PDCCH monitoring to identify whether there are scheduled transmissions for the UE in each configured search space (SS). However, when transmissions are not always scheduled for the UE, the UE performs unnecessary PDCCH monitoring every time. In this case, the UE's battery may be depleted quickly. Therefore, to save UE power, the BS can configure C-DRX for the UE, which should be configured to perform PDCCH monitoring for an on duration and a off duration when PDCCH monitoring is not required. From the BS's perspective, the UE's C-DRX can also contribute to energy saving (ES). For example, since the BS does not need to send PDCCH to a specific UE during the UE's C-DRX off duration, it can use PDCCH resources for other purposes or gain ES gains through DTX / DRX. However, even during the off duration, the UE can use / transmit signals in pre-configured resources (e.g., SR, PUCCH, CG-PUSCH, etc.) without being restricted as needed. In this regard, the BS should remain ready to receive UL signals that can be transmitted from the UE at any time. Furthermore, since C-DRX is UE-specific, the DRX cycle or on / off duration may be misaligned among UEs within the cell. In this case, when the on-duty duration of a UE is configured using Time Division Multiplexing (TDM), the BS may have difficulty anticipating ES gain because the BS cannot sleep or perform a sleep operation to send PDCCH during each on-duty duration.

[0192] Therefore, similar to C-DRX for UEs, the BS can utilize cell-specific DTX / DRX configurations that periodically repeat active and inactive periods to save energy by shutting down the transmission / reception of specific signals / channels during inactive periods. To transmit and receive data, the UE should be in RRC_CONNECTED mode by establishing a connection (or RRC connection) with the BS. When there is no UE activity for a specific period, the BS can transition the UE to RRC_IDLE state to reduce UE power consumption. Whenever transmission / reception is needed, the UE may need to transition back to connected mode (or RRC connected mode). This RRC signaling used for connected mode transitions can increase the UE's signal transmission and reception latency. Alternatively, when the UE needs to frequently transmit small amounts of data, not only latency (e.g., latency caused by additional RRC signaling) but also signaling overhead may increase. To reduce the BS's signaling overhead and latency (e.g., UE signal transmission / reception latency) caused by such frequent RRC state changes, a new mode / state called RRC_INACTIVE has been introduced in the NR. In inactive mode, signal transmission / reception operations can be performed quickly with low signaling overhead by stopping / pausing the RRC connection.

[0193] When cell DTX / DRX operations are applied not only to UEs in RRC connected mode but also to UEs in idle and inactive modes, methods for setting cell DTX / DRX configuration parameters, methods for activating cell DTX / DRX configuration, and methods for transmitting / receiving signals and channels affected by cell DTX / DRX operations will be described in detail.

[0194] A UE in (RRC) connected mode / state can perform PDCCH monitoring during the periodic on duration to identify the presence of DL / UL signals to be transmitted / received. Upon receiving a PDCCH, a UE in connected mode can perform DL reception or UL transmission according to the PDCCH indication. In the case of UL signal transmission, if there is data to be transmitted in the UL buffer, the UE can wake up from sleep mode and send a scheduling request (SR), regardless of C-DRX. When the UE is in idle mode, the UE can periodically monitor paging or paging signals, and when the UE is not the target UE of the paging signal, it can operate in idle mode DRX (I-DRX) to re-enter sleep mode.

[0195] When it is said that a UE operates in sleep mode, this can mean "regardless of the activity time determined by C-DRX" or "even during periods other than the activity time determined by C-DRX". For example, a UE can be put into sleep mode regardless of the DRX activity time and / or inactivity time. The period of time in C-DRX operation that repeatedly includes an on duration and an off duration is called a DRX cycle. The length of a DRX cycle can be defined as the time from the start of the on duration to the start of the next on duration, and DRX cycles include long DRX cycles and short DRX cycles. When the length of a DRX cycle is long, the PDSCH to be sent by the BS can occur immediately after the end of a specific on duration of the UE. In this case, the transmission delay of the PDSCH may increase because the BS must wait until the next on duration of the UE. However, from the BS's perspective, since the UE does not send periodic CSI (P-CSI) or sounding reference signal (SRS) during the off duration, the BS can allocate resources for P-CSI or SRS to other UEs, thereby improving resource utilization, and the UE can also perform a switch to power-saving mode to save energy during the off duration.

[0196] Long and short DRX cycles can be configured simultaneously, and the long DRX cycle should be set to an integer multiple of the short DRX cycle (with the same onDurationTimer value). In this case, the UE can operate in the long DRX cycle when there is no data activity during the on-duration duration of the long DRX cycle (e.g., when no PDCCH is received). Conversely, when there is data activity, the UE can operate in the short DRX cycle for the duration of drx-ShortCycleTimer, and can switch back to the long DRX cycle when there is no data activity during the on-duration duration of the short DRX cycle. Similar to the long cycle, the start of the on-duration duration in the short DRX cycle can be determined by or based on the values ​​of drx-StartOffset and drx-SlotOffset.

[0197] The BS can instruct the UE to directly switch to DRX sleep mode via the DRX command MAC CE, instead of operating in active mode, until the active duration ends. In other words, the BS can terminate the UE's current active time and immediately put it into DRX cycle (or DRX sleep mode) via the DRX command MAC CE. When only a long DRX cycle is configured for the UE, the UE can operate in long DRX cycle mode. When a short DRX cycle is also configured for the UE, the UE can immediately enter short DRX cycle mode after receiving the DRX command MAC CE. Alternatively, when the BS instructs a long DRX command MAC CE, the UE can perform long DRX cycle operation even if a short DRX cycle is configured.

[0198] Furthermore, the BS can adjust the start point (or start time) of a long DRX cycle using the RRC parameter drx-LongCycleStartOffset. The value of drx-LongCycleStartOffset is defined in milliseconds, allowing the long DRX cycle to begin at a slot boundary. Additionally, the start point of the on-duration can be set at a slot-level granularity using another RRC parameter, drx-SlotOffset. In this case, the position of the on-duration can be relatively defined as the position obtained by applying a slot offset indicated by drx-SlotOffset from the reference point indicated by drx-LongCycleStartOffset. In other words, the start point of the on-duration can be determined after the slot offset indicated by drx-SlotOffset from the reference point indicated by drx-LongCycleStartOffset.

[0199] When a UE is configured to wake up via C-DRX only during the active duration to monitor the presence of PDCCH (or DCI) sent to the UE, the UE can save energy compared to continuously monitoring the PDCCH (e.g., in every time slot). Furthermore, when the BS has no data to transmit during the upcoming active duration of the UE, the BS can send a WUS to the UE before the start of the active duration to inform the UE that it does not need to wake up (i.e., it does not need to start the onDurationTimer). In this case, the UE's battery can be further saved. In UEs configured with C-DRX, the BS can send a WUS (which can be sent in DCI format 2_6) to the UE at the WUS timing configured before the active duration, indicating that the UE does not need to wake up during that active duration. Upon receiving the WUS indication (or DCI format 2_6), the UE can remain in sleep mode without transitioning to active mode. In this case, a larger ES (Energy Optimization) can be implemented for the UE.

[0200] Similar to C-DRX configuration for a UE, cell DTX / DRX configuration can include parameters such as periodicity, time slot / offset, and on-duration. Cell DTX and cell DRX configurations can be configured and activated / deactivated independently. That is, cell DTX can be configured without cell DRX configuration, or cell DTX can be activated only. Conversely, cell DRX can be configured without cell DTX configuration, or cell DTX can be activated only without cell DRX configuration. In other words, even if both cell DTX and cell DRX are configured, only one of them can be activated. Similar to C-DRX for a UE, cell DTX / DRX operation has a structure including an active period (on-duration) and an inactive period. During the active period, all signals and channels are transmitted / received without restriction, and during the inactive period, the transmission / reception of all signals and channels is disabled. Alternatively, during the inactive period, specific signals and channels can be transmitted / received only to a limited extent. For example, during time periods other than active periods (e.g., inactive periods), only PDCCH transmission or reception of specific signals (such as RACH / SR PUCCH) may be permitted. Cell DTX / DRX configuration can be configured and activated solely via RRC signaling. Alternatively, all or some parameters related to cell DTX / DRX configuration may be configured by RRC, and cell DTX / DRX configuration may be activated via L1 signaling (e.g., group common DCI) (such as PDCCH / DCI). During the active period of cell DTX / DRX, all signals and channels may be transmitted / received without special restrictions, as is the case in normal BS operation. Time periods other than active periods (or inactive periods) can be essentially considered inactive periods. In this case, transmission / reception of signals / channels other than predetermined signals / channels may be restricted during inactive periods. Minimal transmission / reception during such inactive periods can provide ES gain to the BS, and such cell DTX / DTX operation can be considered as operation for a NES state / mode set to on.

[0201] In addition to periodically repeating the pre-configured cell DTX / DRX configuration for a specific on / off duration pattern, the BS can also configure cell shutdown, which completely shuts down a specific cell for a specific time to save more energy. When a cell is shut down, a UE connected to the deactivated cell cannot send or receive data at all. Therefore, the BS needs to move the UE to another activated cell. Specifically, when the target cell for cell shutdown is the PCell of a specific UE, the BS can trigger a handover procedure for the UE to change the PCell. The triggering of the handover procedure can be dynamically indicated via L1 (UE-specific or group-common) signaling. For this purpose, using the DCI format to activate / deactivate the cell DTX / DRX configuration may be beneficial in terms of signaling overhead, because the BS can dynamically indicate cell shutdown to multiple UEs in the cell in a group-common manner. Furthermore, since the DCI format includes an information block for each serving cell, a handover procedure for a specific UE's PCell can be triggered by adding a cell shutdown indication bit to the information block for the PCell.

[0202] In this regard, Conditional Handover (CHO) is a method in which the UE autonomously executes / triggers a handover procedure even if the BS does not directly instruct the UE to handover (HO) when pre-configured conditions are met. The source cell evaluates whether at least one HO condition (RSRP / RSRQ of the reference signal, SINR, etc.) is met for the UE configured with CHO, and when at least one of the HO conditions is met, the UE can execute the HO procedure of sending RACH to the target cell.

[0203] In the following text, when it is said that the BS is operating in NES mode for the ES, this can refer to the following operation: the BS is pre-configured to shut down the transmission of a specific DL signal for a specific period of time (the BS's DTX period), and dynamically indicates one of the multiple shutdown periods. The DL signal in a shutdown period may not be transmitted within a predefined time period. Furthermore, it can refer to power-saving operations of the BS and UE not only in the time domain but also in the frequency domain and / or spatial domain. Power-saving operations in the frequency domain can refer to BWP handover, dynamic RB adaptation, etc., and power-saving operations in the spatial domain can refer to semi-statically or dynamically shutting down a specific receive antenna port of the BS, thereby stopping the BS from transmitting / receiving signals through the shut antenna port.

[0204] In this way, the BS can indicate the activation / deactivation of CHO triggers and / or cell DTX / DRX configurations for cell shutdown via DCI format 2_9, which is a DCI format defined for the activation / deactivation of CHO triggers and / or cell DTX / DRX configurations for cell shutdown.

[0205] The DCI format 2_9 for the activation / deactivation definition of the CHO trigger for cell shutdown and / or cell DTX / DRX configuration can be configured / defined as follows.

[0206] Specifically, the UE can receive information about the cell DTX configuration and / or cell DRX configuration for the serving cell via higher-level signaling such as RRC signaling. In this case, the UE can be dynamically instructed to activate or deactivate the cell DTX / DRX configuration in a group common manner via DCI format 2_9 (or the UE can be configured to activate or deactivate the cell DTX / DRX configuration via higher-level signaling such as RRC signaling). Since the UE can have multiple serving cells, DCI format 2_9 can include multiple information blocks corresponding to the respective serving cells. Each information block can be configured to include at least one bit for activating or deactivating the cell DTX configuration and one bit for activating or deactivating the cell DRX configuration for the corresponding serving cell. When the UE is configured to monitor DCI format 2_9 in the Type 3 Common Search Space (CSS), the UE can pre-configure the position of the information block it should monitor within DCI format 2_9 via RRC parameters (e.g., position-inDCI-NES).

[0207] Furthermore, the bit width of each information block in DCI format 2_9 can vary depending on the presence or absence of cell DTX / DRX configuration. For example, an information block corresponding to a serving cell configured with only cell DTX configuration or cell DRX configuration may include 1 bit, and an information block corresponding to a serving cell configured with both cell DTX configuration and cell DRX configuration may include 2 bits. Therefore, when a CHO trigger bit for cell shutdown of a specific serving cell is additionally included in the information block corresponding to that specific serving cell, the information block for that specific serving cell may include 1, 2, or N bits depending on the presence of cell DTX / DRX configuration (where N=1 if the CHO trigger bit is 1 bit). Alternatively, the CHO trigger bit may be set separately from the information block indicating the activation or deactivation of cell DTX / DRX configuration within DCI format 2_9 at a specific location (e.g., at the beginning or end of DCI format 2_9, or before / after a specific information block).

[0208] The BS can increase the ES gain for the BS and / or UE by using DCI format 2_9 as defined, to indicate CHO triggering for cell shutdown and / or activation / deactivation of cell DTX / DRX configuration. For example, from the BS's operational perspective, when the number of UEs accessing the cell is small or there is almost no data activity depending on cell conditions (e.g., late at night), it is necessary to increase the BS's ES gain through cell shutdown. In this case, the BS may need to trigger a CHO for the UE using DCI format 2_9.

[0209] However, the UE does not perform PDCCH monitoring during periods other than the active period to conserve power. Alternatively, a UE configured to monitor DCI format 2_6 may exceptionally perform monitoring for DCI format 2_6 with a ps offset before the start of the on-duration. In other words, a UE configured with UE C-DRX does not perform other PDCCH monitoring during periods other than the active period (e.g., the active period based on C-DRX configuration), except in the case of monitoring configured with DCI format 2_6. Therefore, even if DCI format 2_9 indicates cell DTX / DRX (de)activation and / or cell shutdown, the UE may only be able to receive it during the UE's on-duration (or active period).

[0210] In this scenario, when the BS intends to dynamically instruct cell shutdown during periods other than the active period, the BS must wait until the on-duty duration (or active period) of the UE configured with C-DRX is reached before sending DCI format 2_9. This can unnecessarily increase the latency of the HO procedure and / or the activation / deactivation latency of the cell DTX / DRX configuration. Furthermore, since the C-DRX configuration is specifically instructed / configured for the UE, the on-duty duration (or active period) can differ for each UE within the cell. In this case, depending on the conditions within the cell, it may be difficult to provide immediate CHO triggering and / or indication of activation / deactivation for the cell DTX / DRX configuration, potentially leading to cell power-off delays. Such delays in cell power-off can significantly reduce the BS / UE ES gain.

[0211] Therefore, under certain circumstances, even during inactive periods, the UE needs to monitor DCI format 2_9, and the following methods 1 and 2 can be considered as methods for monitoring DCI format 2_9 during inactive periods.

[0212] The active period defined below can be the union of the operating time of the timer (inactivityTimer and / or the timer for retransmission) configured for DRX and a predefined period of the on-duration. For example, when receiving a PDCCH during the on-duration, a UE configured with UE C-DRX can activate the inactivityTimer. The UE can wait to receive a transmit / receive schedule from the BS until the inactivity timer expires. Additionally, the UE can maintain an active state for retransmission even when the timer for retransmission is operating. Therefore, the active period associated with UE C-DRX operation can be the union of the periods in each time slot during which PDCCH monitoring is performed (such as the operating time of the aforementioned specific timer and / or the predefined on-duration). That is, the following description is given with the understanding that the active period (or the active period associated with UE C-DRX configuration) is a period of time that may be expected to be scheduled due to the operation of the aforementioned timers and / or the predefined on-duration.

[0213] 1. Method 1

[0214] Method 1 can be a method for determining whether to perform monitoring for DCI format 2_9 during C-DRX inactive periods (the remaining time periods excluding active periods) based on the configuration scheme of DCI format 2_9.

[0215] As a method for performing monitoring of DCI format 2_9 based on the configuration scheme of DCI format 2_9, the following methods 1-1, 1-2 and 1-3 can be considered.

[0216] (1) Method 1-1: When the CHO trigger bit is configured to be included in DCI format 2_9, a method for monitoring DCI format 2_9 is performed during the C-DRX inactivity period.

[0217] When the CHO trigger bit is configured to be included in DCI format 2_9, the UE can perform monitoring for DCI format 2_9 even during periods of UE C-DRX inactivity. The CHO trigger bit can be configured to be included in DCI format 2_9 under at least one of the following conditions.

[0218] - ① The case where the RRC parameter of the indication information block in DCI format 2_9 is further included to indicate the start bit position for CHO triggering (in other words, the case where the RRC parameter of the indication / notification information block in DCI format 2_9 is further configured to indicate the (start) position (which notifies the bit position for CHO triggering).

[0219] - ② The case where the bit width of the additional information block is configured in the RRC parameter of the indicator information block at the starting bit position within DCI format 2_9.

[0220] - ③ The case where configuration information for the CHO trigger bit is provided through a separate RRC parameter.

[0221] In other words, when a field / bit for the CHO trigger bit is defined / configured in DCI format 2_9 via RRC signaling, the UE can perform monitoring for DCI format 2_9 at at least one monitoring opportunity (MO) configured for DCI format 2_9, even during inactive periods.

[0222] (2) Method 1-2: A method to skip monitoring for DCI format 2_9 during all or part of the UE’s C-DRX inactivity period when the CHO trigger bit is not configured to be included in DCI format 2_9.

[0223] When the CHO trigger bit is not configured to be included in DCI format 2_9, the UE can skip monitoring for DCI format 2_9 during the UE's C-DRX inactivity period.

[0224] Alternatively, when the CHO trigger bit is not configured to be included in DCI format 2_9, the UE may perform limited monitoring of DCI format 2_9 only during certain inactive periods. For example, the UE may perform monitoring of DCI format 2_9 during the aforementioned UE C-DRX active periods and certain inactive periods. For example, the UE may monitor DCI format 2_9 only in MOs located in odd or even time slots among all MOs (configured for DCI format 2_9) associated with inactive periods. Alternatively, the UE may monitor DCI format 2_9 only once every N times (where N is a parameter previously configured / indicated by the BS) among all MOs associated with inactive periods. For example, when the CHO trigger bit is not configured to be included in DCI format 2_9, even if the MO corresponds to an inactive period, the UE may exceptionally perform monitoring of DCI format 2_9 in MOs located in odd or even time slots or the Nth time slot among all MOs configured for DCI format 2_9.

[0225] (3) Method 1-3: The BS configures whether to monitor DCI format 2_9 during the UE C-DRX inactive period based on the presence or absence of the CHO trigger bit.

[0226] The UE can be individually configured by the BS to monitor DCI format 2_9 during UE C-DRX inactivity periods based on whether the CHO trigger bit is configured to be included in DCI format 2_9. For example, when the CHO trigger bit is configured to be included in DCI format 2_9, the BS can instruct / configure the UE to perform monitoring for DCI format 2_9 during UE C-DRX inactivity periods. Alternatively, when the CHO trigger bit is configured to be included in DCI format 2_9, the BS can instruct / configure the UE not to perform monitoring for DCI format 2_9 during UE C-DRX inactivity periods. Alternatively, when the CHO trigger bit is not configured to be included in DCI format 2_9, the BS can instruct / configure the UE to perform monitoring for DCI format 2_9 during UE C-DRX inactivity periods. Alternatively, when the CHO trigger bit is not configured to be included in DCI format 2_9, the BS may instruct / configure the UE not to perform monitoring for DCI format 2_9 during UE C-DRX inactivity periods.

[0227] (4) Method 1-4: The monitoring period of DCI format 2_9 used for CHO triggering and the monitoring period of DCI format 2_9 used for cell DTX / DRX are set to always be the same or set separately.

[0228] For example, the content of DCI format 2_9 may include the CHO trigger bit + (de)activation bit in a specific MO of DCI format 2_9 and the (de)activation bit only in other MOs.

[0229] Specifically, the monitoring periodicity can be set separately for DCI format 2_9 including the CHO trigger bit and DCI format 2_9 excluding the CHO trigger bit. For example, the UE can be configured to always have the same monitoring periodicity for DCI format 2_9 for CHO triggering and DCI format 2_9 for cell DTX / DRX, regardless of the inclusion of the CHO trigger bit. Alternatively, the monitoring periodicity of DCI format 2_9 including the CHO trigger bit can be set to an integer multiple (or odd / even time slots) of the monitoring periodicity of DCI format 2_9 for cell DTX / DRX. For example, the UE can be configured to monitor DCI format 2_9 including the cell DTX / DRX (de)activation bit + CHO trigger bit only in odd time slots across all MOs for DCI format 2_9, and monitor DCI format 2_9 including only the cell DTX / DRX (de)activation bit in the remaining MOs.

[0230] (5) Method 1-5: When CHO is triggered, maintain cell DTX / DRX in the previous active / deactivated state (do not read the remaining bits in DCI format 2_9), and when CHO is not triggered, activate (deactivate) cell DTX / DRX configuration according to cell DTX / DRX indication for each information block included in DCI format 2_9.

[0231] Typically, when a CHO is triggered via DCI format 2_9, the cell DTX / DRX can remain in its previous active / deactivated state (without reading bits from DCI format 2_9). For example, when the UE recognizes that a CHO has been triggered via DCI format 2_9, it can keep the active cell active and the deactivated cell deactivated without decoding the remaining bits of DCI format 2_9. When a CHO is not triggered, the UE can activate / deactivate the cell DTX / DRX according to the cell DTX / DRX activation or deactivation indication in each information block within DCI format 2_9.

[0232] 2. Method 2

[0233] Method 2 relates to a method for performing monitoring for DCI format 2_9 based on a wake-up indicator or wake-up indication of DCI format 2_6. For example, the UE can determine whether to perform monitoring for DCI format 2_9 during inactive periods based on the monitoring results of DCI format 2_6.

[0234] DCI format 2_6 uses power-saving RNTI (PS-RNTI) scrambling, and the starting position of the block to be read (monitored) by each UE in DCI format 2_6 can be determined / configured by the parameter ps-PositionDCI-2-6. The block for each UE can include a wake-up indication field and a Scell ​​sleep indication field. When the 1-bit wake-up indication in the wake-up indication field is 0, the timer for the next (long) DRX cycle (i.e., drx-onDurationTimer) is not started, and when the 1-bit wake-up indication in the wake-up indication field is 1, the timer for the next (long) DRX cycle can be started. The UE can monitor scheduling information from the BS while the timer is running. The Scell ​​sleep indication can be configured as a bitmap, and the size of the bitmap can be determined according to the DormancyGroupID configuration.

[0235] Furthermore, DCI format 2_6 can be transmitted (received from the UE's perspective) only during periods other than the UE's active periods (i.e., C-DRX inactive periods), and the size of DCI format 2_6 can be determined by the parameter (RRC parameter) sizeDCI-2-6. Additionally, for UEs configured to monitor DCI format 2_6, default behaviors can be configured for cases where DCI format 2_6 is not detected or not monitored. For example, "wake-up" or "sleep" operations can be set as the default behavior for the UE.

[0236] As described above, a UE configured with UE C-DRX can perform PDCCH monitoring in each time slot only during a period based on a pre-configured on duration for power saving and a period based on a retransmission / inactivity timer (i.e., the active period). Exceptionally, a UE can only perform PDCCH monitoring (i.e., monitor DCI format 2_6) in periods other than the active period (or the inactive period) if it is configured to monitor DCI format 2_6, and monitoring of the remaining DCI formats, including DCI format 2_9, can only be performed during the active period. Therefore, the BS's cell DTX / DRX (de)activation indication and CHO trigger indication can only be transmitted / received within a limited time period.

[0237] From a BS operation perspective, when the number of UEs connected to the cell is small or there is almost no data activity depending on cell conditions (e.g., late at night), it is necessary to increase the BS's ES gain through cell DTX / DRX activation and / or cell shutdown. That is, the BS may need to trigger cell DTX / DRX activation and / or CHO for the UE via DCI format 2_9. However, when the BS aims to dynamically indicate cell shutdown and / or cell DTX / DRX activation during periods other than active periods, the BS should wait until the on-duration (or active period) of the UE configured with UE C-DRX before sending DCI format 2_9. Therefore, this may unnecessarily increase the delay of HO and / or cell DTX / DRX activation. Furthermore, since UE C-DRX configuration is UE-specific, the on-duration (or active period) may differ for each UE within the cell. In this case, the BS may be unable to provide immediate CHO trigger indication based on the situation within the cell, potentially leading to a delay in BS power-off and a significant reduction in the BS / UE ES gain.

[0238] Therefore, to conserve UE and / or BS energy, the UE may need to perform monitoring for DCI format 2_9 exceptionally, even during inactive periods, based on monitoring results for DCI format 2_6. For example, when DCI format 2_6 is not detected / monitored, the UE can determine whether to perform monitoring for DCI format 2_9 during C-DRX inactive periods by combining the wake-up indication field or default behavior of DCI format 2_6. In this case, flexible monitoring can be configured / determined by considering the trade-off between BS and UE power savings and immediate cell DTX / DRX and / or CHO trigger indications.

[0239] In this regard, at least one of the following methods may be considered.

[0240] (1) Method 2-1: based on wake-up monitoring DCI format 2_9 indicated by the detected / received DCI format 2_6.

[0241] When the wake-up indication (or wake-up indicator) included in the detected / received DCI format 2_6 indicates "wake-up (i.e., start of drx-onDurationTimer)", the UE can perform monitoring for DCI format 2_9 during the on-duration duration and the C-DRX inactivity period associated with the on-duration duration.

[0242] For example, when the wake-up indication in the monitored DCI format 2_6 indicates "wake-up", the UE can be configured to perform monitoring for DCI format 2_9 during both the on-duration and associated UE C-DRX inactivity periods. In other words, when the bit value of the wake-up indication field in DCI format 2_6 indicates "wake-up" (i.e., when the bit value 1 indicating the start of drx-onDurationTimer is set), the UE performs monitoring for other PDCCHs, including DCI format 2_9, during the subsequent on-duration (i.e., the on-duration indicating wake-up), and the MO can be configured to allow the UE to exceptionally perform monitoring for DCI format 2_9 during all (or part) of the UEC-DRX inactivity period (from the end of the on-duration indicating wake-up until the next (periodic) on-duration). For example, upon receiving a DCI in DCI format 2_6 (or a PDCCH including DCI) with a bit value of 1 indicating the start of drx-onDurationTimer, the UE can perform monitoring for DCI format 2_9 at the MO configured for DCI format 2_9 during the operation time of drx-onDurationTimer (on-duration or active period) and the inactive period (after drx-onDurationTimer expires and before the next on-duration).

[0243] (2) Method 2-2: Based on the detected / received DCI format 2_6 indication "enter sleep", skip monitoring of DCI format 2_9.

[0244] Conversely, when the wake-up indication included in the received / detected DCI format 2_6 indicates "entering sleep" (or a bit value of 0 indicating that drx-onDurationTimer is not started), the UE can skip monitoring of DCI format 2_9 during the on-duration duration indicating entering sleep and the UE C-DRX inactivity period associated with that on-duration duration.

[0245] (3) Method 2-3: Based on the detected / received DCI format 2_6 indication "enter sleep", perform limited monitoring of DCI format 2_9.

[0246] In method 2-3, the UE may exceptionally perform monitoring for DCI format 2_9 during the on-duration period when the wake-up indication has indicated "enter sleep".

[0247] Specifically, when the wake-up indication for DCI format 2_6 indicates "enter sleep," the UE can remain in sleep mode for the subsequent on-duration period (i.e., the on-duration period during which the wake-up indication indicates "enter sleep" or the on-duration period during which it is "off") without performing PDCCH monitoring for the remaining DCI formats (excluding DCI format 2_9). In other words, the UE can perform monitoring for DCI format 2_9 only during the on-duration period when the wake-up indication indicates "off." However, the UE can skip monitoring for DCI format 2_9 during the C-DRX inactivity period associated with the "off" on-duration period.

[0248] Alternatively, it is possible to configure whether to perform monitoring for DCI format 2_9 separately when the wake-up indication of DCI format 2_6 indicates "enter sleep". For example, even if the wake-up indication of DCI format 2_6 indicates "enter sleep", the BS can configure the UE to perform monitoring for DCI format 2_9 during the associated UE C-DRX inactivity period.

[0249] Alternatively, configuration information can be provided in advance regarding whether to perform monitoring for DCI format 2_9 during the entire "off" on-duration (within the wake-up indication "off" via DCI format 2_6) and its associated UE C-DRX inactivity period (or in each of the on-duration and inactivity periods).

[0250] (4) Method 2-4: Determine whether to perform monitoring for DCI format 2_9 based on the length of the UE C-DRX cycle or inactive period.

[0251] The UE can determine whether to perform monitoring for DCI format 2_9 based on the length of the UE C-DRX cycle or inactive period (e.g., short / long DRX cycle).

[0252] Specifically, the UE can determine whether to perform monitoring for DCI format 2_9 during UE C-DRX inactivity periods based on the length of the UE C-DRX cycle or inactivity period. For example, a UE configured with a short DRX cycle may not perform monitoring at the MO of DCI format 2_9 configured for inactivity periods because the length from one on-duration duration to the next (periodic) on-duration duration is short. Conversely, when the length of the inactivity period is relatively long due to the lack of a short DRX cycle configured for the UE (e.g., a long DRX cycle), the UE may perform monitoring at the MO of DCI format 2_9 configured for inactivity periods. Alternatively, considering the UE's energy-saving aspects, the UE may not perform monitoring at the MO of DCI format 2_9 configured for inactivity periods when a long DRX cycle is configured, and may only perform monitoring at the MO of DCI format 2_9 configured for inactivity periods when a short DRX cycle is configured.

[0253] Alternatively, the decision to perform monitoring for DCI format 2_9 during inactive periods can be determined based on the DRX cycle period of the UE's C-DRX. For example, if a specific threshold is preset, and the UE's C-DRX cycle is greater than (greater than, equal to, or exceeding) the specific threshold, the UE can perform monitoring for DCI format 2_9 during inactive periods. Conversely, if the UE's C-DRX cycle is less than (less than, equal to, or lower than) the specific threshold, the UE can skip monitoring for DCI format 2_9 during inactive periods. Alternatively, considering UE energy efficiency, if a specific threshold is preset and the UE's C-DRX cycle is less than (less than, equal to, or lower than) the specific threshold, the UE can perform monitoring for DCI format 2_9 during inactive periods. Conversely, if the UE's C-DRX cycle is greater than (greater than, equal to, or exceeding) the specific threshold, the UE can skip monitoring for DCI format 2_9 during inactive periods.

[0254] (5) Method 2-5: When DCI format 2_6 is not detected / received, determine whether to monitor DCI format 2_9 based on the default behavior.

[0255] The UE can determine whether to monitor DCI format 2_9 based on at least one of the aforementioned methods (method 2-1, method 2-2, method 2-3 and method 2-4) by combining the default behavior configured for the case where DCI format 2_6 is not received / detected.

[0256] Specifically, for energy saving, the BS does not always transmit DCI (e.g., DCI format 2_6) at every MO configured for DCI format 2_6. Therefore, a default behavior can be configured regarding whether the UE should "wake up" or "go to sleep" when DCI format 2_6 is not detected. In this case, the UE can determine whether to monitor DCI format 2_9 by applying at least one of the aforementioned methods (method 2-1, method 2-2, method 2-3, and method 2-4) based on the default behavior configured for not receiving / detecting DCI format 2_6.

[0257] For example, when the default behavior is configured as "go to sleep" and no DCI format 2_6 is detected / discovered / received, method 2-2 and / or method 2-3 can be applied based on the go to sleep default behavior. Alternatively, when the default behavior is configured as "wake up" and no DCI format 2_6 is detected / discovered / received, method 2-1 can be applied based on the wake up default behavior.

[0258] Figure 11 This is a diagram illustrating a method for monitoring a second DCI by a UE.

[0259] As described above, even during an RRC connection with the BS, the UE can perform DRX-related operations based on the C-DRX configuration. The UE can transition to wake-up or sleep mode based on active periods (or C-DRX active periods) and inactive periods (or C-DRX inactive periods) according to the C-DRX configuration. For example, the UE can determine the active period based on the on-duration of the drx-StartOffset and drx-SlotOffset configurations included in the configuration information, as well as DRX-related timers (onDurationTimer, drx-InactivityTimer, shortDRX-CycleTimer, etc.), and determine the remaining periods in the DRX cycle other than the active periods as inactive periods. In the following text, DCI reception / monitoring can correspond to the reception / monitoring of the PDCCH including DCI.

[0260] Specifically, refer to Figure 11 The UE can receive C-DRX configuration information from the BS (S111). See reference... Figure 7 The configuration information described may include parameters such as on-duration, onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimer, longDRX-Cycle, drxStartOffset, drxShortCycleTimer, shortDRX-Cycle, and drx-SlotOffset.

[0261] A UE configured with C-DRX can detect / monitor a first DCI including a wake-up indication field (S113). The first DCI can be a DCI format 2_6 including wake-up indication information, which indicates whether the UE should wake up or sleep during an active period based on configuration information. For example, when a first bit value associated with wake-up (e.g., 1) is included in the wake-up indication field / information, the UE can start onDurationTimer and perform monitoring for all PDCCHs including the DCI during onDurationTimer operation. As mentioned above, the first DCI is a DCI that can be exceptionally sent during inactive periods, and the UE can detect / monitor whether the first DCI is received at a predefined timeout (e.g., an MO configured to monitor the first DCI) during an inactive period.

[0262] Subsequently, the UE can determine, based on the detection result of the first DCI, whether to monitor the second DCI related to cell DRX / DTX during the inactive period configured by the configuration information (S115). For example, a UE configured with C-DRX can combine the monitoring / detection result of the first DCI to determine whether to monitor the second DCI configured for activation / deactivation for cell DRX / DTX (e.g., DCI format 2_9). That is, in order to minimize the delay of energy-saving operations for the BS and / or UE, the UE can exceptionally monitor the second DCI under certain circumstances, even during inactive periods. For example, as in method 2, the UE can determine whether to exceptionally monitor the second DCI during inactive periods based on the monitoring result of the first DCI. Alternatively, as in method 1 above, the UE can determine whether to exceptionally monitor the second DCI during inactive periods based on whether the CHO trigger bit is configured to be included for the second DCI.

[0263] Specifically, when a first DCI, including indication information indicating wake-up, is detected during a specific on-duration period (i.e., the on-duration period of a DRX cycle that begins after the first DCI is detected), the UE performs monitoring for the second DCI during an inactive period associated with the specific on-duration period (the remaining period in the DRX cycle excluding the specific on-duration period indicated by the first DCI, or the period from the end of the specific on-duration period to the beginning of the specific on-duration period of the next cycle).

[0264] For example, when a first DCI including wake-up indication information with bit values ​​associated with wake-up is detected, the UE can initiate an onDurationTimer and transition to the wake-up state. In this case, the UE can perform monitoring for the second DCI even during the inactive period from the expiration of the onDurationTimer until the start of the next cycle's on duration. That is, the UE can perform monitoring for the second DCI during both the active period indicated by the first DCI and the corresponding inactive period.

[0265] As described above, the on-time duration associated with the monitoring of the second DCI and its corresponding / associated inactivity period refer to the on-time duration and remaining period of the DRX cycle that begins after the monitoring of the first DCI (e.g., the remaining period of the DRX cycle excluding the on-time duration). The following description is given under the understanding that the on-time duration refers to the on-time duration of the DRX cycle that begins after the time point at which the monitoring of the first DCI is performed.

[0266] Specifically, when a first DCI including indication information indicating sleep is detected during the on-duration period, the UE can skip monitoring of the second DCI during the inactivity period associated with the on-duration period. For example, when a first DCI including wake-up indication information with sleep-related bit values ​​is detected, the UE can maintain a sleep state during the on-duration period without activating onDurationTimer. In this case, the UE can skip monitoring of the second DCI not only during the on-duration period but also during the associated inactivity period. Alternatively, the UE can perform monitoring of the second DCI only during the on-duration period and skip monitoring of the second DCI during the inactivity period associated with the on-duration period.

[0267] Alternatively, the UE may fail to detect the first DCI. In this case, as described above, the UE can determine whether to monitor the PDCCH including the DCI during the on-duration period based on a preset default behavior. For example, when wake-up is set as the default behavior for the UE, the UE can wake up during the on-duration period to monitor the PDCCH if the first DCI is not detected. In this case, monitoring of the second DCI can be performed exceptionally even during inactive periods associated with the on-duration period. Conversely, when sleep is set as the default behavior for the UE, the UE sleeps during the on-duration period in which the first DCI is not detected and can skip monitoring of the second DCI during inactive periods associated with the on-duration period indicating sleep (or the "off" on-duration period).

[0268] Figure 12This diagram illustrates a method for the BS to send a second DCI to the UE.

[0269] Reference Figure 12 The BS can send C-DRX configuration information to the UE (S121). See reference... Figure 7 The configuration information described may include parameters such as on-duration, onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimer, longDRX-Cycle, drxStartOffset, drxShortCycleTimer, shortDRX-Cycle, and drx-SlotOffset.

[0270] Then, the BS can determine whether to send the second DCI during the inactive period configured for the UE based on whether the first DCI has been sent (S123). Alternatively, as in method 1 described above, the BS can determine whether to exceptionally send the second DCI during the inactive period based on whether the CHO trigger bit is configured to be included in the second DCI.

[0271] For example, when the BS has already sent a first DCI to the UE, the BS can determine whether to send a second DCI during an inactive period associated with the on-time duration indicated by the first DCI, based on the wake-up indication information included in the first DCI. For example, when sending a first DCI including wake-up indication bit values, the BS can send the second DCI to the UE even during the associated inactive period. Alternatively, when the BS has already sent a first DCI including wake-up indication bit values ​​indicating sleep to the UE, the BS may choose not to send the second DCI during the inactive period. Alternatively, the BS may exceptionally send the second DCI only during the on-time duration indicating sleep.

[0272] Alternatively, when the BS has not yet sent the first DCI to the UE, it can determine whether to send the second DCI during inactivity periods based on the default behavior configured for the UE. For example, when wake-up is set as the default behavior for the UE, the BS can send the second DCI during inactivity periods. Conversely, when sleep is set as the default behavior for the UE, the BS can skip the transmission of the second DCI during inactivity periods.

[0273] In this way, the proposed disclosure can minimize the latency caused by the UE's C-DRX operation when applying cell DRX / DTX. Alternatively, the proposed disclosure can minimize the latency caused by the UE's C-DRX operation when performing cell DRX operation by exceptionally allowing the UE to monitor DCI format 2_9 during inactive periods. Alternatively, the proposed disclosure can flexibly schedule whether to send DCI format 2_9 during inactive periods based on DCI format 2_6.

[0274] Example of a communication system using this disclosure

[0275] Although not limited thereto, the various descriptions, functions, processes, proposals, methods and / or operation flowcharts disclosed in this document can be applied to various fields requiring wireless communication / connectivity (5G) between devices.

[0276] In the following description, it will be illustrated in more detail with reference to the accompanying drawings. In the following drawings / description, unless otherwise specified, the same reference numerals may refer to the same or corresponding hardware blocks, software blocks, or functional blocks.

[0277] Figure 13 An example of a communication system applied to this disclosure is shown.

[0278] Reference Figure 13The communication system 1 applied to this disclosure includes wireless devices, base stations (BS), and networks. Herein, a wireless device refers to a device that performs communication using a radio access technology (RAT) (e.g., 5G New RAT (NR) or Long Term Evolution (LTE)) and may be referred to as a communication / radio / 5G device. Wireless devices may include (but are not limited to) robots 100a, vehicles 100b-1 and 100b-2, extended reality (XR) devices 100c, handheld devices 100d, home appliances 100e, Internet of Things (IoT) devices 100f, and artificial intelligence (AI) devices / servers 400. For example, a vehicle may include a vehicle with wireless communication capabilities, an autonomous vehicle, and a vehicle capable of performing communication between vehicles. Herein, a vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). XR devices can include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices, and can be implemented in the form of head-mounted displays (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Handheld devices can include smartphones, smart tablets, wearable devices (e.g., smartwatches or smart glasses) and computers (e.g., laptops). Home appliances can include TVs, refrigerators, and washing machines. IoT devices can include sensors and smart meters. For example, the BS and network can be implemented as wireless devices, and a particular wireless device 200a can operate as a BS / network node relative to other wireless devices.

[0279] Wireless devices 100a to 100f can connect to network 300 via BS 200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can connect to AI server 400 via network 300. Network 300 can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although wireless devices 100a to 100f can communicate with each other via BS 200 / network 300, wireless devices 100a to 100f can also perform direct communication (e.g., sidelink communication) without going through the BS / network. For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0280] Wireless communication / connections 150a, 150b, or 150c can be established between wireless devices 100a to 100f / BS 200 or between BS 200 and BS 200. In this document, wireless communication / connections can be established via various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication), or inter-BS communication (e.g., relay, integrated access backhaul (IAB)). Wireless devices and BS / wireless devices can transmit / receive radio signals to / from each other via wireless communication / connections 150a and 150b. For example, wireless communication / connections 150a and 150b can transmit / receive signals via various physical channels. For this purpose, at least a portion of the configuration information for configuring the process of transmitting / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes can be performed based on various proposals of this disclosure.

[0281] Examples of wireless devices using this disclosure

[0282] Figure 14 Wireless devices applicable to this disclosure are illustrated.

[0283] Reference Figure 14 The first wireless device 100 and the second wireless device 200 can transmit radio signals via various RATs (e.g., LTE and NR). In this document, {first wireless device 100 and second wireless device 200} can correspond to... Figure 13 {Wireless Device 100x and BS 200} and / or {Wireless Device 100x and Wireless Device 100x}.

[0284] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and additionally include one or more transceivers 106 and / or one or more antennas 108. The processors 102 may control the memories 104 and / or the transceivers 106, and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor 102 may process information in the memory 104 to generate a first information / signal, and then transmit a radio signal including the first information / signal via the transceivers 106. The processor 102 may receive a radio signal including a second information / signal via the transceivers 106, and then store the information obtained by processing the second information / signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various information relating to the operation of the processor 102. For example, the memory 104 may store software code including commands for performing some or all of the processes controlled by the processor 102 or for performing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. In this document, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 106 may be connected to processor 102 and transmit and / or receive radio signals via one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used interchangeably with radio frequency (RF) units. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0285] Specifically, the first wireless device or UE 100 may include a processor 102 connected to the transceiver 106 and a memory 104. The memory 104 may include components for performing and referencing... Figures 10 to 12 At least one program related to the operations described in the implementation method.

[0286] The processor 102 can control the transceiver 106 to receive configuration information for C-DRX from the BS, detect a first DCI including wake-up indication information, and determine, based on the result of detecting the first DCI, whether to monitor a second DCI related to cell DRX or cell DTX during an inactive period configured by the configuration information.

[0287] Alternatively, a processing means for controlling the UE may be configured, the processing means including a processor 102 and a memory 104. In this case, the processing means may include at least one processor and at least one memory connected to the at least one processor and storing instructions that, based on execution by the at least one processor, cause the UE to: receive configuration information for C-DRX from the BS; detect a first DCI including wake-up indication information; and, based on the result of detecting the first DCI, determine whether to monitor a second DCI related to cell DRX or cell DTX during an inactive period configured by the configuration information.

[0288] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and additionally include one or more transceivers 206 and / or one or more antennas 208. The processors 202 may control the memories 204 and / or the transceivers 206, and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processors 202 may process information in the memories 204 to generate a third information / signal, and then transmit a radio signal including the third information / signal via the transceivers 206. The processors 202 may receive a radio signal including a fourth information / signal via the transceivers 206, and then store the information obtained by processing the fourth information / signal in the memories 204. The memories 204 may be connected to the processors 202 and may store various information relating to the operation of the processors 202. For example, the memories 204 may store software code including commands for performing some or all of the processes controlled by the processors 202 or for performing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. In this document, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 206 may be connected to processor 202 and transmit and / or receive radio signals via one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. Transceiver 206 may be used interchangeably with an RF unit. In this disclosure, a wireless device may represent a communication modem / circuit / chip.

[0289] Specifically, the second wireless device or BS 200 may include a processor 2102 and a memory 204 connected to the transceiver or RF transceiver 206. The memory 204 may include components for performing and referencing... Figures 10 to 12 At least one program related to the operations described in the implementation method.

[0290] The processor 202 can control the transceiver 206 to send configuration information for C-DRX to the UE, and determine whether to send a second DCI related to cell DRX or cell DTX during an inactive period configured for the UE by the configuration information based on whether a first DCI including wake-up indication information is sent.

[0291] The hardware elements of wireless devices 100 and 200 will be described in more detail below. One or more protocol layers may be implemented by (but are not limited to) one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). One or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information, according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document, and provide the generated signals to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive signals (e.g., baseband signals) and acquire PDUs, SDUs, messages, control information, data, or information from one or more transceivers 106 and 206, according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document.

[0292] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field-programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 to be driven by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document can be implemented using firmware or software in the form of code, commands, and / or command sets.

[0293] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories 104 and 204 may be configured with read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard disk drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104 and 204 may be located internally and / or externally to one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0294] One or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels mentioned in the methods and / or operation flowcharts of this document to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and transmit and receive radio signals. For example, one or more processors 102 and 202 may perform control to enable one or more transceivers 106 and 206 to transmit user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 may perform control to enable one or more transceivers 106 and 206 to receive user data, control information, or radio signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document through one or more antennas 108 and 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert received radio signals / channels, etc., from RF band signals to baseband signals so that the received user data, control information, radio signals / channels, etc., may be processed using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc., processed using one or more processors 102 and 202 from baseband signals to RF band signals. For this purpose, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0295] Examples of wireless devices using this disclosure

[0296] Figure 15 Another example of a wireless device applied to this disclosure is shown. The wireless device can be implemented in various forms depending on the use case / service (see reference). Figure 13 ).

[0297] Reference Figure 15 Wireless devices 100 and 200 can correspond to Figure 14The wireless devices 100 and 200 can be configured from various elements, components, units / parts, and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and an additional component 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include... Figure 14 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, transceiver 114 may include Figure 14 The device comprises one or more transceivers 106 and 206 and / or one or more antennas 108 and 208. Control unit 120 is electrically connected to communication unit 110, memory 130, and add-on components 140, and controls the overall operation of the wireless device. For example, control unit 120 may control the electrical / mechanical operation of the wireless device based on programs / code / commands / information stored in memory unit 130. Control unit 120 may transmit information stored in memory unit 130 to an external source (e.g., other communication devices) via communication unit 110 through a wireless / wired interface, or store information received from an external source (e.g., other communication devices) via communication unit 110 in memory unit 130 via a wireless / wired interface.

[0298] The additional component 140 can be configured differently depending on the type of wireless device. For example, the additional component 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device can be configured according to (but is not limited to) a robot ( Figure 13 100a), vehicles ( Figure 13 100b-1 and 100b-2), XR device ( Figure 13 100c), handheld device ( Figure 13 100d), home appliances ( Figure 13 100e), IoT devices ( Figure 13 100f), digital broadcasting terminals, holographic devices, public safety devices, MTC devices, medical devices, fintech devices (or financial devices), security devices, climate / environment devices, AI servers / devices ( Figure 13 400), BS ( Figure 13 This can be achieved through 200 network nodes, etc. Wireless devices can be used in mobile or fixed locations depending on the use case / service.

[0299] exist Figure 15In wireless devices 100 and 200, various elements, components, units / parts, and / or modules may be interconnected entirely via wired interfaces, or at least a portion thereof may be wirelessly connected via communication unit 110. For example, in each of wireless devices 100 and 200, control unit 120 and communication unit 110 may be wired connected, and control unit 120 and first units (e.g., 130 and 140) may be wirelessly connected via communication unit 110. The various elements, components, units / parts, and / or modules within wireless devices 100 and 200 may also include one or more elements. For example, control unit 120 may be configured as a collection of one or more processors. As an example, control unit 120 may be configured as a collection of communication control processors, application processors, electronic control units (ECUs), graphics processing units, and memory control processors. In another example, memory 130 may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), flash memory, volatile memory, non-volatile memory, and / or combinations thereof.

[0300] Examples of vehicles or autonomous vehicles using this disclosure

[0301] Figure 16 The illustration shows a vehicle or autonomous vehicle applicable to this disclosure. The vehicle or autonomous vehicle may be a mobile robot, car, train, manned / unmanned aerial vehicle (AV), vessel, etc.

[0302] Reference Figure 16 The vehicle or autonomous vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 may be configured as part of the communication unit 110. Blocks 110 / 130 / 140a to 140d respectively correspond to... Figure 15 Blocks 110 / 130 / 140.

[0303] Communication unit 110 can send and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and roadside units), and servers. Control unit 120 can perform various operations by controlling the components of the vehicle or autonomous vehicle 100. Control unit 120 may include electronic control unit (ECU). Additionally, drive unit 140a enables the vehicle or autonomous vehicle 100 to move on a road. Drive unit 140a may include an engine, motor, powertrain, wheels, brakes, steering mechanism, etc. Power supply unit 140b supplies power to the vehicle or autonomous vehicle 100 and includes wired / wireless charging circuitry, battery, etc. Sensor unit 140c can acquire vehicle status, surrounding environment information, user information, etc. Sensor unit 140c may include inertial measurement unit (IMU) sensors, collision sensors, wheel sensors, speed sensors, slope sensors, weight sensors, heading sensors, position modules, vehicle forward / reverse sensors, battery sensors, fuel sensors, tire sensors, steering sensors, temperature sensors, depth sensors, ultrasonic sensors, lighting sensors, pedal position sensors, etc. Autonomous driving unit 140d can implement technologies for maintaining the vehicle within its lane, technologies for automatically adjusting speed (e.g., adaptive cruise control), technologies for autonomously driving along a determined path, and technologies for automatically setting a route if a destination is set, etc.

[0304] For example, communication unit 110 can receive map data, traffic information data, etc., from an external server. Autonomous driving unit 140d can generate an autonomous driving path and driving plan from the acquired data. Control unit 120 can control drive unit 140a, enabling the vehicle or autonomous vehicle 100 to move along the autonomous driving path according to the driving plan (e.g., speed / direction control). During autonomous driving, communication unit 110 can periodically or non-periodically acquire recent traffic information data from an external server and acquire surrounding traffic information data from neighboring vehicles. During autonomous driving, sensor unit 140c can acquire vehicle status and / or surrounding environment information. Autonomous driving unit 140d can update the autonomous driving path and driving plan based on newly acquired data / information. Communication unit 110 can transmit information about vehicle location, autonomous driving path, and / or driving plan to an external server. The external server can predict traffic information data using AI technology, etc., based on information collected from the vehicle or autonomous vehicle, and provide the predicted traffic information data to the vehicle or autonomous vehicle.

[0305] Here, the wireless communication technologies implemented in the wireless devices (XXX, YYY) of this specification may include, in addition to narrowband IoT for low-power communication, LTE, NR, and 6G. For example, NB-IoT technology may be an example of low-power wide-area network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the aforementioned names. Alternatively, the wireless communication technologies implemented in the wireless devices (XXX, YYY) of this specification may perform communication based on LTE-M technology. In this case, as an example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced machine-type communication). For example, LTE-M technology may be implemented according to at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE machine-type communication, and / or 7) LTE M, and is not limited to the aforementioned names. Alternatively, considering low-power communication, the wireless communication technology implemented in the wireless devices (XXX, YYY) of this specification is at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN), and is not limited to the aforementioned names. As an example, ZigBee technology can be used to generate personal area networks (PANs) related to low / low power digital communication based on various standards such as IEEE 802.15.4, and can be referred to by various names.

[0306] The above embodiments are implementations in which the components and features of this disclosure are combined in a predetermined form. Unless otherwise expressly stated, each component or feature should be considered optional. Each component or feature may be implemented without being combined with other components or features. Additionally, embodiments of this disclosure may be constructed by combining some components and / or features. The order of operations described in the embodiments of this disclosure may be changed. Some configurations or features of one embodiment may be included in other embodiments, or may be replaced by corresponding configurations or features of other embodiments. Clearly, embodiments may be constructed by combining claims that are not expressly referenced in the claims, or may be included as new claims by amendments made after filing.

[0307] In this document, the embodiments of the present disclosure are described primarily based on the signal transmission / reception relationship between the terminal and the base station. Such a transmission / reception relationship is extended in the same / similar manner to signal transmission / reception between the terminal and a repeater or between the base station and a repeater. In some cases, specific operations described in this document as being performed by the base station can be performed by its upstream nodes. That is, obviously, various operations performed by the base station or by network nodes other than the base station for communicating with the terminal in a network including multiple network nodes containing the base station can be performed. The base station can be replaced by terms such as fixed station, node B, eNode B (eNB), access point, etc. Additionally, the terminal can be replaced by terms such as user equipment (UE), mobile station (MS), mobile subscriber station (MSS).

[0308] In the hardware configuration, the embodiments of this disclosure can be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

[0309] In firmware or software configuration, the methods according to embodiments of this disclosure can be implemented in the form of modules, processes, functions, etc. Software code can be stored in a storage unit and executed by a processor. The memory is located inside or outside the processor and can send data to and receive data from the processor via various known means.

[0310] As described above, a detailed description of preferred embodiments of this disclosure has been provided to enable those skilled in the art to implement and perform this disclosure. Although reference has been made to preferred embodiments of this disclosure, those skilled in the art will understand that various modifications and alterations can be made to this disclosure within its scope.

[0311] Industrial applicability

[0312] The embodiments described above are applicable to various mobile communication systems.

Claims

1. A method comprising the following steps: Receive configuration information for Connected Discontinuous Reception (C-DRX) from the base station (BS); The detection includes the first downlink control information (DCI) containing wake-up indication information. as well as Based on the result of detecting the first DCI, determine whether to monitor the second DCI related to cell DRX or cell discontinuous transmission (DTX) during the inactive period configured by the configuration information.

2. The method according to claim 1, wherein, Based on the fact that the first DCI was not detected, a wake-up operation was performed as a preset default operation, and the monitoring of the second DCI was performed during the inactive period.

3. The method according to claim 1, wherein, Since the first DCI is not detected, a sleep operation is performed as a preset default operation, and the monitoring of the second DCI is not performed during the inactive period.

4. The method according to claim 1, wherein, Based on the detection of the first DCI, which includes wake-up indication information with bit values ​​associated with wake-up, the monitoring of the second DCI is performed during the inactivity period.

5. The method according to claim 1, wherein, Based on the detection of the first DCI, which includes wake-up indication information with sleep-related bit values, the monitoring of the second DCI is not performed during the inactivity period.

6. The method according to claim 5, wherein, The monitoring of the second DCI is performed only during the duration of sleep initiation indicated by the first DCI.

7. The method according to claim 1, wherein, The wake-up indication information includes a first bit value or a second bit value, wherein the first bit value indicates the start of drx-onDurationTimer for the next DRX cycle, and the second bit value indicates that the drx-onDurationTimer for the next DRX cycle has not been started.

8. The method according to claim 1, wherein, The second DCI format also includes a CHO trigger bit indicating whether a conditional switch (CHO) is triggered.

9. The method according to claim 1, wherein, The first DCI is in DCI format 2_6, and the second DCI is in DCI format 2_9.

10. A computer-readable recording medium that records a program for performing the method according to claim 1.

11. A user equipment (UE), the UE comprising: Radio frequency (RF) transceivers; as well as The processor is connected to the RF transceiver. The processor controls the RF transceiver to receive configuration information for Connected Mode Discontinuous Reception (C-DRX) from the base station (BS), detects first downlink control information (DCI) including wake-up indication information, and determines, based on the result of detecting the first DCI, whether to monitor a second DCI related to cell DRX or cell discontinuous transmission (DTX) during an inactive period configured by the configuration information.

12. The UE according to claim 11, wherein, Based on the fact that the first DCI was not detected, a wake-up operation was performed as a preset default operation, and the monitoring of the second DCI was performed during the inactive period.

13. The UE according to claim 11, wherein, Since the first DCI is not detected, a sleep operation is performed as a preset default operation, and the monitoring of the second DCI is not performed during the inactive period.

14. A processing apparatus for controlling a user equipment (UE), the processing apparatus comprising: At least one processor; as well as At least one memory, connected to the at least one processor and storing instructions, the instructions being executed by the at least one processor to cause the UE to: Receive configuration information for Connected Discontinuous Reception (C-DRX) from the base station (BS); The detection includes the first downlink control information (DCI) containing wake-up indication information; and Based on the result of detecting the first DCI, determine whether to monitor the second DCI related to cell DRX or cell discontinuous transmission (DTX) during the inactive period configured by the configuration information.

15. A method comprising the following steps: Send configuration information for Connected Mode Discontinuous Reception (C-DRX) to the User Equipment (UE); as well as Based on whether a first downlink control information (DCI) including wake-up indication information is sent, it is determined whether a second DCI related to cell DRX or cell discontinuous transmission (DTX) is sent during an inactive period configured for the UE by the configuration information.

Images