Method and apparatus for performing wireless communication using low-power wakeup receiver

Abstract

The present embodiments provide a method for a terminal to perform wireless communication using a low-power wakeup receiver (LP-WUR), the method comprising the steps of: configuring capability information related to reception of a low-power wakeup signal (LP-WUS) via a low-power wakeup receiver; and transmitting the capability information to a base station via a transceiver.

Description

Method and device for performing wireless communication using a low-power wake-up receiver

[0001] The present embodiments propose a method and apparatus for performing wireless communication using a low-power wake-up receiver in a next-generation wireless access network (in this disclosure, “5G,” “NR [New Radio],” “5G-Advanced,” “6G,” or a subsequent 3GPP wireless access network).

[0002] 3GPP continues to research and develop wireless communication technologies. In wireless communication systems, in addition to latency, stability, and availability, energy efficiency of the terminal is also a crucial consideration. Current terminals may require frequent charging depending on individual usage. Designing for extended battery life is essential for improving energy efficiency and enhancing user experience. Energy efficiency is crucial for terminals without a continuous energy source.

[0003] Power consumption may vary depending on the configured wake-up period length. However, using large DRX cycles to meet battery life requirements, for example, results in high latency, making it unsuitable for services that require both long battery life and low latency.

[0004] As part of this aspect, specific designs are needed to enable terminals to consume power more efficiently when performing wake-up operations.

[0005] Embodiments of the present disclosure can provide a method and device for performing wireless communication using a low-power wake-up receiver.

[0006] In one aspect, the present embodiments may provide a method for a terminal to perform wireless communication using a low power wakeup receiver (LP-WUR), the method including a step of configuring capability information related to reception of a low power wakeup signal (LP-WUS) through the low power wakeup receiver, and a step of transmitting the capability information to a base station through a transceiver.

[0007] In another aspect, the present embodiments may provide a method for a base station to control the operation of a terminal performing wireless communication using a low power wakeup receiver (LP-WUR), the method including the steps of receiving capability information required for reception of a low power wakeup signal (LP-WUS) through the low power wakeup receiver from the terminal and transmitting low power wakeup signal configuration information to the terminal based on the capability information.

[0008] In another aspect, the present embodiments provide a terminal for performing wireless communication using a low power wakeup receiver (LR), including a low power wakeup receiver, a transceiver, and a controller for controlling operations of the low power wakeup receiver and the transceiver, wherein the controller configures capability information related to reception of a low power wakeup signal (LP-WUS) through the low power wakeup receiver, and transmits the capability information to a base station through the transceiver.

[0009] In another aspect, the present embodiments provide a base station that controls the operation of a terminal that performs wireless communication using a low-power wake-up receiver, the base station including a transmitter, a receiver, and a controller that controls the operation of the transmitter and the receiver, wherein the controller receives capability information required for receiving a low-power wake-up signal (LP-WUS) through the low-power wake-up receiver from the terminal, and transmits low-power wake-up signal configuration information to the terminal based on the capability information.

[0010] According to the present embodiments, a method and device for performing wireless communication using a low-power wake-up receiver capable of performing a wake-up operation that consumes power efficiently can be provided.

[0011] In addition, a terminal capability management method can be provided to support a transmission and reception environment tailored to various characteristics of a receiver with low standby power.

[0012] FIG. 1 is a schematic diagram illustrating the structure of an NR wireless communication system to which the present embodiment can be applied.

[0013] FIG. 2 is a drawing for explaining a frame structure in an NR system to which the present embodiment can be applied.

[0014] FIG. 3 is a diagram for explaining a resource grid supported by a wireless access technology to which the present embodiment can be applied.

[0015] FIG. 4 is a diagram for explaining a bandwidth part supported by a wireless access technology to which the present embodiment can be applied.

[0016] FIG. 5 is a diagram illustrating an example of a synchronization signal block in a wireless access technology to which the present embodiment can be applied.

[0017] FIG. 6 is a diagram for explaining a random access procedure in a wireless access technology to which the present embodiment can be applied.

[0018] Figure 7 is a drawing for explaining CORESET.

[0019] FIG. 8 is a diagram illustrating a procedure for a terminal to perform wireless communication using a low-power wake-up receiver according to one embodiment.

[0020] FIG. 9 is a diagram illustrating a procedure for a base station to control the operation of a terminal performing wireless communication using a low-power wake-up receiver according to one embodiment.

[0021] Fig. 10 is a drawing showing the configuration of a terminal according to another embodiment.

[0022] Fig. 11 is a drawing showing the configuration of a base station according to another embodiment.

[0023] Hereinafter, some embodiments of the present disclosure will be described in detail with reference to exemplary drawings. When adding reference numerals to components in each drawing, identical components may have the same numerals as much as possible even if they are shown in different drawings. In addition, when describing the present embodiments, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the technical idea of ​​the present invention, the detailed description may be omitted. When "includes," "has," "consists of," etc. are used in this specification, other parts may be added unless "only" is used. When a component is expressed in the singular, it may include a case in which the plural is included unless specifically stated otherwise.

[0024] Additionally, terms such as first, second, A, B, (a), (b), etc. may be used to describe components of the present disclosure. These terms are only intended to distinguish the components from other components, and the nature, order, sequence, or number of the components are not limited by the terms.

[0025] In a description of the positional relationship of components, when it is described that two or more components are "connected," "combined," or "connected," it should be understood that the two or more components may be directly "connected," "combined," or "connected," but that the two or more components may also be further "interposed" with another component to be "connected," "combined," or "connected." Here, the other component may be included in one or more of the two or more components that are "connected," "combined," or "connected" to each other.

[0026] In the description of the temporal flow relationship related to components, operation methods, or manufacturing methods, for example, when the temporal or flow relationship is described as “after”, “following”, “next to”, “before”, etc., it may also include cases where it is not continuous, unless “immediately” or “directly” is used.

[0027] Meanwhile, when numerical values ​​or corresponding information (e.g., levels, etc.) for components are mentioned, even without separate explicit description, the numerical values ​​or corresponding information may be interpreted as including an error range that may occur due to various factors (e.g., process factors, internal or external impact, noise, etc.).

[0028] The wireless communication system in this specification refers to a system for providing various communication services such as voice, data packets, etc. using wireless resources, and may include a terminal, a base station, or a core network.

[0029] The embodiments disclosed below can be applied to wireless communication systems using various wireless access technologies. For example, the embodiments can be applied to various wireless access technologies such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), SC-FDMA (single carrier frequency division multiple access), or NOMA (non-orthogonal multiple access). In addition, the wireless access technology may not only refer to a specific access technology, but also to each generation of communication technology established by various communication agreement organizations such as 3GPP, 3GPP2, WiFi, Bluetooth, IEEE, and ITU. For example, CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless 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 in wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved UTRA). IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e.UTRA is 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 (evolved-UMTSterrestrial radio access), employing OFDMA in the downlink and SC-FDMA in the uplink. Thus, the present embodiments can be applied to currently disclosed or commercialized wireless access technologies, as well as wireless access technologies currently under development or to be developed in the future.

[0030] Meanwhile, the term "terminal" in this specification is a comprehensive concept that refers to a device that includes a wireless communication module that performs communication with a base station in a wireless communication system, and should be interpreted as a concept that includes not only UE (User Equipment) in WCDMA, LTE, NR, HSPA, and IMT-2020 (5G or New Radio), but also MS (Mobile Station), UT (User Terminal), SS (Subscriber Station), and wireless device in GSM. In addition, the terminal may be a user portable device such as a smartphone depending on the usage type, and in a V2X communication system, it may mean a vehicle, a device including a wireless communication module in the vehicle, etc. In addition, in the case of a Machine Type Communication system, it may mean an MTC terminal, M2M terminal, URLLC terminal, etc. that is equipped with a communication module to perform machine type communication.

[0031] The base station or cell in this specification refers to an end that communicates with a terminal in terms of a network, and includes various coverage areas such as Node-B, eNB (evolved Node-B), gNB (gNode-B), LPN (Low Power Node), Sector, Site, various types of antennas, BTS (Base Transceiver System), Access Point, Point (e.g., Transmission Point, Reception Point, Transmission / Reception Point), Relay Node, Mega Cell, Macro Cell, Micro Cell, Pico Cell, Femto Cell, RRH (Remote Radio Head), RU (Radio Unit), and Small Cell. In addition, a cell may mean including a BWP (Bandwidth Part) in the frequency domain. For example, a serving cell may mean an Activation BWP of a terminal.

[0032] Since the various cells listed above have a base station that controls one or more cells, the base station can be interpreted in two meanings. 1) It can be a device itself that provides a mega cell, macro cell, micro cell, pico cell, femto cell, or small cell in relation to a wireless area, or 2) it can indicate the wireless area itself. In 1), all devices that provide a given wireless area are controlled by the same entity or that interact to cooperatively configure the wireless area are all indicated as a base station. Depending on how the wireless area is configured, a point, a transceiver point, a transmission point, a reception point, etc. can be an embodiment of a base station. In 2), the wireless area itself that receives or transmits a signal from the perspective of a user terminal or a neighboring base station can also be indicated as a base station.

[0033] In this specification, a cell may mean a component carrier having coverage of a signal transmitted from a transmission / reception point or a transmission / reception point itself.

[0034] Uplink (UL, or uplink) refers to a method of transmitting and receiving data from a terminal to a base station, and downlink (DL, or downlink) refers to a method of transmitting and receiving data from a base station to a terminal. Downlink may refer to communication or a communication path from multiple transmission / reception points to a terminal, and uplink may refer to communication or a communication path from a terminal to multiple transmission / reception points. In this case, in the downlink, the transmitter may be part of the multiple transmission / reception points, and the receiver may be part of the terminal. In addition, in the uplink, the transmitter may be part of the terminal, and the receiver may be part of the multiple transmission / reception points.

[0035] Uplink and downlink transmit and receive control information through control channels such as PDCCH (Physical Downlink Control CHannel) and PUCCH (Physical Uplink Control CHannel), and transmit and receive data by configuring data channels such as PDSCH (Physical Downlink Shared CHannel) and PUSCH (Physical Uplink Shared CHannel). Hereinafter, the situation in which signals are transmitted and received through channels such as PUCCH, PUSCH, PDCCH, and PDSCH is also expressed in the form of 'transmitting and receiving PUCCH, PUSCH, PDCCH, and PDSCH'.

[0036] For clarity of explanation, the technical idea of ​​this invention is described below mainly with reference to the 3GPP LTE / LTE-A / NR (New RAT) communication system, but the technical features of this invention are not limited to the communication system.

[0037] After researching 4G (4th-Generation) communication technology, 3GPP develops 5G (5th-Generation) communication technology to meet the requirements of the next-generation wireless access technology of the ITU-R. Specifically, 3GPP develops LTE-A pro, which enhances LTE-Advanced technology to meet the requirements of the ITU-R, and NR, a new communication technology separate from 4G communication technology. Both LTE-A pro and NR refer to 5G communication technology, and in the following, 5G communication technology will be explained with NR as the focus, unless a specific communication technology is specifically mentioned.

[0038] The operating scenario in NR defines various operation scenarios by adding considerations for satellites, automobiles, and new verticals to the existing 4G LTE scenario, and in terms of service, it supports the eMBB (Enhanced Mobile Broadband) scenario, the mMTC (Massive Machine Communication) scenario that has high terminal density but is deployed over a wide area and requires low data rate and asynchronous access, and the URLLC (Ultra Reliability and Low Latency) scenario that requires high responsiveness and reliability and can support high-speed mobility.

[0039] To meet these scenarios, NR introduces a wireless communication system that incorporates new waveform and frame structure technologies, low latency technologies, support for ultra-high frequency bands (mmWave), and forward compatibility technologies. In particular, NR systems offer various technological changes in terms of flexibility to ensure forward compatibility. The key technical features of NR are described below with reference to the drawings.

[0040]

[0041] <NR 시스템 일반>

[0042] Figure 1 is a schematic diagram illustrating the structure of an NR system to which the present embodiment can be applied.

[0043] Referring to Fig. 1, the NR system is divided into 5GC (5G Core Network) and NR-RAN parts, and the NG-RAN is composed of gNBs and ng-eNBs that provide user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol termination for UE (User Equipment). gNBs or gNBs and ng-eNBs are interconnected via the Xn interface. gNBs and ng-eNBs are each connected to the 5GC via the NG interface. The 5GC can be configured to include an AMF (Access and Mobility Management Function) that is responsible for the control plane such as terminal access and mobility control functions, and an UPF (User Plane Function) that is responsible for the control function for user data. NR includes support for both frequency bands below 6 GHz (FR1, Frequency Range 1) and frequency bands above 6 GHz (FR2, Frequency Range 2).

[0044] gNB refers to a base station that provides NR user plane and control plane protocol termination to terminals, and ng-eNB refers to a base station that provides E-UTRA user plane and control plane protocol termination to terminals. The base station described in this specification should be understood to encompass both gNB and ng-eNB, and may also be used to refer to gNB or ng-eNB separately as needed.

[0045] <NR 웨이브 폼, 뉴머롤러지 및 프레임 구조>

[0046]

[0047] NR uses the CP-OFDM waveform with a cyclic prefix for downlink transmission, and CP-OFDM or DFT-s-OFDM for uplink transmission. OFDM technology is easily combined with MIMO (Multiple Input Multiple Output) and offers the advantages of high spectral efficiency and low-complexity receivers.

[0048] Meanwhile, in NR, the requirements for data rates, latency, and coverage differ across the three scenarios mentioned above. Therefore, it is necessary to efficiently satisfy these requirements across the frequency bands that comprise any NR system. To this end, technologies have been proposed to efficiently multiplex radio resources based on multiple different numerologies.

[0049] Specifically, the NR transmission numerator is determined based on the sub-carrier spacing and the cyclic prefix (CP), and is changed exponentially with the μ value being an exponent value of 2 based on 15 kHz, as shown in Table 1 below.

[0050] μ서브캐리어 간격Cyclic prefixSupported for dataSupported for synch015NormalYesYes130NormalYesYes260Normal, ExtendedYesNo3120NormalYesYes4240NormalNoYes

[0051] As shown in Table 1 above, the numerology of NR can be divided into five types according to the subcarrier spacing. This is different from the fixed subcarrier spacing of LTE, one of the 4G communication technologies, at 15 kHz. Specifically, the subcarrier spacing used for data transmission in NR is 15, 30, 60, and 120 kHz, and the subcarrier spacing used for synchronization signal transmission is 15, 30, 12, and 240 kHz. In addition, the extended CP is applied only to the 60 kHz subcarrier spacing. Meanwhile, the frame structure in NR is defined as a 10 ms frame consisting of 10 subframes with the same length of 1 ms. One frame can be divided into half frames of 5 ms, and each half frame contains 5 subframes. In the case of a 15 kHz subcarrier spacing, one subframe consists of one slot, and each slot consists of 14 OFDM symbols. FIG. 2 is a diagram for explaining the frame structure in an NR system to which the present embodiment can be applied. Referring to FIG. 2, a slot is fixedly composed of 14 OFDM symbols in the case of a normal CP, but the length of the slot in the time domain may vary depending on the subcarrier spacing. For example, in the case of a numerology with a 15 kHz subcarrier spacing, a slot is composed of 1 ms, which is the same length as a subframe. In contrast, in the case of a numerology with a 30 kHz subcarrier spacing, a slot is composed of 14 OFDM symbols, but two slots may be included in one subframe with a length of 0.5 ms. That is, a subframe and a frame are defined with a fixed time length, and a slot is defined by the number of symbols, so the time length may vary depending on the subcarrier spacing.

[0052] Meanwhile, NR defines slots as the basic scheduling unit and also introduces mini-slots (or sub-slots, or non-slot-based scheduling) to reduce transmission delay in the wireless section. Using wider subcarrier spacing reduces transmission delay in the wireless section by shortening the length of each slot inversely. Mini-slots (or sub-slots) are designed to efficiently support URLLC scenarios and allow scheduling in units of 2, 4, or 7 symbols.

[0053] Furthermore, unlike LTE, NR defines uplink and downlink resource allocation at the symbol level within a single slot. To reduce HARQ delay, a slot structure was defined that allows HARQ ACK / NACKs to be transmitted directly within the transmission slot. This slot structure is referred to as a self-contained structure and will be described in detail.

[0054] NR is designed to support a total of 256 slot formats, of which 62 are used in 3GPP Rel-15. It also supports a common frame structure that configures FDD or TDD frames through various combinations of slots. For example, it supports a slot structure in which all symbols in a slot are set to downlink, a slot structure in which all symbols are set to uplink, and a slot structure in which downlink and uplink symbols are combined. NR also supports data transmission being distributed and scheduled across one or more slots. Therefore, a base station can use a slot format indicator (SFI) to inform a UE whether a slot is a downlink slot, an uplink slot, or a flexible slot. The base station can indicate the slot format by indicating an index of a table configured through UE-specific RRC signaling using the SFI, and can also indicate it dynamically through DCI (Downlink Control Information) or statically or semi-statically through RRC.

[0055] <NR 물리 자원 >

[0056] In relation to physical resources in NR, antenna ports, resource grids, resource elements, resource blocks, and bandwidth parts are considered.

[0057] Antenna ports are defined such that the channel through which a symbol on an antenna port is carried can be inferred from the channel through which another symbol on the same antenna port is carried. Two antenna ports are said to be quasi co-located (or quasi co-located) if the large-scale properties of the channel through which a symbol on one antenna port is carried can be inferred from the channel through which a symbol on the other antenna port is carried. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0058] FIG. 3 is a diagram for explaining a resource grid supported by a wireless access technology to which the present embodiment can be applied.

[0059] Referring to Figure 3, a resource grid may exist for each numeral, as NR supports multiple numerals on the same carrier. Furthermore, resource grids may exist based on antenna ports, subcarrier spacing, and transmission direction.

[0060] A resource block (RB) consists of 12 subcarriers and is defined solely in the frequency domain. Furthermore, a resource element (RE) consists of one OFDM symbol and one subcarrier. Therefore, as shown in Figure 3, the size of a single RB can vary depending on the subcarrier spacing. NR also defines "Point A," which serves as a common reference point for the RB grid, as well as common RBs and virtual RBs.

[0061] FIG. 4 is a diagram for explaining a bandwidth part supported by a wireless access technology to which the present embodiment can be applied.

[0062] Unlike LTE, where the carrier bandwidth is fixed at 20 MHz, NR sets the maximum carrier bandwidth from 50 MHz to 400 MHz for each subcarrier interval. Therefore, it is not assumed that all terminals will use the entire carrier bandwidth. Accordingly, NR allows terminals to designate bandwidth parts (BWPs) within the carrier bandwidth, as illustrated in Figure 4. Furthermore, bandwidth parts are associated with a single numerology, consist of a subset of consecutive common resource blocks, and can be dynamically activated over time. Each terminal is configured with up to four bandwidth parts for both the uplink and downlink, and data is transmitted and received using the bandwidth parts activated at a given time.

[0063] In the case of a paired spectrum, the uplink and downlink bandwidth parts are set independently, and in the case of an unpaired spectrum, the downlink and uplink bandwidth parts are set in pairs so that they can share a center frequency to prevent unnecessary frequency re-tuning between downlink and uplink operations.

[0064] <NR 초기 접속>

[0065] In NR, a terminal performs cell search and random access procedures to connect to a base station and perform communication.

[0066] Cell search is a procedure in which a terminal synchronizes to the cell of a corresponding base station, obtains a physical layer cell ID, and obtains system information using a synchronization signal block (SSB) transmitted by the base station.

[0067] FIG. 5 is a diagram illustrating an example of a synchronization signal block in a wireless access technology to which the present embodiment can be applied.

[0068] Referring to FIG. 5, SSB is composed of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), each occupying 1 symbol and 127 subcarriers, and a PBCH spanning 3 OFDM symbols and 240 subcarriers.

[0069] The terminal receives SSB by monitoring SSB in the time and frequency domain.

[0070] SSB can be transmitted up to 64 times in 5ms. Multiple SSBs are transmitted in different transmission beams within 5ms, and the terminal performs detection assuming that SSBs are transmitted every 20ms based on a specific beam used for transmission. The number of beams that can be used for SSB transmission within 5ms can increase as the frequency band increases. For example, up to 4 SSB beams can be transmitted below 3GHz, up to 8 in the frequency band between 3GHz and 6GHz, and up to 64 different beams can be used for SSB transmission in the frequency band above 6GHz.

[0071] SSB contains two symbols in one slot, and the starting symbol and number of repetitions within the slot are determined as follows depending on the subcarrier spacing.

[0072] Meanwhile, unlike SS in conventional LTE, SSB is not transmitted at the center frequency of the carrier bandwidth. This means that SSB can be transmitted even in locations other than the center of the system bandwidth, and when supporting wideband operation, multiple SSBs can be transmitted in the frequency domain. Accordingly, the terminal monitors SSB using the synchronization raster, which is a candidate frequency location for monitoring SSB. The carrier raster, which is the center frequency location information of the channel for initial access, and the synchronization raster are newly defined in NR. The synchronization raster has a wider frequency interval than the carrier raster, which can support the terminal's fast SSB search.

[0073] A UE can obtain the MIB through the PBCH of the SSB. The MIB (Master Information Block) includes the minimum information required for the UE to receive the remaining system information (RMSI, Remaining Minimum System Information) broadcast by the network. In addition, the PBCH may include information on the position of the first DM-RS symbol in the time domain, information for the UE to monitor SIB1 (e.g., SIB1 numerology information, information related to SIB1 CORESET, search space information, PDCCH-related parameter information, etc.), offset information between the common resource block and the SSB (the absolute position of the SSB within the carrier is transmitted through SIB1), etc. Here, the SIB1 numerology information is also applied equally to some messages used in the random access procedure for the UE to access the base station after completing the cell search procedure. For example, the numerology information of SIB1 may be applied to at least one of messages 1 to 4 for the random access procedure.

[0074] The aforementioned RMSI may refer to SIB1 (System Information Block 1), and SIB1 is broadcast periodically (e.g., every 160 ms) in the cell. SIB1 contains information necessary for the UE to perform the initial random access procedure and is periodically transmitted via PDSCH. In order for the UE to receive SIB1, it must receive numerology information used for SIB1 transmission and CORESET (Control Resource Set) information used for SIB1 scheduling via PBCH. The UE checks scheduling information for SIB1 using SI-RNTI in CORESET and acquires SIB1 on PDSCH according to the scheduling information. The remaining SIBs, excluding SIB1, may be transmitted periodically or upon request of the UE.

[0075] FIG. 6 is a diagram for explaining a random access procedure in a wireless access technology to which the present embodiment can be applied.

[0076] Referring to FIG. 6, once cell search is complete, the terminal transmits a random access preamble for random access to the base station. The random access preamble is transmitted via the PRACH. Specifically, the random access preamble is transmitted to the base station via the PRACH, which consists of consecutive radio resources in a specific slot that is periodically repeated. Generally, when a terminal initially accesses a cell, a contention-based random access procedure is performed, and when performing random access for beam failure recovery (BFR), a non-contention-based random access procedure is performed.

[0077] The UE receives a random access response to the transmitted random access preamble. The random access response may include a random access preamble identifier (ID), an UL Grant (uplink radio resource), a temporary C-RNTI (Temporary Cell - Radio Network Temporary Identifier), and a TAC (Time Alignment Command). Since one random access response may include random access response information for one or more UEs, the random access preamble identifier may be included to indicate which UE the included UL Grant, temporary C-RNTI, and TAC are valid for. The random access preamble identifier may be an identifier for the random access preamble received by the base station. The TAC may be included as information for the UE to adjust uplink synchronization. The random access response may be indicated by a random access identifier on the PDCCH, i.e., an RA-RNTI (Random Access - Radio Network Temporary Identifier).

[0078] Upon receiving a valid random access response, the terminal processes the information contained in the random access response and performs scheduled transmission to the base station. For example, the terminal applies TAC and stores a temporary C-RNTI. Furthermore, using the UL Grant, the terminal transmits data stored in its buffer or newly generated data to the base station. In this case, information that identifies the terminal must be included.

[0079] Finally, the terminal receives a downlink message for contention resolution.

[0080] <NR CORESET>

[0081] The downlink control channel in NR is transmitted in a CORESET (Control Resource Set) with a length of 1 to 3 symbols, and transmits uplink / downlink scheduling information, SFI (Slot format Index), TPC (Transmit Power Control) information, etc.

[0082] To ensure system flexibility, NR introduced the CORESET concept. CORESET (Control Resource Set) refers to time-frequency resources for downlink control signals. A terminal can decode control channel candidates using one or more search spaces within the CORESET time-frequency resources. A QCL (Quasi CoLocation) assumption is established for each CORESET, which is used to inform the characteristics of analog beam direction in addition to the delay spread, Doppler spread, Doppler shift, and average delay assumed by the conventional QCL.

[0083] Figure 7 is a drawing for explaining CORESET.

[0084] Referring to Figure 7, a CORESET can exist in various forms within the carrier bandwidth within a single slot, and in the time domain, a CORESET can consist of up to three OFDM symbols. In addition, a CORESET is defined as a multiple of six resource blocks up to the carrier bandwidth in the frequency domain.

[0085] The first CORESET is indicated via the MIB as part of the initial bandwidth part configuration, allowing the terminal to receive additional configuration and system information from the network. After establishing a connection with the base station, the terminal can receive and configure one or more CORESET information via RRC signaling.

[0086] Wider bandwidth operations

[0087] Existing LTE systems supported scalable bandwidth operation for any LTE Component Carrier (CC). That is, depending on the deployment scenario, any LTE operator could configure a single LTE CC with a bandwidth ranging from a minimum of 1.4 MHz to a maximum of 20 MHz, and a normal LTE terminal supported transmission and reception capabilities of 20 MHz bandwidth for a single LTE CC.

[0088] However, in the case of NR, the design is made to support NR terminals with different transmission and reception bandwidth capabilities through a single wideband NR CC, and accordingly, it is required to configure one or more bandwidth parts (BWP, bandwidth part(s)) consisting of segmented bandwidths for any NR CC, and to support flexible wider bandwidth operation through different bandwidth part configurations and activations for each terminal.

[0089] Specifically, in NR, one or more bandwidth parts can be configured through one serving cell configured from the terminal's perspective, and the terminal is defined to activate one downlink bandwidth part (DL bandwidth part) and one uplink bandwidth part (UL bandwidth part) in the serving cell to use them for uplink / downlink data transmission and reception. In addition, when multiple serving cells are configured in the terminal, that is, for the terminal to which CA is applied, it is defined to activate one downlink bandwidth part and / or uplink bandwidth part for each serving cell to use the radio resources of the serving cell to use them for uplink / downlink data transmission and reception.

[0090] Specifically, an initial bandwidth part for an initial access procedure of a terminal in an arbitrary serving cell is defined, one or more UE-specific bandwidth part(s) are configured for each terminal through dedicated RRC signaling, and a default bandwidth part for a fallback operation can also be defined for each terminal.

[0091] However, it can be defined that multiple downlink and / or uplink bandwidth parts can be activated and used simultaneously depending on the capability and bandwidth part(s) configuration of the terminal in any serving cell, but in NR rel-15, it is defined that only one downlink bandwidth part (DL bandwidth part) and one uplink bandwidth part (UL bandwidth part) can be activated and used in any terminal at any time.

[0092] In this specification, the terms frequency, frame, subframe, resource, resource block, region, band, subband, control channel, data channel, synchronization signal, various reference signals, various signals or various messages related to NR (New Radio) may be interpreted in the past or present meaning or in various meanings used in the future.

[0093] In wireless communication systems, energy efficiency of the terminal is a crucial consideration, in addition to latency, stability, and availability. Current terminals may require frequent charging depending on individual usage. Designing for extended battery life is essential for improving energy efficiency and enhancing user experience. Energy efficiency is crucial for terminals without a continuous energy source.

[0094] Power consumption may vary depending on the configured wake-up period length. However, if a large discontinuous reception (DRX) cycle is used to meet battery life requirements, this may result in high latency, making it unsuitable for services that require both long battery life and low latency.

[0095] Terminals must wake up periodically, once per DRX cycle, which dictates power consumption during periods of no signal or data traffic. Power consumption can be significantly reduced if terminals can wake only when triggered, such as by paging. This can be achieved by using a wakeup signal that triggers the main radio and a separate receiver that monitors the wakeup signal with ultra-low power consumption. The main radio operates for data transmission and reception and can be turned off or in hibernation mode unless turned on.

[0096] The power consumption for monitoring the wake-up signal may vary depending on the wake-up signal design and the hardware module of the wake-up receiver used to detect and process the signal.

[0097] In the present disclosure, the Main Radio (MR) may be used to mean a Tx / Rx module, i.e., a transmitter, receiver, or transceiver, that operates for NR signals / channels in addition to low-power wake-up related signals / channels. In addition, the Low-Power Wake-Up Receiver (LP-WUR; LR) may be used to mean an Rx module, i.e., a receiver, that operates to receive / process low-power wake-up related signals / channels. In addition, the MR mode may mean performing communication in the Main Radio, and the LR mode may mean performing communication using the low-power wake-up receiver.

[0098] Below, a method for performing wireless communication using a low-power wake-up receiver will be described with reference to related drawings.

[0099] FIG. 8 is a diagram illustrating a procedure (800) in which a terminal transmits and receives data in full-duplex communication according to one embodiment.

[0100] Referring to FIG. 8, the terminal can configure capability information related to receiving a low power wakeup signal (LP-WUS) through a low power wakeup receiver (S810).

[0101] In order to perform a low-power wake-up operation using a low-power wake-up receiver, the terminal may configure capability information related to the low-power wake-up operation. For example, the capability information may include at least one of support for a low-power wake-up signal, information on a receivable frequency band, information on required reception power, and applicable modulation method information. In this case, the modulation method information may further include information on whether a separately defined modulation method of the low-power wake-up signal other than OOK and FSK is supported, for example, a modulation method such as an overlaid OFDM sequence. In addition, the capability information may include at least one of time gap information between reception of the low-power wake-up signal and monitoring of the downlink control channel through the transceiver. In addition, the capability information may include information on whether monitoring of the downlink control channel through the transceiver is possible in the on state of the low-power wake-up receiver. That is, the capability information may further include information on whether the low-power wake-up receiver can be kept on while monitoring the downlink control channel by turning on the transceiver upon receiving a low-power wake-up signal through the low-power wake-up receiver.

[0102] Specifically, the capability information may be composed of one or more of the following information. Whether the terminal can receive LP-WUS, the LP-WUS reception band range of the terminal, the receiver type or required reception power, the maximum or minimum delay until MR wake-up after LP-WUS reception, etc. may be included in the capability information. In addition, the capability information may include the allowable phase error or required phase precision, the allowable transmission signal modulation method such as OOK, FSK, or other defined WUS modulation method, the maximum number of bits that can be transmitted through different frequencies per time interval, and the allowed or supported unit time interval interval corresponding to one symbol interval, which is usually OOK, FSK. In addition, the capability information may include the minimum or maximum synchronization execution interval required, the number of LP-WUSs that can be received simultaneously, whether reception is possible when the MR is in a wake-up state in relation to whether there is interoperability with the MR, the average wake-up frequency or work execution frequency according to the terminal service characteristics, the required delay from traffic generation to WUS transmission, or from WUS transmission to traffic transmission, or from traffic generation to traffic transmission, etc.

[0103] The capability information may be configured as an RRC message. That is, the terminal may transmit the capability information to the base station via RRC, etc. According to one example, the capability information may be included in at least one of the existing RRC messages, such as UE-NR-Capability, PDCP-Parameters, RLC-Parameters, MAC-Parameters, Phy-Parameters, RF-Parameters, FeatureSets, and FeatureSetDownlink. Alternatively, according to another example, the capability information may be included in an RRC message that conveys information about a newly defined LP-WUS-related capability.

[0104] For example, capability information may be configured when a request for capability information is received from a base station. That is, the terminal may configure capability information based on the capability information received from the base station.

[0105] Alternatively, the capability information may be configured based on configuration information supported by the base station for low-power wake-up signals. That is, the terminal may receive information from the base station in advance regarding candidate configuration values ​​supported by the base station for parameters required for low-power wake-up operations. In this case, the terminal may determine the configuration values ​​usable by the terminal from among the received candidate configuration values.

[0106] Alternatively, the terminal may receive information from the base station regarding candidate setting values ​​that the base station can support for parameters required for low-power wake-up operations based on capability information. The terminal may determine a preferred or optimal setting value among the received candidate setting values.

[0107] Referring again to FIG. 8, the terminal can transmit capability information to the base station via the transceiver (S820).

[0108] The terminal can transmit capability information to the base station via RRC, etc. In one example, the capability information can be transmitted by being included in at least one of the existing RRC messages such as UE-NR-Capability, PDCP-Parameters, RLC-Parameters, MAC-Parameters, Phy-Parameters, RF-Parameters, FeatureSets, and FeatureSetDownlink. Alternatively, in another example, the capability information can be transmitted by being included in an RRC message that conveys information about a newly defined LP-WUS-related capability.

[0109] For example, when a terminal determines a usable configuration value among candidate configuration values ​​received from a base station, the terminal may indirectly transmit capability information to the base station in the form of reporting the determined configuration value. In this case, the reporting may be performed using an RRC message. Alternatively, the reporting may be in the form of a bitmap indicating availability in response to the configuration values ​​set by the base station. Each component of the bitmap may include some information such as a modulation scheme, frequency band, and time interval. This may be transmitted via a newly defined PUCCH format for LP-WUS availability feedback.

[0110] Thereafter, the terminal can receive configuration information set for a low-power wake-up operation. Based on the received configuration information, the terminal can monitor a low-power wake-up signal through a low-power wake-up receiver. If a condition triggering monitoring of a downlink control channel, such as reception of a low-power wake-up signal, is met, the terminal can monitor the downlink control channel through a transceiver. Thereafter, the terminal can perform wireless communication with the base station through the transceiver.

[0111] Accordingly, a method and device for performing wireless communication using a low-power wake-up receiver capable of performing a wake-up operation that consumes power efficiently can be provided.

[0112] FIG. 9 is a diagram illustrating a procedure (900) for a base station to transmit and receive data in full-duplex communication according to one embodiment. The description given above in FIG. 8 may be omitted to avoid redundant explanation. In this case, the omitted content may be substantially equally applied to the base station, as long as it does not conflict with the technical spirit of the invention.

[0113] Referring to FIG. 9, the base station can receive capability information required for receiving a low power wakeup signal (LP-WUS) through a low power wakeup receiver from the terminal (S910).

[0114] In order to perform a low-power wake-up operation using a low-power wake-up receiver, the terminal may configure capability information related to the low-power wake-up operation. For example, the capability information may include at least one of support for a low-power wake-up signal, information on a receivable frequency band, information on required reception power, and applicable modulation method information. In this case, the modulation method information may further include information on whether a separately defined modulation method of the low-power wake-up signal other than OOK and FSK is supported, for example, a modulation method such as an overlaid OFDM sequence. In addition, the capability information may include at least one of time gap information between reception of the low-power wake-up signal and monitoring of the downlink control channel through the transceiver. In addition, the capability information may include information on whether monitoring of the downlink control channel through the transceiver is possible in the on state of the low-power wake-up receiver. That is, the capability information may further include information on whether the low-power wake-up receiver can be kept on while monitoring the downlink control channel by turning on the transceiver upon receiving a low-power wake-up signal through the low-power wake-up receiver.

[0115] Specifically, the capability information may be composed of one or more of the following information. Whether the terminal can receive LP-WUS, the LP-WUS reception band range of the terminal, the receiver type or required reception power, the maximum or minimum delay until MR wake-up after LP-WUS reception, etc. may be included in the capability information. In addition, the capability information may include the allowable phase error or required phase precision, the allowable transmission signal modulation method such as OOK, FSK, or other defined WUS modulation method, the maximum number of bits that can be transmitted through different frequencies per time interval, and the allowed or supported unit time interval interval corresponding to one symbol interval, which is usually OOK, FSK. In addition, the capability information may include the minimum or maximum synchronization execution interval required, the number of LP-WUSs that can be received simultaneously, whether reception is possible when the MR is in a wake-up state in relation to whether there is interoperability with the MR, the average wake-up frequency or work execution frequency according to the terminal service characteristics, the required delay from traffic generation to WUS transmission, or from WUS transmission to traffic transmission, or from traffic generation to traffic transmission, etc.

[0116] The capability information may be configured as an RRC message. That is, the base station may receive the capability information from the terminal via RRC, etc. According to one example, the capability information may be included in at least one of the existing RRC messages, such as UE-NR-Capability, PDCP-Parameters, RLC-Parameters, MAC-Parameters, Phy-Parameters, RF-Parameters, FeatureSets, and FeatureSetDownlink. Alternatively, according to another example, the capability information may be included in an RRC message that conveys information about a newly defined LP-WUS-related capability.

[0117] For example, a base station may transmit a request for capability information to a terminal. That is, the terminal may configure capability information based on the capability information received from the base station.

[0118]

[0119] Alternatively, the capability information may be configured based on configuration information that the base station can support for low-power wake-up signals. That is, the base station may transmit to the terminal in advance information about candidate configuration values ​​that the base station can support for parameters required for low-power wake-up operations. In this case, the terminal may determine the configuration values ​​usable by the terminal from among the received candidate configuration values.

[0120] Alternatively, the base station may transmit to the terminal information about candidate setting values ​​that the base station can support for parameters required for low-power wake-up operations, based on capability information. The terminal may determine a preferred or optimal setting value among the received candidate setting values.

[0121] The base station can receive capability information from the terminal via RRC, etc. In one example, the capability information can be transmitted by being included in at least one of the existing RRC messages such as UE-NR-Capability, PDCP-Parameters, RLC-Parameters, MAC-Parameters, Phy-Parameters, RF-Parameters, FeatureSets, and FeatureSetDownlink. Alternatively, in another example, the capability information can be transmitted by being included in an RRC message that carries information about a newly defined LP-WUS-related capability.

[0122] For example, when a terminal determines a usable configuration value from among candidate configuration values ​​received from a base station, the base station can indirectly receive capability information from the terminal in the form of a report of the determined configuration value. In this case, the report can be performed using an RRC message. Alternatively, the report can be in the form of a bitmap indicating availability in response to the configuration values ​​set by the base station. Each component of the bitmap can include some information such as a modulation scheme, a frequency band, and a time interval. This can be received via a newly defined PUCCH format for LP-WUS availability feedback.

[0123] Referring again to FIG. 9, the base station can transmit low-power wake-up signal configuration information to the terminal based on capability information (S920).

[0124] The base station may transmit configuration information set for low-power wake-up operations, such as low-power wake-up signal configuration information, to the terminal. The base station may transmit a low-power wake-up signal to the terminal based on the transmitted configuration information.

[0125] Based on the received configuration information, the terminal can monitor a low-power wakeup signal via a low-power wakeup receiver. If a condition triggering downlink control channel monitoring, such as the receipt of a low-power wakeup signal, is met, the terminal can monitor the downlink control channel via the transceiver. The base station can then perform wireless communication with the terminal via the transceiver.

[0126] Accordingly, a method and device for performing wireless communication using a low-power wake-up receiver capable of performing a wake-up operation that consumes power efficiently can be provided.

[0127] Hereinafter, each embodiment related to a method of performing wireless communication using a low-power wake-up receiver will be specifically described with reference to related drawings.

[0128] The present disclosure provides a terminal capability management method for transmitting and receiving signals via a low-power receiver in a 3GPP NR system. In particular, the present disclosure provides a terminal capability management method for supporting various characteristics of a receiver for transmitting and receiving wake-up signals in a form receivable by a receiver with low standby power, and a transmission and reception environment tailored to these characteristics.

[0129] In 3GPP NR, technologies such as idle / inactive operation and discontinuous transmission (DTX) / discontinuous reception (DRX) transmission methods are used to save terminal power. In addition, for terminal power saving, in a DTX / DRX environment, in order to reduce blind decoding for PDCCH monitoring of the next cycle, a DCI that notifies the necessity of transmission in the cycle prior to the PDCCH was transmitted. This is commonly referred to as a terminal wake-up signal, and is transmitted through DCI Format 2-6 in a search space defined for sending the DCI. The DCI has the following contents, and is transmitted scrambled using a special RNTI (Radio Network Temporary Identifier) ​​called PS_RNTI.

[0130] - block number 1, block number 2, ..., block number N

[0131] Block-related information is set, such as location, through RRC signaling, and each block consists of 1 bit for wake-up indication and a preset number of bits between 0 and 5 for scell dormancy indication. The terminal can determine whether PDCCH monitoring for reception in the next DRX cycle is necessary through reception of the signal, and if it is indicated that reception is not necessary, transmission and reception in the cycle can be skipped.

[0132] Meanwhile, an Idle UE periodically performs paging to determine whether it needs to transition to the Connected state. This paging is configured for each user group, and to prevent additional power consumption due to unnecessary paging to wake up UEs within the same group, a more sophisticated paging message can be transmitted using a Paging Early Indication (PEI) message. This message is transmitted in DCI format 2-7 and through a search space specifically defined for this DCI. The DCI contains the following contents and is scrambled using a special RNTI, PEI_RNTI, for this purpose.

[0133] - Paging early indication: The size is determined at the upper level, the corresponding position is determined for each UE, and if the bit of the corresponding position is 1, the next paging occasion is read.

[0134] - TRS (tracking reference signal) availability indication: included when required.

[0135] Meanwhile, in cases where it is necessary to perform terminal power reduction on a larger scale due to requirements such as Ambient IoT or REDCAP (Reduced Capability), a wake-up signal (referred to as LP-WUS in this disclosure) that supports a receiver with low standby power in hardware and a receiver that receives the signal (referred to as LP-WUR in this disclosure) have been introduced.

[0136] These LP-WUS and LP-WUR can be applied to low-power WUS / WUR for power-sensitive small form factor devices, including IoT use cases such as industrial sensors or controllers, and wearables, but are not limited thereto. They can also be applied to other use cases where low-power wake-up operations can be applied.

[0137] To achieve this, a detailed design is required for the architecture of a low-power wakeup receiver and the wakeup signal to support the wakeup receiver. Furthermore, a detailed design is required for the L1 procedures and upper-layer protocol changes required to support the wakeup signal. Furthermore, the system impacts, such as network power consumption, coexistence with non-low-power WUR terminals, and network coverage / capacity / resource overhead, must be studied.

[0138] In particular, for the design of LP-WUS, signals with the following structures can be used.

[0139] - OOK (On-Off Keying): This is a method of dividing a signal transmission section into time series and transmitting 1 bit for each time section based on whether or not a specific frequency signal was transmitted in that time section.

[0140] - FSK (Frequency-Shift Keying): A method of dividing a signal transmission section into a time series and transmitting K bits for each time section based on which frequency signal was transmitted in that time section. Here, the number of transmittable frequencies used is 2 to the power of K.

[0141] - OFDMA-based signal: This is a method that uses a signal of a similar form to the existing PDCCH or RACH preamble / reference signal / sync signal.

[0142] Additionally, two types of receiving methods are being discussed for receiving the LP-WUS.

[0143] - Type 1: This is an always-on receiver, which has high relative power consumption but does not have any time constraints on the transmission signal.

[0144] - Type 2: This is a receiver that turns on periodically, has low relative power consumption, but has a time constraint on the transmission signal and requires periodic synchronization.

[0145] Among these, a new synchronization signal, LP-SS (low power synchronization signal), was introduced for Type 2 to synchronize low-power receiving terminals.

[0146] With regard to the hardware characteristics of the receiver, improvements are discussed for three types of receivers for receiving OOK, two types of receivers for receiving FSK, and a receiver for receiving OFDMA-based signals.

[0147] OOK receivers being discussed include RF (Radio Frequency) envelope-based receivers that have low standby power but high noise sensitivity and therefore high required transmit power; IF (Intermediate Frequency) receivers that have good noise sensitivity but relatively high standby power and low hardware cost; and Zero-IF receivers that are similar to IF receivers but can borrow the structure of existing OFDM receivers. In addition, FSK receivers being discussed include receivers that have the basic structures of IF receivers and Zero-IF receivers attached in parallel. OFDMA-based receivers being discussed include existing OFDM-based receivers that have a structure similar to FSK receivers or omit modules that require a lot of power, such as IFFT (Inverse fast Fourier transform), by using matched filters.

[0148] Existing NR signals are based on OFDM and consist of a set of resource elements (REs) with a time interval equal to the symbol length for each subcarrier. The newly introduced LP-WUS must fundamentally utilize a structure that can be received with relatively low power compared to OFDM signal receivers, and thus, different signal types can be used compared to existing OFDM. These signals come in a wide variety of types, and the optimal signal may vary depending on the characteristics or required performance of the terminal. Therefore, a method for managing terminal capabilities related to LP-WUS is required to configure a transmission and reception environment that satisfies each required characteristic of terminals operating based on LP-WUS. In particular, in order for a base station to establish an LP-WUS transmission environment in which terminals can receive with optimal performance, there is a need to exchange capability information in advance, in the form of information about the type of hardware receiver and the signal that the terminal can transmit and receive, and at what quality.

[0149] The present disclosure provides a method for exchanging capability information of a receiving terminal for transmitting and receiving LP-WUS signals. In particular, a method is provided for transmitting a WUS format and hardware characteristics usable by the terminal to a base station and providing feedback on established WUS signal settings.

[0150] The present disclosure provides (1) a method for configuring terminal capability information, (2) a method for transmitting terminal capability information, and (3) a method for providing terminal feedback according to signal settings.

[0151]

[0152] Example 1. Method for configuring terminal capability information

[0153] Hardware used to receive LP-WUS signals can advantageously limit the types of signals it can accept to reduce power consumption. For example, it may be advantageous for a single piece of hardware to operate within a predefined, strictly defined set of possible candidates for the transmission frequency, transmission power, signal waveform, beam configuration, and modulation type. In other words, the hardware of a single low-power terminal may have limitations in the aforementioned transmission frequency, minimum reception power, signal waveform, beam, and modulation types.

[0154] In addition, since LP-WUS and general NR are operated on different hardware and the NR transmission hardware and the state transition of the Main Radio (MR) are performed by LP-WUS, the delay from LP-WUS to MR state transition can be defined. In addition, in case of periodic reception as in the aforementioned Type 2, the time required for synchronization, the average frequency at which Wake-up is performed, the required delay, etc. can also be included in the capability information. That is, the capability information of a terminal receiving LP-WUS can be composed of one or more of the following information.

[0155] - Whether the terminal can receive LP-WUS

[0156] - LP-WUS reception band range of the terminal

[0157] - Receiver type or required receiving power

[0158] - Maximum or minimum delay from LP-WUS reception to MR wake-up

[0159] - Allowable phase error or required phase accuracy

[0160] - Allowable transmission signal modulation method: OOK / FSK / other defined WUS modulation method

[0161] - The maximum number of bits that can be transmitted over different frequencies in one time interval

[0162] - Allowed or supported unit time interval: This usually means one symbol interval for OOK / FSK.

[0163] - Minimum or maximum synchronization interval required

[0164] - Number of LP-WUS that can be received simultaneously

[0165] - Interoperability with MR: Whether reception is possible when MR is in wake-up state

[0166] - Average wake-up frequency or task execution frequency according to terminal service characteristics

[0167] - Required delay from traffic generation to WUS transmission, or from WUS transmission to traffic transmission, or from traffic generation to traffic transmission

[0168] The values ​​set above can be set to multiple values, and can also be set differently for different capability information. For example, the available bandwidth range for OOK and FSK can be set differently.

[0169]

[0170] Example 2. Method for transmitting terminal capability information

[0171] This embodiment is a method for a terminal to transmit its LP-WUS-related capability information to a base station via RRC or the like. To this end, a new RRC message that transmits unique LP-WUS-related capability information may be defined. The capability-related information provided in Embodiment 1 may be configured in one or more of the following RRC messages.

[0172] - UE-NR-Capability

[0173] - PDCP-Parameters

[0174] - RLC-Parameters

[0175] - MAC-Parameters

[0176] - Phy-Parameters

[0177] - RF-Parameters

[0178] - FeatureSets

[0179] - FeatureSetDownlink

[0180] - A new RRC message that carries unique LP-WUS-related capability information.

[0181] Within the above RRC message, terminal capabilities can be transmitted by configuring an RRC message in the following format.

[0182] - Whether the terminal can receive LP-WUS, transmitted in the form of Enumerated {supported}

[0183] - Message related to the terminal's LP-WUS reception band range, expressed in the form of band number, start and end ARFCN, or common RB index of the configured downlink band.

[0184] - Available receiver types, expressed in index form

[0185] - Required receive power expressed in dBm, or in the form of an offset relative to the SSB, CSI-RS, or PDSCH transmit power of a specific MCS.

[0186] - Maximum or minimum delay from LP-WUS reception to MR wake-up, expressed as a representative value index, absolute time value, etc.

[0187] - Allowable phase error or required phase accuracy, expressed as phase value, rate per cycle, etc., or whether infinite error is allowed.

[0188] - A method of modulating an acceptable transmission signal, expressed in the form of a bitmap or index, etc.

[0189] - The maximum number of bits that can be transmitted over different frequencies per time interval, expressed as an integer or power of 2.

[0190] - Allowable unit time intervals expressed as SCS indexes corresponding to slot lengths, or absolute time values, or integer values ​​representing multiples of the shortest slot length.

[0191] - The maximum or minimum required synchronization execution interval, expressed as a representative value index, absolute time value, etc.

[0192] - The number of LP-WUS that can be received simultaneously, expressed as an integer, etc.

[0193] - Whether or not there is interoperability with MR, expressed as support for simultaneous reception with MR in the form of Enumerated {supported}

[0194] - Average wake-up frequency expressed as a representative value index, absolute time value, etc., or task execution frequency expressed as a terminal category or service type.

[0195] - The required delay from traffic generation to WUS transmission, or from WUS transmission to traffic transmission, or from traffic generation to traffic transmission, expressed as a representative value index, absolute time value, terminal category, or service type.

[0196] - Combination information of two or more of the above capability elements, in the form of a table index or sub-RRC message.

[0197] Information related to the corresponding capability can be defined within a single RRC message or across different RRC messages. For example, band information can be defined in RF-Parameters, and the allowed signal modulation method can be defined in Phy-Parameters.

[0198]

[0199] Example 3. Terminal feedback method according to signal setting

[0200] A terminal can transmit its capability information to a base station by following the procedure below.

[0201] First, it can be transmitted together with other capability information at the time of initial connection. That is, if LP-WUS related capability information is requested in the request list transmitted by the UE-CapabilityRAT-RequestList message sent by UECapabilityEnquery, the terminal can transmit a message similar to that set in Embodiment 2 in UE-NR-Capability or an internal detailed RRC message. After receiving the capability, the base station can perform LP-WUS configuration according to the terminal capability information and transmit it back to the terminal. That is, the procedure in this case is as follows.

[0202] <1> The base station requests LP-WUS related capabilities to the UE.

[0203] <2> The terminal transmits its own capability information related to LP-WUS.

[0204] <3> The base station transmits the LP-WUS settings to be actually used to the terminal.

[0205] Alternatively, if the base station performs LP-WUS-related configuration prior to reporting the capability via RRC, the terminal can indirectly transmit capability information by reporting which of these configurations it can use. To this end, a report request using a new RRC message requesting the report can be transmitted from the base station to the terminal after the LP-WUS configuration. Alternatively, the request message can be included in the LP-WUS configuration or performed implicitly. In other words, the terminal can always report the corresponding feedback when the LP-WUS-related configuration is performed. The procedure in this case is as follows.

[0206] <1> The base station transmits the LP-WUS settings that it can operate to the terminal.

[0207] <2> The terminal feeds back its available LP-WUS settings to the base station.

[0208] <3> The base station transmits the LP-WUS settings to be actually used to the terminal.

[0209] The feedback may be implemented using the method used to construct the RRC message in Example 2. Alternatively, it may be in the form of a bitmap indicating availability in response to the LP-WUS transmission methods configured by the base station. Each element of the bitmap may include some information, such as modulation scheme, frequency band, and time interval. This may be transmitted via a newly defined PUCCH format for LP-WUS availability feedback.

[0210] A hybrid procedure of the two procedures described above can also be considered, following the following sequence:

[0211] <1> The base station requests LP-WUS related capabilities to the UE.

[0212] <2> The terminal transmits its own capability information related to LP-WUS.

[0213] <3> The base station transmits the LP-WUS candidate settings to the terminal.

[0214] <4> The terminal feeds back its preferred LP-WUS setting(s) to the base station.

[0215] <5> The base station transmits the LP-WUS settings to be actually used to the terminal.

[0216]

[0217] Meanwhile, LP-SS for low-power wake-up receivers can be used for time and / or frequency synchronization and RRM measurements. In this case, the synchronization signal can be configured as part of the LP-WUS or separately. Furthermore, the synchronization signal can be configured as an aperiodic signal or a periodic signal transmitted at a predetermined period. In the case of LP-WUR capable of receiving existing PSS / SSS, the existing PSS / SSS can be used as the synchronization signal.

[0218] The structure of an LP-SS can be composed of a sequence, or a sequence followed by encoded bits (including CRC). An LP-SS can be configured per cell and can transmit a beam index. For example, if an overlay OFDM sequence is supported for an LP-SS, the same sequence type can be used for both the LP-SS and the LP-WUS.

[0219] Signals / channels in LP-WUS and MR can be transmitted and received within the same band. Furthermore, signals / channels in LP-WUS and MR can be transmitted and received on the same carrier within the band. Alternatively, signals / channels in LP-WUS and MR can be transmitted and received on different carriers within the band.

[0220] Alternatively, the signals / channels in LP-WUS and MR may be transmitted and received in different bands. That is, LP-WUS may be transmitted and received in a band other than the frequency band in MR, such as an unlicensed band.

[0221] LP-WUS can be configured in conjunction with bandwidth parts set for the terminal. LP-WUS can be configured to be transmitted in the initial bandwidth part. Alternatively, LP-WUS can be configured for a location in the frequency domain where it is transmitted for each bandwidth part. For example, it can be configured with a predetermined number of consecutive resource blocks (PRBs) at the top or bottom of each bandwidth part, or it can be configured with a predetermined number of resource blocks spaced apart by an offset value from the top or bottom of each bandwidth part.

[0222] LP-WUS can be configured to transmit and receive within a guard band configured in a frequency band.

[0223] The LP-WUS bandwidth size is configured as an integer number of PRBs, and can be configured to be 5 MHz or less in IDLE / Inactive mode, and can be configured to a maximum of 20 MHz. However, this is only an example and can be set differently as needed.

[0224] If the channel condition of LP-WUS is worse than a predetermined standard, repeated transmission of LP-WUS can be configured. Also, if the channel condition of LP-WUS is worse than a predetermined standard, the transmission cycle of LP-WUS can be set to be shorter. Also, if the channel condition of LP-WUS is worse than a predetermined standard, the wake-up operation using LP-WUR can be converted to a legacy wake-up operation in MR.

[0225] In RRC CONNECTED mode, a minimum time interval between LP-WUS reception and the MR initiating PDCCH monitoring may be configured. In this case, the minimum time interval may be determined at least in part based on the LP-WUS processing time, the MR transition time for ramp-up, and the MR's time / frequency synchronization. Furthermore, the minimum time interval may be reported to the base station as capability information of the terminal. In this case, at least one minimum time interval information supportable by the terminal may be reported.

[0226] In addition, the present disclosure proposes a specific method for an operation to be performed after waking up when a terminal that seeks to minimize power consumption by using a low-power wake-up receiver (WUR) receives a wake-up signal (WUS) through the WUR.

[0227] The terminal may include an ultra-low power receiver, separate from the existing transceiver, so as to receive a wake-up signal from the base station while consuming only the minimum power even in a short period or always ON state. The ultra-low power receiver is defined as a receiver that can receive only the wake-up signal and essential signals related thereto, and is a receiver separate from the transceiver used for conventional data transmission and reception. When the terminal enters deep sleep mode or low power wake-up receiver (WUR) mode, the transceiver (Main Radio, MR tx. / rx. module) used to transmit and receive conventional NR signals / channels is turned OFF, and only the LP wake-up receiver is turned ON to receive only the wake-up signal and essential signals related thereto, thereby drastically reducing the power consumption of the terminal. At this time, a terminal that receives a wake-up signal through the receiver can be instructed to switch to main radio (MR) mode, and the terminal can switch the mode from LR to MR and perform communication through a transceiver for existing NR data transmission and reception.

[0228] The present disclosure proposes a specific method for resolving an error situation that may occur when an unintended terminal receives a wake-up signal for a terminal that monitors WUS only through LP-WUR with the MR transceiver turned off based on the aforementioned contents, and for allowing the terminal and base station to quickly recognize this and re-transmit to LR / deep sleep mode (or maintain LR ON state, or synchronize low-power receiver mode between each other).

[0229] The present disclosure proposes a method for turning on / off (i.e., PDCCH monitoring) the LP-WUR and MR modules of a terminal that monitors a Wake Up Signal (WUS) through a Low-Power Wake Up Receiver (LP-WUR, LR) upon receiving a Wake Up signal. More specifically, when the terminal receives a WUS through the LP-WUR, it is proposed to set a timer (i.e., LR_transition_timer) to define a period for continuing downlink monitoring of LR and MR while maintaining the WUR in the ON state for a specific period of time even when the tx. / rx. module of the main radio for data transmission and reception is powered ON.

[0230] The terminal can monitor the downlink through two receivers with both LR and MR powered ON while the timer is running. If the terminal successfully receives a PDCCH that is set to be monitored by the terminal through the MR while the timer is running, the terminal terminates the timer and turns off the LP-WUR receiver. In other words, WUS monitoring through LP WUR is stopped. If an indicator indicating a transition to LR mode is received from the base station while the timer is running or the timer expires, the terminal can turn off the power of the MR module and switch to LR mode to maintain WUS monitoring.

[0231] While the timer is running, the terminal keeps both the Wake-Up Receiver and the Main Radio Transceiver ON, and continues the downlink monitoring set in each mode. If the terminal receives a PDCCH transmitted to itself via MR while the timer is running, the terminal turns OFF the LR receiver of the terminal and turns ON only the MR tx. / rx. module. That is, the conventional NR operation is performed. If the timer expires or if the base station instructs the terminal to switch to LP-WUR mode while the timer is running, the terminal can turn OFF the MR tx / rx module (i.e., stop PDCCH monitoring via the MR module) and continue WUS monitoring via LP-WUR only. If an additional WUS is received via LP-WUR while the timer is running, the terminal can restart the timer and continue monitoring via MR and LR while the timer is running as described above.

[0232] In addition, when the terminal receives a WUS through LP-WUR, the terminal turns ON the power of the tx. / rx. module of the main radio for data transmission and reception and switches the WUR to OFF. That is, the terminal always keeps ON only one radio module among the MR and LR, and can determine which radio module to activate based on whether or not WUS is received, timer expiration, LR setting information, or LR activation / deactivation instruction information. Accordingly, when the LR mode is set for any terminal, or additionally, LR mode activation is instructed, the terminal can maintain the LR on and MR off states. When the terminal receives a WUS from the base station through LR, the terminal can turn off the LR and turn on the MR to monitor the PDCCH.

[0233] At this time, if the timer for LR switching expires or explicit LR mode switching instruction information is received from the base station, the terminal turns off MR and turns on LR again to switch to LR mode. Specifically, the terminal that receives WUS in LR mode and switches to MR mode monitors PDCCH through MR and starts the timer for switching to LR mode. If the terminal successfully receives PDCCH that is set to be monitored by the terminal through MR while the timer is running, the terminal can restart the timer or stop the LR switching operation based on the timer. In the latter case, the terminal can enter LR mode again by explicit LR mode switching setting or LR mode activation instruction information of the base station. In the former case, the terminal can enter LR mode when the restarted timer expires or by explicit setting / instruction information of the terminal.

[0234] The timer of the present disclosure is a timer that starts when a WUS is received on a WUR, and while the timer is running, the terminal performs both WUS and PDCCH monitoring through LR and MR, and provides a period for maintaining both modes simultaneously for the duration of the timer, instead of performing an immediate switch from LR to MR. In other words, the terminal can perform a switch from LR to MR only when it receives a clear signal from the base station for a switch to MR after receiving a WUS.

[0235] Additionally, the timer may be defined as the same timer as the timer for transitioning from MR mode to LR mode. That is, the timer is defined as a timer that is (re)started when a PDCCH or WUS is received in MR or LR. If the terminal receives an LR-related configuration message including the LR_transition_timer from the base station, the terminal in MR mode (re)starts the LR_transition _timer whenever it receives a PDCCH. When the timer expires, the terminal enters LR mode.

[0236] If the terminal receives a WUS in LR mode, it starts the LR_transition_timer, and if the terminal successfully receives the PDCCH that it is set to monitor through MR (i.e., if the terminal successfully receives the RNTI-based DCI format that it is set to monitor), it restarts the LR_transition_timer.

[0237] If an indication explicitly notifying entry into LR mode is received while the timer is running, the timer is stopped. Alternatively, if the terminal receives a WUS in LR mode, the LR_transition_timer is started, and if reception of a PDCCH that the terminal is configured to monitor through MR is successful (i.e., reception of an RNTI-based DCI format that the terminal is configured to monitor is successful), the LR_transition_timer is stopped so that the MR mode is maintained until explicit LR mode transition setting or LR mode activation indication information is received from the base station.

[0238] The above LR_transition_timer is a new timer, and the timer value for any terminal can be set by the base station. Alternatively, the LR-transition_timer can reuse an existing timer value. For example, the DRX inactivity timer for the terminal's DRX operation can be utilized as the above LR_transition_timer.

[0239] The above LR_transition_timer is set for each terminal or individual terminal belonging to a terminal group in LR mode set to monitor any one WUS, and when the corresponding WUS is transmitted by the base station, the base station can also activate the same timer value for the LR_transition_timer set for each terminal set to monitor the corresponding WUS. Through this, the base station can detect a PDCCH transmission / reception error of a terminal that needs to switch to MR mode according to WUS transmission according to the operation embodiment of the terminal according to WUS reception defined above, or synchronize terminals that have switched to MR mode according to WUS transmission and have switched back to LR mode according to timer expiration among terminals.

[0240] For example, the proposed timer can also be applied to PDCCH transmission / reception errors on MR after WUS transmission / reception between the base station and the terminal. That is, this means that the proposed timer can operate not only at the terminal but also at the base station. Even if the transmission of the WUS was correct to the desired UE, if the base station does not receive any feedback (e.g., HARQ feedback for the PDCCH) from the terminal during the proposed timer, it may be that the terminal did not wake up for some reason, or woke up but did not receive the PDCCH on the MR. In this case, the terminal may have re-entered LR mode or may not have switched to MR mode. In order for the base station to recognize such a situation, the base station can start the proposed timer when it transmits a WUS to the terminal, and can retry the WUS transmission to the LR receiver of the terminal when the timer expires. If, while the timer is running, any UL signal (e.g., HARQ feedback for DL ​​data) is received from the terminal, the timer stops and the terminal's MR mode transition can be recognized.

[0241] If a time interval is defined between the time at which the base station transmits the WUS on the LR and the time at which the PDCCH corresponding to the transmitted WUS is transmitted on the MR, the value of the timer can be set to a value greater than the time interval.

[0242] According to the above-described method, for a terminal configured to monitor LP-WUS via LR from a base station, an LR_transition_timer value for maintaining an MR activation state according to WUS reception and a timer-based LR mode transition according to the period may be set by the base station. However, the LR_transition_timer value may be set through a separate RRC parameter for the terminal configured for LR-WUS monitoring, or may follow a DRX inactivity timer value.

[0243] A terminal for which LP-WUS monitoring information is set, or a terminal for which LP-WUS monitoring information is set and monitoring for LP-WUS via LR is activated based on this (i.e., a terminal switched to LR mode), performs monitoring for WUS via LR according to the LP-WUS monitoring setting information. At this time, if reception of LP-WUS of a base station via LR is performed by any terminal, the terminal activates MR to perform monitoring for PDCCH based on the RNTI set to be monitored by the terminal. However, in this case, the LR_transition_timer is operated while maintaining a dual activation mode state that maintains an activated state for LR, and if PDCCH reception is successful via MR before the timer expires, the timer can be spotted and transitioned to a complete MR state (i.e., LR can be switched off).

[0244] On the other hand, if PDCCH reception through MR is not performed until LR-transition_timer expires after MR is switched to active state upon WUS reception, the terminal turns off MR and operates in LR mode again. Alternatively, if WUS is received, LR can be defined to be turned off and MR can be switched on, thereby switching to a complete MR state. In this case, if PDCCH reception through MR is successful while LR_transition_timer is running, the terminal can restart the LR_transition_timer. In this case as well, if PDCCH reception through MR is not performed until LR_transition_timer expires, the terminal can turn off MR and switch back to LR mode.

[0245] The above LR_transition_timer allows the base station or the network to manage the timer value according to the setting value for each terminal, and when the LR_transition_timer is activated for any terminal, the base station or the network can synchronize the timer count of the terminal based on the LR-transition_timer value set for the terminal and operate the timer. Accordingly, the base station or the network can synchronize the expiration and reset / restart of the LR-transition_timer for any terminal and synchronize whether or not to switch the LR mode accordingly.

[0246] The methods provided in this disclosure may be applied independently or may be combined and operated in any form. Furthermore, the terms used in this disclosure are arbitrary names that facilitate understanding of new terms. In practice, the technical concepts of this disclosure may be applied even when other terms with the same meaning are used.

[0247] According to the method provided in the present disclosure, terminal capability information for efficiently performing transmission and reception of LP-WUS signals transmitted in a form different from general NR can be shared.

[0248]

[0249] Hereinafter, the configuration of a terminal and a base station capable of performing some or all of the embodiments described with reference to FIGS. 1 through 9 will be described with reference to the drawings. The above description may be omitted to avoid redundant description, and in this case, the omitted content may be substantially equally applied to the description below, as long as it does not conflict with the technical spirit of the invention.

[0250] Fig. 10 is a drawing showing the configuration of a terminal (1000) according to another embodiment.

[0251] Referring to FIG. 10, a terminal (1000) according to another embodiment includes a low-power wake-up receiver (1020), a transceiver (1030), and a controller (1010) that controls the operation of the low-power wake-up receiver and the transceiver. According to an example, the transceiver is not limited to a single device, and may be composed of separate devices corresponding to the transmitter and the receiver.

[0252] The controller (1010) controls the overall operation of the terminal (1000) according to the method of performing wireless communication using a low-power wake-up receiver necessary to perform the present invention described above.

[0253] The controller (1010) may configure capability information related to reception of a low power wakeup signal (LP-WUS) via a low power wakeup receiver. In order to perform a low power wakeup operation using the low power wakeup receiver, the controller (1010) may configure capability information related to the low power wakeup operation. For example, the capability information may include at least one of support for a low power wakeup signal, information on a receivable frequency band, information on required reception power, and information on applicable modulation scheme. In this case, the modulation scheme information may further include information on support for a modulation scheme of a separately defined low power wakeup signal other than OOK and FSK, for example, a modulation scheme such as an overlaid OFDM sequence. In addition, the capability information may include at least one of information on a time gap between reception of a low power wakeup signal and monitoring of a downlink control channel via the transceiver. Additionally, the capability information may include information on whether the downlink control channel can be monitored through the transceiver while the low-power wake-up receiver is in the on state. That is, the capability information may further include information on whether the low-power wake-up receiver can be maintained in the on state while monitoring the downlink control channel by turning the transceiver on upon receiving a low-power wake-up signal through the low-power wake-up receiver.

[0254] The capability information may be configured as an RRC message. That is, the controller (1010) may transmit the capability information to the base station via RRC, etc. According to one example, the capability information may be included in at least one of the existing RRC messages such as UE-NR-Capability, PDCP-Parameters, RLC-Parameters, MAC-Parameters, Phy-Parameters, RF-Parameters, FeatureSets, and FeatureSetDownlink. Alternatively, according to another example, the capability information may be included in an RRC message that transmits information on a newly defined LP-WUS related capability.

[0255] For example, capability information may be configured when a request for capability information is received from a base station. That is, the controller (1010) may configure capability information according to capability information received from the base station.

[0256] Alternatively, the capability information may be configured based on configuration information that the base station can support for low-power wake-up signals. That is, the controller (1010) may receive, in advance, from the base station information on candidate setting values ​​that the base station can support for parameters required for low-power wake-up operations. In this case, the controller (1010) may determine setting values ​​usable by the terminal from among the received candidate setting values.

[0257] Alternatively, the controller (1010) may receive information from the base station about candidate setting values ​​that can be supported by the base station for parameters required for low-power wake-up operations, configured based on capability information. The controller (1010) may determine a preferred or optimal setting value for the terminal among the received candidate setting values.

[0258] The controller (1010) can transmit capability information to a base station via a transceiver. The controller (1010) can transfer the capability information to the base station via RRC, etc. According to one example, the capability information can be transmitted by being included in at least one of the existing RRC messages such as UE-NR-Capability, PDCP-Parameters, RLC-Parameters, MAC-Parameters, Phy-Parameters, RF-Parameters, FeatureSets, and FeatureSetDownlink. Alternatively, according to another example, the capability information can be transmitted by being included in an RRC message that conveys information on a newly defined LP-WUS-related capability.

[0259] For example, when the controller (1010) determines a configuration value available to the terminal from among candidate configuration values ​​received from the base station, the controller (1010) may indirectly transmit capability information to the base station in the form of reporting the determined configuration value. In this case, the reporting may be performed using an RRC message. Alternatively, the reporting may be in the form of a bitmap indicating availability in response to the configuration values ​​set by the base station. Each component of the bitmap may include some of the information, such as a modulation scheme, a frequency band, and a time interval. This may be transmitted via a newly defined PUCCH format for LP-WUS availability feedback.

[0260] Thereafter, the controller (1010) can receive configuration information set for a low-power wake-up operation. Based on the received configuration information, the controller (1010) can monitor a low-power wake-up signal through a low-power wake-up receiver. If a condition triggering monitoring of a downlink control channel, such as reception of a low-power wake-up signal, is met, the controller (1010) can monitor the downlink control channel through a transceiver. Thereafter, the controller (1010) can perform wireless communication with a base station through the transceiver.

[0261] Accordingly, a method and device for performing wireless communication using a low-power wake-up receiver capable of performing a wake-up operation that consumes power efficiently can be provided.

[0262] Fig. 11 is a drawing showing the configuration of a base station (1100) according to another embodiment.

[0263] Referring to FIG. 11, a base station (1100) according to another embodiment includes a transmitter (1120), a receiver (1130), and a controller (1110) that controls the operation of the transmitter and the receiver.

[0264] The controller (1110) controls the overall operation of the base station (1100) according to the method of performing wireless communication using the low-power wake-up receiver required to perform the aforementioned invention. The transmitter (1120) transmits downlink control information, data, and messages to the terminal through the corresponding channel. The receiver (1130) receives uplink control information, data, and messages from the terminal through the corresponding channel.

[0265] The controller (1110) may receive capability information required for receiving a low power wakeup signal (LP-WUS) through a low power wakeup receiver from a terminal. In order to perform a low power wakeup operation using the low power wakeup receiver, the terminal may configure capability information related to the low power wakeup operation. For example, the capability information may include at least one of support for a low power wakeup signal, information on a receivable frequency band, information on required reception power, and information on applicable modulation scheme. In this case, the modulation scheme information may further include information on whether a modulation scheme of a separately defined low power wakeup signal other than OOK and FSK, such as a modulation scheme such as an overlaid OFDM sequence, is supported. In addition, the capability information may include at least one of information on a time gap between reception of a low power wakeup signal and monitoring of a downlink control channel through the transceiver. Additionally, the capability information may include information on whether the downlink control channel can be monitored through the transceiver while the low-power wake-up receiver is in the on state. That is, the capability information may further include information on whether the low-power wake-up receiver can be maintained in the on state while monitoring the downlink control channel by turning the transceiver on upon receiving a low-power wake-up signal through the low-power wake-up receiver.

[0266] The capability information may be configured as an RRC message. That is, the controller (1110) may receive the capability information from the terminal via RRC, etc. According to one example, the capability information may be included in at least one of the existing RRC messages such as UE-NR-Capability, PDCP-Parameters, RLC-Parameters, MAC-Parameters, Phy-Parameters, RF-Parameters, FeatureSets, and FeatureSetDownlink. Alternatively, according to another example, the capability information may be included in an RRC message that conveys information on a newly defined LP-WUS-related capability.

[0267] For example, the controller (1110) may transmit a request for capability information to the terminal. That is, the terminal may configure capability information based on the capability information received from the base station.

[0268] Alternatively, the capability information may be configured based on configuration information that the base station can support for low-power wake-up signals. That is, the controller (1110) may transmit information in advance about candidate setting values ​​that the base station can support for parameters required for low-power wake-up operations to the terminal. In this case, the terminal may determine a setting value usable by the terminal from among the received candidate setting values.

[0269] Alternatively, the controller (1110) may transmit information on candidate setting values ​​that can be supported by the base station for parameters required for low-power wake-up operations based on capability information to the terminal. The terminal may determine a preferred or optimal setting value among the received candidate setting values.

[0270] The controller (1110) may receive capability information from the terminal via RRC, etc. According to one example, the capability information may be transmitted by being included in at least one of the existing RRC messages such as UE-NR-Capability, PDCP-Parameters, RLC-Parameters, MAC-Parameters, Phy-Parameters, RF-Parameters, FeatureSets, and FeatureSetDownlink. Alternatively, according to another example, the capability information may be transmitted by being included in an RRC message that conveys information on a newly defined LP-WUS-related capability.

[0271] For example, when a terminal determines a usable setting value from among candidate setting values ​​received from a base station, the controller (1110) can indirectly receive capability information from the terminal in the form of reporting the determined setting value. In this case, the reporting can be performed using an RRC message. Alternatively, the reporting can be in the form of a bitmap indicating availability in response to the setting values ​​set by the controller (1110). Each component of the bitmap can include some of the information such as modulation method, frequency band, and time interval. This can be received through a newly defined PUCCH format for LP-WUS availability feedback.

[0272] The controller (1110) may transmit low-power wake-up signal configuration information to the terminal based on capability information. The controller (1110) may transmit configuration information set for a low-power wake-up operation, such as low-power wake-up signal configuration information, to the terminal. The controller (1110) may transmit a low-power wake-up signal to the terminal based on the transmitted configuration information.

[0273] Based on the received configuration information, the terminal can monitor a low-power wake-up signal via a low-power wake-up receiver. If a condition triggering monitoring of a downlink control channel, such as receipt of a low-power wake-up signal, is met, the terminal can monitor the downlink control channel via a transceiver. Thereafter, the controller (1110) can perform wireless communication with the terminal via the transceiver.

[0274] Accordingly, a method and device for performing wireless communication using a low-power wake-up receiver capable of performing a wake-up operation that consumes power efficiently can be provided.

[0275] The above-described embodiments may be supported by standard documents disclosed in at least one of the wireless access systems, IEEE 802, 3GPP, and 3GPP2. That is, steps, components, and parts not described in the present embodiments to clearly illustrate the technical concepts herein may be supported by the above-described standard documents. Furthermore, all terms disclosed in this specification may be explained by the above-described standard documents.

[0276] The embodiments described above may be implemented through various means. For example, the embodiments may be implemented through hardware, firmware, software, or a combination thereof.

[0277] In the case of hardware implementation, the method according to the present embodiments may be implemented by one or more ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), DSPDs (Digital Signal Processing Devices), PLDs (Programmable Logic Devices), FPGAs (Field Programmable Gate Arrays), processors, controllers, microcontrollers, or microprocessors.

[0278] When implemented using firmware or software, the methods according to the present embodiments may be implemented in the form of devices, procedures, or functions that perform the functions or operations described above. The software code may be stored in a memory unit and executed by a processor. The memory unit may be located within or outside the processor and may exchange data with the processor via various known means.

[0279] Additionally, terms such as "system," "processor," "controller," "component," "module," "interface," "model," or "unit" as described above may generally refer to a computer-related entity, such as hardware, a combination of hardware and software, software, or software in execution. For example, the aforementioned components may be, but are not limited to, a process driven by a processor, a processor, a controller, a control processor, an object, a thread of execution, a program, and / or a computer. For example, both an application running on a controller or a processor and the controller or the processor may be components. One or more components may be within a process and / or thread of execution, and the components may be located on a single device (e.g., a system, a computing device, etc.) or distributed across two or more devices.

[0280] The above description is merely an illustrative example of the technical idea of ​​the present disclosure, and those skilled in the art to which the present disclosure pertains will appreciate that various modifications and variations can be made without departing from the essential characteristics of the technical idea of ​​the present disclosure. In addition, the present embodiments are not intended to limit the technical idea of ​​the present disclosure but rather to explain it, and therefore the scope of the technical idea of ​​the present disclosure is not limited by these embodiments. The scope of protection of the present disclosure should be interpreted by the claims below, and all technical ideas within a scope equivalent thereto should be interpreted as being included within the scope of the rights of the present disclosure.

[0281]

[0282] CROSS-REFERENCE TO RELATED APPLICATION

[0283] This patent application claims priority under 35 USC §119(a) to Korean Patent Application No. 10-2023-0087727, filed in Korea on July 6, 2023, and Korean Patent Application No. 10-2024-0086797, filed in Korea on July 2, 2024, the entire contents of which are incorporated herein by reference. In addition, this patent application claims priority in countries other than the United States for the same reasons, the entire contents of which are incorporated herein by reference.

Claims

1. A method for a terminal to perform wireless communication using a low power wakeup receiver (LP-WUR), A step of configuring capability information related to receiving a low power wakeup signal (LP-WUS) through the low power wakeup receiver; and A method comprising the step of transmitting the above capability information to a base station via a transceiver.

2. In paragraph 1, The above capability information is: A method comprising at least one of information on whether the low-power wake-up signal is supported, information on a receivable frequency band, information on required reception power, information on applicable modulation method, information on a time gap between the reception of the low-power wake-up signal and the monitoring of the downlink control channel through the transceiver, and information on whether the downlink control channel can be monitored through the transceiver in the on state of the low-power wake-up receiver.

3. In paragraph 1, The above capability information is: How to configure RRC messages.

4. In paragraph 1, The above capability information is: A method configured when a request for the above capability information is received from the base station.

5. In paragraph 1, The above capability information is: A method configured based on configuration information supportable by the base station for the low-power wake-up signal.

6. A method for controlling the operation of a terminal performing wireless communication using a low power wakeup receiver (LP-WUR) by a base station, A step of receiving capability information required for receiving a low power wakeup signal (LP-WUS) through the low power wakeup receiver from the terminal; and A method comprising the step of transmitting low-power wake-up signal configuration information to the terminal based on the above capability information.

7. In paragraph 6, The above capability information is: A method comprising at least one of information on whether the low-power wake-up signal is supported by the terminal, information on a receivable frequency band, information on required reception power, information on applicable modulation method, information on a time gap between the reception of the low-power wake-up signal and the monitoring of the downlink control channel through the transceiver of the terminal, and information on whether the downlink control channel can be monitored through the transceiver in the on state of the low-power wake-up receiver.

8. In paragraph 6, The above capability information is: How to configure RRC messages.

9. In paragraph 6, The above capability information is: A method configured when a request for the above capability information is transmitted to the terminal.

10. In paragraph 6, The above capability information is: A method configured based on configuration information supportable by the base station for the low-power wake-up signal.

11. In a terminal performing wireless communication using a low power wakeup receiver (LP-WUR), Low power wake-up receiver; Transmitter and receiver; and Including a controller that controls the operation of the low-power wake-up receiver and the transceiver, The above controller, A terminal that configures capability information related to receiving a low power wakeup signal (LP-WUS) through the low power wakeup receiver and transmits the capability information to a base station through the transceiver.

12. In paragraph 11, The above capability information is: A terminal including at least one of information on whether the low-power wake-up signal is supported, information on a receivable frequency band, information on required reception power, information on an applicable modulation method, information on a time gap between the reception of the low-power wake-up signal and the monitoring of the downlink control channel through the transceiver, and information on whether the downlink control channel can be monitored through the transceiver in the on state of the low-power wake-up receiver.

13. In paragraph 11, The above capability information is: A terminal consisting of RRC messages.

14. In paragraph 11, The above capability information is: A terminal configured when a request for the above capability information is received from the base station.

15. In paragraph 11, The above capability information is: A terminal configured based on configuration information that can be supported by the base station for the low-power wake-up signal.

Images