Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure is characterized by comprising: a reception unit that receives a first reference signal (RS) on a first carrier common to a plurality of terminals in a first band; and a control unit that, on the basis of the measurement result of the first RS, controls the reception of a downlink (DL) channel on a second carrier in a second band different from the first band and specific to the terminal. According to one aspect of the present disclosure, advanced services that surpass 5G NR can be achieved.

Description

Terminal, Wireless Communication Method, and Base Station

[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system.

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified for the purpose of achieving further high data rates, low latency, etc. (Non-Patent Document 1). Also, for the purpose of further increasing capacity and sophistication of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9), LTE-Advanced (3GPP Rel. 10-14) was specified.

[0003] Successor systems to LTE (for example, also referred to as 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later, etc.) are also being considered.

[0004] 3GPP TS 36.300 V8.12.0, "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)", April 2010

[0005] In future wireless communication systems (for example, Rel. 21 and later, 6G systems), in order to solve social issues in the 2030s and later, the realization of advanced services beyond the 5G NR system is expected.

[0006] However, it is necessary to consider carrier regulations and RS transmission / reception control for realizing such services, but this consideration has not been sufficient. If this consideration is insufficient, there is a risk that advanced services beyond 5G NR will not be realized.

[0007] Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can realize advanced services beyond 5G NR.

[0008] A terminal according to one aspect of the present disclosure is characterized by having a receiving unit that receives a first reference signal (RS) in a first carrier common to a plurality of terminals in a first band, and a control unit that controls the reception of a downlink (DL) channel in a second carrier specific to the terminal in a second band different from the first band, based on the measurement result of the first RS.

[0009] According to one aspect of this disclosure, it is possible to realize advanced services that go beyond 5G NR.

[0010] Figure 1 shows an example of initial access / 4-step RA. Figure 2 shows an example of 2-step RA. Figures 3A and 3B show an overview of MIMO. Figure 4A shows an overview of the cellular system. Figure 4B shows an overview of the cell-free system. Figure 5A shows an example overview of Cell-Free Configuration Assumption 1. Figure 5B shows an example overview of Cell-Free Configuration Assumption 2. Figure 5C shows another example overview of Cell-Free Configuration Assumption 2. Figure 6 shows an example of carrier design in this disclosure. Figures 7A / 7B / 7C show an example of carrier in this disclosure. Figure 8 shows an example of RS receive control. Figure 9 shows an example of RS receive control. Figure 10 shows an example of P-RS transmit control. Figure 11 shows an example of P-RS transmit control. Figure 12 shows an example of RS / channel receive control. Figure 13 shows an example of RS / channel receive control. Figure 14 shows an example of RS / channel receive control. Figure 15 shows an example of RS / channel receive control. Figure 16 shows an example of carrier / bandwidth used for RS / channel transmission / reception. Figure 17 shows an example of RS / channel receive control. Figure 18 shows an example of RS / channel receive control. Figure 19 shows an example of QCL relationship in this disclosure. Figure 20 shows an example of QCL relationship in this disclosure. Figure 21 shows an example of initial access. Figure 22 shows an example of carrier / bandwidth used for RS / channel transmission / reception. Figure 23 shows an example of carrier / bandwidth used for RS / channel transmission / reception. Figure 24 shows an example of RS#1 and RS#2 resource settings. Figure 25 shows an example of RS#1 and RS#2 resource settings. Figure 26 shows an example of Embodiment 5.1. Figure 27 shows an example of Embodiment 5.2. Figure 28 shows an example of Type 2P-RS#1 and P-RS#2 resource settings. Figure 29 shows an example of resource settings for Type 2P-RS#1 and P-RS#2. Figure 30 shows an example of resource settings for Type 2P-RS#1 and Type 1P-RS#1.Figure 31 shows an example of resource configuration for Type 2P-RS#1 and Type 1P-RS#1. Figure 32 shows an example of Embodiment 5.3C. Figure 33 shows an example of Embodiment 5.3C. Figure 34 shows an example of information regarding Type 2P-RS#1 resources for measuring peripheral cells. Figure 35 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Figure 36 shows an example of a base station configuration according to one embodiment. Figure 37 shows an example of a user terminal configuration according to one embodiment. Figure 38 shows an example of the hardware configuration of a base station and user terminal according to one embodiment. Figure 39 shows an example of a vehicle according to one embodiment.

[0011] (TCI, Spatial Relations, QCL) The NR controls the receive processing (e.g., at least one of receive, demapping, demodulation, and decoding) and transmit processing (e.g., transmit, mapping, precoding, modulation, and encoding) of at least one of the signal and channel (referred to as signal / channel) in the UE based on the Transmission Configuration Indication state (TCI state).

[0012] The TCI state may represent the one applied to the downlink signal / channel. The equivalent of the TCI state applied to the uplink signal / channel may be expressed as a spatial relation.

[0013] TCI status refers to information about signal / channel quasi-co-location (QCL), and may also be called spatial reception parameters or spatial relation information. TCI status may be set in the UE for each channel or signal.

[0014] QCL is an index that indicates the statistical properties of a signal / channel. For example, if one signal / channel and another signal / channel have a QCL relationship, it may mean that we can assume that at least one of the following is identical between these different signals / channels: Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter).

[0015] The spatial reception parameters may correspond to the received beam of the UE (e.g., the received analog beam), or the beam may be identified based on the spatial QCL. In this disclosure, QCL (or at least one element of QCL) may be interpreted as sQCL (spatial QCL).

[0016] Multiple types of QCLs (QCL types) may be defined. For example, four QCL types A-D may be provided, each with different parameters (or parameter sets) that can be assumed to be identical.

[0017] The assumption by a User Engineer (UE) that one control resource set (CORESET), channel, or reference signal is in a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be called a QCL assumption.

[0018] The UE may determine at least one of the transmit beam (Tx beam) and receive beam (Rx beam) of a signal / channel based on the TCI status or QCL assumption of the signal / channel.

[0019] The TCI state may, for example, be information regarding the QCL between the channel in question (in other words, the reference signal (RS) for that channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by upper-layer signaling, physical layer signaling, or a combination thereof.

[0020] Physical layer signaling may include, for example, Downlink Control Information (DCI).

[0021] The channel / RS to which the TCI status is applied may be called the target channel / RS, or simply the target.

[0022] The channel on which the TCI state or spatial relationship is set (specified) may be, for example, at least one of the following: Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Physical Uplink Shared Channel (PUSCH), or Physical Uplink Control Channel (PUCCH).

[0023] Furthermore, the RS that has a QCL relationship with the channel may be at least one of the following: a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), a Tracking CSI-RS (also called a Tracking Reference Signal (TRS)), or a QCL detection reference signal (also called a QRS).

[0024] An SSB is a signal block that includes at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). An SSB may also be called an SS / PBCH block.

[0025] The RS of a QCL type X in a TCI state may also mean the RS in relation to a certain channel / signal (or its DMRS) and QCL type X, and this RS may be called the QCL source [RS], QCL type X source [RS], etc., in that TCI state.

[0026] In NR, the following four quasi co-location (QCL) types are defined: • QCL Type A (Doppler shift, Doppler spread, mean delay, and delay spread) • QCL Type B (Doppler shift and Doppler spread) • QCL Type C (Doppler shift and mean delay) • QCL Type D (Spatial reception parameters)

[0027] The following combinations of DL channels / signals and QCL types can be used.

[0028] The TCI status for a periodic (P)-tracking reference signal (TRS) (a P-CSI-RS resource in the NZP-CSI-RS-ResourceSet with trs-Info configured) indicates one of the following QCL types: • Type C and Type D using SSB. • Type C using SSB and Type D using a repetitive CSI-RS.

[0029] The TCI status for aperiodic (AP)-TRS indicates one of the following QCL types: Type A and Type D, using P-TRS.

[0030] The TCI state for repetitive CSI-RS represents one of the following QCL types: • Type A and Type D using TRS. • Type A using TRS and Type D using repetitive CSI-RS. • Type C and Type D using SSB.

[0031] The TCI status for non-repetitive CSI-RS represents one of the following QCL types: • Type A and Type D using TRS. • Type A using TRS and Type D using SSB. • Type A using TRS and Type D using repetitive CSI-RS. • Type B using TRS (Type D is not applicable).

[0032] A unified TCI framework can control multiple types of channels / RS (UL / DL) using a common framework. Instead of defining TCI states or spatial relationships for each channel as in Rel. 15, the unified TCI framework may specify a common beam (joint TCI state) and apply it to all UL and DL channels, or it may apply a common beam for UL (UL TCI state) to all UL channels and a common beam for DL ​​(DL TCI state) to all DL channels.

[0033] One beam for both DL and UL (one joint TCI state), or one beam for DL ​​and one beam for UL (two separate TCI states, DL TCI state and UL TCI state) are being considered.

[0034] The Unified TCI Framework supports the following modes 1 through 3: <<Mode 1>> MAC CE based TCI state indication <<Mode 2>> DCI based TCI state indication by DCI format 1_1 / 1_2 with DL assignment <<Mode 3>> DCI based TCI state indication by DCI format 1_1 / 1_2 without DL assignment

[0035] The DCI in Mode 2 / Mode 3 described above may also be called beam-indicating DCI.

[0036] In this disclosure, the terms DCI-indicated TCI state, indicated TCI state, unified TCI state, TCI state applied to multiple types of channels / signals, joint TCI state for DL ​​and UL, DL TCI state, UL TCI state, Rel. 17 TCI state, common TCI state, single unified TCI state to be set, and single unified TCI state to be activated may be interpreted as one another.

[0037] In this disclosure, the terms TCI state set by RRC parameters, configured TCI state, set TCI state, TCI state that does not conform to the unified TCI state, TCI state other than the unified TCI state, TCI state / spatial relationship set for a specific channel / signal, and individual TCI state may be interpreted interchangeably.

[0038] For PDCCH / PDSCH systems that do not have a unified TCI state set, the TCI state will be one of the following QCL types: • Type A and Type D using TRS. • Type A using TRS and Type D using repetitive CSI-RS. • Type A and Type D using non-repetitive (non-TRS) CSI-RS.

[0039] For PDCCH / PDSCH with a unified TCI state, the TCI state will be one of the following QCL types: • Type A and Type D using TRS. • Type A using TRS and Type D using repetitive CSI-RS.

[0040] For UL Transmit (Tx) spatial filtering, several RSs can be used: • SSB / CSI-RS / SRS can be set / instructed as the [QCL] source RS for determining the UL Tx spatial filter. • If the Joint TCI state is set, SSB / CSI-RS is applicable as the [QCL] source RS for determining the UL Tx spatial filter.

[0041] (Initial Access Procedure) In the initial access procedure of NR, UE (RRC_IDLE mode) performs a random access procedure after receiving an SS / PBCH block (SSB) (see Figure 1).

[0042] In the random access procedure, Msg. 1 (PRACH / Random Access Preamble / Preamble) is sent, Msg. 2 (PDCCH, PDSCH including Random Access Response (RAR)) is received, Msg. 3 (PUSCH scheduled by the RAR UL grant) is sent, and Msg. 4 (PDCCH, PDSCH including UE contention resolution identity) is received (see Figure 1). Subsequently, when the UE sends an ACK in response to Msg. 4 from the base station (network), the RRC connection is established (RRC_CONNECTED mode).

[0043] The reception of SSB includes PSS detection, SSS detection, PBCH-DMRS detection, and PBCH reception. PSS detection performs detection of a part of the physical cell ID (PCI), detection of OFDM symbol timing (synchronization), and (coarse) frequency synchronization. SSS detection includes detection of the physical cell ID. PBCH-DMRS detection includes detection of (a part of) the SSB index within a half radio frame (5 ms). PBCH reception includes detection of the system frame number (SFN) and radio frame timing (SSB index), reception of the configuration information for receiving the remaining minimum system information (RMSI, SIB1), and recognition of whether the UE can camp on that cell (carrier).

[0044] SSB has a bandwidth of 20 RBs and a time of 4 symbols. The transmission period of SSB can be set from {5, 10, 20, 40, 80, 160} ms. In a half frame, multiple symbol positions of SSB are defined based on the frequency range (FR1, FR2).

[0045] PBCH has a payload of 56 bits. N repetitions of PBCH are transmitted within a period of 80 ms. N depends on the SSB transmission period.

[0046] System information consists of the MIB carried by PBCH, RMSI (SIB1), and other system information (OSI). SIB1 includes RACH configuration and information for performing the RACH procedure. The time / frequency resource relationship between SSB and the PDCCCH monitoring resource for SIB1 is set by PBCH.

[0047] The frequency at which the UE searches for PSS / SSS may be called the synchronization raster.

[0048] In NR, the center frequency of SSB is located on the synchronization raster.

[0049] The synchronization raster is defined for each frequency range (FR1 / FR2).

[0050] The wider the frequency interval of the synchronous raster (the fewer the number of synchronous rasters), the shorter the search time during initial access and the lower the load.

[0051] The list of potential frequency locations where component carriers (CCs) are placed is called a channel raster.

[0052] The spacing of synchronization rasters is determined to satisfy specific conditions. Specifically, the spacing of synchronization rasters is determined such that, regardless of which channel raster has the minimum channel bandwidth (CBW) at which CC is placed, there is at least one synchronization raster in which the SSB bandwidth is included in that CBW.

[0053] If the UE fails to receive SSB data on a specific synchronization raster within a specified period, it will attempt to receive SSB data on another synchronization raster. The length of this period depends on the UE implementation.

[0054] During initial access, the order in which the UE searches for synchronized rasters depends on the UE implementation. For efficient searching, a Global Synchronization Channel Number (GSCN) is defined, and the GSCN offset / GSCN range is notified to the UE.

[0055] Except during the initial access, the search frequencies for PSS / SSS are instructed to the UE by the network (NW, e.g., base station).

[0056] For example, when instructed to perform RSRP / RSRQ / SINR measurements on surrounding cells, the UE specifies the SSB frequency using the higher-level parameter "MeasObjectNR".

[0057] For example, if instructed to add a serving cell, the UE is given the SSB frequency using the higher-level parameter "FrequencyInfoDL".

[0058] For example, UE (RRC_IDLE mode) is specified using SIB4 (InterFreqCarrierFreqInfo) to indicate the SSB frequency.

[0059] A base station using beam correspondence transmits multiple SSBs using multiple beams (analog beams) for each SSB transmission cycle. These multiple SSBs may be called SSB bursts. Each of these multiple SSBs has multiple SSB indices. When a UE detects one SSB, it transmits a PRACH in the RACH occasion associated with that SSB index and receives a RAR in the RAR window.

[0060] Furthermore, NR is considering multiple PRACH formats (PRACH preamble formats). A Random Access (RA) preamble using each PRACH format includes RACH OFDM symbols. In addition, an RA preamble may include at least one of a cyclic prefix (CP) and a guard period (GP). For example, PRACH formats 0 to 3 use long-sequence preamble sequences in RACH OFDM symbols. PRACH formats A1 to A3, B1 to B4, C0, and C2 use short-sequence preamble sequences in RACH OFDM symbols.

[0061] (Random Access Procedures) NR supports random access procedures for establishing UL synchronization. Random access procedures include collision-based random access (also known as Contention-Based Random Access (CBRA), etc.) and non-collision-based random access (also known as Non-CBRA, Contention-Free Random Access (CFRA), etc.).

[0062] In Collision-Type Random Access (CBRA), the User Encoder (UE) transmits a preamble randomly selected from several preambles defined for each cell (also known as a random access preamble, random access channel (PRACH), RACH preamble, etc.). Collision-Type Random Access is a UE-led random access procedure and can be used, for example, during initial access, or when starting or resuming UL transmission.

[0063] On the other hand, in non-collision random access (Non-CBRA, CFRA), the base station assigns a preamble to the UE specifically via the downlink control channel (Physical Downlink Control Channel (PDCCH)), and the UE transmits the preamble assigned by the base station. Non-collision random access is a network-driven random access procedure and can be used, for example, during handover, or when DL transmission is started or resumed (when transmission of DL retransmission instruction information in the UL is started or resumed).

[0064] As shown in Figure 1, in the random access procedure, the UE receives information indicating the configuration of the random access channel (PRACH) (PRACH configuration, RACH configuration) in advance through system information (e.g., MIB (Master Information Block) and / or SIB (System Information Block)) or higher-layer signaling (e.g., RRC (Radio Resource Control) signaling).

[0065] The PRACH configuration information can include, for example, multiple preambles defined for each cell (e.g., preamble format), time resources used for PRACH transmission (e.g., system frame number, subframe number), and frequency resources (e.g., an offset indicating the starting position of a 6-resource block (PRB: Physical Resource Block) (prach-FrequencyOffset)).

[0066] When the UE transitions from the idle (RRC_IDLE) state to the RRC connected (RRC_CONNECTED) state (for example, during initial access), or when the RRC connected state is in place but UL synchronization has not been established (for example, when UL transmission is started or resumed), it randomly selects one of several preambles indicated by the PRACH configuration information and transmits the selected preamble via PRACH (Message 1, Msg. 1).

[0067] When a base station detects a preamble, it sends a Random Access Response (RAR) in response (Message 2, Msg. 2). If the UE fails to receive the RAR within a predetermined period (RAR window) after sending the preamble, it increases the PRACH transmit power and retransmits the preamble. This increase in transmit power during retransmission is also known as power ramping.

[0068] Upon receiving the RAR, the UE adjusts the UL transmission timing based on the timing advance (TA) included in the RAR and establishes UL synchronization. The UE also sends a control message for the upper layer (L2 / L3: Layer 2 / Layer 3) using the UL resource specified by the UL grant included in the RAR (Message 3, Msg. 3). This control message includes the UE identifier (UE-ID). This UE identifier may be, for example, C-RNTI (Cell-Radio Network Temporary Identifier) ​​if the RRC connection is active, or it may be a higher layer UE-ID such as S-TMSI (System Architecture Evolution-Temporary Mobile Subscriber Identity) if the state is idle.

[0069] The base station sends a collision resolution message in response to a control message from a higher layer (Message 4, Msg. 4). This collision resolution message is sent based on the identifier of the UE included in the control message. A UE that successfully detects the collision resolution message sends an acknowledgment (ACK) in HARQ (Hybrid Automatic Repeat reQuest) to the base station. As a result, the idle UE transitions to the RRC connection state.

[0070] On the other hand, a UE that fails to detect the collision resolution message determines that a collision has occurred, re-selects a preamble, and repeats the random access procedure of messages 1 to 4. When the base station detects that the collision has been resolved by an ACK from the UE, it sends a UL grant to that UE. The UE then sends UL data using the UL resources allocated by the UL grant.

[0071] In the random access method described above, a UE can autonomously initiate a random access procedure when it wishes to send UL data. Furthermore, since UL data is sent using UL resources specifically allocated to the UE by UL grants after UL synchronization is established, highly reliable UL transmission becomes possible.

[0072] A random access procedure that utilizes sending Msg. 1, receiving Msg. 2, sending Msg. 3, and receiving Msg. 4 is also called a four-step random access procedure, a four-step random access procedure, four-step RACH, or four-step random access (RA).

[0073] Furthermore, NR supports a two-step random access procedure. This two-step random access procedure is also called a two-step random access procedure, two-step RACH, or two-step RA.

[0074] The two-step RA may consist of a first step in which the UE transmits to the base station and a second step in which the base station transmits to the UE (see Figure 2).

[0075] For example, in the first step, at least one of a UL signal and a UL channel (hereinafter also referred to as UL signal / UL channel), which include a preamble and a message, may be transmitted from the UE to the base station. The preamble may be configured to play a similar role to message 1 (PRACH) in a four-step RA. The message may be configured to play a similar role to message 3 (PUSCH) in a four-step RA. The message transmitted in the first step may be called message A (Msg. A).

[0076] Furthermore, in the second step, at least one of the DL signal and DL channel (hereinafter also referred to as DL signal / DL channel), which includes a response and contention-resolution, may be transmitted from the base station to the UE. The response may be configured to perform a similar role to message 2 (random access response (RAR) transmitted in PDSCH) in the 4-step RA. The contention-resolution may be configured to perform a similar role to message 4 (PDSCH) in the 4-step RA. The message transmitted in the second step may be called message B (Msg. B).

[0077] Furthermore, UE may send ACK / NACK in response to Msg. B. This ACK / NACK may be called ACK / NACK(A / N) for Msg. B, Msg. B ACK / NACK(A / N), HARQ-ACK for Msg. B, Msg. B HARQ-ACK, etc.

[0078] (Cell-free) Existing wireless communication systems (e.g., 5G NR) employ a cellular system in which, in principle, one antenna / transmit / receive point (TRP) forms one cell. The area formed by such a cell is a fixed / static area.

[0079] Furthermore, existing wireless communication systems (e.g., Rel. 16 and later) have introduced Distributed Multi Input Multi Output (Distributed MIMO, e.g., multi-TRP using multiple TRPs) which forms a communication area by the coverage of multiple antennas / TRPs. Distributed MIMO allows for simultaneous communication using multiple antennas / TRPs, as well as communication using a single antenna / TRP.

[0080] By adopting distributed MIMO, a more favorable line-of-sight environment can be established, and MIMO performance can be improved.

[0081] Figures 3A and 3B are diagrams illustrating the overview of MIMO. Figure 3A shows an example of Co-located MIMO. In Co-located MIMO, one UE communicates with one antenna / TRP.

[0082] On the other hand, Figure 3B shows an example of distributed MIMO. In distributed MIMO, one UE communicates with multiple coordinated antennas / TRPs.

[0083] In future wireless communication systems (e.g., Rel. 20 and beyond), the introduction of self-free communication is being considered with the aim of further improving performance and energy efficiency through reducing interference between multiple antennas / TRPs, creating a line-of-sight environment that supports the use of high frequencies, improving the overall frequency utilization efficiency of the system, and applying equal and high-quality communication to each user.

[0084] Selfly may also be called selfly massive MIMO (mMIMO) or large-scale distributed MIMO (D-MIMO). Selfly uses coherent coordination of a large number of access points. Selfly may include at least one of the following: ultra-dense deployment, scalable cooperation, user-centric clustering, supercarrier aggregation, or analog fronthaul. The user plane for selfly may provide more flexible scheduling than existing scheduling. The control plane for selfly may retain several forms of cells to facilitate signaling.

[0085] In cell-free systems, unlike conventional cellular systems, a single area (which may also be called a cell or subcell) may be formed by multiple antennas / TRPs. In other words, this area may mean a cell that is independent of the position of the antennas / TRPs.

[0086] In self-free systems, the set of antennas / TRPs used for area formation may be changed according to the needs of the user audience (UE). For example, the set of antennas / TRPs may be changed based on factors other than antenna / TRP coverage, such as the number of UEs, traffic volume, or communication purpose (e.g., initial access, data communication, measurement, reporting, etc.).

[0087] In other words, in a self-free setup, coverage between multiple antennas / TRPs may overlap.

[0088] In a cell-free configuration, the direction in which each antenna / TRP transmits a synchronization signal (which may be called, for example, a synchronization signal block (SSB), a synchronization signal / physical broadcast channel (SS / PBCH) block, etc.) may be controlled.

[0089] Furthermore, in a self-free system, the central unit (CU) and distributed unit (DU) may be virtualized for each antenna. Alternatively, each antenna may be managed by the CU alone.

[0090] Figure 4A is a diagram illustrating the overview of the cellular system. Figure 4A shows the cells formed by each antenna / TRP, and the UE communicates based on these cells.

[0091] On the other hand, Figure 4B shows an overview of a cell-free system. In the example shown in Figure 4B, the installed antennas / TRPs do not form fixed / static cells in the cellular system. As shown in Figure 4B, in a cell-free system, one or more antennas / TRPs form areas depending on the conditions. Therefore, in a cell-free system, each antenna / TRP does not have to correspond to the same physical cell ID, and areas between multiple antennas / TRPs may overlap.

[0092] Self-reliance may be achieved, for example, by adjusting a set of antennas / TRPs controlled by a central control unit (e.g., a CU).

[0093] In a cell-free system, a first cell (which may be called, for example, a cell / supercell / macrocell / large cell) with a fixed physical range, similar to a cell in a 5G NR system, and a second cell (which may be called, for example, a subcell / area / microcell / cell / small cell / second cell within the first cell) whose physical range changes quasi-statically / dynamically based on conditions, may be formed.

[0094] For example, the first cell may be called a supercell to distinguish it from a second cell. If a supercell consists of multiple second cells, the second cells may have the same definition / operation / coverage as existing cells in the NR. For example, the second cells may be called subcells to distinguish them from the first cell. If a supercell or cell consists of multiple subcells, the subcells may have the same definition / operation / coverage as existing cells in the NR.

[0095] The first cell may be a cell newly defined in a future wireless communication system, or a cell definition from an existing wireless communication system may be reused.

[0096] The configurations of the first and second cells can be assumed to be as follows: Assumption 1: The first cell is composed of multiple TRPs, each having a single cell ID (physical cell ID (PCI)). Multiple TRPs can cooperate in sending and receiving data. Assumption 2: The first cell is composed of multiple TRPs (or subcells) with different cell IDs. Multiple TRPs / subcells can cooperate in sending and receiving data.

[0097] Figure 5A shows an example of the overview of hypothetical configuration 1 for cell-free operation. In the example shown in Figure 5A, each TRP included in the first cell (supercell / cell) has the same PCI (PCI #0). Multiple TRPs can communicate in cooperation with a single UE.

[0098] Figure 5B shows an example of an overview of hypothetical configuration 2 for cell-free operation. In the example shown in Figure 5B, each TRP included in the first cell (supercell / cell) has a different PCI (PCI #0 to #9). Multiple TRPs can communicate in cooperation with a single UE.

[0099] Figure 5C shows another example of the overview of assumption 2 of the cell-free configuration. In the example shown in Figure 5C, a PCI is assigned to each TRP contained in the first cell (supercell / cell). In the example shown in Figure 5C, unlike the example in Figure 5B, the same one PCI may correspond to multiple TRPs. Multiple TRPs can communicate in cooperation with a single UE.

[0100] Transmitting / receiving with TRP / subcell coordination may be based on at least one of the following methods supported in NR: - Single TRP / subcell transmission with dynamic TRP / subcell switching (single TRP transmission). - Joint transmission using multiple TRP / subcells (multi-TRP joint transmission). The joint transmission may be based on single DCI or multi-DCI. The joint transmission may be non-coherent joint transmission (NCJT) or coherent joint transmission (CJT).

[0101] Assuming an ideal backhaul and close coordination for self-free operation, CJT may be preferred over NCJT in a joint transmission scheme, and single DCI-based joint transmission may be preferred over multi-DCI-based joint transmission.

[0102] Selfly can enable large-scale distributed MIMO, low-layer (e.g., L2 / L1) mobility, and flexible TRP clustering. For example, when applied to ultra-high-density TRP, cell / TRP clustering for mobility / control and data can be separated.

[0103] Cell-free design offers several advantages, including: • Increased TRP density per cell. This improves the Signal-Noise Ratio (SNR) across all UEs, including conventional cell edge areas. • Flexible (e.g., UE-centric) TRP clustering for cell construction. This reduces the number of UEs affected by inter-cell / inter-TRP interference. • Enhanced mobility at lower layers. A single clustering can accommodate more TRPs, enabling seamless movement through, for example, L1-level operations.

[0104] With regard to self-free design, either Concept 1 or 2 below may be applied.

[0105] <Concept 1> Selfly targets the selection of multiple TRPs / access points (APs), and transmission / reception with TRPs / APs is limited to data only (e.g., PDSCH / PUSCH) (e.g., at the physical / MAC layer). In this case, there is no significant impact on cell selection, initial access, or mobility compared to existing methods. LTM (L1 / L2-triggered mobility, e.g., LTM prior to Rel. 18) may be reusable, or LTM functionality may be enhanced. L1 measurement / reporting or enhanced SRS transmission may be performed for the selection of multiple TRPs / APs, CSI measurement / reporting or enhanced SRS transmission for CSI of TRPs / APs with different clusterings, etc.

[0106] <Concept 2> The selection of multiple TRP / APs and transmission / reception with TRP / APs applies to both control channels / signals (e.g., in RRC) and data (e.g., PDSCH / PUSCH) (e.g., in the physical / MAC layer).

[0107] In this case, compared to existing methods, there are impacts on cell selection, initial access, and mobility, in addition to the measurement / reporting of L1 / CSI for data in Concept 1. For example, since the UE needs to access multiple TRP / APs during initial access, the SSB / SI / RACH also needs to be redesigned.

[0108] When clustering multiple TRP / APs for control channels / signals and data, the clustering method (e.g., TRP / APs within the cluster) may be the same or different. In this case, potential impacts may arise when clustering is performed on multiple DU / CUs located in geographically different locations.

[0109] <CC (Carrier Aggregation (CA) Scenarios) of Different Frequencies> Selfly may be applied to CC (CA scenarios) of different frequencies. The above multiple TRP / AP may be processed individually for each CC or jointly across multiple CCs. For example, clustering and scheduling may take into account both the dimensions of the TRP and the dimensions of the CC.

[0110] (Analysis) Future wireless communication systems (e.g., Rel. 21 and beyond, 6G systems) are expected to realize advanced services that go beyond 5G NR systems, such as those exemplified below, in order to solve social issues in the 2030s and beyond: • Scalable networks (NW). • Easy-to-operate NW. • Sustainable / resilient NW. • Improved performance (e.g., throughput / capacity) at lower bit costs. • Significant reduction in the cost / complexity / power consumption of cellular networks. • Increased revenue / creation of new value through cellular networks.

[0111] For scalable networks, it is desirable that the basic design of a 6G system be applicable not only to use cases within the 6G system but also to potential new use cases that may arise later. This is because it will be beneficial and practical for features that are expected to be released in the future.

[0112] For easily operable networks, it is desirable to avoid specifying multiple options for the same purpose.

[0113] For sustainable and fast-recovering networks, significant cost and energy consumption reductions are desirable for both the network side and the terminals (user terminals, user equipment (UE)). Furthermore, improved fault tolerance and rapid recovery capabilities against all kinds of events (e.g., operational errors, high traffic, disasters, etc.) are also desirable.

[0114] To realize these services, it is necessary to consider the regulations of the carriers through which UE / NW communicates, as well as the transmission / reception control of RS, but this consideration has not been sufficient. If this consideration is insufficient, there is a risk that advanced services beyond 5G NR will not be realized.

[0115] Therefore, the inventors conceived of RS transmission / reception control for future wireless communication systems. In this disclosure, the cell configuration may be the cell-free configuration described above, and is not limited thereto.

[0116] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.

[0117] (Various substitutions) In this disclosure, words enclosed in parentheses () may indicate an explanation of the preceding word (e.g., an explanation of spelling), a paraphrase, a specific example, or supplementary explanation. Also, in this disclosure, words enclosed in square brackets [] may be interpreted as part of the overall meaning of the text, or they may be interpreted as being excluded (ignored). Note that parentheses () and square brackets [] may be used for purposes / meanings other than those described above.

[0118] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0119] In this disclosure, terms such as notice, activate, deactivate, indicate (or specify), select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and capable of operating may be interpreted interchangeably.

[0120] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Elements (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0121] In this disclosure, the upper layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and other messages (e.g., messages from the core network, such as positioning protocol messages (e.g., NR Positioning Protocol A (NRPPPa) / LTE Positioning Protocol (LPP)) messages).

[0122] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0123] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

[0124] (Wireless communication method) <Embodiment 0> The UE may monitor multiple frequencies (for example, which may be called monitoring frequencies / synchronous rasters) to detect a first carrier (for example, which may be called a perch carrier).

[0125] If a first carrier is detected, the UE may perform a synchronous operation (which may be called a first synchronous operation) and receive / retrieve information (e.g., system information).

[0126] The UE may perform initial access / random access on a second carrier (which may be called an anchor carrier, for example) based on the received / acquired information (e.g., system information) and establish an RRC connection with the NW. At least a portion of the initial access / random access may be performed on the first carrier.

[0127] The UE may transmit / receive data on a third carrier (which may be called a data carrier, for example) that is set up by signals transmitted / received on a second carrier.

[0128] Please note that the names such as perch carrier, anchor carrier, and data carrier used in this disclosure are merely examples and are not limited to these names.

[0129] <<Monitoring Frequency / Synchronization Raster>> The monitoring frequency / synchronization raster may indicate the frequency position of the synchronization signal block (SSB) that the UE can use for system acquisition.

[0130] In existing NRs (e.g., up to Rel. 18), the frequency position (center frequency) of the synchronization signal block is expressed as N * 1200 kHz + M * 50 kHz (where N is an integer from 1 to 2499, and M is 1, 3, or 5) for frequencies from 0 to 3000 MHz (Frequency Range (FR) 1), and as 3000 MHz + N * 1.44 MHz (where N is an integer from 0 to 14756) for frequencies above 3000 MHz (FR 2).

[0131] Furthermore, during initial access to an existing NR, the order in which the UE searches for synchronized rasters depends on the UE implementation. For efficient searching, a Global Synchronization Channel Number (GSCN) is defined, and the GSCN range is notified to the UE. This GSCN is represented as 3N + (M - 3) / 2 in FR1 and as 7499 + N in FR2.

[0132] In this disclosure, the number of monitoring frequency / synchronous rasters may be more limited (e.g., smaller) than the number of monitoring frequency / synchronous rasters in existing NRs. In other words, the frequency spacing of the monitoring frequency / synchronous rasters may be wider than in existing NRs.

[0133] For example, the location of a synchronization raster may be defined based on its relationship to information related to a frequency band (e.g., a frequency band index). The UE may monitor or search for the location of a synchronization raster associated with a frequency band index. Alternatively, the UE may assume that the location of a synchronization raster is associated with a frequency band index, and may monitor or search for the synchronization raster based on that assumption.

[0134] For example, the bandwidth in which a GSCN or synchronous raster is defined may be limited. A UE may monitor or search for the bandwidth in which a GSCN or synchronous raster is defined among the bandwidths supported by the UE. Alternatively, a UE may assume that a GSCN or synchronous raster is defined in only a specific bandwidth among the bandwidths supported by the UE, and may monitor or search for a GSCN or synchronous raster based on that assumption.

[0135] For example, in a given bandwidth, a GSCN or synchronous raster may be defined only at specific frequency positions. For example, in a given bandwidth, a GSCN or synchronous raster may be defined within X Hz (where X is any number) from the lower limit of that bandwidth. A UE may monitor or search for a GSCN or synchronous raster in each of the bandwidths it supports, only at the specific frequency positions where such a GSCN or synchronous raster is defined. Alternatively, a UE may assume that a GSCN or synchronous raster is defined only at specific frequency positions in a given bandwidth, and may monitor or search for a GSCN or synchronous raster based on that assumption.

[0136] This allows for an extension of the time required for cell search per frequency (i.e., the period of the synchronization signal block per frequency), thereby reducing network energy consumption and shortening the time required for initial access.

[0137] The monitoring frequency resources detected by the UE may correspond to potential perch carriers (first carriers).

[0138] <<Perch Carrier>> The first carrier may be a carrier common to multiple UEs.

[0139] The first carrier could be a common carrier regardless of the use case / service / device type, for example.

[0140] In the first carrier, common signals (e.g., synchronization signal blocks / master information blocks / system information blocks) may be transmitted. Furthermore, the transmission and reception of data (e.g., application layer information) is not assumed in the first carrier. Also, the transmission and reception of information relating to a specific UE or a specific group of UEs (e.g., information other than that relating to the second carrier) is not assumed in the first carrier.

[0141] The first carrier (and the signal transmitted in it) may always be kept in the ON state.

[0142] Signals transmitted on the first carrier (e.g., synchronization signal blocks / master information blocks / system information blocks) may include information about an anchor carrier (second carrier) that is available in the system or used by the UE.

[0143] The first carrier may have a frequency lower than a specific value (for example, 800 MHz).

[0144] The first carrier may correspond to a single (base station) beam.

[0145] The UE may perform a first synchronization in the first carrier. The first synchronization may mean a first step / level (e.g., coarse) synchronization among multiple (e.g., two) step / level synchronizations.

[0146] The first carrier may, for example, be included in a coverage band.

[0147] By defining and utilizing the first carrier in this way, it is possible to cover all future use cases and contribute to achieving a scalable network.

[0148] <<Anchor Carrier>> The second carrier may be a carrier / frequency used for network connection / control.

[0149] The second carrier may be an individual carrier for each UE, for multiple UEs (UE groups), for each use case, or for each service. A UE may determine which second carrier is compatible with its device based on information obtained from the first carrier.

[0150] In the second carrier, at least one of the following transmissions / receptions / operations may occur: - Transmission / reception of a system information block for a specific use case (e.g., enhanced Mobile Broadband (eMBB)); - Connection establishment; - Transmission / reception of a wake-up signal (WUS); - Wake-up receiver (WUR) operation; - Second synchronization; - Information about the third carrier.

[0151] The terms "Wake-up signal (WUS)" and "Wake-up receiver" may be interpreted as "Low-power wake-up signal (LP-WUS)" and "Low-power wake-up receiver (LP-WUR)."

[0152] By using a second carrier to perform LP-WUS / WUR related operations, it is possible to reduce network energy consumption and user energy consumption.

[0153] The second carrier (and the signals transmitted on it) does not have to be always on (it may be in a dormant state). For example, the transmission of signals on the second carrier (DL transmission / UL transmission) may be supported to be performed on demand in response to a wake-up signal / trigger signal.

[0154] The second synchronization may refer to the second step / level (e.g., a more precise) synchronization among multiple (e.g., two) step / level synchronizations. For example, a UE may achieve the first synchronization on the first carrier and the second synchronization on the second carrier.

[0155] The second carrier may be included in the first carrier in certain cases (for example, in the case of a [narrowband] IoT device). Alternatively, the second carrier may be configured as a carrier that overlaps the same frequency band as the first carrier.

[0156] The second carrier may, for example, be included in a coverage band.

[0157] At least one operation performed on the second carrier may also be performed on the first / third carrier. Furthermore, at least one operation performed on the first / third carrier may also be performed on the second carrier.

[0158] <<Data Carrier>> The third carrier may be a carrier used for transmitting / receiving data.

[0159] The third carrier could be an individual carrier for each UE, for multiple UEs (UE groups), for each use case, or for each service.

[0160] The third carrier (and the signals transmitted on it) does not have to be always on (it may be in a dormant state). For example, the transmission of signals on the third carrier (DL transmission / UL transmission) may be supported to be performed on demand in response to a wake-up signal / trigger signal.

[0161] The third carrier may be included in both the coverage band and the capacity band, for example. The third carrier within the capacity band may be used as a surplus carrier.

[0162] The third career may include the first / second career.

[0163] UE / NW may use the first carrier as a third carrier only in specific cases. Such specific cases may be, for example, at least one of (re-)initial access, fallback cases, and mobility on the second carrier.

[0164] UE may use / monitor the first carrier as a third carrier. Also, U may use / monitor the first carrier as a third carrier in the case of mobility on the first carrier.

[0165] The first, second, and third carriers corresponding to terrestrial networks (TN) and the first, second, and third carriers corresponding to non-terrestrial networks (NTN) may be defined separately or in common.

[0166] Furthermore, certain devices (for example, devices that do not perform cell search / RRC connectivity (e.g., Ambient IoT (A-IoT))) do not need to use a second carrier.

[0167] Figure 6 shows an example of carrier design in this disclosure. Figure 6 shows a low-frequency band (coverage band) and a high-frequency band (capacity band). In the example shown in Figure 6, after the UE is powered on, the UE performs a cell search using the monitoring frequency. Next, the monitoring frequency resource detected by the UE becomes the perch carrier (first carrier), and the perch carrier receives information about the anchor carrier (second carrier). The UE performs initial access (IA) using at least one of the perch carrier and the anchor carrier. From the cell search to the completion of IA, the UE is in idle mode.

[0168] After initial access is complete, the UE enters RRC connection (CONNECTED) mode. The UE receives information about the data carrier (third carrier) on the anchor carrier. The UE performs additional synchronization on the anchor carrier. The UE transmits / receives data on the data carrier for a specific use case (e.g., eMBB / other purposes).

[0169] In the example shown in Figure 6, if the UE returns to idle mode / inactive mode, RRC reconnection may be performed using LP-WUS / WUR and at least one of mobility operations.

[0170] In the example shown in Figure 6, carriers other than the perch carrier may be on-demand carriers (i.e., carriers that are not always on) from the viewpoint of reducing network energy. For example, on-demand transmission / setting, where transmission is controlled based on a wake-up signal / trigger signal, may be supported for at least one of the second carrier (anchor carrier) and the third carrier (data carrier), while on-demand transmission / setting may not be supported for the first carrier (perch carrier).

[0171] As an example, the UE may transmit a wake-up / trigger signal based on information about a second carrier received on the first carrier, and receive a signal transmitted on the second carrier in response to the wake-up / trigger signal. As another example, the UE may transmit a wake-up / trigger signal based on information about a third carrier received on the second carrier, and receive a signal transmitted on the third carrier in response to the wake-up / trigger signal.

[0172] In the example shown in Figure 6, the UE may obtain a first synchronization (or information regarding the first synchronization) on the first carrier and a second synchronization (or information regarding the second synchronization) on the second carrier. In this case, the UE may perform transmission and reception on the first carrier (or transmission and reception on the first carrier and transmission and reception on a portion of the second carrier) based on the first synchronization, and perform transmission and reception on the second and third carriers (or transmission and reception on a portion of the second carrier and transmission and reception on the third carrier) based on the second synchronization.

[0173] <<Modification of Embodiment 0>> The UE may assume that if it enters idle mode / inactive mode again after RRC connection, it will use the previous first / second carrier.

[0174] Furthermore, if the UE enters idle / inactive mode again after RRC connection, it may be assumed that synchronization on the previous first / second carrier has been completed.

[0175] The carrier design of this disclosure may be applied to a cell-free configuration as appropriate. For example, the first carrier in this disclosure may correspond to a first cell (e.g., a supercell) or a second cell (e.g., an area). Also, for example, the second carrier in this disclosure may correspond to a first cell (e.g., a supercell) or a second cell (e.g., an area). Also, for example, the third carrier in this disclosure may correspond to a second cell (e.g., an area).

[0176] <Analysis 1> In existing systems (e.g., NR), SSB must be transmitted / received on the carrier to which the UE attempts initial access. Additionally, TRS / CSI-RS (QCL type A source RS for PDCCH / PDSCH) must be transmitted / received on all carriers to which PDCCH / PDSCH is transmitted / received. Furthermore, different periodic RS (QCL type D source RS) must be transmitted for different transmit (Tx) / receive (Rx) beams.

[0177] On the other hand, in future wireless communication systems (e.g., 6G), periodic RS may not be transmitted or received in at least some (some) of the carriers in which PDCCH / PDSCH / PUCCH / PUSCH is transmitted or received. For example, in the carriers in which PDCCH / PDSCH / PUCCH / PUSCH is transmitted or received, there may be carriers in which periodic RS is not supported.

[0178] Periodic RS may be transmitted / received on a specific carrier. The specific carrier may be at least one of the first carrier, the second carrier, and the third carrier. Alternatively, the specific carrier may be defined by the specification.

[0179] In this disclosure, the terms carrier, component carrier (CC), bandwidth portion (BWP), band, [frequency] band, etc., may be interpreted interchangeably.

[0180] In this disclosure, a single carrier (CC) may be a single frequency band (see Figure 7A), a set of continuous frequency bands (see Figure 7B), or a set of discontinuous frequency bands (see Figure 7C).

[0181] In this disclosure, the following terms may be defined as follows: • RS#1: The RS used for initial access. • RS#2: The RS used as the QCL source RS for a specific DL signal / channel. • RS#3: The RS used for a specific purpose different from RS#2.

[0182] For example, RS#1 may be an SSB in an existing system. Alternatively, RS#1 may be a signal for initial access that is newly defined in a future wireless communication system (for example, a signal having a similar configuration / role to an SSB in an existing system).

[0183] For example, RS#2 may be a CSI-RS / TRS used as the QCL source RS for PDCCH / PDSCH in an existing system. Alternatively, RS#2 may be a signal used as the QCL source RS for a specific DL signal / channel, newly defined in a future wireless communication system.

[0184] For example, RS#3 may be CSI-RS (or a signal with a similar configuration / role) used in existing systems for CSI measurement / mobility / RRM. Alternatively, RS#3 may be a signal newly defined in future wireless communication systems for a specific purpose different from RS#2.

[0185] In this disclosure, RS[#X] may be at least one of the following RSs. Note that RS[#X] may be RS#1, RS#2, or RS#3. ・P-RS[#X]: Periodic RS[#X]. ・A-RS[#X]: Aperiodic RS[#X]. ・SP-RS[#X]: Semi-persistent RS[#X].

[0186] In this disclosure, the QCL relationship / QCL information between A (QCL source RS) and B (target RS) (for example, that A and B are QCLs [for a specific QCL type / QCL parameter], and that B is QCL with A [for a specific QCL type / QCL parameter]) may be defined by the specification or may be set / instructed / notified to the UE by specific higher-layer signaling (for example, higher-layer signaling indicating a TCI state).

[0187] In this disclosure, a higher-layer signaling (e.g., TCI-State) indicating a TCI state may include one or more QCL information. Each of the one or more QCL information may include information indicating one or more cells / BWPs and information indicating one or more QCL types / QCL parameters.

[0188] In this disclosure, the QCL source RS and target RS may be transmitted / received on the same carrier or on different carriers.

[0189] <Embodiment 1> Embodiment 1 relates to the QCL relationship between RS#1 and RS#2 / RS#3.

[0190] P-RS#1 may be transmitted / received on the first carrier.

[0191] P-RS#2 / P-RS#3 may conform to at least one of the following options A1 to A3.

[0192] Option A1: P-RS#2 / P-RS#3 may always be transmitted / received on the first carrier. In other words, P-RS#2 / P-RS#3 may be transmitted / received only on the first carrier and not on the second / third carriers.

[0193] Option A2: P-RS#2 / P-RS#3 may be transmitted / received on the first carrier (depending on the base station settings). In other words, P-RS#2 / P-RS#3 may be transmitted / received on the first carrier, or on the second / third carrier.

[0194] Option A3: P-RS#2 / P-RS#3 does not necessarily have to be transmitted / received on the first carrier. In other words, P-RS#2 / P-RS#3 may be transmitted / received only on the second / third carrier, and may not be transmitted / received on the first carrier.

[0195] If P-RS#2 / P-RS#3 is not transmitted / received on the first carrier, RS#2 / RS#3 may comply with at least one of the following options B1 and B2.

[0196] Option B1: A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 may be transmitted / received on the first carrier.

[0197] Option B2: P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 may be transmitted / received on other carriers (e.g., a second carrier / a third carrier).

[0198] RS#2 / RS#3 may have RS#1 on the same carrier as the QCL source RS. The UE may assume that RS#2 / RS#3 is a QCL with respect to RS#1 on the same carrier and a specific QCL type / QCL parameter.

[0199] For example, in option B1, A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 on the first carrier may have P-RS#1 within the same carrier (in this case, the first carrier) as the QCL source RS (see Figure 8). The UE may assume that A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 on the first carrier are QCLs with respect to P-RS#1 within the same carrier (in this case, the first carrier) and specific QCL types / QCL parameters.

[0200] In Option B2, a constraint may or may not be imposed that P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 are not transmitted / received on the first carrier. If such a constraint is imposed, the UE does not need to expect to receive P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 on the first carrier.

[0201] RS#2 / RS#3 within a carrier may have RS#1 in a different carrier from the one on which RS#2 / RS#3 is transmitted / received as a QCL source RS. The UE may assume that RS#2 / RS#3 within a carrier is a QCL with respect to a specific QCL type / QCL parameter with respect to RS#1 in a different carrier from the one on which RS#2 / RS#3 is transmitted / received.

[0202] For example, in option B2, P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 on a certain carrier (e.g., a second carrier / a third carrier) may have P-RS#1 in a different carrier (e.g., a first carrier) as the QCL source RS (see Figure 9). The UE may assume that P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 on a certain carrier (e.g., a second carrier / a third carrier) is a QCL with respect to P-RS#1 in a different carrier (e.g., a first carrier) and a specific QCL type / QCL parameter.

[0203] According to Embodiment 1 described above, the UE can appropriately receive RS#2 / RS#3 based on the QCL relationship between RS#1 and RS#2 / RS#3.

[0204] <Analysis 2> In existing systems (e.g., NR), P-RS (e.g., P-RS#1 / P-RS#2) must be transmitted on all carriers (see Figure 10).

[0205] On the other hand, future wireless communication systems (e.g., 6G) may support cases where P-RS is not transmitted in some carriers / bands (see Figure 11).

[0206] Here, it is considered necessary for the UE to monitor / receive at least one P-RS on at least one carrier for purposes such as time / frequency tracking, Doppler estimation, and delay estimation.

[0207] To enable the UE to properly perform time / frequency tracking, Doppler estimation, delay estimation, etc., constraints may be imposed on cases where P-RS is not transmitted. The constraints may be at least one of the following: • P-RS is transmitted on at least one carrier with a bandwidth M (Hz). This constraint may be applied per band / per frequency range. • The [maximum] (frequency direction) difference between the PDCCH / PDSCH and the P-RS that is the QCL source (e.g., P-RS #2) is less than a certain value (e.g., N (Hz)) (below a certain frequency).

[0208] <Embodiment 2> Embodiment 2 relates to RS / channel reception control.

[0209] <<Embodiment 2.1>> The UE does not need to monitor the first carrier after the initial access / RRC connection.

[0210] P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) may be transmitted / received on a carrier different from the first carrier (e.g., a second carrier / a third carrier).

[0211] P-RSs (e.g., P-RS#1 / P-RS#2 / P-RS#3) in a carrier different from the first carrier (e.g., a second carrier / a third carrier) may or may not have P-RSs (e.g., P-RS#1) in the first carrier as QCL source RSs. The UE may or may not assume that P-RSs (e.g., P-RS#1 / P-RS#2 / P-RS#3) in a carrier different from the first carrier (e.g., a second carrier / a third carrier) are QCLs with respect to P-RSs (e.g., P-RS#1) in the first carrier and certain QCL types / QCL parameters.

[0212] The UE may conform to at least one of the following options C1 and C2.

[0213] Option C1: The UE does not need to monitor the second carrier after the initial access / RRC connection (it may stop monitoring).

[0214] In option C1, P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) may be transmitted / received on a carrier different from the first / second carrier (e.g., a third carrier).

[0215] In option C1, P-RSs (e.g., P-RS#1 / P-RS#2 / P-RS#3) in a carrier different from the second carrier (e.g., a third carrier) may or may not have P-RSs (e.g., P-RS#1) in the first carrier as QCL source RSs. The UE may or may not assume that P-RSs (e.g., P-RS#1 / P-RS#2 / P-RS#3) in a carrier different from the second carrier (e.g., a third carrier) are QCLs with respect to P-RSs (e.g., P-RS#1) in the first carrier and certain QCL types / QCL parameters.

[0216] Option C2: The UE may monitor (or continue to monitor) the second carrier after the initial access / RRC connection.

[0217] In option C2, P-RS may be transmitted / received on the second carrier. P-RS on the second carrier may be used for beam fault detection (BFD), radio resource management (RRM), time / frequency tracking, Doppler estimation, delay estimation, etc.

[0218] Option C2 may further conform to at least one of options C2-1 and C2-2.

[0219] Option C2-1: P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) does not need to be transmitted / received on a carrier different from the second carrier (e.g., a third carrier).

[0220] In option C2-1, A-RS / SP-RS (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) may be transmitted / received on a carrier different from the second carrier (e.g., a third carrier).

[0221] In option C2-1, an A-RS / SP-RS (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) in a carrier different from the second carrier (e.g., a third carrier) may have a P-RS (e.g., P-RS#2 / P-RS#3) in the second carrier as a QCL source RS. The UE may assume that an A-RS / SP-RS (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) in a carrier different from the second carrier (e.g., a third carrier) is a QCL with respect to a P-RS (e.g., P-RS#2 / P-RS#3) in the second carrier and a specific QCL type / QCL parameter.

[0222] In option C2-1, the P-RS in the second carrier (e.g., P-RS#2 / P-RS#3) may have the P-RS in the first carrier (e.g., P-RS#1) as the QCL source RS. The UE may assume that the P-RS in the second carrier (e.g., P-RS#2 / P-RS#3) is a QCL with respect to the P-RS in the first carrier (e.g., P-RS#1) and a particular QCL type / QCL parameter.

[0223] Option C2-2: P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) may also be transmitted / received on a carrier different from the second carrier (e.g., a third carrier).

[0224] In option C2-2, a P-RS / A-RS / SP-RS (e.g., P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) in a carrier different from the second carrier (e.g., a third carrier) may have a P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) in the same carrier from which the P-RS / A-RS / SP-RS is transmitted / received as a QCL source RS. The UE may assume that a P-RS / A-RS / SP-RS (e.g., P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) on a carrier different from the second carrier (e.g., a third carrier) is a QCL with respect to a specific QCL type / QCL parameter with respect to a P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) on the same carrier from which that P-RS / A-RS / SP-RS is transmitted / received.

[0225] In option C2-2, a P-RS / A-RS / SP-RS (e.g., P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) in a carrier different from the second carrier (e.g., a third carrier) may have a P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) in a carrier different from the carrier on which the P-RS / A-RS / SP-RS is transmitted / received (e.g., the first carrier / second carrier, another third carrier) as a QCL source RS. The UE may assume that a P-RS / A-RS / SP-RS (e.g., P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) on a carrier different from the second carrier (e.g., a third carrier) is a QCL with respect to a specific QCL type / QCL parameter with respect to a P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) on a carrier different from the carrier on which that P-RS / A-RS / SP-RS is transmitted / received (e.g., the first carrier / second carrier, another third carrier).

[0226] <<Embodiment 2.2>> The UE may monitor (and continue to monitor) the first carrier after the initial access / RRC connection.

[0227] P-RS may be transmitted / received on the first carrier. P-RS on the first carrier may be used for BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.

[0228] A UE with specific capabilities may receive / measure the P-RS on the first carrier. A UE with specific capabilities (hereinafter also referred to as the first UE) may receive signals / channels on the first carrier / other carriers (e.g., a third carrier). The specific capabilities may include the ability to monitor multiple carriers and at least one wideband. In this disclosure, the terms UE with specific capabilities, high-end UE, wideband-supporting terminal, wideband terminal, eMBB terminal, first UE, UE, etc., may be interpreted interchangeably.

[0229] A UE that supports only a certain number of carriers or a certain bandwidth or less (hereinafter also referred to as a second UE) may be a UE that does not have the above-mentioned specific capabilities. In this disclosure, the terms UE that does not have specific capabilities, low-end UE, terminal that does not support broadband, terminal that supports only narrowband, narrowband terminal, URLLC (Ultra Reliable and Low Latency Communications) terminal, IoT terminal, second UE, UE, etc., may be interpreted interchangeably.

[0230] For the first UE, at least one of the following options D1 and D2 may be applied. For the second UE, options D1 / D2 may or may not be applied.

[0231] <<<Option D1>>> P-RS does not need to be transmitted to the first UE on the first carrier and other carriers (e.g., the third carrier) (it is sufficient if P-RS is transmitted on the first carrier or other carriers). Therefore, P-RS (e.g., P-RS#2 / P-RS#3) does not need to be transmitted on the third carrier. In this case, the RS overhead on the third carrier can be reduced.

[0232] An A-RS / SP-RS (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) in a first carrier / other carrier (e.g., a third carrier) may have a P-RS (e.g., P-RS#1) in the first carrier as a QCL source RS. The UE may assume that an A-RS / SP-RS (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) in a first carrier / other carrier (e.g., a third carrier) is a QCL with respect to a P-RS (e.g., P-RS#1) in the first carrier and a particular QCL type / QCL parameter.

[0233] An A-RS / SP-RS (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) in another carrier (e.g., a third carrier) may have a P-RS (e.g., P-RS#2 / P-RS#3) in a different carrier (e.g., a second carrier) as a QCL source RS. The UE may assume that an A-RS / SP-RS (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) in another carrier (e.g., a third carrier) is a QCL with respect to a specific QCL type / QCL parameter and a P-RS (e.g., P-RS#2 / P-RS#3) in a different carrier (e.g., a second carrier).

[0234] In option D1, a P-RS (e.g., P-RS#2 / P-RS#3) in a carrier different from the first carrier (e.g., a second carrier) may have a P-RS (e.g., P-RS#1) in the first carrier as a QCL source RS. The UE may assume that a P-RS (e.g., P-RS#2 / P-RS#3) in a carrier different from the first carrier (e.g., a second carrier) is a QCL with respect to a specific QCL type / QCL parameter and a P-RS (e.g., P-RS#1) in the first carrier.

[0235] <<<Option D2>>> P-RS may be transmitted on both the first carrier and other carriers (e.g., second carrier / third carrier). In this case, the operation / processing of the UE can be simplified.

[0236] An A-RS / SP-RS (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) in a first carrier / other carrier (e.g., a third carrier) may have a P-RS (e.g., P-RS#1) in the first carrier as a QCL source RS. The UE may assume that an A-RS / SP-RS (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) in a first carrier / other carrier (e.g., a third carrier) is a QCL with respect to a P-RS (e.g., P-RS#1) in the first carrier and a particular QCL type / QCL parameter.

[0237] P-RSs in the first / second / third carrier (e.g., P-RS#2 / P-RS#3) may have a different P-RS in the same carrier (e.g., P-RS#1) as a QCL source RS. The UE may assume that the P-RSs in the first / second / third carrier (e.g., P-RS#2 / P-RS#3) are QCLs with respect to a particular QCL type / QCL parameter and a different P-RS in the same carrier (e.g., P-RS#1).

[0238] A P-RS in the second / third carrier (e.g., P-RS#2 / P-RS#3) may have a P-RS in a different carrier (e.g., the first carrier) (e.g., P-RS#1) as a QCL source RS. The UE may assume that the P-RS in the second / third carrier (e.g., P-RS#2 / P-RS#3) is a QCL with respect to a specific QCL type / QCL parameter and the P-RS in the different carrier (e.g., P-RS#1).

[0239] A-RS / SP-RS (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) in the first / second / third carrier may have P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) in the same carrier as QCL source RS. The UE may assume that A-RS / SP-RS (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) in the first / second / third carrier is a QCL with respect to a specific QCL type / QCL parameter and a P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) in the same carrier.

[0240] A-RS / SP-RS (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) in the first / second / third carrier may have P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) in different carriers as QCL source RS. The UE may assume that A-RS / SP-RS (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) in the first / second / third carrier is a QCL with respect to a specific QCL type / QCL parameter and a P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) in different carriers.

[0241] <<<Supplement to Option D2>>> The first UE / second UE may assume / expect that P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) exists on the first carrier / other carrier (e.g., third carrier) set up for the second UE. In this case, the UE may stop / cancele monitoring of the first carrier after initial access / RRC connection.

[0242] <<Embodiment 2.3>> The UE may follow at least one of the following receiving controls A1 to A4. Note that the individual controls / operations described in receiving controls A1 to A4 may be combined as appropriate.

[0243] The following reception controls A1 to A4 are preferably applied when the band on which P-RS is transmitted and the band on which PDCCH / PDSCH is transmitted in the carrier monitored by the UE are the same, but they may also be applied when these bands are different.

[0244] <<<Receive control A1>>> The UE may monitor the first carrier, at least one of the second carrier, and the third carrier at all times (or after initial access is complete (during RRC connection mode)).

[0245] For example, in Figure 12, the UE monitors the first carrier and the third carrier after the initial access is completed (while in RRC connection mode).

[0246] The UE may use the P-RS transmitted on the first / second carrier to perform at least one of the following: BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.

[0247] For example, in Figure 12, the UE uses the P-RS#1 transmitted on the first carrier to perform at least one of the following: BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.

[0248] The UE may receive A-RS / SP-RS on the third carrier. The A-RS / SP-RS on the third carrier may be QCL'd with respect to specific QCL types / QCL parameters with respect to P-RS on the first / second carrier.

[0249] For example, in Figure 12, the UE receives A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 on the third carrier. A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 on the third carrier is a QCL for P-RS#1 on the first carrier and a specific QCL type / QCL parameter.

[0250] The UE may receive a PDCCH / PDSCH on the third carrier based on at least one of the P-RS on the first / second carrier and the A-RS / SP-RS on the third carrier. The PDCCH / PDSCH [DMRS [port]] on the third carrier may also QCL for the A-RS / SP-RS on the third carrier and a specific QCL type / QCL parameter.

[0251] For example, in Figure 12, the UE receives PDCCH / PDSCH on the third carrier based on A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 on the third carrier. PDCCH / PDSCH [DMRS [port]] on the third carrier is QCL for A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 and specific QCL type / QCL parameters on the third carrier.

[0252] Receiving control A1 is preferably applied to high-end UEs, but may also be applied to low-end UEs.

[0253] According to the reception control A1, the UE can properly receive the RS / channel using at least one of the first carrier and the second carrier, and the third carrier.

[0254] <<<Receive Control A2>>> The UE may not monitor the first carrier after the initial access is complete (while in RRC connection mode), but instead monitor the second / third carrier.

[0255] For example, in Figure 13, the UE does not monitor the first carrier after the initial access is complete (while in RRC connection mode), but instead monitors the third carrier.

[0256] The UE may receive a P-RS on a second / third carrier. The P-RS on the second / third carrier may be QCL'd with the P-RS on the first carrier for a specific QCL type / QCL parameter. In this case, the P-RS on the first carrier may be the P-RS received in the initial access procedure (e.g., the latest / last P-RS received in the initial access procedure).

[0257] The UE may use the P-RS transmitted on the second / third carrier to perform at least one of the following: BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.

[0258] For example, in Figure 13, the UE uses P-RS#1 / P-RS#2 / P-RS#3 transmitted on the third carrier to perform at least one of the following: BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.

[0259] The UE may receive a PDCCH / PDSCH on the third carrier based on the P-RS on the second / third carrier. The PDCCH / PDSCH [DMRS [port]] on the third carrier may QCL for the P-RS on the second / third carrier and a specific QCL type / QCL parameter.

[0260] For example, in Figure 13, the UE receives PDCCH / PDSCH on the third carrier based on P-RS#1 / P-RS#2 / P-RS#3 on the third carrier. PDCCH / PDSCH [DMRS [port]] on the third carrier is QCL for P-RS#1 / P-RS#2 / P-RS#3 on the third carrier and specific QCL type / QCL parameters.

[0261] Receiving control A2 is preferably applied to low-end UEs, but may also be applied to high-end UEs.

[0262] According to receive control A2, the UE can properly receive RS / channel using the second / third carrier. Furthermore, since it is no longer necessary to monitor the first channel after initial access is complete (during RRC connection mode), the monitoring load on the UE can be reduced.

[0263] <<<Receive Control A3>>> If P-RS is transmitted on the first carrier and also on the second / third carrier, the UE may not monitor the first carrier after the initial access is complete (while in RRC connection mode) and instead monitor the second / third carrier. In other words, after the initial access is complete (while in RRC connection mode), the UE may prioritize receiving / monitoring the P-RS on the second / third carrier over the P-RS on the first carrier.

[0264] For example, in Figure 14, P-RS#1 is transmitted on the first carrier, and P-RS#1 / P-RS#2 / P-RS#3 are transmitted on the second carrier. In this case, the UE does not monitor the first carrier after the initial access is complete (while in RRC connection mode), but monitors the second carrier. In other words, after the initial access is complete (while in RRC connection mode), the UE prioritizes receiving / monitoring P-RS#1 / P-RS#2 / P-RS#3 on the second carrier over P-RS#1 on the first carrier.

[0265] The P-RS on the second / third carrier may be QCL with respect to a specific QCL type / QCL parameter compared to the P-RS on the first carrier. In this case, the P-RS on the first carrier may be the P-RS received in the initial access procedure (e.g., the latest / last P-RS received in the initial access procedure).

[0266] The UE may use the P-RS transmitted on the second / third carrier to perform at least one of the following: BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.

[0267] For example, in Figure 14, the UE uses P-RS#1 / P-RS#2 / P-RS#3 transmitted on the second carrier to perform at least one of the following: BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.

[0268] The UE may receive A-RS / SP-RS on the third carrier. The A-RS / SP-RS on the third carrier may be QCL'd with respect to specific QCL types / QCL parameters with respect to P-RS on the second / third carrier.

[0269] For example, in Figure 14, the UE receives A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 on the third carrier. A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 on the third carrier is a QCL with respect to specific QCL type / QCL parameters with respect to P-RS#1 / P-RS#2 / P-RS#3 on the second carrier.

[0270] The UE may receive a PDCCH / PDSCH on the third carrier based on at least one of the P-RS on the second / third carrier and the A-RS / SP-RS on the third carrier. The PDCCH / PDSCH [DMRS [port]] on the third carrier may also QCL for the A-RS / SP-RS on the third carrier and a specific QCL type / QCL parameter.

[0271] For example, in Figure 14, the UE receives PDCCH / PDSCH on the third carrier based on A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 on the third carrier. PDCCH / PDSCH [DMRS [port]] on the third carrier is QCL for A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 and specific QCL type / QCL parameters on the third carrier.

[0272] Furthermore, if P-RS is transmitted on the first, second, and third carriers, the UE may monitor only the third carrier and not the first and second carriers after the initial access is complete (while in RRC connection mode). In other words, after the initial access is complete (while in RRC connection mode), the UE may prioritize receiving / monitoring the P-RS on the third carrier among the P-RS on the first, second, and third carriers.

[0273] Receiving control A3 is preferably applied to high-end UEs, but may also be applied to low-end UEs.

[0274] According to receive control A3, the UE can properly receive RS / channels using the second / third carrier. Furthermore, since it is no longer necessary to monitor the first / second channel after initial access is complete (during RRC connection mode), the monitoring load on the UE can be reduced.

[0275] <<<Receive Control A4>>> The UE may monitor the third carrier instead of the first and second carriers after the initial access is complete (while in RRC connection mode).

[0276] The UE may receive a P-RS on a third carrier. The P-RS on the third carrier may be QCL'd with the P-RS on the first carrier for a specific QCL type / QCL parameter. In this case, the P-RS on the first carrier may be the P-RS received in the initial access procedure (e.g., the latest / last P-RS received in the initial access procedure).

[0277] The UE may use the P-RS transmitted on the third carrier to perform at least one of the following: BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.

[0278] For example, in Figure 15, at least one of the following is performed using P-RS#1 / P-RS#2 / P-RS#3 transmitted on the third carrier: BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.

[0279] The UE may receive PDCCH / PDSCH on the third carrier based on the P-RS on the third carrier. The PDCCH / PDSCH [DMRS [port]] on the third carrier may QCL for the P-RS on the third carrier and specific QCL type / QCL parameters.

[0280] For example, in Figure 15, the UE receives PDCCH / PDSCH on the third carrier based on P-RS#1 / P-RS#2 / P-RS#3 on the third carrier. PDCCH / PDSCH [DMRS [port]] on the third carrier is QCL for P-RS#1 / P-RS#2 / P-RS#3 on the third carrier and a specific QCL type / QCL parameter.

[0281] Receiving control A4 is preferably applied to low-end UEs, but may also be applied to high-end UEs.

[0282] According to reception control A4, the UE can properly receive RS / channel using a third carrier. Furthermore, since it is no longer necessary to monitor the first and second channels after initial access is complete (during RRC connection mode), the monitoring load on the UE can be reduced.

[0283] <<Embodiment 2.4>> Depending on the capabilities of the UE, the carrier / bandwidth used for transmitting / receiving RS / channels may be determined.

[0284] A first UE (e.g., a high-end UE) may receive RS / channels using a low-frequency band (e.g., a coverage band) and a high-frequency band (e.g., a capacity band).

[0285] A second UE (e.g., a low-end UE) may receive RS / channels without using high-frequency bands (e.g., capacity bands). In other words, the second UE may receive RS / channels using only low-frequency bands (e.g., coverage bands).

[0286] In the high-frequency band, P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) does not need to be transmitted.

[0287] In the low-frequency band, P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) may be transmitted.

[0288] Figure 16 shows an example of a carrier / bandwidth used for transmitting / receiving RS / channels. The first and second UEs may use bandwidth F0 for initial access (and may monitor bandwidth F0). The first UE may use bandwidth F1 for receiving data (channels) and at least one A-RS / SP-RS (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) (and may monitor bandwidth F1). The second UE may use bandwidth F2 for receiving data (channels) and at least one P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) (and may monitor bandwidth F2).

[0289] The first UE may monitor multiple carriers (or more than a certain number of carriers).

[0290] The second UE may monitor one carrier (or a certain number of carriers or fewer).

[0291] The first UE may continuously receive and monitor P-RS signals transmitted in the first carrier / second carrier included in bandwidth F0 (e.g., P-RS#1 in the first carrier, P-RS#1 / P-RS#2 / P-RS#3 in the second carrier) (even after initial access is complete / while in RRC connection mode).

[0292] The second UE does not need to monitor (or stop / cancel monitoring) P-RS signals transmitted on the first / second carrier included in bandwidth F0 (e.g., P-RS#1 on the first carrier, P-RS#1 / P-RS#2 / P-RS#3 on the second carrier) (or other signals / all signals) (after initial access is complete / during RRC connection mode).

[0293] P-RS may be used for at least one of the following: BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.

[0294] The first UE may use the P-RS (e.g., P-RS #1) in the first carrier for at least one of the following: time / frequency tracking, Doppler estimation, delay estimation, etc.

[0295] The second UE may use P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) on the carrier receiving the data / control information (e.g., a third carrier) for at least one of the following: time / frequency tracking, Doppler estimation, delay estimation, etc.

[0296] According to Embodiment 2.4, the carrier / bandwidth used for transmitting / receiving RS / channels can be appropriately allocated according to the capabilities of the UE.

[0297] <<Embodiment 2.5>> The period of the P-RS may be determined for each carrier on which the P-RS is transmitted. For example, the period of the P-RS on the second carrier / third carrier may be longer than the period of the P-RS on the first carrier.

[0298] A UE may switch the carrier used for P-RS reception / monitoring as needed (on demand). A UE monitoring a specific carrier for P-RS reception may monitor a different carrier if certain conditions are met (for example, if it receives information instructing it to change the carrier being monitored).

[0299] On the second / third carrier, P-RS#1 (e.g., SSB) may be transmitted. In this case, P-RS#1 may be used in at least one of the RRM, beam management (BM), or RA procedures. If P-RS#1 is used in the RA procedure, P-RS#1 may be associated with a specific signal / channel (e.g., RACH).

[0300] P-RS#2 / P-RS#3 (e.g., CSI-RS / TRS) may be transmitted on the second / third carrier. In this case, P-RS#2 / P-RS#3 may be used in at least one of the RRM, beam management (BM), and RA procedures.

[0301] P-RS#2 / P-RS#3 (e.g., CSI-RS / TRS) may be transmitted on the first carrier. The first UE (e.g., high-end UE) does not have to receive P-RS#2 / P-RS#3 on the first carrier. The second UE (e.g., low-end UE) may receive P-RS#2 / P-RS#3 on the first carrier.

[0302] The UE may stop / cancele monitoring of the first carrier after initial access is complete and monitor the second / third carriers. In this case, the RS for initial access (e.g., P-RS #1 on the first carrier) becomes unnecessary, and the period of the P-RS on the second / third carriers can be lengthened, thereby reducing network energy consumption (Network Energy Saving (NES)). Furthermore, the second / third carriers can be used to acquire QCL information (e.g., Doppler shift / Doppler spread) on the third carrier, track time / frequency, etc.

[0303] UE may camp on to the second carrier in RRC idle mode.

[0304] <<Embodiment 2.6>> The UE may follow at least one of the following receiving controls B1 and B2. The individual controls / operations described in receiving controls B1 and B2 may be combined as appropriate. In addition, the individual controls / operations described in receiving controls B1 and B2 may be combined as appropriate with the individual controls / operations described in receiving controls A1 to A4 above.

[0305] The following reception controls B1 and B2 are preferably applied when the band on which P-RS is transmitted and the band on which PDCCH / PDSCH is transmitted in the carrier monitored by the UE are the same, but they may also be applied when these bands are different.

[0306] <<<Receive Control B1>>> If a short-period P-RS (hereinafter also referred to as short-period P-RS) is transmitted on the first carrier and a long-period P-RS (hereinafter also referred to as long-period P-RS) is transmitted on the second / third carrier, the UE may not monitor the first carrier after the initial access is complete (while in RRC connection mode) and instead monitor the second / third carrier. In other words, after the initial access is complete (while in RRC connection mode), the UE may prioritize receiving / monitoring the long-period P-RS on the second / third carrier over the short-period P-RS on the first carrier.

[0307] For example, in Figure 17, a short-period P-RS#1 (e.g., SSB) is transmitted on the first carrier, and a long-period P-RS#2 / long-period P-RS#3 (e.g., CSI-RS / TRS) is transmitted on the second carrier. In this case, the UE does not monitor the first carrier after initial access is complete (while in RRC connection mode), but monitors the second carrier. In other words, after initial access is complete (while in RRC connection mode), the UE prioritizes receiving / monitoring the long-period P-RS#2 / long-period P-RS#3 on the second carrier over the short-period P-RS#1 on the first carrier.

[0308] The long-period P-RS in the second / third carrier may be QCL with respect to a specific QCL type / QCL parameter with respect to the short-period P-RS in the first carrier. In this case, the short-period P-RS in the first carrier may be the short-period P-RS received in the initial access procedure (e.g., the latest / last short-period P-RS received in the initial access procedure).

[0309] The UE may receive P-RS / A-RS / SP-RS on the third carrier.

[0310] For example, in Figure 17, the UE receives P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 (e.g., CSI-RS / TRS) on the third carrier.

[0311] The UE may use long-period P-RS transmitted on the second carrier and at least one of P-RS / A-RS / SP-RS transmitted on the third carrier to perform at least one of the following: BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.

[0312] For example, in Figure 17, the UE uses at least one of the following to perform BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.: a long-period P-RS#2 / long-period P-RS#3 transmitted on the second carrier and P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 transmitted on the third carrier.

[0313] P-RS / A-RS / SP-RS in the third carrier may QCL with respect to long-period P-RS in the second carrier and specific QCL type / QCL parameters. One long-period P-RS may QCL with respect to multiple P-RS / A-RS / SP-RS and specific QCL type / QCL parameters.

[0314] For example, in Figure 17, P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 in the third carrier may QCL with respect to a specific QCL type / QCL parameter with respect to a long-period P-RS#2 / long-period P-RS#3 in the second carrier. Also, in Figure 17, one long-period P-RS may QCL with respect to two P-RS / A-RS / SP-RS and respect to a specific QCL type / QCL parameter.

[0315] P-RS / A-RS / SP-RS in the third carrier may loosely QCL with long-period P-RS in the second carrier. One long-period P-RS may loosely QCL with multiple P-RS / A-RS / SP-RS. In this disclosure, A being loosely QCL with B may mean that A is QCL with B for a specific QCL type / QCL parameter, that A is not QCL with B for at least one QCL parameter, that A is QCL with B for some QCL parameters, that the time synchronization between A and B is less than or equal to a specific value (e.g., X (ns)), or that the frequency synchronization between A and B is less than or equal to (e.g., Y (Hz)).

[0316] For example, in Figure 17, the P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 in the third carrier may loosely QCL with the long-period P-RS#2 / long-period P-RS#3 in the second carrier. Also, in Figure 17, one long-period P-RS may loosely QCL with two A-RS / SP-RS.

[0317] The P-RS / A-RS / SP-RS in the third carrier do not necessarily have to be the long-period P-RS and QCL in the second carrier.

[0318] For example, in Figure 17, the P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 in the third carrier do not necessarily have to be the long-period P-RS#2 / long-period P-RS#3 and QCL in the second carrier.

[0319] The UE may receive a PDCCH / PDSCH on the third carrier based on a long-period P-RS on the second carrier and at least one of a P-RS / A-RS / SP-RS on the third carrier. The PDCCH / PDSCH [DMRS [port]] on the third carrier may QCL for a specific QCL type / QCL parameter and a P-RS / A-RS / SP-RS on the third carrier.

[0320] For example, in Figure 17, the UE receives PDCCH / PDSCH on the third carrier based on P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 on the third carrier. PDCCH / PDSCH [DMRS [port]] on the third carrier is QCL for P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3 and specific QCL type / QCL parameters on the third carrier.

[0321] The reception control B1 is preferably applied to high-end UEs, but may also be applied to low-end UEs.

[0322] According to the receive control B1, the UE can properly receive the RS / channel using the second / third carrier. Furthermore, since it is no longer necessary to monitor the first channel after the initial access is completed (during RRC connection mode), the monitoring load on the UE can be reduced.

[0323] <<<Receive Control B2>>> If a short-period P-RS is transmitted on the first carrier and a long-period P-RS is transmitted on the second carrier, the UE may monitor the second carrier instead of the first carrier after the initial access is completed (while in RRC connection mode).

[0324] The UE may receive a long-period P-RS on the second carrier. The long-period P-RS on the second carrier may QCL with respect to a specific QCL type / QCL parameter with respect to the short-period P-RS on the first carrier. In this case, the short-period P-RS on the first carrier may be the short-period P-RS received in the initial access procedure (e.g., the latest / last short-period P-RS received in the initial access procedure).

[0325] The UE may use the long-period P-RS transmitted on the second carrier to perform at least one of the following: BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.

[0326] For example, in Figure 18, at least one of the following is performed using the long-period P-RS#2 / long-period P-RS#3 transmitted on the second carrier: BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.

[0327] The UE may receive PDCCH / PDSCH on the second carrier based on the long-period P-RS on the second carrier. The PDCCH / PDSCH [DMRS [port]] on the second carrier may QCL for the long-period P-RS on the second carrier and a specific QCL type / QCL parameter.

[0328] For example, in Figure 18, the UE receives PDCCH / PDSCH on the second carrier based on the long-period P-RS#2 / long-period P-RS#3 on the second carrier. The PDCCH / PDSCH [DMRS [port]] on the second carrier is a QCL for the long-period P-RS#2 / long-period P-RS#3 on the second carrier and a specific QCL type / QCL parameter.

[0329] On the second carrier, A-RS / SP-RS (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) may be transmitted as the QCL source RS of PDCCH / PDSCH. In this case, PDCCH / PDSCH [DMRS [port]] may QCL for the A-RS / SP-RS on the second carrier and specific QCL type / QCL parameters.

[0330] In receive control B2, the second carrier may be the same as the third carrier (the second carrier may be included in the third carrier). In other words, in receive control B2, the second carrier and the third carrier may be interchangeable.

[0331] In reception control B2, the band monitored by the UE may be the same as that of the first carrier / second carrier.

[0332] The reception control B2 is preferably applied to low-end UEs, but may also be applied to high-end UEs.

[0333] According to receive control B2, the UE can properly receive the RS / channel using the second carrier. Furthermore, since it is no longer necessary to monitor the first channel after the initial access is completed (during RRC connection mode), the monitoring load on the UE can be reduced.

[0334] <<Embodiment 2.7>> The QCL information of the PDCCH / PDSCH may be obtained based on the first QCL information and the second QCL information. The UE may receive the PDCCH / PDSCH using the QCL information of the PDCCH / PDSCH.

[0335] The first QCL information may be information preferably obtained from the P-RS measurement results. For example, the first QCL information may be information related to Doppler. The second QCL information may be information that can be obtained without the P-RS measurement results, or information that cannot be obtained from the P-RS measurement results, etc. For example, the second QCL information may be information preferably obtained within the same carrier / band as PDCCH / PDSCH.

[0336] The first QCL information and the second QCL information may be obtained according to at least one of the following options E1 to E3. In each of options E1 to E3, the first QCL information may be replaced with the second QCL information, and the second QCL information may be replaced with the first QCL information.

[0337] Option E1: The first QCL information may be obtained based on the measurement results of short-period P-RS (e.g., P-RS#1, SSB), and the second QCL information may be obtained based on the measurement results of long-period P-RS (e.g., P-RS#2 / P-RS#3, CSI-RS / TRS).

[0338] Option E2: The first QCL information may be obtained based on the measurement result of RS in the same carrier / band as the PDCCH / PDSCH, and the second QCL information may be obtained based on the measurement result of RS in a different carrier / band than the PDCCH / PDSCH.

[0339] Option E3: The first QCL information may be obtained based on the P-RS (measurement results), and the second QCL information may be obtained based on the A-RS / SP-RS (measurement results).

[0340] For each QCL type / QCL parameter, it may be specified which QCL information is used. For example, a first QCL type / QCL parameter may be specified that uses either the first QCL information or the second QCL information, or a second QCL type / QCL parameter may be specified that uses both the first and second QCL information.

[0341] When a first QCL type / QCL parameter is set / instructed, it may also be set / instructed whether to use the first QCL information or the second QCL information.

[0342] The QCL relationship between PDCCH / PDSCH and RS used for receiving PDCCH / PDSCH may follow at least one of the following options F1 and F2. Note that the individual controls / operations described in options F1 and F2 may be combined as appropriate.

[0343] Options F1 and F2 below are preferably applied when the band containing the carrier on which P-RS is transmitted (e.g., the second carrier) and the band containing the carrier on which PDCCH / PDSCH is transmitted (e.g., the third carrier) are different from each other, but they may also be applied when these bands are the same.

[0344] <<<Option F1>>> Both P-RS and A-RS / SP-RS may be set / instructed as the QCL source RS for PDCCH / PDSCH. The UE may receive PDCCH / PDSCH using first QCL information based on the measurement result of P-RS and second QCL information based on the measurement result of A-RS / SP-RS.

[0345] For example, as shown in Figure 19, the PDCCH / PDSCH transmitted in band #2 may be QCL1 with a long-period P-RS (e.g., P-RS#2 / P-RS#3) transmitted in a different band (band #1). Also, the PDCCH / PDSCH transmitted in band #2 may be QCL2 with an A-RS / SP-RS (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) transmitted in the same band (band #2). The UE may receive the PDCCH / PDSCH based on QCL1 and QCL2.

[0346] <<<Option F2>>> A-RS / SP-RS may be set / instructed as the QCL source RS for PDCCH / PDSCH, and P-RS may be set / instructed as the QCL source RS for A-RS / SP-RS. The UE may receive PDCCH / PDSCH using first QCL information based on the measurement result of P-RS and second QCL information based on the measurement result of A-RS / SP-RS.

[0347] For example, as shown in Figure 20, an A-RS / SP-RS transmitted in band #2 (e.g., A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) may be QCL (QCL1) with a long-period P-RS (e.g., P-RS#2 / P-RS#3) transmitted in a different band (band #1). Also, a PDCCH / PDSCH transmitted in band #2 may be QCL (QCL2) with an A-RS / SP-RS transmitted in the same band (band #2). The UE may receive the PDCCH / PDSCH based on QCL1 and QCL2.

[0348] According to Embodiment 2.7, the UE can appropriately transmit and receive RS / channel data using the RS / channel QCL relationship.

[0349] <<Variation of Embodiment 2>> The UE may use the P-RS on the second carrier to acquire QCL information used for transmitting and receiving RS / channel on the third carrier.

[0350] The UE may use the measurement results of the P-RS (e.g., P-RS#1, SSB) on the first carrier to initiate the measurement of the RS (e.g., RS#2 / RS#3, CSI-RS / TRS) on the second carrier. The UE may determine the time / frequency of the RS on the second carrier based on the measurement results of the P-RS on the first carrier.

[0351] When the UE initiates measurement of the RS on the second carrier (e.g., RS#2 / RS#3, CSI-RS / TRS), it may perform certain processing (e.g., correlation detection) on the RS on the second carrier. In this case, the UE may perform time / frequency synchronization of the RS on the second carrier without using the measurement results of the P-RS on the first carrier (e.g., P-RS#1, SSB).

[0352] If the first / second carrier falls within a specific frequency band (e.g., a low-frequency band within FR1), an analog beam may not be used.

[0353] According to Embodiment 2 described above, the UE can properly receive RS / channel. Furthermore, if P-RS is not transmitted on some carriers after RRC connection, the RS overhead can be reduced.

[0354] <Embodiment 3> Embodiment 3 relates to the configuration of RS resources.

[0355] The resources for RS#1 / RS#2 / RS#3 may conform to at least one of the following options G1 and G2.

[0356] Option G1: Resources for RS#1 / RS#2 / RS#3 may be configured per BWP / per carrier.

[0357] Option G2: Resources for RS#1 / RS#2 / RS#3 may be set for each set of carriers.

[0358] In option G2, if an RS resource (e.g., P-RS#1) is configured on one carrier (included in the set of carriers), then an RS resource does not need to be configured on the other carriers (included in that set).

[0359] According to the embodiment 3 described above, RS resources can be appropriately configured.

[0360] <Embodiment 4> Embodiment 4 relates to RS / channel reception control.

[0361] During initial access, the UE may use the QCL information of the P-RS (e.g., P-RS#1, SSB) to receive a specific DL signal (e.g., Msg.2 / Msg.4) and transmit a specific UL signal (e.g., Msg.1 / Msg.3).

[0362] After RRC connection, the UE may receive (or configure) P-RS / A-RS / SP-RS (e.g., P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3, CSI-RS / TRS) resources (e.g., time resources / frequency resources / code resources / sequence resources) (using RRC signaling).

[0363] Figure 21 shows an example of initial access. As shown in Figure 21, the UE may use (and monitor) a band containing at least one of the first and second carriers for initial access.

[0364] At least one of the first carrier and the second carrier may be located in the low-frequency band (coverage band).

[0365] The UE may receive a P-RS (e.g., SSB) on the first carrier. In Figure 21, the UE receives P-RS #1 on the first carrier.

[0366] A UE that has received / measured a P-RS on the first carrier may perform a random access (RA) procedure on the second carrier. The RA procedure on the second carrier may include at least one of receiving one or more initial access DL signals (e.g., Msg. 2 / Msg. 4) and transmitting one or more initial access UL signals (e.g., Msg. 1 / Msg. 3).

[0367] The UE may perform at least one step of a random access (RA) procedure on the second carrier based on the reception / measurement result of the P-RS on the first carrier (e.g., QCL information). For example, in Figure 21, the UE receives Msg. 2 on the second carrier based on the reception / measurement result of P-RS #1 on the first carrier (e.g., QCL information).

[0368] The RA procedure in the second carrier may be a 4-step RA or a 2-step RA. Furthermore, the RA procedure in the second carrier may be a CBRA or a CFRA.

[0369] A UE (UE in RRC connection mode) that has completed the RA procedure on the second carrier may transmit and receive signals / channels on the third carrier.

[0370] <<Embodiment 4.1>> After RRC connection, the UE may monitor RS#2 (e.g., TRS) instead of RS#1 (e.g., SSB).

[0371] Figure 22 shows an example of a carrier / bandwidth used for transmitting / receiving RS / channels. The first and second UEs may use bandwidth G0 for initial access (and may monitor bandwidth G0). The first UE may use bandwidth G1 for receiving data (channels) and at least one A-RS / SP-RS (e.g., A-RS#2 / SP-RS#2) (and may monitor bandwidth G1). The second UE may use bandwidth G2 for receiving data (channels) and at least one P-RS (e.g., P-RS#2) (and may monitor bandwidth G2).

[0372] The first UE and the second UE may, in the initial access procedure, receive a P-RS (e.g., P-RS#1) transmitted on a first carrier included in bandwidth G0.

[0373] The first UE may decide whether or not to receive / monitor P-RS (e.g., P-RS #1 on the first carrier, P-RS #2 on the second carrier) transmitted on the first / second carrier included in bandwidth G0 after initial access is complete / while in RRC connection mode. For example, if P-RS (e.g., P-RS #2) is transmitted on the carrier included in bandwidth G1 (e.g., the third carrier), the first UE does not need to receive / monitor P-RS transmitted on the first / second carrier included in bandwidth G0 (it may stop / cancele receiving / monitoring P-RS transmitted on the first / second carrier included in bandwidth G0). If P-RS (e.g., P-RS #2) is not transmitted on the carrier included in bandwidth G1 (e.g., the third carrier), the first UE may receive / monitor P-RS transmitted on the first / second carrier included in bandwidth G0. Figure 22 shows a case where P-RS is not transmitted in bandwidth G1.

[0374] The second UE does not need to monitor (or stop / cancel monitoring) the P-RS signals transmitted on the first / second carrier included in bandwidth G0 (e.g., P-RS #1 on the first carrier, P-RS #2 on the second carrier) (or other signals / all signals) after initial access is complete / while in RRC connection mode.

[0375] For the second UE, a P-RS (e.g., P-RS#2) on a third carrier included in bandwidth G2 may (always) be transmitted. The second UE may expect to receive a P-RS on bandwidth G2 (on a third carrier included in it) after initial access completion / during RRC connection mode.

[0376] The first UE may use at least one of the following for at least one of BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.: P-RS / A-RS / SP-RS (e.g., P-RS#2 / A-RS#2 / SP-RS#2) on the third carrier and DMRS of PDCCH / PDSCH.

[0377] For example, in Figure 22, the first UE may use at least one of the A-RS#2 / SP-RS#2 and the DMRS of PDCCH#2 / PDSCH#2 in the third carrier included in the bandwidth G1 for at least one of BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.

[0378] Furthermore, the first UE may use at least one of the following for BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.: A-RS / SP-RS (e.g., A-RS#2 / SP-RS#2) on the third carrier and DMRS on the PDCCH / PDSCH. In other words, the first UE does not have to use P-RS on the third carrier for BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc. In this case, P-RS on the third carrier does not have to be transmitted.

[0379] The second UE may use at least one of the following for at least one of BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.: the P-RS (e.g., P-RS#2) on the carrier receiving the data / control information (e.g., the third carrier) and the DMRS of the PDCCH / PDSCH.

[0380] For example, in Figure 22, the second UE may use at least one of the following for at least one of BFD, RRM, time / frequency tracking, Doppler estimation, delay estimation, etc.: P-RS#2 in the third carrier included in bandwidth G2 and DMRS of PDCCH#1 / PDSCH#1.

[0381] The first UE may perform time / frequency synchronization based on P-RS#1 on a first carrier included in band G0. After initial access is complete, the UE may receive P-RS / A-RS / SP-RS (e.g., P-RS#2 / A-RS#2 / SP-RS#2) on a third carrier included in band G1 based on time / frequency synchronization.

[0382] The second UE may perform time / frequency synchronization based on P-RS#1 on the first carrier included in band G0. After initial access is complete, the UE may receive P-RS#2 (e.g., TRS) on the third carrier included in band G2 based on time / frequency synchronization.

[0383] QCL types / QCL parameters indicating loose QCL relationships for time / frequency synchronization may be defined. In this disclosure, a loose QCL relationship for time / frequency synchronization between A and B may mean that the time synchronization between A and B is less than or equal to a specific value (e.g., X (ns)), or that the frequency synchronization between A and B is less than or equal to (e.g., Y (Hz)). The loose QCL relationship for time / frequency synchronization may be set / instructed / notified to the UE, or may be defined by specification.

[0384] A loose QCL relationship for time / frequency synchronization between a P-RS (e.g., P-RS#1) on a first carrier included in bandwidth G0 and a P-RS / A-RS / SP-RS (e.g., P-RS#2 / A-RS#2 / SP-RS#2) on a third carrier included in bandwidth G1 may be set / instructed / notified to the UE, or may be specified by the specification.

[0385] A loose QCL relationship regarding time / frequency synchronization between a P-RS on a first carrier included in bandwidth G0 (e.g., P-RS#1) and a P-RS on a third carrier included in bandwidth G2 (e.g., P-RS#2) may be set / instructed / notified to the UE, or may be specified by the specification.

[0386] The precision of time / frequency synchronization between multiple carriers may be specified by the specifications. In this case, a loose QCL relationship for time / frequency synchronization may not apply.

[0387] According to Embodiment 4.1, even in cases where the UE does not monitor the first carrier / second carrier after the initial access connection, the UE can properly transmit and receive RS / channels.

[0388] <<Embodiment 4.2>> After RRC connection, the UE may monitor either RS#1 (e.g., SSB) or RS#2 (e.g., TRS).

[0389] Figure 23 shows an example of a carrier / bandwidth used for transmitting / receiving RS / channels. The first and second UEs may use bandwidth H0 for initial access (and may monitor bandwidth H0). The first UE may use bandwidth H1 for receiving data (channels) and at least one P-RS / A-RS / SP-RS (e.g., P-RS#1 / A-RS#2 / SP-RS#2) (and may monitor bandwidth H1). The second UE may use bandwidth H2 for receiving data (channels) and at least one P-RS (e.g., P-RS#2) (and may monitor bandwidth H2).

[0390] The first and second UEs may, in the initial access procedure, receive a P-RS (e.g., P-RS#1) transmitted on a first carrier included in bandwidth H0.

[0391] The first UE may decide whether or not to receive / monitor P-RS (e.g., P-RS #1 on the first carrier, P-RS #1 on the second carrier) transmitted on the first / second carrier included in bandwidth H0 after initial access is complete / while in RRC connection mode. For example, if both P-RS #1 and P-RS #2 are transmitted on the carrier included in bandwidth H1 (e.g., the third carrier), the first UE does not need to receive / monitor P-RS #1 transmitted on the first / second carrier included in bandwidth H0 (it may stop / cancele receiving / monitoring P-RS transmitted on the first / second carrier included in bandwidth H0). If only one of P-RS#1 and P-RS#2 is transmitted in bandwidth H1 (for example, only P-RS#2 is transmitted), the first UE may receive / monitor P-RS#1 transmitted in the first / second carrier included in bandwidth H0. Figure 22 shows the case where P-RS#1 is not transmitted in bandwidth H1 (only P-RS#2 is transmitted).

[0392] The second UE does not need to monitor (or stop / cancel monitoring) P-RS signals transmitted on the first / second carrier included in bandwidth H0 (e.g., P-RS #1 on the first carrier, P-RS #1 on the second carrier) (or other signals / all signals) after initial access is complete / while in RRC connection mode.

[0393] For the second UE, both P-RS#1 and P-RS#2 may (always) be transmitted on a third carrier included in band H2. The second UE may expect to receive both P-RS#1 and P-RS#2 on band H2 (the third carrier included in it) after initial access completion / in RRC connection mode.

[0394] The first UE may perform time / frequency synchronization based on P-RS#1 on a first carrier included in band H0. After initial access is complete, the UE may receive P-RS / A-RS / SP-RS (e.g., P-RS#2 / A-RS#2 / SP-RS#2) on a third carrier included in band H1 based on time / frequency synchronization.

[0395] The second UE may perform time / frequency synchronization based on P-RS#1 on the first carrier in band H0. After initial access is complete, the UE may receive P-RS (e.g., P-RS#1) on the second carrier in band H2 based on time / frequency synchronization.

[0396] A loose QCL relationship for time / frequency synchronization between a P-RS (e.g., P-RS#1) on a first carrier included in band H0 and a P-RS / A-RS / SP-RS (e.g., P-RS#2 / A-RS#2 / SP-RS#2) on a third carrier included in band H1 may be set / instructed / notified to the UE, or may be specified by the specification.

[0397] A loose QCL relationship regarding time / frequency synchronization between a P-RS (e.g., P-RS#1) on a first carrier included in bandwidth H0 and a P-RS (e.g., P-RS#1) on a second carrier included in bandwidth H0 may be set / instructed / notified to the UE, or may be specified by the specification.

[0398] A loose QCL relationship regarding time / frequency synchronization between a P-RS on a second carrier in bandwidth H0 (e.g., P-RS#1) and a P-RS on a third carrier in bandwidth H2 (e.g., P-RS#2) may be set / instructed / notified to the UE, or specified by the specification.

[0399] According to Embodiment 4.2, even in cases where the UE does not monitor the first carrier / second carrier after the initial access connection, the UE can properly transmit and receive RS / channels.

[0400] <<Variation of Embodiment 4>> RS#1 (e.g., P-RS#1) may be used for initial access / handover (mobility) measurements. P-RS#1 may also be associated with the number of transmit beams of the base station. The base station may transmit RS#1 on all resources regardless of the beams used by the UE after RRC connection in the cell containing the base station.

[0401] RS#2 (e.g., P-RS#2) may be used only by UEs after RRC connection. A base station may transmit RS#2 only in the RS#2 resources corresponding to the beams used by UEs after RRC connection in the cell containing the base station.

[0402] The time / frequency resource density of RS#2 (e.g., TRS) may be greater than that of RS#1 (e.g., SSB). In this case, the base station can improve the peak throughput of the PDSCH by allocating more resources to the PDSCH by stopping / canceling the transmission of unused RS#2 resources.

[0403] The base station does not need to stop / cancele the transmission of unused RS#1 resources. In this case, other UEs before the RRC connection can use RS#1 to establish the RRC connection. Furthermore, the other UEs can hand over to the cell containing the base station.

[0404] Figure 24 shows an example of resource configuration for RS#1 and RS#2. In Figure 24, SSB#0 to #7 are shown as resources for RS#1. Also, TRS#0 to #7 are shown as resources for RS#2. Note that in Figure 24, the beam (TCI state) for SSB#X corresponds to TRS#X. Multiple beams for multiple / all SSBs may be used by a UE (e.g., a UE after RRC connection) (multiple / all beams for multiple / all SSBs may be configured / activated for the UE). In addition, resources for multiple / all TRS corresponding to multiple / all beams for multiple / all SSBs may be transmitted. For example, as shown in Figure 24, if multiple beams for multiple / all SSBs within one SSB cycle (e.g., SSB #0 to #7) are set / activated for the UE, then TRS may be transmitted in multiple / all TRS resources corresponding to those beams (e.g., TRS #0 to #7).

[0405] Figure 25 shows an example of resource configuration for RS#1 and RS#2. In Figure 25, SSB#0 to #7 resources are shown as resources for RS#1. Resources TRS#0 to #7 resources are shown as resources for RS#2. In Figure 25, the beam (TCI state) for SSB#X corresponds to TRS#X. One or a portion of the beams for one or a portion of the SSBs may be used by a UE (for example, a UE after RRC connection) (one or a portion of the beams for one or a portion of the SSBs may be configured / activated for the UE). In addition, one or a portion of the TRS resources corresponding to one or a portion of the beams for one or a portion of the SSBs may be transmitted. For example, as shown in Figure 25, if one or a portion of beams for one or a portion of SSBs (e.g., SSB #0) within one cycle of an SSB are configured / activated for a UE, a TRS (e.g., TRS #0) may be transmitted in one or a portion of TRS resources corresponding to one or a portion of beams.

[0406] P-RS#1 (e.g., SSB) and P-RS#2 (e.g., TRS) may be transmitted on the same carrier or on different carriers.

[0407] When P-RS#1 (e.g., SSB) and P-RS#2 (e.g., TRS) are transmitted on the same carrier / band, the QCL relationship between P-RS#1 and P-RS#2 may be defined / indicated / notified (P-RS#1 and P-RS#2 may QCL for specific QCL types / QCL parameters).

[0408] The UE may receive P-RS#2 (e.g., TRS) using a time / frequency synchronized based on P-RS#1 (e.g., SSB).

[0409] The UE may receive P-RS#2 (e.g., TRS) using a received spatial domain filter identified / determined by the reception of P-RS#1 (e.g., SSB).

[0410] When P-RS#1 (e.g., SSB) and P-RS#2 (e.g., TRS) are transmitted on different carriers / bands, the QCL relationship between P-RS#1 and P-RS#2 does not need to be defined / instructed / notified (P-RS#1 and P-RS#2 do not need to be QCL).

[0411] When P-RS#1 (e.g., SSB) and P-RS#2 (e.g., TRS) are transmitted on different carriers / bands, a loose QCL relationship between P-RS#1 and P-RS#2 may be specified / instructed / notified (P-RS#1 and P-RS#2 may have a loose QCL).

[0412] The UE may or may not use the reception results of P-RS#1 (e.g., SSB) (e.g., time / frequency synchronization based on P-RS#1, received spatial domain filter identified / determined based on P-RS#1) for the reception of P-RS#2 (e.g., TRS).

[0413] The UE may use the notified / configured / instructed RS#2 (e.g., TRS) resources to perform at least one of the following: time / frequency synchronization, or identification / determination of a received spatial domain filter. In this case, RS#2 may be a periodic signal or may be received multiple times. In other words, these controls / operations may be applied to P-RS#2.

[0414] According to Embodiment 4 described above, the UE can properly receive RS / channel. Furthermore, if P-RS is not transmitted on some carriers after RRC connection, the RS overhead can be reduced.

[0415] <Embodiment 5> Embodiment 5 relates to beam fault detection (BFD), wireless link monitoring (RLM), and mobility.

[0416] <<Analysis 3>> For BFD / RLM / mobility, it is preferable for the UE to measure / receive P-RS (e.g., P-RS#1 / P-RS#2 / P-RS#3) on a third carrier.

[0417] A UE may measure / receive P-RS#2 transmitted to other UEs (UEs after RRC connection) for measurements in the cell in which the UE is contained / connected (e.g., its own cell / serving cell) (e.g., measurements for BFD / RLM).

[0418] The UE may measure P-RS#1 for measurements in cells that do not contain the UE (e.g., peripheral cells / candidate cells / non-serving cells) (e.g., measurements for mobility).

[0419] In BFD / RLM / mobility measurements, it is undesirable to use only P-RS#1 on the first carrier. Therefore, for BFD / RLM / mobility measurements, P-RS#1 may be transmitted on a third carrier, each included in multiple bands.

[0420] For carrier aggregation (CA) within the same band (e.g., intra-band co-located CA), it is preferable that P-RS#1 is transmitted on at least one carrier within one band.

[0421] <<Embodiment 5.1>> For mobility measurements, P-RS#1 may be set up / transmitted in each of multiple bands / bandwidths.

[0422] The UE may receive P-RS#1 in each band / bandwidth. The UE may also use P-RS#1 in each band / bandwidth to perform mobility measurements.

[0423] UE may use P-RS#1 in each band / bandwidth for measurements for BFD / RLM.

[0424] UE may perform BFD / RLM measurements using P-RS#2 / A-RS#2 / SP-RS#2 in each band / bandwidth. In this case, P-RS#2 / A-RS#2 / SP-RS#2 transmitted on the same carrier as P-RS#1 may be used for BFD / RLM measurements, or P-RS#2 / A-RS#2 / SP-RS#2 transmitted on a different carrier than P-RS#1 may be used for BFD / RLM measurements.

[0425] Figure 26 shows an example of Embodiment 5.1. As shown in Figure 26, P-RS#1 may be transmitted in each of a plurality of bands (for example, P-RS#1 in carrier #2 of band #1, P-RS#1 in carrier #2 of band #2). The UE may use at least one of P-RS#1 in carrier #2 of band #1 and P-RS#1 in carrier #2 of band #2 for mobility measurements. The UE may use at least one of P-RS#1 in carrier #2 of band #1, P-RS#1 in carrier #2 of band #2, P-RS#2 / A-RS#2 / SP-RS#2 in carriers #0 / #1 / #2 of band #1, and P-RS#2 / A-RS#2 / SP-RS#2 in carriers #0 / #1 / #2 of band #2 for BFD / RLM measurements.

[0426] The carrier to which P-RS#1 is transmitted may be set for each band / bandwidth. For example, in a first band / bandwidth (e.g., low frequency band, coverage band), the carrier to which P-RS#1 is transmitted may be the first carrier / second carrier. Also, in a second band / bandwidth (e.g., high frequency band, capacity band), the carrier to which P-RS#1 is transmitted may be the third carrier.

[0427] By setting and transmitting P-RS#1 in each of the multiple bands / bandwidths, the UE can appropriately determine the handover destination cell using the P-RS#1 transmitted in each of the multiple bands / bandwidths. Furthermore, the UE can perform BFD / RLM using the P-RS#1 transmitted in each of the multiple bands / bandwidths, and at least one of P-RS#2 / A-RS#2 / SP-RS#2.

[0428] <<Embodiment 5.2>> When P-RS#1 is set / transmitted in each of multiple bands / bandwidths (for example, when Embodiment 5.1 is applied), a first carrier / second carrier / third carrier may be set / defined in each of the multiple bands / bandwidths (for each band / bandwidth) (see Figure 27).

[0429] The first UE (for example, a high-end UE) may use the first / second / third carriers in the low-frequency band for RS / channel reception, or it may use the first / second / third carriers in the high-frequency band for RS / channel reception.

[0430] For example, in Figure 27, the first UE may use the first carrier / second carrier / third carrier of band #1 for RS / channel reception, or it may use the first carrier / second carrier / third carrier of band #2 for RS / channel reception.

[0431] A second UE (for example, a low-end UE) may use the first / second / third carriers in the low-frequency band for RS / channel reception. The second UE does not have to use the first / second / third carriers in the high-frequency band for RS / channel reception.

[0432] For example, in Figure 27, the second UE may use the first carrier / second carrier / third carrier of band #1 for RS / channel reception. The second UE does not have to use the first carrier / second carrier / third carrier of band #2 for RS / channel reception.

[0433] By setting / defining a first carrier, a second carrier, and a third carrier in each of the multiple bands / bandwidths (for each band / bandwidth), the UE can properly receive RS / channels using P-RS#1 within the supported bands / bandwidths.

[0434] <<Embodiment 5.3>> Multiple types of P-RS#1 (Type 1 P-RS#1 / Type 2 P-RS#1) may be defined as P-RS#1.

[0435] Type 1P-RS#1 may consist of multiple signals / channels (or a single signal block containing multiple signals / channels). The multiple signals / channels may be PSS, SSS, PBCH, PBCH DMRS, etc.

[0436] Type 1P-RS#1 may be transmitted on the first carrier.

[0437] Type 2P-RS#1 may also be the signal received by the UE after the RRC connection.

[0438] Type 2P-RS#1 may not have at least some of the functions / configurations of Type 1P-RS#1 (e.g., functions for detection). For example, Type 2P-RS#1 may not include at least one of PSS, SSS, PBCH, and PBCH DMRS, nor may it include at least some of the time / frequency resources of Type 1P-RS#1.

[0439] Type 2P-RS#1 may be CSI-RS / TRS. In this case, the time / frequency density of Type 2P-RS#1 may be less than that of P-RS#2 (CSI-RS / TRS used as the QCL source RS for PDCCH / PDSCH).

[0440] Type 2P-RS#1 may be scrambled using the physical cell ID (PCI). Type 2P-RS#1 may be used for measuring received power / interference for each PCI (e.g., measuring RSRP / SINR).

[0441] The transmission method for P-RS#1 may be specified for each type. For example, Type 1 P-RS#1 may be transmitted on the first carrier, and for Type 2 P-RS#1, it may be determined whether or not it is transmitted per carrier / per band / per bandwidth.

[0442] In a carrier where Type 1 P-RS#1 is transmitted (for example, the first carrier), P-RS#2 may or may not be transmitted.

[0443] <<<Embodiment 5.3A>>> The resource to which Type 2P-RS#1 is transmitted (Type 2P-RS#1 resource) may be a different resource from the resource to which P-RS#2 is transmitted (P-RS#2 resource). Alternatively, the Type 2P-RS#1 resource may be a part of the P-RS#2 resource.

[0444] A base station may transmit Type 2P-RS#1 on all Type 2P-RS#1 resources, regardless of the active / configured TCI state of the UE after RRC connection within the cell formed by the base station. If a Type 2P-RS#1 resource overlaps with a PDCCH / PDSCH resource, the PDCCH / PDSCH (resource) may be rate-matched / punctured (or the PDCCH / PDSCH may not be transmitted on that PDCCH / PDSCH resource).

[0445] A base station may decide whether or not to transmit P-RS#2 based on the active / configured TCI state of the UE after RRC connection within the cell formed by the base station. For example, the base station may transmit P-RS#2 in a P-RS#2 resource corresponding to the active TCI state of the UE after RRC connection within the cell containing the base station. Conversely, the base station does not have to transmit P-RS#2 in a P-RS#2 resource corresponding to the inactive TCI state of the UE after RRC connection within the cell containing the base station.

[0446] If the P-RS#2 resource for transmitting P-RS#2 (e.g., the P-RS#2 resource corresponding to the active TCI state) overlaps / overlaps with the resource of PDCCH / PDSCH, the PDCCH / PDSCH (resource) may be rate-matched / punctured (or PDCCH / PDSCH may not be transmitted / received in that PDCCH / PDSCH resource).

[0447] If the P-RS#2 resource where P-RS#2 is not transmitted (e.g., the P-RS#2 resource corresponding to an inactive TCI state) overlaps / overlaps with the resource of PDCCH / PDSCH, PDCCH / PDSCH may be transmitted / received in that PDCCH / PDSCH resource.

[0448] Whether P-RS#2 is transmitted or not in each P-RS#2 resource may be notified from the base station to the UE.

[0449] Whether P-RS#2 is transmitted or not in each P-RS#2 resource may not be notified from the base station to the UE. When PDCCH / PDSCH is scheduled in the configured P-RS#2 resource, the UE may receive PDCCH / PDSCH without determining whether P-RS#2 is transmitted or not in the P-RS#2 resource.

[0450] Figure 28 shows an example of resource configuration for Type 2P-RS#1 and P-RS#2. In Figure 28, Type 2P-RS#1_1 to Type 2P-RS#1_4 are shown as Type 2P-RS#1 resources. Also, P-RS#2_1 to P-RS#2_4 are shown as P-RS#2 resources. Note that in Figure 28, the beam (TCI state) for Type 2P-RS#1_X corresponds to P-RS#2_X. Multiple / all beams for multiple / all Type 2P-RS#1 may be used by the UE (e.g., the UE after RRC connection) (multiple / all beams for multiple / all Type 2P-RS#1 may be configured / activated for the UE). Also, multiple / all P-RS#2 resources corresponding to multiple / all beams for multiple / all Type 2P-RS#1 may be transmitted. For example, as shown in Figure 28, if multiple beams for multiple / all type 2P-RS#1 (e.g., type 2P-RS#1_1 to type 2P-RS#1_4) are configured / activated for the UE, then P-RS#2 may be transmitted in multiple / all P-RS#2 resources corresponding to those beams (e.g., P-RS#2_1 to P-RS#2_4).

[0451] Figure 29 is a diagram showing an example of resource settings for Type 2P-RS#1 and P-RS#2. In Figure 29, Type 2P-RS#1_1 to Type 2P-RS#1_4 are shown as Type 2P-RS#1 resources. Also, P-RS#2_1 to P-RS#2_4 are shown as resources of P-RS#2. Note that in Figure 29, the beam (TCI state) for Type 2P-RS#1_X corresponds to P-RS#2_X. A UE (e.g., a UE after RRC connection) may use one / part of the beams for one / part of Type 2P-RS#1 (one / part of the beams for one / part of Type 2P-RS#1 may be set / activated for the UE). Also, one / part of the resources of P-RS#2 corresponding to one / part of the beams for one / part of Type 2P-RS#1 may be transmitted. For example, as shown in Figure 29, when one / part of the beams for one / part of Type 2P-RS#1 (e.g., Type 2P-RS#1_1) are set / activated for the UE, P-RS#2 may be transmitted in one / part of the P-RS#2 resources (e.g., P-RS#2_1) corresponding to one / part of the beams.

[0452] <<<Embodiment 5.3B>>> The resource in which Type 2P-RS#1 is transmitted (Type 2P-RS#1 resource) may be a resource different from the resource in which Type 1P-RS#1 is transmitted (Type 1P-RS#1 resource). Or, the Type 2P-RS#1 resource may be a part of the resource of Type 1P-RS#1.

[0453] The base station may transmit Type 2P-RS#1 in all Type 2P-RS# instances regardless of the active / set TCI state of the UE after RRC connection within the cell formed by the base station. When the Type 2P-RS#1 resource overlaps / overlaps with the resource of PDCCH / PDSCH, the PDCCH / PDSCH (resource) may be rate-matched / punctured (or PDCCH / PDSCH may not be transmitted in that PDCCH / PDSCH resource).

[0454] A base station may decide whether or not to transmit a type 1P-RS#1 based on the active / configured TCI state of the UE after RRC connection within the cell formed by the base station. For example, a base station may transmit a type 1P-RS#1 to a type 1P-RS#1 resource corresponding to the active TCI state of the UE after RRC connection within the cell containing the base station. Conversely, a base station does not have to transmit a type 1P-RS#1 to a type 1P-RS#1 resource corresponding to the inactive TCI state of the UE after RRC connection within the cell containing the base station.

[0455] If a Type 1P-RS#1 resource on which a Type 1P-RS#1 is transmitted (for example, a Type 1P-RS#1 resource corresponding to an active TCI state) overlaps with a PDCCH / PDSCH resource, the PDCCH / PDSCH (resource) may be rate-matched / punctured (or the PDCCH / PDSCH may not be transmitted / received in that PDCCH / PDSCH resource).

[0456] If a Type 1P-RS#1 resource that does not transmit Type 1P-RS#1 (for example, a Type 1P-RS#1 resource corresponding to an inactive TCI state) overlaps with a PDCCH / PDSCH resource, then PDCCH / PDSCH may be transmitted / received in that PDCCH / PDSCH resource.

[0457] The presence or absence of Type 1P-RS#1 transmissions in each Type 1P-RS#1 resource may be notified from the base station to the UE.

[0458] The presence or absence of Type 1P-RS#1 transmissions in each Type 1P-RS#1 resource does not need to be notified from the base station to the UE. If a PDCCH / PDSCH is scheduled in a configured Type 1P-RS#1 resource, the UE may receive the PDCCH / PDSCH without determining whether or not a Type 1P-RS#1 transmission is being made in that resource.

[0459] Figure 30 shows an example of resource configuration for Type 2P-RS#1 and Type 1P-RS#1. In Figure 30, Type 2P-RS#1_1 to Type 2P-RS#1_4 are shown as Type 2P-RS#1 resources. Similarly, Type 1P-RS#1_1 to Type 1P-RS#1_4 are shown as Type 1P-RS#1 resources. Note that in Figure 30, the beam (TCI state) for Type 2P-RS#1_X corresponds to Type 1P-RS#1_X. Multiple / all beams for multiple / all Type 2P-RS#1 may be used by a UE (e.g., a UE after RRC connection) (multiple / all beams for multiple / all Type 2P-RS#1 may be configured / activated for the UE). Also, multiple / all Type 1P-RS#1 resources corresponding to multiple / all beams for multiple / all Type 2P-RS#1 may be transmitted. For example, as shown in Figure 30, if multiple beams for multiple / all type 2P-RS#1 (e.g., type 2P-RS#1_1 to type 2P-RS#1_4) are configured / activated for the UE, then type 1P-RS#1 may be transmitted in multiple / all type 1P-RS#1 resources corresponding to those beams (e.g., type 1P-RS#1_1 to type 1P-RS#1_4).

[0460] Figure 31 shows an example of resource configuration for Type 2P-RS#1 and Type 1P-RS#1. In Figure 31, Type 2P-RS#1_1 to Type 2P-RS#1_4 are shown as Type 2P-RS#1 resources. Similarly, Type 1P-RS#1_1 to Type 1P-RS#1_4 are shown as Type 1P-RS#1 resources. Note that in Figure 31, the beam (TCI state) for Type 2P-RS#1_X corresponds to Type 1P-RS#1_X. One or some beams for one or some Type 2P-RS#1 may be used by a UE (e.g., a UE after RRC connection) (one or some beams for one or some Type 2P-RS#1 may be configured / activated for the UE). Additionally, one or more Type 1P-RS#1 resources corresponding to one or more beams for one or more Type 2P-RS#1 may be transmitted. For example, as shown in Figure 31, if one or more beams for one or more Type 2P-RS#1 (e.g., Type 2P-RS#1_1) are set up / activated for the UE, then Type 1P-RS#1 may be transmitted in one or more Type 1P-RS#1 resources (e.g., Type 1P-RS#1_1) corresponding to one or more beams.

[0461] <<<Embodiment 5.3C>>> Type 2P-RS#1 may be transmitted on multiple carriers. In this case, Type 2P-RS# may be transmitted according to at least one of the following options H1 and H2.

[0462] Option H1: Each carrier may transmit at least one of type 1P-RS#1 and type 2P-RS#1 (see Figure 32).

[0463] If interference (e.g., SINR / RSRQ) is set up as a beam report of surrounding cells for mobility (e.g., L1 / L3 beam report), the UE may expect / assume that it will receive at least one of type 1P-RS#1 and type 2P-RS#1 on each carrier.

[0464] According to option H1, the UE can appropriately determine the handover cell based on interference measurements.

[0465] Option H2: At least one of type 1P-RS#1 and type 2P-RS#1 may be transmitted on at least one carrier within each band / bandwidth (see Figure 33).

[0466] If power measurements (e.g., RSRP) are set up as beam reports for peripheral cells for mobility (e.g., L1 / L3 beam reports), the UE may expect / assume that it will receive at least one of type 1P-RS#1 and type 2P-RS#1 on at least one carrier within each band / bandwidth.

[0467] According to option H2, the UE can appropriately determine the handover cell based on the received power measurement.

[0468] <<<Embodiment 5.3D>>> Type 2P-RS#1 may notify less information than Type 1P-RS#1 (it may not notify at least some of the information notified by Type 1P-RS#1).

[0469] Type 1P-RS#1 reception may include at least one of PSS detection, SSS detection, PBCH-DMRS detection, and PBCH reception. PSS detection may include at least one of detection of a portion of the physical cell ID (PCI), detection (synchronization) of OFDM symbol timing, and (coarse) frequency synchronization. SSS detection may include detection of the physical cell ID. PBCH-DMRS detection may include detection of (a portion of) the SSB index within a half-radio frame (5ms). PBCH reception may include at least one of detection of the system frame number (SFN) and radio frame timing (SSB index), reception of configuration information for receiving remaining minimum system information (RMSI, SIB1), and recognition of whether a UE can camp in that cell (carrier).

[0470] Type 2P-RS#1 does not need to notify at least one of the PCI and SSB indices.

[0471] A UE (e.g., a UE after RRC connection) may receive information about a type 2P-RS#1 resource for measuring peripheral cells. This information may include information about at least one of a PCI (e.g., the PCI of a peripheral cell that is a candidate for handover) and an SSB index (e.g., an SSB index corresponding to an SSB transmitted in a peripheral cell that is a candidate for handover). This information may be transmitted using RRC signaling. The SSB index may be a CSI-RS resource indicator (CRI).

[0472] Figure 34 shows an example of information regarding type 2P-RS#1 resources for measuring peripheral cells. As shown in Figure 34, resources for measuring peripheral cells (e.g., time, frequency, sequence ID, etc.) may be notified per PCI / SSB index (or CRI).

[0473] Based on information regarding the type 2P-RS#1 resource for measuring peripheral cells, the UE may perform at least one of the following using the type 2P-RS#1 resource per PCI: received power measurement (e.g., RSRP measurement) and interference measurement (e.g., SINR / RSRQ measurement).

[0474] Information regarding a Type 2P-RS#1 resource for measuring surrounding cells may include information on all surrounding cells or information on some of the surrounding cells.

[0475] For example, if the peripheral cells that are candidates for handover are only some of the peripheral cells (e.g., in the case of L1L2-triggered mobility (LTM)), the information regarding the type 2P-RS#1 resources for measuring the peripheral cells may include PCI / SSB indexes / type 2P-RS#1 resources corresponding to the peripheral cells that are candidates for handover (e.g., time, frequency, sequence ID, etc.), but may not include PCI / SSB indexes / type 2P-RS#1 resources corresponding to peripheral cells that are not candidates for handover.

[0476] If all peripheral cells are candidates for handover, the information regarding the type 2P-RS#1 resource for measuring peripheral cells may include the PCI / SSB index / type 2P-RS#1 resource corresponding to the candidate peripheral cells (all peripheral cells).

[0477] Certain restrictions may be imposed for proper RSRP / SINR / RSRQ measurement. These restrictions may include at least one of the following: • The type of measurement resource of the connected cell (e.g., the cell itself / serving cell) is the same as the type of measurement resource of the surrounding cell (e.g., candidate cell). • The time / frequency resource density of the measurement resource of the connected cell is the same as the time / frequency resource density of the measurement resource of the surrounding cell.

[0478] Unless otherwise specified, an offset value may be set / notified to be added to / subtracted from / applied to at least one of the measured RSRP / SINR / RSRQ values ​​between different types of measurement resources, and between time / frequency resource densities of different measurement resources.

[0479] By limiting the information notified by Type 2P-RS#1, the resources required for Type 2P-RS#1 can be reduced compared to Type 1P-RS#1, thereby reducing RS overhead.

[0480] According to Embodiment 5 described above, by using Type 2P-RS#1, BFD / RLM / mobility can be appropriately performed.

[0481] <Supplementary> <<Notification of Information to UE>> Any information notification from [a network (Network (NW)) (e.g., a base station (Base Station (BS)))] to a UE in the above-described embodiment (in other words, reception of any information from the BS by the UE) may be performed using physical layer signaling (e.g., DCI), upper layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0482] When the above notification is performed by MAC CE, the MAC CE may be identified by including a new logical channel ID (Logical Channel ID (LCID)) that is not defined in the existing standard in the MAC subheader.

[0483] When the above notification is performed by DCI, the above notification may be performed by a specific field of the DCI, a radio network temporary identifier (Radio Network Temporary Identifier (RNTI)) used for scrambling cyclic redundancy check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0484] Also, any information notification to the UE in the above-described embodiment may be performed periodically, semi-persistently, or aperiodically.

[0485] <<Notification of Information from UE>> Any information notification from the UE to [NW] in the above-described embodiment (in other words, transmission / reporting of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), upper layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

[0486] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID not specified in existing standards in the MAC subheader.

[0487] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.

[0488] Furthermore, the notification of any information from the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0489] <<Regarding the application of each embodiment>> In UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the embodiments described above may be applied (or used) if any or more of the following conditions are met: - A higher-layer parameter indicating the specific process / operation / control / assumption / information is set; - The specific process / operation / control / assumption / information is determined based on the relevant higher-layer parameter; - The specific process / operation / control / assumption / information is designated / activated / triggered by MAC CE / DCI / UCI / Resource / Channel / RS; - A specific UE capability indicating (or related to) the specific process / operation / control / assumption / information is reported or supported; - The application of the specific process / operation / control / assumption / information is determined based on specific conditions.

[0490] The above-mentioned specific UE capability may indicate at least one of the following: • Supporting the above-mentioned specific processing / operation / control / assumment / information,

[0491] Furthermore, the above-mentioned specific UE capability may be a capability that applies across all frequencies (commonly regardless of frequency), a capability per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), a capability per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), a capability per subcarrier spacing (SCS), or a capability per feature set (FS) or feature set per component-carrier (FSPC).

[0492] Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes regardless of the duplexing scheme), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

[0493] If the above conditions are not met, UE / BS may follow the behavior specified in existing 3GPP releases.

[0494] The third carrier may mean a carrier / bandwidth capable of transmitting and receiving any signal / channel. In this case, the first / second carrier in the above-described embodiment may be read as the third carrier.

[0495] (Note) The following inventions are added with respect to one embodiment of the present disclosure (in particular, Embodiment 1). [Note 1] A terminal having: a receiving unit that detects a carrier common to a plurality of terminals for synchronization and receives a first reference signal (RS) transmitted on the carrier; and a control unit that controls the reception of a second RS different from the first RS based on the first RS. [Note 2] The terminal according to Note 1, wherein the second RS is transmitted on the same carrier to which the first RS is transmitted. [Note 3] The terminal according to Note 1 or Note 2, wherein the second RS is transmitted on a carrier different from the carrier to which the first RS is transmitted. [Note 4] The terminal according to any one of Notes 1 to 3, wherein the control unit assumes that the first RS and the second RS are QCLs for a specific pseudo-collocation (QCL) parameter.

[0496] (Note) The following inventions are added with respect to one embodiment of the present disclosure (in particular, Embodiment 2). [Note 1] A terminal having: a receiving unit that receives a first reference signal (RS) in a first carrier common to a plurality of terminals in a first band; and a control unit that controls the reception of a downlink (DL) channel in a second carrier specific to the terminal in a second band different from the first band, based on the measurement result of the first RS. [Note 2] The terminal according to Note 1, wherein the receiving unit stops monitoring the first carrier after initial access. [Note 3] The terminal according to Note 1 or Note 2, wherein the first RS is an RS that is not transmitted in the second band. [Note 4] The terminal according to any one of Notes 1 to 3, wherein the control unit assumes that the DL channel is in pseudo-collocation (QCL) with both the first RS and a second RS transmitted in the second band.

[0497] (Note) The following inventions are added with respect to one embodiment of the present disclosure (in particular, Embodiment 4). [Note 1] A terminal having: a receiving unit that receives a periodic first reference signal (RS) for initial access in a first carrier common to a plurality of terminals in a first band; and a control unit that controls the reception of at least one periodic second RS and a non-periodic third RS in a second carrier specific to the terminal in a second band different from the first band after the initial access. [Note 2] The terminal according to Note 1, wherein the receiving unit stops monitoring the first RS when it receives the second RS after the initial access. [Note 3] The terminal according to Note 1 or Note 2, wherein the receiving unit monitors the first RS when it receives the third RS after the initial access. [Note 4] The terminal according to any one of Notes 1 to 3, wherein the control unit assumes that the first RS and the second RS are in a pseudo-collocation (QCL) relationship with respect to at least one of time synchronization and frequency synchronization.

[0498] (Note) The following inventions are added with respect to one embodiment of the present disclosure (in particular, Embodiment 5). [Note 1] A terminal having: a receiving unit that receives a first periodic reference signal (P-RS) used for initial access on a first carrier common to a plurality of terminals, and a second P-RS used after the initial access on a second carrier specific to the terminal; and a control unit that controls at least one measurement of interference and received power based on at least one of the first P-RS and the second P-RS. [Note 2] The terminal according to Note 1, wherein the resources of the second P-RS are part of the resources of the first P-RS. [Note 3] The terminal according to Note 1 or Note 2, wherein, when the measurement of interference is set, the control unit assumes that at least one of the first P-RS and the second P-RS is received on each carrier. [Note 4] When the measurement of the received power is set, the control unit assumes that at least one of the first P-RS and the second P-RS is received in at least one carrier in each band, the terminal as described in any of Notes 1 to 3.

[0499] (Wireless Communication System) The configuration of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any of the wireless communication methods according to the above embodiments of this disclosure, or a combination thereof.

[0500] Figure 35 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

[0501] Furthermore, the wireless communication system 1 may support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and the like.

[0502] In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the Secondary Node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0503] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity where both MN and SN are NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0504] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. User terminals 20 may be located within at least one cell. The arrangement, number, shape, size, etc., of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.

[0505] The wireless communication system 1 may utilize Multi Input Multi Output (MIMO). For example, one cell may be formed by one antenna / base station 10, or by multiple antennas / base stations 10. One [virtual] cell (which may be called a supercell, for example) may be composed of multiple [virtual] cells (which may be called subcells, for example). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell whose physical range fluctuates quasi-statically / dynamically. In this case, the wireless communication system 1 may be called a cell-free system.

[0506] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

[0507] Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz. Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be in a frequency band higher than FR2.

[0508] Furthermore, the user terminal 20 may communicate in each CC using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0509] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 / Xn interface, etc.) or wireless (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.

[0510] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0511] The core network 30 may include network functions (NF) such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Multiple functions may be provided by a single network node. Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.

[0512] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0513] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-OFDM), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0514] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

[0515] In the wireless communication system 1, a Physical Downlink Shared Channel (PDSCH), a Broadcast Channel (PBCH), or a Physical Downlink Control Channel (PDCCH) may be used as the downlink channel, which is shared by each user terminal 20.

[0516] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0517] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

[0518] Lower-layer control information may be transmitted by PDCCH. The lower-layer control information may include, for example, Downlink Control Information (DCI) which includes scheduling information for at least one of PDSCH and PUSCH.

[0519] Furthermore, the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Furthermore, PDSCH may be read as DL data, and PUSCH may be read as UL data.

[0520] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. A UE may monitor CORESETs associated with a given search space based on the search space configuration.

[0521] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

[0522] PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery acknowledgment information (for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell.

[0523] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted from the names of various channels.

[0524] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc., may be transmitted. In the wireless communication system 1, the DL-RS may include a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc.

[0525] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.

[0526] Furthermore, in the wireless communication system 1, the uplink reference signal (UL-RS) may include a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. The DMRS may also be called a user-specific reference signal (UE-specific Reference Signal).

[0527] (Base Station) Figure 36 shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmitting / receiving unit 120, the transmitting / receiving antenna 130, and the transmission line interface 140 may be provided.

[0528] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0529] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

[0530] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may also control transmission and reception, measurement, etc., using the transmitting / receiving unit 120, transmitting / receiving antenna 130, and transmission path interface 140. The control unit 110 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transmitting / receiving unit 120. The control unit 110 may also perform call processing of communication channels (setting, releasing, etc.), status management of the base station 10, management of wireless resources, etc.

[0531] The transmitting / receiving unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0532] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0533] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0534] The transmitting / receiving unit 120 may transmit the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 may also receive the uplink channel, uplink reference signal, etc.

[0535] The transmitting / receiving unit 120 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0536] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform processing on data and control information acquired from the control unit 110, for example, at the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), and the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), to generate a bit sequence to be transmitted.

[0537] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, discrete Fourier transform (DFT) processing (if necessary), inverse fast Fourier transform (IFFT) processing, precoding, and digital-to-analog conversion, and output a baseband signal.

[0538] The transmitting / receiving unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 130.

[0539] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 130.

[0540] The transmitting / receiving unit 120 (receiving processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0541] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc., based on the received signal. The measurement unit 123 may also measure received power (e.g., Reference Signal Received Power (RSRP)), reception quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0542] The transmission path interface 140 may send and receive signals (backhaul signaling) with devices included in the core network 30 (e.g., network nodes that provide NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0543] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0544] The base station 10 may be separated into three elements: a Radio Unit (RU), a Distributed Unit (DU), and a Central Unit (CU). For example, the RU may implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level physical layer functions (precoding, IFFT, FFT, etc.). The DU may implement higher-level physical layer functions (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

[0545] In this disclosure, base station 10 may include a single device that implements all the functions of RU, DU, and CU, or it may include multiple devices that each implement some of the functions of RU, DU, and CU and are connected to each other. In this disclosure, base station 10 may be interpreted as RU / DU / CU.

[0546] The transmitting / receiving unit 120 may transmit a first reference signal (RS) on a carrier common to multiple terminals for synchronization.

[0547] The control unit 110 may control the transmission of a second RS, which is different from the first RS, and is received based on the first reference signal (RS).

[0548] The transmitting / receiving unit 120 may transmit a first reference signal (RS) on a first carrier that is common to multiple terminals within the first band.

[0549] The control unit 110 may control the transmission of a terminal-specific downlink (DL) channel on a second carrier in a second band different from the first band, which is received based on the measurement results of the first RS.

[0550] The transmitting / receiving unit 120 may transmit a periodic first reference signal (RS) for initial access on a first carrier that is common to multiple terminals within the first band.

[0551] The control unit 110 may, after the initial access, control the transmission of at least one periodic second RS and a non-periodic third RS on a terminal-specific second carrier in a second band different from the first band.

[0552] The transmitting / receiving unit 120 may transmit a first periodic reference signal (P-RS) used for initial access on a first carrier common to multiple terminals, and transmit a second P-RS used after the initial access on a second carrier specific to its own terminal.

[0553] The control unit 110 may control at least one measurement of interference and received power using at least one of the first P-RS and the second P-RS.

[0554] (User Terminal) Figure 37 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0555] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0556] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

[0557] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may also control transmission and reception, measurement, etc., using the transmitting / receiving unit 220 and the transmitting / receiving antenna 230. The control unit 210 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transmitting / receiving unit 220.

[0558] The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0559] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.

[0560] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0561] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.

[0562] The transmitting / receiving unit 220 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0563] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc., on data and control information acquired from the control unit 210 to generate a bit sequence to be transmitted.

[0564] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion, and output a baseband signal.

[0565] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

[0566] The transmitting / receiving unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 230.

[0567] On the other hand, the transmitting / receiving unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 230.

[0568] The transmitting / receiving unit 220 (receiving processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0569] The transmitting / receiving unit 220 (measuring unit 223) may perform measurements related to the received signal. For example, the measuring unit 223 may perform RRM measurement, CSI measurement, etc., based on the received signal. The measuring unit 223 may also measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0570] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources may be, for example, Non Zero Power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources may be at least one of the following: NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.

[0571] In this disclosure, the transmitting unit and receiving unit of the user terminal 20 may be composed of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0572] The transmitting / receiving unit 220 may detect a carrier common to multiple terminals for synchronization (e.g., a perch carrier) and receive a first reference signal (RS) (e.g., P-RS#1) transmitted on the carrier (Embodiment 1).

[0573] The control unit 210 may control the reception of a second RS (e.g., P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) that is different from the first RS, based on the first RS (Embodiment 1).

[0574] The second RS may be transmitted on the same carrier on which the first RS is transmitted (Embodiment 1).

[0575] The second RS may be transmitted on a different carrier (e.g., an anchor carrier / data carrier) from the carrier on which the first RS is transmitted (Embodiment 1).

[0576] The control unit 210 may assume that the first RS and the second RS are QCLs for a specific pseudo-collocation (QCL) parameter (Embodiment 1).

[0577] The transmitting / receiving unit 220 may receive a first reference signal (RS) (e.g., P-RS#1) on a first carrier (e.g., a perch carrier) that is common to multiple terminals in the first band (Embodiment 2).

[0578] The control unit 210 may control the reception of a downlink (DL) channel on a second carrier (e.g., a data carrier) specific to the terminal within a second band different from the first band, based on the measurement results of the first RS (Embodiment 2).

[0579] The transmitting / receiving unit 220 may stop monitoring the first carrier after the initial access (Embodiment 2).

[0580] The first RS may be an RS that is not transmitted in the second band (Embodiment 2).

[0581] The control unit 210 may assume that the DL channel is in a pseudo-collocation (QCL) with both the first RS and the second RS transmitted in the second band (e.g., P-RS#2 / P-RS#3 / A-RS#2 / A-RS#3 / SP-RS#2 / SP-RS#3) (Embodiment 2).

[0582] The transmitting / receiving unit 220 may receive a periodic first reference signal (RS) (e.g., P-RS#1) for initial access on a first carrier (e.g., perch carrier) that is common to multiple terminals in the first band (Embodiment 4).

[0583] The control unit 210 may, after the initial access, control the reception of at least one periodic second RS (e.g., P-RS#2) and a non-periodic third RS (e.g., A-RS#2) in a second carrier (e.g., data carrier) specific to the terminal in a second band different from the first band (Embodiment 4).

[0584] If the transmitting / receiving unit 220 receives the second RS after the initial access, it may stop monitoring the first RS (Embodiment 4).

[0585] If the transmitting / receiving unit 220 receives the third RS after the initial access, it may monitor the first RS (Embodiment 4).

[0586] The control unit 210 may assume that the first RS and the second RS are in a pseudo-collocation (QCL) relationship with respect to at least one of time synchronization and frequency synchronization (Embodiment 4).

[0587] The transmitting / receiving unit 220 may receive a first periodic reference signal (P-RS) (e.g., type 1 P-RS #1) used for initial access on a first carrier (e.g., perch carrier) common to multiple terminals, and a second P-RS (e.g., type 2 P-RS #1) used after the initial access on a second carrier specific to its own terminal.

[0588] The control unit 210 may control at least one measurement of interference and received power based on at least one of the first P-RS and the second P-RS.

[0589] The second P-RS resource may be a part of the first P-RS resource.

[0590] When the interference measurement is set, the control unit 210 may assume that at least one of the first P-RS and the second P-RS is received on each carrier.

[0591] When the measurement of the received power is set, the control unit 210 may assume that at least one of the first P-RS and the second P-RS is received in at least one carrier within each band.

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

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

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

[0595] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0596] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, the processing may be performed by one processor, or it may be performed by two or more processors simultaneously, sequentially, or by other means. Note that the processor 1001 may be implemented using one or more chips.

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

[0598] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

[0599] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

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

[0601] The storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a Compact Disk (Compact Disc ROM (CD-ROM)), a Digital Use Disk, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. The storage 1003 may also be called an auxiliary storage device.

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

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

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

[0605] Furthermore, the base station 10 and the user 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), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0606] Furthermore, devices included in the core network 30 (for example, network nodes that provide NF) may also be implemented using the functional block / hardware configuration described above.

[0607] (Variations) Terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

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

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

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

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

[0612] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

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

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

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

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

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

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

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

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

[0621] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

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

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

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

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

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

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

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

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

[0630] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

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

[0632] Any information described in this disclosure (e.g., variables, constants, parameters) may be communicated from any first device (e.g., UE / base station) to any second device (e.g., base station / UE) that indicates / specifies (or relates to) the value of such any information, even if not specifically stated in the embodiments described above.

[0633] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0634] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Elements (CEs).

[0635] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).

[0636] The determination may be made by a value represented by one bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

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

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

[0639] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0640] In this disclosure, terms such as “precoding,” “precoder,” “weight (precoding weight),” “quasi-co-location (QCL),” “transmission configuration indication state (TCI state),” “spatial relation,” “spatial domain filter,” “transmit power,” “phase rotation,” “antenna port,” “layer,” “number of layers,” “rank,” “resource,” “resource set,” “beam,” “beam width,” “beam angle,” “antenna,” “antenna element,” “panel,” “UE panel,” “transmitting entity,” and “receiving entity” may be used interchangeably.

[0641] In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel" (e.g., a Demodulation Reference Signal (DMRS) port). In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel" (e.g., a reference signal resource, an SRS resource, etc.). Resources may include time / frequency / code / spatial / power resources. Furthermore, a spatial domain transmit filter may include at least one of a spatial domain transmit filter and a spatial domain receive filter.

[0642] The above group may include, for example, at least one of the following: a spatial relationship group, a code division multiplexing (CDM) group, a reference signal (RS) group, a control resource set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, or a panel group.

[0643] Furthermore, in this disclosure, terms such as beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), and RS may be interpreted interchangeably.

[0644] Furthermore, in this disclosure, TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc., may be interpreted interchangeably.

[0645] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interpreted interchangeably.

[0646] In this disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, subset may be interpreted interchangeably.

[0647] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information (TCI state)" may be interpreted as mutually exclusive as "a set of spatial relationship information (TCI state)," "one or more pieces of spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive. Spatial relationship information and spatial relationship may be interpreted as mutually exclusive.

[0648] In this disclosure, terms such as “Base Station (BS),” “wireless base station,” “fixed station,” “NodeB,” “eNB (eNodeB),” “gNB (gNodeB),” “access point,” “Transmission Point (TP),” “Reception Point (RP),” “Transmission / Reception Point (TRP),” “panel,” “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.

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

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

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

[0652] A mobile station may also be called 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 appropriate term.

[0653] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.

[0654] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

[0655] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), 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 Internet of Things (IoT) device such as a sensor.

[0656] Figure 39 shows an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, a pneumatic pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

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

[0658] The electronic control unit 49 consists of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 installed in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0659] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression amount signals acquired by accelerator pedal sensor 55, brake pedal depression amount signals acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals acquired by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc.

[0660] The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, display, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of information / services (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.

[0661] The information service unit 59 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) or output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

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

[0663] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 sends and receives data (information) via the communication port 63 to the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40.

[0664] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

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

[0666] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 59 installed in the vehicle. The information service unit 59 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 60).

[0667] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, various sensors 50-58, etc., which are provided in the vehicle 40.

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

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

[0670] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes having base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0671] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0672] Each aspect / embodiment described in this disclosure is Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (where x is, for example, an integer or decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, systems utilizing Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, and next-generation systems extended, modified, created, or defined based thereon may also be applied. Furthermore, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

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

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

[0675] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to mean judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0676] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0677] Furthermore, “judgment (decision)” may be considered as “judgment (decision)” of resolving, selecting, choosing, establishing, comparing, etc. In other words, “judgment (decision)” may be considered as “judgment (decision)” of some action. In this disclosure, “judgment (decision)” may be interpreted as mutually interchangeable with the actions described above.

[0678] Furthermore, in this disclosure, “determine / determining” may be interpreted as “assume / assuming,” “expect / expecting,” or “consider / considering.” In addition, in this disclosure, “not expecting to do…” may be interpreted as “expecting not to do….”

[0679] In this disclosure, "expect" may be rephrased as "be expected." For example, "expect(s) ..." (where "..." may be expressed as a that clause, an infinitive, etc.) may be rephrased as "be expected ..." or "do (the verb without "to" if "..." is an infinitive)." Similarly, "does not expect ..." may be rephrased as "be not expected ..." or "do not (the verb without "to" if "..." is an infinitive)." Furthermore, "An apparatus A is not expected ..." may be rephrased as "An apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).

[0680] The term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0681] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0682] In this disclosure, when two elements are connected, they can be considered to be "connected" or "coupled" to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

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

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

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

[0686] In this disclosure, "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").

[0687] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

[0688] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "B based on A", "B during / while A", "B before A", "B at (the same time as) / on A", "B after A", "B since A", and "B until A" may be interchangeable. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information.

[0689] In this disclosure, timing, time, duration, time instance, any unit of time (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc., may be interpreted interchangeably.

[0690] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.

Claims

1. A terminal having: a receiving unit that receives a first reference signal (RS) in a first carrier common to multiple terminals in a first band; and a control unit that controls the reception of a downlink (DL) channel in a second carrier specific to the terminal in a second band different from the first band, based on the measurement result of the first RS.

2. The terminal according to claim 1, wherein the receiving unit stops monitoring the first carrier after initial access.

3. The terminal according to claim 1, wherein the first RS is an RS that is not transmitted in the second band.

4. The terminal according to claim 1, wherein the control unit assumes that the DL channel is in pseudo-collocation (QCL) with both the first RS and the second RS transmitted in the second band.

5. A wireless communication method for a terminal, comprising the steps of: receiving a first reference signal (RS) in a first carrier common to multiple terminals in a first band; and controlling the reception of a downlink (DL) channel in a second carrier specific to the terminal in a second band different from the first band, based on the measurement result of the first RS.

6. A base station having: a transmitting unit that transmits a first reference signal (RS) on a first carrier common to multiple terminals in a first band; and a control unit that receives the measurement result of the first RS and controls the transmission of a downlink (DL) channel on a terminal-specific second carrier in a second band different from the first band.

Images