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

Abstract

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

Description

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

[0001] This specification relates to a wireless communication system, and more specifically, to a method and device for transmitting and receiving wireless signals.

[0002] Wireless communication systems are widely deployed to provide various types of communication services, such as voice and data. Typically, wireless communication systems are multiple access systems that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power). 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] As more and more communication devices demand ever-increasing communication traffic, the need for next-generation 5G systems, which offer enhanced wireless broadband communication capabilities over existing LTE systems, is growing. This next-generation 5G system, known as NewRAT, differentiates communication scenarios into Enhanced Mobile Broadband (eMBB), Ultra-reliability and low-latency communication (URLLC), and Massive Machine-Type Communications (mMTC).

[0004] Here, eMBB is a next-generation mobile communication scenario with characteristics such as High Spectrum Efficiency, High User Experienced Data Rate, and High Peak Data Rate; URLLC is a next-generation mobile communication scenario with characteristics such as Ultra Reliable, Ultra Low Latency, and Ultra High Availability (e.g., V2X, Emergency Service, and Remote Control); and mMTC is a next-generation mobile communication scenario with characteristics such as Low Cost, Low Energy, Short Packet, and Massive Connectivity (e.g., IoT).

[0005] The technical problem to be achieved by the present invention is to provide a more accurate and efficient signal transmission and reception method and a device therefor.

[0006] The technical challenges are not limited to the technical challenges mentioned above, and other technical challenges not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0007] A method for a terminal to receive a signal according to one aspect may include the steps of: receiving configuration information for C-DRX (Connected mode Discontinuous Reception) from a base station; detecting first downlink control information (DCI) including wake-up indication information; and determining, based on a detection result of the first DCI, whether to monitor second DCI related to cell DRX or cell Discontinuous Transmission (DTX) during an inactive time interval set through the configuration information.

[0008] Alternatively, based on the wake-up operation being performed as a preset default operation by non-detection of the first DCI, the monitoring of the second DCI is characterized in that it is performed in the inactive period.

[0009] Alternatively, based on the sleep operation being performed as a preset default operation by non-detection of the first DCI, monitoring of the second DCI is characterized in that it is not performed in the inactive period.

[0010] Alternatively, based on the detection of the first DCI including the wake-up indication information having a bit value related to wake-up, the monitoring of the second DCI is characterized in that it is performed in the inactive period.

[0011] Alternatively, based on the detection of the first DCI including the wake-up indication information having a bit value associated with sleep, the monitoring of the second DCI is characterized in that it is not performed in the inactive period.

[0012] Alternatively, the monitoring of the second DCI is characterized in that it is performed only for the onDuration section in which sleep is indicated by the first DCI.

[0013] Alternatively, the wake-up indication information is characterized by including a first bit value indicating the start of drx-onDurationTimer for the next DRX cycle or a second bit value indicating that drx-onDurationTimer for the next DRX cycle is not started.

[0014] Alternatively, the second DCI format is characterized by further including a Conditional Handover (CHO) triggering bit indicating whether to trigger a CHO.

[0015] Alternatively, the first DCI is characterized in that it is DCI format 2_6, and the second DCI is DCI format 2_9.

[0016] A recording medium storing programs for performing the method of receiving the above-described signal according to another aspect may be provided.

[0017] A terminal performing the method of receiving the above-described signal according to another aspect may be provided.

[0018] A processing device may be provided for controlling a terminal that performs the method of receiving the above-described signal according to another aspect.

[0019] According to another aspect, the method of transmitting a signal by the above-described base station may include the steps of transmitting configuration information for C-DRX (Connected mode Discontinuous Reception) to a terminal; and determining, based on whether to transmit first downlink control information (DCI) including wake-up indication information, whether to transmit second downlink control information (DCI) related to cell DRX or cell Discontinuous Transmission (DTX) in an inactive time interval set for the terminal through the configuration information.

[0020] According to various embodiments, signals can be transmitted or received more accurately and efficiently in a wireless communication system.

[0021] Alternatively, power usage of the network and / or terminals in a wireless communication system can be more efficiently controlled.

[0022] The effects that can be obtained in various embodiments are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0023] The drawings attached to this specification are intended to provide an understanding of the present invention, illustrate various embodiments of the present invention, and together with the description of the specification serve to explain the principles of the present invention.

[0024] Figure 1 is a drawing for explaining physical channels used in a 3GPP NR system and a general signal transmission method using them.

[0025] Figure 2 illustrates the structure of a radio frame.

[0026] Figure 3 illustrates a resource grid of slots.

[0027] Figure 4 illustrates an example of physical channels being mapped within a slot.

[0028] FIG. 5 and FIG. 6 are diagrams for explaining Idle Mode DRX (Discontinuous Reception) operation.

[0029] FIGS. 7 to 9 are diagrams for explaining DRX operation in RRC (Radio Resource Control) connected mode.

[0030] Figure 10 is a diagram for explaining a method of monitoring DCI format 2_6.

[0031] Figure 11 is a diagram for explaining a method for a terminal to perform monitoring of a second DCI.

[0032] Figure 12 is a diagram for explaining a method for a base station to transmit a second DCI to a terminal.

[0033] Figures 13 to 16 illustrate a communication system (1) and a wireless device applicable to the present invention.

[0034] The following technologies can be used in various wireless access systems, such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with radio technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented with radio technologies such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented with radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is a part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (long term evolution) is part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A.

[0035] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing RAT (Radio Access Technology) is emerging. Furthermore, massive MTC (Machine Type Communications), which connects multiple devices and objects to provide various services anytime, anywhere, is also a key issue to be considered in next-generation communication. Furthermore, communication system design that considers reliability and latency-sensitive services / terminals is being discussed. Accordingly, the introduction of next-generation RATs that consider enhanced Mobile BroadBand Communication (eMBB), massive MTC, and Ultra-Reliable and Low Latency Communication (URLLC) is being discussed. In one embodiment of the present invention, for convenience, the corresponding technology is referred to as NR (New Radio or New RAT).

[0036] The term 'base station' used in this specification may be replaced with terms such as fixed station, Node B, gNode B (gNB), Access Point (AP), cell, or transmission and reception point (TRP). The term 'relay node' may be replaced with terms such as Relay Node (RN) or Relay Station. In addition, the term 'terminal' may be replaced with terms such as User Equipment (UE), Mobile Station (MS), Mobile Subscriber Station (MSS), or Subscriber Station (SS).

[0037] For clarity of explanation, the description will focus on 3GPP NR, but the technical idea of ​​the present invention is not limited thereto.

[0038] The following documents may be referenced for background information, definitions of terms, abbreviations, etc. related to the present invention (Incorporated by Reference).

[0039] - 38.211: Physical channels and modulation

[0040] - 38.212: Multiplexing and channel coding

[0041] - 38.213: Physical layer procedures for control

[0042] - 38.214: Physical layer procedures for data

[0043] - 38.215: Physical layer measurements

[0044] - 38.300: NR and NG-RAN Overall Description

[0045] - 38.304: User Equipment (UE) procedures in idle mode and in RRC Inactive state

[0046] - 38.321Medium Access Control (MAC) protocol specification

[0047] - 38.331: Radio Resource Control (RRC) protocol specification

[0048] - 37.213: Introduction of channel access procedures to unlicensed spectrum for NR-based access

[0049] - 36.355: LTE Positioning Protocol

[0050] - 37.355: LTE Positioning Protocol

[0051] 용어 및 약어

[0052] - 5GC: 5G Core Network

[0053] - 5GS: 5G System

[0054] - NES: network energy saving

[0055] - ES: energy saving

[0056] - SSB: synchronization signal / PBCH block

[0057] - FR: frequency range

[0058] - CC: component carrier

[0059] - NCGI : NR Cell Global Identifier

[0060] - SI: system information

[0061] - PCell: primary cell

[0062] - SCell: secondary cell

[0063] - PDCCH: Physical Downlink Control CHannel

[0064] - PDSCH: Physical Downlink Shared CHannel

[0065] - PUSCH: Physical Uplink Shared CHannel

[0066] - CSI: Channel state information

[0067] - RRM: Radio resource management

[0068] - SCS: Sub-carrier spacing

[0069] - RLM: Radio link monitoring

[0070] - DCI: Downlink Control Information

[0071] - CAP: Channel Access Procedure

[0072] - Ucell: Unlicensed cell

[0073] - TBS: Transport Block Size

[0074] - TDRA: Time Domain Resource Allocation

[0075] - SLIV: Starting and Length Indicator Value (This is an indicator value for the starting symbol index and number of symbols within the slot of the PDSCH and / or PUSCH, and can be set as a component of the entry that constitutes the TDRA field within the PDCCH that schedules the corresponding PDSCH and / or PUSCH.)

[0076] - BWP: BandWidth Part (can be composed of consecutive resource blocks (RBs) on the frequency axis and can correspond to one numerology (e.g., sub-carrier spacing, CP length, slot / mini-slot duration). In addition, multiple BWPs can be configured on one carrier (the number of BWPs per carrier can also be limited), but the number of activated BWPs can be limited to a part of it (e.g., 1) per carrier.)

[0077] - CORESET: COntrol REsourse SET (refers to the time-frequency resource area where PDCCH can be transmitted, and the number of CORESETs per BWP may be limited.)

[0078] - REG: Resource element group

[0079] - SFI: Slot Format Indicator (An indicator indicating the symbol level DL / UL direction within a specific slot(s), transmitted through the group common PDCCH.)

[0080] - COT: Channel occupancy time

[0081] - SPS: Semi-persistent scheduling

[0082] - QCL: Quasi-Co-Location (QCL relationship between two reference signals means 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 antenna port(s) of the corresponding RS). In the NR system, four QCL types are defined as follows. 'typeA': {Doppler shift, Doppler spread, average delay, delay spread}, 'typeB': {Doppler shift, Doppler spread}, 'typeC': {Doppler shift, average delay}, 'typeD': {Spatial Rx parameter} For any DL RS antenna port(s), the first DL RS is set as a reference for QCL type X (X=A, B, C, or D), and additionally, the second DL RS is set as a reference for QCL type Y (Y=A, B, C, or D but X≠Y) ) can be set as a reference to

[0083] - TCI: Transmission Configuration Indication (A TCI state includes the QCL relationship between one or more DL RSs, such as DM-RS ports of the PDSCH, the DM-RS port of PDCCH, or the CSI-RS port(s) of a CSI-RS resource. For the 'Transmission Configuration Indication' field in the DCI that schedules the PDSCH, the TCI state index corresponding to each code point that constitutes the field is activated by the MAC CE, and the TCI state setting for each TCI state index is set through RRC signaling. In the Rel-16 NR system, the TCI state is set between DL RSs, but in future releases, setting between DL RS and UL RS or UL RS and UL RS may be allowed. Examples of UL RSs include SRS, PUSCH DM-RS, and PUCCH DM-RS.)

[0084] - SRI: SRS resource indicator (Indicates one of the SRS resource index values ​​set in the 'SRS resource indicator' among the fields in the DCI that schedules the PUSCH. When transmitting a PUSCH, the UE can transmit the PUSCH using the same spatial domain transmission filter used for transmitting and receiving the reference signal linked to the corresponding SRS resource. At this time, the reference RS is set by RRC signaling through the SRS-SpatialRelationInfo parameter for each SRS resource, and SS / PBCH block, CSI-RS, or SRS can be set as the reference RS.)

[0085] - TRP: Transmission and Reception Point

[0086] In a wireless communication system, a terminal receives information from a base station via the downlink (DL) and transmits it to the base station via the uplink (UL). The information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type and purpose of the information being transmitted and received.

[0087] Figure 1 is a drawing for explaining physical channels used in a 3GPP NR system and a general signal transmission method using them.

[0088] When a terminal is powered on again from a powered-off state or enters a new cell, it performs an initial cell search operation, such as synchronizing with the base station, in step S101. To this end, the terminal receives a Synchronization Signal Block (SSB) from the base station. The SSB includes a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). The terminal synchronizes with the base station based on the PSS / SSS and obtains information such as a cell ID (cell identity). In addition, the terminal can obtain broadcast information within the cell based on the PBCH. Meanwhile, the terminal can check the downlink channel status by receiving a Downlink Reference Signal (DL RS) during the initial cell search phase.

[0089] After completing the initial cell search, the terminal can obtain more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on the physical downlink control channel information in step S102.

[0090] Thereafter, the terminal may perform a random access procedure such as steps S103 to S106 to complete connection to the base station. To this end, the terminal may transmit a preamble through a physical random access channel (PRACH) (S103) and receive a response message to the preamble through a physical downlink control channel and a corresponding physical downlink shared channel (S104). In the case of contention-based random access, a contention resolution procedure such as transmission of an additional physical random access channel (S105) and reception of a physical downlink control channel and a corresponding physical downlink shared channel (S106) may be performed.

[0091] The terminal that has performed the procedure as described above can then perform the general uplink / downlink signal transmission procedure, such as receiving a physical downlink control channel / physical downlink shared channel (S107) and transmitting a physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) (S108). The control information that the terminal transmits to the base station is collectively referred to as uplink control information (UCI). UCI includes HARQ ACK / NACK (Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK), SR (Scheduling Request), CSI (Channel State Information), etc. CSI includes CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indication), etc. UCI is generally transmitted through PUCCH, but can be transmitted through PUSCH when control information and traffic data must be transmitted simultaneously. Additionally, UCI can be transmitted aperiodically via PUSCH upon request / instruction from the network.

[0092] Figure 2 illustrates the structure of a radio frame. In NR, uplink and downlink transmissions are organized into frames. Each radio frame is 10 ms long and is divided into two 5 ms half-frames (HF). Each half-frame is divided into five 1 ms sub-frames (SF). A sub-frame is divided into one or more slots, and the number of slots within a sub-frame depends on the subcarrier spacing (SCS). Each slot contains 12 or 14 OFDM (Orthogonal Frequency Division Multiplexing) symbols, depending on the cyclic prefix (CP). When a normal CP is used, each slot contains 14 OFDM symbols. When an extended CP is used, each slot contains 12 OFDM symbols.

[0093] Table 1 illustrates that when CP is normally used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS.

[0094] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 15KHz (u=0)1410130KHz (u=1)1420260KHz (u=2)14404120KHz (u=3)14808240KHz (u=4)1416016

[0095] * N slot symb : Number of symbols in the slot

[0096] * N frame,u slot : Number of slots in the frame

[0097] * N subframe,u slot : Number of slots in a subframe

[0098] Table 2 illustrates that when extended CP is used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS.

[0099] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 60KHz (u=2)12404

[0100] The structure of the frame is only an example, and the number of subframes, number of slots, and number of symbols in the frame can be varied.

[0101] In an NR system, OFDM numerology (e.g., SCS) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., SF, slot, or TTI) (conveniently referred to as TU (Time Unit)) consisting of the same number of symbols may be set differently between the merged cells. Here, the symbol may include an OFDM symbol (or CP-OFDM symbol), an SC-FDMA symbol (or Discrete Fourier Transform-spread-OFDM, DFT-s-OFDM symbol).

[0102] Figure 3 illustrates a resource grid of a slot. A slot includes multiple symbols in the time domain. For example, in the case of a regular CP, one slot includes 14 symbols, but in the case of an extended CP, one slot includes 12 symbols. A carrier includes multiple subcarriers in the frequency domain. A Resource Block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A Bandwidth Part (BWP) is defined as multiple consecutive Physical RBs (PRBs) in the frequency domain and can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication is performed through activated BWPs, and only one BWP can be activated for a single terminal. Each element in the resource grid is referred to as a Resource Element (RE), to which one complex symbol can be mapped.

[0103] Figure 4 illustrates an example of mapping physical channels within a slot. In an NR system, a frame is characterized by a self-contained structure in which a DL control channel, DL or UL data, and a UL control channel can all be included within a single slot. For example, the first N symbols within a slot can be used to transmit a DL control channel (e.g., PDCCH) (hereinafter, DL control region), and the last M symbols within a slot can be used to transmit a UL control channel (e.g., PUCCH) (hereinafter, UL control region). N and M are each integers greater than or equal to 0. A resource region (hereinafter, data region) between the DL control region and the UL control region can be used to transmit DL data (e.g., PDSCH) or UL data (e.g., PUSCH). GP provides a time gap when a base station and a terminal switch from a transmission mode to a reception mode or from a reception mode to a transmission mode. Some symbols at the time of switching from DL to UL within a subframe can be set as GP.

[0104] The PDCCH carries Downlink Control Information (DCI). For example, the PCCCH (i.e., DCI) carries the transmission format and resource allocation of the downlink shared channel (DL-SCH), resource allocation information for the uplink shared channel (UL-SCH), paging information for the paging channel (PCH), system information on the DL-SCH, resource allocation information for upper layer control messages such as random access responses transmitted on the PDSCH, transmission power control commands, activation / deactivation of Configured Scheduling (CS), etc. The DCI includes a cyclic redundancy check (CRC), which is masked / scrambled with various identifiers (e.g., Radio Network Temporary Identifier, RNTI) depending on the owner or usage of the PDCCH. For example, if the PDCCH is for a specific terminal, the CRC is masked with the terminal identifier (e.g., Cell-RNTI, C-RNTI). If the PDCCH is for paging, the CRC is masked with the Paging-RNTI (P-RNTI). If the PDCCH is for system information (e.g., a System Information Block, SIB), the CRC is masked with the System Information RNTI (SI-RNTI). If the PDCCH is for a random access response, the CRC is masked with the Random Access-RNTI (RA-RNTI).

[0105] For PDCCH reception, the UE may monitor (e.g., perform blind decoding) a set of PDCCH candidates in a CORESET. The PDCCH candidates represent the CCE(s) that the UE monitors for PDCCH reception / detection. PDCCH monitoring may be performed in one or more CORESETs on an active DL BWP on each activated cell in which PDCCH monitoring is configured. The set of PDCCH candidates that the UE monitors is defined as a PDCCH Search Space (SS) set. The SS set may be a Common Search Space (CSS) set or a UE-specific Search Space (USS) set.

[0106] Table 3 illustrates the PDCCH search space.

[0107] Search SpaceTypeRNTIUse CaseType0-PDCCHCommonSI-RNTI on a primary cellBroadcast of System InformationType0A-PDCCHCommonSI-RNTI on a primary cellBroadcast of System InformationType1-PDCCHCommonRA-RNTI or TC-RNTI on a primary cellMsg2, Msg4 in RACHType2-PDCCHCommonP-RNTI on a primary cellPagingSystem Information change notificationType3-PDCCHCommonINT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, C-RNTI, MCS-C-RNTI or CS-RNTIGroup signalingUE SpecificC-RNTI, MCS-C-RNTI or CS-RNTIUE signaling (eg, PDSCH / PUSCH)

[0108] SS sets can be configured via system information (e.g., MIB) or UE-specific higher layer (e.g., RRC) signaling. Each DL BWP of a serving cell can have up to S (e.g., 10) SS sets configured. 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.

[0109] - searchSpaceId: Indicates the ID of the SS set.

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

[0111] - monitoringSlotPeriodicityAndOffset: Indicates the PDCCH monitoring period period (in slot units) and the PDCCH monitoring period offset (in slot units).

[0112] - monitoringSymbolsWithinSlot: Indicates the first OFDMA symbol(s) for PDCCH monitoring within the slot where PDCCH monitoring is configured. It is indicated through a bitmap, and each bit corresponds to each OFDMA symbol within the slot. The MSB of the bitmap corresponds to the first OFDM symbol within the slot. The OFDMA symbol(s) corresponding to the bit(s) with a bit value of 1 corresponds to the first symbol(s) of the CORESET within the slot.

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

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

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

[0116] Based on the CORESET / SS set configuration, a UE can monitor PDCCH candidates in one or more SS sets within a slot. An opportunity (e.g., time / frequency resources) for monitoring PDCCH candidates is defined as a PDCCH (monitoring) opportunity. One or more PDCCH (monitoring) opportunities can be configured within a slot.

[0117] PUCCH formatLength in OFDM symbolsNumber of bitsUsageEtc01 - 2≤2HARQ, SRSequence selection14 - 14≤2HARQ, [SR]Sequence modulation21 - 2>2HARQ, CSI, [SR]CP-OFDM34 - 14>2HARQ, CSI, [SR]DFT-s-OFDM(no UE multiplexing)44 - 14>2HARQ, CSI, [SR]DFT-s-OFDM(Pre DFT OCC)

[0118] 1) PUCCH Format 0 (PF0)

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

[0120] - Number of OFDM symbols constituting a single PUCCH: 1 to X symbols (e.g., X = 2)

[0121] - Transmission structure: Consists of only UCI signals without DM-RS, and transmits the UCI status by selecting and transmitting one of multiple sequences.

[0122] 2) PUCCH Format 1 (PF1)

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

[0124] - Number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0125] Transmission Structure: DM-RS and UCI are configured in TDM format on different OFDM symbols, with UCI multiplying a specific sequence with modulation (e.g., QPSK) symbols. Cyclic Shift (CS) / Orthogonal Cover Code (OCC) is applied to both UCI and DM-RS to support CDM between multiple PUCCH resources (following PUCCH Format 1) (within the same RB).

[0126] 3) PUCCH Format 2 (PF2)

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

[0128] - Number of OFDM symbols constituting a single PUCCH: 1 to X symbols (e.g., X = 2)

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

[0130] 4) PUCCH Format 3 (PF3)

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

[0132] - Number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0133] Transmission structure: DMRS and UCI are configured / mapped to different symbols in TDM format, and transmitted by applying DFT to the corrupted UCI bits. OCC is applied to UCI at the DFT front end, and CS (or IFDM mapping) is applied to DMRS to support multiplexing to multiple terminals.

[0134] 5) PUCCH Format 4 (PF4)

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

[0136] - Number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

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

[0138] DRX (Discontinuous Reception) Operation

[0139] 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 DRX configuration information.

[0140] A UE operating based on DRX repeatedly turns ON / OFF its reception operation. For example, when DRX is configured, the UE attempts to receive / detect PDCCH (e.g., monitor PDCCH) only during a predetermined time interval (e.g., ON), and does not attempt PDCCH reception during the remaining time (e.g., OFF / Sleep).

[0141] At this time, the time that the terminal must attempt to receive the PDCCH is called On-duration, and On-duration is defined once per DRX cycle. The UE can receive DRX configuration information from a base station (e.g., gNB) through RRC signaling and perform DRX operation by receiving (Long) DRX command MAC CE.

[0142] Meanwhile, DRX configuration information can be included in MAC-CellGroupConfig. IE MAC-CellGroupConfig is used to configure MAC parameters for a cell group including DRX.

[0143] DRX (Discontinuous Reception) refers to an operation mode in which a UE (User Equipment) discontinuously receives / monitors a downlink channel to reduce battery consumption. In other words, a UE configured for DRX can reduce power consumption by discontinuously receiving downlink signals. DRX operation is performed in a DRX cycle, where On Duration represents a time interval that is periodically repeated. DRX includes On Duration and Sleep Duration (or Opportunity for DRX). On Duration represents a time interval during which the UE monitors the PDCCH 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 State and RRC_INACTIVE State, DRX is used to discontinuously receive a paging signal.

[0144] - RRC_Idle State: A state in which a wireless connection (RRC connection) is not established between the base station and the terminal.

[0145] - RRC Inactive State: A wireless connection (RRC connection) is established between the base station and the terminal, but the wireless connection is inactive.

[0146] - RRC_Connected state: A wireless connection (RRC connection) is established between the base station and the terminal.

[0147] DRX is basically divided into Idle mode DRX, Connected DRX (C-DRX), and Extended DRX. DRX applied in the RRC IDLE state is called IDLE mode DRX, and DRX applied in the RRC CONNECTED state is called Connected mode DRX (C-DRX).

[0148] eDRX (Extended / enhanced DRX) is a mechanism that can extend the cycle of IDLE mode DRX and C-DRX. Whether eDRX is allowed in IDLE mode DRX can be set based on system information (e.g., SIB1).

[0149] SIB1 may include an eDRX-Allowed parameter. The eDRX-Allowed parameter is a parameter indicating whether IDLE mode extended DRX is allowed.

[0150] (1) IDLE mode DRX

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

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

[0153] Hereinafter, 'PDCCH' may refer to MPDCCH, NPDCCH, and / or general PDCCH. Hereinafter, 'UE' may refer to MTC UE, BL (Bandwidth Reduced Low Complexity) / CE (Coverage Enhanced) UE, NB-IoT UE, RedCap (RedCap) UE, general UE, and / or IAB-MT (Mobile Termination).

[0154] FIG. 5 is a flowchart illustrating an example of a method for performing IDLE mode DRX operation.

[0155] The UE receives IDLE mode DRX configuration information from the base station through upper layer signaling (e.g., system information) (S110).

[0156] Additionally, the UE determines a Paging Frame (PF) and a Paging Occasion (PO) for monitoring the PDCCH in 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).

[0157] Additionally, the UE monitors the PDCCH in the PO of the determined PF (S130). Meanwhile, the UE monitors only one time interval (PO) per paging DRX cycle. For example, the time interval may be a slot or a subframe.

[0158] Additionally, if the UE receives a PDCCH (more precisely, a CRC of the PDCCH) scrambled by the P-RNTI during the On Duration (i.e., if paging is detected), the UE can transition to connected mode and transmit and receive data with the base station.

[0159] Figure 6 is a diagram showing an example of IDLE mode DRX operation.

[0160] Referring to Fig. 6, when there is traffic (data) directed to a UE in the RRC_Idle state (hereinafter referred to as 'Idle state'), paging occurs toward the UE.

[0161] Therefore, the UE wakes up every (paging) DRX cycle and monitors the PDCCH.

[0162] If paging is present, the UE transitions to the Connected state and receives data. Otherwise, the UE may enter sleep mode again.

[0163] (2) Connected mode DRX (C-DRX)

[0164] C-DRX is DRX applied in RRC Connected State. The DRX cycle of C-DRX can be configured as a short DRX cycle and / or a long DRX cycle. The short DRX cycle is optional.

[0165] When C-DRX is configured, the UE performs PDCCH monitoring during the On Duration. If a PDCCH is successfully detected during PDCCH monitoring, the UE operates (or runs) the Inactive Timer and remains in the Awake State. On the other hand, if no PDCCH is successfully detected during PDCCH monitoring, the UE enters the Sleep State after the On Duration ends.

[0166] When C-DRX is configured, PDCCH reception Occasions (e.g., slots having PDCCH search spaces / candidates) may be configured discontinuously based on the C-DRX configuration. On the other hand, when C-DRX is not configured, PDCCH reception Occasions (e.g., slots having PDCCH search spaces / candidates) may be configured continuously according to the PDCCH search space configuration. Meanwhile, PDCCH monitoring may be limited to a time interval set as a Measurement Gap regardless of the C-DRX configuration.

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

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

[0169] - on-duration: The period (duration) during which the UE waits to receive a PDCCH after waking up. If the UE successfully decodes the PDCCH, the UE stays awake and starts the drx-inactivity timer.

[0170] - onDurationTimer: The period (Duration) at which the DRX Cycle starts; for example, it can mean the time period that should be continuously monitored from the start of the DRX cycle, and can be expressed in ms.

[0171] - drx-InactivityTimer: Duration after the PDCCH Occasion corresponding to the PDCCH indicating a new UL or DL ​​transmission for the MAC entity; for example, it may be a time period in milliseconds after the UE decodes a PDCCH with scheduling information. That is, the duration during which the UE waits to successfully decode another PDCCH after the last PDCCH decoded. If no other PDCCH is detected within this period, the UE transitions to Sleep mode.

[0172] The UE restarts the drx-inactivity timer after successful decoding of the PDCCH for initial transmission only, not for retransmission.

[0173] - drx-RetransmissionTimer: For DL, the maximum duration until a DL retransmission is received; For UL, the maximum duration until an acknowledgment for a UL retransmission is received. For example, for UL, it is the number of slots for the BWP (Bandwidth part) in which the TB (Transport Block) to be retransmitted is transmitted, and for DL, it is the number of slots for the BWP (Bandwidth part) in which the TB (Transport Block) to be retransmitted is received.

[0174] - longDRX-Cycle: On Duration occurrence cycle (Period)

[0175] - drxStartOffset: Subframe number where the DRX cycle starts

[0176] - drxShortCycleTimer: The period (Duration) during which the UE must follow the short DRX cycle;

[0177] - shortDRX-Cycle: DRX Cycle that runs for the number of drxShortCycleTimer when Drx-InactivityTimer ends

[0178] - drx-SlotOffset: Delay before drx-onDurationTimer starts; can be expressed in ms, or in multiples of 1 / 32ms.

[0179] - Active Time: The total period (Duration) that the UE monitors the PDCCH, including (a) the “On-duration” of the DRX cycle, (b) the time that the UE performs continuous reception while the drx-inactivity timer has not expired, and (c) the time that the UE performs continuous reception while waiting for a retransmission opportunity.

[0180] More specifically, when the DRX Cycle is configured, the Active Time for the serving cell of the DRX group includes the following times:

[0181] - (a) drx-onDurationTimer or (b) drx-InactivityTimer configured for the DRX group. or

[0182] - (c) drx-RetransmissionTimerDL or drx-RetransmissionTimerUL for all serving cells in the DRX group. or

[0183] - (d) ra-ContentionResolutionTimer or msgB-ResponseWindow. or

[0184] - (e) a section in which a Scheduling Request is transmitted via PUCCH and is pending, or

[0185] - (f) If a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity is not received after successfully receiving a Random Access Response (RAR) for a random access preamble not selected by the MAC entity during contention-based random access.

[0186] Additionally, when DRX 'ON' is set through the DRX command of MAC CE (command element) (S320), the UE monitors the PDCCH during the ON Duration of the DRX cycle based on the DRX setting (S330).

[0187] Figure 8 is a diagram showing an example of C-DRX operation.

[0188] Referring to FIG. 8, when the UE receives scheduling information (e.g., DL Assignment or UL Grant) in the RRC_Connected State (hereinafter referred to as Connected State), the UE executes the DRX Inactivity Timer and the RRC Inactivity Timer.

[0189] DRX mode starts after the DRX Inactivity Timer expires. The UE wakes up from the DRX Cycle and monitors the PDCCH for a predetermined period of time (on duration timer).

[0190] In this case, when Short DRX is set, when the UE starts DRX mode, the UE first starts a Short DRX Cycle, and after the Short DRX Cycle ends, the UE starts a Long DRX Cycle. At this time, the Long DRX Cycle is a multiple of the Short DRX Cycle. That is, the UE wakes up more frequently in the Short DRX Cycle. After the RRC Inactivity Timer expires, the UE transitions to the Idle state and performs Idle mode DRX operation.

[0191] Figure 9 illustrates a DRX Cycle. The C-DRX operation was introduced to save power for the UE. If the UE does not receive a PDCCH within the on-duration defined for each DRX cycle, it enters sleep mode and does not perform transmission / reception until the next DRX cycle.

[0192] On the other hand, if the UE receives a PDCCH in On-duration, the Active time may be maintained (or increased) based on the operation of the inactivity timer, retransmission timer, etc. If no additional data is received within the Active time, the UE may perform a sleep operation until the next DRX operation.

[0193] In NR, a wake up signal (WUS) is introduced to obtain additional power saving gains from the existing C-DRX operation. The WUS may be used to indicate whether the UE should perform PDCCH monitoring during the on-duration of each DRX cycle (or multiple DRX cycles). If the UE does not detect a WUS in a designated or indicated WUS occasion, the UE may remain in sleep mode without performing PDCCH monitoring for one or more DRX cycles associated with the WUS.

[0194] (3) Wake Up Signal (DCI Format 2_6)

[0195] Figure 10 is a diagram for explaining a method of monitoring DCI format 2_6.

[0196] In the power saving technology of the Rel-16 NR system, when a DRX operation is performed, whether or not each DRX cycle wakes up can be notified to the terminal through DCI format 2_6.

[0197] Referring to Figure 10, the monitoring occasion for DCI format 2_6 can be determined by the ps-Offset indicated by the network and the Time Gap reported by the terminal. The Time Gap reported by the terminal can be interpreted as a preparation period required for operations after the terminal wakes up.

[0198] Referring to FIG. 10, the network can instruct the terminal to configure a search space (SS) set capable of monitoring DCI format 2_6. The SS set configuration can instruct the terminal to monitor DCI format 2_6 through consecutive slots of a duration length at intervals of a monitoring periodicity.

[0199] In the DRX configuration, the monitoring window for monitoring DCI format 2_6 is determined by the start point of the DRX cycle (e.g., the point where the on-duration timer starts) and the ps-Offset configured by the network. In addition, PDCCH monitoring may not be required in the Time Gap section reported by the UE. Finally, the SS Set monitoring occasion where the UE performs actual monitoring can be determined as the first Full Duration (i.e., Actual Monitoring Occasions in FIG. 10) within the monitoring window.

[0200] By detecting DCI format 2_6 in the monitoring window set based on ps-Offset, the base station can instruct the terminal whether to wake up or not in the next DRX cycle.

[0201] NES (network energy saving)

[0202] Energy conservation at base stations is a key consideration in wireless communication systems, including 3GPP, as it can contribute to building eco-friendly networks by reducing carbon emissions and reducing the operational expenditure (OPEX) of telecommunications operators. In particular, the introduction of 5G communications will require higher transmission rates, necessitating base stations to be equipped with more antennas and provide services over wider bandwidths and frequency bands. Consequently, recent studies have shown that base station energy costs have reached up to 20% of total OPEX. This heightened interest in base station energy conservation has led to the approval of a new study item, "Study on Network Energy Savings," in certain scenarios (e.g., 3GPP NR Release 18).

[0203] Specifically, in order to improve the energy saving capability of the base station from the perspective of transmission and reception, the following enhancement techniques are being considered.

[0204] - A method for more fine-tuning transmission and / or reception dynamically and / or semi-statically in one or more of the network energy-saving techniques in the time, frequency, space and power domains, and for achieving more efficient operation through potential UE assistance / feedback and potential UE assistance information.

[0205] Below, a method for monitoring PDCCH in a time period other than the active time (e.g., inactive time) when C-DRX (Connected-Mode Discontinuous Reception) is set for the terminal is described in detail.

[0206] PDCCH monitoring outside UE C-DRX active time

[0207] When a terminal initially connects to a base station and enters connected mode (or RRC connection state), it must continuously perform PDCCH monitoring to check if there is a transmission scheduled for it in each configured search space (SS). However, if there is not always a schedule for the UE, the terminal performs PDCCH monitoring operation unnecessarily every time. In this case, the battery of the terminal may be quickly consumed. Therefore, in order to save power of the terminal, the base station can set C-DRX (connected mode discontinuous reception), which sets a time period (ON duration) during which PDCCH monitoring should be performed and a time period (OFF duration) during which PDCCH monitoring does not need to be performed. From the base station's perspective, the C-DRX of the terminal can also help with ES (energy saving). For example, since the base station does not need to transmit the PDCCH for a specific terminal during the C-DRX OFF duration of the corresponding terminal, the resource of the PDCCH for the corresponding terminal can be used for other purposes or ES gain can be obtained through DTX / DRX. However, the terminal may be able to use / transmit signals without restrictions on pre-configured resources (e.g., SR, PUCCH, CG-PUSCH, etc.) as needed even during the OFF duration. In this regard, the base station must wait for reception of the terminal's UL signal, which may be transmitted at any time. In addition, since C-DRX is configured UE-specifically, the DRX cycle or ON / OFF duration may not be aligned for each terminal within a cell.In this case, if the ON duration of the terminals is configured in a TDM format, it may be difficult to expect ES gain since the base station cannot perform sleep or sleep operation for PDCCH transmission for each ON duration.

[0208] Therefore, the base station can save energy by turning off transmission / reception of specific signals / channels in inactive periods through Cell(-specific) DTX / DRX configuration where active and inactive periods are repeated periodically, similar to C-DRX for UE. In order for a terminal to transmit and receive data, it must be in RRC_connected mode by configuring a connection (or RRC connection) with the base station. If there is no activity of the terminal for a certain period of time, the base station can reduce the power consumption of the terminal by transitioning the terminal to RRC_IDLE state. The terminal may need to transition back to connected mode (or RRC connected mode) whenever transmission / reception is required. The latency of signal transmission and reception of the terminal may increase due to RRC signaling for such transition of the connected mode. Alternatively, if a terminal needs to frequently transmit small data, not only may the delay increase (e.g., delay due to additional RRC signaling) but also the signaling overhead may increase. To reduce the signaling overhead and delay (e.g., delay in transmitting and receiving signals at the terminal) at the base station due to such frequent RRC state changes, a new mode / state called RRC_INACTIVE has been introduced in NR. In the inactive mode, the RRC connection is suspended, allowing signal transmission / reception operations to be performed quickly and with less signaling overhead.

[0209] Hereinafter, when applying Cell DTX / DRX operation to UEs in idle and inactive modes as well as terminals in RRC connection mode, a method for setting parameters of Cell DTX / DRX configuration and an activation method, and a method for transmitting / receiving signals and channels affected by Cell DTX / DRX operation are described in detail.

[0210] (RRC) A terminal in connected mode / state can perform PDCCH monitoring at a periodic ON duration to check whether there is a DL / UL signal to transmit / receive. When a PDCCH is received, the terminal in connected mode can perform DL reception or UL transmission according to the instruction of the PDCCH. In case of transmission of a UL signal of the terminal, if there is data to be sent in the UL buffer regardless of C-DRX, the terminal can wake up from sleep mode and transmit SR (Scheduling Request). In case of a terminal in idle mode, the terminal can periodically monitor paging or a paging signal, and if it is not the target terminal of the paging signal, it can operate in idle mode DRX (I-DRX) in which it enters sleep mode again.

[0211] Here, the meaning of the terminal operating in sleep mode may mean “regardless of the active time determined by C-DRX” or “also in a period other than the active time determined by C-DRX.” For example, the terminal may be in sleep mode regardless of the active time and / or inactive time of the DRX. Meanwhile, in the C-DRX operation, a time period consisting of ON duration and OFF duration is repeated, which is called a DRX cycle. The length of the DRX cycle can be defined as from the start point of the ON duration to before the next ON duration, and the DRX cycle includes a Long DRX cycle and a Short DRX cycle. If the length of the DRX cycle becomes long, a PDSCH may be generated to be sent by the base station immediately after a specific ON duration of the terminal ends. In this case, the delay in transmitting the PDSCH may increase since the base station must wait until the next ON duration of the terminal. However, from the base station's perspective, since the terminal does not transmit P-CSI (or Periodic CSI) or SRS (Sounding Reference Signal) during the OFF duration, the base station can increase resource utilization in that it can allocate resources for P-CSI or SRS to other UEs, and the base station can also perform an operation to switch the terminal to an energy saving mode for power saving during the OFF duration.

[0212] Meanwhile, a Long DRX cycle and a short DRX cycle can be set simultaneously, and at this time, the Long DRX cycle must be set to an integer multiple of the short DRX cycle (the onDurationTimer values ​​are the same). In this case, the UE can operate in the Long DRX cycle if there is no data activity during the ON duration of the Long DRX cycle (e.g., if there is no PDCCH reception). Conversely, if there is data activity, the UE can operate in the short DRX cycle for as long as drx-ShortcycleTimer, and if there is no data activity during the ON duration of the short DRX cycle, the UE can switch back to the long DRX cycle and operate. At this time, the start of the ON duration in the Short DRX cycle can be determined based on the drx-StartOffset and drx-SlotOffet values, or based on the drx-StartOffset and drx-SlotOffet values, similar to the long cycle.

[0213] The base station can instruct the terminal to not operate in active mode until the end of the ON duration and to switch directly to DRX sleep mode through the DRX command MAC CE. That is, the base station can terminate the current active time for the terminal through the DRX command MAC CE and directly enter the DRX cycle (or DRX sleep mode). If only the long DRX cycle is configured for the terminal, the terminal can operate in the long DRX cycle. If the short DRX cycle is also configured for the terminal, the terminal can enter the short DRX cycle mode directly after receiving the DRX command MAC CE. Alternatively, if the base station instructs the Long DRX command MAC CE, the terminal can perform the long DRX cycle operation even if the short DRX cycle is configured.

[0214] In addition, the base station can control the starting point (or starting time) of the long DRX cycle through the RRC parameter drx-LongcycleStartOffset. At this time, the value of drx-LongcycleStartOffset is defined in ms units so that the long DRX cycle can start at the slot boundary. In addition, the starting point of the On duration can be set at slot level granularity through another RRC parameter drx-SlotOffset. In this case, the position of the On duration can be defined relatively to the position obtained by applying the slot offset indicated by drx-SlotOffset from the reference point indicated by drx-LongcycleStartOffset. In other words, the starting point of the On duration can be determined after the slot offset indicated by drx-SlotOffset from the reference point indicated by drx-LongcycleStartOffset.

[0215] If a terminal wakes up only during the On duration through the C-DRX configuration and monitors whether a PDCCH (or DCI) has been transmitted to itself, energy savings (ES) can be achieved compared to continuously (e.g., every slot) monitoring the PDCCH. In addition, if the base station has no data to transmit during the upcoming On duration of the terminal, the base station can transmit a WUS to the terminal before the On duration of the terminal starts to inform the terminal that there is no need to wake up during the On duration (i.e., there is no need to start the onduration timer). In this case, the battery of the terminal can be further saved. Here, the base station can transmit a WUS that can be transmitted in DCI format 2_6 at a WUS opportunity set before the On duration for terminals among those configured with C-DRX that have no data to transmit / receive during the upcoming On duration, thereby informing the terminal that there is no need to wake up during the current On duration. A terminal that has received the WUS indication (or DCI format 2_6) can continue to maintain the sleep mode without switching to the active mode. In this case, more ES can be achieved for the terminal.

[0216] Meanwhile, the Cell DTX / DRX configuration may include parameters such as periodicity, slot / offset, and On duration, similar to the C-DRX configuration of the UE. In addition, the Cell DTX configuration and the Cell DRX configuration may be configured independently of each other and may be activated / deactivated independently of each other. That is, only Cell DTX may be configured without the Cell DRX configuration, or only Cell DTX may be activated. Alternatively, conversely, only Cell DRX may be configured without the Cell DTX configuration, or only Cell DTX may be activated without the Cell DRX configuration. In other words, even if both Cell DTX and Cell DRX are configured, only one of the two settings may be activated. The Cell DTX / DRX operation may have an active time period (On duration) in which all signals and channels are transmitted and received without restriction, and an inactive time period in which all signals and channels are transmitted and received OFF, similar to the C-DRX of the UE. Alternatively, only transmission / reception of specific signals and channels may be performed in a restricted manner during the inactive time period. For example, only PDCCH transmission or reception of specific signals such as RACH / SR PUCCH may be allowed during a time period other than the active time period (e.g., the inactive time period). Cell DTX / DRX configuration may be configured and activated only by RRC signaling. Alternatively, all / part of the parameters related to Cell DTX / DRX configuration may be configured by RRC, and Cell DTX / DRX configuration may be activated through L1 signaling such as PDCCH / DCI (e.g., group-common DCI).The active time period or active time period of Cell DTX / DRX can transmit and receive all signals and channels without any special restrictions on signal transmission and reception, just like the normal operation of the base station. The time period other than the active time period (or, inactive time period) can be basically regarded as an inactive time period. In this case, transmission and reception of signals / channels other than the preset signals and channels can be restricted during the inactive time period. Since only the minimum transmission / reception is performed during this inactive time period, the base station can obtain ES (energy saving) benefit, and thus, this operation of Cell DRX / DTX can be considered as an operation when the NES state / mode is ON.

[0217] In addition, the base station can set Cell OFF to completely turn off a specific cell for a certain period of time in order to save more energy, separately from the Cell DTX / DRX configuration in which a specific ON / OFF duration pattern is periodically repeated in advance. When Cell OFF is performed, terminals connected to the turned off cell cannot transmit / receive data at all. Therefore, the base station needs to move the terminals to another cell that is turned on. In particular, if the target cell of Cell OFF is the PCell of specific terminals, the base station can trigger a handover procedure to the terminals to change the PCell. At this time, the trigger of the handover procedure can be dynamically indicated through L1 (UE-specific or group-common) signaling. To this end, if the DCI format for activating / deactivating the Cell DTX / DRX configuration is utilized, there may be an advantage in terms of signaling overhead because the base station can dynamically instruct multiple terminals within a cell to turn off Cell in a group-common manner. In addition, since the DCI format is composed of information blocks for each serving cell, a handover procedure for the PCell can be triggered by adding a cell OFF indication bit to the information block for the PCell of a specific terminal.

[0218] In this regard, Conditional handover (CHO) is a method in which a terminal performs / triggers a handover procedure on its own when a pre-set condition is satisfied, even if the base station does not directly issue a HO (handover) command to the terminal. A terminal for which CHO is set from a source cell evaluates whether at least one HO condition (RSRP / RSRQ of reference signal, SINR, etc.) is satisfied, and if at least one of the above HO conditions is satisfied, it can perform a HO procedure to transmit a RACH to a target cell.

[0219] Hereinafter, the fact that the base station operates in the NES mode for ES may mean that the base station sets multiple OFF intervals (DTX intervals of the base station) in advance to turn off transmission of specific DL signals during specific time intervals and dynamically indicates one of the multiple OFF intervals. Here, the DL signal in the one OFF interval may not be transmitted during the predefined time interval. In addition, it may mean an energy saving operation of the base station and the terminal for operations in the frequency domain and / or the spatial domain as well as the time domain. Here, the energy saving operation in the frequency domain may mean BWP switching, dynamic RB adaptation, etc., and the energy saving operation in the spatial domain may mean semi-statically or dynamically turning off a specific receiving antenna port of the base station to stop performing signal transmission and reception of the base station through the turned off antenna port, etc.

[0220] In this way, the base station can instruct activation / deactivation of Cell DTX / DRX settings and / or CHO triggering for Cell OFF through DCI format 2_9, which is a DCI format defined for activation / deactivation of Cell DTX / DRX settings and / or CHO triggering for Cell OFF.

[0221] First, DCI format 2_9, which is defined for CHO triggering for activation / deactivation of the above-described Cell DTX / DRX settings and / or Cell OFF, can be configured / defined as follows.

[0222] Specifically, the terminal can receive information about Cell DTX configuration(s) and / or cell DRX configuration(s) for the serving cell through higher layer signaling, such as RRC signaling. In this case, the terminal can be instructed to dynamically activate or deactivate the Cell DTX / DRX configuration in a group-common manner through DCI format 2_9 (or, the terminal can be configured to activate or deactivate the configured Cell DTX / DRX configuration through higher layer signaling, such as RRC). Since the terminal can have multiple serving cells, the DCI format 2_9 can be configured with multiple information blocks corresponding to each of the multiple serving cells. Each information block can be configured to include at least 1 bit for activating or deactivating the cell DTX configuration configured for the corresponding serving cell and 1 bit for activating or deactivating the cell DRX configuration. When DCI format 2_9 monitoring is set in Type-3 CSS (Common Search Space) for a terminal, the terminal can be configured in advance through an RRC parameter (e.g., position-inDCI-NES) for the position of the information block that it should monitor within DCI format 2_9.

[0223] In addition, each information block of the DCI format 2_9 may have a different bit width depending on whether cell DTX / DRX is set. For example, an information block corresponding to a serving cell set only with Cell DTX setting or cell DRX setting may be configured with 1 bit, and an information block corresponding to a serving cell set with both Cell DTX setting and cell DRX setting may be configured with 2 bits. Accordingly, when a CHO triggering bit for Cell OFF of a specific serving cell is additionally included in an information block corresponding to the specific serving cell, the information block of the specific serving cell may be configured with 1, 2, or N bits (N=1 when the CHO triggering bit is 1 bit) depending on whether cell DTX / DRX is set. Alternatively, the CHO triggering bit may be set at a specific location (e.g., at the very beginning or very end of DCI format 2_9, or before / after a specific information block, etc.) separate from the information block indicating the activation or deactivation of cell DTX / DRX settings in DCI format 2_9.

[0224] The base station can increase the energy saving of the base station and / or the energy saving benefit of the terminal by instructing the activation / deactivation of the Cell DTX / DRX setting and / or the CHO triggering for Cell OFF using the DCI format 2_9 defined as above. For example, in terms of base station operation, it is necessary to increase the energy saving benefit of the base station through Cell OFF when the number of terminals connected to the cell is small or there is little data activity (e.g., late at night) depending on the cell situation. In this case, the base station may need to trigger CHO to the terminals through the DCI format 2_9.

[0225] However, the terminal does not perform PDCCH monitoring outside the active time period in order to save power. Alternatively, a terminal configured to exceptionally monitor DCI format 2_6 may perform monitoring for DCI format 2_6 a time period ps-Offset before the onDuration starts. In other words, a terminal configured with UE C-DRX does not perform other PDCCH monitoring in a time period (e.g., an inactive time period) outside the active time period (e.g., an active time period according to the C-DRX configuration), except when monitoring of DCI format 2_6 is configured. Accordingly, even in the case of DCI format 2_9 indicating Cell DTX / DRX (de)activation and / or Cell OFF, the terminal may be able to receive only during the onDuration (or the active time period) of the terminal.

[0226] In this case, if the base station wants to dynamically indicate cell OFF in a time period other than the active time period, the base station must wait until the onDuration (or active time period) of the terminal for which C-DRX is configured before transmitting DCI format 2_9, which may unnecessarily increase the delay in the HO procedure and / or the delay in activation / deactivation of the Cell DTX / DRX configuration. In addition, since the C-DRX configuration is UE-specifically indicated / configured, the onDuration (or active time period) may be different for each terminal within the cell. In this case, it may be difficult to immediately trigger CHO and / or indicate activation / deactivation of the Cell DTX / DRX configuration depending on the situation within the cell, which may result in a delay in cell power off. This delay in cell power off may significantly reduce the energy saving benefit of the base station / terminal.

[0227] Therefore, the terminal needs to monitor DCI format 2_9 even for the inactive time period in certain cases, and as a method for monitoring DCI format 2_9 in the inactive time period, the following methods 1 and 2 can be considered.

[0228] Meanwhile, the active time interval defined below may be a union of the operation times of timers configured in relation to DRX (such as an inactivitytimer and / or a timer for retransmission) and the time interval of a predefined onDuration. For example, a terminal configured with UE C-DRX may start an inactivity timer when a PDCCH is received in onDuation. The terminal may wait to receive a transmission / reception scheduling of the base station until the inactivity timer expires. In addition, the terminal may maintain an active state for retransmission even when a timer for retransmission operates. Therefore, the active time interval related to the UE C-DRX operation may be a union of the operation times of the above-described specific timers and / or intervals for performing PDCCH monitoring for each slot with a predefined onDuration. That is, in the following, the active time interval (or the active time interval related to the UE C-DRX configuration) is explained assuming that it is a time interval in which scheduling can be expected by the operation of the above-described timer and / or a predefined onDuration.

[0229] 1. Method 1

[0230] Method 1 may be a method for determining whether to perform DCI format 2_9 monitoring in a C-DRX inactive time interval (a time interval other than an active time interval) based on a configuration method of DCI format 2_9.

[0231] Methods for performing monitoring of DCI format 2_9 based on the configuration of the above-described DCI format 2_9 may include the following methods 1-1, 1-2, and 1-3.

[0232] (1) Method 1-1: A method of performing DCI format 2_9 monitoring in a C-DRX inactive time period when the CHO triggering bit is set to be included in DCI format 2_9.

[0233] When the CHO triggering bit is set to be included in DCI format 2_9, the terminal may monitor DCI format 2_9 even during the UE C-DRX inactivity time period. Here, the CHO triggering bit being set to be included in DCI format 2_9 may be at least one of the following cases.

[0234] - ① In case an RRC parameter indicating the starting bit position for CHO triggering purposes is additionally included in the RRC parameter indicating the starting bit position of the information block in DCI format 2_9 (in other words, in case an RRC parameter indicating the starting bit position for CHO triggering purposes is additionally set in the RRC parameter indicating / informing the starting bit position for the information block in DCI format 2_9)

[0235] - ② When the bit width of the additional information block is set in the RRC parameter that indicates the start bit position of the information block within DCI format 2_9.

[0236] - ③ If the configuration information for the CHO triggering bit is provided as a separate RRC parameter

[0237] That is, if the field / bit of the CHO triggering bit is (additionally) defined / set for the DCI format 2_9 by RRC signaling, the terminal can perform monitoring of the DCI format 2_9 in at least one MO (Monitoring Occasion) set for the DCI format 2_9 even during the inactive time period.

[0238] (2) Method 1-2: A method of omitting monitoring of DCI format 2_9 in all or part of the C-DRX inactivity time period of the terminal when the CHO triggering bit is not set to be included in DCI format 2_9.

[0239] The terminal may omit monitoring for DCI format 2_9 during the C-DRX inactivity time period of the terminal if the CHO triggering bit is not set to be included in DCI format 2_9.

[0240] Alternatively, if the CHO triggering bit is not set to be included in the DCI format 2_9, the terminal may perform DCI format 2_9 monitoring only in some time intervals during the inactive time interval. For example, the terminal may perform monitoring for the DCI format 2_9 in the UE C-DRX active time interval and some time intervals. For example, the terminal may monitor the DCI format 2_9 only in an MO located in an odd or even slot among all MOs (configured for the DCI format 2_9) associated with the inactive time interval. Alternatively, the terminal may monitor the DCI format 2_9 only once per N times (N is a parameter preset / instructed by the base station) among all MOs associated with the inactive time interval. For example, if the CHO triggering bit is not set to be included in DCI format 2_9, the terminal may perform DCI format 2_9 monitoring even during an exceptionally inactive time period for an MO located in an odd or even slot or the Nth slot among all MOs set for DCI format 2_9.

[0241] (3) Method 1-3: A method for setting whether to monitor DCI format 2_9 in the UE C-DRX inactivity time period according to the presence or absence of a CHO triggering bit by the base station.

[0242] The terminal may also be separately configured by the base station to monitor DCI format 2_9 during the UE C-DRX inactivity time interval depending on whether the CHO triggering bit is set to be included in DCI format 2_9. For example, the base station may instruct / configure the terminal to perform DCI format 2_9 monitoring during the UE C-DRX inactivity time interval if the CHO triggering bit is set to be included in DCI format 2_9. Alternatively, the base station may instruct / configure the terminal not to perform DCI format 2_9 monitoring during the UE C-DRX inactivity time interval if the CHO triggering bit is set to be included in DCI format 2_9. Alternatively, the base station may instruct / configure the terminal to perform DCI format 2_9 monitoring during the UE C-DRX inactivity time interval if the CHO triggering bit is not set to be included in DCI format 2_9. Alternatively, the base station may instruct / configure the UE not to perform DCI format 2_9 monitoring during the UE C-DRX inactivity time period if the CHO triggering bit is not set to be included in DCI format 2_9.

[0243] (4) Method 1-4: How to always set the monitoring cycle of DCI format 2_9 for CHO triggering and the monitoring cycle of DCI format 2_9 for cell DTX / DRX to be the same or set each individually.

[0244] For example, in a specific MO (Monitoring occasion(s)) of DCI format 2_9, the contents of the DCI format may be composed of (de)activation bits + CHO triggering bits, and in other specific MO(s), the contents of the DCI format may be composed of only (de)activation bits.

[0245] Specifically, the monitoring period between the DCI format 2_9 including the CHO triggering bit and the DCI format 2_9 without the CHO triggering bit can be individually set. For example, the terminal may always set the monitoring period of the CHO triggering DCI format 2_9 and the monitoring period of the DCI format 2_9 for cell DTX / DRX to be the same, regardless of whether the CHO triggering bit is included. Alternatively, the monitoring period of the DCI format 2_9 including the CHO triggering bit can be set to be an integer multiple (or an even or odd slot) of the monitoring period of the DCI format 2_9 for cell DTX / DRX. For example, among all MOs for DCI format 2_9, DCI format 2_9 consisting of Cell DTX / DRX (de)activation bits + CHO triggering bits can be monitored only in odd slots, and DCI format 2_9 consisting of only Cell DTX / DRX (de)activation bits can be monitored in the remaining MOs.

[0246] (5) Method 1-5: When CHO is triggered, the cell DTX / DRX maintains the previous activation / deactivation state (without reading the remaining bits in DCI format 2_9), and when CHO is not triggered, the cell DTX / DRX setting is (de)activated according to the cell DTX / DRX instruction per information block included in DCI format 2_9.

[0247] Specifically, when CHO is triggered via DCI format 2_9, cell DTX / DRX can maintain its previous enable / disable state (without reading the bits in DCI format 2_9). For example, when recognizing that CHO is triggered via DCI format 2_9, the terminal can maintain the enable for the Cell that was in the enabled state and maintain the disable for the Cell that was in the disabled state without decoding the remaining bits in DCI format 2_9. When CHO is not triggered, the terminal can activate / deactivate Cell DTX / DRX according to the cell DTX / DRX activation or deactivation instruction for each information block in DCI format 2_9.

[0248] 2. Method 2

[0249] Method 2 is a method for performing DCI format 2_9 monitoring based on a wake-up indicator or wake-up indication of DCI format 2_6. For example, the terminal can determine whether to perform DCI format 2_9 monitoring during an inactive time interval based on the monitoring result of DCI format 2_6.

[0250] DCI format 2_6 is scrambled with PS-RNTI (Power Saving RNTI), and the start position of the block to be read (monitored) for each terminal in DCI format 2_6 can be determined / set by the ps-PositionDCI-2-6 parameter. The block for each terminal can be composed of a wake-up indication field and an Scell ​​*?*dormant indication field. If the wake-up indication consisting of 1 bit in the wake-up indication field is 0, the timer (i.e., drx-onDurationTimer) for the next (long) DRX cycle does not start, and if the wake-up indication consisting of 1 bit in the wake-up indication field is 1, the timer for the next (long) DRX cycle can start. Here, the terminal can monitor the scheduling information of the base station while the timer is operating. Scell ​​*?* Dormancy instructions can be composed of a bitmap, and the size of the bitmap can be determined by the DormancyGroupID setting.

[0251] In addition, DCI format 2_6 can be transmitted (received from the terminal's perspective) only in a time period other than the terminal's active time period (i.e., the C-DRX inactive time period), and the size of DCI format 2_6 can be determined by a parameter of sizeDCI-2-6 (RRC parameter). In addition, a terminal configured to monitor DCI format 2_6 can be configured with a default behavior when DCI format 2_6 is detected or not monitored. For example, one of 'wake-up' or 'go-to-sleep' can be configured as the default behavior for the terminal.

[0252] As described above, a terminal for which UE C-DRX is configured can perform PDCCH monitoring for each slot only in a time period according to a pre-configured onDuration for power saving and a time period due to a retransmission / inactivity timer (i.e., an active time period). Exceptionally, only when monitoring of DCI format 2_6 is configured for the terminal, the terminal can perform PDCCH monitoring (i.e., monitoring of DCI format 2_6) in a time period other than the active time period (or, an inactive time period), and for the remaining DCI formats including DCI format 2_9, monitoring can be performed only for the active time period. Therefore, the Cell DTX / DRX (de)activation instruction and the CHO triggering instruction of the base station can be transmitted / received only within a limited time period.

[0253] At this time, in terms of base station operation, it is necessary to increase the energy saving benefit of the base station through Cell DTX / DRX activation and / or Cell OFF when the number of terminals connected to the cell is small or there is little data activity (e.g., late at night) depending on the cell situation. That is, the base station may need to trigger cell DTX / DRX activation and / or CHO for terminals through DCI format 2_9. However, if the base station wants to dynamically instruct Cell OFF and / or cell DTX / DRX activation in a time period other than the active time period, the base station must wait until the onDuration (or active time period) of the terminal for which UE C-DRX is configured before transmitting DCI format 2_9, which may unnecessarily increase the delay of HO and / or cell DTX / DRX activation. In addition, since the UE C-DRX configuration is UE-specific, the onDuration (or active time period) may be different for each terminal within the cell. In this case, the base station may not be able to issue an immediate CHO triggering instruction depending on the situation within the cell, which may result in a delay in powering off the base station, and the energy saving benefit of the base station / terminal may be significantly reduced.

[0254] Therefore, in order to save energy of the terminal and / or the base station, the terminal may need to exceptionally perform monitoring of DCI format 2_9 even during the inactive time period based on the monitoring result of DCI format 2_6. For example, the terminal may determine whether to perform DCI format 2_9 monitoring during the C-DRX inactive time period in conjunction with the wake-up indication field of DCI format 2_6 or the default behavior when DCI format 2_6 is not detected / monitored. In this case, flexible monitoring may be set / determined by considering the trade-off between power saving of the base station and the terminal and immediate Cell DTX / DRX and / or CHO triggering indication.

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

[0256] (1) Method 2-1: Monitoring of DCI format 2_9 based on wake-up indicated by detected / received DCI format 2_6

[0257] The terminal may perform monitoring of DCI format 2_9 during onDuration and the C-DRX inactivity time period linked to the onDuration when the wake-up instruction (or wake-up indicator) included in the detected / received DCI format 2_6 indicates 'wake-up (i.e., start of drx-onDurationTimer)'.

[0258] For example, the terminal may be configured to monitor DCI format 2_9 both during the onDuration and the UE C-DRX inactivity time interval associated therewith when the wake-up indication within the monitored DCI format 2_6 indicates 'wake-up'. In other words, when the bit value included in the wake-up indication field included in DCI format 2_6 indicates 'wake-up' (i.e., when the bit value of 1 indicating the start of drx-onDurationTimer is set), the terminal may perform monitoring of other PDCCHs including DCI format 2_9 during the subsequent onDuration (i.e., the onDuration in which wake-up is indicated), and an MO may be configured to exceptionally perform monitoring of DCI format 2_9 during the entirety (or part) of the UE C-DRX inactivity time interval (from the end of the onDuration in which wake-up is indicated to before the onDuration of the next (period)). For example, when a DCI of DCI format 2_6 (or a PDCCH including DCI) including a bit value of 1 indicating the start of drx-onDurationTimer is received, the terminal may perform monitoring of DCI format 2_9 in MOs set for DCI format 2_9 within the operating time period (onDuration or active time period) and the inactive time period (before the next onDuration after the expiration of the drx-onDurationTimer) of the drx-onDurationTimer.

[0259] (2) Method 2-2: Omit monitoring of DCI format 2_9 based on 'go-to-sleep' indicated by detected / received DCI format 2_6.

[0260] Alternatively, if the wake-up indication included in the received / detected DCI format 2_6 indicates 'go-to-sleep (or a bit value of 0 indicating that drx-onDurationTimer is not started)', the UE may omit monitoring of DCI format 2_9 during the onDuration period in which go-to-sleep is indicated and the UE C-DRX inactivity time interval associated therewith.

[0261] (3) Method 2-3: Performing limited DCI format 2_9 monitoring based on the 'go-to-sleep' indication by the detected / received DCI format 2_6.

[0262] In case of method 2-3, the terminal can exceptionally perform monitoring of DCI format 2_9 in onDuration instructed to 'go-to-sleep' by wake-up instruction.

[0263] Specifically, if the wake-up instruction indicated by DCI format 2_6 indicates 'go-to-sleep', the terminal may maintain a sleep state without monitoring PDCCH for DCI formats other than DCI format 2_9 in the subsequent onDuration (i.e., the onDuration in which the wake-up instruction indicates 'go-to-sleep' or the onDuration that is turned off). That is, the terminal may exceptionally monitor only DCI format 2_9 in the onDuration that is turned off by the wake-up instruction. However, the terminal may omit monitoring of DCI format 2_9 in the C-DRX inactive time period linked to the turned off onDuration.

[0264] Alternatively, whether to perform monitoring of DCI format 2_9 when the wake-up instruction indicated by DCI format 2_6 indicates 'go-to-sleep' can be separately configured. For example, the base station can configure the terminal to perform monitoring of DCI format 2_9 during the UE C-DRX inactivity time period linked thereto even when the wake-up instruction indicated by DCI format 2_6 indicates 'go-to-sleep'.

[0265] Alternatively, configuration information on whether to perform DCI format 2_9 monitoring for the entire onDuration and the UE C-DRX inactivity time interval associated therewith (or for each of the onDuration and the inactivity time interval) may be provided in advance by a wake-up instruction indicated to the terminal in DCI format 2_6.

[0266] (4) Method 2-4: Determining whether to perform monitoring of DCI format 2_9 based on the length of the UE C-DRX periodicity or inactivity period.

[0267] The terminal may determine whether to perform DCI format 2_9 monitoring based on the UE C-DRX periodicity or the length of the inactivity period (e.g., short / long DRX cycle).

[0268] Specifically, the terminal can determine whether to perform DCI format 2_9 monitoring in the UE-CDRX inactive time interval based on the length of the UE C-DRX cycle or the inactive time interval. For example, a terminal for which a short DRX cycle is set may not perform monitoring in the MO of the DCI format 2_9 set for the inactive time interval because the length from onDuration to the next (cycle) onDuration is short. Conversely, if the short DRX cycle is not set for the terminal and the length of the inactive time interval is relatively long (e.g., a long DRX cycle), the terminal may perform monitoring in the MO of the DCI format 2_9 set for the inactive time interval. Alternatively, considering the power saving aspect of the terminal, a terminal for which a long DRX cycle is set may not perform monitoring in the MO of the DCI format 2_9 set for the inactive time interval, and may perform monitoring in the MO of the DCI format 2_9 set for the inactive time interval only when a short DRX cycle is set.

[0269] Alternatively, whether to perform monitoring of DCI format 2_9 within the inactive time interval may be determined based on the DRX cycle period of the UE C-DRX. For example, if a specific threshold value is set in advance, the terminal may perform monitoring of DCI format 2_9 during the inactive time interval if the UE C-DRX cycle is greater than the specific threshold value (greater than or exceeding the specific threshold value) based on the specific threshold value. Alternatively, if the UE C-DRX cycle is less than the specific threshold value (less than or equal to the specific threshold value), the terminal may omit monitoring of DCI format 2_9 during the inactive time interval. Alternatively, in consideration of the power saving aspect of the terminal, if a specific threshold value is set in advance, and the terminal may perform monitoring of DCI format 2_9 during the inactive time interval if the UE C-DRX cycle is less than the specific threshold value (less than or equal to the specific threshold value) based on the specific threshold value. Conversely, if the UE C-DRX cycle is greater than the above-mentioned specific threshold (above or exceeding the specific threshold value), the terminal may omit monitoring of DCI format 2_9 during the inactive time interval.

[0270] (5) Method 2-5: Determining whether to monitor DCI format 2_9 based on default behavior when DCI format 2_6 is not detected / received

[0271] The terminal may determine whether to monitor the DCI format 2_9 based on at least one of the above-described methods (methods 2-1, 2-2, 2-3, 2-4) based on a default behavior set for when DCI format 2_6 is not received / detected.

[0272] Specifically, the base station does not always transmit DCI (e.g., DCI format 2_6) for each MO configured for DCI format 2_6 in order to save energy. Therefore, a default behavior may be configured for whether the terminal 'wake-up' or 'go-to-sleep' when DCI format 2_6 is not detected. In this case, the terminal may determine whether to monitor the DCI format 2_9 by applying at least one of the above-described methods (methods 2-1, 2-2, 2-3, 2-4) based on the default behavior configured when DCI format 2_6 is not received / detected.

[0273] For example, if the default behavior is set to 'go-to-sleep' and DCI format 2_6 is not detected / found / received, the terminal may apply method 2-2 and / or method 2-3 based on the default behavior of go-to-sleep. Alternatively, if the default behavior is set to wake-up and DCI format 2_6 is not detected / found / received, the terminal may apply method 2-1 based on the default behavior of wake-up.

[0274] Figure 11 is a diagram for explaining a method for a terminal to perform monitoring of a second DCI.

[0275] As described above, the terminal can perform DRX-related operations even during an RRC connection with the base station based on the C-DRX configuration. The terminal can be switched to a wake-up or sleep state based on an active time interval (or C-DRX active period) and an inactive time interval (or C-DRX inactive period) based on the C-DRX configuration. For example, the terminal can determine an active time interval based on an onduration interval set through drx-StartOffset and drx-SlotOffet included in the configuration information and a DRX-related timer (such as an on-duration timer, an inactivity timer, and a short DRX cycle timer), and can determine an inactive time interval for the remaining interval excluding the active time interval in the DRX cycle. Meanwhile, the reception / monitoring of DCI in the following may correspond to the reception / monitoring of a PDCCH including DCI.

[0276] Specifically, referring to FIG. 11, the terminal can receive configuration information for C-DRX from the base station (S111). Here, the configuration information can include parameters such as on-duration, onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimer, longDRX-Cycle, drxStartOffset, drxShortCycleTimer, shortDRX-Cycle, and drx-SlotOffset, as described with reference to FIG. 7.

[0277] Next, the terminal for which C-DRX is configured can detect / monitor the first DCI including a wake-up indication field (S113). Here, the first DCI may be a DCI format 2_6 including wake-up indication information indicating whether the terminal will wake-up or sleep in the active time interval based on the configuration information. For example, if the wake-up indication field / information includes a first bit value (e.g., 1) related to wake-up, the terminal may start onDurationTimer and perform monitoring for all PDCCHs including DCI during the onDurationTimer operation. Meanwhile, as described above, the first DCI is a DCI that can be exceptionally transmitted in the inactive time interval, and the terminal can detect / monitor whether the first DCI is received at a predefined timing (e.g., an MO configured for monitoring the first DCI) in the inactive time interval.

[0278] Next, the terminal can determine whether to monitor the second DCI related to cell DRX / DTX in the inactive time interval set through the configuration information based on the detection result of the first DCI (S115). For example, a terminal configured with C-DRX can determine whether to monitor the second DCI (e.g., DCI format 2_9) for activation / deactivation of cell DRX / DTX configuration in conjunction with the monitoring / detection result of the first DCI. That is, in order to minimize the delay of operations for energy saving of the base station and / or the terminal, the terminal can exceptionally monitor the second DCI in certain cases even in the inactive time interval. For example, the terminal can determine whether to monitor the exceptional second DCI in the inactive time interval based on the monitoring result of the first DCI as in Method 2. Alternatively, the terminal can determine whether to monitor the exceptional second DCI in the inactive time interval based on whether the CHO triggering bit is set to be included for the second DCI as in Method 1 described above.

[0279] Specifically, when a first DCI including instruction information indicating wake-up is detected in a specific onDuration (i.e., an onDuration of a DRX cycle starting after detection of the first DCI), the terminal may perform monitoring for the second DCI in an inactive time interval linked to the specific onDuration (a time interval excluding the specific onDuration indicated by the first DCI in a DRX cycle, or an interval from the end of the specific onDuration to the start of the specific onDuration of the next cycle).

[0280] For example, when the first DCI including the wake-up indication information having a bit value related to wake-up is detected, the terminal may start the onDurationTimer and transition to a wake-up state. In this case, the terminal may also perform monitoring of the second DCI during an inactive time period from the time when the onDurationTimer expires until the start of the onDuration of the next cycle. That is, the terminal may perform monitoring of the second DCI during both an active time period in which wake-up is indicated by the first DCI and a corresponding inactive time period.

[0281] As described above, the onDuration related to the monitoring of the second DCI and the corresponding / linked inactive time interval are for the onDuration of the DRX cycle starting after the monitoring of the first DCI and the remaining interval (e.g., the remaining interval excluding the onDuration in the DRX cycle). The following description assumes that the onDuration is for the onDuration of the DRX cycle starting after the point in time when the monitoring of the first DCI is performed.

[0282] Specifically, if a first DCI including sleep-indicating instruction information is detected in onDuration, the terminal may skip monitoring the second DCI during the inactive time period linked to the onDuration. For example, if the first DCI including the wake-up instruction information having a bit value related to sleep is detected, the terminal may maintain a sleep state in the onDuration without starting the onDurationTimer. In this case, the terminal may skip monitoring the second DCI not only during the onDuration but also during the inactive time period linked thereto. Alternatively, the terminal may exceptionally perform monitoring only for the second DCI in the onDuration, and skip monitoring the second DCI during the inactive time period linked to the onDuration.

[0283] Alternatively, the terminal may not detect the first DCI. In this case, the terminal may determine whether to monitor the PDDCCH including the DCI in onDuration based on the preset default operation as described above. For example, if wake-up is set as the default operation for the terminal, the terminal may wake-up in onDuration and monitor the PDCCH if the first DCI is not detected. In this case, the terminal may exceptionally perform monitoring of the second DCI even in the inactive time period linked to onDuration. Alternatively, if sleep is set as the default operation for the terminal, the terminal may sleep in onDuration if the first DCI is not detected, and monitoring of the second DCI may be omitted in the inactive time period linked to the sleep-indicated onDuration (or, onDuration that is turned off).

[0284] Figure 12 is a diagram for explaining a method for a base station to transmit a second DCI to a terminal.

[0285] Referring to FIG. 12, the base station can transmit configuration information for C-DRX to the terminal (S121). Here, the configuration information can include parameters such as on-duration, onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimer, longDRX-Cycle, drxStartOffset, drxShortCycleTimer, shortDRX-Cycle, and drx-SlotOffset, as described with reference to FIG. 7.

[0286] Next, the base station may determine whether to transmit the second DCI during the inactive time interval set for the terminal based on whether the first DCI has been transmitted (S123). Alternatively, the base station may determine whether to transmit the exceptional second DCI during the inactive time interval based on whether the second DCI is configured to include a CHO triggering bit, as in Method 1 described above.

[0287] For example, when the base station transmits the first DCI to the terminal, the base station may determine whether to transmit the second DCI during the inactive time interval linked to the onDuration indicated by the first DCI based on wake-up indication information included in the first DCI. For example, when the base station transmits the first DCI including the wake-up indication information having a bit value indicating wake-up, the base station may transmit the second DCI to the terminal even during the linked inactive time interval. Alternatively, when the base station transmits the first DCI including the wake-up indication information having a bit value indicating sleep to the terminal, the base station may not transmit the second DCI to the terminal during the inactive time interval. Alternatively, the base station may exceptionally transmit the second DCI only during the onDuration of sleep.

[0288] Alternatively, the base station may determine whether to transmit the second DCI during the inactive time interval based on a default operation set for the terminal when the first DCI is not transmitted to the terminal. For example, if wake-up is set as the default operation for the terminal, the base station may transmit the second DCI during the inactive time interval. Alternatively, if sleep is set as the default operation for the terminal, the base station may omit transmission of the second DCI during the inactive time interval.

[0289] In this way, the proposed invention can minimize the delay in the application of cell DRX / DTX due to the C-DRX operation of the terminal. Alternatively, the proposed invention can minimize the delay in the performance of cell DRX operation due to the C-DRX operation of the terminal by exceptionally allowing the monitoring of the DCI format 2_9 during the inactive time period. Alternatively, the proposed invention can flexibly schedule whether to transmit DCI format 2_9 during the inactive time period based on DCI format 2_6.

[0290] Examples of communication systems to which the invention applies

[0291] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts of the present invention disclosed in this document may be applied to various fields requiring wireless communication / connection (e.g., 5G) between devices.

[0292] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0293] Figure 13 illustrates a communication system applied to the present invention.

[0294] Referring to FIG. 13, a communication system (1) applied to the present invention includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and can be implemented in the form of HMD (Head-Mounted Device), HUD (Head-Up Display) installed in a vehicle, television, smartphone, computer, wearable device, home appliance, digital signage, vehicle, robot, etc. Mobile devices can include smartphone, smart pad, wearable device (e.g., smart watch, smart glass), computer (e.g., laptop, etc.), etc. Home appliances can include TV, refrigerator, washing machine, etc. IoT devices can include sensors, smart meters, etc. For example, base stations and networks can also be implemented as wireless devices, and a specific wireless device (200a) can act as a base station / network node to other wireless devices.

[0295] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0296] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present invention.

[0297] Examples of wireless devices to which the present invention is applied

[0298] Figure 14 illustrates a wireless device applicable to the present invention.

[0299] Referring to FIG. 14, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the base station (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 13.

[0300] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chipset designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present invention, a wireless device may also mean a communication modem / circuit / chipset.

[0301] Specifically, the first wireless device or terminal (100) may include a processor (102) and a memory (104) connected to a transceiver (106). The memory (104) may include at least one program capable of performing operations related to the embodiments described in FIGS. 10 to 12.

[0302] The processor (102) controls the transceiver (106) to receive configuration information for C-DRX (Connected mode Discontinuous Reception) from a base station, detect a first DCI (downlink control information) including wake-up instruction information, and determine whether to monitor a second DCI related to cell DRX or cell DTX (Discontinuous Transmission) during an inactive time interval set through the configuration information based on a detection result of the first DCI.

[0303] Alternatively, a processing device including a processor (102) controlling a terminal and a memory (104) may be configured. In this case, at least one processor; and at least one memory connected to the at least one processor and storing instructions, wherein the instructions, based on being executed by the at least one processor, cause the terminal to: receive configuration information for C-DRX (Connected mode Discontinuous Reception) from a base station, detect a first DCI (downlink control information) including wake-up indication information, and determine whether to monitor a second DCI related to cell DRX or cell DTX (Discontinuous Transmission) during an inactive time interval set through the configuration information based on a detection result of the first DCI.

[0304] The second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). Furthermore, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present invention, a wireless device may also mean a communication modem / circuit / chip.

[0305] Specifically, the second wireless device or base station (200) may include a processor (202) and a memory (204) connected to a transceiver or RF transceiver (206). The memory (204) may include at least one program capable of performing operations related to the embodiments described in FIGS. 10 to 12.

[0306] The processor (202) controls the transceiver (206) to transmit configuration information for C-DRX (Connected mode Discontinuous Reception) to the terminal, and based on whether or not to transmit the first DCI (downlink control information) including wake-up instruction information, the processor (202) can determine whether or not to transmit the second DCI (downlink control information) related to cell DRX or cell DTX (Discontinuous Transmission) during the inactivity time interval set for the terminal through the configuration information.

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

[0308] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For 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, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0309] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0310] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 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, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0311] Examples of wireless devices to which the present invention is applied

[0312] Figure 15 illustrates another example of a wireless device applicable to the present invention. The wireless device may be implemented in various forms depending on the use case / service (see Figure 13).

[0313] Referring to FIG. 15, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 14 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and an additional element (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 15. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 14. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0314] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 13, 100a), a vehicle (Fig. 13, 100b-1, 100b-2), an XR device (Fig. 13, 100c), a portable device (Fig. 13, 100d), a home appliance (Fig. 13, 100e), an IoT device (Fig. 13, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 13, 400), a base station (Fig. 13, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0315] In FIG. 15, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and a first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of a set of one or more processors. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0316] Examples of vehicles or autonomous vehicles to which the present invention is applied

[0317] Figure 16 illustrates a vehicle or autonomous vehicle applicable to the present invention. The vehicle or autonomous vehicle may be implemented as a mobile robot, car, train, manned / unmanned aerial vehicle (AV), ship, etc.

[0318] Referring to FIG. 16, a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving 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 a part of the communication unit (110). Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 of FIG. 15, respectively.

[0319] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit (120) can control elements of the vehicle or autonomous vehicle (100) to perform various operations. The control unit (120) can include an ECU (Electronic Control Unit). The drive unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The drive unit (140a) can include an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit (140b) supplies power to the vehicle or autonomous vehicle (100) and can include a wired / wireless charging circuit, a battery, etc. The sensor unit (140c) can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit (140c) may include an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an incline sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit (140d) may implement a technology for maintaining a driving lane, a technology for automatically controlling speed such as adaptive cruise control, a technology for automatically driving along a set path, a technology for automatically setting a path and driving when a destination is set, etc.

[0320] For example, the communication unit (110) can receive map data, traffic information data, etc. from an external server. The autonomous driving unit (140d) can generate an autonomous driving route and driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or autonomous vehicle (100) moves along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can irregularly / periodically acquire the latest traffic information data from an external server and can acquire surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit (140c) can acquire vehicle status and surrounding environment information. The autonomous driving unit (140d) can update the autonomous driving route and driving plan based on newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving route, driving plan, etc. to the external server. External servers can predict traffic information data in advance using AI technology or other technologies based on information collected from vehicles or autonomous vehicles, and provide the predicted traffic information data to the vehicles or autonomous vehicles.

[0321] Here, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by 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 above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PAN (personal area networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0322] The embodiments described above are combinations of components and features of the present invention in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form an embodiment of the present invention by combining some components and / or features. The order of operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form an embodiment or may be incorporated as a new claim through a post-application amendment.

[0323] In this document, embodiments of the present invention have been described primarily focusing on the signal transmission and reception relationship between a terminal and a base station. This transmission and reception relationship is equally / similarly extended to signal transmission and reception between a terminal and a relay or a base station and a relay. Certain operations described as being performed by a base station in this document may, in some cases, be performed by its upper node. That is, it is obvious that various operations performed for communication with a terminal in a network composed of multiple network nodes including a base station may be performed by the base station or other network nodes other than the base station. The base station may be replaced by terms such as fixed station, Node B, eNode B (eNB), and access point. In addition, the terminal may be replaced by terms such as UE (User Equipment), MS (Mobile Station), MSS (Mobile Subscriber Station).

[0324] Embodiments of the present invention may be implemented by various means, for example, hardware, firmware, software, or a combination thereof. In the case of hardware implementation, an embodiment of the present invention may 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.

[0325] When implemented via firmware or software, an embodiment of the present invention may be implemented in the form of modules, procedures, functions, etc. that perform the functions or operations described above. The software code may be stored in a memory unit and executed by a processor. The memory unit may be located within or outside the processor and may exchange data with the processor via various known means.

[0326] It will be apparent to those skilled in the art that the present invention can be embodied in other specific forms without departing from the scope of the invention. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present invention are intended to be included within the scope of the present invention.

[0327] The embodiments of the present invention as described above can be applied to various mobile communication systems.

Claims

1. A step of receiving configuration information for C-DRX (Connected mode Discontinuous Reception) from a base station; A step of detecting a first DCI (downlink control information) including wake-up indication information; and A method comprising a step of determining whether to monitor a second DCI related to cell DRX or cell DTX (Discontinuous Transmission) during an inactive time interval set through the setting information based on the detection result of the first DCI.

2. In paragraph 1, A method characterized in that monitoring of the second DCI is performed in the inactive period based on the wake-up operation being performed as a preset default operation by non-detection of the first DCI.

3. In paragraph 1, A method characterized in that monitoring of the second DCI is not performed in the inactive period based on the sleep operation being performed as a preset default operation by non-detection of the first DCI.

4. In paragraph 1, A method characterized in that monitoring of the second DCI is performed in the inactive period based on the detection of the first DCI including the wake-up indication information having a bit value related to wake-up.

5. In paragraph 1, A method characterized in that monitoring of the second DCI is not performed in the inactive period based on the detection of the first DCI including the wake-up indication information having a bit value associated with sleep.

6. In paragraph 5, A method characterized in that the monitoring of the second DCI is performed only for the onDuration section in which sleep is indicated by the first DCI.

7. In paragraph 1, A method, characterized in that the wake-up indication information includes a first bit value indicating the start of drx-onDurationTimer for the next DRX cycle or a second bit value indicating that drx-onDurationTimer for the next DRX cycle is not started.

8. In paragraph 1, A method, characterized in that the second DCI format further includes a conditional handover (CHO) triggering bit indicating whether to trigger a conditional handover (CHO).

9. In paragraph 1, A method, characterized in that the first DCI is DCI format 2_6 and the second DCI is DCI format 2_9.

10. A computer-readable recording medium recording a program for performing the method described in paragraph 1. 11.RF(Radio Frequency) transmitter and receiver; and A processor connected to the RF transceiver, A terminal in which the processor controls the RF transceiver to receive configuration information for C-DRX (Connected mode Discontinuous Reception) from a base station, detects first DCI (downlink control information) including wake-up instruction information, and determines whether to monitor second DCI related to cell DRX or cell DTX (Discontinuous Transmission) during an inactive time interval set through the configuration information based on a detection result of the first DCI.

12. In paragraph 11, A terminal characterized in that the monitoring of the second DCI is performed in the inactive period based on the wake-up operation being performed as a preset default operation by non-detection of the first DCI.

13. In paragraph 11, A terminal characterized in that monitoring of the second DCI is not performed in the inactive period based on the sleep operation being performed as a preset default operation by non-detection of the first DCI.

14. In a processing device that controls a terminal, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said terminal causes: A processing device that receives configuration information for C-DRX (Connected mode Discontinuous Reception) from a base station, detects a first DCI (downlink control information) including wake-up instruction information, and determines whether to monitor a second DCI related to cell DRX or cell DTX (Discontinuous Transmission) during an inactive time interval set through the configuration information based on a detection result of the first DCI.

15. Step of transmitting configuration information for C-DRX (Connected mode Discontinuous Reception) to the terminal; A method comprising a step of determining whether to transmit second DCI (downlink control information) related to cell DRX or cell DTX (Discontinuous Transmission) during an inactive time interval set for the terminal through the configuration information based on whether first DCI (downlink control information) including wake-up instruction information is transmitted.

Images