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

Abstract

An LP-WUS, which is a signal received through a low-power receiver of a terminal before PDCCH monitoring is performed may be used in order to dynamically change a semi-static configuration related to PDCCH monitoring. Specifically, some of values of a PDCCH monitoring-related parameter configured through an RRC parameter may be indicated via the LP-WUS, or the values of the PDCCH monitoring-related parameter may be changed via the LP-WUS.

Description

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

[0001] This specification relates to methods and devices used in wireless communication systems.

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

[0003] The technical problem to be achieved through this specification is to provide a method for efficiently transmitting and receiving wireless communication signals and an apparatus for doing so.

[0004] The technical challenges are not limited to those described above, and other technical challenges can be inferred from the embodiments.

[0005] The present specification provides a method and apparatus for transmitting and receiving signals in a wireless communication system.

[0006] In one aspect of the present specification, a method is provided comprising: receiving configuration information including parameters related to PDCCH monitoring; receiving an LP-WUS through a first receiver of a terminal; and monitoring a PDCCH through a second receiver of the terminal based on the LP-WUS and the configuration information, wherein the LP-WUS includes information related to an instruction or change regarding the value of the parameters.

[0007] In another aspect of the present specification, a device for performing the method comprises a terminal, a processor, and a storage medium.

[0008] In another aspect of the present specification, a method is provided comprising: transmitting configuration information including parameters related to PDCCH monitoring; transmitting an LP-WUS for a first receiver of a terminal; and transmitting a PDCCH for a second receiver of the terminal based on the LP-WUS and the configuration information, wherein the LP-WUS includes information related to an instruction or change regarding the value of the parameters.

[0009] In another aspect of the present specification, a base station, a processor, and a storage medium are provided as an apparatus for performing the method.

[0010] The above devices may include at least a terminal, a network, and an autonomous vehicle capable of communicating with other autonomous vehicles other than the device.

[0011] The embodiments of this specification described above are merely some of the preferred embodiments of this specification, and various embodiments reflecting the technical features can be derived and understood by those skilled in the art based on the detailed description.

[0012] According to one embodiment of the present specification, when a signal is transmitted and received between communication devices, there is an advantage that more efficient signal transmission and reception can be performed through an operation differentiated from the prior art.

[0013] The technical effects are not limited to those described above, and other technical effects may be inferred from the examples.

[0014] Figure 1 illustrates the structure of a radio frame.

[0015] Figure 2 illustrates a resource grid of slots.

[0016] FIG. 3 illustrates a communication procedure between a terminal and a base station applicable to the present disclosure.

[0017] FIGS. 4 to 7 are drawings for explaining a signal transmission and reception method according to an embodiment of the present disclosure.

[0018] FIGS. 8 to 10 illustrate devices according to embodiments of the present disclosure.

[0019] The following technologies can be used in various wireless access systems such as CDMA, FDMA, TDMA, OFDMA, and SC-FDMA. CDMA can be implemented using wireless technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented using wireless technologies such as GSM (Global System for Mobile Communications), GPRS (General Packet Radio Service), and EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented using wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is part of the UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is part of E-UMTS (Evolved UMTS) using E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0020] For the sake of clarity, the description is based on 3GPP communication systems (e.g., LTE, NR), but the technical scope of this specification is not limited thereto. LTE refers to technology from 3GPP TS 36.xxx Release 8 onwards. Specifically, LTE technology from 3GPP TS 36.xxx Release 10 onwards is referred to as LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onwards is referred to as LTE-A pro. 3GPP NR refers to technology from TS 38.xxx Release 15 onwards. LTE / NR may be referred to as a 3GPP system. "xxx" indicates a specific standard document number. LTE / NR may be collectively referred to as a 3GPP system. Regarding background technology, terms, abbreviations, etc. used in the description of this specification, reference may be made to matters described in previously published standard documents. For example, the following documents may be referenced.

[0021] 3GPP NR

[0022] - 38.211: Physical channels and modulation

[0023] - 38.212: Multiplexing and channel coding

[0024] - 38.213: Physical layer procedures for control

[0025] - 38.214: Physical layer procedures for data

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

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

[0028] Figure 1 illustrates the structure of a wireless frame used in NR.

[0029] In NR, uplink (UL) and downlink (DL) transmissions consist of frames. A radio frame has a length of 10 ms and is defined as two 5 ms half-frames (HF). A half-frame is defined as five 1 ms subframes (SF). A subframe is divided into one or more slots, and the number of slots within a subframe depends on the subcarrier spacing (SCS). Each slot contains 12 or 14 OFDM(A) symbols depending on the cyclic prefix (CP). When normal CP is used, each slot contains 14 symbols. When extended CP is used, each slot contains 12 symbols. Here, the symbols may include OFDM symbols (or CP-OFDM symbols) or SC-FDMA symbols (or DFT-s-OFDM symbols).

[0030] Table 1 illustrates how the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS when a standard CP is used.

[0031] [Table 1]

[0032]

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

[0034] [Table 2]

[0035]

[0036] In an NR system, OFDM(A) numerology (e.g., SCS, CP length, etc.) can be configured differently among multiple cells merged into a single terminal (User Equipment; UE). Accordingly, the (absolute time) interval of a time resource (e.g., SF, slot, or TTI) (collectively referred to as TU (Time Unit) for convenience) composed of the same number of symbols can be configured differently among the merged cells.

[0037] NR supports multiple OFDM (Orthogonal Frequency Division Multiplexing) numerologies (e.g., subcarrier spacing, SCS) to support various 5G services. For example, if the SCS is 15 kHz, it supports a wide area in traditional cellular bands, and if the SCS is 30 kHz / 60 kHz, it can support dense-urban, lower latency, and wider carrier bandwidth.

[0038] The NR frequency band is defined by two types of frequency ranges (FR) (FR1 / FR2). FR1 / FR2 can be configured as shown in Table 3 below. Additionally, FR2 can refer to millimeter wave (mmW).

[0039] [Table 3]

[0040]

[0041] Figure 2 illustrates the slot structure of an NR frame.

[0042] A slot contains multiple symbols in the time domain. For example, in the case of a standard CP, one slot contains 14 symbols, and in the case of an extended CP, one slot contains 12 symbols. A carrier contains multiple subcarriers in the frequency domain. A Resource Block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. Multiple RB interlacs (simply interlacs) can be defined in the frequency domain. An interlac m∈{0, 1, ..., M-1} can be composed of (common) RBs {m, M+m, 2M+m, 3M+m, ...}. M represents the number of interlacs. A Bandwidth Part (BWP) is defined as multiple consecutive RBs (e.g., physical RB, PRB) in the frequency domain and can correspond to a single OFDM numerology (e.g., SCS(u), CP length, etc.). A carrier wave may contain up to N (e.g., 5) BWPs. Data communication is performed through the active BWPs, and only one BWP can be active for a single terminal within a single cell / carrier wave. In the resource grid, each element is referred to as a Resource Element (RE), and one modulation symbol can be mapped to it.

[0043] In a wireless communication system, a terminal receives information from a base station via the downlink (DL) and transmits information to the base station via the uplink (UL). The information transmitted and received by the base station and the terminal includes data and various control information, and various physical channels and signals exist depending on the type and purpose of the information being transmitted and received. A physical channel corresponds to a set of resource elements (REs) that carry information originating from the upper layer. A physical signal corresponds to a set of resource elements (REs) used by the physical layer (PHY), but it does not carry information originating from the upper layer. The upper layer includes the MAC (Medium Access Control) layer, RLC (Radio Link Control) layer, PDCP (Packet Data Convergence Protocol) layer, RRC (Radio Resource Control) layer, etc.

[0044] DL physical channels include PBCH (Physical Broadcast Channel), PDSCH (Physical Downlink Shared Channel), and PDCCH (Physical Downlink Control Channel). DL physical signals include DL RS (Reference Signal), PSS (Primary Synchronization Signal), and SSS (Secondary Synchronization Signal). DL RS includes DM-RS (Demodulation RS), PT-RS (Phase-tracking RS), and CSI-RS (Channel-state Information RS). UL physical channels include PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), and PUCCH (Physical Uplink Control Channel). UL physical signals include UL RS. UL RS includes DM-RS, PT-RS, and SRS (Sounding RS).

[0045] The base station can be, for example, gNodeB.

[0046] 6G network architecture

[0047] FIG. 3 illustrates a communication procedure between a terminal and a base station applicable to the present disclosure. FIG. 3 illustrates the operation of a terminal (100) and a base station (200) transmitting and / or receiving data, and the operation performed prior to this.

[0048] Referring to FIG. 3, in step 101, the terminal (100) and the base station (200) perform synchronization. For example, the terminal (100) performs an initial cell search operation. Specifically, the terminal (100) can detect at least one synchronization signal transmitted from the base station (200) according to a predefined rule. Here, the synchronization signal may include a plurality of synchronization signals (e.g., primary synchronization signal, secondary synchronization signal) classified according to structure or use. Through this, the terminal (100) can identify the boundaries of the frame, subframe, slot, and / or symbol of the base station (200) and obtain information about the base station (200) (e.g., cell identifier).

[0049] In step 103, the terminal (100) obtains system information transmitted from the base station (200). The system information is information related to the attributes, characteristics, and / or capabilities of the base station (200) required to connect to the base station (200) and use the service, and can be classified according to content (e.g., whether it is essential for connection), transmission structure (e.g., channel used, whether it is provided on-demand), etc., and can be classified, for example, into a master information block (MIB) and a system information block (SIB). If necessary, the terminal (100) may transmit a signal requesting the system information prior to receiving the system information. However, the request and provision of the system information may be performed after the random access procedure described later.

[0050] In step 105, the terminal (100) and the base station (200) perform a random access procedure. The terminal (100) may transmit and / or receive at least one message for the random access procedure (e.g., random access preamble, RAR (random access response) message, etc.) based on information related to the random access channel of the base station (200) obtained through system information (e.g., channel location, channel structure, structure of supported preamble, etc.). For example, the terminal (100) may transmit a preamble (e.g., MSG1) through the random access channel, receive a RAR message (e.g., MSG2), transmit a message (e.g., MSG3) containing information related to the terminal (100) (e.g., identification information) to the base station (200) using scheduling information included in the RAR message, and receive a message (e.g., MSG4) for contention resolution and / or connection establishment. As another example, MSG1 and MSG3 can be transmitted and received as a single message, or MSG2 and MSG4 can be transmitted and received as a single message.

[0051] In step 107, the terminal (100) and the base station (200) perform signaling of control information. Here, the control information may be defined in various layers, such as a layer that controls the connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transmission channels (e.g., a media access control (MAC) layer), and a layer that handles physical channels (e.g., a physical (PHY) layer). For example, the terminal (100) and the base station (200) may perform at least one of signaling to establish a connection, signaling to determine settings related to communication, and signaling to indicate allocated resources.

[0052] In step 109, the terminal (100) and the base station (200) transmit and / or receive data. That is, the terminal (100) and the base station (200) can process, transmit and / or receive data based on the signaling of control information. For example, when transmitting data, the terminal (100) or the base station (200) may perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and resource mapping on the information bits. Conversely, when receiving data, the terminal (100) or the base station (200) may perform at least one of signal extraction from resources, antenna-specific waveform demodulation, signal placement considering layer mapping, constellation demapping, descrambling, and channel decoding.

[0053] 6G System Core Technology

[0054] As core implementation technologies for 6G systems, technologies such as artificial intelligence (AI), THz (Terahertz) communication, optical wireless technology, FSO backhaul network, massive MIMO technology, blockchain, 3D networking, quantum communication, unmanned aerial vehicles, cell-free communication, wireless information and energy transfer (WIET), integration of sensing and communication, integration of access backhaul networks, holographic beamforming, big data analysis, and large intelligent surface (LIS) can be adopted.

[0055] LP-WUS

[0056] The contents examined above can be applied in combination with the proposed methods described below, or can be supplemented to clarify the technical characteristics of the proposed methods.

[0057] In addition, the methods described below can be applied in the same way to the NR system (licensed band) or shared spectrum described above, and it goes without saying that the technical concept proposed in this specification can be modified or replaced to fit the terms, expressions, structures, etc. defined in each system so that it can be implemented in the system as well.

[0058] In the Rel-18 NR standard, discussions are underway to introduce LP-WUS (low power wake-up signal) and LP-WUR (low power wake-up receiver or low power wake-up radio), a separate receiver capable of receiving it, as a method for reducing power consumption that differs slightly from the terminal power consumption reduction techniques introduced or supported in Rel-16 / 17 and others. When the receiver within the terminal (the receiver in the downlink) in existing NR systems is referred to as MR (Main radio / receiver), LP-WUR refers to a separate receiver (i.e., companion radio / receiver) that can be introduced to reduce the power consumption of the MR. LP-WUR can be simply represented as LR.

[0059] The following describes the options for LP-WUS waveform generation methods. These can be understood as different methods for MC-OOK (Multi-carrier On-Off Keying) and MC-FSK (Multi-carrier Frequency Shift Keying) waveform generation.

[0060] Figures 4 and 5 show options for the LP-WUS waveform generation method.

[0061] Figures 4 and 5 relate to MC-ASK (amplitude shift keying) waveform generation. In Figures 4 and 5, K is the size of the iFFT (inverse fast Fourier transform) of CP-OFDMA (Cyclic Prefix-Orthogonal Frequency Division Multiplexing Access), and N is the number of subcarriers used in LP-WUS, including potential guard bands.

[0062] Figure 4 shows option OOK-1.

[0063] In option OOK-1, 1 OFDM symbol contains a single bit. For the subcarriers of the LP-WUS, OOK=1 means that all subcarriers are modulated. OOK=0 means that all subcarriers are zero power (from a baseband perspective).

[0064] Figure 5 shows option OOK-5.

[0065] Referring to Fig. 5, in option OOK-4, the M-bit OOK in the time domain is transformed. N subcarriers of OOK-1 are generated by the transformation (DFT / Least Square). N' samples are generated from the M bits. Signal modification may or may not be used. Truncation or other additional modifications may or may not be used. If not used, N and N' are the same. N' can be equal to K.

[0066] In FIGS. 4 and 5, the modulated subcarriers may be, for example, QAM (Quadrature Amplitude Modulation) symbols, sequences, or other signals.

[0067] The subcarriers of the potential guard band are zero power (from the baseband perspective). Optionally, of the two additional segments, one can always be modulated and the other can always be transmitted as zero power (from the baseband perspective).

[0068] In addition to OOK-1 and OOK-4, OOK-2 and OOK-3 are available as options.

[0069] Symbols modified in the OOK method may be referred to as OOK symbols. For convenience of writing below, "OOK-1 and / or OOK-4" may be simply denoted as "OOK-1 / 4".

[0070] For OOK-1, one OOK symbol can be matched to one OFDM symbol interval, and for OOK-4, M OOK symbols can be mapped to one OFDM symbol interval. Therefore, 1 bit can be transmitted per OFDM symbol for OOK-1, and M bits can be transmitted per OFDM symbol for OOK-4. If MC (Manchester encoding) is additionally used in LP-WUS, twice the number of OFDM symbols may be required to transmit the same bit. Meanwhile, a terminal (including LP-WUR) that receives LP-WUS can perform an action to wake up MR; to do this, an ID (identifier) ​​capable of distinguishing each terminal or terminal (sub)group may be included in the LP-WUS signal. The UE ID may use (for example) the 5G-S-TMSI value or a value reduced by modulo operation. Depending on the ID used, this value may be approximately 48 bits. Accordingly, a significant number of OFDM symbols may be used to transmit a UE ID via OOK-1 / 4. For example, assuming the use of MC to transmit a 48-bit UE ID, 96 OFDM symbols are required for OOK-1. If the part containing information such as the UE ID is referred to as the message part of the LP-WUS, and a preamble part is transmitted along with it to assist in the reception of the message part, the number of required OFDM symbols may increase. The preamble part can convey information necessary for the LR to detect and decode the message part. Figure 6 illustrates an example of LP-WUS transmission including a preamble part and a message part.

[0071] If an LP-WUS signal transmitted to a specific terminal (or group of terminals) occupies a specific (frequency / time) channel for an extended period, it can result in inefficient resource usage for both the network and the terminal. From the perspective of receiving such LP-WUS signals, they may be vulnerable to interference. Furthermore, if accurate time synchronization is not ensured, the LP-WUR may need to attempt monitoring for a duration longer than the actual length of the LP-WUS signal. When an LP-WUS signal consists of a preamble part and a message part, effective signal configuration and setting methods are required.

[0072] Meanwhile, the LP-WUS signal may be used in conjunction with the OOK waveform with an overlaid sequence. Depending on how the overlaid sequence is overlaid on each OOK signal or OFDM signal, it may affect the LP-WUS transmission time and / or the frequency resources occupied by the LP-WUS. Additionally, if information is transmitted through the overlaid sequence, this may serve as a method to expand the utilization of the LP-WUS signal. However, not all LP-WUSs can detect / decode the overlaid sequence. If the overlaid sequence modulates each subcarrier in the frequency domain, only LP-WUSs possessing Fast Fourier Transform (FFT) and / or frequency domain sequence correlation capabilities can receive the overlaid sequence. Even if the sequence is overlaid on each OOK symbol or OFDM symbol in the time domain, only LP-WUSes possessing time domain sequence correlation capabilities can receive the sequence. Since the LP-WUR of the lowest complexity may only distinguish between ON / OFF of OOK symbols, the overlaid sequence needs to be designed to take these various types of LP-WURs into account.

[0073] Meanwhile, a separate LP-SS (low power synchronization signal) may be defined and transmitted for time / frequency synchronization required for receiving the LP-WUR transmitted from the LP-WUR. The LP-SS may be a signal / waveform generated according to an OOK or FSK waveform generation method (similar to the LP-WUS), and an overlaid sequence may be applied. The LP-SS may be a signal transmitted periodically or aperiodisically. Based on the LP-SS, the LP-WUR may measure the power of the received signal, etc., to offload or relax the RRM measurement of the MR.

[0074] As described above, the LP-WUS signal (transmitted by the base station) may consist of a preamble part and a message part. The preamble part may contain information necessary to receive the message part transmitted subsequently (e.g., data rate, modulation, encoding method of the message part, etc.). Alternatively, the preamble part may contain a known sequence / signal without conveying specific information. Or, a separate known sequence / signal may be transmitted together before or after the preamble part. The message part may carry identity information (for a specific terminal or terminal (sub)group), or simply transmit a wake-up indication for multiple terminals. Alternatively, cell-related information, emergency-related information such as ETWS (Earthquake and Tsunami Warning System) / CMAS (Commercial Mobile Alert System), system-related information (regarding the terminal) such as tracking area, RAN (radio access network) area, and SI (system information) change instructions, or paging-related information may be transmitted. Additionally, a Cyclic Redundancy Check (CRC) may be transmitted along with the preamble part and / or message part. In this case, the CRC may be generated based on the preamble part and / or message part. Depending on the configuration, the CRC may not be added. The proposed methods are described assuming a preamble part, message part, and / or CRC having these characteristics, but are not necessarily limited to LP-WUS transmissions composed of such a structure.

[0075] In the proposal below, the term "occasion" may refer to a transmission occasion (TO) where the base station transmits a signal, or a monitoring occasion (MO) where the receiver (such as an LP-WUR) monitors the signal, depending on the context. Since TO signifies an opportunity for a signal to be transmitted, the signal may not be transmitted at that location (depending on the configuration or the needs of the base station). Since MO signifies an opportunity to monitor the signal, the receiver may not monitor the signal at that location (depending on the configuration or the needs / situations of the base station / terminal). Additionally, for the sake of convenience, even if expressed simply as MO or TO, MO, TO, or MO and TO may be indicated depending on the proposed method and context.

[0076] In the proposal below, the LP-WUS opportunity may mean an opportunity for the preamble part and / or message part of the LP-WUS to be transmitted. In the proposal below, setting the opportunity of the LP-SS / LP-WUS can be interpreted as setting one or more of the period, starting time, ending time, duration, offset within the period, and frequency at which the corresponding signal is transmitted of the LP-SS / LP-WUS.

[0077] In the following proposal, it is assumed that LP-SS is transmitted periodically (unless otherwise noted). However, the proposed method and configuration method can be applied equally to LP-SS that is transmitted non-periodically.

[0078] In the proposal below, the preamble part of the LP-WUS is described under the assumption that it is intended to convey configuration information for the delivery of a subsequent message part, or that it includes such information delivery part and a known sequence / signal. However, if the information for the delivery of the message part is conveyed through the LP-SS, or if the preamble part is used as a known sequence / signal (without separate information delivery), the preamble or preamble part in the proposed method described below may be replaced by the LP-SS.

[0079] In this specification, the symbols '●', '■', and '◆' listed at the beginning of each paragraph may indicate vertical or horizontal relationships between the descriptions within each paragraph. Specifically, they may denote higher-level categories in the order of '●', '■', and '◆'. For example, '■' listed after '●' may be an elaboration on '●'. '◆' listed after '■' may be an elaboration on '■'.

[0080] In various examples of the present disclosure, " / " and "," should be interpreted as indicating "and / or." For example, "A / B" may mean "A and / or B." Furthermore, "A, B" may mean "A and / or B." Furthermore, "A / B / C" may mean "at least one of A, B and / or C." Furthermore, "A, B, C" may mean "at least one of A, B and / or C."

[0081] In conventional NR, the PDCCH monitoring operation of a terminal can be determined through parameters such as RRC configured semi-statically. For example, the terminal receives one or more SS (Search Space) settings per cell and / or per BWP, through which it determines the PDCCH MO (monitoring occasion) and performs PDCCH monitoring operations at the corresponding PDCCH MO. The SS settings may include the duration, offset, and the period of the PDCCH MO. Additionally, the SS settings may include information such as the DCI format to be transmitted via the PDCCH to be monitored by the terminal at the corresponding SS. If a change to the pre-configured SS settings is required, the terminal must receive the changed settings semi-statically through RRC reconfiguration; however, such reconfiguration operations may require significant latency and the use of separate time / frequency resources. Depending on the situation, this can be a factor that limits the flexibility of the network. Meanwhile, in conventional NR systems, SSSG switching and PDCCH monitoring adaptation / skipping operations were introduced for the purpose of PDCCH monitoring adaptation. However, these operations are also limited switching operations between a series of SS set related candidates semi-statically set through RRC, etc., and moreover, they have the limitation of being applicable only to specific SS sets (or SS set groups).

[0082] In order for a terminal to detect DCI, it must accurately know the location and size of the frequency resource where the corresponding PDCCH is transmitted. However, to avoid transmitting separate signaling for this purpose, the terminal in an NR system does not receive this information directly from the base station. Instead, the terminal detects the DCI by finding the actual transmitted PDCCH and performing blind detection / decoding (BD) on all PDCCH candidates that can be transmitted from the PDCCH MO configured via RRC, etc.

[0083] Such BD operations can significantly consume power from the terminal. The DCI transmitted to the terminal may be one of several types of DCI formats depending on its purpose, and the amount of frequency resources (e.g., number of CCEs or AL) occupied by the PDCCH transmitting it may vary depending on the size of the DCI. In other words, to detect a single DCI, the terminal must attempt PDCCH detection and decoding for all transmittable DCI formats and all possible PDCCH candidates.

[0084] To this end, the terminal is configured with the number of PDCCH candidates for each aggregation level (AL) per SS set, and determines the location of the corresponding frequency resource (e.g., CCE index) according to specific rules. Through this process, the terminal can determine information regarding the PDCCH candidates to be monitored.

[0085] Meanwhile, LP-WUS refers to a signal that can be detected with low power (e.g., using only energy detection without FFT operations). The terminal requires a separate receiver (commonly called LP-WUR) to receive LP-WUS. While the terminal is monitoring / detecting the LP-WUS signal, the main receiving module for receiving NR signals / channels can remain in a sleep state, which can reduce the terminal's power consumption.

[0086] For example, the terminal monitors only the LP-WUS while in sleep mode, and wakes up from sleep mode to monitor the PDCCH only when a wake-up instruction is received through the LP-WUS. Compared to a method of performing blind detection on all PDCCH MOs, power consumption due to PDCCH monitoring can be significantly reduced.

[0087] If PDCCH monitoring settings can be changed and / or controlled via LP-WUS, the terminal's PDCCH monitoring operation can be improved more efficiently. Specifically, if information regarding PDCCH candidates can be transmitted via LP-WUS, the number of BDs that the terminal needs to perform can be effectively reduced.

[0088] For example, prior to receiving a PDCCH, information regarding the DCI format that the terminal needs to receive may be transmitted via LP-WUS, or information regarding the DCI format that the terminal does not need to receive may be transmitted. Through this, the terminal can reduce the number of PDCCH candidates that need to be considered during the BD process. As another example, prior to receiving a PDCCH, information regarding the AL of the PDCCH candidate that the terminal needs to monitor may be transmitted via LP-WUS, or information regarding the AL that the terminal does not need to monitor may be transmitted. In this case as well, the terminal can reduce the number of PDCCH candidates that need to be considered during the BD process.

[0089] Hereinafter, methods for dynamically controlling the PDCCH monitoring settings of a terminal using LP-WUS are proposed in this specification.

[0090] Settings related to PDCCH monitoring of a terminal can be configured semi-statically through RRC, etc. In this specification, a method is proposed to change some of these settings through LP-WUS.

[0091] In this specification, for convenience of explanation, the signal indicating or changing settings related to PDCCH monitoring is denoted as LP-WUS; however, the method proposed in this specification can actually be applied to all signals that can be received by a low-power receiver compared to a general receiver for receiving conventional data channels and control channels. The method proposed in this specification can also be applied to signals that are modulated and transmitted using OOK (on-off keying) or FSK (Frequency Shift Keying) and can be received in a non-coherent manner, and is not limited to specific signals defined in a specific standard.

[0092] For example, the signals and channels of an NR system are modulated and transmitted using the OFDM method. To receive this, the receiver of an NR terminal performs a Fast Fourier Transform (FFT) on the received signal, and then decodes and detects the data channel and control channel in the frequency domain. On the other hand, LP-WUS can be modulated and transmitted using the OOK method, and can be received without FFT operations using only energy detection or envelope detection.

[0093] The base station can instruct / change parameters regarding the PDCCH (or included DCI) monitored by the terminal via LP-WUS. Parameter instruction related to PDCCH monitoring via LP-WUS can be classified into two cases as follows.

[0094] Case #1: A case where specific parameter values ​​are indicated / changed via LP-WUS to reduce the number of SS sets and / or PDCCH candidates for blind detection (BD) performed by the terminal for the purpose of reducing the terminal's power consumption. The parameter indication corresponding to this case may be a method of indicating the parameters listed in [Method #1] below (e.g.).

[0095] Case #2: This may be a case where parameter instructions are given via LP-WUS that do not correspond to Case #1 above, and where the terminal changes the time / frequency resources of the SS set it monitors, or instructs / changes parameters related to the association relationship, linking relationship, monitoring method, etc. of the SS set via LP-WUS. The parameter instructions corresponding to this case may be (for example) the method of instructing the parameters listed in [Method #2] below.

[0096] ● Case #1: For the purpose of reducing the power consumption of the terminal, specific parameter values ​​may be indicated and / or changed via LP-WUS so that the number of SS sets and / or PDCCH candidates related to BD that the terminal must perform may be reduced. Case #1 may be implemented, for example, by a method of indicating the parameters listed in [Method #1] below.

[0097] ● Case #2: This is a case where parameters not corresponding to Case #1 are indicated or changed via the LP-WUS. Specifically, parameters related to the time / frequency resources of the SS set monitored by the terminal, the association relationships between SS sets, the linking relationships, the monitoring method, etc., may be indicated and / or changed via the LP-WUS. Case #2 may be implemented, for example, by the method of indicating parameters listed in [Method #2] below.

[0098] The method proposed below may be a setting method or an operation method regarding the operation of a terminal receiving a change or instruction of a parameter corresponding to Case #1 and / or Case #2 through LP-WUS.

[0099] In operating this method, the LP-WUS, subsequent PDCCH (or PDCCH candidate), SS set, and / or associated CORESET may be linked or associated with each other. Such association may be expressed by (i) using a specific bit that has the same value for the LP-WUS and PDCCH candidate, or (ii) being defined / established by setting the LP-WUS index and SS set index to be the same.

[0100] Additionally, in this specification, an SS set and / or PDCCH whose setting value can be indicated or changed via LP-WUS may refer to a so-called two-stage PDCCH (e.g., a control channel transmitted separately as a first PDCCH and a second PDCCH) for splitting and transmitting one DCI information (e.g., PDSCH / PUSCH scheduling information) through two or more PDCCH parts. The indication or change of the PDCCH monitoring setting via LP-WUS may be applied to the setting information of one or both of the respective PDCCH parts (e.g., the first PDCCH or the second PDCCH).

[0101] In the following proposal, unless otherwise noted, the expression "configure something in relation to LP-WUS" may include, depending on the context, (i) the meaning of configuring the terminal / cell to support the corresponding function, (ii) the meaning of the configured corresponding function being activated, or (iii) both of these meanings.

[0102] Additionally, unless otherwise noted, "active / inactive time" and "active / inactive duration" may be used interchangeably with the same meaning. Similarly, "active time" and "on-duration" may also be used interchangeably, which may refer to the active PDCCH monitoring period defined / determined by the terminal's DRX setting (or the cell's DTX / DRX setting).

[0103] In addition, unless otherwise noted, the LP-WUS signal is assumed to be a signal modulated by MC-OOK (an OOK signal generated using an OFDM structure or multiple subcarriers / frequency tones). However, the proposed method and configuration method can be applied in the same way even when an MC-FSK signal, an OFDM-based signal, or a single-tone signal is used as the LP-WUS.

[0104] Finally, unless otherwise noted, it is assumed that the LP-WUS signal is transmitted periodically. However, the proposed method and configuration method can be applied equally to LP-WUS signals transmitted non-periodically.

[0105] In the following proposal, (unless otherwise noted) while receiving the LP-WUS, the MR (main radio) for receiving the conventional NR signal / channel may be in a sleep state, and the terminal may be in a state where it monitors the LP-WUS using only a separate receiver (LP-WUR). However, the methods of this specification may also be applied even when the MR is not in a sleep state during the period in which the terminal monitors the LP-WUS.

[0106] In the proposal below, a terminal (connected mode) that receives LP-WUS (unless otherwise noted) can wake up the MR, monitor the PDCCH, and / or receive configured DL assignments. However, the proposed method is not necessarily limited to these operations.

[0107] [Method #1] Method for providing information related to PDCCH candidates to be monitored by the terminal via LP-WUS

[0108] The base station can instruct / change parameters regarding the PDCCH (or included DCI) monitored by the terminal via LP-WUS. A reduction in the number of BDs by the terminal can be expected through the proposed method. Meanwhile, if the terminal does not receive / cannot receive parameter instructions via LP-WUS, the terminal can monitor the PDCCH through PDCCH monitoring-related settings (or SS set-related settings) configured via RRC, etc. In this case, the terminal can monitor the PDCCH without obtaining the BD reduction effect through the proposed method below. The parameters instructed via LP-WUS may be one or more of the parameters regarding the PDCCH (or included DCI), including the parameters listed below.

[0109] ● SS (Set) Type

[0110] ■ Information regarding one or more SS (set) types to be monitored by the terminal may be transmitted. Alternatively, information regarding one or more SS (set) types that the terminal does not need to monitor may be transmitted. For example, instructions to monitor a specific SS set type (e.g., Type0-PDCCH CSS set) may be transmitted to the terminal. As another example, instructions to monitor (or not monitor) either a USS (UE-specific SS) or a CSS may be transmitted to the terminal.

[0111] ■ An SS (set) corresponding to the indicated SS (set) type may be a target SS (set) for changing the parameters proposed below.

[0112] ● SS (Set) Index

[0113] ■ Information regarding one or more SS (set) indices to be monitored by the terminal may be transmitted. Alternatively, information regarding one or more SS (set) indices that the terminal does not need to monitor may be transmitted. For example, information regarding one of N SS set IDs per BWP may be transmitted (e.g., N=8 or 16).

[0114] ■ The SS (set) corresponding to the indicated SS (set) index may be the target SS (set) for changing the parameters proposed below.

[0115] ● DCI size or PDCCH length (e.g., number of symbols or size of frequency resources)

[0116] ■ For example, the size of the DCI to be monitored by the terminal may be directly specified, or the number of OFDM symbols and / or REs and / or RBs of the PDCCH for the transmission of the DCI may be specified. Through this, the terminal can determine the number of CCEs or ALs for the transmission of the PDCCH.

[0117] Alternatively, when several different DCI sizes are predefined / set, such as fallback DCI, non-fallback DCI for DL, non-fallback DCI for UL, and other DCIs, one of the set DCI sizes may be indicated.

[0118] ■ Expected Effects: A reduction in the amount of BD on the terminal can be expected. The base station can configure and transmit DCI of various sizes.

[0119] ● Indicates one or more ALs that the terminal should attempt (or does not need to attempt) PDCCH monitoring.

[0120] ■ For example, (with AL {1, 2, 4, 8} and the number of PCs for each AL specified via RRC), a terminal instructed via LP-WUS to monitor the PDCCH of AL 4 can monitor only the PDCCH of AL 4 without monitoring the PDCCH of AL {1, 2, 8}. As another example, a terminal instructed via LP-WUS that there is no need to monitor the PDCCH of AL 8 can attempt to monitor only the PDCCH of other ALs (configured via RRC, etc.), excluding the PDCCH of AL 8.

[0121] ■ Expected effect: A reduction in the amount of BD on the terminal can be expected.

[0122] ● Indicate the number of PCs per AL

[0123] ■ The number of PCs (PDCCH candidates) per AL of the SS set (or ± delta relative to the value set by RRC, etc.) may be indicated. For example, the number of PCs for a specific AL may be directly indicated. For instance, if the number of PCs for a specific AL 'n' is indicated as '0', the terminal may not attempt to monitor the PDCCH of that AL during the BD process. If the number of PCs for a specific AL is set by RRC, etc., the number of PCs for that AL may be reset to the value indicated via LP-WUS.

[0124] Alternatively, multiple candidate PC combinations may be pre-configured for each AL, and one of the pre-configured PC combinations may be indicated via LP-WUS. For example, for all N PCs configured in AL n (via RRC, etc.), multiple combinations such as 1) odd PC indexes, 2) even PC indexes, 3) first N / 2 indexes, 4) second N / 2 indexes, 5) all PCs, 6) no PC may be pre-configured, and one of the configured combinations may be indicated via LP-WUS.

[0125] ■ Expected effects: The dropping rate of configured SSs can be reduced. If the PC of a specific SS is set to 0, monitoring for that SS set can be skipped.

[0126] ● Specify DCI format, or specify RNTI (or scrambling LP-WUS to the corresponding RNTI)

[0127] ■ The format of the DCI transmitted via PDCCH may be specified. If the DCI size varies by DCI format, the terminal can determine the DCI size and / or the size of the PDCCH (e.g., number of OFDM symbols or number of CCEs) based on the DCI format specified via LP-WUS, thereby reducing the BD burden.

[0128] Alternatively, an RNTI applicable to DCI or PDCCH may be indicated.

[0129] ● Indicates the SS set group ID that the terminal will attempt to monitor (or skip) PDCCH monitoring.

[0130] ■ To monitor a specified SS set group, the terminal may perform an SS set group switching operation. Alternatively, it may operate to omit monitoring of the specified SS set group.

[0131] ● Instruct to skip PDCCH monitoring

[0132] ■ The terminal may be instructed not to monitor the PDCCH for a specific period of time after receiving the LP-WUS.

[0133] ■ The above specific time may mean the fastest PDCCH MO or the fastest slot after receiving LP-WUS, and may be set via RRC, etc.

[0134] ■ The above omission of PDCCH monitoring can be configured to apply only to specific SS set types. For example, it may be configured so that USS is not monitored, or Type0 PDCCH is not monitored.

[0135] In relation to Method #1, one of multiple codepoints (pre-configured) may be indicated to the terminal through a single LP-WUS. For each codepoint, a combination of the following information (related to multiple SS set settings) may be configured.

[0136] ● Whether PDCCH monitoring is enabled for each SS set setting

[0137] ● Types of DCI formats included in each SS set setting for which PDCCH monitoring is enabled

[0138] ● AL combinations among the ALs included in each SS set configuration for which PDCCH monitoring is enabled

[0139] ● The number of PCs (per AL) included in each SS set configuration, or combinations of PCs for which PDCCH monitoring is enabled

[0140] For example, each codepoint or bitmap indicated via LP-WUS may indicate the "number of ALs and / or PCs per AL for each SS set setting" according to a pre-configured content. Specifically, when one of K codepoints is transmitted via LP-WUS, some settings (or parameters) of the SS set settings for one (or more than) of N SS sets may be changed or indicated. For example, when codepoint #k is transmitted, the number of PCs for AL=x and AL=y in the SS set setting of SS set #n may be set / changed to a and b, respectively, and at the same time, the number of PCs for AL=x, AL=y, and AL=z in the SS set setting of SS set #(n+1) may be set / changed to c, d, and e, respectively. Additionally, codepoint #(k+1) may change / indicate the number of PCs for some ALs of another specific SS set. In this way, each of the K code points can be configured to change / instruct some settings or parameters for different SS sets (or multiple SS sets).

[0141] According to the method proposed in this specification, the meaning of each code point (or bitmap) transmitted via LP-WUS may be predefined or set through higher-level parameters such as RRC / SIB. For example, a specific type of RRC table may be set in the terminal, and when the terminal receives a specific code point via LP-WUS, it can refer to the table to identify the parameters that need to be changed. Tables 4 through 6 are examples of RRC tables, but the method proposed in this specification is not limited thereto. As long as the principle is maintained, various forms of pre-setting methods (e.g., different types of RRC tables) may be applied. Additionally, an RRC table may be set individually for each parameter, or an RRC table for multiple parameters may be set. That is, an RRC table for a single parameter and an RRC table for multiple parameters may be set in different forms.

[0142] Code Point 0 Number of PCs for AL=2 = a_1 Number of PCs for AL=4 = a_2 Number of PCs for AL=8 = a_3 Number of PCs for AL=2 = b_1 Number of PCs for AL=4 = b_2 Number of PCs for AL=8 = b_3 .........Number of PCs for KAL=2 = z_1 Number of PCs for AL=4 = z_2 Number of PCs for AL=8 = z_3

[0143] Code Point 0SS set #0 Number of PCs for AL=2=a_1 Number of PCs for AL=4=a_2 Number of PCs for AL=8=a_31SS set #1 Number of PCs for AL=2=b_1 Number of PCs for AL=4=b_2.........KSS set #(N-1) Number of PCs for AL=4=z_1 Number of PCs for AL=8=b_2

[0144] Code Point 0 For all SS set The number of PCs for AL=2 is 8 The number of PCs for AL=4 is 4 The number of PCs for AL=8 is 21 For all SS set The number of PCs for all ALs is 22 For all SS set The number of PCs for AL=4 is 8 The number of PCs for other ALs is 03 For all SS set The number of PCs for all ALs is 2 DCI size is 100 bit (without CRC) 4 SS set #1 SS set group ID = 0 5 SS set #2 SS set group ID = 1 5 SS set #3 SS set group ID = 1 .........

[0145] Additionally, if Carrier Aggregation (CA) is configured on the terminal, scheduled cell index information that is the target of PDCCH monitoring (BD) may be indicated via LP-WUS. For example, if multiple candidate cell combinations are configured in advance and one of the predefined combinations is indicated via LP-WUS, the terminal can perform BD only on the SS set configured / corresponding to that cell combination or on the PDCCH candidates of that SS set. As another example, in combination with the other parameter configuration method described above, if multiple cell combinations and AL / PC sets for each cell within the combination are configured in advance and one of the predefined cell combinations and AL / PC sets for each cell within the combination is indicated via LP-WUS, the terminal can perform BD only on the indicated cell combination and the AL / PC set for each cell within that combination.

[0146] If a preamble (or preamble part) is transmitted along with the LP-WUS, the type and / or index of the SS set may be transmitted through the preamble, and the proposed parameter change value may be transmitted through the message part following the preamble.

[0147] The parameter transmission proposed above may be in the form of a codepoint. For example, when information regarding the DCI size is transmitted via LP-WUS, several configurable DCI sizes are mapped to each codepoint, and one of the codepoints may be indicated via LP-WUS. Alternatively, the parameter transmission may be in the form of a bitmap. For example, when the number of PDCCH candidates per AL is indicated, the 5 bits of the bitmap are configured to correspond to AL=1, 2, 4, 8, and 16, respectively, and the terminal may assume a value set as RRC if each bit is '0', and assume a separately defined number of candidates (e.g., 0) if each bit is '1'.

[0148] In addition, if two or more of the proposed parameters are indicated or modified via LP-WUS, the indication or modification of the parameters may be performed through multiple code points. For example, if information regarding DCI size and the number of candidates per AL is transmitted simultaneously via LP-WUS, two code points may each transmit the corresponding information. The meaning of each code point may be defined in advance. Among the configuration values ​​for a specific SS set ID, the items and values ​​to be updated may be transmitted via multiple code points through LP-WUS.

[0149] Multiple code points can be configured with a fixed length or a variable length. As an example of a fixed length, if there are N parameters that can be instructed via the LP-WUS, the LP-WUS is composed of N code points; valid values ​​are transmitted through code points corresponding to parameters that require modification, while specific values ​​(e.g., 0) can be transmitted through code points corresponding to parameters that do not require modification. The order of the N parameters can be predefined or set. As an example of a variable length, there is a method in which only K parameters (K < N) that require modification / instruction are transmitted via the LP-WUS. In this case, K code points can be transmitted consecutively to convey K pairs of "parameter separator" and "parameter instruction / modification content," and the LP-WUS can be configured with a variable length in this manner.

[0150] [Method #2] Method for providing information regarding PDCCH candidates to be monitored by the terminal via LP-WUS

[0151] The base station can instruct or change parameters regarding the PDCCH (or DCI included therein) that the terminal monitors via the LP-WUS. Through the proposed method, the terminal's PDCCH monitoring settings can be temporarily changed.

[0152] If the terminal does not receive or is unable to receive parameter instructions through LP-WUS, the terminal can monitor the PDCCH according to the PDCCH monitoring related settings (or SS set related settings) set through RRC, etc.

[0153] The parameters indicated through LP-WUS may be one or more parameters regarding PDCCH (or DCI included therein), including the items listed below. For convenience of explanation, the parameters have been organized based on the RRC IE of the PDCCH monitoring-related settings (or SS set settings) defined in the NR standard, but the proposed method is not limited thereto and can be applied to setting parameters having the same or similar functions.

[0154] RRC IE 'SearchSpace' related parameters:

[0155] (1) MO setting value

[0156] - It may include periodicity, offset, duration, monitoring pattern, etc.

[0157] - Each of the period / offset / interval values ​​may be specified in the form of an index, or one of the predefined values ​​may be specified to reduce signal overhead.

[0158] - The start time of application may vary depending on the specified parameter. For example, if the cycle is changed via LP-WUS, the terminal can monitor the PDCCH by applying the changed setting value starting from the next frame (or subframe) of the frame (or subframe) that received the LP-WUS.

[0159] (2) SS type

[0160] - An index mapped to the DCI format can be specified.

[0161] (3) SS set group ID

[0162] - The group ID set for a specific SS set can be directed / changed.

[0163] (4) PDCCH transmission frequency resource location

[0164] - Corresponds to freqMonitorLocation or a similar parameter among the NR SS set setting values.

[0165] - The location of frequency resources can be indicated via codepoints or bitmaps. For example, the entire frequency resource (or the frequency resource of the CORESET associated with the SS set) is divided into N segments, and each segment can be indicated using a codepoint or a bitmap.

[0166] (5) SS linking ID

[0167] - If an SS set index is indicated along with this parameter via LP-WUS, the two SS sets can have a connection relationship.

[0168] Even if a connection relationship between an SS set corresponding to an SS connection ID and another SS set has already been established via RRC, etc., the setting changed via LP-WUS takes precedence during the validity period.

[0169] (6) CORESET ID

[0170] - If a CORESET ID is specified along with an SS set index via LP-WUS, the SS set can be changed to be associated with the CORESET of the specified index.

[0171] RRC IE 'CrossCarrierSchedulingConfig' related parameters:

[0172] (1) nCI or nCI-Value

[0173] - The value to be used as nCI (one of 0 to 7) can be indicated / changed via LP-WUS.

[0174] (2) carrierIndicatorSizeDCI-1-2 or carrierIndicatorSizeDCI-0-2

[0175] - The size (0~3) of the carrier indicator field can be directly indicated / changed.

[0176] (3) enableDefaultBeamForCCS

[0177] - For PDSCHs with CCS (cross-carrier scheduling), whether to apply the default beam (enable / disable) can be indicated / changed.

[0178] (4) ccs-BlindDetectionSplit

[0179] - The BD / CCE splitting ratio between SpCell and SCell can be indicated / changed.

[0180] RRC IE 'monitoringCapabilityConfig' related parameters:

[0181] - One of r15-monitoringCapabilityConfig, r16-monitoringCapabilityConfig, or r17-monitoringCapability can be specified / changed.

[0182] Other parameters:

[0183] ● The CCE index to which PDCCH is transmitted can be indicated / changed.

[0184] ● For example, some values ​​of the hashing function (Equation 1) that determines the CCE index of a PDCCH defined in the TS 38.213 standard may be changed or added.

[0185]

[0186] ■ Specifically, the value indicated as Y_p in the above mathematical formula 1 may be indicated / changed.

[0187] Alternatively, an offset may be applied to Y_p or the final result value during the CCE index calculation process.

[0188] ◆ For example, if Y_p is determined as X based on the CORESET index and slot index, and offset Z is indicated through LP-WUS, the terminal can calculate the CCE index by replacing Y_p = X with Y_p = X+Z.

[0189] ◆ As another example, if the result of mathematical formula 1 is determined to be X, and offset Z is indicated through LP-WUS, the terminal can determine the CCE (start) index for PDCCH monitoring as X+Z.

[0190] ■ of the above mathematical formula 1 Add an offset to the calculated result of, The first index of the CCE to which PDCCH is transmitted can be indicated / changed by adding an offset to the result value.

[0191] In relation to Method #2, a specific one of a plurality of pre-configured code points may be indicated to the terminal through a single LP-WUS. For each code point, a combination of the following information (related to multiple SS set configurations) may be configured.

[0192] ● Whether PDCCH monitoring is enabled for each SS set setting

[0193] ● Types of DCI formats included in each SS set setting for which PDCCH monitoring is enabled

[0194] ● AL combinations among the ALs included in each SS set configuration for which PDCCH monitoring is enabled

[0195] ● The number of PCs (per AL) included in each SS set configuration, or combinations of PCs for which PDCCH monitoring is enabled

[0196] For example, each code point or bitmap indicated via the LP-WUS can indicate the period, offset, and interval of the PDCCH MO for each SS set setting according to a preset content. Specifically, when one of K code points is transmitted via the LP-WUS, some settings (or parameters) of the SS set settings can be changed or indicated to one (or multiple) of N SS sets. For example, code point #k can instruct SS set #n to change the period to X1 and the offset to Y1, and simultaneously instruct SS set #(n+1) to change the period to X2 and the offset to Y1. Additionally, code point #(k+1) can be configured to change the period, offset, and interval for another specific SS set. In this way, each of the K code points can be configured to change / instruct some settings / parameters of different SS sets (or multiple SS sets).

[0197] According to the method proposed in this specification, the meaning of a code point (or bitmap) transmitted via LP-WUS may be predefined or set through higher-level parameters such as RRC / SIB. For example, if a specific RRC table is set in a terminal and the terminal receives a specific code point via LP-WUS, it can identify the parameters that need to be changed according to the table. Tables 7 through 9 are examples of RRC tables, but the method proposed in this specification is not limited thereto. As long as the principle is maintained, various forms of pre-setting methods (e.g., different forms of RRC tables) may be applied. Additionally, an independent RRC table may be set for each parameter, or an RRC table for multiple parameters may be set. An RRC table for a single parameter and an RRC table for multiple parameters may be set in different forms.

[0198] Code Point 0For all SS setn_CI=1 (or apply by adding 1 to n_CI)1For all SS setn_CI=2 (or apply by adding 2 to n_CI).........KFor all SS setn_CI=8 (or apply by adding 8 to n_CI)

[0199] Code point0SS set #0Periodicity=8 slots1SS set #1Periodicity=16 slots, duration=4 slots2SS set #2Periodicity=20 slots.......

[0200] Code point 0For all SS setCORESET ID = 21SS set #0CORESET ID = 12SS set #1CORESET ID = 13SS set #2CORESET ID = 04SS set #3CORESET ID = 3.......

[0201] Additionally, regarding Method #2, if Carrier Aggregation (CA) is configured on the terminal, scheduled cell index information that is the target of PDCCH monitoring (BD) may be indicated via LP-WUS. For example, if multiple candidate cell combinations are configured in advance and one of the predetermined combinations is indicated via LP-WUS, the terminal can perform BD only on the SS set configured / corresponding to that cell combination or on the PDCCH candidates of that SS set. As another example, in combination with the other parameter configuration method described above, if multiple cell combinations and AL / PC sets for each cell within the combination are configured in advance and one of the pre-configured cell combinations and AL / PC sets for each cell within the combination is indicated via LP-WUS, the terminal can perform BD only on the indicated cell combination and the AL / PC set for each cell within that combination.

[0202] If a preamble (or preamble part) is transmitted along with the LP-WUS, the type and / or index of the SS set may be transmitted through the preamble, and the proposed parameter change value may be transmitted through the message part following the preamble.

[0203] The parameter transmission proposed above may be in the form of a codepoint. For example, when information regarding the DCI size is transmitted via LP-WUS, several configurable DCI sizes are mapped to each codepoint, and one of the codepoints may be indicated via LP-WUS. Alternatively, the parameter transmission may be in the form of a bitmap. For example, when the number of PDCCH candidates per AL is indicated, the 5 bits of the bitmap are configured to correspond to AL=1, 2, 4, 8, and 16, respectively, and the terminal may assume a value set as RRC if each bit is '0', and assume a separately defined number of candidates (e.g., 0) if each bit is '1'.

[0204] In addition, if two or more of the proposed parameters are indicated or modified via LP-WUS, the indication or modification of the parameters may be performed through multiple code points. For example, if information regarding DCI size and the number of candidates per AL is transmitted simultaneously via LP-WUS, two code points may each transmit the corresponding information. The meaning of each code point may be defined in advance. Among the configuration values ​​for a specific SS set ID, the items and values ​​to be updated may be transmitted via multiple code points through LP-WUS.

[0205] Multiple code points can be configured with a fixed length or a variable length. As an example of a fixed length, if there are N parameters that can be instructed via the LP-WUS, the LP-WUS is composed of N code points; valid values ​​are transmitted through code points corresponding to parameters that require modification, while specific values ​​(e.g., 0) can be transmitted through code points corresponding to parameters that do not require modification. The order of the N parameters can be predefined or set. As an example of a variable length, there is a method in which only K parameters (K < N) that require modification / instruction are transmitted via the LP-WUS. In this case, K code points can be transmitted consecutively to convey K pairs of "parameter separator" and "parameter instruction / modification content," and the LP-WUS can be configured with a variable length in this manner.

[0206] [Method #3] Validity period of configuration values ​​directed / changed via LP-WUS

[0207] When a terminal receives instructions or changes to PDCCH monitoring settings via LP-WUS, the validity period of the setting value may be defined or set by one or more of the following options. Before receiving or detecting LP-WUS, the terminal may perform PDCCH monitoring according to the value set via RRC, etc.

[0208] ● Option 1: Valid only in the fastest PDCCH MO (or the slot containing the PDCCH MO) after LP-WUS reception / detection.

[0209] ■ When the terminal successfully receives / detects LP-WUS, it applies the setting change to the first PDCCH MO (or the slot containing the MO) that arrives after receiving LP-WUS (or after a predefined / set processing time).

[0210] ■ Subsequently, PDCCH monitoring is performed through one of the following two methods.

[0211] ◆ PDCCH monitoring can be performed according to pre-set values ​​such as RRC.

[0212] ◆ PDCCH monitoring may be suspended until a new LP-WUS instruction is received.

[0213] ● Option 2: Valid for a specific time interval after reception / detection by LP-WUS

[0214] ■ The terminal applies the changed settings only for a "specific time" after receiving the LP-WUS (or after a predefined / set processing time).

[0215] ■ "Specific time" can be defined / set in units of (i) N OFDM symbols, (ii) slots, or (iii) N msecs, and can also be calculated based on a timer / counter. For example, the terminal may determine that the setting value indicated by the LP-WUS is valid during the time interval from receiving the LP-WUS (or after a predefined / set processing time) to X OFDM symbols, slots, or PDCCH MOs. The time interval can be determined by a timer / counter that increases (or decreases) for each OFDM symbol, slot, or PDCCH MO.

[0216] ■ When a "specific time" has elapsed, the terminal follows one of the following two methods:

[0217] ◆ PDCCH monitoring can be performed according to pre-set values ​​such as RRC.

[0218] ◆ PDCCH monitoring may be suspended until a new LP-WUS instruction is received.

[0219] ● Option 3: Configuration values ​​indicated or changed via LP-WUS remain valid unless otherwise instructed.

[0220] ■ Unless there is an additional change instruction, the terminal continues to regard the setting value instructed by LP-WUS as a valid value.

[0221] ■ However, if there are new instructions, follow one of the following three methods:

[0222] ◆ PDCCH monitoring can be performed according to pre-set values ​​such as RRC.

[0223] ◆ PDCCH monitoring may be suspended until a new LP-WUS instruction is received.

[0224] ◆ PDCCH monitoring can be performed according to the values ​​indicated / changed through the new LP-WUS.

[0225] LP-WUS can be transmitted via N consecutive OFDM symbols (or N*M OOK symbols, e.g., N>=1, M>=1). "After receiving LP-WUS" means after the time when the last symbol of the LP-WUS, consisting of multiple OFDM symbols (or OOK symbols), is received. Indications or changes to configuration values ​​via LP-WUS may not be applied before this time.

[0226] If the N*M value is greater than a specific value, a single LP-WUS symbol may be TDMed and transmitted into two or more parts. In this case, the configuration value instruction / change via LP-WUS may be applied after the last symbol of the last part is received.

[0227] Meanwhile, a time offset between the LP-WUS and the PDCCH whose monitoring settings are changed by it can be defined / set. For example, if the terminal does not detect the PDCCH for a specific time window (Max time offset) after the setting instruction / change caused by the LP-WUS, it may report this fact to the base station. Additionally, the terminal may apply the changed setting value only to the PDCCH received after a minimum time offset has passed following the reception of the LP-WUS.

[0228] In this regard, the operation of the terminal can be defined as follows.

[0229] ● The terminal applies the contents instructed by the LP-WUS after a minimum time offset, but if no PDCCH is detected during a specific timer, the terminal may report a "no PDCCH" status to the base station.

[0230] ● If no PDCCH is detected during the above timer, the terminal can fallback to the previous operation. For example, the terminal can perform BD operations for all SS settings, AL, number of PCs per AL, DCI format, etc. set through RRC, etc.

[0231] ● The above reporting or fallback operation may be performed when there is no PDCCH detection during the timer and at the same time no additional LP-WUS detection.

[0232] A connected mode terminal can be configured to monitor an LP-WUS during the DRX inactive time in the LR state (low-power receiver usage state). In this case, when the terminal detects an LP-WUS that instructs the setting / changing of PDCCH monitoring parameters (e.g., BD parameters) according to the proposed method, the terminal can perform PDCCH monitoring based on the PDCCH monitoring parameters changed / instructed through the LP-WUS during the DRX active time (or DRX on-period timer operation period) associated with the LP-WUS.

[0233] Additionally, if a PDCCH monitoring omission operation is instructed within the DRX active time, the terminal can switch from MR to LR during the omission period to monitor the LP-WUS. In this state, if the terminal detects an LP-WUS that changes / instructs PDCCH monitoring parameters, the terminal can switch to the MR state after the PDCCH monitoring omission ends and perform PDCCH monitoring based on the changed / instructed PDCCH monitoring parameters.

[0234] [Method #4] How to Set Up LP-WUS MO

[0235] The terminal can receive the monitoring occasion (MO) of the LP-WUS for directing / changing the PDCCH monitoring settings through upper layer parameters such as RRC.

[0236] ● LP-WUS MO can be configured with parameters such as periodicity, offset (based on the start of a frame or subframe), and interval (e.g., the number of consecutive slots monitoring LP-WU'S within a period), which are set through higher-level parameters such as RRC or SIB.

[0237] ● The period of the LP-WUS MO can be set to K times the period of a specific PDCCH (or SS set) for which a configuration change is directed via the LP-WUS. K may be predefined or set. Additionally, the offset and interval may be determined by adding or subtracting a specific value (delta) from the offset and interval of the corresponding PDCCH (or SS set). delta may be predefined or set. For example, the period of the LP-WUS MO can be set to 2 times (or 0.5 times) the period of the SS set with the lowest index among the SS sets subject to configuration change, and the offset and interval may be set to the value of that SS set minus 1 symbol / slot. Alternatively, the period, offset, and interval of the LP-WUS MO may be set based on SS set index 0 instead of the lowest index among the SS sets subject to configuration change.

[0238] In addition, the LP-WUS MO can be set / determined based on the MO of the PDCCH (or SS set) whose setting is indicated / changed through the LP-WUS.

[0239] ■ The period of the LP-WUS MO can be set to be equal to a specific value among the periods of the corresponding PDCCH (or SS set), or determined as N times that specific value. The specific value may be the minimum or maximum value among the periods of the PDCCH (or SS set), and in some cases, the period of SS set index 0 (or the SS set with the lowest index) may be selected. N can be set separately through upper-level parameters such as RRC.

[0240] ■ The LP-WUS MO can be set to a position that is offset from the MO of a specific PDCCH (or SS set). For example, the LP-WUS MO can be set to be positioned K symbols (or slots) ahead of the MO of the SS set with the lowest index among the SS sets to be changed. As another example, the LP-WUS MO can be set to be positioned K symbols (or slots) ahead of the MO of SS set index 0.

[0241] A terminal with DRX operation configured can be configured to monitor the PDCCH only during the ON period of each DRX cycle. In this case, the LP-WUS MO can be determined based on the DRX configuration.

[0242] For example, the period of the LP-WUS MO can be set to be the same as the set DRX cycle, or set / determined as a multiple or divisor of the DRX cycle. Additionally, the LP-WUS MO can be set to be positioned X symbols (or slots) ahead of the start symbol or slot of the DRX ON period.

[0243] LP-WUS MO may refer to the symbols (e.g., OFDM symbols) that the LP-WUS actually receives. If a single indication message is transmitted over multiple symbols, the MO may include the first to the last symbols that the terminal monitors / receives. As another example, if the LP-WUS is transmitted over multiple symbols, the LP-WUS MO may refer only to the first (or last) symbol that the terminal monitors / receives.

[0244] Additionally, LP-WUS can be transmitted via N consecutive OFDM symbols (or N*M OOK symbols, e.g., N>=1, M>=1). If the N*M value is greater than a certain threshold, a single LP-WUS symbol may be transmitted in TDM mode in two or more parts, in which case the terminal can apply instructions / changes to the configuration values ​​via LP-WUS after receiving the last symbol.

[0245] [Method #5] Method for configuring frequency resources transmitted by LP-WUS

[0246] When PDCCH monitoring settings are directed or changed through LP-WUS, the frequency resources transmitted by the LP-WUS may be set as part of the frequency resources of the PDCCH targeted for directing or changing. The frequency resources of the LP-WUS may be set within the frequency resources of the CORESET configured in the terminal, and specific rules may be defined so that the LP-WUS becomes part of the CORESET.

[0247] For example, LP-WUS can be transmitted through X RBs starting from the lowest or highest RE of the CORESET frequency resource. X can be predefined or configured. The CORESET can be determined according to the PDCCH that directs / changes the configuration through the LP-WUS. For example, for a terminal in an RRC idle or inactive state, the LP-WUS resource can be configured / determined based on CORESET#0. For a terminal with multiple CORESETs configured, the LP-WUS resource can be configured / determined based on the CORESET having the lowest index.

[0248] Additionally, the frequency resources of the LP-WUS may be determined within a BWP where the PDCCH and / or SS set is configured. In this case as well, specific rules may be established so that the frequency resources of the LP-WUS become part of the corresponding BWP. For example, the LP-WUS may be transmitted over Y RB intervals starting from the lowest or highest RE of the BWP, where Y may be predefined or configured. For instance, for a terminal in an RRC idle or inactive state, frequency resources may be configured / determined based on the initial BWP. For a terminal in an RRC connected state, frequency resources of the LP-WUS may be configured / determined based on the active BWP.

[0249] The frequency resources of the LP-WUS may be configured independently as separate frequency resources, regardless of the PDCCH or BWP.

[0250] [Method #6] Method to distinguish terminals (groups) receiving LP-WUS

[0251] LP-WUS can be transmitted to any terminal (or all terminals within the cell) or to a specific terminal (or group of terminals).

[0252] When LP-WUS is transmitted to a specific terminal (group), information that can distinguish the terminal (group) through the LP-WUS may be transmitted along with it. This information may be transmitted in the form of code points (each code point referring to one or more terminals or terminal groups) or bitmaps (each bit referring to one or more terminals or terminal groups), and specific examples are as follows.

[0253] ● The ID of the terminal (e.g., TMSI, Temporary Mobile Subscriber Identity) or part thereof may be transmitted through LP-WUS.

[0254] ● The terminal's RNTI (Radio Network Temporary Identifier) ​​information can be transmitted through LP-WUS.

[0255] ● The ID of a terminal group (e.g., subgroup index) or part thereof may be transmitted through LP-WUS.

[0256] ● Multiple terminals (e.g., all terminals / terminal groups within a cell) can be indicated through a specific code point or bitmap value of the LP-WUS.

[0257] In addition, time / frequency resources for transmitting LP-WUS may be separately configured for each terminal or terminal group. In this case, the terminal (group) can monitor / receive LP-WUS only from specific time / frequency resources configured for it, thereby reducing or eliminating the burden of transmitting additional information via LP-WUS to distinguish terminals (groups).

[0258] In another embodiment, information distinguishing terminals (groups) receiving LP-WUS can be configured or transmitted separately as LP-WUS contents and time / frequency resources in which LP-WUS is transmitted. For example, if the ID of a terminal group is transmitted via LP-WUS, each terminal within that terminal group can monitor / receive LP-WUS at a different time / frequency resource. Conversely, LP-WUS can be configured to be monitored at a different time / frequency resource for each terminal group, and the ID of a terminal within the group (which may be an ID that is configured or calculated separately for each group) may be transmitted via LP-WUS.

[0259] [Method #7] Method to Ensure Instruction Reliability via LP-WUS

[0260] When setting values ​​related to PDCCH monitoring are indicated or changed through LP-WUS, some setting parameters may change the location of the time / frequency resource where the PDCCH (candidate) is transmitted, so the terminal may send feedback to the base station to inform it that it has successfully received LP-WUS.

[0261] For example, if the parameter "indicating the location of the frequency resource where the PDCCH is transmitted," mentioned in [Method #2], is indicated via the LP-WUS, the terminal may transmit an ACK signal to the base station after receiving the LP-WUS. If the ACK signal is not transmitted, the base station will not know when the terminal can monitor the PDCCH according to the changed settings. The base station may transmit the PDCCH according to the changed settings after receiving the ACK signal from the terminal. On the other hand, if the base station does not receive an ACK signal from the terminal within a specific time (e.g., measurable by a timer counting per symbol / slot) after transmitting the LP-WUS instructing the change of the PDCCH settings, the base station may not transmit the PDCCH according to the changed settings and may (1) transmit the PDCCH according to the previous settings, or (2) not transmit the PDCCH at all. This mode of operation may be applied specifically to the parameters listed in [Method #1], but is not necessarily limited thereto.

[0262] On the other hand, some other configuration parameters can be used to reduce the number of BD operations of the terminal without changing the location of the time / frequency resources where the PDCCH (candidate) is transmitted. In this case, the terminal can perform PDCCH monitoring (BD operation) according to the value after detecting the configuration value directed / changed by the LP-WUS, without needing to send separate feedback to the base station.

[0263] For example, if "AL that does not require PDCCH monitoring" is indicated as one of the parameters in [Method #1], the terminal may not monitor the corresponding AL in subsequent PDCCH MOs without separate feedback. This mode of operation may also be applied specifically to the parameters listed in [Method #1], but is not necessarily limited thereto.

[0264] In one embodiment, (for both of the above cases) an indicator indicating whether the PDCCH is transmitted according to a setting change directed by the LP-WUS may be included in the content of the PDCCH (or DCI). The terminal can check through the indicator whether it has correctly received the PDCCH transmitted according to the changed setting.

[0265] The indicator may be in the form of a 1-bit toggle between '0' and '1', and the value may be switched between 0 and 1 whenever there is a setting change through LP-WUS to notify the terminal whether the setting has been changed. In another embodiment, the value of the indicator may be '0' when the PDCCH follows the RRC setting, and the value of the indicator may be '1' when it follows the setting indicated through LP-WUS.

[0266] Examples of terminal operation are the same as Option 1 and Option 2.

[0267] ● Option 1: When a terminal that has been instructed to change the monitoring settings confirms that the indicator is '1', or when a terminal that has not been instructed to change the monitoring settings confirms that the indicator is '0', the terminal can detect the corresponding PDCCH and DCI normally and operate according to the control signal through them.

[0268] ● Option 2: If a terminal that has been instructed to change the monitoring settings confirms that the indicator is '0', or if a terminal that has not been instructed to change the monitoring settings confirms that the indicator is '1', the terminal may not detect the PDCCH and DCI and may report to the base station that an incorrect PDCCH has been transmitted.

[0269] However, as mentioned earlier, depending on the parameters indicated or changed via the LP-WUS, feedback to the base station may not be necessary. Therefore, Option 1 and Option 2 may operate selectively depending on the type of parameter indicated by the LP-WUS, and in some cases, the operation method of the terminal may be predefined or set for each parameter.

[0270] [Method #8] How to Indicate / Change Multiple Cell PDCCH Transmission Parameters via LP-WUS

[0271] When a terminal monitors / receives PDCCH for multiple cells, the terminal can be instructed to change the PDCCH monitoring settings for all multiple cells by receiving LP-WUS from a specific cell.

[0272] For example, a terminal configured with CA can collectively change the PDCCH monitoring settings for all cells on the CA (e.g., PCell and SCell) including that cell by receiving LP-WUS from a specific cell (e.g., PCell).

[0273] As another example, if a terminal has multiple scheduled cell combinations configured in advance via RRC, etc., it can collectively change the PDCCH monitoring settings for all of the cell combinations by receiving one of the cell combinations through LP-WUS.

[0274] [Method #9] How to Indicate / Change (Switch) PDCCH Transmission Mode via LP-WUS

[0275] When a terminal receives instructions or changes to the monitoring settings of the PDCCH through LP-WUS, the following two scenarios can be considered.

[0276] ● Case-1: Before monitoring the PDCCH, the terminal can always be instructed to set monitoring settings via the LP-WUS. The terminal's PDCCH monitoring is performed in two stages. In the first stage, the terminal receives the LP-WUS and obtains settings related to monitoring the PDCCH via the LP-WUS. In the subsequent second stage, the terminal performs monitoring of the PDCCH. Therefore, if the terminal does not receive the LP-WUS, it may not monitor or receive the subsequently transmitted PDCCH. This operation can be applied when the time / frequency resource location of the PDCCH that the terminal needs to monitor changes, and is particularly used when the parameters mentioned in [Method #2] are instructed or changed via the LP-WUS. For convenience, this is referred to as the two-stage mode.

[0277] ● Case-2: The terminal can monitor the PDCCH regardless of whether it receives the LP-WUS. If the terminal detects a change in the PDCCH monitoring settings through the LP-WUS, it can monitor the PDCCH according to the changed settings. This operation applies when the parameters indicated / changed through the LP-WUS do not change the form of the DCI or the time / frequency resources through which the PDCCH is transmitted, and is particularly used when the parameters mentioned in [Method #1] are indicated / changed. For convenience, this is referred to as one-stage mode.

[0278] The terminal may be instructed / configured to switch between one-stage mode and two-stage mode. Such switching may be configured or instructed through one of the following methods.

[0279] ● Alt-1: Switching may be indicated through separate signaling. For example, one-stage mode or two-stage mode may be directly indicated via LP-WUS. Alternatively, switching to two-stage mode may be indicated via a separate DCI. Additionally, the terminal may request the corresponding switching from the base station via signals / channels such as SR, UL WUS, etc.

[0280] ● Alt-2: Switching can be triggered by a pre-defined rule. For example, a switching pattern can be pre-set via RRC, and switching between one-stage and two-stage modes can occur based on a timer. As another example, switching can be configured to occur based on SFN or every X number of SSB reception cycles. The SFN value and X value at which switching occurs can be pre-defined or set.

[0281] ● Alt-3: If a terminal operating in two-stage mode fails to receive LP-WUS Y times consecutively or cumulatively, or fails to receive LP-WUS for a specific time set separately, the terminal may automatically switch to one-stage mode.

[0282] [Method #10] How to Adjust BD / CCE Budget or BD / CCE Limit via LP-WUS

[0283] In order to maintain the complexity and power consumption caused by PDCCH monitoring of the terminal at a certain level or to limit the amount of computation of the terminal to below a certain level, the number of BDs that the terminal can perform and the amount of frequency resources required for channel estimation for PDCCH decoding (e.g., can be expressed in CCE units) may be defined as a specific budget / limit value.

[0284] For example, the 3GPP TS 38.213 document specifies the maximum number of BDs per slot per cell (Table 10) and the maximum number of CCEs to be estimated per channel (Table 11). Additionally, depending on the configuration, the terminal may use a BD / CCE budget in units of mini-slots (or symbol groups) or a BD / CCE budget in units of slot groups (separate definitions exist in this case as well).

[0285] Under these circumstances, a method is proposed to dynamically adjust the BD / CCE budget of the terminal through LP-WUS. By changing / instructing the maximum number of BDs and CCEs allowed for a specific slot, mini-slot, or slot group through LP-WUS, the computational load and power consumption of the terminal can be efficiently managed.

[0286] Table 10 illustrates the maximum number of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell (M). In this specification, BD budget / limit refers to M.

[0287] μMaximum number of monitored PDCCH candidates per slot and per serving cell (M)044136222320

[0288] Table 11 illustrates the maximum number of non-overlapped CCEs per slot for a DL BWP with SCS configuration μ∈{0,1,2,3} for a single serving cell. In this specification, the CCE budget / limit refers to C.

[0289] μMaximum number of non-overlapped CCEs per slot and per serving cell (C)056156248332

[0290] Depending on the number of configured SS sets and the configured values, the terminal may operate to monitor PDCCH candidates in excess of the BD / CCE budget. This situation is referred to as overbooking.

[0291] In this case, the terminal may monitor only some SS sets according to specific rules and not monitor the remaining SS sets. For example, if overbooking occurs, the terminal may skip monitoring SS sets in order of decreasing SS set index. This behavior is referred to as dropping.

[0292] A terminal capable of receiving instructions / changes to monitoring settings via LP-WUS prior to receiving a PDCCH can control the degree of overbooking and dropping by adjusting the BD / CCE budget of the PDCCH (or SS set) subsequently received via LP-WUS. For example, the terminal's total BD / CCE budget is maintained via LP-WUS, while the number of BD / CCEs to be monitored for a specific interval (symbol / slot) can be temporarily increased or decreased. Specifically, in the case of a 15 kHz SCS, the terminal's actual BD budget per cell is maintained at 44, but the BD budget for a specific symbol / slot can be set to be greater or smaller than 44. However, even in this case, a control device may be introduced to ensure that the terminal's actual BD does not exceed 44. The validity period of the budget change / instruction may be determined according to the method presented in [Method #3].

[0293] In addition, when a terminal obtains DCI information (or PDSCH / PUSCH scheduling information) through two or more PDCCHs, the BD / CCE budget of some or all of these PDCCHs can be increased or decreased through LP-WUS. For example, when a terminal monitors a two-stage PDCCH that obtains DCI information through two PDCCHs, the BD / CCE budget ratio of the first PDCCH and the second PDCCH can be adjusted through LP-WUS.

[0294] In addition, for terminals with CA configured, the total BD limit for all monitored cells is maintained, while the BD limit for a specific cell can be set relatively large or small. Furthermore, for terminals supporting two or more active BWPs, the BD / CCE budget for each cell can be adjusted. In this case, the BD / CCE limits adjusted by numerology can also be distinguished by BWPs having the same SCS.

[0295] A-IoT (Ambient Internet of Things)

[0296] A-IoT can be a new type of device or segment that operates solely on energy harvested from the surrounding environment. For example, A-IoT can refer to a new class of Internet of Things devices that operate by being powered by various energy sources harvestable from the surrounding environment, such as radio waves, light, motion, and thermal energy.

[0297] For example, active signal generation and / or backscattering may be one of the communication technologies considered to achieve low-power operation of A-IoT devices. For example, backscattering is a widely used technique in radio frequency identification (RFID) that can enable a device to communicate with a network by reflecting incident waves after modulating them with information to be transmitted. For example, the device may be powered by an incident RF signal or stored energy.

[0298] For example, A-IoT devices can be classified into various device types, such as passive, semi-passive, and active, depending on the energy storage and transmission signal generation methods. For example, a passive device does not have an energy storage device (e.g., a capacitor) and can communicate based on backscatter communication technology. For example, a semi-passive device has an energy storage device and can communicate using backscatter communication technology with the assistance of the energy storage device. For example, an active device has an energy storage device and can communicate by actively generating signals using active RF components and stored energy. For example, in the present disclosure, the following three types of IoT devices may be considered. For example, device A may be a device without energy storage and without independent signal generation (e.g., a device supporting backscatter transmission). For example, device B may be a device with energy storage and without independent signal generation (e.g., a device supporting backscatter transmission). In this case, for example, the use of the stored energy may include amplification of the reflected signal. For example, device C may be a device with energy storage and independent signal generation (e.g., a device with an active RF component for transmission).

[0299] For example, the following basic topologies may be considered to support A-IoT devices in indoor and outdoor scenarios. For example, basic topologies may include a direct connection between a base station and an A-IoT device, a connection between a base station, an intermediate node, and an A-IoT device, support for connection by an auxiliary node, and / or a connection between a terminal and an A-IoT device. The basic topologies proposed in this disclosure are merely examples, and the proposals of this disclosure may be extended and applied to other topologies.

[0300] A-IoT devices can be classified into two types as follows. For example, a Type 1 device has a maximum power consumption of approximately 1 uW, is capable of energy storage, has no amplification function, and can perform transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station or terminal, or a separate node). For example, a Type 2 device has a maximum power consumption of approximately several hundred uW, is capable of energy storage, has an amplification function, and can perform transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station or terminal, or a separate node) or by using a signal generated internally.

[0301] For example, in addition to the classification methods described above, the type / class of an A-IoT device may be distinguished based on parameters associated with device characteristics (e.g., presence / capacity of energy storage, degree of energy / power consumption, presence / capability of amplification, presence / capability of a band-pass filter (BPF), supported DL / UL transmission method(s), etc.) or combinations of parameters. Here, for example, the BPF capability may be distinguished by the 3-dB bandwidth of the supported BPF, sharpness, etc., and the UL transmission methods may be distinguished by, for example, backscattered UL transmission, UL transmission by internal signal generation, etc.

[0302] In addition, the type / class of an A-IoT device may be subdivided based on parameters associated with the above device characteristics (e.g., presence / capacity of energy storage, degree of energy / power consumption, presence / capability of amplification, presence / capability of a band-pass filter (BPF), supported DL / UL transmission method(s), etc.) or combinations of such parameters. For example, the above-described Type 2 device may be classified into Type 2a when it performs transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station or terminal, or a separate node), and Type 2b when it performs transmission using a signal generated internally. In this case, Types 2a and 2b may be identical in that they have a maximum power consumption of approximately several hundred uW, are capable of energy storage, and have amplification capabilities.

[0303] LP-WUS can be transmitted and received between A-IoT devices. Specifically, the waveform transmitted from the reader to the A-IoT device may correspond to the waveform proposed through the embodiments of this specification. The A-IoT device may include only LR without MR. Therefore, when the A-IoT device receives LP-WUS, it may perform operations such as initial connection or data transmission and reception via LR instead of an operation to trigger (or activate) MR.

[0304] It is evident that the examples of the proposed methods described above can also be included as one of the implementation methods and thus can be regarded as a type of proposed method. Furthermore, while the proposed methods described above may be implemented independently, they may also be implemented in the form of a combination (or merger) of some proposed methods. Rules may be defined so that information regarding the application of the proposed methods (or information regarding the rules of the proposed methods) is communicated by a base station to a terminal or by a transmitting terminal to a receiving terminal via a predefined signal (e.g., a physical layer signal or a higher layer signal).

[0305] Implementation example

[0306] FIG. 7 is a flowchart according to one embodiment.

[0307] Referring to FIG. 7, an embodiment based on the methods of the present specification may be a method comprising: receiving configuration information including parameters related to PDCCH monitoring (S701); receiving an LP-WUS through a first receiver of a terminal (S703); and monitoring a PDCCH through a second receiver of the terminal based on the LP-WUS and the configuration information (S705).

[0308] The configuration information may be a parent parameter (or information element, IE) comprising a single parameter described in Method #1 and / or Method #2. For example, the configuration information may mean one or more of SearchSpace, CrossCarrierSchedulingConfig, and monitoringCapabilityConfig, which are RRC IEs described in Method #2. Alternatively, the configuration information may mean a parent RRC IE comprising one or more of SearchSpace, CrossCarrierSchedulingConfig, and monitoringCapabilityConfig.

[0309] The first receiver corresponds to a separate receiver for receiving LP-WUS (i.e., LP-WUR), and the second receiver corresponds to the main receiver (i.e., MR). The second receiver may be a receiver for receiving paging signals or control signals for paging signals. Alternatively, the second receiver may be a receiver capable of receiving PDCCH. Although the specific names may be changed from LP-WUR and MR to something else, the first receiver is designed to consume relatively less power than the second receiver. The main receiver may be a receiver of an existing NR system, and even if it is a receiver by a communication system other than an NR system, it may correspond to the main receiver if it is a receiver that is triggered based on the reception of a signal from another receiver that consumes relatively less power.

[0310] However, in the case of an A-IoT device, only the first receiver among the first receiver and the second receiver may be included.

[0311] In addition to the basic operation of FIG. 7, other operations disclosed in this specification may be combined.

[0312] For example, the LP-WUS may include information related to instructions or changes to the values ​​of parameters included in the configuration information. As an example of parameters included in the configuration information, the values ​​of one or more of the parameters disclosed in Method #1 and Method #2 may be indicated or changed by the LP-WUS.

[0313] As a specific example, the configuration information includes information about ALs associated with monitoring the PDCCH, and the LP-WUS may include information about which ALs among the ALs included in the configuration information the terminal will use for monitoring or will not use. The terminal can monitor the PDCCH based on the ALs directed and / or changed by the configuration LP-WUS.

[0314] Additionally, LP-WUS may include information regarding the number of PDCCH candidates per AL of the SS set. The specific form of the information regarding the number of PDCCH candidates may follow that described in Method #1.

[0315] The code points disclosed in Method 1 and Method 2 may be used in a form in which the LP-WUS transmits information related to instructions or changes to the values ​​of parameters related to PDCCH monitoring. For example, a table for indicating or changing the values ​​of parameters related to PDCCH monitoring may be stored in advance in the terminal (e.g., Tables 4 to 9), and a code point may be included in the LP-WUS to indicate an index of the said table.

[0316] The validity period of 'information related to instructions or changes to the values ​​of parameters included in the configuration information' received via the LP-WUS can be determined based on Method #3. For example, according to Option 1 of Method #3, the PDCCH may be monitored based on the information included in the LP-WUS only at the earliest monitoring opportunity after receiving the LP-WUS. After the earliest monitoring opportunity after receiving the LP-WUS, the terminal may perform PDCCH monitoring based on the configuration information or stop PDCCH monitoring. As another example, the validity period of the information received via the LP-WUS may be determined based on other options disclosed in Method #3.

[0317] The time and frequency resources of the LP-WUS MO can be determined according to the description in Method #4 and / or Method #5.

[0318] Information about a terminal or terminal group to be received by the LP-WUS may be included in the LP-WUS according to Method #6. The indication / change of parameters through the LP-WUS may be applied only to the terminal corresponding to the information about the terminal or terminal group included in the LP-WUS.

[0319] In relation to the instruction / modification of parameters via LP-WUS, the operation of Method #7 may be performed to ensure reliability between the base station and the terminal. For example, the PDCCH may include information regarding whether the value of a parameter of the configuration information has been indicated or modified by the LP-WUS.

[0320] The instruction / modification of parameters via LP-WUS can be performed for multiple cells according to Method #9. Referring to Method #9, one of a one-stage mode (first mode) capable of receiving / monitoring PDCCH regardless of reception of LP-WUS, and a two-stage mode (second mode) capable of receiving PDCCH only after reception of LP-WUS may be configured on the terminal, and switching between the two modes may be performed through one of Alt-1, Alt-2, or Alt-3 of Method #9. When switching is performed, the terminal may perform PDCCH monitoring based on the mode after switching.

[0321] Through the LP-WUS, the maximum number of PDCCH candidates M monitored per serving cell and slot and the maximum number of non-overlapping CCEs C per serving cell and slot can be changed / instructed. A specific example can be implemented according to Method #10. The terminal can perform PDCCH monitoring based on the changed M and / or C.

[0322] FIG. 8 illustrates an example of a communication system 1 to which the implementations of the present specification apply. Referring to FIG. 8, the communication system (1) to which the present specification applies includes a wireless device, a BS, and a network. Here, a wireless device refers to a device that performs communication using wireless access technology (e.g., 5G NR (New RAT), LTE (e.g., E-UTRA)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Thing) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with wireless communication capabilities, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, vehicles may include UAVs (Unmanned Aerial Vehicles) (e.g., drones). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices and may be implemented in the form of HMDs (Head-Mounted Devices), HUDs (Head-Up Displays) equipped in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Portable devices may include smartphones, smartpads, wearable devices (e.g., smartwatches, smart glasses), computers (e.g., laptops, etc.). Home appliances may include TVs, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, BS and networks may be implemented as wireless devices, and specific wireless devices may operate as BS / network nodes to other wireless devices.

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

[0324] Wireless communication / connection (150a, 150b) may be established between wireless devices (100a~100f) / BS (200) and BS (200) / wireless devices (100a~100f). Here, the wireless communication / connection may be established through uplink / downlink communication (150a) and sidelink communication (150b) (or D2D communication) using various wireless access technologies (e.g., 5G NR). Through the wireless communication / connection (150a, 150b), wireless devices and BS / wireless devices may transmit / receive wireless signals to / from each other. To this end, based on various proposals of the present specification, at least some of the following may be performed: a process for setting various configuration information for transmitting / receiving wireless signals, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and a resource allocation process.

[0325] FIG. 9 is a block diagram illustrating examples of communication devices capable of performing the method according to the present specification. Referring to FIG. 9, a first wireless device (100) and a second wireless device (200) can transmit and / or receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} may correspond to {wireless device (100x), BS (200)} and / or {wireless device (100x), wireless device (100x)} of FIG. 8.

[0326] The first wireless device (100) includes one or more processors (102) and one or more memories (104), and may additionally include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memory (104) and / or transceivers (106) and may be configured to implement the functions, procedures and / or methods described / suggested below. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (106). Additionally, the processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and then store information obtained from the signal processing of the second information / signal in the memory (104). Memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, memory (104) may store software code containing instructions for performing some or all of the processes controlled by the processor (102) or for performing the procedures and / or methods described / suggested below. Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals through one or more antennas (108). The transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be interchangeably used with an RF (Radio Frequency) unit. In this specification, a wireless device may mean a communication modem / circuit / chip.

[0327] The second wireless device (200) includes one or more processors (202) and one or more memories (204), and may additionally include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memory (204) and / or transceivers (206) and may be configured to implement the functions, procedures and / or methods described / suggested below. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal in the memory (204). Memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the procedures and / or methods described / suggested below. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeably used with an RF unit. In this specification, a wireless device may mean a communication modem / circuit / chip.

[0328] The wireless communication technology implemented in the wireless device (100, 200) of this specification may include LTE, NR, and 6G, as well as Narrowband Internet of Things for low-power communication. In this case, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may perform communication based on LTE-M technology. In this case, for example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) with consideration for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4 and may be referred to by various names.

[0329] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). One or more processors (102, 202) may generate one or more protocol data units (PDU) and / or one or more service data units (SDU) according to the functions, procedures, proposals and / or methods disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document. One or more processors (102, 202) may generate a signal (e.g., baseband signal) containing a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document.

[0330] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The functions, procedures, proposals, and / or methods disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the functions, procedures, proposals, and / or methods disclosed in this document may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The functions, procedures, proposals, and / or methods disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0331] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0332] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc., of this document to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the functions, procedures, proposals, methods and / or operation flowcharts, etc., disclosed in this document from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and / or receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be connected to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and / or receive user data, control information, wireless signals / channels, etc., as mentioned in the functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document through one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.

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

[0334] The additional configuration (140) can be configured in various ways depending on the type of wireless device. For example, the additional configuration (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 8, 100a), a vehicle (Fig. 8, 100b-1, 100b-2), an XR device (Fig. 8, 100c), a portable device (Fig. 8, 100d), a home appliance (Fig. 8, 100e), an IoT device (Fig. 8, 100f), a UE for digital broadcasting, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device (Fig. 8, 400), a BS (Fig. 8, 200), a network node, etc. Wireless devices can be used in a movable or fixed location depending on the use—e.g., service.

[0335] In FIG. 10, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least partially connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be connected via a wire, and the control unit (120) and the first unit (e.g., 130, 140) may be connected wirelessly via the communication unit (110). Additionally, each element, component, unit / part, and / or module within the wireless device (100, 200) may include one or more additional elements. For example, the control unit (120) may be composed of one or more sets of processors. For example, the control unit (120) may be composed of a set of communication control processors, application processors, ECUs (Electronic Control Units), graphics processing processors, memory control processors, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, transitory memory, non-transitory memory, and / or a combination thereof.

[0336] In this specification, at least one memory (e.g., 104 or 204) may store instructions or programs, and said instructions or programs may, when executed, cause at least one processor operablely connected to said at least one memory to perform operations according to some embodiments or implementations of this specification.

[0337] In this specification, a computer-readable (non-transient) storage medium may store at least one instruction or computer program, and when executed by at least one processor, said at least one instruction or computer program may cause said at least one processor to perform operations according to some embodiments or implementations of this specification.

[0338] In this specification, a processing device or apparatus may include at least one processor and at least one computer memory connectable to said at least one processor. said at least one computer memory may store instructions or programs, and said instructions or programs, when executed, may cause at least one processor operablely connected to said at least one memory to perform operations according to some embodiments or implementations of this specification.

[0339] In this specification, a computer program may include program code stored on at least one computer-readable (non-transient) storage medium and, when executed, perform operations according to some implementations of this specification or cause at least one processor to perform operations according to some implementations of this specification. The computer program may be provided in the form of a computer program product. The computer program product may include at least one computer-readable (non-transient) storage medium.

[0340] A communication device of this specification comprises at least one processor; and at least one computer memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations according to the examples(s) of this specification described below.

[0341] As described above, the embodiments of this specification can be applied to various wireless communication systems.

Claims

1. A step of receiving configuration information including parameters related to PDCCH (physical downlink control channel) monitoring; A step of receiving an LP-WUS (low power-wake up signal) through a first receiver of a terminal; The step of monitoring the PDCCH through the second receiver of the terminal based on the LP-WUS and the configuration information; The above LP-WUS includes information related to an instruction or change regarding the value of the above parameter, method.

2. In Paragraph 1, The above configuration information includes information regarding specific ALs (aggregation levels) among one or more search space settings for PDCCH monitoring, and The above LP-WUS includes information regarding the AL among the above ALs that will be used for the PDCCH monitoring or the AL that will not be used for the PDCCH monitoring. method.

3. In Paragraph 1, The above LP-WUS includes information regarding the number of PDCCH candidates associated with one or more of the above ALs, method.

4. In Paragraph 1, The above LP-WUS includes a code point for indicating an index of a table related to the values ​​of a plurality of parameters included in the above configuration information, method.

5. In Paragraph 1, Monitoring based on information related to the indication or change of the value of the parameter, only for the PDCCH candidate of the fastest PDCCH monitoring opportunity after reception of the above LP-WUS, method.

6. In Paragraph 5, After the aforementioned earliest PDCCH monitoring opportunity, PDCCH monitoring is suspended until the reception of a new LP-WUS, method.

7. In Paragraph 1, The above LP-WUS includes information regarding a terminal or terminal group to which information related to instructions or changes to the value of the parameter will be used. method.

8. In Paragraph 1, The above PDCCH includes information regarding whether the value of the parameter was indicated or changed by the above LP-WUS, method.

9. In Paragraph 1, The above LP-WUS includes information related to indicating or changing the value of a parameter related to PDCCH monitoring on a plurality of cells, method.

10. In Paragraph 1, The above PDCCH monitoring is performed based on a first mode or a second mode, and The first mode above is a mode in which PDCCH monitoring is performed regardless of whether the LP-WUS receives, and The above second mode is a mode in which PDCCH monitoring is performed only when the LP-WUS is received, and Switching between the first mode and the second mode is performed according to certain conditions, method.

11. In Paragraph 1, Based on the above LP-WUS, the values ​​of M and C related to the above PDCCH monitoring are changed, and The above M is (i) a maximum number of monitored PDCCH candidates per slot and per serving cell, and (ii) a maximum number of monitored PDCCH candidates per slot and per serving cell. The above C is i) a serving cell and (ii) a maximum number of non-overlapped CCEs (control channel elements) per slot and per serving cell, method.

12. First receiver and second receiver; At least one processor; and It includes at least one memory connected to the at least one processor to be operable, and storing instructions that cause the at least one processor to perform a specific operation when executed. The above specific operation is: A step of receiving configuration information including parameters related to PDCCH (physical downlink control channel) monitoring; A step of receiving an LP-WUS (low power-wake up signal) through a first receiver of a terminal; The step of monitoring the PDCCH through the second receiver of the terminal based on the LP-WUS and the configuration information; The above LP-WUS includes information related to an instruction or change regarding the value of the above parameter, Terminal.

13. A computer-readable non-volatile storage medium comprising at least one computer program that enables a terminal including at least one processor to perform an operation, wherein the operation is: A step of receiving configuration information including parameters related to PDCCH (physical downlink control channel) monitoring; A step of receiving an LP-WUS (low power-wake up signal) through a first receiver of a terminal; The step of monitoring the PDCCH through the second receiver of the terminal based on the LP-WUS and the configuration information; The above LP-WUS includes information related to an instruction or change regarding the value of the above parameter, Storage medium.

14. A step of transmitting configuration information including parameters related to PDCCH (physical downlink control channel) monitoring; A step of transmitting an LP-WUS (low power-wake up signal) for a first receiver of a terminal; The step of transmitting a PDCCH for a second receiver of the terminal based on the LP-WUS and the configuration information; The above LP-WUS includes information related to an instruction or change regarding the value of the above parameter, method.

15. At least one transceiver; At least one processor; and It includes at least one memory connected to the at least one processor to be operable, and storing instructions that cause the at least one processor to perform a specific operation when executed. The above specific operation is: A step of transmitting configuration information including parameters related to PDCCH (physical downlink control channel) monitoring; A step of transmitting an LP-WUS (low power-wake up signal) for a first receiver of a terminal; The step of transmitting a PDCCH for a second receiver of the terminal based on the LP-WUS and the configuration information; The above LP-WUS includes information related to an instruction or change regarding the value of the above parameter, Base station.

16. A computer-readable non-volatile storage medium comprising at least one computer program that causes a base station comprising at least one processor to perform an operation, wherein the operation is: A step of transmitting configuration information including parameters related to PDCCH (physical downlink control channel) monitoring; A step of transmitting an LP-WUS (low power-wake up signal) for a first receiver of a terminal; The step of transmitting a PDCCH for a second receiver of the terminal based on the LP-WUS and the configuration information; The above LP-WUS includes information related to an instruction or change regarding the value of the above parameter, Storage medium.

Images