Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives information pertaining to a target cell serving as a serving cell switching candidate and information pertaining to a transmission configuration indicator (TCI) state; and a control unit that determines a TCI state switching delay on the basis of a list of active TCI states included in the information pertaining to the TCI state.

Description

Terminal, wireless communication method and base station

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

[0002] Long Term Evolution (LTE) has been specified for the Universal Mobile Telecommunications System (UMTS) network with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

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

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

[0005] In future wireless communication systems (e.g., wireless communication systems after Rel. 17 / 5G), it is expected that communications will be controlled based on inter-cell mobility including a non-serving cell, or inter-cell mobility using multiple transmission / reception points (e.g., Multi-TRP (MTRP)). In inter-cell mobility, it is also expected that candidate cells will be set and switching between the serving cell and candidate cells will be performed using L1 / L2 signaling.

[0006] However, when inter-cell mobility (e.g., switching between a serving cell and a candidate cell) is applied, how to set / apply a Transmission Configuration Indication state (TCI state) corresponding to the candidate cell becomes an issue. If the TCI state of the candidate cell cannot be set / applied appropriately, the quality of communication may be degraded.

[0007] The present disclosure has been made in consideration of such points, and one of its objectives is to provide a terminal, a wireless communication method, and a base station that are capable of appropriately controlling communications even when TCI state switching delay is supported.

[0008] A terminal according to one aspect of the present disclosure has a receiving unit that receives information regarding a target cell that is a candidate for switching the serving cell and information regarding a transmission configuration indicator (TCI) state, and a control unit that determines a TCI state switching delay based on a list of active TCI states included in the information regarding the TCI state.

[0009] According to one aspect of the present disclosure, communication can be appropriately controlled even when a TCI state switching delay is supported.

[0010] Figure 1A illustrates an example of UE mobility in Rel. 17. Figure 1B illustrates an example of UE mobility in Rel. 18. Figure 2 illustrates an example of an LTM procedure. Figure 3 illustrates an example of a comparison between L3 handover and Rel. 18 LTM. Figure 4 illustrates an example of serving cell and candidate cell association. Figure 5A illustrates a first example of candidate cell configuration option 2. Figure 5B illustrates a second example of candidate cell configuration option 2. Figure 6 illustrates serving cell switch example 1. Figure 7 illustrates serving cell switch example 2. Figure 8 illustrates serving cell switch example 3. Figure 9 illustrates an overview of L1L2-triggered mobility (LTM). Figure 10 illustrates PDCCH-ordered RACH with random access response (RAR) monitoring for a serving cell. FIG. 11 is a diagram illustrating a PDCCH-instructed RACH (PDCCH-ordered RACH) without random access response (RAR) monitoring for a candidate cell. FIGS. 12A and 12B illustrate an example of a unified / common TCI framework. FIG. 13 is a diagram illustrating an example of TCI state information elements (or RRC parameters). FIG. 14 is a diagram illustrating an example of an RS serving as a QCL source. FIGS. 15A to 15C are diagrams illustrating an example of a QCL rule. FIG. 16 is a conceptual diagram illustrating an example of a method for determining a TCI state switching delay according to the first embodiment. FIG. 17 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 18 is a diagram illustrating an example of a configuration of a base station according to an embodiment. FIG. 19 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment. FIG. 20 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to an embodiment. FIG. 21 is a diagram illustrating an example of a vehicle according to an embodiment.

[0011] (TCI, spatial relationship, QCL) In NR, it is considered to control the reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, and encoding) in a UE of at least one of a signal and a channel (referred to as a signal / channel) based on a transmission configuration indication state (TCI state).

[0012] The TCI state may represent that which is applied to a downlink signal / channel, and the equivalent of the TCI state that is applied to an uplink signal / channel may be expressed as a spatial relation.

[0013] The TCI state is information about the Quasi-Co-Location (QCL) of signals / channels, and may also be called spatial reception parameters, spatial relation information, etc. The TCI state may be configured in the UE for each channel or signal.

[0014] The QCL is an index indicating the statistical properties of signals / channels. For example, if a signal / channel has a QCL relationship with another signal / channel, it may mean that it can be assumed that at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, and a spatial parameter (e.g., a spatial Rx parameter) is the same between these different signals / channels (i.e., the signals / channels have a QCL with respect to at least one of these).

[0015] The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be identified based on a spatial QCL. The QCL (or at least one element of the QCL) in the present disclosure may be replaced with sQCL (spatial QCL).

[0016] A plurality of types (QCL types) of QCL may be defined. For example, four QCL types A to D may be provided, each having different parameters (or parameter sets) that can be assumed to be the same. The parameters (which may be referred to as QCL parameters) are as follows: QCL type A (QCL-A): Doppler shift, Doppler spread, mean delay, and delay spread QCL type B (QCL-B): Doppler shift and Doppler spread QCL type C (QCL-C): Doppler shift and mean delay QCL type D (QCL-D): Spatial reception parameters.

[0017] The UE's assumption that a Control Resource Set (CORESET), channel, or reference signal has a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be referred to as a QCL assumption.

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

[0019] The TCI state may be, for example, information about the QCL between the channel of interest (in other words, the Reference Signal (RS) for that channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination thereof.

[0020] The channel / signal to which the TCI state is applied may be called a target channel / reference signal (target channel / RS), or simply a target, and the other signal may be called a reference reference signal (reference RS), a source RS, or simply a reference.

[0021] The channel for which the TCI state or spatial relationship is set (specified) may be, for example, at least one of a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), a physical uplink shared channel (PUSCH), and a physical uplink control channel (PUCCH).

[0022] Furthermore, the RS that has a QCL relationship with the channel may be at least one of, for example, a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), a tracking CSI-RS (also called a tracking reference signal (TRS)), a QCL detection reference signal (also called a QRS), a demodulation reference signal (DMRS), etc.

[0023] An SSB is a signal block including at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). An SSB may also be referred to as an SS / PBCH block.

[0024] An RS of QCL type X in a TCI state may refer to an RS that has a QCL type X relationship with a certain channel / signal (DMRS), and this RS may be called a QCL source of QCL type X in the TCI state.

[0025] (L1 / L2 Inter-Cell Mobility) As described above, it is being considered that a UE performs UL transmission to one or more cells / TRPs. The following scenario 1 or scenario 2 can be considered as a procedure in this case. In the present disclosure, the term "serving cell" may be replaced with the TRP in the serving cell. The terms "layer 1 / layer 2" (L1 / L2) and "DCI / Medium Access Control Control Element (MAC CE)" may be interchangeable. In the present disclosure, a physical cell identity (PCI) different from the physical cell identity (PCI) of the current serving cell may be simply referred to as a "different PCI." The terms "non-serving cell," "cell having a different PCI," and "additional cell" may be interchangeable.

[0026] <Scenario 1> Scenario 1 corresponds to, for example, multi-TRP inter-cell mobility, but may be a scenario that does not correspond to multi-TRP inter-cell mobility.

[0027] (1) The UE receives from the serving cell the configuration necessary for using radio resources for data transmission and reception, including the SSB configuration for beam measurement of the TRP corresponding to a PCI different from that of the serving cell and the resources of the different PCI. (2) The UE performs beam measurement of the TRP corresponding to the different PCI and reports the beam measurement results to the serving cell. (3) Based on the above report, the Transmission Configuration Indication (TCI) state associated with the TRP corresponding to the different PCI is activated by L1 / L2 signaling from the serving cell. (4) The UE transmits and receives using UE-dedicated channels on the TRP corresponding to the different PCI. (5) The UE must always cover the serving cell, including in the case of multiple TRPs. As in conventional systems, the UE must use common channels from the serving cell, such as the Broadcast Control Channel (BCCH) and the Paging Channel (PCH).

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

[0029] Figure 1A shows an example of UE movement in Rel. 17. Assume that the UE moves from a cell (serving cell) with PCI #1 to a cell (additional cell) with PCI #3 (which overlaps with the serving cell). In this case, Rel. 17 does not support switching of serving cells via L1 / L2.

[0030] An additional cell is a cell with an additional PCI that is different from the PCI of the serving cell. The UE can receive / transmit UE-dedicated channels from the additional cell. The UE needs to be within the coverage of the serving cell to receive UE common channels (e.g., system information / paging / short messages). When the UE moves out of the coverage of the serving cell, a cell change is required, such as by handover (also called L3 mobility).

[0031] <Scenario 2> In scenario 2, L1 / L2 inter-cell mobility is applied. With L1 / L2 inter-cell mobility, the serving cell can be changed using functions such as beam control without RRC reconfiguration. In other words, transmission and reception with an additional cell is possible without handover. Since handover requires RRC reconnection, which results in a period when data communication is unavailable, by applying L1 / L2 inter-cell mobility that does not require handover, data communication can be continued even when the serving cell is changed. Scenario 2 may be applied, for example, in Rel. 18. In scenario 2, for example, the following procedure is performed.

[0032] (1) The UE receives SSB configuration for a cell with a different PCI (additional cell) from the serving cell for beam measurement / serving cell change. (2) The UE performs beam measurement for the cell using the different PCI and reports the measurement results to the serving cell. (3) The UE may receive the configuration for the cell with a different PCI (serving cell configuration) via higher layer signaling (e.g., RRC). That is, pre-configuration for the serving cell change may be performed. This configuration may be performed together with or separately from the configuration in (1). (4) Based on the above report, the TCI state of the cell with a different PCI may be activated via L1 / L2 signaling in accordance with the serving cell change. The activation of the TCI state and the serving cell change may be performed separately. (5) The UE changes the serving cell (assumed serving cell) and starts reception / transmission using the pre-configured UE-dedicated channel and TCI state.

[0033] That is, in Scenario 2, the serving cell (the serving cell assumed by the UE) is updated by L1 / L2 signaling. Scenario 2 may be applied in Rel. 18.

[0034] Figure 1B shows an example of UE mobility in Rel. 18. In Rel. 18, the serving cell is switched by L1 / L2 (e.g., DCI / MAC CE). The UE can receive / transmit UE-dedicated channels / common channels to / from the new serving cell (or target serving cell). The UE may move out of the coverage of the current serving cell (e.g., current serving cell).

[0035] <L1L2-triggered mobility (LTM) procedure> Fig. 2 is a diagram showing an example of the LTM procedure. Note that L1 / L2 inter-cell mobility and L1L2-triggered mobility (LTM) may be interpreted as interchangeable. Note that the procedure in Fig. 2 corresponds to the above-mentioned scenario 2. Each procedure in Fig. 2 will be described in detail below.

[0036] 1: After RRC connection, the UE sends a Measurement Report message to the base station (gNB). The gNB decides to use LTM based on the Measurement Report and starts preparing the candidate cell.

[0037] 2: The gNB sends an RRCReconfiguration message to the UE including LTM candidate cell configurations for one or more candidate cells.

[0038] 3: The UE stores the received LTM candidate cell configuration and sends an RRCReconfigurationComplete message to the gNB.

[0039] 4a / 4b: Before receiving the cell switch command, the UE performs DL / UL synchronization with the candidate cell and acquires the timing advance (TA).

[0040] 5: The UE performs L1 measurements on the configured candidate cell and transmits a lower layer (physical layer, L1) measurement report to the gNB. Note that the UE may transmit the measurement report to the gNB before UL synchronization with the candidate cell. Step 5 may be performed between steps 4a / 4b described above. Furthermore, activation of the TCI state between the UE and the current serving cell may be performed between steps 4b and 5.

[0041] 6: The gNB decides to perform a cell switch to the target cell and sends a MAC CE to the UE to trigger the cell switch, including the candidate configuration index of the target cell. As a result, the UE's cell configuration is switched to that of the target cell.

[0042] 7: If the cell switch requires the UE to perform a random access procedure, the UE performs a random access procedure toward the target cell. Note that the UE may perform the random access procedure in response to a RACH procedure request from the gNB.

[0043] 8: The UE notifies the gNB that the cell switch to the target cell has been successfully completed.

[0044] Note that the UE may perform the above steps 4 to 8 multiple times based on the LTM candidate cell configuration received in step 2 for the next LTM cell switch.

[0045] <Reduced Interruption Time> In Rel. 18 L1 / L2 inter-cell mobility (e.g., the above-mentioned scenario 2), the UE can reduce the time without data transmission (interruption time). When Rel. 18 LTM is applied, the time without data transmission (interruption time) can be reduced compared to the method of handover based on L3 measurement results (L3 handover). Specific processes for each are described below.

[0046] Figure 3 shows an example comparison between L3 handover and Rel. 18 LTM. In the case of L3 handover, the UE first performs L3 measurements and decides to perform handover based on the measurement results. Then, the UE and the current serving cell perform RRC reconfiguration. The UE then performs DL and UL synchronization with the target serving cell. The UE performs L1 measurements / reports for the target serving cell, receives beam instructions, and then transmits the first UL data to the target serving cell. In this case, the UE does not transmit UL data during the period from the handover decision to the first UL data transmission (interruption time).

[0047] In the Rel. 18 LTM case, the UE first performs L3 measurements. Then, the UE, the current serving cell, and the target serving cell perform RRC reconfiguration. Then, the UE establishes DL synchronization with the target serving cell. Then, the UE performs L1 measurements / reports to the current serving cell and the target serving cell to establish UL synchronization. Then, the current serving cell sends a cell switch command (including beam indication) to the UE via L1 / L2 (DCI / MAC CE). Then, the UE transmits the first UL data to the target serving cell. In this case, the period from receiving the cell switch command to transmitting the first UL data is the UL transmission interruption time, but this interruption time is shorter than in the case of L3 handover.

[0048] (Setting of Multiple Candidate Cells) FIG. 4 is a diagram showing an example of association between a serving cell and a candidate cell. SpCell #0, SCell #1, or SCell #2 is assumed to be a serving cell. Note that SpCell means a special cell (including a primary cell (PCell) and a primary secondary cell (PSCell)). SCell means a secondary cell. SpCell #0 is associated with candidate cell #0-1, candidate cell #0-2, and candidate cell #0-3. SCell #1 is associated with candidate cell #1-1. SCell #2 is associated with candidate cell #2-1 and #2-2. In this way, one or more candidate cells (candidate serving cells) may be associated with a serving cell.

[0049] Regarding the setting of candidate cells (candidate cells) when changing the serving cell, for example, the following options 1 and 2 are possible.

[0050] <Option 1> As with inter-cell mobility in Rel. 17, the information in the serving cell configuration (ServingCellConfig) may include information about multiple candidate cells. In this case, the multiple candidate cells need to share the same configurations of PDCCH / PDSCH / UL, etc. as the serving cell.

[0051] For example, in inter-cell mobility in Rel. 17, "mimoParam-r17" is added under the serving cell configuration (ServingCellConfig), and PCI configuration information is added. mimoParam-r17 may include additionalPCI-ToAddModList-r17, which is an information list of additional SSBs with PCIs different from the PCI of the serving cell. The same configuration as the serving cell may be applied to candidate cells (additional cells, cells with additionalPCI), with the exception of some information.

[0052] <Option 2> Multiple candidate cells may be associated with each serving cell by reusing the carrier aggregation (CA) configuration framework, with a complete configuration (e.g., ServingCellConfig) corresponding to each cell. That is, the candidate cells may not share configuration information with the serving cell and may have a separate configuration. The UE is provided with the complete configuration for each candidate cell, allowing it to communicate properly with the candidate cells.

[0053] In the CA configuration framework, an SpCell can be configured for each cell group, and multiple SCells can be added. By reusing the CA framework, a serving cell can be configured for each cell group for L1 / L2 inter-cell mobility, and multiple candidate cells can be configured. Candidate cells can be activated / deactivated by the MAC CE. Candidate cells can be activated / deactivated by activating / deactivating TCI information corresponding to the candidate cells by the MAC CE. This method is considered to be beneficial for reducing the complexity of UE operations.

[0054] 5A is a diagram showing a first example of Option 2 for candidate cell configuration. In the example of FIG. 5A, a common candidate cell pool for cell switching in the MCG / SCG is applied to the candidate cells. In other words, the candidate cells are treated as one pool (group) regardless of frequency band.

[0055] 5B is a diagram showing a second example of the candidate cell configuration option 2. In the example of FIG. 5B, multiple cell groups are configured, and cell group switching is possible by L1 / L2 signaling. Candidate cells are configured for each cell group, and the configuration for each group includes the indices of the corresponding SpCell and SCell.

[0056] (Signaling for Serving Cell Change Indication) Implicit or explicit signaling for serving cell change indication will now be described.

[0057] [Aspect 1] In aspect 1, implicit signaling for a serving cell change indication is described.

[0058] [[Option 1-1]] When a specific control resource set (CORESET) (e.g., at least one of CORESET#0, CORESET of CH5 Type0-CSS, and CORESET of CH6 / CH7 / CH8 CSS) is indicated (activated) by a MAC CE together with one or more TCI states associated with cells of PCIs different from that of the serving cell (when one or more TCI states associated with cells of PCIs different from that of the serving cell are indicated / activated by a MAC CE for a specific CORESET), the UE may determine to change the serving cell to another cell (cell x, a cell with a different PCI). In other words, this activation may implicitly indicate that the serving cell will be changed to another cell.

[0059] In this case, the UE may update 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.

[0060] [[Option 1-2]] When the MAC CE activates / deactivates the TCI states of the PDSCH, if all such TCI states activated by the MAC CE are associated with the same cell x having a PCI different from that of the serving cell, the UE may determine to change the serving cell to another cell (cell x), i.e., this association may implicitly indicate that the serving cell will be changed to another cell.

[0061] In the case where this option applies, if the NW (base station) does not change the serving cell, when the MAC CE activates the TCI state of a PDSCH associated with a cell with a different PCI, it must also include the TCI state related to another cell (e.g., the current serving cell or a second cell with a different PCI).

[0062] [[Options 1-3]] If the MAC CE activates / deactivates unified TCI states (e.g., corresponding to the unified TCI framework in Rel. 17) and all activated unified TCI states are associated with the same cell x with different PCIs, the UE may determine to change the serving cell to another cell (cell x), i.e., this association may implicitly indicate that the serving cell will be changed to another cell.

[0063] [Aspect 2] In aspect 2, explicit signaling for a serving cell change instruction will be described. In aspect 2, for example, the above-mentioned scenario 2 is applied.

[0064] [Option 2-1] An example of a serving cell change instruction will be described below. Note that activation / deactivation of a non-serving cell, change of a serving cell, and transmission / reception with another cell (non-serving cell) having a physical cell ID different from the physical cell ID of the serving cell may be interpreted as interchangeable.

[0065] The UE may receive a new MAC CE including at least one of the fields (information) indicating the following (1) to (3) corresponding to a non-serving cell, which is used for activating / deactivating the non-serving cell. When the UE receives the MAC CE, the UE may determine to change the serving cell to another cell (non-serving cell). Furthermore, the UE may control transmission and reception of DL signals / UL signals with the non-serving cell based on the information. Note that the non-serving cell may be one or multiple. In the example shown below, a MAC CE including multiple fields indicating multiple non-serving cell indexes is applied.

[0066] (1) Serving cell ID, (2) BWP ID, and (3) Non-serving cell ID used for activation. The non-serving cell ID may be replaced with any information corresponding to the non-serving cell (that can identify the non-serving cell).

[0067] As an example of (3), any of (3-1) to (3-5) may be applied. (3-1) PCI (PCI used directly). For example, 10 bits are used. (3-2) Re-creation index (new ID) of non-serving cells. The new ID may be associated with a part of the PCI and configured only for serving and non-serving cells used (available) by the UE. The new ID can reduce the number of bits compared to the PCI. (3-3) CSI reporting configuration ID (CSI-ReportConfigId) (when CSI-ReportConfig corresponds to one or more non-serving cells). (3-4) CSI resource configuration ID (CSI-ResourceConfigId) (when CSI-ResourceConfigId corresponds to one or more non-serving cells). (3-5) Bitmap indicating activation / deactivation of each non-serving cell. The size (number of bits) of the bitmap may be the same as the number of non-serving cells configured on this CC. For example, when activating the second non-serving cell among three non-serving cells, "010" is set.

[0068] At least one of the pieces of information included in the MAC CE may be included in the DCI. Alternatively, at least one of the serving cells activated by the MAC CE may be indicated by the DCI. The MAC CE / DCI may include a field indicating the TCI status / SSB / CSI-RS from a cell having a different PCI so that the UE can recognize the DL beam to monitor on the target cell (post-change serving cell). The UE may create and transmit a beam report (CSI report) using the TCI status / SSB / CSI-RS.

[0069] [[Option 2-2]] The UE may receive a MAC CE in which a new 1-bit field "C" is added to the existing MAC CE. The field indicates whether to change the serving cell. The UE may receive the MAC CE and determine whether to change the serving cell to another cell based on the field.

[0070] [Option 2-3] In addition to the MAC CE in Option 2-2, the MAC CE may further include a field indicating the serving cell index / PCI / other ID (such as the new ID in Option 2-1 above), and a field indicating the TCI state / SSB / CSI-RS of the target cell (the serving cell after the change).

[0071] In this way, since the instruction for the serving cell change instruction is indicated by the MAC CE / DCI, the UE can appropriately change the serving cell.

[0072] [Serving Cell Switch Example 1] Figure 6 is a diagram showing Serving Cell Switch Example 1. For example, in a serving cell SpCell #0 of an MCG / SCG, if an instruction to change the serving cell to candidate cell #0-2 is given by L1 / L2 signaling, candidate cell #0-2 becomes the new serving cell SpCell #0. Also, for example, in a serving cell SCell #2 of an MCG / SCG, if an instruction to change the serving cell to candidate cell #2-1 is given by L1 / L2 signaling, candidate cell #2-1 becomes the new serving cell SCell #2.

[0073] [Serving Cell Switch Example 2] The RRC / MAC CE may configure a global candidate cell ID (cell #3, ..., 8) for each cell group, band, FR, and UE. The UE may be instructed to switch the serving cell by the global candidate cell ID.

[0074] Figure 7 illustrates a serving cell switch example 2. Similar to Figure 5A, a pool of multiple candidate cells can be configured, and the serving cell can be switched to any (activated) candidate cell in the pool by L1 / L2 signaling. In this case, the configured candidate cell can be either an SpCell or an SCell based on the L1 / L2 signaling.

[0075] The UE may receive an indication of a serving cell change (from cell #2-1 to candidate cell #4) via MAC CE / DCI, and the indicated candidate cell #4 becomes the SpCell of the new cell group (MCG / SCG).

[0076] Serving Cell Switch Example 3 The RRC / MAC CE may configure a cell group, and the UE may perform a serving cell switch based on the cell group switch.

[0077] 8 is a diagram showing a serving cell switch example 3. The UE receives an instruction to change the cell group having the serving cell (change to candidate cell group #1) via MAC CE / DCI. Then, the cells included in the indicated candidate cell group #1 become the new serving cells (SpCell, SCell). For example, candidate cells #0, #1, and #2 included in the indicated candidate cell group #1 become the new SpCell #0, SCell #1, and SCell #2. In other words, the serving cell group is switched.

[0078] (Overview of L1L2-triggered mobility (LTM)) In L1L2-triggered mobility (LTM) supported in Rel. 18 and later, L1 inter-frequency measurements (e.g., L1 inter-frequency measurements) may be supported. Also, DL synchronization / UL synchronization of a candidate cell based on at least SSB before a cell switch command may be supported.

[0079] 9 is a diagram showing an overview of L1L2-triggered mobility (LTM). LTM and L1 / L2 inter-cell mobility may be interpreted as interchangeable.

[0080] The UE receives candidate cell configurations from the NW during UE reconfiguration. RRC , including Tproccesing1 / Tproccesing2. T RRC(e.g., max. 10 ms) is the processing time for RRC Reconfiguration carrying candidate cell configurations. Tproccesing1 / Tproccesing2 (e.g., max. 20 ms for same FR, max. 40 ms for different FR) are the time for UE processing before and after the cell switch command, respectively. This may include L2 / 3 reconfiguration, RF retuning, baseband retuning, security update if required, etc.

[0081] DL synchronization is T search , T Δ , T margin Includes: T search (e.g., 0 ms if the cell is known, up to 60 ms if the cell is unknown) is the time it takes to search for the target cell. Δ is the time for fine tracking and acquisition of all timing information. T margin (e.g., max. 2 ms) is the time for post-processing of SSB and CSI-RS.

[0082] L1 measurement is T meas (including SMTC period (e.g. 20 ms)). T meas is the measured delay from the appearance of the target to the cell switch command.

[0083] UL synchronization is T IU , T RAR , T cmd Includes: T IU (e.g., up to 15 ms) is the time of uncertainty interruption in acquiring the first available PRACH opportunity in the new cell. RAR (e.g., maximum 4 ms) is the RAR delay time. cmd (e.g., maximum 5 ms) is the processing time for L1 / L2 commands (HARQ and paging).

[0084] T cmd T after first-datais the time at which the UE performs its first DL reception / UL transmission on the indicated beam of the target cell after RAR.

[0085] 10 is a diagram showing an example of a PDCCH-ordered RACH with RAR monitoring. In the present disclosure, a source cell and a source cell group may be interchangeable. Also, a candidate cell and a candidate cell group may be interchangeable.

[0086] The source cell may transmit information regarding the configuration of the candidate cell (e.g., candidate cell configuration information) to the UE. The source cell may also transmit a PDCCH order (e.g., DCI format 1_0) used to trigger the PRACH to the UE. The PDCCH order (or DCI) may indicate a candidate cell (e.g., one candidate cell) / Random Access Occasion (RO) that is the target of the PRACH trigger / transmission. The UE transmits the PRACH in the RACH procedure to the candidate cell based on the PDCCH order to acquire the TAG / TA.

[0087] Next, the source cell transmits a response signal (RAR) to the PRACH to the UE. The RAR may include information about the TA (e.g., TA indication). The RAR (e.g., the PDSCH containing the RAR / the PDCCH scheduling the PDSCH) may be monitored in a specific search space (e.g., the common search space (CSS)) of a specific cell (e.g., the SpCell) among the current serving cells (only within the Distributed Unit (DU)). Then, the source cell performs TA adjustment (e.g., TA maintenance).

[0088] Next, the source cell may send a cell switch command to the UE. TA information may also be moved / notified from the source cell to the target cell. The UE may control UL transmission based on the acquired TA after cell switching. For example, the UE may perform the first UL transmission using the initial TA if UL synchronization with all candidate cells has not been completed after the initial cell switch.

[0089] Fig. 11 is a diagram showing an example of a PDCCH ordered RACH without RAR monitoring. Only the differences between Fig. 11 and Fig. 10 will be described.

[0090] In the example of Fig. 11, the PDCCH order used to trigger the PRACH may indicate one or more candidate cells (e.g., multiple candidate cells) / random access occasions that are targets for PRACH trigger / transmission. The UE may transmit PRACH in the RACH procedure to candidate cells based on the PDCCH order to acquire multiple TAGs / TAs. The source cell does not transmit a PRACH response signal (e.g., RAR). The source cell may indicate TA information (e.g., TA indication) to the UE using a cell switch command.

[0091] In the present disclosure, a RACH without RAR and a RACH without RAR monitoring (e.g., a RACH without RAR monitoring) may be interpreted as interchangeable. A RACH may be interpreted as a PRACH transmission triggered by a PDCCH order. A RACH procedure / PRACH transmission without RAR monitoring may be interpreted as a RACH procedure / PRACH transmission in which RAR monitoring is not required, or a RACH procedure / PRACH transmission in which RAR monitoring is not required.

[0092] (Unified / Common TCI Framework) The unified TCI framework allows multiple types of channels / RSs (UL / DL) to be controlled by a common framework. The unified TCI framework does not specify TCI states or spatial relationships for each channel as in Rel. 15. Instead, it may specify a common beam (common TCI state) and apply it to all UL and DL channels, or it may apply a common beam for UL to all UL channels and a common beam for DL ​​to all DL channels.

[0093] One common beam for both DL and UL, or one common beam for DL ​​and one common beam for UL (two common beams overall) are considered.

[0094] The UE may assume the same TCI state for UL and DL (joint TCI state, joint TCI pool, joint common TCI pool, joint TCI state set). The UE may assume different TCI states for 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).

[0095] The default beams for UL and DL may be aligned via MAC CE based beam management (MAC CE level beam indication). The default TCI state of the PDSCH may be updated to align with the default UL beam (spatial relationship).

[0096] DCI-based beam management (DCI-level beam indication) may indicate a common beam / unified TCI state from the same TCI pool for both UL and DL (joint common TCI pool, joint TCI pool, set). X (>1) TCI states may be activated by the MAC CE. The UL / DL DCI may select one from the X active TCI states. The selected TCI state may apply to both UL and DL channels / RS.

[0097] The TCI pool (set) may be multiple TCI states configured by RRC parameters, or multiple TCI states (active TCI states, active TCI pools, sets) activated by MAC CE among the multiple TCI states configured by RRC parameters. Each TCI state may be a QCL type A / D RS. SSB, CSI-RS, or SRS may be configured as the QCL type A / D RS.

[0098] The number of TCI states corresponding to each of one or more TRPs may be specified. For example, the number N (≧1) of TCI states applied to UL channels / RSs (UL TCI states) and the number M (≧1) of TCI states applied to DL channels / RSs (DL TCI states) may be specified. At least one of N and M may be notified / configured / instructed to the UE via higher layer signaling / physical layer signaling.

[0099] In the present disclosure, when N=M=X (X is any integer), it may mean that X TCI states (joint TCI states) common to UL and DL (corresponding to X TRPs) are notified / configured / indicated to the UE. Also, when N=X (X is any integer) and M=Y (Y may be any integer, Y=X), it may mean that X UL TCI states (corresponding to X TRPs) and Y DL TCI states (i.e., separate TCI states) (corresponding to Y TRPs) are notified / configured / indicated to the UE.

[0100] For example, when N=M=1 is written, this may mean that a TCI state common to one UL and DL for a single TRP is notified / configured / indicated to the UE (joint TCI state for a single TRP).

[0101] Also, for example, when N=1 and M=1 are written, this may mean that one UL TCI state and one DL TCI state for a single TRP are separately notified / configured / instructed to the UE (separate TCI states for a single TRP).

[0102] Also, for example, when N=M=2 is written, this may mean that a TCI state common to multiple (two) ULs and DLs for multiple (two) TRPs is notified / configured / instructed to the UE (joint TCI state for multiple TRPs).

[0103] Also, for example, when N=2 and M=2, it may mean that multiple (two) UL TCI states and multiple (two) DL TCI states for multiple (two) TRPs are notified / configured / instructed to the UE (separate TCI states for multiple TRPs).

[0104] In the above example, the values ​​of N and M are 1 or 2, but the values ​​of N and M may be 3 or more, and N and M may be different.

[0105] Support for N = M = 1 is being considered for Rel. 17. For example, it may be supported to indicate one common beam (e.g., a common beam) using RRC / MAC CE / DCI, and the common beam may be applied to multiple DL / UL channels / reference signals. Other cases may also be supported in Rel. 18 and later.

[0106] 12A and 12B illustrate an example of a unified TCI framework. FIG. 12A illustrates an example of a joint DL / UL TCI state, and FIG. 12B illustrates an example of a separate TCI state.

[0107] In the example of Figure 12A, RRC parameters (information elements) configure multiple TCI states for both DL and UL. In this disclosure, the TCI states configured by the RRC parameters may be referred to as configured TCI states or configured TCI states (e.g., configured TCI states). The MAC CE may activate multiple TCI states from the configured TCI states. The DCI may indicate one of the activated TCI states. In this disclosure, the TCI state indicated by the DCI may be referred to as indicated TCI state or indicated TCI state (e.g., indicated TCI state).

[0108] The DCI may be a UL DCI (e.g., a DCI used to schedule a PUSCH) or a DL DCI (e.g., a DCI used to schedule a PDSCH). The indicated TCI state may apply to at least one (or all) of the UL / DL channels / RS. One DCI may indicate both a UL TCI and a DL TCI.

[0109] In the example of this figure, a point may be one TCI state that applies to both UL and DL, or two TCI states that apply to UL and DL respectively.

[0110] At least one of the multiple TCI states configured by the RRC parameters and the multiple TCI states activated by the MAC CE may be referred to as a TCI pool (common TCI pool, joint TCI pool, TCI state pool). The multiple TCI states activated by the MAC CE may be referred to as an active TCI pool (active common TCI pool).

[0111] In the present disclosure, higher layer parameters (RRC parameters) for setting multiple TCI states may be referred to as configuration information for setting multiple TCI states, or simply as "configuration information." Also, in the present disclosure, being instructed to set one of multiple TCI states using DCI may mean receiving indication information instructing one of the multiple TCI states included in DCI, or may simply mean receiving "instruction information."

[0112] In the example of Figure 12B, the RRC parameters configure multiple TCI states (joint common TCI pools) for both DL and UL. The MAC CE may activate multiple TCI states (active TCI pools) from the configured multiple TCI states. Separate active TCI pools for each of the UL and DL may be configured / activated.

[0113] The DL DCI or a new DCI format may select (indicate) one or more (e.g., one) TCI states. The selected TCI state may apply to one or more (or all) DL channels / RSs. The DL channels may be PDCCH / PDSCH / CSI-RS. The UE may determine the TCI state of each DL channel / RS using the TCI state behavior (TCI framework) of Rel. 16. The UL DCI or a new DCI format may select (indicate) one or more (e.g., one) TCI states. The selected TCI state may apply to one or more (or all) UL channels / RSs. The UL channels may be PUSCH / SRS / PUCCH. In this way, different DCIs may indicate UL TCI and DL DCI separately.

[0114] It is assumed that in Rel. 17 NR and later, the MAC CE / DCI supports beam activation / indication to a TCI state associated with a different physical cell identifier (PCI), and in Rel. 18 NR and later, the MAC CE / DCI supports indicating a serving cell change to a cell with a different PCI.

[0115] The method of setting / indicating the TCI state (e.g., joint DL / UL TCI state) in Fig. 12A and the method of setting / indicating the application of the TCI state (e.g., separate TCI state) in Fig. 12B may be switched and applied. Whether the joint DL / UL TCI state or the separate TCI state is applied may be configured by a base station to the UE by a higher layer parameter.

[0116] (Indicated TCI State / Configured TCI State) For Rel. 17 TCI states, unified / common TCI state may mean the Rel. 17 TCI state indicated using (Rel. 17) DCI / MAC CE / RRC (indicated Rel. 17 TCI state).

[0117] In the present disclosure, the terms indicated Rel. 17 TCI state, indicated TCI state, unified / common TCI state, TCI state applicable to multiple types of signals (channels / RS), and TCI state for multiple types of signals (channels / RS) may be interpreted interchangeably.

[0118] The indicated Rel. 17 TCI state may be shared with at least one of the UE-specific reception of PDSCH / PDCC (updated using Rel. 17 DCI / MAC CE / RRC), PUSCH of dynamic grant (DCI) / configured grant, and multiple (e.g., all) dedicated PUCCH resources. The TCI state indicated by DCI / MAC CE / RRC may be referred to as the indicated TCI state or the unified TCI state.

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

[0120] The configured Rel. 17 TCI state may not be shared with at least one of the UE-specific reception of PDSCH / PDCC (updated using Rel. 17 DCI / MAC CE / RRC), PUSCH of dynamic grant (DCI) / configured grant, and multiple (e.g., all) dedicated PUCCH resources. The configured Rel. 17 TCI state may be configured by RRC / MAC CE per CORESET / per resource / per resource set, and may not be updated even if the indicated Rel. 17 TCI state (common TCI state) is updated.

[0121] It is being considered that the indicated Rel. 17 TCI state will be applied to UE-specific channels / signals (RS), and that the UE will be notified by higher layer signaling (RRC signaling) whether the indicated Rel. 17 TCI state or the configured Rel. 17 TCI state will be applied to non-UE-specific channels / signals.

[0122] It is being considered that the RRC parameters for the configured Rel. 17 TCI state (TCI state ID) will have the same configuration as the RRC parameters for the TCI state in Rel. 15 / 16. It is also being considered that the configured Rel. 17 TCI state will be configured / instructed per CORESET / per resource / per resource set using RRC / MAC CE. It is also being considered that the UE will determine the configuration / instruction based on specific parameters.

[0123] It is considered that the UE updates the indicated TCI state and the configured TCI state separately. For example, if the unified TCI state for the indicated TCI state is updated, the UE may not update the configured TCI state. It is also considered that the UE may determine whether to update the configured TCI state based on a specific parameter.

[0124] Furthermore, regarding the PDCCH / PDSCH, it is being considered to use higher layer signaling (RRC / MAC CE) to switch whether the indication Rel. 17 TCI state is applied or not (the configured Rel. 17 TCI state is applied, or a TCI state configured separately from the indication Rel. 17 TCI state is applied).

[0125] Regarding intra-cell beam indication (TCI state indication), it is being considered to support Rel. 17 TCI state indication for a UE-specific CORESET and its associated PDSCH, and a non-UE-specific CORESET and its associated PDSCH.

[0126] Also, for inter-cell beam indication (e.g., L1 / L2 inter-cell mobility), it is considered that indication Rel. 17 TCI states will be supported for UE-specific CORESETs and their associated PDSCHs.

[0127] In Rel. 15, whether to indicate the TCI state for CORESET #0 was up to the implementation of the base station. In Rel. 15, for CORESET #0 for which a TCI state is indicated, the indicated TCI state is applied. For CORESET #0 for which a TCI state is not indicated, the SSB and QCL selected at the time of the latest (most recent) PRACH transmission are applied.

[0128] In the unified TCI state framework for Rel. 17 and later, the TCI state for CORESET #0 is being considered.

[0129] For example, in the unified TCI state framework for Rel. 17 and later, whether or not to apply the indicated Rel. 17 TCI state associated with the serving cell for the Rel. 17 TCI state indication in CORESET #0 is configured by RRC for each CORESET, and if not, the legacy MAC CE / RACH signaling mechanism may be used.

[0130] Note that the CSI-RS associated with the Rel. 17 TCI state applied to CORESET #0 may be QCL'd with the SSB associated with the serving cell PCI (physical cell ID) (similar to Rel. 15).

[0131] For CORESET #0, a CORESET with a common search space (CSS), and a CORESET with a CSS and a UE-specific search space (USS), whether to follow the Rel. 17 TCI state may be configured for each CORESET by an RRC parameter. If the Rel. 17 TCI state is not configured to be followed for that CORESET, the configured Rel. 17 TCI state may be applied to that CORESET.

[0132] For non-UE-dedicated channels / RSs (except CORESET), whether to follow the indicated Rel. 17 TCI state may be configured by an RRC parameter for each channel / resource / resource set. If the indicated Rel. 17 TCI state is not configured for that channel / resource / resource set, the configured Rel. 17 TCI state may apply to that channel / resource / resource set.

[0133] (Channels / RSs to which the indicated TCI state applies) The indicated TCI state by the MAC CE / DCI may apply to the following channels / RSs:

[0134] [PDCCH] - If followUnifiedTCIState is configured for CORESET0, the indicated TCI state applies. Otherwise, the Rel. 15 specifications apply for that CORESET. That is, CORESET0 follows the TCI state activated by the MAC CE or is QCL'd with SSB. - For CORESETs with USS / CSS type 3 and index other than 0, the indicated TCI state always applies. - For CORESETs with index other than 0 and at least CSS type other than 3, if followUnifiedTCIState is configured, the indicated TCI state applies. Otherwise, the configured TCI state for that CORESET applies to that CORESET.

[0135] [PDSCH] - The indicated TCI state always applies to all UE-dedicated PDSCHs. - For non-UE-dedicated PDSCHs (PDSCHs scheduled by DCI in CSS), the indicated TCI state may apply if followUnifiedTCIState is set (for the CORESET of the PDCCH that schedules that PDSCH). Otherwise, the configured TCI state for that PDSCH applies to that PDSCH. If followUnifiedTCIState is not set for a PDSCH, whether a non-UE-dedicated PDSCH follows the indicated TCI state may depend on whether followUnifiedTCIState is set for the CORESET used to schedule that PDSCH.

[0136] [CSI-RS] For an A-CSI-RS for CSI acquisition or beam management, if followUnifiedTCIState is set (for CORESET of the PDCCH that triggers that A-CSI-RS), the indicated TCI state applies. For other CSI-RSs, the configured TCI state for that CSI-RS applies.

[0137] [PUCCH] - For all dedicated PUCCH resources, the indicated TCI state always applies.

[0138] [PUSCH] - For dynamic / configured grant PUSCH, the indication TCI state always applies.

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

[0140] Active DL TCI State Switch (Switching) Delay for Unified TCI State The active DL TCI state switch (switching) delay requirement for unified TCI state may apply to UEs that have the parameter (DLorJoint-TCIState) configured for the DL channel in the serving cell.

[0141] This requirement may also apply to all serving cell lists simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, and simultaneousU-TCI-UpdateList4 in MR-DC / standalone NR, provided that all serving cells in the list have the same serving cell and BWP configured in the parameter (unifiedTCI-StateRef-r17).

[0142] The UE must complete the switching of the active DL TCI state within a delay time (TCI state switching delay).

[0143] If the target DL TCI state indicates an additional PCI that is different from the PCI of the configured serving cell, this requirement may apply if the following conditions are met: - The active BWP of the serving cell and the cell with the additional PCI are the same; - The center frequency, SCS, and SFN offset of the cell with the additional PCI are the same as those of the serving cell; - The cell with the additional PCI is known to the UE.

[0144] A cell with an additional PCI may be known if the following conditions are met: - The UE has sent a valid L3 measurement report for the cell with the additional PCI in the last 5 seconds before the L1-RSRP measurement is configured. - The timing offset between the serving cell and the cell with the additional PCI is within the CP of the corresponding SCS. Otherwise (if these conditions are not met), the cell with the additional PCI is unknown.

[0145] Also, the MAC CE-based downlink TCI state switching delay requirement applies to DL TCI state switching using a unified TCI state (separate DL TCI state / joint TCI state) switching frame.

[0146] If a source RS in DL TCI state / Joint TCI state is associated with a PCI different from the serving cell, this requirement applies if the cell with the different PCI meets the known cell condition described above. If the known cell condition is not met, a longer delay may be expected.

[0147] In the case of a joint TCI state switch, if the target PL-RS is not maintained, the UE is not expected to receive DL reception based on the target TCI state before completing the switch between the DL TCI state and the UL TCI state.

[0148] If the target TCI state is known, when the UE receives a PDSCH carrying (including) a MAC CE activation command in slot n, the UE can receive a UE-dedicated PDCCH / PDSCH in the first slot after the predetermined slot by applying the target TCI state of the serving cell in which the TCI state change occurred.

[0149] Here, the predetermined slot mentioned above is (n+T HARQ +3N slot subframe,μ+TO k *(T first-SSB +T SSB-proc) / NR slot length)-th slot.

[0150] The UE receives the data in slot (n+T HARQ +3N slot The UE can receive the UE-dedicated PDCCH / PDSCH by applying the old TCI state until the T HARQ is the timing between DL data transmission and acknowledgement.

[0151] Also, ・T first-SSB is the time for the first SSB transmission after the MAC CE to be decoded by the UE. The SSB corresponds to QCL Type A / Type C for the target TCI state. SSB-proc is, for example, 2 ms (milliseconds). k is 1 if the target TCI state is not in the list of active TCI states of the PDSCH / PDCCH, and 0 otherwise.

[0152] (QCL Rules for TCI States) As described above, Rel. 18 and later are expected to support L1 / L2 inter-cell mobility (e.g., L1L2-triggered mobility (LTM)). In this case, it is expected that each TCI state includes up to two QCL types (e.g., qcl-types), and that the source RS for each QCL type in the QCL information (e.g., QCL-Info) of the TCI state is provided based on at least the RS configuration for LTM.

[0153] 13 is a diagram showing an example of a TCI-State information element (e.g., a TCI-State information element) supported in Rel. 17 and earlier. The TCI-State information element (or an RRC parameter) may associate one or two DL reference signals with corresponding QCL types.

[0154] In the LTM supported by Rel. 18, it is also assumed that SSB is used for L1 measurements / L1 beam reports for candidate cells (e.g., non-serving cells before receiving a cell switch command) (e.g., only SSB-based L1 measurements / L1 beam reports are supported). Alternatively, it is also assumed that CSI-RS measurements for candidate cells are additionally supported in the LTM.

[0155] In Rel. 15-17, configuring an SSB as a QCL source (or QCL source RS) in the TCI state for a PDCCH / PDSCH is not supported. In Rel. 15-17, a TRS / CSI-RS can be configured as a QCL source for a DMRS of a PDCCH / PDSCH, and an SSB can be configured as a QCL source for the TRS / CSI-RS.

[0156] In LTM in Rel. 18 and later, it is assumed that TCI states (e.g., each TCI state having up to two QCL types (pcl-types) and at least one source RS of the QCL type of the TCI state) are provided based on the RS configuration for LTM, but sufficient consideration has not been given to the TCI states supported for candidate cells. If the TCI states (e.g., QCL type / source RS of QCL type, etc.) for candidate cells are not appropriately applied, degradation of communication quality may occur.

[0157] The QCL rules when synchronization signal blocks (e.g., SSB) cannot be set to the TCI state of DMRS for a given DL channel may be as follows:

[0158] The predetermined DL channel may be at least one of a PDCCH and a PDSCH. In the following description, the predetermined DL channel is exemplified as a PDCCH / PDSCH, but is not limited thereto.

[0159] If the SSB cannot be set to the TCI state of the DMRS of the PDCCH / PDSCH (or the SSB cannot be the QCL source of the DMRS of the PDCCH / PDSCH), the TRS / CSI-RS may be the QCL source (e.g., QCL source) of the DMRS of the PDCCH / PDSCH, and the SSB may be the QCL source of the TRS / CSI-RS (see Figure 14).

[0160] 14 shows an example in which the TRS / CSI-RS serves as a QCL source (e.g., a QCL source) for the DMRS of the PDCCH / PDSCH and the SSB serves as a QCL source for the TRS / CSI-RS for candidate cell #1. Candidate cell #1 may be a cell associated with a PCI different from the PCI of the serving cell.

[0161] In this case, at least one of the following QCL rules 1-1 to 1-3 may be applied / supported. In the present disclosure, the QCL rule may be read as a case.

[0162] The UE may assume that one of the QCL types in QCL Rule 1-1 to QCL Rule 1-3 is indicated by the TCI state indicated by the network (e.g., a base station). The TCI state indicated by the base station may be indicated by DCI / MAC CE / RRC. QCL Rule 1-1 to QCL Rule 1-3 may be applied / supported both when the unified TCI state (e.g., dl-OrJointTCI-StateList) is not configured and when the unified TCI state (e.g., dl-OrJointTCI-StateList) is configured, respectively (or either one of them).

[0163] All, one, or two of QCL rules 1-1 to 1-3 may be supported. The applied / supported QCL rules may be defined in a specification or may be configured in the UE by the base station using RRC parameters. The applicable QCL rules are not limited to these, and a combination of a QCL type A RS of one QCL rule and a QCL type D RS of another QCL rule may be applied.

[0164] [QCL Rule 1-1] QCL Rule 1-1 may be defined as follows: QCL Type A RS: TRS (with a different PCI) QCL Type D RS: Same CSI-RS resource as QCL Type A RS

[0165] The RS corresponding to the QCL Type A RS may be a CSI-RS in which a predetermined higher layer parameter (e.g., trs-Info) is configured (or a CSI-RS in a CSI-RS resource set in which trs-Info is configured). Furthermore, the RS corresponding to the QCL Type A RS may be configured to correspond to a PCI (e.g., PCI of a candidate cell / additional cell / non-serving cell) different from the PCI of the serving cell (see FIG. 15A). When LTM is configured / applied, RS resource configuration (e.g., CSI-RS resource configuration) for each candidate cell may be supported.

[0166] For example, the reference RS (e.g., TRS / CSI-RS) corresponding to QCL Type A / QCL Type D may further be a CSI-RS having a PCI different from the PCI of the serving cell. That is, as the reference RS (e.g., TRS / CSI-RS) corresponding to QCL Type A / QCL Type D, in addition to (or instead of) the CSI-RS corresponding to the PCI of the serving cell, a CSI-RS having a PCI different from the PCI of the serving cell may be used.

[0167] When LTM is configured / applied, the UE may assume that the pseudo-colocation type of the TCI state (e.g., TCI-State or indicated DLorJointTCIState) indicated by the base station is a TRS of a PCI different from the PCI of the serving cell (e.g., QCL type A) or a CSI-RS of the same type as QCL type A (e.g., QCL type D).

[0168] As an example, Type-A RS and Type-D RS in QCL Rule 1-1 may be defined as follows: Type-A RS is a CSI-RS resource of a non-zero power CSI-RS resource set (e.g., NZP-CSI-RS-ResourceSet) for which upper layer parameters (e.g., trs-Info) are configured, Type-D RS is the same CSI-RS resource as Type-A RS, and the Reference RS may further be a CSI-RS with a PCI different from the PCI of the serving cell.

[0169] [QCL Rule 1-2] QCL Rule 1-2 may be defined as follows: QCL Type A RS: TRS (with a different PCI) QCL Type D RS: CSI-RS with repetition (with a different PCI)

[0170] The RS corresponding to the QCL Type-A RS may be configured for a PCI different from the PCI of the serving cell (e.g., the PCI of a candidate cell / additional cell / non-serving cell) (see FIG. 15B). When LTM is configured / applied, RS resource configuration (e.g., CSI-RS resource configuration) for each candidate cell may be supported.

[0171] The RS corresponding to the QCL type D RS may be a CSI-RS in which a higher layer parameter related to repetition (for example, repetition) is configured.

[0172] For example, the reference RS (e.g., TRS / CSI-RS) corresponding to QCL Type A / QCL Type D may further be a CSI-RS having a PCI different from the PCI of the serving cell. That is, as the reference RS (e.g., TRS / CSI-RS) corresponding to QCL Type A / QCL Type D, in addition to (or instead of) the CSI-RS corresponding to the PCI of the serving cell, a CSI-RS having a PCI different from the PCI of the serving cell may be used.

[0173] In this case, if multiple (e.g., two) reference RSs have PCIs different from that of the serving cell, the PCIs different from that of the serving cell may be the same PCI. That is, two reference RSs (e.g., resource RSs) may be configured to be associated with the same candidate cell (or a non-serving cell). The two reference RSs may 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).

[0174] When LTM is configured / applied, the UE may assume that the pseudo-colocation type of the TCI state (e.g., TCI-State or indicated DLorJointTCIState) indicated by the base station is a TRS of a PCI different from the PCI of the serving cell (e.g., QCL type A), or a CSI-RS corresponding to a PCI different from the PCI of the serving cell and for which repetition is set.

[0175] As an example, Type-A RS and Type-D RS in QCL Rule 1-2 may be defined as follows: Type-A RS are CSI-RS resources in a non-zero-power CSI-RS resource set (e.g., NZP-CSI-RS-ResourceSet) configured with an upper layer parameter (e.g., trs-Info), Type-D RS are CSI-RS resources in a non-zero-power CSI-RS resource set (e.g., NZP-CSI-RS-ResourceSet) configured with an upper layer parameter repeition, and the Reference RS may also be a CSI-RS with a PCI different from the PCI of the serving cell. If both Reference RSs have a PCI different from that of the serving cell, the PCI different from that of the serving cell may be the same PCI.

[0176] [QCL Rules 1-3] QCL Rules 1-3 may be defined as follows: QCL Type A RS: CSI-RS without trs-Info and repetition (with a different PCI) QCL Type D RS: Same CSI-RS resource as QCL Type A RS

[0177] The RS corresponding to the QCL type A RS may be a CSI-RS in which higher layer parameters related to trs (e.g., trs-Info) and higher layer parameters related to repetition (e.g., repetition) are not configured. Also, the RS corresponding to the QCL type A RS may be configured corresponding to a PCI (e.g., PCI of a candidate cell / additional cell / non-serving cell) different from the PCI of the serving cell (see FIG. 15C). When LTM is configured / applied, RS resource configuration (e.g., CSI-RS resource configuration) for each candidate cell may be supported.

[0178] For example, the reference RS (e.g., TRS / CSI-RS) corresponding to QCL Type A / QCL Type D may further be a CSI-RS having a PCI different from the PCI of the serving cell. That is, as the reference RS (e.g., TRS / CSI-RS) corresponding to QCL Type A / QCL Type D, in addition to (or instead of) the CSI-RS corresponding to the PCI of the serving cell, a CSI-RS having a PCI different from the PCI of the serving cell may be used.

[0179] When LTM is configured / applied, the UE may assume that the pseudo-colocation type of the TCI state (e.g., TCI-State or indicated DLorJointTCIState) indicated by the base station is a CSI-RS of a PCI different from the PCI of the serving cell (e.g., QCL type A) or a CSI-RS of the same type as QCL type A (e.g., QCL type D).

[0180] As an example, Type-A RS and Type-D RS in QCL Rules 1-3 may be defined as follows: Type-A RS is a CSI-RS resource of a non-zero power CSI-RS resource set (e.g., NZP-CSI-RS-ResourceSet) configured without any upper layer parameters (e.g., trs-Info) and upper layer parameters (e.g., repetition), Type-D RS is the same CSI-RS resource as Type-A RS, and the Reference RS may further be a CSI-RS with a PCI different from the PCI of the serving cell.

[0181] In QCL Rules 1-1 to 1-3, the UE may assume that the center frequency, SCS, and SFN offset of an SSB (or SS / PBCH block) from a serving cell and an SSB with a PCI different from that of the serving cell are the same. If inter-cell LTM (e.g., inter-frequency LTM) is not supported, in QCL Rules 1-1 to 1-3, the UE may not assume that the center frequency, SCS, and SFN offset of an SSB (or SS / PBCH block) from a serving cell and an SSB with a PCI different from that of the serving cell are the same.

[0182] (Analysis) Meanwhile, in Rel. 18 LTM, the TCI state of the target cell is included in the MAC CE for the cell switch command, where the TCI state index is selected and signaled from the TCI state previously activated by the MAC CE or the TCI state configured by the RRC.

[0183] As mentioned above, if the TCI state indicated by the MAC CE (indicated TCI state) is not (one of) the previously activated TCI states, the UE utilizes (applies) a longer TCI state switching delay.

[0184] That is, it is assumed that the time until the designated TCI state is applied differs depending on the above-mentioned cases, so it is necessary to consider the direction of application of the TCI state switching delay depending on each case.

[0185] If the application of the TCI state switching delay cannot be controlled appropriately, cell switching may not be performed appropriately, resulting in a decrease in throughput / deterioration in communication quality.

[0186] Therefore, the present inventors have studied methods for applying a TCI state switching delay and have come up with an example of this embodiment.

[0187] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. Note that the following embodiments / aspects (e.g., cases) may be used alone or in combination of at least two of them.

[0188] (Various Alternative Readings, etc.) In the present disclosure, "A / B" and "at least one of A and B" may be interchangeable. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0189] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read interchangeably. In the present disclosure, terms such as support, control, controllable, operate, and operate may be read interchangeably.

[0190] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.

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

[0192] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0193] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.

[0194] In the present disclosure, cell, PCI, serving cell, SpCell, source serving cell (source cell), reference / reference cell, CC, BWP, BWP within CC, and band may be interchangeable. In the present disclosure, additional cell, other cell, non-serving cell, cell with a different PCI, candidate cell, candidate serving cell, cell with a PCI different from the PCI of the current serving cell, another serving cell, target cell, target serving cell, and neighbor cell may be interchangeable. In the present disclosure, switch, change, and update may be interchangeable. Serving cell may be interchangeable with the serving cell before the switch or the serving cell after the switch. LTM application, cell application, and cell switch may be interchangeable. LTM application, beam application, and beam switch may be interchangeable.

[0195] In the present disclosure, RACH resource, RA resource, PRACH preamble, occasion, RACH occasion (RO), PRACH occasion, repetition resource, repetition setting resource, resource configured for RO / repetition, time instance and frequency instance, time resource and frequency resource, RO / preamble resource, repetition, PRACH resource, time / frequency resource for PRACH, preamble setting / index, mask setting / index, PRACH setting may be read as interchangeable.

[0196] In the present disclosure, a candidate cell and a candidate cell group may be interchangeable. A candidate cell in the present disclosure may be a candidate cell indicated in a PDCCH order. A PDCCH order and a DCI (e.g., DCI format 1_0) may be interchangeable. In the present disclosure, an RO, an RO index, and an RO# may be interchangeable.

[0197] The following description may be applied to inter-cell mobility (e.g., L1 / L2 inter cell mobility) or to communication control other than inter-cell mobility. L1 / L2 inter-cell mobility may be interpreted as at least one of cell switching, cell switch, and cell change.

[0198] (Wireless communication method)

[0199] In the present disclosure, in the MAC CE for cell switch command, the UE is instructed to use one or more TCI states (IDs) after cell switch, where the TCI states (IDs) are based on a list of TCI states configured by RRC in the target cell or other cells (serving cell / other candidate cells).

[0200] The NW (gNB) may activate / deactivate the TCI state of one or more candidate cells before a cell switch command.

[0201] An active TCI state in the target cell (the new cell indicated by the cell switch command) may or may not exist.

[0202] Here, different TCI state switching delays may be assumed depending on whether the indicating TCI state is activated or not.

[0203] In the present disclosure, the following cases 1 and 2 may be assumed.

[0204] Case 1: Prior to a cell switch command indicating a target cell, the UE may or may not have an active TCI state in the target cell.

[0205] <Case 2> Before a cell switch command indicating a target cell, the UE must have an active TCI state in the target cell. In this case, the NW (gNB) must activate the TCI state in the target cell before a cell switch command for the target cell.

[0206] The embodiments of the present disclosure can be broadly categorized as follows: First embodiment: A method for determining a TCI state switching delay. Second embodiment: SSB or TRS / CSI-RS as a QCL source in a TCI state. <First embodiment> In the first embodiment, a method for determining a TCI state switching delay will be described. Fig. 16 is a conceptual diagram showing an example of a method for determining a TCI state switching delay according to the first embodiment.

[0207] In switching from the TCI state of a source cell (eg, serving cell) to the TCI state of a target cell, the TCI state switching delay may be determined based on the following equation:

[0208] If the target TCI state is known, when the UE receives a PDSCH carrying (including) a MAC CE activation command in slot n, the UE can receive a UE-dedicated PDCCH / PDSCH in the first slot after the predetermined slot by applying the target TCI state of the serving cell in which the TCI state change occurred.

[0209] Here, the predetermined slot mentioned above is (n+T HARQ +3N slot subframe,μ+TO k *(T first-SSB +T SSB-proc ) / NR slot length)-th slot.

[0210] The UE receives the data in slot (n+T HARQ +3N slot The UE can receive the UE-dedicated PDCCH / PDSCH by applying the old TCI state until the T HARQ is the timing between DL data transmission and acknowledgement.

[0211] Also, ・T first-SSBis the time for the first SSB transmission after the MAC CE to be decoded by the UE. The SSB corresponds to QCL Type A / Type C for the target TCI state. SSB-proc is, for example, 2 ms (milliseconds).

[0212] Also, TO k is 1 if the target TCI state is not in the list of active TCI states of the PDSCH / PDCCH, and 0 otherwise.

[0213] More specifically, TO k is 1 if the target TCI state for the target cell is not in the list of active TCI states of the PDSCH / PDCCH for the target cell / LTM, and 0 otherwise (see Figure 16).

[0214] Here, the list of active TCI states of the PDSCH / PDCCH may be interchangeably read as a list of active TCI states for the indicated TCI state or a list of active TCI states for the unified TCI state.

[0215] If the target TCI state for the target cell is not in the list of active TCI states, the target TCI state for the target cell may be directly activated and indicated by the MAC CE for the cell switch command. In this case, the UE may have to wait for a longer switch delay (TO k =1) can be assumed (see Figure 16).

[0216] If the target TCI state for the target cell is in the list of active TCI states, the target TCI state for the target cell may be activated by an existing MAC CE (e.g., a Rel. 17 MAC CE for unified TCI state or DCI activation / deactivation) and indicated by the MAC CE for the cell switch command before the UE receives the MAC CE for the cell switch command. In this case, the UE may experience a shorter switch delay (TO k =0) can be assumed (see Figure 16).

[0217] In this way, the UE determines the TCI state switching delay (TO) to apply based on whether the target TCI state is in the list of active TCI states (see Figure 16). k =0 / 1).

[0218] In addition, the UE may receive a PDSCH including a MAC CE for a cell switch command in slot n.

[0219] The UE can receive UE-dedicated or UE-common PDCCH / PDSCH by applying the target TCI state of the target cell indicated in the MAC CE for the cell switch command.

[0220] In this disclosure, the TCI state of the target cell may refer to the TCI state setting of the SpCell / serving cell or the TCI state setting of the LTM.

[0221] <Additional Note> At least one of the following options 1 and 2 may be applied to LTM candidate cells on a different frequency: <Option 1> LTM candidate cells on a different frequency from the serving cell may be treated only as unknown cells. <Option 2> New conditions may be defined for LTM candidate cells on a different frequency from the serving cell.

[0222] According to the first embodiment described above, the UE can appropriately determine / judge the TCI state switching delay depending on the case.

[0223] Second Embodiment The second embodiment describes SSB or TRS / CSI-RS as a QCL source in a TCI state.

[0224] In this disclosure, QCL source, SSB, and TRS / CSI-RS may be read interchangeably.

[0225] It is being considered whether to support either SSB or TRS / CSI-RS as a QCL source in the TCI state.

[0226] For example, before the cell switch command, the UE does not need to monitor the TRS / CSI-RS of the candidate cell, however, since the UE has reported the SSB-based L1-RSRP of the candidate cell, it has already measured the SSB for the target cell.

[0227] Therefore, at the time of the cell switch command, the UE has already measured the SSB of the target cell, but has not yet measured the TRS / CSI-RS of the target cell.

[0228] If the SSB can be a QCL source in the TCI state for the DMRS of the PDCCH / PDSCH, the QCL rules described above may be applied.

[0229] As described above, when the UE receives a cell switch command, the UE has not yet measured the QCL source RS corresponding to the TRS / CSI-RS in the TCI state. The following effects may be expected.

[0230] The formula for the TCI state switching delay is not affected, and the TCI state switching delay may be calculated assuming that the indicated TCI state is unknown in the existing specifications. Here, the SSB in the existing specifications may refer to the QCL source SSB of the TRS / CSI-RS. Also, the QCL source SSB of the TRS / CSI-RS may be the QCL source of the DMRS for the PDCCH / PDSCH of the target cell.

[0231] The above means that the UE updates its TCI state assumption after measuring only the root SSB (TRS / CSI-RS QCL source), regardless of whether the UE has measured the TRS / CSI-RS QCL source for DMRS.

[0232] An additional TCI state switching delay may be assumed to allow the UE to measure the QCL source of the TRS / CSI-RS relative to the DMRS. k *(T first-SSB +T SSB-proc) / NR slot length" and when the TCI state is indicated by the MAC CE for the cell switch command, "TO k *(T first-SSB +T SSB-proc ) / NR slot length" is "TO k *(T first-SSB +T SSB-proc ) / NR slot length + T first-CSI-RS +T CSI-RS-proc " or "T first-CSI-RS +T CSI-RS-proc " may be replaced with

[0233] According to the second embodiment described above, the UE can appropriately determine / judge the TCI state switching delay depending on the case.

[0234] <Supplementary Information> [Notification of Information to UE] In the above-described embodiments, any information may be notified to the UE (from a network (NW) (e.g., a base station (BS))) (in other words, reception of any information from the BS by the UE) using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0235] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

[0236] When the notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0237] Furthermore, notification of any information to the UE in the above embodiments may be performed periodically, semi-persistently, or aperiodically.

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

[0239] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID, which is not defined in existing standards, in the MAC subheader.

[0240] If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.

[0241] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.

[0242] [Application of Each Embodiment] At least one of the above-described embodiments may be applied when a specific condition is met. The specific condition may be defined in a standard or may be notified to a UE / BS using higher layer signaling / physical layer signaling.

[0243] At least one of the above-described embodiments may be applied only to UEs that have reported or support a specific UE capability. Note that "supporting" and "whether to support" may be interpreted as interchangeable.

[0244] The specific UE capability may indicate at least one of the following: - Supporting specific processing / operation / control / information for at least one of the above embodiments; - Supporting setting of unified TCI state; - Supporting LTM; - Supporting TRS / CSI-RS being configured as QCL type A / D RS; - Supporting SSB being configured as QCL type A / D RS; - Supporting TCI state switching delay; - Supporting QCL rules for TCI states.

[0245] Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (e.g., one or a combination of a cell, a band, a band combination, a BWP, a component carrier, etc.), or may be a capability for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or may be a capability for each subcarrier spacing (SubCarrier Spacing (SCS)), or may be a capability for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

[0246] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

[0247] Furthermore, at least one of the above-described embodiments may be applied when the UE configures / activates / triggers specific information related to the above-described embodiments (or performs the operations of the above-described embodiments) through higher layer signaling / physical layer signaling. For example, the specific information may be information indicating that LTM is enabled, any RRC parameter for a specific release (e.g., Rel. 18 / 19), etc.

[0248] If the UE does not support at least one of the specific UE capabilities or is not configured with the specific information, the UE may apply, for example, the behavior of Rel. 15 / 16 / 17.

[0249] (Supplementary Notes) The following inventions are supplementary notes regarding an embodiment (first and second embodiments) of the present disclosure. [Supplementary Note 1] A terminal having: a receiver that receives information on a target cell that is a candidate for serving cell switching and information on a transmission configuration indicator (TCI) state; and a controller that determines a TCI state switching delay based on a list of active TCI states included in the information on the TCI states. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the controller applies a longer TCI state switching delay when a target TCI state for the target cell is included in the list compared to when the target TCI state is not included in the list. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the controller applies a predetermined QCL rule as a QCL source for a TCI state for a synchronization signal block. [Supplementary Note 4] The terminal according to any of Supplements 1 to 3, wherein the controller assumes that an indicated TCI state for a target cell having an additional physical cell ID (PCI) is unknown.

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

[0251] 17 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 (which may be simply referred to as system 1) may be a system that realizes communication using Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) specified by the Third Generation Partnership Project (3GPP).

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

[0253] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (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.

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

[0255] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The locations and numbers of the cells and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

[0256] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CCs) and dual connectivity (DC).

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

[0258] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

[0259] The multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

[0260] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

[0261] The core network 30 may include network functions (Network Functions (NF)) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). A single network node may provide multiple functions. Communication with an external network (e.g., the Internet) may also be performed via the DN.

[0262] The user terminal 20 may be a terminal that supports at least one of communication methods such as LTE, LTE-A, and 5G.

[0263] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the wireless communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0264] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (e.g., other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

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

[0266] Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), or the like may be used as an uplink channel.

[0267] The PDSCH transmits user data, higher layer control information, a System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit a Master Information Block (MIB).

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

[0269] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as a UL grant, a UL DCI, etc. Note that the PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.

[0270] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources for searching for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.

[0271] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

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

[0273] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

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

[0275] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.

[0276] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), or the like may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0277] (Base Station) Fig. 18 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

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

[0279] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

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

[0281] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0282] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit. The transmitting unit may be configured from a transmission processing unit 1211 and an RF unit 122. The receiving unit may be configured from a reception processing unit 1212, the RF unit 122, and a measurement unit 123.

[0283] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0284] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0285] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0286] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0287] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0288] The transceiver unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 130.

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

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

[0291] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may 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 may be output to the control unit 110.

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

[0293] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0294] The transceiver 120 may transmit information about a target cell that is a candidate for switching the serving cell and information about a transmission configuration indicator (TCI) state, and the controller 110 may determine a TCI state switching delay based on a list of active TCI states included in the information about the TCI state.

[0295] (User Terminal) Fig. 19 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

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

[0297] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on common understanding in the technical field to which the present disclosure relates.

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

[0299] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0300] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0301] The transmitting / receiving antenna 230 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0302] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0303] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0304] The transceiver unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

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

[0306] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and if not, it may not be necessary to perform DFT processing as the transmission processing.

[0307] The transceiver unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 230.

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

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

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

[0311] The measurement unit 223 may derive channel measurements for CSI calculation based on the channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on the interference measurement resources. The interference measurement resources may be at least one of an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. Note that CSI-IM may be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. Note that in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeably read as interchangeable.

[0312] Note that the transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.

[0313] The transceiver 220 may receive information about a target cell that is a candidate for serving cell switching and information about a transmission configuration indicator (TCI) state. The controller 210 may determine a TCI state switching delay based on a list of active TCI states included in the information about the TCI states. If the target TCI state for the target cell is included in the list, the controller 210 may apply a longer TCI state switching delay than if the target TCI state is not included in the list. The controller 210 may apply a predetermined QCL rule as a QCL source for the TCI state for the synchronization signal block. The controller 210 may assume that the indicated TCI state for a target cell with an additional physical cell ID (PCI) is unknown.

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

[0315] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As described above, the implementation method of each is not particularly limited.

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

[0317] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0318] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

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

[0320] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.

[0321] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.

[0322] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

[0323] Storage 1003 is a computer-readable recording medium and may be composed of at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

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

[0325] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

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

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

[0328] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

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

[0330] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering performed by a transceiver in the frequency domain, and specific windowing performed by a transceiver in the time domain.

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

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

[0333] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0334] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0335] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

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

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

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

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

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

[0341] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may be composed of one or more resource blocks.

[0342] In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

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

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

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

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

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

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

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

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

[0351] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

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

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

[0354] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0355] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0356] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

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

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

[0359] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0360] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "layer," "number of layers," "rank," "resource," "resource set," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," "UE panel," "transmitting entity," "receiving entity," etc. may be used interchangeably.

[0361] In the present disclosure, the term "antenna port" may be interchangeably read as an antenna port for any signal / channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the term "resource" may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time / frequency / code / space / power resources. Furthermore, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0362] The group may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, a Reference Signal (RS) group, a Control Resource Set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, and the like.

[0363] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.

[0364] In addition, in the present disclosure, the terms TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc. may be read interchangeably.

[0365] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

[0366] In the present disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In the present disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.

[0367] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. The "spatial relationship information (TCI state)" may be interchangeable with "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. The TCI state and the TCI may be interchangeable. The spatial relationship information and the spatial relationship may be interchangeable.

[0368] In the present disclosure, terms such as "base station (BS)," "radio 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," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0369] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

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

[0371] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0372] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

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

[0374] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0375] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0376] 21 is a diagram showing an example of a vehicle according to an 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, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air 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.

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

[0378] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (for example, an input / output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0379] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.

[0380] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0381] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

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

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

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

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

[0386] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).

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

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

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

[0390] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc.), or a combination thereof.

[0391] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0392] Each aspect / embodiment described in the present disclosure may be a technology other than 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 (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

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

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

[0395] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0396] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0397] Furthermore, "determination" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "determining" some kind of action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.

[0398] Furthermore, in this disclosure, "determine / determining" may be interchangeably read as "assume / assuming," "expect / expecting," "consider / considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interchangeably read as "assumes not to do...."

[0399] In the present disclosure, "expect" may be interchangeably read as "be expected." For example, "expect(s) ..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected ...." "does not expect ..." may be interchangeably read as "be not expected ...." Furthermore, "An apparatus A is not expected ..." may be interchangeably read as "an apparatus B other than apparatus A does not expect ... from apparatus A" (e.g., if apparatus A is a UE, apparatus B may be a base station).

[0400] The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0401] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0402] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0403] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

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

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

[0406] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with "i-th" (i is an arbitrary integer) attached (for example, "highest" may be interchangeable with "i-th highest").

[0407] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.

[0408] In the present disclosure, terms such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during / while A," "B before A," "B at (the same time as) / on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A, B, and the like herein may be replaced with appropriate expressions such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be approximately zero (immediately after or immediately before). A time offset may also be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after a time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.

[0409] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.

[0410] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The description of the present disclosure is for illustrative purposes only and does not impose any limiting meaning on the invention according to the present disclosure.

[0411] This application is based on Japanese Patent Application No. 2023-133911, filed on August 21, 2023, the contents of which are incorporated herein in their entirety.

Claims

1. A terminal having a receiving unit that receives information regarding a target cell that is a candidate for serving cell switching and information regarding a transmission configuration indicator (TCI) state, and a control unit that determines a TCI state switching delay based on a list of active TCI states included in the information regarding the TCI state.

2. The terminal according to claim 1, wherein the control unit applies a longer TCI state switching delay when a target TCI state for the target cell is included in the list compared to when the target TCI state is not included in the list.

3. The terminal according to claim 1, wherein the control unit applies a predetermined QCL rule as a QCL source of the TCI state for the synchronization signal block.

4. The terminal of claim 1, wherein the control unit assumes that the indication TCI state for a target cell having an additional physical cell ID (PCI) is unknown.

5. A wireless communication method for a terminal, comprising the steps of: receiving information regarding a target cell that is a candidate for switching the serving cell and information regarding a transmission configuration indicator (TCI) state; and determining a TCI state switching delay based on a list of active TCI states included in the information regarding the TCI state.

6. A base station having: a transmitting unit that transmits information regarding a target cell that is a candidate for switching the serving cell and information regarding a transmission configuration indicator (TCI) state; and a control unit that determines a TCI state switching delay based on a list of active TCI states included in the information regarding the TCI state.

Images