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

The method improves wireless communication system efficiency by allowing terminals to dynamically manage signal monitoring based on wake-up signal settings, optimizing power usage and enhancing accuracy for diverse communication scenarios.

WO2024237600A1PCT designated stage expired Publication Date: 2024-11-21LG ELECTRONICS INC
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
PCT/KR2024/006385
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-04-04
Filing Date
2024-05-10
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Current wireless communication systems face challenges in accurately and efficiently transmitting and receiving signals, particularly in managing power consumption and optimizing signal monitoring processes, especially in scenarios requiring low power usage like IoT devices and massive MTC communications.

Method used

The method involves a terminal receiving system information about a wake-up signal (WUS) to determine whether to perform a less power-consuming monitoring operation, including settings for the WUS waveform, time, and frequency resources, and activation/deactivation, allowing for dynamic power management and efficient signal processing.

Benefits of technology

This approach enhances signal transmission and reception accuracy and efficiency while reducing power consumption, particularly beneficial for next-generation wireless communication systems like 5G and NR, supporting massive MTC and eMBB applications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024006385_21112024_PF_FP_ABST
    Figure KR2024006385_21112024_PF_FP_ABST
Patent Text Reader

Abstract

A method for a terminal to receive a signal in a wireless communication system according to an embodiment of the present disclosure may comprise the steps of: receiving system information including a configuration related to a wake-up signal (WUS) through a first reception operation; and determining, on the basis of the system information, whether to perform monitoring of the WUS through a second reception operation that consumes less power than the first reception operation, wherein the configuration related to the WUS may include information about the waveform of the WUS.
Need to check novelty before this filing date? Find Prior Art

Description

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

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method for transmitting or receiving an uplink / downlink signal and a device therefor.

[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] The technical task to be achieved is to provide a method and a device for transmitting or receiving signals more accurately and efficiently in a wireless communication system.

[0004] Other technical challenges can be inferred from the embodiments disclosed in the detailed description.

[0005] A method for a terminal to receive a signal in a wireless communication system includes receiving system information including settings related to a wake-up signal (WUS) through a first receiving operation; and determining, based on the system information, whether to perform monitoring of the WUS through a second receiving operation that consumes lower power than the first receiving operation, wherein the settings related to the WUS may include information about a waveform of the WUS.

[0006] The settings related to the above WUS may include at least one of information on time and frequency resources of the above WUS, or information on activation / deactivation of the above WUS.

[0007] The above system information may further include settings related to a second synchronization signal for synchronization in the second receiving operation.

[0008] The second synchronization signal may be set differently from the first synchronization signal for synchronization in the first receiving operation.

[0009] The position of the second synchronization signal can be determined based on the position of a synchronization signal block (SSB) including the first synchronization signal.

[0010] The terminal can determine by itself whether to perform monitoring of the WUS based on whether the terminal operates in an RRC (radio resource control) idle / inactive state.

[0011] The terminal may perform a random access process to request transmission of the WUS to the network based on the decision to perform monitoring of the WUS.

[0012] Whether or not monitoring of the WUS should be performed while the terminal is operating in an RRC connection state can be explicitly set via network signaling.

[0013] Based on the quality of the signal measured through the first receiving operation, it can be determined whether to perform monitoring of the WUS through the second receiving operation.

[0014] The signal measured through the first receiving operation may include at least one of a first synchronization signal for synchronization in the first receiving operation or a second synchronization signal for synchronization in the second receiving operation.

[0015] According to another aspect, a computer-readable recording medium having recorded thereon a program for performing the above-described method may be provided.

[0016] According to another aspect, a device for wireless communication includes a memory storing commands; and a processor operating by executing the commands, wherein the operation of the processor includes receiving system information including settings related to a wake-up signal (WUS) through a first receiving operation; and determining, based on the system information, whether to perform monitoring of the WUS through a second receiving operation consuming lower power than the first receiving operation, wherein the settings related to the WUS may include information on a waveform of the WUS.

[0017] The device may further include a first receiver configured to perform the first receiving operation; and a second receiver configured to perform the second receiving operation.

[0018] The above device may be a terminal operating in a wireless communication system or a processing device controlling the terminal.

[0019] In another aspect, a method for transmitting a signal by a base station in a wireless communication system includes determining a setting related to a wake-up signal (WUS) for supporting a second reception operation that consumes less power than a first reception operation of a terminal; transmitting system information including the setting related to the WUS; and transmitting the WUS based on the setting related to the WUS, wherein the setting related to the WUS may include information on a waveform of the WUS.

[0020] According to another aspect, a base station for wireless communication includes a memory storing commands; and a processor operating by executing the commands, wherein the operation of the processor includes determining a setting related to a wake up signal (WUS) for supporting a second reception operation that consumes less power than a first reception operation of a terminal; transmitting system information including the setting related to the WUS; and transmitting the WUS based on the setting related to the WUS, wherein the setting related to the WUS may include information on a waveform of the WUS.

[0021] According to one embodiment, signals can be transmitted and received more accurately and efficiently in a wireless communication system.

[0022] Other technical effects may be derived from the embodiments disclosed in the detailed description.

[0023] Figure 1 illustrates physical channels used in a 3GPP system, which is an example of a wireless communication system, and a general signal transmission method using the channels.

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

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

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

[0027] Figure 5 illustrates a PDCCH (Physical Downlink Control Channel) transmission and reception process.

[0028] Figure 6 illustrates the PDSCH reception and ACK / NACK transmission process.

[0029] Figure 7 illustrates a PUSCH transmission process.

[0030] Figures 8 to 10 are drawings for explaining DRX-related operations.

[0031] Figure 11 is a drawing for explaining WUS.

[0032] Fig. 12 is a diagram for explaining the operation of a network and a terminal according to one embodiment.

[0033] FIG. 13 illustrates a flowchart of a method for a terminal to receive a signal in a wireless communication system according to one embodiment.

[0034] FIG. 14 illustrates a flowchart of a method for a base station to transmit a signal in a wireless communication system according to one embodiment.

[0035] Figures 15 to 18 illustrate a communication system (1) and a wireless device applicable to the present disclosure.

[0036] 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.

[0037] 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).

[0038] 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).

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

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

[0041] 3GPP LTE

[0042] - 38.211: Physical channels and modulation

[0043] - 38.212: Multiplexing and channel coding

[0044] - 38.213: Physical layer procedures for control

[0045] - 38.214: Physical layer procedures for data

[0046] - 38.215: Physical layer measurements

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

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

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

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

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

[0052] - 36.355: LTE Positioning Protocol

[0053] - 37.355: LTE Positioning Protocol

[0054] 용어 및 약어

[0055] - 5GC: 5G Core Network

[0056] - 5GS: 5G System

[0057] - AP: Access Point

[0058] - CID: Cell ID

[0059] - E-CID: Enhanced Cell ID

[0060] - PRS: Positioning Reference Signal

[0061] - RRM: Radio Resource Management

[0062] - TP: Transmission Point

[0063] - TRP: Transmission and Reception Point

[0064] - UE: User Equipment

[0065] - SSB: Synchronization Signal Block

[0066] - SFN: System Frame Number

[0067] - SS: Search Space

[0068] - CSS: Common Search Space

[0069] - USS: UE-specific Search Space

[0070] - PDCCH: Physical Downlink Control Channel

[0071] - PDSCH: Physical Downlink Shared Channel;

[0072] - PUCCH: Physical Uplink Control Channel;

[0073] - PUSCH: Physical Uplink Shared Channel;

[0074] - DCI: Downlink Control Information

[0075] - UCI: Uplink Control Information

[0076] - SI: System Information

[0077] - SIB: System Information Block

[0078] - MIB: Master Information Block

[0079] - RRC: Radio Resource Control

[0080] - DRX: Discontinuous Reception

[0081] - RNTI: Radio Network Temporary Identifier

[0082] - CSI: Channel state information

[0083] - PCell: Primary Cell

[0084] - SCell: Secondary Cell

[0085] - PSCell: Primary SCG(Secondary Cell Group) Cell

[0086] - CA: Carrier Aggregation

[0087] - WUS: Wake up Signal

[0088] - PO: Paging Occasion

[0089] - PEI: Paging Early Indication

[0090] - PEI-O: PEI Occasion

[0091] - NES: Network Energy Saving

[0092] - RO: RACH Occasion

[0093] - RAR: Random Access Response

[0094] - SDT: Small Data Transmission

[0095] - LP-WUS: Low Power Wake-Up Signal

[0096] - LP-WUR: Low-Power Wake-Up Receiver

[0097] - LP-SS: Low-Power Synchronization Signal

[0098] - XR: Abbreviation for eXtended Reality, VR (virtual reality), AR (augmented reality), MR (mixed reality)

[0099] - RRM: Radio Resource Management

[0100] 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.

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

[0102] 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.

[0103] 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.

[0104] 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.

[0105] 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.

[0106] 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.

[0107] 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.

[0108] 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

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

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

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

[0112] 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.

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

[0114] 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.

[0115] 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).

[0116] 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.

[0117] 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. The 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.

[0118] 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 a 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).

[0119] Figure 5 illustrates a PDCCH transmission / reception process.

[0120] Referring to FIG. 5, a base station can transmit a CORESET (Control Resource Set) configuration to a terminal (S502). A CORESET is defined as a set of REGs (Resource Element Groups) with a given numerology (e.g., SCS, CP length, etc.). A REG is defined as one OFDM symbol and one (P)RB. Multiple CORESETs for one terminal can overlap in the time / frequency domain. A CORESET can be configured through system information (e.g., Master Information Block, MIB) or upper layer (e.g., Radio Resource Control, RRC, layer) signaling. For example, configuration information for a given common CORESET (e.g., CORESET #0) can be transmitted through the MIB. For example, a PDSCH carrying SIB1 (system information block 1) can be scheduled by a specific PDCCH, and CORESET #0 can be for transmission of a specific PDCCH. Additionally, the configuration information for CORESET #N (e.g., N>0) may be transmitted via RRC signaling (e.g., cell-common RRC signaling or terminal-specific RRC signaling). For example, the terminal-specific RRC signaling carrying the CORESET configuration information may include, but is not limited to, various signaling such as an RRC setup message, an RRC reconfiguration message, and / or BWP configuration information. Specifically, the CORESET configuration may include the following information / fields:

[0121] - controlResourceSetId: Indicates the ID of CORESET.

[0122] - frequencyDomainResources: Represents the frequency domain resources of the CORESET. It is indicated through a bitmap, and each bit corresponds to an RB group (= 6 (consecutive) RBs). For example, the MSB (Most Significant Bit) of the bitmap corresponds to the first RB group in the BWP. The RB group corresponding to the bit with a bit value of 1 is allocated as the frequency domain resource of the CORESET.

[0123] - duration: Indicates the time domain resource of CORESET. It indicates the number of consecutive OFDM symbols that make up CORESET. Duration has a value of 1 to 3.

[0124] - cce-REG-MappingType: Indicates the mapping type between CCE (Control Channel Element) and REG. Interleaved and non-interleaved types are supported.

[0125] - interleaverSize: Indicates the interleaver size.

[0126] - pdcch-DMRS-ScramblingID: Indicates the value used for initializing PDCCH DMRS. If pdcch-DMRS-ScramblingID is not included, the physical cell ID of the serving cell is used.

[0127] - precoderGranularity: Indicates the precoder granularity in the frequency domain.

[0128] - reg-BundleSize: Indicates the REG bundle size.

[0129] - tci-PresentInDCI: Indicates whether the TCI (Transmission Configuration Index) field is included in the DL-related DCI.

[0130] - tci-StatesPDCCH-ToAddList: Indicates a subset of TCI states defined in the PDCCH configuration. TCI states are used to provide the Quasi-Co-Location (QCL) relationship between DL RS(s) and PDCCH DMRS ports within an RS set (TCI-state).

[0131] In addition, the base station can transmit a PDCCH SS (Search Space) configuration to the terminal (S504). The PDCCH SS configuration can be transmitted via higher layer signaling (e.g., RRC signaling). For example, the RRC signaling can include various signaling such as an RRC setup message, an RRC reconfiguration message, and / or BWP configuration information, but is not limited thereto. In FIG. 5, for convenience of explanation, the CORESET configuration and the PDCCH SS configuration are illustrated as being signaled separately, but the present invention is not limited thereto. For example, the CORESET configuration and the PDCCH SS configuration can be transmitted via a single message (e.g., a single RRC signaling) or can be transmitted separately via different messages.

[0132] A PDCCH SS configuration may include information regarding the configuration of a PDCCH SS set. A PDCCH SS set may be defined as a set of PDCCH candidates for which a terminal performs monitoring (e.g., blind detection). A terminal may be configured with one or more SS sets. Each SS set may be a USS set or a CSS set. For convenience, a PDCCH SS set may also be referred to simply as "SS" or "PDCCH SS" hereinafter.

[0133] A PDCCH SS set includes PDCCH candidates. A PDCCH candidate represents a CCE(s) monitored by a UE for PDCCH reception / detection. Here, monitoring includes blind decoding (BD) of PDCCH candidates. One PDCCH (candidate) consists of 1, 2, 4, 8, or 16 CCEs depending on the AL (Aggregation Level). One CCE consists of 6 REGs. Each CORESET configuration is associated with one or more SSs, and each SS is associated with one COREST configuration. One SS is defined based on one SS configuration, and an SS configuration may include the following information / fields.

[0134] - searchSpaceId: Indicates the ID of SS.

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

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

[0137] - monitoringSymbolsWithinSlot: Indicates the first OFDM 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 OFDM symbol within the slot. The MSB of the bitmap corresponds to the first OFDM symbol within the slot. The OFDM 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.

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

[0139] - searchSpaceType: Indicates CSS (Common Search Space) or USS (UE-specific search space) and the DCI format used in the corresponding SS type.

[0140] Thereafter, the base station generates and transmits a PDCCH to the terminal (S506), and the terminal can monitor PDCCH candidates in one or more SSs for PDCCH reception / detection (S508). 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.

[0141] Table 3 illustrates the characteristics of each SS type.

[0142] TypeSearch SpaceRNTIUse CaseType0-PDCCHCommonSI-RNTI on a primary cellSIB DecodingType0A-PDCCHCommonSI-RNTI on a primary cellSIB DecodingType1-PDCCHCommonRA-RNTI or TC-RNTI on a primary cellMsg2, Msg4 decoding in RACHType2-PDCCHCommonP-RNTI on a primary cellPaging DecodingType3-PDCCHCommonINT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, C-RNTI, MCS-C-RNTI, or CS-RNTI(s)UE SpecificC-RNTI, or MCS-C-RNTI, or CS-RNTI(s)User specific PDSCH decoding

[0143] 표 4는 PDCCH를 통해 전송되는 DCI 포맷들을 예시한다.

[0144] DCI formatUsage0_0Scheduling of PUSCH in one cell0_1Scheduling of PUSCH in one cell1_0Scheduling of PDSCH in one cell1_1Scheduling of PDSCH in one cell2_0Notifying a group of UEs of the slot format2_1Notifying a group of UEs of the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE2_2Transmission of TPC commands for PUCCH and PUSCH2_3Transmission of a group of TPC commands for SRS transmissions by one or more UEs

[0145] DCI format 0_0 is used to schedule a TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​can be used to schedule a TB-based (or TB-level) PUSCH or a CBG (Code Block Group)-based (or CBG-level) PUSCH. DCI format 1_0 is used to schedule a TB-based (or TB-level) PDSCH, and DCI format 1_1 can be used to schedule a TB-based (or TB-level) PDSCH or a CBG-based (or CBG-level) PDSCH (DL grant DCI). DCI format 0_0 / 0_1 may be referred to as UL grant DCI or UL scheduling information, and DCI format 1_0 / 1_1 may be referred to as DL grant DCI or DL ​​scheduling information. DCI format 2_0 is used to convey dynamic slot format information (e.g., dynamic SFI) to the terminal, and DCI format 2_1 is used to convey downlink pre-emption information to the terminal. DCI format 2_0 and / or DCI format 2_1 can be conveyed to the terminals within a group through the group common PDCCH, which is a PDCCH conveyed to the terminals defined as a group.

[0146] DCI format 0_0 and DCI format 1_0 may be referred to as fallback DCI formats, while DCI format 0_1 ​​and DCI format 1_1 may be referred to as non-fallback DCI formats. In the fallback DCI format, the DCI size / field configuration remains the same regardless of the terminal configuration. On the other hand, in the non-fallback DCI format, the DCI size / field configuration varies depending on the terminal configuration.

[0147] The mapping type from CCE to REG is set to either a non-interleaved CCE-REG mapping type or an interleaved CCE-REG mapping type.

[0148] - Non-interleaved CCE-REG mapping type (or localized mapping type) (Fig. 5): One REG bundle is composed of 6 REGs for a given CCE, and all REGs for a given CCE are contiguous. One REG bundle corresponds to one CCE.

[0149] - Interleaved CCE-REG mapping type (or Distributed mapping type): A REG bundle is composed of 2, 3, or 6 REGs for a given CCE, and the REG bundles are interleaved within a CORESET. A REG bundle within a CORESET composed of 1 or 2 OFDM symbols is composed of 2 or 6 REGs, and a REG bundle within a CORESET composed of 3 OFDM symbols is composed of 3 or 6 REGs. The size of the REG bundle is set for each CORESET.

[0150] Figure 6 illustrates a PDSCH reception and ACK / NACK transmission process. Referring to Figure 6, a terminal can detect a PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI formats 1_0, 1_1), and the PDCCH indicates a DL assignment-to-PDSCH offset (K0) and a PDSCH-HARQ-ACK reporting offset (K1). For example, DCI formats 1_0, 1_1 can include the following information:

[0151] - Frequency domain resource assignment: Indicates the set of RBs allocated to the PDSCH.

[0152] - Time domain resource assignment: K0 (e.g., slot offset), indicates the starting position of the PDSCH within slot #n+K0 (e.g., OFDM symbol index), and the length of the PDSCH (e.g., number of OFDM symbols).

[0153] - PDSCH-to-HARQ_feedback timing indicator: Indicates K1

[0154] - HARQ process number (4 bits): Indicates the HARQ process ID (Identity) for data (e.g., PDSCH, TB)

[0155] - PUCCH resource indicator (PRI): Indicates the PUCCH resource to be used for UCI transmission among multiple PUCCH resources within the PUCCH resource set.

[0156] Afterwards, the terminal receives PDSCH from slot #(n+K0) according to the scheduling information of slot #n, and when reception of PDSCH is finished in slot #n1 (where, n+K0≤n1), UCI can be transmitted through PUCCH in slot #(n1+K1). Here, UCI may include HARQ-ACK response for PDSCH. In Fig. 6, for convenience, it is assumed that SCS for PDSCH and SCS for PUCCH are the same and slot # n1 = slot #n+K0, but the present invention is not limited thereto. If the SCSs are different, K1 can be indicated / interpreted based on the SCS of PUCCH.

[0157] When the PDSCH is configured to transmit at most 1 TB, the HARQ-ACK response may consist of 1 bit. When the PDSCH is configured to transmit at most 2 TB, the HARQ-ACK response may consist of 2 bits if spatial bundling is not configured, and may consist of 1 bit if spatial bundling is configured. When the HARQ-ACK transmission timing for multiple PDSCHs is designated as slot #(n+K1), the UCI transmitted in slot #(n+K1) includes HARQ-ACK responses for multiple PDSCHs.

[0158] Whether a UE should perform spatial bundling for a HARQ-ACK response can be configured (e.g., via RRC / higher layer signaling) for each cell group. For example, spatial bundling can be individually configured for each HARQ-ACK response transmitted over the PUCCH and / or each HARQ-ACK response transmitted over the PUSCH.

[0159] Spatial bundling can be supported when the maximum number of TBs (or codewords) that can be received at a time (or scheduled via 1 DCI) in the serving cell is 2 (or more than 2) (e.g., when the upper layer parameter maxNrofCodeWordsScheduledByDCI corresponds to 2-TB). Meanwhile, more than 4 layers can be used for 2-TB transmission, and up to 4 layers can be used for 1-TB transmission. Consequently, when spatial bundling is configured for the cell group, spatial bundling can be performed for serving cells that can schedule more than 4 layers among the serving cells in the cell group. On the serving cell, a terminal that wishes to transmit a HARQ-ACK response via spatial bundling can generate the HARQ-ACK response by performing a (bit-wise) logical AND operation on the A / N bits for multiple TBs.

[0160] For example, assuming that a terminal receives a DCI scheduling 2 TB and receives 2 TB via PDSCH based on the DCI, the terminal performing spatial bundling can generate a single A / N bit by logically ANDing the first A / N bit for the first TB and the second A / N bit for the second TB. Consequently, if both the first TB and the second TB are ACKs, the terminal reports the ACK bit value to the base station, and if either TB is NACK, the terminal reports the NACK bit value to the base station.

[0161] For example, if only 1-TB is actually scheduled on a serving cell configured to receive 2-TB, the terminal can generate a single A / N bit by logically ANDing the A / N bit for the 1-TB with bit value 1. Consequently, the terminal reports the A / N bit for the 1-TB to the base station as is.

[0162] A base station / terminal has multiple parallel DL HARQ processes for DL ​​transmission. These multiple parallel HARQ processes allow DL transmissions to be performed continuously while waiting for HARQ feedback regarding the success or failure of the previous DL transmission. Each HARQ process is associated with a HARQ buffer in the MAC (Medium Access Control) layer. Each DL HARQ process manages state variables such as the number of transmissions of MAC Physical Data Blocks (PDUs) in the buffer, HARQ feedback for MAC PDUs in the buffer, and the current redundancy version. Each HARQ process is identified by a HARQ process ID.

[0163] Figure 7 illustrates a PUSCH transmission process. Referring to Figure 7, a terminal can detect a PDCCH in slot #n. Here, the PDCCH includes uplink scheduling information (e.g., DCI formats 0_0 and 0_1). DCI formats 0_0 and 0_1 can include the following information.

[0164] - Frequency domain resource assignment: Indicates the set of RBs allocated to PUSCH.

[0165] - Time domain resource assignment: Slot offset K2 indicates the starting position (e.g., symbol index) and length (e.g., number of OFDM symbols) of the PUSCH within the slot. The starting symbol and length can be indicated through SLIV (Start and Length Indicator Value) or can be indicated separately.

[0166] Thereafter, the terminal can transmit a PUSCH in slot #(n+K2) according to the scheduling information of slot #n. Here, the PUSCH includes a UL-SCH TB.

[0167] Paging

[0168] The network can (i) access UEs in RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states via paging messages, and (ii) notify UEs in RRC_IDLE, RRC_INACTIVE states, and RRC_CONNECTED states of system information changes and ETWS / CMAS (Earthquake and Tsunami Warning System / Commercial Mobile Alert System) indications via short messages. Both paging messages and short messages are transmitted based on PDCCH based on P-RNTI. Paging messages are transmitted on Paging Control Channel (PCCH), which is a logical channel, while short messages are transmitted directly on PDCCH, which is a physical channel. Since PCCH, which is a logical channel, is mapped to PDSCH, it can be understood that paging messages are scheduled based on P-RNTI based PDCCH.

[0169] While in RRC_IDLE, the UE monitors the paging channel for core network (CN)-initiated paging. In RRC_INACTIVE, the UE also monitors the paging channel for radio access network (RAN)-initiated paging. The UE does not need to continuously monitor the paging channel. Paging DRX is defined so that a UE in RRC_IDLE or RRC_INACTIVE monitors the paging channel for only one paging occasion (PO) per DRX cycle. The paging DRX cycle is configured by the network as follows:

[0170] 1) For CN-initiated paging, the basic cycle is broadcast through system information.

[0171] 2) For CN-initiated paging, the UE-specific period is set via NAS signaling.

[0172] 3) For RAN-initiated paging, a UE-specific period is set via RRC signaling.

[0173] Since the POs of UEs for CN-initiated and RAN-initiated paging are both based on the same UE ID, the two POs overlap. The number of POs in a DRX cycle can be configured through system information, and the network can distribute UEs to POs based on their IDs.

[0174] When in RRC_CONNECTED, the UE monitors the paging channel on each PO signaled in the system information for SI change indications and PWS notifications. For Bandwidth Adaptation (BA), the UE in RRC_CONNECTED only monitors the paging channel of the active BWP with the configured common search space.

[0175] For shared spectrum channel access, the UE may configure additional PDCCH monitoring occasions within its PO to monitor paging. However, if the UE detects a P-RNTI-based PDCCH transmission within its PO, the UE does not need to monitor subsequent PDCCH monitoring occasions within that PO.

[0176] The UE can use Discontinuous Reception (DRX) in RRC_IDLE and RRC_INACTIVE states to reduce power consumption. The UE monitors one Paging Opportunity (PO) per DRX cycle. A PO is a set of PDCCH monitoring Occasions, which may consist of multiple time slots (e.g., subframes or OFDM symbols) in which paging DCIs can be transmitted. A paging frame (PF) is a radio frame and may contain one or more PO(s) or the starting point of a PO.

[0177] In multi-beam operation, the UE assumes that the same paging message and the same short message are repeated on all transmit beams. The paging message is the same for both RAN-initiated paging and CN-initiated paging.

[0178] When the UE receives RAN-initiated paging, it initiates the RRC Connection Resume procedure. If the UE receives CN-initiated paging in RRC_INACTIVE state, the UE transitions to RRC_IDLE and notifies the NAS.

[0179] PF and PO for paging are determined as follows:

[0180] - SFN's decision on PF:

[0181] (SFN + PF offset ) mod T = (T div N)*(UE_ID mod N)

[0182] - Determination of index (i_s) representing the index of PO:

[0183] i_s = floor(UE_ID / N) mod Ns

[0184] The following parameters can be used in PF and i_s calculations:

[0185] - T: DRX cycle of the UE (T is determined by the shortest of the UE-specific DRX values ​​(if configured by RRC and / or higher layers) and the default DRX value broadcast in the system information; in RRC_IDLE state, the default value is applied if no UE-specific DRX is configured by higher layers).

[0186] - N: Total number of paging frames in T

[0187] - Ns: Number of POs in PF

[0188] - PF offset : Offset used to determine PF

[0189] - UE_ID: 5G-S-TMSI mode 1024

[0190] DRX (Discontinuous Reception)

[0191] (1) RRC_CONNECTED DRX

[0192] Figure 8 is a drawing for explaining the DRX operation of the terminal.

[0193] A terminal can perform DRX operation while performing the procedures and / or methods described / proposed above. A terminal configured for DRX can reduce power consumption by discontinuously receiving DL signals. DRX can be performed in the RRC (Radio Resource Control)_IDLE state, RRC_INACTIVE state, and RRC_CONNECTED state. In the RRC_IDLE state and RRC_INACTIVE state, DRX is used to discontinuously receive paging signals. Hereinafter, DRX performed in the RRC_CONNECTED state (RRC_CONNECTED DRX) will be described.

[0194] Referring to FIG. 8, a DRX cycle consists of an On Duration and an Opportunity for DRX. The DRX cycle defines the time interval at which the On Duration is periodically repeated. The On Duration represents the time period that the UE monitors to receive a PDCCH. When DRX is configured, the UE performs PDCCH monitoring during the On Duration. If a PDCCH is successfully detected during PDCCH monitoring, the UE starts an inactivity timer and remains awake. On the other hand, if no PDCCH is successfully detected during PDCCH monitoring, the UE enters a sleep state after the On Duration ends. Therefore, when DRX is configured, PDCCH monitoring / reception may be performed discontinuously in the time domain when performing the procedures and / or methods described / proposed above. For example, when DRX is configured, in one embodiment of the present invention, PDCCH reception occasions (e.g., slots having PDCCH search spaces) may be set discontinuously according to the DRX configuration. On the other hand, when DRX is not configured, PDCCH monitoring / reception may be performed continuously in the time domain when performing the procedures and / or methods described / proposed above. For example, when DRX is not configured, in one embodiment of the present invention, PDCCH reception occasions (e.g., slots having PDCCH search spaces) may be set continuously. On the other hand, PDCCH monitoring may be limited in a time interval set as a measurement gap, regardless of whether DRX is configured.

[0195] Table 5 shows the process of the terminal related to DRX (RRC_CONNECTED state). Referring to Table 5, DRX configuration information is received through upper layer (e.g., RRC) signaling, and whether DRX is turned on / off is controlled by the DRX command of the MAC layer. When DRX is configured, the terminal can perform PDCCH monitoring discontinuously when performing the procedure and / or method described / proposed in the present invention.

[0196] Type of signalsUE procedure1 st stepRRC signaling(MAC-CellGroupConfig)- Receive DRX configuration information2 nd StepMAC CE((Long) DRX command MAC CE)- Receive DRX command3 rd Step-- Monitor a PDCCH during an on-duration of a DRX cycle

[0197] Here, MAC-CellGroupConfig contains configuration information required to set MAC (Medium Access Control) parameters for a cell group. MAC-CellGroupConfig may also contain configuration information regarding DRX. For example, MAC-CellGroupConfig may contain the following information to define DRX: - Value of drx-OnDurationTimer: Defines the length of the start period of the DRX cycle.

[0198] - Value of drx-InactivityTimer: Defines the length of time period during which the terminal remains awake after a PDCCH opportunity is detected indicating initial UL or DL ​​data.

[0199] - Value of drx-HARQ-RTT-TimerDL: Defines the maximum time interval between the reception of a DL initial transmission and the reception of a DL retransmission.

[0200] - Value of drx-HARQ-RTT-TimerDL: Defines the maximum length of the time interval from when a grant for UL initial transmission is received until a grant for UL retransmission is received.

[0201] - drx-LongCycleStartOffset: Defines the time length and start point of the DRX cycle.

[0202] - drx-ShortCycle (optional): Defines the time length of the short DRX cycle.

[0203] Here, if any one of drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerDL is in operation, the terminal maintains an awake state and performs PDCCH monitoring at every PDCCH opportunity.

[0204] (2) RRC_IDLE DRX

[0205] In the RRC_IDLE and RRC_INACTIVE states, DRX is used to discontinuously receive paging signals. For convenience, DRX performed in the RRC_IDLE (or RRC_INACTIVE) state is referred to as RRC_IDLE DRX.

[0206] Therefore, when DRX is configured, PDCCH monitoring / reception may be performed discontinuously in the time domain when performing the procedures and / or methods described / proposed above.

[0207] Figure 9 illustrates a DRX cycle for paging.

[0208] Referring to FIG. 9, DRX can be configured for discontinuous reception of paging signals. The terminal can receive DRX configuration information from the base station through upper layer (e.g., RRC) signaling. The DRX configuration information can include configuration information for a DRX cycle, a DRX offset, a DRX timer, etc. The terminal repeats the On Duration and the Sleep duration according to the DRX cycle. The terminal can operate in wakeup mode in the On duration and in sleep mode in the Sleep duration.

[0209] In wake-up mode, a terminal may monitor a PO to receive a paging message. A PO refers to a time resource / period (e.g., a subframe, a slot) during which the terminal expects to receive a paging message. PO monitoring includes monitoring a PDCCH (or MPDCCH, NPDCCH) scrambled with a P-RNTI (hereinafter, paging PDCCH) in the PO. A paging message may be included in the paging PDCCH or included in a PDSCH scheduled by the paging PDCCH. One or more POs are included in a PF (Paging Frame), and the PF may be periodically configured based on a UE_ID. Here, a PF corresponds to one radio frame, and the UE_ID may be determined based on the IMSI (International Mobile Subscriber Identity) of the terminal. When DRX is configured, the terminal monitors only one PO per DRX cycle. When a terminal receives a paging message from a PO indicating a change in its ID and / or system information, the terminal may perform a RACH process to initialize (or re-establish) a connection with the base station, or receive (or acquire) new system information from the base station. Accordingly, when performing the procedures and / or methods described / proposed above, PO monitoring may be performed discontinuously in the time domain to perform a RACH process for connection with the base station, or to receive (or acquire) new system information from the base station.

[0210] Figure 10 illustrates an extended DRX (eDRX) cycle.

[0211] According to the DRX cycle configuration, the maximum cycle duration can be limited to 2.56 seconds. However, for terminals that perform intermittent data transmission and reception, such as MTC terminals or NB-IoT terminals, unnecessary power consumption may occur during the DRX cycle. To further reduce the power consumption of the terminal, a method has been introduced to significantly extend the DRX cycle based on the power saving mode (PSM) and the paging time window (PTW) or paging transmission window, and the extended DRX cycle is simply referred to as an eDRX cycle. Specifically, Paging Hyper-frames (PH) are periodically configured based on the UE_ID, and PTW is defined within the PH. The terminal can perform a DRX cycle during the PTW duration and switch to wakeup mode in its PO to monitor the paging signal. One or more DRX cycles (e.g., wakeup mode and sleep mode) of FIG. 9 may be included within the PTW duration. The number of DRX cycles within a PTW period can be configured by the base station via higher layer (e.g. RRC) signaling.

[0212] Wake-up signal (WUS) / Paging Early Indication (PEI)

[0213] In LTE Rel-15 NB-IoT and MTC, a wake-up signal (WUS) has been introduced for the purpose of power saving of terminals. The WUS is a signal that notifies in advance whether an actual paging transmission exists in a paging target search space of a specific location. When a base station wishes to transmit a paging to a PO (paging occasion) of a specific location, it can transmit the WUS to the WUS transmission location(s) associated with the PO. The terminal monitors the WUS transmission location associated with the PO of the specific location, and if a WUS is detected at the WUS transmission location, it can expect that a paging will be transmitted from the corresponding PO. If a WUS is not detected at the WUS transmission location, the terminal can obtain the benefit of power saving by not expecting a paging from the corresponding PO. In LTE Rel-16 NB-IoT and MTC, a terminal-group WUS has been introduced for the purpose of improving the power saving benefit of the Rel-15 WUS. Terminal-group WUS has the advantage of reducing the probability of unnecessary wake-up of the terminal by using the transmission location and sequence of WUS determined based on the terminal-group ID of the terminal.

[0214] Figure 11 is a diagram illustrating a WUS in an LTE system. Referring to Figure 11, in MTC and NB-IoT, a WUS can be used to reduce power consumption associated with paging monitoring. A WUS is a physical layer signal that indicates whether a terminal monitors a paging signal (e.g., MPDCCH / NPDCCH scrambled with P-RNTI) depending on the cell configuration. For a terminal that is not configured with eDRX (i.e., only DRX is configured), a WUS can be associated with one PO (N=1). On the other hand, for a terminal that is configured with eDRX, a WUS can be associated with one or more POs (N≥1). If a WUS is detected, the terminal can monitor N POs after being associated with the WUS. On the other hand, if a WUS is not detected, the terminal can remain in sleep mode by skipping PO monitoring until monitoring the next WUS. The terminal can receive configuration information for a WUS from a base station and monitor the WUS based on the WUS configuration information. The configuration information for a WUS may include, for example, a maximum WUS duration, the number of consecutive POs associated with the WUS, gap information, etc. The maximum WUS duration represents the maximum time period during which a WUS can be transmitted, and may be expressed as a ratio with the maximum number of repetitions (e.g., Rmax) associated with a PDCCH (e.g., MPDCCH, NPDCCH). A UE may expect repeated WUS transmissions within the maximum WUS duration, but the actual number of WUS transmissions may be less than the maximum number of WUS transmissions within the maximum WUS duration. For example, the number of WUS repetitions may be less for a UE within good coverage. Resources / opportunities during which a WUS can be transmitted within the maximum WUS duration are referred to as WUS resources. A WUS resource may be defined as a plurality of consecutive OFDM symbols and a plurality of consecutive subcarriers.A WUS resource can be defined as multiple consecutive OFDM symbols and multiple consecutive subcarriers within a subframe or slot. For example, a WUS resource can be defined as 14 consecutive OFDM symbols and 12 consecutive subcarriers. A terminal that detects a WUS does not monitor the WUS until the first PO associated with the WUS. If a WUS is not detected during the maximum WUS interval, the terminal does not monitor the paging signal in the POs associated with the WUS (or remains in sleep mode).

[0215] Even in communication systems such as NR, whether a terminal should monitor paging DCIs in a PO or whether paging DCIs are provided can be indicated through PEIs (e.g., sequence- or DCI-based Paging Early Indication). If the terminal successfully detects a PEI, it monitors the paging DCI (and / or the PDSCH carrying the paging message). If a PEI is not detected, the terminal can skip monitoring paging DCIs in the corresponding PO.

[0216] Receive and activate LP-WUS configuration

[0217] In this specification, Main Radio is abbreviated as MR and low-power Wake-up Receiver (LP-WUR) is abbreviated as LR, following the terminology used in standardization discussions related to low-power Wake-up Signal (LP-WUS).

[0218] MR refers to a general receiver for receiving signals at NR terminals, and MR can be used to receive NR OFDM signals, etc. In other words, the terminal's receiver in the current NR standard can be understood as the main radio.

[0219] LP-WUR refers to a receiver that can be newly added to a terminal to receive low-power signals, and newly designed low-power signals such as LP-WUS or LP-SS can be received through LP-WUR. LP-WUR can have the characteristics of low cost and low power consumption compared to MR.

[0220] Specifically, according to the current NR standard, the terminal must wake up periodically for every DRX cycle, which accounts for a large portion of the power consumption during periods when there is no signal or information transmission. If the terminal can wake up only when triggered (e.g., to perform a paging operation), the terminal's power consumption can be significantly reduced. To this end, LP-WUS can be used to trigger the MR, which is normally asleep to save power consumption, and LP WUS can be received by introducing a separate receiver, LR, which can operate with ultra-low power consumption.

[0221] LR signals, such as LP-WUS or LP-SS, can be configured / transmitted differently from MR signals in the time / frequency axis. For example, LR signals, such as LP-WUS / LP-SS, can be modulated with OOK (On-Off Keying). OOK-modulated LR signals are aligned with the boundaries of time resources (e.g., slots or symbols in the time axis), but can be transmitted without being aligned with the boundaries of frequency resources (e.g., REs, subcarriers, etc. in the frequency axis). For example, LP-WUS can be configured to indicate the presence / absence (1 / 0) of a signal within a specific time interval, and a terminal can receive the LP-WUS signal only by energy detection (or envelope detection) of the LP-WUS within the specific time interval.

[0222] The OOK symbols of these LP-WUSs may be overlaid with i) a sequence for spectrum flattening, ii) an OFDM sequence for increasing transmission coverage, and / or iii) an OFDM sequence for transmitting additional information. In the case of ii) / iii), the LR signal may be an OOK sequence detectable through envelope detection, and the On symbols of the sequence may be composed of OFDM modulation symbols. In particular, in the case of iii), if OFDM demodulation is possible for the OFDM overlaid OOK sequence, additional meaningful information bits may be obtained.

[0223] Thus, the LR signal can be either a regular OOK signal (without overlaid OFDM) or an OFDM overlaid OOK signal. The LP-WUR of the terminal can be defined by distinguishing between two types.

[0224] - LP-WUR Type #1: Wake-up receiver capable of energy detection only

[0225] - LP-WUR Type #2: Wake-up receiver capable of OFDM sequence detection

[0226] LP-WUR Type #1 is a wake-up receiver that is configured for low cost and can only determine the presence or absence of a signal (energy detection or envelope detection). Therefore, it is a receiver that can only detect an OOK signal (e.g., a general OOK signal or an OOK signal portion excluding the overlaid OFDM in an OFDM overlaid OOK signal).

[0227] LP-WUR Type #2 is a wake-up receiver that can detect OFDM sequences at a higher cost than Type #1 and also supports energy detection. Therefore, it is a receiver that can detect / decode not only general OOK signals without overlaid OFDM, but also OFDM-overlaid OOK signals. It can also receive PSS / SSS of existing NR signals.

[0228] Terminals must perform RRM measurements via the MR at specific intervals. Replacing at least some of these RRM measurements on the MR with RRM measurements utilizing LP-WUR can significantly reduce terminal power consumption. In other words, if the MR can be powered off (or sleep) for extended periods without activating and performing RRM measurements at specific intervals, it can significantly reduce terminal power consumption.

[0229] Several alternatives for LR architecture are being discussed, which could result in different power consumption during LR's "on" and "off" states. Consequently, if LR's "on" state power consumption is significant enough to be negligible, or for other reasons, the terminal may be required to activate or deactivate LR.

[0230] Additionally, procedures and operations for receiving settings for LP-WUS reception after a terminal initially connects to a serving cell may be defined. The terminal may receive LP-WUS-related settings and define the necessary operations for receiving them using LR.

[0231] Since MR wake-up requires a lot of energy and time, reducing the number of MR wake-ups and the time it takes to wake up and operate is advantageous in terms of power saving of the terminal. To this end, after the terminal initially accesses a cell, it can receive settings such as whether the cell supports LP-WUS-related operations, and if so, the procedure for performing them, and the time / frequency resources for transmitting LP-WUS. An operation can be defined in which the terminal receives LP-WUS-related settings and then receives an indication from the cell whether LP-WUS is currently actually supported or whether support has been discontinued.

[0232] In this disclosure, when a terminal supports an operation utilizing LP-WUS (i.e., supports LP-WUR), we propose an operation for setting whether a cell supports LP-WUS transmission and for activating / deactivating LP-WUS reception in the cell.

[0233] The following description is based on periodic or receivable LP-WUS (and LP-SS), but the scope of the rights is not limited thereto and can be applied to all signals provided periodically. The application of the proposed methods is not limited to NR systems. The distinction between each method or option in the following description is intended to clarify the description and is not to be construed as limiting the meaning that each must be implemented as an independent invention. For example, the methods / options described below can be implemented individually, but at least some of them can also be implemented in a combined form as long as they do not conflict with each other.

[0234] [Proposal 1] Signaling of LP-WUS (and LP-SS) related configuration information in the serving cell.

[0235] The terminal proposes signaling of configuration information related to whether the current serving cell supports LP-WUS-related operations and, if so, whether the current serving cell supports LP-WUS-related operations.

[0236] When a terminal initially accesses a new cell or performs a handover, it receives system information of the cell. To this end, the terminal utilizes MR to receive minimum information blocks (MIB and SIB1). Other system information (other system information: OSI) may be periodically broadcast or transmitted in a specific manner to the terminal. If the terminal supports LR, the terminal may receive a system information block (SIB) containing settings related to LP-WUS transmission. For this purpose, a new SIB containing settings related to LP-WUS transmission may be defined, and is simply referred to as SIB_LP in this disclosure.

[0237] In other words, if the terminal supports LR, after receiving the MIB, it can receive the OSI related SIB (SIB_LP) (broadcast or transmitted by request) to receive the settings related to LP-WUS transmission. At this time, SIB_LP can receive information on LP-SS, which is a reference signal that can be received through LP-WUR. For example, it can include waveform information constituting LP-SS, information on time / frequency resources of LP-SS, etc. For example, the waveform information can include information on whether only the OOK signal is supported as the LP-SS( / WUS) signal or whether the OFDM overlaid OOK signal is also supported. And / or, the waveform information can include information on whether the signal is an OOK signal or an OFDM overlaid OOK signal. In addition, the settings for LP-WUS can be received. In addition to waveform information constituting the LP-WUS and information about the time / frequency resources of the LP-WUS, information about the activation / deactivation operation of the LP-WUS may be included. Information about the activation / deactivation operation of the LP-WUS is related to activation / deactivation from the perspective of the base station / network, and may include information such as the cell being capable of supporting LP WUS but not currently supporting it.

[0238] LP-SS-related settings can be determined independently of system information receivable via MR. For example, when a UE initially attaches to a new cell, it utilizes the synch raster when searching for SSB transmitted from that cell. That is, candidate locations where SSB can be transmitted are predetermined for the cell, and these can be used to find and receive SSB transmission locations via MR. Similarly, the UE can utilize information such as the predetermined synch raster to receive LP-SS using LR. Therefore, the UE can find and receive LP-SS via LR in parallel with the process of finding and receiving SSB via MR. The synch raster information at this time can be set to be the same as or different from that for SSB. Alternatively, the LP-SS transmission location can be determined based on the SSB. If the UE accurately locates the SSB, the possible locations for LP-SS transmission can be determined based on this, and the UE can receive this using LR.

[0239] The terminal can receive LP-WUS reception information (e.g., time / frequency resources of LP-WUS, transmission cycle, etc.) through SIB_LP as described above. The terminal can receive LP-SS based on the settings received through SIB_LP. LR synchronization can be achieved by receiving LP-SS, and synchronization information of MR can also be used as an auxiliary. Based on this information, the terminal can know the transmission location and cycle of LP-WUS and receive LP-WUS based on this. For example, if the terminal can obtain LR synchronization information through assistance of MR, it can be expected to receive LP-WUS after a small number of LP-SS receptions or without receiving LP-SS.

[0240] Alternatively, the transmission of LP-WUS may not be semi-static but may be changed by the base station. In this case, the terminal may consider obtaining information related to the transmission of LP-WUS through LP-SS. That is, SIB_LP may contain transmission information of LP-SS that may be semi-static, and LP-SS may contain information related to LP-WUS. This may be for the scheduling flexibility of the base station related to LP-WUS.

[0241] [Proposal 2] Terminals in IDLE / INACTIVE mode enable / disable LP-WUS reception

[0242] Proposal 1 allows a terminal to receive settings for LP-WUS reception from a serving cell and operate accordingly, and LP-WUS reception operations can be activated or deactivated by specific conditions or instructions. LP-WUS reception operations can be activated / deactivated by the base station, by the terminal, or by the terminal itself if specific conditions are met.

[0243] For example, a UE in RRC IDLE / INACTIVE mode can autonomously decide whether to receive LP-WUS provided by the cell. From the network / base station's perspective, such autonomous decisions made by the UE in IDLE / INACTIVE mode may not be known, and thus the base station may need to consider both LP WUS of the MR's PEI and LR.

[0244] Meanwhile, as described below, in RRC Connected mode, the terminal may decide, but the network / base station may also explicitly instruct the terminal whether to receive LP WUS. The terminal's autonomous decision may also be reported to the network / base station.

[0245] The LP-WUS reception operation being activated / deactivated by the base station may be an operation to notify whether LP-WUS is transmitted in the corresponding cell. This may not directly instruct the IDLE / INACTIVE mode terminal whether to receive LP-WUS, but may be an operation to notify that LP-WUS is being transmitted in the corresponding cell and that the terminal can utilize it. Accordingly, the terminal can decide whether to receive and utilize LP-WUS based on the information. For example, the terminal may receive LP-WUS to determine whether to page in the corresponding DRX cycle, or may receive PEI without receiving LP-WUS to determine whether to page. Alternatively, the terminal may wake up every DRX cycle and perform paging.

[0246] Activation / deactivation by the base station can be indicated by the SIB (SIB_LP) proposed in Proposal 1 above. The terminal can know whether LP-WUS is supported in the corresponding cell through the SIB and can decide whether to receive LP-WUS based on this. Therefore, the terminal's system information may need to be updated to notify the base station of LP-WUS activation / deactivation. Alternatively, the terminal can be notified via a dedicated RRC whether it can receive LP-WUS in the current cell.

[0247] Activation / deactivation by the base station can be notified through information in the reference signal that can be received as LP-WUR. The terminal needs to receive the reference signal (e.g., LP-SS) to obtain LR synchronization, and the reference signal may include information on activation / deactivation of LP-WUS. For example, when the terminal receives the configuration related to LP-SS, information related to dynamic activation / deactivation may also be included. This may be an instruction to deactivate LP-WUS during a specific period, such as a number of system frames or a number of DRX cycles, when LP-WUS is normally transmitted within the cell. Or, conversely, it may be an instruction to activate LP-WUS during a specific period, when LP-WUS is not transmitted within the cell. Alternatively, whether LP-WUS is transmitted within the cell may explicitly indicate whether it is activated / deactivated.

[0248] Alternatively, the LP-WUS may include an indication that further LP-WUS transmissions are to be deactivated. Such reference signal-based or LP-WUS-based activation / deactivation indications may be relatively more dynamic than SIB or dedicated RRC-based indications. The UE is instructed that there will be no further LP-WUS transmissions for a certain period after receiving the LP-WUS, and the UE can decide whether to receive further LP-WUS based on this information. This deactivation indication may be for the entire cell, or may be limited to a UE or a group of UEs (or subgroups) with a specific ID. This may vary depending on what information the LP-WUS contains. For example, normally, LP-WUS is transmitted within the cell, but the LP-WUS transmission may be deactivated for a certain period after the reception time, for example, for a number of system frames or DRX cycles, through an indication within the LP-WUS. Based on this, the terminal can turn off LR during these periods to save power consumption.

[0249] Additionally, the base station's LP-WUS transmission may be activated based on a terminal's request. It may be considered that the terminal can signal whether it supports LP-WUR through a random access process, etc. This allows the base station to transmit or not transmit LP-WUS based on the presence of a terminal supporting LP-WUR within the cell and the terminal's request for LP-WUS support.

[0250] A terminal can determine whether to receive LP-WUS in a given cell based on certain conditions. The terminal can determine the reception operation based on the coverage of the LP-WUS. In the case of LR, since it is designed for low cost and low power consumption, its coverage may generally be insufficient compared to MR. In other words, if the terminal has poor cell coverage, such as at the cell edge, it may be able to fully receive signals that can be received through MR, but signals that can be received through LR may have insufficient coverage. In this case, continuous reception of LP-WUS using LR may be wasteful in terms of power consumption, so the reception operation of LP-WUS can be stopped. This criterion (or condition) can be set to stop LP-WUS reception using LR because the probability of fully receiving LP-WUS is low even after repeated reception using LR. The criterion can be determined based on LP-SS or LP-WUS. If a terminal cannot completely receive an LP-SS or LP-WUS even after repeatedly receiving it N or more times using LR, it can disable LR and receive it only using MR. In this operation, the terminal may additionally report to the base station that it is not receiving LP-WUS. This may be to assist the base station in determining whether to transmit LP-WUS within the cell.

[0251] The LP-WUS reception operation using the LR of the terminal can also be determined by the state of the MR. When the terminal receives the LP-WUS, it means that the LR is turned on, and this can be determined by whether the MR is on or asleep. For example, if the terminal turns on the MR, the LR may be automatically deactivated (off or asleep). This can be because the main function of the LR of the terminal is to receive the LP-WUS and activate the MR, and after successfully performing this operation, it is deactivated to save power consumption. The ultra-deep sleep state of the MR can also be considered so that it can be switched only when the LR is in the 'on' state. This assumption may be desirable because when the MR is in the ultra-deep sleep state, the terminal can only activate the MR by receiving the LP-WUS using the LR. If LR can be set to be disabled even when MR is in ultra-deep sleep, it may be considered to set MR to be automatically enabled after a certain period of time.

[0252] LR can be activated and deactivated based on the transmission cycle of LP-WUS. If LP-WUS is transmitted periodically, LR can be activated or deactivated accordingly. To achieve this, synchronization may be required through LP-SS reception for a certain period of time before and after the corresponding point in time to obtain LR synchronization information.

[0253] [Proposal 3] Terminal in CONNECTED mode activates / deactivates LP-WUS reception

[0254] A terminal in RRC_CONNECTED mode can have LP-WUS reception enabled or disabled by specific conditions or instructions such as network signaling. When C-DRX is configured for a terminal in CONNECTED mode, an instruction to wake up DRX can be received via LP-WUS, and an instruction to control PDCCH monitoring within C-DRX can be received.

[0255] The LP-WUS reception activation and deactivation instructions for terminals in CONNECTED mode can be utilized in the same manner as the instructions for terminals in IDLE / INACTIVE mode proposed in Proposal 2, for example, SIB or RRC-based, LP-SS-based, or LP-WUS-based. In addition, terminals in CONNECTED mode can receive dynamic instructions via DCI. In addition, activation and deactivation can be determined based on different conditions than in IDLE / INACTIVE mode.

[0256] A UE in RRC_CONNECTED mode may not receive LP-WUS after the DRX Active Time starts. In other words, LR may be deactivated after the DRX Active Time starts. If the UE monitors LP-WUS based on duty-cycle, the transmission cycle of LP-WUS may be the same as the configured cycle of C-DRX. In this case, LP-WUS can be assumed to play a similar role to Rel-16 WUS that instructs the UE to start C-DRX. Therefore, the monitoring occasion of LP-WUS can be set according to the C-DRX cycle of the UE, and based on this, the UE can consider activating LR to receive LP-WUS. If a UE in CONNECTED mode can utilize MR as an auxiliary for LR synchronization, there is no need to receive any more reference signals for synchronization, and fast activation and deactivation operations may be possible.

[0257] The transmission cycle of LP-WUS can be set smaller than the cycle of C-DRX. In this case, the terminal operation may differ depending on whether the monitoring opportunity of LP-WUS is within or outside the DRX Active Time. For example, an LP-WUS received in a monitoring opportunity outside the DRX Active Time can be used to wake-up the C-DRX. Depending on the setting, LR activation / deactivation within the DRX Active Time can be determined, and the operation performed by receiving LP-WUS with LR may differ accordingly. If LR is activated within the DRX Active Time, an LP-WUS that can be monitored within the Active Time can instruct PDCCH monitoring adaptation (monitoring adaptation) within the DRX Active Time.

[0258] The terminal may consider reporting to the base station whether or not it has received LP-WUS within the DRX Active Time. This may be to inform the base station that the terminal has successfully received LP-WUS, thereby indicating that the terminal is not currently unable to properly receive LP-WUS due to issues such as coverage.

[0259] A terminal can report to the base station whether it will monitor LP-WUS within the C-DRX Active Time. This allows the base station to determine whether to instruct the terminal to perform operations via LP-WUS within the DRX Active Time.

[0260] Consider a case where a terminal continuously monitors LP-WUS. In this case, the LP-WUS reception activation / deactivation instructions that can be issued to a terminal in IDLE / INACTIVE mode can be similarly utilized. For example, instructions included in LP-SS or LP-WUS can be received to deactivate for a certain period of time or until reactivation, or can be activated / deactivated under certain conditions.

[0261] Since the UE always monitors LP-WUS, it can notify the base station whether it will receive LP-WUS (or disable LR) within the Active Time through a report after the start of C-DRX Active Time. Based on the report of the UE, the base station can decide whether to transmit an instruction through LP-WUS to the UE. For example, if the UE reports that it will continue to receive LP-WUS even after the start of C-DRX Active Time, the base station can transmit a PDCCH monitoring adaptation instruction through LP-WUS in addition to transmitting a PDCCH monitoring adaptation instruction through DCI. If the UE reports that it will not receive LP-WUS (will disable LR) after the start of C-DRX Active Time, the base station can only transmit an instruction through DCI.

[0262] An action to deactivate LR under certain conditions without reporting from the terminal may be configured. For example, LR may be automatically deactivated after the terminal starts C-DRX. This may be because LP-WUS is used as a signal to wake up the terminal's DRX Active Time. Alternatively, an action may be considered to deactivate LR after a certain period of time has passed since the start of C-DRX Active Time, or to activate LR before a certain period of time has passed before the end of DRX Active Time.

[0263] It is conceivable that the base station may instruct the terminal to activate LP-WUS reception via DCI, a dedicated RRC, or LP-WUS. This instruction implies that the terminal can decide to receive LP-WUS since it is transmitted in the corresponding cell. These instructions can be configured in a similar manner to the instructions for IDLE / INACTIVE mode in Proposal 2.

[0264] [Proposal 4] Determining whether LP-WUS reception is activated based on low-power signals

[0265] We propose a method for utilizing low-power signals to determine the activation of LP-WUS reception. Low-power signals refer to signals that can be received by low-power receivers, such as LP-WUS and LP-SS.

[0266] The terminal can measure cell quality by receiving LP-SS in the MR and determining whether to switch the MR to an ultra-deep sleep state and operate the LR to activate reception of LP-WUS. In other words, the terminal can introduce an operation of receiving and measuring LP-SS in the MR to determine whether reception coverage for LP-WUS is sufficiently good.

[0267] The activation of LP-WUS in the terminal can be determined as follows. The terminal receives SSB in the same manner as before and measures cell quality with the MR. If the result satisfies the condition, the terminal receives LP-SS with the MR and measures cell quality. This may be to determine whether the coverage of LP-SS and LP-WUS received with the LR where the terminal actually operates is sufficient to allow smooth reception when LP-WUS reception is activated. Afterwards, if the MR enters an ultra-deep sleep state, the LR receives LP-SS and performs RRM measurement to ensure that the requirement is satisfied.

[0268] The LP-WUS activation threshold can be used by the base station to indirectly indicate how the terminal will operate. For example, if the threshold is a value that is sufficiently achievable based on the terminal's current conditions, the terminal will automatically activate LP-WUS reception when the conditions set by the base station are met. If the base station sets the threshold to a value that the terminal cannot achieve, the terminal may remain LP-WUS reception disabled until receiving separate instructions from the base station.

[0269] A terminal can request the base station to activate LP-WUS transmission. For example, a terminal in inactive mode can utilize SDT (small data transmission), or a terminal in idle mode can perform a RACH to activate LP-WUS transmission using a differentiated preamble, similar to how it requests an on-demand SIB.

[0270] The proposed method allows the terminal to transition the MR to ultra-deep sleep state more quickly instead of waiting for the next SSB transmission to perform measurements with LP-SS to satisfy the RRM measurement requirement, which can benefit the terminal's power consumption.

[0271] The proposed method can be utilized even when MR and LR are operating simultaneously. For example, in addition to SSB-based measurements performed on MR, LP-SS-based measurements performed on LR can be performed in parallel to satisfy RRM measurement requirements. This may vary depending on the activation power consumption of LR. That is, if LR can operate with sufficiently low power, performing RRM measurements in parallel using LR may be beneficial from a terminal operation perspective.

[0272] [Proposal 5] Determining whether to activate LP-WUS reception based on MR's behavior

[0273] Activation of the LR for LP-WUS reception operation can be determined based on the operation of the MR. When the MR is not activated (e.g., in a sleep state), LP-WUS reception can always be activated and operational. This may be so that a terminal equipped with the LR can receive LP-WUS on the LR when the MR is deactivated, thereby triggering the activation of the MR (wake-up indication). When the MR is activated, LP-WUS reception operation can be deactivated.

[0274] Meanwhile, LP-WUS reception may be activated even when MR is activated. This may be an operation to receive dynamic instructions via LP-WUS even when the terminal operates as MR and monitors the PDCCH. To this end, monitoring occasions for LP-WUS reception may be set, and the LP-WUS reception operation may be configured to be performed periodically.

[0275] For LRs capable of receiving OFDM sequences (e.g., OFDM overlaid sequences), when MR is enabled, only operations for OFDM sequence reception (e.g., OFDM sequence detection) may be disabled, while operations for OOK signal reception (e.g., energy detection) may be performed. These operations may be performed sequentially based on a timer, and operations for OOK signal reception may also be terminated / disabled after the timer expires.

[0276] For example, whether LP-WUS reception is enabled / disabled may be determined in relation to the DRX timer of the terminal (e.g., the DRX timer for MR operation). The MR activation operation of a terminal configured with C-DRX may be based on the DRX Active Time, and whether LP-WUS reception is enabled / disabled may be determined by the DRX timer related thereto.

[0277] Meanwhile, referring to the current NR standard document TS 38.321, the DRX Active Time of the terminal is defined as in Table 6.

[0278] When DRX is configured, the Active Time for Serving Cells in a DRX group includes the time while:- drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or- drx-RetransmissionTimerDL, drx-RetransmissionTimerUL or drx-RetransmissionTimerSL is running on any Serving Cell in the DRX group; or- ra-ContentionResolutionTimer (as described in clause 5.1.5) or msgB-ResponseWindow (as described in clause 5.1.4a) is running; or- a Scheduling Request is sent on PUCCH and is pending (as described in clause 5.4.4 or 5.22.1.5).If this Serving Cell is part of a non-terrestrial network, the Active Time is started after the Scheduling Request transmission that is performed when the SR_COUNTER is 0 for all the SR configurations with pending SR(s) plus the UE-gNB RTT; or- a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successful reception of a Random Access Response for the Random Access Preamble not selected by the MAC entity among the contention-based Random Access Preamble (as described in clauses 5.1.4 and 5.1.4a).

[0279] When drx-onDurationTimer and drx-InactivityTimer are running, LP-WUS reception may be disabled. Since drx-onDurationTimer and drx-InactivityTimer are timers that start when the UE first initiates DRX and after receiving a DCI indicating a new transmission, the UE may not control PDCCH monitoring of the MR through LP-WUS reception. For example, the UE can fully perform PDCCH monitoring with the MR when these timers are running.

[0280] For example, when a retransmission timer for MR (e.g., drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-RetransmissionTimerSL) is running, LP-WUS reception may be activated. When LP-WUS reception is activated and the retransmission timer is running, the UE may perform PDCCH monitoring only for some SS sets, rather than all SS sets. In this way, the UE operates while reducing power consumption by monitoring only some SS sets related to retransmission, but when an LP-WUS is received, the UE may activate monitoring of (another) SS sets where DCI related to the new transmission may be received. This act of activating monitoring of (another) SS sets may be related to SSSG switching. For example, the UE may be configured / instructed to monitor an SS set belonging to SSSG1 when the retransmission timer is running, and to monitor an SS set belonging to SSSG2 when an LP-WUS is received. When the retransmission timer is running, LP-WUS reception may be disabled. This may be the same behavior as when LP-WUS reception is disabled when drx-onDurationTimer and drx-InactivityTimer are running.

[0281] Even when ra-ContentionResolutionTimer and msgB-ResponseWindow related to random access are running, the terminal may operate in the same manner as the terminal operation related to the retransmission timer described above. For example, when the random access timer is running, LP-WUS reception may be activated in the terminal. At this time, the terminal may only monitor some SS sets from which messages related to random access (e.g., msg2, msg4, msgB) may be expected in the MR, but monitoring for other SS sets may be activated as LP-WUS is received. When the retransmission timer is running, LP-WUS reception may be disabled. This may be the same as the operation in which LP-WUS reception is disabled when another DRX timer is running.

[0282] For example, LP-WUS reception can be activated / deactivated based on UL transmission on the MR of the terminal. If the scheduling request (SR) transmission of the terminal is pending, the MR of the terminal can be activated and LP-WUS reception can be deactivated if it is determined to be DRX Active Time. If the terminal transmits a CG PUSCH, whether it is DRX Active Time can be determined based on the retransmission timer, and the terminal can operate in the same manner as the terminal operation described above with respect to the retransmission timer.

[0283] Through this disclosure, a terminal can receive information about whether a cell supports LP-WUS and configure related actions. Based on instructions / configurations from a base station, the terminal can determine whether LP-WUS is received in the cell and configure subsequent actions based on this information. Furthermore, the terminal can receive LP-WUS or configure actions based on specific conditions and perform actions accordingly.

[0284] Here is a brief summary of what we have discussed above. Recently, the introduction of LR has been discussed as a means of power saving of terminals, but since LR operates at low power compared to MR, its coverage is expected to be relatively small. The activation / deactivation of LR needs to be controlled considering its coverage, etc. In relation to the activation / deactivation of LR, i) whether LP-WUS (and LP-SS) is supported from the network's perspective and network signaling of LP-WUS (and LP-SS) related settings, ii) LP-WUS activation / deactivation of RRC IDLE / INACTIVE terminals, and iii) LP-WUS activation / deactivation of RRC CONNECTED terminals were explained, and in addition, a method for determining LP-WUS activation based on a low-power signal was explained.

[0285] Fig. 12 is a diagram for explaining the operation of a network and a terminal according to one embodiment.

[0286] Referring to FIG. 12, the network can determine settings related to an LR signal that can be received at a lower power than an MR signal at a terminal (A05). The settings related to the LR signal can include at least one of information about time and frequency resources of the LR signal, or information about activation / deactivation of the LR signal in the waveform of the LR signal. The LR signal can include at least one of an LP WUS and an LP SS. The LP SS can be configured differently from the MR SS. For example, the LP SS can be determined based on the location of an SSB including the MR SS. The network can transmit settings related to the LR signal through system information (A10). The terminal can receive the system information through the MR.

[0287] The terminal can determine whether to monitor the LR signal in the RRC inactive / idle mode (A15). The terminal can determine whether to monitor the LR signal on its own based on system information (A10) including settings related to the LR signal (A20). For example, the terminal can determine whether to monitor the LR signal based on the measurement quality of the MR signal. The measurement of the MR signal can include at least one of the MR SS or the LR SS. Based on the decision to monitor the LR signal, the terminal can request the network to transmit the LR signal (A25). For example, the request for transmission of the LR signal can be performed through a random access procedure. The network can transmit the LR signal based on the request of the terminal (A30). Meanwhile, FIG. 12 illustrates an example in which LR signal transmission (A30) is performed based on a request (A25) of a terminal (e.g., random access), but depending on the embodiment, transmission / reception / monitoring of LR signals may be performed without a request (A25) of a terminal, and in this case, the request (A25) of the terminal or the LR signal transmission process (A30) provided based on the request illustrated in FIG. 12 may be omitted / changed.

[0288] The network can transmit information (A40) regarding whether the terminal should monitor the LR signal while operating in RRC connected mode (A35). The network can transmit the LR signal to the terminal (A45). The terminal can monitor the LR signal based on the network's instructions (A50).

[0289] FIG. 13 illustrates a flowchart of a method for a terminal to receive a signal in a wireless communication system according to one embodiment.

[0290] Referring to FIG. 13, the terminal can receive system information including settings related to WUS (wake up signal) through the first receiving operation (B05).

[0291] The terminal may include determining, based on the system information, whether to perform monitoring of the WUS through a second receiving operation that consumes lower power than the first receiving operation (B10).

[0292] The settings related to the above WUS may include information about the waveform of the above WUS.

[0293] The settings related to the above WUS may include at least one of information on time and frequency resources of the above WUS, or information on activation / deactivation of the above WUS.

[0294] The above system information may further include settings related to a second synchronization signal for synchronization in the second receiving operation.

[0295] The second synchronization signal may be set differently from the first synchronization signal for synchronization in the first receiving operation.

[0296] The position of the second synchronization signal can be determined based on the position of a synchronization signal block (SSB) including the first synchronization signal.

[0297] The terminal can determine by itself whether to perform monitoring of the WUS based on whether the terminal operates in an RRC (radio resource control) idle / inactive state.

[0298] The terminal may perform a random access process to request transmission of the WUS to the network based on the decision to perform monitoring of the WUS.

[0299] Whether or not monitoring of the WUS should be performed while the terminal is operating in an RRC connection state can be explicitly set via network signaling.

[0300] Based on the quality of the signal measured through the first receiving operation, it can be determined whether to perform monitoring of the WUS through the second receiving operation.

[0301] The signal measured through the first receiving operation may include at least one of a first synchronization signal for synchronization in the first receiving operation or a second synchronization signal for synchronization in the second receiving operation.

[0302] FIG. 14 illustrates a flowchart of a method for a base station to transmit a signal in a wireless communication system according to one embodiment.

[0303] Referring to FIG. 14, the base station can determine settings related to a wake up signal (WUS) to support a second reception operation that consumes lower power than the first reception operation of the terminal (C05).

[0304] The base station can transmit system information including settings related to the above WUS (C10).

[0305] The base station can transmit the WUS based on the settings related to the WUS (C15).

[0306] The settings related to the above WUS may include information about the waveform of the above WUS.

[0307] The settings related to the above WUS may include at least one of information on time and frequency resources of the above WUS, or information on activation / deactivation of the above WUS.

[0308] The above system information may further include settings related to a second synchronization signal for synchronization in the second receiving operation.

[0309] The second synchronization signal may be set differently from the first synchronization signal for synchronization in the first receiving operation.

[0310] The position of the second synchronization signal can be determined based on the position of a synchronization signal block (SSB) including the first synchronization signal.

[0311] Whether or not monitoring of the WUS should be performed while the terminal is operating in an RRC connection state can be explicitly set via network signaling.

[0312] Fig. 15 illustrates a communication system (1) applicable to the present disclosure.

[0313] Referring to FIG. 15, a communication system (1) applied to the present disclosure 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.

[0314] 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).

[0315] 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.

[0316] Figure 16 illustrates a wireless device applicable to the present disclosure.

[0317] Referring to FIG. 16, 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. 16.

[0318] 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 / chip designed to implement a 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 one embodiment of the present invention, the wireless device may mean a communication modem / circuit / chip.

[0319] 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 a 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 receiver included in the transceiver (206) may include a first receiver (MR) supporting a first type of waveform (e.g., OFDM) and a second receiver (LR) supporting a second type of waveform (e.g., OOK). The second receiver may consume less power than the first receiver. The transceiver (206) may be used interchangeably with an RF unit.In one embodiment of the present invention, the wireless device may mean a communication modem / circuit / chip.

[0320] 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) may generate signals (e.g., baseband signals) comprising 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) may 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.

[0321] 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.

[0322] 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.

[0323] 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.

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

[0325] Referring to FIG. 17, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 16 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. 16. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 16. 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).

[0326] 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. 16, 100a), a vehicle (Fig. 16, 100b-1, 100b-2), an XR device (Fig. 16, 100c), a portable device (Fig. 16, 100d), a home appliance (Fig. 16, 100e), an IoT device (Fig. 16, 100f), a terminal for digital broadcasting, 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. 16, 400), a base station (Fig. 16, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0327] In FIG. 17, 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.

[0328] Figure 18 illustrates a vehicle or autonomous vehicle applicable to the present disclosure. The vehicle or autonomous vehicle may be implemented as a mobile robot, a car, a train, a manned or unmanned aerial vehicle (AV), a ship, or the like.

[0329] Referring to FIG. 18, 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. 17, respectively.

[0330] 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.

[0331] 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.

[0332] 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. 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.

[0333] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the spirit and 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.

[0334] The present disclosure may be used in a terminal, base station, or other equipment of a wireless mobile communication system.

Claims

1. In a method for a terminal to receive a signal in a wireless communication system, Receive system information including settings related to WUS (wake up signal) through the first receiving operation; and Including determining based on the system information whether to perform monitoring of the WUS through a second receiving operation that consumes lower power than the first receiving operation; A method in which the settings related to the above WUS include information about the waveform of the above WUS.

2. In paragraph 1, A method wherein the settings related to the WUS include at least one of information on time and frequency resources of the WUS or information on activation / deactivation of the WUS.

3. In paragraph 1, The above system information further includes settings related to a second synchronization signal for synchronization in the second receiving operation, A method wherein the second synchronization signal is set differently from the first synchronization signal for synchronization in the first receiving operation.

4. In paragraph 3, A method wherein the position of the second synchronization signal is determined based on the position of a synchronization signal block (SSB) including the first synchronization signal.

5. In paragraph 1, A method in which the terminal determines by itself whether to perform monitoring of the WUS based on the terminal operating in an RRC (radio resource control) idle / inactive state.

6. In paragraph 5, A method further comprising performing a random access process for requesting transmission of the WUS to the network based on a decision to perform monitoring of the WUS.

7. In paragraph 5, A method in which whether monitoring of the WUS should be performed while the terminal is operating in an RRC connection state is explicitly set through network signaling.

8. In paragraph 1, A method in which it is determined whether to perform monitoring of the WUS through the second receiving operation based on the quality of the signal measured through the first receiving operation.

9. In paragraph 1, A method wherein the signal measured through the first receiving operation includes at least one of a first synchronization signal for synchronization in the first receiving operation or a second synchronization signal for synchronization in the second receiving operation.

10. A computer-readable recording medium having recorded thereon a program for performing the method described in paragraph 1.

11. In a device for wireless communication, memory that stores commands; and A processor that operates by executing the above instructions, The operation of the above processor is as follows: Receive system information including settings related to WUS (wake up signal) through the first receiving operation; and Including determining based on the system information whether to perform monitoring of the WUS through a second receiving operation that consumes lower power than the first receiving operation; The settings related to the above WUS are a device that includes information about the waveform of the above WUS.

12. In paragraph 11, a first receiver configured to perform the first receiving operation; and A device further comprising a second receiver configured to perform the second receiving operation.

13. In paragraph 11, The above device is a terminal operating in a wireless communication system or a processing device controlling the terminal.

14. In a method for a base station to transmit a signal in a wireless communication system, Determine settings related to the wake up signal (WUS) to support a second reception operation that consumes less power than the first reception operation of the terminal; Transmitting system information including settings related to the above WUS; and Including transmitting the WUS based on the settings related to the WUS, A method in which the settings related to the above WUS include information about the waveform of the above WUS.

15. In a base station for wireless communication, memory that stores commands; and A processor that operates by executing the above instructions, The operation of the above processor is as follows: Determine settings related to the wake up signal (WUS) to support a second reception operation that consumes less power than the first reception operation of the terminal; Transmitting system information including settings related to the above WUS; and Including transmitting the WUS based on the settings related to the WUS, The settings related to the above WUS are a base station that includes information about the waveform of the above WUS.

Citation Information

Cited By

  • Communication method and communication device

    WO2026137313A1