Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure is provided with: a reception unit that receives information relating to a candidate cell that is a handover candidate for a serving cell and information relating to a transmission setting indication (TCI) state; and a control unit that determines, with respect to a demodulation reference signal (DMRS) of a DL channel, that one or more quasi co-location types (QCL types) having reference signals corresponding to a physical cell ID (PCI) different from the serving cell are indicated by information relating to the TCI state.

Description

TECHNICAL FIELD

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

[0002] In a Universal Mobile Telecommunication System (UMTS) network, Long Term Evolution (LTE) has been standardized for the purpose of further high-speed data rates, low latency, and so on (Non-Patent Literature 1). Further, LTE-Advanced (3GPP Rel. 10-14) has been standardized for the purpose of further large capacity, higher, and so on of LTE (3rd Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

[0003] A subsequent system of LTE (for example, also referred to as a 5th generation mobile communication system (5G), 5G+, a 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 onwards, and so on) is also being studied.

[0004] PRIOR ART DOCUMENTS

[0005] NON-PATENT LITERATURE

[0006] Non-Patent Literature 1: 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 SUMMARY

[0007] PROBLEMS TO BE SOLVED BY THE INVENTION

[0008] In a future wireless communication system (for example, a Rel. 17 / 5G subsequent wireless communication system), it is envisaged that communication is controlled based on inter-cell mobility including a plurality of non-serving cells, or inter-cell mobility utilizing a plurality of transmission reception points (for example, Multi-TRP (MTRP)). It is also envisaged that, in the inter-cell mobility, a candidate cell is set, and switching / change of a serving cell and the candidate cell is performed using L1 / L2 signaling.

[0009] However, in a case where inter-cell mobility (for example, switching of a serving cell and a candidate cell, and the like) is applied, how to set / apply a Transmission Configuration Indication state (TCI state) corresponding to the candidate cell becomes a problem. In a case where the TCI state of the candidate cell cannot be properly set / applied, there is a concern that the quality of communication is degraded.

[0010] The present disclosure was made in view of the above-described points, and one of the objects is to provide a terminal, a wireless communication method, and a base station capable of properly controlling communication even in a case where a candidate cell is set / supported.

[0011] Means for solving the problem

[0012] A terminal according to an aspect of the present disclosure includes a reception unit that receives information on a candidate cell that is a switching candidate of a serving cell, and information on a Transmission Configuration Indication (TCI) state, and a control unit that, with respect to a Demodulation Reference Signal (DMRS) of a DL channel, judges that it is indicated by the information on the TCI state that there is one or more Quasi Co-Location type (QCL type) having a reference signal corresponding to a physical cell ID (PCI) different from that of the serving cell.

[0013] Effects of the Invention

[0014] According to an aspect of the present disclosure, communication can be properly controlled even in a case where a candidate cell is set / supported. BRIEF DESCRIPTION OF DRAWINGS

[0015] Figure 1A is a diagram illustrating an example of movement of a UE in Rel. 17. Figure 1B is a diagram illustrating an example of movement of a UE in Rel. 18.

[0016] Figure 2 is a diagram illustrating an example of association of a serving cell and a candidate cell.

[0017] Figure 3A is a diagram representing a first example of Option 2 of candidate cell setting. Figure 3B is a diagram representing a second example of Option 2 of candidate cell setting.

[0018] Figure 4 is a diagram representing a service cell switching example 1.

[0019] Figure 5 is a diagram representing a service cell switching example 2.

[0020] Figure 6 is a diagram representing a service cell switching example 3.

[0021] Figure 7 is a diagram representing an outline of L1L2-triggered mobility (LTM).

[0022] Figure 8 is a diagram representing a PDCCH ordered RACH (PDCCH ordered RACH) for a service cell with PDCCH-based indication with random access response (RAR) monitoring.

[0023] Figure 9 is a diagram representing a PDCCH ordered RACH (PDCCH ordered RACH) for a candidate cell with PDCCH-based indication without random access response (RAR) monitoring.

[0024] Figure 10A and Figure 10B represent an example of unified / common TCI framework.

[0025] Figure 11 is a diagram representing an example of information element (or, RRC parameter) of TCI state.

[0026] Figure 12 is a diagram representing an example of RS which becomes a QCL source related to the first embodiment.

[0027] Figures 13A-13C is a diagram representing an example of QCL rule related to the first embodiment.

[0028] Figure 14 is a diagram representing an example of RS which becomes a QCL source related to the second embodiment.

[0029] Figures 15A-15C is a diagram representing an example of QCL rule related to the second embodiment.

[0030] Figure 16A and Figure 16Bis a diagram representing another example of the QCL rule involved in the second embodiment.

[0031] Figure 17 is a diagram representing an example of an outline structure of a wireless communication system involved in an embodiment.

[0032] Figure 18 is a diagram representing an example of a structure of a base station involved in an embodiment.

[0033] Figure 19 is a diagram representing an example of a structure of a user terminal involved in an embodiment.

[0034] Figure 20 is a diagram representing an example of a hardware structure of a base station and a user terminal involved in an embodiment.

[0035] Figure 21 is a diagram representing an example of a vehicle involved in an embodiment. DETAILED DESCRIPTION

[0036] (TCI, Spatial Relation, QCL)

[0037] In NR, it is being studied to control at least one of reception processing (for example, at least one of reception, demapping, demodulation, decoding) and transmission processing (for example, at least one of transmission, mapping, precoding, modulation, coding) of a signal / channel in a UE based on a transmission configuration indication state (TCI state) for at least one of a signal / channel.

[0038] The TCI state can also mean a TCI state applied to a downlink signal / channel. What is equivalent to a TCI state applied to an uplink signal / channel can also be expressed as a spatial relation.

[0039] The so-called TCI state is information related to quasi-co-location (QCL) of a signal / channel, and can also be referred to as spatial reception parameters, spatial relation information, and the like. The TCI state can also be set to a UE per channel or per signal.

[0040] QCL is an indicator of the statistical properties of a signal / channel. For example, it can also mean that when a signal / channel has a QCL relationship with other signals / channels, it can be assumed that at least one of the following is the same among these different signals / channels: Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter) (with regard to at least one of them being the QCL).

[0041] Additionally, the spatial reception parameters may also correspond to the UE's receive beam (e.g., receive analog beam), and the beam may also be determined based on the spatial QCL. The QCL (or at least one element of the QCL) in this disclosure may also be rewritten as sQCL (spatial QCL).

[0042] A QCL can also be defined with multiple types (QCL types). For example, four QCL types, or types AD, can be set, where the parameters (or parameter sets) that can be assumed to be the same are different. These parameters (also called QCL parameters) are represented as follows:

[0043] • QCL Type A (QCL-A): Doppler shift, Doppler spread, average delay, and delay spread.

[0044] • QCL Type B (QCL-B): Doppler shift and Doppler extension,

[0045] • QCL Type C (QCL-C): Doppler shift and average delay,

[0046] • QCL Type D (QCL-D): Spatial reception parameters.

[0047] The UE envisions a relationship between a certain Control Resource Set (CORESET), channel, or reference signal and other CORESETs, channels, or reference signals in a specific QCL (e.g., QCL type D), which can also be called a QCL assumption.

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

[0049] The TCI state can also be, for example, information related to the QCL between the target channel (in other words, the reference signal (RS) used by the channel) and other signals (e.g., other RSs). The TCI state can also be set (indicated) by higher-layer signaling, physical-layer signaling, or a combination thereof.

[0050] In addition, the channel / signal that becomes the application object in the TCI state can also be called the target channel / reference signal (target channel / RS), or simply the target, etc. The other signals mentioned above can also be called reference RS, source RS, or simply reference, etc.

[0051] The channel that is set (specified) to TCI state or spatial relationship can be, for example, at least one of the following: downlink shared channel (Physical Downlink Shared Channel (PDSCH))), downlink control channel (Physical Downlink Control Channel (PDCCH))), uplink shared channel (Physical Uplink Shared Channel (PUSCH))), and uplink control channel (Physical Uplink Control Channel (PUCCH))).

[0052] Furthermore, the RS that is related to the channel as QCL can be at least one of the following: a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Measurement Reference Signal (Sounding Reference Signal (SRS)), a Tracking CSI-RS (also known as a Tracking Reference Signal (TRS)), a QCL Detection Reference Signal (also known as a QRS), or a DeModulation Reference Signal (DMRS).

[0053] An SSB is a block of signals that includes at least one Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a broadcast channel (Physical Broadcast Channel (PBCH)). An SSB can also be referred to as an SS / PBCH block.

[0054] The UE can also receive configuration information (e.g., PDSCH-Config, tci-StatesToAddModList) containing a list of information elements of TCI state via higher-layer signaling.

[0055] The TCI state information element (RRC's "TCI-state IE") set via higher-layer signaling may also include a TCI state ID and one or more QCL information ("QCL-Info"). The QCL information may also include at least one information related to the RS that forms a QCL relationship (RS-related information) and information indicating the QCL type (QCL type information). RS-related information may also include the RS's index (e.g., SSB index, Non-Zero-Power (NZP) CSI-RS resource ID (identifier)), the cell index of the RS, and the index of the Bandwidth Part (BWP) of the RS.

[0056] In Rel.15 NR, as a TCI state of at least one of PDCCH and PDSCH, both RS of QCL type A and RS of QCL type D, or only RS of QCL type A, can be set to the UE.

[0057] When the TRS is set to QCL type A RS, the TRS differs from the DeModulation Reference Signal (DMRS) of the PDCCH or PDSCH, and it is assumed that the same TRS is periodically transmitted over a long period of time. The UE can measure the TRS and calculate the average delay, delay spread, etc.

[0058] A UE whose TRS is set as a QCL type A RS in the TCI state of the DMRS of the PDCCH or PDSCH can assume that the parameters (average delay, delay spread, etc.) of the DMRS of the PDCCH or PDSCH and the QCL type A of the TRS are the same. Therefore, the type A parameters (average delay, delay spread, etc.) of the DMRS of the PDCCH or PDSCH can be obtained from the measurement results of the TRS. When performing channel estimation for at least one of the PDCCH and PDSCH, the UE can use the measurement results of the TRS to perform more accurate channel estimation.

[0059] A UE with a QCL type D RS can use the QCL type D RS to determine the UE receive beam (spatial domain receive filter, UE spatial domain receive filter).

[0060] The RS of QCL type X in TCI state can also refer to the RS that is in a relationship of QCL type X with a certain channel / signal (DMRS), and the RS can also be called the QCL source of QCL type X in TCI state.

[0061] (L1 / L2 inter-cell mobility)

[0062] The UE is studying UL transmission for one or more cells / TRPs. As a procedure in this case, consider scenario 1 or scenario 2 below. Additionally, in this disclosure, the serving cell can also be rewritten as the TRP within the serving cell. Layer 1 / Layer 2 (L1 / L2) and the DCI / Medium Access Control Control Element (MAC CE) can also be rewritten. In this disclosure, a PCI that differs from the physical cell ID (Physical Cell Identity (PCI)) of the current serving cell is sometimes abbreviated as "different PCI". Non-serving cells, cells with different PCIs, and additional cells can also be rewritten.

[0063] <Scenario 1>

[0064] Scenario 1 could be a scenario that corresponds to inter-cell mobility in multi-TRP, but it could also be a scenario that does not correspond to inter-cell mobility in multi-TRP.

[0065] (1) The UE receives from the serving cell: the setting of the SSB for beam measurement of the TRP corresponding to a different PCI from the serving cell, and the settings required for using radio resources for data transmission and reception (including resources for different PCIs).

[0066] (2) The UE performs beam measurement for the TRP corresponding to different PCIs and reports the beam measurement results to the serving cell.

[0067] (3) Based on the above report, the Transmission Configuration Indication (TCI) status associated with the TRP corresponding to different PCIs is activated by L1 / L2 signaling from the serving cell.

[0068] (4) The UE uses the dedicated channel on the TRP corresponding to different PCIs for transmission and reception.

[0069] (5) The UE needs to always cover the serving cell, including in the case of multiple TRPs. Similar to previous systems, the UE needs to use common channels from the serving cell (Broadcast Control Channel (BCCH), Paging Channel (PCH)), etc.

[0070] In Scenario 1, when the UE transmits and receives signals with the additional cell / TRP (the TRP corresponding to the PCI of the additional cell), the serving cell (the assumption of the serving cell in the UE) is not changed. The UE can also set higher-layer parameters associated with the PCI of a non-serving cell from the serving cell. Scenario 1 can also be applied, for example, in Rel. 17.

[0071] Figure 1A This diagram illustrates an example of UE movement in Rel.17. Imagine the UE moving from PCI#1 cell (serving cell) to PCI#3 cell (additional cell) (overlapping with the serving cell). In this scenario, L1 / L2-based handover to the serving cell is not supported in Rel.17.

[0072] An additional cell is a cell with an additional PCI that differs from the serving cell. The UE can receive / transmit UE-dedicated channels (CHs) from the additional cell. On the other hand, in order to receive UE common channels (e.g., system information / paging / SMS), the UE needs to be within the coverage area of ​​the serving cell. If the UE moves outside the coverage area of ​​the serving cell, a handover (also known as L3 mobility) is required to perform cell handover (e.g., RRC reset processing).

[0073] <Scenario 2>

[0074] In Scenario 2, L1 / L2 inter-cell mobility is applied (e.g., L1L1-triggered mobility (L1L2-triggered mobility (LTM))). With L1 / L2 inter-cell mobility, serving cell changes can be performed using functions such as beam control without RRC resetting. In other words, transmission and reception with candidate / additional cells can be performed without handover. Handover requires RRC reconnection, creating periods where data communication is impossible. Therefore, by applying L1 / L2 inter-cell mobility that does not require handover, data communication can continue even during serving cell changes. Scenario 2 can also be applied, for example, in Rel. 18 and later. In Scenario 2, for example, the following process is performed.

[0075] (1) In order to change the beam measurement / serving cell, the UE receives configuration information (e.g., SSB settings, etc.) related to cells (additional cells / candidate cells / target serving cells) with different PCIs from the serving cell (current serving cell).

[0076] (2) The UE performs beam measurements for cells using different PCIs and reports the measurement results to the serving cell.

[0077] (3) The UE can also receive the settings (serving cell / candidate cell settings) of cells with different PCIs through higher-layer signaling (e.g., RRC). That is, it can also make advance settings related to serving cell changes. This setting can be made together with the setting in (1) or separately.

[0078] (4) Based on the above report, the TCI status of cells with different PCIs can also be activated via L1 / L2 signaling according to the change of the serving cell. The activation of the TCI status and the change of the serving cell can also be carried out separately.

[0079] (5) The UE changes its serving cell (the concept of the serving cell) and uses a pre-set UE-specific channel and TCI state to start receiving / transmitting.

[0080] That is, in Scenario 2, the serving cell (the assumption of the serving cell in the UE) is updated via L1 / L2 signaling. Scenario 2 can also be applied in Rel.18.

[0081] Figure 1BThis diagram illustrates an example of UE movement in Rel.18. In Rel.18, the serving cell is switched via L1 / L2 (e.g., DCI / MAC CE). Here, it shows a case where a UE is switched from PCI#1, which corresponds to the current serving cell (e.g., the current serving cell), to PCI#3, which corresponds to the candidate cell (e.g., the target serving cell), via L1 / L2 signaling.

[0082] The UE can receive / transmit common channels (e.g., system information / paging / SMS) / UE-dedicated channels with the new serving cell (target serving cell #3). Thus, the UE can also exit the coverage area of ​​the previous serving cell, PCI #1.

[0083] (Setting up multiple candidate cells)

[0084] Figure 2 This is a diagram illustrating an example of the association between a serving cell and a candidate cell. Let SpCell#0, SCell#1, or SCell#2 be the serving cell (e.g., the current serving cell / a candidate cell to become the serving cell). Additionally, SpCell refers to a special cell (including the primary cell (PCell) and the primary / secondary cell (PSCell)). SCell refers to the secondary cell.

[0085] For SpCell / SCell, candidate cells (e.g., the target serving cell / candidate cells that are not the current serving cell) can also be associated. Figure 2 In this configuration, SpCell#0 is associated with candidate cells #0-1, #0-2, and #0-3. SCell#1 is associated with candidate cell #1-1. SCell#2 is associated with candidate cells #2-1 and #2-2. Similarly, for a serving cell, more than one candidate cell (e.g., the target serving cell / a candidate cell that is not the current serving cell) can be associated.

[0086] Alternatively, for each service cell, the candidate cells may not be explicitly associated.

[0087] Regarding the setting of candidate cells that become candidates in the case of changing serving cells, consider options 1 and 2 below.

[0088] <Option 1>

[0089] As with inter-cell mobility in Rel.17, the information in ServingCellConfig can also include information related to multiple candidate cells. In this case, multiple candidate cells need to share the same PDCCH / PDSCH / UL settings as the serving cell.

[0090] For example, in Rel.17 inter-cell mobility, "mimoParam-r17" is appended under ServingCellConfig, along with PCI configuration information. mimoParam-r17 can also contain additionalPCI-ToAddModList-r17, which is a list of additional SSBs with PCIs different from the serving cell's PCI. In candidate cells (additional cells, cells with additional PCIs), the same settings as the serving cell can be applied, except for some information.

[0091] <Option 2>

[0092] Multiple candidate cells can also be assigned complete settings corresponding to each cell (e.g., ServingCellConfig). That is, candidate cells may not share configuration information with the serving cell, but instead be assigned other settings (e.g., other higher-layer parameters). Because the UE is provided with complete settings for each candidate cell, it is able to communicate appropriately with the candidate cells.

[0093] For example, multiple candidate cells can be associated with each serving cell using a carrier aggregation (CA) configuration framework. Within the CA configuration framework, SpCells can be configured for each cell group, and multiple SCells can be added. For example, serving cells can be configured for each cell group based on L1 / L2 inter-cell mobility, and multiple candidate cells can be configured. Candidate cells can also be activated / deactivated via MAC CE. Alternatively, the TCI information corresponding to the candidate cell can be activated / deactivated via MAC CE, thereby activating / deactivating the candidate cell. This method is considered beneficial for reducing the complexity of UE operation.

[0094] Figure 3A This is a diagram representing the first example of option 2 for candidate cell settings. Figure 3A In the example, the common candidate cell pool used for cell handover in the MCG / SCG is applied to the candidate cells. That is, regardless of the frequency band, the candidate cells are processed as a pool (group).

[0095] Figure 3B This is a diagram representing the second example of option 2 for candidate cell settings. Figure 3B In this example, multiple cell groups are configured, enabling cell group handover via L1 / L2 signaling. Candidate cells are configured for each cell group, and the configuration for each group includes the indexes of the corresponding SpCell and SCell.

[0096] (Signaling used for service cell change instructions)

[0097] At least one of implicit and explicit signaling may also be used in the serving cell change instruction.

[0098] [Method 1]

[0099] In Method 1, the implicit signaling used for service cell change indication is described.

[0100] [[Option 1-1]]

[0101] When a specific Control Resource Set (CORESET) (e.g., at least one of CORESET#0, CH5Type0-CSS, or CH6 / CH7 / CH8 CSS) and one or more TCI states associated with a cell with a PCI different from the serving cell's PCI are indicated (activated) via MAC CE (for a specific CORESET, when one or more TCI states associated with a cell with a PCI different from the serving cell's PCI are indicated / activated via MAC CE), the UE can also determine to change the serving cell to another cell (cell x, a cell with a different PCI). That is, this activation can also implicitly indicate changing the serving cell to another cell.

[0102] In this case, the UE can also update the beams of other CORESET IDs, other CORESETs using CH6 / CH7 / CH8, or other CORESETs using CSS to the same TCI state as the activated TCI state mentioned above.

[0103] [[Options 1-2]]

[0104] When MAC CE activates / deactivates the TCI state of PDSCH, if all the TCI states activated through MAC CE are associated with the same cell x that has a PCI different from the serving cell's PCI, the UE can also determine that the serving cell has been changed to another cell (cell x). That is, this association can also implicitly indicate that the serving cell has been changed to another cell.

[0105] When this option is applied, if the NW (base station) does not change the serving cell, the MAC CE needs to include the TCI state associated with other cells (e.g., the current serving cell or a cell with a second different PCI) when activating the TCI state of the PDSCH associated with a cell with a different PCI.

[0106] [[Options 1-3]]

[0107] MAC CE activates / deactivates unified TCI states (e.g., corresponding to the unified TCI framework in Rel.17). When all activated unified TCI states are associated with the same cell x with different PCIs, the UE can also determine to change the serving cell to another cell (cell x). That is, this association can also implicitly indicate to change the serving cell to another cell.

[0108] [Method 2]

[0109] In Method 2, the explicit signaling used for serving cell change indication is described. Method 2 is applied, for example, in Scenario 2 described above.

[0110] [[Option 2-1]]

[0111] The following is an example of a serving cell change instruction. Additionally, the activation / deactivation of non-serving cells, changes to the serving cell, and sending / receiving data with other cells (non-serving cells) that have a physical cell ID different from the serving cell's physical cell ID can also be mutually modified.

[0112] The UE may also receive a new MAC CE for activating / deactivating a non-serving cell, containing at least one of the fields (1) to (3) below corresponding to the non-serving cell. Upon receiving this MAC CE, the UE may also determine that the serving cell has been changed to another cell (non-serving cell). Furthermore, the UE may control the transmission and reception of DL / UL signals with the non-serving cell based on this information. In addition, there may be one or more non-serving cells. In the example shown below, a MAC CE containing multiple fields representing multiple non-serving cell indices is applied.

[0113] (1) Service cell ID.

[0114] (2) BWP ID.

[0115] (3) The non-serving cell ID used for activation. The non-serving cell ID can also be replaced with any information corresponding to the non-serving cell (that can identify the non-serving cell).

[0116] As an example of (3), any of (3-1) to (3-5) can also be applied.

[0117] (3-1) PCI (PCI that is used directly). For example, 10 bits are used.

[0118] (3-2) Regeneration of the index (new ID) for non-serving cells. The new ID can also be associated with a portion of the PCI and is set only for the serving and non-serving cells used by the UE. The new ID reduces the number of bits compared to the PCI.

[0119] (3-3) CSI report setting ID (CSI-ReportConfigId) (the case where CSI-ReportConfig corresponds to one or more non-serving cells).

[0120] (3-4) CSI Resource Configuration ID (CSI-ResourceConfigId) (CSI-ResourceConfigId corresponds to one or more non-serving cells).

[0121] (3-5) shows the bitmap for the activation / deactivation of each non-serving cell. The size (number of bits) of the bitmap can also be the same as the number of non-serving cells set on the CC. For example, in the case of activating the second of three non-serving cells, it is set to "010".

[0122] At least one of the information contained in the MAC CE can also be included in the DCI. Alternatively, at least one of the serving cells activated via the MAC CE can also be indicated via the DCI. The MAC CE / DCI can also include a field indicating the TCI status / SSB / CSI-RS from a cell with a different PCI, enabling the identification of the DL beam monitored by the UE on the target cell (the changed serving cell). The UE can also use the TCI status / SSB / CSI-RS to generate and send a beam report (CSI report).

[0123] [[Option 2-2]]

[0124] The UE can also receive a MAC CE with a new 1-bit field "C" appended to the existing MAC CE. This field indicates whether a change of serving cell is being performed. The UE can also receive this MAC CE and determine whether to change the serving cell to another cell based on this field.

[0125] [[Options 2-3]]

[0126] For MAC CE in option 2-2, the fields representing the serving cell index / PCI / other ID (such as the new ID in option 2-1 above) and the TCI status / SSB / CSI-RS of the target cell (the changed serving cell) can also be included in MAC CE.

[0127] In this way, the indication for serving cell change is indicated via MAC CE / DCI, so the UE can make appropriate changes to the serving cell.

[0128] [Serving Cell Handover Example 1]

[0129] Figure 4 This is a diagram illustrating example 1 of serving cell handover. In Figure 4 The diagram shows how candidate cells are associated with each serving cell.

[0130] For example, in the serving cell SpCell#0 of the MCG / SCG, if candidate cell#0-2 is instructed to be changed to the serving cell (e.g., SpCell) via L1 / L2 signaling, candidate cell#0-2 becomes the new serving cell SpCell. That is, a handover is performed between serving cell SpCell#0 and candidate cell#0-2.

[0131] Furthermore, in the serving cell SCell#2 of the MCG / SCG, if candidate cell#2-1 is instructed to be changed to a serving cell (e.g., SCell) via L1 / L2 signaling, candidate cell#2-1 becomes the new serving cell SCell. That is, a handover is performed between serving cell SCell#2 and candidate cell#2-1.

[0132] [Serving Cell Handover Example 2]

[0133] The RRC / MAC CE can set a global candidate cell ID (cell#0,...,8) for each cell group, each band, each FR, and each UE. The UE can also be instructed to hand over the serving cell through this global candidate cell ID.

[0134] Figure 5 This is a diagram illustrating example 2 of a serving cell handover. (Compared to...) Figure 3A Similarly, by setting up a pool of multiple candidate cells, the serving cell can be switched to any (activated) candidate cell within the pool via L1 / L2 signaling. In this case, the set candidate cell can become either a SpCell or an SCell based on L1 / L2 signaling.

[0135] For example, in the serving cell SpCell#0 of the MCG / SCG, if candidate cell#4 is instructed to be changed to the serving cell (e.g., SpCell) via L1 / L2 signaling, candidate cell#4 becomes the new serving cell SpCell. That is, a handover is performed between serving cell SpCell#0 and candidate cell#4.

[0136] The UE can also receive indications of serving cell changes (here, the handover between serving cell SPCell#0 and candidate cell #4) via MAC CE / DCI. Then, it can determine that the indicated candidate cell #4 becomes the SpCell of the new cell group.

[0137] [Serving Cell Handover Example 3]

[0138] Figure 6 This is a diagram illustrating Example 3 of serving cell handover. Here, it shows the handover of a cell group instructed via L1 / L2 signaling.

[0139] The UE receives an indication of a change in the serving cell (here, a handover between a cell group containing SpCell#0 / #1 / #2 and a cell group containing candidate cells#0 / #1 / #2) via MAC CE / DCI. Then, a specific cell (here, candidate cell#0) within the cell group of the handover destination becomes the serving cell SpCell. This illustration shows the case where a specific cell becomes a candidate cell corresponding to the same frequency as SpCell, but it is not limited to this. A specific cell can also be indicated.

[0140] Furthermore, candidate cells within the same cell group as candidate cell #0 (here, candidate cell #1 and candidate cell #2) become SCells. That is, the serving cell group and the candidate cell group are switched via L1 / L2 signaling.

[0141] (An overview of L1L1-triggered mobility (L1L2-triggered mobility (LTM))

[0142] In L1L2-triggered mobility (LTM) supported after Rel.18, L1 inter-frequency measurement (e.g., L1 inter-frequency measurement) is also supported. Furthermore, DL synchronization / UL synchronization of candidate cells based at least on the SSB is also supported prior to the cell handover command.

[0143] Figure 7 This is a diagram illustrating the general concept of L1L2-triggered mobility (LTM). LTM and L1 / L2 inter-cell mobility can also be rewritten interchangeably.

[0144] During UE reconfiguration, the UE receives candidate cell configurations from the NW. UE reconfiguration includes T...RRC T proccesing1 / Tproccesing2 T RRC (For example, a maximum of 10ms) is the processing time for RRC reconfiguration (RRC reconfiguration) that carries candidate cell settings (candidate configurations). proccesing1 / Tproccesing2 (For example, a maximum of 20ms when used for the same FR and a maximum of 40ms when used for different FRs) are the times allocated for UE processing before and after the cell handover command. This includes processes such as L2 / 3 reconfiguration, RF retuning, baseband retuning, and security updates if necessary.

[0145] DL synchronization includes T search T Δ T margin T search (For example, 0ms when the cell is known, and a maximum of 60ms when the cell is unknown) is the time required to search for the target cell. Δ This is the time used for fine-grained tracking and acquisition of all timing information. T margin (For example, a maximum of 2ms) is the time used for post-processing of SSB and CSI-RS.

[0146] L1 measurement includes T meas (SMTC cycle (e.g., 20ms)). T meas It is the measurement delay from the time the target appears until the cell handover command is given.

[0147] UL synchronization includes T IU T RAR T cmd T IU (For example, a maximum of 15ms) is the indeterminate interruption time when an initial PRACH opportunity (occasion) is obtained in a new cell. T RAR (For example, a maximum of 4ms) is the RAR latency. T cmd (For example, a maximum of 5ms) is the processing time for L1 / L2 commands (HARQ and paging).

[0148] T cmd The T after that first-data It is the time when the UE performs its initial DL reception / UL transmission on the indicator beam of the target cell after RAR.

[0149] Figure 8 This diagram illustrates an example of a PDCCH-ordered RACH with RAR monitoring. Furthermore, in this disclosure, source cell and source cell group can be interchanged. Additionally, candidate cell and candidate cell group can also be interchanged.

[0150] The source cell can also send information related to the configuration of candidate cells (e.g., candidate cell configuration information) to the UE. Furthermore, the source cell can also send PDCCH commands (e.g., DCI format 1_0) used in PRACH triggering to the UE. Candidate cells (e.g., a candidate cell) / Random Access Hours (ROs) that can be indicated as the target of PRACH triggering / transmission can also be identified via PDCCH commands (order) (or DCI). For TAG / TA acquisition, the UE sends PRACH during the RACH process to the candidate cell based on the PDCCH commands.

[0151] Next, the source cell sends a Responding Message (RAR) to the UE for the PRACH. The RAR may also contain information related to the TA (e.g., a TA indication). The RAR (e.g., the PDSCH containing the RAR / the PDCCH that schedules the PDSCH) may also be monitored in a specific search space (e.g., the Common Search Space (CSS)) of a specific cell (e.g., SpCell) within the current serving cell (only within the Distributed Unit (DU)). Furthermore, TA adjustments (e.g., TA maintenance) are performed in the source cell.

[0152] Next, the source cell can also send a cell handover command to the UE. Furthermore, TA information can be moved from the source cell to / notified to the target cell. The UE can also control UL transmission based on the acquired TA after a cell handover. For example, if UL synchronization of all candidate cells is not completed after the initial cell handover, the UE can use the initial TA to perform the initial UL transmission.

[0153] Figure 9 This is a diagram illustrating an example of a PDCCH-ordered RACH (RACH based on PDCCH commands) without RAR monitoring. (About...) Figure 9 This is only to explain the relationship with Figure 8 The differences.

[0154] exist Figure 9In this example, the UE may be designated as the target of PRACH triggering / transmission from one or more candidate cells (e.g., multiple candidate cells) / random access opportunities through the PDCCH command used in PRAH triggering. For multiple TAG / TA acquisitions, the UE may also send PRACH during the RACH process to the candidate cells based on the PDCCH command. The source cell does not send a PRACH acknowledgment signal (e.g., RAR). The source cell may also use cell handover commands to indicate TA-related information to the UE (e.g., TA indication).

[0155] In this disclosure, RACH without RAR and RACH without RAR monitoring (e.g., RACH without RAR monitoring) can also be rewritten to each other. RACH can also be rewritten as PRACH transmission triggered by a PDCCH command. RACH / PRACH transmission without RAR monitoring can also be rewritten as RACH / PRACH transmission that does not require RAR monitoring, or RACH / PRACH transmission that does not request RAR monitoring.

[0156] (Unified / Common TCI Framework)

[0157] According to the unified TCI framework, multiple (UL / DL) channels / RS can be controlled through a common framework. Regarding the unified TCI framework, instead of specifying the TCI state or spatial relationship for each channel as in Rel.15, it can either indicate a common beam (common TCI state) and apply it to all channels of UL and DL, or apply the common beam used by UL to all channels of UL and apply the common beam used by DL to all channels of DL.

[0158] We are researching a common beam for both DL and UL, or a common beam for DL ​​and a common beam for UL (integrated as two common beams).

[0159] The UE can also envision the same TCI state for both UL and DL (joint TCI state, joint TCI pool, joint common TCI pool, joint TCI state set). The UE can also envision different TCI states for each of UL and DL (separate TCI state, separate TCI pool, UL separate TCI pool and DL separate TCI pool, separate common TCI pool, UL common TCI pool and DL common TCI pool).

[0160] UL and DL default beam alignment can also be achieved through MAC CE-based beam management (MAC CE level beam indication). The default TCI state of the PDSCH can also be updated and matched with the default UL beam (spatial relationship).

[0161] Alternatively, DCI-based beam management (DCI-level beam indication) can be used to indicate a common beam / unified TCI state based on the same TCI pool used by both UL and DL (joint common TCI pool, joint TCI pool, set). X (>1) TCI states can also be activated via MAC CE. UL / DL DCI can also select one of the X activated TCI states. The selected TCI state can also be applied to the channels / RS of both UL and DL.

[0162] A TCI pool (set) can be either multiple TCI states set via RRC parameters, or multiple TCI states activated by MAC CE from among multiple TCI states set via RRC parameters (activating a TCI state, activating a TCI pool, or a set). Each TCI state can also be a QCL type A / D RS. As a QCL type A / D RS, it can also be set as SSB, CSI-RS, or SRS.

[0163] The number of TCI states corresponding to each of more than one TRP can also be specified. For example, the number of TCI states (UL TCI states) applied in the UL channel / RS (N ≥ 1) and the number of TCI states (DL TCI states) applied in the DL channel / RS (M ≥ 1) can also be specified. At least one of N and M can also be notified / set / indicated to the UE via higher-layer signaling / physical layer signaling.

[0164] In this disclosure, when N = M = X (X is any integer), it can also be intended to notify / set / indicate X TCI states (combined TCI states) common to UL and DL (corresponding to X TRPs) to the UE. Furthermore, when N = X (X is any integer) and M = Y (Y is any integer, or Y = X), it can also be intended to notify / set / indicate X UL TCI states (corresponding to X TRPs) and Y DL TCI states (corresponding to Y TRPs) separately to the UE (i.e., independent TCI states).

[0165] For example, when N=M=1 is recorded, it can also mean to notify / set / indicate a TCI state common to the UL and DL for a single TRP (the joint TCI state for a single TRP) to the UE.

[0166] Furthermore, for example, when N=1 and M=1 is recorded, it may also mean that the UE is separately notified / set / indicated a UL TCI state and a DL TCI state (an independent TCI state for a single TRP).

[0167] Furthermore, for example, when N=M=2 is recorded, it may also mean to notify / set / indicate to the UE the multiple (two) TCI states common to the UL and DL for multiple (two) TRPs (joint TCI states for multiple TRPs).

[0168] Furthermore, for example, when N=2 and M=2 are recorded, it may also mean to notify / set / indicate multiple (two) UL TCI states and multiple (two) DL TCI states (independent TCI states for multiple TRPs) to the UE.

[0169] Furthermore, the above example illustrates the case where N and M have values ​​of 1 or 2, but the values ​​of N and M can also be 3 or higher, and N and M can also be different.

[0170] In Rel. 17, support for N=M=1 is being investigated. For example, it is also possible to support indicating a common beam (e.g., a common beam) via RRC / MAC CE / DCI, which is applied to the channels / reference signals of multiple DL / UL. Furthermore, support for other scenarios is being investigated in Rel. 18 and later.

[0171] Figure 10A as well as Figure 10B An example of the unified TCI framework is shown. Figure 10A An example of a joint DL / UL TCI state is shown. Figure 10B An example of an independent TCI state (e.g., Separate TCI (DLTCI state and UL TCI state)) is shown.

[0172] exist Figure 10AIn the example, the RRC parameter (information element) sets multiple TCI states for both DL and UL. In this disclosure, the TCI state set via the RRC parameter can also be referred to as a configured TCI state or a TCI state setting (e.g., configured TCI states). The MAC CE can also activate multiple TCI states among the configured TCI states. The DCI can also indicate one of the activated TCI states. In this disclosure, the TCI state indicated via the DCI can also be referred to as an indicated TCI state or an indicated TCI state (e.g., indicated TCI state).

[0173] A DCI can be either a UL DCI (e.g., the DCI used for PUSCH scheduling) or a DL DCI (e.g., the DCI used for PDSCH scheduling). The indicated TCI state can also be applied to at least one (or all) of the UL / DL channels / RS. A DCI can also indicate both the UL TCI and the DL TCI.

[0174] In the example in the diagram, a point can be either a TCI state applied to both UL and DL, or two TCI states applied to UL and DL respectively.

[0175] At least one of the multiple TCI states set by RRC parameters and the multiple TCI states activated by MAC CE can also be referred to as a TCI pool (common TCI pool, joint TCI pool, TCI state pool). Multiple TCI states activated by MAC CE can also be referred to as an activated TCI pool (activated common TCI pool).

[0176] Furthermore, in this disclosure, the high-level parameters (RRC parameters) for setting multiple TCI states can also be referred to as setting information for setting multiple TCI states, or simply as "setting information". Additionally, in this disclosure, the use of a DCI to indicate one of multiple TCI states can be either receiving indication information contained in the DCI for indicating one of the multiple TCI states, or simply receiving "indication information".

[0177] exist Figure 10B In the example, the RRC parameter sets multiple TCI states (joint common TCI pool) for both DL and UL. MAC CE can also activate multiple TCI states among the set TCI states (activate TCI pool). It can also set / activate separate TCI pools corresponding to UL and DL respectively.

[0178] The DL DCI or new DCI format can also select (indicate) more than one (e.g., one) TCI state. The selected TCI state can also be applied to more than one (or all) DL channels / RS. The DL channel can also be PDCCH / PDSCH / CSI-RS. The UE can also use the Rel.16 TCI state operation (TCI framework) to determine the TCI state of each DL channel / RS. The UL DCI or new DCI format can also select (indicate) more than one (e.g., one) TCI state. The selected TCI state can also be applied to more than one (or all) UL channels / RS. The UL channel can also be PUSCH / SRS / PUCCH. Thus, different DCIs can separately indicate the UL TCI and the DL DCI.

[0179] From Rel.17 NR onwards, it is envisioned that support will be provided for beam activation / indication to TCI states associated with different physical cell identifiers (PCIs) via MAC CE / DCI. Furthermore, from Rel.18 NR onwards, it is envisioned that support will be provided for indicating changes of serving cells to cells with different PCIs via MAC CE / DCI.

[0180] Figure 10A The method for setting / indicating the TCI status (e.g., combined DL / UL TCI status) and Figure 10B The application of TCI status (e.g., standalone TCI status) setting / indication method can also be switched. Whether to apply the joint DL / UL TCI status or the standalone TCI status can also be set from the base station to the UE via higher-layer signaling.

[0181] (Indicates TCI status / Sets TCI status)

[0182] Regarding the Rel.17 TCI state, the unified / common TCI state can also refer to the Rel.17 TCI state indicated by using (Rel.17) DCI / MACCE / RRC (indicated Rel.17 TCI state).

[0183] In this disclosure, the Rel.17 TCI state, the indicated TCI state (indicated TCI state), the unified / common TCI state, the TCI state applied to multiple signals (channel / RS), and the TCI state used for multiple signals (channel / RS) can also be overwritten with each other.

[0184] Regarding the indication of the Rel.17 TCI status, it can also be shared with the UE-specific receive, dynamic authorization (DCI) / configured authorization PUSCH in the PDSCH / PDCCH (updated using Rel.17 DCI / MAC CE / RRC), and at least one of multiple (e.g., all) dedicated PUCCH resources. The TCI status indicated by DCI / MAC CE / RRC can also be referred to as the indicated TCI status or the unified TCI status.

[0185] Regarding the Rel.17 TCI state, a TCI state other than the unified TCI state can also refer to a Rel.17 TCI state configured using (Rel.17) MAC CE / RRC (configured Rel.17 TCI state). In this disclosure, the configured Rel.17 TCI state, the configured TCI state, the TCI state other than the unified TCI state, and the TCI state applied to a specific type of signal (channel / RS) can also be interchanged.

[0186] Regarding setting the Rel.17 TCI state, it can be independent of sharing with at least one of the UE-specific receive, dynamic license (DCI) / configured license PUSCH, and multiple (e.g., all) dedicated PUCCH resources in the PDSCH / PDCCH (updated using Rel.17 DCI / MAC CE / RRC). Setting the Rel.17 TCI state can also be structured such that it is set per CORESET / per resource / per resource set via RRC / MAC CE, and the setting of the Rel.17 TCI state will not be updated even if the aforementioned indication of the Rel.17 TCI state (public TCI state) is updated.

[0187] We are investigating the application of Rel.17 TCI status indication for UE-specific channels / signals (RS). Additionally, we are investigating the application of Rel.17 TCI status indication for non-UE-specific channels / signals, and which Rel.17 TCI status to set, using higher-layer signaling (RRC signaling) to notify the UE.

[0188] The study is underway to set the RRC parameters associated with setting the Rel.17 TCI state (TCI state ID) to the same structure as the RRC parameters for the TCI state in Rel.15 / 16. The study is also underway to investigate the use of RRC / MAC CE to set / indicate the Rel.17 TCI state per CORESET / per resource / per resource set. Furthermore, the study is underway to investigate how the UE will determine this setting / indication based on specific parameters.

[0189] Research is underway to separately update the TCI indication state and the TCI setting state for the UE. For example, for the UE, if the unified TCI state indicating the TCI state is updated, updating the TCI setting state may not be necessary. Furthermore, research is underway to allow the UE to determine the update based on specific parameters.

[0190] In addition, research is underway on using higher-level signaling (RRC / MAC CE) to switch whether to apply the Rel.17 TCI state indication for PDCCH / PDSCH or not to apply the Rel.17 TCI state indication (applying the Rel.17 TCI state setting, or applying a TCI state that is set separately from the Rel.17 TCI state indication).

[0191] In addition, regarding intra-cell beam indication (TCI status indication), research is underway to support Rel.17 TCI status indication for UE-specific CORESET and PDSCH associated with that CORESET, as well as non-UE-specific CORESET and PDSCH associated with that CORESET.

[0192] In addition, regarding inter-cell beam indication (e.g., L1 / L2 inter-cell mobility), research is underway on UE-specific CORESETs and PDSCHs associated with those CORESETs to support indication of Rel.17 TCI status.

[0193] In Rel.15, whether CORESET#0 indicates a TCI state depends on the base station implementation. In Rel.15, for CORESET#0 that is indicated with a TCI state, that indicated TCI state is applied. For CORESET#0 that is not indicated with a TCI state, the QCL of the SSB selected in the most recent (most recent) PRACH transmission is applied.

[0194] In the unified TCI state framework after Rel.17, the TCI state related to CORESET#0 is being studied.

[0195] For example, within the framework of the unified TCI state after Rel.17, the Rel.17 TCI state indication for CORESET#0 could be configured by RRC for each CORESET to indicate whether the Rel-17 TCI state associated with the serving cell is applied. If not applied, the existing MAC CE / RACH signaling mechanism would be utilized.

[0196] Additionally, the CSI-RS associated with the Rel.17 TCI state applied to CORESET#0 can also perform QCL with the SSB associated with the serving cell PCI (physical cell ID) (same as Rel.15).

[0197] Alternatively, for CORESET#0, CORESETs with a common search space (CSS), and CORESETs with both CSS and a UE-specific search space (USS), the RRC parameter can be used to set whether to comply with the Rel.17 TCI state instruction. If the Rel.17 TCI state instruction is not set for a particular CORESET, the Rel.17 TCI state instruction can be set for that CORESET.

[0198] Alternatively, the RRC parameter can be used to set whether to follow the Rel.17 TCI state instruction for each non-UE-dedicated channel / RS (other than CORESET) on a per-channel / resource / resource-set basis. If the Rel.17 TCI state instruction is not set for that channel / resource / resource-set, the Rel.17 TCI state instruction can also be applied to that channel / resource / resource-set.

[0199] (Channel / RS whose TCI status is indicated by the application)

[0200] The "indicated TCI state" based on MAC CE / DCI can also be applied to the following channels / RS.

[0201] [PDCCH]

[0202] • When CORESET 0 is set to followUnifiedTCIState, the indicated TCI state is applied. Otherwise, the Rel.15 specification is applied for that CORESET. That is, CORESET 0 follows the TCI state activated by MAC CE or performs QCL with SSB.

[0203] • For CORESETs with USS / CSS type 3 and index other than 0, always apply the TCI indicator status.

[0204] • If a CORESET other than index 0 is configured to conform to a uniform TCI state for at least CSS types other than CSS type 3, the indicated TCI state is applied. Otherwise, the configured TCI state is applied to that CORESET.

[0205] [PDSCH]

[0206] • Always apply the TCI status indicator to all UE-dedicated PDSCHs.

[0207] • When a non-UE-dedicated PDSCH (a PDSCH scheduled via DCI within the CSS) has its followUnifiedTCIState set (for the CORESET of the PDCCH that schedules the PDSCH), the indicator TCI State can also be applied. Otherwise, the set TCI State for that PDSCH is applied to that PDSCH. If followUnifiedTCIState is not set for a PDSCH, whether a non-UE-dedicated PDSCH follows the indicator TCI State can be determined based on whether followUnifiedTCIState is set for the CORESET used in scheduling that PDSCH.

[0208] [CSI-RS]

[0209] • When the A-CSI-RS used for CSI acquisition or beam management is set to followUnifiedTCIState (for the CORESET of the PDCCH that triggers the A-CSI-RS), the application indicates the TCI state. For other CSI-RS, the application sets the TCI state ("configured TCI state") for that CSI-RS.

[0210] [PUCCH]

[0211] • Always apply the indicator TCI status for all dedicated PUCCH resources.

[0212] [PUSCH]

[0213] • For dynamic / configured license PUSCH, always apply an indication of TCI status.

[0214] [SRS]

[0215] • When the SRS resource set for A-SRS used for beam management and A / SP / P-SRS used for codebook (CB) / non-codebook (NCB) / antenna switching is set to follow a unified TCI state, the indicated TCI state is applied. For other SRS, the TCI state set within this SRS resource set is applied.

[0216] (analyze)

[0217] As mentioned above, in Rel.18 and later, it is envisioned that support for L1 / L2 inter-cell mobility (e.g., L1L2-triggered mobility (LTM)) is possible. In this case, it is envisioned that each TCI state, containing up to two QCL types (e.g., qcl-types), and the source RS for each QCL type within the QCL information (e.g., QCL-Info) of the TCI state, are provided at least based on the RS settings used for LTM.

[0218] Figure 11 This diagram illustrates an example of a TCI state information element (e.g., a TCI-State information element) supported prior to Rel.17. Through this TCI state information element (or, RRC parameters), one or two DL reference signals can also be associated with the corresponding QCL type.

[0219] In LTM supported by Rel.18, for L1 measurements / L1 beam reporting for candidate cells (e.g., non-serving cells before receiving a cell handover command), it is also envisioned to utilize SSB (e.g., only SSB-based L1 measurements / L1 beam reporting is supported). Alternatively, in LTM, it is also envisioned to additionally support CSI-RS measurements for candidate cells.

[0220] In Rel. 15-17, setting SSB as the QCL source (or QCL source RS) for the TCI state of PDCCH / PDSCH is not supported. In Rel. 15-17, TRS / CSI-RS can be set as the QCL source for the DMRS of PDCCH / PDSCH, and SSB can be set as the QCL source for TRS / CSI-RS.

[0221] In LTM versions after Rel.18, it is envisioned that TCI states (e.g., each TCI state with up to two QCL types (pcl-types) and at least one source RS of the QCL type for the TCI state) will be provided based on the RS settings used by LTM. However, TCI states supporting candidate cells have not been adequately studied. Without proper application of TCI states for candidate cells (e.g., QCL type / QCL type source RS, etc.), there are concerns about degradation in communication quality.

[0222] Therefore, the inventors of this invention studied the TCI state under the condition of supporting / applying LTM and came up with this embodiment.

[0223] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The wireless communication methods involved in each embodiment can be applied individually or in combination.

[0224] In this disclosure, "A / B" and "at least one of A and B" may be rewritten as each other. In addition, in this disclosure, "A / B / C" may also mean "at least one of A, B and C".

[0225] In this disclosure, terms such as notification, activation, deactivation, indication (or indication), selection, configuration, update, and determination can be overridden. Similarly, terms such as support, control, ability to control, operation, and ability to operate can also be overridden.

[0226] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-level parameters, fields, Information Elements (IE), settings, etc., can also be modified interchangeably. In this disclosure, Medium Access Control (MAC) Control Elements (CE), update commands, activation / deactivation commands, etc., can also be modified interchangeably.

[0227] In this disclosure, higher-layer signaling may be, for example, any one or a combination of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., positioning protocol messages (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP) messages, messages from the core network), etc.)

[0228] In this disclosure, MAC signaling may also use, for example, a MAC Control Element (MACCE) or a MAC Protocol Data Unit (PDU). Broadcast information may also be, for example, a Master Information Block (MIB), a System Information Block (SIB), a Minimum System Information (Remaining Minimum System Information (RMSI)), or Other System Information (OSI).

[0229] In this disclosure, physical layer signaling may also be, for example, downlink control information (DCI), uplink control information (UCI), etc.

[0230] In this disclosure, indexes, identifiers (IDs), indicators, resource IDs, etc., can be interchanged. In this disclosure, sequences, lists, sets, groups, clusters, subsets, etc., can also be interchanged.

[0231] In this disclosure, the following terms are used: panel, UE panel, panel group, beam, beam group, precoder, uplink (UL) transmitting entity, transmission / reception point (TRP), base station, spatial relation information (SRI), spatial relation, SRS resource indicator (SRI), control resource set (CORESET), physical downlink shared channel (PDSCH), codeword (CW), transport block (TB), reference signal (RS), antenna port (e.g., demodulation reference signal (DMRS)) port, antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, code division multiplexing (CDM) group, reference signal group, CORESET group, physical uplink control channel). Channel (PUCCH) groups, PUCCH resource groups, resources (e.g., reference signal resources, SRS resources), resource sets (e.g., reference signal resource sets), CORESET pools, downlink transmission configuration indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, quasi-co-location (QCL) and QCL concept can also be rewritten.

[0232] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) can be interchanged. "Spatial relationship information" can also be interchanged with "a set of spatial relationship information," "one or more spatial relationship information," etc. The TCI state and TCI can also be interchanged.

[0233] Furthermore, panel identifiers (IDs) and panels can be interchanged. That is, TRP IDs and TRPs, CORESET group IDs and CORESET groups, etc., can also be interchanged.

[0234] In this disclosure, the TRP, the transmitting point, the panel, the DMRS port group, the CORESET pool, and one of the two TCI states associated with a code point in the TCI field can also be overwritten.

[0235] In this disclosure, the terms "channel," "signal," and "channel / signal" can be interchanged. Similarly, the terms "DL channel," "DL signal," "DL signal / channel," "DL signal / channel transmission / reception," "DL reception," and "DL transmission" can also be interchanged. Furthermore, the terms "UL channel," "UL signal," "UL signal / channel," "UL signal / channel transmission / reception," "UL reception," and "UL transmission" can also be interchanged.

[0236] In this disclosure, applying the TCI state / QCL concept to each channel / signal / resource can also mean applying the TCI state / QCL concept to the transmission and reception of each channel / signal / resource.

[0237] (Wireless communication method)

[0238] The UE may also receive information related to LTM settings (e.g., higher-layer parameter LTMConf-r18). This LTM setting information may also include information about candidate cells that will become handover candidates. In this disclosure, candidate cells are not limited to non-serving cells (e.g., non-serving cells before the cell handover command is received), but may also include serving cells.

[0239] For DMRS of DL channels (e.g., PDCCH / PDSCH), the UE can also be envisioned as being indicated with a specific QCL type (e.g., quasi co-location type(s)) by the TCI state indicated from the base station.

[0240] The TCI state indicated from the base station can also be indicated via DCI / MAC CE / RRC. If LTM is configured / supported, the TCI state can also be indicated via cell handover commands. If the TCI state indicated from the base station includes a uniform TCI state (e.g., the indicated TCI state), the indicated TCI state can be applied to multiple channels in the target cell (or, candidate cell).

[0241] In the following description, the RS of QCL type A / QCL type D is described through the TCI state (or the indicated TCI state), but the QCL types that can be applied to this embodiment are not limited to this, and can also be applied to other QCL types (e.g., QCL type B / QCL type C). Therefore, QCL type A in the following embodiments can also be interchanged with the first QCL type, and QCL type D can also be interchanged with the second QCL type.

[0242] The following description uses the case where LTM is configured as an example, but this implementation is not limited to this. It can also be applied when a PCI different from that of the serving cell is configured.

[0243] The QCL rules / QCL types shown in the following implementation can also be applied to both cases where a uniform TCI state (e.g., dl-OrJointTCI-StateList) is not set and cases where a uniform TCI state (e.g., dl-OrJointTCI-StateList) is set.

[0244] The following description explains the QCL type / QCL rules for DMRS for specific DL channels (e.g., PDCCH / PDSCH), but the applicable channels / signals are not limited to these. For example, DMRS can also be applied to specific UL channels (e.g., PUCCH / PUSCH, or PUCCH / PUSCH with uniform TCI status).

[0245] <First Implementation Method>

[0246] The first implementation relates to QCL rules in cases where it is impossible to set a synchronization signal block (e.g., SSB) for the TCI state of a specific DL channel's DMRS.

[0247] A specific DL channel can also be at least one of PDCCH and PDSCH. In the following description, PDCCH / PDSCH is used as an example of a specific DL channel, but it is not limited to this.

[0248] If the SSB cannot set the TCI status of the DMRS of the PDCCH / PDSCH (or the SSB is not the QCL source of the DMRS of the PDCCH / PDSCH), then the TRS / CSI-RS can become the QCL source of the DMRS of the PDCCH / PDSCH (e.g., QCL source), and the SSB can become the QCL source of the TRS / CSI-RS (see reference). Figure 12 ).

[0249] exist Figure 12An example is shown below: For candidate cell #1, the TRS / CSI-RS becomes the QCL source (e.g., QCL source) of the DMRS of the PDCCH / PDSCH, and the SSB becomes the QCL source of the TRS / CSI-RS. Candidate cell #1 can also be a cell associated with a PCI different from that of the serving cell.

[0250] In this case, at least one of the following QCL rules 1-1 to 1-3 may also be applied / supported. In this disclosure, QCL rules can also be rewritten with cases.

[0251] The UE can also be envisioned as being indicated by a TCI state from the network (e.g., a base station), and thus by one of the QCL types in QCL rules 1-1 to 1-3. The TCI state indicated from the base station can also be indicated via DCI / MAC CE / RRC. QCL rules 1-1 to 1-3 can also be applied / supported in both cases where a uniform TCI state (e.g., dl-OrJointTCI-StateList) is not set, and cases where a uniform TCI state (e.g., dl-OrJointTCI-StateList) is set (or one of these cases).

[0252] QCL rules 1-1 to 1-3 can be supported, or one or two of them can be supported. The applied / supported QCL rules can be defined in the specification or set by the base station to the UE via RRC parameters. The applicable QCL rules are not limited to these; QCL type A RS of a certain QCL rule and QCL type D RS of other QCL rules can also be combined for application.

[0253] [QCL Rule 1-1]

[0254] QCL rule 1-1 can also be defined as follows.

[0255] QCL type A RS: TRS (with a different PCI)

[0256] QCL Type D RS: Same CSI-RS resource as QCL Type A RS

[0257] The RS corresponding to QCL Type A RS can also be a CSI-RS with specific higher-layer parameters (e.g., trs-Info) set (or a CSI-RS within a CSI-RS resource set with trs-Info set). Furthermore, the RS corresponding to QCL Type A RS can also be set to a PCI different from the serving cell's PCI (e.g., the PCI of a candidate cell / additional cell / non-serving cell) (see reference). Figure 13A When LTM is configured / applied, RS resource configuration (e.g., CSI-RS resource configuration) can also be supported on a per-candidate-cell basis.

[0258] For example, the reference RS (e.g., TRS / CSI-RS) corresponding to QCL type A / QCL type D can also be a CSI-RS with a PCI different from the PCI of the serving cell. That is, as a reference RS (e.g., TRS / CSI-RS) corresponding to QCL type A / QCL type D, in addition to (or as a substitute for) the CSI-RS corresponding to the PCI of the serving cell, a CSI-RS with a PCI different from the PCI of the serving cell can also be used.

[0259] When LTM is set / applied, the UE can also be envisioned as: a quasi-co-location type with a TRS (e.g., QCL type A) indicating a PCI different from the PCI of the serving cell, and a CSI-RS (e.g., QCL type D) that is the same as QCL type A, as the TCI state (e.g., TCI-State or indicated DLorJointTCIState) indicated from the base station.

[0260] As an example, type A RS and type D RS of QCL rule 1-1 can also be defined as follows.

[0261] Type A RS is a CSI-RS resource with a non-zero power CSI-RS resource set (e.g., NZP-CSI-RS-ResourceSet) configured with higher-layer parameters (e.g., trs-Info). Type D RS is the same CSI-RS resource as Type A RS. Reference RS can also be a CSI-RS with a PCI different from the PCI of the serving cell.

[0262] [QCL Rules 1-2]

[0263] QCL rules 1-2 can also be defined as follows.

[0264] QCL type A RS: TRS (with a different PCI)

[0265] QCL type D RS: CSI-RS with repetition (with a different PCI)

[0266] The RS corresponding to QCL type A RS can also be set for a PCI that is different from the PCI of the serving cell (e.g., the PCI of the candidate cell / additional cell / non-serving cell) (see reference). Figure 13B When LTM is configured / applied, RS resource configuration (e.g., CSI-RS resource configuration) can also be supported on a per-candidate-cell basis.

[0267] The RS corresponding to QCL type D RS can also be a CSI-RS with high-level parameters (e.g., repetition) set to relate to repetition.

[0268] For example, the reference RS (e.g., TRS / CSI-RS) corresponding to QCL type A / QCL type D can also be a CSI-RS with a PCI different from the PCI of the serving cell. That is, as a reference RS (e.g., TRS / CSI-RS) corresponding to QCL type A / QCL type D, in addition to using a CSI-RS corresponding to the PCI of the serving cell (or, as a substitute for it), a CSI-RS with a PCI different from the PCI of the serving cell can also be used.

[0269] In this case, if multiple (e.g., two) reference RSs have different PCIs from the serving cell, the different PCIs can also be the same PCI. That is, two reference RSs (e.g., resource RSs) can also be configured to be associated with the same candidate cell (or non-serving cell). The two reference RSs can also be an RS corresponding to a first QCL type (e.g., QCL type A) and an RS corresponding to a second QCL type (e.g., QCL type D).

[0270] When LTM is set / applied, the UE can also be envisioned as: a quasi-co-location type of TCI state indicated from the base station (e.g., TCI-State, or indicated DLorJointTCIState), a TRS (e.g., QCL type A) with a PCI different from the PCI of the serving cell, and a CSI-RS corresponding to a PCI different from the PCI of the serving cell and set to repetition.

[0271] As an example, type A RS and type D RS of QCL rule 1-2 can also be defined as follows.

[0272] Alternatively, a Type A RS can be a CSI-RS resource with a non-zero power CSI-RS resource set (e.g., NZP-CSI-RS-ResourceSet) configured with higher-layer parameters (e.g., trs-Info), and a Type D RS can be a CSI-RS resource with a non-zero power CSI-RS resource set (e.g., NZP-CSI-RS-ResourceSet) configured with higher-layer parameters repeating. The reference RS can also be a CSI-RS with a PCI different from the serving cell's PCI. If both reference RSs have a different PCI from the serving cell, the different PCI can be set to the same PCI.

[0273] [QCL Rules 1-3]

[0274] QCL rules 1-3 can also be defined as follows.

[0275] QCL Type A RS: CSI-RS without TRS-Info and repetition (with a different PCI)

[0276] QCL Type D RS: Same CSI-RS resource as QCL Type A RS

[0277] The RS corresponding to QCL type A RS can also be a CSI-RS that has not been configured with higher-level parameters related to TRS (e.g., TRS-Info) or higher-level parameters related to repetition (e.g., repetition). Furthermore, the RS corresponding to QCL type A RS can also be configured to correspond to a PCI different from the serving cell's PCI (e.g., the PCI of a candidate cell / additional cell / non-serving cell) (see reference). Figure 13C When LTM is configured / applied, RS resource configuration (e.g., CSI-RS resource configuration) can also be supported on a per-candidate-cell basis.

[0278] For example, the reference RS (e.g., TRS / CSI-RS) corresponding to QCL type A / QCL type D can also be a CSI-RS with a PCI different from the PCI of the serving cell. That is, as a reference RS (e.g., TRS / CSI-RS) corresponding to QCL type A / QCL type D, in addition to using a CSI-RS corresponding to the PCI of the serving cell (or, as a substitute for it), a CSI-RS with a PCI different from the PCI of the serving cell can also be used.

[0279] When LTM is set / applied, the UE can also be envisioned as: a quasi-co-address type with a PCI (e.g., QCL type A) indicated by a PCI state (e.g., TCI-State, or indicated DLorJointTCIState) from the base station, a CSI-RS with a PCI different from the PCI of the serving cell, and a CSI-RS with the same PCI as QCL type A (e.g., QCL type D).

[0280] As an example, type A RS and type D RS of QCL rules 1-3 can also be defined as follows.

[0281] Alternatively, a Type A RS can be a CSI-RS resource of a non-zero power CSI-RS resource set (e.g., NZP-CSI-RS-ResourceSet) with no higher-level parameters (e.g., trs-Info) and no higher-level parameters (e.g., repetition). A Type D RS can be the same CSI-RS resource as a Type A RS. A reference RS can also be a CSI-RS with a PCI different from the PCI of the serving cell.

[0282] In QCL rules 1-1 to 1-3, the UE may also assume that the center frequency, SCS, and SFN offsets are the same for SSBs (or SS / PBCH blocks) originating from the serving cell and SSBs with a different PCI from the serving cell. In cases where inter-cell LTM (e.g., inter-frequency LTM) is not supported, in QCL rules 1-1 to 1-3, the UE may also not assume that the center frequency, SCS, and SFN offsets are the same for SSBs (or SS / PBCH blocks) originating from the serving cell and SSBs with a different PCI from the serving cell.

[0283] [Support for the new QCL type]

[0284] The QCL type (e.g., a new QCL type) in at least one of QCL rules 1-1 to 1-3 can also be subject to at least one of the following conditions 1-1 to 1-4.

[0285] Condition 1-1

[0286] QCL rules 1-1 to QCL rules 1-3 (or, new QCL types) may also be supported only for QCLs of Rel.15 / 16 or QCLs of Rel.17 (e.g., Unified TCI).

[0287] Conditions 1-2

[0288] QCL rules 1-1 to 1-3 (or, the new QCL type) may also be supported only for RSs associated with a PCI different from that of the serving cell (e.g., reference RS / resource RS). For example, QCL rules 1-1 to 1-3 (or, the new QCL type) may also be applied if an LTM supported after Rel.18 is set (or if a reference RS / resource RS is associated with a PCI different from that of the serving cell).

[0289] On the other hand, for other scenarios, the structure can also be configured to not support QCL rules 1-1 to QCL rules 1-3 (or, new QCL types). Other scenarios could include cases where the reference RS / resource RS is not associated with a PCI different from the serving cell, or cases where there is no reference RS / resource RS associated with a PCI different from the serving cell.

[0290] Conditions 1-3

[0291] QCL rules 1-1 to QCL rules 1-3 (or, new QCL types) may be supported only for at least one of the following scenarios: LTM is set as supported in Rel.18 and ICBM is set as supported in Rel.17. LTM settings supported in Rel.18 and later may also involve associating a reference RS / resource RS with a PCI different from the serving cell. ICBM settings supported in Rel.17 may also involve associating a reference RS / resource RS with a PCI different from the serving cell, and the UE envisions the same center frequency, SCS, and SFN offset for the SSB of the serving cell and the SSB corresponding to the PCI different from that serving cell.

[0292] On the other hand, for other scenarios, the structure can also be configured to not support QCL rules 1-1 to QCL rules 1-3 (or, new QCL types). Other scenarios could include cases where the reference RS / resource RS is not associated with a PCI different from the serving cell, or cases where there is no reference RS / resource RS associated with a PCI different from the serving cell.

[0293] Conditions 1-4

[0294] QCL rules 1-1 to QCL rules 1-3 (or, new QCL types) can also be supported in any case.

[0295] [UE Capability Information]

[0296] UE capabilities can also be introduced / supported for the new QCL types in QCL rules 1-1 to QCL rules 1-3. UE capabilities can also be introduced / supported for situations where QCL rules 1-1 to QCL rules 1-3 (or the new QCL types) can be applied.

[0297] Alternatively, a dedicated UE capability for the new QCL type may not be defined. In this case, all UEs supporting LTM can also support the new QCL type (or at least one of QCL rules 1-1 to QCL rules 1-3) as the default. Thus, even when inter-frequency LTM is supported, the appropriate QCL rules (or QCL types) can be utilized.

[0298] <Second Implementation Method>

[0299] The second implementation relates to QCL rules where a synchronization signal block (e.g., SSB) can be set for the TCI state of a specific DL channel's DMRS, or where setting an SSB for the TCI state of a specific DL channel's DMRS is supported.

[0300] A specific DL channel can also be at least one of PDCCH and PDSCH. In the following description, PDCCH / PDSCH is used as an example of a specific DL channel, but it is not limited to this.

[0301] If the SSB can be set (or supported to be set) to the TCI state of the DMRS of the PDCCH / PDSCH, the SSB can be set as the QCL source (e.g., QCL source) of the DMRS of the PDCCH / PDSCH (see reference). Figure 14 ).

[0302] exist Figure 14 The diagram illustrates an example where, for candidate cell #1, the SSB becomes the QCL source (e.g., QCL source) of the DMRS for the PDCCH / PDSCH. Candidate cell #1 can also be a cell associated with a PCI different from that of the serving cell.

[0303] When it is possible to set the SSB to the TCI state of the DMRS of the PDCCH / PDSCH, the SSB can be applied to one of the RSs of multiple QCL types (e.g., type A and type D) or to both.

[0304] When the SSB can be set to the TCI state of the DMRS of the PDCCH / PDSCH, at least one of the following QCL rules 2-1 to QCL rules 2-5 can also be applied / supported. The UE can also be envisioned as being indicated with at least one of the quasi-co-location types (QCL types) of QCL rules 2-1 to QCL rules 2-5 by the TCI state indicated from the network (e.g., a base station). The TCI state indicated from the base station can also be indicated via DCI / RRC. QCL rules 2-1 to QCL rules 2-5 can also be applied / supported in both cases where a unified TCI state (e.g., dl-OrJointTCI-StateList) is not set, and cases where a unified TCI state (e.g., dl-OrJointTCI-StateList) is set (or one of these cases).

[0305] In QCL rules 2-1 to QCL rules 2-5, either all or one or more rules can be supported. The applied / supported QCL rules can be defined in the specification or set by the base station to the UE via RRC parameters. The applicable QCL rules are not limited to these; QCL type A RS of a certain QCL rule and QCL type D RS of other QCL rules can also be combined for application.

[0306] [QCL Rule 2-1]

[0307] QCL rule 2-1 can also be defined as follows.

[0308] QCL type A RS: TRS (with a different PCI)

[0309] QCL type D RS:SSB (with a different PCI)

[0310] The RS corresponding to QCL Type A RS can also be a CSI-RS with specific higher-layer parameters (e.g., trs-Info) set (or a CSI-RS within a CSI-RS resource set with trs-Info set). Furthermore, the RS corresponding to QCL Type A RS can also be set to a PCI different from the serving cell's PCI (e.g., the PCI of a candidate cell / additional cell / non-serving cell) (see reference). Figure 15A When LTM is configured / applied, RS resource configuration (e.g., CSI-RS resource configuration) can also be supported on a per-candidate-cell basis.

[0311] The RS corresponding to QCL type D RS can also be an SSB. Furthermore, the RS corresponding to QCL type D RS can also be configured to correspond to a PCI different from the serving cell's PCI (e.g., the PCI of a candidate cell / additional cell / non-serving cell). When LTM is configured / applied, RS resource configuration (e.g., SSB resource configuration) can also be supported per candidate cell.

[0312] For example, the reference RS (e.g., TRS (or CSI-RS) / SSB) corresponding to QCL type A / QCL type D can also be a TRS (or CSI-RS) / SSB with a PCI different from the PCI of the serving cell. That is, as a reference RS (e.g., TRS / CSI-RS) corresponding to QCL type A, in addition to using a CSI-RS corresponding to the PCI of the serving cell (or, as a substitute), a CSI-RS with a PCI different from the PCI of the serving cell can also be used. Furthermore, as a reference RS (e.g., SSB) corresponding to QCL type D, in addition to using an SSB corresponding to the PCI of the serving cell (or, as a substitute), an SSB with a PCI different from the PCI of the serving cell can also be used.

[0313] In cases where multiple (e.g., two) reference RSs have different PCIs from the serving cell, the different PCIs can also be the same PCI. That is, two reference RSs (e.g., resource RSs) can also be configured to be associated with the same candidate cell (or non-serving cell). The two reference RSs can also be RSs corresponding to a first QCL type (e.g., QCL type A) and RSs corresponding to a second QCL type (e.g., QCL type D).

[0314] When LTM is set / applied, the UE can also be envisioned as: a quasi-co-location type indicated by the TCI state (e.g., TCI-State, or indicated DLorJointTCIState) from the base station, a TRS (e.g., QCL type A) with a PCI different from the PCI of the serving cell, and an SSB (e.g., QCL type D) with a PCI different from the PCI of the serving cell.

[0315] As an example, type A RS and type D RS of QCL rule 2-1 can also be defined as follows.

[0316] Alternatively, a Type A RS can be a CSI-RS resource of a non-zero power CSI-RS resource set (e.g., NZP-CSI-RS-ResourceSet) with higher-layer parameters (e.g., trs-Info) set, and a Type D RS can be an SS / PBCH block. The reference RS can also be a CSI-RS or SS / PBCH block with a PCI different from the serving cell's PCI. If both reference RSs have a different PCI from the serving cell, the different PCI can be set to the same PCI.

[0317] [QCL Rule 2-2]

[0318] QCL rule 2-2 can also be defined as follows.

[0319] QCL Type A RS:SSB (with a different PCI)

[0320] QCL type D RS: SSB (with a different PCI), or the same SSB as QCL type A RS.

[0321] The RS corresponding to QCL type A RS can also be an SSB. Furthermore, the RS corresponding to QCL type A RS can also be set to a PCI different from the serving cell's PCI (e.g., the PCI of a candidate cell / additional cell / non-serving cell) (see reference). Figure 15B When LTM is configured / applied, RS resource configuration (e.g., SSB resource configuration) can also be supported on a per-candidate-cell basis.

[0322] The RS corresponding to QCL type D RS can also be an SSB. Furthermore, the RS corresponding to QCL type D RS can also be set to a PCI different from the serving cell's PCI (e.g., the PCI of a candidate cell / additional cell / non-serving cell). For example, the RS corresponding to QCL type D RS can also be the same SSB as the QCL type A RS.

[0323] For example, the reference RS (e.g., SSB) corresponding to QCL type A / QCL type D can also be an SSB with a PCI different from the PCI of the serving cell. That is, as a reference RS (e.g., SSB) corresponding to QCL type A / QCL type D, in addition to using an SSB corresponding to the PCI of the serving cell (or, as its alternative), an SSB with a PCI different from the PCI of the serving cell can also be used.

[0324] In cases where multiple (e.g., two) reference RSs have different PCIs from the serving cell, the different PCIs can also be the same PCI. That is, two reference RSs (e.g., resource RSs) can also be configured to be associated with the same candidate cell (or non-serving cell). The two reference RSs can also be RSs corresponding to a first QCL type (e.g., QCL type A) and RSs corresponding to a second QCL type (e.g., QCL type D).

[0325] When LTM is set / applied, the UE can also be envisioned as: a quasi-co-location type indicated by the TCI state (e.g., TCI-State, or indicated DLorJointTCIState) from the base station, an SSB of a PCI different from the PCI of the serving cell (e.g., QCL type A), an SSB of a PCI different from the PCI of the serving cell, or an SSB of the same type as the QCL type ARS (e.g., QCL type D).

[0326] As an example, type A RS and type D RS of QCL rule 2-2 can also be defined as follows.

[0327] Alternatively, a Type A RS can be an SS / PBCH block, a Type D RS can be the same SS / PBCH block as a Type A RS, and a reference RS can also be an SS / PBCH block with a PCI different from that of the serving cell.

[0328] [QCL Rules 2-3]

[0329] QCL rules 2-3 can also be defined as follows.

[0330] QCL Type A RS: CSI-RS other than TRS (with a different PCI)

[0331] QCL type D RS:SSB (with a different PCI)

[0332] The RS corresponding to QCL type A RS can also be a CSI-RS other than a TRS. A CSI-RS other than a TRS can also be a CSI-RS that does not have a specific higher-layer parameter (e.g., trs-Info) set (or a CSI-RS within a CSI-RS resource set that does not have trs-Info set). Furthermore, the RS corresponding to QCL type A RS can also be set to correspond to a PCI different from the serving cell's PCI (e.g., the PCI of a candidate cell / additional cell / non-serving cell) (see reference). Figure 15CWhen LTM is configured / applied, RS resource configuration (e.g., CSI-RS resource configuration) can also be supported on a per-candidate-cell basis.

[0333] The RS corresponding to QCL type D RS can also be an SSB. Furthermore, the RS corresponding to QCL type D RS can also be configured to correspond to a PCI different from the serving cell's PCI (e.g., the PCI of a candidate cell / additional cell / non-serving cell). When LTM is configured / applied, RS resource configuration (e.g., SSB resource configuration) can also be supported per candidate cell.

[0334] For example, the reference RS (e.g., CSI-RS / SSB) corresponding to QCL type A / QCL type D can also be a CSI-RS / SSB with a PCI different from the PCI of the serving cell. That is, as a reference RS (e.g., CSI-RS) corresponding to QCL type A, in addition to using a CSI-RS corresponding to the PCI of the serving cell (or, as a substitute), a CSI-RS with a PCI different from the PCI of the serving cell can also be used. Furthermore, as a reference RS (e.g., SSB) corresponding to QCL type D, in addition to using an SSB corresponding to the PCI of the serving cell (or, as a substitute), an SSB with a PCI different from the PCI of the serving cell can also be used.

[0335] In cases where multiple (e.g., two) reference RSs have different PCIs from the serving cell, the different PCIs can also be the same PCI. That is, two reference RSs (e.g., resource RSs) can also be configured to be associated with the same candidate cell (or non-serving cell). The two reference RSs can also be RSs corresponding to a first QCL type (e.g., QCL type A) and RSs corresponding to a second QCL type (e.g., QCL type D).

[0336] When LTM is set / applied, the UE can also be envisioned as: a quasi-co-location type indicated by the TCI state (e.g., TCI-State, or indicated DLorJointTCIState) from the base station, a CSI-RS other than the PCI of the serving cell (e.g., QCL type A), and an SSB of the PCI of the serving cell (e.g., QCL type D) other than the PCI of the serving cell.

[0337] As an example, type A RS and type D RS of QCL rules 2-3 can also be defined as follows.

[0338] Alternatively, a Type A RS may be a CSI-RS resource in a non-zero power CSI-RS resource set (e.g., NZP-CSI-RS-ResourceSet) for which no higher-layer parameters (e.g., trs-Info) have been set. A Type D RS may be an SS / PBCH block. The reference RS can also be a CSI-RS or an SS / PBCH block with a PCI different from the serving cell's PCI. If both reference RSs have a PCI different from the serving cell's PCI, the different PCI can be set to the same PCI. Furthermore, Type ARS CSI-RS may not have higher-layer parameters related to repetition set.

[0339] [QCL Rules 2-4]

[0340] QCL rules 2-4 can also be defined as follows.

[0341] QCL Type A RS:SSB (with a different PCI)

[0342] QCL type D RS: CSI-RS other than TRS (with a different PCI)

[0343] The RS corresponding to QCL type A RS can also be SSB. Furthermore, the RS corresponding to QCL type D RS can also be set to a PCI different from the serving cell's PCI (e.g., the PCI of the candidate cell / additional cell / non-serving cell) (see reference). Figure 16A When LTM is configured / applied, RS resource configuration (e.g., SSB resource configuration) can also be supported on a per-candidate-cell basis.

[0344] The RS corresponding to QCL type D RS can also be a CSI-RS other than TRS. A CSI-RS other than TRS can also be a CSI-RS that has not had specific higher-layer parameters (e.g., trs-Info) set (or a CSI-RS within a CSI-RS resource set that has not had trs-Info set). Furthermore, the RS corresponding to QCL type D RS can also be set to a PCI different from the serving cell's PCI (e.g., the PCI of a candidate cell / additional cell / non-serving cell). When LTM is set / applied, RS resource settings (e.g., CSI-RS resource settings) can also be supported per candidate cell.

[0345] For example, the reference RS (e.g., CSI-RS / SSB) corresponding to QCL type A / QCL type D can also be a CSI-RS / SSB with a PCI different from the PCI of the serving cell. That is, as a reference RS (e.g., SSB) corresponding to QCL type A, in addition to using an SSB corresponding to the PCI of the serving cell (or, as a substitute), an SSB with a PCI different from the PCI of the serving cell can also be used. Furthermore, as a reference RS (e.g., CSI-RS) corresponding to QCL type D, in addition to using a CSI-RS corresponding to the PCI of the serving cell (or, as a substitute), a CSI-RS with a PCI different from the PCI of the serving cell can also be used.

[0346] In cases where multiple (e.g., two) reference RSs have different PCIs from the serving cell, the different PCIs can also be the same PCI. That is, two reference RSs (e.g., resource RSs) can also be configured to be associated with the same candidate cell (or non-serving cell). The two reference RSs can also be RSs corresponding to a first QCL type (e.g., QCL type A) and RSs corresponding to a second QCL type (e.g., QCL type D).

[0347] When LTM is set / applied, the UE can also be envisioned as: a quasi-co-location type indicated by the TCI state (e.g., TCI-State, or indicated DLorJointTCIState) from the base station, an SSB (e.g., QCL type A) of a PCI different from the PCI of the serving cell, and a CSI-RS (e.g., QCL type D) of a PCI different from the PCI of the serving cell.

[0348] As an example, type A RS and type D RS of QCL rule 2-4 can also be defined as follows.

[0349] Alternatively, a Type A RS can be an SS / PBCH block, and a Type D RS can be a CSI-RS resource in a non-zero power CSI-RS resource set (e.g., NZP-CSI-RS-ResourceSet) without higher-layer parameters (e.g., trs-Info) set. The reference RS can also be a CSI-RS or SS / PBCH block with a PCI different from the serving cell's PCI. If both reference RSs have a different PCI from the serving cell, the different PCI can be set to the same PCI. Furthermore, Type DRS CSI-RS may not have higher-layer parameters related to repetition set.

[0350] [QCL Rules 2-5]

[0351] QCL rules 2-5 can also be defined as follows.

[0352] QCL Type A RS:SSB (with a different PCI)

[0353] QCL type D RS: TRS (with a different PCI)

[0354] The RS corresponding to QCL type A RS can also be SSB. Furthermore, the RS corresponding to QCL type D RS can also be set to a PCI different from the serving cell's PCI (e.g., the PCI of the candidate cell / additional cell / non-serving cell) (see reference). Figure 16B When LTM is configured / applied, RS resource configuration (e.g., SSB resource configuration) can also be supported on a per-candidate-cell basis.

[0355] The RS corresponding to QCL type D RS can also be a CSI-RS with specific higher-layer parameters (e.g., trs-Info) set (or a CSI-RS within a CSI-RS resource set with trs-Info set). Furthermore, the RS corresponding to QCL type D RS can also be set to a PCI different from the serving cell's PCI (e.g., the PCI of a candidate cell / additional cell / non-serving cell). When LTM is set / applied, RS resource settings (e.g., CSI-RS resource settings) can also be supported per candidate cell.

[0356] For example, the reference RS (e.g., SSB / TRS (or CSI-RS)) corresponding to QCL type A / QCL type D can also be an SSB / TRS (or CSI-RS) with a PCI different from the PCI of the serving cell. That is, as a reference RS (e.g., SSB) corresponding to QCL type A, in addition to using an SSB corresponding to the PCI of the serving cell (or, as a substitute), an SSB with a PCI different from the PCI of the serving cell can also be used. Furthermore, as a reference RS (e.g., TRS / CSI-RS) corresponding to QCL type D, in addition to using a CSI-RS corresponding to the PCI of the serving cell (or, as a substitute), a CSI-RS with a PCI different from the PCI of the serving cell can also be used.

[0357] In cases where multiple (e.g., two) reference RSs have different PCIs from the serving cell, the different PCIs can also be the same PCI. That is, two reference RSs (e.g., resource RSs) can also be configured to be associated with the same candidate cell (or non-serving cell). The two reference RSs can also be RSs corresponding to a first QCL type (e.g., QCL type A) and RSs corresponding to a second QCL type (e.g., QCL type D).

[0358] When LTM is set / applied, the UE can also be envisioned as: a quasi-co-location type indicated by the TCI state (e.g., TCI-State, or indicated DLorJointTCIState) from the base station, a TRS (e.g., QCL type A) with a PCI different from the PCI of the serving cell, and an SSB (e.g., QCL type D) with a PCI different from the PCI of the serving cell.

[0359] As an example, type A RS and type D RS of QCL rule 2-5 can also be defined as follows.

[0360] Alternatively, a Type A RS can be an SS / PBCH block, and a Type D RS can be a CSI-RS resource of a non-zero power CSI-RS resource set (e.g., NZP-CSI-RS-ResourceSet) with higher-layer parameters (e.g., trs-Info) set. The reference RS can also be an SS / PBCH block or a CSI-RS with a PCI different from the serving cell's PCI. If both reference RSs have a different PCI from the serving cell, the different PCI can be set to the same PCI.

[0361] In at least one of QCL rules 2-1 to 2-5, the UE may also assume that the center frequency, SCS, and SFN offsets are the same for the SSB of the serving cell and the SSB corresponding to a different PCI from the serving cell. This assumption can also be made without LTM being set (e.g., higher-layer parameters related to LTM setting (e.g., LTMConf-r18)) or with ICBM set to Rel.17 (e.g., specific higher-layer parameters (e.g., SSB-MTC-AdditonalPCI-r17)). For example, when LTM is set between cells of different frequencies (e.g., inter-frequency LTM), the center frequency / SCS / SFN offset of the SSB of the serving cell and the center frequency / SCS / SFN offset of the SSB corresponding to a different PCI from the serving cell can also be set separately.

[0362] In at least one of QCL rules 2-1 to QCL rules 2-5, QCL type A RS may also be transmitted in the same cell / CC as the cell / CC of the cell with the applied TCI state (i.e., the same cell / CC as the target DMRS of PDCCH / PDSCH).

[0363] [Support for the new QCL type]

[0364] The QCL type (e.g., a new QCL type) in at least one of QCL rules 2-1 to 2-5 can also be subject to at least one of the following conditions 2-1 to 2-4.

[0365] Condition 2-1

[0366] QCL rules 2-1 to QCL rules 2-5 (or, new QCL types) may also be supported only for QCLs of Rel.15 / 16 or QCLs of Rel.17 (e.g., Unified TCI).

[0367] Condition 2-2

[0368] QCL rules 2-1 to 2-5 (or, the new QCL type) may also be supported only for RSs associated with a PCI different from that of the serving cell (e.g., reference RS / resource RS). For example, QCL rules 2-1 to 2-5 (or, the new QCL type) may also be applied if an LTM supported after Rel.18 is set (or if a reference RS / resource RS is associated with a PCI different from that of the serving cell).

[0369] On the other hand, for other scenarios, the structure can also be set to not support QCL rules 2-1 to QCL rules 2-5 (or, the new QCL type). Other scenarios could include situations where the reference RS / resource RS is not associated with a PCI different from the serving cell, or where a reference RS / resource RS associated with a PCI different from the serving cell does not exist.

[0370] Conditions 2-3

[0371] QCL rules 2-1 to QCL rules 2-5 (or, new QCL types) may also be supported only for at least one of the following scenarios: LTM is set as supported in Rel.18 and later, and ICBM is set as supported in Rel.17. LTM settings supported in Rel.18 and later may also involve associating a reference RS / resource RS with a PCI different from the serving cell. ICBM settings supported in Rel.17 may also involve associating a reference RS / resource RS with a PCI different from the serving cell, and the UE envisions the same center frequency, SCS, and SFN offset for the SSB of the serving cell and the SSB corresponding to the PCI different from that serving cell.

[0372] On the other hand, for other scenarios, the structure can also be set to not support QCL rules 2-1 to QCL rules 2-5 (or, the new QCL type). Other scenarios could include situations where the reference RS / resource RS is not associated with a PCI different from the serving cell, or where a reference RS / resource RS associated with a PCI different from the serving cell does not exist.

[0373] Conditions 2-4

[0374] QCL rules 2-1 to QCL rules 2-5 (or, new QCL types) can also be supported in any case.

[0375] [UE Capability Information]

[0376] UE capabilities can also be introduced / supported for new QCL types in QCL rules 2-1 to QCL rules 2-5. UE capabilities can also be introduced / supported for situations where QCL rules 2-1 to QCL rules 2-5 (or new QCL types) are applicable.

[0377] UE capabilities can also be introduced / supported for specific QCL rules. For example, UE capabilities can be introduced regarding the presence or absence of support for applying SSB as a QCL type ARS (e.g., QCL rules 2-2 / 2-4 / 2-5). Considering that SSBs may not have sufficient resource (e.g., RE) density for measuring QCL type A information, support / application can also be determined on a per-UE basis based on UE capability information.

[0378] Alternatively, a dedicated UE capability for the new QCL type may not be defined. In this case, all UEs supporting LTM can also support the new QCL type (e.g., at least one of QCL rules 2-1 to QCL rules 2-5) as the default. Thus, even when inter-frequency LTM is supported, the appropriate QCL rules (or QCL types) can be utilized.

[0379] Separate UE capabilities / common UE capabilities may also be introduced for the first and second embodiments. When separate UE capabilities are introduced (e.g., separate UE capabilities), one of these capabilities may be a default UE capability for LTM, while the others are optional functions. For example, all UEs supporting LTM may support the new QCL type shown in the first embodiment (or at least one of QCL rules 1-1 to 1-3) as the default, and based on reports of settings / UE capability information from the base station, apply the new QCL type shown in the first embodiment (e.g., at least one of QCL rules 2-1 to 2-5).

[0380] <Supplement>

[0381] [Information notification to UE]

[0382] The notification of any information from the Network (NW) (e.g., Base Station (BS)) to the UE in the above-described embodiments (in other words, the reception of any information from the BS in the UE) can also be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signals), or combinations thereof.

[0383] In the case where the above notification is made via MAC CE, the MAC CE can also be identified by including a new Logical Channel ID (LCID) that is not specified in the existing standard in the MAC subheader.

[0384] When the above notification is made through a DCI, the notification can also be made through specific fields of the DCI, the Radio Network Temporary Identifier (RNTI) used in the scrambling of the Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0385] Furthermore, the notification of any information to the UE in the above embodiments can also be carried out periodically, semi-persistently, or non-periodically.

[0386] [Notification from UE]

[0387] The notification of any information from the UE (to the NW) in the above embodiments (in other words, the transmission / reporting of any information from the UE to the BS) can also be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MACCE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or combinations thereof.

[0388] In the case where the above notification is made via MAC CE, the MAC CE can also be identified by including a new LCID in the MAC sub-header that is not specified in the existing standard.

[0389] In cases where the above notification is sent via UCI, the above notification may also be sent using PUCCH or PUSCH.

[0390] Furthermore, the notification of any information from the UE in the above embodiments can also be carried out periodically, semi-persistently, or non-periodically.

[0391] [Regarding the application of each implementation method]

[0392] At least one of the above-described implementation methods can also be applied under certain conditions. These specific conditions can be specified in the standard or communicated to the UE / BS using higher-layer signaling / physical layer signaling.

[0393] At least one of the above implementation methods may also be applied only to UEs that have reported a specific UE capability or support that specific UE capability.

[0394] This specific UE capability can also represent at least one of the following:

[0395] • Supports specific processing / operation / control / information for at least one of the above implementation methods (e.g., setting of unified TCI status and BFR of TRP units).

[0396] • Supports setting a unified TCI status;

[0397] • Supports LTM;

[0398] • Supports setting TRS / CSI-RS as QCL type A / D RS;

[0399] • Supports setting SSB as QCL type A / D RS.

[0400] Furthermore, the aforementioned specific UE capabilities can be applied across the entire frequency range (commonly independent of frequency), or per frequency (e.g., one or a combination of cells, bands, band combinations, BWPs, component carriers, etc.), or per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or per subcarrier spacing (SCS), or per feature set (FS) or per component carrier feature set (FSPC).

[0401] Furthermore, the aforementioned specific UE capabilities can be either the ability to apply across all duplex modes (commonly independent of duplex mode) or the capability for each duplex mode (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).

[0402] Furthermore, at least one of the above-described embodiments can also be applied when the UE is set / activated / triggered by specific information associated with the above-described embodiments (or performs the operations of the above-described embodiments) via higher-layer signaling / physical layer signaling. For example, this specific information may be a setting indicating activation of the unified TCI state and information on the BFR of the TRP unit, or any RRC parameter for a specific version (e.g., Rel.18 / 19).

[0403] The UE may also apply operations such as Rel.15 / 16 if it does not support at least one of the specific UE capabilities mentioned above, or if the specific information mentioned above is not set.

[0404] (Postscript)

[0405] With respect to one embodiment of this disclosure, the following invention is noted.

[0406] [Postscript 1]

[0407] A terminal includes: a receiving unit that receives information relating to a candidate cell that is a handover candidate for becoming a serving cell and information relating to a transmission setting indication (TCI) state; and a control unit that, based on a demodulation reference signal (DMRS) for a DL channel, determines that, based on the information relating to the TCI state, it is indicated that it has one or more quasi-co-address types (QCL types) having a reference signal corresponding to a physical cell ID (PCI) different from that of the serving cell.

[0408] [Postscript 2]

[0409] As described in Appendix 1, the terminal wherein the one or more QCL type reference signals are Channel State Information Reference Signals (CSI-RS).

[0410] [Postscript 3]

[0411] As described in Appendix 1 or Appendix 2, the terminal wherein the one or more QCL type reference signals are synchronization signal blocks (SSBs).

[0412] [Postscript 4]

[0413] The terminal described in any one of Appendix 1 to Appendix 3, wherein, when the more than one QCL includes a first QCL type and a second QCL type, the first reference signal of the first QCL type is a synchronization signal block (SSB), and the second reference signal of the second QCL type is a channel state information reference signal (CSI-RS).

[0414] (Wireless communication system)

[0415] The structure of a wireless communication system according to one embodiment of this disclosure will now be described. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above embodiments of this disclosure.

[0416] Figure 17 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment. The wireless communication system 1 (also referred to simply as System 1) may also be a system that uses Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5GNR) as standardized by the Third Generation Partnership Project (3GPP).

[0417] Furthermore, the wireless communication system 1 can also support dual connectivity between multiple radio access technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC can also 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)), etc.

[0418] 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.

[0419] Wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (e.g., MN and SN are dual connectivity between NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0420] The wireless communication system 1 may also include a base station 11 forming a macro cell C1 with a relatively wide coverage area, and a base station 12 (12a-12c) configured within the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. The user terminal 20 may also be located within at least one cell. The configuration and number of each cell and the user terminal 20 are not limited to the arrangement shown in the figure. Hereinafter, without distinguishing between base stations 11 and 12, they will be collectively referred to as base station 10.

[0421] User terminal 20 may also connect to at least one of multiple base stations 10. User terminal 20 may also utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0422] Each CC can also be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). Macro cell C1 can also be included in FR1, and small cell C2 can also be included in FR2. For example, FR1 can also be a frequency band below 6 GHz (sub-6 GHz), and FR2 can also be a frequency band above 24 GHz (above-24 GHz). In addition, the frequency bands, definitions, etc. of FR1 and FR2 are not limited to these; for example, FR1 can also correspond to a frequency band higher than FR2.

[0423] In addition, in each CC, the user terminal 20 may also use at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) for communication.

[0424] Multiple base stations 10 can also be connected via wired (e.g., fiber optic, X2 interface, etc. based on Common Public Radio Interface (CPRI)) or wireless (e.g., NR communication). For example, when NR communication between base stations 11 and 12 is used as a backhaul, base station 11, which is equivalent to a host station, can also be referred to as an Integrated Access Backhaul (IAB) donor, and base station 12, which is equivalent to a relay station, can also be referred to as an IAB node.

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

[0426] The core network 30 may also include, for example, user plane functions (UPF), access and mobility management functions (AMF), session management functions (SMF), unified data management (UDM), application functions (AF), data network (DN), location management functions (LMF), and network functions (NF) such as operation, administration and maintenance (OAM). Alternatively, a single network node may provide multiple functions. Furthermore, communication with external networks (e.g., the Internet) may also be conducted via the DN.

[0427] User terminal 20 can also be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0428] In wireless communication system 1, wireless access methods based on Orthogonal Frequency Division Multiplexing (OFDM) can also be used. For example, in at least one of the downlink (DL) and uplink (UL) links, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA) can also be used.

[0429] The wireless access method can also be referred to as a waveform. In addition, in the wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be used in the wireless access methods of UL and DL.

[0430] As a downlink channel, the wireless communication system 1 can also use downlink shared channels (Physical Downlink Shared Channel (PDSCH)), broadcast channels (Physical Broadcast Channel (PBCH)), downlink control channels (Physical Downlink Control Channel (PDCCH)) and so on, which are shared among the user terminals 20.

[0431] In addition, as uplink channels, the wireless communication system 1 may also use uplink shared channels (Physical Uplink Shared Channel (PUSCH)), uplink control channels (Physical Uplink Control Channel (PUCCH)), random access channels (Physical Random Access Channel (PRACH)) and so on, which are shared by each user terminal 20.

[0432] User data, high-level control information, and System Information Blocks (SIBs) are transmitted via the PDSCH. User data and high-level control information can also be transmitted via the PUSCH. In addition, Master Information Blocks (MIBs) can also be transmitted via the PBCH.

[0433] Lower-layer control information can also be transmitted via PDCCH. This lower-layer control information may include, for example, downlink control information (DCI), which includes scheduling information for at least one of PDSCH and PUSCH.

[0434] Additionally, the DCI that schedules PDSCH can also be called DL allocation, DL DCI, etc., and the DCI that schedules PUSCH can also be called UL authorization, UL DCI, etc. Furthermore, PDSCH can be rewritten as DL data, and PUSCH can be rewritten as UL data.

[0435] In PDCCH detection, a Control Resource Set (CORESET) and a search space can also be utilized. A CORESET corresponds to the resources used to search for DCIs. The search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor CORESETs associated with a specific search space based on search space settings.

[0436] A search space can also correspond to a PDCCH candidate corresponding to one or more aggregation levels. One or more search spaces can also be referred to as a search space set. In addition, the terms "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting" etc. disclosed herein can be rewritten interchangeably.

[0437] The PUCCH can also transmit uplink control information (uplink control information (UCI)) that includes at least one of the following: Channel State Information (CSI), delivery confirmation information (e.g., also known as Hybrid Automatic Repeat Request ACK Knowledge (HARQ-ACK), ACK / NACK, etc.), and Scheduling Request (SR). The PRACH can also transmit random access preambles used for establishing connections with the cell.

[0438] Additionally, in this disclosure, downlink, uplink, etc., may be described without the word "link". Furthermore, it may be stated that the word "physical" is not included at the beginning of various channels.

[0439] In wireless communication system 1, synchronization signals (SS) and downlink reference signals (DL-RS) can also be transmitted. In wireless communication system 1, DL-RS can also transmit cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), positioning reference signals (PRS), and phase tracking reference signals (PTRS).

[0440] Synchronization signals can be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block containing SS (PSS, SSS) and PBCH (and DMRS for PBCH) can also be called an SS / PBCH block, SS block (SSB), etc. In addition, SS, SSB, etc. can also be called reference signals.

[0441] Furthermore, as an uplink reference signal (UL-RS), measurement reference signals (sounding reference signals (SRS)) and demodulation reference signals (DMRS) can also be transmitted in the wireless communication system 1. Additionally, DMRS can also be referred to as a user terminal-specific reference signal (UE-specific reference signal).

[0442] (Base station)

[0443] Figure 18This diagram illustrates an example of the structure of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmit / receive unit 120, a transmit / receive antenna 130, and a transmission path interface (transmission line interface) 140. Alternatively, the control unit 110, the transmit / receive unit 120, the transmit / receive antenna 130, and the transmission path interface 140 may each be provided in more than one manner.

[0444] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the base station 10 may also have other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0445] The control unit 110 performs overall control of the base station 10. The control unit 110 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

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

[0447] The transmitting / receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting / receiving unit 120 can be composed of transmitters / receivers, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmitting / receiving circuits, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0448] The transmitting and receiving unit 120 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 1211 and an RF unit 122. The receiving unit can also be composed of a receiving processing unit 1212, an RF unit 122, and a measurement unit 123.

[0449] The transmitting and receiving antenna 130 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

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

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

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

[0453] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform transmission processing such as channel coding (which may also include error correction coding), modulation, mapping, filter processing (filtering processing), Discrete Fourier Transform (DFT) processing (as needed), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output the baseband signal.

[0454] The transmitting and receiving unit 120 (RF unit 122) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 130.

[0455] On the other hand, the transmitting and receiving unit 120 (RF unit 122) can also amplify, filter, and demodulate the signals of the wireless frequency band received through the transmitting and receiving antenna 130 into the baseband signal.

[0456] The transmitting and receiving unit 120 (receiving and processing unit 1212) can also perform receiving and processing on the acquired baseband signal, including analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data, etc.

[0457] The transmitting / receiving unit 120 (measurement unit 123) can also perform measurements related to the received signal. For example, the measurement unit 123 can also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc., based on the received signal. The measurement unit 123 can also measure received power (e.g., Reference Signal Received Power (RSRP)), received 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 can also be output to the control unit 110.

[0458] The transmission path interface 140 can also transmit and receive signals (backhaul signaling) between the device included in the core network 30 (e.g., the network node providing the NF), other base stations 10, etc., and can also acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0459] In addition, the base station 10 in this disclosure may also be composed of at least one of a transmission and reception unit 120, a transmission and reception antenna 130, and a transmission path interface 140.

[0460] The transmitting and receiving unit 120 can also transmit information related to candidate cells that become serving cells (or, candidates for handover to serving cells) and information related to the transmission setting indication (TCI) status.

[0461] The control unit 110 can also indicate, for the demodulation reference signal (DMRS) of the DL channel, one or more quasi-colocation types (QCL types) having a reference signal corresponding to a physical cell ID (PCI) different from that of the serving cell, by using information related to the TCI state.

[0462] (User terminal)

[0463] Figure 19 This diagram illustrates an example of the structure 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. Alternatively, the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may each be provided as one or more.

[0464] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the user terminal 20 may also have other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0465] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the technical field to which this disclosure pertains.

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

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

[0468] The transmitting and receiving unit 220 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit can also be composed of a receiving processing unit 2212, an RF unit 222, and a measurement unit 223.

[0469] The transmitting and receiving antenna 230 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0470] The transmitting / receiving unit 220 can also receive the downlink channel, synchronization signal, downlink reference signal, etc., mentioned above. The transmitting / receiving unit 220 can also transmit the uplink channel, uplink reference signal, etc., mentioned above.

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

[0472] The transmitting and receiving unit 220 (transmitting processing unit 2211) may, for example, perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control) on the data and control information obtained from the control unit 210, and generate the bit string to be transmitted.

[0473] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may include error correction coding), modulation, mapping, filter processing, DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be transmitted, and output the baseband signal.

[0474] Furthermore, whether or not to apply DFT processing can be based on the settings of transform precoding. For a certain channel (e.g., PUSCH), if transform precoding is enabled, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above in order to transmit the channel using the DFT-s-OFDM waveform. If not, the transmit / receive unit 220 (transmit processing unit 2211) can perform the above transmission processing without performing DFT processing.

[0475] The transmitting and receiving unit 220 (RF unit 222) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 230.

[0476] On the other hand, the transmitting and receiving unit 220 (RF unit 222) can also amplify, filter, demodulate, etc., the signals of the wireless frequency band received by the transmitting and receiving antenna 230.

[0477] The transmitting and receiving unit 220 (receiving and processing unit 2212) can also perform receiving and processing on the acquired baseband signal, such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data.

[0478] The transmitting / receiving unit 220 (measurement unit 223) can also perform measurements related to the received signal. For example, the measurement unit 223 can also perform RRM measurements, CSI measurements, etc., based on the received signal. The measurement unit 223 can 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 can also be output to the control unit 210.

[0479] Additionally, the measurement unit 223 can also derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources can be, for example, non-zero power (NZP) CSI-RS resources. Furthermore, the measurement unit 223 can also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources can be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. Additionally, CSI-IM can also be referred to as CSI-Interference Management (IM), and can be interchanged with zero power (ZP) CSI-RS. Furthermore, in this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., can also be interchanged.

[0480] Alternatively, the transmitting and receiving units of the user terminal 20 in this disclosure may also be composed of at least one transmitting / receiving unit 220 and transmitting / receiving antenna 230.

[0481] The transmitting and receiving unit 220 can also receive information related to candidate cells that are candidates to become serving cells (or to become serving cells) and information related to the state of the transmission setting indication (TCI).

[0482] The control unit 210 may also determine, based on the demodulation reference signal (DMRS) of the DL channel, that it is indicated by information related to the TCI state that it has one or more quasi-co-address types (QCL types) with reference signals corresponding to a physical cell ID (PCI) different from the serving cell.

[0483] Reference signals of one or more QCL types can also be Channel State Information Reference Signals (CSI-RS). Reference signals of one or more QCL types can also be Synchronization Signal Blocks (SSBs). When one or more QCLs include a first QCL type and a second QCL type, the first reference signal of the first QCL type can also be a Synchronization Signal Block (SSB), and the second reference signal of the second QCL type can also be a Channel State Information Reference Signal (CSI-RS).

[0484] (Hardware structure)

[0485] Furthermore, the block diagrams used in the description of the above embodiments illustrate functional units. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Moreover, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using a single device that is physically or logically combined, or it can be implemented by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. A functional block can also be implemented by combining the aforementioned single device or multiple devices with software.

[0486] Here, the functions include judgment, decision, determination, calculation, calculation, processing, export, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, regard as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, a functional block (structural unit) that implements the sending function can also be called a transmitting unit, transmitter, etc. Each of these, as described above, is not particularly limited in its implementation method.

[0487] For example, in one embodiment of this disclosure, the base station, user terminal, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 20This diagram illustrates an example of the hardware structure of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 described above can also be physically configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0488] Furthermore, in this disclosure, terms such as apparatus, circuit, device, section, and unit can be interchanged. The hardware structure of base station 10 and user terminal 20 can be configured to include one or more of the apparatuses shown in the figures, or it can be configured not to include any of the apparatuses.

[0489] For example, only one processor 1001 is shown, but there can be multiple processors. Furthermore, processing can be performed by one processor, or simultaneously, sequentially, or by two or more processors using other methods. Additionally, processor 1001 can be implemented using more than one chip.

[0490] Regarding the functions in base station 10 and user terminal 20, for example, by reading specific software (programs) into hardware such as processor 1001 and memory 1002, so that processor 1001 performs calculations and controls communication via communication device 1004, or by controlling at least one of reading and writing data in memory 1002 and storage device 1003.

[0491] The processor 1001 enables the operating system to operate and control the computer as a whole. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic devices, registers, etc. For example, at least a portion of the control unit 110 (210), the transmit / receive unit 120 (220), etc., described above may also be implemented by the processor 1001.

[0492] 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 performs various processes accordingly. As a program, a program that causes the computer to perform at least a portion of the operations described in the above embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operated in the processor 1001; similar implementations can be made for other functional blocks.

[0493] The memory 1002 may also be a computer-readable recording medium, such as being composed of at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage media. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 is capable of storing executable programs (program code), software modules, etc., for implementing the wireless communication method according to an embodiment of this disclosure.

[0494] Storage device 1003 may also be a computer-readable recording medium, such as a flexible disc, floppy disk, optical disk (e.g., a compact disc ROM), digital multifunction disk, Blu-ray disc, removable disk, hard disk drive, smart card, flash memory device (e.g., a card, stick, key drive), magnetic stripe, database, server, or at least one other suitable storage medium. Storage device 1003 may also be referred to as an auxiliary storage device.

[0495] The communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. To implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmit / receive unit 120 (220) and transmit / receive antenna 130 (230) may also be implemented by the communication device 1004. The transmit / receive unit 120 (220) may also be implemented by physically or logically separating the transmit unit 120a (220a) and the receive unit 120b (220b).

[0496] Input device 1005 is an input device that receives input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, light-emitting diode (LED) lamp, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., a touch panel).

[0497] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 can be configured as a single bus or as different buses between the devices.

[0498] Furthermore, the base station 10 and the user terminal 20 can also be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a field-programmable gate array (FPGA), and can also use this hardware to implement part or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0499] (Modified example)

[0500] Furthermore, the terms described in this disclosure, as well as those necessary for understanding this disclosure, may be replaced with terms that have the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be interchanged. Additionally, a signal may also be a message. A reference signal can also be abbreviated as RS, and may be referred to as pilot, pilot signal, etc., depending on the applied standard. Furthermore, a component carrier (CC) may also be referred to as cell, frequency carrier, carrier frequency, etc.

[0501] A radio frame can also be composed of one or more periods (frames) in the time domain. Each of these periods (frames) that constitute a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

[0502] Here, the parameter set can also be communication parameters applied in at least one of the transmission and reception of a signal or channel. For example, the parameter set can also represent 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 structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

[0503] In the time domain, a time slot can also be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.). In addition, a time slot can also be a time unit based on a set of parameters.

[0504] A time slot can also contain multiple mini-time slots. Each mini-time slot can also consist of one or more symbols in the time domain. Furthermore, a mini-time slot can also be called a sub-time slot. A mini-time slot can also consist of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-time slot can also be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using mini-time slots can also be called PDSCH (PUSCH) mapping type B.

[0505] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also use their respective other names. Furthermore, the time units such as frames, subframes, time slots, mini-time slots, and symbols used in this disclosure can be interchanged.

[0506] For example, a subframe can also be called a TTI, multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is, at least one of a subframe and a TTI can be a subframe in existing LTE (1ms), a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but rather a time slot, mini-time slot, etc.

[0507] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules radio resources (frequency bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0508] TTI can also be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., and can also be a unit of processing such as scheduling and link adaptation. In addition, when a TTI is given, the actual time interval (e.g., the number of symbols) mapped to transmission blocks, code blocks, codewords, etc. can be shorter than the TTI.

[0509] Additionally, where a time slot or a mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can also serve as the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) constituting the minimum time unit of the schedule can also be controlled.

[0510] A TTI with a duration of 1ms can also be referred to as a normal TTI (TTI in 3GPPRel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI can also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub-time slot, a time slot, etc.

[0511] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can also be rewritten as a TTI with a duration of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) can also be rewritten as a TTI with a duration of less than a long TTI but more than 1 ms.

[0512] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can also contain one or more consecutive subcarriers. The number of subcarriers in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers in an RB can also be determined based on the parameter set.

[0513] Furthermore, an RB can contain one or more symbols in the time domain, and can also be a time slot, a mini-time slot, a subframe, or the length of a TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.

[0514] In addition, one or more RBs can also be referred to as Physical Resource Blocks (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0515] In addition, a resource block can also consist of one or more resource elements (REs). For example, an RE can also be a radio resource area consisting of a subcarrier and a symbol.

[0516] The Bandwidth Part (BWP) (also referred to as partial bandwidth, etc.) can also represent a subset of consecutive common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can also be determined by the index of RBs based on the common reference point of the carrier. PRBs can also be defined in a BWP and appended with numbers within that BWP.

[0517] A BWP can also include a UL BWP (the BWP used by UL) and a DL BWP (the BWP used by DL). For a UE, one or more BWPs can also be set within a single carrier.

[0518] At least one of the configured BWPs can be active, and the UE may not intend to transmit or receive specific signals / channels outside of the active BWPs. Additionally, the terms "cell," "carrier," etc., used in this disclosure may be replaced with "BWP."

[0519] Furthermore, the structures described above, such as radio frames, subframes, time slots, mini-time slots, and symbols, are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0520] Furthermore, the information, parameters, etc., described in this disclosure can be represented by absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by a specific index.

[0521] In this disclosure, the names used for parameters, etc., are not limiting names in any respect. Furthermore, the mathematical expressions, etc., using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name; therefore, the various names assigned to these various channels and information elements are not limiting names in any respect.

[0522] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be mentioned throughout the above description, can also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0523] Furthermore, information, signals, etc., can be output in at least one of the following directions: from higher level (upper layer) to lower level (lower layer), and from lower layer to higher level. Information, signals, etc., can also be input and output via multiple network nodes.

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

[0525] The notification of information is not limited to the methods / implementations described in this disclosure, and may also be carried out by other methods. For example, the notification of information in this disclosure may also be implemented 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) etc.), medium access control (MAC) signaling), other signals, or combinations thereof.

[0526] In addition, physical layer signaling can also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. Furthermore, RRC signaling can also be referred to as RRC messages, such as RRC connection setup messages, RRC connection reconfiguration messages, etc. Additionally, MAC signaling can also be notified using, for example, the MAC control element (CE).

[0527] Furthermore, notification of specific information (e.g., a notification of “is X”) is not limited to explicit notification, but can also be implicit (e.g., by not providing that specific information, or by providing other information).

[0528] The determination can be made by a value represented by a single bit (0 or 1), by a true or false value (boolean), or by a numerical comparison (e.g., a comparison with a specific value).

[0529] Whether software is called software, firmware, middleware, microcode, hardware description language, or any other name, it should be broadly interpreted to refer to 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, etc.

[0530] Furthermore, software, instructions, and information can also be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0531] The terms “system” and “network” as used in this disclosure are interchangeable. “Network” may also mean devices included in a network (e.g., base stations).

[0532] In this disclosure, the terms “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”, “beamwidth”, “beam angle”, “antenna”, “antenna element”, “panel”, “UE panel”, “transmitting entity”, and “receiving entity” are used interchangeably.

[0533] Furthermore, in this disclosure, the antenna port can also be rewritten with an antenna port used for any signal / channel (e.g., a DeModulation Reference Signal (DMRS) port). In this disclosure, resources can also be rewritten with resources used for any signal / channel (e.g., reference signal resources, SRS resources, etc.). Additionally, resources can also include time / frequency / code / space / power resources. Moreover, the spatial domain transmission filter can also include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0534] The aforementioned groups may include, for example, at least one of the following: spatial relation group, code division multiplexing (CDM) group, reference signal (RS) group, control resource set (CORESET) group, PUCCH group, antenna port group (e.g., DMRS port group), layer group, resource group, beam group, antenna group, panel group, etc.

[0535] Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), RS, etc., can also be rewritten to each other.

[0536] Furthermore, in this disclosure, the TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, and joint TCI state can also be rewritten to each other.

[0537] Furthermore, in this disclosure, terms such as "QCL", "QCL concept", "QCL relationship", "QCL type information", "QCL property (QCLproperty / properties)", "specific QCL type (e.g., type A, type D) property", and "specific QCL type (e.g., type A, type D)" can be rewritten interchangeably.

[0538] In this disclosure, indexes, identifiers (IDs), indicators, indications, resource IDs, etc., can be interchanged. Sequences, lists, sets, groups, clusters, subsets, etc., can also be interchanged.

[0539] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) can be interchanged. "Spatial relationship information (TCI state)" can also be interchanged with "a set of spatial relationship information (TCI states)," "one or more spatial relationship information," etc. TCI state and TCI can also be interchanged. Spatial relationship information and spatial relationship can also be interchanged.

[0540] In this disclosure, the terms "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" are used interchangeably. There are also instances where the terms macro cell, small cell, femtocell, and picocell are used to refer to a base station.

[0541] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its overall coverage area can be divided into several smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0542] In this disclosure, the situation where a base station sends information to a terminal can also be modified to the situation where the base station instructs the terminal to perform control / operation based on that information.

[0543] In this disclosure, the terms “Mobile Station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” are used interchangeably.

[0544] There are also instances where mobile stations are referred to as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or several other appropriate terms.

[0545] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Additionally, at least one of the base station and the mobile station can also be a device mounted on a moving object, the moving object itself, etc.

[0546] The term "mobile body" refers to a movable object whose speed is arbitrary, including situations where the body is stationary. Examples of such mobile bodies include vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships (ships and other watercraft), airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, hot air balloons, and objects carried on them, but are not limited to these. Furthermore, the mobile body can also be a mobile body that moves autonomously based on operational commands.

[0547] The mobile entity can be a means of transportation (e.g., a vehicle, an airplane, etc.), a mobile entity moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Additionally, at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station can also be an Internet of Things (IoT) device such as a sensor.

[0548] Figure 21 This is a diagram illustrating 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 speed sensor 51, a 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.

[0549] The drive unit 41 is comprised of at least one of an engine, a motor, or a combination of an engine and a motor. The steering unit 42 is configured to include at least a steering wheel (also called a steering handle) that steers at least one of the front wheels 46 and the rear wheels 47 based on operation of the steering wheel by the user.

[0550] The electronic control unit 49 consists of a microprocessor 61, a memory (ROM, RAM) 62, and a communication port (e.g., an input / output (IO) port) 63). Signals from various sensors 50-58 present in the vehicle are input to the electronic control unit 49. The electronic control unit 49 can also be referred to as an electronic control unit (ECU).

[0551] The signals from various sensors 50-58 include the following: current signal from current sensor 50 sensing the current of the motor; rotational speed signal of front wheel 46 / rear wheel 47 obtained by speed sensor 51; air pressure signal of front wheel 46 / rear wheel 47 obtained by air pressure sensor 52; vehicle speed signal obtained by vehicle speed sensor 53; acceleration signal obtained by acceleration sensor 54; accelerator pedal 43 depress amount signal obtained by accelerator pedal sensor 55; brake pedal 44 depress amount signal obtained by brake pedal sensor 56; shift lever 45 operation signal obtained by shift lever sensor 57; and detection signal obtained by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc.

[0552] The information service unit 59 comprises various devices such as a navigation system, audio system, speakers, display, television, and radio, used to provide (output) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 59 uses information obtained from external devices via the communication module 60, etc., to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

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

[0554] The driver assistance system unit 64 comprises various devices used to provide functions for preventing accidents or reducing the driver's workload, such as millimeter-wave radar, light detection and ranging (LiDAR), cameras, positioning detectors (e.g., Global Navigation Satellite System (GNSS), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyroscope systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS), etc.), artificial intelligence (AI) chips, and AI processors, and one or more ECUs that control these devices. Furthermore, the driver assistance system unit 64 sends and receives various information via communication module 60 to realize driver assistance functions or autonomous driving functions.

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

[0556] The communication module 60 can be controlled by the microprocessor 61 of the electronic control unit 49 and is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 60 can be located both inside and outside the electronic control unit 49. The external device can be, for example, the aforementioned base station 10, user terminal 20, etc. Furthermore, the communication module 60 can be, for example, at least one of the aforementioned base station 10 and user terminal 20 (or it can function as at least one of the base station 10 and user terminal 20).

[0557] The communication module 60 can also wirelessly transmit at least one of the signals input to the electronic control unit 49 from the various sensors 50-58 described above, the information obtained based on these signals, and the information based on input from an external (user) source obtained via the information service unit 59 to an external device. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., can also be referred to as input units that receive input. For example, the PUSCH transmitted via the communication module 60 can also contain information based on the aforementioned inputs.

[0558] The communication module 60 receives various information (traffic information, signal information, workshop information, etc.) sent from external devices and displays it on the vehicle's information service unit 59. The information service unit 59 can also be referred to as an output unit that outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH received by the communication module 60 (or the data / information decoded from the PDSCH).

[0559] Furthermore, the communication module 60 stores various types of information received from external devices into a memory 62 that can be utilized by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 can also control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, gear shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, and various sensors 50-58, etc., of the vehicle 40.

[0560] Furthermore, the base station in this disclosure can also be rewritten as a user terminal. For example, various methods / implementations of this disclosure can be applied to structures that replace communication between the base station and the user terminal with communication between multiple user terminals (e.g., also referred to as device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, it can also be configured such that the user terminal 20 has the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be rewritten as terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can also be rewritten as sidelink channel.

[0561] Similarly, the user terminal in this disclosure can also be rewritten as a base station. In this case, it can also be configured such that the base station 10 has the functions of the user terminal 20 described above.

[0562] In this disclosure, operations are assumed to be performed by the base station, and sometimes, depending on the circumstances, by its upper node. In a network containing one or more network nodes having a base station, the various operations performed for communication with a terminal can obviously be performed by the base station, one or more network nodes other than the base station (e.g., considering a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc., but not limited to these), or combinations thereof.

[0563] The various methods / implementations described in this disclosure can be used individually or in combination, and can be switched as needed during execution. Furthermore, the processing procedures, timing sequences, flowcharts, etc., of the various methods / implementations described in this disclosure can be rearranged as long as they do not contradict each other. For example, for the method described in this disclosure, the illustrated order is used to indicate various steps, but the order in which they are indicated is not limited.

[0564] The various methods / implementations described in this disclosure can also be applied to 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 a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Futuregeneration Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE This includes 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-Wideband (UWB)), Bluetooth (registered trademark), systems utilizing other suitable wireless communication methods, and next-generation systems derived from, modified, generated, or specified based on these methods. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, combinations with 5G, etc.) for application.

[0565] As used in this disclosure, the term "based on" does not mean "based on only" unless otherwise specified. In other words, the term "based on" means both "based on only" and "based on at least".

[0566] Any reference to an element using the designations "first," "second," etc., as used in this disclosure does not comprehensively limit the quantity or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to the first and second elements does not imply that only two elements may be used, or that the first element must take precedence over the second element in some form.

[0567] The term "determining" as used in this disclosure can encompass a wide variety of operations. For example, "determining" can also refer to judging, calculating, computing, processing, deriving, investigating, looking up (search, inquiry) (e.g., searching in a table, database or other data structure), and ascertaining.

[0568] In addition, "judgment (decision)" can also refer to receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, accessing (e.g., accessing data in memory), etc., as situations where "judgment (decision)" is performed.

[0569] Furthermore, "judgment (decision)" can also refer to situations where resolving, selecting, choosing, establishing, or comparing are considered as making a "judgment (decision)". That is, "judgment (decision)" can also refer to certain operations as making a "judgment (decision)". In this disclosure, "judgment (decision)" can also be rewritten in relation to the operations described above.

[0570] Furthermore, in this disclosure, "determine / determining" can also be interchanged with "assume / assuming," "expect / expecting," "consider / considering," etc. Additionally, in this disclosure, "not assuming to proceed..." can also be interchanged with "assuming not to proceed..."

[0571] In this disclosure, "expect" can also be interchanged with "be expected." For example, "expect(s) ..." (where "..." can also be expressed using a that clause, to infinitive, etc.) can also be interchanged with "be expected ...." "Does not expect..." can also be interchanged with "be not expected...". Furthermore, "An apparatus A is not expected..." can also be interchanged with "Apparatus B other than apparatus A does not expect..." (for example, if apparatus A is a UE, apparatus B can also be a base station).

[0572] The term "maximum transmit power" as used in this disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[0573] As used in this disclosure, the terms “connected,” “coupled,” or all variations thereof, refer to all direct or indirect connections or combinations between two or more elements, and can include cases where there is one or more intermediate elements between two mutually “connected” or “coupled” elements. The connections or combinations between elements can be physical, logical, or a combination thereof. For example, “connection” can also be rewritten as “access.”

[0574] In this disclosure, when two elements are connected, it is possible to consider using more than one wire, cable, printed electrical connection, etc. to be "connected" or "combined" with each other, and as several non-limiting and non-exclusive examples, to use electromagnetic energy with wavelengths having wireless frequency domain, microwave region, light (both visible and invisible) region to be "connected" or "combined" with each other.

[0575] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other." Additionally, the term can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0576] When the terms "include," "including," and variations thereof are used in this disclosure, these terms, like the term "comprising," mean inclusive. Furthermore, the term "or" as used in this disclosure does not mean XOR.

[0577] In this disclosure, for example, in cases where articles are added through translation, such as a, an, and the in English, the disclosure may also include cases where the noun following these articles is in a plural form.

[0578] In this disclosure, words such as "below," "less than," "above," "more than," and "equal to" can be interchanged. Furthermore, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "slow," "wide," and "narrow," etc., are not limited to the positive, comparative, and superlative degrees, and can be interchanged. Additionally, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "slow," "wide," and "narrow," etc., as expressions with "i" appended (i being any integer), are not limited to the positive, comparative, and superlative degrees, and can be interchanged (for example, "highest" can also be interchanged with "i-th highest").

[0579] In this disclosure, "of", "for", "regarding", "related to", "associated with", etc., can also be rewritten interchangeably.

[0580] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "based on A", "B during / while A", "before A", "at the same time as / on A", "after A", "since A", and "until A" can be rewritten interchangeably. Furthermore, A and B can be replaced with nouns, gerunds, or ordinary sentences, depending on the context. Additionally, the time difference between A and B can be approximately zero (immediately following or immediately preceding). Moreover, a time offset can be applied to the time A occurs. For example, "A" can be rewritten interchangeably with "before / after the time offset of A". This time offset (e.g., more than one symbol / slot) can be predetermined or determined by the UE based on the information provided.

[0581] In this disclosure, timing, moment, time, time instance, arbitrary time unit (e.g., time slot, sub-time slot, symbol, subframe), period, opportunity, resource, etc., can also be overridden.

[0582] The inventions disclosed herein have been described in detail above. However, it will be apparent to those skilled in the art that the inventions disclosed herein are not limited to the embodiments described herein. The description herein is for illustrative purposes only and is not intended to limit the inventions disclosed herein in any way.

Claims

1. A terminal, comprising: The receiving unit receives information related to candidate cells that are potential handover candidates to become serving cells, and information related to the Transmission Setting Indication (TCI) status; and The control unit determines, based on the demodulation reference signal (DMRS) of the DL channel, that it is indicated, through information related to the TCI state, to have one or more quasi-co-address types (QCL types) with reference signals corresponding to physical cell IDs (PCIs) different from those of the serving cell.

2. The terminal as described in claim 1, wherein, The one or more QCL-type reference signals are Channel State Information Reference Signals (CSI-RS).

3. The terminal as described in claim 1, wherein, The one or more QCL type reference signals are synchronization signal blocks (SSBs).

4. The terminal as described in claim 1, wherein, When the more than one QCL includes a first QCL type and a second QCL type, the first reference signal of the first QCL type is a synchronization signal block (SSB), and the second reference signal of the second QCL type is a channel state information reference signal (CSI-RS).

5. A wireless communication method for a terminal, comprising: The steps of receiving information related to a candidate cell that is a handover candidate to become the serving cell, and information related to the Transmission Setting Indication (TCI) status; and For the Decall Reference Signal (DMRS) of the DL channel, the determination is: a step in which the user is instructed, based on information related to the TCI state, to have one or more quasi-co-location types (QCL types) with reference signals corresponding to a physical cell ID (PCI) different from that of the serving cell.

6. A base station, comprising: The transmitting unit transmits information related to candidate cells that have become serving cells and information related to the Transmission Setting Indication (TCI) status; and The control unit, for the demodulation reference signal (DMRS) of the DL channel, indicates one or more quasi-colocation types (QCL types) having reference signals corresponding to physical cell IDs (PCIs) different from those of the serving cell, using information related to the TCI state.

Images