Terminal and communication method

WO2026160310A1PCT designated stage Publication Date: 2026-07-30NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
NTT DOCOMO INC
Filing Date
2026-01-19
Publication Date
2026-07-30

Smart Images

  • Figure JP2026001514_30072026_PF_FP_ABST
    Figure JP2026001514_30072026_PF_FP_ABST
Patent Text Reader

Abstract

This terminal includes: a reception unit that monitors a low-power wake-up signal on the basis of a bandwidth part (BWP) setting related to the low-power wake-up signal; and a control unit that, if the low-power wake-up signal is received, monitors a paging opportunity associated with the low-power wake-up signal. The control unit sets the BWP to at least one of low-power wake up receiver (LR) and main radio (MR) on the basis of the BWP setting.
Need to check novelty before this filing date? Find Prior Art

Description

Terminals and communication methods

[0001] The present invention relates to a terminal and a communication method in a wireless communication system.

[0002] The 3rd Generation Partnership Project (3GPP) is exploring wireless communication methods known as 5G or NR (New Radio) (hereinafter referred to as "NR") in order to achieve even greater system capacity, even faster data transmission speeds, and even lower latency in the wireless section. In order to meet the requirements of achieving a throughput of 10 Gbps or more while keeping the latency in the wireless section below 1 ms for 5G, various wireless technologies and network architectures are being considered (for example, Non-Patent Documents 1 and 2).

[0003] 3GPP TS 38.300 V18.3.0 (2024-09)3GPP TS 38.401 V18.3.0 (2024-09)3GPP TS 38.304 V18.3.0 (2024-09)3GPP TS 38.331 V18.3.0 (2024-09)

[0004] In 3GPP Rel-19, a method called LP (Low Power)-WUS (Wake Up Signal) / WUR (Wake Up Receiver) is being considered with the aim of further reducing the power consumption of conventional WUS (Wake Up Signal).

[0005] The present invention has been made in view of the above points, and aims to receive low-power signals in a wireless communication system using an LP-WUR (Low power Wake up receiver).

[0006] According to the disclosed technology, a terminal is provided which includes a receiving unit that monitors a low-power wake-up signal based on a Bandwidth Part (BWP) setting related to the low-power wake-up signal, and a control unit that, when it receives the low-power wake-up signal, monitors the paging opportunity associated with the low-power wake-up signal, wherein the control unit sets the BWP to at least one of the LR (Low-Power Wake Up Receiver) and MR (Main Radio) based on the BWP setting.

[0007] According to the disclosed technology, in a wireless communication system, low-power signals can be received by an LP-WUR (Low-power Wake-up receiver).

[0008] This is a diagram illustrating a wireless communication system in an embodiment of the present invention. This is a diagram illustrating a wireless communication system in an embodiment of the present invention. This is a sequence diagram illustrating an example of receiving a low-power signal. This is a diagram illustrating an example of receiving a low-power signal (1). This is a diagram illustrating an example of receiving a low-power signal (2). This is a diagram illustrating an example of receiving a low-power signal (3). This is a diagram illustrating an example of BWP switching. This is a diagram illustrating an example of LP-WUS (1) in an embodiment of the present invention. This is a diagram illustrating an example of LP-WUS (2) in an embodiment of the present invention. This is a diagram illustrating an example of LP-WUS (3) in an embodiment of the present invention. This is a diagram illustrating an example of LP-WUS (4) in an embodiment of the present invention. This is a diagram illustrating an example of BWP setting (1) in an embodiment of the present invention. This is a diagram illustrating an example of BWP setting (2) in an embodiment of the present invention. This is a diagram illustrating an example of BWP setting (3) in an embodiment of the present invention. This is a diagram illustrating an example of BWP setting (4) in an embodiment of the present invention. This is a diagram illustrating an example of BWP setting (5) in an embodiment of the present invention. This is a diagram illustrating an example of BWP setting (6) in an embodiment of the present invention. This is a diagram illustrating an example of BWP setting (7) in an embodiment of the present invention. This is a diagram illustrating an example of BWP setting (8) in an embodiment of the present invention. This figure shows an example of BWP settings (9) in an embodiment of the present invention. This figure shows an example of BWP settings (10) in an embodiment of the present invention. This figure shows an example of BWP settings (11) in an embodiment of the present invention. This figure shows an example of BWP settings (12) in an embodiment of the present invention. This figure shows an example of BWP settings (13) in an embodiment of the present invention. This figure shows an example of BWP settings (14) in an embodiment of the present invention. This figure shows an example of the functional configuration of the base station 10 in an embodiment of the present invention. This figure shows an example of the functional configuration of the terminal 20 in an embodiment of the present invention. This figure shows an example of the hardware configuration of the base station 10 or terminal 20 in an embodiment of the present invention. This figure shows an example of the configuration of the vehicle 2001 in an embodiment of the present invention.

[0009] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.

[0010] In the operation of the wireless communication system according to the embodiments of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, for example, existing LTE, but are not limited to existing LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and LTE-Advanced and later technologies (e.g., NR), unless otherwise specified.

[0011] Furthermore, in the embodiments of the present invention described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), which are used in existing LTE technologies, will be used. This is for convenience of description, and similar signals, functions, etc., may be called by other names. In NR, the above terms will be referred to as SS, PSS, SSS, PBCH, PRACH, etc., without any particular distinction from LTE.

[0012] Furthermore, in the embodiments of the present invention, the duplex system may be a TDD (Time Division Duplex) system, an FDD (Frequency Division Duplex) system, or any other system (for example, a Flexible Duplex).

[0013] Furthermore, in the embodiments of the present invention, "configuring" wireless parameters may mean that predetermined values ​​are pre-configured, or that wireless parameters notified from the base station 10 or terminal 20 are configured.

[0014] Figure 1 shows an example of the configuration of a wireless communication system in an embodiment of the present invention. The wireless communication system in the embodiment of the present invention includes a base station 10 and a terminal 20, as shown in Figure 1. Figure 1 shows one base station 10 and one terminal 20, but this is an example, and there may be multiple base stations 10 and terminals 20.

[0015] Base station 10 is a communication device that provides one or more cells and communicates wirelessly with terminal 20. The physical resources of the wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. Base station 10 transmits synchronization signals and system information to terminal 20. Synchronization signals are, for example, PSS and SSS. System information is transmitted, for example, via PBCH and is also called broadcast information. Synchronization signals and system information may be called SSB (SS / PBCH block). As shown in Figure 1, base station 10 transmits control signals or data to terminal 20 via DL (Downlink) and receives control signals or data from terminal 20 via UL (Uplink). Both base station 10 and terminal 20 are capable of transmitting and receiving signals using beamforming. Furthermore, both base station 10 and terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via secondary cells (SCell) and primary cells (PCell) using Carrier Aggregation (CA). In addition, the terminal 20 may communicate via the primary cell of base station 10 and the primary secondary cell group cell (PSCell) of another base station 10 using Dual Connectivity (DC).

[0016] Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. As shown in Figure 1, Terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Terminal 20 also receives various reference signals transmitted from the base station 10 and performs propagation path quality measurement based on the reception results of said reference signals.

[0017] Figure 2 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. Figure 2 shows an example configuration of a wireless communication system when DC (Dual connectivity) is performed. As shown in Figure 2, a base station 10A, which will be an MN (Master Node), and a base station 10B, which will be an SN (Secondary Node), are provided. Base stations 10A and 10B are each connected to the core network. Terminal 20 can communicate with both base station 10A and base station 10B.

[0018] A cell group provided by base station 10A, which is an MN (Mobile Network), is called an MCG (Master Cell Group), and a cell group provided by base station 10B, which is an SN (Mobile Network), is called an SCG (Secondary Cell Group). In a data center, an MCG consists of one PCell and one or more SCells, and an SCG consists of one PSCell (Primary SCG Cell) and one or more SCells.

[0019] The processing operations in this embodiment may be performed using the system configuration shown in Figure 1, the system configuration shown in Figure 2, or any other system configuration. In the following description, " / " means "and / or" unless otherwise specified, or unless it is clear from the context that it has a different meaning.

[0020] 3GPP (registered trademark) is considering a power-saving technology called "Low-Power Wake Up Signal and Receiver." The Low-Power Wake Up Signal is called LP-WUS or simply WUS, and the Low-Power Wake Up Receiver is called LP-WUR, WUR, or LR. As an alternative to the main radio (MR) used in normal data communication, the LR, a simpler circuit that operates with lower power consumption than the MR, is activated to introduce a state called Ultra-Deep Sleep. The LR may have a function that triggers either the power off of the MR or the power on of the MR when the LR receives an LP-WUS signal.

[0021] Furthermore, 3GPP Rel-19 considers the following: For example, it defines a Low Power-Synchronization Signal (LP-SS) with a specific period corresponding to the LP-WUR for serving cell synchronization and / or Radio Resource Management (RRM) in idle / inactive modes. The LP-SS is a signal based on an On-Off Keying (OOK) waveform with or without an overlaid Orthogonal Frequency Division Multiplexing (OFDM) sequence. It also defines further RRM relaxation in the terminal MR for both serving cell and adjacent cell measurements, including necessary conditions, and UE serving cell RRM measurements offloaded from the MR to the LP-WUR.

[0022] The purpose of the RRM procedure in idle / inactive mode is to ensure that the terminal is camp-on to the best cell.

[0023] In serving cell measurement (see Non-Patent Document 3), the terminal measures the SS-RSRP and SS-RSRQ levels of the serving cell, and evaluates the cell selection criteria of the serving cell at least once every M1×N1 DRX cycles. Here, when the SMTC period (T SMTC ) > 20 ms and the DRX (Discontinuous Reception) cycle ≤ 0.64 seconds, M1 = 2; otherwise, M1 = 1. Also, in FR1, N1 = 1, and in FR2, N1 = 3 to 12.

[0024] Adjacent cell measurement (intra-frequency or inter-frequency cell reselection, see Section 5.2.4 of Non-Patent Document 3) needs to be executed only when the serving cell is not strong enough, that is, when at least one of the following is not satisfied. ・ Intra-frequency cell reselection criteria: Srxlev > S IntraSearchP and Squal > S IntraSearchQ ・ Inter-frequency cell reselection criteria: Srxlev > S nonIntraSearchP and Squal > S nonIntraSearchQ

[0025] Also, when the terminal is composed of DRX_IDLE / eDRX_IDLE cycles and the terminal evaluates that the serving cell does not meet the cell selection criteria in Nserv consecutive DRX / eDRX cycles, the terminal starts measuring all adjacent cells indicated by the serving cell regardless of the measurement rules that currently restrict the measurement activity. Here, the cell selection criteria S are Srxlev > 0 and Squal > 0 (see Section 5.2.3.2 of Non-Patent Document 3). Here, Srxlev and Squal are calculated as follows. ・ Srxlev = Q rxlevmeas -(Q rxlevmin +Q rxlevminoffset ) - P compensation -Q offsettemp ・ Squal = Q qualmeas -(Q qualmin +Q qualminoffset ) - Qoffset temp

[0026] For detection and synchronization using LP-WUR, initial synchronization and fine synchronization using SSB may be performed by MR. Initial synchronization may be replaced by coarse synchronization. Further synchronization using LP-SS and / or LP-WUS may be performed by detecting LP-SS and / or LP-WUS with LR. Hereinafter, LP-SS and / or LP-WUS will also be referred to as LP-SS / LP-WUS.

[0027] Figure 3 is a sequence diagram illustrating an example of receiving a low-power signal. In step S101, BS10 transmits a notification regarding LP-SS / LP-WUS to UE20. In step S102, UE20 sets LP-WUR based on the notification. In step S103, BS10 transmits LP-SS / LP-WUS to UE20. In step S104, UE20 detects or receives LP-SS / LP-WUS and performs synchronization, RRM measurement, or MR activation.

[0028] In idle / inactive mode, the UE performing LP-WUS monitoring can enter an ultra-deep sleep (UDS) state, which is an extremely low-power state.

[0029] Because UDS consumes extremely low power, UEs require a longer time to transition from UDS to a communicative state compared to legacy sleep states. Table 1 shows examples of ramp-up times for UEs with UDS and other legacy sleep states.

[0030]

[0031] The period from the processing time of LP-WUS by LR until MR completes synchronization or resynchronization is considered an example of "wake-up delay." This period may also be referred to as the wake-up delay.

[0032] As another example of wake-up delay, some IoT devices have a wake-up delay of, for example, 2000 ms, which is longer than the I (IDLE mode)-DRX cycle length, for example 1280 ms.

[0033] In the RRC CONNECTED mode, the wake-up delay may be the minimum gap from the reception of LP-WUS to the start of MR's PDCCH monitoring. Also, in the RRC CONNECTED mode, the wake-up delay at least includes the processing time of LP-WUS, the transition time for the ramp-up of MR, and the time required for the time-frequency synchronization of MR.

[0034] FIG. 4 is a diagram for explaining an example (1) of receiving a low-power signal. The wake-up delay may include the processing time of LP-WUS, the transition time for the ramp-up of MR, and the time required for the time-frequency synchronization of MR.

[0035] Since the wake-up delay of UDS is larger than that of the legacy sleep state, the time offset shown in FIG. 3 between LO (LP-WUS Occasion) and MO (Monitoring Occasion) and PO (Paging Occasion) may be set to be greater than or equal to the wake-up delay of the UE to ensure that the UE can monitor PO after receiving LP-WUS. Note that the time offset may be a time interval from the start of LO or the start of LO and MO to the start of PO as shown in FIG. 3. Note that the low-power wake-up signal opportunity is an opportunity to monitor a low-power wake-up signal and may be specified by at least a time-domain section. For example, an example of the low-power wake-up signal opportunity may be LO.

[0036] However, as described in the previous slide, since the UE has various wake-up delays, it is desirable to set several time offsets compensated for each wake-up delay.

[0037] Regarding the method of setting the time offset, the following Option 1 or Option 2 may be defined.

[0038] Option 1: The UE reports its ability related to wake-up delay to the network. The offset between LO and PO is set by the network based on the reported ability related to wake-up delay. One or more values may be included in the ability related to wake-up delay. One or more values may be set for the offset between LO and PO. Option 1 can compensate for some wake-up delays of the UE. On the other hand, since all UEs report their abilities related to wake-up delay, the NW overhead and UE complexity become higher. Since the wake-up delay is not specified, the time offset may be too large (e.g., 2000 ms) for an overly long wake-up delay of the UE.

[0039] Option 2: A single offset between LO and PO is set by the network. In this specification, a single value is specified for the wake-up delay, and UEs that support the LP-WUS function are assumed to support wake-up delays below this value. Option 2 can reduce the NW overhead and UE complexity because the time offset is determined without the UE reporting its ability related to wake-up delay. On the other hand, the UE cannot have various wake-up delays.

[0040] FIG. 5 is a diagram for explaining an example (2) of receiving a low-power signal. For example, as shown in FIG. 5, depending on the timing of the paging arrival, a case may occur where a UE that supports a short wake-up delay (e.g., 30 ms) can receive a paging message that can be received in Option 1 but cannot be received in Option 2.

[0041] The I-DRX cycle is assumed to be 1280 ms, and the wake-up delay is assumed to be 400 ms or 800 ms. At this time, the delay may occur with a probability of 400 ms / 1280 ms or 800 ms / 1280 ms. Therefore, Option 2 is not well-suited for UEs that support a short wake-up delay (e.g., 30 ms).

[0042] Figure 6 illustrates an example (3) of receiving a low-power signal. As shown in Figure 6, a UE with an excessively long wake-up delay (e.g., 2000 ms) will not be able to receive paging messages at all POs during the Legacy I-DRX cycle. Furthermore, such a UE will not be able to receive paging messages at all POs during LP-WUS monitoring.

[0043] The following describes how to allocate LP-WUS and LP-SS resources to the carrier band.

[0044] LR may assume an offset for LP-WUS and LP-SS resources with respect to bandwidth allocation. For example, within the MR carrier bandwidth, LR may assume an offset for LP-WUS and LP-SS resources. For example, outside the MR carrier bandwidth, LR may assume an offset for LP-WUS and LP-SS resources.

[0045] For LP-WUS, OOK (on-off keying)-1 and OOK-4 may be supported. For OOK-4, M-value modulation with M being 4 or less may be supported. The SCS of the CP-OFDM symbol used for LP-WUS generation may be the same as or different from one of the SCSs of CP-OFDM used for other NR transmissions.

[0046] For OOK-4 with M > 1, M = 2 and M = 4 may be supported for LP-WUS. For example, M = 4 may be supported for 15 kHz SCS, and M = 4 may be supported for 30 kHz SCS. Furthermore, M = 1 may be supported for OOK-4.

[0047] For channel bandwidths of 5 MHz or more in SCS 15 kHz, X = 11 PRBs without blank guard RBs may be supported for LP-WUS and LP-SS. For SCS 60 kHz and SCS 120 kHz in FR2, X = 11 PRBs may be supported for LP-WUS and LP-SS.

[0048] When RRC is idle or inactive, if at least the associated CD-SSB (Cell Defining SSB) and LP-WUS are on the same carrier, and the associated CD-SSB and initial DL-BWP have the same SCS, then the single SCS for LP-WUS and LP-SS may be the same as that of the associated CD-SSB. It may also be supported if the associated CD-SSB and initial DL-BWP have different SCSs. Furthermore, the single SCS for LP-WUS and LP-SS may be the same as that of the initial BWP for RedCap.

[0049] The single SCS for the LP-WUS used in the LP-WUR may be configured by the base station or may be predefined.

[0050] The initial DL-BWP may be set by the information element DownlinkConfigCommon (see Non-Patent Document 4), or the initial DL-BWP for RedCapUE may be set.

[0051] The following is being considered for LP-WUS / WUR.

[0052] An LP-WUS design that is applicable to both RRC_IDLE / INACTIVE mode and RRC_CONNECTED mode may be employed. An OOK (OOK-1 and / or OOK-4) based LP-WUS having OFDM sequences overlaid on OOK symbols may also be employed.

[0053] The LP-WUS design may ensure that the same information is delivered for RRC_IDLE / INACTIVE operation, regardless of the LP-WUR type. OFDM sequences can carry the information. At least LP-WUS duty cycle monitoring may be supported.

[0054] In RRC_IDLE / INACTIVE mode, the following operations 1)-3) may be performed.

[0055] 1) Procedures and settings for LP-WUS that notify of LP-WUS-triggered paging monitoring may be specified, including at least settings, subgrouping, and start / end conditions for LP-WUS monitoring.

[0056] 2) For the synchronization and / or RRM of the serving cell, an LP-SS having periodicity with Yms of the LP-WUR may be defined. The LP-SS may be based on OOK-1 and / or OOK-4 waveforms with or without an overlaid OFDM sequence. Further down-selection between those with and without an overlaid OFDM sequence may be performed. In the case of an LP-WUR that can receive an existing PSS / SSS, the existing PSS / SSS may be used for synchronization and RRM instead of the LP-SS. The above Y may start at, for example, 320ms, and other values ​​may be defined.

[0057] 3) Further RRM relaxation of the UE's MR for both serving cell measurements and adjacent cell measurements may be specified, along with UE serving cell RRM measurements offloaded from MR to LP-WUR, including necessary conditions.

[0058] In RRC_CONNECTED mode, a procedure may be specified to allow LP-WUS-triggered UE MR-based PDCCH monitoring, including activation or deactivation procedures for LP-WUS monitoring. Note that in CONNECTED mode, UE MR ultra-deep sleep is not considered, and UE RRM, RLM (Radio Link Monitoring), BFD (Beam Failure Detection), and CSI (Channel State Information) measurements are performed by MR.

[0059] Furthermore, the target coverage for LP-WUS and LP-SS may be the coverage for PUSCH in message 3. Also, optimization of the LP-WUS signal design for RRC idle / inactive mode may take precedence over optimization for RRC connected mode.

[0060] For channel bandwidths of 5 MHz or more, X PRBs may be supported for LP-WUS and LP-SS having an SCS of 30 kHz (excluding blanked guard RBs). X = 11 PRBs may also be supported. For LP-SS and LP-WUS with channel bandwidths of 5 MHz or less, a different number of PRBs may be supported. If FR2 applies, a different number of PRBs may be supported for LP-SS and LP-WUS.

[0061] For channel bandwidths of 5 MHz or more in SCS 15 kHz, X = 11 PRBs without blank guard RBs may be supported for LP-WUS and LP-SS. For SCS 60 kHz and SCS 120 kHz in FR2, X = 11 PRBs may be supported for LP-WUS and LP-SS.

[0062] When the RRC is idle / inactive, if at least the associated CD-SSB and LP-WUS are on the same carrier, and the associated CD-SSB and initial DL-BWP have the same SCS, then the single SCS for LP-WUS and / or LP-SS may be the same as that of the associated CD-SSB. If the associated CD-SSB and initial DL-BWP have different SCSs, then the single SCS for LP-WUS and / or LP-SS may be the same as that of the associated CD-SSB. The single SCS for LP-WUS and / or LP-SS may be the same as the initial BWP of RedCap.

[0063] In RRC_CONNECTED mode, LP-WUS may or may not support DCP (DCI with CRC scrambled by PS-RNTI), PDCCH skipping, SSSG (Search Space Set Group) switching, cell DTX, etc.

[0064] For option 1-1 of LP-WUS CONNECTED mode operation, the following assumptions may be made:

[0065] For periodic CSI / L1-RSRP reporting, the UE may be configured in one of the following ways: • Periodic CSI / L1-RSRP may not be reported during the time specified by the configured drx-onDurationTimer if the UE is not instructed to wake up. • Periodic CSI / L1-RSRP is reported periodically during the time specified by the configured drx-onDurationTimer, regardless of whether the UE is instructed to wake up. Note that periodic CSI / L1-RSRP may also be reported during the CDRX active time, as in the legacy specification.

[0066] Regarding options 1-2 for LP-WUS CONNECTED mode operation, the following may be assumed:

[0067] For periodic CSI / L1-RSRP reporting, the UE can be configured in one of the following ways (same as Rel-16 DCP and Option 1-1): • Periodic CSI / L1-RSRP reporting is not required if the UE is not instructed to wake up. • Periodic CSI / L1-RSRP reporting is required periodically, regardless of whether the UE is instructed to wake up.

[0068] When UE is configured using CA in RRC_CONNECTED mode, it may be specified whether and how LP-WUS functions. Cells to which LP-WUS-triggered PDCCH monitoring is applicable may be specified as follows: Other options are not excluded. Option 1: One or more serving cells based on gNB instruction / configuration Option 2: All activated serving cells

[0069] The definitions of CD-SSB and NCD-SSB (see Non-Patent Document 1) may also be as follows:

[0070] When an SSB is associated with an RMSI, it is called a Cell Defining SSB (CD-SSB). A PCell is always associated with a CD-SSB located on a synchronous raster. When an SSB is not associated with an RMSI, it is called a non-Cell Defining SSB (NCD-SSB). If an active BWP does not include a CD-SSB, the NCD-SSB can be used to perform RLM, BFD, and RRM measurements, and measurements for random access resource selection within an active DL-BWP. A UE can be configured with multiple SSBs, provided that each BWP is configured with at most one SSB (CD-SSB or NCD-SSB).

[0071] The NCD-SSB of BWP may be set as follows (see Non-Patent Document 4). The fields in the MIB associated with the CD-SSB and NCD-SSB within the same cell are set to the same value. The NCD-SSB may also be set by the information element BWP-DownlinkDedicated - nonCellDefiningSSB.

[0072] If an NCD-SSB is configured, a UE operating on that BWP will use the NCD-SSB for purposes that would otherwise have been handled by the serving cell's CD-SSB (e.g., synchronization, measurement, RLM, BFD, beam management). Furthermore, other parts of the BWP configuration that reference an SSB (e.g., "SSB" configured in QCL-Info IE, "ssb-Index" configured in RadioLinkMonitoringRS, CFRA-SSB-Resource, PRACH-ResourceDedicatedBFR) implicitly reference this NCD-SSB.

[0073] The NCD-SSB has the same values ​​for the corresponding CD-SSB attributes (e.g., ssb-PositionsInBurst, PCI, ssb-PBCH-BlockPower) as the NonCellDefiningSSB-r17 IE, separate from the attribute values ​​set in the NCD-SSB. In the MIB associated with the NCD-SSB, the systemFrameNumber field indicates the frame boundary and frame number of the NCD-SSB. subCarrierSpacingCommon and dmrs-TypeA-Position may also be set.

[0074] Figure 7 shows an example of BWP switching. As shown in Figure 7, a BWP switching delay occurs when switching from a 15kHz SCS BWP1 to a 30kHz SCS BWP2. For example, BWP switching may be supported as shown in the following case. Note that "switching" and "switching" may be interchangeable.

[0075] Case 1) BWP switching may be performed by RRC reconfiguration using firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id.

[0076] Case 2) BWP switching may be performed upon the expiration of the BWP inactivity timer (bwp-Inactivity timer). When the UE receives DCI, it starts or resets the timer and performs DL and / or UL scheduling, or transmits and receives by CG grant scheduling. The timer is decremented by 1 at the end of a subframe (FR1) or a half-subframe (FR2). When the timer expires, the BWP is switched to "defaultDownlinkBWP-Id".

[0077] Case 3) A BWP switch may be performed by a DCI notifying the BWP switch. The BWP switch may be notified by a DCI, for example, DCI format 0-1 or DCI format 1-1 having a field for "Bandwidth part indicator". The UE does not transmit or receive for a time of "slot offset" from the end of the third symbol after receiving the DCI indicating the BWP switch. The "slot offset" should be greater than or equal to the delay required for the BWP switch. The "slot offset" is the offset between the PDCCH carrying the DCI and the PDSCH or PUSCH scheduled by the DCI.

[0078] Case 4) If there are no PRACH resources configured for active UL-BWP, BWP switching for RACH may be performed.

[0079] When performing LP-WUS monitoring, the following two behaviors may be defined as UE behaviors:

[0080] 1) UE monitoring operation of PDCCH, LP-WUS, and LP-SS when LP-WUS and / or LP-SS are switched. 2) UE monitoring operation of PDCCH, LP-WUS, and LP-SS when BWP is switched but LP-WUS and / or LP-SS are not switched.

[0081] The following describes 1) the UE monitoring operation of PDCCH, LP-WUS, and LP-SS when LP-WUS and / or LP-SS are switched. Note that "LP-WUS / LP-SS" may be replaced with "LP-WUS and / or LP-SS".

[0082] "LP-WUS switching" may mean one or more of the following 1)-7).

[0083] 1) The frequency range and / or center frequency of the LP-WUS / LP-SS is switched or changed. 2) The frequency range and / or center frequency of the LP-WUS / LP-SS to be monitored is switched or changed. 3) The ID of the LP-WUS / LP-SS is switched or changed. 4) The parameters(s) of the LP-WUS / LP-SS, e.g., periodicity, offset, SCS, are switched or changed. 5) Switching to a BWP associated with a different LP-WUS / LP-SS than the BWP before the switch. 6) The BWP is switched. 7) The carrier or serving cell transmitting the LP-WUS / LP-SS is switched.

[0084] When LP-WUS / LP-SS switches, the switching delay of LP-WUS / LP-SS may be assumed as shown in 1) or 2) below.

[0085] 1) The UE may assume that the switching delay of BWP switching and the switching delay of LP-WUS / LP-SS are the same.

[0086] 2) The UE may assume that the switching delay of LP-WUS / LP-SS is different from the switching delay of BWP switching. The switching delay of LP-WUS / LP-SS may be determined by: - ​​The subcarrier interval of BWP, LP-WUS, or LP-SS before and after switching. - The reported UE capability. The UE may support reporting of supported values ​​or types of UE capability for LP-WUS / LP-SS switching delay. - If the switching of BWP, LP-WUS, or LP-SS is triggered by RRC, the switching delay may include the RRC processing delay.

[0087] If the UE is configured to perform LP-WUS / LP-SS monitoring, and BWP, LP-WUS, and / or LP-SS are switched, the UE may expect monitoring behaviors such as those shown in A)-D) below.

[0088] A) The UE does not need to monitor LP-WUS / LP-SS using the LP-WUS / LP-SS parameters until point 1-5 shown below, before switching between LP-WUS / LP-SS.

[0089] 1: The end of the third symbol after receiving a PDCCH indicating BWP switching (e.g., when DCI signals BWP switching). 2: The BWP-Inactivity timer expires (e.g., when the BWP inactivity timer expires). 3: The slot or time after receiving an RRC signaling or PDSCH indicating BWP switching, or T slot (e.g., when RRC signaling signals BWP switching). T is the RRC processing delay. 4: The time when the UE performs the RACH procedure (e.g., when BWP switching is performed for RACH). 5: The time when the UE starts BWP switching.

[0090] B) The UE may monitor the LP-WUS / LP-SS using the LP-WUS / LP-SS parameters after one or two of the following points in time, following the switching of the LP-WUS / LP-SS.

[0091] 1: A slot with a "slot offset" applied after the slot that receives the DCI having a field for BWP switching (for example, when the DCI notifies of BWP switching). The "slot offset" is the offset between the slot having the DCI carrying the BWP switching instruction and the slot having the PDSCH or PUSCH scheduled by the DCI. 2: A slot with a BWP, LP-WUS, or LP-SS switching delay applied after the UE has initiated BWP, LP-WUS, or LP-SS switching (for example, in the cases 1 / 2 / 4 above). The BWP, LP-WUS, or LP-SS switching delay may or may not include the RRC processing delay.

[0092] Furthermore, the LP-WUS / LP-SS monitoring described above should satisfy the following conditions. For example, these conditions include performing monitoring using MO and monitoring outside of RX active hours.

[0093] C) During a BWP, LP-WUS, or LP-SS switchover period, the UE may perform the following actions: - The UE falls back to the legacy procedure for PDCCH monitoring. For example, if C-DRX is configured, the UE follows the legacy C-DRX procedure for PDCCH monitoring. - The UE always assumes PDCCH monitoring for serving cells associated with LP-WUS / LP-SS. If LP-WUS / LP-SS is in one BWP of one serving cell, the UE does not need to monitor the PDCCH of the serving cell when the BWP switches and the LP-WUS / LP-SS switches accordingly. - The UE assumes that LP-WUS is not detected, or that LP-WUS is detected but does not trigger PDCCH monitoring, or that PDCCH monitoring is not triggered.

[0094] D) After the BWP, LP-WUS, or LP-SS switching is complete, the UE may perform the following actions:

[0095] - The UE monitors PDCCH. For example, an LP-WUS may be assumed to indicate a wake-up for PDCCH monitoring in the new BWP. - The UE assumes DRX active mode. - The UE monitors the LP-WUS in the new BWP as described in B above. - The UE assumes non-DRX active mode. - The UE follows legacy DRX operation. For example, LP-WUS monitoring is not configured for the new BWP.

[0096] Figure 8 shows an example (1) of LP-WUS in an embodiment of the present invention. As shown in Figure 8, LP-WUS is associated with PCell's BWP.

[0097] Figure 9 shows an example (2) of LP-WUS in an embodiment of the present invention. Figure 9 is an enlarged view of the frequency range of the PCell serving cell in Figure 8. As shown in Figure 9, the BWP switches in the PCell, and the LP-WUS switches accordingly. On the other hand, no BWP switching occurs in the other serving cells. As shown in Figure 9, after stopping LP-WUS monitoring in the 15kHz SCS BWP1, LP-WUS monitoring may be resumed in the 30kHz SCS BWP2 after a BWP switching delay has elapsed. The LP-WUS may be associated with each BWP.

[0098] The following describes the UE behavior related to PDCCH / LP-WUS / LP-SS monitoring when BWP switches but LP-WUS / LP-SS does not.

[0099] "LP-WUS / LP-SS does not switch" may mean one or more of the following cases 1)-6).

[0100] 1) The frequency range or center frequency of the LP-WUS / LP-SS does not switch or change. 2) The frequency range or center frequency of the LP-WUS / LP-SS monitoring does not switch / change. 3) The ID of the LP-WUS / LP-SS does not switch or change. 4) The parameters of the LP-WUS / LP-SS, such as periodicity, offset, and SCS, do not change. 5) The BWP before and after the switch are associated with the same LP-WUS / LP-SS. 6) The LP-WUS / LP-SS and the switched BWP are in different carriers or serving cells.

[0101] If the UE is configured using LP-WUS / LP-SS monitoring, and the BWP switches but the LP-WUS / LP-SS does not switch, the UE will follow the LP-WUS / LP-SS monitoring behavior shown in A) and / or B) below.

[0102] A) During the BWP switch period, the UE may assume one of the following: - The UE does not monitor LP-WUS / LP-SS. - The UE monitors LP-WUS / LP-SS. If the UE detects an LP-WUS indicating PDCCH monitoring, the UE assumes that PDCCH monitoring will not be triggered or will not be triggered for the serving cell where the BWP switch occurred. The UE does not monitor PDCCH, or does not monitor PDCCH within the serving cell where the BWP switch occurred.

[0103] B) After the BWP switchover is complete, the UE may assume one or more of the following: • The UE monitors PDCCH on the new BWP. For example, it assumes an LP-WUS that signals a wake-up for PDCCH monitoring on the new BWP. • The UE assumes DRX active mode. • The UE monitors LP-WUS. • The UE assumes non-DRX active mode. • The UE follows legacy DRX operation. For example, it does not configure LP-WUS monitoring for the new BWP.

[0104] Figure 10 shows an example (3) of LP-WUS in an embodiment of the present invention. Figure 11 shows an example (4) of LP-WUS in an embodiment of the present invention. Figure 11 is an enlarged view of the frequency ranges of serving cells Cell #1 and Cell #3 of PCell in Figure 10. As shown in Figure 11, LP-WUS is not associated with PCell's BWP. PCell's LP-WUS is associated with BWP1 and BWP2. LP-WUS does not switch with PCell's BWP. As shown in Figure 11, UE may continue monitoring LP-WUS even when BWP switching occurs in other serving cell Cell #3.

[0105] The following describes how the UE configures the BWP for the LR and MR. The UE may receive information regarding the configuration of the BWP for the LR and MR from the base station or network.

[0106] Option 1: LR or MR may assume a BWP setting for only one of LR or MR.

[0107] Case 1: In the case of an OOK-based receiver or OFDM-based receiver that does not use SSB, the following Alt may apply.

[0108] Alt1: TDM case or FDM case. LR uses BWP settings for LP-WUS and LP-SS, while MR does not use BWP settings and only uses frequency gap settings for CD-SSB, NCD-SSB, or PDCCH.

[0109] Alt2: TDM case or FDM case. MR uses BWP settings for CD-SSB, NCD-SSB, or PDCCH, while LR does not use BWP settings and uses only frequency gap settings for LP-WUS and LP-SS.

[0110] Case 2: For OFDM-based receivers using SSB, the following Alt may apply.

[0111] Alt1: TDM case or FDM case. LR uses BWP settings for LP-WUS and LP-SS, while MR does not use BWP settings and uses only frequency gap settings for CD-SSB, NCD-SSB, or PDCCH. At least one of CD-SSB or NCD-SSB must be within the BWP of LR when in RRC_CONNECTED mode.

[0112] Option 2: LR and MR may assume BWP settings for LR and MR.

[0113] Case 1: If the receiver type is an envelope detector or an OFDM receiver without SSB, the following Alt may apply.

[0114] Alt. 1: TDM case or FDM case. LR: Initial DL BWP for Legacy UE MR: Initial DL BWP for Legacy UE

[0115] Alt. 2: TDM case or FDM case. LR: Initial DL-BWP set by LP-WUS "InitialDownlinkBWP-LPWUS" MR: Initial DL-BWP for Legacy UE Option 1: LR-BWP is a case located outside MR-BWP. Option 2: LR-BWP is a case located inside MR-BWP.

[0116] Alt. 3: TDM case or FDM case. LR: Initials DL-BWP of LPWUS "InitialDownlinkBWP-LPWUS" MR: Initials DL-BWP of LPWUS "InitialDownlinkBWP-LPWUS"

[0117] Alt. 4: TDM case or FDM case. LR: Initial DL-BWP for RedCap MR: Initial DL-BWP for RedCap

[0118] Alt. 5: TDM case or FDM case. LR: Initial DL BWP for LPWUS "InitialDownlinkBWP-LPWUS". MR: Initial DL-BWP for RedCap. Option 1: LR-BWP is a case located outside MR-BWP. Option 2: LR-BWP is a case located inside MR-BWP.

[0119] Alt. 6: TDM case or FDM case. LR: Initial DL-BWP for Legacy UE MR: Initial DL-BWP for RedCap Option 1: MR-BWP is a case located outside LR-BWP. Option 2: MR-BWP is a case located inside LR-BWP.

[0120] Case 2: For OFDM-based receivers using SSB, the following Alt may apply.

[0121] Alt. 1: TDM case or FDM case. Figure 12 shows an example of BWP setting (1) in an embodiment of the present invention. Figure 12 shows an example of the TDM case. Figure 13 shows an example of BWP setting (2) in an embodiment of the present invention. Figure 13 shows an example of the FDM case. LR: Initial DL-BWP for Legacy UE. MR: Initial DL-BWP for Legacy UE. CD-SSB is located inside or outside LR-BWP.

[0122] Alt. 2: TDM case or FDM case. LR: Initial DL-BWP for LPWUS "InitialDownlinkBWP-LPWUS". MR: Initial DL-BWP for Legacy UE. Option 1 LR-BWP is located outside MR-BWP. Figure 14 shows an example of BWP setting (3) in an embodiment of the present invention. Figure 14 shows an example of Option 1. Option 2 LR-BWP is located inside MR-BWP and CD-SSB is located outside LR-BWP. Figure 15 shows an example of BWP setting (4) in an embodiment of the present invention. Figure 15 shows an example of Option 2. Option 3 LR-BWP is located inside MR-BWP and CD-SSB is located inside LR-BWP. Figure 16 shows an example of BWP setting (5) in an embodiment of the present invention. Figure 16 shows an example of Option 3. The initial DL-BWP of LPWUS is located outside or inside the initial DL-BWP of LegacyUE, and SSB may be within the BWP of at least LR, at least in connected mode.

[0123] Alt. 3: TDM case or FDM case. Figure 17 shows an example (6) of BWP settings in an embodiment of the present invention. Figure 17 shows an example of the TDM case. LR: Initial DL-BWP of LPWUS "InitialDownlinkBWP-LPWUS". MR: Initial DL-BWP of LPWUS "InitialDownlinkBWP-LPWUS".

[0124] Alt. 4: TDM case or FDM case. Figure 18 shows an example (7) of the BWP configuration in an embodiment of the present invention. Figure 18 shows an example of the TDM case. LR: Initial DL-BWP for RedCap. MR: Initial DL-BWP for RedCap. CD or NCD-SSB is located inside or outside of LR-BWP.

[0125] Alt. 5: TDM case or FDM case. LR: Initial DL-BWP for LPWUS "InitialDownlinkBWP-LPWUS". MR: Initial DL-BWP for RedCap. Option 1 LR-BWP is located outside MR-BWP. Figure 19 shows an example of BWP configuration (8) in an embodiment of the present invention. Figure 19 shows an example of Option 1. Option 2 LR-BWP is located inside MR-BWP, and CD-SSB and NCD-SSB are located outside LR-BWP. Figure 20 shows an example of BWP configuration (9) in an embodiment of the present invention. Figure 20 shows an example of Option 2. Option 3 LR-BWP is located inside MR-BWP, and CD-SSB and NCD-SSB are located inside LR-BWP. Figure 21 shows an example of BWP settings (10) in an embodiment of the present invention. Figure 21 shows an example of option 3. Option 4 LR-BWP is located inside MR-BWP, CD-SSB is located outside LR-BWP, and NCD-SSB is located inside LR-BWP. Figure 22 shows an example of BWP settings (11) in an embodiment of the present invention. Figure 22 shows an example of option 4. Option 5 LR-BWP is located inside MR-BWP, CD-SSB is located inside LR-BWP, and NCD-SSB is located outside LR-BWP. Figure 23 shows an example of BWP settings (12) in an embodiment of the present invention. Figure 23 shows an example of option 5. The initial DL-BWP of LPWUS is located outside or inside the initial DL-BWP of RedCap, and SSB may be within the BWP of LR, at least when in RRC_CONNECTED mode.

[0126] Alt. 6: TDM case or FDM case. LR: Initial DL-BWP for Legacy UE. MR: Initial DL-BWP for RedCap, and the SSB must be within the LR BWP at least when in RRC_CONNECTED mode. Option 1 The MR-BWP is located outside the LR-BWP. Figure 24 shows an example of BWP configuration (13) in an embodiment of the present invention. Figure 24 shows an example of Option 1. Option 2 The MR-BWP is located inside the LR-BWP, and the CD-SSB and NCD-SSB are located outside the LR-BWP. Figure 25 shows an example of BWP configuration (14) in an embodiment of the present invention. Figure 25 shows an example of Option 2. Option 3: MR-BWP is located inside LR-BWP, and CD-SSB and NCD-SSB are located inside LR-BWP. Option 4: MR-BWP is located inside LR-BWP, CD-SSB is located outside LR-BWP, and NCD-SSB is located inside LR-BWP. Option 5: MR-BWP is located inside LR-BWP, CD-SSB is located inside LR-BWP, and NCD-SSB is located outside LR-BWP. The initial DL-BWP of RedCap is located outside or inside the initial DL-BWP of LegacyUE, and the SSB may be located inside the LR BWP at least when in RRC_CONNECTED mode.

[0127] UE may be configured with BWP for LP-WUS. The following configurations are possible:

[0128] In RRC_IDLE / INACTIVE mode, similar to MR, the following options are possible on the same carrier:

[0129] Case 2: The receiver type is an OFDM receiver using SSB.

[0130] Alt. 1 LR: Initial DL-BWP for Legacy UE. MR: Initial DL-BWP for Legacy UE.

[0131] Alt. 2 LR: Initial DL-BWP for LPWUS "InitialDownlinkBWP-LPWUS". MR: Initial DL-BWP for Legacy UE.

[0132] Alt. 3 LR: DL-BWP, the initials of LPWUS "InitialDownlinkBWP-LPWUS". MR: DL-BWP, the initials of LPWUS "InitialDownlinkBWP-LPWUS".

[0133] Alt. 4 LR: Initial DL-BWP for RedCap MR: Initial DL-BWP for RedCap

[0134] Alt. 5 LR: Initial DL-BWP for LPWUS "InitialDownlinkBWP-LPWUS". MR: Initial DL-BWP for RedCap.

[0135] Alt. 6 LR: Initial DL-BWP for Legacy UE MR: Initial DL-BWP for RedCap

[0136] According to the above-described embodiment, in the wireless communication system, the UE can set a BWP related to LP-WUS and / or LP-SS and perform monitoring of MOs within the target LO.

[0137] In other words, in a wireless communication system, low-power signals can be received by an LP-WUR (Low-power Wake-up receiver).

[0138] (Device Configuration) Next, an example of the functional configuration of the base station 10 and terminal 20 that perform the processes and operations described above will be explained. The base station 10 and terminal 20 include the functions to carry out the above-described embodiment. However, the base station 10 and terminal 20 may each be equipped with only some of the functions in the embodiment.

[0139] <Base Station 10> Figure 26 is a diagram showing an example of the functional configuration of a base station 10 in an embodiment of the present invention. As shown in Figure 26, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 26 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment of the present invention.

[0140] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The transmitting unit 110 also transmits setting information, instructions, and notifications related to the low-power wake-up signal to the terminal 20. The transmitting unit 110 also transmits notifications to the terminal regarding the switching of monitoring operations. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 and obtaining information from the received signals, for example, information from a higher layer. The transmitting unit 110 also has the function of transmitting PSS, SSS, PBCH, DL / UL control signals, etc. to the terminal 20. The receiving unit 120 also receives inter-network node messages from other network nodes.

[0141] The setting unit 130 stores pre-set setting information and various setting information to be transmitted to the terminal 20. The content of the setting information includes, for example, information related to measurements in low-power signals.

[0142] As described in the embodiment, the control unit 140 performs control related to setting, instructing, and notifying about low-power wake-up signals and the like. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120.

[0143] <Terminal 20> Figure 27 is a diagram showing an example of the functional configuration of terminal 20 in an embodiment of the present invention. As shown in Figure 27, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 27 is merely an example. Any functional classification and name of functional unit is acceptable as long as it can perform the operations according to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as the communication unit.

[0144] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The transmitting unit 210 also transmits capability information related to the low-power wake-up signal to the base station 10. The receiving unit 220 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. The receiving unit 220 also receives paging notification information, setting information, instructions, and notifications related to the low-power wake-up signal from the base station 10. For example, the receiving unit 220 receives the low-power wake-up signal from the base station 10. The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores pre-set setting information. The content of the setting information is, for example, information related to measurements in low-power signals.

[0145] As described in the embodiment, the control unit 240 performs control related to setting, instructing, and notifying of low-power wake-up signals. The signal transmission function unit of the control unit 240 may be included in the transmission unit 210, and the signal reception function unit of the control unit 240 may be included in the reception unit 220.

[0146] (Hardware Configuration) The block diagrams (Figures 26 and 27) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the one device or the multiple devices with software.

[0147] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0148] For example, the base station 10, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 28 is a diagram showing an example of the hardware configuration of the base station 10 and terminal 20 according to one embodiment of the present disclosure. The above-mentioned base station 10 and terminal 20 may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0149] In the following explanation, the term "device" can be read as "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0150] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the storage device 1002 and auxiliary storage device 1003.

[0151] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0152] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 26 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 27 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-described processes have been explained as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line.

[0153] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of the present disclosure.

[0154] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital multipurpose disk, a Blu-ray® disk), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0155] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antenna, amplifier section, transmitting and receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting and receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section.

[0156] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0157] Furthermore, each device, such as the processor 1001 and the storage device 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0158] Furthermore, the base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0159] Figure 29 shows an example of the configuration of vehicle 2001. As shown in Figure 29, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

[0160] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user.

[0161] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0162] Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 for sensing motor current, front or rear wheel rotation speed signals acquired by rotation speed sensor 2022, front or rear wheel air pressure signals acquired by air pressure sensor 2023, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression signals acquired by accelerator pedal sensor 2029, brake pedal depression signals acquired by brake pedal sensor 2026, shift lever operation signals acquired by shift lever sensor 2027, and detection signals acquired by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0163] The Information Service Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. The Information Service Unit 2012 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0164] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0165] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via the communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 provided in the vehicle 2001.

[0166] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information with external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

[0167] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include the information based on the above input.

[0168] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0169] <Configuration relating to this embodiment> (1) A terminal having a receiving unit that monitors the low-power wake-up signal based on the BWP (Bandwidth Part) setting related to the low-power wake-up signal, and a control unit that, when the low-power wake-up signal is received, monitors the paging opportunity associated with the low-power wake-up signal, wherein the control unit sets the BWP to at least one of the LR (Low-Power Wake Up Receiver) and MR (Main Radio) based on the BWP setting. (2) The terminal according to paragraph 1, wherein the control unit sets the BWP to either the LR or the MR. (3) The terminal according to paragraph 1, wherein the control unit sets the BWP to each of the LR and the MR. (4) The terminal according to paragraph 1, wherein when the control unit switches the low-power wake-up signal associated with a certain BWP, it assumes a switching delay and does not perform monitoring of the low-power wake-up signal until a certain point in time. (Clause 5) The terminal according to Clause 1, wherein when the control unit switches the BWP, it does not assume a switching delay for monitoring the low-power wake-up signal that is not associated with the BWP. (Clause 6) A communication method in which a terminal performs the following steps: a procedure for monitoring the low-power wake-up signal based on the BWP (Bandwidth Part) setting related to the low-power wake-up signal; a procedure for monitoring the paging opportunity associated with the low-power wake-up signal when the low-power wake-up signal is received; and a procedure for setting the BWP on at least one of the LR (Low-Power Wake Up Receiver) and MR (Main Radio) based on the BWP setting.

[0170] In any of the above configurations, a low-power signal can be received by an LP-WUR (Low-power Wake-up receiver) in the wireless communication system. Furthermore, according to paragraphs 2 to 5, in the wireless communication system, the UE can set up a BWP related to LP-WUS and / or LP-SS and perform monitoring of MOs within the target LO.

[0171] (Supplement to Embodiments) Embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.

[0172] Furthermore, notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0173] Each aspect / embodiment described in this disclosure may be applied to at least one of the following systems: LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (new Radio), W-CDMA®, GSM®, CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

[0174] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0175] In this specification, specific operations performed by the base station 10 may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station 10, it is clear that various operations performed for communication with the terminal 20 can be performed by the base station 10 and at least one of the other network nodes (for example, an MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station 10, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0176] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0177] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0178] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0179] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0180] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0181] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0182] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0183] The terms “system” and “network” as used in this disclosure are interchangeable.

[0184] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0185] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0186] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "base station equipment", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0187] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0188] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information.

[0189] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0190] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0191] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0192] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminals 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0193] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above.

[0194] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in a table, database, or other data structure), or ascertaining. “Determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0195] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0196] The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard.

[0197] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0198] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

[0199] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.

[0200] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0201] A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0202] Numerical logic may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerical logic may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0203] A slot may consist of one or more symbols in the time domain (such as OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A slot may also be a time unit based on neurologic.

[0204] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called a PDSCH (or PUSCH) mapping type B.

[0205] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0206] For example, one subframe may be called a Transmission Time Interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0207] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, the base station schedules each terminal 20 to allocate wireless resources (such as the frequency bandwidth and transmission power available to each terminal 20) in TTI units. However, the definition of TTI is not limited to this.

[0208] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

[0209] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled.

[0210] A TTI with a time length of 1 ms may be called a normal TTI, a long TTI, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, a slot, etc.

[0211] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0212] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0213] Furthermore, the time domain of the RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0214] One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0215] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0216] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a particular neurology in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP.

[0217] A BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be set within a single carrier for a UE.

[0218] At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0219] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0220] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0221] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0222] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0223] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0224] This international patent application claims priority based on Japanese Patent Application No. 2025-010992, filed on 24 January 2025, and the entire contents of Japanese Patent Application No. 2025-010992 are incorporated herein by reference.

[0225] 10 Base station 110 Transmitting unit 120 Receiving unit 130 Setting unit 140 Control unit 20 Terminal 210 Transmitting unit 220 Receiving unit 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driver assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

1. A terminal comprising: a receiving unit that monitors the low-power wake-up signal based on the Bandwidth Part (BWP) setting related to the low-power wake-up signal; and a control unit that, when the low-power wake-up signal is received, monitors the paging opportunity associated with the low-power wake-up signal, wherein the control unit sets the BWP to at least one of the LR (Low-Power Wake Up Receiver) and MR (Main Radio) based on the BWP setting.

2. The terminal according to claim 1, wherein the control unit sets BWP to either LR or MR.

3. The terminal according to claim 1, wherein the control unit sets BWP to each of the LR and MR.

4. The terminal according to claim 1, wherein when the control unit switches the low-power wake-up signal associated with a BWP, it assumes a switching delay and does not perform monitoring of the low-power wake-up signal until a certain point in time.

5. The terminal according to claim 1, wherein the control unit does not assume a switching delay when switching the BWP, in monitoring the low-power wake-up signal that is not associated with the BWP.

6. A communication method in which a terminal performs the following steps: a procedure for monitoring a low-power wake-up signal based on a Bandwidth Part (BWP) setting related to a low-power wake-up signal; a procedure for monitoring a paging opportunity associated with a low-power wake-up signal when the low-power wake-up signal is received; and a procedure for setting a BWP on at least one of the Low-Power Wake Up Receiver (LR) and Main Radio (MR) based on the BWP setting.