Terminal and communication method

Abstract

To receive a low-power signal using an LP-WUR (Low power Wake up receiver) in a wireless communication system.SOLUTION: A terminal includes a receiving unit that monitors a low-power wake-up signal on the basis of a 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 a paging opportunity associated with the low-power wake-up signal, and the control unit sets the BWP to at least one of an LR (Low-Power Wake-Up Receiver) and an MR (Main Radio) on the basis of the BWP setting.SELECTED DRAWING: Figure 8

Description

[Technical Field]

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

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) is currently studying a wireless communication system called 5G or NR (New Radio) (hereinafter, this wireless communication system will be referred to as "NR") in order to achieve a larger system capacity, a higher data transmission speed, and a lower latency in wireless sections. In 5G, various wireless technologies and network architectures are being studied to meet the requirements of achieving a throughput of 10 Gbps or more while keeping the latency in wireless sections to 1 ms or less (for example, Non-Patent Document 1 and Non-Patent Document 2). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP TS 38.300 V18.3.0 (2024-09) [Non-patent document 2] 3GPP TS 38.401 V18.3.0 (2024-09) [Non-patent document 3] 3GPP TS 38.304 V18.3.0 (2024-09) [Non-patent document 4] 3GPP TS 38.331 V18.3.0 (2024-09) Summary of the Invention [Problem to be solved by the invention]

[0004] 3GPP Rel-19 is considering an ultra-low power LP (Low Power)-WUS (Wake Up Signal) / WUR (Wake Up Receiver) system 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 has an object to receive a low power signal in a wireless communication system using a low power wake-up receiver (LP-WUR). [Means for solving the problem]

[0006] According to the disclosed technology, a terminal is provided that includes a receiving unit that monitors a low-power wake-up signal based on a 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 a paging opportunity associated with the low-power wake-up signal, and the control unit sets the BWP to at least one of an LR (Low-Power Wake-Up Receiver) and an MR (Main Radio) based on the BWP setting. [Effects of the Invention]

[0007] According to the disclosed technology, a low power signal can be received by a low power wake-up receiver (LP-WUR) in a wireless communication system. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. [Figure 2] 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. [Figure 3] FIG. 10 is a sequence diagram illustrating an example of receiving a low-power signal. [Figure 4]FIG. 10 is a diagram for explaining an example (1) of receiving a low-power signal. [Figure 5] FIG. 10 is a diagram for explaining an example (2) of receiving a low-power signal. [Figure 6] FIG. 10 is a diagram for explaining an example (3) of receiving a low-power signal. [Figure 7] FIG. 10 is a diagram illustrating an example of switching of BWP. [Figure 8] FIG. 1 is a diagram showing an example (1) of an LP-WUS according to an embodiment of the present invention. [Figure 9] FIG. 10 is a diagram showing an example (2) of an LP-WUS according to an embodiment of the present invention. [Figure 10] FIG. 10 is a diagram showing an example (3) of an LP-WUS according to an embodiment of the present invention. [Figure 11] FIG. 10 is a diagram showing an example (4) of an LP-WUS according to an embodiment of the present invention. [Figure 12] FIG. 10 is a diagram showing an example (1) of a BWP setting in an embodiment of the present invention. [Figure 13] FIG. 10 is a diagram showing an example (2) of BWP settings in the embodiment of the present invention. [Figure 14] FIG. 10 is a diagram showing an example (3) of BWP settings in the embodiment of the present invention. [Figure 15] FIG. 10 is a diagram showing an example (4) of BWP settings in the embodiment of the present invention. [Figure 16] FIG. 10 is a diagram showing an example (5) of BWP settings in the embodiment of the present invention. [Figure 17] FIG. 10 is a diagram showing an example (6) of BWP settings in the embodiment of the present invention. [Figure 18] FIG. 10 is a diagram showing an example (7) of BWP settings in the embodiment of the present invention. [Figure 19] FIG. 10 is a diagram showing an example (8) of BWP settings in the embodiment of the present invention. [Figure 20] FIG. 10 is a diagram showing an example (9) of BWP settings in the embodiment of the present invention. [Figure 21] FIG. 10 is a diagram showing an example of BWP setting in an embodiment of the present invention. [Figure 22] FIG. 11 is a diagram showing an example (11) of BWP settings in an embodiment of the present invention. [Figure 23] FIG. 12 is a diagram showing an example (12) of BWP settings in an embodiment of the present invention. [Figure 24] FIG. 13 is a diagram showing an example of BWP setting in an embodiment of the present invention. [Figure 25] FIG. 14 is a diagram showing an example (14) of BWP settings in an embodiment of the present invention. [Figure 26] 2 is a diagram illustrating an example of a functional configuration of a base station 10 according to an embodiment of the present invention. [Figure 27] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 20 according to the embodiment of the present invention. [Figure 28] 2 is a diagram illustrating an example of a hardware configuration of a base station 10 or a terminal 20 according to an embodiment of the present invention. [Figure 29] FIG. 2 is a diagram showing an example of the configuration of a vehicle 2001 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0010] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are used as appropriate. However, the existing technologies are, for example, but not limited to, the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR) unless otherwise specified.

[0011] Furthermore, in the embodiments of the present invention described below, terms used in existing LTE, 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), are used. This is for convenience of description, and similar signals, functions, etc. may be called by other names. The above-mentioned terms in NR are 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 method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).

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

[0014] Fig. 1 is a diagram showing an example of the configuration of a wireless communication system according to an embodiment of the present invention. As shown in Fig. 1, the wireless communication system according to the embodiment of the present invention includes a base station 10 and a terminal 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.

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

[0016] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in Fig. 1, the 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. The terminal 20 also receives various reference signals transmitted from the base station 10 and measures the propagation path quality based on the reception results of the reference signals.

[0017] Fig. 2 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. Fig. 2 shows an example of the configuration of a wireless communication system in which DC (Dual connectivity) is implemented. As shown in Fig. 2, a base station 10A serving as an MN (Master Node) and a base station 10B serving as an SN (Secondary Node) are provided. The base station 10A and the base station 10B are each connected to a core network. The terminal 20 can communicate with both the base station 10A and the base station 10B.

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

[0019] The processing operations in this embodiment may be executed in the system configuration shown in Fig. 1, in the system configuration shown in Fig. 2, or in other system configurations. 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 currently studying a power consumption reduction 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. The LR, a simple circuit that operates with lower power consumption than the Main Radio (MR) used in normal data communications, operates as an alternative to the MR, introducing a state called Ultra-Deep Sleep. The LR may have a function that triggers the MR to be powered off or powered on when it receives an LP-WUS signal.

[0021] 3GPP Rel-19 also considers the following: For example, it specifies 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 mode / inactive mode. 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 specifies necessary conditions, further RRM relaxation in the MR of the UE for both serving cell measurements and neighbor cell measurements, 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 camped on 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. SMTC If FR1 is greater than 20 ms and the DRX (Discontinuous Reception) cycle is less than or equal to 0.64 seconds, then M1 = 2; otherwise, M1 = 1. Also, N1 = 1 in FR1, and N1 = 3 to 12 in FR2.

[0024] Neighbor cell measurements (intra- or inter-frequency cell reselection, see section 5.2.4 of 3GPP TS 36.210) only need to be performed if the serving cell is not strong enough, i.e., if one of the following is not met: 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] Furthermore, if the terminal is configured with a DRX_IDLE / eDRX_IDLE cycle and the terminal evaluates that the serving cell does not satisfy the cell selection criterion in Nserv consecutive DRX / eDRX cycles, the terminal starts measuring all neighboring cells indicated by the serving cell, regardless of the measurement rule that currently restricts the measurement activity. Here, the cell selection criterion S is 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] Regarding detection and synchronization by LP-WUR, initial synchronization and fine synchronization using SSB may be performed by MR. Note that initial synchronization may be replaced by coarse synchronization. Further synchronization by LP-SS and / or LP-WUS may be performed by detecting LP-SS and / or LP-WUS by LR. Hereinafter, LP-SS and / or LP-WUS are also referred to as LP-SS / LP-WUS.

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

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

[0029] Because UDS has extremely low power consumption, a UE takes longer to transition from UDS to a communication-enabled state compared to a legacy sleep state. Examples of ramp-up times for a UE with UDS and other legacy sleep states are shown in Table 1.

[0030] [Table 1]

[0031] The period from the time it takes for the LR to process the LP-WUS until the MR completes synchronization or resynchronization is considered an example of a “wake-up delay.” This period may also be referred to as a wake-up delay.

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

[0033] In the RRC CONNECTED mode, the wake-up delay may be the minimum gap between the reception of the LP-WUS and the start of PDCCH monitoring by the MR, and includes at least the processing time of the LP-WUS, the transition time for ramping up the MR, and the time-frequency synchronization time of the MR.

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

[0035] Since the wake-up delay of UDS is longer than that of the legacy sleep state, the time offset shown in FIG. 3 between LO (LP-WUS Occasion), MO (Monitoring Occasion), and PO (Paging Occasion) may be set to be equal to or greater than the wake-up delay of the UE to ensure that the UE can monitor the PO after receiving the LP-WUS. Note that the time offset may be the time interval from the beginning of LO or the beginning of LO and MO to the beginning of the 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 an interval in the time domain. For example, an example of a low-power wake-up signal opportunity may be LO.

[0036] However, as mentioned in the previous slide, UEs have different wake-up delays, so it is desirable to set several time offsets that compensate for each wake-up delay.

[0037] The following option 1 or option 2 may be specified for the time offset setting method.

[0038] Option 1: The UE reports its wake-up delay capability to the network. The offset between LO and PO is configured by the network based on the reported wake-up delay capability. One or more values ​​may be included in the wake-up delay capability. One or more values ​​may be configurable for the offset between LO and PO. Option 1 can compensate for some wake-up delays of UEs. On the other hand, since all UEs report their wake-up delay capability, the network overhead and UE complexity are higher. Because the wake-up delay is not specified, the time offset may be too large (e.g., 2000 ms) for a UE with a long wake-up delay.

[0039] Option 2: A single offset between LO and PO is configured by the network. In this specification, a single value is specified for the wake-up delay, and UEs that support the LP-WUS feature shall support a wake-up delay equal to or less than this value. Option 2 reduces network overhead and UE complexity because the time offset is determined without the UE reporting its wake-up delay capability. However, UEs cannot have different wake-up delays.

[0040] 5 is a diagram illustrating 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 UE that supports a short wake-up delay (e.g., 30 ms) may be unable to receive a paging message in Option 2, even though it can receive it in Option 1.

[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. In this case, 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] 6 is a diagram illustrating an example (3) of receiving a low-power signal. As shown in FIG. 6, a UE with a long wake-up delay (e.g., 2000 ms) cannot receive paging messages in all POs during a legacy I-DRX cycle. Also, the UE cannot receive paging messages in all POs during LP-WUS monitoring.

[0043] The following describes a method for allocating LP-WUS and LP-SS resources to carrier bands.

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

[0045] For LP-WUS, on-off keying (OOK)-1 and OOK-4 may be supported. For OOK-4, M-ary modulation with M less than or equal to 4 may be supported. The SCS of the CP-OFDM symbols used for LP-WUS generation may be the same as or different from one of the SCSs of the CP-OFDM symbols 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. Note that M=1 may also be supported for OOK-4.

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

[0048] In the RRC idle or inactive state, the single SCS for the LP-WUS and LP-SS may be the same as the associated CD-SSB, at least when 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. Note that the case where the associated CD-SSB and initial DL-BWP have different SCSs may be supported. Note that the single SCS for the LP-WUS and LP-SS may be the same as the initial BWP for RedCap.

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

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

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

[0052] A LP-WUS design that is commonly applicable to both RRC_IDLE / INACTIVE and RRC_CONNECTED modes may be adopted, including an OOK (OOK-1 and / or OOK-4) based LP-WUS with an OFDM sequence overlaid on the OOK symbols.

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

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

[0055] 1) It may specify the procedure and settings for LP-WUS to notify monitoring of paging triggered by LP-WUS, including at least the settings, subgrouping and start / end conditions for LP-WUS monitoring.

[0056] 2) For serving cell synchronization and / or RRM, an LP-SS with a periodicity of Y ms for 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. Note that for 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 from, for example, 320 ms, but other values ​​may also be defined.

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

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

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

[0060] For channel bandwidths of 5 MHz or greater, X PRBs may be supported for LP-WUS and LP-SS with SCS 30 kHz (blanked guard RBs not included). X may equal 11 PRBs. Other numbers of PRBs may be supported for LP-SS and LP-WUS with channel bandwidths of 5 MHz or less. Other numbers of PRBs may be supported for LP-SS and LP-WUS when applicable to FR2.

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

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

[0063] In the RRC_CONNECTED mode, the 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, and the like.

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

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

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

[0067] For periodic CSI / L1-RSRP reporting, the UE can be configured with one of the following (same as Rel-16 DCP and Option 1-1): If the UE is not instructed to wake up, periodic CSI / L1-RSRP may not be reported. Periodic CSI / L1-RSRP may be reported periodically whether the UE is instructed to wake up or not.

[0068] When a UE is configured with CA in RRC_CONNECTED mode, it may specify whether / how LP-WUS functions. Cells to which PDCCH monitoring triggered by LP-WUS is applicable may be specified as follows, with other options 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 be as follows:

[0070] When an SSB is associated with an RMSI, the SSB is called a Cell Defining SSB (CD-SSB). A PCell is always associated with a CD-SSB located on the synchronization raster. When an SSB is not associated with an RMSI, the SSB 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, as well as 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 the BWP may be set as follows (see Non-Patent Document 4): The fields in the MIB associated with the CD-SSB and NCD-SSB in the same cell are set to the same value. The NCD-SSB may also be set by the information element BWP-DownlinkDedicated-nonCellDefiningSSB.

[0072] When an NCD-SSB is configured, a UE operating in this BWP uses the NCD-SSB for purposes for which it would otherwise have used the serving cell's CD-SSB (e.g., synchronization, measurements, RLM, BFD, beam management). Furthermore, other parts of the BWP configuration that refer to an SSB (e.g., "SSB" configured in the QCL-Info IE, "ssb-Index" configured in the RadioLinkMonitoringRS, CFRA-SSB-Resource, PRACH-ResourceDedicatedBFR) implicitly refer to 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) apart from the attribute values ​​set in the NonCellDefiningSSB-r17 IE. In the MIB associated with the NCD-SSB, the systemFrameNumber field indicates the frame boundary and frame number of the NCD-SSB. The subCarrierSpacingCommon and dmrs-TypeA-Position may also be set.

[0074] FIG. 7 is a diagram showing an example of BWP switching. As shown in FIG. 7, when switching from BWP1 with 15 kHz SCS to BWP2 with 30 kHz SCS, a BWP switching delay occurs. For example, BWP switching may be supported as shown in the following cases. 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 triggered by the expiration of the BWP inactivity timer (bwp-Inactivity timer). The UE starts or resets this timer when it receives DCI and performs DL and / or UL scheduling or transmits / receives with CG grant scheduling. This timer is decremented by 1 at the end of a subframe (FR1) or half subframe (FR2). When this timer expires, the BWP is switched to the "defaultDownlinkBWP-Id".

[0077] Case 3) BWP switching may be performed by DCI indicating BWP switching. BWP switching may be indicated by DCI, for example, DCI format 0-1 or DCI format 1-1 having a "Bandwidth part indicator" field. The UE does not transmit or receive until the "slot offset" time from the end of the third symbol after receiving the DCI indicating BWP switching. The "slot offset" should be equal to or greater than the delay required for BWP switching. 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 in the active UL-BWP, BWP switching for RACH may be performed.

[0079] For LP-WUS monitoring, the following two UE behaviors may be specified:

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

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

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

[0083] 1) The frequency range and / or center frequency of LP-WUS / LP-SS is switched or changed. 2) The frequency range and / or center frequency of the LP-WUS / LP-SS being monitored is switched or changed. 3) The ID of the LP-WUS / LP-SS is switched or changed. 4) The parameter(s) of LP-WUS / LP-SS, such as periodicity, offset, SCS, is switched or changed. 5) Switching to a BWP associated with a different LP-WUS / LP-SS than the previous BWP. 6) BWP can be switched. 7) The carrier or serving cell transmitting 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: Subcarrier spacing for BWP, LP-WUS or LP-SS before and after switching. Reported UE Capabilities: The UE may support reporting of UE capabilities of supported values ​​or types of 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] When the UE is configured for LP-WUS / LP-SS monitoring and when BWP, LP-WUS and / or LP-SS switch, the UE may assume monitoring behaviors such as A)-D) shown below.

[0088] A) The UE may not monitor the LP-WUS / LP-SS using the LP-WUS / LP-SS parameters until points 1-5 below before switching between LP-WUS / LP-SS.

[0089] 1: End of the third symbol after receiving a PDCCH indicating BWP switching (e.g., when DCI indicates BWP switching). 2: The bwp-Inactivity timer expires (e.g., when the BWP inactivity timer expires). 3: The slot or T slots after the slot or time when RRC signaling or PDSCH indicating BWP switching is received (for example, when RRC signaling indicates BWP switching), where T is the RRC processing delay. 4: Time when the UE performs the RACH procedure (e.g., when performing BWP switching for RACH). 5: Time when UE starts BWP switching.

[0090] B) The UE may monitor the LP-WUS / LP-SS using the parameters of the LP-WUS / LP-SS from point 1 or 2 below after switching between the LP-WUS / LP-SS.

[0091] 1: The slot after the slot in which the DCI carrying the BWP switching field is received with a "slot offset" applied (e.g., when the DCI signals BWP switching). The "slot offset" is the offset between the slot with the DCI carrying the BWP switching indication and the slot with the PDSCH or PUSCH scheduled by the DCI. 2: The slots to which the BWP, LP-WUS or LP-SS switching delay is applied after the UE initiates BWP, LP-WUS or LP-SS switching (e.g., for Case 1 / Case 2 / Case 4 above). The BWP, LP-WUS or LP-SS switching delay may or may not include the RRC processing delay.

[0092] The above LP-WUS / LP-SS monitoring should satisfy the following conditions: For example, these conditions include the condition for performing monitoring in MO and the condition for monitoring outside of RX active time.

[0093] C) During the BWP, LP-WUS or LP-SS switching period, the UE may perform the following actions: The UE falls back to legacy procedures for PDCCH monitoring. For example, if C-DRX is configured, the UE follows legacy C-DRX procedures for PDCCH monitoring. The UE always assumes PDCCH monitoring for the serving cell to which the LP-WUS / LP-SS is associated. If the LP-WUS / LP-SS is within 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 no LP-WUS is detected, or that an LP-WUS is detected but does not trigger PDCCH monitoring, or that PDCCH monitoring is not triggered.

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

[0095] The UE monitors the PDCCH, for example, LP-WUS may be assumed to indicate 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 behavior, i.e. does not configure LP-WUS monitoring for the new BWP.

[0096] 8 is a diagram showing an example (1) of an LP-WUS in an embodiment of the present invention. As shown in Fig. 8, the LP-WUS is associated with a BWP of a PCell.

[0097] Fig. 9 is a diagram showing an example (2) of an LP-WUS according to an embodiment of the present invention. Fig. 9 is a diagram showing an expanded frequency range of the serving cell of the PCell in Fig. 8. As shown in Fig. 9, the BWP switches in the PCell, and the LP-WUS switches accordingly. Meanwhile, no BWP switching occurs in other serving cells. As shown in Fig. 9, after LP-WUS monitoring is stopped in BWP1 with a 15 kHz SCS, LP-WUS monitoring may be resumed in BWP2 with a 30 kHz SCS after a BWP switching delay has elapsed. An LP-WUS may be associated with each BWP.

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

[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 LP-WUS / LP-SS does not switch or change. 2) The frequency range or center frequency of LP-WUS / LP-SS monitoring does not switch / change. 3) The LP-WUS / LP-SS ID does not switch or change. 4) The parameters of LP-WUS / LP-SS, e.g., periodicity, offset, and SCS, do not change. 5) The BWP before the switch and the BWP 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 with LP-WUS / LP-SS monitoring, and if BWP switches and LP-WUS / LP-SS does not switch, the UE shall follow the LP-WUS / LP-SS monitoring behavior shown in A) and / or B) below.

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

[0103] B) After the BWP switchover is completed, the UE may assume one or more of the following: The UE monitors the PDCCH in the new BWP. For example, assume LP-WUS indicating wake-up for PDCCH monitoring in the new BWP. The UE assumes DRX active mode. ·UE monitors LP-WUS. The UE assumes non-DRX active mode. The UE follows legacy DRX behavior, i.e. does not configure LP-WUS monitoring for the new BWP.

[0104] Fig. 10 is a diagram showing an example (3) of an LP-WUS according to an embodiment of the present invention. Fig. 11 is a diagram showing an example (4) of an LP-WUS according to an embodiment of the present invention. Fig. 11 is a diagram showing an expanded view of the frequency ranges of serving cells Cell#1 and Cell#3 of the PCell in Fig. 10. As shown in Fig. 11, the LP-WUS is not associated with the BWP of the PCell. The LP-WUS of the PCell is associated with BWP1 and BWP2. The LP-WUS does not switch together with the BWP of the PCell. As shown in Fig. 11, the UE may continue monitoring the LP-WUS even when BWP switching occurs in another serving cell Cell#3.

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

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

[0107] Case 1: For OOK-based receivers or OFDM-based receivers without SSB, the following Alt may apply.

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

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

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

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

[0112] Option 2: The LR and MR may assume a BWP configuration for the 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: Initials for Legacy UE DL BWP

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

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

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

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

[0119] Alt.6: TDM case or FDM case. LR: Initials DL-BWP for legacy UE MR: Initials DL-BWP for RedCap Option 1: The MR-BWP is located outside the LR-BWP. Option 2: The MR-BWP is located inside the LR-BWP.

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

[0121] Alt. 1: TDM case or FDM case. Fig. 12 is a diagram showing an example (1) of BWP settings in an embodiment of the present invention. Fig. 12 shows an example of the TDM case. Fig. 13 is a diagram showing an example (2) of BWP settings in an embodiment of the present invention. Fig. 13 shows an example of the FDM case. LR: Initials DL-BWP for Legacy UE. MR: Initials DL-BWP for Legacy UE. The CD-SSB is located inside or outside the LR-BWP.

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

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

[0124] Alt. 4: TDM case or FDM case. Fig. 18 is a diagram showing an example (7) of BWP settings in an embodiment of the present invention. Fig. 18 shows an example of the TDM case. LR: The initials DL-BWP for RedCap. MR: The initials DL-BWP for RedCap. The CD or NCD-SSB is located inside or outside the LR-BWP.

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

[0126] Alt.6: TDM case or FDM case. LR: Initials DL-BWP for Legacy UE. MR: RedCap initials DL-BWP, SSB must be in BWP of at least LR at least when in RRC_CONNECTED mode. Option 1: The MR-BWP is located outside the LR-BWP. Figure 24 is a diagram showing an example (13) of BWP configuration in an embodiment of the present invention. Figure 24 shows an example of this 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 is a diagram showing an example (14) of BWP configuration in an embodiment of the present invention. Figure 25 shows an example of this option 2. Option 3: The MR-BWP is located inside the LR-BWP, and the CD-SSB and NCD-SSB are located inside the LR-BWP. Option 4: The MR-BWP is located inside the LR-BWP, the CD-SSB is located outside the LR-BWP, and the NCD-SSB is located inside the LR-BWP. Option 5: The MR-BWP is located inside the LR-BWP, the CD-SSB is located inside the LR-BWP, and the NCD-SSB is located outside the LR-BWP. The initial DL-BWP of RedCap may be located outside or inside the initial DL-BWP of the legacy UE, and the SSB may be within the BWP of the LR at least when in RRC_CONNECTED mode.

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

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

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

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

[0131] Alt.2 LR:LPWUS "InitialDownlinkBWP-LPWUS" initials DL-BWP. MR: Initials DL-BWP for legacy UE

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

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

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

[0135] Alt.6 LR: Initials DL-BWP for legacy UE MR: Initials DL-BWP for RedCap

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

[0137] That is, in a wireless communication system, a low power signal can be received by a low power wake-up receiver (LP-WUR).

[0138] (Device configuration) Next, a description will be given of an example of the functional configuration of the base station 10 and the terminal 20 that execute the processes and operations described above. The base station 10 and the terminal 20 include functions for implementing the above-described embodiments. However, the base station 10 and the terminal 20 may each include only a part of the functions of the embodiments.

[0139] <Base station 10> Fig. 26 is a diagram showing an example of the functional configuration of base station 10 in the embodiment of the present invention. As shown in Fig. 26, 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 Fig. 26 is merely an example. The functional divisions and names of the functional units may be any names as long as they can perform the operations related to the embodiment of the present invention.

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

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

[0142] As described in the embodiments, the control unit 140 controls settings, instructions, and notifications related to low-power wake-up signals, etc. A functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and a functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0143] <Terminal 20> Fig. 27 is a diagram showing an example of the functional configuration of terminal 20 in the embodiment of the present invention. As shown in Fig. 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 Fig. 27 is merely an example. As long as the operations related to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as a communication unit.

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

[0145] As described in the embodiments, the control unit 240 controls the settings, instructions, and notifications related to the low-power wake-up signal. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0146] (Hardware configuration) The block diagrams (FIGS. 26 and 27) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or the multiple devices with software.

[0147] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0148] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 28 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above 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 description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0150] Each function in the base station 10 and the terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0151] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0152] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 26 may be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 27 may be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0153] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0154] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk 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 versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of the storage device 1002 and the secondary storage device 1003.

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

[0156] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, 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 may be configured using different buses between each device.

[0158] Furthermore, base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

[0159] Fig. 29 shows an example configuration of a vehicle 2001. As shown in Fig. 29, the 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 the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0160] The drive unit 2002 is configured, for example, by 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 operated by the user.

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

[0162] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a front or rear wheel rotation speed signal obtained by a rotation speed sensor 2022, a front or rear wheel air pressure signal obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

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

[0164] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0165] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are 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 an external device. For example, it transmits and receives various information to and from the external device 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, a mobile station, or the like.

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

[0168] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker 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 external devices 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 to 2029, etc. provided in the vehicle 2001.

[0169] <Configuration of this embodiment> (Section 1) a receiver that monitors a low-power wakeup signal based on a BWP (Bandwidth Part) setting associated with the low-power wakeup signal; a control unit that, when receiving the low power wake-up signal, monitors a paging occasion associated with the low power wake-up signal; The control unit sets a BWP to at least one of a Low-Power Wake Up Receiver (LR) and a Main Radio (MR) based on the BWP setting. (Section 2) 2. The terminal according to claim 1, wherein the control unit sets a BWP in either the LR or the MR. (Section 3) 2. The terminal according to claim 1, wherein the control unit sets a BWP for each of the LR and the MR. (Section 4) The terminal according to claim 1, wherein the control unit assumes a switching delay when switching the low power wake-up signal associated with a certain BWP and does not monitor the low power wake-up signal until a certain point in time. (Section 5) 2. The terminal of claim 1, wherein the control unit, when switching BWPs, does not assume a switching delay due to monitoring of the low power wakeup signal not associated with the BWP. (Section 6) monitoring the low power wakeup signal based on a BWP (Bandwidth Part) setting associated with the low power wakeup signal; if the low power wake-up signal is received, monitoring a paging occasion associated with the low power wake-up signal; and a procedure for setting a BWP in at least one of a Low-Power Wake Up Receiver (LR) and a Main Radio (MR) based on the BWP setting.

[0170] Any of the above configurations allows a low power signal to be received by a low power wake-up receiver (LP-WUR) in a wireless communication system. Also, according to paragraphs 2 to 5, in the wireless communication system, a UE can set a BWP related to an LP-WUS and / or an LP-SS and monitor an MO in a target LO.

[0171] (Supplementary explanation of the embodiment) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, 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; two or more items may be combined as needed, and items described in one item may apply to items described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of the processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.

[0172] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0173] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), 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 (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark), IEEE 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.

[0174] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

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

[0176] The information or signals described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0177] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0178] In the present disclosure, the determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0179] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0180] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

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

[0182] Note that terms explained 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 a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0183] As used in this disclosure, the terms "system" and "network" are used interchangeably.

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

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

[0186] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "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. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0188] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0189] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. 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 some other suitable terminology.

[0191] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does 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, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between a plurality of terminals 20 (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0193] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

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

[0195] The terms "connected," "coupled," or any variation thereof, refer to 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" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

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

[0197] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0198] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

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

[0200] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0201] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed 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] Numerology may be communication parameters that apply to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

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

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

[0205] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[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. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 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, a base station performs scheduling to allocate wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

[0208] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0209] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0210] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0211] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

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

[0213] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0214] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

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

[0216] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0217] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0218] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0219] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio 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, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0220] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0221] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0222] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0223] Although the present disclosure has been described in detail above, it is 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 spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0224] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device 2001 Vehicle 2002 Drive unit 2003 Steering section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 front wheel 2008 rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 RPM 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 Driving Assistance Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. a receiver that monitors the low power wakeup signal based on a BWP (Bandwidth Part) setting related to the low power wakeup signal; a control unit that, when receiving the low power wake-up signal, monitors a paging occasion associated with the low power wake-up signal; The control unit sets the BWP to at least one of a low-power wake-up receiver (LR) and a main radio (MR) based on the BWP setting.

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

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

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

5. The terminal of claim 1 , wherein the control unit, when switching between BWPs, does not assume a switching delay due to monitoring the low power wakeup signal not associated with the BWP.

6. monitoring the low power wakeup signal based on a BWP (Bandwidth Part) setting associated with the low power wakeup signal; if the low power wake-up signal is received, monitoring a paging occasion associated with the low power wake-up signal; and a procedure for setting a BWP to at least one of a Low-Power Wake Up Receiver (LR) and a Main Radio (MR) based on the BWP setting.

Images